1949451 Oracle 11.2.0 Database Upgrade to Release on Unix (Quick Reference)

October 16, 2017 | Author: Sri Agnimithra | Category: Oracle Database, Oracle Corporation, Databases, Installation (Computer Programs), Computer Architecture
Share Embed Donate

Short Description

Oracle Database Upgrade...


SAP Note


  1949451 - Oracle 11.2.0: Database Upgrade To Release on Unix (Quick Reference) Version   12     Validity: 18.09.2014 - active  


Language   English (Master)

Header Data Released On 18.09.2014 12:36:35 Release Status Released for Customer Component BC-DB-ORA Oracle Priority Recommendations / Additional Info Category Consulting

Symptom Upgrade to Oracle Database 11g Release 2 ( This SAP note is valid for Unix and Linux platforms. It can be used as a quick reference for standard database upgrades to Oracle Database Release For a detailled and complete description of the upgrade procedure, refer to the SAP document 'Database Upgrade Guide: Upgrade to Oracle Database 11g Release 2 ( Unix'. References Document


Description / Link

Database Upgrade Guide: Upgrade to Oracle Database  SAP 11g Release 2 (11.2): Unix For Oracle Patch Set Release

Document Version 4.00 2013-12-12 or later For Oracle database upgrades from release to For Oracle database upgrades from release 11.2.0.x to Download from http://service.sap.com/instguides -> Database Upgrades -> Oracle

SAP Product Availability Matrix (PAM)



SAP Note 1431797 - Oracle 11.2.0: Troubleshooting the SAP/Oracle http://service.sap.com/sap/support/notes/1431797 Database Upgrade SAP Note 1431793 - Oracle 11.2.0: Upgrade Scripts

SAP/Oracle http://service.sap.com/sap/support/notes/1431793

SAP Note 1798976 - Oracle 11.2.0: Uprade Companion SAP/Oracle http://service.sap.com/sap/support/notes/1798976  for Oracle RAC and Oracle ASM SAP Note 1949250 - Oracle 11.2.0: Patches / Patch collections for

SAP/Oracle http://service.sap.com/sap/support/notes/1949250

SAP Note 1949451 - Oracle 11.2.0: Oracle Database Upgrade To Release (Quick Reference)

SAP/Oracle http://service.sap.com/sap/support/notes/1949451 (= this SAP note)

SAP Note 1524205 - Oracle 11.2.0: Database Software SAP/Oracle http://service.sap.com/sap/support/notes/1524205 Installation SAP Note 1525025 - Oracle 11.2.0: Database Software SAP/Oracle http://service.sap.com/sap/support/notes/1525025 Deinstallation Oracle Database 11g Release 2 (11.2) Documentation Library



Oracle Database Upgrade Guide 11g Release 2 (11.2)




Other Terms Oracle Database patch set, release Oracle Database 11g Release 2 ( Database Upgrade, DBUA, Database Upgrade Assistant, 11.2.01,,,

Reason and Prerequisites This note applies to database upgrades of SAP installations with SAP NetWeaver on Oracle with Oracle Single Instance. This note applies to database upgrades on Unix/Linux platforms only. This note applies to database upgrades from Oracle database source releases, or to Oracle database target release References for other Upgrade Scenarios

Reference / Document

Upgrade Scenario This guide can be used for

Database Upgrade Guide: Upgrade to Oracle Database 11g Release 2 (11.2): Unix For Oracle Patch Set Release and Document Version 3.02 - 2012-10-30

l l

Upgrades from source release, or Upgrades to target release or release

This guide can be used for Database Upgrade Guide: Upgrade to Oracle Database 11g Release 2 (11.2): Windows


Upgrades on Windows Platform

This SAP note can be used for SAP note 1798976


Upgrades with Oracle RAC or Oracle ASM on Unix


Solution Upgrading an Oracle Database to Release This SAP note can be used as a quick reference for a standard database upgrade scenario: l l l l l

Single instance (SI) database Database source release:, or Database target release: Dedicated Oracle home  No Grid Infrastructure, no ASM, no RAC

Additional steps that are required for special upgrade scenarios will be added later: l l l

Upgrade with Database Vault Upgrade with Data Guard Upgrade with Shared Oracle home 

Special remarks: l l

OS commands that are used in this SAP note assume C shell. In this SAP note the commands 'startsap r3' and 'stopsap r3' are given as an example to start and stop the SAP instance. Alternatively you  can use 'sapcontrol ' to start or stop SAP.

 vs.  In the context of installing the new Oracle home, the location of the new Oracle home is denoted as .  In the context of upgrading the database, the location of the new Oracle home is denoted as  (see table below). Context



Oracle Home Installation /oracle//11204 Database Upgrade



Database Upgrade Tasks The standard upgrade procedure consists of the following tasks: Step no. Step Description

SAP System Availability


Planning and Checking Prerequisites SAP system available



SAP system available


Database Software Installation

SAP system available


Pre-Upgrade Steps

SAP system available


Database Upgrade Preparations



Guaranteed Restore Point



Database Upgrade



Database Post-Upgrade Steps Part 1 Downtime


Start SAP


Database Post-Upgrade Steps Part 2 SAP system available

SAP system available

Testing the Upgrade Procedure If you want to test the upgrade procedure, you can create a guaranteed restore point -short: a GRP- before the upgrade. After the upgrade you can use this restore point to flashback the database back to this point and rerun the upgrade procedure from the beginning. The necessary steps to reset the datababase including the environment are described at the end of this SAP note in section 'Reset Database to Restore Point created before the Upgrade'.

Important note: if you upgrade from source release 10.2 and you create a guaranteed restore point in that release before the upgrade, the value of database parameter COMPATIBLE can not be advanced automatically to '11.2.0' as long as the restore point exists. In that case you must set COMPATIBLE after the upgrade (see SAP note 1431798) after the restore point has been dropped. Setting COMPATIBLE can be done by running the script 'set_compatible.sql' or by BRSPACE. If you upgrade from release 11.2.0.x to the value of COMPATIBLE is not changed. Plannning and Checking Prerequisites You have to check that the prerequisites for upgrading your database to release are met. Is your SAP Product certified for Oracle Release 11.2? Check that your SAP product is certified for Oracle database release 11.2 --> PAM. What is the current database version (Source Release)? Check and ensure that your current Oracle database release is one the following:,, Connect to the database and check the version as follows: SQL> select version from v$instance; Is there enough free disk space? Ensure that there is enough free disk space for the installation of a new Oracle home, for the Oracle stage and for the Fast Recovery Area (if  required). For the initial installation of the new Oracle home you need a minimum of 5Gb (depending on your platform). You must consider that the  installation of patches (SBP, $ORACLE_HOME/.patch_storage, space for relinking etc.) requires additional disk space. Therefore you should have at least ~10Gb for the new Oracle home. About 30Gb of disk space should be sufficient for a guaranteed restore point to flashback the changes of an upgrade. Disk space for

Minimum Recommended

New Oracle Home

~10 Gb

Software stage (local) ~6 Gb Fast Recovery Area

~10 Gb or more ~10 Gb

~30 Gb

Checking OS Kernel Parameters and OS Package Requirements Check the Oracle database installation guide for software requirements (supported OS, OS versions, required OS packages, OS kernel parameters, etc.). When you install the new software, this will automatically be checked by the Oracle Universal Installer. Checking basic system properties Property

References and Further Information

Is the database to upgrade a RAC database?

See SAP note 1798976. 

Do the database files reside in ASM?

See SAP note 1798976.

Is a block change tracking file configured (BCT)?

See SAP note 964619. SQL> select status, filename from V$BLOCK_CHANGE_TRACKING;

Standby-Database (Data Guard)? Is the database located on an Oracle Engineered System (i.e. ODA or Exadata)? Does the database share the Oracle home with other databases? Is Database Vault enabled in the database?

Database Vault requires additional steps, i.e. you must enable XML DB in the  new Oracle home.

Is the software owner 'oracle'?

This is an SAP Installation with RAC, ASM, Engineered System or Shared Oracle home.

Is the software owner 'ora'?

SAP Standard Installation

  Preparation Log on as Software Owner Log on as the Oracle software owner - 'oracle' or 'ora' - and open a command shell (Bourne shell or C shell). OS commands that are  used in this SAP note assume C shell. There are certain differences when you log on to the database server between software owner 'oracle' and software owner 'ora'. See the following table: 'oracle'


'oracle' should be used as software owner only. For administration (incl. upgrade of the database) a dedicated administrator account should be used.

'ora' is used as software owner AND database administrator. Environment ORACLE_HOME, ORACLE_BASE,

No .dbenv* scripts, no database specific environment set

ORACLE_SID, PATH, LD_LIBRARY_PATH, DB_SID etc. is set through .dbenv* scripts

DB_SID is not set

DB_SID is set

Home directory is /home/oracle

Home directory is /oracle/$DB_SID

Runtime Oracle home -if set- is /oracle//112

Runtime Oracle home is /oracle//112_64

Set Environment Variable DISPLAY Setting the DISPLAY environment variable is only needed if you want to start Oracle Universal Installer (OUI) or Database Upgrade Assistant  (DBUA) in interactive mode. For silent mode, setting DISPLAY is not required. Set DISPLAY

$ setenv DISPLAY

Check DISPLAY $ echo DISPLAY is set to $DISPLAY Verify DISPLAY $ xclock & Prepare Oracle Software Stage Step


Create Directory

Example: $ mkdir -p /oracle/stage/11204

Download Oracle DVDs from SWDC



Copy the DVDs (SAR files) to the Oracle stage 

$ cd $ cp OR111264.SAR /oracle/stage/11204 $ cp OR211264.SAR /oracle/stage/11204

Goto Oracle stage and extract the Oracle Database Software

Ensure that 'SAPCAR' is in the path. Otherwise use the full path. $ cd /oracle/stage/11204 $ SAPCAR -xvf OR111264.SAR $ SAPCAR -xvf OR211264.SAR

Ensure that 'SAPCAR' is in the path or use the full path.

Define ORACLE_STAGE_11204 environment variable

$ setenv ORACLE_STAGE_11204 /oracle/stage/11204/database/SAP


Update SAP RUNINSTALLER Note: This step is only necessary if the new RUNINSTALLER version contains bug fixes or new features that are needed for your situation. If a newer version for of SAP RUNINSTALLER is available, you can download this version from SAP note 1524205 and install it. Checking Permissions in ORACLE_BASE Before you start with the installation of the software, you should check that you have permissions to write to the Oracle Base directory. $ echo $ORACLE_BASE && touch $ORACLE_BASE/write_test && rm $ORACLE_BASE/write_test && echo Permissions OK $ echo $ORACLE_BASE && test -w $ORACLE_BASE || echo Write permissions missing $ echo $ORACLE_BASE && test -w $ORACLE_BASE && echo Write permissions OK Checking contents of oratab $ test -e /var/opt/oracle/oratab && more /var/opt/oracle/oratab $ test -e /etc/oratab && more /etc/oratab This file contains a list of databases / database instances and their corresponding Oracle homes. The format of the entries is: ::Y|N Expected result (Example): One Oracle Database

Multiple databases

:/oracle//11203:N # # #

:/oracle//11203:N :/oracle//11203:N :/oracle//11203:N #

Checking contents of oraInst.loc $ test -e /var/opt/oracle/oraInst.loc && more /var/opt/oracle/oraInst.loc $ test -e /etc/oraInst.loc && more /etc/oraInst.loc Expected result: Software Owner Contents  'oracle'

inventory_loc= inst_group=oinstall


inventory_loc= inst_group=dba

Backing Up the Central Inventory $ cd /.. $ zip -r oraInventory.zip oraInventory Example: central inventory is located in /oracle (=$ORACLE_BASE) $ cd /oracle $ zip -r oraInventory.zip oraInventory Database Software Installation Install Oracle Database Software No. Step

Non-silent Installation (default)

Silent Installation (recommended)


Goto stage

$ cd /oracle/stage/11204/database/SAP


Check prerequisites


$ ./RUNINSTALLER -check silent


Check RUNINSTALLER installation settings

$ ./RUNINSTALLER noinstall

$ ./RUNINSTALLER -noinstall For further options, see SAP Note 1524205. -silent


Install the software


$ ./RUNINSTALLER -nocheck For further options, see SAP Note 1524205. -silent


Run scripts as root (root.sh)

$ su root -c "$ /oracle/$DB_SID/11204/root.sh"

This script must be run for silent and nonsilent installations.


Run scripts as root (orainstRoot.sh)

$ su root -c "/oracle/oraInventory/orainstRoot.sh"

This script must be run after the first Oracle  home was installed.


For further options, see SAP Note 1524205.

Install Oracle Database SAP Bundle Patch (SBP) l l l

This step is mandatory. It is recommended to install the latest SBP. Follow the instructions in the SBP README to install the SBP. Below is an example for the installation of an SBP. Setting environment variable OHRDBMS is not necessary as the Oracle home where the SBP is installed is inactive. 

Note: the Oracle home where the SBP is going to be installed is inactive which means that no Oracle processes are currently running from this Oracle home. Step



SBP Operating System Requirements

$ setenv IHRDBMS /oracle/$DB_SID/11204 $ setenv OHRDBMS /oracle/$DB_SID/112_64 # upgrade from 11.2.0.x $ setenv OHRDBMS /oracle/$DB_SID/102_64 # upgrade from $ setenv SBPFUSER # /usr/sbin/fuser or /sbin/fuser

Configure environment variables according to SBP README.

SBP Pre-Installation Steps

$ unzip -qd $IHRDBMS ... (see SBP README for the complete Download the SBP file and extract OPatch and command) MOPatch to the Oracle home.

$ $SBPFUSER $IHRDBMS/bin/oracle Installing the SAP Bundle $ env ORACLE_HOME=$IHRDBMS Patch $IHRDBMS/MOPatch/mopatch.sh -v -s

Ensure that the installation of the SBP finishes successfully. Check for the message "Link script "./link..sh" executed successfully."

SBP Post-Installation Steps

SBP post-installation steps will be performed AFTER the database upgrade. Keep the shell with the environment of SBP patching open!

Nothing to do here.

Minimal Downtime Patching If you are using the concept of patching Oracle homes with minimal downtime, please check SAP Note 1696869 for instructions how you can clone  a new Oracle home from an existing Oracle home.  Exit from Current Command Shell (optional) At this point the new Oracle home is completely installed and you can exit from the current shell. Pre-Upgrade Steps Start a New Command Shell Log on to the database server as database administrator and set DISPLAY in the environment (if not yet set). Perform pre-upgrade checks Run these checks in the environment of the database that is going to be upgraded. These checks do not change contents or configuration of the  database. When finished, check the resulting log file 'pre_upgrade_status.log' for errors and warnings. $ setenv ORACLE_HOME_TGT /oracle/$DB_SID/11204 $ cd $ORACLE_HOME_TGT/sap/ora_upgrade/pre_upgrade

$ sqlplus / as sysdba @pre_upgrade_status.sql Perform pre-upgrade tasks Run these tasks in the environment of the database that is going to be upgraded. Afterwards you should run the pre-upgrade checks again. When finished, check the corresponding log files pre_upgrade_status.log and pre_upgrade_tasks.log for errors and warnings. $ setenv ORACLE_HOME_TGT /oracle/$DB_SID/11204 $ cd $ORACLE_HOME_TGT/sap/ora_upgrade/pre_upgrade $ sqlplus / as sysdba @pre_upgrade_tasks.sql $ sqlplus / as sysdba @pre_upgrade_status.sql Perform Database Check with BRCONNECT This steps is optional. $ brconnect -u / -c -f check Database Upgrade Preparations Backup the Database Ensure that you have a valid backup of your database before you start the upgrade. You must be able to restore the database from the backup if  the upgrade fails. Stop the SAP Application (as SAP System Administrator) Stop the SAP system with 'stopsap r3' or the corresponding 'sapcontrol ' command. This is the point where the downtime for the upgrade procedure begins! Stop the database listener (as Oracle Database Administrator) Stopping the database listener is a measure to prevent new remote database connections during the upgrade process. Note: stop the listener only if this listener is dedicated for this database and does not serve as listener for other database instances. $ lsnrctl stop [] Create Guaranteed Restore Point If you create a guaranteed restore point just before starting the database upgrade you can use this restore point after the upgrade to flashback the database back to this point. This can be helpful in case of upgrade errors or for testing the upgrade procedure. The steps for this procedure are  described here. You can either use BRSPACE command or SQL scripts (from ORACLE_HOME_TGT/sap/ora_upgrade/pre_upgrade) for creating and managing the restore point. Prerequisite: In order to create a restore point, the fast recovery area must be configured (see SAP note 966073). Step

SQL Script

$ sqlplus / as sysdba SQL> show parameter db_recovery_file_dest SQL> SELECT * FROM V$RECOVERY_FILE_DEST; Check Fast Recovery SQL> SELECT * FROM Area Status and Configuration V$FLASH_RECOVERY_AREA_USAGE;


$ brspace -f mfback -a fbshow

If FRA is not yet configured, see SAP note 966073. Create guaranteed restore point

$ cd $ORACLE_HOME_TGT/sap/ora_upgrade/pre_upgrade $ brspace -f mfback -a rpcreate -f -g -p $ sqlplus / as sysdba @grp_create_restore_point.sql GRP_BEFORE_UPGRADE_11204

List restore point

$ sqlplus / as sysdba @grp_list_restore_point.sql

$ brspace -f mfback -a rpshow

Database Upgrade No. Step

Command Set environment variable ORACLE_HOME_SRC to the current ORACLE_HOME value! $ setenv ORACLE_HOME_SRC $ORACLE_HOME


The following setting should work for all releases: Specify Source Oracle Home $ setenv ORACLE_HOME_SRC $ORACLE_HOME For upgrades from release 10.2: $ setenv ORACLE_HOME_SRC /oracle/$DB_SID/102_64 For upgrades from release 11.2.0.x with software owner ora: $ setenv ORACLE_HOME_SRC /oracle/$DB_SID/112_64 For upgrades from release 11.2.0.x with software owner oracle: $ setenv ORACLE_HOME_SRC /oracle/$DB_SID/112 Set environment variable ORACLE_HOME_TGT to the location where you installed the new Oracle home.


Specify Target Oracle Home $ setenv ORACLE_HOME_TGT /oracle/$DB_SID/11204 $ cd $ORACLE_HOME_TGT/sap/ora_upgrade/post_upgrade $ env | grep ORACLE_HOME


Check Upgrade Settings

$ echo ORACLE_HOME is set to $ORACLE_HOME $ echo ORACLE_HOME_SRC is set to $ORACLE_HOME_SRC $ echo ORACLE_HOME_TGT is set to $ORACLE_HOME_TGT $ ./dbua.sap.sh -q l



Perform Database Upgrade

Check DBUA Log Files


Option #1: Run DBUA in interactive, non-silent mode: $ cd $ORACLE_HOME_TGT/sap/ora_upgrade/post_upgrade $ ./dbua.sap.sh Option #2: Run DBUA in silent mode: $ cd $ORACLE_HOME_TGT/sap/ora_upgrade/post_upgrade $ ./dbua.sap.sh -silent


Location of DBUA logs: $ORACLE_BASE/cfgtoollogs/dbua/$DB_SID/upgrade


$ cd $ORACLE_BASE/cfgtoollogs/dbua/$DB_SID $ ls -l $ cd upgrade Check important DBUA log files (UpgradeResults.html, CustomScript.log). You can also check DBUA log files for ORA-messages using the script 'check_dbua_logs.sh'. $ cd $ORACLE_HOME_TGT/sap/ora_upgrade/post_upgrade $ ./check_dbua_logs.sh


  Database Post-Upgrade Steps Part 1 Change Runtime Oracle home (symbolic link) This step is required when you upgraded from release 11.2.0.X to Remove the old symbolic link and create a new symbolic link. $ rm /oracle/$DB_SID/112_64 $ ln -s /oracle/$DB_SID/112_64 /oracle/$DB_SID/11204 In the scenario 'upgrade ->' the symbolic link should already be created during the installation of the new Oracle home. /oracle/$DB_SID/112_64 --> /oracle/$DB_SID/11204 Set ORACLE_HOME (Upgrade from --> Keep the shell where you performed the upgrade. For this task, start another shell and adapt .dbenv*sh scripts. After adapting the old ORACLE_HOME path in the .dbenv scripts, log off and log on  again and check the environment. $ env | grep ORA $ env | grep PATH $ env | grep LIB Ensure that the environment variables PATH and LD_LIBRARY_PATH refer to the same ORACLE_HOME. Also change .dbenv scripts for adm user. Set ORACLE_HOME (Upgrade from 11.2.0.x --> There should be nothing to do with the ORACLE_HOME env. variable because ORACLE_HOME is already set to $OHRDBMS. Check the environment: $ env | grep ORA $ env | grep PATH $ env | grep LIB Ensure that the environment variables PATH and LD_LIBRARY_PATH refer to the same ORACLE_HOME. Check SQL*Net Files Before you start the database or the listener from the new Oracle home, check and adapt the SQL*Net profiles $ cd $ORACLE_HOME/network/admin $ vi tnsnames.ora listener.ora sqlnet.ora Start database from Runtime Oracle home OHRDBMS Note: this is the first time that you start the database instance after the upgrade from the new Oracle home using the runtime home environment. $ sqlplus / as sysdba startup You might get the warning "ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance" if SSFS is not configured. Check COMPATIBLE and Guaranteed Restore Point SQL> show parameter compatible Upgrade from 10.2: If you created a GRP before, drop the GRP and set compatible.

CustomScript.log: POST-UPGRADE: Checking for guaranteed restore points GUARANTEED RESTORE POINT: GRP_BEFORE_UPGRADE At least one restore point exists. Parameter COMPATIBLE can not be set now. You have to set COMPATIBLE after this upgrade manually. SQL> drop restore point GRP_BEFORE_UPGRADE; $ sqlplus / as sysdba @set_compatible.sql Check Post-upgrade status $ cd $ORACLE_HOME/sap/ora_upgrade/post_upgrade $ sqlplus / as sysdba @post_upgrade_status Check the log file. Update SAP BR*Tools / Update Statistics $ brconnect -u / -c -f stats -t system_stats $ brconnect -u / -c -f stats -t oradict_stats $ brconnect -u / -c -f stats -t all -f collect -p 4 Check Database Parameter Settings See SAP note 1431798. Perform SBP Post-install Steps Perform SBP Post-install instructions according to the SBP README. Perform Manual Post-Upgrade Steps for the Patch of Bug 14373728 Reference: My Oracle Support Doc Id 1537496.1 The patch for bug 14373728 has been included in version Depending on the value of COMPATIBLE before/during the upgrade to this patch requires manual post-upgrade steps. Database Upgrade Scenario What to do From 11.2.0.x to

No manual steps needed. The patch is automatically applied and enabled. Before/During the database upgrade, the value of COMPATIBLE was < '11'. The following manual post-upgrade steps are required: Preparation Ensure that COMPATIBLE has been set to a value >= '11' SQL> show parameter compatible Reference: SAP Note 1431798 For RAC database: SQL> alter system set cluster_database=false scope = spfile;

From 9.2.0.x to or from 10.2.0.x to

Shutdown the database cleanly. Manual Post-Installation Steps

  Startup the database in upgrade mode and run the dictionary script. SQL> startup upgrade SQL> @?/rdbms/admin/c1102000.sql SQL> shutdown immediate Post-Installation For RAC database: SQL> alter system set cluster_database=true scope = spfile; Start the database in normal mode.   Check LOCAL_LISTENER setting $ sqlplus /nolog SQL> conn / as sysdba SQL> show parameter local_listener If the parameter LOCAL_LISTENER was not set before the upgrade, it will normally be set by DBUA to 'LISTENER_'. DBUA also adds a corresponding entry to the tnsnames.ora file in the new Oracle home. Example: entry in tnsnames.ora:   LISTENER_OQ1.WORLD =   (ADDRESS = (COMMUNITY = SAP.WORLD)(PROTOCOL = TCP)(HOST = wdflbmd6813)(PORT = 1527))

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance ORA-00119: invalid specification for system parameter LOCAL_LISTENER ORA-00132: syntax error or unresolved network name 'LISTENER_OQ1' Start the Database Listener If the SQL*Net files are stored in the $ORACLE_HOME/network/admin, go to this directory and check the contents of these files. There should be no references to the old Oracle home. Then start the listener from the new Oracle home. $ lsnrctl start [] Configure Block Change Tracking If block change tracking was enabled before the upgrade, you should configure block change tracking again (SAP note 964619). SQL> ALTER DATABASE ENABLE BLOCK CHANGE TRACKING USING FILE '' REUSE; Backup the Database You should perform a complete database backup. Start SAP Check that SAP can connect to the database $ R3trans -d Start the SAP Application Log on as adm and start the SAP application: $ startsap r3 or $ startsap or $ sapcontrol -nr -function Start $ sapcontrol -nr -function GetProcessList Checking the SAP Application Check that the SAP application runs fine with the new Oracle release. When everything is ok, release SAP for SAP users. Database Post-Upgrade Steps Part 2 Drop Restore Point If a guaranteed restore point was created before the ugprade, it must be dropped. If you do not drop the restore point and the fast recovery area is  full, the database would stop. Only if you want to rerun the database upgrade, then you should not drop the restore point. Step

SQL Script


List restore point

$ sqlplus / as sysdba @grp_list_restore_point.sql

$ brspace -f mfback -a rpshow

Drop guaranteed restore point

$ cd $ORACLE_HOME_TGT/sap/ora_upgrade/pre_upgrade $ sqlplus / as sysdba @grp_drop_restore_point.sql

$ brspace -c force -f mfback -a rpdrop -f -g -p GRP_BEFORE_UPGRADE_11204

List restore point

$ sqlplus / as sysdba @grp_list_restore_point.sql

$ brspace -f mfback -a rpshow

Deinstall the old Oracle Home See SAP Note 1525025. Reset Database to Restore Point created before the Upgrade If you upgraded the database to, but you are not satisfied with the result or you want to rerun the whole upgrade procedure for testing purposes, you can use the guaranteed restore point that you created before the upgrade and flashback the database to the state before the upgrade. The following table shows the steps that are required. Step



Stop listener from the new Oracle home

$ lsrnctl stop

Environment must be set to use the new Oracle home

Start database in the new Oracle home

$ sqlplus / as sysdba SQL> startup

Environment must be set to use the new Oracle home Expected result:

Check scripts to use for flashback operation

Check which restore points are available

grp_create_restore_point.sql $ cd grp_drop_restore_point.sql $ORACLE_HOME_TGT/sap/ora_upgrade/pre_upgrade grp_flashback_2_restore_point.sql $ ls -l grp*.sql grp_list_restore_point.sql grp_open_resetlogs.sql $ sqlplus / as sysdba @grp_list_restore_point.sql $ brspace -f mfback -a rpshow

Flashback to $ sqlplus / as sysdba GRP_BEFORE_UPGRADE_11204 @grp_flashback_2_restore_point.sql

At least one restore point should be available with name GRP_BEFORE_UPGRADE_11204 Alternatively use BRSPACE to reset the  database back to the restore point. If you upgraded from 11.2.0.x to, you have to change the symbolic link of the runtime Oracle home .

Change environment to old Oracle home

If you upgraded from 10.2.0.x to, you have to change the .dbenv* scripts to the old Oracle home, then log off and log on again.

Open the database in the old Oracle home

$ sqlplus / as sysdba @grp_open_resetlogs.sql

Start the listener in the old Oracle home

$ lsnrctl start

After flashback to GRP the database must be opened with RESETLOGS option.

$ cd $ORACLE_HOME_TGT/network/admin Cleanup SQL*Net profiles in the new $ ls -l listener.ora, sqlnet.ora, tnsnames.ora Oracle home $ rm -i listener.ora, sqlnet.ora, tnsnames.ora

Remove SQL*Net profiles from /network/admin listener.ora, sqlnet.ora, tnsnames.ora

$ cd $ORACLE_HOME_TGT/dbs Cleanup database profiles in the new $ ls -l *${DB_SID}*.ora Oracle home $ rm -i *${DB_SID}*.ora

Remove init.ora, spfile.ora, orapw, lk, hc_.dat

Cleanup SAP profiles in the new Oracle home

$ cd $ORACLE_HOME_TGT/dbs $ rm -i *${DB_SID}*.sap $ rm -i *${DB_SID}*.utl

Remove init.sap, init.utl from

Check the SAP can connect

$ R3trans -d

as adm, for SAP NetWeaver systems with ABAP stack

Start SAP (optional)

$ startsap r3

as adm, for SAP NetWeaver systems with ABAP stack Either restore a backup of the oratab file from before the ugprade or edit the oratab file manually. Search for the entry of the database and replace by .

Edit oratab file

Example: :/oracle//11204:N Replace this entry by the old entry: :/oracle//11203:N Deinstall new Oracle home


Drop restore point

You should drop the restore point if you want to run the system for a while in the old environment. If you want to test the upgrade again, you can use this restore point for another flashback operation.

$ sqlplus / as sysdba @grp_drop_restore_point.sql

Other Attributes Database System

Oracle 11.2

Validity This document is not restricted to a software component or software component version

View more...


Copyright ©2017 KUPDF Inc.