| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> Re: bug 2322620
Thanks a lot Mr. Lewis.
Best regards,
Rhojel Echano
"Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk>
Sent by: oracle-l-bounce_at_freelists.org
05/27/2004 02:02 PM
Please respond to oracle-l
To: <oracle-l_at_freelists.org>
cc:
Subject: Re: bug 2322620
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/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
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
 |
 |