Oracle Primavera Global Business Unit

Three Bala Plaza West
Suite 700
Bala Cynwyd, PA 19004 USA
Customer Support: http://www.primavera.com/point/

Release Notes

Oracle Primavera Version 9.0sp1c

General Availability September 11, 2009

Note: This patch is supported with 9.0sp1. 9.0sp1 must be installed prior to this patch installation.

IMPORTANT: This patch contains resolution of a specific defect, or defects, as outlined in the Changes section of this readme. The patch is intended as an emergency repair until the same defect is resolved in the next regularly scheduled release. The patch has been tested and verified for the documented defect resolutions only. Full regression testing has not been applied. Please keep this in mind when determining whether or not to apply this patch.

Changes in this Release

NOTE: ‘POINT-#######’ refers to the customer POINT incident number

Changes in the 9.0sp1b Release

NOTE: ‘POINT-#######’ refers to the customer POINT incident number

Changes in the 9.0sp1a Release

NOTE: ‘POINT-#######’ refers to the customer POINT incident number

Applying This Patch:

9.0sp1c patch is delivered as a ZIP file.

On the Primavera Core Server:

1. Expand the archive into a new directory. For information on WinZip or zip, refer to the associated documentation.
   
2. If running, stop the existing Primavera 9.0sp1 core application server.
   
3. Copy the contents of the Primavera directory (created when you expanded the archive file) into the root of your Primavera server installation, adding and replacing files. If you are prompted whether to overwrite files, click Yes.
   
4. Execute the \Primavera\utils\database\[mssql or oracle] version of the setupSSviews.bat file, using the following syntax:
   
   • For Oracle:
     

     setupSSviews.bat <Database_Alias> <User_ID> <Password>
where:
     

     • <Database_Alias> is the name of the alias that points to the database instance that stores the Primavera core schema (PVDB).
       
     • <User_ID> is the ID of the account that owns these tables (for example, PVDB).
       
     • < Password> is the password of the owner account.
     
     
   • For MSSQL:
     

     setupSSviews.bat <Database_Server_Name> <Database> <User_ID> <Password>
where:

     
     
     • <Database_Server_Name> is the name of the database server instance (typically, this is the name of the computer hosting MS SQL Server).
       
     • <Database> is the name of the database that stores the Primavera core schema (PVDB).
       
     • <User_ID> is the ID of the account that owns these tables (for example, PVDB).
       
     • <Password> is the password of the owner account.
   
   
5. If you are using Actuate Reports against the Primavera application, from the \Primavera\utils\database\[mssql or oracle] directory, run populateReportingTables.bat file, using the following syntax:
   
   • For Oracle:
     

     populateReportingTables.bat <Database_Alias> <User_ID> <Password>
where:
     

     • <Database_Alias> is the name of the alias that points to the database instance that stores the Primavera core schema (PVDB).
       
     • <User_ID> is the ID of the account that owns these tables (for example, PVDB).
       
     • < Password> is the password of the owner account.
     
     
   • For MSSQL:
     

     populateReportingTables.bat <Database_Server_Name> <Database> <User_ID> <Password>
where:

     
     
     • <Database_Server_Name> is the name of the database server instance (typically, this is the name of the computer hosting MS SQL Server).
       
     • <Database> is the name of the database that stores the Primavera core schema (PVDB).
       
     • <User_ID> is the ID of the account that owns these tables (for example, PVDB).
       
     • <Password> is the password of the owner account.
   
   
6. If you are using Primavera Delivery Manager, from the \Primavera\utils\database\mssql\DM directory, run upgradeDMDB.bat using the following syntax:
   

   upgradeDMDB.bat <Database_Server_Name> <Database> <User_ID> <Password>
where:
   

   • <Database_Server_Name> is the name of the database server instance (typically, this is the name of the computer hosting MS SQL Server).
     
   • <Database> is the name of the database that stores the DM schema.
     
   • < User_ID> is the ID of the account that owns these tables.
     
   • <Password> is the password to the owner account.
   
   
7. Restart the Primavera application server.

The Primavera application is now upgraded.

Primavera API:

1. In a web browser, start the Primavera web client (http://host.domain.com/primavera/web) and open the Options page.
   
2. In the Install Client Components pane of the page, click Primavera API Client Components: Install and follow the setup screen to install the API Client.
   
3. Follow the instructions related to the Microsoft Excel add-in to re-install the required files.

The Primavera API is now upgraded.

On the Primavera Standalone Import Connector Host:

Note: Any existing or future 9.0sp1 installation of Standalone Import Connector on individual workstations must be updated with the following steps.

1. Stop the Primavera Standalone Import Connector server if its running.
   
2. Expand the archive into a new directory. For information on WinZip or zip, refer to the associated documentation.
   
3. Copy ptsserverpatch.jar from the \Primavera\lib directory (created when you expanded the archive) into the \lib directory of your Primavera standalone import connector installation.

The Primavera Standalone Import Connector is now upgraded.