The following list summarizes the procedures to perform after the P6 EPPM upgrade:
Backup Procedures
- Oracle recommends you make a backup of your newly upgraded database.
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. 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 the 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.
- 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. See the P6 EPPM System Administration Guide for details.
- Assign new or modified privileges to users. See information about security profiles in the P6 EPPM Application Administration Guide.
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 the P6 EPPM Application Administration Guide for details on the default admin superuser.