Database Administration (MOSC)

MOSC Banner

event="10513 trace name context forever, level 2" is not disabling SMON transaction recovery

edited Jan 26, 2009 2:35AM in Database Administration (MOSC) 13 comments
 Hi,

We are having shutdown immediate problem after cloning, as soon as duplicate DB completes we try to shutdown the database and it hangs. We could review it and found that there were 12 Dead transactions and 67000 blocks required to be rolled back. We were doubting it so we did set this event at cloning time.

Effectively this event should disable these dead transaction recovery but it does not take effect. This time we let the shutdown coutinue for 4 hours before the shutdown abort. The number of blocks changed from 67000 to 10000. During this 4 hour of time smon was taking 100% cpu. Note -

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center