Documents
Product Categories
SAP Homogeneous System Copy
Product Categories
SAP Homogeneous System Copy
SAP Homogeneous System Copy
Jun 28, 2024adm/.cshrc;env" or /bin/csh -c "source /home/
adm/.login;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 755.
● 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 69].
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database Independent System Copy PUBLIC 61 Note
Some tools such as jsplitter may create files while the installer is running. The required free space
in the /tmp directory depends on the amount of databases which you intend to unload.
● 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,
adm, and your database-specific operating system users (see also sections 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
, 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).
Output Properties
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 8192 KB
coredumpsize unlimited
descriptors 8192
memoryuse 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 Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
62 PUBLIC Database Independent System CopyOutput sh Output ksh Properties
cpu time (seconds) cpu time (seconds) unlimited
file size (blocks) file size (blocks) unlimited
data seg size (kbytes) data size (Kibytes) unlimited
stack size (kbytes) stack size (Kibytes) 8192 KB
core file size (blocks) core file size (blocks) unlimited
open files nofile 8192
max memory size (kbytes) max memory size (Kibytes) unlimited
End of ''Platform'': HP-UX, Linux, Oracle Solaris
● Make sure that the following ports are not used by other processes:
○ 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=
○ 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=
● If you want to perform the export in unattended mode, see System Provisioning Using a Parameter Input
File [page 71] which describes an improved procedure using inifile.params.
● Specify an empty directory with sufficient disk space for the export dump on the host where you want to
perform the export. Make sure that this directory does not contain any files from any previous system copy
exports. If you cancelled a system copy export and want to perform the export again, make sure that you
remove all files from the previously cancelled export before you start the export from scratch.
● Caution: Make sure that you shut down all SAP application servers before the export. The database must
still be running. Otherwise, the target system might be inconsistent.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database Independent System Copy PUBLIC 634.1.5.2 Running the Installer
This section describes how to run the installer to perform the export for system copy.
Prerequisites
For more information, see Prerequisites for Running the Installer [page 61].
Context
The installer has a web browser-based GUI named “SL Common GUI of the Software Provisioning Manager” -
“SL Common GUI” for short.
This procedure describes an installation where you run the installer and use the SL Common GUI, that is you
can control the processing of the installer from a browser running on any device.
For more information about the SL Common GUI, see Useful Information About the Installer [page 69].
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 adm user or built-in administrator.
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 export , 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 must 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 Preparing the Media Required for Performing the Export [page 43].
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 Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
64 PUBLIC Database Independent System CopyOnly 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:
//sapinst
Note
If you want to run a system copy with parallel export/import using the Migration Monitor with the
R3load socket option, and the target database is declustered, start the installer for the database
instance export with command line option SUPPORT_DECLUSTERING=false
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:
//sapinst SAPINST_USE_HOSTNAME=''
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.
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.
...
************************************************************************
O pen your browser and paste the following URL address to access the GUIh ttps://[]:4237/sapinst/docs/index.htmlL ogon users: []************************************************************************
. ..
Note
If the host specified by cannot be reached due to a special network configura tion,
proceed as follows:
1. Terminate the installer as described in Useful Information about the Installer [page 69].
2. Restart the installer from the command line with the SAPINST_GUI_HOSTNAME=
property.
You can use a fully-qualified host name.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database Independent System Copy PUBLIC 65If you have a supported web browser (see Prerequisites for Running the Installer [page 61]) 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.
Caution
After opening the browser URL, make sure that the URL in the browser starts with “https://” to avoid
security risks such as SSL stripping .
Before you reach the Welcome screen, your browser warns you that the certificate of the sapinst
process on this computer could not be verified.
Proceed as follows to avoid security risks such as a man-in-the-middle attack:
1. Click on the certificate area on the left hand side in the address bar of your browser, and view the
certificate.
2. Open the certificate fingerprint or thumbprint, and compare all hexadecimal numbers to the ones
displayed in the console output of the installer.
Proceed as follows to get the certificate fingerprint or thumbprint from the server certificate
printed in the installer console:
1. Go to the sapinst_exe.xxxxxx.xxxx directory in the temporary directory to which the
installer has extracted itself:
/.sapinst/
2. In the sapinst_exe.xxxxxx.xxxx directory, execute the sapgenpse tool with the
command line option get_my_name -p.
As a result, you get the server fingerprint or thumbprint from the server certificate.
3. Accept the warning to inform your browser that it can trust this site, even if the certificate could not
be verified.
The SL Common GUI opens in the browser by displaying the Welcome screen.
5. On the Welcome screen, choose System Copy Source System Based
on AS ABAP .
Note
Select the corresponding system copy option from the tree structure according to the sequence of the
process flow for the database-independent system copy procedure [page 47].
Note
Do not perform these steps if you perform a system copy using a database-specific method because
then you do not perfom an export using Software Provisioning Manager 1.0 (the “installer”) but only
use Software Provisioning Manager 1.0 for installing the target system. For more information, see
Database-Specific System Copy [page 88]).
6. Choose Next.
Note
If there are errors during the self-extraction process of the installer, you can find the log fi le
dev_selfex.out in the temporary directory.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
66 PUBLIC Database Independent System Copy7. 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 , and choose either F1 or the HELP tab. Then the available help
text is displayed in the HELP tab.
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 Database only: If your source system has Oracle Database Vault, consider the additional
information in SAP Note 2218115 .
Caution
The signature of installation media and installation archives is checked automatically during the De fine
Parameters phase while processing the Media Browser and - if you perform an archive-based
installation - the Software Package Browser screens.
Note that this automatic check is only committed once and not repeated if you modify artifacts such
as SAR archives or files on the media after the initial check has been done. This means that - 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.
For more information, see 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 export procedure.
9. To start the execution, choose Next.
The installer starts the export and displays its progress of the system copy export during the processing
phase.
10. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after the installer has fi nished.
Sometimes these remain 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.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database Independent System Copy PUBLIC 6711. If you copied installation media to your hard disk, you can delete these files when the installer has
successfully completed.
12. For security reasons, we recommend that you delete the .sapinst directory within the home directory of
the user with which you ran the installer:
/.sapinst/
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.
14. The installer log files contain IP addresses and User IDs such as the ID of your S-User. For security, data
protection, and privacy-related reasons we strongly recommend that you delete these log files once you do
not need them any longer.
You find the installer log files in the sapinst_instdir directory. For more information, see Useful
Information about the Installer [page 69].
Related Information
Useful Information about the Installer [page 69]
Interrupted Processing of the Installer [page 75]
Troubleshooting with the Installer [page 78]
4.1.5.2.1 Additional Information about the Installer
The following sections provide additional information about the installer.
Useful Information about the Installer [page 69]
This section contains some useful technical background information about the installer and the
installer GUI.
System Provisioning Using a Parameter Input File [page 71]
Provisioning with Software Provisioning Manager (“the installer”), for example installation, of SAP
systems in unattended mode with a parameter input file.
Interrupted Processing of the Installer [page 75]
Here you find information about how to restart the installer if its processing has been interrupted.
Troubleshooting with the Installer [page 78]
This section tells you how to proceed when errors occur while the installer is running.
Troubleshooting during the Export Process [page 79]
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
68 PUBLIC Database Independent System CopyIf the export process aborts during the Execute Service phase (for example, due to a hardware failure,
such as power outage, operating system crash, file system full), you have to repeat the export of the
complete package.
Using the Step State Editor (SAP Support Experts Only) [page 80]
This section describes how to use the Step State Editor available in the installer.
4.1.5.2.1.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” for short) has the web browser-based “SL Common GUI of
the Software Provisioning Manager” - “SL Common GUI” for short.
The SL Common GUI 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.
As of version 1.0 SP24 Patch Level (PL) 5, Software Provisioning Manager comes with a new look and feel of
the SL Common GUI. For more information, see https://blogs.sap.com/2018/11/10/new-look-for-
software-provisioning-manager/ .
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
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 61].
If you need to run the SL Common GUI in accessibility mode, apply the standard accessibility functions of
your web browser.
● As soon as you have started the sapinst executable, the installer creates a .sapinst directory
underneath the /home/ directory where it keeps its log files. is the user with which you
have started the installer.
After you have reached the Welcome screen and selected the relevant installer option for the SAP system
to be exported , the installer creates a directory sapinst_instdir where it keeps its log files, and which
is located 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 by default.
All log files which have been stored so far in the .sapinst folder are moved to the sapinst_instdir
directory as soon as the latter has been created.
If you want the sapinst_instdir directory to be created in another directory than /tmp, set the
environment variable TEMP, TMP, or TMPDIR to this directory before you start the installer.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database Independent System Copy PUBLIC 69Shell Used Command
Bourne shell (sh) TEMP=
export TEMP
C shell (csh) setenv TEMP
Korn shell (ksh) export TEMP=
Caution
Make sure that the installation directory is not mounted with NFS, or there might be problems when
the Java Virtual Machine is started.
The installer records its progress in the keydb.xml file located in the sapinst_instdir directory.
Therefore, if required, you can continue with the installer from any point of failure, without having to repeat
the already completed steps and without having to reenter the already processed input parameters. For
security reasons, a variable encryption key is generated as soon as the sapinst_instdir directory is
created by the installer. This key is used to encrypt the values written to the keydb.xml file.
Recommendation
We recommend that you keep all installation directories until the system is completely and correctly
installed.
● 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 after the
installer has finished. You can safely delete them.
The temporary directory also contains the log file dev_selfex.out from the self-extraction process of
the installer, 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
● If you want to perform the export in unattended mode, see System Provisioning Using a Parameter Input
File [page 71] which describes an improved procedure using inifile.params.
● Before starting the export, make sure that you have at least the same amount of disk space available in /
sapmnt////program as is used in /sapmnt//
//root/origin.
During the export, some archives are written to the program subdirectories and the tool aborts if there is
not enough space.
● If required, stop the installer by choosing the Cancel button.
Note
If you need to terminate the installer, press Ctrl + C .
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
70 PUBLIC Database Independent System Copy4.1.5.2.1.2 System Provisioning Using a Parameter Input File
Provisioning with Software Provisioning Manager (“the installer”), for example installation, of SAP systems in
unattended mode with a parameter input file.
Prerequisites
Provisioning of SAP systems can also be done in unattended mode without the user interface of the installer.
This means that, after inserting the required parameters into a parameter-file and running the sapinst
executable by providing the path to this parameter-file , the installation will run in the background and no
further user interaction is required.
Context
This section describes the steps that you need to execute in addition to the procedure described in this guide,
when running the installer in unattended mode using a parameter input file.
Since the new Web-based SL Common GUI (see Useful Information about the Installer [page 69]) was
introduced in 2017 there are two ways to run the unattended mode: “observer mode” and “non-observer
mode”.
Observer Mode
If you are running an installation in unattended mode but you are sitting in front of the screen, you might want
to check the progress from time to time. In this case the “observer mode” makes sense.
Start the installation as described below in the Solution section, using the following parameters:
S APINST_INPUT_PARAMETERS_URL=S APINST_EXECUTE_PRODUCT_ID=SAPINST_SKIP_DIALOGS=true
The Software Provisioning Manager will start the installation in the background AND start a Web Dispatcher
and provide an URL to access the SL Common GUI. The user who has started the installation can now connect
to the URL and observe the progress of the installation, for example to look at the logfiles in the Web browser.
However, all parameters will be taken from the parameter input file and can not be changed in the Web browser.
Non-Observer Mode
Choose that mode if you want to run a “scripted” or by other means automated scenario, for example
overnight. In that case it is crucial that the process is started without a Web Dispatcher and therefore without a
GUI. Otherwise, the automation could be stuck if the installer encounters a situation that requires user
interaction.
Start the installation as described below in the Solution section, using the following parameters (use the same
parameters like for Observer Mode, but provide SAPINST_START_GUISERVER=false in addition):
S APINST_INPUT_PARAMETERS_URL=SAPINST_EXECUTE_PRODUCT_ID=
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database Independent System Copy PUBLIC 71S APINST_SKIP_DIALOGS=trueSAPINST_START_GUISERVER=false
This will start the installation but this time NO Web Dispatcher will be started and no URL to access the SL
Common GUI will be provided either. So the user can not follow the processing of the installation in a Web
browser and the installation will run completely in the background.
If the process runs into an error, SAPinst will abort and you have to check for the reason in the log files.
Restrictions
In exceptional cases, parameters prompted or displayed in the Software Provisioning Manager UI are not
maintainable in the parameter input file. If one of those parameters, that are only available in the GUI mode of
the Software Provisioning Manager, is needed for your unattended installations, you should create a ticket in
the best fitting component below BC-INS to get the issue analyzed.
Must Know about the Input Parameter File
● The parameter input file only contains values that you entered in the Software Provisioning Manager GUI.
● With the SAPinst 749.0.69 or by other means patch we provide a better encryption of passwords in
Software Provisioning Manager files:
If the parameter input file has parameters which are encrypted with Des25 encryption, the instkey.pkey
file available in the installation directory contains the key for the encryption. The instkey.pkey file must
be always located in the same directory as the parameter input file and is used to decrypt the values of the
encrypted parameters. If you need to copy a parameter input file to another directory, you must also copy
the instkey.pkey file to this directory.
● Not explicitly set parameters are documented as comments in the generated parameter input file.
● Each parameter has got a documentation assigned as a comment on top.
Example
Example for a parameter that is not used and therefore commented out:
# Specify whether Software Provisioning Manager is to drop the schema if
i t exists. <= Documentation# HDB_Schema_Check_Dialogs.dropSchema = false
Example
Example for a parameter that is used:
# The name of the database schema. <= DocumentationHDB_Schema_Check_Dialogs.schemaName = SAPABAP2
● The media information is provided using the following convention:
SAPINST.CD.PACKAGE.=
For each media location a line.
● Restriction: Currently you can only specify complete media, not paths to single files like *.SAR archives.
Make sure that you enter the full paths to all required media, relative paths are not sufficient:
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
72 PUBLIC Database Independent System Copy Example
Example on UNIX:
S APINST.CD.PACKAGE.KERNEL = /mnt/KERNELS APINST.CD.PACKAGE.LOAD = /mnt/LOADSAPINST.CD.PACKAGE.RDBMS = /mnt/RDBMS
Example
Example on Windows:
S APINST.CD.PACKAGE.KERNEL = C:\sapdvds\KERNELS APINST.CD.PACKAGE.LOAD = C:\sapdvds\LOADSAPINST.CD.PACKAGE.RDBMS =C:\sapdvds\RDBMS
When performing a system copy, you need to add one additional media path:
SAPINST.CD.PACKAGE.MIGRATION1 =
● Caution:
If you want to use archives for your installation, you must copy all files that are to be used to a single
directory. In the parameter input file you must specify this directory as a download basket, using the
archives.downloadBasket parameter.
Make sure that there is only one version of the same archive in the directory, for example
SAPEXE_.SAR
Procedure
1. You plan and prepare the run as described in Planning [page 23] and Preparation [page 39].
2. Create a text file that has “.params” as a suffix as follows:
1. Start the installer as described in Running the Installer [page 64].
2. Choose the option you want to run, and follow the instructions on the screens by entering all
parameter values
3. Stop after the Parameter Summary screen has been displayed
4. Find the parameter input file named “inifile.params” in the installation directory
5. Rename the “inifile.params” file. For example, you can rename it to “my_inifile.params”.
3. Adjust the values of the parameter input file as follows:
1. Edit the parameter input file (“my_inifile.params”) file and modify the parameters according to
your needs.
2. Add required media or archives information line by line.
4. Identify the Product-ID:
○ To start in unattended mode, you need to know the component ID for the option that are required for
your provisioning scenario.
Proceed as follows:
1. Open the sapinst_dev.log in the installation directory.
2. Check for the “product-id”
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database Independent System Copy PUBLIC 73 Example
product-id=NW_ABAP_ASCS:NW750.ADA.ABAP
○ Alternatively, you can check the header of the generated “my_inifile.params” file.
Example
product id ''NW_ABAP_ASCS:NW750.ADA.ABAP''
5. Run the installer [page 64] with the parameters required for unattended mode:
○ In observer mode: Start the sapinst executable from an empty directory with the following
parameters:
S APINST_INPUT_PARAMETERS_URL=S APINST_EXECUTE_PRODUCT_ID=SAPINST_SKIP_DIALOGS=true
○ In non-observer mode: Start the sapinst executable from an empty directory with the following
parameters:
SAPINST_INPUT_PARAMETERS_URL=SAPINST_EXECUTE_PRODUCT_ID=
SAPINST_SKIP_DIALOGS=true
S APINST_START_GUISERVER=false
6. After the installer has completed, perform follow-up activities as described in Follow-Up Activities [page
149].
Related Information
SAP Note 2849054
SAP Note 2742212
SAP Note 2626837
SAP Note 2669183
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
74 PUBLIC Database Independent System Copy4.1.5.2.1.3 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 or 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 processing of the installer by choosing Cancel in the SL Common 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.
The following table describes the options in the dialog box:
Option Definition
Retry The installer retries the installation from the point of failure without repeating any of
the previous steps.
This is possible because the installer records its 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.
Stop The installer stops the installation, closing the dialog box, the installer GUI, and the
GUI server.
The installer records its progress in the keydb.xml file. Therefore, you can continue
with the installer from the point of failure without repeating any of the previous steps.
See the procedure below.
Continue The installer continues the installation from the current point.
View Log 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.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database Independent System Copy PUBLIC 75Procedure
1. Log on to the installation host as a user with the required permissions as described in Running the Installer
[page 64] .
2. Make sure that the media media required for the export are still available.
For more information, see Preparing the Media Required for Performing the Export [page 43] .
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
3. Restart the installer from the directory to which you unpacked the Software Provisioning Manager archive
by executing the following command:
/sapinst
4. The installer is restarting.
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.
...
************************************************************************
O pen your browser and paste the following URL address to access the GUIh ttps://[]:4237/sapinst/docs/index.htmlL ogon users: []************************************************************************
. ..
Note
If the host specified by cannot be reached due to a special network configura tion,
proceed as follows:
1. Terminate the installer as described in Useful Information about the Installer [page 69].
2. Restart the installer from the command line with the SAPINST_GUI_HOSTNAME=
property.
You can use a fully-qualified host name.
If you have a supported web browser (see Prerequisites for Running the Installer [page 61]) 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.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
76 PUBLIC Database Independent System Copy Caution
After opening the browser URL, make sure that the URL in the browser starts with “https://” to avoid
security risks such as SSL stripping .
Before you reach the Welcome screen, your browser warns you that the certificate of the sapinst
process on this computer could not be verified.
Proceed as follows to avoid security risks such as a man-in-the-middle attack:
1. Click on the certificate area on the left hand side in the address bar of your browser, and view the
certificate.
2. Open the certificate fingerprint or thumbprint, and compare all hexadecimal numbers to the ones
displayed in the console output of the installer.
Proceed as follows to get the certificate fingerprint or thumbprint from the server certificate
printed in the installer console:
1. Go to the sapinst_exe.xxxxxx.xxxx directory in the temporary directory to which the
installer has extracted itself:
/.sapinst/
2. In the sapinst_exe.xxxxxx.xxxx directory, execute the sapgenpse tool with the
command line option get_my_name -p.
As a result, you get the server fingerprint or thumbprint from the server certificate.
3. Accept the warning to inform your browser that it can trust this site, even if the certificate could not
be verified.
The SL Common GUI opens in the browser 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:
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database Independent System Copy PUBLIC 77Alternative Behavior
Perform a new run The installer does not continue the interrupted export for system copy option.
Instead, it moves the content of the old installer directory and all installer-spe
cific 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______
Example
log_01_Oct_2016_13_47_56
Note
All actions taken by the export for system copy before you stopped it (such
as creating 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.
Continue with the existing one The installer continues the interrupted export for system copy from the point of
failure.
4.1.5.2.1.4 Troubleshooting with the Installer
This section tells you how to proceed when errors occur while the installer is running.
Context
If an error occurs, the installer:
● Stops processing
● Displays a dialog informing you about the error
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
78 PUBLIC Database Independent System CopyProcedure
1. Check SAP Note 2393060 for known installer issues.
2. If an error occurs during the Define Parameters or the Execute Service phase, do one of the following:
○ Try to solve the problem:
○ To check the installer log files (sapinst.log and sapinst_dev.log) for errors, choose the LOG
FILES tab.
Note
The LOG FILES tab is only available if you have selected on the Welcome screen the relevant
installer option for the SAP system to be exported .
If you need to access the log files before you have done this selection, you can find them in
the .sapinst directory underneath the /home/ directory, where is the user
that you used to start the installer.
For more information, see Useful Information about the Installer [page 69].
○ To check the log and trace files of the installer GUI for errors, go to the directory
/.sapinst/
○ Then continue by choosing Retry.
○ If required, abort the installer by choosing Cancel in the tool menu and restart the installer. For more
information, see Interrupted Processing of the Installer [page 75].
3. If you cannot resolve the problem, report an incident using the appropriate subcomponent of BC-INS*.
For more information about using subcomponents of BC-INS*, see SAP Note 1669327 .
4.1.5.2.1.5 Troubleshooting during the Export Process
If the export process aborts during the Execute Service phase (for example, due to a hardware failure, such as
power outage, operating system crash, file system full), you have to repeat the export of the complete package.
Procedure
● System Copy – export (common issues)
a. Remove the . dump files, the .TOC file, and the .log file.
b. Make sure that all tables in the .*TSK* file have the status flag xeq or err set.
c. Repeat the export of the complete package.
● System Copy – export on UNIX (especially for upgraded systems)
Symptom:
Processes started under the OS users adm or ora cannot create or open files in the
installer directory.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database Independent System Copy PUBLIC 79Reason:
Only members of the sapinst UNIX group can access the installer directory.
Solution:
a. Manually associate adm and ora OS users with sapinst group if this association
is missing.
b. Verify the /etc/group file and check if the sapinst group exists and OS users are members of this
group.
c. If the sapinst group does not exist yet, start the installer. The installer creates this group during
startup before the product catalog list is displayed.
d. Edit /etc/group file and associate OS users with sapinst group.
e. Continue with the export.
4.1.5.2.1.6 Using the Step State Editor (SAP Support Experts
Only)
This section describes how to use the Step State Editor available in the installer.
Note
Only use the Step State Editor if the SAP Support requests you to do so, for example to resolve a
customer incident.
Prerequisites
● SAP Support requests you to use the Step State Editor.
● Make sure that the host where you run the installer meets the requirements listed in Prerequisites for
Running the Installer [page 61].
Procedure
1. Start the installer from the command line as described in Running the Installer [page 64] with the
additional command line parameter SAPINST_SET_STEPSTATE=true
2. Follow the instructions on the installer screens and fill in the parameters prompted during the De fine
Parameters phase until you reach the Parameter Summary screen.
3. Choose Next.
The Step State Editor opens as an additional dialog. Within this dialog you see a list of all steps to be
executed by the installer during the Execute Service phase. By default all steps are in an initial state.
Underneath each step, you see the assigned installer component. For each step you have a Skip and a
Break option.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
80 PUBLIC Database Independent System Copy○ Mark the checkbox in front of the Break option of the steps where you want the installer to pause.
○ Mark the checkbox in front of the Skip option of the steps which you want the installer to skip.
4. After you have marked all required steps with either the Break or the Skip option, choose OK on the Step
State Editor dialog.
The installer starts processing the Execute Service phase and pauses one after another when reaching
each step whose Break option you have marked. You can now choose one of the following:
○ Choose OK to continue with this step.
○ Choose Step State Editor to return to the Step State Editor and make changes, for example you
can repeat the step by marking the checkbox in front of the Repeat option.
○ Choose Cancel to abort the installer.
5. Continue until you have run through all the steps of the Execute Service phase of the installer.
4.1.5.3 Restarting R3load Processes
You can restart failed or canceled R3load processes while the Migration Monitor is still running.
Context
The state files export_state.properties and import_state.properties (see Output Files [page 189])
allow package states to be manually updated to restart failed R3load processes.
Example
If package processing failed and the package state has the value “–”, the state can be set to “0” and
processing of the package is restarted.
If you want to restart failed or canceled R3load processes that are using the socket option, R3load processes
that process the same package must not be running.
Procedure
● Restarting R3load Processes Without Using the Socket Option
a. To restart package processing, set the package state from “–” to “0”.
b. To skip package processing, set the package state from “0” or “–” to “+”. (This is not recommended,
because it can cause inconsistent data files or database content.)
c. If the package is currently being processed (the package state is “?”), then any manual modifica tions
to the package state are ignored.
● Restarting R3load Processes Using the Socket Option
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database Independent System Copy PUBLIC 81a. Make sure that no related R3load processes (export or import) are running. For example, if you want to
restart an R3load export process and the corresponding import process that processes the same
package is still running, cancel it or wait until it has finished.
b. There are four possible situations where an R3load restart may be required. Proceed as required:
○ If both the import and the export are completed successfully, there is nothing to do.
○ If the export was completed successfully, but the import is canceled with errors, proceed as
follows:
○ If the export was successful but the import was canceled when creating the index or the
primary key, set the status for export_state.properties from “+” to “0”.
○ If the export was completed successfully but the import was canceled when loading the table
content, set the status for export_state.properties from “+” to “0” and for the export
TSK file from “ok” to “err”.
○ If both the export and the import are canceled with errors, proceed as follows:
○ If the errors in export and import relate to the same table, there is nothing to do.
○ If the errors relate to different tables, set the status of the first object with errors in both the
export and the import TSK file to “err” and in the export_state.properties and
import_state.properties files to “–”.
Example
Export TSK File Import TSK File
Table Name Status Table Name Status
TAB_1 ok TAB_1 ok
TAB_2 err TAB_2 ok
TAB_3 xeq TAB_3 err
TAB_4 xeq TAB_4 xeq
The first object with errors here is TAB_2 (export). This means that in the import TSK fi le
the status for TAB_2 must be set from “ok” to “err”. The entry in the
export_state.properties and import_state.properties files also must be set
from “+” to “0”.
○ If the import is completed successfully but the export was canceled with errors, you can set the
status in the export_state.properties from “–” to “+”.
c. Restart the installer or the Migration Monitor to proceed with the system copy.
4.1.6 Setting Up the Target System
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
82 PUBLIC Database Independent System CopyRelated Information
Transferring the Export Files to the Target Host [page 83]
Installing the Target System [page 84]
4.1.6.1 Transferring the Export Files to the Target Host
This section describes how to transfer the complete export directory with its structure and the generated
DBSIZE.XML file to the target host.
Context
As an alternative, you can also share the complete export directory so that it can be accessed from the target
host.
Procedure
1. On the target host, create a directory with sufficient space for the database export files
available.
Caution
Do not create this directory under the installation directory or another directory that contains
installation information (such as the installation media or export files).
Otherwise, the installer does not ask you to specify the export directory and automatically chooses one
that you may not want to use. In this case, the installer does not display the export directory and you
cannot change it.
2. Transfer all files and directories (recursively) that are located on the source host in the migration export
directory from the source host to the target host.
You can choose one of the following methods:
○ Use the migration monitor with the file transfer protocol (FTP) copy option.
Note
Make sure that you use binary mode for transferring the files.
○ Copy the export dump directory manually to the target host.
○ The export dump directory can be shared and thus made accessible on the target host (network
share).
3. Check the permissions of the transferred files on the target host.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database Independent System Copy PUBLIC 83 Note
All files have to be accessible for user adm of the target system which is created during the target
system installation.
4.1.6.2 Installing the Target System
This section describes how to set up the target system using the installer.
Prerequisites
● There is enough free space on the target system for the database load.
To find out the size of the export and the sizes of the tablespaces or dbspaces that will be created, look
at the file DBSIZE.XML, which is located in the following directory:
/DB/
● SAP MaxDB only: If the database platform of your target system is SAP MaxDB, you must reserve at least
twice as much space as specified in the DBSIZE.XML file. During the import, monitor the remaining free
space in the database using the SAP MaxDB administration tools Database Manager or Database Studio,
and increase it if required.
● The installer automatically performs a reload. If the database software has already been unpacked or
installed, or if the database already exists, the installer recognizes this automatically and skips the related
steps.
Context
This system copy guide describes only the export of the source system in detail. For the installation of the
target system, you use the installation guide for the database and operating system platform of your target
system. This procedure describes only the additional system copy-specific steps for the target system
installation and refers for the remaining steps to the target system installation guide [page 22].
In the following, we refer to this guide as the “installation guide”.
Procedure
1. Prepare the target system host as described in the installation guide for the operating system and
database platform intended for the target system.
2. Start the installer as described in the installation guide for the operating system and database platform
intended for the target system.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
84 PUBLIC Database Independent System Copy Caution
If you plan to use Advanced Configuration options during the SAP System Database Import, make sure
you have installed the most current version of the installer to avoid performance problems during the
Define Parameters phase. You can find the latest version of the installer at:
http://support.sap.com/sltoolset System Provisioning Download Software Provisioning
Manager
Note
If you are running a system copy with parallel export/import using the Migration Monitor with the
R3load socket option and started the export with command line option
SUPPORT_DECLUSTERING=false (see System Copy Procedure [page 48]), you must now 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.
3. On the Welcome screen, navigate to the following folder according to the requirements of your target
system: System Copy Target System Based
on AS ABAP .
4. Run the option required for your system copy.
To install the target system, follow the instructions in the installer input screens (Define Parameters phase)
and enter the required parameters.
If you need to perform some follow-up activities in the target system [page 151] before it is started by the
installer, make sure that on the Parameters Settings screen you choose parameter mode Custom. Then the
installer will display the Actions Before SAP System Start screen, where you can choose Interrupt before
starting the SAP system.
Caution
Heterogeneous system copy: When installing the database instance, you either have to choose
parameter mode Custom or have to check the Database Import screen on the summary screen and
then revise this screen. Only then appears the screen where you can enter the migration key, which is
required for a heterogeneous system copy. If you forget to revise this screen setting during the De fine
Parameters phase, the installer will abort in the processing phase when checking the migration key and
will ask you for a valid migration key.
Note
Oracle Database only: If your source system has Oracle Database Vault, consider the additional
information in SAP Note 2218115 .
Caution
○ If you perform a Unicode conversion, the data import into the target system might abort because
of missing space in the database tablespace or dbspace. Enlarge the database or database
container, in which the table will be created in the target database. The required size for the table
will be 15 times larger than in the non-Unicode source system.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database Independent System Copy PUBLIC 85○ Do not create the installation directory (for example: sapinst_instdir) in the following
directories:
○ /usr/sap/
○ /sapmnt/
○ If you want to perform export processes in parallel to import processes and you have prepared the
export, you must do the following:
○ Choose Custom on the Parameter Mode screen.
○ Select Parallel Export and Import on the SAP System Database Import screen.
○ On the SAP System Database screen, choose Standard System Copy/Migration (Load-Based).
The SAP data dump from the migration export media that was created during the database instance
export is loaded in the newly installed SAP system database.
○ When the installer displays the Media Browser screen and prompts for the Export Location, enter the
path to the export directory .
○ If you perform a heterogeneous system copy, enter the Migration Key on the Database Import screen.
5. Complete the installation as described in the installation documentation for your SAP component.
○ If you have to restart the import after an error, just restart the installer. The import continues with the
table that has not yet been successfully imported.
○ If you have to restart failed R3load processes, see Restarting R3load Processes [page 81].
○ You can use the Migration Checker tools to ensure that the import has been performed
successfully. The package checker and the object checker automatically check that the import
has started and that all objects have been imported. In addition, you can use the table checker tool
to verify that the number of rows that have been exported is equal to the number of rows in the
database by using the table of content (TOC) files. For more information about the table checker,
see SAP Note 2009651 . For more information about all these checks see the Migration Checker
User Guide. It is contained in the MIGCHECK.SAR archive as MigrationChecker.pdf and is available
in the following directory of the installer:
/COMMON/INSTALL/MIGCHECK.SAR
○ As an alternative to the table checker, you can perform Table Comparison with Software Update
Manager (SUM) [page 192].
Proceed as follows:
1. Make sure that the primary application server instance is not started after the import has fi nished
successfully.
If your system is based on SAP NetWeaver 7.4 or higher, you can mark the check box Interrupt
installation before starting the SAP system on the screen Actions Before SAP System Start to
ensure this.
2. Run table comparison [page 193]
3. Start the instances of the target system.
Note
If you have to restart failed R3load processes, see Restarting R3load Processes [page 81].
You can use the Migration Checker to ensure that the import has been performed successfully. The
Migration Checker automatically checks that the import has started and that all objects have been
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
86 PUBLIC Database Independent System Copyimported. For more information about additional checks with the Migration Checker, see the Migration
Checker User Guide contained in the MIGMON.SAR archive, which is available in the following directory:
You can use the Migration Checker tools to ensure that the import has been performed
successfully. The package checker and the object checker automatically check that the import
has started and that all objects have been imported. In addition, you can use the table checker tool
to verify that the number of rows that have been exported is equal to the number of rows in the
database by using the table of content (TOC) files. For more information about the table checker,
see SAP Note 2009651 . For more information about all these checks see the Migration Checker User
Guide. It is contained in the MIGCHECK.SAR archive as MigrationChecker.pdf and is available in the
following directory of the installer:
/COMMON/INSTALL/MIGCHECK.SAR
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database Independent System Copy PUBLIC 875 Database-Specific System Copy
The following sections describe the database-specific methods for the system copy.
Note
When performing a system copy using a database-specific method, it is not required to run the installer in
the source system to export it. You only have to run the installer on the target host to install the target
system.
Process
Follow the sequence of steps described in the process flows below for a:
● Standard system
● Distributed system
● High-availability system
Standard System
Note
When performing a system copy using a database-specific method, it is not required to run the installer in
the source system to export it. You only have to run the installer on the target host to install the target
system.
Process Flow on the Source System (Export)
1. Oracle only: You generate the control file structure for the target database [page 94].
2. Oracle only: If required, you create an offline backup of the source database [page 102].
Process Flow on the Target System
Note
For the target system installation, you use the installation guide [page 22] for your target operating system
and database.
In the following we refer to this documentation as “installation guide”.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
88 PUBLIC Database-Specific System Copy1. Oracle only: You prepare the target system [page 98]:
1. Start the installer as described in the installation guide and follow the instructions on the installer
screens until the installer requests you to install the database software and to perform the database
backup/restore.
2. You create the database file system (if not yet existing).
3. You install the database software.
2. Start the installer as described in the installation guide and follow the instructions on the installer screens
until you are requested to perform the database backup/restore.
Note
If required, you have to restart the installer as described in the installation guide.
3. To complete the system copy, you perform the follow-up activities [page 149].
Distributed System or High Availability System
Note
When performing a system copy using a database-specific method, it is no longer required to run the
installer in the source system to export it. You only have to run the installer on the target host to install the
target system.
Process Flow on the Source System (Export)
1. Oracle only: On the database instance host of the source system, you generate the control file structure
for the target database [page 94].
2. Oracle only: If required, on the database instance host, you create an offline backup of the source
database [page 102].
Process Flow on the Target System
Note
For the target system installation, you use the installation guide [page 22] for your target operating system
and database.
In the following we refer to this documentation as “installation guide”.
1. Oracle only: You prepare the target system [page 98]:
1. On the database instance host, start the installer as described in the installation guide and follow the
instructions on the installer screens until the installer requests you to install the database software and
to perform the database backup/restore.
2. On the database instance host, you create the database file system (if not yet existing).
3. On the database instance host, you install the database software.
2. On the database instance host, start the installer as described in the installation guide and follow the
instructions on the installer screens until you are requested to perform the database backup/restore.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 89 Note
If required, you have to restart the installer as described in the installation guide.
3. To complete the system copy, you perform the follow-up activities [page 149].
5.1 Oracle-Specific Procedure
Purpose
In an SAP system environment, you can create a homogeneous copy of an Oracle database by copying
database files. This method is suitable for creating an exact copy of an existing database. The source of the
copy can be an online or offline backup, or the file system of your source host.
You use the installer for the installation on the target system host as described in the installation
documentation for your SAP component. Only the installer steps for setting up and loading the database steps
are different.
Advantages
● You can use existing offline backups (provided that redo logs were cleaned up with forced log switches).
● This method is faster than the R3load method.
Disadvantages
● Offline backup/copy of database files in a heterogeneous environment is not possible because the
hardware of the source and target systems must be binary-compatible.
● Source system host and target system host must be different.
● You must shut down the SAP system and the database during offline backup/copy of database files.
● You cannot change the database schema and the tablespace names.
Prerequisites
● You must use the same Oracle release and patch level for your database in the source and target system.
● The source and target systems must run on different hosts for security reasons.
● The source and target systems must be binary compatible.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
90 PUBLIC Database-Specific System Copy Note
You can also perform a system copy from 32-bit systems to 64-bit systems and the other way around
(same operating system assumed) even if source and target system are not binary compatible.
● If your source system uses the US7ASCII character set, you must choose this character set when
installing the target system. The installer prompts for the character set during the installation (key:
Database Character Set). The installation default is WE8DEC or UTF8 for Unicode systems. To find out
the character set used by the source system, connect to the source database as user sap or
sapr3 with sqlplus and enter: SELECT * FROM V$NLS_PARAMETERS;
● If your source system has Oracle Database Vault, consider the additional information in SAP Note 2218115
.
Oracle Storage-Based System Copy Methods Available in the Installer
You can choose between the following methods:
● Database already recovered, continue with database-specific post activities
You have already performed backup/restore with Oracle-specific methods. In this case, the installer does
not need to perform the backup/restore. You just have to ensure that the restored Oracle database on your
target system is up and running.
● Performing Online or Offline Recovery with saphostctrl [page 91]
● Using a CONTROL.SQL File Created by the ORABRCOPY Tool [page 94]
Related Information
Database-Specific System Copy [page 88]
5.1.1 Performing Online or Offline Recovery with
“saphostctrl”
This section describes how to perform a recovery using saphostctrl.
For the offline recovery method, we recommend that you shut down the database. Alternatively, the software
provisioning manager (the “installer” for short) can also make an instance recovery of the database if it has not
been shut down before the copy process.
For the online recovery 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.
A “shared directory” can be any directory path which the source system and the target system can access. The
archives and also the init.ora files from the source system will be saved in this directory
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 91Restrictions
You cannot change the database schemas SAP and SAPDB. There is no “move”
schema.
The can be changed because the rename process is able to create new control files with a new
.
The can be also changed.
Related Information
Performing Online Recovery [page 92]
Performing Offline Recovery [page 93]
5.1.1.1 Performing Online Recovery
For the online recovery method, you have to proceed as follows.
Procedure
1. You can set the source database to a backup mode using the following command:
saphostctrl -user sapadmsaphostctrl -function PrepareDatabaseCopy -dbname
-dbtype ora -dbconfdir -copymethod Online -timeout -1
2. Back up the data files, for example using image copy or snapshot technology.
3. 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 -dbtype ora -
dbconfdir -copymethod Online -timeout -1
4. Start the target system installation and follow the instructions on the installer screens.
Start the target system installation as described in the Installation Guide - Installation of SAP Systems
Based on the Application Server ABAP of SAP NetWeaver 7.1 to 7.5x on UNIX : Oracle (see Accessing the
Installation Guides [page 22]).
5. On the Performing Oracle Storage Based System Copy screen, select option Online or Offline Recovery
Method with saphostctrl
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
92 PUBLIC Database-Specific System Copy5.1.1.2 Performing Offline Recovery
For the offline recovery method, you have to proceed as follows.
Procedure
1. Shut down the source database.
2. Back up the data files, for example using image copy or snapshot technology.
3. Start the target system installation and follow the instructions on the installer screens.
Start the target system installation as described in the Installation Guide - Installation of SAP Systems
Based on the Application Server ABAP of SAP NetWeaver 7.1 to 7.5x on UNIX : Oracle (see Accessing the
Installation Guides [page 22]).
4. On the Performing Oracle Storage Based System Copy screen, select option Online or Offline Recovery
Method with saphostctrl.
5. Leave the dialog field of the empty while performing an offline recovery while no
additonal files from the source system are needed.
6. When the installer stops for database restore, copy all saved files to the target System.
Make sure that you also copy either the source spfile.ora file - which must contain parameters
and not only the entry spfile=… - or the source spfile.ora file.
5.1.2 Using a CONTROL.SQL File Created by the ORABRCOPY
Tool
Related Information
Generating the Control File Structure [page 94]
Preparing the Target System (Oracle) [page 98]
Restoring the Database Files on the Target System [page 99]
Restoring the Database Files on the Target System with BR*Tools [page 101]
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 935.1.2.1 Generating the Control File Structure
Use
The OraBRCopy Java tool writes a file CONTROL.SQL to the current working directory, which can be used
without further adaptations on the target system.
For more information about command line options and output files of the OraBRCopy tool, see Additional
Information about the OraBRCopy Tool [page 214].
Prerequisites
Recommendation
We recommend that you shut down the SAP system before you perform the following steps. The database
must still be running.
Procedure
1. Create an installation directory with permissions 777 on the source system.
2. Copy the ORABRCOPY.SAR archive from the directory to which you unpacked the
SWPM10SP_.SAR file and extract it using SAPCAR.
You can find the archive in the following directory:
/COMMON/INSTALL/ORA/ORABRCOPY.SAR
3. Make sure that all redo log groups are archived
4. Start the OraBRCopy tool as an OS user with Oracle DBA privileges:
○ user ora
○ user adm
5. Execute the ora_br_copy.sh script in one of the following ways:
○ If you perform an offline manual copy, enter the following commands:
./ora_br_copy.sh -generateFiles -forceLogSwitches -targetSid -
password -listenerPort
The tool creates the files CONTROL.SQL, CONTROL.TRC and init.ora in your
installation directory, shuts down and restarts the database and performs the required log switches.
○ If you perform an offline or online backup using BR*Tools, enter the following commands:
./ora_br_copy.sh -generateFiles -targetSid -password
-listenerPort
Note
During the online backup, the database must be up and running. To ensure this, this command
must not contain the parameter -forceLogSwitches.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
94 PUBLIC Database-Specific System CopyThe tool creates the files CONTROL.SQL, CONTROL.TRC and init.ora in your
installation directory, and performs the required log switches.
Note
If an error occurs, check the log file:
/ora.brcopy.log
6. Verify and, if necessary, update the CONTROL.SQL control file using the CONTROL.TRC trace file as follows.
Example
In the following example, entries of CONTROL.SQL written in bold should be compared and changed according
to the trace file:
REM
====================================================================
REM CONTROL.SQL
REM
REM SAP AG Walldorf
REM Systeme, Anwendungen und Produkte in der Datenverarbeitung
REM
REM (C) Copyright SAP AG 2004
REM
====================================================================
REM Generated at:
REM Fri Sep 17 08:33:25 CEST 2005
REM for target system NEW
REM on
REM Windows 2000 5.0 x86
CONNECT / AS SYSDBA
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE
SET DATABASE "NEW"
RESETLOGS
ARCHIVELOG
MAXLOGFILES 255
MAXLOGMEMBERS 3
MAXDATAFILES 1022
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 95MAXINSTANCES 50
MAXLOGHISTORY 1134
LOGFILE
GROUP 1 (
''/oracle/NEW/origlogA/log_g11m1.dbf'',
''/oracle/NEW/mirrlogA/log_g11m2.dbf''
) SIZE 50M,
GROUP 2 (
''/oracle/NEW/origlogB/log_g12m1.dbf'',
''/oracle/NEW/mirrlogB/log_g12m2.dbf''
) SIZE 50M,
GROUP 3 (
''/oracle/NEW/origlogA/log_g13m1.dbf'',
''/oracle/NEW/mirrlogA/log_g13m2.dbf''
) SIZE 50M,
GROUP 4 (
''/oracle/NEW/origlogB/log_g14m1.dbf'',
''/oracle/NEW/mirrlogB/log_g14m2.dbf''
) SIZE 50M
DATAFILE
''/oracle/NEW/sapdata1/system_1/system.data1'',
''/oracle/NEW/sapdata3/ims_1/ims.data1'',
''/oracle/NEW/sapdata3/ims_2/ims.data2'',
''/oracle/NEW/sapdata3/ims_3/ims.data3'',
''/oracle/NEW/sapdata3/ims_4/ims.data4'',
''/oracle/NEW/sapdata4/ims_5/ims.data5'',
''/oracle/NEW/sapdata4/ims_6/ims.data6'',
''/oracle/NEW/sapdata4/ims_7/ims.data7'',
''/oracle/NEW/sapdata4/ims_8/ims.data8'',
''/oracle/NEW/sapdata4/ims_9/ims.data9'',
''/oracle/NEW/sapdata1/ims700_1/ims700.data1'',
''/oracle/NEW/sapdata1/ims700_2/ims700.data2'',
''/oracle/NEW/sapdata1/ims700_3/ims700.data3'',
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
96 PUBLIC Database-Specific System Copy''/oracle/NEW/sapdata1/ims700_4/ims700.data4'',
''/oracle/NEW/sapdata2/ims700_5/ims700.data5'',
''/oracle/NEW/sapdata2/ims700_6/ims700.data6'',
''/oracle/NEW/sapdata2/ims700_7/ims700.data7'',
''/oracle/NEW/sapdata2/ims700_8/ims700.data8'',
''/oracle/NEW/sapdata2/ims700_9/ims700.data9'',
''/oracle/NEW/sapdata3/ims700_10/ims700.data10'',
''/oracle/NEW/sapdata4/ims700_11/ims700.data11'',
''/oracle/NEW/sapdata1/imsUSR_1/imsUSR.data1'',
''/oracle/NEW/sapdata2/roll_1/roll.data1''
;
ALTER DATABASE OPEN RESETLOGS;
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE
''/oracle/NEW/sapdata3/temp_1/temp.data1''
SIZE 350M REUSE AUTOEXTEND OFF;
Note
In the above example, entries and values of CONTROL.SQL written in bold should be compared to the trace
file.
Changes to be made
1. If you want to migrate your database from 32-bit to 64-bit or vice versa, add the following lines at the
bottom of the CONTROL.SQL file:
shutdown immediate
startup upgrade
spool utlirp.log
@?/rdbms/admin/utlirp.sql
spool off
shutdown immediate
startup
spool utlrp.log
@?/rdbms/admin/utlrp.sql
spool off
exit
2. MAXLOGFILES 255
...
The numbers must be greater than or equal to the corresponding numbers in the trace file.
3. GROUP 1 (
''/oracle/NEW/origlogA/LOG_G11M1.DBF'',
''/oracle/NEW/MIRRLOGA/LOG_G11M2.DBF''
) SIZE 50M,
Group 2 (
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 97…
The sizes of the respective groups must be equal to the sizes of the corresponding groups in the trace file.
4. ''/oracle/NEW/sapdata1/SYSTEM_1/SYSTEM.DATA1'',
''/oracle/NEW/sapdata3/ims_1/ims.DATA1'',
…
''/oracle/NEW/sapdata1/ims700_1/ims700.DATA1''
…
The count of the data files must be equal to the count of the corresponding data files in the trace file.
5. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE
''/oracle/NEW/sapdata3/temp_1/temp.DATA1''
SIZE 350M REUSE AUTOEXTEND OFF;
…
The size must be equal to the corresponding size in the trace file.
6. The number of rows with ALTER TABLESPACE must be equal to the number of corresponding rows in the
trace file.
5.1.2.2 Preparing the Target System (Oracle)
This section describes how to prepare the target system for Oracle-specific system copy.
Prerequisites
Make sure that sapdata file systems on the target system host are large enough.
Procedure
1. Install the target SAP system with the installer as described in the installation documentation for your SAP
solution.
Caution
When you perform a system copy with the Oracle backup/restore method, you cannot change the
database schema and the tablespace names of the new target system. When installing the target
primary application server instance, the target database instance, or the target additional application
server instance make sure that you enter the correct database schema names (which are the database
schema names of the source system). The schema names of the source and target system must be
identical.
a. On the Welcome screen, choose System Copy Target
System .
b. When the installer prompts for the database copy method, choose Homogeneous System Copy
(Backup/Restore).
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
98 PUBLIC Database-Specific System Copyc. Proceed until the installer stops to restore the database files on the target system.
The following message is displayed:
SAPinst now stops the installation. Proceed as follows:...
2. If necessary, extract the Oracle stage archives manually and install the Oracle software as described in the
installation documentation for your SAP solution.
3. Restore the database files on the target system.
4. If they do not exist, create the following directories on the target system:
○ /oracle//mirrlog
○ /oracle//origlog
○ /oracle//sapdata
○ /oracle//sapreorg
○ /oracle//saparch
○ /oracle//oraarch
○ /oracle//saptrace
○ /oracle//saptrace/background
○ /oracle//saptrace/usertrace
○ /oracle//origlogA/cntrl
○ /oracle//sapdata1/cntrl
○ /oracle//saparch/cntrl
○ /oracle//sapcheck
○ If Oracle TDE is enabled, make sure that you also copy the Oracle wallet key file to the target system.
The wallet file is located under /oracle//orawallet/tde/*.
5. Make sure that the following directories are empty (except the subdirectory saparch/cntrl):
○ /oracle//saparch
○ /oracle//oraarch
6. All directories must be owned by the software owner oracle:oinstall (default for Oracle 12c) of the
target database or ora:dba (default for Oracle 11g).
To do this, enter the following command:
Oracle 12c: chown -R oracle:oinstall
Oracle 11g: chown -R ora:dba
5.1.2.3 Restoring the Database Files on the Target System
Use
Caution
If you do not use an offline backup but copy the database files directly from the source to the target system
host, make sure that you shut down the database on the source system before you copy the listed files
from the source to the target directories.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 99Procedure
1. Copy the following files from the source to the target system host either by using an offline backup or by
copying the listed files from the source directories to the target directories.
Directories on UNIX
Source and Target Directory Files
/oracle//sapdata All files
/oracle//origlog All files
/oracle//mirrlog All files
Source: CONTROL.SQL
Target:
Source: init.ora
Target: /oracle//
_/dbs
Directories on Windows
Source and Target Directory Files
:\oracle\\sapdata All files
:\oracle\\origlog All files
:\oracle\\mirrlog All files
Source: CONTROL.SQL
Target:
Source: init.ora
Target: \oracle\\_\database
2. After you have copied the database files, make sure that the files on the source and target system are not
located in different directories or drives. If required, make the corresponding changes in the files
control.sql and the init.ora.
3. Verify that the created directories and copied files have the owner ora, belong to the
group dba, and have the permissions 740.
4. Make sure that the control files are not restored. If necessary, remove them.
The file names are specified by the parameter control_files of the init.ora file.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
100 PUBLIC Database-Specific System Copy5.1.2.4 Restoring the Database Files on the Target System
with BR*Tools
Procedure
1. Copy the following files from the source system host to the target system host by copying manually the
listed files from the source directories to the target directories.
Source and Target Directory Files
Source: CONTROL.SQL
Target:
Source: init.ora
Target: /oracle//
_/dbs
2. Call the restore and recovery function of BR*Tools.
If you follow these instructions, the prerequisites are fulfilled. The main prerequisite is that the
corresponding BR*Tools logs (BRBACKUP detailed and summary log, BRARCHIVE summary log) are copied
from the source to the target system. In addition, the postprocessing steps mentioned in the SAP Note
1003028 are covered during the standard system copy procedure.
Note
If Oracle TDE [page 207] is enabled when using BR recovery, you need to provide your wallet
password.
You can specify the wallet password with the BRRECOVER option -pw .
Example:
brrecover -u / -t reset -b last -f -pw -c force
For more information about the execution of restore and recovery under the control of BRRECOVER and the
exact syntax of BRRECOVER, see the section Homogeneous Database Copy in SAP Note 1003028 .
For more information about BR*Tools, see the SAP Library [page 22] for your release at:
Note
Navigate to the SAP Help Portal page for the SAP NetWeaver release your SAP product is based on as
described in section Accessing the SAP Library [page 22] , and then continue the navigation as
described below.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 101SAP NetWeaver Release Location
SAP NetWeaver 7.3 EHP1 and higher SAP NetWeaver Library: Function-Oriented View
Administration of Databases Database Administration for
Oracle SAP Database Guide: Oracle BR*Tools for Oracle DBA
3. Shut down the Oracle database instance as follows:
sqlplus /nolog
shutdown immediate
exit
5.1.3 Creating a Backup
Create a backup if required. Choose between the following possibilities: Performing an offline backup manually
or an offline or online backup with BR*Tools.
Related Information
Creating an Offline Backup [page 102]
Creating an Offline or Online Backup with BR*Tools [page 103]
5.1.3.1 Creating an Offline Backup
Create an offline backup, if required. There are different possibilities for preparing the actual transfer of the
database files:
● If you have an up-to-date offline backup, you can use it (provided that redo logs were cleaned up with
forced log switches).
● If you want to transport the database file (for example, on tape) or if you have to perform the database
shutdown at a certain time, stop the database (normal shutdown) and perform a complete offline backup.
You can use the trace file CONTROL.TRC created by OraBrCOPY to determine the file system trees that
have to be saved.
● Stop the database (normal shutdown) and copy the database files when the actual transfer to the target
system takes place. You do not have to perform any preparations for the actual transfer now. Proceed with
the next steps.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
102 PUBLIC Database-Specific System Copy5.1.3.2 Creating an Offline or Online Backup with BR*Tools
You can use any backup strategy supported by BR*Tools as the basis for a system copy: offline or online, with
or without BACKINT, with or without RMAN, complete or incremental, and so on. The backup strategy must
simply be valid for restore and recovery. This means that a complete restore and recovery of the source
database must be possible. In addition for BACKINT and RMAN, the external backup tools must be configured so
that a restore is possible on the target host.
Procedure
Proceed as described in the SAP Library [page 22] for your release at:
Note
Navigate to the SAP Help Portal page for the SAP NetWeaver release your SAP product is based on as
described in section Accessing the SAP Library [page 22] , and then continue the navigation as described
below.
SAP NetWeaver Library: Function-Oriented View Administration of Databases Database Administration
for Oracle SAP Database Guide: Oracle BR*Tools for Oracle DBA BR*Tools in Action Backup and
Database Copy with BR*Tools
5.2 SAP MaxDB-Specific Procedure
In an SAP system environment, you can create a homogeneous copy of an SAP MaxDB database by using the
backup and restore method. This method is suitable for creating an exact copy of an existing database. The
source of the copy is a complete data backup of your source database.
Prerequisites
● Byte order – little-endian or big-endian
You can use the backup and restore method to copy systems with the same byte order. That is, you can
copy a system based on little-endian to another system based on little-endian. You can also copy a system
based on big-endian to another system based on big-endian. Check SAP Note 552464 to find out which
processor and operating system combination uses which byte order.
● Data backup
You perform the complete data backup of your source database.
● Recovery tool (manual restore)
You are using the SAP MaxDB Database Manager (DBMGUI) version 7.5.0 Build 12 or above. For more
information, see:
http://maxdb.sap.com/doc/7_6/default.htm Tools Database Manager GUI
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 103Alternatively, you can use Database Studio. For more information, see:
http://maxdb.sap.com/doc/7_7/default.htm Tools Database Studio
● Database Software
The database software on the target host must have the same version as the software on the source host.
The build number of the software version on the target host must be greater than or equal to the version on
the source host.
● Size of the data on the target system
The size of the target system must be greater than the used space on the source system. You can find the
size of the used pages on the source system as follows:
dbmcli —d —u , —n —u SQL
sap, sql_execute ''SELECT USEDPERM FROM SERVERDBSTATISTICS''
The result of this query is the amount of used space, expressed as the number of 8 KB pages. To get the
used space in MB, divide this value by 128. When the installer prompts you, configure the database data
volumes according to this value.
Context
The installer is used for installation on the target system host as described in the installation documentation for
your SAP solution at http://support.sap.com/sltoolset System Provisioning Installation Option . In
the installer, you select the backup and restore method as the database installation method.
This description is not valid for the liveCache system copy.
Caution
Make sure that you know the password of the database system administrator (SUPERDBA) from the
source system before you start the procedure below. Otherwise, you cannot access the database contents
on the target system.
You must also know the name of the SQL database schema on the source system, SAP – for
example, SAPR3.
You can perform this procedure in the following ways:
● Manual restore
The installer stops before the database instance initialization and asks you to perform the restore on the
target database. After you have performed restore and post-restore activities, you can continue the
installation in the installer.
● Automatic restore
The installer performs the restore to import the data into the target system.
In this scenario, you have to use a single file as the backup medium for the whole backup. The restore can
use any SAP MaxDB backup, as long as it is a single file.
Note
The minimum size of the database is calculated from the size of the backup file.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
104 PUBLIC Database-Specific System CopyAdvantages
● You can use existing offline backups.
● This method is faster than the database-independent method using R3load [page 47].
Disadvantage
You can only copy between systems with the same byte order.
Perform the following steps on the target system:
Procedure
1. To import the target system, start the installer as follows and then follow the prompts:
System Copy Target System
2. When the installer prompts for the database copy method, choose Homogeneous System Copy.
3. In the MaxDB Backup Template screen, choose one of the following, Manual Restore, or Restore by Software
Provisioning Manager:
○ Manual restore
In the execution phase, you are prompted to do the following:
1. Start the data recovery wizard from DBMGUI
1. Register your database instance in the DBMGUI
2. Check the database instance in the admin state.
3. Choose Recovery Recovery with Initialization ...
4. In type of recovery, select Restore a medium.
5. Specify the backup medium.
6. Start the restore procedure.
Note
The recovery wizard does not start the recovery immediately. It initializes the database
instance first. It takes some time for the database server to format the database volumes.
2. After the restore, check the state of the target database instance. Change the database state to
online if it is not already in online state.
3. Delete the entries from the following tables to make sure that information about the backup
history for update statistics in the Computing Center Management System (CCMS) from the old
system does not appear in the new system:
CNHIST, CNREPRT, CNMEDIA, DBSTATHADA, DBSTAIHADA, DBSTATIADA, DBSTATTADA,
SDBAADAUPD
4. Continue with the installer or restart it if you stopped it during the recovery.
○ Restore by the Installer
Enter the following information:
○ Template name
○ Device/file
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 1054. After installation is completed, maintain the database connection for CCMS.
For more information, see SAP Note 588515 .
5.3 IBM Db2 for Linux, UNIX, and Windows- Specific
Procedures
The database-specific procedure for the creation of a system copy is based on a restore of an existing online or
offline backup. Therefore, this method is also referred to as backup/restore procedure. Since you can use a Db2
backup cross-platform within certain limitations (see below), this method is not limited to the homogenous
system copy only.
Note
This backup/restore procedure described here only works using the installer. System copy using native Db2
backup/restore procedures without the installer are not supported for SAP systems.
Prerequisites
● It must be possible to restore the backup of the source system on the platform of the target system.
Note
For more information about cross-platform backups, also see Backup and restore operations between
different operating systems and hardware platforms in the IBM Db2 Information Center at https://
publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/
com.ibm.db2.luw.admin.ha.doc/doc/c0005960.html .
● If errors occur when restoring the backup on the target system, the complete restore must be repeated.
● If you restore from an encrypted Db2 database backup, you need to make sure that your Db2 instance is
set up for encryption in order to access the data from the backup image.
The installer will configure the Db2 instance for encryption and create a keystore file in which you must
provide the master key of the backup. For details, see the procedure below.
Context
Note
You can also create an SAP system copy with a Db2 database if more advanced techniques like file system
snapshots are available. The necessary procedure in this case is called database relocation. The database
relocation procedure differs significantly from the backup/restore procedure and is not described in this
guide.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
106 PUBLIC Database-Specific System CopyFor more information, see the Database Administration Guide: SAP on IBM Db2 for Linux, UNIX, and
Windows, section db2inidb Option: as snapshot.
The installer is used for the installation on the target system host as described in the installation
documentation for your SAP component. Before you start the installer on the target system make sure that all
prerequisites for the SAP system installation are met. Especially, make sure that the relevant file systems are
available. For more information, see the installation guide [page 22].
In the ABAP system, only the installer steps for setting up and loading the database are replaced by a database
restore.
Advantages of the Backup Method
● You can use existing online and offline backups.
● Using the backup method is faster than the database-independent method [page 47].
Disadvantages of the Backup Method
● You cannot change the name of the database schema. The name of the database schema is the same as
that of the source system.
However, you can change the name of the connect user during the Define Parameters phase of the target
system installation.
● You cannot copy an individual MCOD component to another system. You can only copy the complete
system.
Procedure
1. You perform an online or offline backup.
If you use an online backup to copy your system, a roll forward of your database is required after the
database restore on the target system. As a prerequisite, the respective database logs must be accessible.
We, therefore, recommend that you include the necessary log files in the backup image. Logs are included
in the online backup image as long as the option EXCLUDE LOGS is not specified.
2. To create a target system, run the installer on the target system host by choosing the following on the
Welcome screen: System Copy Target System
Perform the installation options in the given sequence and follow the instructions on the installer dialogs.
When the installer prompts for the database copy method, choose Homogeneous System Copy.
Note
If you restore from an encrypted database or you want to encrypt your new database from an
unencrypted backup, you must select Use Db2 native encryption in the Define Parameters phase. The
Db2 instance will be configured to allow usage of Db2 native encryption, and a keystore file and a new
master key will be created.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 107 Caution
Be aware of the following constraints when using the backup method for a homogeneous system copy:
○ You cannot change the name of the database schema, during the dialog phase make sure that you
enter the database schema exactly as on your source system.
○ The tablespace names remain the same during the database restore. However, you can change
them after the installation.
○ If you want to change the name or the location of the Db2 container on the target system, you have
to adapt the Db2 container paths or names in the redirected restore script and then perform a
redirected restore. For more information, see the documentation Database Administration Guide:
SAP on IBM Db2 for Linux, UNIX, and Windows, section Usage of Tool brdb6brt.
3. Multi-Partition Database Environments only: Add database partitions
If you copy a system with multiple database partitions, the target system must have the same number of
partitions as the source system. For more information, see Setting up partitioned database environments in
the IBM Db2 Information Center at: http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?
topic=/com.ibm.db2.luw.qb.server.doc/doc/t0023605.html
4. If you restore from an encrypted backup image, you must provide the master key used with the backup
image.
a. Log on as db2 to your database host.
b. Run the following command:
setenv PATH ${PATH}:/db2/db2/sqllib/gskit/bin
c. Depending on your platform, run the following:
AIX: setenv LIBPATH ${LIBPATH}:/db2/db2/sqllib/lib64/gskit
HP: setenv SHLIB_PATH ${SHLIB_PATH}:/db2/db2/sqllib/lib64/gskit
Linux and Solaris: setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/db2/db2/
sqllib/lib64/gskit
d. Import the master key from your source system. Make sure the file permissions allow access to the
source keystore file. You can choose to import all master keys from the source system or only the one
used with the backup image by adding -label to the following command:
gsk8capicmd_64 -cert -import -db .p12 -target /db2/
db2/keystore/sapdb2_db_encr.p12
e. Make sure that you add encryption options to your restore command.
○ If your target database is encrypted, insert the following:
encrypt cipher key length master key label
sap_db2__dbencr_000
where is either AES or 3DES
Recommendation
We recommend that you use the master key label of your target system. This was generated by
the installer before the exit step.
○ If your target database is unencrypted, insert the following:
no encrypt
For more information, see the IBM documentation for the database restore command.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
108 PUBLIC Database-Specific System Copy5. Restore your database.
To restore your database, you can choose between one of the following options:
○ Simple database restore
To perform a database restore, use the Db2 RESTORE command. For more information, see the IBM
manual Db2 Command Reference.
Note
With a simple restore, you can neither change the name nor the location of Db2 containers.
○ Redirected restore
This is the recommended method.
A redirected restore allows you to change the name or the location of the Db2 container. To perform a
redirected restore, you use the Db2 RESTORE DATABASE command with the REDIRECT GENERATE
SCRIPT option. For more information, see RESTORE DATABASE command in the IBM Db2 Information
Center at:
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/
com.ibm.db2.luw.admin.cmd.doc/doc/r0001976.html .
Alternatively, you can use the tool brdb6brt that retrieves a database backup and creates a CLP
script to restore this backup image. Since brdb6brt needs to connect to the source system, the
source system must be available. For more information about how to use the tool brdb6brt, see
Redirected Restore Using brdb6brt in the Database Administration Guide: SAP on IBM Db2 for Linux,
UNIX, and Windows.
If you have used an online backup, you have to make sure that you have access to the log files that were
created during the online backup. You also have to perform a rollforward operation to bring the database
into a consistent state.
If you have chosen to use Db2 native encryption for your target database, verify that your restored
database is encrypted by checking the database configuration with db2 get db config for
and search for “Encrypted database = YES” in the output.
You can now continue with the installation.
Next Steps
After the installation on the target system, do the following:
● To adhere to the SAP standard naming conventions for tablespaces, we recommend that you consider
renaming the tablespaces after the installation to reflect the new system name. Each tablespace must be
renamed individually. To rename a tablespace, enter the following command:
db2 rename tablespace to
Example
db2 rename tablespace #DIMD to #DIMD
If you use the deferred table creation function and you renamed your tablespaces, you also have to
execute the following command using the db6util tool:
db6util -rtvt #% #%
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 109For more information, see SAP Note 1227165 .
Caution
Make sure that you use an up-to-date version of the db6util tool. You require at least a version that
supports the option -rtvt. To check the command options of the db6util tool, enter the following
command:
db6util -h
In addition, you have to update the tablespace names in tables TSDB6, IADB6, and TADB6. To rename all
tablespaces in the respective tables according to the standard naming conventions, use the following
commands:
○ For table TSDB6, enter the following SQL command:
update .tsdb6 set tabspace = ''#''||
substr(tabspace,5,length(tabspace)-4),indspace=''#''||
substr(indspace,5,length(indspace)-4)
○ For table IADB6, enter the following SQL command:
update .iadb6 set tabspace = ''#''||
substr(tabspace,5,length(tabspace)-4)
○ For table TADB6, enter the following SQL command:
update .tabdb6 set tabspace = ''#''||
substr(tabspace,5,length(tabspace)-4)
● If you performed a redirected restore, check all settings of the database manager and database
configuration parameters. Specifically, make sure that the following configuration parameters point to the
correct path:
○ DIAGPATH (DBM)
○ DFTDBPATH (DBM)
○ Path to log files (DB)
○ If set, NEWLOGPATH (DB), OVERFLOWLOGPATH (DB), FAILARCHPATH (DB) and MIRRORLOGPATH (DB)
More Information
● Database Administration Guide: SAP on IBM Db2 for Linux, UNIX, and Windows available at https://
help.sap.com/viewer/db6_admin.
● IBM Knowledge Center at https://www.ibm.com/support/knowledgecenter/SSEPGG
● IBM Db2 manuals at http://www-01.ibm.com/support/docview.wss?uid=swg27023558
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
110 PUBLIC Database-Specific System Copy5.4 IBM Db2 for z/OS Specific Procedures
In an SAP system environment, you can create a homogeneous system copy of a DB2 database using the
offline system copy method.
Prerequisites
The following prerequisites must be fulfilled to use this method:
● The permissions of the source and target systems must be completely separate. The source system must
not be able to use the resources of the target system, and the target system must not be able to use the
resources of the source system.
● RACF authorization for the target DB2 subsystem is complete.
● Source and target systems must work with DB2 managed objects.
● Procedures of the source and the target system are defined in the DB2 PROCLIB.
● Source and target systems have appropriate entries in the APF list.
● Volumes of the source and target systems are managed by SMS.
● At first source and target systems run with the same DB2 service level. After copying the source system to
a target system, you can migrate or upgrade both systems to a higher service level.
Context
This document assumes that the database schema of your SAP system is SAPR3. If you employ a differe nt
schema, adapt the references to SAPR3 in the following SQL statements and jobs to reflect the actual schema
name.
The following section describes an offline system copy method for SAP systems on IBM Db2 for z/OS.
Advantage of the Offline System Copy Method
This method is faster than the database-independent method [page 47].
Restriction of the Offline System Copy Method
At the moment, you cannot copy an individual MCOD component to another system. You can only copy the
complete system.
Note
The offline system copy must be performed by an experienced database administrator.
You can find an adapted procedure for an online system copy in the IBM documentation High Availability for
SAP on zSeries Using Autonomic Computing Technologies.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 111Process Flow of the Main Steps in this Procedure
The following sections contain the detailed steps involved in the homogeneous system copy procedure for Db2
for z/OS.
The offline system copy can be divided into the following steps:
Procedure
1. Step 1: Check the Source System and Stop it after Successful Check [page 112]
2. Step 2: Consider DB2 Procedures of the Target System [page 114]
3. Step 3: Delete All Obsolete Objects of the Target System [page 114]
4. Step 4: Copy All Objects of the Source System into the Target System [page 114]
5. Step 5: Add All DB2 Subsystem Libraries to a PARMLIB Containing Definitions Required for APF [page 114]
6. Step 6: Alter the BSDS of the Target System [page 115]
7. Step 7: Change Entries of logcopy Data Sets in the BSDS of the Target System [page 115]
8. Step 8: Customize DB2 Modules Using DSNTIJUZ [page 115]
9. Step 9: Configure the Distributed Data Facility (DDF) [page 116]
10. Step 10: Start the Target System Using ACCESS(MAINT) [page 116]
11. Step 11: Update the DB2 Catalog Using CATMAINT UPDATE VCAT SWITCH [page 116]
12. Step 12: Stop and Restart the Target System [page 116]
13. Step 13: Create DSNTEP2 and DSNTEP4 Load Modules for the Target System [page 117]
14. Step 14: Alter All WLM Environments of Stored Procedures [page 117]
15. Step 15: Perform Post-Offline System Copy Actions (Optional) [page 117]
5.4.1 Step 1: Check the Source System and Stop it after
Successful Check
Procedure
1. Check the source system for active threads using the following DB2 command: DIS THD(*)
If there are active threads, stop all applications running against the source system.
2. Check the source system for authorized utilities using the following DB2 command: DIS UTIL(*)
The command shows the status of all utility jobs known to DB2. You should get the following message: NO
AUTHORIZED UTILITY FOUND FOR UTILID = *
If there are utilities, wait for their successful completion or terminate them.
3. Ensure that all DB2 objects of the source system are started in RW mode.
You can check this using the following DB2 command: DISPLAY DATABASE(*) SPACENAM(*) RES
The command displays all databases, table spaces, or indexes in a restricted status.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
112 PUBLIC Database-Specific System CopyYou should get the following message: NO DATABASES FOUND
In all other cases do not proceed. We recommend that you repair all databases, table spaces, or indexes
identified as restricted. For more information, see the command reference of Db2 for z/OS.
4. The source system must be stopped and restarted now in ACCESS(MAINT).
ACCESS(MAINT) prohibits access to any authorization IDs other than SYSADM, SYSOPR and SECADM.
5. Later in this workflow all WLM ENVIRONMENTs of DB2 procedures must be altered in the target system.
Identify all created procedures and WLM ENVIRONMENTs with the following SQL statement:
SELECT ''ALTER PROCEDURE '' CONCAT
SCHEMA CONCAT ''."'' CONCAT NAME CONCAT ''"''
CONCAT '' WLM ENVIRONMENT ''
CONCAT STRIP(WLM_ENVIRONMENT) CONCAT '';''
FROM SYSIBM.SYSROUTINES
WHERE ROUTINETYPE=''P'';
SELECT ''ALTER SPECIFIC FUNCTION '' CONCAT
SCHEMA CONCAT ''."'' CONCAT SPECIFICNAME CONCAT ''" ''
CONCAT '' WLM ENVIRONMENT ''
CONCAT STRIP(WLM_ENVIRONMENT) CONCAT '';''
FROM SYSIBM.SYSROUTINES
WHERE ROUTINETYPE=''F''
AND FENCED = ''Y'';
The result of this query should look like the following:
Note
This is only an excerpt from the result.
ALTER PROCEDURE DSNADM."ADMIN_TASK_LIST" WLM ENVIRONMENT D990_GENERAL;
ALTER PROCEDURE DSNADM."ADMIN_TASK_OUTPUT" WLM ENVIRONMENT D990_GENERAL;
ALTER PROCEDURE DSNADM."ADMIN_TASK_STATUS" WLM ENVIRONMENT D990_GENERAL;
ALTER PROCEDURE DSNADM."ADMIN_TASK_STATUS" WLM ENVIRONMENT D990_GENERAL;
A LTER PROCEDURE SYSPROC."DSNACICS" WLM ENVIRONMENT D128_GENERAL;
Keep the results of this query in a safe place.
6. Stop the source system again.
7. After the source system has completely terminated, print the contents of all source system boot strap
datasets using utility DSNJU004.
Carefully save the output. The values of START RBA and END RBA of all logcopy datasets are needed later
in this workflow.
Caution
Do not start the source system until all objects (boot strap datasets, LOGCOPY, VSAM clusters and
so on) are copied into the target system. Otherwise the target system might be highly inconsistent.
Therefore it is strongly recommended to prevent the source system from being started until step 4
[page 114] of this process flow has been completed successfully.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 1135.4.2 Step 2: Consider DB2 Procedures of the Target System
Consider the following cases:
● Homogeneous system copy of the source system is provided in an existing target system. In this case you
can skip step 2.
● Homogeneous system copy of the source system is provided in a nonexistent target system. In this case
customize and run a private copy of DSNTIJMV to update the DB2 PROCLIB.
5.4.3 Step 3: Delete All Obsolete Objects of the Target
System
Consider the following cases:
● Homogeneous system copy of the source system is provided in a target system that already exists.
In this case delete all obsolete bootstrap datasets, logcopy datasets, archives, VSAM clusters. Ensure that
all obsolete objects of the target system are deleted.
● Homogeneous system copy of the source system is provided in a non-existing target system.
In this case you can skip step 3. All necessary datasets are copied from the source system in step 4 [page
114] of this process flow.
5.4.4 Step 4: Copy All Objects of the Source System into the
Target System
1. Ensure that the source system is still stopped.
Otherwise boot strap datasets, logcopy datasets, VSAM clusters are allocated by the source
system and cannot be copied.
2. Customize and run a job using, for example, program ADRDSSU.
Use ADRSSU parameter RENUNC to rename all objects to reflect the high-level qualifiers of the target
system.
3. Now you can restart the source system without any risk of inconsistency in the target system.
5.4.5 Step 5: Add All DB2 Subsystem Libraries to a PARMLIB
Containing Definitions Required for APF
Consider the following cases:
● The target system was already up and running in the past, so that all definitions required for authorized
program facility (APF) already exist.
In this case you can skip step 5.
● The target system was never up and running.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
114 PUBLIC Database-Specific System CopyIn this case add all definitions required for APF to an appropriate PARMLIB and set APF. Otherwise the
target system cannot be started.
5.4.6 Step 6: Alter the BSDS of the Target System
Change VSAMCAT in the bootstrap data sets (BSDS) of the target system. Use the DSNJU003 utility in DB2 with
parameter NEWCAT VSAMCAT to reflect the new VSAMCAT high-level qualifier.
Repeat this step for each data sharing member BSDS of data sharing systems, .
5.4.7 Step 7: Change Entries of logcopy Data Sets in the
BSDS of the Target System
Use DB2 utility DSNJU003 to delete obsolete and invalid DSNAME entries using the DELETE DSNAME parameter.
In the same job you can define the name of the new logcopy data sets with the NEWLOG DSNAME parameter.
Carefully customize the STARTRBA and ENDRBA parameters using the values of the source system.
Repeat this step for each data sharing member BSDS of data sharing systems.
5.4.8 Step 8: Customize DB2 Modules Using DSNTIJUZ
For the target system you have to customize the DB2 data-only load module DSNHMCID, the application
defaults load module (DSNHDECP), and the subsystem parameter module using DSNTIJUZ.
At least change the following parameters:
● The name of the libraries identified in STEPLIB, SYSLIB
● SYSLMOD DD statements
● The ADMTPROC parameter, if the administrative task scheduler is used
● The CATALOG parameter
● The FCCOPYDDN parameter
● The IRLMPRC parameter
● The IRLMSID parameter
● The ARCPFX1 and ARCPFX2 parameters, if the target system is to run with archiving.
If the target system is to run without archiving, identified by parameter OFFLOAD=NO, the ARCPFX2 /
ARCPFX2 parameters must not be changed. However, for security reasons it is recommended to run the
target system with archiving.
Other parameters of the target system can be modified as requested by the owner of the subsystem.
Repeat this step for each data sharing member BSDS of data sharing systems.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 1155.4.9 Step 9: Configure the Distributed Data Facility (DDF)
Use the DSNJU003 stand-alone utility to change the bootstrap data sets (BSDS). Adjust LOCATION,
LUNAME,PORT, and RESPORT considering the new Distributed Data Facility (DDF) environment.
Repeat this step for each data sharing member BSDS of data sharing systems.
5.4.10 Step 10: Start the Target System Using
ACCESS(MAINT)
You must be able to start the target system with ACCESS(MAINT), otherwise the CATMAINT utility fails in the
next step [page 116] of this process flow.
If the target system does not start successfully, do not proceed with Step 11: Update the DB2 Catalog Using
CATMAINT UPDATE VCAT SWITCH [page 116].
For data sharing systems, start the first member and continue with Step 11: Update the DB2 Catalog Using
CATMAINT UPDATE VCAT SWITCH [page 116].
5.4.11 Step 11: Update the DB2 Catalog Using CATMAINT
UPDATE VCAT SWITCH
Use the CATMAINT utility with option VCAT SWITCH to provide the new high-level qualifier of the target system
in the DB2 catalog.
For data sharing systems, run this step with the first started member.
5.4.12 Step 12: Stop and Restart the Target System
Stop and restart the target system.
When the target system is restarted, you have to check the SYSLOG carefully for normal completion.
Caution
Do not proceed with the next step [page 117] if problems occur while the target system is being stopped or
restarted.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
116 PUBLIC Database-Specific System Copy5.4.13 Step 13: Create DSNTEP2 and DSNTEP4 Load Modules
for the Target System
Create, test, and run the DSNTEP2 and DSNTEP4 load modules. To be able to do this, you have to customize and
run DSNTEJ1L.
5.4.14 Step 14: Alter All WLM Environments of Stored
Procedures
Use
In step 1 [page 112] of this process flow, you ran a query to prepare all ALTER PROCEDURE statements for the
target system.
Now you have to customize the result of the query by changing the WLM ENVIRONMENT value for the WLM
ENVIRONMENT names of the target system.
Procedure
1. Ensure that the APPLICATION ENVIRONMENT NAMES and the appropriate PROCEDURE NAMES exist in the
DB2 PROCLIB and that the APPLICATION ENVIRONMENTS are activated.
2. Run all ALTER PROCEDURE commands in the target system using the DSNTEP2 program.
5.4.15 Step 15: Perform Post-Offline System Copy Actions
(Optional)
1. As all GRANTs of the source system are still valid, check them using SPUFI by executing the following
command: SELECT * FROM SYSIBM.SYSUERAUTH;
Maintain this table according to your needs.
2. Grant new users or revoke obsolete users.
3. If required, change the user authorizations of the target system.
The IBM Db2 catalog still contains the authorizations of the source system.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 1175.5 SAP ASE 16.0 Server-Specific Procedure
This section describes how to perform a homogeneous system copy of a SAP ASE 16.0 database by using the
load database dump method, or the attach database device method in an SAP environment. The
installer supports both methods.
Prerequisites
Before you start the system copy procedure, implement SAP Note 1612437 .
Context
The load database dump method and the attach database device method have the following
advantages compared to the R3load method:
● You can use an existing full database dump and optionally also transaction dumps.
● You can copy the complete database software and database devices (all files below /sybase/) to
the target system and use this copy to create the target system.
● These methods are faster than the database-independent method [page 47].
For more information about system copy with SAP ASE 16.0 as target database, see SAP Note 1697542 .
Procedure
1. Provide the database files required for the target system setup using one of the following ways:
○ Suspend write operations to the database devices of the source system database together with the
creation of a database manifest file (using SAP ASE 16.0 command quiesce database
_tag hold for external dump to ), copy all necessary
files to the target system, and enable the write operation again (using SAP ASE 16.0 command
quiesce database _tag release).
○ Create a backup (SAP ASE 16.0 command dump database).
2. Copy the files to the target system.
3. Run the installer to install the target system by choosing the following on the Welcome screen:
SAP ASE System Copy Target System Based on
Note
○ Choose the installation services in exactly the order they appear. For more information, see the
installation guide [page 22] for your SAP NetWeaver-based system on SAP ASE.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
118 PUBLIC Database-Specific System Copy○ On the installer screen SAP SystemDatabase, make sure that you select Homogeneous System
Copy (SAP ASE-specific: Attach database device or Load database dump).
○ The installer asks you if you want to use either an already existing SAP ASE installation on the
target system or the database software from the installation media.
○ Depending on the method chosen, you have to enter either the path to the database dump files or
the location of the database manifest file. The installer tries to find the database devices
mentioned in the manifest file automatically, otherwise it asks for the files during the installer
execution phase.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Database-Specific System Copy PUBLIC 1196 Copying Single Instances Only
If you want to copy single instances of your SAP system only, you can use one of the following procedures,
depending on your use case.
Caution
You cannot copy single product instances, usage types, or components!
Note
This system copy guide describes only the export of the source system in detail. For the installation of the
target system, you use the installation guide for the database and operating system platform of your
target system. This procedure describes only the additional system copy-specific steps for the target
system installation and refers for the remaining steps to the target system installation guide [page 22].
Copying the Primary Application Server Instance Only [page 121]
With this procedure, you can move a primary application server instance to a different host within your
system.
Copying the Database Only – Move Database Instance [page 121]
This section is about how to move a database instance to a different host within your system.
Depending on your database, you can perform the move using either database-specific methods or the
SAP standard method based on R3load .
Copying the Database Only – Refresh Database Instance [page 123]
With this procedure you can refresh an existing database instance - that is a new database instance is
installed - without having to copy the primary application server instance and to reinstall additional
applications servers. You can perform the refresh using either database-specific methods or the SAP
standard method based on R3load .
Copying the Database Only - Refresh Database Content [page 124]
Using the Refresh Database Content option in the installer you can refresh the content of an existing
database using a database backup without having to copy the primary application server instance, and
to reinstall additional applications servers. No new database instance is installed. The sections below
describe how to use the Refresh Database Content option for your database.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
120 PUBLIC Copying Single Instances Only6.1 Copying the Primary Application Server Instance Only
With this procedure, you can move a primary application server instance to a different host within your system.
Prerequisites
The ABAP central services instance (ASCS instance) is installed.
Procedure
1. Shut down all application servers.
2. Uninstall the old primary application server instance as described in the Additional Information section of
the installation guide .
3. On your target host, start the installer as described in Running the Installer [page 64] .
4. On the Welcome screen, navigate to the following folder according to the requirements of your target
system:
System Copy Target System Distributed System or High-Availability
System Based on Primary Application Server Instance .
5. After the installation has finished, restart all additional application server including the instance services.
6.2 Copying the Database Only – Move Database Instance
This section is about how to move a database instance to a different host within your system. Depending on
your database, you can perform the move using either database-specific methods or the SAP standard method
based on R3load .
Note
For Oracle Database you cannot use the database-independent method described in the Procedure below.
Instead, you must use the database specic method (see Oracle-Specific Procedure [page 90]) to copy or
restore your database in the target system.
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Copying Single Instances Only PUBLIC 121Context
“Move” means moving the database instance to a different host to refresh the database content. The
procedure below describes the database-independent method, which is not feasible for all databases. For using
database-specific methods, see Database-Specific System Copy [page 88].
If you only want to “refresh” the database content with the database instance staying on the same host, use
either the procedure described in Copying the Database Only – Refresh Database Instance [page 123] or the
procedure described in Copying the Database Only - Refresh Database Content [page 124]
For more information, see https://blogs.sap.com/2017/03/02/refresh-database-content-without-reinstalling-
the-database-or-kernel-for-abap-systems/
Note
● Consider the following:
○ The must not be changed.
○ When copying the database only, you cannot change to another database but need to perform a
database-homogeneous copy.
○ The old database instance cannot be uninstalled using the installer-based uninstall procedure. This
always deletes the current database of the system.
Procedure
1. On the source host, run the installer to perform the export in one of the following ways:
○ If you perform the export using R3load, on the Welcome screen, choose
System Copy Source System Based on AS ABAP Database Instance Export to
export the database.
○ If you perform the export using database-specific tools, you must start them manually.
2. On the target host, stop all SAP application server instances, but leave the ASCS instance running.
3. On the target system, run the installer and choose System Copy Target
System Based on AS ABAP Database Refresh or Move to install the database.
Note
Since the target database instance is to replace the source database, do not change the .
4. When the installer has completed the installation of the database, restart your system including all
instance services.
5. Shut down the old database instance.
6. SAP MaxDB only: Set up the xuser entries from the home directory of the user adm on each
application server as follows:
xuser -U -u , -d -n -S SAPR3 -t 0 -I 0
set
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
122 PUBLIC Copying Single Instances OnlyThe required keys and dbusers are as follows:
○ Key DEFAULT with dbuser SAP
○ Key c with dbuser control
○ Key w with dbuser superdba
Related Information
Running the Installer [page 64]
6.3 Copying the Database Only – Refresh Database
Instance
With this procedure you can refresh an existing database instance - that is a new database instance is installed
- without having to copy the primary application server instance and to reinstall additional applications servers.
You can perform the refresh using either database-specific methods or the SAP standard method based on
R3load .
Prerequisites
● The source system and the target system already exist.
● You must prepare the kernel media and the RDBMS media as described in section Preparing the Installation
Media in the installation guide [page 22].
Context
This procedure implies a “refresh of the database instance” using kernel and RDBMS media with the database
instance staying on the same host.
If you want to “move” the database instance to a different host, use the procedure described in Copying the
Database Only – Move Database Instance [page 121].
If you want to only refresh the database content using a database backup - that is without using kernel and
RDBMS media, and without installing a new database instance - use the procedure described in Copying the
Database Only - Refresh Database Content [page 124]
For more information, see https://blogs.sap.com/2017/03/02/refresh-database-content-without-reinstalling-
the-database-or-kernel-for-abap-systems/
System Copy for SAP Systems Based on the Application Server ABAP of SAP NetWeaver 7.3
EHP1 to 7.52 on UNIX
Copying Single Instances Only PUBLIC 123Procedure
1. On the source system, perform the export in one of the following ways:
○ If you perform the export using R3load, start the installer and on the Welcome screen choose
System Copy Source System Based on AS ABAP Database
Instance Export to export the database.
○ If you perform the export using database-specific tools, you must start them manually.
2. On the target host, stop all SAP application server instances, but leave the ASCS instance running.
3. Run the installer and choose