SAP Note 26972 - INST: 3.0/3.1 R/3 Inst. - ORACLE Parallel Server

Symptom:

+---------------------------------------------------------------------+
I R/3 Installation on UNIX - ORACLE Parallel Server I
I I
+---------------------------------------------------------------------+

Related Notes:
3.0D 3.0E 3.0F 3.1G Title
----------------------------------------------------------------------
31451 44795 47946 50183 R/3 Installation on UNIX
31445 44804 47942 50184 R/3 Installation on UNIX - ORACLE Database
31450 44796 47954 50189 R/3 Installation on UNIX - OS Dependencies
31449 44797 51690 50192 R/3 Advanced Installation/ Homog. System Copy

Cause and prerequisites

Problems discovered after publication of the Installation Guide.

Solution

The note is maintained in English only. No German version exists.

DO NOT CHANGE OR ADD INFORMATION TO THIS NOTE !

If you want to contribute something, please send a mail to to any of:
Winfried Nesselhauf winfried.nesselhauf@sap-ag.de
Robert Voelkel robert.voelkel@sap-ag.de

table of contents (sorted by date)
===================================

date section description
-----------------------------------------------------------------------
04/JUL/1997 1 3.1G: Oracle 7.3.2.3: DB startup fails
13/DEC/1996 1 3.0E: SICK error at 1st SAPGUI connect after startup
13/DEC/1996 1 3.0D: Oracle patches required
12/DEC/1996 1 Adapt SAPFS.TPL after creating raw link script
04/NOV/1996 1 3.0E: Executables of sapdba, etc. must be extracted
04/SEP/1996 1 3.0D: File OPSFILENAME is not on CD
04/SEP/1996 2 3.0D: New name for the file DEFAULT.CONF

Sections of this note are:
1 General Notes
2 RS 6000 SP Specific Notes
3 RM1000 Specific Notes

1. General Notes

----------------------< d019628 04/SEP/1996 >------------------------
ONLY 3.0D:
File OPSFILENAME is not on CD:
In the guide the file OPSFILENAME is mentioned. This file does not exist on the CD. Please substitute OPSFILENAME with OPSFILE during reading the Guide. This file you will find on the CD.

----------------------< d020783 04/NOV/1996 >--------------------
ONLY 3.0E:
Executables of new administrations tools must be extracted:
On page 4-2 (Installing the OPS Administration Extensions), a note mentions a number of files to be copied.
These files are compressed in the file
/sapmnt//exe/INSTALL/SAPDBA.CAR
You have to extract SAPDBA.CAR before you can copy the executables to /sapmnt//exe:
Extracting: cd /sapmnt//exe/INSTALL
/sapmnt//exe/CAR -xvf SAPDBA.CAR

----------------------< d020783 12/DEC/1996 >------------------------
3.0D and 3.0E
Adapt SAPFS.TPL after creating raw link script
After having created the raw link script with R3INST (see section "Preparing the DBB Installation" in Chapter "Common OPS Installa- tion" of the OPS Installation Guide), adapt the file SAPFS.TPL as follows:
1. Exit R3INST
2. Edit the file SAPFS.TPL: Replace the line
OPSFILE = /OPSFILE
with
OPSFILENAME = /OPSFILE
Without this change in SAPFS.TPL, no freelists or freelist groups are created for the tables listed in the file /OPSFILE.

----------------------< d020783 13/DEC/1996 >------------------------
ONLY 3.0D:
Oracle patches required
Installation of Oracle 7.3.2.1 (the Oracle version on the 3.0D OPS Installation CD) requires the following Oracle patches:
bug383534, bug389223, bug393692,
bug375721, bug387086, bug390288, bug401115,
bug382196, bug389032, bug391720, bug419181.
The patches can be downloaded from sapservX:
Directory: /home/ftp/general/3rdparty/oracle/SP2/7321
File: PATCH_7321_SP2.tar.Z

----------------------< d020783 13/DEC/1996 >------------------------
ONLY 3.0E:
SICK error at 1st SAPGUI connect after startup
After startup of an application server, the first SAPGUI trying to connect to this server receives the error message "Inconsistency with database: call transaction SICK".
The user cannot log on. Subsequent attempts to connect are successful.
Cause:
R/3 System suggests that release 3.0E would not be supported with Oracle release 7.3.2.1.0 However, R/3 on Oracle Parallel Server is supported with this database release.
Solution:
The error can be ignored.
The error message is not displayed if you add the following line to the profile DEFAULT.PFL: abap/ignore_icc =2
However, other error messages are also not displayed then. Error messages are still written to the SysLog.

----------------------< d022237 04/JUL/1997 >------------------------
Only 3.1G:
After installing Oracle 7.3.2.3, the startup of the database instance
fails with the following error message:

SVRMGR> startup parallel
LCC-00161: ORACLE error (possible syntax error) parameter [NULL]
ORA-04017: Message 4017 not found; product=RDBMS; facility=ORA

The solution: include the following entry in the ocommon.ora file:
max_dump_file_size=200000


RS 6000 SP Specific Notes
----------------------< d019628 04/SEP/1996 >------------------------
ONLY 3.0D:
New name for the file DEFAULT.CONF
The Filename of the template file for configuring the distributed lockmanager is not DEFAULT.CONF. The rigth name is DEFAULT.CON.

2. RM1000 Specific Notes

Additional key words

OPS