Fallback procedure to copy History files from Release 19.0 to a previous Release

Document ID : KB000010200
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

Upgrade from any CA SYSVIEW for DB2 Release published previous to Release 19.0 and tested the fallback procedure for History files. It was not possible to unload HISTSTAT and HISTACCT files from Release 19.0 and then load them to the previous published Release with defined History files. You will receive DBG21023E error message. 
 
DBG21023E ... HISTORY: FILE histfile INVALID HISTORY FILE : ...

Instructions:

Officially this is not supported, some of the IDB2 records have been changed in size for CA SYSVIEW for DB2 19.0 and they might be truncated during the fallback.

Unofficially there is a method that it should work:

1) Use Release 19.0 IDB2UIFI utility to unload the Release 19.0 History files to SMF.
- Use options /REQ=UNLDHIST,UNLOAD=ALL,REMPOS=NO
- ddnames HISTSTAT and HISTACCT need to be allocated to the Release 19.0 History files.
- SMFOUT needs to be allocated to a VBS dataset.

2) Reload the SMF file produced in Step 1 into a clean LDS files using the previous
Release version of the IDB2UIFI utility.
- use options /REQ=LOADHIST
- SMFIN needs to be allocated to the data set produced in step 1 (SMFOUT).
- HISTSTAT and HISTACCT ddnames must be allocated to the clean history files
(The size should match Release 19.0 versions) for the Release 17.0 version.

The following information might be lost during the procedure: Long IDB2 accounting records (>32K), parallelism rollup details, ...