Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Possible to recover from failed use of zerodbid

RE: Possible to recover from failed use of zerodbid

From: Mark W. Farnham <>
Date: Fri, 22 Oct 2004 12:38:42 -0400
Message-ID: <>

Did you attempt to shut down, repair init.ora and try again?

If you have to abort or kill outside of Oracle, you may need to ipcrm the shared memory segments before you retry.

If it got to the part where it whacked your online redo logs, you will need to copy those back in from where you saved them as the first part of the "recovery" process. Sometimes (Really, support, I've never done this, wink, wink;) you can take the archived version of that vintage log from your archives on the other system and paste it into the online log.

Someone else may have a more conventional repair if the shut down, fix params, and try again thing doesn't work.



-----Original Message-----
[]On Behalf Of Stephen.Lee_at_DTAG.Com Sent: Friday, October 22, 2004 12:06 PM
Subject: Possible to recover from failed use of zerodbid

No I didn't use the newdbid utility because I forgot about it.

Now that is out of the way, I have an "analyst" on the other end at metalink who just doesn't get the scenario I am describing and refuses to get some help. It's always gratifying to know that those six-figure support fees you pay to Oracle go to help the winos from the Salvation Army shelter find work.

So I'll check on the list to see if anyone knows the black arts that must be applied to recover from the following scenario:

Copied a database.
Recreated the control file changing the database name. Spent a few hours, making changes for the environment for the new database. One of those changes was to reduce the number of rollback segments.
==> Forgot to change the rollback_segments in the init.ora. ($*@#$*@!!)
Went through steps to change dbid using zerodbid. Open resetlogs failed because rollback_segments parameter was wrong. We are now hosed.

As far as I know, some low-level block fiddling is required ??? Or might there be a magic, undocumented command to tell the instance forget about what it sees in file headers and trust me that it's OK to reset everything and open anyway?


Received on Fri Oct 22 2004 - 11:35:13 CDT

Original text of this message