Advanced Application of Duplicate copy RMAN database (3) replication process
Advanced Application of Duplicate copy RMAN database (1) Overview
Advanced Application of Duplicate copy RMAN database (2) auxiliary instance
Different configurations determine different replication process.
A remote site, a copy of the same path structure (Duplicating a Database on a Remote Host with the Same Directory Structure)
For this option, the operation is too simple, you do not even modify the initialization parameter file, or rename the copied data files (unfortunately, do the test so that it can not serve as our first choice, the general tests have only a machine, can let me a virtual one operating system?) If more than one machine, then this operation is very save trouble, the steps is also low:
1, create a secondary instance.
2, Rman connect and run the duplicate command, the end.
Was really very simple, right, well then I come for you to find trouble spots, pay attention to step 2, its implementation is there are several pre-conditions. The great oracle or an adult again decentralized its noble powers, and give you to make a choice, as follows:
l If there is no configured automatically assigned channels, then manually specify the table forget that at least one auxiliary channel.
l Table forget NOFILENAMECHECK parameters specified.
l As said earlier, if the auxiliary instance does not start the server-side initialization parameter file, specify the PFILE parameter table forgotten. More Table forget the file must be running the RMAN client side.
For example, suppose you have configured the automatic distribution channel and decided to start the auxiliary instance using the pfile, then RMAN to connect to the target database and auxiliary instance, there is only need to do the following:
DUPLICATE TARGET DATABASE TO dupdb
PFILE = F: oracleproduct10.2.0adminjssduppfileinit.ora
NOFILENAMECHECK;
Finally, RMAN will automatically open the database in RESETLOGS and rebuild REDO LOGS. Completed.
Second, the remote site to copy the structure of the different paths (Duplicating a Database on a Remote Host with a Different Directory Structure)
If the copy of the database created in the remote site, and the directory structure is inconsistent, then you have to modify several initialization parameters in order to copy the database data files can be access in the new directory structure. This type of reproduction also may be divided into several Class:
1, in the initialization parameters to rename copy files and log files, copy the following steps:
a) First of all, or create the auxiliary instance. Note that the configuration of initialization parameters, according to some adjustments in the following way.
l browse initialization parameter to the end of the parameters and _DEST include path parameters, confirm the path to be effective to create a copy of the database.
l Set DB_FILE_NAME_CONVERT parameters, allowed to automatically convert the data file path.
l Set LOG_FILE_NAME_CONVERT parameters, allowed to automatically convert the log file path.
The so-called Road in 1000, I have to choose one, in addition to the above-mentioned methods it addition, there are many other ways to specify the file storage path, such as CONFIGURE AUXNAME or SET NEWNAME commands and so on. But here is the writing initialization parameters to rename the type of replication, not too much of the chapter, and chapters devoted to the back. Interested friends may wish to keep your curiosity, look down:)
b) RMAN to connect and execute duplicate command, the end.
Here also requires attention to the secondary channel of distribution and pfile load (if you are using pfile it).
For example, we use automatic distribution channel, and the auxiliary instance using a server-side initialization parameter file, which, under the command dulicate more simple: the
DUPLICATE TARGET DATABASE TO dupdb;
The main work in this way create a secondary instance.
2, in the Duplicate command to rename the data, log files, copy the following steps:
a. Create auxiliary instance.
b. RMAN to connect to run Duplicate command, pay attention to here need to add some parameters are as follows:
l-channel, or channel! If there is no automatic distribution channel, then manually specify at least one auxiliary channel.
l through the LOGFILE clause specifies the address for a copy of the database redo logs size.
l through the DB_FILE_NAME_CONVERT converting the original data file path to the new path.
l pfile, see pfile. If you are using a pfile, then specify the pfile parameter table forgotten.
For example, we use automatic allocation of channels, but the auxiliary instance does not use a server-side initialization parameter file, manually specify the log file data file path, the sample is as follows:
DUPLICATE TARGET DATABASE TO dupdb
PFILE = F: oracleproduct10.2.0adminjssduppfileinit.ora
DB_FILE_NAME_CONVERT = (F: oracleoradatajssweb, F: oracleoradatajssdup)
LOGFILE
'F: oracleoradatajssdupredo01.log' SIZE 20M,
'F: oracleoradatajssdupredo02.log' SIZE 20M,
'F: oracleoradatajssdupredo03.log' SIZE 20M;
3, use the SET NEWNAME command to rename the data file, copy the following steps:
a. Create auxiliary instance.
b. RMAN to connect and then follow these steps:
l Configure channel;
l Use SET NEWNAME command to set the new path data file;
l Duplicate command to set logfile, such as the auxiliary instance pfile to load using pfile.
This section focuses on SET NEWNAME command format, see example:
RUN
(
# Set new filenames for the datafiles
SET NEWNAME FOR DATAFILE 1 TO 'F: oracleoradatajssdupsystem01.dbf';
SET NEWNAME FOR DATAFILE 2 TO 'F: oracleoradatajssdupundotbs01.dbf';
...
# Issue the duplicate command
DUPLICATE TARGET DATABASE TO dupdb
# Create at least two online redo log groups
...
)
4, use the CONFIGURE AUXNAME command to rename the data file, copy the following steps:
Slightly with the same, not detailed, the only difference at that is CONFIGURE AUXNAME command format, such as cases, and the configure command is executed outside the block in the run:
# Configure the new desired filenames
CONFIGURE AUXNAME FOR DATAFILE 1 TO 'F: oracleoradatajssdupsystem01.dbf';
CONFIGURE AUXNAME FOR DATAFILE 2 TO 'F: oracleoradatajssdupundotbs01.dbf';
# ... Add more CONFIGURE AUXNAME commands as needed
But should be noted that, duplicate after completing the implementation of recommended removal CONFIGURE AUXNAME. This would not have been the future of a similar impact on operations.
# Clear specified auxiliary names for the datafiles
CONFIGURE AUXNAME FOR DATAFILE 1 CLEAR;
CONFIGURE AUXNAME FOR DATAFILE 2 CLEAR;
3, the local creation (Creating a Duplicate Database on the Local Host)
And a second "remote site to copy the structure of the different paths" has more than 95% similarity. The only difference is that the local would need to pay attention created by the target database is not the same DB_NAME. This is mainly reflected in the auxiliary instance in the configuration of initialization parameters, the other steps described in the second copy can be completely different methods, so it is not detailed:)
In addition, another such copy to the ASM storage systems, or to OMF storage replication, etc., copy the process and basically similar, but the initialization parameter file is set different parameters, or parameter into different Value Bale.
Name Xie nonsense from the above analysis we can, although the oracle so many sub-types of operations, but the original aim 2 is at its core, the first one is to ensure that auxiliary instance initialization parameter file, the file path the validity of the first two, when the implementation of duplicate instances of attention and support with the initialization parameter settings. Above eloquent Tootoo saliva which are under various circumstances to you, for example, duplicate command and how to effectively cope with initialization parameter settings. How, you noticed this? He He is not too late, let's begin at once to enter combat in:)
Related Posts of Advanced Application of Duplicate copy RMAN database (3) replication process
-
SGA extended the principle of 32bit oracle
SGA extended the principle of 32bit oracle From: http://www.itpub.net/247048.html Because the median 32bitrnoracle restrictions can only visit the oracle process 4g (2 of 32 power) following virtual memory address, the time at a lot of people this is ...
-
Using SQL TRACE and TKPROF
Can type in the operating system to obtain tkprof all available options and output options to sort a list of note has Sort Option Description call analysis prscnt execnt fchcnt the implementation of the number of extraction Analysis of the implementa ...
-
High Availability Oracle Flashback
Brief introduction Flashback Database is a point in time (PIT) restore the database approach. This incomplete recovery strategy can be used to restore the logic because of human error cause damage to the database. At the introduction of 10g, it is de ...
-
An example of the use of TKPROF
First, view and edit parameters SQL> show parameter max_dump_file_size NAME TYPE VALUE ------------------------------------ ----------- --- --------------------------- max_dump_file_size string UNLIMITED SQL> show parameter user_dump_dest NAME TYPE
-
Diagnosis and principles of order
SQL> select disk.value "Disk", mem.value "Mem", 2 (disk.value / mem.value) * 100 "Ratio" 3 from v $ sysstat mem, v $ sysstat disk 4 where mem.name = 'sorts (memory)' 5 and disk.name = 'sorts (disk)'; D ...
-
ORACLE 10G dataguard configuration Step by Step
oracle dataguard













Leave a Reply