As part of the duplicating operation, RMAN manages the following:. First we must create a password file for the duplicate instance. Create an INIT. ORA parameter file for the auxiliary instance, you can copy that from the target instance and then modify the parameters.
Make sure that a full backup of the target is accessible on the duplicate host. You can use the following BASH script to backup the target database. Thank you, Rajasekhar Amudala Email: br8dba gmail. If you want to duplicate to specific target directory, i have not tried before you can try like this.
Your email address will not be published. Notify me of new posts by email. Currently you have JavaScript disabled.
In order to post comments, please make sure JavaScript and Cookies are enabled, and reload the page. Click here for instructions on how to enable JavaScript in your browser. The order of precedence determines how RMAN renames the online redo logs. If you specify none of the first three options, then RMAN uses the original target redo log filenames for the duplicate database files. There are several means of specifying new names to be used for the datafiles of your duplicate database.
Listed in order of precedence, they are:. Note that you can specify multiple conversion pairs and use ASM disk groups. If you do not use any of the preceding options, then the duplicate database reuses the original datafile filenames from the target database.
RMAN re-creates datafiles for temporary tablespaces as part of the process of duplicating a database. When using tape backups, you must make the tapes containing the backups accessible to the remote node. You can achieve this goal by physically moving the tape to a drive attached to the remote host or by means of a network-accessible tape server. As part of the duplicating operation, RMAN automates the following steps:. Restores the target datafiles to the duplicate database and performs incomplete recovery by using all available incremental backups and archived redo logs.
Shuts down and starts the auxiliary instance refer to "Task 4: Start the Auxiliary Instance" for issues relating to client-side versus server-side initialization parameter files.
During duplication, RMAN must perform incomplete recovery because the online redo logs in the target are not backed up and cannot be applied to the duplicate database. The farthest that RMAN can go in recovery of the duplicate database is the most recent redo log archived by the target database.
Read-only tablespaces are included by default. If you omit them, then you can add them later. You can create the duplicate database in a new host.
By default, the DUPLICATE command creates the duplicate database from the most recent backups of the target database and then performs recovery to the most recent consistent point contained in the archived redo logs. You can register the duplicate database in the same recovery catalog as the target database. This is true whether or not the duplicate database is on the same host as the target. Duplicating a database with RMAN involves a number of prerequisites and restrictions. When duplicating a database, RMAN generates names for the required database files.
This section describes the different stages of file creation:. When choosing names for the duplicate control files, make sure you set the parameters in the initialization parameter file of the auxiliary database correctly; otherwise, you could overwrite the control files of the target database.
RMAN needs new names for the online redo log files of the duplicate database. Note that you can specify multiple conversion pairs. If an online log file already exists at the named location and is of the correct size, it is reused for the duplicate. Transforms target filenames based on the parameters set. Makes the duplicate filenames the same as the filenames from the target. Rules higher in the order of precedence override rules lower in the list.
If the target and duplicate databases are in the same host, then do not use the name of an online redo log currently in use by the target database. There are several means of specifying new names to be used for the datafiles of your duplicate database. Listed in order of precedence, they are:. If you do not use any of the preceding options, then the duplicate database reuses the original datafile locations from the target database.
When duplicating to host B, you use a configured channel to duplicate as follows:. RMAN re-creates datafiles for temporary tablespaces as part of the process of duplicating a database. There are several means of specifying locations for duplicate database tempfiles. It is not always necessary to duplicate all tablespaces of a database. For example, you may plan to generate reports at the duplicate that require only a subset of tablespaces from your target database.
It contains the following topics:. After duplication is complete, you can query the views in the duplicate database described in Table and Table to determine which datafiles were skipped. After duplication, you can manually add or drop these tablespaces.
For instructions on how to create and maintain Oracle password files, refer to Oracle Database Administrator's Guide. The auxiliary instance must be accessible through Oracle Net.
Create a client-side initialization parameter file for the auxiliary instance. The parameters listed in Table must be set to the values specified. You cannot use the same database name for the target and duplicate when the duplicate is in the same Oracle home as the target.
The block size for the auxiliary database must match that of the target database. Table Filename Conversion Initialization Parameters. When duplicating to the same host or to a new host with a different file system, pay attention to all initialization parameters specifying path names. Verify that all paths are accessible on the host where the database is being duplicated.
Example shows sample initialization parameter settings for the duplicate database. You can run this command before or after instance startup.
For example, you can create a server-side parameter file in the default location as follows, specifying the filename of the client-side initialization parameter file in the FROM clause:. Because RMAN shuts down and restarts the auxiliary instance as part of the duplication process, you must tell RMAN which client-side file to use if you use a client-side parameter file. It is highly recommended that you create a server-side parameter file for use in database duplication.
0コメント