IBM InfoSphere Change Data Capture for DB2 zOS, CHC9201I (CDCz) Attempting to reconnect to DB2 after start ACCESS(MAINT)

Technote (troubleshooting)


Problem(Abstract)

A restart of DB2 in normal mode and recycle of DB2 subsystems used as replication
sources experiences several DB2 CAF errors.

From the CDCz Jeslog we see the following messages
+CHC9220W (CDCz) DB2 is undergoing a normal shutdown. Ending DB2 dependent tasks.
+CHC9201I (CDCz) Attempting to reconnect to DB2
+CHC9204W (CDCz) DB2 is not available; waiting for it to start
+CHC9205I (CDCz) DB2 is now available.

However, the subscription were not running. CDCz Started task had to be recycled.

Symptom

The following sequence of events may occur.

CHC9210E DB2 CAF CONNECT request has failed. ReturnCode=8, ReasonCode=X'00F30002'
CHC9204W DB2 is not available; waiting for it to start failed. ReturnCode=8, reasonCode=X'00F30056'



Cause

CDCz Started task appears to think that DB2 is still in access(maint) mode.


The reason code from DB2 states:
00F30056
Explanation
An IDENTIFY request for connection to DB2® was rejected. DB2 had been
started in restricted access mode. Only authorization IDs authorized to
perform maintenance functions are permitted access to DB2.
System action
The connection request is not processed.
User response
Retry the connection request after DB2 has been restarted in full access
mode.

What we would have expected after DB2 restarted would have
been the following message

CHC9102I IBM InfoSphere CDC for z/OS initialization is complete
.
CDCz issues a DB2 CAF CONNECT request to establish a connection to the DB2 subsystem
.


Environment

DB2 zOS running in normal mode with CDCz

Diagnosing the problem

User's need to investigate the CDCz JESLOG along with the SYSLOG and review the timeframe from which DB2 was started in access(maint) to normal.

Here is an example of what a user should find:

11190 1731215 - R= DB2 !START DB2 PARM(DSNZMAIN) ACCESS(MAINT)
11190 1731217 - R= DB2 S DB2AMSTR
Indicates DB2 started in maint mode.
.
The CDCz jeslog shows :
16:58:52 +CHC9220W (CDCz) DB2 is undergoing a normal shutdown. Ending DB2
16:58:52 +CHC5003I (CDCz) A DB2 Trace has been stopped in buffer "OP8"
16:58:52 +CHC9201I (CDCz) Attempting to reconnect to DB2
16:58:53 +CHC9204W (CDCz) DB2 is not available; waiting for it to start.
SYSLOG time for start with access maint shows:
11190 1733035 R= DB2AMSTR DSNY014I ! DSNYSTRT DB2 WAS STARTED
WITH ACCESS(MAINT)
11190 1733035 R= CDCz +CHC9205I (CDCzProc) DB2 is now available

CDCz jeslog shows
17:33:03 +CHC9205I (CDCz) DB2 is now available however, at this time we issue the message
2011/07/09 16:58:53 DSC CHC9204W DB2 is not available;
2011/07/09 17:33:03 DSC CHC9205I DB2 is now available
2011/07/09 17:33:10 DSC CHC9210E DB2 CAF CONNECT request has
failed.ReturnCode=8, ReasonCode=X'00F30056'
11190 1743072 R= DB2AMSTR DSNY001I ! SUBSYSTEM STARTING
11190 1743303 R= DB2AMSTR DSN9022I ! DSNYASCP 'START DB2' NORMAL
COMPLETION.

Please provide IBM Support with the following should you encounter this issue:
1. The CDCz Jeslog
2. The SYSLOG at time of failure
3. Console Dump at time of failure.

Resolving the problem

Recycling the CDCz Started task will detected DB2 being active and resume.

Historical Number

08381
422
000

Product Alias/Synonym

CDCz

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

InfoSphere Change Data Capture
InfoSphere Change Data Capture for z/OS

Software version:

6.2.1, 6.5

Operating system(s):

z/OS

Reference #:

1507227

Modified date:

2011-08-23

Translate my page

Machine Translation

Content navigation