shutdown immediate not going , backup fail

hi, my oracle db is not shutting down, hence backup was hanging. i have provided the logs as below. it comes irregularly. any advise? thanks


Shutting down instance (immediate)
License high water mark = 23

ORACLE V8.0.6.1.0 - Production vsnsta=0
vsnsql=c vsnxtr=3
Windows NT V4.0, OS V5.101, CPU type 586


also, a proper shutdown and backup successful will have these additional logs as below. but when it did not shutdown and backup successful, it is missing the below entries

ALTER DATABASE CLOSE NORMAL
SMON: disabling tx recovery
SMON: disabling cache recovery
Thread 1 closed at log sequence 14326
Completed: ALTER DATABASE CLOSE NORMAL
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT

When you shutdown immediate, that tells the database in laymens terms "Hey I want you to shutdown but only after everyone who is presently connected finishes thier job and don't accept any new connections while you're at it"

So, with that said you either have a process that's out there that is not finished and or hanging up or one that might be rolling back in that case you'd want to see if SMON was out there acting a fool. Often times you'll see an entry in the alert log about SMON finsihing up stuff. I can't remember what the entry says off the top of my head.

Just for grins why don't you post the last hundred lines of your alert log from a failed shutdown.

Quote:

---

Originally posted by OracleDoc
When you shutdown immediate, that tells the database in laymens terms "Hey I want you to shutdown but only after everyone who is presently connected finishes thier job and don't accept any new connections while you're at it"

---

I am sorry but is not what immediate does! That is shutdown transactional

Shutting Down with the IMMEDIATE Option
Use immediate database shutdown only in the following situations:

To initiate an automated and unattended backup
When a power shutdown is going to occur soon
When the database or one of its applications is functioning irregularly and you cannot contact users to ask them to log off or they are unable to log off
To shut down a database immediately, use the SHUTDOWN command with the IMMEDIATE option:

SHUTDOWN IMMEDIATE


Immediate database shutdown proceeds with the following conditions:

No new connections are allowed, nor are new transactions allowed to be started, after the statement is issued.
Any uncommitted transactions are rolled back. (If long uncommitted transactions exist, this method of shutdown might not complete quickly, despite its name.)
Oracle does not wait for users currently connected to the database to disconnect. Oracle implicitly rolls back active transactions and disconnects all connected users.
The next startup of the database will not require any instance recovery procedures.

Shutting Down with the TRANSACTIONAL Option
When you want to perform a planned shutdown of an instance while allowing active transactions to complete first, use the SHUTDOWN command with the TRANSACTIONAL option:

SHUTDOWN TRANSACTIONAL


Transactional database shutdown proceeds with the following conditions:

No new connections are allowed, nor are new transactions allowed to be started, after the statement is issued.
After all transactions have completed, any client still connected to the instance is disconnected.
At this point, the instance shuts down just as it would when a SHUTDOWN IMMEDIATE statement is submitted.
The next startup of the database will not require any instance recovery procedures.


I stand corrected. Thanks pando

here's a link that may help out with your problem.
http://metalink.oracle.com/metalink/...&p_id=164504.1

hi, i am on sap. so i triggered offline backup from one of the
transaction codes. what happens is that the system will issue shutdown
immediate and its not possible for me to intervene manually..

any help?

perhaps it was rolling back a really big transaction

svrmgrl will let you open another session to issue a "shutdown abort". BUT the rollback has to take place sometime, either at shudown or at startup (instance recovery).

Quote:

---

Originally posted by yls177

any help?

---

Don't do a cold backup.

Know what the database is doing instead of trying to administer it from a generic tool.