Академический Документы
Профессиональный Документы
Культура Документы
I could take the old approach and use RMAN backups or use 11gs new
feature DUPLICATE FROM ACTIVE database, which doesnt need any backup
from target database. I preferred to use the second approach.
Step-by-step instructions
In this guide, assume we are migrating a single instance database HRDEV to a two
node RAC database HRPRD with the following specifications:
Source database:
Database name: HRDEV
Single instance
Version: 11.2.0.3
Hostname: dev-db-01
Filesystem: ASM
Target database:
RAC 2 nodes
Version: 11.2.0.3
ORACLE_HOME: /apps/oracle/product/11.2.0/db_1
GI_HOME: /apps/grid/11.2.0/
Hostname: prd-db-01/prd-db-02
Filesystem: ASM
Diskgroup: +HR
For target database HRPRD, we assume that an empty database has already been
created with two instances, spfile and controlfiles already exist, and the database is
already a member of clusterware. As a matter of fact, we will use only instances of
this database as auxiliary instance, and all datafiles can be deleted manually before
duplication, as this database is going to be a refreshed from HRDEV database by
our DUPLICATE command.
8
shutdown immediate
9
startup nomount
10
6 (GLOBAL_DBNAME = HRPRD)
)
7
)
8
Make sure that ORACLE_HOME in this entry points to correct home, which is
the home from which HRPRD database runs.
10 HRPRD1 =
11 (DESCRIPTION =
For HRPRD, since it is a new and empty database, we may need to create a
password file for it as follows:
1 . oraenv
2 HRPRD1
3 cd $ORACLE_HOME/dbs
I have assumed that the SYS password on the source database HRDEV is sys.
Try above commands on both target and auxiliary hosts prd-db-01 and dev-db-
01. Do not continue unless your connectivity is fine.
}
6
11
srvctl start db -d HRPRD
12