SAP Software Provisioning Manager software Operations Guide

Preparing the File System [page 42] .

6. You make the global file system with the renamed

available on the instance hosts of the system that you plan to rename.

For more information, see

7. We strongly recommend that you perform a full system backup before starting the rename procedure, if you do not have other means to restore the original system in case of problems.

3.2 Creating Operating System Users and Groups

During the installation, the installer checks all required accounts (users, groups) and services on the local machine. The installer checks whether the required users and groups already exist. If not, it creates new users and groups as necessary.

The sapinst_instdir directory belongs to a group named sapinst. If this group is not available, it is created automatically as a local group.

Only valid for 'Platform': z/OS

Note

IBM DB2 for z/OS only:

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

C U S T O M E R

Users and groups that need to be created on z/OS need to be created manually before the installation is

started. For more information, see Necessary z/OS Group and User IDs [page 26] .

End of 'Platform': z/OS

If you do not want the installer to create operating system users, groups, and services automatically, you can optionally create them before the installation is started. This might be the case if you use central user management such as Network Information System (NIS).

For distributed installations, unless you are using global accounts or NIS, you must create the target users automatically using the installer or manually on the operating system, before starting the system rename :

Caution

The user ID (UID) and group ID (GID) of SAP users and groups must be identical for all servers belonging to an SAP system.

This does not mean that all users and groups have to be installed on all SAP servers.

IBM DB2 for z/OS only:

Only valid for 'Platform': z/OS

On z/OS, instead of NIS, RACF may be used. For more information, see section Security Settings for z/OS in the Security Guide for SAP on IBM DB2 for z/OS, which is available on the SAP Service Marketplace at http:// service.sap.com/instguidesnw

<Your_SAP_NetWeaver_Release>

Operations Database-Specific

Guides SAP Security Guide: DB2 for z/OS

End of 'Platform': z/OS

The installer checks if the required services are available on the host and creates them if necessary. See the log messages about the service entries and adapt the network-wide (NIS) entries accordingly.

The installer checks the NIS users, groups, and services using NIS commands. However, the installer does not change NIS configurations.

Recommendation

For a distributed or a high-availability system, we recommend that you distribute account information

(operating system users and groups) over the network, for example by using Network Information Service

(NIS).

If you want to use global accounts that are configured on a separate host, you can do this in one of the following ways:

● You start the installer and choose

System Rename Preparation Operating System Users and

Groups

For more information, see

● You create operating system users and groups manually. Check the settings for these operating system users.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

User Settings

●

Only valid for 'Platform': Oracle Solaris

Oracle Solaris: If your operating system is Oracle Solaris 10 or higher, follow the parameter recommendations for SAP applications in SAP Note 724713 .

End of 'Platform': Oracle Solaris

●

Only valid for 'Platform': AIX

AIX: Make sure that you have set the limits for operating system users as described in SAP Note 323816

End of 'Platform': AIX

●

Only valid for 'Platform': HP-UX, Linux, Oracle Solaris

HP-UX, Linux, Oracle Solaris: Make sure that you have set the limits for operating system users root,

<sapsid> adm, and your database-specific operating system users (see also section "Creating Operating

System Users and Groups" and "Running the Installer" in the installation guide).

Caution

Caution: the limit mechanism supports hard and soft limits. The soft limit cannot be bigger than the hard limit. The hard limit can be set/increased by the root user like:

limit -h <limit>

<new_value>

, for example

limit -h datasize unlimited

○ Using csh shell, the output of command limit needs to be at least as follows:

Example

The following table lists example output taken from SUSE Linux Enterprise Server 11 (x86_64).

Table 4:

Output Properties cputime filesize datasize stacksize coredumpsize descriptors memoryuse unlimited unlimited unlimited

8192 KB unlimited

8192 unlimited

○ Using sh or ksh shell, the output of command ulimit -a needs to be at least as follows:

Example

The following table lists example output taken from SUSE Linux Enterprise Server 11 (x86_64).

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

C U S T O M E R

Table 5:

Output sh cpu time (seconds) file size (blocks) data seg size (kbytes) stack size (kbytes) core file size (blocks) open files max memory size (kbytes)

Output ksh cpu time (seconds) file size (blocks) data size (Kibytes) stack size (Kibytes) core file size (blocks) nofile max memory size (Kibytes)

Properties unlimited unlimited unlimited

8192 KB unlimited

8192 unlimited

End of 'Platform': HP-UX, Linux, Oracle Solaris

● All users must have identical environment settings. Any change to the environment – such as variables, or paths – is at your own responsibility.

● The sapinst_instdir directory belongs to a group named sapinst. If this group is not available, it is created automatically as a local group. For security reasons, SAP recommends you to remove the sapinst group from the operating system user groups after the execution of the installer has completed.

● If you have multiple operating system users with user ID (UID) 0, you must assign the sapinst group to all of them.

● Do not delete any shell initialization scripts in the home directory of the operating system users. This applies even if you do not intend to use the shells that these scripts are for.

● Oracle Database only:

If you use NFS-V4 file system, you have to create the ora

<dbsid>

user and - if your database release is

Oracle 12 - the oracle user on the NFS server. You can do this either manually or by running

Operating

System Users and Groups

. This user must have the same user ID as the ora

<dbsid>

user and - if your database release is Oracle 12 - the oracle user on the database server.

Otherwise, you see the error message FSL-02098 Could not change owner of ... during the installation of the database instance.

● SAP MaxDB only:

If you create the sdb user manually, make sure that you lock it for the installation. In most cases, the installer locks this user after it has been created.

● If you install an SAP system with instances distributed over several hosts, make sure that the following requirements are met:

○ The user ID (UID) and group ID (GID) of each operating system user must be unique and the same on each instance host that belongs to the same SAP 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) used during the installation.

For example, if you want to install an additional application server instance for an existing SAP system, you must make sure that the group ID of group sapinst created on the host of the additional application server instance is different from the group ID of any other group on the primary application server instance host of the existing SAP system.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

○ If you use local operating system user accounts instead of central user management (for example,

NIS), users

<sapsid> adm, sapadm, and the database operating system user must have the same password on all hosts.

○ SAP HANA Database only:

○ If you use local operating system user accounts instead of central user management (for example,

NIS), users

<sapsid> adm and sapadm must have the same password on all hosts.

○ If you use local operating system user accounts, make sure that you install your SAP system in

Custom

mode and specify suitable IDs for user

<sapsid> adm and group sapsys on all hosts. The IDs have to be the same on all hosts. If you choose

Typical

mode, you are not asked to specify the user and group IDs.

● If you create operating system users manually or use already existing operating system users, make sure that the home directory for each of these users is not the root directory ( / ) .

● Make sure that the home directory of user

<sapsid> adm is not critical for recursive changes on permissions.

When operating system users are created by the installer, the permissions on the home directories of these users are changed recursively. This can cause unpredictable errors if you define a critical home directory.

For example, the home directory must not be / or /usr/sap.

●

Only valid for 'Platform': HP-UX

HP-UX: To prevent terminal query errors in the

<sapsid> adm environment, comment out the line eval

'tset -s -Q -m ':?hp' in the /etc/skel/.login script. For more information, see SAP Note

1038842 .

End of 'Platform': HP-UX

Operating System Users and Groups

The installer chooses available operating system user IDs and group IDs unless you are installing an additional application server instance. On anadditional application server instance you have to enter the same IDs as on the host of the primary application server instance.

If you have multiple operating system users with user ID (UID) 0, you must assign the sapinst group to all of them.

Recommendation

For security reasons, we recommend that you remove the operating system users from the group sapinst after the installer has completed.

We recommend that you specify this “cleanup” already during the

Define Parameters

phase on the

Cleanup

Operating System Users

screen. Then, the removal of the operating system users from the group sapinst is done automatically.

IBM DB2 for z/OS:

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

C U S T O M E R

Table 6: Users and Their Groups

User

<sapsid>adm root

Table 7: Groups and Members

Groups sapsys

Primary Group sapsys sapsys sapinst

Members

● <sapsid>adm

● root

● <sapsid>adm

● root

SAP MaxDB and SAP HANA Database:

Table 8: Users and Groups

User Primary Group root None

<sapsid> adm

SAP MaxDB only: sqd <dbsid>

SAP MaxDB only: sdb

Table 9: Groups and Members

Groups sapsys sapsys sapsys sdba sapinst

Additional Group sapinst sapinst sapinst, sdba

Members

SAP MaxDB:

SAP HANA database:

<sapsid> adm

SAP MaxDB: root, <sapsid> adm, sqd <dbsid>

SAP HANA database: root, <sapsid> adm

Secondary Groups sapinst sapinst

Description

Superuser of the UNIX oper ating system

SAP system administrator

Owner of database instance

<DBSID>

Database software owner

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

Groups

SAP MaxDB only: sdba

IBM DB2 for Linux, UNIX and Windows:

Table 10: Users and Groups

User

Superuser of the UNIX operating system root

Members sqd <dbsid>

, sdb

SAP system administrator<sapsid>adm

ABAP connect user sap<sapsid>

Note

Only used on the database host.

Primary Group

No primary group is assigned by the installer (additional group is sapinst) sapsys (db<dbsid>ctl as secondary group) db<dbsid>mon db2<dbsid>

Note

Only used on the database host.

db<dbsid>adm (sapinst as secondary group)

Table 11: Groups and Members

Groups sapsys db<dbsid>ctl db<dbsid>adm db<dbsid>mnt db<dbsid>mon

Members

<sapsid>adm

db2<dbsid>

ABAP connect user sap<sapsid>

Oracle:

Table 12: SAP System Users and Groups

User Primary Group root

Additional Groups

No primary group assigned by the installer.

sapinst

Comment

Superuser of the UNIX operat ing system

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

C U S T O M E R

User

<sapsid> ora adm

<dbsid> oracle

Primary Group sapsys dba dba

Table 13: SAP System Groups and Members

Groups sapsys oper dba sapinst asmoper asmadmin

Additional Groups Comment oper, dba, sapinst

The following groups are al ways required for Oracle 12, but for Oracle 11 only if you want to use Oracle ASM: asmoper, asmdba

SAP system administrator and for Oracle 12 the default data base administrator oper, sapinst, oinstall

Database administrator

This user is only required on the host where the database in stance runs.

oper, sapinst, asmoper, asmadmin, asmdba, oinstall

Oracle Software Owner and da tabase administrator

This user is only required on the host where the database in stance runs.

This user is only required for

Oracle 12 or Oracle 11 with

ASM/Exadata.

Members

<sapsid> adm

, oracle (always required for

Oracle 12; for Oracle 11 only required if you want to use

Oracle ASM)

, oracle (always required for

Oracle 12; for Oracle 11 only required if you want to use

Oracle ASM) root, <sapsid> adm, ora <dbsid>

, oracle (always re quired for Oracle 12; for Oracle 11 only required if you want to use Oracle ASM)

<sapsid> adm (always required for Oracle 12; for Oracle 11 only required if you want to use Oracle ASM), Oracle oracle (always required for Oracle 12; for Oracle 11 only re quired if you want to use Oracle ASM)

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

Groups asmdba

Members

<sapsid> adm (always required for Oracle 12; for Oracle 11 only required if you want to use Oracle ASM), Oracle oinstall (always required for Oracle 12; for Oracle 11 only required if you want to use Oracle ASM) oracle (always required for Oracle 12; for Oracle 11 only re quired if you want to use Oracle ASM), ora

<dbsid>

SAP Adaptive Server Enterprise:

Table 14: Users and Groups

User:

UNIX superuser root

SAP system administrator <sapsid>adm syb<dbsid>

Note

Only used on the database host.

Primary Group:

No primary group assigned by SAPinst (group

sapinst

is as signed as secondary group).

sapsys

(

sapinst

as secondary group)

sapsys

SAP Host Agent:

Table 15: User and Groups of the SAP Host Agent

User Primary Group Additional Group sapadm sapsys –

Comment

SAP Host Agent administrator

Note

If sapadm does not exist, it is cre ated during the SAP Host Agent installation using /bin/false shell.

Make sure that /bin/false can be used as a login shell.

Only valid for 'Platform': AIX

AIX: Add /bin/false to the list of valid login shells (attribute shells) in /etc/security/ login.cfg.

End of 'Platform': AIX

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

C U S T O M E R

Table 16: Groups and Members of the SAP Host Agent User

Groups Members sapsys sapinst sapadm sapadm

3.3 Necessary z/OS Group and User IDs

The following are lists of the group and z/OS user IDs necessary for your SAP system on z/OS. If these group or user IDs do not already exist in your system, you must create them.

For more information, see section Security Settings for z/OS in the Security Guide for SAP on IBM DB2 for

z/OS, which is available on the SAP Service Marketplace at http://service.sap.com/instguidesnw

<Your_SAP_NetWeaver_Release>

Operations Database-Specific Guides SAP Security Guide: DB2 for z/OS

Users and Groups for z/OS

Table 17: Necessary z/OS Group and User IDs

Group/User ID

Database Administration User ID

DB Connect User ID for AS ABAP

Description Usage Type

AS ABAP Temporary user needed for the SAP installation.

Permanent user needed for the database connec tion. You are free to choose the name of this user. If you are installing both usage types, we advise you to choose different names for the user IDs for AS

ABAP.

AS ABAP

Group ID for ABAP Schema Permanent group needed for the ABAP schema.

This group ID must be the same as the name of the

ABAP schema that you specify during installation. If you are installing both usage types, you must choose different names for the group IDs for ABAP schema and Java schema.

AS ABAP

Users and Groups for z/OS UNIX System Services

Before the installation, you must create each of the following groups and users in RACF for your SCS or ASCS instance on z/OS UNIX System Services.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

For each group and user listed in the following table, you must create an entry in the table /etc/ ualiastable, to ensure that each group and user can be used in both upper and lowercase.

Table 18: Necessary z/OS UNIX System Services Group and User IDs

Group/User ID Description Usage Type sapsys

<dasid>

Group ID

User ID to install an SAP central serv ices instance on z/OS sapinst adm User ID

Group ID adm User ID sapadm User ID

Permanent group needed for the central serv ices instance on z/OS.

AS ABAP

AS Java

Diagnostics Agent

SAP Host Agent

Permanent user needed for the central services instance on z/OS.

AS ABAP

Temporary user needed for the SAP central services instance installation.

AS ABAP

Diagnostics Agent

SAP Host Agent

Permanent group needed for the central serv ices instance on z/OS.

AS ABAP

Diagnostics Agent

Permanent user needed by the Diagnostics

Agent.

Permanent user needed by the SAP Host

Agent.

AS ABAP

Diagnostics Agent

AS ABAP

Diagnostics Agent

SAP Host Agent

Caution

The user ID (UID) and group ID (GID) of SAP users and groups must be identical for all servers belonging to an SAP system.

This does not mean that all users and groups have to be installed on all SAP servers.

Enhanced ASCII Setup on z/OS

To enable enhanced ASCII support, see the procedure in section

User ID

and

to Run the

Host and Diagnostics Agent on z/OS

in the Security Guide for SAP on IBM DB2 for z/OS, which is available on the SAP Service Marketplace at http://service.sap.com/instguidesnw

<Your_SAP_NetWeaver_Release>

Operations Database-Specific Guides SAP Security Guide: DB2 for z/OS

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

C U S T O M E R

3.4 Performing a System Copy by Copying the File System

You can duplicate a source SAP system by copying the file system, and then rename the target system to obtain two separate SAP systems. This section describes how to copy the file system of a source SAP system and its database.

Prerequisites

You have shut down the SAP system including the database and the instance agents.

● To check that they are stopped, enter the following command:

ps -ef | grep <source_SAPSID>

● In addition, you can also make sure that the services of the system instances are stopped by executing the following command as user

<sapsid> adm:

sapcontrol -nr <InstanceNumber> -function StopService

Procedure

●

Note

Make sure that during the copy of the file system, the links are not dereferenced.

● If you have a central system, proceed as follows: a. On the target host, copy /usr/sap/

to /usr/sap/

<target_SAPSID>

b. On the target global host, copy /

to /

● If you have a distributed system, proceed as follows: a. Export the file system under /

including its subdirectories exe, global, and profile from the global host.

b. Mount the exported file system /

on all other hosts of the distributed system.

c. Remove the directories of the source system, which have been moved from the list of NFS exported file systems under /

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

3.5 Deleting Additional Application Server Instances

The system rename procedure does not implicate additional application server instances. Therefore, if additional application server instances are installed on your system, delete them before you start the rename procedure, and reinstall additional application server instances as required after the system rename.

Prerequisites

● You have installed your SAP system with standard SAP tools according to the installation documentation.

● You have made the media available that you used for installing the system on the additional application server instance host that you want to delete.

Context

Note

You cannot delete an additional application server instance remotely. You have to run the tool to delete them locally on each additional application server instance host.

All file systems and subdirectories of the selected additional application server instance are deleted during the uninstall process.

The uninstall process is designed to remove as much of the additional application server instance as possible.

If an item cannot be removed, a message informs you that you have to remove this item manually. As soon as you confirm the message, the uninstall process continues.

Procedure

1. Start the tool as described in

Performing Preparation Steps for IBM DB2 for Linux, UNIX, and Windows [page 30]

2. On the

Welcome

screen, choose

<SAP_Product>

Software Life-Cycle Options Uninstall

3. Follow the instructions in the input dialogs to delete an additional application server instance.

Note

For more information about the input parameters, place the cursor on the relevant field and press

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

C U S T O M E R

3.6 Database-Specific Preparation

You have to do some preparation steps in the database of the system you want to rename.

Make sure you have completed the preparation steps for your database as described in the relevant section below.

Performing IBM DB2 for z/OS – Specific Preparation Steps [page 33]

Performing Oracle-Specific Preparation Steps [page 35]

Performing SAP ASE -Specific Preparation Steps [page 36]

Performing SAP MaxDB-Specific Preparation Steps [page 37]

Performing SAP liveCache-Specific Preparation Steps [page 38]

Performing SAP liveCache Client-Specific Preparation Steps [page 39]

Performing SAP HANA Database-Specific Preparation Steps [page 40]

3.6.1 Performing Preparation Steps for IBM DB2 for Linux,

UNIX, and Windows

This section describes prerequisites and preparation steps that you have to perform for IBM DB2 for Linux,

UNIX, and Windows before starting the system rename procedure.

Prerequisites

● The database is up and running.

● The patch level of db6util is patch level 10 or higher. For more information, see SAP Note

1776691 .

● The patch level of the brdb6brt tool is patch level 32 or higher.

If tool brdb6brt does not exist within the /sapmnt/

<SAPSID> /exe directory, download and install it as described in SAP Note 511323 . Information about the latest patches of tool brdb6brt you can find in

SAP Note 867914 .

● IBM DB2 for Linux, UNIX, and Windows V10.1 and Higher only:

Make sure that your

<sapsid> adm user has execute permission for function sysproc.admin_get_storage_paths by running the following command on your source system as user db2

<dbsid>

db2 "grant execute on specific function sysproc.admin_get_storage_paths to user

<sapsid>adm"

● The version of SAP Host Agent must be 7.21 PL 1 or higher.

Only valid for 'Platform': HP-UX

If your operating system is HP-UX, the version of SAP Host Agent must be 7.20 PL 157 or higher.

End of 'Platform': HP-UX

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

●

Only valid for 'Platform': Oracle Solaris

If your operating system is Solaris SPARC or Solaris X86_64, the database version must be 9.7 FP7 or higher.

End of 'Platform': Oracle Solaris

Procedure

1. Create the relocate.template file as described below. This file is required in the tool dialog phase.

a. On the source system, log on as user db2

<dbsid>

and create the directory sapdbctrl-config under /tmp. This does not apply if the directory already exists.

Note

If directory /tmp does not exist, you must create it before you perform the steps listed below.

Proceed as follows:

1. Execute cd /tmp.

2. Execute mkdir ./sapdbctrl-config

3. Log off from the system.

b. Log on again as user root on the source system.

c. Execute cd /usr/sap/hostctrl/exe.

d. Execute ./saphostctrl -function PrepareDatabaseCopy -dbname

<DBSID> -dbtype db6

-dbconfdir /tmp/sapdbctrl-config/ -dbinstance db2 <dbsid> -copymethod Offline.

The system creates the relocate.template file in the /tmp/sapdbctrl-config directory.

Check if the file relocate.template contains one or more entries for CONT_PATH or

STORAGE_PATH. If not you must not start the system rename procedure.

This is an example of the files created in the sapdbctrl-config directory: root@db6xen008[Linux]/tmp/sapdbctrl-config > ls -la total 28 drwxr-x--- 2 db2ph5 dbph5adm 4096 Oct 6 23:51 .

drwxr-xr-x 9 db2ph5 dbph5adm 4096 May 16 13:36 ..

-rw-r----- 1 db2ph5 dbph5adm 2584 Oct 11 09:23 db2ph5.cfg

-rw-r--r-- 1 root root 46 Oct 11 09:23 db2ph5.net

-rw-r--r-- 1 root root 8810 Oct 11 09:23 relocate.template

2. Provide all database-related directories on the target system. This includes the following directories:

○ /db2/

<DBSID> /

○ The file system of the home directory of db2sid (default:/db2/db2

<dbsid>

To provide the required directories, use one of the following methods:

Note

The commands below are given as an example if your home directory is db2

<dbsid>

. You have to adjust them for all required directories.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

C U S T O M E R

○ If the source and the target system are located on one and the same host, proceed as follows:

If you want to adjust or rename your SAP system on the same host, keep all directories at their locations.

The tool will find and move them to the correct directory and set the required ownerships and permissions.

Note

If /db2/db2

<dbsid>

or /db2/

<DBSID>

is a mount point or there are mount points under these directories (for example /db2/

<DBSID> /sapdata1 is a mount point), proceed as follows:

1. Stop the SAP system including its instance agents.

2. Unmount the mount points.

3. Before you start the system rename, mount the file systems under the target

<DBSID>

or db2 <dbsid>

○ If the source and the target system are located on different hosts, proceed in one of the following ways:

○ Mount all file systems manually on the target system

Recommendation

This is the recommended option.

Note

If /db2/db2

<dbsid>

or /db2/

<DBSID>

is a mount point or there are mount points under these directories (for example /db2/

<DBSID> /sapdata1 is a mount point), then mount the file systems under the target

<DBSID>

or db2

<dbsid>

○ Copy the directories using the copy command of the operating system.

Note

When you provide required database related directories on the target host, use the source

<DBSID>

within the directory names. The tool will find and move them to the correct location and set the required ownerships and permissions.

To keep the current ownership of the directory and softlinks, use an archiving tool as follows:

source host:~ # tar -cpf /tmp/db2<dbsid_source>.tar /db2/db2<dbsid_source> source host:~ # tar -cpf /tmp/<DBSID_source>.tar /db2/<DBSID_source> source host:~ # scp /tmp/db2<dbsid_source>.tar <user>@<dbsid_source>:/tmp source host:~ # scp /tmp/<DBSID_source>.tar <user>@<target host>:/tmp target host:~ # tar -xvf /tmp/db2<dbsid_source>.tar /db2/db2<dbsid_source> target host:~ # tar -xvf /tmp/<DBSID_source>.tar /db2/<DBSID_source>

3. Make sure the contents of the db6_update_db.SAR archive attached to SAP Note 1365982 are available in the sapdbctrl-config directory.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

Note

Make sure the permissions of file db6_update_db.sh and db6_update_db.jar are rwxr-xr-x. To check the file permissions, enter the following command:

ls -l db6_update_db.sh db6_update_db.jar

To change the file permission enter the following command:

chmod 755 db6_update_db.sh db6_update_db.jar

4. Make sure that you stop all system and database processes before you start the system rename procedure. To check that they are stopped, enter the following command:

ps -ef | grep db2

3.6.2 Performing IBM DB2 for z/OS – Specific Preparation

Steps

This section describes the prerequisites and preparation steps that you have to perform for IBM DB2 for z/OS before starting the system rename procedure.

Context

No rename actions are performed on the database subsystem itself.

There are two types of renaming:

Procedure

● Rename of an SAP system without copying the IBM DB2 for z/OS subsystem:

○ The application server is renamed; no changes are made on the IBM DB2 for z/OS subsystem.

○ The renamed SAP system stays connected to the original IBM DB2 for z/OS subsystem

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

C U S T O M E R

Figure 1: Rename of an SAP System without copying the IBM DB2 for z/OS Subsystem

● Rename of an SAP system after copying the IBM DB2 for z/OS subsystem.

Before running the tool , you have to copy your IBM DB2 for z/OS database using the offline system copy method.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

Figure 2: Rename of an SAP System after copying the IBM DB2 for z/OS Subsystem

For more information about the system copy procedure, see the SAP Note 680746 .

3.6.3 Performing Oracle-Specific Preparation Steps

This section describes prerequisites and preparation steps that you have to perform for the Oracle database before starting the system rename procedure.

Procedure

1. For the offline backup method, we recommend that you shut down the database. Alternatively, the installer can also make an instance recovery of the database if it has not been shut down before the copy process. For the online backup method, you have to set the database to a backup mode and the backup control files and the Oracle archives will be copied to an existing shared directory. You can set the database to a backup mode using the following command:

saphostctrl -function PrepareDatabaseCopy -dbname <DBSID> -dbtype ora -dbconfdir

<shared_directory> -copymethod Online -timeout -1

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

C U S T O M E R

After the database backup has finished, you have to set the database back to a normal mode using the following command:

saphostctrl -function FinalizeDatabaseCopy -dbname <DBSID> -dbtype ora dbconfdir <shared_directory> -copymethod Online -timeout -1

2. Copy the required files and directories contained under the /oracle directory from the source host to the target host. These are at least the following directories with all contained subdirectories and files:

<DBSID>

, stage, oraInventory, client

○ Make sure that all Oracle files, especially the control files, are stored under SAPDATA_HOME. If the control files are not located in SAPDATA_HOME, it is not possible to set the permissions for them.

○ If /oracle/

<DBSID>

is a mount point or there are mount points under /oracle/

<DBSID>

(for example /oracle/

<DBSID> /sapdata1 is a mount point), proceed as follows:

1. Stop the SAP system including its instance agents.

2. Unmount the mount points.

3. Before you start the system rename, mount the file systems under the new database system ID

(

<DBSID>

3.6.4 Performing SAP ASE -Specific Preparation Steps

This section describes the prerequisites and preparation steps that you have to perform for SAP ASE before starting the system rename procedure.

Procedure

1. Stop the SAP system and the source database server.

2. Prepare the filesystem for the system rename. You can apply one of the following scenarios:

Note

The commands below are given as an example. We assume that your home directory is /sybase/

<DBSID>

. You must adjust them according to your needs for all required directories.

○ Adjust or rename an SAP System on the same host with no mount points:

If you want to adjust or rename your SAP system on the same host and there are no mount points under /sybase/

<DBSID>

, keep all directories at their locations. The installer will find and move them to the correct directory and set the required ownerships and permissions.

○ Adjust or rename an SAP System on the same host with mount points:

If you want to adjust or rename your SAP system on the same host and there are mount points under /sybase/

<DBSID_Source>

, you must remount all file system at the new location /sybase/

<DBSID_Target>

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

Note

If /sybase/

<DBSID>

is a mount point or there are mount points under /sybase/

<DBSID>

- for example, /sybase/

<DBSID> /sapdata_1 is a mount point - proceed as follows:

1. Unmount the mount points.

2. Mount the file systems under the new SAP system ID.

○ Create a copy system on the same host:

If you want to create a copy of the system on the same host, use the following command to copy the directories keeping the current ownerships and permissions:

cp -pPr /sybase/<DBSID_Source> /sybase/<DBSID_Target>

○ Create a copy system on a different target host:

If the source and the target system are located on different hosts, proceed in one of the following ways:

○ If mount points are involved, mount all file systems manually on the target system

○ If no mount points are involved, copy the directories using the copy command of the operating system.

source host:~ # scp -r /sybase/<DBSID_Source> <User>@<Target_Host>:/ sybase/<DBSID_Target>

3.6.5 Performing SAP MaxDB-Specific Preparation Steps

This section describes the prerequisites and preparation steps that you have to perform for SAP MaxDB before starting the system rename procedure.

Procedure

1. On the target host, create the SAP MaxDB OS group sdba and the SAP MaxDB OS user sdb. The group and the user must have the same IDs as on the source host.

2. Make available the entire SAP MaxDB file system content from the source host on the target host with the following directories (if available), while keeping the ownership and access permissions:

/sapdb/ <SOURCE_DBSID> /

/sapdb/clients/

/sapdb/programs

/sapdb/data

/etc/opt/sdb

/usr/spool/sql

/var/lib/sdb

3. If the directories are implemented on the mount points, pay attention to the following:

○ The directory /sapdb/

<SRC>

is implemented as a mount point.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

C U S T O M E R

In this case, the rename procedure creates directory /sapdb/

<TRG>

, which does not contain a mounted file system. The procedure transfers the contents of /sapdb/

<SRC>

to /sapdb/

<TRG>

. You must therefore make sure that there is enough space in file system /sapdb/ to store the contents of / sapdb/ <SRC>

○ The mount points below directory /sapdb/

<SRC> / are subject to the same restrictions.

○ SAP Note

2346237 describes the process for configuring mount points during the system name procedure.

4. Check free space in the SAP MaxDB directories:

○ The /sapdb/

<SOURCE_DBSID> / directory must contain enough space to locate the archives of the following subdirectories: db data

○ The /sapdb/clients/

<SOURCE_DBSID>

directory must contain enough free space to locate the archives of all subdirectories.

5. Make sure that you stop all system and database processes before you start the rename procedure. You can check this by using the following call:

ps -efa | grep sdb

3.6.6 Performing SAP liveCache-Specific Preparation Steps

This section describes the prerequisites and preparation steps that you have to perform for SAP liveCache before starting the system rename procedure.

Procedure

1. On the target host, create the SAP liveCache OS group sdba and the SAP liveCache OS user sdb. The group and the user must have the same IDs as on the source SAP liveCache host.

2. Make available the entire SAP liveCache file system content from the source host on the target host with the following directories (if available), while keeping the ownership and access permissions:

/sapdb/ <SOURCE_LVC> /

/sapdb/clients/

/sapdb/programs

/sapdb/data

/etc/opt/sdb

/usr/spool/sql

/var/lib/sdb

3. If the directories are implemented on the mount points, pay attention to the following:

○ The directory /sapdb/

<SRC>

is implemented as a mount point.

In this case, the rename procedure creates directory /sapdb/

<TRG>

, which does not contain a mounted file system. The procedure transfers the contents of /sapdb/

<SRC>

to /sapdb/

<TRG>

. You

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

must therefore make sure that there is enough space in file system /sapdb/ to store the contents of / sapdb/ <SRC>

○ The mount points below directory /sapdb/

<SRC> / are subject to the same restrictions.

○ SAP Note

2346237 describes the process for configuring mount points during the system name procedure.

4. Check free space in the SAP liveCache directories:

○ The /sapdb/

<SOURCE_LVC> / directory must contain enough space to locate the archives of the following subdirectories: db data

○ The /sapdb/clients/

<SOURCE_LVC>

directory must contain enough free space to locate the archives of all subdirectories.

5. Make sure that you stop all system and database processes before you start the rename procedure. You can check this by using the following call:

ps -efa | grep sdb

6. Make sure that there are no temporary files in the file system when you start the system rename process.

3.6.7 Performing SAP liveCache Client-Specific Preparation

Steps

This section describes the prerequisites and preparation steps that you have to perform for SAP liveCache client before starting the system rename procedure.

Context

These steps are not required if the SAP liveCache Server is also located on the same host and SAP liveCache

Server-specific preparation steps are already done or will be done.

Procedure

1. On the target host, create the SAP liveCache OS group sdba and the SAP liveCache OS user sdb. The group and the user must have the same IDs as on the source SAP liveCache client host.

2. Make available the entire file system content of the SAP liveCache client from the source host on the target host with the following directories (if available), while keeping the ownership and access permissions:

/sapdb/clients/

/sapdb/programs

/sapdb/data

/etc/opt/sdb

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

C U S T O M E R

/usr/spool/sql

/var/lib/sdb

3. Check free space in the SAP liveCache client directories:

The /sapdb/clients directory must contain enough space to locate the archives of all subdirectories.

3.6.8 Performing SAP HANA Database-Specific Preparation

Steps

This section describes the prerequisites and preparation steps that you have to perform forSAP HANA database before starting the system rename procedure.

Context

You can use the installer only for renaming the application server instances, and the ABAP central services instance , but you can not rename the SAP HANA database with this tool. If you want to rename the SAP HANA database, you have to do this as a separate step in advance .

Procedure

You perform the rename for the SAP HANA database as described in section Changing the SAP HANA System in the SAP HANA Administration Guide at http://help.sap.com/hana_platform

System

Administration

3.7 Preparing the System Rename Media

This section describes how to prepare the media required for the system rename procedure.

Note

The signature of media is checked automatically by the installer during the

Define Parameters

phase while processing the

Media Browser

screens. As of now the installer only accepts media whose signature has been checked. See also the description of this new security feature in SAP Note 2393060 .

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

Related Information

Downloading and Extracting the Software Provisioning Manager Archive [page 41]

3.7.1 Downloading and Extracting the Software Provisioning

Manager Archive

You must always download and extract the Software Provisioning Manager 1.0 archive from the SAP Software

Download Center because you must use the latest version.

Procedure

1. Download the latest version of the Software Provisioning Manager 1.0 archive

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR from: https://launchpad.support.sap.com/#/softwarecenter

SUPPORT PACKAGES & PATCHES By

Alphabetical Index (A-Z) S SOFTWARE PROVISIONING MANAGER

2. Get the latest version of the SAPCAR tool on the host where you want to run the installer: a. Go to https://launchpad.support.sap.com/#/softwarecenter

SUPPORT PACKAGES &

PATCHES

and search for “

sapcar

”.

b. Select the archive file for your operating system and download it to an empty directory.

c. Rename the executable to

sapcar.exe

For more information about SAPCAR, see SAP Note 212876 .

3. Using the latest version of SAPCAR, you can verify the signature of the downloaded

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR archive as follows: a. Get the latest version of the SAPCRYPTOLIB archive to your installation host as follows:

1. Go to https://launchpad.support.sap.com/#/softwarecenter

SUPPORT PACKAGES &

PATCHES

and search for “

sapcryptolib

”.

2. Select the archive file for your operating system and download it to the same directory where you have put the SAPCAR executable.

3. Use the following command to extract the SAPCRYPTOLIB archive to the same directory where you have put the SAPCAR executable:

sapcar –xvf sapcryptolibp_84…sar –R <target directory>

4. Download the Certificate Revocation List from

https://tcs.mysap.com/crl/ crlbag.p7s

and move it into the same directory.

b. Verify the signature of the downloaded

SWPM10SP <Support_Package_Number> _ <Version_Number> .SAR archive by executing the following command:

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

C U S T O M E R

Note

Check SAP Notes 2178665 and 1680045 whether additional information is available.

/<Path to SAPCAR>/sapcar -tvVf <Path to Download Directory>/

SWPM10SP<Support_Package_Number>_<Version_Number>.SAR -crl<file name of revocation list>

4. Unpack the Software Provisioning Manager archive to a local directory using the following command:

/<Path to SAPCAR>/sapcar -xvf <Path to Download Directory>/

SWPM10SP<Support_Package_Number>_<Version_Number>.SAR <Path to Unpack Directory>

Note

Make sure that all users have read permissions for the directory where you want to unpack the installer.

Caution

Make sure that you unpack the Software Provisioning Manager archive to a dedicated folder. Do not unpack it to the same folder as other installation media.

3.8 Preparing the File System

Use this step to make the file system available on the system that you plan to rename.

Prerequisites

You have performed the database specific preparation steps.

Note

You have to mount the file system before you start the system rename procedure.

Procedure

● If your system is a central system (all system instances reside on one host) and the /usr/sap/

and /

directories are mount points, proceed as follows: a. Stop the SAP system including its instance agents.

○ To check that they are stopped, enter the following command:

ps -ef | grep <source_SAPSID>

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

○ In addition, you can also make sure that the services of the system instances are stopped by executing the following command as user

<sapsid> adm:

sapcontrol -nr <InstanceNumber> -function StopService

b. Unmount the mount points /usr/sap/

<source_SAPSID>

and /

c. Before you start the system rename, mount the file system, which you have unmounted in the previous step, under the new

● If your system is a distributed system, proceed as follows: a. Stop all SAP system instances including their instance agents.

○ To check that they are stopped, enter the following command:

ps -ef | grep <source_SAPSID>

○ In addition, you can also make sure that the services of the system instances are stopped by executing the following command as user

<sapsid> adm:

sapcontrol -nr <InstanceNumber> -function StopService

b. Unmount /

<sapmnt> / <Source_SAPSID> /* directories on all system hosts.

c. Remove /

<sapmnt> / <Source_SAPSID> /* from the list of mounted file systems on all system hosts.

d. Move /

on all hosts.

e. Adapt the file system exports on the global host. You can do this using a tool for your operating system, such as YaST2 on SuSE Linux. Proceed as follows:

1. Remove /

<sapmnt> / <Source_SAPSID> /* from the list of export file systems.

2. Add /

<sapmnt> / <Target_SAPSID> /* to the list of export file systems.

f. Export the file system.

g. Mount /

<sapmnt> / <Target_SAPSID> /* on all system hosts. Make sure that the file system will also be mounted after a reboot. You can do that using a tool for your operating system, such as YaST2 on

SuSE Linux.

Related Information

Database-Specific Preparation [page 30]

Running the Installer [page 48]

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

Preparation

C U S T O M E R

4 System Rename Procedure

4.1 System Rename Procedure Checklist

This section includes the renaming steps that you have to perform for the following options:

● Standard system

● Distributed system

The installer adapts the SAP system on an operating system level. The system parameters are adapted offline.

The installer automatically starts the following instances during the system rename:

● Database

● Instance agents of a UNIX operating system

● ABAP Central services instance (ASCS instance) if an ASCS instance is available

Central System

You check the Prerequisites for Running the Installer [page 45] and run the installer to rename the system as

described in

Running the Installer [page

Distributed and High-Availability System

Note

See also table System Rename Options and Sequence how to Execute Them in

48]

1. If your SAP system has an ASCS instance, you check the

Prerequisites for Running the Installer [page

45]

and run the installer to rename the ASCS instance as described in Running the Installer [page 48]

2. You make sure that the global directories (exe, profile, global) are exported to the instance hosts of the SAP system to be renamed.

If your SAP system has an ASCS instance and the ASCS instance host is the SAP global host of the system, you export the global directories to the database instance host, to the primary application server instance host, and – if required – to the additional application server instance hosts of the SAP system to be renamed.

For more information, see

Preparing the File System [page 42] .

3. You check the

Running the Installer [page 48]

and run the installer to rename the database instance as described in

4. You check the

primary application server instance as described in Running the Installer [page 48]

and run the installer to rename the

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

5. Optional: You check the

and run the installer to rename existing standalone Gateway instances as described in

6. Optional: You check the

and run the installer to rename the SAP Web Dispatcher instance as described in

follow-up activities [page 67]

Next Steps

You perform

4.2 Prerequisites for Running the Installer

Make sure you fulfil the following prerequisites before running the installer.

● If you want to use the SL Common GUI, make sure that the following web browser requirements are met:

○ You have one of the following supported browsers on the device where you want to run the SL

Common GUI: Google Chrome, Mozilla Firefox, Microsoft Edge, or Microsoft Internet Explorer 11.

Always use the latest version of these web browsers.

Recommendation

We recommend using Google Chrome.

○ If you copy the SL Common GUI URL manually in the browser window, make sure that you open a new

Web browser window in private browsing mode (Internet Explorer), incognito mode (Chrome) or private browsing mode (Firefox). This is to prevent Web browser plugins and settings from interfering with the SL Common GUI.

For more information about the SL Common GUI, see Useful Information About the Installer [page 54] .

● We recommend that you use the csh shell for the installation. If you want to use another shell, make sure that you have read SAP Note 202227 .

The installer 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 the installer, execute the following command as user

<sapsid> adm to make sure that the csh scripts are up-to-date:

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

● Make sure that your operating system does not delete the contents of the temporary directory /tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for example by using a crontab entry.

Make sure that the temporary directory has the permissions 777.

● Make sure that you have at least 300 MB of free space in the installation directory for each installation option. In addition, you need 300 MB free space for the installer executables. If you cannot provide 300

MB free space in the temporary directory, you can set one of the environment variables TEMP, TMP, or

TMPDIR to another directory with 300 MB free space for the installer executables.

You can set values for the TEMP, TMP, or TMPDIR environment variable to an alternative installation

directory as described in section Useful Information About the Installer [page 54]

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

C U S T O M E R

● The following information is only valid if you use the Java GUI:

Make sure that your DISPLAY environment variable is set to

<Host_Name>:0.0

, where

<Host_Name>

is the host on which you want to display the installer GUI.

You can set values for the DISPLAY environment variables as follows:

Table 19:

Shell Used Command

Bourne shell (sh)

DISPLAY=<Host_Name>:0.0

export DISPLAY

C shell (csh)

Korn shell (ksh)

setenv DISPLAY <Host_Name>:0.0

export DISPLAY=<Host_Name>:0.0

● Make sure that umask is set to

022

for the user with root permissions that you want to use for running the installer.

As the user with root permissions that you want to use for running the installer, enter the following command:

umask 022

●

Only valid for 'Platform': AIX

AIX: Make sure that you have set the limits for operating system users as described in SAP Note 323816

End of 'Platform': AIX

●

Only valid for 'Platform': HP-UX, Linux, Oracle Solaris

HP-UX, Linux, Oracle-Solaris: Make sure that you have set the limits for operating system users root,

<sapsid> adm, and your database-specific operating system users (see also section "Creating Operating

System Users and Groups" and "Running the Installer" in the installation guide).

Caution

Caution: the limit mechanism supports hard- and soft-limits. The soft-limit cannot be bigger than the hard-limit. The hard-limit can be set/increased by the root user like:

limit -h <limit>

<new_value>

, for example

limit -h datasize unlimited

○ Using csh shell, the output of command limit needs to be at least as follows:

Example

The following table lists example output taken from SUSE Linux Enterprise Server 11 (x86_64).

Table 20:

Output Properties cputime filesize datasize unlimited unlimited unlimited

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

Output stacksize coredumpsize descriptors memoryuse

Properties

8192 KB unlimited

8192 unlimited

○ Using sh or ksh shell, the output of command ulimit -a needs to be at least as follows:

Example

The following table lists example output taken from SUSE Linux Enterprise Server 11 (x86_64).

Table 21:

Output sh Output ksh Properties cpu time (seconds) file size (blocks) data seg size (kbytes) cpu time (seconds) file size (blocks) data size (Kibytes) unlimited unlimited unlimited stack size (kbytes) core file size (blocks) open files max memory size (kbytes) stack size (Kibytes) core file size (blocks) nofile max memory size (Kibytes)

8192 KB unlimited

8192 unlimited

End of 'Platform': HP-UX, Linux, Oracle Solaris

● Make sure that the following ports are not used by other processes:

○ When using the SL Common GUI:

○ Port 4237 is used by default as HTTPS port for communication between the installer and the SL

Common GUI.

If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter:

SAPINST_HTTPS_PORT=<Free Port Number>

○ Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer processing.

The filled-out evaluation form is then sent to SAP using HTTPS.

If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter:

SAPINST_HTTP_PORT=<Free Port Number>

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

C U S T O M E R

○ When using the Java SDT GUI:

○ Port 21212 is used by default for communication between the installer GUI server and the installer

GUI client.

If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter:

SAPINST_DIALOG_PORT=<Free Port Number>

○ Port 4239 is used by default for displaying the feedback evaluation form at the end of the installer processing.

The filled-out evaluation form is then sent to SAP using HTTPS.

If this port cannot be used, you can assign a free port number by executing sapinst with the following command line parameter:

SAPINST_HTTP_PORT=<Free Port Number>

● If you want to change the host name of your system, change the computer name and the host name on OS level and make sure that the host name resolution and UNC paths work.

For more information, see SAP Note 129997 .

If you want to change the virtual host name, see SAP Note 962955 .

● SAP ASE: Make sure the system and database are not running when starting the installer.

● IBM DB2 for z/OS: Check that your hosts meet the requirements for the installer options that you want to perform.

4.3 Running the Installer

This section describes how to run the installer to perform the system rename .

Prerequisites

For more information, see Prerequisites for Running the Installer [page 45]

Context

Software Provisioning Manager (the “installer” for short) offers two GUIs:

● The new web browser-based “SL Common GUI of the Software Provisioning Manager” - “SL Common

GUI” for short

● The “classic” Java-based GUI with a CUI client and server - “Java SDT GUI” for short

Note

If the SL Common GUI does not meet your requirements you can still use the “classic” Java SDT GUI.

You then have to start the sapinst executable with the command line option

SAPINST_SLP_MODE=false

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

In cases where both GUIs behave the same way, we address them as “installer GUI”.

For more information, see Useful Information About the Installer [page 54] .

This procedure describes an installation where you use one of the following GUI scenarios:

● You run the installer and use the SL Common GUI. Then you can control the processing of the installer in the browser running on any device.

● You run the installer and use the Java SDT GUI. Both are running on the same host.

The following information is only valid if you use the Java SDT GUI:

● If you need to see the installation on a remote display, we recommend that you

perform a remote installation [page 59] , where the installer GUI is running on a separate host from the installer.

● Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to the installer GUI on Windows workstations. For more information, see SAP Note 1170809 .

Procedure

1. Log on to the host where you want to run the installer.

Make sure that you log on as a user with root permissions.

Caution

Make sure that this user has not set any environment variables for a different SAP system or database.

Caution

Do not use an existing

<sapsid> adm user.

SL Common GUI only: If your security policy requires that the person running the installer is not allowed to know the credentials of a user with root permissions on the host where the installer is to perform the system rename , you can specify another operating system user for authentication purposes. You do this using the SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command line. You have to confirm that the user is a trusted one. For more information, see SAP Note

1745524 .

2. Make the required media available.

For more information, see

Recommendation

Make the installation media available locally . For example, if you use Network File System (NFS), reading from media mounted with NFS might fail.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

C U S T O M E R

Only valid for 'Platform': Oracle Solaris

Note

If you mount installation media, make sure that you do this with option

nomaplcase

End of 'Platform': Oracle Solaris

3. Start the installer as follows:

Open a command prompt and enter the following command:

/<Path_To_Unpack_Directory>/sapinst

The installer GUI starts automatically by displaying the

Welcome

screen.

Note

If you want to use a virtual host name, start the installer with the installer property

SAPINST_USE_HOSTNAME as follows:

/<Path_To_Unpack_Directory>/sapinst SAPINST_USE_HOSTNAME=<Virtual_Host_Name>'

Caution

Make sure that the installation directory is not mounted with NFS, or there might be problems when starting the Java Virtual Machine.

4. The installer is starting up.

Depending on the type of the installer GUI you want to use, do one of the following:

○ If you use the SL Common GUI, the installer now starts and waits for the connection with the SL

Common GUI.

You can find the URL you require to access the SL Common GUI at the bottom of the shell from which you are running the installer.

Sample Code

...

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

*******

Open your browser and paste the following URL address to access the GUI https://[ <hostname> ]:4237/sapinst/docs/index.html

Logon users: [ <users> ]

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

*******

...

If you have a supported web browser (see

information in section Implementing Oracle Database Vault with the Installer [page 74]

) installed on the host where you run the installer, you can open this URL directly in the shell. Otherwise open the

URL in a supported web browser that runs on another device.

The SL Common GUI opens in the browser by displaying the

Welcome

screen.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

Note

Before you reach the

Welcome

screen, your browser might warn you that the certificate of the sapinst process on this computer could not be verified. Accept this warning to inform your browser that it can trust this site, even if the certificate could not be verified.

○ If you use the Java SDT GUI - that is you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

, the Java SDT GUI starts automatically by displaying the

Welcome

screen.

5. In the

Welcome

screen, proceed according to your system variant :

○ If your system is a standard system , choose

System Rename Standard System System

Rename

○ If your system is a distributed system, choose

System Rename Distributed System

<System_Rename_Option>

Choose the system rename options as required and in the order they appear.

Table 22: System Rename Options and Sequence how to Execute Them

Option Description When to Execute Execution Order

System Rename for ASCS

Instance

System Rename for ERS

Instance

Executes system rename for the ASCS instance

If your system does not have an ASCS instance, skip this option.

First step for systems with

AS ABAP, if they have an

ASCS instance

Executes system rename for the ERS instance

If your system does not have an ERS instance, skip this option.

Execute this option after you have performed the rename option for the

ASCS instance (if availa ble) above, as required

System Rename for Data base Instance

Executes system rename for the database instance

Execute in any case (even if you change the SAP sys tem ID, the host name or the instance number)

Execute this option after you have performed the rename options for the

ASCS instance (if availa ble) and the ERS instance above, as required

System Rename for the

Primary Application

Server Instance

Executes system rename for the primary application server instance

Execute this option after renaming the database in stance.

Execute this option after you have performed the rename options for the

ASCS instance (if availa ble), the ERS instance, and the database instance above, as required

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

C U S T O M E R

Option Description When to Execute Execution Order

System Rename for a

Gateway Instance

Executes system rename for a standalone Gateway instance

If your system host does not have a standalone

Gateway instance, skip this option.

Execute this option after you have performed the rename options for the

ASCS instance (if availa ble), the ERS instance, the database instance, and the primary application server instance above, as required

System Rename for Web

Dispatcher Instance

Executes system rename for the SAP Web Dis patcher instance

If your system does not have an SAP Web Dis patcher instance, skip this option.

Execute this as last option

6. Choose

Next

7. Follow the instructions in the installer input screens and enter the required parameters.

Note

To find more information on each parameter during the

Define Parameters

phase, position the cursor on the required parameter input field :

○ If you use the SL Common GUI, choose either

F1 displayed in the

HELP

tab.

or the

HELP

tab. Then the available help text is

○ If you use the Java SDT GUI, choose

. Then a dialog opens with the available help text.

Note

IBM DB2 for Linux, UNIX, and Windows only: When you are asked for the security administrator, enter a user that has DB2 SECADM authorities. By default, db2

has these authorities.

Note

○ Oracle only:

In the

ABAP Schema Name

screen, make sure that the name of the ABAP schema is correct.

○ Oracle Database only: If your source system has Oracle Database Vault, consider the additional

Caution

The signature of media is checked automatically during the

Define Parameters

phase while processing the

Media Browser

screens.

Keep in mind that this automatic check is only committed once and not repeated if you modify artefacts such as SAR archives or files on the media after the initial check has been done - that is if you modify artefacts later on either during the remaining

Define Parameters

phase or later on during the

Execute Service

phase the signature is not checked again.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

See also the description of this new security feature in SAP Note 2393060 .

8. After you have entered all requested input parameters, the installer displays the

Parameter Summary

screen. This screen shows both the parameters that you entered and those that the installer set by default.

If required, you can revise the parameters before starting the system rename procedure.

9. To start the execution, choose

Next

The installer starts the rename procedure and displays its progress on the

Task Progress

screen.

The installer starts the export and displays its progress of the system copy export during the processing phase.

When the system rename option has finished successfully, the installer displays the message

Execution of

<Rename_Option>

has completed

10. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after the installer has finished.

Sometimes these remain in the temporary directory.

Note

If there are errors with the installer extraction process, you can find the log file dev_selfex.out in the temporary directory.

Recommendation

Keep all installer 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 installer directories with all their contents. Save the copy to a physically separate medium, such as a medium or a USB drive that is separate from your installation hosts.

This might be useful for analyzing any issues that might occur later when using the system. For security reasons, do not keep the installer directories on hosts where you processed it, but make sure that you delete them after saving them separately.

11. If you copied installation media to your hard disk, you can delete these files when the installer has successfully completed.

12. Java GUI only: For security reasons, we recommend that you delete the .sdtgui directory within the home directory of the user with which you ran the installer:

<User_Home> /.sdtgui/

13. For security reasons, we recommend that you remove the operating system users from the group sapinst after you have completed the installation.

Note

This step is only required, if you did not specify during the

Define Parameters

phase that the operating system users are to be removed from the group sapinst after the execution of the installer has completed.

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

C U S T O M E R

Related Information

Useful Information About the Installer [page 54]

Interrupted Processing of the Installer [page 56]

Performing Remote Processing of the Installer (Java SDT GUI only) [page 59]

Starting the Java SDT GUI Separately [page 61]

Running the Installer in Accessibility Mode [page 63]

Troubleshooting with the Installer [page 65]

4.4 Additional Information About the Installer

The following sections provide additional information about the installer.

Related Information

Useful Information About the Installer [page 54]

Interrupted Processing of the Installer [page 56]

Performing Remote Processing of the Installer (Java SDT GUI only) [page 59]

Starting the Java SDT GUI Separately [page 61]

Running the Installer in Accessibility Mode [page 63]

Troubleshooting with the Installer [page 65]

4.4.1 Useful Information About the Installer

This section contains some useful technical background information about the installer and the installer GUI.

● Software Provisioning Manager (the installer) offers two GUIs:

○ The new web browser-based “SL Common GUI of the Software Provisioning Manager” - “SL Common

GUI” for short

○ The “classic” Java-based GUI with a CUI client and server - “Java SDT GUI” for short

The SL Common GUI of the Software Provisioning Manager (or “SL Common GUI” for short) uses the SAP

UI Development Toolkit for HTML5 - also known as SAPUI5 - a client-side HTML5 rendering library based on JavaScript. The benefits of this new user interface technology for the user are:

○ Zero foot print, since only a web browser is required on the client

○ New controls and functionality, for example, view logs in web browser.

The SL Common GUI connects the web browser on a client with the sapinst executable - which is part of

Software Provisioning Manager - running on the installation host using the standard protocol HTTPS.

For the SL Common GUI the installer provides a pre-generated URL at the bottom of the shell from which you are running the installer . If you have a supported web browser installed on the host where you run the

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

installer, you can start the SL Common GUI directly from this URL. Otherwise, open a web browser supported by the SL Common GUI on any device and run the URL from there.

For more information about supported web browsers see

Prerequisites for Running the Installer [page

45]

If the SL Common GUI does not meet your requirements, you can still use the “classic” Java SDT GUI. To do so, you must start the sapinst executable with the command line option

SAPINST_SLP_MODE=false

You can switch back to the default installer GUI at any time with the following steps:

1. Stop the installer.

2. Restart the installer with command line option

SAPINST_SLP_MODE=false

3. On the

What do you want to do?

screen choose

Continue with the existing run

● The installer creates the installation directory sapinst_instdir directly below the temporary directory.

The installer finds the temporary directory by checking the value of the TEMP, TMP, or TMPDIR environment variable. If no value is set for these variables, the installer uses /tmp as default installation directory.

If you want to use an alternative installation directory, set the environment variable TEMP, TMP, or TMPDIR to the required directory before you start the installer.

Table 23:

Shell Used Command

Bourne shell (sh)

TEMP=<Directory> export TEMP

C shell (csh)

Korn shell (ksh)

setenv TEMP <Directory> export TEMP=<Directory>

Caution

Make sure that the installation directory is not mounted with NFS, otherwise there might be problems when the Java Virtual Machine is started.

● For each option, the installer creates a subdirectory located in the sapinst_instdir directory.

● The installer extracts itself to the temporary directory. These executables are deleted again after the installer has stopped running.

Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You can safely delete them.

The temporary directory also contains the log file dev_selfex.out from the extraction process, which might be useful if an error occurs.

Caution

If the installer cannot find a temporary directory, the installation terminates with the error FCO-00058.

● To see a list of all available installer properties, start the installer as described above with the option

-p

./sapinst -p

● This information is only relevant if you use the Java GUI of the installer: If you need to run the installer in accessibility mode, proceed as described in

Running the Installer in Accessibility Mode [page 63]

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

C U S T O M E R

● If required, stop the installer by choosing one of the following, depending on the installer GUI you use:

○ In the SL Common GUI, choose the

Cancel

button.

○ In the Java SDT GUI, choose

SAPinst Exit Process

in the Java SDT GUI menu..

Note

If you need to terminate the installer, press

Ctrl

4.4.2 Interrupted Processing of the Installer

Here you find information about how to restart the installer if its processing has been interrupted.

Context

The processing of the installer might be interrupted for one of the following reasons:

● An error occurred during the

Define Parameters

Execute

phase:

The installer does not abort the installation in error situations. If an error occurs, the installation pauses and a dialog box appears. The dialog box contains a short description of the choices listed in the table below as well as a path to a log file that contains detailed information about the error.

● You interrupted the installation by choosing

○

Cancel

in the SL Common GUI

○

Exit Process

in the

SAPinst

menu in the Java SDT GUI

Caution

If you stop an option in the

Execute

phase, any system or component installed by this option is incomplete and not ready to be used. Any system or component uninstalled by this option is not completely uninstalled.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

The following table describes the options in the dialog box:

Table 24:

Option Definition

Retry

Stop

The installer retries the installation from the point of failure without repeating any of the previous steps.

This is possible because the installer records the installation progress in the keydb.xml file.

We recommend that you view the entries in the log files, try to solve the problem, and then choose

Retry

If the same or a different error occurs, the installer displays the same dialog box again.

The installer stops the installation, closing the dialog box, the installer GUI, and the

GUI server.

The installer records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps. See the procedure below.

Continue

View Log

The installer continues the installation from the current point.

Access installation log files.

The following procedure describes the steps to restart an installation, which you stopped by choosing

Stop

, or to continue an interrupted installation after an error situation.

Procedure

1. Log on to the installation host as a user with the required permissions as described in Running the Installer

[page 48]

2. Make sure that the media required for the system rename are still available.

For more information, see

Recommendation

Make the installation media available locally. For example, if you use remote file shares on other

Windows hosts, CIFS shares on third-party SMB-servers, or Network File System (NFS), reading from media mounted with NFS might fail.

Only valid for 'Platform': Oracle Solaris

Note

Oracle Solaris: If you mount installation media, make sure that you do this with option

nomaplcase

End of 'Platform': Oracle Solaris

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

C U S T O M E R

3. Restart the installer from the directory to which you unpacked the Software Provisioning Manager archive by executing the following command:

<Path_To_Unpack_Directory>/sapinst

4. The installer is restarting.

Depending on the type of the installer GUI you want to use, do one of the following:

○ If you use the SL Common GUI, the installer now starts and waits for the connection with the SL

Common GUI.

You can find the URL you require to access the SL Common GUI at the bottom of the shell from which you are running the installer.

Sample Code

...

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

*******

Open your browser and paste the following URL address to access the GUI https://[ <hostname> ]:4237/sapinst/docs/index.html

Logon users: [ <users> ]

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

*******

...

If you have a supported web browser (see

● The remote host meets the prerequisites for starting the installer as described in

) installed on the host where you run the installer, you can open this URL directly in the shell. Otherwise open the

URL in a supported web browser that runs on another device.

The SL Common GUI opens in the browser by displaying the

Welcome

screen.

Note

Before you reach the

Welcome

○ If you use the Java SDT GUI - that is you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

, the Java SDT GUI starts automatically by displaying the

Welcome

screen.

5. From the tree structure on the

Welcome

screen, select the installation option that you want to continue and choose

Next

The

What do you want to do?

screen appears.

6. On the

What do you want to do?

screen, decide between the following alternatives and continue with

Next

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

Table 25:

Alternative

Perform a new run

Continue with the existing one

Behavior

The installer does not continue the interrupted system rename option. Instead, it moves the content of the old installer directory and all installer-specific files to a backup directory. Afterwards, you can no longer continue the old option.

The following naming convention is used for the backup directory: log_ <Day> _ <Month> _ <Year> _ <Hours> _ <Minutes> _ <Seconds>

Example log_01_Oct_2016_13_47_56

Note

All actions taken by the system rename before you stopped it (such as cre ating directories or users) are not revoked.

Caution

The installer moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly.

The installer continues the interrupted system rename from the point of fail ure.

4.4.3 Performing Remote Processing of the Installer (Java

SDT GUI only)

Here you find information about how to process the installer on a remote host.

Note

This section is only valid if you use the Java SDT GUI. That is, you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

Prerequisites

Prerequisites for

Running the Installer [page 45]

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

C U S T O M E R

● Both computers are in the same network and can ping each other.

To test this:

1. Log on to your remote host and enter the command:

ping <Local_Host>

2. Log on to the local host and enter the command:

ping <Remote_Host>

● If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER command line parameter, make sure that this user exists on the remote host.

Context

You use this procedure to process the installer on a remote host. In this case, the installer runs on the remote host, and the installer GUI runs on the local host. The local host is the host from which you control the installation with the installer GUI. The installer GUI connects using a secure SSL connection to the installer.

If your security policy requires that the person performing the installation by running the installer GUI on the local host is not allowed to know the credentials of a user with root permissions on the remote host, you can specify another operating system user for authentication purposes. You do this using the

SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command line.

You have to confirm that the user is a trusted one. For more information, see SAP Note 1745524 .

Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to the installer GUI on Windows workstations. For more information, see SAP Note 1170809 .

Procedure

1. Log on to the remote host as a user with root permissions.

Caution

Make sure that this user has not set any environment variables for a different SAP system or database.

2. Make the installation media available on your remote host.

For more information, see

Starting the Installer GUI Separately [page 61]

Recommendation

Make the installation media available locally . For example, if you use Network File System (NFS), reading from media mounted with NFS might fail.

Only valid for 'Platform': Oracle Solaris

Note

Oracle Solaris: If you mount installation media, make sure that you do this with option

nomaplcase

End of 'Platform': Oracle Solaris

3. Open a command prompt and change to the directory to which you unpacked the Software Provisioning

Manager archive.

C U S T O M E R

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

4. Check the version of the sapinst executable by entering the following command:

<Path_To_Unpack_Directory>/sapinst -sfxver

The version of the sapinst executable must be exactly the same as the version of the sapinstgui executable on the local host (see also

5. Start the installer by entering the following command:

<Path_To_Unpack_Directory>/sapinst

Note

If you need to specify another operating system user for authentication purposes, enter the following command:

<Path_To_Unpack_Directory>/sapinst

SAPINST_REMOTE_ACCESS_USER=<Specified_OS_User>

Note

If you are running a system copy with parallel export/import using the Migration Monitor and started the export with command line option

SUPPORT_DECLUSTERING=false

, you have to start the installer for the installation of the target database instance with command line option

SUPPORT_DECLUSTERING=true

for the import during the target system installation.

For more information, see the system copy guides at http://support.sap.com/sltoolset

Provisioning System Copy Option Guide for Systems Based on SAP NetWeaver 7.1 & Higher

System

The installer now starts and waits for the connection to the installer GUI. You see the following at the command prompt: guiengine: no GUI connected; waiting for a connection on host <Host_Name> , port

<Port_Number> to continue with the installation

6. Start the installer GUI on your local host as described in

Starting the Installer GUI Separately [page 61]

4.4.4 Starting the Java SDT GUI Separately

Here you find information about how to start the Java SDT GUI separately.

Note

This section is only valid if you use the Java SDT GUI. That is, you started the sapinst executable with command line option

SAPINST_SLP_MODE=false

System Rename for SAP Systems Based on the Application Server of SAP NetWeaver 7.1 to

7.5 ABAP on UNIX

System Rename Procedure

C U S T O M E R

Prerequisites

The host on which you want to start the installer GUI meets the prerequisites for starting the installer as described in