Inventory_loc=/ ~ ]$ cat / ~ ]$ lsnrctl status Red Hat Enterprise Linux Server release 5.10 ~ ]$ uname –p –r Pre-requisite checks ~ ]$ cat /etc/redhat-release So if anything goes wrong while upgradation we can use “SID_restore. Here, I say the safest way because, it takes the backup before starting the upgradation and creates 3 scripts at your backup location 1) startup_SID.sql 2) shutdown_SID.sql and 3) SID_restore. And DBUA is the simplest and safest way to upgrade. As per the Oracle, We can upgrade Oracle 11.1.0.6.0 onwards versions of Oracle 11.2.0.3.0 directly. Out-of-Place Upgrade- Install binaries in new ORACLE_HOME In-place Upgrade – Install binaries in same ORACLE_HOME. There are two methods to upgrade database server: Upgrading Oracle 11.1.0.6.0 to Oracle 11.2.0.3.0 Using DBUA (Database Upgrade Assistant):.Upgrading Oracle 11.1.0.6.0 to Oracle 11.2.0.3.0 Using DBUA (Database Upgrade Assistant).This document, separating into two parts: We installed Linux-el6.5 and Oracle 11.2.0.3.0 on Ironman and tried to clone the database but Oracle 11.2.0.3.0 RMAN is not compatible with RMAN 11.1.0.6.0, So we have upgraded old (Punisher) to Oracle 11.2.0.3.0 first and then clone the database on the new Ironman server. But we used the RMAN utility to clone the database on the new (Ironman) server.
We could use data pump utilities to restore the dumps. The old server (Punisher) was running on a single instance ( iolnxeng) database with 367 schemes, tablespaces, users, etc. The actual scenario is : we have one Dev Oracle database server (Punisher) running on Linux-el5.10 and Oracle 11.1.0.6.0 But due to some hardware failure, we have shifted this server on brand new DELL PowerEdge R720 (Ironman). This blog is tested on DEV Oracle database servers ( and ).
0 kommentar(er)
