Sybase Database in a SAN Environment Using EVA Snapclone Technology (August 2007)

This command generates a trace file to be written to the destination where the

production DB1 initialization parameter

USER_DUMP_DEST

is pointing to. In this

case, the trace file is in

$ORACLE_HOME/DB1/admin/udump directory.

However, this trace file is unorganized and needs to be reshaped. The reshaped trace

file is provided in the form of an SQL script controlClone.sql, as shown below:

connect / as sysdba

STARTUP NOMOUNT

pfile=/prod/oracle9/clonebase/TEST/admin/pfile/initTEST.ora

CREATE CONTROLFILE SET DATABASE "TEST" RESETLOGS NOARCHIVELOG

-- SET STANDBY TO MAXIMIZE PERFORMANCE

MAXLOGFILES 5

MAXLOGMEMBERS 3

MAXDATAFILES 100

MAXINSTANCES 1

MAXLOGHISTORY 907

LOGFILE

GROUP 1 (

'/prod/TEST/log1/redo01.log'

) SIZE 100M,

GROUP 2 (

'/prod/TEST/log2/redo02.log'

) SIZE 100M

-- STANDBY LOGFILE

DATAFILE

'/prod/TEST/sys/system01.dbf',

'/prod/TEST/sys/undotbs01.dbf',

'/prod/TEST/sys/undotbs02.dbf',

'/prod/TEST/sys/undotabs03.dbf',

'/prod/TEST/sys/indx01.dbf',

'/prod/TEST/sys/tools01.dbf',

'/prod/TEST/users/users01.dbf',

CHARACTER SET WE8ISO8859P1;

Execute controlClone.sql in the clone’s instance by entering the following command:

SQL> @controlClone.sql

Connected to an idle instance.

ORACLE instance started.