Expert Advice

NAS_AA_RS_DB2WorkloadState  
Situation Description
Suggested Actions
Situation Description

This situation is triggered when the state of the workload as determined by the DB2 capture server or DB2 apply server is considered to be unsatisfactory. Valid values for the DB2 capture workload state and DB2 apply workload state are INACTIVE and REPLICATE CONTINUOUS. Of these values, only REPLICATE CONTINUOUS is considered satisfactory.

When the situation becomes true, NetView message AQN008I is issued as a notification for automation by the Geographically Dispersed Parallel Sysplex® (GDPS®) solution.

 

Suggested Actions

When the Q Apply program follows the error action to stop the queue, the following scenarios are most likely to cause the Q Apply workload to become inactive:

  • DEADLOCK_RETRY limit exceeded
  • Target tablespace is full or not available, e.g. SQLCODE -904
  • Duplicate key for secondary unique indexes
  • Conflict action is Q and the Q Apply program receives a SQLCODE -803
  • For problem determination, check the Q Apply log file for diagnostic message ASN7627E program_name : program_identifier : The Q Apply browser browser_name (receive queue queue_name, replication queue map queue_map_name) terminated with error code error_code.

    The error_code in message ASN7627E could be an SQLCODE, a WebSphere MQ reason code, or a replication diagnostic code. Check the Q Apply log file for any diagnostic or error messages prior to message ASN7627E that feature the error code.

The following scenario is most likely to cause a Q Capture workload to become inactive:

  • An MQPUT error, which can be detected by message ASN0575E program_name : program_identifier : The program encountered a WebSphere MQ error reason_code while issuing the WebSphere MQ command command on object name.

    For example, ASN0575E "Q Capture" : "ASN" : "WorkerThread" : The program encountered a WebSphere MQ error "2053" while issuing the WebSphere MQ command "MQPUT" on object "Q1".

  • Check the reason_code on message ASN0575E to determine the problem that caused the workload to be stopped. See the reason code documentation in the WebSphere MQ Application Programming Reference for an explanation of this WebSphere MQ reason code and for information about actions that you might need to take.

    For other scenarios that may cause a Q Capture workload to become inactive, check the Q Capture log file for possible diagnostic or error messages.

 

Copyright IBM Corp. 2011 All Rights Reserved US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contact IBM