Sap System Rename

SAP System Rename GuideSAP System Rename for SAP Systems Based on SAP NetWeaverUsing SAPinst

Target Audience ■ System administrators ■ Technology consultants

PUBLICDocument version: 1.0 – 2011-11-28

Document History

CAUTION

Before you start the implementation, make sure you have the latest version of this document.

You can find the latest version at the following location: http://service.sap.com/

instguides.

The following table provides an overview of the most important document changes.

Version Date Description

1.0 2011-11-28 Initial version

2/32 PUBLIC 2011-11-28

http://service.sap.com/instguides


Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 SAP Notes for the SAP System Rename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.2 How to Use this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.1 Maintaining Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.2 Mounting the File System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.3 Checking Profile Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3.4 Performing a System Copy by Copying the File System . . . . . . . . . . . . . . . . . . 10

3.5 Deleting Dialog Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.6 Database-Specific Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.6.1 Performing Preparation Steps for IBM DB2 for Linux, UNIX, and

Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.6.2 Oracle-Specific Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.6.3 Performing SAP MaxDB-Specific Preparation Steps . . . . . . . . . . . . . . . . . . . . . 14

3.6.4 Performing Microsoft SQL Server-Specific Preparation Steps . . . . . . . . . . . . . . 15

3.7 Preparing the System Rename Installation Media . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 4 Renaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.1 Running SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 5 Follow-up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.1 General Follow-Up Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.2 Performing Follow-Up Activities for SAP MaxDB . . . . . . . . . . . . . . . . . . . . . . . 23

Chapter A Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

A.1 The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2011-11-28 PUBLIC 3/32

This page is left blank for documents that are printed on both sides.

1 Introduction

This document explains how to rename an SAP system with the SAP System Rename tool. This tool

is part of the installation tool SAPinst.

The procedure described in this guide is valid for SAP systems based on SAP NetWeaver with the

following release levels:

■ SAP NetWeaver 7.0

■ SAP NetWeaver 7.0 including Enhancement Package 1



CAUTION

You should perform a system rename using SAPinst only if your SAP system is installed with

standard SAP tools according to the installation documentation available at

service.sap.com/instguides .

In the case of deviations from this documentation, you act on your own responsibility. Be aware

that additional consulting effort might be necessary.

Constraints

You need to consider the following constraints before you start the system rename:

■ Windows only: The renaming of a high availability system is not supported.

■ The following operating system and database releases listed in the Product Availability Matrix

(PAM) are not available for SAP System Rename:

● IBM DB2 for Linux, UNIX, and Windows on Windows

● IBM DB2 for Linux, UNIX, and Windows versions lower than 9.1 including fix pack 10

● Sybase ASE

● zOS/IBM DB2 for z/OS

● AS400/IBM DB2 for i

For a comprehensive list of supported operating system and database releases, see the PAM at:

http://service.sap.com/pam .

Use Cases

With the SAP System Rename tool you can adapt the following parameters of an SAP system:

■ SAP system ID

■ Database ID

■ Instance numbers of the instances on the SAP system

1 Introduction

2011-11-28 PUBLIC 5/32

http://service.sap.com/pam

■ Host names

This is required in the following cases:

■ You want to rename an existing system.

■ You performed a system copy by copying the file system [page 10] of a source SAP system and its database

and want to rename the target system.

1.1 SAP Notes for the SAP System Rename

Read the following SAP Notes before you start SAP System Rename. These SAP Notes contain the most

recent information on SAP System Rename as well as corrections to the relevant documentation. Make

sure that you have the most recent version of each SAP Note. You can find all SAP Notes at http://

service.sap.com/notes.

SAP Notes for SAP System Rename

SAP Note Number Title Description

1619720 SAP System Rename for SAP Systems based on SAP NetWeaver

Problems discovered after the publication of the SAP System Rename guide

1.2 How to Use this Guide

This documentation comprises the description of the system rename procedure using SAPinst and

system-rename-specific steps. For general or system-copy-specific information, see the system copy

documentation relevant for your release, which you can find at: http://service.sap.com/

instguides .

1. You decide on the system parameters you want change in the rename process.

2. You follow the steps in each phase:

■ Planning [page 7]

■ Preparation [page 9]

■ Renaming [page 17]

■ Follow-Up Activities [page 23]

1 Introduction

1.1 SAP Notes for the SAP System Rename

6/32 PUBLIC 2011-11-28

http://service.sap.com


http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1619720&_NLANG=en&_NVERS=0



2 Planning

This section includes the planning steps that you have to perform when you want to rename an SAP

system using SAPinst.

Relevance

■ The system rename procedure is valid for the following environments:

● ABAP

● Java

● Dual-Stack (ABAP and Java)

■ You can perform the system rename on both central and distributed systems.

■ With the system rename procedure, you can rename the following instances:

● Database instance

● Central instance

● SAP Central Services for Java or ABAP

● Enqueue Replication Server

NOTE

You cannot use the SAP System Rename tool to rename dialog instances.

If you have installed dialog instances, you have to do the following:

1. Delete the dialog instances manually [page 11] from the system before the system rename.

2. Reinstall the dialog instances on the system after the system rename.

2 Planning

2011-11-28 PUBLIC 7/32


3 Preparation

This section includes the preparation steps that you have to perform when you want to rename an

SAP system using SAPinst.

3.1 Maintaining Users and Groups

SAPinst checks whether the required users and groups already exist. If not, it creates new users and

groups as necessary. If you do not want SAPinst to create operating system users and groups

automatically, you can optionally create them before the system rename process with SAPinst.

This step is mandatory only in the following cases:

■ Your operating system is HP-UX.

■ You want to use global accounts that are configured on separate hosts.

In all other cases, this step is optional.

Procedure

1. Log on to your SAP system as described in Running SAPinst [page 17].

2. On the Welcome screen, choose System Rename Additional Preparation Options Operating System Users

and Groups .

3.2 Mounting the File System

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

NOTE

If your operating system is UNIX, you have to mount the file system before you start the system

rename.

If your operating system is Windows, you do not have to perform these preparatory steps.

Procedure

UNIX

■ If /usr/sap/<SID> and /<sapmnt>/<SID> are mount points, you have to do the following:

1. Stop the SAP system including its instance agents.

2. Unmount the mount points /usr/sap/<source SID> and /<sapmnt>/<source SID>.

3. Mount the file system under the new SAP system ID before you start the system rename.

3 Preparation

3.1 Maintaining Users and Groups

2011-11-28 PUBLIC 9/32

■ If your system is a distributed system, you have to do the following in addition:

1. Export the file system under /<sapmnt>/<target SID> including its subdirectories exe,

global, and profile from the global host.

2. Mount the exported file system /<sapmnt>/<target SID> on all other hosts of the distributed

system.

3. Delete the old file system exports under /<sapmnt>/<source SID>.

Windows

■ If you want to perform the system rename on a central system, you can start the rename without

any further preparatory steps.

■ If you want to perform the system rename on a distributed system, you have to prepare the SAP

global host. To do this, run SAPinst [page 17] and choose System Rename Distributed System Prepare

SAP Global Host .

3.3 Checking Profile Parameters

Unlike in SAP systems based on SAP NetWeaver 7.1 or higher, the storage of the kernel in /usr/sap/

<SAPSID>/SYS/exe/(n)uc/<os> linking to /<sapmnt>/<SID>/exe/(n)uc/<os> is not supported.

Therefore, make sure that the DIR_CT_RUN profile parameter of the source system points to /usr/sap/

<SAPSID>/SYS/exe/run, which is linked to /<sapmnt>/<SID>/exe.

NOTE

This step is only required for UNIX systems.

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 services (Windows) or

instance agents (UNIX).

Procedure

Windows

■ For each instance that you want to rename, copy the respective file system X:\usr\sap\<SID> of

the source system to Y:\usr\sap\<target SID> on the target instance host.

3 Preparation

3.3 Checking Profile Parameters

10/32 PUBLIC 2011-11-28

■ If the share saploc already exists on the target host, copy the file system X:\usr\sap\<SID> of your

source system to \\saploc\<target SID>.

If the share saploc does not exist, assign a drive to saploc which will then be created.

UNIX

If you have a central system, proceed as follows:

1. On the target host, copy /usr/sap/<SID> to /usr/sap/<target SID>.

2. On the target global host, copy /<sapmnt>/<SID> to /<sapmnt>/<target SID>.

If you have a distributed system, proceed as follows:

1. Export the file system under /<sapmnt>/<target SID> including its subdirectories exe, global,

and profile from the global host.

2. Mount the exported file system /<sapmnt>/<target SID> on all other hosts of the distributed

system.

3. Delete old file system exports under /<sapmnt>/<source SID>.

3.5 Deleting Dialog Instances

The system rename procedure does not implicate dialog instances. Therefore, if dialog instances are

installed on your system, delete them before you start the rename procedure, and install dialog instances

newly as required after the system rename.

NOTE

You cannot delete a dialog instance remotely. You have to run SAPinst to delete them locally on

each dialog instance host.

Prerequisites

■ You have installed your SAP system with standard SAP tools according to the installation

documentation.

■ You are logged on with a user account that has the required authorization to run the SAPinst tool.

For more information, see Required User Authorization for Running SAPinst in the installation

documentation for your SAP solution at http://service.sap.com/instguides .

CAUTION

Do not use the user <sapsid>adm to delete the SAP system.

■ On the dialog instance host that you want to delete, you have made available the Installation Master

DVD that you used to install the system.

Procedure

During the uninstall process, all file systems and subdirectories of the selected dialog instance are

deleted.

3 Preparation

3.5 Deleting Dialog Instances

2011-11-28 PUBLIC 11/32


The uninstall process is designed to remove as much as possible of the dialog instance to be deleted. 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.

1. Start SAPinst from the Installation Master of your release as described in Running SAPinst [page

17].

2. On the Welcome screen, choose Software Life-Cycle Options Uninstall .

3. Follow the instructions in the SAPinst input dialogs to delete a dialog instance.

NOTE

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

press F1 in SAPinst.

4. Windows only:

When you have finished, delete the local user group SAP_<SAPSID>_LocalAdmin manually as

follows:

1. Choose Start Programs Administrative Tools Computer Management .

2. Choose Local Users and Groups Groups .

3. Right-click the local group SAP_<SAPSID>_LocalAdmin and choose Delete.

3.6 Database-Specific Preparation

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 using SAPinst.

NOTE

The system rename using SAPinst is not available for IBM DB2 for Linux, UNIX, and Windows on

Windows.

Prerequisites

The database is up and running.

Procedure

1. Create the relocate.template file. This file is required in the SAPinst dialog phase.

Proceed as follows:

1. On the source system, log on as user db2<dbsid> and create the directory sapdbctrl–

config under /db2/db2<DBSID>/. This does not apply if the directory already exists.

Proceed as follows:

1. Execute cd /db2/db2<DBSID>/.

2. Execute mkdir ./sapdbctrl–config

3 Preparation


12/32 PUBLIC 2011-11-28

3. Log off from the system.

2. On the source system, log on again as user root.

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

4. Execute export LD_LIBRARY_PATH=/usr/sap/hostctrl/exe.

5. Execute ./sapdbctrl prepareCopy <DBSID> -c/db2/db2<DBSID>/sapdbctrl-config -t

db6 -m Offline.

In the directory /db2/db2<sid>/sapdbctrl-config, the system creates the

relocate.template file.

SYNTAX

This is an example for the relocate.template file:

root@db6xen008[Linux]/db2/db2ph5/sapdbctrl-config > ls -la total 28drwxr-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. Copy all file systems that are related to the database. This includes the following:

■ /db2/<SID, DBSID>/

■ The file system of the home directory of db2sid (default:/db2/db2>dbsid>)

■ The file system of the database software (default: /db2/db2>dbsid>/db2_software)

NOTE

The technical names of the file systems in your system may deviate from the default.

3. Mount all file systems that contain the database ID of the source system manually under the

database ID of the target system.

3.6.2 Oracle-Specific Preparation

This section describes prerequisites and preparation steps that you have to perform for the Oracle

database before starting the system rename using SAPinst.

UNIX

■ As of Oracle release 11.2.03, ORACLE_HOME automatically points to /oracle/<SID>/1120x as relative

link. If you use an older Oracle version and have created an absolute link, you have to delete the

original link and create a relative link.

■ 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, the permissions for them can not be set.

Windows

■ You have shut down the database.

■ You have installed the Oracle database software on the target system.

3 Preparation


2011-11-28 PUBLIC 13/32

With the SAP System Rename tool, it is not possible to rename the Oracle database software

automatically.

For more information about how to install the Oracle database software, see the installation

documentation of your release and stack at: http://service.sap.com/instguides.

3.6.3 Performing SAP MaxDB-Specific Preparation Steps

This section describes prerequisites and preparation steps that you have to perform for SAP MaxDB

before starting the system rename procedure.

Prerequisites

Windows

■ You have copied the file system of the source system. Make sure that the drives where the files are

stored on the target system are the same as on the source system.

■ You have not manually renamed files before starting the SAPinst rename procedure.

UNIX

You have manually copied the entire file system with the following directories (if available):

■ /sapdb/<SID>/

■ /sapdb/clients/

■ /sapdb/programs

■ /sapdb/data

■ /etc/opt/sdb

■ /usr/spool/sql

Procedure

Windows

1. Create a database-specific configuration file sapdbConfig.txt, which describes the software of the

source system and store it locally on the host.

EXAMPLE

Database-specific configuration file sapdbConfig.txt

IndepDataPath=c:/sapdb/data

GlobalProgramsPath=c:/sapdb/programs

<source_DBSID>=c:/sapdb/ <source_DBSID>/db

<source_DBSID>/PrivateDataPath=c:/sapdb/ <source_DBSID>/data

CL_<source_DBSID>/PrivateDataPath=c:/sapdb/clients/<source_DBSID>/data

3 Preparation


14/32 PUBLIC 2011-11-28


2. If you want to rename an existing system on the same host, make sure that you shut down the

SAP system including the database and that all SAP and SAP MaxDB related services are offline

before your start SAPinst. To check this, verify that the services Xserver* and MaxDB* are stopped.

3. Deregister the database instance and the database software. to do so, open a command prompt as

administrator and enter the following:

<drive:>\sapdb\programs\pgm\dbmcli –d<SID> -u controlUser,controlPassword

db_offline

<drive:>\sapdb\programs\pgm\dbmcli –d<SID> -u controlUser,controlPassword db_unreg

<drive:>\sapdb\programs\pgm\dbmcli –R\sapdb\<SID>\db inst_unreg

<drive:>\sapdb\<SID>\db\bin\x_server stop

<drive:>\sapdb\<SID>\db\bin\x_server remove

UNIX

1. If you copied the file system from a server different than the server of the target system, create an

sdba user and an sdba group on the target system. The user ID and the group ID must both

correspond to the ID of the source system. Make sure that the user sdba is locked.

2. Since the System Rename tool is not able to rename mountpoints, you have to adapt mountpoints

under /sapdb manually to the target system.

3. Adapt the directories /sapdb/<SID>, /sapdb/clients/<SID>, and /sapdb/<SAP SID> to the system

ID of the target system using the command mv.

4. Make sure that you stop all system and database processes before you start the SAPinst rename

procedure. You can check this by using the call ps –efa | grep sdb.

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

process.

3.6.4 Performing Microsoft SQL Server-Specific Preparation Steps

This section describes prerequisites and preparation steps that you have to perform for Microsoft SQL

Server before starting the system rename using SAPinst.

NOTE

You only have to perform these steps if you want to copy your system as described in Performing a

System Copy by Copying the File System [page 10].

If you plan to rename a correctly configured SAP system or a clone of such a system, manual

preparation is not required.

Prerequisites

The database instance is up and running.

3 Preparation


2011-11-28 PUBLIC 15/32

Procedure

1. Detach the source system database.

2. Copy the database files from the source system to the target system.

3. Attach the source system database again.

4. Attach the copied database files as <source_DBSID> to the SQL Server on the target host.

NOTE

Make sure that you use the same database name on the target system as on the source system

because SAPinst checks for the name of the source database during the system rename

procedure.

3.7 Preparing the System Rename Installation Media

This section describes how to prepare the installation media that is required for the system rename

using SAPinst.

Procedure

1. Download the installation media from the software distribution center on SAP Service Marketplace

using the following path:

http://service.sap.com/swdc Installations and Upgrades Ramp-Up Releases and Beta Software

Installation and Upgrade SAP LANDSCAPE VIRT MGT STD 1.0 SAP System Rename .

2. Create a download directory on the host on which you want to run SAPinst

3. Download the software to the download directory.

3 Preparation

3.7 Preparing the System Rename Installation Media

16/32 PUBLIC 2011-11-28

http://service.sap.com/swdc

4 Renaming

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

■ Central system

■ Distributed system

SAP System Rename adapts the system on an operating system level. The system parameters are adapted

offline.

SAP System Rename automatically starts the following instances during the system rename:

■ Database

■ Instance agents of a UNIX operating system

■ Instance services of a Windows operating system

NOTE

SAP System Rename does not start the target system!

4.1 Running SAPinst

This section describes how to run the installation tool SAPinst. SAPinst includes a GUI client and a GUI

server, which both use Java.

The procedure describes a renaming process where SAPinst, GUI client, and GUI server are running

on the same host. In the following, GUI client and GUI server are addressed as “SAPinst GUI”.

Useful Information About SAPinst

■ When you start SAPinst, it automatically starts the SAPinst GUI.

■ Only valid for: Windows |

SAPinst creates the installation directory sapinst_instdir, which is located directly in the %

ProgramFiles% directory. If SAPinst is not able to create sapinst_instdir there, it tries to create

sapinst_instdir in the directory defined by the environment variable TEMP.End of: Windows |

Only valid for: UNIX |

Shell Used Command

Bourne shell (sh) TEMP=<directory>

export TEMP

C shell (csh) setenv TEMP <directory>

Korn shell (ksh) export TEMP=<directory>

End of: UNIX |

4 Renaming

4.1 Running SAPinst

2011-11-28 PUBLIC 17/32

RECOMMENDATION

We recommend that you keep all installation directories until the system is completely and

correctly installed.


SAPinst creates a subdirectory for each installation option called sapinst_instdir

\<installation_option_directory>, which is located in %ProgramFiles%.End of: Windows |


SAPinst extracts itself to a temporary directory called sapinst_exe.xxxxxx.xxxx, which is located

in %TEMP%, %TMP%, %TMPDIR%, or %SystemRoot%. These files are deleted after SAPinst has stopped

running.End of: Windows |

The temporary directory sapinst_exe.xxxxxx.xxxx sometimes remains undeleted. You can safely

delete it.

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 SAPinst cannot find a temporary directory, the installation terminates with the error

FCO-00058.

■ During the installation, the default ports 21200, 21212, and 4239 are used for communication

between SAPinst, GUI server, GUI, and HTTP server, as follows:

● SAPinst uses port 21200 to communicate with the GUI server.

● The GUI server uses port 21212 to communicate with the GUI client.

● 4239 is the port of the HTTP server, which is part of the GUI server.

If the ports for SAPinst and the GUI server are already in use, SAPinst automatically searches for

free port numbers. If the search fails, SAPinst exits.

Only valid for: Windows |

In this case or if you want SAPinst to use specific ports, open a command prompt and change to

the required directory as follows:End of: Windows |


cd /d <media drive>:\DATA_UNITS\SYSTEM_RENAME\SBC700_IM_<platform>

End of: Windows |


Execute sapinst.exe with the following command line parameters:End of: Windows |

● SAPINST_DIALOG_PORT=<port_number_sapinst_to_gui_server>

● GUISERVER_DIALOG_PORT=<port_number_gui_server_to_gui_client>

● GUISERVER_HTTP_PORT=<port_number_http_server>

4 Renaming

4.1 Running SAPinst

18/32 PUBLIC 2011-11-28


To see a list of all the available SAPinst properties, open a command prompt and start SAPinst with

command line parameter -p:End of: Windows |


sapinst.exe -p

End of: Windows |


To see a list of all available SAPinst properties, start SAPinst as described above with command line

parameter -p:End of: UNIX |


./sapinst -p.End of: UNIX |


If you need to run SAPinst in accessibility mode, make sure that you have activated and adjusted

accessibility settings as described in Running SAPinst in Accessibility Mode in the installation

documentation of your release.End of: Windows |

■ If required, you can stop SAPinst by choosing SAPinst Cancel in the SAPinst GUI menu.

NOTE


If you need to terminate SAPinst, you can do this by pressing Ctrl + C .End of: UNIX |


If you need to terminate SAPinst you can do this by choosing File Exit in the menu of

the Program Starter window.End of: Windows |

Prerequisites

■ Only valid for: UNIX |

We recommend that you use the csh shell. If you want to use another shell, make sure that you

have read SAP Note 202227.

SAPinst uses csh scripts 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>/<sapsid>adm/.cshrc;env"

End of: UNIX |


Make sure that you use an account with the required user authorization to run SAPinst.

4 Renaming

4.1 Running SAPinst

2011-11-28 PUBLIC 19/32


For more information, see Required User Authorization for Running SAPinst in the installation

documentation of your release.End of: Windows |


Make sure that umask is set to 022 for user root.

As user root, enter the following command: umask 022End of: UNIX |


Check the following values for user root:

● In csh, execute limit

Output Properties

cputime unlimited

filesize unlimited

datasize unlimited

stacksize 8192 KB

coredumpsize unlimited

descriptors 8192

memorysize unlimited

● In sh or ksh, execute ulimit -a

Output Properties

time(seconds) unlimited

file(blocks) unlimited

data(kbytes) unlimited

stack(kbytes) 8192

coredump(blocks) unlimited

nofiles(descriptors) 8192

memory(KBytes) unlimited

If your parameter settings differ from the settings above, change these values accordingly.

EXAMPLE

If you have to change the value for descriptors to 8192, proceed as follows:

◆ In csh, execute:

limit descriptors 8192

◆ In sh or ksh execute:

ulimit -n 8192

End of: UNIX |

Procedure

1. Only valid for: UNIX |

Log on to the installation host as user root.End of: UNIX |

4 Renaming

4.1 Running SAPinst

20/32 PUBLIC 2011-11-28


Log on to the installation host using an account with the required user authorization to run

SAPinst.End of: Windows |


CAUTION

Make sure that the root user has not set any environment variables for a different SAP system

or database.

End of: UNIX |

2. Only valid for: UNIX | IBM DB2 for Linux and UNIX and Windows;MaxDB;Oracle |

Change to the directory with the sapinst executable for your operating system by entering the

following command: cd <mountpoint>/DATA_UNITS/SYSTEM_RENAME/SBC700_IM_<platform>.End of: UNIX | IBM DB2 for Linux and UNIX and Windows;MaxDB;Oracle |


Start SAPinst by executing the following command: ./sapinstEnd of: UNIX |


Start SAPinst by double-clicking sapinst.exe from the following path:End of: Windows |


<media drive>:\DATA_UNITS\SYSTEM_RENAME\SBC700_IM_<platform>

End of: Windows |


NOTE

If you need to perform the installation in accessibility mode, open a command prompt, change

to the <media drive>:\DATA_UNITS\SYSTEM_RENAME\SBC700_IM_<platform> directory, and

execute sapinst.exe –accessible.

For more information, see Running SAPinst in Accessibility Mode in the installation documentation

of your release.

End of: Windows |


The GUI starts automatically by displaying the Welcome screen.End of: Windows |

4. In the Welcome screen, proceed according to your system variant :

■ If your system is a central system , choose System Rename Central System SAP System

Rename .

■ If your system is a distributed system, choose System Rename Distributed System <System

Rename Option> . Perform the system rename options as required and in the order they appear.

5. Only valid for: Windows |

If SAPinst prompts you to log off from your system, log off and on again.

4 Renaming

4.1 Running SAPinst

2011-11-28 PUBLIC 21/32

SAPinst restarts automatically.End of: Windows |

6. Follow the instructions in the SAPinst input screens and enter the required parameters.

NOTE

■ SAP MaxDB on Windows only: In the Storage Based Copy Configuration File for SAP MaxDB

screen, enter the path to the database-specific configuration file sapdbConfig.txt, which

you stored locally on the host.

■ Oracle on Windows only: In the ABAP Schema Name screen, make sure that the name

of the ABAP schema is correct.

NOTE

For more information about the input parameters, position the cursor on the parameter and

press F1 .

After you have entered all requested input parameters, SAPinst displays the Parameter Summary screen.

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

required, you can revise the parameters before starting the split procedure.


We recommend that you delete the directory <user_home>/.sdtgui/.End of: UNIX |


We recommend that you delete the directory %userprofile%\.sdtgui\.End of: Windows |

4 Renaming

4.1 Running SAPinst

22/32 PUBLIC 2011-11-28

5 Follow-up Activities

5.1 General Follow-Up Activities

This section refers to the follow-up activities that you have to perform after the renaming of your SAP

system.

The follow-up activities for SAP System Rename are identical with the follow-up activities for SAP

System Copy for the following SAP NetWeaver releases:

■ SAP NetWeaver 7.0: For more information on the follow-up activities for SAP System Rename,

see SAP Service Marketplace at http://service.sap.com/instguides of your release/stack.

■ SAP NetWeaver 7.0 (including Enhancement Package 1): For more information on the follow-

up activities for SAP System Rename, see SAP Service Marketplace at http://service.sap.com/

instguides of your release/stack.







5.2 Performing Follow-Up Activities for SAP MaxDB

The SAP System Rename tool does not adapt entries in the Windows program menu to the renamed

software. If you want to use the software after the system rename, proceed as described below.

Procedure

1. On the target system, choose Start All Programs SAP MaxDB .

2. Rename the folders SID and CL_SID according to the new system ID.

3. Select all subfolders of the folder SID, choose Properties in the context menu, and adapt the system

ID.

Proceed accordingly with folder CL_SID.

5 Follow-up Activities

5.1 General Follow-Up Activities

2011-11-28 PUBLIC 23/32






A Reference

A.1 The Main SAP Documentation Types

The following is an overview of the most important documentation types that you need in the various

phases in the life cycle of SAP software.

Cross-Phase Documentation

SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 languages, as

well as many glossary entries in English and German.

■ Target group:

● Relevant for all target groups

■ Current version:

● On SAP Help Portal at http://help.sap.com Glossary

● In the SAP system in transaction STERM

SAP Library is a collection of documentation for SAP software covering functions and processes.

■ Target group:

● Consultants

● System administrators

● Project teams for implementations or upgrades


● On SAP Help Portal at http://help.sap.com (also available as documentation DVD)

The security guide describes the settings for a medium security level and offers suggestions for raising

security levels. A collective security guide is available for SAP NetWeaver. This document contains

general guidelines and suggestions. SAP applications have a security guide of their own.

■ Target group:


● Technology consultants

● Solution consultants


● On SAP Service Marketplace at http://service.sap.com/securityguide

Implementation

The master guide is the starting point for implementing an SAP solution. It lists the required installable

units for each business or IT scenario. It provides scenario-specific descriptions of preparation,

A Reference


2011-11-28 PUBLIC 25/32

http://help.sap.com

http://help.sap.com

http://service.sap.com/securityguide

execution, and follow-up of an implementation. It also provides references to other documents, such

as installation guides, the technical infrastructure guide and SAP Notes.

■ Target group:


● Project teams for implementations


● On SAP Service Marketplace at http://service.sap.com/instguides

The installation guide describes the technical implementation of an installable unit, taking into

account the combinations of operating systems and databases. It does not describe any business-related

configuration.

■ Target group:





Configuration Documentation in SAP Solution Manager – SAP Solution Manager is a life-cycle

platform. One of its main functions is the configuration of business scenarios, business processes, and

implementable steps. It contains Customizing activities, transactions, and so on, as well as

documentation.

■ Target group:





● In SAP Solution Manager

The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system. The

Customizing activities and their documentation are structured from a functional perspective. (In order

to configure a whole system landscape from a process-oriented perspective, SAP Solution Manager,

which refers to the relevant Customizing activities in the individual SAP systems, is used.)

■ Target group:


● Project teams for implementations or upgrades


● In the SAP menu of the SAP system under Tools Customizing IMG

Production Operation

The technical operations manual is the starting point for operating a system that runs on SAP

NetWeaver, and precedes the application operations guides of SAP Business Suite. The manual refers

A Reference


26/32 PUBLIC 2011-11-28



users to the tools and documentation that are needed to carry out various tasks, such as monitoring,

backup/ restore, master data maintenance, transports, and tests.

■ Target group:




The application operations guide is used for operating an SAP application once all tasks in the

technical operations manual have been completed. It refers users to the tools and documentation that

are needed to carry out the various operations-related tasks.

■ Target group:






Upgrade

The upgrade master guide is the starting point for upgrading the business scenarios and processes of

an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of

an upgrade. It also refers to other documents, such as upgrade guides and SAP Notes.

■ Target group:


● Project teams for upgrades



The upgrade guide describes the technical upgrade of an installable unit, taking into account the

combinations of operating systems and databases. It does not describe any business-related

configuration.

■ Target group:





Release notes are documents that contain short descriptions of new features in a particular release or

changes to existing features since the previous release. Release notes about ABAP developments are the

technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide

(IMG).

■ Target group:

A Reference


2011-11-28 PUBLIC 27/32





● Consultants



● On SAP Service Marketplace at http://service.sap.com/releasenotes

● In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)

A Reference


28/32 PUBLIC 2011-11-28

http://service.sap.com/releasenotes

Typographic Conventions

Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

ExampleExample

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

http://www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ■ Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

■ Cross-references to other documentation or published works

Example ■ Output on the screen following a user action, for example, messages ■ Source code or syntax quoted directly from a program ■ File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

2011-11-28 PUBLIC 29/32

http://www.sap.com



SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle and Java are registered trademarks of Oracle.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP companySybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

30/32 PUBLIC 2011-11-28


SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2011 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Date post:	24-Oct-2014
Category:	Documents
Upload:	liliana-delgado-manzano
View:	1,256 times
Download:	9 times

Sap System Rename

Documents