Salesforce

Database unable to complete crash recovery process when started via AdminServer

« Go Back

Information

 
TitleDatabase unable to complete crash recovery process when started via AdminServer
URL NameDatabase-unable-to-complete-crash-recovery-process-when-started-via-adminserver
Article Number000118496
EnvironmentProduct: OpenEdge
Version: 11.6.1, 11.6.2, 11.6.3, 11.6.4, 11.7.x, 12.x
OS: Windows
Question/Problem Description
Database crash recovery process hangs after some time when started via AdminServer

After starting the database with DBMAN database crash recovery process hangs and does not complete

When database startup is managed by the AdminServer it eventually times waiting for the database to register while crash recovery is hanging 8484

Database crash recovery still doesn't complete when AdminServer Timeouts are disabled (DBypassDatabaseTiming=true)

Database is configured to use Crash Recovery Status (-crStatus) and Crash Recovery Transaction Display (-crTXDisplay)
 
Steps to Reproduce
Clarifying Information
Error Message* Worst case (WTC) monitor timed out. (8484)
Defect NumberDefect ADAS-7170
Enhancement Number
Cause
The Display messages, -crStatus -crTXDisplay, that report on how long crash recovery will take go to STDERR instead of STDOUT.  The reason the database crash process hangs is because OpenEdge Management (OEM) doesn't read STDERR, which causes the output buffer to fill. This in turn causes the database process to hang while trying to write messages.
Resolution
Upgrade to OpenEdge 11.7.4 or later where the database process output handling is updated to redirect STDERR to STDOUT when launching any database process.
Workaround
After a database crash, truncate the bi file before starting the database managed by the AdminServer:

$   proutil <dbname> -C truncate bi -crStatus 15 -crTXDisplay

Note: The parameters -crStatus and -crTXDisplay work only with proserve and proutil -C truncate bi. 

For further information refer to Article  How to display how far along bi crash recovery is within the whole process?  

Alternatively, remove the Crash Recovery Status (-crStatus) and Crash Recovery Transaction Display (-crTXDisplay) parameters from the conmgr.properties file.
Notes
Keyword Phrase
Last Modified Date5/9/2023 8:01 PM

Powered by