| 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: 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
-----Original Message-----
Sent: Wednesday, April 11, 2001 5:06 AM
To: Multiple recipients of list ORACLE-L
Hi
We clone very frequent (once a week at least) on the same machine and never encountered that problem yet, What are the steps you are taking??
Jack
"Morrow,
Steve" To: Multiple recipients of list
ORACLE-L <ORACLE-L_at_fatcity.com>
<SMorrow_at_admin cc:
.usf.edu> Subject: Temporarily Renaming
the sgadefSID.dbf File
Sent by:
root_at_fatcity.c
om
Hi All,
Trying to clone our PROD to a test database on the same machine for testing our 734-->8i upgrade, and of course we're encountering the "can't-start-the-new-without-shutting-down-the-old" database problem (ie, ORA-9782 on the CREATE CONTROLFILE command). We've worked around this in the past by scheduling a time to bring down PROD.
I know that this is the safest, most reliable way (besides NOT doing this
on
a production box...but I have no choice), but believe it or not, I actually
saw a reference on a Metalink forum to rename the sgadefSID.dbf file, start
up the new database, then rename the file to its original name. Obviously
sgadef gets created at instance startup as a memory map, but it doesn't
look
like it's used for anything after that (it's certainly doesn't seem to be
written to). I do know that you can get an octal dump of the file to
determine the shared memory ID for whatever reason.
Everything else I've heard/seen about this file has pretty much said DON'T TOUCH IT!!! But if the instance only uses it at instance startup, is there any harm in renaming it temporarily to get the other database up? If so...why?
And have any of you tried renaming or deleting the file in your cloning (or other) efforts? Did it blow up, or work?
TIA,
Steve
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). Received on Wed Apr 11 2001 - 11:39:07 CDT
 |
 |