When I read some of the mailing lists, I discover that the shutdown immediate problem is quite common.
The most common solution suggested to this problem is to do :
But it is also suggested to force a checkpoint before i issue a
"shutdown abort" command.
When we issue "shutdown abort" command, instant recovery is required at the next database startup.
Now when we give startup restrict command, will the database do recovery in the background by using the online redo log files ???
How much time should I wait for before I issue shutdown immediate command after issuing startup restrict since the database might be doing
instant recovery in hte background ????
Thanks for your help !!
Originally posted by bikramjeet77
I have a problem while shutting down Oracle8i database.
Every morning the cronjob shuts down the database and takes the backup and starts it up again.
It works most of the time.
But what happens sometimes is that the database doesnt shutdown and keeps hanging.
I try to shutdown the database using the command:
SQL> shutdown immediate
When I see the trace file, I see this line in the file:
"SHUTDOWN: waiting for active calls to complete"
This line is repeated throught the file from the time that I gave the shutdown command.
Is it because too many oracle user processes are running at that time ??
Because on an average, over 100 users access the site simultenoulsy.
Or what else could be the reason that the database doesnt shutdown and keeps waiting forever ????