NOTE: The schema validation utility requires admuser to have full DBA rights to function with an Oracle database. If logging in with ‘admuser’ (to Oracle) and Schema Validation crashes, please ask the Database Administrator to make sure that ‘admuser’ is assigned the DBA Role.

1. Download the following file: P5database.zip
   
   These files are the database files for 5.0 SP4/5 but the Schema validation utility is backwards compatible.
    


2. Unzip the file to a location on a local hard drive.
    


3. Open Windows Explorer and navigate to the \database folder created inside the folder used in Step 2.
    


4. Refer to the steps below, begin with Step 3.

If using the Validate Schema tool from Primavera 5.0 base release CD’s:

1. Insert: “CD 1″.
    


2. Open: Windows Explorer and navigate to following subfolder on CD 1:  \install\database
    


3. Run: ValSch.exe
    


4. Select the correct RDBMS type (Oracle, SQL Server or Interbase)
    
       
   
   
    


5. Complete the Login dialog box.  The Username and Password are the schema owner (Oracle default is Admuser, SQL default is Privuser).  Click: Connect
    


6. Set the schema preferences:
   
   Select the correct schema type.  (‘PM’ vs ‘MM’)
   

   IMPORTANT: Use the pull-down menu to set the ‘Choose Schema’ selection. 
   This would be identical to the ’Database Version Label is’ value. 
    
   




7. Click: Run

NOTE: The default configuration entries for a standalone installation are localhost\primavera for the server host name and PMDB$primavera for the database name.

FIX 1:
Click back to the Database Configuration and correct the database name.

CAUSE 2:
Connecting to an existing MSDE instance and there were no network protocols enabled for the MDSE instance.

FIX 2:  
Enable the TCP/IP and Named Pipes in SQL Server Network Utility:

1. Click Start, and then click Run.


2. In the Run dialog box, type Svrnetcn in the Open box, and then click OK. 
   
   
   
    Note:  By default, the Svrnetcn.exe file is available in the following folder: 
    Installation Drive/Program Files/Microsoft SQL Server/80/Tools/BINN
    


3. Click OK.


4. In the Server Network Utility dialog box, click the General tab.
   
   
   
    


5. Select your instance of Microsoft SQL Server 2000 Desktop Engine (Windows) or select your instance of MSDE 2000 SP3a or SQL Server 2000 from the Instance(s) on this server list.


6. In the Disabled Protocols list box, select TCP/IP, and then click Enable.


7. Again in the Disabled Protocols list box, select Named Pipes, and then click Enable. 
   
   
    


8. In the Enabled Protocols list box, select TCP/IP, and then click Properties.
   
   
   
    


9. In the <Server Name> – TCP/IP dialog box, type 1433 in the Default Port box (or any unused port) , and then click OK.


10. In the Server Network Utility dialog box, click OK.
    Note:   You may receive a message that states that the changes made will be saved but the changes will take effect only after you restart the SQL Server service. 


11. In the Server Network Utility message box, click OK.


12. Restart the windows service of MSDE or SQL Server 2000 via Control Panels > Administration Tools > Services    (MSSQL$PRIMAVERA) 

FIX 3:
Disable the firewall setting on the XP machine (ensure the machine has other anti-virus/firewall software) which has the MSDE database installed. You will then find the connection will be successful.

FIX 4:
Replace ‘localhost’ with the actual machine name in the db alias connection information

FIX 5:
Enter the server name correctly.  (Example: “localhost\primavera”)

1. GoTo Start, Run and type “cmd” and hit <Enter>


2. At the command prompt, type: “osql -U sa -P prima -S localhost\primavera” and hit <Enter>


3. At the 1> prompt, type: “select name from sysdatabases” and hit <Enter>


4. At the 2> prompt, type: “go” and hit <Enter>


5. This will return a list of all databases on the server.  If databases were created successfully, you should see “pmdb$primavera” and “mmdb$primavera”

FIX 6:
Run ConfigAsst.exe from CD1 to create databases:  (See admin guide pg. 36)

FIX 7:
Start the database windows service for the MSSQL instance

Set the service to Automatic so it will restart after a shutdown of the machine.

If running full SQL 2000, Authentication setting is set to “Windows Only”. 

FIX 8:

Within Enterprise Manager, right click on servername, go to “Properties”.  On Security tab, set Authentication to “SQL Server and Windows”

The SQL port was changed on the server and either: 1.) the new port is not dynamcially resolving, or 2.) there is already a static port specified on the client machine.

FIX 9:  (to be done from the machine that can’t connect to the database)

1. Click: Start, Run.


2. Type: cliconfg, Click: OK.


3. In the SQL Server Client Network Utility, click: ‘Alias’ (tab)


4. If an alias is already defined, and its name matches the server name being used while configuring a Primavera Project Management connection, adjust the port number and close.  Otherwise, proceed to the next step:
    


5. Click: ‘Add’ (button), TCP/IP.


6. Type a name in ‘Server alias’.


7. ‘Server name’ must match the database location.
   NOTE: Specify the instance name, if there is one.


8. ‘Dynamically determine port’ should NOT be checked.


9. ‘Port number’ must match the new port of the SQL Service.


10. Click: OK, Apply, OK.

The application was installed using the “Client Applications” whereas the intention was to install the Stand-alone version of the software, which installs a database locally for the client to connect to.

FIX 10:

Uninstall the software and re-install, choosing Stand-alone rather than Client applications

The client machine and database server are on different domains.

FIX 11:

Use the Database Server’s IP address, when prompted for ‘Host Name’.

The SQL Database Server TCP port was changed and the Server was never restarted.

FIX 12:

Restart the SQL Server.

NOTE: The default configuration entries for a standalone installation are localhost\primavera for the server host name and PMDB$primavera for the database name.

FIX 1:
Click back to the Database Configuration and correct the database name.

CAUSE 2:
Connecting to an existing MSDE instance and there were no network protocols enabled for the MDSE instance.

FIX 2:  
Enable the TCP/IP and Named Pipes in SQL Server Network Utility:

1. Click Start, and then click Run.


2. In the Run dialog box, type Svrnetcn in the Open box, and then click OK. 
   
   
   
    Note:  By default, the Svrnetcn.exe file is available in the following folder: 
    Installation Drive/Program Files/Microsoft SQL Server/80/Tools/BINN
    


3. Click OK.


4. In the Server Network Utility dialog box, click the General tab.
   
   
   
    


5. Select your instance of Microsoft SQL Server 2000 Desktop Engine (Windows) or select your instance of MSDE 2000 SP3a or SQL Server 2000 from the Instance(s) on this server list.


6. In the Disabled Protocols list box, select TCP/IP, and then click Enable.


7. Again in the Disabled Protocols list box, select Named Pipes, and then click Enable. 
   
   
    


8. In the Enabled Protocols list box, select TCP/IP, and then click Properties.
   
   
   
    


9. In the <Server Name> – TCP/IP dialog box, type 1433 in the Default Port box (or any unused port) , and then click OK.


10. In the Server Network Utility dialog box, click OK.
    Note:   You may receive a message that states that the changes made will be saved but the changes will take effect only after you restart the SQL Server service. 


11. In the Server Network Utility message box, click OK.


12. Restart the windows service of MSDE or SQL Server 2000 via Control Panels > Administration Tools > Services    (MSSQL$PRIMAVERA) 

FIX 3:
Disable the firewall setting on the XP machine (ensure the machine has other anti-virus/firewall software) which has the MSDE database installed. You will then find the connection will be successful.

FIX 4:
Replace ‘localhost’ with the actual machine name in the db alias connection information

FIX 5:
Enter the server name correctly.  (Example: “localhost\primavera”)

1. GoTo Start, Run and type “cmd” and hit <Enter>


2. At the command prompt, type: “osql -U sa -P prima -S localhost\primavera” and hit <Enter>


3. At the 1> prompt, type: “select name from sysdatabases” and hit <Enter>


4. At the 2> prompt, type: “go” and hit <Enter>


5. This will return a list of all databases on the server.  If databases were created successfully, you should see “pmdb$primavera” and “mmdb$primavera”

FIX 6:
Run ConfigAsst.exe from CD1 to create databases:  (See admin guide pg. 36)

FIX 7:
Start the database windows service for the MSSQL instance

Set the service to Automatic so it will restart after a shutdown of the machine.

If running full SQL 2000, Authentication setting is set to “Windows Only”. 

FIX 8:

Within Enterprise Manager, right click on servername, go to “Properties”.  On Security tab, set Authentication to “SQL Server and Windows”

The SQL port was changed on the server and either: 1.) the new port is not dynamcially resolving, or 2.) there is already a static port specified on the client machine.

FIX 9:  (to be done from the machine that can’t connect to the database)

1. Click: Start, Run.


2. Type: cliconfg, Click: OK.


3. In the SQL Server Client Network Utility, click: ‘Alias’ (tab)


4. If an alias is already defined, and its name matches the server name being used while configuring a Primavera Project Management connection, adjust the port number and close.  Otherwise, proceed to the next step:
    


5. Click: ‘Add’ (button), TCP/IP.


6. Type a name in ‘Server alias’.


7. ‘Server name’ must match the database location.
   NOTE: Specify the instance name, if there is one.


8. ‘Dynamically determine port’ should NOT be checked.


9. ‘Port number’ must match the new port of the SQL Service.


10. Click: OK, Apply, OK.

The application was installed using the “Client Applications” whereas the intention was to install the Stand-alone version of the software, which installs a database locally for the client to connect to.

FIX 10:

Uninstall the software and re-install, choosing Stand-alone rather than Client applications

The client machine and database server are on different domains.

FIX 11:

Use the Database Server’s IP address, when prompted for ‘Host Name’.

The SQL Database Server TCP port was changed and the Server was never restarted.

FIX 12:

Restart the SQL Server.

Error: Unable to resolve privileged username and password

Failed Logon:com.jnetdirect.jsql.u:

TCP/IP connection failed to host:java.net.ConnectException: Connection refused.

connect url:jdbc:JSQLConnect://localhost:1433/database=PMDB

Error: Unable to resolve privileged username and password

Failed Logon:com.jnetdirect.jsql.u:

TCP/IP connection failed to host:java.net.ConnectException: Connection refused.

-or-

An unchecked buffer exists in an encryption function.  A buffer overrun can occur as a result and can be used to either cause the SQL Server service to fail, or to cause code to run in the security context of the server that is running SQL Server.

For more information about this problem, please refer to the following URL

http://support.microsoft.com/kb/322853/en-us

http://www.microsoft.com/downloads/details.aspx?FamilyID=9552d43b-04eb-4af9-9e24-6cde4d933600&displaylang=en

http://www.microsoft.com/technet/prodtechnol/sql/2000/downloads/servicepacks/sp3.mspx

1.  Ensure that you have a full and current backup of the Project Management database.

2.  Run the following query against the database (substituting the name of the admuser in the PMDB schema if necessary).  Please be aware that any rows returned from that query are orphaned task records.

select * from admuser.task where proj_id not in (select proj_id from admuser.project);

3.  If the users of the Project Management software feel that their projects are complete and are working correctly, delete the orphaned records, using the following SQL statement:

delete from admuser.task where proj_id not in (select proj_id from admuser.project);

To resolve this issue with Interbase:

1.  Make a backup of the database.

2.  Open the Interbase Console by going to Start, Programs, Interbase, Interbase Console.

3. Log into the Interbase Console by right clicking the local server and selecting login.  Enter sysdba as your username and masterkey as your password.

4.  Expand the local server, right click database and select register.  When the box comes up select the location of your gdb file, and again enter sysdba and masterkey as the username and password.

5.  Go to the Tools menu, and select Interactive SQL.

6.  Enter the following line into the command window:

7.  Run a delete statement to get rid of the task_id’s for the invalid proj_id’s:

Delete from Task where task_id = <task_id that was returned in the previous select statement>;

    delete all the task_id’s that came back from the select statement

8.  Go to the Transactions menu, and choose Commit.

You will now be able to upgrade the database.

ex: DELETE FROM ADMUSER_1.PROJISSU WHERE PROJ_ID = :PROJ_ID and (WORKSPACE_ID IS NOT NULL)

Enabling Server Roles for privuser has the effect of changing the logical delete views used by Privuser to filter out logically deleted records from displaying in the application. 

Missing Logical Delete Views could also cause the application to look directly at the physical tables.

The “PRIVATE” database User is incorrectly configured as ADMUSER, rather PRIVUSER.

If ADMUSER is accessing the tables it looks DIRECTLY at the table and sees ALL records including logically deleted records.
If PRIVUSER is accessing the tables it uses the privuser VIEWS of the table that filter out the logically deleted records.

Multiple PMDB Schemas located in the same Oracle Instance.  PRIVUSER has GRANT SELECT, INSERT,UPDATE, DELETE for all tables in both schemas. 

Fix 1:

Make sure, in SQL Server Enterprise Manager, that security logins privuser and pubuser are not granted Server Roles.

To verify and correct this issue:

1. Log into SQL Server Enterprise Manager as an administrator.
    


2. Expand the Security folder and highlight Logins.
    


3. Right click on Privuser and select Properties.
   
   
    


4. Go to the Server Roles tab and uncheck ALL boxes for server roles:
   
   
    

See also Solution ID prim44013 - What roles and rights should PRIVUSER and PUBUSER have for Microsoft SQL Server?

Run Schema Validation to check for missing Logical Delete Views. Recreate missing logical delete views with the statements found in the create scripts in the install\database\scripts directory for the type of database being used.

SEE ALSO: prim29487 - ”How to validate a PMDB / MMDB database schema?”

Administer Private database logins to change the DB User to the ‘privuser’ User account.

SEE ALSO: Solution ID prim24867 - ”How to administer the private database logins username and password”  for instructions on changing the private database login.

Revoke the SELECT, INSERT, UPDATE, DELETE privilege for PRIVUSER for the incorrect schema. 

FOR EXAMPLE:

Schema1′s Users  – ADMUSER, PRIVUSER and PUBUSER. ( Correct Schema )

Schema2′s Users – ADMUSER_1, PRIVUSER_1 and PUBUSER_1. ( Incorrect Schema )

REVOKE SELECT, INSERT, UPDATE, DELETE ON ADMUSER_1.ACCOUNT to PRIVUSER;

The revoke statement needs to run for every table in the schema.  You can use the ordp_grn.sql script found on CD1 in the  \install\database\scripts\install\or\drop\pmdb directory.

This script will need to be edited to add the schema owner (admuser_1.) before the name of each table. 

The PRIVUSER will still have the SELECT, INSERT, UPDATE, DELETE privilege on the ADMUSER SCHEMA. 

To resolve this, an Oracle DBA is required to extend the tablespace size in order to write more data into it. The following command can be used to extend the tablespace size.

To confirm the server is installed, go to Start/Settings/Control Panel/Administrative Tools/Services and look for ‘InterBase Server’. 

Confirm the status is ‘Started’.

If the server is not installed, it may be installed from a 4.x CD.  This can be found in the Install/Database/interbase folder. 

Launch the ibinst.exe to install InterBase Server.

For instructions on how to use Configasst.exe to upgrade, refer to:

“How do I upgrade a standalone Interbase 4.1 database (GDB) to standalone MSDE 5.0 using ConfigAsst.exe?” 

NOTE:  When upgrading an Interbase database, the upgrade wizard automatically names the new MSDE database PMDB$Primavera.  If that database already exists, the upgrade will not be successful.  To rename the existing PMDB$Primavera database to a new name, please refer to:

“‘Database PMDB$Primavera exists on server’ when upgrading to Primavera 5.0″ 

Also, please confirm that the database name is correct as this error is generated when an incorrect database name is entered.

How to install the Interbase Server

A database alias is a pointer that provides information to Project Management, Portfolio Analysis (only available with 5.0) or Methodology Management as to what type of database to access and where the database is located.

Creating an alias:

1.  Launch Project Management, or Methodology Management.
2.  In the Database field, click on the Ellipse button. 

3.  Click Add. (To update or reconfigure an existing alias, highlight the Alias and select Configure.)

4.  Enter an Alias name in the Database Alias field and select the database type in the Driver Type field. 

     Alias names can be almost any name, the default alias “PMDB” is typically configured to connect to a “PMDB$Primavera” default database.\

     Some descriptive alias names that people have used are things like ( local, laptop, server, server1, server2 ) where the alias is intended to descriptively identify a specific database.

     Others simply make the alias name match the database name     

     Valid driver options are Oracle or Microsoft SQL Server

      

5a.  If you select Oracle, type the Oracle connect string.

      




5b.  If you select Microsoft SQL Server, type the Host Name (server machine name) and database name.




NOTE: If you are connecting to a SQL database in a non-default instance, enter SERVER_NAME\INSTANCE_NAME.  The default instance name created for a Primavera 5.0/6.0 Stand-alone installation is “PRIMAVERA” so you would enter  <SERVER_NAME>\PRIMAVERA.

The default Host Name for Primavera 5.x/6.x Stand-alone installation is localhost\primavera  (Note: When trying to connect to a standalone database on a machine that does not have a network cable plugged in, ‘localhost’ is not recognized as a valid replacement for the machine name.  Therefore, replace ‘localhost’ with the actual machine name).




The default Database name for Primavera 5.x/6.x Stand-alone installation is PMDB$PRIMAVERA




    




7.  Click Next and enter pubuser (Default) as the Username and Password for the Public logon info.  Enter your specific Public Login Information if the public username/password has been changed.




    




8.  Click Next, then Next again to test the connection.   Click Finish to complete the wizard.  Then click Select to choose the new database connection and then login to the database.  
     The default application user for a standalone installation is admin for username and password.

MSDE and the Client Applications got installed but the PMDB and MMDB databases failed to install.

Missing registry entries for DBExpress.

There is an updated DBExpress SQL Server driver. 

1. Click Here to download the latest SQL Server / MSDE DBExpress driver.  Save to the Windows Desktop, then unzip the file and copy the dbexpsda.dll file into the c:\windows\system32 folder.

2. Cold boot the machine to register the new driver.

3. Run configasst.exe and create the databases manually.

4. Run dbconfig to configure the aliases to connect the database to the client applications and test.

NOTE:  This Enhancement Request is for the creation of versions equipped with a Primavera 5.0 user interface and related options.

Workarounds:

• prim46035 - “How to backup and restore a Primavera 5.0 database, running on MSDE 2000 (stand-alone)?”
  
  (OR)
   


• prim14224 - “How to backup / restore a Primavera Contractor 4.1 Database?”

Alternative Solution:

  http://teratrax.com/tdm/download.aspx

2. Add the address of the primavera database to the database engine server location. (right click and select add server option. Type the address 搇ocalhost\primavera?

3. Go to the Database node on the GUI and locate the PMDB database which should be could pmdb$primavera.

4. Open the Query Analyser tool and run the backup script or click on the backup database button.

SQL SERVER DEADLOCKS:

*****************************************************

*EXCEPTIONREPORT*

*****************************************************

Date:3/2/2006 10:16:48 AM

Executable:PM.exe

Application:Primavera Project Management

Event Code:PRMDB-1755-6

Message:

PRM DBAccess Error: SQL Server Error: Transaction

(Process ID 223) was deadlocked on lock resources with

another process and has been chosen as the deadlock

victim. Rerun the transaction.

Context:

1: TfrmLogin.FormCreate

2:

3:

4:

5:

6:

7:

8:

9:

10:

Detail:

Type:EprmDBSQLExecutionFailure

Object Type: TCDBEdit

A deadlock is much like an infinite loop:  If you let it go, it will continue until the end of time, until your server crashes, or until the power goes out (whichever comes first).

Fortunately, SQL Server has a built-in algorithm for resolving deadlocks.  It will choose one of the deadlock participants and roll back its transaction.  From this it will display a message, like the Event Code Received.

Go into Edit, User Preferences, Startup Filters – which defaults to Current Project Data Only:

Change the preference on all Project Management Client Machines to ‘View all data (no filter):

The last step is to modify the PM.ini, the default location is C:\Program Files\Primavera\Project Management,

under the [DATABASE] section, add the following parameters:
allowdirtyreads=true

That is,  importing from privuser  to privuser1,  the synonms are created for privuser1 however the synonyms point to the admuser tables.  

NOTE: Even though the synonyms are not pointing to the desired tables, they do exist so ValSchema will not report these are errors.

- Synonyms must be dropped for privuser and pubuser using the ordp_syn.sql provided on CD1:\install\database\scripts\install\or\drop\pmdb  MODIFIED FOR YOUR SCHEMA USERS
example script:  ordp_syn_pub1priv1.sql

- Then synonyms and grants must be recreated by modifying the SQL statements for creating synonyms and grants in the manual oracle create script on CD1\install\database\scripts\install\or\orpm_ins.sql    MODIFIED FOR YOUR SCHEMA USERS

example script: new_syngrnt_priv1.sql

SQLSE-1751-A error

SQL Server Error: ORA-06550: line 1, column 7:

PLS-00306: wrong number or types of arguments in call to ‘CASCADE_DELETE’orde

ORA-06550: line 1, column 7:

PL/SQL: Statement ignored

Session -1 — privuser (PM.exe) — Cp1252 — 2064-6C66-10.49.198.104

DB Connection oracle.jdbc.driver.OracleConnection@21447f

Request type: GET_SP_RESULT

Command text: CASCADE_DELETE

Parameter count: 14

0 — INPUT — String = UDFTYPE

1 — INPUT — String = 286

2 — RESULT — Integer = 0

3 — RESULT — String =

4 — INPUT — String =

5 — INPUT — String =

6 — INPUT — String =

7 — INPUT — String = UDFTYPE

8 — INPUT — String = 286

9 — RESULT — Integer = 0

10 — RESULT — String =

11 — INPUT — String =

12 — INPUT — String =

13 — INPUT — String =

Block count: 0

Total data size: 0 bytes (before compression)

Total job time spent to push in the queue: 0 ms

Total job time: 0 ms (not including compression)

Purge Deletes failed with the following error: CLEANUP_LOGICAL_DELETES Error: SQL Server Error: ORA-06550: line 1, column 7:

PLS-00306: wrong number or types of arguments in call to ‘CLEANUP_LOGICAL_DELETES’

ORA-06550: line 1, column 7:

PL/SQL: Statement ignored

Session -1 — privuser (PM.exe) — Cp1252 — 2064-6C66-10.49.198.104

DB Connection oracle.jdbc.driver.OracleConnection@21447f

Request type: GET_SP_RESULT

Command text: CLEANUP_LOGICAL_DELETES

Parameter count: 8

0 — INPUT — Integer = 0

1 — RESULT — Integer = 0

2 — RESULT — String =

3 — INPUT — Integer = 1

4 — INPUT — Integer = 0

5 — RESULT — Integer = 0

6 — RESULT — String =

7 — INPUT — Integer = 1

Block count: 0

Total data size: 0 bytes (before compression)

Total job time spent to push in the queue: 0 ms

Total job time: 0 ms (not including compression)

NOTE:  This message only appears when connecting to the PM database using compression server.  It does not appear when connecting directly to the PM database using the Oracle client (no compression server).

Run the following queries through sqlplus under a DBA account.(ex. SYS)

Choosing  “click here” displays the following error window:

Error signature
AppName: pm.exe  AppVer: 4.1.5000.2 ModName: kernel32.dll

IN VERSION 5.0:

Error signature
AppName: pm.exe  AppVer: 5.0.4.00.36 ModName: kernel32.dll

The following error window also displays:

“Application Error
Eception EDBEngineError in modul PM.exe at XXXXXXXX.
General SQL error.
database file appears corrupt (cannot find BLOB page (201)).” 

The Event View application log may have a message similar to the following:

Event Type:Error

Event Source:Application Error

Event Category:None

Event ID:1000

Date:3/21/2006

Time:3:13:27 PM

User:N/A

Computer:        Computer_name

Description:

Faulting application pm.exe, version 4.1.1000.62, faulting module kernel32.dll, version 5.1.2600.2180, fault address 0x0001eb33.

To correct:

For Interbase: 

Launch the Interbase Console, connect to the database in question and login as sysdba/masterkey.
The default file location for the Interbase database file is C:\Program Files\Primavera\database\PM\pmdb.gdb.

OR

For MSDE

Login to OSQL: 

OSQL 朥 sa 朠 prima 朣 <server>\primavera 杁 pmdb$primavera

Then run the following script to fix the problem.

Update userdata set user_data = null where topic_name = ‘pm_settings’ and user_id in (select user_id from users where user_name = ‘admin’)

Now what you need is an export of a registry key which stores the public login information (pubuser).  In the registry go to HKEY_LOCAL_MACHINE\Software\Primavera\5.0\Databases\PM\Aliases\PMDB (or other alias name if you changed from default).  Export the registry key with the name of your alias. 

Now on the machines you will be bringing these configurations to, place the copied DBXConnections.ini on top of the one that is already there, and import the registry key to overwrite the one that is there from the initial install.