DSNJ317I ARCHIVE LOG QUIESCE PERIOD EXPIRED. NUMBER OF OUTSTANDING UR'S = xxxx. ARCHIVE LOG PROCESSING WILL BE TERMINATED, AND UPDATE ACTIVITY AGAINST DB2 RESOURCES WILL BE RESUMED. HH:MM:SS

Explanation

An -ARCHIVE LOG MODE(QUIESCE) command was processed by the Db2 subsystem; however, the Db2 subsystem was not able to quiesce all update activity in the user-specified quiesce time interval.

System action

This message is informational only. The Db2 subsystem determined that 'xxxx' units of recovery (URs) did not reach a point of consistency during the quiesce period, and therefore could not be stopped from continuing their associated update processing.

Consequently, the -ARCHIVE LOG processing will be terminated. The current active log data set(s) will not be truncated, and will not be switched to the next available active log data set(s). The log archive (offload) task will not be created. All jobs and users suspended during the quiesce will be resumed, and normal update activity against Db2 resources will be commenced.

This message will be followed by the DSNJ312I message.

Operator response

Contact the system programmer.

System programmer response

A determination must be made whether the outstanding (non-quiesced) URs represent significant work.

Each user on the system has a unit of recovery if they are modifying Db2 resources. URs are also created by the Db2 subsystem itself for internal processing. Since the purpose of the MODE(QUIESCE) option is to have all URs reach a point of consistency (commit point) before the active log data set is truncated and offloaded, determine all outstanding non-queued jobs and users by using -DISPLAY THREAD and the MVS 'D A,L' operator command.

It should be noted that URs may be outstanding due to lock contention between a user or job which holds a resource (and has reached a point of consistency), and a user or job which wants a lock (and therefore cannot reach a point of consistency).

Before resubmitting the -ARCHIVE LOG command with the MODE(QUIESCE) option, either:
  • Wait until the threads have been deallocated.
  • Wait until the Db2 subsystem is less busy.
  • Force the offending thread(s) to terminate.
  • Use the TIME option to dynamically override and extend the maximum quiesce time period specified in subsystem parameters.
  • Or, if having all URs reach a point of consistency in the active log is no longer critical, issue the -ARCHIVE LOG command without the MODE(QUIESCE) option.

Important: If the decision is made to use the -ARCHIVE LOG command without the MODE(QUIESCE) option, the active log data set(s) will be truncated without regard to quiescing activity on the Db2 subsystem. If the resulting archive log data set is used for recovery, it is possible that some URs may be found to be inflight, in-abort, in-commit, or indoubt during Db2 initialization.

If expiration of the quiesce period before all URs reach a consistent point are a chronic problem, you might need to adjust the value of the QUIESCE subsystem parameter.