If you haven't done so, download the Primavera P6 Enterprise Project Portfolio Management R8.3 for <platform> folder and extract the contents.
Go to the location of the extracted contents and locate the P6_R8.3\p6suite\database folder.
Note: Make a backup copy of any files you will modify before you edit them.
For Release 8.3.2, execute the following steps:
From the command line, execute: sqlplus sys/password as sysdba
Go to \scripts\install\PM_08_03_00 and execute the manual_script_before_upgrade.sql
If you don’t have a default user, ADMUSER, go to \scripts\install\PM_08_03_00, update the user in the script, and then execute the orpm_grantpriv.sql script.
Log into the database as ADMUSER or use your custom administrative user name if you created one.
Go to \scripts\install\PM_08_03_00 and execute the orpm_init_px.sql script to create a PX tablespace.
Executing this script will create the PMDB_PX_DAT1 tablespace, which will hold PX data.
Note: Modify the tablespace name in this script if you changed the default tablespace name (PMDB_PX_DAT1).
Go to \scripts\install\PM_08_03_00 and execute the orpm_create_plus_users.sql script.
Notes:
Running the orpm_create_plus_users.sql script automatically creates the database user name: PxRptUser. If you created another user name and wish to use that when running P6 EPPM database scripts, replace the PxrRtUser name with your custom user name in all applicable scripts before running them.
Do not use special characters in the database name, privileged user, public user, or PX reporting user name, for example: { } [ ] : ; < > , . ? ! @ # $ % ^ & * ( ) - _ | / \ ~ `
Go to \scripts\install\PM_08_03_00 and execute the orpm_create_bguser_upgrade.sql script.
Go to \scripts\install\PM_08_03_00 and execute the orpm_grantpriv_bguser_upgrade.sql script.
Go to \scripts\common and execute the or_disable_triggers.sql script.
Go to \scripts\upgrade\PM_08_03_00 and execute one of the following scripts:
ORPM_p62.sql, if upgrading from P6 version 6.2.1
ORPM_p621sp1.sql, if upgrading from P6 version 6.2.1 service pack 1
ORPM_p70sp1.sql, if upgrading from P6 version 7.0, 7.0 service pack 1, or 7.0 service pack 2
ORPM_p7.0sp3.sql, if upgrading from P6 version 7.0 service pack 3
ORPM_p70sp5.sql if upgrading from P6 version 7.0 service pack 5
ORPM_p80.sql if upgrading from P6 version 8.0
ORPM_p81.sql if upgrading from P6 version 8.1
ORPM_p81sp3.sql if upgrading from P6 version 8.1 service pack 3
ORPM_p82.sql if upgrading from P6 version 8.2
ORPM_p82sp2.sql if upgrading from P6 version 8.2 service pack 2
ORPM_p82sp2f10.sql if upgrading from P6 version 8.2 service pack 2 Hotfix 10
ORPM_p83.sql if upgrading from P6 version 8.3 or 8.3 service pack 1
Notes:
If you did not execute the orpm_init_px.sql script to create a PX tablespace or you changed the name of the PMDB_PX_DAT1 tablespace, modify all occurrences of PMDB_PX_DAT1 in the upgrade script with the name you used for the tablespace.
If you changed the default privuser name, update the name in this script with your custom user name.
If you're using version ORPM_p70sp1.sql or later, skip to the next step.
If you're using a version before ORPM_p70sp1.sql, go to \scripts\common and execute the or_update_usereng.sql script to grant all users with P6 Professional module access rights to the Projects section in P6.
Note: Prior to P6 version 7.0, users with Project Management module access also had rights to the Projects section in P6 Web Access. For security reasons, beginning with P6 version 7.0, P6 Professional module access only grants rights to log into the P6 Professional module.
Go to \scripts\common and execute the or_post_upgrade script.
Go to \scripts\upgrade\PM_08_03_00 and execute the orpm_grants.sql script.
Note: If you changed the default user names, update the privuser, pubuser, and PxRptUser names in this script with your custom user names.
Go to \scripts\upgrade\PM_08_03_00 and execute the orpm_ctxindex.sql script
Go to \scripts\upgrade\PM_08_03_00 and execute the orpm_dbcrudseq.sql script
Go to \scripts\upgrade\PM_08_03_00 and execute the orpm_synonyms.sql script.
Caution: The orpm_synonyms.sql script contains a table called PUBUSER, do not replace it if you have to change the pubuser user name.
Note: If you changed the default user names, you must update the admuser, privuser, pubuser, and pxrptuser names in this script with your custom user names.
Go to \scripts\source\PM_08_03_00 and execute the orpm_src.plb script.
Go to \scripts\source\PM_08_03_00 and execute the orpm_secpac.sql script.
Note: If you changed the default user names, update the admuser, privuser, and pxrptuser names in this script with your custom user names.
Go to \scripts\source\PM_08_03_00 and execute the orpm_logon_trigger.sql script.
Go to \scripts\install\PM_08_03_00 and execute the orpm_database_version.sql and orpm_querylib.sql scripts.
Go to \scripts\common and execute the or_enable_triggers.sql script.
Run the databaselogins.bat (on Windows) or databaselogins.sh (on Linux) to upgrade the encryption of privilege user passwords.
Log into the database as background job user.
Go to \scripts\install\PM_08_03_00 and execute the orpm_init_bgjobs.sql script.
Log into the P6 EPPM database as PxRptUser or use your custom PX reporting user name.
Follow steps a-c if you changed the default admuser name.
If you did not change the default admuser name, skip a-c and go to the next step.
Go to \scripts\source\PM_08_03_00 and edit the orpm_px_rpt_src.sql script.
Replace the default admuser name with your custom admuser name.
Save and close the script file.
Go to \scripts\source\PM_08_03_00 and execute the orpm_px_rpt_src.sql script.
