Upgrading the P6 EPPM Oracle Database

To upgrade the P6 EPPM Oracle Database:

  1. If you haven't done so, download the Primavera P6 Enterprise Project Portfolio Management <release_level> for <platform> folder and extract the contents.
  2. Go to the location of the extracted contents and locate the P6_<release_level>\p6suite\database folder.

    Note Make a backup copy of any files you will modify before you edit them.

  3. Navigate to the following locations, open the designated scripts in a text editor, and modify the schema user references to match your actual schema user names:
    1. \scripts\install\PM_<release level>\manual_script_before_upgrade.sql

      If you are not using the schema names admuser or pxrptuser, update the references with your actual admuser and pxrptuser names.

    2. \scripts\install\PM_<release level>\manual_script_before_install.sql

      You must apply grant options to the SYSTEM schema user or a custom user associated with the Oracle DBA role. If you plan to use a custom schema user, other than SYSTEM, to complete steps which require a DBA role, then you must update the references to SYSTEM in the script with the new custom schema user associated with the DBA role.

    3. \scripts\install\PM_<release level>\orpm_grant_privileges.sql

      If you are not using the schema names admuser, privuser, bgjobuser, pubuser, and pxrptuser update the references with your actual admuser, privuser, bgjobuser, pubuser, and pxrptuser names.

      Note If you are upgrading from 8.1 or later, you can skip steps d, e, f, and g.

    4. \scripts\install\PM_<release_level>\orpm_create_bguser_upgrade.sql script.

      Modify the tablespace or bgjobuser name in this script if you changed the default tablespace name (PMDB_DAT1) or the default bgjobuser name.

    5. \scripts\install\PM_<release_level>\orpm_init_px.sql

      Modify the tablespace name in this script if you changed the default tablespace name (PMDB_PX_DAT1).

    6. \scripts\install\PM_<release_level>\orpm_create_plus_users.sql

      If you want to create a user without a default name, you need to update pxrptuser with your actual pxrptuser name.

      If you are using a custom admuser name, you need to modify the reference to admuser with your actual admuser name.

      Note Do not use special characters in the database name, privileged user, public user, or PX reporting user name, for example: { } [ ] : ; < > , . ? ! @ # $ % ^ & * ( ) - _ | / \ ~ `

  4. Complete the following steps:
    1. From the command line, run the following and provide the password when prompted: sqlplus sys@<db_tns_names_entry> as sysdba
    2. Go to \scripts\install\PM_<release_level> and run the manual_script_before_upgrade.sql script.
    3. Go to \scripts\install\PM_<release_level> and run the manual_script_before_install.sql script.

      Note If you are upgrading from 8.1 or later, you can skip steps d, e, f, and g and then continue to step h.

    4. Go to \scripts\install\PM_<release_level> and run orpm_create_bguser_upgrade.sql script.
    5. Go to \scripts\install\PM_<release_level> and run orpm_init_px.sql script.
    6. Go to \scripts\install\PM_<release_level> and run orpm_create_plus_users.sql script.
    7. Go to \scripts\install\PM_<release_level>, update the user in the script, and then run the orpm_grant_privileges.sql script.
  5. Complete the following steps:
    1. From the command line, run the following and provide the password when prompted: sqlplus <admuser>@<db_tns_names_entry>
    2. Go to \scripts\common\PM_<release_level> and run the or_disable_triggers.sql script.
    3. Go to \scripts\upgrade\PM_<release_level> and run the script closest to the version of P6 EPPM that you are trying to upgrade. For example:
    • 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 patch set 2 Hotfix 10
    • ORPM_p83.sql, if upgrading from P6 version 8.3
    • ORPM_p832.sql, if upgrading from P6 version 8.3 or 8.3 service pack 2
    • ORPM_p833.sql, if upgrading from P6 version 8.3 or 8.3 service pack 3
    • ORPM_p834.sql, if upgrading from P6 version 8.3 or 8.3 service pack 4
    • ORPM_p835.sql, if upgrading from P6 version 8.3 or 8.3 service pack 5
    • ORPM_p84.sql, if upgrading from P6 version 8.4 or 8.4 patch set 1
    • ORPM_p841.sql, if upgrading from P6 version 8.4 or 8.4 patch set 1
    • ORPM_p843.sql, if upgrading from P6 version 8.4 or 8.4 patch set 3
    • ORPM_P151.sql, if upgrading from P6 version 15.1
    • ORPM_P152.sql, if upgrading from P6 15 R2
    • ORPM_P161.sql, if upgrading from P6 16 R1
    • ORPM_P162.sql, if upgrading from P6 16 R2

      Note

      • If you did not run 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.
  6. Complete the following steps:
    1. From the command line, run the following and provide the password when prompted: sqlplus <admuser>@<db_tns_names_entry>
    2. Go to \scripts\source\PM_<release_level> and run the orpm_admuser_upgrade.sql script.
  7. Complete the following steps:
    1. From the command line, run the following and provide the password when prompted: sqlplus <privuser>@<db_tns_names_entry>
    2. Go to \scripts\source\PM_<release_level> and run the orpm_privuser.sql script.
  8. Complete the following steps:
    1. From the command line, run the following and provide the password when prompted: sqlplus <pxrptuser>@<db_tns_names_entry>
    2. Go to \scripts\source\PM_<release_level> and run the orpm_pxrptuser.sql script.
  9. Complete the following steps:
    1. From the command line, run the following and provide the password when prompted: sqlplus <system>@<db_tns_names_entry>

      Note If you changed the system username to a custom dba user in step 3b, you need to run orpm_reset_priv.sql as the custom dba user instead of the default system user.

    2. Go to \scripts\install\PM_<release_level> and run the orpm_reset_priv.sql script.
  10. Run the databaselogins.bat (on Windows) or databaselogins.sh (on Linux) to upgrade the encryption of privilege user passwords.

Last Published Monday, December 8, 2025