For backup purposes, take image copies of catalog and directory objects.
Procedure
To copy catalog and directory objects, use the following
guidance:
-
If you are migrating from a Db2 12 system, and new
function is not activated on your Db2 13 subsystem, use the
DSNTIJIC job that is produced by running the installation CLIST in MIGRATE mode.
-
When LISTDEF is used for catalog and directory objects, LISTDEF object
expansion for the COPY utility issues message DSNU1530I for obsolete catalog or
directory objects. If OPTIONS EVENT(ITEMERROR,SKIP) is specified, the object is
skipped, and RC 4 is issued. Otherwise, the COPY utility terminates with RC 8.
-
When LISTDEF is not used for catalog and directory objects, the COPY utility
skips new or obsolete catalog and directory objects during processing and issues
message DSNU1530I with RC0 for each skipped object. For example, before new
function is activated in Db2 13, the COPY utility skips
catalog and directory objects that are new in Db2 13. After new function is
activated, the COPY utility skips catalog and directory objects that are
obsolete in Db2 13.
Specifying OPTIONS EVENT(ITEMERROR,SKIP) or OPTIONS EVENT(ITEMERROR,HALT) does
not impact the skipping of new or obsolete objects.
-
Ensure that the following table spaces are copied in a COPY statement that does
not include other table spaces:
- FL 501
DSNDB06.SYSTSUTL (which contains the utility
history table SYSIBM.SYSUTILITIES)
- FL 504 DSNDB06.SYSTSOEV (which contains the utility object-level history
table SYSIBM.SYSOBJEVENTS)
This same restriction applies to any indexes on SYSUTILITIES or SYOBJEVENTS
that have been altered to have the COPY YES attribute; ensure that no other
indexes are included in the COPY statement. This restriction prevents any
contention in case utility history collection is active. You can copy
DSNDB06.SYSTSUTL, DSNDB06.SYSTSOEV, and their indexes in the same COPY
statement.
