Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Shutdown abort: could not shutdown the database....

Shutdown abort: could not shutdown the database....

From: <zigzagdna_at_yahoo.com>
Date: Tue, 31 Jul 2007 12:00:38 -0700
Message-ID: <1185908438.395078.148890@z28g2000prd.googlegroups.com>

I am using Oracle 10.1.0.4 on Windows Server 2003. Today, in production, no one could connect to database. They will just keep waiting and may get an error:

ORA-25254: time-out in LISTEN while waiting for a message
ORA-06512: at "SYS.DBMS_AQ", line 577
ORA-06512: at "SYSMAN.EMD_NOTIFICATION", line 509
ORA-06512: at line 1

Aletrt.log had same message (i.e., problem was not because some folder was 100%full lor no of processes exceeded).

I wanted to restart the database. Windows Service was up, so I connected to database and ran:
Shutdown abort
However abort got hung as well. Waited for 10 minutes, then I tried to restart Oracle Windows Service. Windows Service will not start. Oradim.log did not have any useful information, same was true for event log.

Eventually, I rebooted Windows Server and everything started working.

Can anything be done to avoid this problem other than moving off of Windows Server which is not practical.
Thanks.
I am using Oracle 10.1.0.4 on Windows Server 2003. Today, in production, no one could connect to database. They will just keep waiting and may get an error:

ORA-25254: time-out in LISTEN while waiting for a message
ORA-06512: at "SYS.DBMS_AQ", line 577
ORA-06512: at "SYSMAN.EMD_NOTIFICATION", line 509
ORA-06512: at line 1

Aletrt.log had same message (i.e., problem was not because some folder was 100%full lor no of processes exceeded).

I wanted to restart the database. Windows Service was up, so I connected to database and ran:
Shutdown abort
However abort got hung as well. Waited for 10 minutes, then I tried to restart Oracle Windows Service. Windows Service will not start. Oradim.log did not have any useful information, same was true for event log.

Eventually, I rebooted Windows Server and everything started working.

Can anything be done to avoid this problem other than moving off of Windows Server which is not practical.
Thanks. Received on Tue Jul 31 2007 - 14:00:38 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US