DB Shutdown Problem

[fighter]

Hi Friends,

I have a problem with shutting down the database.

When the DB is up for say a couple of months, and if try to use shutdown immediate it takes a long time and does not bring the DB down.

Ultimately I have to use shutdown abort ---> startup and then use
shutdown immediate, which works fine.

Can anyone help me with reason for the same and resolution to this.

Regds,

[dhar_kiran]

It might be, because Processes are taking much time in rollbacking
current transactions(because of heavy DML's), when u give shutdown immediate command.

1. Yes, The best thing you can do is, shutdown abort ->startup restrict -> shutdown normal

[davey23uk]

no, the best thing you can do is analyze the problem and see what is going on

[dhar_kiran]

ok..then Davey what could be the reason?????

[gandolf989]

ok..then Davey what could be the reason?????

Have you read the alert log lately?

[davey23uk]

just guessing and using shutdown abort isnt a solution

[gandolf989]

just guessing and using shutdown abort isnt a solution

I was at Oracle Open World a few years ago, and one of the presenters suggested that people always use shutdown abort.

[davey23uk]

name and shame my dear fellow

[fighter]

Below is a snapshot of alert log file.

Is it something related to License high water mark = 364.

Sun Apr 23 02:01:07 2006
Shutting down instance (immediate)
License high water mark = 364
Sun Apr 23 02:06:16 2006
SHUTDOWN: waiting for active calls to complete.
Sun Apr 23 02:38:41 2006
Shutting down instance (immediate)
License high water mark = 364
Sun Apr 23 02:40:23 2006
Shutting down instance (abort)
License high water mark = 364
Instance terminated by USER, pid = 13418
Sun Apr 23 02:40:37 2006
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
LICENSE_MAX_USERS = 0
Starting up ORACLE RDBMS Version: 8.1.6.0.0.
System parameters with non-default values:
processes = 350
sessions = 450
timed_statistics = TRUE
.
.
.
.
.
.

[davey23uk]

Sun Apr 23 02:06:16 2006
SHUTDOWN: waiting for active calls to complete.

there you go, check v$transaction to see what is going on at that time