Creation/Update of DataWarhouse database tables (DB2) took more than 30 minutes
Creating (or Update) the tables for the DataWarehouse (CLM 4.0.5, repotools –createWarehouse) took more than 30 minutes to complete. During this time there are minutes without any CPU load and disk IO Creation of all other tables (i.e. CCM, JTS, QM) took less than 1 Minute (with CPU load and disk IO of db2 processes)
Here we have to wait for 30 minutes The data warehouse was upgraded successfully.
Any ideas, why this takes so long?
|
2 answers
The data warehouse does take a long time to create. One of the reasons is it needs to prefill the RIDW.D_DATE table with dates that span a 50 year period. Also the number of tables and other artifacts in the data warehouse is much larger than the apps (ccm, qm, jts...). Another reason could also be the extensive use of triggers in the schema. The trigger SQL needs to be validated and probably compiled.
|
After several tests we found the root cause for this problem. Reason is the long time for GRANT permissions to the RPTUSER in DB2.
Unfortunately this isn’t documented in the Jazz documentation (perhaps it is a bug and should not happen)
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.