SAP Basis Tech Supports

Symptom

***********************************************************************
*
* 6.20/6.40 Patch Collection Installation on
* Oracle / UNIX
*
***********************************************************************

Other terms

SAP Web AS 6.20, SAP Web AS 6.40, 6.20/6.40 Patch Collection, 6.20/6.40 based products Installation Master, Unix, Oracle, Installation

Reason and Prerequisites
You want to install an SAP system on UNIX using the “6.40 based products Installation Master(Edition May 2008)” DVD (Material Number 51033746).You want to install an SAP system on UNIX using the “6.20/6.40 based products Installation Master(Edition July 2007)” DVD (Material Number 51032936).

Solution

DO NOT CHANGE OR ADD INFORMATION TO THIS NOTE !
If you want to contribute something, please send a mail to:
Klaus Billig klaus.billig@sap.com

You can use DVD “6.20/6.40 based products Installation Master” to install the following SAP systems:
SAP BW 3.1 (contained in “Edition July 2007″ only)mySAP CRM 4.0 / SAP SRM 3.0 (contained in “Edition July 2007″ only)mySAP CRM 4.0 SR1mySAP ERP 2004 SR1SAP R3E 4.7 Extension Set 2 SR1mySAP SCM 4.0 (contained in “Edition July 2007″ only)mySAP SCM 4.1mySAP SRM 4.0 SR1SAP Solution Manager 3.2 SR1SAP NetWeaver ‘04 SR1

For more information, see SAP Note 969660 (6.20/6.40 Patch Collection Installation on UNIX)

Contents

Sections of this note are:

1. General (1)2. Pre-Installation (2)3. Installation (3)4. Post-Installation (4)5. High Availability (5)

The “General” section contains general informations about how to obtain the available editions of “6.20/6.40 based products Installation Master” DVD, about general restrictions and problems.
The remaining sections (”Pre-Installation”, “Installation”, “Post-Installation”, “High-Availability”) contain workarounds for known installation problems and bugs which have not yet been fixed.
In these remaining sections, each entry is marked with a prefix to make clear which installation type or SAP system the information applies to. If there is no prefix, the information applies to all types or SAP systems.
Entries that are only valid for the patch collection edition May 2008 or July 2007 are marked respectively. Otherwise the information is valid for both patch collection editions.
The following prefixes are used:

Date Section Description
———————————————————————–
16/DEC/08 3 Oracle 10.2.0: BRCONNECT “check” function returns many alert errors MISSING_STATISTICS
18/JUL/08 3 (…)runCatprocSql was executed with status ERROR
26/OCT/07 3 Error FKD-00079 in sapinst_dev.log
22/APR/07 3 Linux PPC_64 only, distributed database server installation: Invalid environment of adm
16/JAN/07 3 R3load error on DIGITAL Unix (OSF)
15/SEP/06 3 ORACLE_HOME is not set correctly for user adm during a distributed installation
11/AUG/06 3 Error in step BRCONNECT_IND_ORA
24/MAY/06 3 RUNINSTALLER does not work. Cause: /oracle is owned by adm
15/FEB/06 3 Wrong path to RUNINSTALLER in SAPinst message box “SAPinst now stops the installation…you must install the Oracle database as follows…”
25/JUL/05 2 comment on file system /oracle/client
17/MAR/05 3 set umask to 022 for running script /tmp/orainstRoot.sh
08/MAR/05 4 Run installation scripts for Oracle-DB monitor
08/FEB/05 3 Network Adapter could not establish the connection
04/AUG/04 2 ABAP+Java only: Selecting a SCHEMA-ID
07/MAY/04 3 Update Statistics with brconnect fails
14/APR/04 3 Creating SAPDB user password:do not use “initial”
10/MAR/04 3 LINUX/IA64 only: Error in invocing target install of Oracle makefile
14/JAN/04 3 Error ORA-1403 when accessing table SAPUSER
24/JUL/03 3 JDBC connection error: restart Oracle listener
12/MAY/03 3 Linux: Only for Installation on SuSE SLES8 (Linux)
17/SEP/02 2 Oracle on HP Tru64 UNIX 5.x with TruCluster SW
16/AUG/02 2+3 HP-UX 11 64-Bit: Apply latest patch
14/AUG/02 2+3 File systems > 2 GB are mandatory for Oracle inst.
14/AUG/02 3 ORA-00060 + ORA-00604: Cancel and restart SAPinst
23/OCT/01 3 RUNINSTALLER: Error in writing to dir. /tmp/OraInstall
05/APR/00 2 HP-UX 11.0 64-bit + 32-bit Ora: Set SHMMAX < 4GB
10/AUG/98 4 ORA-01031 in stopdb.log
14/JUL/98 2 Two Oracle databases on the same host
03/MAR/98 2 AIX: Asynchronous I/O must be available
10/JUL/97 2 HP Tru64 UNIX: check shmmax if RAM >= 2GB

=======================================================================
1 General

=======================================================================

1.) How to obtain DVD “6.20/6.40 based products Installation Master”

See the “General” section in SAP Note 969660 (6.20/6.40 Patch Collection Installation : Unix)

2.) Supported versions of the Oracle database:

AKK 6.40 Installation Patch Collection supports Oracle 9.2 and 10.2.
Check SAP Note 539921 for the current patch set for Oracle 9.2.Check SAP Note 871735 for the current patch set for Oracle 10.2.
See also section”3.) Retroactive Release of Oracle 10.2″
Note:
The installer chooses Oracle database server version ‘102′ by default.
If you want to install a Java only system with Oracle 9.2, you m u s t choose the following installation option on the Welcome screen of the installation master DVD:
SAP NetWeaver ‘04 SR1 -> Initial Installation Tasks -> Java System -> Oracle -> Custom Installation – Java System
On the screen ‘Oracle > Database System’ choose database server version ‘920′ instead of ‘102′.

3.) Retroactive Release of Oracle 10.2
New Installation Master and Oracle 10.2 RDBMS DVDs
If you want to install SAP Web AS 6.40 SR1 with Oracle 10.2, do not use the original SAP NetWeaver ‘04 Installation Master DVD.
Order the new Installation Master DVD produced for the installation withOracle 10.2 along with the Oracle 10.2 RDBMS DVDs.
You can also download these DVDs from SAP Service Marketplace at http://service.sap.com/swdc.
See also SAP Note 940794.Check whether you have to apply additional support packages
After completing the installation with Oracle 10.2 successfully,you have to check the level of the Basis Support package available on the system.
868681 Oracle Database 10g: Database Release Check
949785 Basis 640, DDIC: Necessary enhancement due to Oracle 10.2
949516 Basis 620, DDIC: Necessary enhancement on account of Oracle 10.2

4.) Required Kernel DVD
Use theSAP NetWeaver 04 SR 1 Kernel DVDfor your database for the installation, except for Informix 10. For Informix 10, you must use the Informix 10.00 DVD.Although you perform a Unicode installation, SAPinst might also ask for the non-Unicode kernel DVD. Therefore have this DVD available for the installation.

NOTE:
Check also SAP Note 969660 for database-independent archives that you have to update.
For information on downloading files from sapserv, see SAP Note 19466.

5.) File requirements of Oracle sapdata file systems

(pure space requirements can also be found in file DBSIZE.XML on the Export DVD; the recommended values that are also listed in the following table are a little bit larger than the values contained in DBSIZE.XML):
SAP Web AS ABAP 6.40 SR1:
File System NameSpace Requirement/oracle//sapdata1600 MB/oracle//sapdata21200 MB/oracle//sapdata3700 MB/oracle//sapdata415000 MBSUM17500 MB

SAP ECC 5.0 SR1:
File System NameSpace Requirement/oracle//sapdata113000 MB/oracle//sapdata211000 MB/oracle//sapdata313000 MB/oracle//sapdata415000 MBSUM52000 MB

SAP SRM Server 5.0 SR1:
File System NameSpace Requirement/oracle//sapdata14500 MB/oracle//sapdata25000 MB/oracle//sapdata34500 MB/oracle//sapdata44500 MBSUM18500 MB

Note: These values are only guiding values. Each file in thesefilesystems can grow up to 10,0 GB maximum.
Exception: For Linux the values listed in the table above are maximum values.

6.) Comment on file system /oracle/client

The file system you have to set up for Oracle client software is /oracle/client. The directory /oracle/client/92x_32 or /oracle/client/92x_64 is created by SAPinst during installation.

7.) Aliases “/ti” and “/network” no longer available on SMP

The quicklinks “/ti” and “/network” which are listed in chapter “Information on SAP Service Marketplace” in the installation guides are no longer available.

=======================================================================
2 Pre-Installation

————————————————
ABAP+Java only: Choosing a SCHEMA-ID
When choosing the SCHEMA-ID, it is highly recommendednotto use the default value . For more information, see SAP Note 617444.
————————————————
Oracle on HP Tru64 UNIX 5.x with TruCluster SW
If you are installing Oracle on HP Tru64 5.x together with TruCluster software (even in a one node cluster configuration), see SAP Note 382717 for additional installation information. If instructions in this SAP Note are not applied, Oracle may not work properly or not operate at all.
———————————————
HP-UX 11 64-Bit: Apply latest patch
Apply the latest patch as described in SAP Note 431881. Otherwise,
immediately after the start, the SAPDBA and BR tools (Version 6.10) may hang during the setup of the first database link on HP-UX 11 64-bit.
——————————————–
File systems > 2 GB are mandatory for Oracle inst.
For the installation of SAP systems on Oracle/UNIX, create file systems larger than 2 GB (see corresponding section for creating file systems in the documentation ‘SAP Software on UNIX: OS Dependencies’). Otherwise, an error similiar to the one listed below may occur during the installation:
IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed rc=99, table “T022D”
(SQL error 1237)
ORA-01237: cannot extend datafile 2
ORA-01110: data file 2: ‘/oracle/I21/sapdata4/i21_1/i21.data1
ORA-27059: skgfrsz: could not reduce file size
——————————————–
HP-UX 11.0 64-bit + 32-bit Ora: Set SHMMAX < 4GB
If you want to install a 32-bit Oracle database on HP-UX 11.0 64-bit, set kernel paramter SHMMAX to a value less than 4GB. Otherwise, the initialization process fails (ORA-3113). See SAP Note 195205 for more information.
------------------------———————
AIX only: Asynchronous I/O must be available
Check if asynchronous I/O is available both on the database and the application server:
lsdev -C -t aio
must output “Available Asynchronous I/O” (”Defined” instead of “Available” is not sufficient.).
If asynchronous I/O is not available, assure that you have run the script rootpre.sh as prompted by runInstaller (Oracle 8.1.x).
———————————————
Two Oracle databases on the same host
If you want to install two Oracle databases on the same host, see SAP Note 98252.
———————————————
HP Tru64 UNIX only:
If you have 2 GB RAM or more, ensure that the OS kernel parameter
shmmax matches the corresponding ORACLE parameters. Otherwise, there
might be insufficient memory for the ORACLE System Global Area.
Procedure:
After installing the database, check the following parameters in the
file /oracle//dbs/init.ora:
db_block_buffers, db_block_size, log_buffer, shared_pool_size
The result of
(db_block_buffers * db_block_size) + log_buffer + shared_pool_size
must be less than the value of shmmax.
If it is not, increase shmmax as described in SAP Note 356370.

=======================================================================
3 Installation

—————-16/DEC/08, D022850>————————–
Oracle 10.2.0: BRCONNECT “check” function returns many alert errors MISSING_STATISTICS
You have the following options to solve the problem:
If you use Oracle 10.2.0.4: Before loading SAP data into the database, you must install the optimizer merge fix according to SAP note 1165319. Otherwise, after you have installed the SAP system, log on as user ora and create the missing statistics with the command:
brconnect -u / -c -f stats -t missingIf you use Oracle 10.2.0.2: After you have installed the SAP system, log on as user ora and create the missing statistics with the command:
brconnect -u / -c -f stats -t missing
See also SAP Note 1284406.
——————–—————————
(…)runCatprocSql was executed with status ERROR
Symptom:
You see an error message like the following in sapinst_dev.log:
ERROR …..
FCO-00011 The step runCatprocSql with step key NW_Onehost ind ind ind ind 0 0 NW_Onehost_System ind ind ind ind 1 0 NW_CreateDBandLoad ind ind ind ind 10 0 NW_CreateDB ind ind ind ind 0 0 NW_OraDBCheck ind ind ind ind 0 0 NW_OraDBMain ind ind ind ind 0 0 NW_OraDBStd ind ind ind ind 3 0 NW_OraDbBuild ind ind ind ind 5 0 runCatprocSql was executed with status ERROR .
This error only occurs if Oracle patch 10.2.04 is installed.
Solution:
There are two ways to resolve this problem:
Modify control.xml and restart the installation1. Edit file control.xml in your installation directory (default sapinst_instdir).2. Search for “this.runCatproc = “3. Go to “script.execute_AbortOnFailure();” some lines below.4. Replace “script.execute_AbortOnFailure();” with “script.execute();”.5. Restart Sapinst and choose “Continue with the Old Option”Update the sapinst executable and restart the installation1. Download the newest sapinst executable from the Software Distribution Center as follows:a) Go to http://service.sap.com/swdc.b) On the right-hand panel, choose “Search for Software”.c) Enter “sapinst” as search term.d) Choose the sapinst executable for your release (640, 700, 710).2. Replace the existing sapinst executable with the downloaded sapinst executable3. Restart Sapinst and choose “Continue with the Old Option”

—————————————————-
Error FKD-00079 in sapinst_dev.log:
Symptom:
FKD-00079 no parameter table with the name T_ORA_OCLFILE exists
Solution:
1. Search for line
COMMONDBORA
CREATEDBORA
3. Insert the following line:
OraBackRel< /namespace>
Result:

COMMONDBORA
< namespace> CREATEDBORA
OraBackRel
4. Restart your installation with the option “Continue old installation”.

———————–————————–
Linux PPC_64 only, distributed database server installation:
Invalid environment of adm
On the database server the oracle client software is not extracted. All required oracle libraries are located under /oracle//102_64/lib
Solution:
Set the environment variable LD_LIBRARY_PATH in the login
scripts to /oracle//102_64/lib

————————-————————
Error during R3LOAD for DIGITAL Unix only
During load database you get the following error in R3load logfiles SAP*.log
DbSl Trace: OCI-call ‘OCIInitialize’ failed: rc = -1
DbSl Trace: OCI-call ‘OCIErrorGet’ failed: rc = -2 (DB)
ERROR: db_connect rc = 256
DbSl Trace: OCI-call ‘OCIInitialize’ failed: rc = -1
DbSl Trace: OCI-call ‘OCIErrorGet’ failed: rc = -2 (DB)
ERROR: DbSlErrorMsg rc = 99
/sapmnt/XXX/exe/R3load: job finished with 1 error(s)
Solution:
Use the latest sapinst patch as describe in SAP note 929929.
———————–————————
Wrong setting of ORACLE_HOME for user adm on distributed installation
Symptom:
You install a distributed system with
oracle server version 9.20oracle client version 9.20.
You do not install the central instance or dialog instance on the
database instance host.
The ORACLE_HOME variable is not set correctly:
ORACLE_HOME is set to /oracle/client/92x_ but the oracore files are located under the Pseudo ORACLE_HOME /oracle//920_/oracore The connect to db fails: The correct path for ORACLE_HOME must be /oracle//920_.
Solution:
Change your .dbenv_.csh or .dbenv_.sh in the home
directory of adm user as follows:
Changes for csh:
================
1. Search in .dbenv*csh for the following lines:
if ( $USER != $ORASID ) then
set _f=/sapmnt//profile/DEFAULT.PFL
set _t=/oracle//920_/bin/sqlplus
2. Insert the following new line:
set _o=/oracle/920_/oracore
3. Go to the following line:
setenv TNS_ADMIN /oracle//920_/network/admin4. Remove the next line:
setenv ORACLE_HOME `echo $ORA_NLS33 | awk -F_ ‘{printf(”%s_”,$1)}5. Insert the following new lines:
if ( -r “$_o” ) then
setenv ORACLE_HOME /oracle//920_
else
setenv ORACLE_HOME `echo $ORA_NLS33 | awk -F_ ‘{printf(”%s_”,$1)}
fi
endif

Changes for sh:
===============
1. Search in .dbenv*.sh for the following lines:
if [ $USER != $ORASID ]; then
_f=/sapmnt//profile/DEFAULT.PFL
_t=/oracle//920_/bin/sqlplus
2. Insert the following new line
_o=/oracle//920_/oracore
3. Go to the following line:
TNS_ADMIN=@ORACLE_HOME@/network/admin4. Remove the next line
ORACLE_HOME=`echo $ORA_NLS33 | awk -F_ ‘{printf(”%s_”,$1)} {printf(”%2.2s”,$2)}’`5. Insert the following new lines
if [ -r "$_o" ]; then
ORACLE_HOME=/oracle/< DBSID>/920_
else
ORACLE_HOME=`echo $ORA_NLS33 | awk -F_ ‘{printf(”%s_”,$1)}
{printf(”%2.2s”,$2)}’`
fi

Result:
now the env variable is set to ORACLE_HOME=/oracle//920_ for the dialog instance or central instance.
———————–—————————
Error in step BRCONNECT_IND_ORA
Symptom:
The following error occurs in step BRCONNECT_IND_ORA:
ERROR 2006-08-04 13:10:32 BRCONNECT_IND_ORA ExecuteCheck:0
Exit code from /sapmnt/QO1/exe/brconnect: 9.
ERROR 2006-08-04 13:10:32 BRCONNECT_IND_ORA InternalInstallationDo:0
Phase failed.
ERROR 2006-08-04 13:10:32 BRCONNECT_IND_ORA InstallationDo:0
Phase failed.
ERROR 2006-08-04 13:10:32 InstController Action:0
Step BRCONNECT_IND_ORA could not be performed.
ERROR 2006-08-04 13:10:34 Main :0
Installation failed.
ERROR 2006-08-04 13:10:34 Main :0
Installation aborted.
Cause:
brconnect does not find all required libraries that are located under
$ORACLE_HOME/lib.
Solution:
Set environment variable LD_LIBRARY_PATH (AIX: LIBPATH; HP-UX:
SHLIB_PATH) to $LD_LIBRARY_PATH:/oracle//10_/lib(64).
Example for csh:
setenv LD_LIBRARY_PATH $LD_LIBRARY_PATH:/oracle/C11/102_64/lib
Example for ksh:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/oracle/C11/102_64/lib

————————–————————-
RUNINSTALLER does not work. Cause: /oracle is owned by adm
Symptom:
The Oracle RUNINSTALLER does not work.
One possible cause is that /oracle is owned by adm.
Solution: Change the permission of /oracle and /oracle/oraInventory using the following commands:
chown ora:dba /oraclechown ora:dba /oracle/oraInventory

————————–————————–
Wrong path to RUNINSTALLER on SAPinst dialog “SAPinst now stops the installation…you must install the Oracle database as follows…”
Symptom:
The path to the oracle RUNINSTALLER can be wrong on the SAPinst dialog for some UNIX operating systems.
Solution:
The correct path for the following operating systems is:
LINUX*, SOLARIS*, HP_IA64:
/oracle/stage/102_<32 or 64>/database/SAP/RUNINSTALLERAIX* and HP_PARISC:
/oracle/stage/102_64/database/Disk1/SAP/RUNINSTALLER

————————-————————–
Oracle Client Installation:
Central Instance and Dialog instance hosts:
Only check the option “Install Oracle Client Software” in SAPinst if your database instance is located on a different server than the central or dialog instance you are installing AND if the Oracle client software has not been extracted on this central or dialog instance host before(for example the directory /oracle/client/92x_64 is empty).
Database instance hosts:
Please check the option “Install Oracle Client Software” in SAPinst as this will create a link between the client software directory and the database software. The client will not be installed by SAPinst in this case as it is not needed.
Database instance hosts for MCOD systems:
If you are installing an additional SAP system into an existing database, DO NOT check the option “Install Oracle Client Software” in SAPinst.

————————–————————
set umask to 022 for running script /tmp/orainstRoot.sh
When the Oracle Universal Installer prompts you to run script /tmp/orainstRoot.sh, you need to make sure that umask is set to 022 in the root shell.
———————-—————————
Symptom:
The Network Adapter could not establish the connection.
The oracle listener is not running correct on the database host
You can check it with the command lsnrctl status as user orasid
Solution
Please start the oracle listener as orasid user:
lsnrctl start
or stop the listener and restart it with
lsnrctl stop
lsnrctl start
————————————————–
Update Statistics with brconnect fails
SAPinst interrupts with the following error message:
ERROR 2004-03-04 14:00:25 CJS-00288 Could not update database statistics. DIAGNOSIS: Command brconnect -u / -c -f stats -o SAPQO1 -t all -m +I -s P10 -f allsel, collect,method,precision,keep -p 4 returned 3, which is not a success code. SOLUTION: See brconnect.log for details.
Please implement note 717677 and continue the installation.
————————————————–
Creating SAPDB user password, do not use “initial”
When creating the user password for the Oracle schema user SAPD, your are not permitted to use “initial” as the password.
Otherwise you will get an error message.
————————————————–
LINUX/IA64 only: Error in invocing target install of Oracle makefile
Symptom:
Error in invoking target install of makefile
/oracle//920_64/network/lib/ins_oemagent.mk
Solution:
1. Log on as user root and enter the following command:
rpm -Uvh –oldpackage \
/usr/linux_em/Misc/ia64/binutils-2.12.90.0.15-39.ia64.rpm2. Continue the Oracle installation as user ora.3. After having finished the Oracle installation incl. patching enter
the following command as user root:
rpm -Uvh /usr/linux_em/Misc/ia64/binutils-2.14.90.0.5-44.ia64.rpm

————————————————-
Error ORA-1403 when accessing table SAPUSER
Symptom:
During installation following error message will get into the log files dev_w0, dev_w1, etc. of the work processes: “C *** ERROR => ORA-1403 when accessing table SAPUSER”
Solution:
If you do not observe any other problems (like e. g. the system not coming up) the error message can be ignored.
————————————————-
JDBC connection error: restart Oracle listener
If a connection error (”ERROR: Connect failed to database”) occurs while connecting to the database with the JDBC driver during the installation with the SAP J2EE Engine, perform the following commands as user ora to restart the Oracle listener:
lsnrctl stop
lsnrctl start
————————————————–
Linux: Only for Installation on SuSE SLES8 (Linux)
The database software has to be Oracle release 9.2.0 (starting with SAP Kernel 4.6D). Probably you need to order the appropriate CD separately.Besides you must update SuSE SLES8. More information about how to prepare the operating system is available at:http://sdb.suse.de/en/sdb/html/hacht_sap_on_SLES8.html (English)http://sdb.suse.de/de/sdb/html/hacht_sap_on_SLES8.html (German)
Download the corresponding PDF document and read especially the section regarding Oracle.After the installation of the SAP software has finished, you should check that the environment variable “http_proxy” is not set with respect to the users “ora” and “adm”. Otherwise, you may get an “Error 46 initializing SQL*Plus” when starting “sqlplus”.

———————————————
HP-UX 11 64-Bit: Apply latest patch
If, immediately after the start, the SAPDBA and BR tools (Version 6.10) hang during the setup of the first database link on HP-UX 11 64-bit and you didn’t apply the latest patch as described in section 1 of this SAP Note, see SAP Note 431881.
——————————————–
File systems > 2 GB are mandatory for Oracle inst.
For the installation of SAP systems on Oracle/UNIX, create file systems larger than 2 GB (see corresponding section for creating file systems in the documentation ‘SAP Software on UNIX: OS Dependencies’). Otherwise, an error similiar to the one listed below may occur during the installation:
IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed rc=99, table “T022D”
(SQL error 1237)
ORA-01237: cannot extend datafile 2
ORA-01110: data file 2: ‘/oracle/I21/sapdata4/i21_1/i21.data1
ORA-27059: skgfrsz: could not reduce file size
—————————————————
ORA-00060 + ORA-00604: Cancel and restart SAPinst
Very rarely, the following errors may occur together during the load with SAPinst:
ORA-00604: error occurred at recursive SQL level 2
ORA-00060: deadlock detected while waiting for resource
In this case, cancel and restart the installation.
Nevertheless, we ask you to open a customer message in component BC-INS-UNX, so that we are able to trace the cause for this problem.
————————-————————-
RUNINSTALLER: Error in writing to dir. /tmp/OraInstall
If RUNINSTALLER has been run previously and the RUNINSTALLER errors (”Error in writing to directory /tmp/OraInstall. Please ensure that this directory is writable and has at least 25 MB of disk space. Installation cannot continue.”
“Bad file number”),
whereas /tmp has enough directory space and the user has read/write execute privileges for /tmp/OraInstall, remove the /tmp/OraInstall directory and run the installer again.

=======================================================================
4 Post-Installation

————————–————————-
Run installation scripts for Oracle-DB monitor
To be able to use the full range of functions provided by the new Oracle
Performance Monitor (transaction ST04N), you need to run installation
scripts according to SAP Note 706927.

=======================================================================
5 HIGH AVAILABILITY

As of NW04 SR1, you can perform a high availability installation of your SAP Web Application Server. For more information, see SAP Note 803018 and SAP Service Marketplace at service.sap.com/ha.