We just had two cases of the [2662] with two completely different customers on the same day as you. The event 10015 or 10020 or 10025 or whatever solved both, but it was weird to have them right on top of each other. What was pretty funny was the fact that when Torben Holm from Miracle ran into it at a customer site he called Morten Egan of Miracle and asked what to do and was REALLY impressed with Mortens incredibly fast answer... until he realised Morten was on a similar case :-). So this is probably a Universal 2662 Thing. Some butterfly out in Brazil flew a bit faster than usual, or something. Mogens Mladen Gogala wrote: > On 07/13/2004 10:55:52 PM, Rivaldi Bahar wrote: > >>That's the undocumented parameter I've tried that I got >>from metalink. >>The result is database recovery completed but >>ora-600[2662] in trace file and the db shutdown when >>trying to 'open resetlogs'. > > > There is also a very well undocumented parameter called: > > _screw_up_database_for_no_particular_reason > > You are on your way to document it. ---------------------------------------------------------------- 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 -----------------------------------------------------------------