TIP 04: Duplicating a Database in 10g by Joel Pèrez

Question

Hi OTN Readers!
Everyday I get connection on Internet and one of the first issues that
I do is to open the OTN main page to look for any new article or any
new news about the Oracle Technology. After I open the main page of
OTN Forums and I check what answers I can write to help some people
to work with the Oracle Technology and I decided to begin to write some
threads to help DBAs and Developers to learn the new features of 10g.
I hope you can take advantage of them which will be published here in
this forum. For any comment you can write to me directly to : [email protected] . Apart from your comments you can suggest to me any topic to write an article like this.
Please do not replay this thread, if you have any question related to
this I recommend you to open a new post. Thanks!
The tip of this thread is: Duplicating a Database in 10g
Joel Pérez
http://otn.oracle.com/experts

Answer 1

Step 6: Editing the file generated
The file generated is going to be like this:
Dump file f:\ora9i\admin\copy1\udump\copy1_ora_912.trc
Thu May 20 16:27:37 2004
ORACLE V9.2.0.1.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.0 Service Pack 4, CPU type 586
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Windows 2000 Version 5.0 Service Pack 4, CPU type 586
Instance name: copy1
Redo thread mounted by this instance: 1
Oracle process number: 10
Windows thread id: 912, image: ORACLE.EXE
*** SESSION ID:(9.38) 2004-05-20 16:27:37.000
*** 2004-05-20 16:27:37.000
# The following are current System-scope REDO Log Archival related
# parameters and can be included in the database initialization file.
# LOG_ARCHIVE_DEST=''
# LOG_ARCHIVE_DUPLEX_DEST=''
# LOG_ARCHIVE_FORMAT=ARC%S.%T
# REMOTE_ARCHIVE_ENABLE=TRUE
# LOG_ARCHIVE_MAX_PROCESSES=2
# STANDBY_FILE_MANAGEMENT=MANUAL
# STANDBY_ARCHIVE_DEST=%ORACLE_HOME%\RDBMS
# FAL_CLIENT=''
# FAL_SERVER=''
# LOG_ARCHIVE_DEST_1='LOCATION=f:\ora9i\RDBMS'
# LOG_ARCHIVE_DEST_1='MANDATORY NOREOPEN NODELAY'
# LOG_ARCHIVE_DEST_1='ARCH NOAFFIRM SYNC'
# LOG_ARCHIVE_DEST_1='NOREGISTER NOALTERNATE NODEPENDENCY'
# LOG_ARCHIVE_DEST_1='NOMAX_FAILURE NOQUOTA_SIZE NOQUOTA_USED'
# LOG_ARCHIVE_DEST_STATE_1=ENABLE
# Below are two sets of SQL statements, each of which creates a new
# control file and uses it to open the database. The first set opens
# the database with the NORESETLOGS option and should be used only if
# the current versions of all online logs are available. The second
# set opens the database with the RESETLOGS option and should be used
# if online logs are unavailable.
# The appropriate set of statements can be copied from the trace into
# a script file, edited as necessary, and executed when there is a
# need to re-create the control file.
#     Set #1. NORESETLOGS case
# The following commands will create a new control file and use it
# to open the database.
# Data used by the recovery manager will be lost. Additional logs may
# be required for media recovery of offline data files. Use this
# only if the current version of all online logs are available.
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "COPY1" NORESETLOGS  NOARCHIVELOG
--  SET STANDBY TO MAXIMIZE PERFORMANCE
    MAXLOGFILES 50
    MAXLOGMEMBERS 5
    MAXDATAFILES 100
    MAXINSTANCES 1
    MAXLOGHISTORY 226
LOGFILE
  GROUP 1 'C:\COPY1\COPY1\REDO01.LOG'  SIZE 10M,
  GROUP 2 'C:\COPY1\COPY1\REDO02.LOG'  SIZE 10M,
  GROUP 3 'C:\COPY1\COPY1\REDO03.LOG'  SIZE 10M
-- STANDBY LOGFILE
DATAFILE
  'C:\COPY1\COPY1\SYSTEM01.DBF',
  'C:\COPY1\COPY1\UNDOTBS01.DBF',
  'C:\COPY1\COPY1\CWMLITE01.DBF',
  'C:\COPY1\COPY1\DRSYS01.DBF',
  'C:\COPY1\COPY1\EXAMPLE01.DBF',
  'C:\COPY1\COPY1\INDX01.DBF',
  'C:\COPY1\COPY1\ODM01.DBF',
  'C:\COPY1\COPY1\TOOLS01.DBF',
  'C:\COPY1\COPY1\USERS01.DBF',
  'C:\COPY1\COPY1\XDB01.DBF'
CHARACTER SET WE8ISO8859P1
# Recovery is required if any of the datafiles are restored backups,
# or if the last shutdown was not normal or immediate.
RECOVER DATABASE
# Database can now be opened normally.
ALTER DATABASE OPEN;
# Commands to add tempfiles to temporary tablespaces.
# Online tempfiles have complete space information.
# Other tempfiles may require adjustment.
ALTER TABLESPACE TEMP ADD TEMPFILE 'C:\COPY1\COPY1\TEMP01.DBF'
     SIZE 41943040  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
# End of tempfile additions.
#     Set #2. RESETLOGS case
# The following commands will create a new control file and use it
# to open the database.
# The contents of online logs will be lost and all backups will
# be invalidated. Use this only if online logs are damaged.
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "COPY1" RESETLOGS  NOARCHIVELOG
--  SET STANDBY TO MAXIMIZE PERFORMANCE
    MAXLOGFILES 50
    MAXLOGMEMBERS 5
    MAXDATAFILES 100
    MAXINSTANCES 1
    MAXLOGHISTORY 226
LOGFILE
  GROUP 1 'C:\COPY1\COPY1\REDO01.LOG'  SIZE 10M,
  GROUP 2 'C:\COPY1\COPY1\REDO02.LOG'  SIZE 10M,
  GROUP 3 'C:\COPY1\COPY1\REDO03.LOG'  SIZE 10M
-- STANDBY LOGFILE
DATAFILE
  'C:\COPY1\COPY1\SYSTEM01.DBF',
  'C:\COPY1\COPY1\UNDOTBS01.DBF',
  'C:\COPY1\COPY1\CWMLITE01.DBF',
  'C:\COPY1\COPY1\DRSYS01.DBF',
  'C:\COPY1\COPY1\EXAMPLE01.DBF',
  'C:\COPY1\COPY1\INDX01.DBF',
  'C:\COPY1\COPY1\ODM01.DBF',
  'C:\COPY1\COPY1\TOOLS01.DBF',
  'C:\COPY1\COPY1\USERS01.DBF',
  'C:\COPY1\COPY1\XDB01.DBF'
CHARACTER SET WE8ISO8859P1
# Recovery is required if any of the datafiles are restored backups,
# or if the last shutdown was not normal or immediate.
RECOVER DATABASE USING BACKUP CONTROLFILE
# Database can now be opened zeroing the online logs.
ALTER DATABASE OPEN RESETLOGS;
# Commands to add tempfiles to temporary tablespaces.
# Online tempfiles have complete space information.
# Other tempfiles may require adjustment.
ALTER TABLESPACE TEMP ADD TEMPFILE 'C:\COPY1\COPY1\TEMP01.DBF'
     SIZE 41943040  REUSE AUTOEXTEND ON NEXT 655360  MAXSIZE 32767M;
# End of tempfile additions.
#As you can see, you have there different ways to recreate the controlfile. In Our case, We are going to recreate the controlfiles so:
STARTUP NOMOUNT
CREATE CONTROLFILE SET DATABASE "COPY2" RESETLOGS NOARCHIVELOG
-- SET STANDBY TO MAXIMIZE PERFORMANCE
MAXLOGFILES 50
MAXLOGMEMBERS 5
MAXDATAFILES 100
MAXINSTANCES 1
MAXLOGHISTORY 226
LOGFILE
GROUP 1 'C:\COPY2\COPY2\REDO01.LOG' SIZE 10M,
GROUP 2 'C:\COPY2\COPY2\REDO02.LOG' SIZE 10M,
GROUP 3 'C:\COPY2\COPY2\REDO03.LOG' SIZE 10M
-- STANDBY LOGFILE
DATAFILE
'C:\COPY2\COPY2\SYSTEM01.DBF',
'C:\COPY2\COPY2\UNDOTBS01.DBF',
'C:\COPY2\COPY2\CWMLITE01.DBF',
'C:\COPY2\COPY2\DRSYS01.DBF',
'C:\COPY2\COPY2\EXAMPLE01.DBF',
'C:\COPY2\COPY2\INDX01.DBF',
'C:\COPY2\COPY2\ODM01.DBF',
'C:\COPY2\COPY2\TOOLS01.DBF',
'C:\COPY2\COPY2\USERS01.DBF',
'C:\COPY2\COPY2\XDB01.DBF'
CHARACTER SET WE8ISO8859P1
Note: two important issues to denote in the sentence above is the word "SET" instead of "REUSE" and the controlfiles must be recreated in RESETLOG mode because the database must be opened in RESETLOG mode.
If you use the word "REUSE" instead of "SET" the opening of the database is going to request recovery of the datafile of the tablespace system.
So, apply this to recreate the controlfiles:
- Start the service in windows for the database COPY2
- Get connection through SQL*Plus as system
- Shut down the database with shutdown abort
- Start the database up in nomount stage
- apply the sentence to recreate the controlfile.
C:\>SET ORACLE_SID=COPY2
C:\>sqlplus /nolog
SQL*Plus: Release 9.2.0.1.0 - Production on Thu May 20 16:46:49 2004
Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
SQL> conn sys as sysdba
Enter password:
Connected.
SQL>
SQL> shutdown abort
ORACLE instance shut down.
SQL>
SQL>
SQL> startup nomount
ORACLE instance started.
Total System Global Area  135338868 bytes
Fixed Size                   453492 bytes
Variable Size             109051904 bytes
Database Buffers           25165824 bytes
Redo Buffers                 667648 bytes
SQL>
SQL>
SQL> CREATE CONTROLFILE SET DATABASE "COPY2" RESETLOGS  NOARCHIVELOG
  2  --  SET STANDBY TO MAXIMIZE PERFORMANCE
  3      MAXLOGFILES 50
  4      MAXLOGMEMBERS 5
  5      MAXDATAFILES 100
  6      MAXINSTANCES 1
  7      MAXLOGHISTORY 226
  8  LOGFILE
  9    GROUP 1 'F:\COPY2\COPY2\REDO01.LOG'  SIZE 10M,
10    GROUP 2 'F:\COPY2\COPY2\REDO02.LOG'  SIZE 10M,
11    GROUP 3 'F:\COPY2\COPY2\REDO03.LOG'  SIZE 10M
12  -- STANDBY LOGFILE
13  DATAFILE
14    'F:\COPY2\COPY2\SYSTEM01.DBF',
15    'F:\COPY2\COPY2\UNDOTBS01.DBF',
16    'F:\COPY2\COPY2\CWMLITE01.DBF',
17    'F:\COPY2\COPY2\DRSYS01.DBF',
18    'F:\COPY2\COPY2\EXAMPLE01.DBF',
19    'F:\COPY2\COPY2\INDX01.DBF',
20    'F:\COPY2\COPY2\ODM01.DBF',
21    'F:\COPY2\COPY2\TOOLS01.DBF',
22    'F:\COPY2\COPY2\USERS01.DBF',
23    'F:\COPY2\COPY2\XDB01.DBF'
24  CHARACTER SET WE8ISO8859P1
25  ;
Control file created.
SQL>Joel Pérez
http://otn.oracle.com/experts