Migrate Oracle10.2.0.564-bit RMAN to 11.2.0.3x64

Migrate Oracle10.2.0.564-bit RMAN to 11.2.0.3x64

Oracle 10.2.0.5 64-bit RMAN migration to 11.2.0.3x64

This article uses the migration method to migrate and upgrade the database from 10 Gb to 11 GB.

Recommended reading:

Clone an Oracle EBS Database

User-managed database clone

RMAN-based database cloning on the same machine

RMAN duplicate Database

I. Environment Introduction
1. source database environment
Operating system version: OEL5.8 x64
Database Version: 10.2.0.5 x64
Database sid Name: orcl
The installation directory of Oracle 10g 10.2.0.5 (64bit) is as follows:
Database software:/u01/app/oracle/product/10.2.0/db_1
Database File:/u01/app/oracle/oradata/orcl
Archive Directory:/u01/archivelog
RMAN Directory:/u01/rman_bak/data

2. target database environment
Operating system version: OEL5.8 x64
Database Version: 11.2.0.3 x64
Database sid Name: orcl
The installation directory of Oracle 11g 11.2.0.3 (64bit) is as follows (no database is created)
Database software:/u01/app/oracle/product/11.2.0/db_1
Database File:/u01/app/oracle/oradata/orcl
Archive Directory:/u01/archivelog
RMAN Directory:/u01/rman_bak/data
Oracle 11g 11.2.0.3 (64bit) Installation File
P10404530_112030_Linux-x86-64_1of7.zip
P10404530_112030_Linux-x86-64_2of7.zip

3. Upgrade ideas
1) Oracle 10.2.0.2 can be upgraded to 11g 11.2.0.3.
2) create a database directory for Oracle 11.2.0.3.
3) execute the utlu112i. SQL script of the Oracle 11.2.0.3x64 database on the Oracle 10.2.0.5x64 database.
4) back up the Oracle 10.2.0.5x64 database and upload it to the 11g database server.
5) restore the 10 Gb database to the 11 GB database and upgrade it.

Ii. RMAN backup source 10 Gb Database
1. Execute the utlu112i. SQL script on the Oracle 10g Database

First, you need to upload the utlu112i. SQL script under 11g $ ORACLE_HOME/rdbms/admin to the $ ORACLE_HOME/rdbms/admin directory of 10g and execute it.
Run the script on 10 Gb. The script can check the information before the upgrade and must be executed. Otherwise, an error will occur during recovery.
SQL> @? /Rdbms/admin/utluw. I. SQL
# No errors during execution

2. Back up the source database
Note: It records database DBID (DBID = 1349744318) and is useful for restoration.
[Oracle @ oradb ~] $ Rman target/
Recovery Manager: Release 10.2.0.5.0-Production on Sunday July 28 12:34:56 2013
Copyright (c) 1982,200 7, Oracle. All rights reserved.
Connected to target database: ORCL (DBID = 1349744318)
RMAN>
Run {
Allocate channel c1 device type disk;
Backup incremental level 0
Format '/u01/rman_bak/data/db_full _ % U. bak'
Tag '2017-07-28-full'
Database plus archivelog;
Release channel c1;
}
# Backup control files and parameter files
RMAN> backup current controlfile format '/u01/rman_bak/data/control20130728.bak ';
RMAN> backup spfile format '/u01/rman_bak/data/spfile20130728.bak ';

4. Copy the/u01/rman_bak/data directory to the 11g database server.

Iii. 11 GB database recovery preparation
1. Create a basic directory for the 11g Database
# Su-oracle
Mkdir-p/u01/app/oracle/admin/orcl/{adump, dpdump, pfile, scripts}
Mkdir-p/u01/app/oracle/oradata/orcl
Mkdir-p/u01/app/oracle/flash_recovery_area/ORCL

2. Create a log file
Mkdir-p/u01/archivelog

3. Restore the rman backup database to the/u01/rman_bak/data directory.
# Su-oracle
$ Cd/u01
[Root @ rman data] # ll
-Rw-r -- 1 root 7110656 07-24 22:23 control20130728.bak
-Rw-r -- 1 root 38029824 07-24 db_full_01ofj0gt_00001.bak
-Rw-r -- 1 root 545660928 07-24 db_full_02ofj0h1_4241.bak
-Rw-r -- 1 root 7168 07-24 db_full_03ofj0hs_1_1.bak
-Rw-r -- 1 root 98304 07-24 22:23 spfile20130728.bak

For more details, see the next page: