@24-JAN-01, rpowell.uk, Distribution justification: "Leaving as
@ noncustomer-viewable, since says customers should never set this
@ event unless advised to do so by support." - dbither.us
Event: 10013
Text: Instance Recovery
-------------------------------------------------------------------------------
Note:
Events should NEVER be set by customers unless advised to do so by
Oracle Support Services. See for more details.
Explanation:
This event displays useful messages about the state of transaction
recovery directly to the trace files. This can help to diagnose problems
related to transaction recovery and is best used in conjunction with
some other event such as to dump the UBA's as applied.
Example Output:
+++ Instance Recovery Started +++
Instant Recovery: cache recovery returned.
SMON: about to recover undo segment %d ****
SMON: lock conflict caught and ignored ****
SMON: mark undo segment %d as %s ****
Recovering transaction (%d, %d)
Fully recovered transaction (2, 18) by (3) rec
Partially recovered transaction (4, 20) by (20) rec
+++ End of Instance Recovery +++
%d is a number
%s is a string eg: 'available' or 'need recovery'
**** These three type of message also appear in the alert file.
e.g:
SMON: about to recover undo segment 2
SMON: mark undo segment 2 as available
© 2008 – 2011, www.oracledatabase12g.com. 版权所有.文章允许转载,但必须以链接方式注明源地址,否则追究法律责任.
相关文章 | Related posts:
- EVENT: 10015 "Write Trace for Undo Segment Recovery"
- Database Hangs Because SMON is taking 100% CPU doing transaction recovery
- EVENT:10061 disable SMON from cleaning temp segment
- EVENT:10218 dump uba of applied undo
- EVENT:10052 “Stop SMON from cleaning up obj$”
- EVENT:10226 trace CR applications of undo for data
- EVENT: 10500 “turn on traces for SMON”
- EVENT:10228 trace application of redo by kcocbk
- VIEW: X$KTUXE – Transaction Entry (table)
- EVENT:10211 check index block integrity
最新评论