Resolving DB2 Active Log Issues: A Step-by-Step Guide for Administrators
DB2 Active Log Issues and Resolution Procedure
This blog describes the DB2 Active LOG Data Set issues and how to resolve step by steps is in detailed described here. This will help any DB2 Administrator to resolve and get the knowledge from the documentations
In case if the Active Log data set is showing up error, you will get the following message in the SR Panel
Now, as DB2 Administrator you can get the data set information and understand the issue. Each step given with MVS commands, JCL Utilities, and DB2 Commands.
STEP 1 : GO TO 8.7 OPTION and check LOG using – DISPLAY LOG command
– DISPLAY LOG
STEP 2: STOP DB2 using /-STOP DB2 command
STEP 3: We have to run DSNJU004 offline utility to get RBA value.
DSNJU004 utility JCL
//OPER001A JOB ‘DSNJU004’,NOTIFY=OPER001,CLASS=A,REGION=0M
//STEP1 EXEC PGM=DSNJU004
//STEPLIB DD DSN=DSN810.SDSNLOAD,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=DSNZ.BSDS01,DISP=SHR
DSNJU004 utility output:
We have to note HIGHEST RBA WRITTEN value & HIGHEST RBA OFFLOADED value
STEP 4: Delete old logs and create New logs in the same name. Using DSNJU003 utility we can delete old and create new.
//OPER001A JOB ‘DSNJU003’,NOTIFY=OPER001,CLASS=A,REGION=0M
//STEP1 EXEC PGM=DSNJU003
//STEPLIB DD DSN=DSN810.SDSNLOAD,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=DSNZ.BSDS01,DISP=SHR
//SYSUT2 DD DSN=DSNZ.BSDS02,DISP=SHR
//SYSIN DD *
DELETE DSNAME=DSNZ.LOGCOPY1.DS01
DELETE DSNAME=DSNZ.LOGCOPY2.DS01
DELETE DSNAME=DSNZ.LOGCOPY1.DS02
DELETE DSNAME=DSNZ.LOGCOPY2.DS02
NEWLOG DSNAME=DSNZ.LOGCOPY1.DS01,COPY1
NEWLOG DSNAME=DSNZ.LOGCOPY2.DS01,COPY2
NEWLOG DSNAME=DSNZ.LOGCOPY1.DS02,COPY1
NEWLOG DSNAME=DSNZ.LOGCOPY2.DS02,COPY2
/*
//
STEP 5: Start db2 using /-START DB2.
STEP 6: : GO TO 8.7 OPTION and check LOG
The below are important DB2 error messages and the description which any point in time DB2 Administrator can keep them handy for immediate resolution steps
DSNJ017E csect-name WARNING – OFFLOAD TASK HAS BEEN ACTIVE SINCE date-time AND MAY HAVE STALLED.
Explanation: While switching active log data sets, DB2 found that the offload task has been active since the last time DB2 switched active log data sets. The offload task began archiving an active log data set at date-time.
System action: DB2 continues processing. If statistics class 3 is active, IFCID 0335 is written. This message will be deleted when the offload task completes the archive process.
System programmer response: This may be an indication that there may be an outstanding tape mount request or that the offload task may no longer be functioning. This situation can result in a log-full situation if DB2 can not archive log data sets when they fill. You should reply to any tape mount requests and monitor offload activity very closely. You can issue the -DISPLAY LOG command to display the status of the offload task, and the -ARCHIVE LOG CANCEL OFFLOAD command can be used to terminate and restart the offload process. Prior to terminating the offload task, obtain a dump of the DB2 MSTR address space for problem determination.
DSNJ004I ACTIVE LOG COPY n INACTIVE, LOG IN SINGLE MODE, ENDRBA=…
Explanation: This message is sent when the dual active logging option is selected and copy ’n’ becomes inactive. A log copy becomes inactive when the next active log data set is not ready when required. ENDRBA is the last byte of log data written on copy ’n’. This is usually caused by a delay in off-load.
System action: The log is switched to single mode until the next data set for copy ’n’ is ready for logging. If DB2 is shut down or abends while in single mode with the ZPARM option still set for dual active data sets, the previous state of the active log data sets determines what happens when DB2 is started, as follows: v If fewer than two data sets are available (not flagged as STOPPED) for each set of active logs, DB2 startup terminates and message DSNJ112E is issued. v If an active log data set is in NOTREUSABLE state, DB2 can be started in single logging mode, but dual mode takes effect when the other active log data set becomes available after offloading.
Operator response: Execute an MVS Display System Requests command (D R,L for example) to ensure that there are no outstanding requests that are related to the log off-load process. Take the necessary action to satisfy any requests, and permit off-load to continue.
System programmer response: If the switch to single mode was caused by the lack of a resource required for off-load, the necessary resource should be made available to allow off-load to complete and thus permit dual logging to proceed. If recovery is required, information from this message might be required as input to the change log inventory (DSNJU003) utility.
DSNJ111E OUT OF SPACE IN ACTIVE LOG DATA SETS
Explanation: Due to delays in off-load processing, all available space in all active log data sets has been exhausted. DB2 recovery logging cannot continue.
System action: The DB2 log manager waits for an available data set.
Operator response: Execute an MVS Display System Requests command (D R,L for example) to ensure that there are no outstanding requests that are related to the log off-load process. Take the necessary action to satisfy any requests, and permit off-load to continue.
System programmer response: If the delay was caused by the lack of a resource required for off-load, the necessary resource must be made available to allow off-load to complete and thus permit logging to proceed.
We are experienced good implementation skills of these tools EDz, EAz, IDz, DBB, UCDz install, configure and customize and do training enablement. Rich experience in IBM Developer for z and IBM DBB Training by with content delivery of 5 days based on the coverage and team size of trainees.
We also explore other products from Heirlooms Computing, Micro Focus, Modern Systems for Application Analysis, Development IDE for Mainframe applications.
Contact us as vlakshmie@vrgzlabs.com for any Mainframe Training, Mainframe Modernization Training, Implementations, Mainframe Consulting engagements and customization projects.
