Upgrade to Oracle Database 11 Release 2 Based on Oracle Patch Set Release 11.2.0.

4
C re a te d :

2014/06/23 02:01 PM

Ta g s :

Oracle

URL:

https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui/main.do

U p d a te d :

2014/07/14 09:18 AM

TO DO
Get note, current version has no text 1458580 - Oracle Upgrade to 11g Release 2 (11.2) on Windows
resume from pg 31 - Post-Upgrade
* means note to self
DoSo Code(page #s from the upgrade guide)
Planning Phase:
1. You check the original version of your database
1. Enter the following command:
sqlplus version>
Enter the following commands:
sqlplus / as sysdbaSQL> select version from v$instance;
2. You check the hardware and software requirements

1. The complete list of hardware and software requirements for every platform is included in the Oracle
documentation. The hardware and software requirements are also checked in detail during the software
installation phase.
3. You check additional requirements for the upgrade
4. You decide whether you want to use multiple Oracle homes
5. You check the SAP System prerequisites
1. Notes 1416108, 1414733, 1433301 and 1417124 aren't applicable to any of our systems

Oracle Database Upgrade(pg 21):

1. You install the Oracle 11.2 software [page 21].
1. Stop the SAP system (not the database instance) with the SAP MMC
2. See SAP note 1431799 for information about identifying and installing the correct Oracle database software
version
1. If you copy the files from the RDBMS media to a local disk, do not use directory names containing blanks
3. Start the Oracle Universal Installer (OUI) with the PowerShell or command script (sapserver.cmd).
1. For support reasons, do not use the setup.exe file in the directory <media_DRIVE>:\database\. Using
sapserver.cmd or sapserver.ps1 guarantees a unique setup of the ORACLE_HOME that is common to
SAP systems.
2. If a command prompt window appears, specify the drive letter of the local disk where you want to install the
Oracle software, and the <DBSID>. The command prompt window only appears if you perform a new
installation (under a different user), or if the ORACLE_HOME and <DBSID> are not set.
4. In the Oracle Universal Installer, enter the information as shown in the table on pg 24 & 25 of the upgrade guide
5. Install the required Oracle patches [page 23] (if available).
1. See SAP note 1949250 for which Oracle Database patches have been released for SAP on top of the
11.2.0.4.0 patch set.
2. Stop the services OracleMTSRecoveryService and Distributed Transaction Coordinator.
3. Follow the instructions of the bundle patch README to install the bundle patch with OPatch.
4. Follow the instructions of the corresponding patch READMEs to install the generic patch(es) with OPatch.
5. Start the services OracleMTSRecoveryService and Distributed Transaction Coordinator.
6. You have to update the Oracle Instant Client software to the current version of your release (11.2.0.4).
1. Stop the central instance and dialog instance (if available)
2. See SAP Note 998004 for instructions on how to update the Oracle Instant Client software. The following
steps are from that SAP Note:
1. Download the latest supported Oracle Instant Client from SAP Service Marketplace at
http://service.sap.com/oracle

2. Delete the Oracle Instant Client. Since the contents of a newer Oracle Instant Client might differ from
the client version you are currently using, you first have to delete the current Oracle Instant Client as
follows:
1. Download deldbclient.vbs, which is included in the deldbclient.zip file attached to SAP Note
998004
2. Stop all application servers, including the central instance.
3. On the central instance host, open a command prompt as <SAPSID>adm, change the current
working directory to DIR_CT_RUN, and run cscript.exe //nologo deldbclient.vbs in this directory.
4. Repeat the previous step on every application server instance DIR_EXECUTABLE directory.
3. Unpack the Oracle Instant Client to DIR_CT_RUN using SAPCAR -xvf <OCL SAR Archive>
4. Start your SAP application servers. The Oracle Instant Client is automatically distributed to the
instance-specific DIR_EXECUTABLE directories.
3. Do not restart the central instance and dialog instance (if available).[upgrade guide pg 24. contradicts SAP
Note]
2. You copy and adapt the old Oracle SQL*Net files [page 24].
1. After the database software installation, you must copy the old SQL*Net files, that is, listener.ora, sqlnet.ora, and
tnsnames.ora, and adapt them as described on pg 25 of the upgrade guide
3. You run the pre-upgrade scripts.
1. See SAP Notes 1431793 and 1431797 for troubleshooting guides. Following is from Note 1431793:
2. In order to use SAP-specific upgrade scripts, you must log on to the database server as the Oracle database
administrator user and change the current directory to the location of the upgrade scripts. cd
% ORACLE_HOME% \sap\ora_upgrade\pre_upgrade
3. check the pre-upgrade status
Option #1: run both pre-upgrade information tools in one step
OS> sqlplus / as sysdba @pre_upgrade_status.sql
In this step both pre-upgrade information tools utlu112i.sql (Oracle-generic) and utlu112i_sap.sql
(SAP-specific) are executed and the result is logged in 'pre_upgrade_status.log'.
Option #2: run the pre-upgrade information scripts one after ther other
Running the generic pre-upgrade information utility utlu112i.sql:

4.
5.

6.

7.

SQL> spool pre_upgrade_info.log

SQL> @utlu112i.sql
SQL> spool off
Running the SAP-specific pre-upgrade checks
SQL> spool pre_upgrade_checks.log
SQL> @pre_upgrade_checks.sql
SQL> spool off
Running pre-upgrade-tasks is recommended to improve the performance of the upgrade process:
OS> sqlplus / as sysdba
SQL> spool pre_upgrade_tasks.log
SQL> @pre_upgrade_tasks.sql
SQL> spool off
You back up the Oracle database [page 26].
You remove the old Oracle Listeners [page 26].
1. Choose StartAll Programs<Old_Oracle_Home>Configuration and Migration ToolsNet
Configuration Assistant.
On the Welcome screen, choose Listener Configuration and then Next.
Choose Delete listener and select the listener you want to delete from the drop-down list (normally this is the
listener with the name LISTENER).
You change the environment for user <sapsid>adm [page 26].
1. Make sure you have stopped the SAP system and that the database is running.
2. In the user environment of <sapsid>adm, rename the following variables:
1. ORACLE_HOME
2. TNS_ADMIN (if it exists)
3. Log off and log on again to activate the changes.
You upgrade the Oracle database [page 27].
1. To upgrade the database, use the Oracle Database Upgrade Assistant (DBUA). If there are any issues see SAP
Note 1431797 - Oracle 11.2.0: Troubleshooting the Database Upgrade

2. If not yet stopped, stop the SAP system.

3. Do not stop the database instance. The database instance must be running in the current (old) environment
4. Change the registry entry of ORA_<DBSID>_AUTOSTART by entering the
command:<new_Oracle_Home>\bin\oradim -edit sid <dbsid> startmode manual
5. Start the Oracle Database Upgrade Assistant using one of the following options:
1. *Read note 1431793
You use a PowerShell script (recommended). To start the Oracle Database Upgrade Assistant (DBUA)
with a PowerShell script, proceed as described in SAP Note 1431793, section Performing Database
Upgrade on Windows. The advantage of using a PowerShell script is that all required parameters are
already specified in the DBUA, and manual post-installation tasks are reduced to a minimum.
These steps are from note 1431793, section Performing Database Upgrade on Windows
1. Open a Windows Powershell in elevated mode (run as administrator) and change the working
directory to<ORACLE_HOME>\sap\ora_upgrade\post_upgrade.
2. From this Powershell you run the dbua.sap.ps1 script.
PS> cd <ORACLE_HOME>\sap\ora_upgrade\post_upgrade
PS> .\dbua.sap.ps1
You use the Start menu: Choose StartAll ProgramsOracle <NEW_ORACLE_HOME_NAME>Configuration and Migration ToolsDatabase Upgrade Assistant.
Note that if you use this method, you do not automatically run the SAP-specific DBUA upgrade scripts, and
you have to run them after the upgrade manually.
6. Read SAP Note 1431793 section 4,
7. Proceed as shown in the table on pg 28 of the upgrade guide. Recommendation: You should not use the 'Back'
button of the Database Upgrade Assistant as this might change the preconfigured settings. Instead of going
back, you should better cancel DBUA and start the script 'dbua.sap.ps1' again.
Post-Upgrade:
1. You set the user environment variables [page 31].

2.

3.

4.

5.

1. In the user environment and system environment <sapsid>adm, check the PATH variable and, if required, remove
all parts referring to the old Oracle version.
2. In the user environment of <sapsid>adm, set the ORACLE_HOME variable to the correct value for Oracle 11g,
for example to: <DRIVE>:\ORACLE\<DBSID>\11204.
3. If you have two or more Oracle Homes, make sure that the user environment variable PATH of the <sapsid>adm
user points to the corresponding %Oracle_Home%\bin directory.
4. Set the user environment variable TNS_ADMIN to point to the directory \\<sapglobalhost>\sapmnt\
<DBSID>\SYS\profile\oracle.
5. Log off and log on again to activate the environment changes in your user session.
You create the Oracle TNSListener service [page 32].
1. Stop the old Oracle listener before you create the Oracle TNSListener Service.
2. Open a command prompt and enter the following
command:<Complete_Path_To_New_Oracle_Home>\bin\lsnrctl start <Listener_Name>
You change the registry value of Oracle Autostart [page 34].
1. Change the registry value of ORA_<DBSID>_AUTOSTART. Open a command prompt and enter the following
command:<new_Oracle_Home>\bin\oradim -edit -sid <dbsid> -startmode manual
2. Ignore the error message: Unable to start service, OS Error 1056.
3. Alternatively, use regedit.exe to change the registry key to value FALSE. The registry key is available at
HKLM:\Sofware\Oracle\KEY_<DBSID>11204.
You check the start up type of the Oracle services [page 34].
1. Start the Oracle services (Database and Listener), if not yet started.
2. Start the Distributed Transaction Coordinator Service.
You update BR*Tools and the SAP executables [page 35].
1. The BR*Tools of Version 7.20 and higher require the Microsoft Visual Studio 2005 Redistributables. For more
information about and how to install them, see SAP Note 684106.
2. Apply the following latest available packages for the SAP executables in the following sequence for:
1. SAPEXE( http://service.sap.com/swdcDownloadSupport Packages and PatchesSupport
Packages and Patches - Entry by Application GroupAdditional ComponentsSAP
KernelSAP Kernel <platform>SAP Kernel <your SAP release>Windows Server on

<platform># Database Independent)

2. dw_xxx(same download location as SAPEXE)
3. SAPEXEDB(http://service.sap.com/swdcDownloadSupport Packages and
PatchesSupport Packages and Patches - Entry by Application GroupAdditional
ComponentsSAP KernelSAP Kernel <platform>SAP Kernel <your SAP
release>Windows Server on <platform>Oracle)
4. lib_dbsl(same download location as SAPEXEDB)
5. Download the most current version of the BR*Tools
from:http://service.sap.com/swdcDownloadSupport Packages and PatchesSupport
Packages and Patches - Entry by Application GroupAdditional ComponentsSAP Kernel
SAP Kernel <platform>SAP Kernel <version>Windows Server on <platform>Oracle
Oracle DBATLxxxx.sarDBATLxxxx.sar - see SAP Note note 12741 for latest version
6. Unpack BR*Tools to the DIR_CT_RUN [page 48] directory.
7. Update the SAPDBA role as <sapsid>adm user as follows[pg 36]:
1. Go to the %ORACLE_HOME%\database directory:cd % ORACLE_HOME% \database
2. Copy sapdba_role.sql from the DIR_CT_RUN directory to the %ORACLE_HOME%\database
directory.
3. Determine the SAPSCHEMA_ID by entering the following commands:
sqlplus /nolog
SQL> connect / as sysdba
SQL> select username from dba_users where username like 'SAP% ';
For the schema, you have to use the names beginning with SAP, e.g.
SAPW41,SAPSR3,SAPSR4,SAPSR3DB (Java)
Close sqlplus with this command:SQL>exit
1. Execute the following SQL commands for all existing SAP schemas in the database:
sqlplus /nolog @sapdba_role <SAPSCHEMA_ID>
sqlplus /nolog @sapdba_role <SAPSCHEMA_ID>DB
6. You perform post-upgrade tasks [page 36].

1. Gather Oracle optimizer statistics by executing the following commands as the <sapsid>adm user:
brconnect -u / -c -f stats -t system_stats
brconnect -u / -c -f stats -t oradict_stats
2. Check the Oracle database parameters against SAP Note 1431798 and adjust them if necessary.You can find
an automated script in SAP Note 1171650 to help you check whether your SAP system complies with the
database parameter recommendations at any given point in time.
3. Update the Oracle database statistics with BRCONNECT as follows:
brconnect -u / -c -f stats -t all -f collect -p 4
4. Run post_ugprade_status.sql.
Open a command prompt and change to the directory
<new_oracle_home>\sap\ora_upgrade\post_ugprade.
From this directory start sqlplus.exe and enter the following commands:SQL>connect / as
sysdbaSQL>@post_upgrade_status.sql
This provides an overview of the status of the upgraded database.
7. You delete the old Oracle software [page 37]. To deinstall the Oracle 11.2 software, you use the deinstallation tool, see
SAP Note 1591580
1. Stop the service Distributed Transaction Coordinator.
2. Stop the services of the old Oracle Home.
3. Oracle 11g: To check, run the command: <Old_Oracle_Home>\deinstall\deinstall.bat -checkonly.
4. To deinstall, run the command: <Old_Oracle_Home>\deinstall\deinstall.bat
5. Follow the instructions for the Oracle Home you want to remove.
1. On the Welcome screen, choose Deinstall Products.
2. On the Content tab of the Inventory dialog box, check the node representing your old Oracle Home and
press the Remove button.
3. Confirm the removal of the products in the popup that appears
6. If available, delete the services in which the name contains the old Oracle Home name.
To delete a service, open a command prompt and enter:sc delete <service_name>
7. In the Windows Explorer, delete the old Oracle home directory to prevent that an Oracle process can start again

from the old Oracle home.

8. Delete the entry Oracle <OLD_ORACLE_HOME_NAME>, if it exists, in the Windows Start menu
8. You back up the database [page 40].
9. You configure the new features for Oracle Database 11g Release 2 (11.2) [page 41].
see SAP Note 1431800

Notes
means note's been read
314671 - Long WINDOWS domain names and Oracle 8.1.x or higher
1431800 - Oracle 11.2.0: Central Technical Note
1431797 - Oracle 11.2.0: Troubleshooting the Database Upgrade
1431793 - Oracle 11.2.0: Upgrade Scripts
1398634 - Oracle database 11g: Integration in SAP environment
1431798 - Oracle 11.2.0: Database Parameter Settings
1458580 - Oracle Upgrade to 11g Release 2 (11.2) on Windows[note's empty]
1431796 - Oracle 11.2.0: Troubleshooting the Software Installation
1431799 - Oracle 11.2.0: Current Patch Set
1949250 - Oracle 11.2.0: Patches / Patch collections for 11.2.0.4
998004 - Update the Oracle Instant Client on Windows
850306 - Oracle Critical Patch Update Program
134592 - Importing the SAPDBA role (sapdba_role.sql)
839182 - Oracle patch installation with OPatch
834917 - Oracle Database 10g: New database role SAPCONN
1430669 - BR*Tools support for Oracle 11g

1519872 - SAP Database User Profile SAPUPROF

758563 - Oracle Metalink access for SAP customers
684106 - Microsoft runtime DLLs
12741 - Current versions of BR*Tools
1591580 - Oracle 11.2.0: Oracle Home administration on Windows
1696869 - Patching of Oracle Homes with Minimal Downtime(1431800)
973450 - Oracle Advanced Security: Network encryption
974781 - Oracle internal maintenance jobs
1522952 - Password Complexity Verification Function
1915325 - Oracle 11.2.0: LOCAL_LISTENER
1171650 - Automated Oracle DB parameter check
1739274 - Oracle 11.2.0: Database Parameter COMPATIBLE
789011 - FAQ: Oracle memory areas
1565421 - Oracle 11g: dbms_redefinition may flush shared pool
1627481 - Preemptive redolog switches in Oracle 11.2
690241 - The Shared SQL Area in the Shared Pool and large SQL Stmnts
1502374 - Database Vault Policy Scripts for SAP (11.2)
740897 - Info about the Oracle license scope; Required Oracle options
1256322 - Establishing a remote database connection in DBACOCKPIT