Use the DSN1COPY and CHECK INDEX utilities to verify the integrity of the Db2 directory and catalog table spaces on the subsystem that you are migrating.
About this task
Important: This migration step identifies data integrity issues that might interfere
with subsequent migration tasks.
Tip: For best results, use this process to check the Db2 catalog and directory regularly, even outside of the migration process.
Procedure
To verify the integrity of your Db2 directory and catalog table
spaces:
-
Run the DSN1COPY utility with the CHECK option on all catalog table spaces to ensure that the
table space pages are physically correct and that the catalog table spaces are clustered.
When you run this utility on segmented table spaces or LOB table spaces, you might
receive message DSN1985I. You can ignore this message.
The segmented table spaces in the directory and catalog are:
- DSNDB01.SPT01
- DSNDB01.SYSUTILX
- DSNDB06.SYSDDF
- DSNDB06.SYSSTATS
The LOB table spaces in the
directory and catalog are:
- DSNDB01.SYSDBDXA
- DSNDB01.SYSSPUXA
- DSNDB01.SYSSPUXB
- DSNDB06.SYSJAUXA
- DSNDB06.SYSJAUXB
- DSNDB06.SYSPLUXA
- DSNDB06.SYSPLUXB
- DSNDB06.SYSTSATX
- DSNDB06.SYSTSCHD
- DSNDB06.SYSTSCHR
- DSNDB06.SYSTSCTD
- DSNDB06.SYSTSCTR
- DSNDB06.SYSTSDQE
- DSNDB06.SYSTSDQH
- DSNDB06.SYSTSDQO
- DSNDB06.SYSTSDQS
- DSNDB06.SYSTSDQT
- DSNDB06.SYSTSIXR
- DSNDB06.SYSTSIXT
- DSNDB06.SYSTSOBX
- DSNDB06.SYSTSPDT
- DSNDB06.SYSTSPHX
- DSNDB06.SYSTSPKX
- DSNDB06.SYSTSPTX
- DSNDB06.SYSTSPVR
- DSNDB06.SYSTSQRA
- DSNDB06.SYSTSSNL
- DSNDB06.SYSTSSXL
- DSNDB06.SYSTSTRT
- DSNDB06.SYSTSVAD
- DSNDB06.SYSTSVAT
- DSNDB06.SYSTSVTR
- DSNDB06.SYSTSVWT
- Run the CHECK DATA and CHECK INDEX utilities.
- Run the following query on your Db2 12 catalog tables to ensure that you do not have a STOGROUP that is defined with both specific and non-specific volume IDs.

SELECT * FROM SYSIBM.SYSVOLUMES V1
WHERE VOLID ¬= '*' AND
EXISTS (SELECT * FROM SYSIBM.SYSVOLUMES V2
WHERE V1.SGNAME = V2.SGNAME AND
V2.VOLID = '*')

If the preceding query returns any rows, the identified STOGROUPs have both specific and non-specific volume IDs. Table spaces in databases that use these STOGROUPs cannot be image-copied or recovered until ALTER STOGROUP is used to remove volumes, so that the STOGROUP has either specific or non-specific volume IDs.