By Jeffrey Mcdaniel-Oracle on Aug 12, 2015
If you are using the Primavera Data Warehouse (previously Primavera Reporting Database) and pulling data from P6 then the Global and Project publication services are your life line for data. If those services are not running your data in Primavera Data Warehouse\Analytics will be out of date. If you encounter an issue where you Security service seems to be failing repeatedly, which can be caused by bad data (such as duplicate rows in USERS table), it may be appropriate to force a 'Full.'
By forcing a 'full' update you are essentially telling the global services that security has never been run and to calculate everything again. The extended schema is all based on update dates. It will compare for related tables and compare those rows with entries in the SETTINGS table. To make it recalculate everything you would remove the related rows in Settings. Be very careful here, removing all rows from Settings would cause a global wide Full which may take many many hours to run and use server resources to accomplish and could have an impact on P6. Delete only what is necessary.
In this example we are going to do a 'Full' for security. Here are the steps:
1- Connect as ADMUSER and run the following:
delete from SETTINGS where NAMESPACE in (
2- Run the global service for Security. Be prepared this will take much longer than the usual daily run as it will be recalculating all security.
After the service has been completed run your ETL process. This way you will have all the latest on both the extended schema and data warehouse\Analytics side.