Steve,
When I was on 7.3.4, I used this procedure every time I cloned, which was
at least weekly.
I never had a problem with Production while doing this. After I cloned the
files, I would rename the
file, bring up the cloned instances, and then name the file back to the
original name.
The file was only with the new name for just a few minutes. I was told by
those around me that users
on the production database could still process, just those signing on had to
retry in a few minutes.
Since usually cloned the test database farily early in the morning [around
6:30 am] , there were very few
attempting to sign on.
After I migrated to 8i, this "file renaming" wasn't required.
HTH,
Bill Gentry
DBA
Allina Health System
Minneapolis, MN 55403
612-775-1190
[EMAIL PROTECTED]
----- Original Message -----
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Tuesday, April 10, 2001 3:35 PM
> 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
> _____________________________
> Steve Morrow
> IT/Tech Support
> University of South Florida
> phone: 813-974-5519
> [EMAIL PROTECTED]
>
> --
> Please see the official ORACLE-L FAQ: http://www.orafaq.com
> --
> Author: Morrow, Steve
> INET: [EMAIL PROTECTED]
>
> 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: [EMAIL PROTECTED] (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).
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Bill Gentry
INET: [EMAIL PROTECTED]
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: [EMAIL PROTECTED] (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).
