If you are connecting multiple P6 data sources to your Star schema, Oracle Database Enterprise Edition, you must use partitioning.
Note: Oracle Standard Edition does not have partitioning.
If your Star schema is installed using Oracle Enterprise Edition without partitioning, the P6 EPPM database should be a small-sized database as defined in the P6 Analytics and P6 Reporting Database Planning and Sizing. Partitioning helps keep performance consistent over time for each ETL run. This is particularly important when enabling activity or WBS-level history. If you choose not to use partitioning, Oracle recommends that you not use activity and WBS-level history gathering. If the P6 EPPM database is larger than the defined criteria of a small-sized database, Oracle recommends you use Oracle Database Enterprise Edition with Partitioning.
Notes:
Without partitioning, the amount of time it takes to run the ETL process will increase over time. Track the row counts in the w_project_history_f, w_wbs_history_f, w_activity_history_f. It can also track tables ending in _HF and _HD for Type II history dimensions. As the size of these tables increases the need for partitioning will also increase. You can monitor these run times in the staretl.html and staretlprocess.log located in the <installation directory>\log folder. Oracle Database Enterprise Edition with Partitioning is the solution for growth over time within the history tables.
Legal Notices
Copyright © 1999, 2014,
Oracle and/or its affiliates. All rights reserved.
Last Published Friday, January 31, 2014