note 1169801 - inst.netweaver 7.0 ehp1&business suite 7 - unix.pdf

28
7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 1/28 06.08.2013 Page 1 of 28 SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite 7 - UNIX  Note Language: English Version: 45 Validity: Valid Since 31.07.2012 Summary Symptom *********************************************************************** * * Installation on Unix * SAP NetWeaver 7.0 EHP1 * (SAP NetWeaver 7.0 EHP1, * SAP ERP 6.0 EHP4, * SAP CRM 7.0, * SAP SRM 7.0, * SAP SCM 7.0 ) * * *********************************************************************** Other terms SAPinst, SAP NetWeaver 7.0 EHP1 ,SAP ERP 6.0 EHP4, SAP CRM 7.0, SAP SRM 7.0, SAP SCM 7.0 Reason and Prerequisites Problems discovered after the 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: Klaus Billig klaus.billig@ sap.com Always use the latest documentation version (see SAP Service Marketplace at: http://service.sap.com/installNW70 http://service.sap.com/erp-inst http://service.sap.com/crm-inst http://service.sap.com/srm-inst http://service.sap.com/instguides -> SAP Business Suite Applications -> SAP SCM -> SAP SCM Server Contents Sections of this note are: 1. General

Upload: pubirz

Post on 28-Oct-2015

1.098 views

Category:

Documents


1 download

DESCRIPTION

NWDI Notes

TRANSCRIPT

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 1/28

06.08.2013 Page 1 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

 Note Language: English Version: 45 Validity: Valid Since 31.07.2012

Summary

Symptom 

***********************************************************************

*

* Installation on Unix

* SAP NetWeaver 7.0 EHP1

* (SAP NetWeaver 7.0 EHP1,

* SAP ERP 6.0 EHP4,

* SAP CRM 7.0,

* SAP SRM 7.0,

* SAP SCM 7.0 )

*

*

***********************************************************************

Other termsSAPinst, SAP NetWeaver 7.0 EHP1 ,SAP ERP 6.0 EHP4, SAP CRM 7.0, SAP SRM

7.0, SAP SCM 7.0

Reason and PrerequisitesProblems discovered after the 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:

Klaus Billig [email protected]

Always use the latest documentation version (see SAP Service Marketplace

at:

http://service.sap.com/installNW70

http://service.sap.com/erp-inst

http://service.sap.com/crm-inst

http://service.sap.com/srm-inst

http://service.sap.com/instguides -> SAP Business Suite Applications -> SAP

SCM -> SAP SCM Server

Contents

Sections of this note are:

1. General

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 2/28

06.08.2013 Page 2 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

2. OS-Dependencies

3. Pre-Installation

4. Installation

5. Post-Installation

6. Corrections in the installation guides

Date Section Description

-----------------------------------------------------------------------

JUN/19/12 2 Support of Solaris 11

MAY/24/12 3 Ensure that you have applied SAP Note 1697164.

APR/04/12 4 Dialog instance installation: Do not unpack old kernel

archives

JUN/29/11 2 HP-UX: do not use 75 as instance numberJUN/29/11 2 HP-UX: do not use 02 as instance number

JUN/29/11 2 AIX: do not use 01 or 02 as instance number

MAR/07/11 4 Uninstall: Do not select checkbox "Remove all instances

of the SAP system or standalone engine on this host" if you do not want to

uninstall the complete SAP system.

MAR/04/11 5 Adjust profile parameters as described in SAP Note

1104735

JAN/18/11 3 HP-UX only: OS user authentication does not work with

LDAP

JUN/24/10 4 Do not use Japanese characters in SAP system profiles

JUN/18/10 5 startsap/stopsap command throws "No instance profile

found" error

APR/29/10 3 Make sure that the csh scripts are up-to-date

FEB/18/10 3 Home directory of OS users must not be '/'

DEC/07/09 5 EPC, EP:'WELCOME_CLAUSE' instead of welcome text and

user name

NOV/17/09 4 ERROR FJS-00003 TypeError: NWInstance.bySIDandLocal

is not a function

NOV/17/09 3 ABAP+Java,Java, Java Add-In: Exchange control.xml

when installing with virtual host name

NOV/09/09 4 ABAP, ABAP+Java: ERROR FCO-00011: step

adaptInstanceProfiles was executed with status ERROR

OCT/22/09 4 Make sure that umask is set to 022

AUG/26/09 1 Unicode and non-Unicode support

JUL/23/09 4 SAPINST fails at phase "Start Java Engine"MAY/19/09 5 AIX: Check user limits for operating system users

MAR/27/09 4 ABAP, ABAP+Java, AIX: Do not use 01 or 02 for instance

number

MAR/16/09 4 Changing "Custom" to "Typical" on "Parameter Summary"

screen does not work

Symptom: You want to change from "Custom" to "Typical" parameter mode or

MAR/13/09 4 Restarting sapinst aborts with error message

MAR/05/09 5 Delete usagetype.properties file manually due to

security reasons

FEB/24/09 4 Make sure that GID of 'sapinst' is unique

FEB/24/09 5 Dealing safely with installation directories

FEB/13/09 3 ABAP+Java, Java: Make sure there is not an olderversion of the JCE policy zip file on the installation host.

JAN/30/09 4 Uninstall Diagnostics Agent only: Manually delete

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 3/28

06.08.2013 Page 3 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

the <smdsid>adm user.

DEC/19/08 3 Dialog Instance: Check entries in sapservices file

and naming of profile backup files

OCT/02/08 1 mounts under /<sapmnt>/<SAPSID> must be permanent

SEP/05/08 5 SCM, ABAP: Error message in SM21 after

installation.

AUG/28/08 4 Error when using the "Media Browser" screen

AUG/28/08 4 SAPinst finished successfully but error on command line

JUL/24/08 5 ABAP+Java,Java: Keystore views are not created

during the very first start

APR/02/08 4 zLinux: ERP Rapid Configuration: Execution of the

command "db2radm -m chkc" failed

MAR/26/08 5 EPC, EP: "HTTP response: 500 - Internal Server

Error" when accessing Forms Builder iView

MAR/25/08 4 ABAP: liveCache Client in SCM Installations

19/FEB/08 4 ABAP+Java,Java Add-In:FSL-01003 Unable to modify

account user="<sapsid>adm" uid="<user ID of <sapsid>adm"

DEC/19/07 4 ABAP+Java, Java Add-In: SAPinst terminates with

error message in step createJSFOCT/29/07 1 SAPinst GUI: Close buttons ('X') of message boxes

do not work

02/MAY/07 2 Release of HP-UX 11i for Itanium processor family

23/AUG/07 4 Using "Back" button with "Typical" Mode

31/JUL/07 3 OS users: do not delete shell initialization

scripts

17/JUL/07 4 Linux x86_64: Error "cannot open libj9vm22.so"

12/JUN/07 4 Uninstall: Error message FCO-00011

01/JUN/07 4 Uninstall aborts with error message

04/MAY/07 5 Errors in syslog: Unable to create directory

05/MAR/07 3 Copy Installation Master DVD if only one DVD drive

available

05/FEB/07 5 Post-installation step before running the Template

Installer

15/NOV/06 5 Incorrect permissions of softlinks to sapinit

system startup script

15/NOV/06 5 Incorrect permissions of some files under

DIR_INSTANCE/j2ee/ctc

24/OCT/06 5 Error message when you close SAPinst GUI

19/OCT/06 4 Error during uninstall on HP-UX: "Login <sid>adm is

currently in use"

11/OCT/06 4 Java HA: SAPinst hangs during deployment

18/SEP/06 2 AIX 5.3, AIX 5.2 Maintenance Level (ML)

08/SEP/06 5 BI Java / PI: Setting Environment Variable

CPIC_MAX_CONV23/AUG/06 4 Non-Unicode kernel DVD required for Unicode

installation

21/JUN/06 3 same password for local OS user accounts on all

hosts

14/JUN/06 5 Java: Passwords are logged plain in the http-access

logs

31/MAY/06 4 Java: Import of software units or usage types fails

with message "Access denied"

19/MAY/06 4 Sharing same JDK between system based on

NetWeaver 2004s SR3 and other software

18/APR/06 3 Installing dialog instance(s) for an SAP system

upgraded to SAP NetWeaver 2004s SR312/APR/06 5 (PI): Client copy considerations

10/APR/06 5 ABAP, ABAP+Java: Check value of parameter

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 4/28

06.08.2013 Page 4 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

rdisp/bufrefmode in DEFAULT.PFL

06/APR/06 5 Java on SUNOS/X86_64 5.10 - 64 Bit:

FATAL: Caught OutOfMemoryError! Node will exit with exit code 666

28/MAR/06 5 (PI): Increase number of dialog work processes

22/MAR/06 5 Java, ABAP+Java: J2EE Engine reboots permanently

17/MAR/06 5 ABAP dialog instance: check parameter

login/system_client

28/FEB/06 1 New SAPCAR for products based on SAP NW 2004s

05/DEC/05 4 ABAP: UNICODE conversion error

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

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

This SAP Note contains information relevant to the following installationtypes (usage types, software units). EHP1, you can also install the

NetWeaver 7.0 EhP1 usage types.

o SAP NetWeaver 7.0 EHP1, including:

- AS ABAP (ABAP)

- AS Java (Java)

- AS ABAP and AS Java (ABAP+Java)

- SAP NetWeaver Development Infrastructure (DI)

- SAP NetWeaver Business Intelligence Java (BI Java)

- SAP NetWeaver Enterprise Portal (EP)

- SAP NetWeaver Mobile Infrastructure (MI)

- SAP NetWeaver Process Integration (PI)

o SAP ERP 6.0 EHP4, including:

- SAP ERP Application Set (ERP-APP)

- SAP ERP Biller Direct (BD)

- SAP ERP Business Packages (BP-ERP)

- SAP ERP Learning Solution (Content Player) (LSOCP)

- SAP ERP Extended E-Selling Components (XECO)

- SAP ERP Self Services (XSS)

- SAP ERP Utilities Customer E-Services (UCES)

- SAP ERP Retail Store Applications (IS-R-SRS)

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 5/28

06.08.2013 Page 5 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

- SAP ERP Portal Content Self Services (BP-XSS)

- SAP ERP Portal Content Common(BP-Common)

o SAP CRM 7.0, including:

- SAP CRM Application Set (CRM-APP)

- SAP CRM Java Components (JCRM)

- SAP CRM Business Packages (BP-CRM)

- SAP SRM 7.0 including:

- SAP SRM Application Set (SRM-APP)

- SAP SRM Live Auction Cockpit (SRMLAC)

- SAP SRM Business Packages (BP-SRM)

o SAP SCM 7.0 including:

- SAP SCM Server (SCM-APP)

- SAP SCM Replenishment Workbench for Store (SCMRWBS)

- SAP SCM Event Manager Web Communication Layer (SCMEMWCL)

This note contains information relevant to the following installation types

(usage types):

o AS ABAP (ABAP)

o AS Java (Java)

o AS ABAP and AS Java (ABAP+Java)

o Business Intelligence Java (BI Java)

o Development Infrastructure (DI)

o Enterprise Portal Core (EPC)

o Enterprise Portal (EP)

o Mobile Infrastructure (MI)

o Process Integration (PI)

Each entry is marked with a prefix (ABAP, Java, ABAP+Java, BI, DI, EP, MI,

PI) to make clear which installation type the information applies to.

The prefix "HA" is for "High Availability".

If there is no prefix, the information applies to all types.

See also related SAP Notes "SAP NetWeaver 7.0 SR3 Installation on

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 6/28

06.08.2013 Page 6 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

UNIX:<your database>" for database-specific information:

o 1169802 SAP NetWeaver 7.0 EHP1 Installation on UNIX:Oracle

o 1172652 SAP NetWeaver 7.0 EHP1 Installation on UNIX: MaxDB

o 1171535 DB6: SAP NetWeaver 7.0 EHP1 - Installation on UNIX

Unicode and Non-Unicode SupportEvery new installation of an SAP system is Unicode.

If you install a dialog instance to an existing non-Unicode system (that

has been upgraded to the current release), then the dialog instance is

installed automatically as a non-Unicode instance. SAPinst determines if a

non-Unicode system exists and chooses the right executables for the system

type.

-----------------------< D034879 OCT/02/08 >--------------------------

Make sure that the required mounts under /<sapmnt>/<SAPSID> are permanent.Otherwise automatic start of the instance services will not work when you

reboot the system.

-----------------------< D027171 OCT/29/07 >--------------------------

SAPinst GUI: Close button ('X') of message boxes does not work

Symptom:

You cannot close message boxes of SAPinst GUI using the close button ('X').

Solution:

Use the buttons of the message box instead.

-----------------------< D027171 FEB/28/06 >--------------------------

New SAPCAR for products based on SAP NW 7.0

SAPCAR has been made downward compatible for all Releases. Due to this

change, older versions of SAPCAR can no longer unpack the current SAR

files. To unpack the archives, you need at least SAPCAR 700 or SAPCAR 640

with patch level 4 or higher.

For the latest SAPCAR version, see SAP Service Marketplace at

service.sap.com/swdc.

For more information, see Note 212876.

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

2 OS Dependencies

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

This section contains operating system-specific information that is not

covered by the installation guide.

o As of SAP Web AS 6.40 SR1 (SAP NetWeaver '04 SR1) the former

documentation "SAP Software on UNIX - OS Dependencies" has been

re-integrated in the installation guides.

So, you find all OS-specific information furtheron in the

installation guides.

See SAP Service Marketplace at:

http://service.sap.com/installNW70

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 7/28

06.08.2013 Page 7 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

http://service.sap.com/erp-inst

http://service.sap.com/crm-inst

http://service.sap.com/srm-inst

o As of SAP NetWeaver 2004s (7.0) SR1, the SAP Note "SAP Software

on UNIX : OS Dependencies for <current release>" was merged with

the

this SAP note (SAP NetWeaver <release> Installation on UNIX).

o NOTE:

For information on downloading patches from SAP, see

http://service.sap.com/sp-stacks

o Installation Perequisite Checker:

As of SAP NetWeaver 7.0 (2004s) and Business Suite 2005 (CRM 5.0,

ERP 6.0 (2005), CRM 5.0, SRM 5.0, SCM 5.0), you check the hardware

and software requirements for your operating system (OS) and the

SAP system instances using the Prerequisite Checker tool.

The Prerequisite Checker provides detailed information about the

requirements that you need to meet before you start the

installation. For example, it checks the requirements for the

different installation services.

For more information, see chapter "Hardware and Software

Requirements"

in the installation guide for your SAP solution and SAP Note

855498.

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

AIX:

 Minimum AIX Technology Level (TL)To check the operating system version on your installation hosts, enter the

relevant command for your operating system release:

o AIX 7.x: The output of the command oslevel -s should be at least7100-00-00-0000.

o AIX 6.x: The output of the command oslevel -s should be at least

6100-00-01.

o AIX 5.3: The output of the command oslevel -s should be at least

5300-05-01 (TL 5 SP 1).

o AIX 5.2: The output of the command oslevel -s should be at least

5200-10-07-0902 (TL 10 SP 7).

C++ Runtime Environment:Check the C++ runtime level with the following commands:

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 8/28

06.08.2013 Page 8 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

AIX 7.x:

o lslpp #L xlC.aix*.rte:

The output must be at least 11.1.0.1.

o lslpp #L xlC.rte

The output must be at least 11.1.0.1.

AIX 6.x:

o lslpp #L xlC.aix61.rte:

The output must be at least 10.1.0.0.

o lslpp #L xlC.rte:

The output must be at least 10.1.0.0.

AIX 5.x:

o lslpp #L xlC.aix50.rte:

The output must be at least 9.0.0.9.

o lslpp #L xlC.rte:

The output must be at least 9.0.0.9.

---------------------<C2620001 ,18/SEP/06>-------------------------

AIX 5.3, AIX 5.2 Maintenance Level (ML)

Use the command "oslevel -r" to check the operating system for the

following minimum ML:

o ML 5 on AIX 5.3 for all SAP kernel releases

o ML 3 on AIX 5.2 for SAP kernel version >= 700

If you use NIM Service Handler (NIMSH), do not use 01 or 02 as SAP system

instance number. SAPinst uses the instance number for the internal message

server port 39<instance number>. The NIM client daemon uses reserved ports

3901 and 3902.

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

HP-UX:

---------------------<C5064343 ,02/MAY/07>-------------------------

HP has released HP-UX 11i for the Itanium processor family.

HP-UX 11i for Itanium is built from the same code base as HP-UX 11i for

PA-RISC and has the same look-and-feel.

In general, all OS requirements for HP-UX are valid for both the PA-RISC

version and the Itanium versions.

There are some exceptions due to new functionality of the latest HP-UX

releases.

For more information on HP-UX 11iv3 and HP-UX 11.31, see SAP Note 1031960.

Do not use 75 as SAP system instance number because this number is already

used by the operating system. For more information, see SAP Note 29972.

Do not use 02 as SAP system instance number because this number is used to

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 9/28

06.08.2013 Page 9 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

determine the port number for report RSLGCOLL, which is 14<instance_number>

by default. The port 1402 however is already used by the OS process

rstlisten. If you decide to use 02 as the instance number anyway, the

instance fails to start during the installation process. You then have to

change the port number for report RSLGCOLL manually to continue with the

installation. For more information, see Running SAPinst [page 70].

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

LINUX:

<no entries yet>

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

SOLARIS:

Solaris:

Support of Solaris 11:Solaris 11 is supported for SAP system installation.For more information,

see SAP Note 1669684.

NOTE

Solaris 11 might not have been released yet for all database platforms and

versions. If you want to install on Solaris 11, first check the product

availability matrix (PAM) available at http://service.sap.com/pam to see

whether your database platform or version is supported.

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

3 Pre-Installation======================================================================

-----------------------<D057436 24/MAY/12 >--------------------------

Ensure that you have applied SAP Note 1697164.

-----------<D048554, 18/JAN/11>-------------------------------------

HP-UX only: OS user authentication does not work with LDAP.

If an LDAP directory server is used for SAP operating system users, check

SAP Note 1547989.

-----------<D029385, 29/APR/10>---------------------------------------

Make sure that the csh scripts are up-to-date

SAPinst uses csh scripts during the installation to obtain the environment

for user <sapsid>adm.

This is also true if user <sapsid>adm already exists from an earlier SAP

system installation, and the shell of this user is not csh.

Before you start SAPinst, execute the following command as user <sapsid>adm

to make sure that the csh scripts are up-to-date:

/bin/csh -c "source /<home>/<sid>adm/.cshrc;env"

For more information about recommended shells for the installation with

SAPinst, see SAP Note 202227.

------------------< D029385, 18/FEB/10 >----------------------------

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 10/28

06.08.2013 Page 10 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

If you create operating system users (<sapsid>adm, <dasid>adm, sapadm,

ora<dbsid>, db2<dbsid>, sqd<dbsid>) manually or use already existing

operating system users, make sure that the home directory for each of these

users is not the root directory ( / ).

------------------< D029385, 17/NOV/09 >----------------------------

ABAP+Java,Java, Java Add-in: Exchange control.xml when installing with

virtual host name

Caution: This entry in only valid if you do not use the installation

master medium for the Oracle 11 backward release (see SAP Note 1478350).

Symptom:

If you want to install an SAP system with virtual host name using

environment variable SAPINST_USE_HOSTNAME on a host (in a standalone

system) or hosts (in a distributed system) where one or more other SAP

systems already exist, you must replace the control.xml file of the

installation master DVD with the modified control.xml file that is attachedto this SAP Note.

Solution:

Proceed as follows:

1. Copy the installation master DVD to a local directory on the

installation host(s).

2. Go to tab strip "Attachments" of this SAP Note and download the

attached control.zip file.

3. Unpack the control.zip file.

4. Go to the folder <inst_master_DVD>/<your operating system>/<your

product>/WEBAS/IND (for example

<mount_dir>/IM_LINUX_X86_64/NW701/WEBAS/IND) and replace the existing

control.xml file with the new one that you got from control.zip.

5. You can now start the installation as described in the installation

guide.

Note:

If you do not apply the workaround described under "Solution", you get

various errors during the installation process (for example 'instance has

no properties' in step 'unpackJ2EEINSTALL' if you install the Java

Add-In). You then have to restart the installation with option "Run a NewOption" after having done the modifications described above (choose "Run a

new Option" on the "What do you want to do" screen).

-----------------------<D039123 13/FEB/09>--------------------------

ABAP+Java, Java: Make sure there is not an older version of the JCE policy

zip file for your platform on the installation host.

If there is an old JCE policy zip file, the Prerequisite Checker does not

recognize this fact. Because of this, SAPInst throws a

java.lang.SecurityException during the Create Secure Store step stating the

jurisdiction policy files are not signed by trusted signers.

-----------------------<D034879 19/DEC/08 >--------------------------

Dialog Instance: Check entries in sapservices file and naming of profile

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 11/28

06.08.2013 Page 11 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

backup files

If you want to install an additional application server instance (AAS) to

an existing SAP system, make sure that:

o There is exactly one entry in the /usr/sap/sapservices file for

each SAP instance installed on this host. Be sure to check that the

entry refers to the correct profile.

o There are no profile backup files with an underscore '_' in their

profile name. If so, you must replace the '_' with a '.'.

Example:

Rename

/usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2_D20081204 to

/usr/sap/S14/SYS/profile/S14_DVEBMGS20_zsi-aix693p2.D20081204.

-----------------------<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 scriptsare for.

---------------------<D027120, 05/MAR/07>----------------------------

Copy Installation Master DVD if only one DVD drive available

If you are performing a local installation and there is only one DVD drive

available on your installation host, you must copy at least the

Installation Master DVD to the local file system.

---------------------<D034879, 21/JUN/06>----------------------------

same password for local OS user accounts on all hosts

If you install a distributed system and you do not use central user

management (for example, NIS), and you use local

operating system user accounts instead, then <sapsid>adm and

the database operating system user must have the same

password on all hosts.

---------------------<D034879, 18/APR/06>----------------------------

Installing dialog instance(s) for an SAP system upgraded to SAP NetWeaver

7.0 SR3

If you want to install a dialog instance for an SAP system upgraded to

SAP NetWeaver 7.0 SR3, do the following:

 ABAP+Java system ================

1. Edit DEFAULT.PFL.

a) Insert a line with the parameter 'rdisp/msserv_internal = 'and set

it to a free port number.

2. Edit the central services instance profile.

a) Set the parameter 'rdisp/msserv' to 0.

b) Insert a line with the parameter 'rdisp/msserv_internal = 'and setit to the port number that was assigned before to rdisp/msserv.

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 12/28

06.08.2013 Page 12 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

c) Restart all instances.

Example:

========

- DEFAULT.PFL

Before:...

rdisp/msserv = sapms<your SAP system ID>

...

 After:...

rdisp/msserv = sapms<your SAP system ID>

rdisp/msserv_internal = <free port number>

...

- Central services instance profile:

Before:...

rdisp/msserv = 4711

...

 After:...

rdisp/msserv = 0

rdisp/msserv_internal = 4711

...

Java system ===========

1. Edit the central services instance profile.

2. Set the parameter 'rdisp/msserv' to '0'.

3. Insert a line with the parameter 'rdisp/msserv_internal = 'and set it

to the port number that was assigned before to rdisp/msserv

4. Restart the central services instance.

Example:

========Central services instance profile:

Before:...

rdisp/msserv = 4711

...

 After:...

rdisp/msserv = 0

rdisp/msserv_internal = 4711

...

 ABAP system 

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 13/28

06.08.2013 Page 13 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

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

1. Edit DEFAULT.PFL.

2. Insert a line with the parameter 'rdisp/msserv_internal = 'and set it

to a free port number.

3. Restart all instances.

Example:

========

DEFAULT.PFL

Before:...

rdisp/msserv = sapms<your SAP system ID>

...

 After:...

rdisp/msserv = sapms<your SAP system ID>rdisp/msserv_internal = <free port number>

...

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

4 Installation======================================================================

----------------<D037196, APR/04/12>-------------------

Dialog instance installation: Do not unpack old kernel archives

Symptom:

The kernel of the central instance has a higher version than the kernel of

a dialog instance being installed. Ensure that the kernel of the central

instance is not overwritten during the installation of the dialog instance.

Solution:

Apply SAP Note 1701575.

----------------<D042481, MAR/07/11>-------------------

Uninstall: Do not select checkbox "Remove all instances of the SAP system

or standalone engine on this host" if you do not want to uninstall the

complete SAP system.Symptom:

Do not select checkbox "Remove all instances of the SAP system or

standalone engine on this host" if you do not want to uninstall the

complete SAP system or standalone engine.

For example, do not select this checkbox if you only want to uninstall a

dialog instance of an existing SAP system distributed over several hosts.

Otherwise SAPinst will also remove the contents of mounted global

directories under /<sapmnt>/<SAPSID>/ such als instance profiles and kernel

executables.

------------------------<D029385, JUN/24/10>----------------------Do not use Japanese characters in SAP system profiles

Symptom:

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 14/28

06.08.2013 Page 14 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

You have made entries (for example comments) in SAP system profiles in

/<sapmnt>/<SAPSID>/profile .

You get an error message that a profile parameter is not set.

Solution:

Proceed as follows:

1. Remove all japanese characters from the SAP system profiles.

2. Restart the installation from the beginning.

On the "What do you want to do?" screen, choose "Run a new option".

------------------------<D029385,NOV 17,09>-----------------------

ERROR FJS-00003 TypeError: NWInstance.bySIDandLocal is not a function

Symptom:

You get an error message like the following:

 message ERROR 2009-10-22 17:30:54.197 [iaxxejsbas.cpp:204]

FJS-00003 TypeError: NWInstance.bySIDandLocal is not a function (in

script NW_Doublestack_DBind ind ind ind, line 90363: ???):Solution:

Proceed as follows:

1. Stop the installation.

2. Download the control.zip file from tab "Attachments" of this SAP Note

and extract it to your local file system.

3. Go to the installation directory sapinst_instdir.

4. Replace the existing control.xml file with the one you extracted from

control.zip.

5. Restart the installation.

6. On the "What do you want to do" screen, choose "Continue with the old

option".

-----------------------------<D029385,NOV 09,09>------------------

ABAP, ABAP+Java: ERROR FCO-00011: step adaptInstanceProfiles was executed

with status ERROR

Symptom:During the installation of the DB-instance of a distributed system, you get

an error message like the following :

FCO-00011 The step adaptInstanceProfiles with step key|NW_Doublestack_DB|ind|ind|ind|ind|0|0|NW_GetSidMaybeProfiles|ind|ind|ind|i

nd|2|

|NW_GetSidFromProfilesPartial|ind|ind|ind|ind|1|0|NW_getFQDN|ind|ind|

ind|ind|3|0|adaptInstanceProfileswas executed with status ERROR ( Last

error reported by the step :TypeError: NWInstance.bySIDandLocal is not a

function (in script NW_Doublestack_DB|ind|ind|ind|ind, line 90363: ???)).

Solution:Proceed as follows

1. Make a local copy of the DEFAULT.PFL file.

You can find this file in the profile directory of the SAP global host

in the following directory: /<sapmnt>/<SAPSID>/profile

2. Edit the DEFAULT.PFL file and delete the line that starts with

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 15/28

06.08.2013 Page 15 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

SAPFQDN=

3. Restart the installation of the DB-instance

4. On the "What do you want to do" Screen, choose "Run a new option"

5. On the screen "SAP System > DNS Domain Name", enter the domain of the

DB-instance host.

---------------------<C5064343, OCT 22, 09>--------------------------

Make sure that umask is set to 022

Make sure that umask is set to 022 for user root. As user root, enter the

following command: umask 022

---------------------<D001712, JUL 23, 09>--------------------------

SAPINST fails at phase "Start Java Engine"

Symptom:

SAPINST fails at phase "Start Java Engine"Solution:

Proceed as follows:

1. Insert the following line into /sapmnt/<SAPSID>/profile/<Instance

Profile>:

jstartup/native_stack_size = 2097152

2. Save <Instance Profile>.

3. Continue the installation by choosing "Retry".

---------------<D027120, MAR 27,09>-----------------------

ABAP, ABAP+Java, AIX: Do not use 01 or 02 for instance number

If you are using NIM Service Handler (NIMSH), do not use 01 or 02 for the

instance number. SAPinst uses the instance number for the internal

message server port 39<instance number>. The NIM client daemon uses

reserved ports 3901 and 3902.

---------------<D027120, MAR 16,09>-----------------------

Changing "Custom" to "Typical" on the "Parameter Summary" screen does not

work.

Symptom: You want to change from "Custom" to "Typical" parameter mode or

from "Typical" to "Custom" parameter mode by using the "Revise" button onthe "Parameter Summary" screen. However, this does not work.

Cause:

In "Revise" mode, you can change all parameters that you can select from

the "Parameter Summary" screen except for the parameter mode ("Typical" or

"Custom").

Solution: Restart the installation with option "Run a new option".

---------------------<D027120, MAR 13, 09>--------------------------

Restarting sapinst aborts with error message

Symptom:

After restart sapinst aborts with an error message like the following:FKD-00049 XML parser error: error: no DTD specified, can't validate in

line 2, 2 in file /Install/statistic.xml.

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 16/28

06.08.2013 Page 16 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

Solution:

Remove the file statistic.xml from the installation directory and restart

sapinst.

---------------------<D034879, FEB 26, 09>--------------------------

Make sure that GID of 'sapinst' is unique

If you are installing an SAP system whose instances are to run on several

hosts (distributed or high-availability system), make sure that the group

ID of group 'sapinst' is always different from the group ID of any other

group (for example, of group 'sapsys') that is used during the

installation.

Example:

You are installing an additional application server instance to an existing

SAP system.

Then you must make sure that the group ID of group 'sapinst' that is

created on the host of the additional application server instance is

different from the group ID of any other group (for example, of group

'sapsys') on the primary application server instance host of the existing

SAP system.

----------------------<I021802, JAN 30, 09>---------------------------

Uninstall Diagnostics Agent only: Manually delete the <smdsid>adm user.

Symptom:

You have uninstalled a Diagnostics Agent instance using SAPinst with

installation option Software Life-Cycle Options -> Uninstall-> Uninstall -

Solution Manager Diagnostics Agent

After the uninstall with SAPinst has finished successfully, user

<smdsid>adm is still existing.

Solution:

Delete user <smdsid>adm manually.

----------------------<D027120, AUG 26, 08>---------------------------

Error when using the "Media Browser" screen

Symptom:

You get the following error while you select an installation DVD

on the "Media Browser" screen:

Caught ESAPinstException in Modulecall:

could not call evaluator in class CCdCheckUserInput.

Solution:

Restart SAPinst and continue with the old installation option.

---------------------<D027120, AUG 26, 08>----------------------------SAPinst finished successfully but error on command line

Symptom:

The installation has finished successfully, but you see an error message

like the following displayed on the command line:

ERROR 2008-06-17 13:28:19.250 [iaxxclib.cpp:219]

CLib::unload()

FRY-00003 Cannot close library iamodapp.sl: Cannot close

'/tmp/install/sapinst_exe.5806.1213684641/iamodapp.sl' due to remaining

dependencies.

aCC runtime: Uncaught exception of type "ELib".

iauxsysex.c:317: child /tmp/install/sapinst_exe.5806.1213684641/sapinst(pid 5807) has crashed. Executable directory is /tmp/install/sapinst_exe

.5806.1213684641. Contact Support.

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 17/28

06.08.2013 Page 17 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

iaextract.c:888: child has signaled an exec error. Keeping directory

/tmp/install/sapinst_exe.5806.1213684641

You might also see an error message like the following:

INFO 2009-01-15 15:25:19.286 [syuxcpath.cpp:351]

CSyPath::createFile()

Creating file /tmp/sapinst_instdir/.lastInstallationLocation.

Closing RFC connection 000:DDIC:EN:uxi321:00::QE1:...

Closing RFC connection 000:DDIC:EN:uxi321:00::QE1:... Done!

Closing RFC connection 000:SAP*:EN:uxi321:00::QE1:...

Closing RFC connection 000:SAP*:EN:uxi321:00::QE1:... Done!

Closing RFC connection 001:DDIC:EN:uxi321:00::QE1:...

Closing RFC connection 001:DDIC:EN:uxi321:00::QE1:... Done!

Closing RFC connection 001:SAP*:EN:uxi321:00::QE1:...

Closing RFC connection 001:SAP*:EN:uxi321:00::QE1:... Done!

iauxsysex.c:318: child /tmp/sapinst_exe.18114.1232011142/sapinst

(pid 18115) has crashed.Executable directory is /tmp/sapinst_exe.18114.1232011142.

Contact Support.

iaextract.c:895: child has signaled an exec error.

Keeping directory /tmp/sapinst_exe.18114.1232011142

Solution:

You can ignore this error message.

-----------------------<D036661 02/APR/08 >---------------------------

zLinux: ERP Rapid Configuration: Execution of the command "db2radm -m

chkc"fails

Symptom:When performing ERP Rapid Configuration on zLinux, you get an error message

like the following:

ERROR 2008-03-07 10:42:52.241

CJSlibModule::writeError_impl()

MUT-03010 Execution of the command "db2radm -m chkc" finished with

status TST_ERROR.

ERROR 2008-03-07 10:42:52.243

CJSlibModule::writeError_impl()

MUT-03010 Execution of the command "db2radm -m chkc" finished with

status TST_ERROR.

ERROR 2008-03-07 10:42:52.291 [sixxcstepexecute.cpp:951]

FCO-00011 The step setInstanceValues2 with step key

rapidconfig ind ind ind ind 0 0 NW_GetCI ind ind ind ind 1 0 NW_getDBIn

fo ind ind ind ind 2 0 NW_DB2_DBParameters ind ind ind ind 1 0 setInstan

ceValues2 was executed with status ERROR ( Last error reported by the

step :Execution of the command "db2radm -m chkc" finished with status

TST_ERROR.).

Solution:Proceed as described in SAP Note 1151952.

-----------------------<D036661 25/MAR/08 >---------------------------ABAP: liveCache Client in SCM Installations

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 18/28

06.08.2013 Page 18 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

Symptom:

When you install an SCM system, liveCache client software is automatically

installed, even when you explicitly choose not to install liveCache server

during the installation.

Solution:

There is no solution currently available. However, this has no effect on

the functioning of your SCM system.

-------------------------<D042481, 19/FEB/08>--------------------------

ABAP+Java,Java Add-In: FSL-01003 Unable to modify account

user="<sapsid>adm" uid="<user ID of <sapsid>adm"

Symptom:

You get an error message like the following:

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

WARNING 2008-01-16 18:30:18Existing account <sapsid>adm is not a member of group sapinst. Changing

membership of account.

ERROR 2008-01-16 18:30:18

FSL-05014 Command '/usr/sbin/usermod' with parameters '-G

"dba,oper,sapsys,sapinst" <sapsid>adm' failed with return code 8: Login

<sapsid>adm is currently in use

.

ERROR 2008-01-16 18:30:18

FSL-01003 Unable to modify account user="<sapsid>adm" uid="<user ID of

<sapsid>adm>".

ERROR 2008-01-16 18:30:18

MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error text

undefined.

ERROR 2008-01-16 18:30:18

FCO-00011 The step createAccounts with step key

|NW_Addin_SCS|ind|ind|ind|ind|0|0|NW_Users_Create_Do|ind|ind|ind|ind|3|0|cr

eateAccounts was executed with status ERROR .

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

Solution:

1. Stop the ABAP stack as described in the installation guide (Additional

Information -> Starting and Stopping the SAP System).

2. Open a command prompt and execute the command '/usr/sbin/usermod'.

3. Continue with the installation.

You can do this in one of the following ways:

o If you choose parameter mode "Typical", proceed as follows:

1.) Check the entry in the "User ID" field for <sapsid>adm onscreen "SAP System > Administrator Password".

2.) On the "Parameter Summary Screen", select "Diagnostics Agent >

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 19/28

06.08.2013 Page 19 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

OS User Parameters".

3.) Enter a user ID that is not already assigned to the <sapsid>adm

user or to any other user in the "User ID" field for the

<smdsid>adm .

o If you choose parameter mode "Custom":

You can enter the user ID directly during the phase "Define

Parameters" on the screen "Diagnostics Agent > OS User Parameters".

However, you can also check and - if required - change the user ID

assigned to <smdsid>adm via the "Parameter Summary Screen" as

described above.

If you do not perform these steps, you might get an error during the

installation of the central instance or of dialog instances like the

following:

o in sapinst_dev.log:

ERROR 2008-01-29 16:26:44.698 [syuxcuser.cpp:1654]

CSyUserImpl::addToOS(const CUserData& data,ISyProgressObserver*)FSL-01002 Unable to create account <sapsid>adm. UserId 1000 is not

unique.

o in smd.log:

[createOSUser]

User account already existing: {

role:SMDAdm

type:USER

systems:os

name:smdadm

password:XXXXXX

instancenumber:98

...

-----------------------<D029385, 19/DEC/07>--------------------------

ABAP+Java, Java Add-In: SAPinst terminates with error message in step

createJSF

Symptom:

SAPinst terminates with the following error message:

ERROR 2007-12-17 12:13:42.463

CJSlibModule::writeError_impl()

CJS-30196 The function module "PRGN_GEN_PROFILES_FOR_ROLES"

cannot be used for 'remote' calls.

TRACE 2007-12-17 12:13:42.473 [iaxxejsbas.hpp:460]EJS_Base::dispatchFunctionCall()

JS Callback has thrown unknown exception. Rethrowing.

ERROR 2007-12-17 12:13:42.493 [iaxxgenimp.cpp:731]

showDialog()

FCO-00011 The step createJSF with step key |NW_Onehost|ind|ind|ind|ind|0|

0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CI_Instance|ind|ind|ind|ind|11|0

|

NW_CI_Instance_Doublestack|ind|ind|ind|ind|3|0|createJSF was executed with

status ERROR .

Solution:Follow the instructions in SAP Note 1126481.

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 20/28

06.08.2013 Page 20 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

-----------------------<D031117, 17/JUL/07>--------------------------

Linux x86_64: Error "cannot open libj9vm22.so"

Symptom:

SAPinst aborts during "Start Java engine" with the following error:

libjvm.so preloadLibrary: /opt/IBMJava2-amd64-142/jre/libj9vm22.so: cannot

open shared object file: No such file or directory libjvm.so failed to

load: j9vm22

Solution:

Proceed as described in SAP Note 1066142.

-----------------------<d023322, 12/JUN/07>--------------------------

Uninstall: Error message FCO-00011

Symptom:

During "Uninstall System / Standalone Engine / Optional Standalone Unit"

you get the following error message:

***********************************************************************

FCO-00011 The step removeSystemUsers with step key

NW_Uninstall ind ind ind ind 0 0 NW_System_Uninstall ind ind ind ind 3

0 NW_System_Uninstall_Users ind ind ind ind 5 0 removeSystemUsers wasexecuted with status ERROR .

***********************************************************************

Solution:

1. Stop sapinst

2. Remove or comment out with "//" the following line in control.xml :

user.removePrivileges(ad.privileges);

3. Restart sapinst with continue old installation

-------------------------<D039055, 01/JUN/07>--------------------------

Uninstall aborts with error message

Symptom:

SAPinst aborts during "Uninstall System / Standalone Engine / Optional

Standalone Unit" with an error message like the following :

**********************************************************************

ERROR 2007-04-26 10:31:05.164

FSH-00006 Return value of function /usr/sbin/userdel is 8.

ERROR 2007-04-26 10:31:05.164

FSL-01004 Unable to delete account user="qe1adm" uid="101".

ERROR 2007-04-26 10:31:05.174

MUT-03025 Caught ESyException in Modulecall: ESAPinstException: errortext undefined.

ERROR 2007-04-26 10:31:05.214

FCO-00011 The step removeSystemUsers with step key

NW_Uninstall ind ind ind ind 0 0 NW_System_Uninstall ind ind ind ind 3

0 NW_System_Uninstall_Users ind ind ind ind 5 0 removeSystemUsers was

executed with status ERROR .

***********************************************************************

Solution:

Proceed as follows:

1. Terminate the "saposcol" process with the command "saposcol -k".

2. Press "Retry" and continue uninstall

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 21/28

06.08.2013 Page 21 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

------------------<D042481, 19/OCT/06 -------------------------------

Error during uninstall on HP-UX: "Login <sid>adm is currently in use"

Symptom

While running one of the installation services under "Additional Software

Lifecycle Tasks -> Uninstall", you get an error like the following in

sapinst_dev.log:

Login qe1adm is currently in use

ERROR 2006-09-18 09:33:57 [syuxcuser.cpp:1084]

CSyUserImpl::remove()

FSH-00006 Return value of function /usr/sbin/userdel is 8.

ERROR 2006-09-18 09:33:57 [syuxcuser.cpp:1092]

CSyUserImpl::remove()

FSL-01004 Unable to delete account user="qe1adm" uid="101".

ERROR 2006-09-18 09:33:57

CJSlibModule::writeError_impl()

MUT-03025 Caught ESyException in Modulecall: ESAPinstException: error

Solution:

stop all processes running with <sid>adm and press RETRY

-----------------<I031421, 11/OCT/06>---------------------------

HA Java: SAPinst hangs during deployment

Symptom: SAPinst hangs during deployment in a HA setup. SDM logs say that

SDM is waiting for a control instance of the cluster to start.

Cause:

SDM uses as a SDM host the local host of the system on which it was

installed, not the HA virtual host.

SDM requests JStartUp to start the central instance and asks regularly

JStartUp if the instance is up and running.

JStartUp returns a list with instances and SDM searches in it for a control

instance running on a host the same as SDM host.

But the control instance on HA system is running with the virtual host

which is not equal with the SDM host (local host).

Solution:

Apply SAP Note 757692.

--------------------<D025095, 23/AUG/06>---------------------------

Although you perform a Unicode installation, SAPinst might also ask for the

non-Unicode kernel DVD. Therefore have this DVD available for the

installation.

---------------------<D026715, 31/MAY/06>----------------------------

Java: Import of software units or usage types fails with message "Access

denied"

Solution:

Proceed as described in related SAP Note 946377.

---------------------<I031908, 19/MAY/06>----------------------------

Sharing same JDK between system based on NetWeaver 7.0 SR3 and other

software

Symptom:You are installing a SAP system based on NetWeaver 7.0 SR3 and want to use

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 22/28

06.08.2013 Page 22 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

a JDK that is already in use for other software packages.

During the installation SAPinst prompts for JDK and JCE Unlimited Strength

Jurisdiction policy archives and uses them to overwrite your JDK's existing

JCE policy archives.

Cause:SAPinst does not set "read" permission for "other" to these archives which

may cause problems in other software using the same JDK.

Solution:Do the following after the installation:

1. Assign "read" permission for "other" to the policy files in

<JDK_HOME>/jre/lib/security of your JDK.

2. Switch the group of the policy files in <JDK_HOME>/jre/lib/security of

your JDK from "sapinst" back to "root".

----------------<D019130,05/DEC/05>------------------

ABAP: UNICODE conversion errorSymptom: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:

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 23/28

06.08.2013 Page 23 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

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.

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.

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

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

-----------------------<04/MAR/11, D029385>-----------------------

Adjust profile parameters as described in SAP Note 1104735

Symptom:

Some profile parameters were not set correctly during the installation.

Solution:

Adjust profile parameters as described in SAP Note 1104735.

-----------------------<18/JUN/09, C5047504 >-----------------------

startsap/stopsap command throws "No instance profile found" error

Symptom:

When you try to start or stop the SAP system with the startsap/stopsap

command, you get a "No instance profile found" error.

Solution:

Make sure that the host names defined in the DNS server match the names of

the SAP system instance hosts. In particular, keep in mind that host names

are case-sensitive. For example, if the names of the SAP system instance

hosts are in upper case, but the same host names are defined in the DNS

server in lower case, starting and stopping the system does not work.

---------------------<I032692, DEC 07, 09>--------------------------

EPC, EP:'WELCOME_CLAUSE' instead of welcome text and user name

Symptom:

Instead of welcome text and the name of the user at the header iView of theportal, a string 'WELCOME_CLAUSE' is displayed.

Solution:

Apply SAP Note 1344869.

-----------------------<19/MAY/09, D042481>--------------------------

AIX: Check user limits for operating system users

Check and - if required - adjust user limits for operating system users as

described in SAP Note 323816.

-------------------<D041479, MAR 05, 2009>----------------------------

Delete usagetype.properties file manually due to security reasonsSymptom:

Once the installation with SAPinst has finished successfully, you have to

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 24/28

06.08.2013 Page 24 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

manually delete the usagetype.properties file.

This file contains data that is not fully secure. It is possible that the

data might be cracked if access is available for a long period. The data

might be outdated by that time in any case, but we cannot guarantee this

because it depends on how you use the system.

Solution:

Proceed as follows:

1. On UNIX, change to directory /usr/sap/<SAPSID>/config

On Windows, change to directory <Drive>:\usr\sap\<SAPSID>\config

2. Delete the usagetype.properties file manually.

-----------------------<24/FEB/09, D041479>--------------------------

Dealing safely with installation directories

Keep all installation directories until you are sure that the system,

including all instances, is completely and correctly installed. Once the

system is completely and correctly installed, make a copy of the

installation directories with all their contents and save it to aphysically separate medium, such as a DVD or a USB drive separate from your

installation hosts. This might be useful for analyzing issues occurring

later when you use the system. For security reasons, do not keep

installation directories on installation hosts, but make sure that you

delete them after saving them separately.

------------------------<05/SEP/08, I043270>---------------------

SCM, ABAP: Error message after installation.

You get the following error in SM21 after installation:

Database error -10709 at CON

> Connection failed (RTE:database not running: no request pipe

To solve the problem install a liveCache.

-------------------<I045708, 24/JUL/08>--------------------------------

ABAP+Java,Java: Keystore views are not created during the very first start

Symptom:

You get an error like the following in

/usr/sap/<SAPSID>/<INSTANCE>/j2ee/cluster/server0/log/defaultTrace.0.trc

File parsed: /usr/sap/QO1/JC00/j2ee/cluster/server0/log/defaultTrace.0.t

FOUND "Line 336: fatal" CREATED ON Wed Jul 2 15:09:28 2008 IN /usr/sap/Q

/JC00/j2ee/cluster/server0/log/defaultTrace.0.trc: #1.5#0017A41132BE002E

000002A000032850004510A33DD78DA#1215004168517#com.sap.engine.services.keystore##com.sap.engine.services.keystore#######Thread[_keystore_manage

 _system_thread_,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Fatal#1#/

System/Security#Java###Source: com.sap.engine.services.security.exceptio

.BaseSecurityException: Unexpected - cannot create a configuration.;

Description: system user based security support for view [TicketKeystore

and user [null] not generated; Consequences: keystore view [TicketKeysto

is not created for user [null]; Countermeasures:see log for details##

FOUND "Line 337: fatal" CREATED ON Wed Jul 2 15:09:28 2008 IN /usr/sap/Q

/JC00/j2ee/cluster/server0/log/defaultTrace.0.trc: #1.5#0017A41132BE002E

000002B000032850004510A33DD79AA#1215004168517#com.sap.engine.services.

keystore##com.sap.engine.services.keystore#######Thread[_keystore_managesystem_thread_,10,SAPEngine_System_Thread[impl:5]_Group]##0#0#Fatal##Jav

(thread: _keystore_managed_system_thread_, view:TicketKeystore , user: n

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 25/28

06.08.2013 Page 25 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

- create view permissions failed:

Solution:

Proceed as described in SAP Note 1230057

-------------------<I043531, 26/MAR/08>--------------------------------

EPC, EP: "HTTP response: 500 - Internal Server Error" when accessing Forms

Builder iView

Symptom:You get an "HTTP response: 500 - Internal Server Error" when trying to

access the Forms Builder iView.

Solution:Proceed as described in SAP Note 1150307.

-------------------<D041727, 04/MAY/07>--------------------------------

Errors in syslog: Unable to create directory

Symptom:

You get an error like the following in the syslog, when you start the

system for the first time:

18:50:23 DIA 000 000 SAPSYS F6 9 Unable to create

directory . Error no. 17

18:50:23 BTC 008 000 SAPSYS F6 7 Directory was created

18:50:26 DIA 000 000 SAPSYS D0 1 Transaction Canceled

BT 513 ( )

18:50:26 DIA 000 000 SAPSYS R6 8 Perform rollback

18:50:26 DIA 000 000 SAPSYS F6 1 TemSe input/output to

unopened file

18:50:26 DIA 000 000 SAPSYS R3 8 Error at DB commit,

return code 001024

Cause:

The DIALOG and BATCH process try to create a directory at the same time.

The DIALOG process fails with error 17 (ALREADY EXIST). The BATCH process

creates the directory successfully.

Further errors in syslog that you can see at that time might be related

this cause. You get these errors only when you start the system for the

first time.

Solution:

You can ignore these errors.

------------------------<D034879, 15/NOV/06>-------------------------

Incorrect permissions of softlinks to sapinit system startup script

Symptom:Incorrect permissions of softlinks to sapinit system startup script are

set. These softlinks should be owned by group root, not group sapinst.

Solution:

You can ignore this issue.

------------------------<D034879, 15/NOV/06>-------------------------

Incorrect permissions of some files under DIR_INSTANCE/j2ee/ctc

Symptom:

Some files under DIR_INSTANCE/j2ee/ctc have incorrect permissions. These

files should be owned by group sapsys, not by group sapinst.

Solution:

You can ignore this issue.

------------------------<D027120, 24/OCT/06>-------------------------

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 26/28

06.08.2013 Page 26 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

Error message when you close SAPinst GUI

Symptom:

Sapinst has finished successfully. However, an error like the following is

written on the console when you close Sapinst GUI:

iauxsysex.c:317: child /tmp/sapinst_exe.4584.1159433231/sapinst (pid 4585)

has crashed. Executable directory is /tmp/sapinst_exe.4584.

1159433231. Contact Support.

iaextract.c:814: child has signaled an exec error. Keeping directory

/tmp/sapinst_exe.4584.1159433231

Solution:

You can ignore this error message.

------------------------<D038283, 08/SEP/06>--------------------------

BI Java / PI: Setting Environment Variable CPIC_MAX_CONV

Proceed as follows:

1. Log on to your SAP system as a user with administration rights and run

transaction RZ10

2. Set the value gw/max_conn_per_wp to a higher value (at least 200) and

restart the system.

------------------------<d020990, 29/MAY/06>--------------------------

Install Replicated Enqueue Server for High Availability (HA)

If you want to install a high-availability system with switchover software,

you need to install the standalone replicated enqueue server.

For a Java system, you must install the standalone replicated enqueue

server. For an ABAP system, we strongly recommend you to install it.

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 2004s -> English -> SAP

NetWeaver Library -> SAP NetWeaver by Key Capability -> Application

Platform by Key Capability -> ABAP Technology -> Client/Server Technology

-> The SAP Lock Concept -> Standalone Enqueue Server -> Installing the

Standalone Enqueue Server

-----------<D031385, 12/APR/06>---------------------------------------

PI: Client copy considerations

We recommend that you use client 001 as source client. However, you can

also use client 000 as source client.

Make sure you use the profile SAP_UCUS.

Do not use the profile SAP_CUST as stated in the SAP Library

documentation .After the client copy, you must logon to your J2EE engine and change the

parameter ume.r3.connection.master.client to the new PI/XI client.

-----------<D034879, 10/APR/06>---------------------------------------

ABAP, ABAP+Java:Check value of parameter rdisp/bufrefmode in DEFAULT.PFL

After the installation, you must check the value of the parameter

rdisp/bufrefmode in DEFAULT.PFL:

o For an SAP NetWeaver 2004s system without dialog instances, the

value must be set to 'sendoff,exeauto'.

o For an SAP NetWeaver 2004s system with dialog instances, the

value must be set to 'sendon,exeauto'.

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 27/28

06.08.2013 Page 27 of 28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

For more information, see SAP Note 14754.

-----------<D041479, 27/MAR/06>-----------------------------------------

(PI): Increase number of dialog work processes

After the installation has finished, you need to increase the number of

dialog work processes to at least 5.

-------------<D002892, 22/MAR/06>------------------------------

Java, ABAP+Java: J2EE Engine reboots permanently

After the successful installation of the SAP system, the J2EE Engine

reboots permanently. To solve the problem, set the VM parameter "-Xss2m"

according to SAP Note 716604.

---------------------<D034879, 17/MAR/06>----------------------------

ABAP dialog instance: check parameter login/system_client

If the profile parameter login/system_client is not set in the defaultprofile, the dialog instance installation will set it to 001.

If client 001 is not your productive client, change the parameter in the

default profile.

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

6 Corrections in the installation guides======================================================================

Header Data

Release Status: Released for Customer

Released on: 31.07.2012 14:04:49

Master Language: English

Priority: Correction with high priority

Category: Installation information

Primary Component: BC-INS Installation Tools

 Valid Releases

Software Component Release From

Release

To

Release

and

Subsequent

SAP_BASIS 70 701 701

Related Notes

7/14/2019 Note 1169801 - Inst.NetWeaver 7.0 EHP1&Business Suite 7 - UNIX.pdf

http://slidepdf.com/reader/full/note-1169801-instnetweaver-70-ehp1business-suite-7-unixpdf 28/28

SAP Note 1169801 - Inst.NetWeaver 7.0 EHP1/Business Suite7 - UNIX

Number Short Text

1701575 Don't unpack old kernel archives when installing DI/AAS

1696716 Creating a modified Solaris kernel medium

1517451 Creating a modified AIX kernel medium

1268493 NW 7.01/BS 7: Inst.Add.Java Usage Types/Software Units

1234384 Inst. NW/SOLMAN 7.0 EhP1/7.0 EhP1 SR1 - Diagnostics Agent

1233080 Client copy creates BI clients

1230057 Keystore views are not created during the very first start

1172733 SAP NetWeaver 7.0 EHP1/Business Suite 7 on UNIX:SAP MaxDB

1159020 SAP NetWeaver 7.0 EHP1/Business Suite 7: IBM DB2 for z/OS

928952 Web Dispatcher Installation based on NW 7.0(2004s)

927508 Standalone Gateway Installation based on NW 7.0(2004s)

789220 Support Package levels for SAP NetWeaver install./upgrades

788151 Post Installation Steps for Groupware after an upgrade

323816 User limits on AIX

 Attachments

File

Type

File Name Language Size

ZIP control.zip E 1,194 KB