-
Hi. Due to error in OS system (W2K) a database crushed on me. Just to be on the safe side I shutdown the database by doing:
ORADIM -SHUTDOWN -SID GLXYN -SHUTTYPE srvc,inst -SHUTMODE i
After it was shutdown, we started up the db by doing
ORADIM -STARTUP -SID GLXYN -STARTMODE AUTO
This hang for an hour, apparntly doing nothing. So after killing to above session, we decided to shutdown the db again using the above example again, which now gave the error
DIM-00018: Failed to stop Oracle service
O/S-Error: (OS 997) Overlapped I/O operation is in progress
Has anyone else ecountered this type of error, and if so, what was the solution?
Cheers
Fiona
-
Sorry Fiona, I've never seen this before. I think the good news is that it is OS error and not an Oracle error. Have you re-booted the server? Did you check the Oracle services?
MH
-
Originally posted by Fiona
[b]a database crushed on me[b]
Thank goodness it was just a database (and not all the Database administrators out here) !!!!
-
I have seen similar issues.
The long startup could be because the database was doing automatic recovery after dealing you the crushing blow. If you had a long running transaction with lots of changes but no commit, it can take just as long for the undo/recovery.
Since it was in recovery, you ran into the io overlap issue.
You should check the alert log to see if it was in recovery (many of the later releases of Oracle will but a statement about recovery starting and completing there.)
