Ensure you:
Note: This section is based on large implementations. Refer to the Summary of Physical Hardware Sizing section for details on small and medium implementations.
Check | Item |
|---|---|
| Reviewed the Primavera Analytics Planning and Sizing Guide for sizing and spacing guidelines. |
| Can connect to the P6 EPPM and/or Primavera Unifier database. Note: If you are using Microsoft SQL Server, ensure you can connect to the P6 EPPM database through the Oracle Gateway. |
| Can connect to the Primavera Data Warehouse database instance. |
| Configured TNSNAMES correctly with all instances. |
| Defined the ORACLE_HOME path on the server running the ETL scripts so it can find SQLLDR. |
| Can connect JDBC and OCI on the ETL server. Note: You can test the connection with a sample Java application. |
| Verified the user running scripts on the server has Read and Write permissions to install the directory. Note: On UNIX systems, create and install the database as 'Oracle' user.
|
| Placed all servers in same data center with a Gigabit Ethernet connection between servers. |
| Verified each ETL Process server has 8-12 core processors. |
| Verified each database server has 8-10 core processors. |
| Are running the ETL Server on 64-bit machine to allow for large memory allocations. |
| Set the Java Max Heap setting to at least 4 GB of memory. Allow for more memory, if available, for the Java process. |
| Set the Bulk Load files location from the ETL process to a location with a large amount of available disk space. Note: These files can become large depending on the size of the database. Available space should range from a few gigs to many tens of gigabytes. |
| Are using a supported Operating System. See the Tested Configurations document for supported operating systems. |