Information

Title	Database errors 509 and 510 after abnormal shutdown using no crash protection (-i) parameter

URL Name	P16660

Article Number	000123277

Environment	Product: Progress Product: OpenEdge Version: All supported versions OS: All supported platforms

Question/Problem Description

Database errors 509 and 510 occurring after abnormal shutdown using no crash protection (-i) parameter
Unable to start Progress database after no integrity (-i) session has crashed.

Steps to Reproduce

Clarifying Information

Machine was rebooted while the database was running in a single or multi-user mode.

Error Message	The last session was run with the no integrity (-i) parameter. (509) Your database cannot be repaired. You must restore a backup copy. (510) drexit: Initiating Abnormal Shutdown

Defect Number

Enhancement Number

Cause

A Progress database cannot go through crash recovery if for any reason the session using -i parameter crashes and terminates abnormally. This includes shutting down the database using "proshut -byF", while transactions are being processed.

Resolution

Restore database from the last backup.

If restoring from backup is not a viable option and you must recover the data "as it is" with potential risk of a logical and physical database integrity. See article Consequences of using the -F startup option for additional information on how to force access into a database.

Workaround

Notes

Keyword Phrase

Last Modified Date	11/20/2020 7:32 AM

Database errors 509 and 510 after abnormal shutdown using no crash protection (-i) parameter

Information