Requirements After the Upgrade from 7.0 to P6 EPPM

The following list summarizes the procedures you need to perform after the P6 EPPM upgrade:

Backup Procedures

Oracle recommends that you make a backup of your newly upgraded database.

User Name and Password Procedures

For security reasons, Oracle strongly recommends you replace the default database users' (admuser, privuser, pubuser, bgjobuser, and pxrptuser) passwords immediately after a manual database installation or an upgrade from P6 version 7.0. Do not use special characters in the database name, privileged user, public user, or PX reporting user name, for example: { } [ ] : ; < > , . ? ! @ # $ % ^ & * ( ) - _ | / \ ~ `
For instructions on how to replace the private database login, follow the instructions in Modifying Private Database Logins for P6 EPPM. For all other database user names and passwords, use the tools included with Oracle Database. The background job user has to be reset only for manual installations.
Oracle recommends using strong passwords. Strong passwords in P6 EPPM contain between 8 and 20 characters and at least one numeric and one alpha character. To further strengthen the password, use a mixture of upper and lower case letters.

Application Configuration Procedures

Install the new P6, P6 Professional, and any additional components.
From P6 EPPM Release 8, all recurring job service functions are hosted by P6. Due to this change, after upgrading to P6 EPPM Release 8 or later, you must configure Scheduled Services settings in the Primavera P6 Administrator to use recurring job services. See the P6 EPPM System Administration Guide for more information.
Resummarize all projects to accurately reflect your summary data. See information about configuring a separate server for job services in the P6 EPPM System Administration Guide.
Assign new or modified privileges to users. See information about security profiles in the P6 EPPM Application Administration Guide.
All previously defined module access (except Contributor module access (formerly Team Member), security profiles, OBS access, and resource security settings will still apply to existing users after the database upgrade. For users who had Contributor and P6 Professional module access, they will keep their access during the database upgrade; however, once you edit these users post-upgrade, P6 will remove Contributor module access to comply with current P6 EPPM functionality. The upgrade process will only remove Contributor access during the upgrade if users had Contributor and additional module access assignments other than P6 Professional; all other assignments will remain selected. See the P6 EPPM Application Administration Guide for information on defining module access, security profiles, OBS access, and resource security.
During the upgrade to the latest version of P6 EPPM, some P6 Activity Views settings will reset. After the upgrade, use the Customize Detail Windows feature to modify the settings that should appear for each view. See the P6 Help for information on how to edit Activity Views.
From P6 EPPM Release 8, P6 saves filter definitions globally. Filters still work for Activity Views, but all standard filter assignments are reset during the upgrade process. Views that had standard filters applied prior to upgrade, will no longer have those filters. After the upgrade is completed, re-apply filters to your views. See the P6 Help for information on how to edit Activity Views.

Security Procedures

For security reasons, Oracle strongly recommends that on-premises users replace the default Admin Superuser (admin) immediately after a manual database installation or an upgrade from P6 version 7.0 or earlier. See information on the default Admin Superuser in the P6 EPPM Application Administration Guide for guidelines on this process. See the P6 EPPM Application Administration Guide for information on changing the default admin superuser.

Related Topics