RE: Temporarily Renaming the sgadefSID.dbf File

Hi Steve,

Yes, you MUST rename the sgadefPROD.dbf file while the CREATE CONTROLFILE command is issued, or you'll get that error on 7.3. This is fixed in 8.0 and up.

The inability to do a daily hotbackup of our PROD db to TEST was a big enough problem for us that I logged a TAR. It was Oracle's solution (workaround) to rename the sgadef file. So, I figured my arse was covered in case of catastrophy. :)

We were running a script daily that did a backup of PROD to TEST, renamed the sgadefPROD file, CREATE CONTROLFILE SET DATABASE "TEST" RESETLOGS, renamed the sgadefPROD file back, and attempted auto-recovery via RECOVER DATABASE USING BACKUP CONTROLFILE. Under 8, we're still doing the same, sans sgadef moves.

Good luck!

Rich Jesse                          System/Database Administrator
Rich.Jesse_at_qtiworld.com             Quad/Tech International, Sussex, WI USA

> -----Original Message-----
> From: Morrow, Steve [mailto:SMorrow_at_admin.usf.edu]
> Sent: Wednesday, April 11, 2001 12:01
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Temporarily Renaming the sgadefSID.dbf File
>
>
> I appreciate the responses I've gotten.
>
> Jack, we're running 734 and 8i on four different Sun boxes
> (all running
> Solaris 8). Only one has given us any problems. Otherwise,
> we can clone
> away on the other three either by one: shutting down the
> source database,
> copy the source datafiles to the new target filesystem,
> making the necessary
> mods to the new init.ora and create-controfile script (including new
> db_name, new paths, etc), bringing up the new database, then
> the source
> database, or two: restoring a backup from the source
> database to the same
> machine but different filesystem, recreating the controlfile,
> and starting
> it up. We haven't encountered the ORA-9782 on either of
> these as far as I
> can remember. Why we have the problem on this one box I have
> absolutely no
> idea.
>
> For the "problem" box, we restore the hot backup files to another
> filesystem, copy and modify the init.ora of the source, backup the
> controlfile to trace (of the source) and modify this for the
> target (new
> db_name and everything). We shut down the source database, run the
> create-controlfile script against the new (with ORACLE_SID
> set to the new),
> then startup the source. No problem.
>
> If we keep the source database up, then the
> create-controlfile script does a
> STARTUP NOMOUNT, then proceeds to the CREATE CONTROLFILE,
> only to bomb with:
>
> CREATE CONTROLFILE SET DATABASE "DVL5" RESETLOGS ARCHIVELOG
> *
> ORA-01503: CREATE CONTROLFILE failed
> ORA-01565: error in identifying file
> '/u01/oradata/DVL5/system01.dbf'
> ORA-09782: sfifi: another instance has the same database mounted.
>
> We have actually gotten around this once by rcp'ing the
> restored files to
> one of the other boxes, creating the controlfile there...then
> shutting down
> the database and copying all the files back to the "problem"
> box. In this
> case, we were able to start the database just fine. But now
> we don't have
> the space on the "temp" box to hold all the datafiles, so
> this isn't an
> option.
>
> Hope this makes sense to somebody. Assuming that it *is* the
> presence of
> the sgadef.dbf file, this is why I've asked if I can work
> around the error
> by renaming the file for the duration of bringing the new
> database up. I
> understand that we won't have to worry about this anymore in 8i.
>
> Thanks again!
> Steve

This message has been scanned for viruses with Trend Micro's Interscan VirusWall.

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Jesse, Rich
  INET: Rich.Jesse_at_qtiworld.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).