Jobs preventing IASP vary off

Some jobs can prevent the successful vary off of a Db2® Mirror IASP. If this occurs, the list of jobs can be viewed by querying the MIRROR_SUSPENDING_JOBS table function.

The vary off of the IASP will continue to fail until all jobs with Db2 Mirror database connections have completed their suspend processing for a previous suspend request. Allowing the IASP to vary off before jobs have completed their suspend processing could cause replicated objects to become out of sync.

If an IASP vary off request is unable to proceed because of jobs with pending suspend processing, the user is alerted with a CPDC926 message sent to both the joblog of the job issuing the vary off request and to the QSYSOPR message queue. For steps on accessing Db2 Mirror alerts, see Accessing Db2 Mirror QSYSOPR messages from the Db2 Mirror GUI.

The MIRROR_SUSPENDING_JOBS table function can be used to query which jobs are preventing the vary off of the IASP. Callers of the table function should retrieve results from the SOURCE node (ie. the node on which the IASP vary off is being issued). See MIRROR_SUSPENDING_JOBS table function for more information.

Reasons why a job might prevent IASP vary off

Jobs will prevent the vary off processing of an IASP if they have not completed their processing of a previous suspend. Typically, jobs will recognize and quickly complete their processing of the suspension of Db2 Mirror replication. However, in some cases, a job may prevent the vary off processing longer than expected. This may occur for the following reasons:

The job is held.
The job is executing a long running commit or rollback.
The job is executing a long running SQL statement like an ALTER TABLE or MERGE.

If a held job is preventing the vary off, the recommendation is to release the job so that suspend processing can complete for that job.

For jobs with a long running commit or rollback of a transaction, the recommendation is to allow the job to finish the committable work.

For jobs executing a long running SQL statement, the recommendation is to allow the SQL statement to finish.

If you are unable to wait for jobs to complete their pending work, you may choose to end some of the jobs that are preventing a vary off. It is recommended to allow all suspend processing to finish.

If after inspecting the jobs and performing any necessary actions, vary off of the Db2 Mirror IASP still fails, it is recommended to contact support.