IBM Db2 - The Ultimate Database for Cloud, Analytics & Mobile
We recently moved our first datasharing DB2 from V11 to V12 in a test environment.
In order to build up a comprehensive backup procedure, we did the following:
- While still in V11, we saved (physical save with FDR) all the DSNDB06, DSNDB01, logcopy and BSDS files relative to the DB2 V11.
- Moved up DB2 from V11 to V12 (code + catalog), and reach that level V12R1M504.
Then the restore procedure :
First restoring DSNDB06, DSNDB01, logcopy and BSDS (with PGM=FDRDSF => so physically replacing all the V12 catalog TS with its V11 counterparts and deleting those created in V12) and plugging the code toward V11 files again, at this point we should have everything back in V11...code is back in V11, but the catalog remains libelled as V12 !!!
=> BEGIN DISPLAY OF GROUP(DB2xxx ) CATALOG LEVEL(121) MODE(X )
Same thing after reinitializing SCA and lock structures dedicated to DB2.
The others DB2 part of the datasharing remained in V11 all along.
So does anyone know why DB2 keeps this catalog level while all the traces of V12 were obviously erased ?