Kbase P30672: What are the error messages that are written to the log when dealing with 2Phase and going through C
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/23/2010 |
|
Status: Verified
GOAL:
What are the error messages that are written to the log when dealing with 2Phase and going through Crash Recovery?
GOAL:
What error messages will I receive when starting 2Phase without performing recovery?
GOAL:
What error messages will I receive when starting 2Phase with the recover option?
GOAL:
If I have 2Phase enabled and experience a crash which results in limbo transactions, how will these limbo transactions be identified on startup?
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
FIX:
You will receive these errors when starting 2Phase and there are limbo transactions present within the database:
The database contains limbo transactions. (2043)
Transaction , on coordinator #, is in a limbo state. (2038)
See list on the *.lg file. Use proutil <dbname> -C 2phase recover. (2042)
These errors mean that during crash recovery, one or more limbo distributed transactions were found and listed in the database log (.lg) file. Use the 2phase recover option of proutil to commit or abort them.
If you have used the recover option to proutil (proutil dbname -C 2phase recover) you receive the following messages on initialization:
Transaction , on coordinator #, is in a limbo state. (2038)
Commit transaction , on coordinator # (y commit, n abort, q quit)? (2039)
Are you sure you want to commit <transaction-number> (y
)? (2040)
or
Are you sure you want to abort <transaction-number> (y
)? (2041)
Then appropriate action will then be recorded in the transaction log.