The Db2 load utility encounters duplicate rows loading the Sysview for Db2 for z/OS (IDB2) application detail archive tables when the rows are not really duplicates.
The tables that can be affected by this problem are: APPLICATION_DETAIL, APPL_BP_DETAIL, APPL_DDF_DETAIL, APPL_GBP_DETAIL and APPL_PGM_DETAIL.
The thread end time store clock values for the two threads are different but when converted result in the same timestamp value. This timestamp value is used for the table's END_DATE_TIME TIMESTAMP column which is included as a key column in the table's UNIQUE INDEX. For example, the following two STCK values convert to the same timestamp value:
Accounting record QWACESC STCK Converted to timestamp ------------------------------------------------------------------- C7FCB78E315665C9 2011-06-27-20.59.40.764582 C7FCB78E31566A86 2011-06-27-20.59.40.764582
There are two possible solutions that will resolve this problem for future archival executions.
Note: Adding IFCID-SEQ-NUM as the last field in the IQL and DB2 Load utility control statements saves having to update all the POSITION parameters in the DB2 load utility control statements.
Please be aware that if you chose to add the new column to the TABLE and UNIQUE INDEX you will need to modify the migration procedure(s) that will be supplied with a future release.
The solution to add the column to the table and unique index will be permanently implemented in a future release when Db2 10 support is added to the archive tables.