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 
<[EMAIL PROTECTED]>     
                    <SMorrow@admin       cc:                                           
                          
                    .usf.edu>            Subject:     Temporarily Renaming the 
sgadefSID.dbf File                
                    Sent by:                                                           
                          
                    [EMAIL PROTECTED]                                                     
                          
                    om                                                                 
                          
                                                                                       
                          
                                                                                       
                          
                    10-04-2001                                                         
                          
                    22:35                                                              
                          
                    Please respond                                                     
                          
                    to ORACLE-L                                                        
                          
                                                                                       
                          
                                                                                       
                          



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).




=====================================================================
De informatie verzonden in dit e-mailbericht is vertrouwelijk en is
uitsluitend bestemd voor de geadresseerde. Openbaarmaking,
vermenigvuldiging, verspreiding en/of verstrekking van deze informatie aan
derden is, behoudens voorafgaande schriftelijke toestemming van Ernst &
Young, niet toegestaan. Ernst & Young staat niet in voor de juiste en
volledige overbrenging van de inhoud van een verzonden e-mailbericht, noch
voor tijdige ontvangst daarvan. Ernst & Young kan niet garanderen dat een
verzonden e-mailbericht vrij is van virussen, noch dat e-mailberichten
worden overgebracht zonder inbreuk of tussenkomst van onbevoegde derden.

Indien bovenstaand e-mailbericht niet aan u is gericht, verzoeken wij u
vriendelijk doch dringend het e-mailbericht te retourneren aan de verzender
en het origineel en eventuele kopieën te verwijderen en te vernietigen.

Ernst & Young hanteert bij de uitoefening van haar werkzaamheden algemene
voorwaarden, waarin een beperking van aansprakelijkheid is opgenomen. De
algemene voorwaarden worden u op verzoek kosteloos toegezonden.
=====================================================================
The information contained in this communication is confidential and is
intended solely for the use of the individual or entity to whom it is
addressed. You should not copy, disclose or distribute this communication
without the authority of Ernst & Young. Ernst & Young is neither liable for
the proper and complete transmission of the information contained in this
communication nor for any delay in its receipt. Ernst & Young does not
guarantee that the integrity of this communication has been maintained nor
that the communication is free of viruses, interceptions or interference.

If you are not the intended recipient of this communication please return
the communication to the sender and delete and destroy all copies.

In carrying out its engagements, Ernst & Young applies general terms and
conditions, which contain a clause that limits its liability. A copy of
these terms and conditions is available on request free of charge.
=====================================================================





--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
  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).

Reply via email to