Database Upgrade Guide Upgrade to Oracle Database 10g Release 2 (10.2): UNIX Target Audience —.µsºl Technology Consultants —.µsºl System Administrators
PUBLIC —.µŠ�£S"në,¹çð»ł*ëÈ Ù› %î qѳ c$×ëŒ� ;jhŽŁˆ°ÜsÁy Þ{S ”z Ÿ j†> ›À +G
Document History
CAUTION
Before you start the implementation, make sure you have the latest version of this document. You can find the latest version at the following location: http://service.sap.com/instguides Database Upgrades Oracle The following table provides an overview of the most important document changes. Version
Date
Description
3.0 2.11
2009-08-25 2007-02-21
2.1
2006-08-28
2.0
2006-08-01
Major update Error correction in section Disabling Database User Locking Mechanism For Failed Logins: command line connect / as sysdba inserted Various changes including new section Disabling Database User Locking Mechanism for Failed Logins Various changes including new section Installing Oracle Critical Patch Updates
2/48
PUBLIC
2009-08-25
Table of Contents
Chapter 1 1.1 1.2 1.3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SAP Notes for the Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . More Information on SAP Service Marketplace . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2 2.1 2.2 2.3 2.4
Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Checking the Original Version of Your Database . . . . . . . . . . . . . . . . . . . . . . . . 9 Checking Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . 10 Reviewing the Oracle-Specified Kernel Parameters and Shell Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Checking Additional Requirements for the Upgrade . . . . . . . . . . . . . . . . . . . . 11
Chapter 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10
Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Correct UNIX Users, Groups, and Authorizations . . . . . . . . . . . Checking the Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running the Pre-Upgrade Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the Prerequisites for the Oracle Universal Installer . . . . . . . . . . . . . Checking the SAP System Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrating to Automatic Undo Management . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping Statspack Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the SYSTEM and SYSAUX Tablespace for Freespace . . . . . . . . . . . . Checking for Invalid Database Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Oracle Instant Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13 13 14 15 16 17 18 18 19 19 20
Chapter 4 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.1.6
Oracle Database Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking and Setting the Environment Variables . . . . . . . . . . . . . . . . . . . . . . Backing Up the Oracle Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Steps for the AIX Operating System . . . . . . . . . . . . . . . . . . . . . . . Running the Oracle Universal Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Current Patch Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Required Interim Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21 21 22 23 24 24 26 27
2009-08-25
PUBLIC
5 6 6 7
3/48
4.1.7 4.1.8 4.1.9 4.2 4.2.1 4.2.2
Copying and Adapting the SQL*Net Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up the Oracle Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shutting Down the SAP System and Oracle Listener Process . . . . . . . . . . . . . . Database Structure Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the oratab Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Database Upgrade Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27 28 29 29 29 30
Chapter 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 5.14 5.15 5.16 5.17
Post-Upgrade Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finalizing the Environment of the ora<dbsid>User . . . . . . . . . . . . . . . . . . . . Checking the Upgraded Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating BR*Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performing Post-Upgrade Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Oracle Critical Patch Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking the oratab Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the Listener Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Renaming the Old $ORACLE_HOME/bin Directory . . . . . . . . . . . . . . . . . . . . Checking the Read Authorization of the <sapsid>adm User . . . . . . . . . . . . . Changing the Environment for the <sapsid>adm user . . . . . . . . . . . . . . . . . . Checking SAP Profile Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Location of the JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disabling Database User Locking Mechanism For Failed Logins . . . . . . . . . . . . Checking the National Character Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the New Features for Oracle Database 10g Release 2 (10.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33 33 34 35 36 36 38 38 39 39 40 40 40 41 43 43 43
4/48
PUBLIC
44
2009-08-25
1
Introduction
1 Introduction
This documentation explains how to upgrade the Oracle database for the SAP system on the UNIX operating system: ¸¾˜zòí From Oracle version 9.2.0 or Oracle Database 10g Release 1 (10.1.0.4) ¸¾˜zòí To Oracle Database 10g Release 2 (10.2) CAUTION
SAP certifies Oracle 10.2 only from release 10.2.0.2. SAP does not certify nor support Oracle 10.2.0.1. Make sure that your target release is Oracle 10.2.0.2 or later. This documentation only covers the upgrade from Oracle 9.2.0.4 or later – including Oracle 10.1.0.4 – to Oracle Database 10g Release 2 (10.2). NOTE
Oracle offers and supports direct database upgrades from Oracle 8.1.7 to Oracle 10.2 although we do not recommend this. We do not describe direct upgrades in this documentation. SAP has not tested and validated the direct upgrade path from Oracle 8.1.7 to Oracle 10.2. If you intend to perform a direct upgrade from Oracle 8.1.7 to Oracle 10.2, see the Oracle Database 10g Release 2 (10.2) upgrade documentation. You can obtain the Oracle documentation at the Oracle Technology Network (OTN) website. You use the tools Oracle Universal Installer (OUI), Oracle SQL*Plus, and Oracle Database Upgrade Assistant (DBUA) to perform the upgrade. CAUTION
Make sure you have the latest version of this document. You can always find this as follows: http://service.sap.com/instguides Database Upgrades Oracle . NOTE
In this document we use <DBSID> for the database instance identifier and <SAPSID> for the SAP system identifier. These can be different if your: ¸¾˜zòí Database system uses Oracle Real Application Cluster (RAC) ¸¾˜zòí SAP system uses Multiple Components in One Database (MCOD) Implementation Considerations
2009-08-25
PUBLIC
5/48
1
Introduction
1.1
New Features
Implementation Considerations
lÕZád& For more information about implementation considerations, including the most important SAP Notes for the upgrade, see Planning [page 9]. lÕZád& Be sure to read the relevant SAP Notes before beginning the upgrade. These notes contain the most recent information about the upgrade, as well as corrections to the documentation. You can find the most recent version of the SAP Notes at http://service.sap.com/notes lÕZád& Make sure you are using the Oracle Universal Installer (OUI) shipped with the installation CDs for Oracle Database 10g Release 2 (10.2).
1.1 New Features For the complete list of new features of the Oracle Database 10g Release 2 (10.2), see the New Features documentation from Oracle. You can access the complete Oracle documentation at the Oracle Technology Network (OTN) website. RECOMMENDATION
We recommend that you check the most important new features in the Oracle documentation since some new features might affect the operation of your production system.
1.2 SAP Notes for the Upgrade Make sure that you read the following SAP Notes, which you can find at http://service.sap.com/notes: Number
Title
Remarks
819830
Oracle Database 10g: Additional Information on upgrade: UNIX Oracle Database 10g: Integration into the SAP environment Oracle Database 10g: New Functions
Required late-breaking information
720886 828268
830576
Parameter recommendations for Oracle 10g
841728
10.2: Solutions for installation and upgrade problems Oracle 10.2.0: Applying Patch Set / Patches / Patch Collection
839187
6/48
Provides information about integration of Oracle Database 10g products / options within SAP Provides information about the Oracle Database 10g features that can be used within an SAP environment. In addition, contains links to notes describing the procedure to activate some of the new Oracle Database 10g features. Provides information about Oracle initialization parameters that need to be reset to their default values or which need to be removed Describes known software installation problems and solutions or workarounds Contains important information about the installation of the current patch set, patch (UNIX) or patch collection (Windows), and critical patch update (UNIX) for Oracle 10.2.0.4
PUBLIC
2009-08-25
1
Introduction
1.3
More Information on SAP Service Marketplace
Number
Title
Remarks
871735 871096
Current patch set for Oracle 10.2.0 Oracle Database 10g: Patch sets/ patches for 10.2.0 Oracle 10.2.0: Patches/Patch collections for Oracle 10.2.0.4 Oracle Critical Patch Update Program Importing the SAPDBA role (sapdba_role.sql) Oracle Database 10g: New database role SAPCONN Oracle Database 10g: Instant Client Release 10 on Unix Oracle Database 10g: OPatch
Describes the current Oracle patch set Lists the status of Oracle patch sets and interim patches for 10.2.0.2 Lists the status of Oracle patch sets and interim patches for 10.2.0.4 Describes the current Oracle security fixes
1137346 850306 134592 834917 819829 839182 306408 868681
OPatch: Oracle tool for patch installation Oracle Database 10g: Database Release Check
Describes how to update the SAPDBA role after the upgrade Describes the new SAPCONN role, which replaces the native CONNECT role from Oracle Required for upgrading Oracle client software to Oracle Database 10g Release 2 (10.2) Describes how to use OPatch with Oracle Database 10g Release 2 (10.2) Describes how to install an Oracle patch with OPatch Describes some additional transports to be applied to SAP systems 640 and below before upgrade to Oracle database 10g
1.3 More Information on SAP Service Marketplace You can find more information as following on SAP Service Marketplace: Description
Internet Address
Title
SAP Notes Oracle Database Administration
http://service.sap.com/notes
None SAP Database Guide: Oracle
SAP Software Distribution Center Oracle Database Upgrade Guide – that is, the guide you are now reading Oracle upgrade documentation in Oracle Metalink or My Oracle Support
2009-08-25
www.sdn.sap.com/irj/sdn/
SAP ON ORACLE KNOWLEDGE CENTER Documentation ora
SAP
http://service.sap.com/swdc
http://service.sap.com/ instguides
None Upgrade to Oracle Database <Version>: UNIX
Database Upgrades
Oracle http://download.oracle.com /docs/cd/B19306_01/server.
Upgrade: Oracle Database Upgrade Guide 10g Release 2 (10.2)
102/b14238/toc.htm http://metalink.oracle.com
PUBLIC
#mãL±Ú 10g Upgrade Companion Document ID: 466181.1 #mãL±Ú Complete Checklist for Manual Upgrades to 10gR2 Document ID: 316889.1
7/48
1
Introduction
1.3
More Information on SAP Service Marketplace
Description
Oracle Technology Network (OTN) forum
Internet Address
Title
http://forums.oracle.com/
N â&#x20AC;&#x161;]â&#x201E;˘% Complete checklist for manual upgrades of Oracle databases from any version to any version on any platform Document ID: 421191.1 None
forums/forum.jspa? forumID=583&start=0
8/48
PUBLIC
2009-08-25
2
Planning
2.1
Checking the Original Version of Your Database
2 Planning
RECOMMENDATION
Before the production upgrade, make sure that you perform a test upgrade on your backup system, either with database upgrade assistant (DBUA) (recommended) or manually. 1. 2. 3. 4.
You check the original version of your database [page 9]. You check the hardware and software requirements [page 10]. You review the Oracle-specified kernel parameters and shell limits [page 11]. You check additional requirements for the upgrade [page 11].
2.1 Checking the Original Version of Your Database You need to check the original version of the database you want to upgrade. CAUTION
This SAP upgrade documentation only covers the standard upgrade from Oracle 9.2.0.4 or later to Oracle Database 10g Release 2 (10.2) using the Oracle Database Upgrade Assistant (DBUA). Process
In the following special cases you need to obtain more information: !©!„a If you are upgrading from Oracle 8.1.7 or an earlier release, read the Oracle Database 10g Release 2 (10.2) upgrade documentation for information on the special steps required. Although Oracle supports direct upgrades from Oracle 8.1.7 to Oracle 10.2.0, we recommend customers running Oracle 8.1.7 to first upgrade to Oracle 9.2.0 and then to Oracle 10.2.0. !©!„a If you are upgrading from Oracle 9.2.0 to Oracle Database 10g Release 2 (10.2) in manual mode. !©!„a If the source database runs Oracle 9.2.0.3, 9.2.0.2, or 9.2.0.1, you need to update the source database to patch set 9.2.0.4 or later. The DBUA checks for the source release of the Oracle 9.2 database. If the source database runs on a lower version than Oracle 9.2.0.4 you cannot proceed. For more information in these special cases, see the documentation for the Oracle Database 10g Release 2 (10.2) upgrade at the Oracle website. RECOMMENDATION
If the source database is Oracle 10.1 we strongly recommend that it is at least version Oracle 10.1.0.4.
2009-08-25
PUBLIC
9/48
2
Planning
2.2
Checking Hardware and Software Requirements
2.2 Checking Hardware and Software Requirements You need to check that you meet the hardware and software requirements for running the new Oracle release. The complete list of hardware and software requirements for every platform is included in the Oracle documentation. CAUTION
To make sure that the checks complete successfully, you must complete this procedure before running the Oracle Universal Installer [page 24]. Prerequisites
You can access the complete Oracle documentation referred to below as a member of the Oracle Technology Network (OTN). Procedure
1.
2.
Note the following general hardware requirements: ¥ØÏ oR At least 1024 MB of physical RAM ¥ØÏ oR About 500 MB free space in the /tmp directory ¥ØÏ oR At least 10 GB for the Oracle Home directory, consisting of: ¥ØÏ o= 3 to 5 GB for the Oracle software ¥ØÏ o= About 5 GB for the patch information stored by OPATCH tool This high space requirement is necessary due to the large number of patches that must be applied on top of any given Oracle patch set. Check that your operating system meets the software requirements for running the new Oracle release, including all required patches. You might need to upgrade your operating system before you start. The complete list of software requirements for every operating system is included in the Oracle documentation. RECOMMENDATION
3.
If you have access to Oracle Metalink we strongly recommend that you read document 169706.1. This document provides information on all operating system prerequisites and is regularly updated. Obtain the full and updated list of hardware and software requirements from the relevant Oracle database installation guide for your operating system, which you can find at the Oracle website. Select the appropriate documentation for Oracle Database 10g Release 2 (10.2). CAUTION
If your database resides on Network Attached Storage (NAS) you need to review and implement the Oracle NAS guidelines. You need to mount network file systems with specific mount options, which you can find in the Oracle installation guide.
10/48
PUBLIC
2009-08-25
2
Planning
2.3
Reviewing the Oracle-Specified Kernel Parameters and Shell Limits
2.3 Reviewing the Oracle-Specified Kernel Parameters and Shell Limits You need to review the Oracle-recommended kernel parameters and shell limits for your operating system with Oracle Database 10g Release 2 (10.2). These are only recommendations from Oracle for optimizing the system performance in production environments. If the recommended settings are not suitable for your system you must tune the kernel parameters accordingly. Procedure
Obtain the recommended shell limits and kernel parameters from the relevant Oracle database installation guide for your operating system, which you can find at: www.oracle.com/technology/documentation
Select the appropriate documentation for Oracle Database 10g Release 2 (10.2).
2.4 Checking Additional Requirements for the Upgrade You need to check the additional requirements for the Oracle database upgrade as described in this section. Procedure
1.
Make sure you have read the SAP Notes for the upgrade [page 6], which you can find at http://service.sap.com/notes
2.
3.
Make sure your operating system and initial database version meets SAP requirements. We approve specific combinations of operating system version, database version, SAP release, and SAP kernel release: µÈk Ãè SAP Release 4.6x, see SAP Note 156548 µÈk Ãè SAP Release 6.x, see SAP Note 407314 To upgrade from a remote PC, you need X-Windows software on the PC, as described in SAP Note 432861. RECOMMENDATION
4.
In some situations the OUI and DBUA screens are not displayed correctly when started remotely. In such cases we recommend you to start the OUI and the DBUA directly from the console. Download the Oracle Database 10g Release 2 (10.2) installation guide for your operating system from the Oracle Technology Network (OTN). You need this document to review the hardware and software requirements and to configure the kernel parameters and shell limits.
2009-08-25
PUBLIC
11/48
2
Planning
2.4
Checking Additional Requirements for the Upgrade RECOMMENDATION
5.
If you have access to Oracle Metalink we strongly recommend that you read document 169706.1. This document provides information on all operating system prerequisites and is regularly updated. Download the Oracle Database 10g Release 2 (10.2) software and the latest patch sets and required patches or patch collection. The list of patches is described in SAP Notes 1137346 and 1137346. You can download the patches from: http://service.sap.com/swcenter-3pmain CAUTION
6.
PfiÄ %Ì The patches listed in SAP Note 1137346 are mandatory. To avoid severe database problems, make sure that you install all these patches. PfiÄ %Ì SAP certifies Oracle 10.2 only from release 10.2.0.2. SAP does not certify nor support Oracle 10.2.0.1. Make sure that your target release is Oracle 10.2.0.2 or later. Download the latest version of the Oracle 10.2 Instant Client software from: http://service.sap.com/swcenter-3pmain
7.
Download the latest version of the DBATOOLS (BR*Tools) to be used immediately after the database upgrade from: http://service.sap.com/swdc
12/48
PUBLIC
2009-08-25
3
Preparation
3.1
Checking the Correct UNIX Users, Groups, and Authorizations
3 Preparation
You have to complete the following preparations: 1. You check the correct UNIX users, groups, and authorizations [page 13]. 2. You check the directory structure [page 14]. 3. You run the pre-upgrade script [page 15]. 4. You check the prerequisites for the Oracle Universal Installer [page 16]. 5. You check the SAP System prerequisites [page 17]. 6. If required, you migrate to automatic undo management [page 18]. 7. If required, you stop Statspack reports [page 18]. 8. You check the SYSTEM and SYSAUX tablespace for freespace [page 19]. 9. If required, you check for invalid database objects [page 19]. 10. You install the Oracle Instant Client [page 20].
3.1 Checking the Correct UNIX Users, Groups, and Authorizations You need to check that the ora<dbsid> user has write authorization for the /oracle directory, since the ora<dbsid> user performs the database installation. Procedure
1.
Enter the following commands: touch /oracle/write_test rm /oracle/write_test
If the user ora<dbsid> does not have write authorization, log on to your system with the user root and enter the command: chgrp dba /oracle chmod 775 /oracle
2.
Check if you are able to start an XTERM as the Oracle user since this is the user who starts the OUI. Enter the following command with the user ora<dbsid>: umask 022
2009-08-25
PUBLIC
13/48
3
Preparation
3.2
Checking the Directory Structure
3.2 Checking the Directory Structure You need to verify the availability and correctness of the following Oracle directories: ØÖ^é5² stage directory ØÖ^é5² Oracle inventory directory ØÖ^é5² Home directory Procedure
1.
Check the Oracle stage directory, usually called /oracle/stage. If this directory does not exist, create it manually. If it already exists it might contain software stages from previous installations or upgrades. 1. For the upgrade to Oracle Database 10g Release 2 (10.2) create the staging directory /oracle/ stage/102_64. 2. Make sure that you have around 2 GB free space for the SAR files. To extract all RDBMS SAR files requires around 5 GB of free space in the staging directory but for this upgrade you only require the SAR file containing the database component. You can find the SAR file in OR110264.SAR for 64-bit platforms or OR110232.SAR for 32-bit platforms. If there is not enough space, you can delete previous stage directories. 3. When the RDBMS CDs have been mounted, use the SAP tool SAPCAR to extract all the RDBMS CDs to /oracle/stage/102_64 as user ora<sid>. For example, the following command extracts a single CD: SAPCAR –xvf OR110264.SAR
After you have finished the extraction of all the RDBMS CDs, the following subdirectories exist under /oracle/stage/102_64: ØÖ^é5² ØÖ^é5² ØÖ^é5² ØÖ^é5² ØÖ^é5²
database client clusterware companion gateways NOTE
4.
14/48
For some platforms Disk1 and Disk2 might be created as subdirectories of database, client, clusterware, companion, and gateways. The gateways subdirectory is not created for the following platforms: ØÖ^é5² Linux on Power ØÖ^é5² HP_UX on Itanium ØÖ^é5² Solaris x86_64 After extraction of the Oracle software to /oracle/stage/102_64 do the following: 1. Rename the original SAP folder by performing one of the following:
PUBLIC
2009-08-25
3
Preparation
3.3
Running the Pre-Upgrade Script
™8Ó*è”
mv /oracle/stage/102_64/database/SAP /oracle/stage/102_64/database/ SAP_ORIG
™8Ó*è”
mv /oracle/stage/102_64/database//Disk1/SAP /oracle/stage/102_64/ database//Disk1/SAP_ORIG
2.
3.
Download the file RDBMS_SAP_32.zip (for 32-bit platforms) or RDBMS_SAP_64.zip (for 64bit platforms) attached to SAP Note 819830 and copy it to a temporary location such as /tmp. Extract the zip file by performing one of the following for 64-bit platforms (replace “64” with “32” for 32-bit platforms): ™8Ó*è”
cd /oracle/stage/102_64/database unzip /tmp/RDBMS_SAP_64.zip
™8Ó*è”
cd /oracle/stage/102_64/database/Disk1 unzip /tmp/RDBMS_SAP_64.zip
2.
You now see the directory SAP extracted with the updated version of SAP-specific files. Check the Oracle inventory directory. The Oracle inventory directory maintains the inventory of all Oracle software installed on the system. The path to the Oracle inventory directory is mentioned in the file oraInst.loc, which you can find under /var/opt/oracle or under /etc. One of the entries of oraInst.loc or inventory_location points to the location of the Oracle inventory. When you execute the OUI for the first time on the system, the OUI prompts you for the path to the inventory directory. The default location for the Oracle inventory is $ORACLE_BASE/ oraInventory. NOTE
3.
This applies only to systems where the OUI has been executed for the first time. The OUI automatically creates theoraInst.loc and the inventory directory. You do not need to create these directories manually. Create the empty Oracle home directory before starting the OUI. You need to create the Oracle home directory before you can start the Oracle software installation. The Oracle Home directory is normally /oracle/<DBSID>/102_64.
3.3 Running the Pre-Upgrade Script You run the Oracle pre-upgrade information tool. This tool provides information on the existing preupgrade database. It also suggests any changes that you need to make before you start the upgrade. NOTE
You always execute this script as the ora<dbsid> user connected to the database as sysdba in the Oracle 9i environment.
2009-08-25
PUBLIC
15/48
3
Preparation
3.4
Checking the Prerequisites for the Oracle Universal Installer
Prerequisites
You are logged on as user ora<dbsid> in the Oracle 9i environment with the database also started up. For more information about how to extract the script from the Oracle 10.2.0.4 patchset software without installing the patchset software, see SAP Note 1237838. Procedure
Execute the following commands: sqlplus /nolog SQL> connect / as sysdba SQL> spool /tmp/pre_upgrade.log SQL> @/oracle/stage/102_64/database/SAP/utlu102i.sql
or: SQL> @/oracle/stage/102_64/database/Disk1/SAP/utlu102i.sql SQL> spool off SQL> exit
Result
You can check the results of the pre-upgrade script by looking at the log file /tmp/pre_upgrade.log. CAUTION
Make the changes listed in the log file, otherwise you might have problems during the upgrade. If the log file from the pre-upgrade script reports stale optimizer statistics for the Oracle 9.2 database, you need to execute the script gather_optimizer_statistics.sql attached to SAP Note 819830. This applies only to the Oracle 9.2 database.
3.4 Checking the Prerequisites for the Oracle Universal Installer You must check the prerequisites for the Oracle Universal Installer (OUI). Procedure
1. 2.
Log on as the Oracle user ora<dbsid>. Execute the following commands: ˙Fµàš† 32-bit platforms: cd /oracle/stage/102_32/database ./runInstaller –executeSysPrereqs
˙Fµàš† 64-bit platforms, one of the following: ˙Fµàšî cd /oracle/stage/102_64/database ./runInstaller –executeSysPrereqs
16/48
PUBLIC
2009-08-25
3
Preparation
3.5
Checking the SAP System Prerequisites
x�’¯½
cd /oracle/stage/102_64/database/Disk1 ./runInstaller –executeSysPrereqs
If the OUI complains that the operating system version is not certified or supported, you can ignore this. If OUI reports missing OS patches, you need to apply these before you can continue.
3.5 Checking the SAP System Prerequisites You must check the prerequisites for the SAP system (ABAP) release 6.40 and lower. You need to: 1. Update the database library (dbsl) to the latest patch level 2. Apply a correction to the ABAP system This is necessary to make the SAP system compatible for the Oracle Database 10g release checks. 3. If the SAP kernel uses the Oracle 9.2 client software (this is the case if you use the 640 or EXT kernels), you also need to update the Oracle client software to at least release 9.2.0.7. If you do not update the Oracle 9.2 client software, core dumps in the SAP system after the upgrade to Oracle Database 10g. 4. You need to execute an SQL script that creates a new role on the database. This is necessary due to changes to the Oracle CONNECT role in Oracle 10.2. 5. You must upgrade Java systems to at least Service Pack 13 before you can upgrade to Oracle Database 10g. Procedure
1.
Download the latest version of dbsl (dboraslib.so, dboraslib.sl, or dboraslib.o) for your release from: http://service.sap.com/swdc
2.
Check the level of your Basis support package using this table: SAP Release (SAP_BASIS)
Basis Support Package Level
46B 46C 46D 6.10 6.20 6.40
SAPKB46B57 SAPKB46C48 SAPKB46D38 SAPKB61041 SAPKB62044 SAPKB64009
x�’¯½x If the level of your Basis support package is higher than or equal to that shown above, no additional corrections are necessary. x�’¯½x If the level of your Basis support package is lower than the one shown in the table above, you need to apply an additional transport correction to your system as described in SAP Note 868681.
2009-08-25
PUBLIC
17/48
3
Preparation
3.6
Migrating to Automatic Undo Management
3.
Download the latest version of the Oracle Client software â&#x20AC;&#x201C; OCL92064.SAR or OCL92032.SAR â&#x20AC;&#x201C; from: http://service.sap.com/swcenter-3pmain
This is described in SAP Note 886783. Make sure that you install the newest version of the Oracle client software on all application servers, including the database server if there is an SAP application running on the database server. NOTE
4.
If you cannot update the client software because there are several other application servers running on the same host, see SAP Note 964783. Execute the SQL script sapconn_role.sql as follows: cp /oracle/stage/102_64/database/SAP/sapconn_role.sql $ORACLE_HOME/dbs
or: cp /oracle/stage/102_64/database/Disk1/SAP/sapconn_role.sql $ORACLE_HOME/dbs cd $ORACLE_HOME/dbs sqlplus /nolog @sapconn_role
3.6 Migrating to Automatic Undo Management This step is only relevant if your database still uses manual undo management (rollback tablespace and rollback segments). If your database still uses rollback segments for undo management we strongly recommend you to migrate to automatic undo management before starting the database update to Oracle database 10g. Otherwise you might run into errors. Procedure
1. 2.
Read SAP Note 600141, which is the central note describing automatic undo management. This note also gives you an overview of the concepts involved. Follow the step-by-step instructions in the note to migrate to automatic undo management.
3.7 Stopping Statspack Reports This step deletes the Statspack jobs with DBMS_JOB.REMOVE. Prerequisites
This step is only relevant if the Statspack package has been activated on the database for monitoring purposes. For more information about Statspack, see SAP Note 717484. Procedure
1.
Log on as the user under which the statspack jobs run (usually PERFSTAT):
18/48
PUBLIC
2009-08-25
3
Preparation
3.8
Checking the SYSTEM and SYSAUX Tablespace for Freespace SQL> connect PERFSTAT/<pwd> SQL> select job, what from user_jobs;
2.
This displays a list of the jobs that are currently entered under the user PERFSTAT. Delete all jobs with the print job number <jobnr>: SQL> connect PERFSTAT/<pwd> SQL> execute dbms_job.remove( <jobnr> );
3.8 Checking the SYSTEM and SYSAUX Tablespace for Freespace You need to make sure that the SYSTEM and SYSAUX tablespaces have at least 750 MB freespace. This is necessary due to a bug in the Oracle database that can cause the Oracle Database Upgrade Assistant (DBUA) to underestimate the required freespace. NOTE
The SYSAUX tablespace is available only if the source database is already Oracle 10.1. If your source database is Oracle 9.2, there is no SYSAUX tablespace. In this case, you can ignore references to the SYSAUX tablespace in this section. Procedure
Check if the SYSTEM or SYSAUX tablespace have enough freespace. You can check this by executing one of the following commands as the ora<dbsid> user: 4¼Ý˚¡© brspace –f dbshow –c tsinfo –s SYSTEM 4¼Ý˚¡© brspace –f dbshow –c tsinfo –s SYSAUX If the free space is less than 750 MB, use your preferred database administration tool to increase the size by using one of the following options: 4¼Ý˚¡© Setting the AUTOEXTEND option for the existing datafile to ON. 4¼Ý˚¡© Adding an additional datafile. 4¼Ý˚¡© Resizing the existing datafile. NOTE
For systems that use raw devices for the datafiles, the AUTOEXTEND option might not work because of the fixed size of the raw devices. In this case you might need to add another datafile by adding a new volume or partition on the operating system.
3.9 Checking for Invalid Database Objects This optional step lets you check if there are any invalid database objects before the database upgrade to Oracle database 10g starts. After the upgrade it helps you distinguish database objects that have become invalid due to the upgrade process from those that were already invalid to start with.
2009-08-25
PUBLIC
19/48
3
Preparation
3.10
Installing the Oracle Instant Client
Procedure
1.
Execute the following commands: SQL> spool invalid_objects SQL> select unique object_name, object_type, owner from dba_objects where status = 'INVALID'; SQL> @?/rdbms/admin/utlrp.sql SQL> select unique object_name, object_type, owner from dba_objects where status = 'INVALID'; SQL> spool off
2.
A list of invalid objects before the upgrade is now generated. Check the list of invalid objects after the upgrade. If any objects in the list from before the upgrade are also in the list of invalid objects after the upgrade, you can be sure that this is not due to the upgrade process. RECOMMENDATION
If possible, delete or compile any invalid objects before the upgrade. CAUTION
If there is a table called PLAN_TABLE either in the SYS or SYSTEM schema, you must drop it with the following commands before starting the database upgrade: SQL> drop table "SYS"."PLAN_TABLE"; SQL> drop table "SYSTEM"."PLAN_TABLE";
3.10 Installing the Oracle Instant Client You have to extract the Oracle Instant Client software. This is necessary if the JDBC driver location [page 41] refers to the Oracle Instant Client directory, rather than to the Oracle home directory. The Instant Client is also needed for BR*TOOLS Release 700, which you install during the post-upgrade phase. Procedure
Install the Oracle Database 10g Instant Client for UNIX as described in SAP Note 819829.
20/48
PUBLIC
2009-08-25
4
Oracle Database Upgrade
4.1
Database Software Installation
4 Oracle Database Upgrade
This section describes how to upgrade the Oracle database. Prerequisites
You have completed the following: G�U" Planning [page 9] G�U" Preparations [page 13] Process Flow
You install the database software [page 21]. You upgrade the database structure [page 29]. Result
You have completed the upgrade. Now perform the post-upgrade steps [page 21].
4.1 Database Software Installation As part of the Oracle database upgrade [page 21] you upgrade the software. NOTE
You can upgrade the database software while the SAP system is still running with the existing database (that is, Oracle 8.1.7 or Oracle 9.2). Therefore, to reduce downtime you can perform the following steps before you stop your system. The exception to this is for AIX where you need to run an additional script as the root user, as described in Adapting the AIX Kernel (AIX only) [page 24]. You need to shut down all Oracle instances on the host before running this script. Process Flow
1. 2. 3.
You check and set the environment variables [page 22]. You back up the Oracle inventory [page 23]. G�º Ă }¼²y [G?*â&#x20AC;&#x2122;ďż˝ Ă?ŸÍĂ&#x161;ĂŠV!NgĂŽĂ&#x201C;HXĂŤ~ĂŤÂŞĂĽĂł +Ăązb
You perform steps for the AIX operating system [page 24]. G�° Ă }�² G/*Ă&#x2039;ďż˝EĂ?°Ă&#x2020;Ă&#x161;â&#x20AC;&#x161;VçNt
4. 5. 6. 7.
You run the Oracle Universal Installer [page 24]. You install the current patch set [page 26]. You install required interim patches [page 27]. You copy and adapt the old Oracle SQL*Net files [page 27].
2009-08-25
PUBLIC
21/48
4
Oracle Database Upgrade
4.1
Database Software Installation
8. 9.
You back up the Oracle database [page 28]. You shut down the SAP system and Oracle listener process [page 29].
4.1.1 Checking and Setting the Environment Variables To install the database software [page 21], you need to check and set the environment variables of user ora<dbsid> because this user installs the Oracle software. NOTE
For more information about changes to the environment of the SAP user <sapsid>adm, see Changing the Environment for the <sapsid>adm User [page 40]. Prerequisites
You set the environment variables below by editing the files .dbenv_<host>.sh and .dbenv_<host>.csh in the home directory of ora<dbsid>. CAUTION
Do not make the changes to the environment permanent as long as the old database is still running. You make them permanent in the post-upgrade phase. We recommend you to back up the old environment files before making the changes permanent. Procedure
1.
Make sure the following environment variables are not set:
2.
;ã|uóa TWO_TASK ;ã|uóa ORA_NLS ;ã|uóa ORA_NLS32 ;ã|uóa ORA_NLS33 Set the following environment variables: Environment Variable
Value
DISPLAY
<hostname>:0.0
NOTE <hostname>:0.0 is the host on which the Oracle Universal Installer (OUI) is to be displayed. ORACLE_BASE
/oracle
ORACLE_SID
<DBSID>
ORACLE_HOME
One of the following values: /oracle/<DBSID>/102_32 /oracle/<DBSID>/102_64
NLS_LANG
22/48
Set this to the output of the script CHECKS.SQL, which you can find in one of the following: ;ã|uóa 64-bit platforms
PUBLIC
2009-08-25
4
Oracle Database Upgrade
4.1
Database Software Installation Environment Variable
Value /oracle/stage/102_64/database/Disk1/SAP
or /oracle/stage/102_64/database/SAP
Í −ʼ< 32-bit platforms /oracle/stage/102_32/database/SAP
NOTE
The database must be open before you execute the script CHECKS.SQL. ORA_NLS10
$ORACLE_HOME/nls/data
SAPDATA_HOME
/oracle/<DBSID>
The setting of the DISPLAY environment variable is described in SAP Note 432861. To make sure that the OUI screen can be displayed correctly on your system, you might have to start an X terminal (xterm) session and run the command: $ xhost +
3.
4.
Set the corresponding environment variable for the library path: Operating System
Environment Variable
Value
AIX Solaris, HP Tru64 UNIX, Linux HP-UX
LIBPATH
$ORACLE_HOME/lib:$LIBPATH
LD_LIBRARY_PATH
$ORACLE_HOME/lib:$LD_LIBRARY_PATH
SHLIB_PATH
$ORACLE_HOME/lib:$SHLIB_PATH
This makes sure that dynamic libraries are loaded first from $ORACLE_HOME/lib. Include $ORACLE_HOME/bin in your PATH or path variable, where $ORACLE_HOME is the variable that you set in step 2 above. NOTE
5.
Make sure there is only one $ORACLE_HOME/bin in your PATH or path variable. Make sure that the path variable does not contain the old $ORACLE_HOME/bin. Check if the temporary directory (usually /tmp) has at least 400 MB of free space. If not, set up the TEMP or TMPDIR environment variables to specify a temporary directory on the filesystem. RECOMMENDATION
You can check the correctness of the new environment with the UNIX env command. Or you can run the UNIX umask command and check that the returned value is 22.
4.1.2 Backing Up the Oracle Inventory Before you install the database software [page 21] you need to back up the Oracle inventory. Procedure
1.
If the Oracle inventory exists, check its location by looking at the entry in one of the following files:
2009-08-25
PUBLIC
23/48
4
Oracle Database Upgrade
4.1
Database Software Installation
‡NTeZŁ /var/opt/oracle/oraInst.loc ‡NTeZŁ /etc/oraInst.loc The location is shown as follows: inventory_loc=<path to Oracle inventory>
2.
Make a backup of your existing Oracle inventory before you start the Oracle Database 10g Release 2 (10.2) software installation.
‡NT−�[łZÝ(‘Ý‚'sÀÖ-é<"D±k KL1Ö?rò<˙˛flÎ…Ël•zA
4.1.3 Performing Steps for the AIX Operating System To install the database software [page 21] on the AIX operating system, you need to run the rootpre.sh script to adapt the AIX kernel and also execute a command as the root user. Prerequisites
If several Oracle instances run on one computer, you must shut these down before adapting the kernel. Procedure
1.
Run the rootpre.sh script as follows: 1. Log on to the system with user ora<dbsid> if you are not already logged on. 2. Change to the directory /oracle/stage/102_64/database/Disk1/rootpre using the following command: cd /oracle/stage/102_64/database/Disk1/rootpre
3.
Make sure that the user root is assigned the environment of ora<dbsid>: su root
4.
Call the script rootpre.sh: ./rootpre.sh
5.
Log off with the user root: exit
2.
Remove any currently unused modules in kernel and library memory by entering the following command as user root: # /usr/sbin/slibclean
‡NT•�[łRÝq‘™‚7słÖaé "i± ÕK_
4.1.4 Running the Oracle Universal Installer To install the database software [page 21] you run the Oracle Universal Installer (OUI). Procedure
1.
Log on as user ora<dbsid>.
24/48
PUBLIC
2009-08-25
4
Oracle Database Upgrade
4.1
Database Software Installation
2.
3.
Since you are already logged on as user root, you can switch to user ora<dbsid> by entering the following command: su – ora<dbsid>. If you install Oracle database software with Release 10.2.0.1 or 10.2.0.x on a new operating system or a new operating system version, the Oracle Universal Installer might not yet recognize or support this operating system. Follow the instructions in SAP Note 980426. Make sure that the DISPLAY environment variable is set to <host_name>:0.0, where <host_name> is the host on which you want to display the GUI of the Oracle Universal Installer (OUI). Shell Used
Command
Bourne shell (sh)
DISPLAY=<host_name>:0.0 export DISPLAY
C shell (csh) Korn shell (ksh)
4.
setenv DISPLAY <host_name>:0.0 export DISPLAY=<host_name>:0.0
Start the OUI with the user ora<dbsid> as follows: C¿y¨ƒV For 32-bit systems, enter the following: cd /oracle/stage/102_32/database/SAP ./RUNINSTALLER
C¿y¨ƒV For 64-bit systems, enter one of the following: C¿y¨ƒ9 cd /oracle/stage/102_64/database/Disk1/SAP ./RUNINSTALLER
C¿y¨ƒ9
cd /oracle/stage/102_64/database/SAP ./RUNINSTALLER
5.
You see a message that a response file is being generated. It might take several minutes before you see the OUI screen. Respond to the OUI as follows: Prompt or Condition
Action
When you run the OUI for the first time on this host, a dialog box, Specify File Locations Destination..., appears. This dialog box proposes the inventory location as / oracle/oraInventory and the installation group as dba. Available Product Components Product-Specific Prerequisite Checks This phase checks if all necessary requirements for installing and running the database have been met.
Accept the OUI proposal and continue by choosing Next.
Java Development Kit (JDK)
2009-08-25
Confirm the default selections by choosing Next. For items that are flagged as warnings or failed, review the cause for the warning or failure on screen and fix the problem if possible. Alternatively you can verify the items manually and confirm them by clicking the checkbox. You can find details about each check by clicking on the relevant item. HP Tru64: Enter the location of the JDK.
PUBLIC
25/48
4
Oracle Database Upgrade
4.1
Database Software Installation Prompt or Condition
Action
Summary page
Check the information on this page and then start the installation. Execute the file $ORACLE_HOME/root.sh with the user root, and confirm the dialog box by choosing OK. If this is the first time that the Oracle software has been installed on this host, the OUI also asks you to execute a second script, /oracle/oraInventory/ orainstRoot.sh, as the root user. Execute this script as well. Continue by choosing Next.
When the Install step has completed, a dialog box appears.
6.
7.
At the end of the installation, in case there are any Configuration Assistants that have been started automatically (for example, Oracle Net) choose Cancel and terminate the Net Config Assistant. You can ignore messages that some of the config assistants failed to complete successfully. The Installer finishes, reporting that the Oracle installation was successful. It also informs you about the services that it started. You can find the port numbers for these services in the $ORACLE_HOME/install/portlist.ini file. To exit the OUI, choose Exit and confirm the dialog box that appears. NOTE
You can now access the Oracle 10.2 online documentation, which was installed during the last step. You can find the entry point to the Oracle online documentation at $ORACLE_BASE/ doc/index.htm.
4.1.5 Installing the Current Patch Set After the database software installation [page 21], you need to install the current Oracle Database 10g Release 2 (10.2) patch set. Prerequisites
eEž¢ÿ„ For more information on the latest patch set available for Oracle 10.2 see SAP Note 839187. eEž¢ÿ„ For more information about how to install the patch set, see the patch set README file. CAUTION
Do not perform any of the post-installation steps mentioned in the patch set README file. The post-installation steps are to be performed only on an existing Oracle 10.2 database. At this stage you have only installed the Oracle 10.2 software. The database itself is still not Oracle 10.2. Therefore, make sure that you do not perform the post-installation steps mentioned in the README file. eEž¢ÿ„ You only have to install the latest (that is, the current) patch set. Procedure
1.
Log on at the operating system level with the ora<dbsid> user.
26/48
PUBLIC
2009-08-25
4
Oracle Database Upgrade
4.1
Database Software Installation
2.
Install the patch set as described on the patch set README file. For more information, see SAP Note 839187.
4.1.6 Installing Required Interim Patches After the database software installation [page 21], you need to install required interim patches, using the Oracle tool OPatch. You need these interim patches in addition to the current patch set. RECOMMENDATION
You can install all the required interim patches in a single step using the Oracle tool MOPatch, which you can find at SAP Note 1027012. MOPatch can also download patches directly from SAP Service Marketplace and check for any potential patch conflicts. Prerequisites
kê#�Vg Make sure you have already installed the current patch set [page 26]. kê#�Vg Check SAP Notes 871096 and 1137346 to find the list of required patches to be installed. kê#�Vg Check SAP Note 839182 for instructions on how to use OPatch. Procedure
1. 2.
Log on at the operating system level as the ora<dbsid> user. Install the patches, following the instructions in SAP Note 839182. NOTE
3.
You can apply the patches in any order. We recommend that you first copy the patches to a directory called ora_patches in $ORACLE_HOME. After all the patches have been successfully applied, you can query the status with the following command: $ORACLE_HOME/OPatch/opatch lsinventory
This command lists all the patches that have been applied to the software installation.
4.1.7 Copying and Adapting the SQL*Net Files After the database software installation, you must copy and modify the old SQL*Net files, that is, listener.ora, sqlnet.ora, and tnsnames.ora. Procedure
1. 2.
Log on as user ora<dbsid>. If ora<dbsid> has environment variable TNS_ADMIN set, do the following:
2009-08-25
PUBLIC
27/48
4
Oracle Database Upgrade
4.1
Database Software Installation
1.
3.
4.
Choose a new location for the new SQL*Net parameter files and set TNS_ADMIN to point to the new location <new_TNS_ADMIN>. 2. Copy the SQL*Net parameter files from the old location <old_TNS_ADMIN> to <new_TNS_ADMIN>. 3. Edit the new SQL*Net files by adapting all file paths for the new directory. Be sure to adapt the value of ORACLE_HOME in the listener.ora file. If ora<dbsid> has not set the TNS_ADMIN environment variable, Oracle first searches in /etc, in $ORACLE_HOME/network/admin for the SQL*Net parameter files. Choose which of the following applies to your installation: Ð Bàcx The SQL*Net parameter files are located in directory /etc: 1. Make a backup copy of the files. 2. Edit the new SQL*Net files by adapting all file paths for the new directory. Be sure to adapt the value of ORACLE_HOME in the listener.ora file. Ð Bàcx The SQL*Net parameter files are located in <old_ORACLE_HOME>/network/admin: 1. Copy the SQL*Net parameter files from <old_ORACLE_HOME> to <new_ORACLE_HOME>. 2. Edit the new SQL*Net files by adapting all file paths for the new directory. Be sure to adapt the value of ORACLE_HOME in the listener.ora file. Since your database is still running in the old environment, do not start the listener with the new listener.ora file at this point.
4.1.8 Backing Up the Oracle Database You must have a complete and usable database backup otherwise you might lose data. We recommend you to back up all your Oracle 9i archive logs before you start the upgrade. The upgrade changes the parameter log_archive_format to 10.2.0. After the upgrade has completed BRARCHIVE cannot back up archive files from before the upgrade (that is, from Oracle 9i or earlier) because of this change to log_archive_format. Procedure
1.
Create a complete database backup and back up any archive logs from Oracle 9i. RECOMMENDATION
Before backing up the archive logs, switch the log files with the following SQL command: alert system switch logfile
2. 3.
Make sure that you do a log file switch for all online redo log files. Check that the backup is usable. If for any reason you have problems during the upgrade you must be able to restore the database from this backup. If you want to separate the alert log file of Oracle 9i from that of Oracle Database 10g Release 2 (10.2), you can move the alert log file to a different name with the following command:
28/48
PUBLIC
2009-08-25
4
Oracle Database Upgrade
4.2
Database Structure Upgrade cd /oracle/<DBSID>/saptrace/background mv alert_<SID>.log alert_<SID>.log-SV-9.2.0
4.1.9 Shutting Down the SAP System and Oracle Listener Process You need to shut down the SAP system and the Oracle listener running process running in the old ORACLE_HOME, for example, in /oracle/<DBSID>/920_64. Procedure
1.
Stop the SAP application server by entering the following command as user <sapsid>adm: stopsap r3
2.
Stop the Oracle listener by entering the following command as user ora<dbsid>: lsnrctl stop NOTE
Make sure that processes that log on to the database, such as CRON jobs, are not active during the upgrade. Make sure that you reschedule these processes when the upgrade has finished.
4.2 Database Structure Upgrade As part of the Oracle database upgrade [page 21] you upgrade the database structure. Prerequisites
You have installed the database software [page 21]. Process Flow
1. 2.
You check the oratab entry [page 29]. You start the Database Upgrade Assistant to perform the upgrade [page 30].
Result
Now continue with the Post-Upgrade Steps [page 33].
4.2.1 Checking the oratab Entry To upgrade the database structure [page 29], you need to check the entry for the oratab file. Prerequisites
You can find the oratab file as follows:
2009-08-25
PUBLIC
29/48
4
Oracle Database Upgrade
4.2
Database Structure Upgrade
¾ ¾½vÔ
¾ ¾RSˆk¨ãj7õm—ä¿•tåèOí$łµŽÅèsá»ú JæWr勘[u&Ÿûôô=fí ƒ bß|Èáu ˙‡ÑÙiŠz¡ÜR?5µ˘¬˝¹ýƒ 9mÊì¦"’⁄ˇrÛ‚Í
/etc ¾ ¾XSˆk€ã37ºmflää•8åÀOÀ$ãµÄÅÏsûà aJÕWNåæ˜TuNŸþôı={í&ƒDb¡|¬áx ˙flÑ«i…zóÜt? µM¬é¹Ù
¾ ¾½vÔ
¾ ¾RSˆk¨ãj7õm—ä¿•tåèOí$łµŽÅèsá»ú JôWT弘 u˝ŸÂô§=™í
/var/opt/oracle ¾ ¾XSˆk€ã37ºmflää•8åÒOæ$×µžÅõsú»³ ŁJÛ
Procedure
1.
Make sure that the oratab file contains the following entry: <DBSID>:<old_ORACLE_HOME>:N
Where old_ORACLE_HOME stands for the path to the old oracle software installation. EXAMPLE
2.
The entry for a system with a <DBSID> equal to C11 is as follows: C11:/oracle/C11/920_64:N. If this entry does not exist, insert it using a text editor.
4.2.2 Starting the Database Upgrade Assistant To upgrade the database structure [page 29] you need to start the Oracle Database Upgrade Assistant (DBUA). The DBUA tool is a graphical tool that leads you step by step through the upgrade. Prerequisites CAUTION
Make sure that you start the DBUA in the Oracle 10.2 user environment. To do this, carefully check the first point below. ¾ ¾½vÔ Confirm that the following environment variables point to Oracle 10.2 directories: ¾ ¾½v» ORACLE_HOME points to /oracle/<DBSID>/102_64 ¾ ¾½v» PATH ¾ ¾½v» ORA_NLS10 ¾ ¾½v» LD_LIBRARY_PATH orSHLIB_PATH or LIBPATH ¾ ¾½vÔ Before you start the DBUA make sure that the DISPLAY environment variable is correctly set. Procedure
1.
You start the DBUA: cd $ORACLE_HOME/bin ./dbua
2.
Respond appropriately to the DBUA dialogs: The Welcome screen provides information about the upgrade assistant 1. Choose Next to continue.
30/48
PUBLIC
2009-08-25
4
Oracle Database Upgrade
4.2
Database Structure Upgrade
2.
The Databases screen lets you select the database to be upgraded. Select the correct database and choose Next. The DBUA now analyzes the database to be upgraded, performs pre-upgrade checks, and issues warnings if necessary. You can ignore warnings about the following: R83 ´Ă&#x201A; Stale optimizer statistics R83 ´Ă&#x201A; Changes to the Oracle CONNECT role You need to analyze and act on other warnings. RECOMMENDATION
We recommend you to resolve warnings other than those listed above. Otherwise you might later have problems during the actual upgrade.
3.
The SYSAUX Tablespaces screen lets you modify the attributes for the SYSAUX tablespace, which is added automatically to all new Oracle Database 10g databases. Make the following entries: R83 ´Ă&#x201A; Datafile Path: $SAPDATA_HOME/sapdata1/sysaux_1/sysaux.data1 NOTE
4.
5.
Make sure that you substitute the value for $SAPDATA_HOME with the full path name â&#x20AC;&#x201C; for example, /oracle/<DBSID> â&#x20AC;&#x201C; in the above command. You cannot use environment variables directly in the input field since the DBUA cannot evaluate SAP-specific environment variables. R83 ´Ă&#x201A; Select Reuse Existing File Name. R83 ´Ă&#x201A; Enter 1000 MB in Size. R83 ´Ă&#x201A; Select AUTOEXTEND ON. R83 ´Ă&#x201A; Enter 100 MB in Increment. R83 ´Ă&#x201A; Enter 2000 MB in Maximum Size. The Recompiling Invalid Objects screen lets you choose whether the DBUA has to automatically recompile all PL/SQL modules after the upgrade. If the database server has multiple CPUs, the DBUA automatically proposes the number of parallel processes to be used for the recompilation. The turn off archiving option means that archiving is switched off for the duration of the upgrade so that the upgrade finishes faster. Accept the default values, select Recompile invalid objects after the upgrade, turn off archiving for the duration of the upgrade, and choose Next. The Backup screen lets you specify whether you want the DBUA to back up the database. Since you have already backed up the database, select I have already backed up my database and choose Next. The Management Options screen lets you set up the database so that it can be managed with the Enterprise Manager.
2009-08-25
PUBLIC
31/48
4
Oracle Database Upgrade
4.2
Database Structure Upgrade
3.
6. Make sure that Configure the database with Enterprise Manager is not selected and choose Next. Before you start it, the DBUA displays a summary of the changes to be made. This includes the warnings that you ignored or did not fix, components to be upgraded, parameters to be added, removed, and changed after the upgrade. Review the summary of changes and choose Back to make any final adjustments, if required. NOTE
4.
5.
For a complete list of obsolete and deprecated parameters, see the documentation for Oracle Database 10g Release 2 (10.2). Start the database upgrade by choosing Finish. The DBUA automatically removes the database initialization parameters that are now obsolete in Oracle Database 10g Release 2 (10.2). The upgrade process itself runs for some time, depending mainly on the size of the database and the capacity of the hardware. When the DBUA has completed successfully the results of the upgrade are displayed Review the changes made and exit the DBUA.
32/48
PUBLIC
2009-08-25
5
Post-Upgrade Steps
5.1
Finalizing the Environment of the ora<dbsid>User
5 Post-Upgrade Steps
After the Oracle database upgrade, you need to perform the steps described here. 1. You finalize the environment of the ora<dbsid> user [page 33]. 2. You check the upgraded database [page 34]. 3. You update BR*Tools [page 35]. 4. You back up the database [page 36]. 5. You perform post-upgrade tasks [page 36]. 6. You install Oracle critical patch updates [page 38]. 7. You check the oratab entry [page 38]. 8. You start the listener process [page 39]. 9. You rename the old $ORACLE_HOME/bin directory [page 39]. 10. You check the read authorization of the <sapsid>adm user [page 40]. 11. You change the environment for the <sapsid>adm user [page 40]. 12. You check the SAP profile parameters [page 40]. 13. You change the location of the JDBC driver [page 41]. 14. You restart the SAP system [page 43]. 15. You disable the database user locking mechanism on failed logins [page 43]. 16. If necessary, you change the national character set of your database to UTF8 [page 43]. 17. You configure the new features for Oracle Database 10g Release 2 (10.2) [page 44].
5.1 Finalizing the Environment of the ora<dbsid>User You need to make sure that the changes you made to the Oracle user environment are permanently stored in the profiles (.cshrc, .dbenv_<hostname>.csh, and so on). Procedure
Check the values for the environment variables as described in Checking and Setting the Environment Variables [page 22]. NOTE
Make sure that the environment does not contain any variables that still refer to the old database release.
2009-08-25
PUBLIC
33/48
5
Post-Upgrade Steps
5.2
Checking the Upgraded Database
5.2 Checking the Upgraded Database You need to check the upgraded database. Procedure
1.
Check that the database is now running with Oracle Database 10g Release 2 (10.2) software in an Oracle Database 10g Release 2 (10.2) environment by entering the following commands: 1. Log on to the database as the ora<sid> user. 2. Enter the following command to start SQLPLUS: sqlplus / as sysdba
3.
Enter the following SQL commands: 1. Enter the following command to determine the release of the installed software: SQL> select version from V$INSTANCE; EXAMPLE
This is an example of the output from this command: VERSION 10.2.0.2.0
2.
Enter the following command to determine the release and status of the installed database components: SQL> select comp_id, version, status from dba_registry; EXAMPLE
This is an example of the output from this command: COMP ID VERSION STATUS CATALOG 10.2.0.2.0 VALID CATPROC 10.2.0.2.0 VALID
2.
3.
Make sure that the command returns the status VALID. 3. Check that the version returned in the previous two commands is identical. Check that the value for the version returned from the above command is the same level as the installed patchset. For example, if the installed patchset is Oracle 10.2.0.2, the above command should also report the version for the CATALOG and CATPROC components as 10.2.0.2. After the upgrade check that the following document is created: $ORACLE_HOME/assistants/dbua/doc/help/DefaultBehaviorChangesin10g.html NOTE
You need to check this document carefully because it contains information on important changes in the default behavior of the new Oracle 10.2 database.
34/48
PUBLIC
2009-08-25
5
Post-Upgrade Steps
5.3
Updating BR*Tools RECOMMENDATION
If the old database used an initialization file init<DBSID>.ora, theDBUA automatically creates an spfile. We recommend that you continue to use the spfile. Do not switch back to the initialization file after the upgrade.
5.3 Updating BR*Tools You update BR*Tools to the latest release, with the latest patch level. After extracting the latest BR*Tools release you need to update the SAPDBA role using the script sapdba_role.sql. This is essential so that the new release of BR*Tools works correctly. The script is automatically extracted when you extract BR*Tools. Procedure
1.
Download the most current version of the BR*Tools from SAP Service Marketplace at: http://service.sap.com/swdc
2.
After you have extracted the newest BR*Tools, copy the BR*Tools configuration files init<DBSID>.sap and init<DBSID>.utl from the old $ORACLE_HOME/dbs directory to the new one: cd <old $ORACLE_HOME>/dbs cp init<DBSID>.sap $ORACLE_HOME/dbs cp init<DBSID>.utl $ORACLE_HOME/dbs init<DBSID>.utl is only available if you are using a third-party backup solution. NOTE init<DBSID>.dba is no longer needed because BR*Tools release 6.40 SAPDBA is no longer
3.
available. Execute the following commands as the ora<dbsid> user to update the SAPDBA role: cp /usr/sap/<SAPSID>/SYS/exe/run/sapdba_role.sql $ORACLE_HOME/dbs cd $ORACLE_HOME/dbs 5™DérRŒ[R Vaq ‰°x„ž˘÷2Mp¼™¾^ı2 èÂÞIݶ ™ê[üñÔÖb
sqlplus /nolog @sapdba_role <SAPSCHEMA_ID> 5™DãrRŒSRPV.q ‰ëxÀž0÷ M ¼¤¾‚ı< 5™DérRŒ[R Vaq ‰°x„ž˘÷2Mp¼™¾^ı2 èÂÞIÖ¶.™Ý[ÍñÔÖb
sqlplus /nolog @sapdba_role <SAPSCHEMA_ID>DB 5™DãrRŒSRPV.q ‰ëxÀž;÷7M&¼Ł¾‚ı<
NOTE
If you have an ABAP+Java system, you have to enter both commands. CAUTION
Make sure that you execute this command for every SAPSCHEMA_ID in your database.
2009-08-25
PUBLIC
35/48
5
Post-Upgrade Steps
5.4
Backing Up the Database
5.4 Backing Up the Database You need to back up your upgraded Oracle Database 10g database. CAUTION
You risk losing data if you do not back up your database. Procedure
Perform a full database backup.
5.5 Performing Post-Upgrade Tasks You need to perform certain post-upgrade tasks. Procedure
1.
Change database compatibility by executing the following SQL command as the ora<dbsid> user: SQL> alter system set compatible='10.2.0' scope = spfile;
2. 3.
Restart the Oracle database. Deactivate the Oracle recycle bin by executing the following SQL command as the ora<dbsid> user: SQL> purge dba_recyclebin; SQL> alter system set recyclebin = 'off' scope = spfile;
4.
For more information, see SAP Note 838982. Gather Oracle optimizer statistics as follows: 1. Execute the following commands as the ora<dbsid> user: brconnect -u / -c -f stats -t system_stats brconnect -u / -c -f stats -t oradict_stats
2.
Execute the following commands with SQLPlus: SQL> exec dbms_scheduler.disable('GATHER_STATS_JOB'); SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_CONFIG_JOB'); SQL> exec dbms_scheduler.disable('ORACLE_OCM.MGMT_STATS_CONFIG_JOB');
5.
Identify the objects that are invalid after the upgrade as follows: 1. Execute the following commands as the ora<dbsid> user: SQL> @?/rdbms/admin/utlrp.sql; SQL> spool $ORACLE_HOME/cfgtoollogs/invalid_post.log SQL> select count(*) from dba_objects where status = 'INVALID'; SQL> select substr(owner,1,12) owner, substr(object_name,1,30) object, substr (object_type,1,30) type, status from dba_objects where status <>'VALID' order by owner; SQL> spool off;
36/48
PUBLIC
2009-08-25
5
Post-Upgrade Steps
5.5
Performing Post-Upgrade Tasks
2.
6.
7.
Check the log file invalid_post.log. created at $ORACLE_HOME/ cfgtoollogs/ invalid_post.log to compare the invalid objects before the start of the upgrade. Check the Oracle database parameters against SAP Note 830576 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. Restart the database to activate the changes: 1. Log on to the database with SQL*Plus 2. Execute the following commands: sqlplus / as sysdba shutdown immediate startup
8.
Gather statistics for SAP schemas: 1. With Oracle Database 10g all tables have statistics, which means that you need to update some entries in the DBSTATC table before starting BRCONNECT, as follows: Download the script updDBSTATC10.sql from SAP Note 819830. ÂÈ›– For 32-bit platforms: sqlplus /nolog SQL> connect / as sysdba SQL> @/oracle/stage/102_32/database/SAP/updDBSTATC10.sql
ÂÈ›– For 64-bit platforms, do one of the following: ÂÈ›–} sqlplus /nolog SQL> connect / as sysdba SQL> @/oracle/stage/102_64/database/SAP/updDBSTATC10.sql
ÂÈ›–}
sqlplus /nolog SQL> connect / as sysdba SQL> @/oracle/stage/102_64/database/Disk1/updDBSTATC10.sql
2.
Update the DBCHECKORA control table after the upgrade as follows: 1. Choose one of the following: ÂÈ›– For 32-bit platforms, enter the following command: cd /oracle/stage/102_32/database/SAP
2.
ÂÈ›– For 64-bit platforms, enter one of the following commands: ÂÈ›–} cd /oracle/stage/102_64/database/SAP ÂÈ›–} cd /oracle/stage/102_64/database/Disk1/SAP Choose one of the following: ÂÈ›– For systems other than Business Warehouse, enter the following command: sqlplus sap<sid>/<pwd> @dbcheckora10_oltp.sql
ÂÈ›– For Business Warehouse only, enter the following command: sqlplus sap<sid>/<pwd> @dbcheckora10_olap.sql
2009-08-25
PUBLIC
37/48
5
Post-Upgrade Steps
5.6
Installing Oracle Critical Patch Updates NOTE
3.
Call this script for every SAP ABAP schema on the database Update the Oracle database statistics with BRCONNECT as follows: brconnect -c -u / -f stats -t all â&#x20AC;&#x201C;f collect -p 4 NOTE
For more information about update statistics, see the documentation SAP Database Guide: Oracle at: www.sdn.sap.com/irj/sdn/ora SAP ON ORACLE KNOWLEDGE CENTER SAP Documentation
5.6 Installing Oracle Critical Patch Updates The Oracle Critical Patch Updates contain a collection of security-related fixes that are released once every quarter. Since these patches contain important fixes to significant security problems, we strongly recommend you to apply these Critical Patch Updates. See central SAP Note 850306 for information about the latest CPU to be installed. Prerequisites
4XbĂ°C Make sure you have already installed the current patch set [page 26]. 4XbĂ°C Make sure that you have installed all the required interim patches described in SAP Note 871096. 4XbĂ°C Check SAP Note 850306 to determine which Oracle CPU is needed. Procedure
1. 2.
Log on at the operating-system level as the ora<dbsid> user. Install the patches, following the instructions in the README document of the Critical Patch Update. Make sure that you complete the post-installation steps described in the README document.
5.7 Checking the oratab Entry You check the entry for the oratab file. Prerequisites
You can find the oratab file as follows: 4XbË&#x153;fĂ&#x161;<c?Ÿ´mĹĄĂĽÂł_=m9:Ă&#x192;Ă?Uâ&#x201E;˘ ÜÊ(ĂŁbâ &#x201E;½Ă&#x201E;ïòUĂ&#x17E;\â&#x20AC;&#x153;BĹĄÂąUN>Ăł(Ă&#x2021; Ă&#x2039; 6Ë&#x2021;ťŸ :*Uâ&#x20AC; Ă&#x2022;Ă&#x17D;Ă´Ă&#x2026;oVË&#x203A;äOrâ&#x2C6;&#x2019;'°â&#x20AC;&#x17E;b⿚Ë&#x2021;{Ă&#x2021;GCâ&#x20AC;&#x161;x°Ă&#x152;�ÝĂ&#x153;?â&#x20AC;˘ďż˝ÂŤ
/etc 4Xb fĂ&#x161;<k?ü´"ťþ³ =!9 Ă&#x192;Ă˝UĂŞ LĂśĂ&#x17D;(Ă bť½°ïà Uâ\ĂŁBâ&#x201E;˘Âą=N;ĂłFĂ&#x2021; Ă&#x2039;&6WĹĄĂŚ ^*Xâ&#x20AC; Ă&#x2022;Ă&#x2DC;ô¡oBË&#x203A;ÂśOTâ&#x2C6;&#x2019; °Ă&#x2122;b ¿ť
38/48
PUBLIC
2009-08-25
5
Post-Upgrade Steps
5.8
Starting the Listener Process
š±€Ö«ì냨M7 r�-è p‘{ž˜)nµfÊü˚7ß4È˙®³éŒí“`šçŸhr¾;˙Ím£
/var/opt/oracle š±€Ü«ì딨 7Gr‘-³ <‘Až )"µaÊá˚,ß}Èł®œ
Procedure
1.
Make sure that there is an entry as follows in your oratab file: <DBSID>:<new_ORACLE_HOME>:N new_ORACLE_HOME indicates the path to the Oracle Database 10g software. EXAMPLE
2.
The entry for a system with <DBSID> equal to C11 is as follows: C11:/oracle/C11/102_64:N. If the entry does not exist, insert it using a text editor.
5.8 Starting the Listener Process You start the listener process. Prerequisites
Make sure that you have copied the SQL*Net configuration files from the old Oracle installation to the location of the Oracle Datbase 10g software, as described in Copying and Adapting the SQL*Net Files [page 27]. Procedure
1.
Start the listener: lsnrctl start
2.
Check that you can remotely connect to the database through the listener: sqlplus SAP<SAPSCHEMA_ID>/pwd@SID
5.9 Renaming the Old $ORACLE_HOME/bin Directory Once the database is running correctly, you need to rename the bin directory from the old $ORACLE_HOME to prevent accidental usage of the old binaries. Procedure
Rename the old Oracle home directory bin with the following command: mv <old_oracle_home>/bin <old_oracle_home>/bin-old CAUTION
Do not rename the entire old_oracle_home in case you have SAP systems (SAP kernel release 6.40 and lower) running on the database server. This is because the SAP system running on the database server might still use the Oracle 9i client software.
2009-08-25
PUBLIC
39/48
5
Post-Upgrade Steps
5.10
Checking the Read Authorization of the <sapsid>adm User
5.10 Checking the Read Authorization of the <sapsid>adm User You check the read authorization of the <sapsid>adm user. Procedure
1. 2.
Make sure that the <sapsid>adm user has read authorization for the directory $ORACLE_HOME. If this is not true, enter the following command as the ora<dbsid> user: chmod 755 $ORACLE_HOME
5.11 Changing the Environment for the <sapsid>adm user You have to change the environment for the <sapsid>adm user, but only on the database server. NOTE
You do not need to change the environment for <sapsid>adm on application servers because SAP applications still use Oracle9i clients. Procedure
1.
On the database server set the ORACLE_HOME environment variable to point to the location of the Oracle Database 10g software installation, for example: /oracle/<DBSID>/102_<32>/<64>
2. 3. 4.
Make sure that the change to the user environment is permanently stored in the profiles (.cshrc, .dbenv_<hostname>.csh, and so on). Log out and log on again as the <sapsid>adm user. Check whether R3trans can connect to the database: R3trans –d
5.12 Checking SAP Profile Parameters You have to check the following SAP profile parameters: ªÉ’DÃfl ªÉ’DÃfl ªÉ’DÃfl
DIR_ORAHOME DIR_CLIENT_ORAHOME DIR_SERVER_ORAHOME
Procedure
1.
Set DIR_ORAHOME and DIR_CLIENT_ORAHOME in the instance profiles to the corresponding values of the ORACLE_HOME environment variable of the <sapsid>adm user. These variables point to the ORACLE_HOME used by the application server.
40/48
PUBLIC
2009-08-25
5
Post-Upgrade Steps
5.13
Changing the Location of the JDBC Driver
2.
Set DIR_SERVER_ORAHOME in the default profile to the value of the ORACLE_HOME environment variable of the ora<dbsid> user on the database server.
â&#x20AC;&#x2DC;7l+5OĹ&#x201A; â&#x2C6;&#x2019;V~{T 7NĂ?稏à 7Ă â&#x20AC;Śv³¨ÎĂ&#x20AC;ĂŤ=ĂŚĂťĂ&#x17D;Ă&#x17D;â&#x20AC;° â&#x20AC;˘â&#x20AC;&#x201D;½ozPâ&#x20AC;°Â¤Ă&#x201E;5]ZÞĹ Ă&#x153;Ă&#x2039;#Ă&#x201A; $â &#x201E;RĂŞ â¹Ă&#x160;Ăš7%Ă&#x2014;ĂŚeĂłâ&#x20AC;&#x2DC;Ă&#x17E;Ă&#x201E;Sâ&#x20AC;&#x153;8Ă&#x2026;ĂłIĂ? eĂşâ&#x20AC;&#x153;RlC
5.13 Changing the Location of the JDBC Driver If you have an SAP system with Java components, you may have to change the location of the JDBC driver after you have upgraded the database. Otherwise the J2EE Engine cannot start because the location of the JDBC driver still points to the path of the old ORACLE HOME. You change the location of the JDBC driver as follows: â&#x20AC;&#x2DC;7lĂ&#x201E; â&#x20AC; In files that are located in the database you use the J2EE Engine Config Tool to change the JDBC driver location. â&#x20AC;&#x2DC;7lĂ&#x201E; â&#x20AC; In files that are not located in the database you use Note Pad or another text editor to change the JDBC driver location. CAUTION
â&#x20AC;&#x2DC;7lĂ&#x201E; â&#x20AC; Make sure when you change the driver location that you use a forward slash "/" or backward slash "\" as appropriate. â&#x20AC;&#x2DC;7lĂ&#x201E; â&#x20AC; Make sure that you replace the old driver location in all locations stated in the following procedure. Procedure
1.
Change to the config.properties file, which is located in the following directory: â&#x20AC;&#x2DC;7lĂ&#x201E; â&#x20AC;
â&#x20AC;&#x2DC;7l+5OĹ&#x201A; â&#x2C6;&#x2019;V~{T 7NĂ?稏à 7Ă â&#x20AC;Śv³¨ÎĂ&#x20AC;ĂŤ=ĂŚĂťĂ&#x17D;Ă&#x17D;â&#x20AC;˘ ÂŁâ&#x20AC;&#x201D;â&#x2C6;&#x2019;oKP ¤ò
/usr/sap/<SAPSID>/JC<instance_number>/j2ee/configtool â&#x20AC;&#x2DC;7l!5OĹ&#x201A; â&#x2C6;&#x2019; ~4T 7 Ă?¨â&#x20AC;&#x2DC;Ă 2Ă Ă&#x2022;v´¨!Ă&#x20AC;ĂĽ
â&#x20AC;&#x2DC;7lĂ&#x201E; â&#x20AC;
â&#x20AC;&#x2DC;7l+5OĹ&#x201A; â&#x2C6;&#x2019;V~{T 7NĂ?稏à 7Ă â&#x20AC;Śv³¨ÎĂ&#x20AC;ĂŤ=ĂŚĂťĂ&#x17D;Ă&#x17D;â&#x20AC;° â&#x20AC;˘â&#x20AC;&#x201D;½ozPâ&#x20AC;°Â¤Ă&#x201E;5]ZÞĹ Ă&#x153;Ă&#x2039;#Ă&#x201A; $â &#x201E;RĂŞ Ú¹à Ú2%Ă&#x2026;ĂŚ)óÌĂ&#x17E;ĂŤSI8Ă?
/usr/sap/<SAPSID>/DVEBMGS<instance_number>/j2ee/configtool â&#x20AC;&#x2DC;7l!5OĹ&#x201A; â&#x2C6;&#x2019; ~4T 7 Ă?¨â&#x20AC;&#x201D;à à âvâ&#x20AC;&#x201C;¨ªĂ&#x20AC;Ă&#x201C;=½ÝŸĂ&#x17D;ÂŤ Ăšâ&#x20AC;&#x201D;ÂśoKPĂ&#x2013;¤ï5Ë?ZĹ&#x201A;Ăžďż˝ â&#x20AC;ŚĂ&#x2039;DĂ&#x201A;%$ďż˝R+ ÂĽ
1. 2.
Open the file with your text editor and search for the property rdbms.DriverLocation. Replace the old driver location with the new one: /oracle/client/10x_<32/64>/instantclient/<java_class_archive>.jar
2.
where <java_class_archive>.jar is classes12.jar or ojdbc14.jar In the same directory as in the first step, start the J2EE Engine - ConfigTool by double-clicking the configtool.sh file. 1. Change to Configuration Editor mode. 2. Use the Edit mode to replace the driver location in the following property sheets that contain the string rdbms.driverLocation= followed by the driver location: â&#x20AC;&#x2DC;7lĂ&#x201E; â&#x20AC;
cluster_data/Propertysheet instance.properties.IDXXXXXXX/ IDXXXXXXX.JavaParameters
2009-08-25
PUBLIC
41/48
5
Post-Upgrade Steps
5.13
Changing the Location of the JDBC Driver
where XXXXXXX is the instance number NOTE
Make sure that you change all occurrences. There might be several IDXXXXXX.JavaParameters properties in the property sheet. EÌ÷ EÌ÷
cluster_data/dispatcher/IDXXXX/kernel/propertysheet ConfigurationManager cluster_data/server/IDXXXX/kernel/propertysheet ConfigurationManager
where XXXX is the instance number NOTE
3.
If you have more than one server or dispatcher you must modify all relevant property sheets. 3. Close the J2EE Engine - ConfigTool. Change to the bootstrap.properties file, which is located in the following directory: EÌ÷
EÌ˘%ÅÂ ç· À¡ë�4«łŁ–*ƒqÈòìü¹} iµ€Ñ‘ñ^ä©è²‘49ÇC
/usr/sap/<SAPSID>/JC<instance_number>/j2ee/cluster/bootstrap EÌ %Å çî ‘¡û�o«×Ł¦*…qžòëüv}
EÌ÷
EÌ˘%ÅÂ ç· À¡ë�4«łŁ–*ƒqÈòìü¹} iµ€Ñ‘ú^Ç©ß²¾4²ÇuyŒ§±é«{>qôÍzg&·BJd)™& jXáłfi¥Fà`ãM)
/usr/sap/<instance_ID>/DVEBMGS<instance_number>/j2ee/ cluster/bootstrap
1. 2.
Open the file with your text editor and search for the property rdbms.DriverLocation. Replace the old driver location with the new one: /oracle/client/10x_<32/64>/instantclient/<java_class_archive>.jar CAUTION
If you have more than one J2EE Engine server installed, you must repeat steps 2 and 3 for all servers. EÌ %Å çî ‘¡û�o«×Ł�*€q©òÚüý}2iî€⁄‘Ú^¾©Ô²‘4ïÇ^yקƒé®{aqfiÍRg>·…J8
4.
Change to the sdmrepository.sdc file, which you can find in the following directory: EÌ÷
EÌ˘%ÅÂ ç· À¡ë�4«łŁ–*ƒqÈòìü¹} iµ€Ñ‘ñ^ä©è²‘49ÇC
/usr/sap/<SAPSID>/JC<instance_number>/SDM/program/config/ EÌ %Å çî ‘¡û�o«×Ł¦*…qžòëüv}
EÌ÷
EÌ˘%ÅÂ ç· À¡ë�4«łŁ–*ƒqÈòìü¹} iµ€Ñ‘ú^Ç©ß²¾4²ÇuyŒ§±é«{>qôÍzg&·BJd)™& jXáłfi¥Fà`ãM)
/usr/sap/<SAPSID>/DVEBMGS<instance_number>/SDM/program/config/
1.
Search for the following text: <Param type="String" hide="false" name="jarPaths" encrypted="false" displayName="Driver Paths (separated by ;)">
2.
If required, replace the old driver location with the new one, such as one of the following: /oracle/<DBSID>/102_64/jdbc/lib/<java_class_archive>.jar /oracle/client/10x_<32/64>/instantclient/<java_class_archive>.jar
EÌ %Å çî ‘¡û�o«×Ł�*€q©òÚüý}2iî€⁄‘Ú^¾©Ô²‘4ïÇ^yקƒé®{aqfiÍRg>·…J8
5.
Change to the rdb.properties file, which is located in the following directory: /usr/sap/<SID>/<INSTANCE>/j2ee/deploying
1.
42/48
Open the file with your text editor and search for the property rdbms.DriverLocation.
PUBLIC
2009-08-25
5
Post-Upgrade Steps
5.14
Starting the SAP System
2.
Replace the old driver location with the new one: /oracle/client/10x_<32/64>/instantclient/<java_class_archive>.jar
6.
Change to the templateconfigurator.properties file, which is located in the following directory: /usr/sap/<SID>/<INSTANCE>/j2ee
1. 2.
Open the file with your text editor and search for the property RDBMS_DRIVER_LOCATION. Replace the old driver location with the new one: /oracle/client/10x_<32/64>/instantclient/<java_class_archive>.jar
ËØ0Y߃Ld; 6ô¹¬fl¬ò~ù½@˙û¢gÁã{¸r®? ;HxvÑä4&T(‚ES ;¼J¦ÀCb(ò•DuÍ'+ XG8ÿN“’‹›‘¥
5.14 Starting the SAP System You need to restart the SAP system. Procedure
1.
If R3trans connects without problems, start the SAP system: Startsap
2.
Check the new Oracle version using SAP transaction ST04.
5.15 Disabling Database User Locking Mechanism For Failed Logins When upgrading an Oracle database to Oracle version 10g, user locking is automatically activated so that, if you repeatedly enter invalid login information, the user is locked. By default, ten invalid login attempts are allowed before the user is locked. Since old SAP systems first try to log in with a standard user (sapr3) and password, this locking mechanism might lock the user when starting the system. For more information, see SAP Note 951167. Procedure
To deactivate user locking after invalid logon attempts, enter the following information in sqlplus: sqlplus /nolog sql>connect / as sysdba sql>ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED; sql>exit
5.16 Checking the National Character Set If your database still runs with a national character set (NLS_NCHAR_CHARACTERSET) different from UTF8, you need to change it to UTF8. You can expect to experience severe problems during SAP upgrades if the database national character set is not set to UTF8. If you already use a Java system or plan to use one in the future, the national character set must be UTF8.
2009-08-25
PUBLIC
43/48
5
Post-Upgrade Steps
5.17
Configuring the New Features for Oracle Database 10g Release 2 (10.2)
Procedure
If necessary, follow SAP Note 669902 to change the national character set to UTF8.
5.17 Configuring the New Features for Oracle Database 10g Release 2 (10.2) You need to configure the new Oracle Database 10g Release 2 (10.2) features. Procedure
For more information about new features with Oracle Database 10g Release 2 (10.2) see SAP Note 828268. This note provides links to other SAP notes that describe how to configure or activate each new feature.
44/48
PUBLIC
2009-08-25
Typographic Conventions
Example
Description
<Example>
Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”. Arrows separating the parts of a navigation path, for example, menu options
Example Example Example Example
http://www.sap.com /example
123456 Example
Example
EXAMPLE
EXAMPLE
2009-08-25
Emphasized words or expressions Words or characters that you enter in the system exactly as they appear in the documentation Textual cross-references to an internet address Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web Hyperlink to an SAP Note, for example, SAP Note 123456 È "s J Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options. È "s J Cross-references to other documentation or published works È "s J Output on the screen following a user action, for example, messages È "s J Source code or syntax quoted directly from a program È "s J File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE Keys on the keyboard
PUBLIC
45/48
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com
© Copyright 2009 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. Disclaimer
Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.
46/48
PUBLIC
2009-08-25
Documentation in the SAP Service Marketplace
You can find this document at the following address: https://service.sap.com/instguides
2009-08-25
PUBLIC
47/48
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com
Š Copyright 2009 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.