Problem:
Production application job and DBA Fast Area health check job failed. A DEDB area was inaccessible to the requested service when the application program issued a database request or when the application program reached a commit point. The AREA was stopped due to inconsistent dataset definitions.
+DATABASE=DBNAME FORMAT=DEDB ACTION=FH=IMS AREAS=N/A
REASON CODE=28 AREA=NAMExxxx DBD AND DATA SET DEFINITIONS INCONSISTENT IMXX
AREA=NAMExxxx DD=FCALxxxx CLOSED IMXX
DATASET NAMExxxx SUCCESSFULLY DEALLOCATED IMXX
AREA=NAMExxxx STOPPED IMXX
DFS554A JOBNAMEX 00002 STEP01 PGMNAMEX(2) 000,4000 PSB 2013/104 1:00:35
Reason:
REORG/RESIZE was cancelled for last week due to IPL and Business requirement in the last movement. REORG/RESIZE setup completed but schedule flow cancelled spotlight the bug in the REORG setup tool. A Fast path Area selected to be RESIZED last weekend was picked up by the DBDGEN process during this week RESIZE Flow, even though a different AREA of different database was selected to be RESIZED this weekend after deleting last week setup.
The 2 AREA’s of 2 different Fast path database were selected for RESIZE for DBDGEN process but REORG after DBD change did complete for only one AREA.
Even the ACBLIB flip in online region completed after the RESIZE/REORG flow completed.
Fix:
The impacted AREA was REORG/RESIZED by unloading the AREA using the inactive ACBLIB . Delete/define and load the AREA using the active ACBLIB. The key is to use the inactive ACBLIB during unload as otherwise the job will fail with message “DMAC inconsistent with DMB”. Run Pointer checker to confirm there is no issue after REORG and started the AREA fixed the problem.
Lesson Learnt:
Validate the DBDGEN after the REORG/RESIZE setup for correct list of AREA’s.
The key to fix the problem if occurs, is to use the inactive ACBLIB during unload as otherwise the job will fail with message “DMAC inconsistent with DMB”. Validate the delete /define to match the RESIZE Requested.
No comments:
Post a Comment