Salesforce

How to display how far along bi crash recovery is within the whole process?

« Go Back

Information

 
TitleHow to display how far along bi crash recovery is within the whole process?
URL NameHow-to-display-how-far-bi-crash-recovery-is-within-the-whole-process
Article Number000180207
EnvironmentProduct: OpenEdge
Version: 11.6.1 and later
OS: All supported platforms
Question/Problem Description
How to display how far along bi crash recovery is within the whole process ?
How long will bi crash recovery take and how many transactions need to be undone ?
How to estimate of the progress of the current bi crash recovery phase ?
Determining if there are many transactions to back out during crash recovery, or only one long-running transaction
Steps to Reproduce
Clarifying Information
Error Message
Defect NumberEnhancement PSC00248780
Enhancement Number
Cause
Resolution
OpenEdge 11.6.1 enabled two new parameters to assist in predicting how long crash recovery will take and report on how many transactions are involved :
  • Crash Recovery Status (-crStatus) defaults to 30 seconds when not specified.
  • Crash Recovery Transaction Display (-crTXDisplay) must be specified to enable it.
Note: The parameters -crStatus and -crTXDisplay work only with proserve and proutil -C truncate bi. 

Syntax: -crStatus n
 
Where "n" is the time, in seconds, between crash recovery progress messages.
The default is 30 seconds.
Specify 0 to turn off crash recovery progress messages
Each crash recovery progress message contains the following details to the screen only:
  • The current crash recovery phase.
  • An estimate of the progress of the current crash recovery phase, expressed as the percent complete.
  • The current block being processed.
  • The total number of elapsed seconds for the current phase 
  • Optionally, if -crTXDisplay is also specified, the counter of the BI cluster.

Syntax: -crTXDisplay 

Transaction display message contains the following to the screen only:
  • The transaction ID 
  • The timestamp when the transaction began 
  • The user number that initiated the transaction 
  • The counter of the BI cluster that was current when the transaction began 
Example:  

$   proutil dbname -C truncate bi -crStatus 10 -crTXDisplay
 
OpenEdge Release 11.6.3 as of Thu Sep  8 19:01:50 EDT 2016

Transaction 27973 by user 7 at 2017/02/08@12:02:15. Counter: 1
Transaction 27975 by user 5 at 2017/02/08@12:02:47. Counter: 123

Physical Undo  6% at block 13047. 969 blocks processed in 10 seconds. Counter: 408

Logical Undo 24% at block 10525. 3491 blocks processed in 20 seconds. Counter: 329
Logical Undo 35% at block 9072. 4944 blocks processed in 30 seconds. Counter: 284
Logical Undo 42% at block 8017. 5999 blocks processed in 40 seconds. Counter: 251
Logical Undo 50% at block 6976. 7040 blocks processed in 50 seconds. Counter: 219
Logical Undo 70% at block 4094. 9922 blocks processed in 60 seconds. Counter: 128
Logical Undo 79% at block 2901. 11115 blocks processed in 70 seconds. Counter: 91
Logical Undo 88% at block 1576. 12440 blocks processed in 80 seconds. Counter: 50
Logical Undo 97% at block 363. 13653 blocks processed in 90 seconds. Counter: 12
Logical Undo 100% at block 0. 14016 blocks processed in 93 seconds. Counter: 1

For Crash Recovery Status with databases started by the AdminServer:

Since OpenEdge 11.7.4 or later, from the OE Console, navigate to the Database Configuration, Default Configuration and add these parameters in the General section ---- other arguments:-crStatus 5 -crTXDisplay

For versions prior to OpenEdge 11.6.1

Refer to the advice provided in the Workaround Section of Article:
Workaround
Notes
Keyword Phrase
Last Modified Date5/9/2023 7:59 PM

Powered by