Information

Title	Database crashes due to error 9450, 9445, 9446, 4229 and 1124

URL Name	000031448

Article Number	000136206

Environment	Product: OpenEdge Version 10.x, 11.x Product: Progress Version: 9.x OS: Windows

Question/Problem Description

Database crashes due to error 9450, 9445, 9446, 4229 and 1124
Getting bkioread errors regarding insufficient disk space when starting database.

BKIOREAD BKIOWRITE errors are being reported on the fixed extents for certain data areas in the database during runtime.
Database log file has errors 9450, 9445, 9446, 4229 and 1124 during Emergency Shutdown.

Steps to Reproduce

Clarifying Information

Sufficient disk space is available.
The errors occur at different times.
The errors occur at different file offsets in different areas.
No 3rd Party Software, scanning, backup that accesses the runtime database.

Error Message	SYSTEM ERROR: wrong dbkey in block. Found <dbkey1>, should be <dbkey2>(1124) Begin ABNORMAL shutdown code (2249) Corrupt block detected when reading from database. (4229) SYSTEM ERROR: read wrong dbkey at offset <offset> in file <file> found <dbkey>, expected <dbkey>, retrying. area <number> (9445) SYSTEM ERROR: <bkioWrite>: Bad file descriptor was used during <Write>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (9446) bkioRead:Insufficient disk space during Read, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (9450)

Error Message

SYSTEM ERROR: wrong dbkey in block. Found <dbkey1>, should be <dbkey2>(1124)
Begin ABNORMAL shutdown code (2249)
Corrupt block detected when reading from database. (4229)
SYSTEM ERROR: read wrong dbkey at offset <offset> in file <file> found <dbkey>, expected <dbkey>, retrying. area <number> (9445)
SYSTEM ERROR: <bkioWrite>: Bad file descriptor was used during <Write>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (9446)
bkioRead:Insufficient disk space during Read, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (9450)

Defect Number

Enhancement Number

Cause

This is a Windows Memory Manager problem when there is not enough memory available to the Windows Paged Pool when the server is very busy and demand for memory is high.

Resolution

Increase the Windows PagedPoolSize value to allow a larger paged pool. A setting of 0xFFFFFFFF will allocate the maximum Paged Pool in lieu of other resources to the computer.

Suggestions from Microsoft: Server is unable to allocate memory from the system paged pool (http://support.microsoft.com/kb/312362)

The maximum PagedPoolSize is 0xFFFFFFFF.

Default PoolUsageMaximum is 80%. At which the Memory Manager trims pool memory which may need to be adjusted to ensure memory is released fast enough.

Reboot the machine and then start the database. If the problem persists, contact OpenEdge Technical Support with the following information:
a. The Database lg file (compressed)
b. The Windows Event Log
c. The current settings of PagedPoolSize, PoolUsageMaximum and Memory available.
d. The exact OpenEdge Version (including Service Pack/Hotfix as apply) and Windows version.

Workaround

Notes

References to Other Documentation:

Progress Article(s):
000012465, Database crashes with bkio read errors weekly due to insufficient resources on Windows

Keyword Phrase

Last Modified Date	9/13/2015 3:19 AM