Re: ORA-00472 PMON terminated with error

Yet more information, from the DBWR trace log this time.

If it matters to help diagnose the cause of the error: I'm writing to an optical drive that is set to act like a hard drive.

I cannot log in to Oracle to shut down-- ORA-472 error. Should I simply bring the NT O/S down?

I've never had to recover an Oracle database -- but I don't need to worry about this particular data set; however, I would like to bring the system back to a stable state.

Advice is appreciated.

TIA
Tim

KCF write/open error dba-0xe006e22 block = ox6e22 online=1 file=14 G:\mtlife\mtlife_d.ora
error=9215 txt: 'OSD-04016: error queuing an asynchronous I/O request.' error 1242 detected in background process OPIRIP: Uncaught error 447. Error stack:

ORA-00447: fatal error in background process
ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
ORA-01114: IO error writing block to file 14 (block #28194)
ORA-01110: data file 14: 'g:\mtlife\mtlife_d.ora'
ORA-09215: sfqio: error detected in IOCompletionRoutine
OSD-04016: Error queuing an asynchronous I/O request.

Tim Romano wrote in message <6kd3v2$3dc2_at_helium.superstream.net>...
>Here's some additional info (I found the PMON trace file):
>
>SESSION ID:(1.1) 1998.05.25.20.42.55.207
>error 471 detected in background process
>OPIRIP: uncaught error 447. Error stack:
>ORA-00447: fatal error in background process
>ORA-00471: DBWR process terminated with error
>
>TIA
>Tim
>
>
>
>
>
>Tim Romano wrote in message <6kd3jn$3dc1_at_helium.superstream.net>...
>>I was updating a Personal Oracle 7.3 database running under Windows NT and
>>got the following error: ORA-00472 PMON process terminated with error
>>
>>I found the following explanation on the web and would appreciate some
>hints
>>with regard to the "background process trace file". What is it called and
>>where is it located?
>>
>>TIA,
>>Tim
>>--------------
>>Cause: The Process Monitor process terminated abnormally.
>>Action: Check the accompanying messages, if any, and the background
process
>>trace file. Correct the problem mentioned in the other messages. Then shut
>>down and restart the instance. If the trace file mentions any other
>>background process messages, check the trace file for the mentioned
>process
>>until the root message is found.
>>---------------
>>
>>
>>
>
>
Received on Mon May 25 1998 - 21:39:34 CDT