Home » RDBMS Server » Server Administration » SMON error and DB startup hangup
SMON error and DB startup hangup [message #60168] Tue, 20 January 2004 10:22 Go to next message
wozniaks
Messages: 1
Registered: January 2004
Junior Member
SMON problem (Oracle9i Release 9.0.1.1.1)

I have a job stream that runs daily @ 3AM, where I shut down the production database and then start it up in restricted mode to do an export of production users. It has been running successfully until recently. On the last run the following script terminated when it went to start the database in restricted mode due to the following error:

ORA-00445 – background process SMON did not start after string seconds
The job stream is set up to bypass all other operations and perform a normal startup. The normal startup hung up when it reached the SMON startup (Show in the ALERT.LOG).

Submitted script ‘exp<sid>StrtUpRstrctd.sql’ to shutdown and startup the database in restricted mode

system/<sid>_sys@<sid>
rem ** **************************************************************
rem Program ID: exp<sid>StrtUpRstrctd.sql
rem
rem Description:
rem
rem Run a sqlplus script 'exp<sid>StrtUpRstrctd.sql' which will
rem perform the following statements:
rem
rem shutdown transactional
rem startup restrict
rem
rem This shutdown the database and startup the database
rem again in 'restricted mode' so that users cannot access the
rem database while the export of the database is in progress
rem
rem ** **************************************************************
spool d:oracleexportexpReportexp<sid>StrtUpRstrctd

connect sys/********@<SID> as sysdba

whenever sqlerror exit 2

shutdown transactional

whenever sqlerror exit 4

startup restrict

whenever sqlerror exit 8

spool off

exit

Spool listing of the startup script of database in restrict mode in ‘expStrtUpRstrctd.lst’.

SQL> shutdown transactional
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL>
SQL> whenever sqlerror exit 4
SQL>
SQL> startup restrict
ORA-00445: background process "SMON" did not start after 120 seconds
SQL>
SQL> whenever sqlerror exit 8
SQL>
SQL> spool off

Listing of process from ‘<sid>ALRT.LOG’

Tue Jan 20 03:00:05 2004
Restarting dead background process EMN0
EMN0 started with pid=26
Tue Jan 20 03:00:05 2004
Shutting down instance: further logons disabled
Shutting down instance (transactional)
All transactions complete. Performing immediate shutdown
License high water mark = 40
Tue Jan 20 03:00:09 2004
ALTER DATABASE CLOSE NORMAL
Tue Jan 20 03:00:09 2004
SMON: disabling tx recovery
SMON: disabling cache recovery
Tue Jan 20 03:00:09 2004
Thread 1 closed at log sequence 578
Tue Jan 20 03:00:09 2004
Completed: ALTER DATABASE CLOSE NORMAL
Tue Jan 20 03:00:09 2004
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archiving is disabled
Shutting down archive processes
archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archiving is disabled
Shutting down archive processes
archiving is disabled
Archive process shutdown avoided: 0 active

******** ******** ******** ******** ******** ******** ********
******** ******** ******** ******** ******** ******** ********

Normal Startup of the database

******** ******** ******** ******** ******** ******** ********
******** ******** ******** ******** ******** ******** ********
Tue Jan 20 03:00:16 2004
Starting ORACLE instance (normal)
Starting up ORACLE RDBMS Version: 9.0.1.1.1.
System parameters with non-default values:
processes = 100
sessions = 120
timed_statistics = TRUE
shared_pool_size = 50331648
large_pool_size = 104857600
java_pool_size = 109051904
enqueue_resources = 600
control_files = D:oracleoradata<sid>CONTROL01.CTL, D:oracleoradata<sid>CONTROL02.CTL, D:oracleoradata<sid>CONTROL03.CTL
db_block_size = 4096
db_cache_size = 33554432
compatible = 9.0.0
fast_start_mttr_target = 0
dml_locks = 528
transactions = 132
undo_management = AUTO
undo_tablespace = UNDOTBS
remote_login_passwordfile= EXCLUSIVE
db_domain =
instance_name = <sid>
dispatchers = (PROTOCOL=TCP)(SER=MODOSE), (PROTOCOL=TCP)(PRE=oracle.aurora.server.GiopServer), (PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServer)
max_shared_servers = 40
utl_file_dir = d:oracleutlfile, d:ftp
background_dump_dest = D:oracleadmin<sid>bdump
user_dump_dest = D:oracleadmin<sid>udump
core_dump_dest = D:oracleadmin<sid>cdump
sort_area_size = 524288
db_name = <sid>
open_cursors = 300
Data Guard broker requires Oracle Enterprise Edition license
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
Dump file D:oracleadmin<sid>bdump<sid>ALRT.LOG

******** ******** ******** ******** ******** ******** ********
******** ******** ******** ******** ******** ******** ********

Had to reboot server at this point because could not be
accessed to be shutdown and restarted

******** ******** ******** ******** ******** ******** ********
******** ******** ******** ******** ******** ******** ********
Tue Jan 20 08:30:22 2004
ORACLE V9.0.1.1.1 - Production vsnsta=0
vsnsql=10 vsnxtr=3
Windows 2000 Version 5.0 Service Pack 4, CPU type 586
Starting up ORACLE RDBMS Version: 9.0.1.1.1.
System parameters with non-default values:
processes = 50
sessions = 60
timed_statistics = TRUE
shared_pool_size = 125829120
large_pool_size = 104857600
java_pool_size = 109051904
control_files = D:oracleoradata<sid>CONTROL01.CTL, D:oracleoradata<sid>CONTROL02.CTL, D:oracleoradata<sid>CONTROL03.CTL
db_block_size = 4096
db_cache_size = 109051904
compatible = 9.0.0
fast_start_mttr_target = 0
undo_management = AUTO
undo_tablespace = UNDOTBS
remote_login_passwordfile= EXCLUSIVE
db_domain =
instance_name = <sid>
dispatchers = (PROTOCOL=TCP)(SER=MODOSE), (PROTOCOL=TCP)(PRE=oracle.aurora.server.GiopServer), (PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServer)
max_shared_servers = 40
utl_file_dir = D:oracleutlfile, D:ftp
job_queue_processes = 3
background_dump_dest = D:oracleadmin<sid>bdump
user_dump_dest = D:oracleadmin<sid>udump
core_dump_dest = D:oracleadmin<sid>cdump
sort_area_size = 1048576
db_name = <sid>
open_cursors = 1000
ifile = D:oracleadmin<sid>pfileinit.ora
drs_start = FALSE
Data Guard broker requires Oracle Enterprise Edition license
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
CJQ0 started with pid=8
Tue Jan 20 08:30:25 2004
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Tue Jan 20 08:30:26 2004
alter database mount exclusive
Tue Jan 20 08:30:33 2004
Successful mount of redo thread 1, with mount id 462538916.
Tue Jan 20 08:30:33 2004
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Tue Jan 20 08:30:33 2004
alter database open
Tue Jan 20 08:30:33 2004
Thread 1 opened at log sequence 578
Current log# 1 seq# 578 mem# 0: D:ORACLEORADATA<sid>REDO01.LOG
Successful open of redo thread 1.
Tue Jan 20 08:30:33 2004
SMON: enabling cache recovery
Tue Jan 20 08:30:33 2004
Undo Segment 1 Onlined
Undo Segment 2 Onlined
Undo Segment 3 Onlined
Undo Segment 4 Onlined
Undo Segment 5 Onlined
Undo Segment 6 Onlined
Undo Segment 7 Onlined
Undo Segment 8 Onlined
Undo Segment 9 Onlined
Undo Segment 10 Onlined
Successfully onlined Undo Tablespace 1.
Tue Jan 20 08:30:33 2004
SMON: enabling tx recovery
Tue Jan 20 08:30:36 2004
replication_dependency_tracking turned off (no async multimaster replication found)
Completed: alter database open
Re: SMON error and DB startup hangup [message #60169 is a reply to message #60168] Tue, 20 January 2004 10:42 Go to previous messageGo to next message
Thiru
Messages: 1089
Registered: May 2002
Senior Member
Hi,
do you see a SMON trace file ? It might have more details of why it wasnt able to start. Were there any changes in $ORACLE_HOME (ie binaries , libraries etc) recently.
You could also check with Oracle support to see if there are any bugs associated with this.

-Thiru
Re: SMON error and DB startup hangup [message #60617 is a reply to message #60168] Thu, 19 February 2004 17:04 Go to previous messageGo to next message
ZERLEI
Messages: 2
Registered: February 2004
Junior Member
wich command I can use to see if the SMON is up and running ?
Is there any single command that i can use to see those background processes running ? I can use
SQL> show parameter writer_processes
To see the LGWR background process?
Thanks
Re: SMON error and DB startup hangup [message #60619 is a reply to message #60617] Fri, 20 February 2004 03:49 Go to previous messageGo to next message
Thiru
Messages: 1089
Registered: May 2002
Senior Member
On Unix,

to see all the smon processes
ps -ef&#124grep smon

to see all oracle background,shared server processes etc

ps -ef&#124grep ora_
Re: SMON error and DB startup hangup [message #419936 is a reply to message #60168] Wed, 26 August 2009 04:28 Go to previous messageGo to next message
Nirnay Jaiswal
Messages: 3
Registered: August 2009
Junior Member
In these cases always check free memory on the server. The other processes running on the server may occupy the memory and when you try to restart the db you will have these type of issues. But as the server was rebooted(memory issues are ruled out), so the db started successfully.

When you are having these type of issues, confirm the same by reducing the SGA size and then try to restart the db.

[Updated on: Wed, 26 August 2009 04:50]

Report message to a moderator

Re: SMON error and DB startup hangup [message #420181 is a reply to message #419936] Thu, 27 August 2009 07:33 Go to previous message
JRowbottom
Messages: 5933
Registered: June 2006
Location: Sunny North Yorkshire, ho...
Senior Member
Let the old threads stay asleep - they get grumpy if you wake them up.

I think they've probably fixed their problem at some point in the last 5 years.
Previous Topic: internals of oracle database
Next Topic: 10g database related
Goto Forum:
  


Current Time: Fri Dec 09 04:18:26 CST 2016

Total time taken to generate the page: 0.08995 seconds