Shulou(Shulou.com)06/01 Report--

Summary

1. The pfile option describes a file at the end of the execution of the rman command used

If rman is enabled on the source side, the pfile is placed on the source side, and if ramn is enabled on the destination side, the pfile is placed on the destination side.

2. Logfile means that the file on the target side is generated in the duplicate command, regardless of which side the rman command is executed

The generated file of logfile is on the target side, and size must be specified when logfile option

3. In general operation, do not add nofilenamecheck unless you know that the datafile and online redo log files on the source and destination are not in the same shared directory.

4. If the * _ file_name_convert parameter is specified in pfile or spifle, but the db_file_name_convert or logfile selection is re-specified in the duplicate command, the setting of the * _ file_name_convert parameter specified in pfile or spifle will be overridden, as shown in experiments 5 and 6 in logfile, * _ file_name_convert, and nofilenamecheck options below.

Pfile option

prerequisite

The source end and destination end are on different machines, do not share / u01/app/oracle/oradata/prod1 paths, and each has its own / u01/app/oracle/oradata/prod1 directory.

The logfile on the source side is located in the path / u01/app/oracle/oradata/prod1, and the pfile or spfile on the destination side does not specify any db_file_name_convert and log_file_name_convert parameters

Source side file / home/oracle/initprod1std.ora (SGA=800M,process=200)

Destination pfile file / home/oracle/initprod1std.ora (SGA=700M,process=190)

Destination pfile file $ORACLE_HOME/dbs/initprod1std.ora (SGA=600M,process=180)

Destination spfile file $ORACLE_HOME/dbs/spfileprod1std.ora (SGA=600M,process=180)

1. Rman is executed on the source server. There is no / home/oracle/initprod1std.ora on the destination side, no spfile on the destination side, and $ORACLE_HOME/dbs/initprod1std.ora is used on the destination side.

Run {

Duplicate target database to prod1std from active database

Pfile=/home/oracle/initprod1std.ora

LOGFILE

'/ u02bind log01.dbf' size 1024m

'/ u02bind log02.dbf' size 1024m

'/ u02bind log03.dbf' size 1024m

NOFILENAMECHECK

}

The result of the target side

SGA=800M

Process=200

Db_data_files.file_name is the same as source side.

The v$logfile.member path is / U02

Indicates that the file / home/oracle/initprod1std.ora on the source side is used, and the logfile in the rman command is generated on the target side

2. Rman is executed on the source server. There is no / home/oracle/initprod1std.ora on the destination side, there is $ORACLE_HOME/dbs/initprod1std.ora on the target side, and the target side uses spfile to start $ORACLE_HOME/dbs/spfileprod1std.ora

Run {

Duplicate target database to prod1std from active database

Pfile=/home/oracle/initprod1std.ora

LOGFILE

'/ u02bind log01.dbf' size 1024m

'/ u02bind log02.dbf' size 1024m

'/ u02bind log03.dbf' size 1024m

NOFILENAMECHECK

}

Error RMAN-05597: Database started with server parameter file and PFILE clause used in command

3. Rman is executed on the source server. There is no / home/oracle/initprod1std.ora on the source server, no / home/oracle/initprod1std.ora on the destination side, no spfile on the destination side, and $ORACLE_HOME/dbs/initprod1std.ora on the destination side

Run {

Duplicate target database to prod1std from active database

Pfile=/home/oracle/initprod1std.ora

LOGFILE

'/ u02bind log01.dbf' size 1024m

'/ u02bind log02.dbf' size 1024m

'/ u02bind log03.dbf' size 1024m

NOFILENAMECHECK

}

RMAN-04017: startup error description: LRM-00109: could not open parameter file'/ home/oracle/initprod1std.ora'

4. Rman is executed on the source server. There is no / home/oracle/initprod1std.ora on the source server, / home/oracle/initprod1std.ora on the destination side, no spfile on the destination side, and $ORACLE_HOME/dbs/initprod1std.ora is used on the destination side.

Run {

Duplicate target database to prod1std from active database

Pfile=/home/oracle/initprod1std.ora

LOGFILE

'/ u02bind log01.dbf' size 1024m

'/ u02bind log02.dbf' size 1024m

'/ u02bind log03.dbf' size 1024m

NOFILENAMECHECK

}

RMAN-04017: startup error description: LRM-00109: could not open parameter file'/ home/oracle/initprod1std.ora'

3 and 4 indicate that the file / home/oracle/initprod1std.ora on the source side is used

Logfile, * _ file_name_convert, nofilenamecheck options

The source end and destination end are on different machines, do not share / u01/app/oracle/oradata/prod1 paths, and each has its own / u01/app/oracle/oradata/prod1 directory.

1. The logfile on the source side is located in the path / u01/app/oracle/oradata/prod1, while the one on the destination side is started with spfile. Spfile does not specify any db_file_name_convert or log_file_name_convert parameters.

Run {duplicate target database to prod1std from active database;}

Error

RMAN-05501: aborting duplication of target database

RMAN-05001: auxiliary file name / u01/app/oracle/oradata/prod1/example01.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name / u01/app/oracle/oradata/prod1/users01.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name / u01/app/oracle/oradata/prod1/undotbs01.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name / u01/app/oracle/oradata/prod1/sysaux01.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name / u01/app/oracle/oradata/prod1/system01.dbf conflicts with a file used by the target database

RMAN-05001: auxiliary file name / u01/app/oracle/oradata/prod1/redo03.log conflicts with a file used by the target database

RMAN-05001: auxiliary file name / u01/app/oracle/oradata/prod1/redo02.log conflicts with a file used by the target database

RMAN-05001: auxiliary file name / u01/app/oracle/oradata/prod1/redo01.log conflicts with a file used by the target database

2. The logfile on the source side is located in the path / u01/app/oracle/oradata/prod1, while the one on the destination side is started with spfile. Spfile does not specify any db_file_name_convert and log_file_name_convert parameters.

Run {duplicate target database to prod1std from active database nofilenamecheck;}

The result of the target side

Db_data_files.file_name is the same as source side.

V$logfile.member is the same as source side.

3. The logfile on the source side is located in the path / u01/app/oracle/oradata/prod1, while the one on the destination side is started with spfile. Spfile does not specify any db_file_name_convert and log_file_name_convert parameters.

Run {duplicate target database to prod1std from active database db_file_name_convert= ('/ u01qapexoradataActionoradatameProd1andu01andoradataloradata;)

Error

RMAN-05501: aborting duplication of target database

RMAN-05001: auxiliary file name / u01/app/oracle/oradata/prod1/redo03.log conflicts with a file used by the target database

RMAN-05001: auxiliary file name / u01/app/oracle/oradata/prod1/redo02.log conflicts with a file used by the target database

RMAN-05001: auxiliary file name / u01/app/oracle/oradata/prod1/redo01.log conflicts with a file used by the target database

4. The logfile on the source side is located in the path / u01/app/oracle/oradata/prod1, while the one on the destination side is started with spfile. Spfile does not specify any db_file_name_convert and log_file_name_convert parameters.

Run {duplicate target database to prod1std from active database

Db_file_name_convert= ('/ u01Compare oradataPlacement oradataAccordlstd')

Logfile

'/ u01Applink oracle size 50m

'/ u01Applink oracle size 50m

'/ u01Applink oracle size 50m

}

Target end result

Db_data_files.file_name is in the / u01/app/oracle/oradata/prod1std directory

V$logfile.member is under / u01/app/oracle/oradata/prod1std path

5. The dbfile,logfile on the source side is located in the path / u01/app/oracle/oradata/prod1, while that on the destination side is started with spfile and specified by spfile.

Db_file_name_convert='/u01/app/oracle/oradata/prod1/','/ u01qqappActionoradataPlacement prod1stdUniver'

Log_file_name_convert='/u01/app/oracle/oradata/prod1/','/ u01qqappActionoradataPlacement prod1stdUniver'

Run {duplicate target database to prod1std from active database

}

Target end result

Db_data_files.file_name is in the / u01/app/oracle/oradata/prod1std directory

V$logfile.member is under / u01/app/oracle/oradata/prod1std path

6. The dbfile,logfile on the source side is located in the path / u01/app/oracle/oradata/prod1, while that on the destination side is started with spfile and specified by spfile.

Db_file_name_convert='/u01/app/oracle/oradata/prod1/','/ u01qqappActionoradataPlacement prod1stdUniver'

Log_file_name_convert='/u01/app/oracle/oradata/prod1/','/ u01qqappActionoradataPlacement prod1stdUniver'

Run {duplicate target database to prod1std from active database

Db_file_name_convert= ('/ u01Accord oradataPlacement oradataplains prod1andlemagemainityu01plains oradataplicationsdata2')

Logfile

'/ u01Applink oracle size 50m

'/ u01 size size 50m

'/ u01Applink oracle size 50m

}

Target end result

Db_data_files.file_name is in the / u01/app/oracle/oradata/data2 directory

V$logfile.member is under / u01/app/oracle/oradata/data2 path

Logfile option without adding size Times error

Run {duplicate target database to prod1std from active database

Db_file_name_convert= ('/ u01Compare oradataPlacement oradataAccordlstd')

Logfile

'/ u01Accord oradataPlacement prod1stdscarp redo01.log'

'/ u01applink oraclescarp prod1stdscarp redo02.log'

'/ u01appranumoracleandoradataPlacement prod1stdscarp redo03.logcards;}

RMAN-00571: =

RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =

RMAN-00571: =

RMAN-00558: error encountered while parsing input commands

RMAN-01009: syntax error: found "comma": expecting one of: "size"

RMAN-01007: at line 1 column 208 file: standard input

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.