Oracle uses RMAN to directly Restore the database from 10g to 11g.

With the upgrade of the Oracle version, RMAN is also enhanced. RMAN in Oracle11g supports the use of different operating systems and different databases. For the compatibility of RMAN, refer:

Oracle RMAN compatibility and FAQs between different versions and different platforms

This article demonstrates an example of restoring 10 Gb to 11 GB in linux.

Target end:

OS: Oracle Linux 6.1 64-bit

DB: 11.2.0.3

 

Source end:

OS: Oracle Linux 6.1 64-bit

DB: 10.2.0.5

Note:

Oracle 10.2.0.1 cannot be upgraded directly to 11gR2. At least upgrade to 10.2.0.2 is required before upgrade to 11gR2. For Oracle Upgrade roadmap, refer to my Blog: oracle9i/10g/11g Database upgrade roadmap)

Simply put, there are two steps:

1. Restore the 10 Gb database to 11 GB

2. Upgrade the restored 10 Gb database to 11 GB.

 

The procedure is as follows.

 

I. Use RMAN to back up the database in the Source database

1.1 run the utlu112i. SQL script on the Source database

Run the utlu112i. SQL script before the Source backup. If the script is not executed, run @? The following error is reported during/rdbms/admin/catupgrd. SQL script:

 

DOC> The following error is generated if the pre-upgrade tool has not been

DOC> run in the old ORACLE_HOME home prior to upgrading a pre-11.2 database:

DOC>

DOC> SELECT TO_NUMBER ('ust _ HAVE_RUN_PRE-UPGRADE_TOOL_FOR_TIMEZONE ')

DOC> *

DOC> ERROR at line 1:

DOC> ORA-01722: invalid number

DOC>

DOC> o Action:

DOC> Shutdown database ("alter systemcheckpoint" and then "shutdown abort ").

DOC> Revert to the original oracle home andstart the database.

DOC> Run pre-upgrade tool against thedatabase.

DOC> Review and take appropriate actionsbased on the pre-upgrade

DOC> output before opening the datatabase inthe new software version.

DOC>

Set utlu112i under 11 GB $ ORACLE_HOME/rdbms/admin. copy the SQL script to $ ORACLE_HOME/rdbms/admin of 10 GB and execute it on 10 Gb. This script can check the information before the upgrade. If the conditions are not met, the list is displayed.

SQL> spool upgrade_info.log

SQL>@? /Rdbms/admin/utluw. I. SQL

Oracle Database 11.2 Pre-UpgradeInformation Tool 19:53:57

Script Version: 11.2.0.3.0 Build: 001

.

**************************************** ******************************

Database:

**************************************** ******************************

--> Name: ANQING

--> Version: 10.2.0.5.0

--> Compatible: 10.2.0.5.0

--> Blocksize: 8192

--> Platform: 64-bit for Linux x86

--> Timezone file: V4

.

**************************************** ******************************

Tablespaces: [make adjustments in thecurrent environment]

**************************************** ******************************

--> SYSTEM tablespace is adequate forthe upgrade.

... Minimum required size: 682 MB

--> UNDOTBS1 tablespace is adequate forthe upgrade.

... Minimum required size: 400 MB

--> SYSAUX tablespace is adequate forthe upgrade.

... Minimum required size: 454 MB

--> TEMP tablespace is adequate for theupgrade.

... Minimum required size: 60 MB

.

**************************************** ******************************

Flashback: OFF

**************************************** ******************************

**************************************** ******************************

Update Parameters: [Update Oracle Database11.2 init. ora or spfile]

Note: Pre-upgrade tool was run on a lowerversion 64-bit database.

**************************************** ******************************

--> If Target Oracle is 32-Bit, referhere for Update Parameters:

-- No update parameter changes are required.

.

 

--> If Target Oracle is 64-Bit, referhere for Update Parameters:

WARNING: --> "sga_target" needs to be increased to at least 596 MB

.

**************************************** ******************************

Renamed Parameters: [Update Oracle Database11.2 init. ora or spfile]

**************************************** ******************************

-- No renamed parameters found. No changesare required.

.

**************************************** ******************************

Obsolete/Deprecated Parameters: [UpdateOracle Database 11.2 init. ora or spfile]

**************************************** ******************************

--> Background_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest"

--> User_dump_dest 11.1 DEPRECATED replaced by "diagnostic_dest"

.

 

**************************************** ******************************

Components: [The following databasecomponents will be upgraded or installed]

**************************************** ******************************

--> Oracle Catalog Views [upgrade] VALID

--> Oracle Packages and Types [upgrade] VALID

--> JServer JAVA Virtual Machine [upgrade] VALID

--> Oracle XDK for Java [upgrade] VALID

--> Oracle Workspace Manager [upgrade] VALID

--> OLAP Analytic Workspace [upgrade] VALID

--> OLAP Catalog [upgrade] VALID

--> EM Repository [upgrade] VALID

--> Oracle Text [upgrade] VALID

--> Oracle XML Database [upgrade] VALID

--> Oracle Java Packages [upgrade] VALID

--> Oracle interMedia [upgrade] VALID

--> Spatial [upgrade] VALID

--> Data Mining [upgrade] VALID

--> Expression Filter [upgrade] VALID

--> Rule Manager [upgrade] VALID

--> Oracle olap api [upgrade] VALID

.

**************************************** ******************************

Miscellaneous Warnings

**************************************** ******************************

WARNING: --> Database is using atimezone file older than version 14.

... After the release migration, it isrecommended that DBMS_DST package

... Be used to upgrade the 10.2.0.5.0database timezone version

... To the latest version which comes withthe new release.

WARNING: --> EM Database ControlRepository exists in the database.

... Direct downgrade of EM DatabaseControl is not supported. Refer to

... Upgrade Guide for instructions to savethe EM data prior to upgrade.

WARNING: --> Your recycle bin is turnedon and currently contains no objects.

... Because it is REQUIRED that therecycle bin be empty prior to upgrading

... And your recycle bin is turned on, youmay need to execute the command:

PURGE DBA_RECYCLEBIN

... Prior to executing your upgrade toconfirm the recycle bin is empty.

.

**************************************** ******************************

Recommendations

**************************************** ******************************

Oracle recommends gathering dictionarystatistics prior

Upgrading the database.

To gather dictionary statistics execute thefollowing command

While connected as SYSDBA:

 

EXECUTE dbms_stats.gather_dictionary_stats;

 

**************************************** ******************************

Oracle recommends reviewing any definedevents prior to upgrading.

 

To view existing non-default events executethe following commands

While connected as sysdba:

Events:

SELECT (translate (value, chr (13) | chr (10), '') FROM sys. v $ parameter2

Where upper (name) = 'event' AND isdefault = 'false'

 

Trace Events:

SELECT (translate (value, chr (13) | chr (10), '') from sys. v $ parameter2

Where upper (name) = '_ TRACE_EVENTS' AND isdefault = 'false'

 

Changes will need to be made in theinit. ora or spfile.

 

**************************************** ******************************

SQL>

 

If you execute this script on 11 GB, the following error will be reported:

SQL> @? /Rdbms/admin/utluw. I. SQL

ERROR:

ORA-04023: Object SYS. STANDARD cocould not bevalidated or authorized

 

MOS:

ORA-04023 On SYS. STANDARD When RunningUTLU111I. SQL or UTLU112I. SQL [ID 984511.1]

 

I found this article on the Internet:

WARNING:-> Database is using an oldtimezone file version.
.... Patch the 10.2.0.1.0 database to timezone file version 4
.... BEFORE upgrading the database. Re-run utlu111i. SQL after
.... Patching the database to record the new timezone file version.

 

To find time zone file version on sourcedatabase (10g) run
SQL> select * from v $ timezone_file;
If time zone file version is lessthan 4 then apply time zone patch 5632264 manually for 10.2.0.1database.

-- We mentioned earlier that 10.2.0.1 cannot be upgraded directly to 11gR2. The reason for this failure may be due to Time zone. The Time zone value of 10.2.0.5 is 4, which meets the conditions. If the timezone value is less than 4, Patch 5632264 is required.

There is no database for 10.2.0.1 on hand, and it cannot be queried for the moment. We have encountered a time zone issue before.

Oracle TTSORA-39322: Cannot use transportable tablespace with different timezone version description

1.2 back up the Source database

Backup Script Reference:

Linux platform RMAN full backup and Incremental Backup shell script

Shell script for incremental RMAN backup under Nocatalog

1 2 3 4 Next Page