Start of changeReinitializing SYSUTILXEnd of change

Start of changeIf you cannot successfully execute the DISPLAY UTILITY and TERMINATE UTILITY commands, you need to reinitialize the directory table space or spaces that contain the SYSUTIL and SYSUTILX tables. Use this method if the table space or table spaces are damaged and you cannot recover them, because errors occur in the LOGAPPLY phase.End of change

About this task

Start of changeFL 509The table space that contains the SYSUTIL and SYSUTILX tables depends on whether that table space has been converted to a universal table space (UTS). It is either DSNDB01.SYSUTILX (non-UTS) or DSNDB01.SYSTSUTM and DSNDB01.SYSTSUTX (UTS). End of change

Start of changeBecause these table spaces contain information about active and outstanding utilities, the process of reinitializing them involves determining which objects have a utility in progress and resolving any pending states to make the object available for access.End of change

Use the following procedure with caution.

Procedure

Start of changeTo reinitialize SYSUTILX, SYSTSUTM, and SYSTSUTX:End of change

  1. Issue the -DIS DB(*) SPACENAM(*) RESTRICT command and analyze the output. Write down the following items:
    • All of the objects with a utility in progress (The objects in UTUT, UTRO, or UTRW status have utilities in progress.)
    • Any pending states for these objects (RECP, CHKP, and COPY are examples of pending states.
  2. Start of change Run the following utility statement: 
    CATMAINT UPDATE UTILX RESET

    This statement resets either the DSNDB01.SYSUTILX table space or the DSNDB01.SYSTSUTM and DSNDB01.SYSTSUTX table spaces. (Db2 determines which table spaces exist and need to be reset.) This statement also resets the indexes on the SYSUTIL and SYSUTILX table.

    End of change
  3. Issue the -START DB(dbname) ACCESS(UT) command for each database that has objects with a utility in progress.
  4. Issue the -START DB(dbname)SPACENAM(spname) ACCESS(FORCE) command on each object with a utility in progress. This action clears all utilities that are in progress or in pending states. (Any pending states are cleared, but you still need to resolve the pending states as directed in the next step.)
  5. Resolve the pending states for each object by running the appropriate utility. For example, if an object was in the RECP status, run the RECOVER utility.
  6. Issue -START DB(dbname) ACCESS(RW) for each database.