I am working with Oracle right now on a similar problem
which looks to be like a network problem depending on the
versions of what you are running. There is a bug that
was fixed in 8.1.7.3 dealing with 3113 errors. Dont
know what version you are running, but that could
have something to do with
the CDUMP directory
created around the same time?
Hopefully, the first thing you did was log a TAR on
MetaLink, right?
- Original Message -
From: "Nguyen, David M" <[EMAIL PROTECTED]>
To: "Multiple recipients of list ORACLE-L"
<[EMAIL PROTECTED]>
S
Did you read Note:1069812.6 on Metalink yet?
Tim
-Original Message-
Sent: Tuesday, October 15, 2002 11:54 AM
To: Multiple recipients of list ORACLE-L
I have oracle8.0.5 running on Solaris8. Here's trace file. I don't think
there is problem with I/O. How do I recover this error?
$m
I have oracle8.0.5 running on Solaris8. Here's trace file. I don't think
there is problem with I/O. How do I recover this error?
$more ssdb_lgwr_272.trc
Dump file /export/home/oracle/product/8.0.5/rdbms/log/ssdb_lgwr_272.trc
Oracle8 Enterprise Edition Release 8.0.5.2.1 - Production
PL/SQL Re
Your instance crashed because the lgwr died... There should be a trace file
for lgwr in the bdump directory... What does it say in the trace file? Are
you having any filesystem issues? The "LGWR: terminating instance due to
error 204" means that there is an I/O error when accessing the
control
At least one of your control files is corrupted, or the disk it
is on is bad:
00204, 0, "error in reading (block %s, # blocks %s) of controlfile"
// *Cause: A disk I/O failure was detected on reading the controlfile.
// *Action: Check if the disk is online, if it is not, bring it online and
