Really appreciate this! Thanls for sharing this and wishing you all the best

Rgs,
Ivan

If you have already executed …
SQL> Shutdown normal;

which will wait forever, until users finish and disconnect,
then how do you change/switch the style of shutdown to use a
SQL> Shutdown immediate
instead ?? They’re BOTH doing a shutdown, and it’s just a matter of whether the database waits or not… and as a DBA, I might want to speed up the
process of doing a shutdown, without doing something drastic, like a SQL> Shutdown abort;

I’m thinking of a syntax more like:
SQL> alter system shutdown type=immediate;
. . . (which is not real syntax, just example )
I know that I could forcably kill every database session, and let the database shutdown after all user connections are gone; but I’d rather see a cleaner syntax.

Now, if that is possible, here’s a slightly harder one:
You are on a large production server, with several client & user apps, plus hundereds of users, when somebody issues a SQL> Shutdown Immediate;
Oracle starts ending transactions, and performing rollbacks, but ti will be several minutes before the
DB-sessions are terminated, and the database is actually shut down. Since I’m a DBA, I can still connect to the database with sqlplus. In the next 2 minutes, how do I issue a command to CANCEL an Oracle shutdown that’s already in progress, and tell the database to Stay UP, returning to normal “open” production status?? (so most of the applications don’t go down, & 75% of the users aren’t even affected??)

There *is* a command of:
SQL> Startup Force;
But inside Oracle, it actually performs a faster
::: Shutdown Abort followed by a
::: Startup

So, while the database does come up in 2 minutes, the Apps+users are cut off from the database, and have to re-connnect, or even re-start dozens of applicationsl

For this, I just want to have Oracle *stop* what it’s doing, return to open/un-restricted status, and stay in regular production. I’m thinking some other
command like ALTER SYSTEM, force open cancel shutdown;
Alter system disable restricted session;
( or something like that )

The desired effect iw that SGA stays in memory, most users/apps only pause for a bit, but never disconnect, the database is quickly back on-line, and running productively.

So — if you fined these, let me know.

greatings.

Best regards

Horst