Re: Shutdown abort: could not shutdown the database....
- From: zigzagdna@xxxxxxxxx
- Date: Tue, 31 Jul 2007 12:51:39 -0700
On Jul 31, 3:37 pm, sybra...@xxxxxxxxx wrote:
On Tue, 31 Jul 2007 12:00:38 -0700, zigzag...@xxxxxxxxx wrote:
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.
Two things
- upgrade to a supported version of Oracle (10gR1 is desupported)
- alter system set aq_tm_processes = 0 prior to shutdown
- kill any jobs inside Oracle related to aq
Apart from that move to a scalable O/S
On Unix you would just find the process id of the dbwr and issue a
kill -9 on that and presto...
--
Sybrand Bakker
Senior Oracle DBA- Hide quoted text -
- Show quoted text -
Thanks. aq_tm_process was alreday set to 0. job_queue_processes=10
which I think is needed by OEM (databse conrol).
.
- Follow-Ups:
- Re: Shutdown abort: could not shutdown the database....
- From: sybrandb
- Re: Shutdown abort: could not shutdown the database....
- References:
- Shutdown abort: could not shutdown the database....
- From: zigzagdna
- Re: Shutdown abort: could not shutdown the database....
- From: sybrandb
- Shutdown abort: could not shutdown the database....
- Prev by Date: Re: some process flooding oracle's .sh_history file
- Next by Date: Recommendations sought for good RAC monitoring tool
- Previous by thread: Re: Shutdown abort: could not shutdown the database....
- Next by thread: Re: Shutdown abort: could not shutdown the database....
- Index(es):
Relevant Pages
|
