It's all about the answers!

Ask a question

Creation/Update of DataWarhouse database tables (DB2) took more than 30 minutes


Dieter Paul (10311620) | asked Jan 21 '14, 6:27 a.m.

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)


CRJAZ2558I Setting the local server rename state to false and the openServerDescriptionServiceTemporarily state to false
.
CRJAZ1365I The server is attempting to connect to the following database: "//localhost:50000/JTS:user=xxxxxxxx;password=
xxxxxxxx;"
CRJAZ1364I The connection to the following database was successful:
 Db Product Name: DB2/NT64
  Db Product Version: SQL10010
  Db URL: jdbc:db2://localhost:50000/JTS:user=xxxxxxxx;password=xxxxxxxx;
  Jdbc Driver Name: IBM Data Server Driver for JDBC and SQLJ
  Jdbc Driver Version: 4.14.121
CRJAZ1971I The server is configured with:
  Public URI: "https://rb-alm-beta-clm.de.bosch.com/jts"
CRJAZ2523I Setting the global server rename state to false and the validation state to false.
CRJAZ2105I Checking for a running server...
CRJAZ1365I The server is attempting to connect to the following database: "//localhost:50000/DW:user=xxxxxxxx;password=x
xxxxxxx;"
CRJAZ1364I The connection to the following database was successful:
 Db Product Name: DB2/NT64
  Db Product Version: SQL10010
  Db URL: jdbc:db2://localhost:50000/DW:user=xxxxxxxx;password=xxxxxxxx;
  Jdbc Driver Name: IBM Data Server Driver for JDBC and SQLJ
  Jdbc Driver Version: 4.14.121
CRRTC8039I The connection to the following data warehouse database was successful:
 DB Product Name: DB2/NT64
  DB Product Version: SQL10010
  DB URL: //localhost:50000/DW:user=xxxxxxxx;password=xxxxxxxx;
  JDBC Driver Name: IBM Data Server Driver for JDBC and SQLJ
  JDBC Driver Version: 4.14.121

Here we have to wait for 30 minutes

The data warehouse was upgraded successfully.


Any ideas, why this takes so long?


2 answers



permanent link
Rafik Jaouani (5.0k16) | answered Jan 21 '14, 10:35 a.m.
JAZZ DEVELOPER
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.

permanent link
Dieter Paul (10311620) | answered Jun 16 '14, 2:31 a.m.

After several tests we found the root cause for this problem. Reason is the long time for GRANT permissions to the RPTUSER in DB2.

It seems that the RPTUSER must be a valid OS (Windows) User. And as this isn’t a Windows user in our system, there are some timeouts.

After added the user to the OS, everything works fine.

Unfortunately this isn’t documented in the Jazz documentation (perhaps it is a bug and should not happen)

Your answer


Register or to post 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.