To show one of the reasons why we can get a row from this query, see the following example. Here, we create a table on a different tablespace and create a relationship between the two tables using the ID column. In order to be successful, we need to resolve the problem and get a no result? Look at the error you get if you perform an incomplete recovery:.
About to export Tablespace Point-in-time Recovery objects The second check is to look at the objects that will be lost after the incomplete recovery. All objects that were created after deletion of those tables, that is, after the time to which we want to perform tablespace recovery, will be lost. Now, it is time to perform the recovery. For example, if you specify all the commands and the initialization parameter, RMAN uses set newname.
If you do not specify any of the first three options, then RMAN uses the original target filenames for the duplicate file. When you specify skip readonly , RMAN does not duplicate the datafiles of these tablespaces. You see the following values in the specified views or tables:. After duplication, you can manually add or drop these tablespaces.
As with online tablespaces, RMAN requires a valid backup for duplication. In this case, specify nofilenamecheck to avoid an error. When duplicating to host B, you issue:. Even though you issued set newname commands for all your datafiles, the duplicate command fails because the duplicate filenames are still in use in the target database.
Create an initialization parameter file for the auxiliary instance and set the following required parameters:. Optionally, set the following parameters:. When duplicating to the same host or to a new host with a different file system, pay special attention to all parameters specifying path names. Following are examples of the initialization parameter settings for the duplicate database:.
Do not create a control file or try to mount or open the auxiliary instance. The auxiliary instance must be accessible via Net8. Before beginning RMAN duplication, mount or open the target database--specifying a parameter file if necessary--if it is not already mounted or open. For example, enter:. To connect to the auxiliary instance, target instance, and recovery catalog, supply the following information when starting up Recovery Manager:.
You can start the RMAN command line interface without a connection to the auxiliary instance, and then use the connect auxiliary command at the RMAN prompt to make the auxiliary connection:.
Make sure you have backups all the datafiles in your target database. If you do not have backups of everything, the duplicate operation fails. The database backup does not have to be a whole database backup: you can use a mix of full and incremental backups of individual datafiles. The archived redo logs are accessible on the node where the duplicate command is operating.
Allocate Auxiliary Channels Before issuing the duplicate command, allocate at least one auxiliary channel within the same run command. If the backups reside on disk, then the more channels you allocate, the faster the duplication will be.
For tape backups, limit the number of channels to the number of devices available for the operation. Generating Files for the Duplicate Database When duplicating a database, perform the following operations:.
When choosing names for the duplicate database control files, make sure that you do not overwrite the init. You have these options for creating the names of the duplicate online redo logs, which are listed in the order of precedence:. Creates redo logs as specified.
Transforms target filenames, e. Note: This parameter allows the redo log to exist as long as the size matches, since it uses the reuse parameter when creating the logs.
Reuses the target filenames. You must specify the nofilenamecheck option when using this method. The order of precedence determines how RMAN renames the online redo logs.
If you specify all options, then RMAN uses the logfile clause and ignores the others. WARNING: If the target and duplicate databases are in the same host, do not use the name of an online redo log currently in use by the target database. Also, do not use the name of a redo log currently in use by the target database if the duplicate database is in a different host and the nofilenamecheck keyword is not used.
Renaming the Datafiles If you want to have different filenames in your duplicate datafile, then you must use parameters or commands to specify them. You have these options for renaming datafiles, listed in the order of precedence:. Creates new datafile filenames. This command must be re-issued each time you want to rename files. This setting stays in effect until disabled with a set auxname You can use this parameter for those files not renamed with either set newname and set auxname.
Re-uses the target filenames. The order of precedence determines how RMAN will name the datafiles. For example, if you specify all the commands and the initialization parameter, RMAN uses set newname. If you do not specify any of the first three options, then RMAN uses the original target filenames for the duplicate file. When you specify skip readonly , RMAN does not duplicate the datafiles of these tablespaces.
You will see the following values in the specified views or tables:. After duplication, you can manually add or drop these tablespaces. As with online tablespaces, RMAN requires a valid backup for duplication. For backup-based duplication, you can either create a password file or use operating system authentication to connect to the auxiliary instance. For active database duplication, you must use password file authentication. To connect to a database by using password file authentication, you must create a password file for the database.
0コメント