SAP Basis Tech Supports

Symptom
This note is valid for the following releases:
SAP NetWeaver 7.1 (i5/OS, Windows and Linux)
Other terms

install, SAPinst, AS/400, Java EE, iSeries,System i, homogeneous system copy, OS/400,Windows, NT, NW, BS, ECC, ERP, SCM, SRM, CRM
Reason and Prerequisites

Problems discovered after publication of the installation guide
Solution

This SAP Note is available in English only.
Topics Date changed
====== ============
1 General Information Jun/2009
2 Pre-Installation Feb/2009
3 Installation Sept/2008
4 Post-Installation Oct/2008
5 Troubleshooting Dec/2007
+===================================================================+
1: General Information

+===================================================================+
i5/OS

———————–————————–
Independent ASPs (iASPs)
Independent ASP(iASP) installations and system copy services is not
supported in SAP Netweaver 7.1. Full support of the this features starts
with SAP Netweaver 7.1 Ehp 1. For iASP installations, see SAP Note
1257481 “SAP NetWeaver Inst. Based on Kernel 7.11: IBM DB2 for i”
+===================================================================+
2: Pre-Installation

+===================================================================+

i5/OS

———————–————————–
SAP system installation on an IBM i 6.1 (V6R1)
The installation package for SAP NetWeaver 7.1 was released before the
general availability of IBM release 6.1. The kernel packages in the
Installation DVD do not support the installation for IBM release 6.1 or
newer. A problem description and solution is available inSAP Note
1134271. To avoid running into this problem, before starting the
installation, patch the Kernel DVD in the installation package as such:
- Copy the Kernel DVD into the IBM file syste (IFS)
- Find and download the latest versions of SAPEXE.SAR and SAPEXEDB.SAR
- Rename the patches by removing the versions and replace them in the
copied Kernel DVD.
- Download the latest ILE.SAR patch. Using SAPCAR, extract SAR file
into a temporary IFS directory (i.e. SAPCAR -xvf ILE. SAR).
- Replace the ILE_TOOLS files in the kernel DVD with the extracted one.
After patching this 3 files in the Kernel DVD, execute the installation
process as documented in the installation guide.
Note: Do not replace the file SAPJVM5.SAR of the Kernel DVD with the
latest version from SMP. Per default the new SAPJVM.SAR is missing the
Java Cryptography Extension Jurisdiction Policy files. This cannot be
handled by the current installation.
——————————————–
When downloading the installation DVD from the SAP marketplace, the
sapinstgui.exe file might not be included. The GUI is available for
downloadad at the SAP marketplace as well.
Download ‘SAPinstgui for Windows Server on IA32 32bit’ (51033240_41)
and execute sapinstgui.exe on Windows.
——————————————–
NW PI 7.1 only
Distributed installation: UID and GID
As described in the installation documentation at the beginning ofchapterInstallationyou must check the UID of ADM and the GID of R3GROUP. These IDs should be the same for all involved System i hosts.
Use the following command for an example to check the UID of ADM: DSPUSRPRF USRPRF(ADM)
Do the same for R3GROUP and the GID. Write these numbers down.
When you are asked for the UID of ADM and for the GID of sapsys (R3GROUP) in the dialog calledSAP System Administratorby SAPinst in subsequent distributed installations of the same SID put in the same values.
Sometimes it is not possible to set the same UID of ADM or the same GID of R3GROUP on all involved System i hosts because they are already in use by another user or group.
In this case exchange the file control.xml on your NW PI 7.1 in the Installation Master DVD with the file control.xml attached to this note. The control.xml is packed in the file NWPI71ControlXML.ZIP. Unpack it and copy it into the DVD directory /DATA_UNITS/IM_OS400_PPC64_DB4/NW07/WEBAS/IND.
——————————————–
Convert the profile file DEFAULT.PFL of all old EBCDIC SAP systems
At the beginning of the installation SAPinst checks all existing SAP systems installed on your iSeries. At that time SAPinst tries to read the file DEFAULT.PFL of each system. Files in EBCDIC cannot be read and the SAPinst will end with a read error. To avoid this error convert all DEFAULT.PFL files written in EBCDIC into ASCII. The EBCDIC SAP system will still be able to handle the converted profile DEFAULT.PFL!
——————————————–
Installing additional double byte language locales
The kernel shipped with this release contains all needed single byte language locales. If you need additional double byte language locales, you have to install the missing locales using additional language DVDs. To determine which language DVD and which language library you have to install, see the IBM internet link: http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/apis/pase_locales.htm or search for terms “pase locales” in the iSeries Information Center.
For example for the double byte locales ZH_TW you need the language DVD “Traditional Chinese” to install the language library QSYS2987.
Before you install an additional double byte language library to create additional double byte locales, make sure that PASE is installed and up-to-date.
After you have installed a new double byte language also all locales of this language are created. As a final step check if there are any PTFs to be installed using the INFOAPAR.

Linux

———————-< C5046158, Feb 2005 >————————-
Users and Permissions
Check that the following directories have an owner and group which is known to the Linux host, for example if you enter command ls -l on those directories, you should not see UIDs/GIDs, but real user names:
/sapmnt//profile
/sapmnt//global
all directories in /usr/sap/trans
For the /sapmnt subdirectories, you could do this by changing the owner to adm and the group to sapsys using qsh on System i:
chgrp sapsys /sapmnt//profile
chown adm /sapmnt//profile
For the /usr/sap/trans subdirectories, you could create artificial users and groups with those UIDs/GIDs on your Linux host.
———————-< C5046158, Feb 2005 >————————-
Format of DEFAULT.PFL
On your Linux host, convert the file /usr/sap//SYS/profile/DEFAULT.PFL to UNIX format.

+===================================================================+
3: Installation

+===================================================================+
——————–—————————-
Fixed with NW701
Do not use an existing when installing a new SAP system. For example, if you have already installed an ABAP system, and want to install a Java system on the same host, make sure that you enter an that is different from the of the first (ABAP) system.
————– ———————————
Java Add-In or dialog instance installation: gateway instance with same
must not exist
If you want to install the Java Add-In for an existing ABAP system or a
dialog instance, make sure that no gateway instance with the same SAP
System ID (SAPSID) exists in your SAP system landscape. If so, you must
reinstall the gateway with a different .
———————–————————–
Using “Back” button with “Typical” Mode
Note the following when you process the screen “Parameter Mode >
Default Settings”: If you chose the “Typical” setting and press “Back”
after processing one or more input screens, the installer now guides
you through all screens with default parameters that it has processed
in the background so far.
i5/OS
——————————————–
SAPCRYPTO.CAR
You do not have to mark the installation option of the security package SAPCRYPTO.CAR. All needed security files are part of the kernel.
But if you are asked to install the SAPCRYPTO.CAR you have to consider the following points:
System i uses the SAPCRYPTO.CAR of AIXthe SAPCRYPTO.CAR of AIX embodies different versions. Make sure to select the 64 bit version of AIX 5.1 when you are asked by SAPinst.

+===================================================================+
4: Post-Installation

+===================================================================+
———————-<16/OCT/08, D035496>————————–
ABAP, ABAP+Java: Error in syslog in SM21, shortdump in ST22
Fixed with SP01
Symptom:
You see an error like the following error in syslog when calling
transaction SM21:
Run-time error “LOAD_PROGRAM_NOT_FOUND” occurred
You see an error like the following error when calling transactionST22:
Runtime Errors LOAD_PROGRAM_NOT_FOUND
Solution:
Apply support package SP01.

———————–<06/DEC/07, D021285>————————–
NW PI 7.1 only
PI components not completely registered in SLD
Symptom:
After setup of PI 7.10 SP4 through upgrade, installation or system copy,
PI components may not be completely registered in the System Landscape
Directory (SLD).
Solution:
Follow the instructions inSAP Note 1117249.
———————–<05/DEC/07, D034879>————————–
Remove all krnlreg entries from profiles

1. Go to /usr/sap//SYS/profile.2. Edit the instance profiles for all SAP system instances __, for example KB1_DVEBMGS01_pwdf2308.3. Remove all ‘krnlreg’ entries from all instance profiles. Take care that the permissions and the ownership of the profiles stays the same.
Note: If you do not remove these krnlreg entries, a deadlock situation may occur while restarting the central services instance.
i5/OS

——————————————–
SAPOSCOL does not run
Check the dev traces of the work processes. If you find entries like this probably the SAPOSCOL is not installed correctly and does not run:
*** ERROR => ShmDelete2(1002): shmctl(6,IPC_RMID,0) (1: Not owner)
[shmux.c 2924]
Solution:
Reinstall the Hostagent manually. For more information see SAP Note 1031096. The file SAPHOSTAGENT.SAR can be found on the SAP Service Marketplace.

+===================================================================+
5: Troubleshooting

+===================================================================+
NW PI 7.1 only
Distributed installation: Phase Create Secure Store fails
Symptom:
The SAPinst breaks in the phaseCreate Secure Storeand a error message box pops up.
Cause:
In the phaseCreate Secure StoreSAPinst tries to change permissions in the IFS on the remote global host using QFileSvr.400. This only happens when the UID of ADM and the GID of R3GROUP are not the same on all involved System i hosts. QFileSvr.400 does not allow to change IFS permissions remotely.
Solution:
Stop the SAPinst.Download the file NWPI71ControlXML.ZIP attached to this note.Rename the file control.xml in your installation directory.Unpack NWPI71ControlXML.ZIP and copy the new file control.xml into the installation directoryStart SAPinst again and continue your old installation.

The new control.xml will not try anymore to change permissions in the IFS remotely using QFileSvr.400 .
———————–————————–
Heterogeneous installation: sapcontrol not found dir DIR_EXECUTABLE and
DIR_CT_RUN
During an heterogeneous installation (that is you install an
SAP system with instances running on different operating systems)
you get the following error message:
sapcontrol not found dir DIR_EXECUTABLE and DIR_CT_RUN
Solution:
Download the attached file NW07_01_REL.zip
Extract the file to your installation directory to update the
control.xml file
Caution: Do not update dialog.xml and keydb.xml
Restart the installation.
RESET N1
i5/OS
———————-< C5069979, May 2007 >————————-
During the phase ‘Unpack SAP archives’ of a distributed installation on System i, SAPinst fails with the following error:
WARNING珽 2007-04-18 15:53:50.345 琲axxbfile.cpp:644
CIaOsFile::chgrp_impl()
FSL-02003 Unable to set owner /qfilesvr.400//sapmnt//exe/uc/as400_pase_64/icmbnd for
Solution:
Log on to , where the file exists locallyChange icmbnd ownership to adm using the following command:
CHGOWN OBJ(’/sapmnt/ /exe/uc/as400_pase_64/icmbnd’) NEWOWN(ADM)Click retry or restart and continue the installation

Linux

———————-< C5046158, Feb 2005 >————————-
Error During sapstart
Make sure you have converted file /usr/sap//SYS/profile/DEFAULT.PFL to UNIX format.