The P6 EPPM database stores P6 EPPM data used by the P6 EPPM applications.
The database administrator (DBA) should perform the steps in this chapter. You must install the database server before you can create the database. See the P6 EPPM Planning and Implementation Guide for details on product versions P6 EPPM supports. See the P6 EPPM Installation and Configuration Guide to use a wizard that automatically creates the database structures and loads the data.
P6 EPPM includes an encryption algorithm that provides enhanced security for private database logins; however, when you manually configure your database, the database does not automatically enforce the encryption algorithm. If you manually configure your database, Oracle recommends that you use this encryption algorithm. To do so, you must reset the private database login. See Resetting Private Database Passwords for instructions. If you automatically configure your database, you do not need to configure the encryption algorithm.
User logins and passwords are not affected.
User Name and Password Tips
- P6 EPPM does not support passwords with multi-byte characters.
- 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.
- 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.
Security Tips
- To configure the Microsoft SQL database server for SSL, see Microsoft's Documentation for instructions on configuring SQL Database Server SSL. Direct questions about Installation and Configurations to Microsoft.
ANSI_PADDING for a Microsoft SQL Server Database Tips
- To prevent duplicate values in P6 EPPM modules appearing due to leading or trailing spaces, ensure that the ANSI_PADDING setting in Microsoft SQL Server is Off. For example, if one user enters "Equipment" and another user enters " Equipment" (with a leading space) for resource codes, the database will store both of these as valid values if ANSI_PADDING is On. If ANSI_PADDING is Off, the database will remove the leading space in the second entry and tell the user to enter a unique ID. See the documentation included with Microsoft SQL Server for more information.
Other Tips
- A SQL database name must not contain a space.