Re: bug 2322620

  • From: "Jonathan Lewis" <jonathan@xxxxxxxxxxxxxxxxxx>
  • To: <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 27 May 2004 07:02:29 +0100

I haven't any information about the parameter and its use,
but here's the name and description of the one that looks
the most obvious:

_corrupt_blocks_on_stuck_recovery
        number of times to corrupt a block when media recovery stuck

There's a script on the website or FAQ below
for listing the hidden parameters.

Regards

Jonathan Lewis

http://www.jlcomp.demon.co.uk

http://www.jlcomp.demon.co.uk/faq/ind_faq.html
The Co-operative Oracle Users' FAQ

http://www.jlcomp.demon.co.uk/seminar.html
Optimising Oracle Seminar - schedule updated May 1st


----- Original Message ----- 
From: <Rhojel_Echano@xxxxxxx>
To: <oracle-l@xxxxxxxxxxxxx>
Sent: Wednesday, May 26, 2004 11:06 AM
Subject: bug 2322620


Hi everyone,
Anybody encountered bug 2322620? It manifests as a "Stuck Recovery"
situation and according to Oracle support, the only workaround is to allow
Oracle to corrupt a block on recovery. In my case, an LOB segment is
causing this.
When the archived logs are being applied to Standby DB and changes on
an LOB segment are present in the log, the recovery session halts with
Ora600.

Here's an excerpt of the bug's text from Metalink:


"For Oracle 8 and Oracle 8i, there is also a hidden init.ora parameter
that one can set to tell Oracle to corrupt the block and continue. Contact
Oracle Support if you need to use this method. "

If anyone can tell me this parameter, then I'll be very glad to be
relieved
from the burden of waiting for Oracle support response.

TIA,
Rhojel Echano



----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Other related posts: