Note 156548 - Released operating systems SAP kernel 4.6x ORACLE

时间：2021-10-15 16:56:44

Summary

Symptom

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

Other terms

SAP Web AS 6.20, SAP Web AS 6.40, 6.20/6.40 Patch Collection (Edition July 2007), 6.20/6.40 based products Installation Master, Unix, Installation

Reason and Prerequisites

You want to install an SAP system on UNIX using the "6.20/6.40 based products Installation Master" DVD.
The following editions are available:

  • NEW! "6.20/6.40 based products Installation Master(Edition May 2008)" DVD (Material Number 51033746).
  • "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

Contents
  1. 1. General(1)
    1. a) General - Edition May 2008 (Material Number 51033746) (1a)
    1. b) General - Edition July 2007 (Material Number 51032936) (1b)
  1. 2. Pre-Installation(2)
  1. 3. Installation(3)
  1. 4. Post-Installation(4)
  1. 5. High Availability(5)


The "General" section contains general informations about how to obtain the "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:

  • ABAP: all ABAP systems
  • ABAP - <component>: specific ABAP component,

           For example, "ABAP-ECC"

  • Java: all Java systems (Web AS Java and all additional Java components)
  • Java Add-In: Java Add-In installation to an existing ABAP system
  • ADS: Adobe Document Services
  • ERP / CRM Java Components: <business suite solution>-<Java component>:

           For example: "ERP-XSS", "CRM-IC".

           You find the key for these prefixes in the respective Java components installation guide.



Date      Section   Description
-----------------------------------------------------------------------
03/JUNE/08   4      ABAP, ABAP+Java: Errors in transaction ST11 (error log files) every time the SAP system is started.
25/APR/08    3      System messages: values for shared memory parameters are not sufficient
31/JUL/07    2      OS users: do not delete shell initialization scripts
26/OCT/06    2      Java: Update SCSCLIENT64UC.SAR on the Java DVD
17/OCT/06    2      Usage of NFS-V4 file system: create OS users manually on NFS server
25/AUG/06    4     EP: SP11 required installation
22/AUG/06    3     KMC: Error "Java Engine did not reach state "Start Application"
18/AUG/06    3     SAP BW 3.1: Incorrect index entries
29/MAY/06    5     Install Replicated Enqueue Server for HA
04/APR/06    3     Error FSL-02015  Node <path> does not exist
06/FEB/06    2     ADS: Running ADS with non-supported platforms
23/JAN/06    4     Java: Inst. Guide correction: "Installing the SAP
License"
16/JAN/06    4     ABAP: Unable to perform job
COLLECTOR_FOR_PERFORMANCEMONITOR
13/JAN/06    2    Inst.Guide correction: SAP Note 5324 obsolete
05/DEC/05    3    Return value of function /usr/sbin/usermod - <option>
<sapsid>adm is 8
05/DEC/05    4     ABAP: UNICODE conversion error
03/AUG/05    3     Java Add-In: Dialog Instance Finalization
28/JUN/05    3     SAPinst GUI crashes "guiengine: no GUI connected"
21/JUN/05    5     ADS: Change startup mode of IIOP service
02/JUN/05    2     AIX 64 bit: PATH must point to JDK/JRE 64 bit
22/APR/05    4     Java: Linux X86_64: Cannot start SLD
04/APR/05    2     ADS: Additional OS Requirements
10/MAR/05    3     Java: Solaris 10 / AIX 5.3: SAPinst aborts with error
21/FEB/05    4     ERP-XSS: Errors in callSdmViaSAPinst.log
09/FEB/05    2     Java: Instance profiles of already installed SAP
systems
08/FEB/05    3     Java: Network Adapter could not establish the
connection
08/FEB/05    4     SCM 4.0/SCM 4.1: BW-specific post-installation steps
04/FEB/05    3     SAPinst GUI does not appear after restart
03/Feb/05    4     CRM-IC: IC requires SAF to be installed
01/FEB/05    4    ABAP (ECC): mySAP ERP new general ledger:
activation with new customers
31/JAN/05    3     ERP-Biller Direct: pop-up requesting post-processing
steps
27/JAN/05    3     Java: SDM server is stopped after the installation
23/DEC/04    3     Java: AIX only: bootstrap error
19/DEC/04    3     Error out of memory
19/DEC/04    3     Java: Error while stopping the SDM server
13/DEC/04    4     Java: Problems when shutting down Web AS Java
09/DEC/04    4     Java: JDI: enhance maximum memory for java compiler
08/DEC/04    4     Java: Timeout during start up of Web AS Java
26/NOV/04    4    Java: Strong crypto deactivated after dialog instance
installation
26/NOV/04    3     ADS: JStartup Framework error in error log
can be ignored
23/NOV/04    2      Additional Java Components : Java Startup parameter
19/NOV/04    3      ADS: Error com.ibm.db2.jcc.c. DisconnectException (on DB6 only)
13/SEP/04    3      SAPinst breaks during an RFC call with "time-out"
27/AUG/04    4      Distributed installation: Check /etc/hosts.equiv
                  and SM59
06/AUG/04    3     Java: Field: J2EE Engine Parameters: number of J2EE
Servers
07/JUN/04    3     HP Tru64: Error FSH-0006 while creating
group sapsys
19/APR/04    2     /ti and /network no longer available on SMP
02/AUG/04    2      ABAP: Choose different SID for standalone gateway
20/JUL/04    4      Running SAPinst: separate inst_dir for each instance
09/JUL/04    3      Freespace check error
13/APR/04    4      Java Add-In: Changing parameters with RZ10 or RZ11
17/MAR/04    5      Missing service entry for SLD gateway
02/MAR/04    5      Configure not more than 99 work processes per server
19/FEB/04    4      Java: OutOfMemoryError
04/FEB/04    4      Java: Additional java components cannot be
accessed after redeployment or upgrade of Web AS Java
31/OCT/03    2      Unicode: Also see SAP Note 544623
24/SEP/03    2      Linux/J2EE: Parameters for Red Hat Ent. Linux 2.1
19/AUG/03    4      SAPinst prompts to manually stop the SCS instance
13/AUG/03    4      Java Add-In only: Run script saproot.sh
25/JUN/03   3+4     SAPinst GUI does not get displayed correctly
19/FEB/03    2      Installation on SuSE SLES8 (Linux) - IBM Java2-SDK
18/DEC/02    4      SAP License: System number must be 18 characters
15/OCT/02    4      64-Bit AIX 5.1: SAPinst GUI causes segment. faults
24/JUN/02    4      HP-UX: Startup problems of SAP Java Connector (JCo)
18/OCT/01    5      ABAP+Java Add-In only: sapcpe in an High-Availability Environment
10/AUG/01    3      NFS mounts: SAP processes abort with signal 9
07/MAR/01    3      Linux: Relevant SAP Note for installation on Linux
09/JAN/01    4      Incomplete path in .sapenv_<hostname>.sh
17/NOV/00    4      HP Tru64: SAP System does not start
30/OCT/00    4      HP Tru64 5.x: Replace saposcol after the inst.
18/OCT/00    4      Linux: Replace saposcol after the installation
16/JUN/00    2      Linux: Errors during exectution of shell scripts
16/MAY/00    4      ABAP+Java Add-In: Import Base, ABA Support Packages
19/JAN/00    4      ABAP+Java Add-In: HP Tru64: Warning during profile
check can be ignored


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

1 General

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

  • If you want to install an SAP system on UNIX using the "6.40 based products Installation Master(Edition May 2008)" DVD (Material Number 51033746), go to section "a) General - Edition May 2008 (Material Number 51033746)".
  • If 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), go to section " b)  General - Edition July 2007 (Material Number 51032936)".


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

a)  General - Edition May 2008 (Material Number 51033746)

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

1.) Products that you can install with DVD "6.20/6.40 based products Installation Master(Edition May 2008)" (Material Number 51033746)

You can use the "6.20/6.40 based products Installation Master(Edition July 2007)" (Material Number 51033746) to install the following SAP systems:

  • mySAP CRM 4.0 SR1
    • ABAP System (SAP CRM Server)
    • Additional CRM Java Components
  • mySAP ERP 2004 SR1
    • ABAP System (SAP ECC Server)
    • Additional ERP Java Components
  • SAP R3E 4.7, Extension Set 2 SR1
    • ABAP System
  • mySAP SCM 4.1
    • ABAP System (SAP SCM Server)
  • mySAP SRM 4.0 SR1
    • ABAP System (SAP SRM Server)
    • Additional SRM Java Components
  • SAP Solution Manager 3.2 SR1
    • ABAP System
  • SAP NetWeaver '04 SR1
    • ABAP System (SAP Web AS ABAP 6.40 SR1)
    • Java System (SAP Web AS Java 6.40 SR1)
    • Search and Classification (TREX)
    • Portal Platform
    • Content Management & Collaboration (KMC)
    • Adobe Document Services (ADS)
    • BI UDI Java Components
    • Exchange Infrastructure (XI)

2.) How to obtain DVD "6.20/6.40 based products Installation Master(Edition May 2008)" (Material Number 51033746)

You can either order the "6.20/6.40 based products Installation Master(Edition May 2008)" (Material number 51033746) directly from SAP, or you can download it from the SAP Software Distribution Center using the following path:
http://service.sap.com/swdc --> Download --> Installations and Upgrades --> Entry by Application Group --> SAP NetWeaver --> SAP NETWEAVER --> SAP NETWEAVER 04 --> Installation and Upgrade --> <OS> --> <Database> --> Installation Master 6.20/6.40 Linux on <OS>
If you cannot find the DVD using this path, you can also search for the DVD as follows:

    1. a) Go to "http://service.sap.com/swdc --> Download --> Installations and Upgrades --> Search for Installations and Upgrades"
    1. b) Enter "
51033746" as search term.

3.) Required installation documentation: Management 4.0 SR1 on <platform> : <database>" available on SAP Service Marketplace at: http://service.sap.com/instguides --> Installation & Upgrade Guides --> mySAP Business Suite Applications --> mySAP CRM --> SAP CRM 4.0 --> General and Technical Installation Guides --> CRM 4.0 SR1 Installation on <platform> - <database>
  • mySAP CRM 4.0 SR1
    • SAP CRM Server 4.0 SR1
      Use the documentation "Installation Guide - SAP Customer Relationship Management 4.0 SR1 on <platform> : <database>" available on SAP Service Marketplace at: http://service.sap.com/instguides --> Installation & Upgrade Guides --> mySAP Business Suite Applications --> mySAP CRM --> SAP CRM 4.0 --> General and Technical Installation Guides --> CRM 4.0 SR1 Installation on <platform> - <database
    • Java Components for mySAP CRM 4.0 SR1
      Use the documentation "Installation Guide - Java Components for SAP Customer Relationship Management 4.0 SR1" available on SAP Service Marketplace at: http://service.sap.com/instguides --> Installation & Upgrade Guides --> mySAP Business Suite Applications --> mySAP CRM --> SAP CRM 4.0 --> General and Technical Installation Guides --> Java Components for CRM 4.0 SR 1
  • mySAP ERP 2004 SR1
    • SAP ECC Server 5.0 SR1
      Use the documentation "Installation Guide - SAP ERP Central Component on <O S> : <database>" available on SAP Service Marketplace at:
      http://service.sap.com/instguides --> Installation & Upgrade Guides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2004 --> SAP ECC 5.0 --> Installation Guides of SAP ECC 5.0 SR1
    • Java Components for mySAP ERP 2004 SR1
      Use the documentation "Installation Guide - Java Components for
      mySAP ERP 2004 SR1" available on SAP Service Marketplace at:
      http://service.sap.com/instguides --> Installation & Upgrade Guides -->
      mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2004 -->
      ERP Java Components
  • SAP R3E 4.7, Extension Set 2 SR1
    Use the documentation " SAP R/3 Enterprise on <platform>:<database>  - Using SAP R/3 Enterprise Core 4.70, SAP R/3 Enterprise Extension Set 2.00, Service Release 1", available on SAP Service Marketplace at:
    http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP Components --> SAP R/3 --> SAP R/3 Enterprise --> SAP R/3 Enterprise Core 4.70 / Ext. Set 2.00 (SR1) http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP SCM --> Using SAP SCM 4.1 Server
  • mySAP SCM 4.1
    Use the documentation "Installation Guide - SAP SCM 4.1 Server on <platform>:<database>  available on SAP Service Marketplace at http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP SCM --> Using SAP SCM 4.1 Server
  • mySRM 4.0 SR1
    • SAP SRM Server 5.0 SR1
      Use the documentation "Installation Guide - SAP Supplier Relationship Management Server 5.0 SR1 on <O S>: <database>" available on SAP Service Marketplace at: http://service.sap.com/instguides --> Installation & Upgrade Guides --> mySAP Business Suite Applications --> mySAP SRM --> Using SAP SRM Server 5.0 --> Installation Guides for SAP SRM Server 5.0
    • Java Components for mySAP SRM 4.0 SR1 (Live Auction Cockpit)
      Use the documentation "Installation Guide - Live Auction Cockpit 2.0" Customer Relationship Management 4.0 SR1" available on SAP Service Marketplace at: http://service.sap.com/instguides --> Installation & Upgrade Guides --> mySAP Business Suite Applications --> mySAP SRM --> Using SAP SRM Server 5.0
  • SAP Solution Manager 3.2 SR1
    Use the documentation "Component Installation Guide - SAP Solution
    Manager 3.2 on <O S> : <database>" available on SAP Service Marketplace
    at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP Components --> SAP Solution Manager --> Release 3.2
  • SAP NetWeaver '04 SR1
    • SAP Web AS ABAP 6.40 SR1
      Use the documentation "Component Installation Guide - SAP Web Application Server ABAP on <O S> : <database>", available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> SAP Web AS --> SAP Web AS 6.40 SR1 and Related Documentation
    • SAP Web AS Java 6.40 SR1
      Use the documentation "Component Installation Guide - SAP Web Application Server Java on <O S> : <database>", available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> SAP Web AS --> SAP Web AS 6.40 SR1 and Related Documentation
    • TREX
      Use the documentation "Installation Guide - Search and Classification (TREX) <release>", available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> Cross NW
    • Enterprise Portal
      Use the documentation "Installation of SAP Enterprise Portal on Web AS 6.40 EP 6.0 <S P> ", available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> SAP EP
    • Knowledge Management & Collaboration
      Use the documentation "Installation of SAP Enterprise Portal on Web AS 6.40 EP 6.0 <S P> ", available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> SAP EP
    • Adobe Document Services
      Use the documentation "Installation Guide - Adobe Document Services for SAP Web Application Server 6.40 SR1 ", available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> SAP Web AS --> SAP Web AS 6.40 SR1 and Related Documentation
    • BI UDI Java Components
      Use the documentation "Installation Guide - SAP Business Warehouse 3.5 SR1, available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> SAP BW
    • Exchange Infrastructure

                    Use the documentation "Installation Guide - SAP Exchange Infrastructure 3.0 SR1, available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> SAP XI

4.) Platform and Database Restrictions:

6.20/6.40 Patch Collection Installation on UNIX (Edition May 2008) is not released for the following OS / DB combinations:

  • HPUX / DB6 V9.5
  • Linux I386 / DB6 V9.5
  • Linux IA64 / DB6 V9.5
  • Linux IA64 / DB6 V9.1 (CRM 4.0 SR1 only!)
  • Solaris X64


See also the database-specific SAP Notes which are attached to this SAP Note for supported versions of your database.


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

b)  General - Edition July 2007 (Material Number 51032936)

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

1.) Products that you can install with DVD "6.20/6.40 based products Installation Master(Edition July 2007)" (Material Number 51032936)

You can use the "6.20/6.40 based products Installation Master(Edition July 2007)" (Material Number 51032936) to install the following SAP systems:

  • SAP BW 3.1
  • mySAP CRM 4.0 SR1
    • ABAP System (SAP CRM Server)
    • Additional CRM Java Components
  • mySAP ERP 2004 SR1
    • ABAP System (SAP ECC Server)
    • Additional ERP Java Web Application Components
  • SAP R3E 4.7, Extension Set 2 SR1
    • ABAP System
  • mySAP SCM 4.0
    • ABAP System (SAP SCM Server)
  • mySAP SCM 4.1
    • ABAP System (SAP SCM Server)
  • mySAP SRM 4.0 SR1
    • ABAP System (SAP SRM Server)
    • Additional SRM Java Components
  • SAP Solution Manager 3.2
    • ABAP System
  • SAP NetWeaver '04 SR1
    • ABAP System (SAP Web AS ABAP 6.40 SR1)
    • Java System (SAP Web AS Java 6.40 SR1)
    • TREX
    • Portal Platform
    • Knowledge Management & Collaboration (KMC)
    • Adobe Document Services (ADS)
    • BI UDI Java Components
    • Exchange Infrastructure (XI)

2.) How to obtain DVD "6.20/6.40 based products Installation Master(Edition July 2007)" (Material Number 51032936)

You have to order the "6.20/6.40 based products Installation Master(Edition July 2007)" (Material number 51032936) directly from SAP. You cannot download it any longer from the SAP Software Distribution Center at: http://service.sap.com/swdc


3.) Required installation documentation:
  • SAP BW 3.1
    Use the documentation "Installation Guide - SAP Business Warehouse 3.5 ,
    available on SAP Service Marketplace at
    http://service.sap.com/instguides --> Installation & Upgrade Guides -->
    SAP NetWeaver --> Release '04 --> Installation --> SAP BW
  • mySAP CRM 4.0
    • SAP CRM Server 4.0:
      Use the documentation "Installation Guide - SAP Customer Relationship Management 4.0 SR1 on <platform> : <database>" available on SAP Service Marketplace at: http://service.sap.com/instguides --> Installation & Upgrade Guides --> mySAP Business Suite Applications --> mySAP CRM --> SAP CRM 4.0 --> General and Technical Installation Guides --> CRM 4.0 SR1 Installation on <platform> - <database>
  • mySAP CRM 4.0 SR1
    • SAP CRM Server 4.0 SR1
      Use the documentation "Installation Guide - SAP Customer Relationship Management 4.0 SR1 on <platform> : <database>" available on SAP Service Marketplace at: http://service.sap.com/instguides --> Installation & Upgrade Guides --> mySAP Business Suite Applications --> mySAP CRM --> SAP CRM 4.0 --> General and Technical Installation Guides --> CRM 4.0 SR1 Installation on <platform> - <database
    • Java Components for mySAP CRM 4.0 SR1
      Use the documentation "Installation Guide - Java Components for SAP Customer Relationship Management 4.0 SR1" available on SAP Service Marketplace at: http://service.sap.com/instguides --> Installation & Upgrade Guides --> mySAP Business Suite Applications --> mySAP CRM --> SAP CRM 4.0 --> General and Technical Installation Guides --> Java Components for CRM 4.0 SR 1
  • mySAP ERP 2004 SR1
    • SAP ECC Server 5.0 SR1
      Use the documentation "Installation Guide - SAP ERP Central Component on <O S> : <database>" available on SAP Service Marketplace at:
      http://service.sap.com/instguides --> Installation & Upgrade Guides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2004 --> SAP ECC 5.0 --> Installation Guides of SAP ECC 5.0 SR1
    • Java Components for mySAP ERP 2004 SR1
      Use the documentation "Installation Guide - Java Components for
      mySAP ERP 2004 SR1" available on SAP Service Marketplace at:
      http://service.sap.com/instguides --> Installation & Upgrade Guides -->
      mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2004 -->
      ERP Java Components
  • SAP R3E 4.7, Extension Set 2 SR1
    Use the documentation " SAP R/3 Enterprise on <platform>:<database>  - Using SAP R/3 Enterprise Core 4.70, SAP R/3 Enterprise Extension Set 2.00, Service Release 1", available on SAP Service Marketplace at:
    http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP Components --> SAP R/3 --> SAP R/3 Enterprise --> SAP R/3 Enterprise Core 4.70 / Ext. Set 2.00 (SR1)
  • mySAP SCM 4.0
    Use the documentation "Installation Guide - SAP SCM 4.1 Server on <platform>:<database>  available on SAP Service Marketplace at http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP SCM --> Using SAP SCM 4.1 Server
  • mySAP SCM 4.1
    Use the documentation "Installation Guide - SAP SCM 4.1 Server on <platform>:<database>  available on SAP Service Marketplace at http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP SCM --> Using SAP SCM 4.1 Server
  • mySRM 4.0 SR1
    • SAP SRM Server 5.0 SR1
      Use the documentation "Installation Guide - SAP Supplier Relationship Management Server 5.0 SR1 on <O S>: <database>" available on SAP Service Marketplace at: http://service.sap.com/instguides --> Installation & Upgrade Guides --> mySAP Business Suite Applications --> mySAP SRM --> Using SAP SRM Server 5.0 --> Installation Guides for SAP SRM Server 5.0
    • Java Components for mySAP SRM 4.0 SR1 (Live Auction Cockpit)
      Use the documentation "Installation Guide - Live Auction Cockpit 2.0" Customer Relationship Management 4.0 SR1" available on SAP Service Marketplace at: http://service.sap.com/instguides --> Installation & Upgrade Guides --> mySAP Business Suite Applications --> mySAP SRM --> Using SAP SRM Server 5.0
  • SAP Solution Manager 3.2
    Use the documentation "Component Installation Guide - SAP Solution
    Manager 3.2 on <O S> : <database>" available on SAP Service Marketplace
    at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP Components --> SAP Solution Manager --> Release 3.2
  • SAP NetWeaver '04 SR1
    • SAP Web AS ABAP 6.40 SR1
      Use the documentation "Component Installation Guide - SAP Web Application Server ABAP on <O S> : <database>", available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> SAP Web AS --> SAP Web AS 6.40 SR1 and Related Documentation
    • SAP Web AS Java 6.40 SR1
      Use the documentation "Component Installation Guide - SAP Web Application Server Java on <O S> : <database>", available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> SAP Web AS --> SAP Web AS 6.40 SR1 and Related Documentation
    • TREX
      Use the documentation "Installation Guide - Search and Classification (TREX) <release>", available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> Cross NW
    • Enterprise Portal
      Use the documentation "Installation of SAP Enterprise Portal on Web AS 6.40 EP 6.0 <S P> ", available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> SAP EP
    • Knowledge Management & Collaboration
      Use the documentation "Installation of SAP Enterprise Portal on Web AS 6.40 EP 6.0 <S P> ", available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> SAP EP
    • Adobe Document Services
      Use the documentation "Installation Guide - Adobe Document Services for SAP Web Application Server 6.40 SR1 ", available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> SAP Web AS --> SAP Web AS 6.40 SR1 and Related Documentation
    • BI UDI Java Components
      Use the documentation "Installation Guide - SAP Business Warehouse 3.5 SR1, available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> SAP BW
    • Exchange Infrastructure

                    Use the documentation "Installation Guide - SAP Exchange Infrastructure 3.0 SR1, available on SAP Service Marketplace at http://service.sap.com/instguides --> Installation & Upgrade Guides --> SAP NetWeaver --> Release '04 --> Installation --> SAP XI

4.) Updating the Installation Master DVD (if required):

In the following cases you must update the "6.20/6.40 based products Installation Master(Edition July 2007)" DVD before you start SAPinst:

  • you want to install a Java system in High Availability (HA) manner or you want to install the Java Add-In for an exisiting HA ABAP system
  • you want to install software unit MapBox (CRM-MBX)


Proceed as follows to apply current updates to the "6.20/6.40 based products Installation Master(Edition July 2007)":

  1. 1. Mount the installation DVDs.
  1. 2. Copy DVD "6.20/6.40 based products Installation Master(Edition July 2007)" to a local file system.
  1. 3. Download the attached NW04_09.SAR archive.
  1. 4. Extract NW04_09.SAR to the root directory of the copied "6.20/6.40 based products Installation Master(Edition July 2007)" using the SAPCAR 6.40 for your operating system. For more information, see SAP Note 212876.
  1. 5. Start SAPinst as described in the appropriate installation guide (see
2.) Required installation documentation).

5.) Required Kernel DVD:
  • Use the SAP NetWeaver 04 SR 1 Kernel DVD for your database, except for Informix 10. For Informix 10, you must use the Informix 10.00 DVD.
    Note:
    The kernel could be sick if you install on new OS versions. Apply the most recent kernel patch after the installation has finished.
  • Although you perform a Unicode installation, SAPinst might also ask for the non-Unicode kernel DVD. Therefore have this DVD available for the installation.

6.) Platform and Database Restrictions:

6.20/6.40 Patch Collection Installation on UNIX is not released for the following applications with the following operating systems and databases:

  • Linux_X86_64 (not released for all databases)
    • BW3.1
    • SCM 4.0
    • CRM 4.0 / SRM 3.0
  • HP_IA64 (not released for MaxDB)
    • CRM 4.0 / SRM 3.0
    • SCM 4.0
  • HP_IA64 (not released for IBM DB2 UDB for Unix and Windows)
    • CRM 4.0 / SRM 3.0
    • SCM 4.0
    • BW 3.1
    • CRM 4.0 SR1
  • HP_IA64 (not released for Informix)
    • CRM 4.0 / SRM 3.0
    • SCM 4.0
  • Linux_IA64
    • CRM 4.0 / SRM 3.0 (not released for all databases)
    • SCM 4.0 (not released for all databases)
    • CRM 4.0 SR1 (not released for IBM DB2 UDB for Unix and Windows)
  • Linux_PPC64 (not released for all databases)
    • CRM 4.0 / SRM 3.0
    • SCM 4.0
    • BW 3.1

           See also the database-specific SAP Notes which are attached to this SAP Note for supported versions of your database.



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

2     Pre-Installation

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


-----------------------<D042481 31/JUL/07 >---------------------------
OS users: do not delete shell initialization scripts
Do not delete any shell initialization scripts in the home directory of the OS users, even if you do not intend to use the shells that these scripts are for.

-----------------------<D025095, 26/OCT/06>-------------------------
Java: Update SCSCLIENT64UC.SAR on the Java DVD:
You have to Update SCSCLIENT64UC.SAR on the Java DVD before you start the installation. Otherwise you will have problems as soon as you patch your system after the installation. For more information, see SAP Note 710914.
Solution:
Proceed as follows to update the Java DVD:

  1. 1. Download SCSCLIENT64UC.SAR from SAP Service Marketplace at:
    http://service.sap.com/swdc
    -> Download
    -> Support Packages and Patches
      -> Entry by Application Group
      -> SAP NetWeaver
        -> SAP NETWEAVER
         -> SAP NETWEAVER 04
          -> Entry by Component
          -> Application Server Java
            -> SAP J2EE Engine 6.40
            -> <operating system>
              -> J2EERTOS*.SAR"WebAS 6.40
                SP<required_patch_level>
                (Part 3/4): OS Depend. parts of Java Runtime"
                (The archives SCS*.SAR are part of J2EERTOS*.SAR).
  1. 2. Copy the Java DVD to your file system
  1. 3. On the copied DVD, replace SCS_<OS>/SCS/UNIX/<OS>/SCSCLIENT64UC.SAR with the downloaded patch.
  1. 4. Start the installation.



-----------------------<D026178, 17/OCT/06>-------------------------
Usage of NFS-V4 file system: create OS users manually on NFS server
If you use NFS-V4 file system, then you have to create the operating system users (<sapsid>adm and database user) for your SAP system manually on the NFS server, before you start the installation.
These users must have the same user ID as the operating system users on the instance host(s) of your SAP system.
Otherwise, you get an error message like the following during the installation:
...
NWException thrown: nw.sapsysBad<SAPSID>2:The default profile /sapmnt/<SAPSID>/profile/DEFAULT.PFL is owned by <SAPSID> <port_number>, which is the <SAPSID> of group nobody.
Remove the group account nobody.
...
If you fail to create OS users like described above and get this error during the installation, mount your file system using NFS-V3. Do not remove the group account nobody as suggested in the error message.


-----------------------<D028955, 07/APR/06>-------------------------
ADS: Running ADS with non-supported platforms
Adobe document services (ADS) are currently not supported to run natively on all platforms supported by SAP systems based on SAP NetWeaver, in particular 64-bit platforms.
To use ADS in SAP landscapes set up on non-supported platforms, you have to install an additional stand-alone AS Java on a platform supported by ADS.
For more information, see SAP Note 925741.


-----------------------<D04147,04/APR/05>------------------------------
Additional OS requirements
The following operating system requirements have to be kept in mind:

  • HP-UX

           Make sure that the following C++ runtime version is installed: HP aC++ -AA runtime libraries (aCC A.03.50) or higher. In addition, the shared library 'libiconv.sl' has to be installed in directory /usr/local/lib.

           Adobe Document Services requires en_US.UTF-8 locale on Unix. This might not be installed by default.

  • AIX

           Make sure that the following C++ runtime version is installed:

           xlC.aix50.rte (version 6.0.0.11). Version 6.0.0. 14 does not work.

           If you apply ADS SP-12 or higher, xlC.aix50.rte (version 7. x and above ) is also supported.



------------------------<D020032, 13/JAN/06>--------------------------
Inst.Guide correction: SAP Note 5324 obsolete
Hardware and Software Requirements --> "For more information on SAP software in PC networks, see SAP Note 5324".
SAP Note 5324 is no longer valid.

------------------------<D027120, 02/JUNE/05>--------------------------
AIX 64 bit: PATH must point to JDK/JRE 64 bit
If the operating system is AIX 64 bit, make sure that the PATH variable points to a JDK/JRE for AIX 64 bit. Otherwise SAPinst will not work.

------------------------<D034879 ,09/FEB/05>----------------------
Java: Instance profiles of already installed SAP systems
Before you install SAP Web AS Java (standalone or Add-In), you need to make sure that the names of the instance profiles of all SAP systems already installed on this host correspond to the SAP naming convention:
<SAPSID>_<instance_name>_<host_name>.
SAPinst creates instance profile names which correspond to this naming convention. So, normally you should not need to change anything. If you do not want to reset the names of the instance profiles to the SAP naming convention, you need at least to create soft links for these profiles to names which correspond to the SAP naming convention.

------------------------<D041479, 23/NOV/04---------------------------
ADS: Java Startup parameter
Please make sure that the Java Startup parameter does NOT contain a '=', it has to be
-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.
services.ts.jts.ots.PortableInterceptor.JTSInitializer

-----------------------<D019659, 02/AUG/04>----------------------------
ABAP: Choose different SID for standalone gateway
Symptom:
Each Central Instance (CI) has its own gateway instance. If you install a standalone gateway instance to the same system ID (SID) as the CI already has, the file in the dir SYS/exe/run will be overwritten when the installer extracts the SAR Archive.
Solution:
Choose a SID for the standalone gateway that is different from the SID
of the CI.


------------------------<D035521, 19/APR/04>--------------------------
/ti and /network no longer available on SMP
The quicklinks /ti and /network which are listed in chapter
"Information on SAP Service Marketplace" are not available any longer.


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

3     Installation

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


-----------------------<D050002,25/APR/08>---------------------------
System messages: values for shared memory parameters are not sufficient
Symptom:
You see system messages like the following while the systems comes up during the installation.

Profile configuration error detected, use temporary corrected setup
Shared Pool 10: ipc/shm_psize_10 = 128000000 (too small)
Shared Pool 10: (smaller than min requirement 132107084)
Shared Pool 10: (estimated size assumed 136000000)

You can find these messages in the traces of the system processes which are located in the DIR_HOME directory.
You can resolve the DIR_HOME parameter by running
./sappfpar name=<SAPSID>.
Dev Traces are named dev_wXX, where XX is the process number.

Solution:
Change the values for shared memory the start profile of the instance as recommended in the messages.


-----------------------<D040270 ,22/AUG/06>---------------------------
KMC: Error "Java Engine did not reach state "Start Application"
Problem:
During the installation of the KMC, you get the following error message:
"CJS-20058  Java EE Engine of SAP system <SAPSID> did not reach state "Starting Applications" after xxx seconds: giving up."
Solution:
Restart the Java engine manually.


-----------------------<D025095 ,18/AUG/06>---------------------------
SAP BW 3.1: Incorrect index entries
After the installation, the PACKCHECK_EXCEPT-OBJ and PACKCHECK_EXCEPT ~0indexes may contain incorrect entries. You can ignore this message.

--------------------------<D019130 ,05/APR/06>------------------------
Error FSL-02015  Node <path> does not exist.
Symptom:
You copied the installation DVDs to disk.
You get the error FSL-02015  Node <path> does not exist.
Solution:
Make sure that the paths to the location of the copied DVDs do not do not contain any blanks.

-----------------------<D042481 ,05/DEC/05>-------------------------
Java: Error in sapinst_dev.log: Return value of function /usr/sbin/usermod - <option> <sapsid>adm is 8
Symptom:
You are performing the installation of a distributed system on HP-UX or Solaris.
SAPinst aborts with error "Error text undefined"
sapinst_dev.log: Return value of function /usr/sbin/usermod -<option> <sapsid>adm is 8.
Solution:

  1. 1. Stop all instances of the SAP system which have already been installed on the installation host using the command stopsap r3 <instance_name>.
  1. 2. Make sure that no processes are running any more under user <sapsid>adm and that user <sapsid>adm is not logged on to the installation host.
  1. 3. Press "Retry".
  1. 4. Restart all instances of the SAP system on the installation host using the command startsap r3 <instance_name>.
  1. 5. Continue with the installation.


-----------------------<D019130,05/DEC/05>-----------------------
ABAP: UNICODE conversion error
Symptom:
During the import into a UNICODE system the following error occurs
(for example in the SAPCLUST.log):

myCluster (63.2.Imp): 2085: (Warning:) inconsistent field names(source): physical field K1N05 appears as logic K1N5.
myCluster (63.2.Imp): 2086: (Warning:) further investigation recommended
myCluster (63.2.Imp): 1924: error when checking key field consistency for logic table TACOPC    .
myCluster (63.2.Imp): 1927: logic table is canonical.
myCluster (63.2.Imp): 1930: received return code 2 from c3_uc_check_key_field_descr_consistency.
myCluster (63.2.Imp): 1224: unable to retrieve nametab info for logic table TACOPC    .
myCluster (63.2.Imp): 8032: unable to acquire nametab info for logic table TACOPC    .
myCluster (63.2.Imp): 2807: failed to convert cluster data of cluster item.
myCluster: CLU4       **00001**
myCluster (63.2.Imp): 319: error during conversion of cluster item.
myCluster (63.2.Imp): 322: affected physical table is CLU4.
(CNV) ERROR: code page conversion failed              rc = 2

------------------------------============----------------------------
|
|                              RSCP - Error
| Error from:            Codepage handling (RSCP)
| code:  128  RSCPENOOBJ   No such object
| Dummy module without real rscpmc[34]
| module: rscpmm   no:    2 line:    75                    T100: TS008
| TSL01: CPV  p3: Dummy-IPC   p4: rscpmc4_init
`---------------------------------------------------------------------

Cause:
This problem is caused by incorrect data which should have been removed from the source system before the export.

Solution:
There are two possible workarounds:

  1. 1. Modify DDL<dbs>.TPL (<dbs> = ADA, DB2, DB4, DB6, IND, MSS, ORA) BEFORE the R3load TSK files are generated;

              search for the keyword "negdat:" and add "CLU4" and "VER_CLUSTR" to this line.

  1. 2. Modify the TSK file (most probably SAPCLUST.TSK) BEFORE R3load import is (re-)started;

              search for the lines starting with "D CLU4 I" and "D VER_CLUSTR I" and change the status (i.e. "err" or "xeq") to "ign" or remove the lines.


------------------------<D035521, 03/AUG/05>------------------------
Java Add-In: Dialog Instance Finalization
Chapter "Running SAPinst on UNIX" -> Table: "Installation Services for a Java Add-In Installation"
Installation Procedure:
"Installing a Java Add-In for a central ABAP system" ->
"b) Java Add-In for ABAP -> <Database> -> Central System -> Dialog
Instance Finalization"
Note: You have to run this installation service on the central instance
host.
Prerequisite: You must have installed before the ABAP dialog instance, to which you want to add the Java Add-In.

Chapter "Running SAPinst on UNIX" -> Table: "Installation Services for a Java Add-In Installation"
Installation Procedure:
"Installing a Java Add-In for a distributed ABAP system" ->
"c) Java Add-In for ABAP -> <Database> -> Distributed System -> Dialog
Instance Finalization"
Note: You have to run this installation service on the host of the ABAP dialog instance, to which you want to add the Java Add-In.
Prerequisite: You must have installed before the ABAP dialog instance, to which you want to add the Java Add-In.


------------------------<D027171, 28/JUN/05>------------------------
SAPinst GUI crashes "guiengine: no GUI connected..."
Symptom:
You are browsing for a software package or file during the dialog phase of the installation. Doing this, SAPinst GUI crashes with the error "guiengine: no GUI connected; waiting for a connection on host <host_name> port 21212 to continue with the installation"
Solution:
You reconnect with the GUI to SAPinst and enter the path to the software package or file manually. Then you can continue with the installation.

------------------------<D026178 ,10/MAR/05>-----------------------
Java: Solaris 10 / AIX 5.3: SAPinst aborts with error
Symptom:
During the installation of SAP Web AS Java or Java Add-In SAPinst
on Solaris 10 / AIX 5.3, SAPinstaborts with the following error message:

sapinst.log:
ERROR 2005-03-07 15:08:42
CJS-20058  J2EE Engine DVEBMGS00 of SAP system QO1 did
not reach state "Starting Applications" after 856 seconds:
giving up.

dev_jcontrol (this file is located in the directory /usr/sap/<instance_name>/work):
[Thr 01] *** ERROR => OS release SunOS 5.10 Generic
sun4u is not supported with
this startup framework (640) [jstartxx_mt. 3866]
Solution:
You need to apply the workaround described in SAP Note 710914.

Symptom:
You want to install a Java System configuring the User
Management Engine against a central ABAP system and you get an error
when validating the user data.
Solution:
You need to apply the workaround described in SAP note 860538


------------------------<D023322 ,08/FEB/05>-----------------------
Java: Network Adapter could not establish the connection
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


------------------------<D027171 ,04/FEB/05>-----------------------
SAPinst GUI does not appear after restart
Symptom:
When you have to restart SAPinst or re-logon the GUI after the pure dialog phase is over, the SAPinst GUI does not appear, although
the sapinst is running.
Cause:
The GUI is shown, when a dialog screen, a message or an update task is sent. When you re-logon after the dialog phase, it may happen, that you start with a long running installation task without new dialog screens, messages or update tasks. The GUI will be displayed only, when the current installation task is finished or an installation error occurs. The progress of the current installation task can be tracked in the sapinst_dev.log file.


----------------------<D039661 ,31/JAN/05>-------------------------
(ERP-BD): pop-up requiring post-processing steps
Symptom:
During the installation of ERP java components a pop-up appears telling
you to perform manual post-processing steps and to check
callSdmViaSapinst.log.
This log contains an error message like this:
PM  Info: Finished successfully: software component 'FSCM_BD'/'sap.
com'/'SAP AG'/'05.20041202080033'
Dec 16, 2004 4:37:42 PM  Warning: Caught CVersProxyAccessException while
saving repository: CVersAccessExceptionError writing new entries into
COMPVERS: java.sql.SQLException: [DataDirect][SQLServer JDBC
Driver][SQLServer]String or binary data would be truncated.
Dec 16, 2004 4:37:42 PM  Info: Starting: Initial deployment: Selected
development component 'com.sap.hcm.ls.webapps'/'sap.com'/'SAP AG'/'300.
0520041202144419.0000' will be deployed.
Solution:
Ignore this pop-up and continue with the installation.

------------------------<I031421 ,27/JAN/05>------------------------
Java: SDM server is stopped after the installation
Symptom:
SDM server is stopped after installation.
You can find out this issue when you open system info page, use Jcmon tool or try to deploy anything via SDM.
Solution:
Start SDM server manually.
Go to the SDM/program directory and run ./StartServer.sh.

------------------------<D019527, 23/DEC/04>--------------------------
Java: AIX only: bootstrap error
The engine does not start, but aborts in the bootstrap phase with the following error message in the bootstrap logfile:

java.io.FileNotFoundException: ./../os_libs/libjmon.so (Cannot open or remove a file containing a running program.).
This message can appear with other libraries as well.

Reason:
Shared modules are considered a global resource by the operating system, and the shared library regions are commonly accessed by every process. Once a module is loaded, it stays loaded and is not automatically removed from the shared library reagion, if a program (e.g. SAPinst) stops using it.

Solution:
Execute the command 'slibclean' as root user before starting the engine.

-------------------------<D027120, 19/DEC/04>--------------------------
Error out of memory:
Symptom: You get an error like
FJS-0003  out of memory (in script InstallationScript_352, line ...)
Reason: The java script library is running out of memory
Solution:

  1. 1. Stop the installation.
  1. 2. Increase swap space.
  1. 3. Restart the installation.


------------------------<I027683, 19/DEC/04>------------------------
Java: Error while stopping the SDM server
Symptom:
a Java Add-In or Java standalone installation stops at the step "Start SAP J2EE Engine".
You get an error message like the following:
An IOException occured while reading from the Server: net.id_000001:
Caught IOException during read of header bytes (-1,):Connection reset
Error in ShutdownServer class. Unknown or unexpected result 4 from alive
checker service was received.
Caught Exception: java.lang.IllegalStateException
java.lang.IllegalStateException: Error in ShutdownServer class. Unknown
or unexpected result 4 from alive checker service was received.
        at com.sap.sdm.control.command.cmds.ShutdownServer.execute(Shutd
ownServer.java:115)
        at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.ex
ecute(GlobalParamEvaluator.java:60)
        at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.ex
ecute(AbstractLibDirSetter.java:46)
        at com.sap.sdm.control.command.decorator.ExitPostProcessor.execu
te(ExitPostProcessor.java:48)
        at com.sap.sdm.control.command.decorator.ClientComponentInitiali
zer.execute(ClientComponentInitializer.java:25)
        at com.sap.sdm.control.command.decorator.SyntaxChecker.execute(S
yntaxChecker.java:37)
        at com.sap.sdm.control.command.Command.exec(Command.java:42)
        at SDM.main(SDM.java:21)

Severe (internal) error. Return code: 16


Solution:
Choose 'Retry'.


----------------------<D041479, 26/NOV/04>---------------
ADS: JStartup Framework error in error log can be ignored
Symptom:
When checking the log files of the Adobe Installation the following error might be found in the error log:
           Error: An error occured while restoring the cluster instances states

           Error: JStartup Framework is not able to deliver an information about the cluster control instances!

           Error: Received exception when restoring Engine state: JStartup Framework is not able to deliver an information about the cluster control instances!

Solution:
You can ignore this error as it does not affect the installation.


---------------------<D024110, 19/NOV/04>--------------------------
ADS: Error com.ibm.db2.jcc.c.DisconnectException (on DB6 (IBM DB2 UDB for UNIX and Windows) only):
Symptom:
You encounter the following error:
com.ibm.db2.jcc.c.DisconnectException: Attempt to fully materialize lob data that is too large for the JVM
Solution:
Proceed as follows:

  1. 1. Check the user limit for user <sapsid>adm and db2<dbsid> with the following command:

              ulimit

  1. 2. If required, increase data, stack and memory according to your needs.
  1. 3. Increase 'Maximum Heap Size'  in the J2EE Config tool (configtool.sh and configtool.bat) for instance_ID, server_ID and dispatcher_ID.
    For more information on this error, see
SAP Note 784568.


------------------------<D025095, 13/SEP/04>----------------------
ABAP: SAPinst breaks during an RFC call with "time-out"
Symptom:
The installation breaks during an RFC call and you find a TRACE
information in sapinst_dev.log with "time-out"
Solution:
Press the "Retry" button and if this does not work, try to restart SAPinst installation.
Background:
This error occures when die RFC Job gets a time-out and the system tries
to show a screen. The SAPinst rfc library can not handle screens.


---09/JUL/04----Freespace check error---------------------------------
SAPinst tool error: The freespace check may not run correctly sometimes.
In this case you receive an error message like that:
Needed space on mountpoint is <number> KB, but got only <number> KB
To proceed with the installation, you must do the following:

  1. 1. Cancel the installation.
  1. 2. Check your disk space according to the installation guide requirements.
    Only proceed with the following procedures, if you have sufficient disk space available!
  1. 3. Edit the file
<SAPinst_INSTDIR>/keydb.xml as follows:
    1. a) Search for string
SAPINST_INST_STATUS.
    1. b) Under this string, search for string
ERROR.
    1. c) Replace
ERROR by OK.
    1. d) Save your settings.
  1. 4. Run ./sapinst in your <SAPinst_INSTDIR>.



------------------------<D037196, 28/JUN/04>--------------------------
Java: Field "J2EE Engine Parameters: Number of J2EE Servers"
In the SAPinst input field "J2EE Engine Parameters: Number of J2EE Servers" do not change the default value "1". When you have finished the installation and the patching of the J2EE engine and its applications, you can manually define further server processes. For more information, see the SAP Library under SAP NetWeaver -> Application Platform (SAP Web Application Server) -> Java Technology in SAP Web Application Server -> Administration Manual -> Server Administration -> SAP J2EE Engine Administration -> Config Tool -> The GUI Config Tool -> Server Configuration -> Configuring Cluster Elements.

------------------------<D019527, 28/JUN/04>--------------------------
Running SAPinst: separate inst_dir for each instance
You need aseparateinstallation directory for the installation of each SAP instance (central instance, database instance, dialog instance and gateway instance).


-------------------------<D029035, 25/JUN/03>--------------------------
SAPinst GUI does not get displayed correctly
If the SAPinst GUI does not get displayed correctly (for example, if the title of a screen is displayed without contents and without buttons), make sure that you have installed the latest version of XServer/Window Manager of your UNIX operating system.

-------------------------<D019527 16/JUN/00>--------------------------
Linux: Errors during exectution of shell scripts
The execution of shell scripts starting with ":" (not with "#!/bin/sh") causes errors or core dumps due to the Linux Kernel. Try solving the problem by rebooting your host or installing a new Linux Kernel (see SAP Note 359566).

------------------------<D041051, 07/JUN/04>--------------------------
HP Tru64 only: Error FSH-00006 while creating group sapsys
Symptom: Error message FSH-00006
Return value of function getgrnam(<group name>) is Successful.
when SAPinst creates group <group name>.
Solution:
When the error occurs stop SAPinst and restart until all groups have
been created. Alternatively, the user can also create the groups
manually and then start SAPinst again.


------------------------<D034879, 02/JUN/04>--------------------------
Do not use instance number 60 when installing a central or dialog instance of your SAP (ABAP) system and you are using the iSCSI protocol between your host and network-attached disk storage.

-------------------------<D025095, 19/AUG/03>--------------------------
SAPinst prompts to manually stop the SCS instance
If SAPinst prompts to manually stop the SCS instance with command "stopsap SCS<No.>", make sure to enter the whole command and not just "stopsap" - otherwise, also the database gets stopped and you have to start the database manually later (an error will then occur during the installation with SAPinst).

-------------------------<D029035, 25/JUN/03>--------------------------
SAPinst GUI does not get displayed correctly
If the SAPinst GUI does not get displayed correctly (for example, if the title of a screen is displayed without contents and without buttons), make sure that you have installed the latest version of XServer/Window Manager of your UNIX operating system.

-----------------------<C5017462, 15/OCT/2002>-------------------------
64-Bit AIX 5.x: SAPinst GUI causes segment. faults
If SAPinst GUI causes segmentation faults on 64-Bit AIX 5.x, set the following parameters in the installation shell:
  ulimit -d unlimited
  ulimit -s unlimited

-----------------------<D029035, 24/JUN/2002>-------------------------
HP-UX: Startup problems of SAP Java Connector (JCo)
If SAP Java Connector (SAP JCo) crashes during the start of the SAP Web AS and its SAP J2EE Engine (error message "java.lang.ExceptionInInitializerError: JCO.classInitialize() Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC' libsapjcorfc.sl: Not enough space"), see SAP Note 523346.

-------------------------<D019527 10/AUG/01>-------------------------
NFS mounts: SAP processes abort with signal 9
The usage of NFS mounts may cause the operating system to abort processes with signal 9 (see SAP Note 426188). Therefore, it is recommended to prefer the usage of sapcpe to normal NFS mounts for SAP executables.


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

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

------------------------<D044990, JUNE/02/08>-------------------------
ABAP, ABAP+Java: Errors in transaction ST11 (error log files) every time the SAP system is started.

Symptom:
You see error messages like the following in transaction ST11
(error log files) every time when the SAP system is started
(IGS and abap appserver with all processes are up and running):

[Thr 4448] Tue Apr 29 12:35:13 2008

[Thr 4448] *** ERROR => SncPDLInit(): DlLoadLib("sncgss64
.dll")=DLENOACCESS
[sncxxdl.0340][Thr 4448] *** ERROR => SncPDLInit()==SNCERR_INIT,
Adapter (#0) sncgss64.d
[sncxxdl.0604][Thr 3108] Tue Apr 29 12:35:14 2008

[Thr 3108] *** ERROR => SncPDLInit(): DlLoadLib("sncgss64
.dll")=DLENOACCESS
[sncxxdl.0340][Thr 3108] *** ERROR => SncPDLInit()==SNCERR_INIT,
Adapter (#0) sncgss64.d
[sncxxdl.0604][Thr 3676] Tue Apr 29 12:35:14 2008

[Thr 3676] *** ERROR => SncPDLInit(): DlLoadLib("sncgss64
.dll")=DLENOACCESS
[sncxxdl.0340][Thr 3676] *** ERROR => SncPDLInit()==SNCERR_INIT,
Adapter (#0) sncgss64.d
[sncxxdl.0604]

Solution:

  1. 1. Apply the latest kernel, IGS, and support packages.
  1. 2. Adjust TCP/IP connection IGS_RFC_DEST as follows:
    1. a) Run transaction SM59.
    1. b) Open TCP/IP connection IGS_RFC_DEST.
    1. c) Set the program id to IGS.<SAPSID>
    1. d) Make sure that the fields for gateway host and gateway service  are empty.
  1. 3. Adjust TCP/IP connection IGS_RFC_DEST in the same way as you did with TCP/IP connection IGS_RFC_DEST.


------------------------<I808897, 25/AUG/06>--------------------------
EP: SP11 required
After the installation has finished successfully, you must patch your EP system to Support Package 11.

------------------------<I021997, 23/JAN/06>--------------------------
Java: Inst. Guide correction: "Installing the SAP License"
Ignore the following wrong note and reference in section "Installing the SAP License" in the installation guides for SAP Web AS Java:
...
<Note>
If you installed a Java system as a prerequisite for the SAP Enterprise Portal installation, do not install the SAP license now. The license of the SAP Web AS Java system is automatically installed as part of the SAP Enterprise Portal installation. For more information, see "Solution Life Cycle Management --> SAP Licenses --> SAP License Keys --> SAP License --> Licensing the Portal" in the SAP Library [...].
...
Solution:
SAP Enterprise Portal is automatically licensed as the rest of the SAP NetWeaver platform by applying the license of SAP Web AS Java.
For more information, see the SAP Library at:
http://help.sap.com/ --> SAP NetWeaver 2004 --> SAP NetWeaver Library Solution Life Cycle Management --> SAP Licenses --> SAP License Keys



------------------------<d019527, 16/JAN/06> -------------------------
ABAP: Unable to perform job COLLECTOR_FOR_PERFORMANCEMONITOR
Symptom:
After the installation the following error message appears in the systemlog (transaction SM21):
EB9  Batch scheduler: Unable to perform job
        COLLECTOR_FOR_PERFORMANCEMONITOR
ECL  > Cause: Planned start date too far in the past
ECM > Action: De-allocate batch job
Solution:
Re-schedule the job (for example, by copying the old one to SM37).


------------------------<I030671 ,19/APR/05>---------------------------
Java: Linux X86_64: cannot start SLD (System Landscape Directory)
Solution: Apply SAP Note 815605.

-------------------------<I027641 ,21/FEB/05>------------------------
ERP-XSS: Errors in callSdmViaSAPinst.log
Symptom:
The installation of ERP 2004 SR1 java components finished successfully.
Nevertheless a pop-up requests to perform manual post-processing steps and to check callSdmViaSapinst.log., for example:
***********************************************************************
java.rmi.RemoteException: Error occurred while starting application sap.com/ess/tra/trp/trt and wait. ...
***********************************************************************
Cause:
The WebDynpro applications have a lazy starting mechanism. This means that they are started upon request. It is normal that some of them need to be stopped after server start. They will be started when a request is sent to them. The reason of the error messages listed in the log file is, that the applications were requested before the deployment of all referenced applications had finished. When a Web Dynpro application tries to start, it tries first to start all referenced components. The traces show that some of the applications are not available, because they were not deployed at that moment.
Solution:
You can ignore these error messages if you are able to start the applications listed in the error message manually.

-------------------------<D035360,08/FEB/05>------------------------
SAP SCM 4.0 / SAP SCM 4.1: BW-specific post-installation steps
The following settings are necessary

  • for performing a client copy which is mandatory for using mySAP SCM and
  • to maintain a BW-client that is necessary for Demand Planning in mySAP SCM

Note that there are dependencies in the installation of SCM-Server and liveCache.
There are also issues when implementing SCM-Support Packages in one queue.

Carry out the following BW-specific post-installation steps:

  1. 1. Install the SCM Server.
  1. 2. Import additional languages (optional).
  1. 3. Apply all Support Packages except SCM-Support Packages
    Apply SCM Support Packages 1 - 10
    Note: It is important that SCM SP 7 and SCM SP 11 are not imported in one queue in order to prevent data loss. Between SCM SP 7 and SCM SP 11 you have to proceed as described below. Therefore you should apply SCM SP 1 - 10.
  1. 4. Create Logical System using transaction BD54.
  1. 5. Maintain a client and assign logical system to the new client using transaction SCC4.
    If you need more than one new client repeat the steps 4 and 5.
  1. 6. If the new client(s) should not be used in combination with liveCache (e.g. Lean-Installation), then the client(s) have to be marked as non liveCache relevant. To do so, execute report /SAPAPO/OM_NONPRODUCTIVE_CLNT and mark the new client(s) as not liveCache relevant.
    You should not execute the report for clients that will be used in combination with liveCache.
  1. 7. If any of the new clients will be used with liveCache, then
    1. a) Install LC as described in the liveCache Installation Guide and apply the latest liveCache-Builds.
    1. b) Create LCA/LDA connections for LC as described in the liveCache Installation Guide.
  1. 8. Logon to one of the new clients with
sap*/pass.
  1. 9. Copy client 000 using transaction SCCL with user profil
SAP_CUST (Customizing).
  1. 10. If one of the clients will be used with liveCache: Create RFC destination and RFC-User for global working on the liveCache, see SAP Note 305634.
  1. 11. Execute report
/SAPAPO/DELETE_LC_ANCHORS using transaction SE38.
  1. 12. Repeat the steps 8 to 11 for all new clients that have been created.
  1. 13. Set parameter
login/system_client = <one of the new clients (e.g. productive client)> in the default profile or in the instance profile(see also SAP Notes 116432 and 116520) and delete entry logon/system_client if it exists.
Do not change this profile setting after you executed step 16.
  1. 14. Stop and restart the system in order to activate the default profile.
  1. 15. Logon to the new client that was set in step 13.
  1. 16. Start transaction RSA1 and enter the logical system name of this client in the upcoming popup.
Note: It might be possible that you have to enter table RSADMINA anddefine the BW-client before you can execute RSA1.
  1. 17. Apply SCM Support Packages >= 11 (see step 3).


-------------------------<I801946, 03/FEB/05>--------------------------
CRM-IC: IC requires SAF to be installed
The IC (Intelligence Connector) requires the Software Agent Framework (SAF) to be installed. To check that the SAF is installed correctly, see section 6.3.4 (SAF: Performing System Checks) in the documentation
"Installation Guide - Java Components for SAP Customer Relationship Management 4.0 SR 1".

------------------------<D023724, 01/FEB/05>--------------------------
ABAP (ECC): mySAP ERP new general ledger: activation with new customers
Symptom: You can see the Customizing Menu for the new general ledger but you cannot post in the new general ledger.
Solution:
Apply SAP Note 811287.

------------------------<D035491, 13/DEC/04>--------------------------
Java: Problems when shutting down the Web AS Java
Solution: Stop the process manually as described in related
SAP Note 799755

------------------------<I024157, 09/DEC/04>--------------------------
Java (JDI): enhance maximum memory for java compiler
If you intend to install Java Development Infrastructure (JDI) on your
SAP Web AS Java, enhance the default settings for maximum memory for
the java compiler as described in SAP Note 759669.

------------------------<D021063, 08/DEC/04>--------------------------
Timeout during starting up of J2EE engine
Symptom:
You start J2EE engine the first time. J2EE engine does not come up
until it runs into timeout
Reason:
Because of starting the first time, the J2EE engine takes more time
for getting synchronized from the database.
Solution:
Check if the engine is started actually. You can check this by
verifying the log file in the work directory of the instance.
If the engine is started, press 'Retry'. Then the engine comes up.


------------------------<D037196>, 26/NOV/04>---------------------------
Java: Strong Crypto deactivated after dialog instance installation
Symptom:
You have installed the SAP Java Cryptographic libraries and a Dialog Instance. Then the following problems arise:

  • The service com.sap.security.core.ume.service is not properly configured
  • The service SSL of the additional dispatcher is set to "manual"

Solution:

  1. 1. Open the visual configtool.
  1. 2. Switch to configuration editor mode.
  1. 3. Select "edit mode" and edit property sheet "pcluster_data/server/cfg/services/Propertysheet com.sap.security.core.ume.service"
  1. 4. Set entry "ume.usermapping.unsecure" to FALSE.
  1. 5. Set the startup mode of the service ssl to "always" for global dispatcher configurations and instance specific dispatcher configurations.

This bug is fixed with SP10.

-------------------------<D026178 27/AUG/04>--------------------------
Distributed installation: Check /etc/hosts.equiv and  SM59
Symptom:
Not sufficient sapxpg configuration causes CPIC errors
Solution:

  1. 1. Check entries for hostname and user of the central instance in file
    /etc/hosts.equiv
  1. 2. Add missing entries in SM59 -> TCP/IP Configuration ->
    SAPXPG_DBDEST_<dbhost> -> Gateway-options
    Gateway-Host
    Gateway-Service


-------------------------<C5038467, 13/APR/04>-------------------------
Java Add-In: Changing parameters with RZ10 or RZ11
Before changing parameter values in the instance profile that are very long (for example, the parameter jstartup/instance_properties), make sure that you have read SAP Note 579190.


-------------------------<D019167 17/MAR/04>--------------------------
Missing service entry for SLD gateway:
If you encounter problems with the automatic data transfer to the SLD system in transaction RZ70 or related batch jobs and this problem is related to a missing service entry: Enter the missing service manually as described in related SAP Note 712594.

-------------------------<D023620 02/MAR/04>--------------------------
Configure not more than 99 work processes per server:
You must not configure more than 99 work processes per application
server because the LUW key can interprete two decimals only.
For details see related SAP Note 9942

------------------------<C5036314, 19/FEB/04>--------------------------
Java: OutOfMemoryError
Symptom:
OutOfMemoryError during installation of additional applications
Solution:
The reason may be that the standard perm size of your system is not sufficient for the Java Virtual Machine. In this case you have to increase the perm size as described in related SAP Note 693662.


------------------------<I024187, 04/FEB/04>--------------------------
Java: additional Java components cannot be accessed after redeployment
or upgrade of Web AS Java
Symptom:
After redeploy of a certain application or upgrade of J2EE Engine this application can not be accessed.
Solution:
See SAP Note 701277.


-------------------------<D003432 13/AUG/03>--------------------------
Java Add-In only: Run script saproot.sh
This section does not apply for SAP DB.
After a Java Add-In installation you must run the script saproot.sh on the central instance host as the user root: /usr/sap/<SAPSID>/SYS/exe/run/saproot.sh <SAPSID>

-------------------------<D029035 18/DEC/02>--------------------------
SAP License: System number must be 18 characters
When installing the SAP License, make sure that the system name is 18 characters long (if required, enlarge the system name with leading zeros - for example, "000000000123456789).

-------------------------<D019628, 18/OCT/01>------------------------
ABAP+Java Add-In only: sapcpe in an High-Availability Environment
If you edited the file sapcpeft (for example, you added the lines
   R3trans   | Local copy
   cleanipc  | Local copy
   saposcol  | Local copy
as you wanted sapcpe to copy R3trans, cleanipc and saposcol locally to the corresponding host for High-Availability purposes), make sure to save these changes to sapcpeft before performing an SAP Kernel change and to add these changes again to the overwritten file sapcpeft after the kernel change.

-------------------------<D022860 09/JAN/01>------------------------
Incomplete path in .sapenv_<hostname>.sh
If you use the Bourne or Korn shell as the login shell for <sapsid>adm and starting/stopping the SAP System fails because startsap/stopsap is not found, this is probably due to an incomplete path specification in $HOME/.sapenv_< hostname>.sh.
To solve this problem, change the line
'for d in /usr/sap/<SAPSID>/SYS/exe/run; do'
to
'for d in /usr/sap/<SAPSID>/SYS/exe/run $HOME .; do'
in the file $HOME/.sapenv_<hostname>.sh.

-------------------------<D022825 17/NOV/00>------------------------
HP Tru64: SAP System does not start
If you have more than 3 GB of extended memory, it may occur that the SAP System can not be started due to missing free memory of class PERM. In this case, see SAP Note 217351.

-------------------------<C5020924 30/OCT/00>------------------------
HP Tru64 5.x: Replace saposcol after the installation
The saposcol on HP Tru64 5.x displays wrong values. Download a new version of saposcol from sapserv<X>. See SAP Note 351876 for more information.

-------------------------<D023035 18/OCT/00>------------------------
Linux: Replace saposcol after the installation
After installation, move (mv) the old version of the executable saposcol from /sapmnt/<SID>/exe to a save place. Then, replace saposcol in /sapmnt/<SID>/exe with the one which you can download from SAP Service Marketplace at: http://service.sap.com/swcenter-main. Make sure that you stop saposcol before. Adapt the file permissions for the new saposcol executable accordingly (owner root, group sapsys, permissions 4710).
When starting saposcol, you may get some error messages like "error: permission denied on key..." which can be ignored.
If saposcol won't start because of shared memory problems, try to restart R/3 (stopsap r3, startsap r3).

-------------------------<D029035 16/MAY/00>------------------------
ABAP+Java Add-In only:
Import Base, ABA Support Packages
Import at least the following Support Packages after the installation:
Base, ABA
See http://service.sap.com/patches to download Support Packages from SAPNet.

-------------------------<D025095 19/JAN/00>------------------------
ABAP+Java Add-In only:
HP Tru64:Warning during profile check can be ignored
The profile check (transaction code RZ10) on HP Tru64 UNIX causes a warning message for the parameter abap/heap_area_total. Ignore this warning message or delete the paramter in the profile.



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

5     High Availability (HA)

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

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.

------------------------<d020990, 29/MAY/06>--------------------------
Install Replicated Enqueue Server for High Availability (HA)
If you want to install a high-availability system with switchover software, we strongly recommend you to install the standalone replicated enqueue server. This fully protects the enqueue server from failure.
For more information on how to install the replicated enqueue server, see:
help.sap.com -> SAP NetWeaver -> SAP NetWeaver 2004 -> English -> SAP NetWeaver -> Application Platform -> ABAP Technology -> Client/Server Technology -> The SAP Lock Concept -> Standalone Enqueue Server -> Installing the Standalone Enqueue Server

Note: in an HA system, the cluster is automatically and cleanly stopped when the host running the enqueue server fails. This feature is available from SAP Web AS 6.40 SP15. This means you no longer need to reset open transactions or enqueue locks because the system does it for you. This feature is available whether or not you have installed the standalone replicated enqueue server.

-----------------------<D041479 ,21/JUN/05>------------------------
Change startup mode of IIOP service
If, after installing Adobe Document Services, you are not able to connect to address
           http://<host>:<port> /AdobeDocumentServices/Config

           error message: "Cannot start service com. adobe~DataManagerService; it has hard reference to service iiop with manual startup mode."

           

You need to change the startup mode of the IIOP service in the configuration tool of the J2EE engine to ALWAYS.

标签：

相关文章