Requirements After the Upgrade from Version 6.2.1 through 7.0 to 16 R2
The following list summarizes the procedures required and recommended to perform AFTER upgrading P6 EPPM:
User Name and Password Procedures
- For security reasons, Oracle strongly recommends that 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 and earlier. Do not use special characters in the database name, privileged user, public user, or PX Reporting user name for example: { } [ ] : ; < > , . ? ! @ # $ % ^ & * ( ) - _ | / \ ~ `
- 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.
- See Modifying Private Database Logins for P6 EPPM for instructions on how to replace the private database login. For all other database user names and passwords, use the tools included with the database.
Application Configuration Procedures
- Install the new P6, P6 Professional, and any additional components.
- Starting with P6 EPPM R8, all recurring job service functions are hosted by P6. Due to this change, after upgrading to P6 EPPM R8 or later, you must configure Scheduled Services settings in the Primavera P6 Administrator to use this functionality. Also, if you're upgrading from version 7.0 or earlier, you must RESUMMARIZE ALL PROJECTS to accurately reflect your summary data. See the P6 EPPM System Administration Guide for information on Scheduled Services and configuring separate servers for job services.
- Assign new or modified privileges to users. See information about global and project 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 P6 EPPM functionality. The upgrade process will remove only 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.
- Starting with P6 EPPM R8, P6 saves filter definitions globally. Filters still work for Activity Views, but all standard filter assignments reset during the upgrade. Due to this change, views that had Standard Filters applied will show all activities after the upgrade. Reapply filters after the upgrade finishes. 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 and earlier. See information on the default Admin Superuser in the P6 EPPM Application Administration Guide for guidelines on this process.
Last Published Friday, February 2, 2024