In the JVM Location field, enter or verify the path to the Java Virtual Machine (JRE path).
You must have the appropriate version of JRE installed on the machine where the ETL process will run. For information on the specific JRE versions and supported operating system configurations, refer to the Tested Configurations document on the release media or download.
The path must refer to a location on the local machine where you installed the P6 Reporting Database configuration utility.
In the Log Detail Level field, choose the level of logging detail that you want to use. The following are the logging detail levels you can choose:
Errors and Warnings Logs errors and warnings.
General Information This is the default value. This logs errors, warnings, and informational messages on the progress of each step.
Debug and Trace Information Provides all general information, errors and warnings, and detailed output of each executed script, query, and connection.
Errors Only Logs only errors and no other information.
Extra Debug Information Provides all general information, errors and warnings. It provides more fine grained information on each executed step and script.
In the Max Java Heap Size (MB) field, enter parameter for the Java Heap Size. This value maps to the JVM –Xmx setting in the Java Runtime Environment settings. The default value (and recommended value) is 1,024 MB.
The minimum value is 512 MB.
When changing the Maximum Java Heap Size setting, the values must be in increments of 512 MB.
In the General Thread Count field, choose the number of threads the ETL process will run. Extraction and Load processes are multi-threaded.
Oracle recommends keeping the default (5) for this setting.
In the Index Building Thread Count field, choose the number of threads that will build the index. It specifies how many threads to run for building indexes for the ODS or Star database.
Oracle recommends keeping the default (5) for this setting.
In the Partitioning section:
Select the Enable Partitioning option to use partitioning.
Notes:
While Oracle recommends that you use a partitioned environment, P6 Reporting Database also supports non-partitioned environments with Oracle Database Standard Edition or the Enterprise Edition. If you choose not to use partitioning, Oracle recommends that you not use activity and WBS-level history gathering. Multiple P6 instances for Star are not supported without partitioning. For more information on database requirements, see the P6 Analytics and P6 Reporting Database Planning and Sizing Guide.
If you implement partitioning, you must license the Oracle Database partitioning option. Your Oracle account representative is always your best source for licensing details.
In the Datasource ID field, enter the number of data sources that you will use in the Star environment.
In the Months per Partition field, enter the number of months between partition ranges. If you have a smaller range of partitions, the data between partitions will move faster.