SAPTechno

Note 311308 - INST: 4.6D SAP Basis Inst. on UNIX - Oracle

Header
Version / Date 74 / 2003-12-08
Priority Correction with high priority
Category Installation information
Primary Component BC-INS-UNX Installation Unix
Secondary Components

Summary
Symptom

**********************************************************************
*                                                                    *
*     SAP Basis Installation on UNIX - Oracle                 4.6D  *
*                                                                    *
**********************************************************************

Other terms

R3SETUP CENTRAL.R3S DATABASE.R3S BASIS

Reason and Prerequisites

Additional information and problems discovered after publication of the Installation Guide.

Solution

    DO NOT CHANGE OR ADD INFORMATION TO THIS NOTE !

If you want to contribute something, please send a mail to:
       Boris Zarske      boris.zarske@sap-ag.de

Contents

date    section  description
-----------------------------------------------------------------------
08/DEC/03   2    Linux: Only Installation Oracle 8.1.7. on SuSE SLES8
12/MAY/03   2    Linux: Only for Installation on SuSE SLES8 (Linux)
09/MAY/03   2    Linux (SuSE SLES8): ORA-12705 at DBRESETDATABASE_*_ORA
17/SEP/02   1    Oracle on Compaq Tru64 UNIX 5.x with TruCluster SW
15/MAY/02   2    Linux: Ora 8.1.7 on Red Hat Linux 7.1
25/MAR/02   1    Problems with sapdba_role.sql: DB*.R3S + DATABASE.R3S
23/JAN/02   2    Oracle ERROR 1078 in phase DBCREATEDB_IND_ORA
08/NOV/01   2    Standalone DB Instance: Enter max. 2000 MB for RAM
23/OCT/01   2    RUNINSTALLER: Error in writing to dir. /tmp/OraInstall
03/SEP/01   2    Linux: Ora 8.1.7 on SLES7
06/AUG/01   2    Adapt .sapenv_<hostname>.sh if used (e.g. Korn shell)
16/JUL/01   2    Linux/Ora 8.0.6: Core dump after Ora SW installation
13/JUL/01   1    AIX/Oracle 8.1.7: Requires patches
06/JUL/01   1    HP-UX/Oracle 8.1.7: Install latest linker patch
05/JUL/01   2    Bad magic number for shared library
05/JUL/01   1    Released Oracle Database Versions
18/JUN/01   1    Oracle File System: Dir. for Oracle Client Software
07/JUN/01   1    Installation on raw devices
07/MAY/01   1    Oracle 8.1.x File Systems: Space req. for /oracle
26/MAR/01   1    Solaris: Installing 64-Bit SAP 4.6D Kernel
16/JAN/01   2    AIX/Oracle 8.0.x AND 8.1.x: Run the script rootpre.sh
11/DEC/00   2    Oracle 8.1.6 on LINUX: Relink problem
15/NOV/00   1    Distribution of Components to Disks: Oracle File Sys.
17/OCT/00   2    Installing Oracle with runInstaller: Patchset install.
26/SEP/00   1    Oracle 8.1.x: GUI required on database host
15/SEP/00   3    DBRAW.R3S: Execute DIPGNTAB after the installation
30/AUG/00   2    Oracle 8.1.6: Correction to installation documentation
30/AUG/00   3    ORA-1031: SAPDBA role assignment
30/AUG/00   2    Installing the Oracle DB Software with runInstaller
07/AUG/00   1    Formats of the Installation Documentation
20/JUL/00   3    Oracle 8.0.6 and 8.1.x: Script CHDBPASS does not work
18/MAY/00   1    64-bit AIX with 64-bit Oracle and 64-bit R/3 kernel
16/MAY/00   2    Ora 8.1.6 w/ 64-Bit R3SETUP on 64-Bit HP-UX 11 or Sun
05/APR/00   1    HP-UX 11.0 64-bit + 32-bit Ora: Set SHMMAX < 4GB
29/MAR/00   1    AIX 4.3.3: Error 11: Resource temporarily unavailable
28/FEB/00   2    Sun/Ora 8.0.6: Core dump when calling 'sqlplus'
17/JAN/00   2    Linux/Ora 8.0.5 with main memory > 1GB: Execute script
14/JAN/00   2    Linux/Ora 8.0.5: Installation with orainst
05/JAN/00  1+2  Remake the executable 'sqlplus'
21/DEC/99   1    File requirements of Oracle sapdata file systems
27/OCT/98  1    Set umask of root to 022 or less
10/AUG/98  3    ORA-01031 in stopdb.log
14/JUL/98   1    Two R/3 Systems on the same host
03/MAR/98   1    AIX: Asynchronous I/O must be available
10/JUL/97   1    Compaq: check shmmax if RAM >= 2GB

Sections of this note are:

1      Pre-Installation
2      Installation
3       Post-Installation

1  Pre-Installation


The installation procedure is described in the 4.6D installation documentation 'SAP Basis Installation on UNIX' for your database. You can download the documentation from http://service.sap.com/instguides.

NOTE:
For information on downloading files from sapserv<X>, see SAP Note 19466.

------------------------<C5020924, 17/SEP/2002>------------------------
Oracle on Compaq Tru64 UNIX 5.x with TruCluster SW
If you are installing Oracle on Compaq 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.

------------------------<D019527, 25/MAR/2002>--------------------
Problems with sapdba_role.sql: DB*.R3S + DATABASE.R3S
Before the installation, adapt section [CRSAPDBAROLE_*] in the command files DB*.R3 and DATABASE.R3S:
   OLD: IGNORE_PATTERN=ORA-01918:
   NEW: IGNORE_PATTERN=ORA-01918: ORA-00942: ORA-06512: ORA-01017:
Additionally, you have to use an R3SETUP with make date 11/20/2001 or newer (use command 'R3SETUP -v' to check the make date). A patched R3SETUP is available on sapserv<X> in the 4.6D patch directory.

------------------------<D029035, 13/JUL/2001>--------------------
AIX/Oracle 8.1.7: Required patches
Oracle 8.1.7 requires the following AIX patches:
     IX72696 IX81863 IX85104 IX87313 IX87382 IX89087
     IX89552 IY02407 IY03412 IY05995 IY07276 IY01050
Install these prior to the Oracle installation.

------------------------<D029385, 06/JUL/2001>--------------------
HP-UX/Oracle 8.1.7: Install latest linker patch
To prevent link problems, ask your hardware partner for the latest linker patch and install it. See SAP Note 399610 for more information.

------------------------<D029035, 05/JUL/2001>--------------------
Released Oracle Database Versions
Although the installtion procedure for several Oracle Database versions may be contained in the installation documentation, not all of these Oracle Database versions are released for every operating system.

------------------------<D019527, 21/DEC/1999>---------------------
File requirements of Oracle sapdata file systems for 4.6D SAP Basis System
See the file DBSIZE.TPL on the Export CD for exact space requirements of each sapdata file system and overall space requirements..

------------------------<D029035, 18/JUN/2001>--------------------
Oracle File System: Dir. for Oracle Client Software
The listed directory for the Oracle client software (installation
documentation --> Installation Planning --> Distribution of Components
to Disks --> Oracle File Systems) depends on the version of the
Oracle client software for your operating system. The used Oracle
client software version is contained in the name of the file
<Kernel CD>\UNIX\<Operating System>\OCL<Client_Version>.CAR.

------------------------<D029035, 07/JUN/2001>--------------------
Installation on raw devices
If you want to install Oracle/UNIX on raw devices, see SAP Note 145654.

------------------------<D029035, 07/MAY/2001>--------------------
Oracle 8.1.x File Systems: Space requirement for /oracle

    1. Additional to the space requirements listed in the installation documentation (version from July 2000, 'SAP Basis Installation on UNIX: Oracle Database' --> Installation Planning --> Distribution of Components to Disks --> Oracle File Systems) 50 MB of free disk space is required for the Oracle Base directory /oracle.
    2. Space requirement for /oracle/stage/817_32 or _64 (Installation and upgrade directory for database software - staging area) is 1600 MB for Oracle 8.1.7.
    3. Space requirement for $ORACLE_HOME (/oracle/<SAPSID>/81<x>_<xy>) is 2 GB.


------------------------<D026178, 26/MAR/2001>--------------------
Solaris: Installing 64-Bit SAP 4.6D Kernel
To install Oracle 8.1.6 with 64-Bit SAP 4.6D Kernel on Sun Solaris, proceed as follows:

    1. Install the 32-bit SAP Kernel with 64-bit Oracle Server Software.
    2. Perform a kernel switch from 32 bit to 64 bit (see SAP Note 353110).


------------------------<D019527, 15/NOV/2000>--------------------
Distribution of Components to Disks: Oracle File System
Create /oracle/<SAPSID> as file system, no matter if you are installing Oracle 8.0.x or 8.1.x. It should not reside in the root directory.

------------------------<D019527, 26/SEP/2000>--------------------
Oracle 8.1.x: GUI required on database host
To be able to install Oracle 8.1.x a graphical user interface (GUI) is required for the database installation with runInstaller.

------------------------<D029035, 07/AUG/2000>--------------------
Formats of the Installation Documentation
Currently, the documentation SAP Basis Installation on UNIX: Oracle Database is only delivered as PDF file.

------------------------<D019527, 18/MAY/2000>--------------------
64-bit AIX with 64-bit Oracle and 64-bit R/3 Kernel
Due to a missing Oracle patch, you can not install 64-bit AIX with 64-bit Oracle Client Software 8.0.5 and a 64-Bit R/3 Kernel. If you want to use the 64-Bit R/3 Kernel, proceed as follows:

    1. Install the 32-bit R/3 Kernel with 64-bit Oracle Server Software.
    2. Perform a kernel switch from 32 bit to 64 bit (see SAP Note 318846).
    3. Install the 64-bit Oracle Client Software 8.0.5 according to SAP Note 303238.


------------------------<D029035, 05/APR/2000>--------------------
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.

------------------------<D028292, 29/MAR/2000>--------------------
AIX 4.3.3: error 11: Resource temporarily unavailable
If you encounter the above error during the installation, see SAP Note 210385 for more information.

------------------------<D019527, 05/JAN/2000>---------------------
Remake the executable 'sqlplus'
After orainst has finished, remake the executable 'sqlplus' according to SAP Note 97953. Then, continue with the installation.
Reliant only: Make sure patch set 8.0.5.2.1 or higher is installed
before remaking 'sqlplus'.

------------------------<D020894, 03/MAR/1998>---------------------
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 stated in the installation guide, section 'Installing the Oracle DB Software with orainst' (Oracle 8.0.x) and as prompted by runInstaller (Oracle 8.1.x) respectively.

------------------------<d022860, 14/JUL/1998>---------------------
Two R/3 Systems on the same host
If you want to install two R/3 Systems on the same host, please see
note 98252.

------------------------<d023322, 27/OCT/1998>---------------------
Set umask of root to 022 or less
During creation of the database, a file temporary orascr.sql is created by root and later accessed by ora<sapsid>.
If root's umask is set to a value higher than 022, this results in failure of the steps that connect to the database because ora<sapsid> cannot access orascr.sql.
The log file contains entries like:
  MGR-01507: unable to open file "orascr.sql"
that are output by earlier steps.
If this happens, proceed as follows:
1. Set root's umask to 022.
2. Delete the line STATUS=OK from the section DBRESETDATABASE_IND_ORA
  and all subsequent steps in the command file.
   The sequence is defined in the EXE section.
3. Restart R3SETUP.

------------------------<d023322, 10/JUL/1997>---------------------
Compaq 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/<SID>/dbs/init<SID>.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 the documentation
R/3 Installation on UNIX, section 'OS-Dependendent Installation Steps
on UNIX'.

In the following, corrections to sections in command files (*.R3S) are listed in alphabetical order and together with the date as listed in the table of conntents, a short description of the error and a solution.

DBR3LOADEXEC_*


13/MAY/1998 (d023322)
Number of parallel R3load processes: Snapshot too old
If you specify more than 3 (Solaris: 1) parallel R3load processes, the error 'Snapshot too old' may occur. In this case, just restart R3SETUP to resolve the error.
The number of parallel R3load processes is prompted by R3SETUP. It can also be specified in the command file (key PROCESSES in section DBR3LOADEXEC_IND_IND).

2 Installation


------------------------<D035521, 08/DEC/03>--------------------------
Linux: Only Installation Oracle 8.1.7. on SuSE SLES8
Symptom:
The Oracle installation tool "RUNINSTALLER" may have problems to start. Some java processes seem to produce heavy load on the CPU, but no window will appear.
Solution:
In this case it may help to download JDK 1.1.8 from SuSE. A description of the solution can be found at:
http://www.suse.de/en/business/certifications/certified_software/ \
        oracle/db/817_sles8.html
Please search on this web page for "Java trouble".

------------------------<C5014427, 12/MAY/03>--------------------------
Linux: Only for Installation on SuSE SLES8 (Linux)

  • The database software has to be:
    • Oracle release 8.1.7.4 (only up to SAP Kernel 4.6D; do not forget to install Oracle Bug Fix 1467074, also known as glibc-2.1.3-stubs patch, see SAP Note 362060).
    • 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<sid>" and "<sid>adm". Otherwise, you may get an "Error 46 initializing SQL*Plus" when starting "sqlplus".


------------------------<C5014427, 09/MAY/03>--------------------------
Linux (SuSE SLES8): ORA-12705 at DBRESETDATABASE_*_ORA
The installation of SAP software stops at phase DBRESETDATABASE_IND_ORA with the following error:
   ORA-12705: invalid or unknown NLS parameter value specified
The problem is caused by the setting of the environment variable ORA_NLS33 regarding the user "root", who called R3SETUP. Before R3SETUP can be restarted, this "root" user has to change the value of ORA_NLS33 according to the database version:

  • Oracle 8.1.7.4:
    export ORA_NLS33=/oracle/<SID>/817_32/ocommon/nls/admin/data
  • Oracle 9.2.x:
    export ORA_NLS33=/oracle/<SID>/920_32/ocommon/nls/admin/data


------------------------<C5014427, 15/MAY/02>--------------------------
Linux: Ora 8.1.7 on Red Hat Linux 7.1
To install an SAP System with Oracle 8.1.7 on Red Hat Linux 7.1, the following peculiarities apply (otherwise, no installer window will appear):

    1. Before installing the Oracle database software with RUNINSTALLER:
      a) Make sure (as user root) that the following RPM packages are installed, which can be found on the Red Hat Linux 7.1 CDs:
      compat-libstdc++-6.2-2.9.0.14
      compat-glibc-6.2-2.1.3.2
      compat-libs-6.2-3
      compat-egcs-6.2-1.1.2.14
      b) Enter: cd /oracle/stage/817_32/Disk1/SAP
      c) Edit the script "RUNINSTALLER" by adding at the beginning of the file (right after "#!/bin/csh") the lines:
      setenv LD_ASSUME_KERNEL 2.2.5
      setenv LDEMULATION elf_i386_glibc21
      setenv GCC_EXEC_PREFIX /usr/i386-glibc21-linux/lib/gcc-lib/
      d) Start the Oracle database installation as user ora<DBSID> by running RUNINSTALLER.
      e) The installation will stop with the message "Error in invoking target install of makefile /oracle/QO1/817_32/ctx/lib/ins_ctx.mk".
      First, import the Oracle patch for bug 1897195. Get the patch file "p1897195_8171_LINUX.zip" via FTP from sapserv/general/3rdparty/oracle/LINUX/8.1.7/81710/Red_Hat7.1/ and install it as user ora<DBSID> according to README.txt (part of the patch file).
      f) Second, install a patch for the compatibility with GLIBC 2.2.2. Get the patch file "glibc-2.1.3-stubs.tar.gz" via FTP from sapserv/general/3rdparty/oracle/LINUX/8.1.7/81710/Suse7.x/ and install it as user ora<DBSID> according to README.stub (part of the patchfile).
      g) Third, relink ctxhxx manually as user ora<DBSID> using the following commands:
      cd /oracle/QO1/817_32/ctx/lib
      make -f env_ctx.mk ctxhxx
      h) Go on with the RUNINSTALLER.
    2. Edit the script "/oracle/stage/817_32/Disk1/runInstaller" by adding at the beginning of the file (right after "#!/bin/sh") the lines:
    export LD_ASSUME_KERNEL=2.2.5
    export LDEMULATION=elf_i386_glibc21
    export GCC_EXEC_PREFIX=/usr/i386-glibc21-linux/lib/gcc-lib/
    3. Install the Oracle 8.1.7.2 patch as user ora<DBSID> by running /oracle/stage/817_32/Disk1/runInstaller.
    4. Proceed with the standard installation procedure.


-------------------------<D029035, 23/JAN/02>-------------------------
Oracle ERROR 1078 in phase DBCREATEDB_IND_ORA
If Oracle error 1078 occurs during the installation in phase
DBCREATEDB_IND_ORA, see SAP Note 372205.

-------------------------<D029035, 08/NOV/01>-------------------------
Standalone DB Instance: Enter max. 2000 MB for RAM
If you are installing a Standalone Database instance, make sure not to
enter more than 2000 MB when R3SETUP prompts for the RAM for the
database instance.

-------------------------<D029035, 22/OCT/01>-------------------------
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 rerun the installer.

------------------------<C5014427, 03/SEP/01>--------------------------
Linux: Ora 8.1.7 on SLES7
To install an SAP System with Oracle 8.1.7 on SLES7 (SuSE Linux Enterprise Server 7), the following peculiarities apply (otherwise, a segmention violation error, a Java error or an ORA-03113: end-of-file on communication channel may occur):

    1. Before installing the Oracle database software with RUNINSTALLER:
      a) Enter: cd /oracle/stage/817_32/Disk1/SAP
      b) Edit the script "RUNINSTALLER" by adding at the beginning of the file (right after "#!/bin/csh") the lines:
      unsetenv LANG
      unsetenv LC_CTYPE
      unsetenv RC_TYPE
      unsetenv NLS_LANG
      unsetenv LC_COLLATE
      c) Start the Oracle database installation as user ora<DBSID> by running RUNINSTALLER.
    2. Immediately after the Oracle database software installation with RUNINSTALLER, install a patch for the compability with GLIBC 2.2.2. Get the patch "glibc-2.1.3-stubs.tar.gz" via FTP from sapserv<X>/general/3rdparty/oracle/LINUX/8.1.7/81710/Suse7.x/ and install it according to the README (part of the file).
    3. Proceed with the standard installation procedure.


------------------------<D019527, 06/AUG/2001>--------------------
Adapt .sapenv_<hostname>.sh if used (e.g. Korn shell)
The file .sapenv_<hostname>.sh created for users ora<dbsid> and <sapsid>adm in the home diretory has to be adapted if you use it (that is, for example, if you are using the Korn shell):

OLD: SHLIB_PATH=...
NEW: SHLIB_PATH=...; export SHLIB_PATH

OLD: LD_LIBRARY_PATH=...
NEW: LD_LIBRARY_PATH=...; export LD_LIBRARY_PATH

OLD: LIBPATH=...
NEW: LIBPATH=...; export LIBPATH

------------------------<C5014427 16/JUL/01>---------------------
Linux/Ora 8.0.6: Core dump after Ora SW installation
If after you install the Oracle software (including executable links) each of the executables (for example, svrmgrl) terminate with a core dump, see SAP Note 380022 and 373203.

------------------------<D029035, 05/JUL/2001>--------------------
Bad magic number for shared library
If this error occurs, see SAP Note 335515.

------------------------<D019128, 16/JAN/2001>--------------------
AIX/Oracle 8.0.x AND 8.1.x: Run the script rootpre.sh
Run the script rootpre.sh no matter if you are installing Oracle 8.1.x or Oracle 8.0.x.
In the installation documentation (version from July 2000), section 'Starting the Script rootpre.sh (AIX only)', the note box 'This section is not valid if you install Oracle 8.1.6.' is wrong.

------------------------<C1016615, 11/DEC/2000>--------------------
During Oracle 8.1.6 install. on LINUX Oracle relink problem may occur
If the relink problem persists, the correct way to eliminate the reason is ONLY to upgrade to Linux enterprise kernel 2.2.16-22 minimum (see SAP Notes 195603, 171356 and 359566).
If there is no way to get this patch kernel at your location via sapserv<X>, you may circumvent the problems by relinking manually as oracle user with the following commands:
cd $ORACLE_HOME/network/lib
make -f ins_net_client.mk ntcontab.o
make -f ins_net_client.mk nnfgt.o
gennfgt
genclntsh
cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk install
Upgrade to the Linux-kernel mentioned above as soon as possible. Otherwise all scripts without #!/bin/sh continue to show up with intermittent bus errors.

------------------------<D029035, 17/OCT/2000>--------------------
Installing Oracle with runInstaller: Patchset installation
Perform the patchset installation described in SAP Note 216889 only until you have to exit the installer as the subsequent steps are part of the standard installation procedure.

------------------------<D029035, 30/AUG/2000>--------------------
Oracle 8.1.6: Correction to installation documentation (July 2000)
Delete in section 'Installing the Oracle DB Software with runInstaller' the following line:
8. Log on with the user ora<sapsid> and enter the command:    $ORACLE_HOME/bin/lsnrctl start

------------------------<D029035, 30/AUG/2000>--------------------
Installing the Oracle DB Software with runInstaller
If the user ora<sapsid> does not have write authorization for the directory /oracle , log on to your system with the user root and enter the command: chmod 777 /oracle

------------------------<D029035, 16/MAY/2000>--------------------
Installing 64-Bit Ora 8.1.6 with 64-Bit R3SETUP on 64-Bit HP-UX 11 or 64-Bit Sun
If you install Oracle 8.1.6 on 64-Bit HP-UX 11 or 64-Bit Sun, you must NOT set the library path environment variable SHLIB_PATH (HP-UX) or LD_LIBRARY_PATH (Sun) of user root before starting R3SETUP as described in the installation documentation.
Additionally, remove SHLIB_PATH or LD_LIBRARY_PATH from files .dbenv_<host>, .(c)sh and .sapenv_<host> of users ora<sid> and <sid>adm: In the corresponding CASE branch of the files, insert comment signs (#) to all lines except the last line (breaksw).
Otherwise, R3SETUP aborts during the first call of sqlplus.

------------------------<D029035, 28/FEB/2000>--------------------
Sun/Ora 8.0.6: Core dump when calling 'sqlplus'
If a client shared library does not correspond to 8.0.6, a core dump occurs when calling 'sqlplus' (only as user <sid>adm). In this case, perform the follwing steps:

    1. Log on as user ora<sid>.
    2. Enter:
    cd sqlplus/lib
    cp env_sqlplus.mk env_sqlplus.mk.save
    3. Edit the file env_sqlplus.mk. Change the line
    TTLIBS=$(LLIBCLNTSH) $(STATICTTLIBS) to
    TTLIBS=$(STATICTTLIBS) $(LLIBCLNTSH)
    4. Enter:
    make -f ins_sqlplus.mk install

This guarantees that sqlplus uses the static libraries first and the core no longer occurs.

------------------------<D019527, 17/JAN/2000>--------------------
Linux/Ora 8.0.5 with main memory > 1GB: Execute script
On a host with Linux and more than 1 GB main memory, execute the script ORASGA.SH as user 'dba' after the installation of the Oracle 8.0.5 software with orainst has finished. The script is located on the Kernel-CD in directory /UNIX/LINUX_32/.

------------------------<D029035, 14/JAN/2000>--------------------
Linux/Ora 8.0.5: Installation with orainst
When installing the Oracle 8.0.5 software with orainst, consider the following differences from the standard installation procedure:

  • Deselect the ONLINE TEXT VIEWER, as it does not exist for Linux. Otherwise, an error occurs that file oraview.vrf is missing.
  • Ignore messages about the ULIMIT paramter.

In the following, corrections to sections in command files (*.R3S) are listed in alphabetical order and together with the date as listed in the table of conntents, a short description of the error and a solution.

DBCREATEDB_*


17/JAN/2000 (d019527)
If error ORA-27123 occurs on a host with Linux and more than 1GB,
execute the script <Kernel-CD>/UNIX/LINUX_32/ORASGA.SH as user 'dba'.

DBCRSAPR3_*


05/JAN/2000 (d019527)
Execution of 'sqlplus' aborts with error message:
ORA-1006: bind variable does not exist
Remake the executable according to SAP Note 97953.

3 Post-Installation


------------------------<D019527, 15/SEP/00>--------------------
DBRAW.R3S: Execute DIPGNTAB after the installation
Due to the missing of step [DIPGNTAB_IND_IND] in the command file DBRAW.R3S, execute DIPGNTAB after the installation as follows:

    1. Log on as user <sapsid>adm.
    2. Enter:
    $ cd <INSTDIR>
    3. Enter:
    $ dipgntab -fprot dipgntab@SAPSYSTEMNAME@.log -rwr40 -srctt DDNTT \
         -srctf DDNTF -dsttt DDNTT -dsttf DDNTF -ttonly TT


------------------------<I010757, 30/AUG/00>--------------------
ORA-1031: SAPDBA role assignment
If after the installation update database statistics via DB13 could not be carried due to Oracle error ORA-1031 (insufficient privileges), apply SAP Note 134592 (SAPDBA: Importing the SAPDBA role).

-------------------------<D019527 20/JUL/00>--------------------------
Oracle 8.0.6 and 8.1.x: Script CHDBPASS does not work
If you want to use script CHDBPASS with Oracle 8.0.6 or 8.1.x, see SAP Note 319211.

-------------------------<D022860 10/AUG/98>--------------------------
"ORA-01031: insufficient privileges" in stopdb.log
If this error message appears in the log file stopdb.log, check if:

    1. The user <sapsid>adm is a member of the group oper.
    2. The directories $ORACLE_HOME and $ORACLE_HOME/dbs have the permissions 755.


Affected Releases
Software Component Release From Release To Release And subsequent
SAP_BASIS4646D46D

Related Notes
372205ERROR 1078 in phase DBCREATEDB_IND_ORA
335515Bad magic number for shared library
165245Distributing Oracle Control files on hard disks
145654Installing SAP Systems on UNIX/Oracle with raw devices
19466Downloading SAP kernel patches