DSNB232I csect-name - UNEXPECTED DATA SET LEVEL ID ENCOUNTERED - LEVEL ID =lvlid EXPECTED LEVEL ID=xlvlid DSN=dsn

Explanation

A required data set of a Db2 table space could not be opened. Db2 encountered an unexpected data set level ID.
lvlid
The unexpected level ID from the data set. If Db2 was unable to retrieve the level ID from the data set (for example, if the data set had been deleted and redefined), the level ID is shown as "X''".
xlvlid
The level ID recorded by Db2 previously and is the expected level ID for opening the data set
dsn
The DSNAME of the data set.

This problem could be the result of data sets that were restored to a level that is inconsistent with other data sets, inconsistent with the Db2 log, or both.

System action

Db2 sends back a 'resource unavailable' SQL code to the application and a reason code explaining the error.

Operator response

Notify the system programmer.

System programmer response

To enable access to a data set reported as down level, take one of the following actions:
  • Restore the page set or partition to the proper level (use DSN1COPY, DFHSM, or another tool).

    Identify the level ID of a copy of the page set or partition by running the DSN1PRNT(FORMAT) utility. The level ID is found in the header page of the page set or partition.

  • Recover the down level page set or partition to currency by running the RECOVER or RECOVER LOGONLY utility.
  • Accept the down levelling by running the REPAIR utility with the LEVELID option.

    This option is only valid if Db2 is able to access the level ID (lvlid is not "X''").

    Inconsistent data problems might result from this action and are the user's responsibility.

  • Replace the contents of the page set or partition using the LOAD REPLACE utility.
  • Explicitly restore the page set to a prior point in time with the RECOVER utility.

If the expected level ID is less than the encountered level ID, it is possible that the object identified in the message was ported from another system improperly or it might indicate that DSNDB01.SYSLGRNX is down level. If the problem is in the object identified in the message, the actions listed above can be used to allow access to the data. If the problem is in SYSLGRNX, this is a serious situation that compromises the recoverability of all objects managed by Db2. Investigate whether SYSLGRNX might have inadvertently been restored to a point in time inconsistent with the rest of the Db2 system.