Skip DWH on Clarity upgrade

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Due to performance there is a need DWH to be removed specifically from the upgrade and added later 

Significant slowness on DWH bootstrap on this step:

8/20/24 8:58 PM (ExecTask) Loading registered objects for data warehouse attributes bootstrap...

 

Environment

Any Supported Clarity Release

Resolution

1. In properties.xml remove the DWH database credentials, set it to OOTB line as per below:
     <dwhDatabaseServer vendor="oracle" sysPassword="change_on_install" dimensionTables="DWH_PPM_DATA_DIM" factTables="DWH_PPM_DATA_FACT" dimensionIndex="DWH_PPM_INDX_DIM" factIndex="DWH_PPM_INDX_FACT" fetchSize="240">
       <database id="Datawarehouse" jndiDatabaseId="jdbc/DatawarehouseDS" vendor="oracle" serviceName="niku" serviceId="niku" driver="oracle.jdbc.driver.OracleDriver" url="jdbc:oracle:thin:@localhost:1521:NIKU" username="ppm_dwh" password="ppm_dwh" schemaName="ppm_dwh" clarityDBLink="PPMDBLINK" isCustomDBLink="false" upgradeStatus="upgradeNotNeeded"/>
    </dwhDatabaseServer>
2. In Clarity UI go to System Options , in Data Warehouse settings delete the Entity for Fiscal Periods, and Save
3. Run the Clarity upgrade
4.  After the upgrade, ask the DBA to restore a new template for DWH database from $clarity/database/backups folder and create a DB LINK to the Clarity db that is being upgraded
5. Enter the correct details for the new DWH schema in CSA, add the Entity back and run Load DWH – Full Load job
6. Proceed with PMO upgrade
7. Bring Clarity up
8. Run a Full Load of Load Data Warehouse job to repopulate the tables

Note: DWH is required for PMO, which is required for MUX, Reporting and Status report, so it has to be set up once you upgrade with Clarity as it's a required component