Friday Aug 08, 2014
Since P6 Reporting Database 2.0 and Analytics 1.0 the ETL process log has been appending during the ETL runs. In 3.2 staretlprocess.log will contain all ETL runs. We received customer feedback on a desire to have a log for each ETL run. With the web configuration utility added in 3.3 this was implemented. In the new configuration tool you can schedule your ETL runs and view the results and logs from the the web config. The logs were separated out so you can see the log for each individual run. This also gives you the option to clean up old logs from your system directory for a given time period.
The existing (non web based) configuration utility will still do the logging based on appending each run to the same log if this is the way you choose to have your ETL process logged. However you should choose one method, either the existing configuration utility or the web based configuration utility and not use both. The new web based config can build up a queue of ETL jobs and avoids any kind of collision. This is a major advantage for those using multiple data sources. You can queue up multiple runs and they will handle the execution. The existing configuration utility does not have a queue mechanism for ETL runs, they are controlled by cron jobs or manually being kicked off so collisions there are possible and you can not have more than one ETL process running at a time. Also because of the different logging methods you should not be running ETL's from both methods because the web configuration utility will not know of the logs for ETL runs kicked off from the STAR installation directory. Each log from the new queue method will have a time stamp and unique name on it for easy identification.
By Jeffrey Mcdaniel-Oracle on Aug 08, 2014
In the P6 Analytics 3.3, the default value of all UDF's (subject area (Project, Activity, etc.) and type (Date, Text, etc.)) were increased from 20 to 40. This includes the RPD changes. When choosing your UDF's from the configuration utility these changes will automatically be reflected in the schema and no changes will be needed in the RPD until you hit 40. We also increased the default value of Codes from 20 to 50. Same updates apply as with UDFs where all schema and RPD changes are automatically reflected up to 50. If adding greater than 50 for Codes or 40 for UDF's the appropriate RPD changes will need to be made to add additional values but all schema side changes will be handled by the ETL process.
Provide new information on Primavera Analytics and Data Warehouse
- Having Trouble Publishing Projects?
- When Configuring Multiple Data Sources...
- I Created an ETL Schedule Through the Web Configuration, How Do I turn the Schedule Off?
- Summary Data and the Summarizer, What is Needed for P6 Analytics?
- Capturing Historical Financial Periods for Analytics
- How Could I Get a Project to Publish After a Certain Amount of Activity Code Changes?
- Why Aren't My Code Changes Being Reflected in Analytics?
- History Selections (Part 2)
- How Historical Selections Effects the Size of Star Schema?
- P6 Analytics and P6 Reporting Database Security Enforcement