SAP Basis Tech Supports

Symptom

This note deals with errors in Oracle Release 9.2.0 that can be eliminated by importing the relevant patch set.
Other terms

Oracle, patch, patchset, 9.2.0, hotfix, 9.2.0.3, 9.2.0.4, 9.2.0.5, 9.2.0.6, 9.2.0.7, 9.2.0.8, 9i, owapatch.sql, SP2-0310
Reason and Prerequisites

You want to import the relevant patch set to eliminate the errors in Oracle Release 9.2.0.
Solution

Current patch set for 9.2.0: 9.2.0.7 / 9.2.0.8
The patch sets are available in the Software Center on SAP Service Marketplace or you can order them on CD (see below for information on ordering CDs). For more information, also see Note 509314.
Before you import a patch, check whether settings (such as events or underscore parameters) have been activated that are different to the standard settings. These settings had to be activated as there were problems with the source patch status. You can deactivate them after you import the new patch. Note 124361 contains the parameters that are recommended as standard.

CAUTION – 9.2.0.7
Also refer to Note 884657 “Known issues specific to the Oracle 9.2.0.7 patch set”.
If you use the Oracle 9.2.x client software, refer to Note 886783.
CAUTION – >=9.2.0.7
Make sure that the _OPTIM_PEEK_USER_BINDS Oracle parameter is set to FALSE before you upgrade to Oracle 9.2.0.7 or higher. Otherwise, serious performance problems are very likely. See also the corresponding point in Note 176754.
CAUTION – AIX 5.3, AIX 6.1, HP-UX 11.23, Solaris 10, LINUX
If the runInstaller terminates while verifying the operating system version during the installation of an Oracle patch set, as in the following example on AIX 5.3
Checking operating system version: must be 5200 or 5100
Failed
then start the runInstaller as follows:
./runInstaller -ignoreSysPrereqs

CAUTION:
To unpack the Oracle 9 patch set, you require the latest version of the unzip utilities, available at www.info-zip.org. Also replace $ORACLE_HOME/bin/unzip with this new version.

The patch sets are available in the Software Center on SAP Service Marketplace (http://service.sap.com/swcenter-3pmain) in the following directories (also see Note 509314):
AIX 5L with Oracle 64 bit
/Oracle/Oracle 64-Bit/Oracle 9.2.0. 64-Bit/Oracle 9.2.0.8. 64-bit/
AIX_5L_64/Patchset_9208_AIX64-5L_a*.bin
HP TRU64 (Digital UNIX) 64-bit
/Oracle/Oracle 64-Bit/Oracle 9.2.0. 64-Bit/Oracle 9.2.0.8. 64-bit/
HP_TRU64/Patchset_9208_TRU64a*.bin
HP-UX 11.* with Oracle 64-bit
/Oracle/Oracle 64-Bit/Oracle 9.2.0. 64-Bit/Oracle 9.2.0.8 64-Bit/
HP_UX_64/Patchset_9208_HP-UX_64_a*.bin
HP-UX IA64 with Oracle 64-bit
/Oracle/Oracle 64-Bit/Oracle 9.2.0. 64-Bit/Oracle 9.2.0.8. 64-bit/
HP_IA64/Patchset_9208_HPUX-IA64_a*.bin
LINUX with Oracle 32-bit
/Oracle/Oracle 32-Bit/Oracle 9.2.0. 32-Bit/Oracle 9.2.0.8. 32-bit/
Linux/Patchset_9208_LINUX_a*.bin
LINUX x86-64
/Oracle/Oracle 64-Bit/Oracle 9.2.0. 64-Bit/Oracle 9.2.0.8. 64-bit/
Linux_x86_64/Patchset_9208_Linux-x86-64_a*.zip
LINUX IA64
/Oracle/Oracle 64-Bit/Oracle 9.2.0. 64-Bit/Oracle 9.2.0.8. 64-bit/
LINUX_IA_64/Patchset_9208_Linux-IA64_a*.bin
SUN Solaris with Oracle 64-bit
/Oracle/Oracle 64-Bit/Oracle 9.2.0. 64-Bit/Oracle 9.2.0.8. 64-bit/
SOLARIS_64/Patchset_9208_SOLARIS64_a*.bin
NT_I386 32-bit
/Oracle/Oracle 32-Bit/Oracle 9.2.0. 32-Bit/Oracle 9.2.0.8. 32-bit/
NT_I386/Patchset_9208_WINNT.zip
The patch set is installed with the runInstaller – see README.html
For more information about installing patch sets, see Note 578683.
In addition, use opatch to install patch 25 for 9.2.0.8.
/Oracle/Oracle 32-Bit/Oracle 9.2.0. 32-Bit/Oracle 9.2.0.8. 32-bit/
NT_I386/9208_Patch25_WINNT.zip
WINNT 64-bit (Windows 2003)
/Oracle/Oracle 64-Bit/Oracle 9.2.0. 64-Bit/Oracle 9.2.0.8. 64-bit/
NT_IA_64/Patchset_9208_WINNT.zip
In addition, use opatch to install patch 25 for Oracle 9208 on WINNT64:
/Oracle/Oracle 64-Bit/Oracle 9.2.0. 64-Bit/Oracle 9.2.0.8. 64-bit/
NT_IA_64/9208_Patch25_WINNT64.zip

Installation:
Installing the Oracle 9.2.0.* Patch set on Windows
See Note 578683 for information about installing the patch set on Windows. You can then continue with the post-installation steps.
Installing the Oracle 9.2.0.* patch set on UNIX:
1. Download the patch set as described in Note 509314.2. Decompress the downloaded patch set into a new directory (/oracle/stage/920*). Since the patch set can be quite large, make sure there is sufficient free space in the file system.3. Stop the R/3 instances, the database and the Listener. For AIX, execute slibclean (/usr/sbin/slibclean) as the root user to clean up unused modules in the kernel and in the memory.4. Start the Installer. Use the Oracle Universal Installer 10.1.0.4.0 runInstaller script, which is in the patch directory under Disk1.5. 9.2.0.8: Use the Oracle Universal Installer 10.1.0.5.0 runInstaller script, which is in the patch directory under Disk1.
CAUTION: If you do NOT use the runInstaller from the Disk1 directory, installation problems may occur on HP-UX 11.0.
6. Install the patch set.a) Start the Installer as follows:
% cd /oracle/stage/9207/Disk1
% ./runInstallerb) Click “Next” on the “Welcome” screen. This brings you to the “File Location” screen.c) As “Source”, enter the products.jar or products.xml file with the complete path to where the patch set was unpacked.
Check whether the correct alias for ORACLE_HOME is entered in the “Destination Name” field, and not “OUIHome1″.d) Click “Next”. The available products are displayed.e) Click “Install”.f) The installation may terminate with the following error message:
Error:
Exception thrown from action: moveFile
Exception Name: UnableToWriteDestinationException
Exception String: Cannot write to
destination $ORACLE_HOME/bin/dbsnmp.sav
Exception Severity: 2
Exception handling set to prompt user with options to RETRY IGNORE

To correct the error, execute the following as the root user:
chown ora:dba $ORACLE_HOME/bin/dbsnmp.sav
g) Start the $ORACLE_HOME/root.sh script as the root user if the Installer prompts you to do so.

CAUTION for LINUX IA64 or AMD 64-bit:
Under Linux Itainium 64, root.sh refers to the /usr/bin directory, even though that directory does not exist.
Therefore, before you execute the root.sh script,
make the following changes:
- edit with vi : vi root.sh
- change the entries /usr/bin to /bin (with the exception of tee and id)
:%s/\/usr\/bin/\/bin/
:%s/\/bin\/tee/\/usr\/bin\/tee/
:%s/\/bin\/id/\/usr\/bin\/id/
- save the file and then execute it as the root user.
If the following errors are reported:
/oracle//

/root.sh: line 45: [: too many arguments
/oracle///root.sh: line 49: $LOG: ambiguous redirect
Change the following lines in the root.sh file with vi:
# ORGINAL
# If LOG is not set, then send output to /dev/null
#
if [ x${LOG} = x ] -o [ ${LOG} = "" ];then <--- change
LOG=/dev/null
else
$CP $LOG ${LOG}0 2>/dev/null
…
change to: if [ x${LOG} = x -o ${LOG} ="" ];then

h) Click “OK” on the Installer screen. “End of installation” is displayed once the installation has been successfully completed.i) Click “Exit” and confirm.

Post – Installation:
The following post-installation steps are NOT valid for systems that have been migrated from Oracle 8.1.7.4 to Oracle 9.2.0.X, because for these systems you must proceed as described in the Installation Guide. (in other words, as of this point you should follow the Installation Guide).

After a successful installation, continue with the following post-installation procedure (this applies to both UNIX and Windows):
When you have installed JVM (Java-enabled) or JVM and XDB, then the init>SID>.ora SHARED_POOL_SIZE and JAVA_POOL_SIZE parameters should be at least 150MB in size.
If this patch set was installed for a cluster database, set the init.ora CLUSTER_DATABASE parameter to FALSE. Set the parameter to TRUE again after the post-installation scripts.
Call SQL*Plus and perform a “connect / as sysdba”
Execute a startup migrate.
startup migrateSince it can take a long time to execute the catpatch.sql script if there are statistics for the SYS schema, you should first check whether these statistics exist:
select count(*) from dba_tables
where last_analyzed is not null and owner=’SYS’;Execute the following script, even if there are no statistics for the DD tables:
exec dbms_stats.delete_schema_stats(’SYS’);Now execute “spool patch.log”.Execute the script “@?/rdbms/admin/catpatch.sql”.Execute “spool off”.Check patch.log for errors and, if necessary, execute catpatch.sql again after the errors have been cleaned up.Execute “shutdown”.Execute “startup”.Execute “@?/rdbms/admin/utlrp.sql”.If your DD tables contained statistics (the result of the above SELECT is not equal to 0), you should create the statistics again by using:

exec dbms_stats.gather_schema_stats(’SYS’);

Execute the script mentioned in Note 871455 to optimize access to DBA_SEGMENTS or DBA_EXTENTS.

In relation to the installation, you may also refer to the README.html file included with the patch set.
Due to the size of the patch sets you want to install, there must be sufficient free space available in the file systems of the Oracle Staging Area as well as in ORACLE_HOME, in order to avoid errors caused – for example – by software that was not fully unpacked during installation.
The patch sets are delivered in ZIP format.
You therefore require UNZIP for your UNIX or Windows platform. This software is available as shareware or freeware on the Internet under:
http://www.info-zip.org/UnZip.html
To be able to use $ORACLE_HOME/bin/runInstaller (in other words, using the PATH variable) to call OUI 10.1.0.2.0 (for Oracle 9.2.0.5) after you install it, you must proceed as follows:

cd $ORACLE_HOME/bin
rm runInstaller
ln -s $ORACLE_HOME/oui/bin/runInstaller.sh runInstaller
The old runInstaller link in the $ORACLE_HOME/bin directory still refers to the OUI Version 2.2.0.18.0 and can no longer be used with Oracle 9.2.0.5.

You must also ensure that the directory
$ORACLE_HOME/oui contains a valid oraparam.ini file.
If you want to order the Oracle 9.2.0.x patch sets on CDs, create a message on the XX-SER-SWFL-SHIP component and refer to the material number that is assigned to your operating system, as follows:
For Oracle 9.2.0.4
51020354 AIX 5L (2 CDs)
51020247 HP-UX
51020248 Solaris 64-bit
51020249 HP Tru64 (2 CDs)
51020250 Linux
The structure of the CDs (except for AIX and TRU64) is as follows:
/UNIX
/UNIX/
/UNIX//920x__release.cpio
/UNIX//README.html
/UNIX//patchnote.css

Note the following when installing the Oracle 920x patch set from the CD:
- for AIX and TRU64, the software is already unpacked on the CD, which means that the installation can be carried out directly from the CD. As the source, you must select the products.jar from the CD under /UNIX//stage.
- for the other platforms,
you must first copy the file 920x__release.cpio into a directory that has already been created and then unpack it.
For the remaining steps of the installation, refer to the README.HTML file, which you can also find on the CD.
Installation patch set 9.2.0.8
After the installation of patch set 9.2.0.8
the following errors occur concerning the SQL script owapatch.sql. when you carry out catpatch.sql (catproc).
The problem is
platform-specific:
- AIX / Solaris 64-bit:
The system issues the following error message:
SP2-0310: unable to open file “$ORACLE_HOME/rdbms/admin/owapatch.sql”
the script does not exist in the patchset, the OWA package is not changed.
the error occurs when you carry out SAPInst or R3setup.
Download the script from SAP Marketplace (see below),
copy it into the $ORACLE_HOME/rdbms/admin directory and
confirm “Retry” in the SAPInst or restart R3setup.
- Linux x86-64:
The script is in the patch set. However, it is not installed in the Oracle Home
and it is not executed. The OWA package is not changed.

- Linux Itanium / HPUX PA-RISC:
The script is in the patch set, but is has the file length 0.
It is installed into the Oracle Home and executed, but due to the
file length 0, the OWA package is not changed.
Solution for these platforms:
You can find the script owapatch.sql on SAP Service Marketplace at: Oracle -> Oracle other -> Scripts Download the file and unpack it into the directory 9.2.0.8 $ORACLE_HOME/rdbms/admin.
If catpatch/catproc calls owapatch.sql correctly in accordance with the platform description,
you only have to carry out catproc again.
If this is not the case, carry out owapatch.sql manually (only Linux x86-64).