DSNB226I csect-name - BUFFER MANAGER PAGE GET ROUTINE DETECTED AN INVALID PAGE IN DBNAME=database-name, SPACENAME=space-name , INSTANCE=instance-number, DATA SET NUMBER= data-set-number, PAGE EXPECTED=X'expected page-number', PAGE NUMBER FOUND=X'page-number'
Explanation
An unexpected page was received during buffer manager (BM) get page processing.
- csect-name
- The name of the control section that issued the message.
- database-name
- The name of the database that contains the involved page set.
- space-name
- The name of the table space or index space for the involved page set.
- instance-number
- The instance number of the table space or index space.
- data-set-number
- The data set number for the involved page set.
- expected page-number
- The page number of the page in error. The buffer manager expected to find this page in the buffer.
- page-number
- The page number of the page that was found in the buffer instead of the expected page.
System action
The application is terminated with abend X'04E' and reason code 00C200F7.
Operator response
Notify the system programmer.
See the information for the given reason code and take the specified action.
System programmer response
If you suspect an error in Db2, see the information about collecting data.
Problem determination
Collect the following diagnostic items:
- Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
- Dynamic dump, taken to SYS1.DUMPxx data set, by Db2 (04E and 04F abends).
- A listing of the SYS1.LOGREC data set, obtained by executing IFCEREP1.
- IDCAMS LISTCAT output for the ICF (VSAM) catalog that contains the Db2 subsystem catalog that defined the failing index or table.
- VTOC listing of the disk volume on which the failing operation occurred.
- DSN1COPY-generated copy of the table and index, taken before any recovery is performed.