第一. Creating a Physical Standby Database
1.1 实验背景
- You have two servers (physical or VMs) with an operating system and Oracle installed on them. In this case I’ve used Oracle Linux 5.6 and Oracle Database 11.2.0.2.
- The primary server has a running instance.
- The standby server has a software only installation.
数据库 | IP | DB_SID | DB_NAME | DB_UNIQUE_NAME | Oracle Net Service Name |
---|---|---|---|---|---|
Primary | 0.0.0.188 | mmpdb3 | mmpdb3 | mmpdb3 | mmpdb3 |
Physical standby | 0.0.0.189 | mmpdb3 | mmpdb3 | mmpdb3sby | mmpdb3sby |
1.2 Primary Server Setup
1.2.1 Logging
|
|
1.2.2 Initialization Parameters
|
|
1.2.3 Service Setup
|
|
1.2.4 Create Standby Controlfile and PFILE
|
|
1.2.5 Create Standby Controlfile and PFILE
|
|
1.3 Standby Server Setup (DUPLICATE)
1.3.1 Copy Files
|
|
1.3.2 Start Listener
|
|
1.3.3 Create Standby Using DUPLICATE
|
|
FOR STANDBY
: This tells the DUPLICATE command is to be used for a standby, so it will not force a DBID change.FROM ACTIVE DATABASE
: The DUPLICATE will be created directly from the source datafile, without an additional backup step.DORECOVER
: The DUPLICATE will include the recovery step, bringing the standby up to the current point in time.SPFILE
: Allows us to reset values in the spfile when it is copied from the source server.NOFILENAMECHECK
: Destination file locations are not checked.
1.4 Start Apply Process
|
|
1.5 Test Log Transport
|
|
1.6 Test data standby database read only
|
|