Sep 05

ORA-01097

Every once in a while, a person comes across something that has been around forever but is a new experience for them. Just today, I hit the ORA-1097 error for the first time in my career. I was in a test database and needed to shut it down.

SQL> shutdown immediate
ORA-01097: cannot shutdown while in a transaction - commit or rollback first

It is the men who become the victim http://downtownsault.org/barishs/ cheap cialis to this particular issue. Before achat cialis cipla taking any herbal or dietary supplements, the man must consult a doctor and only then follow recommended for of medication or natural treatment as prescribed. Taking Kamagra tablets effectively treats the condition allowing downtownsault.org purchase levitra you to have a valid prescription from your licensed doctor. Visit our home page and get click here now online viagra if you have the following conditions Men who are allergic to sildenafil or any other content in erectile dysfunction in many ways.

The solution is obvious. Either commit my transaction or roll it back and then I can proceed.
SQL> commit;




Commit complete.




SQL> shutdown immediate


Database closed.


Database dismounted.


ORACLE instance shut down.
With such a low error number, this must have been around for a very long time. At first I was taken aback by the error. What do you mean I can’t shutdown my instance? Then I read the error message and realized what was happening. I guess this makes sense. Oracle wants to know what to do with your transaction before the shutdown can commence. If you do a SHUTDOWN ABORT, Oracle won’t give you this message but will rollback the transaction on instance recovery.
The moral of the story is even if you have been around a long time and seen a lot, you haven’t seen it all.

bpeasland