Our production database abended with
ADAPROD2 ADANUC ADABAS - ABEND=S000 U0253 REASON=00000000
ABEND CODE 84878000 PSW 070C1000 8131BFB2
After the restart, it seems that the nucleus did repair the checkpoint file (19):20:38:36 ADAN21 00214 Protection log PLOGR1 started 20:38:36 ADAN02 00214 Nucleus run with protection log 01802 20:38:36 ADAL02 00214 2006-12-16 20:38:36 CLOGRS is active 20:38:36 ADAI64 File DDRLOGR1 is being opened in ECKD mode - RABN size 27990 20:38:36 ADANI2 00214 SMGT abend handler active 20:38:36 ADAN03 00214 ADABAS coming up 20:38:36 ADAN55 00214 Recovery data found on Work dataset(s) 20:38:37 ADAN56 00214 Backward repair done 20:38:37 ADAN56 00214 Forward repair done 20:38:37 ADAN56 00214 Autobackout done 20:38:37 ADAN5A 00214 Files modified during autorestart: 20:38:37 ADAN5A 00214 00019
We had problems with the checkpoint file before, applied all available zaps and created the checkpoint file from scratch.
Highest ZAP numbers AI742078, AN742463, AO742063, AU742190
The CP problem has been reported under #585201 (Aug 2005). Maybe this abend has nothing to do with CP file.
Did anyone experience this or a similar problem?
By the way, LA Times is no longer a customer but a user. And a solution might help others.
prod.db2.server.log.G0634V00.txt (69.2 KB)