RDBPROD: How to fix Snapshot file corruption that is causing DBM-F-CANTREADDBS bugchecks (Doc ID 1339190.1)

Last updated on AUGUST 09, 2016

Applies to:

Oracle CODASYL DBMS - Version 7.0 and later
HP OpenVMS Itanium
HP OpenVMS Alpha
Application is failing with bugchecks when accessing CODASYL DBMS database snapshot files. Database access may not be possible at all via the application.


Goal

Bugchecks show either:

***** Exception at 002C0608 : PIOFETCH$VALIDATE_PAGE + 000003F8
%DBM-F-CANTREADDBS, error reading pages 18:631-631
-DBM-F-BADPAGRED, read requesting physical page 18:631 returned page 16389:5254

or

***** Exception at 01351CD4 : PIOUTL$READ_PAGES + 000006E4
%DBM-F-CANTREADDBS, error reading pages 17:45571-45575
-SYSTEM-W-ENDOFFILE, end of file 


The above lines are in the DBOBUGCHK.DMP file.  Use the bugcheck summarizer (<Note: 165466.1>) or edit the file.

The numbers before the first colon are storage area numbers and these equate to snapshot storage areas.  This can be determined by:

$DBO/DUMP/HEAD/OUT=HDR.LIS <database>
$ sea hdr.lis "area id number is 17" /win=(1,0)

This will show if the area is indeed a snapshot area.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms