Solution ID: prim80823
Unable to run Claim Digger / Update Baseline in P6.2.1
Status: Reviewed
Version(s): 6.2.1

Problem: Unable to run Claim Digger on SQL 2005 listening on non-default port.
Problem: Unable to run Claim Digger OR Update Baseline using Oracle Instant Client
Problem: Help, About Primavera (System tab) shows an incorrect JDBC Connection URL
Cause: SQL Server 2005 default Port is 1433, another port is being used.
Cause: Oracle Instant Client is being used to connect to Project Management
Fix:

A new record can be added into the SETTINGS table that will override the JDBC URL found in Help, About Primavera window.  See the examples below:


SQL Server:



INSERT into SETTINGS (namespace, setting_name, setting_value) values (‘Administrator_Settings’, ‘JdbcConnectionURL’, ‘jdbc:sqlserver://<server_name>:<port>;database=<db_name>;’);


<server_name> = SQL Server Machine Name
<port> = SQL Listening Port
<db_name> = Project Management Database Name


Oracle:



INSERT into SETTINGS (namespace, setting_name, setting_value) values (‘Administrator_Settings’, ‘JdbcConnectionURL’, ‘jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<host_name>)(PORT=<port>)))(CONNECT_DATA=(SID=<sid>)))’);


<host_name> = Oracle Server Machine Name
<port> = Oracle Listening Port
<sid> = Oracle Instance Name