Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Waiting for smon to disable tx recovery.
The problem was the initial and next extent size on our temporary
tablespace. On June 3, someone changed it from 2mb to 64k which caused us
to have over 50,000 extents when we bounce the database each night. Of
course it takes along time for Oracle to clean these up.
When we put the extents sizes back to 2mb, all is well.
Thanks for all of your assistance.
Tom
-----Original Message-----
From: Khushalani, Vikram [mailto:vkhushalani_at_grci.com]
Sent: Thursday, June 15, 2000 10:47 AM
To: 'oracledba_at_quickdoc.co.uk'; 'ORACLE-L_at_fatcity.com'
Subject: RE: Waiting for smon to disable tx recovery.
A number of things you could look at including Temporary Tablespace since this is often due to Temporary Tablespace issues also -
(Just a side note - I have often read that a 'shutdown normal' is best
before a backup - so that is what we do)
4) If you have the Oracle Intelligent Agent, any other process, or monitoring tool running then close that process before your attempted shutdown.
Please post the success/failure of all this.
Vikram Khushalani
Oracle DBA
-----Original Message-----
From: Terrian, Thomas [mailto:Thomas.Terrian_at_standardregister.com]
Sent: Thursday, June 15, 2000 7:55 AM
To: 'oracledba_at_quickdoc.co.uk'; 'ORACLE-L_at_fatcity.com'
Subject: Waiting for smon to disable tx recovery.
Does anyone else see this in their alert log file when they bounce their database?:
Waiting for smon to disable tx recovery.
It is happening more and more at my site. Last night we got it 18 times. We do the following each night:
1. Shutdown abort. 2. Startup 3. Shutdown immediate 4. Do our backups 5. Startup
We get the warning messages during step 3. Each time we get the message there is a 5 minute delay so it took us over an hour to bounce the database last night.
AIX 4.3.2, Oracle 8.1.6.1.0
Any ideas?
Tom Terrian
Oracle DBA
(937) 221-1647
Thomas.Terrian_at_standardregister.com