2019-09-23 129352

129352 - Homogeneous system copy with SAP MaxDB

Version 74 Type SAP Note
Language English Master Language German
Priority Recommendations / Additional Info Category Installation information
Release Status Released for Customer Released On 04.07.2017
Component BC-DB-SDB-INS ( Installation with MaxDB )

Please find the original document at https://launchpad.support.sap.com/#/notes/ 129352

Symptom

This note is used as an addition for the notes "INST: X.XX R/3 Inst. -
Homogeneous System Copy"

You want to import a backup of an SAP MaxDB database into another SAP MaxDB
database.

If you want to carry out a system copy for an SAP liveCache database, see SAP
Notes 457425 and 632357.
If you want to carry out a system copy for an SAP Content Server, see SAP Notes
962019 and 389366.

Other Terms

Restore data, Install Serverdb, Instance Install, DBMGUI, system copy, -8003,
RTE header size

Reason and Prerequisites

To generate a database copy, import the backup of a source system into the
target system.
To import a backup from another system, a normal recovery is not sufficient. You
must perform an Instance Install or a Recovery with Initialization.

Prerequisites

• You can only import backups of the database instance into systems where the
processor works with the same byte assortment (Little Endian -> Little
Endian; Big Endian -> Big Endian). SAP Note 552464 describes the permitted
combinations. The current SAP MaxDB documentation provides a complete matrix
for this. To find the documentation, use SAP Note 767598; for more
information, see the glossary entry System Copy.
You can import backups of a 32-bit system on a 64-bit system and vice versa.
• As of SAP MaxDB Version 7.5, backups can also be imported into target
systems in which a higher SAP MaxDB version is running.

Explanation

You can import a backup of database version 7.5.00.50 into a target system with
all of the available SAP MaxDB versions that are higher than or equal to
7.5.00.50 (for example, 7.6, 7.7, and so on).

In the case of database versions < 7.5, the first three digits of the MaxDB
version must correspond in the source system and target system (that is, they

© 2019 SAP SE or an SAP affiliate company. All rights reserved 1 of 8

2019-09-23 129352

must correspond up to build level).

A backup of database version 7.3.00.50 can be implemented in a target system

with database version 7.3.00.60. If you want to import this backup into target
systems with database version 7.4, 7.5, or 7.6 and so on, additional steps are
required.

For a description of the additional steps for a system copy with a database
version upgrade from 7.3 to 7.5 by means of a backup/restore procedure, see SAP
Note 2143316.

Log backups <= 7.5 can be restored only in database versions <= 7.6. These log
backups CANNOT be restored in database versions >= 7.7.

Tools

You use Database Studio or - for really old database versions - the Database
Manager (GUI) for database administration.

• Database Studio
As of database version 7.5, the Database Studio is used for database
administration. We recommend that you use the latest Database Studio Version
7.9.
• Database Manager GUI (DBMGUI)
Database versions below 7.5 can be managed with the DBMGUI. The management
functionality of the DBMGUI is restricted, since no new developments have
been made there since database version 7.7. As of database version 7.8, only
Database Studio can be used. The first three places of the Database Manager
GUI version should be higher than or equal to the version of the database
core. If they are equal, the last two numbers (build level) of the DBMGUI
version can be lower than the numbers of the database core. As of Version
7.6, the third place of the DBMGUI version can also be lower than the
version of the database core.

Source system: Database versions 7.2 and 7.3

Either you generated a consistent data backup (migration) on the source system or
subsequent log backups or consistent incremental backups are available on the
source system.

Source system: Database version >= 7.4

As of database version 7.4, data backups always contain a transaction-consistent

data status. You do not need the migration option to create a backup.

Target system:

A backup template that you can use to import the backup(s) was created in the
target system.

When you define the backup template, keep in mind the same block size that was
also used in the source system template. During the export, the following error
message may occur:
127,RTE header size <current> instead of <expected> bytes on medium <medium_path>

The target system can be smaller or larger than the source system.

Target system size: Database versions 7.2 and 7.3

The minimum target system size is as large as the highest assigned page number

© 2019 SAP SE or an SAP affiliate company. All rights reserved 2 of 8

2019-09-23 129352

in the source system (LAST DATA PNO). You can determine this value in the source
system using the following call (Command Prompt or UNIX shell, one line):

dbmcli -d <database_name> -u <dbm_operator>,<password> -n <database_server> -uSQL sapr3,sap

sql_execute "select maxdatapageno from sysdba.serverdbstatistics"

You can possibly reduce this value by a restart (release of temporary pages).

Target system size: Database version >= 7.4

The minimum target system size is as large as the number of assigned permanent
pages in the source system. Configure the target system in such a way that it
does not become full after the first restart. You can determine the number of
assigned permanent data pages in the source system using the following call:

• dbmcli -d <database_name> -u <dbm_operator>,<password> -n <database_server> -uSQL sapr3 ,sap

sql_execute 'select "Perm Data (Pages)" from info_state'

• As of database version 7.5:

dbmcli -d <database_name> -u <dbm_operator>,<password> -n <database_server> info state

• As of database version 7.6:

As of database version 7.6, you can reduce the database online by deleting
data volumes.

If you do not wish to create the migration backup physically, you can use remote
pipes for transporting the backup. For more information, see SAP Note 489615.

Solution

Carry out the following steps for the system copy:

Source system:

Create a complete system backup:

• Database version >= 7.5

Database Studio: Administration Tasks -> Backup

• Database version < 7.5

Database Manager GUI: DBMGUI -> Backup -> Backup Wizard -> Complete
If no consistent backup (for Migration) is generated with Version 7.2 or 7.3,
you must create a log backup or a consistent incremental backup.

Target system:

Target system: Software

If you are rebuilding the system from scratch (in other words, there is no
software installed), use R3INST, R3Setup, or SAPInst to import the SAP instance
software and the database software. After you have done this, you can terminate
the installation program (if supported).

Target system: Restore

Before the restore, you must initialize the target database. This initialization
formats the log area. Data volumes are only formatted, if they are not
configured as raw devices and are not available in the configured size.

• Database version < 7.5

© 2019 SAP SE or an SAP affiliate company. All rights reserved 3 of 8

2019-09-23 129352

Database Manager GUI: Recovery Wizard with Recovery with Initialization ...
The documentation describes how to use this wizard. SAP Note 767598 contains
the links you need to access the documentation. Open the glossary entry
Database Manager (Database Manager, section Restoring -> Restoring After Initializing a
Database Instance).
If you use Database Manager GUI Version 7.5 and databases of Versions < 7.5,
read SAP Note 864650.
Database Manager GUI First Edition:
• Choose Instance -> Install.
Database name: Name of target database
• If the database instance already exists, choose Reinstall in the dialog
box that follows. If the database instance does not yet exist, you must
select the software version (according to the version of the source
system).
• DBM user (for example, CONTROL) and database system administrator (for
example, SUPERDBA)
• If the database is not in the OFFLINE operating state, you must confirm
the stop.
• If you want to transfer the current database parameters, select Use
current parameters in the window that follows. Otherwise, you can pass the
parameters of the source system from the backup or assign the default
values to the parameters.
• Check database parameters and correct if necessary
• Check the volumes specification and correct if necessary
• Choose Restore Instance.
• Check your specifications and choose Install.
The installation performs the steps Start instance and Initialize configuration.
Next, you have to register the newly installed database instance in the
Database Manager GUI.
To import the data backup, you must proceed as follows in the Database
Manager GUI (make sure that the desired database is selected).
• Choose Recovery -> Database. Under no circumstances should you restart
before the recovery - if you do, the following error occurs after the
restore: -8003: log and data must be compatible.
• Choose Restore Medium.
• Select the backup template.
• Start the restore.
• After importing the data backup, you can either import further backups
or choose Restart.
If you use backup tools of other vendors and a Database Manager GUI
version that does not yet support backup tools of other vendors during
the restore, proceed as described in SAP Note 387583.
• Database version >= 7.5
Database Studio (the database already exists but should be reinitialized):
Access takes place via Administration Tasks -> Recovery.
○

Choose Recover a Medium and select Initialize Database before Recovery for a
○

system copy.
Select the backup copy, continue with Next, and then start the recovery
○

with Start.
SAP Note 767598 contains the links you need to access the
documentation. Choose the glossary entry Restore.

Database Studio (no database exists yet):

• In Database Studio, right-click the server on which the new database

© 2019 SAP SE or an SAP affiliate company. All rights reserved 4 of 8

2019-09-23 129352

should be installed. Choose Administration Tasks -> Create Database.

• Set the radio button to advanced mode and choose Next.
• Specify a database name and choose Next.
• Select the software for the required installation and choose Next.
• Choose Advanced Options or skip this with Next if appropriate.
• Set the password of the DBM user (DBM operator); ideally, use the
password that is also used in the source system.
• The database parameters can be copied from an existing database using
Copy parameters from existing database OR restored from a backup of the
original system using Restore parameters from a backup. To do this, create a
backup template that references the backup.
• Adjust the database parameters for the new database (particularly the
path names) and choose Next.
• Select the volumes for the new database and choose Next.
• Choose Create database for recovery and then choose Start.
• Follow the instructions of the recovery wizard that starts when you
choose Recovery.
• Note that once the database has started and the operating state ONLINE
has been reached, no further log backups can be implemented. In other
words, the recovery process ends when the database is started.

Target system: Loading of system tables

• Database version <= 7.5

dbmcli -d <database_name> -u <dbm_operator>,<password> load_systab -u
<database_system_administrator>,<password> -ud <domain_user_password>
For example:
dbmcli -d N01 -u control,control load_systab -u superdba,admin -ud domain

• Database version >= 7.6

dbmcli -d <database_name> -u <dbm_operator>,<password> load_systab -u
<database_system_administrator>,<password>

• Database version >= 7.7

As of database version 7.7, the DBM command db_online sometimes automatically
executes the DBM command load_systab. However, since this procedure is not
reliable for all possible situations, perform the following steps, too (they
might be redundant but will not cause any harm).
Make the database system administrator known with the following DBM command.
This is required if a database has been completely rebuilt.
dbmcli -d <database_name> -u <dbm_operator>,<password> user_sysdba
<database_system_administrator>,<password_from_backup>
(SAP Note 1090087)
Example:
dbmcli -d P01 -u control,control user_sysdba superdba,<password_from_backup>
If the recovery (with initialization) took place in a previously already
existent database, the database system administrator (for example, superdba)
might have a different password in the source system and target system.
To adjust the password to the previous password of the target system again,
execute the following command:
dbmcli -d <database_name> -u <dbm_operator>,<password> user_put
<database_system_administrator> password=<password_from_target_system>
Example:
dbmcli -d P01 -u control,control user_put superdba password=<password_from_target_system>
The system tables can then be loaded with the DBM command

© 2019 SAP SE or an SAP affiliate company. All rights reserved 5 of 8

2019-09-23 129352

load_systab or with Database Studio:

dbmcli -d <database_name> -u <dbm_operator>,<password> load_systab
If the name of the database user who owns the application data is
SAP<SAPSID>, you can rename the user SAP<NEWSID>
(<NEWSID>=<new_database_name>). To do this, use the following command:
dbmcli -d <new_database_name> -u <dbm_operator>,<password> -uSQL
<database_system_administrator>,<password> sql_execute rename user SAP<SAPSID> to
SAP<NEWSID>
Then, adjust the XUSER entries for the central instance and for all
application servers (as desribed in SAP Note 39439).
In the case of MCOD systems, you can perform this step for each SAP
instance.
If you cannot or do not want to rename the user, you can set the profile
parameter dbs/ada/schema as of SAP Release 6.20.
dbs/ada/schema=SAP<OLDSID>
This is especially applicable if you copy a system that was migrated from an
earlier SAP release and the user is still SAPR3:
dbs/ada/schema=SAPR3

Target system: Deletion of table entries

After the restore, delete all entries from the following tables, so that the
Computing Center Management System (CCMS) in the newly structured system does
not display any actions (for example, backups and UPDATE STATISTICS runs) from
the original system:
CNHIST, CNREPRT, CNMEDIA, DBSTATHADA, DBSTATIHADA, DBSTATIADA, DBSTATTADA,
SDBAADAUPD
To do this, you can execute the script attached to this SAP Note.
Important: You must adjust the XUSER entries before you run the script.
Use the following command:
sqlcli -U DEFAULT -f -i initialize_ccms_tables.sql

Other Components

Component Description

BC-DB-SDB MaxDB

This document refers to

SAP
Title
Note/KBA

962019 System Copy of SAP MaxDB Content Server Database

893506 Parameter change with change from HP-UX PA-RISC to IPF

873286 Unloading/loading SQL optimization statistics data

© 2019 SAP SE or an SAP affiliate company. All rights reserved 6 of 8

2019-09-23 129352
86859 INST: 4.0A/B R/3 Inst. - Homogeneous System Copy

864650 Homogeneous system copy with DBMGUI 7.5

767598 Available SAP MaxDB documentation

632357 Backup of data from liveCache for SCM 4.0 and higher SCM releases

604680 Renaming an SAP DB, SAP MaxDB, or SAP liveCache instance

552464 What is Big Endian / Little Endian? What Endian do I have?

489615 SAP DB or liveCache system copies via remote pipe

39439 XUSER entries for SAP MaxDB

389366 Relocation of documents

387583 SAP DB : Use of external backup IDs with dbmcli

Homogeneous system copy: From SAP DB Version 7.3 with backup/recovery to SAP MaxDB
2143316
Version 7.6

1619726 FAQ: SAP MaxDB Content Server

1090087 DBM command db_online sets database despite error message ONLINE

1030857 Report for additional update after system copy

1020175 FAQ: SAP MaxDB installation, upgrade or applying a patch.

1014782 FAQ: SAP MaxDB system copy

1013441 Upgrade required: Advantages for MaxDB on 64-bit platforms

101215 INST: 3.1I R/3 Inst. - Homogeneous System Copy

This document is referenced by

SAP
Title
Note/KBA

632357 Backup of data from liveCache for SCM 4.0 and higher SCM releases

604680 Renaming an SAP DB, SAP MaxDB, or SAP liveCache instance

962019 System Copy of SAP MaxDB Content Server Database

767598 Available SAP MaxDB documentation

1619726 FAQ: SAP MaxDB Content Server

1020175 FAQ: SAP MaxDB installation, upgrade or applying a patch.

© 2019 SAP SE or an SAP affiliate company. All rights reserved 7 of 8

2019-09-23 129352
1090087 DBM command db_online sets database despite error message ONLINE

39439 XUSER entries for SAP MaxDB

1030857 Report for additional update after system copy

2081702 Problems after recovery with initialization

552464 What is Big Endian / Little Endian? What Endian do I have?

Homogeneous system copy: From SAP DB Version 7.3 with backup/recovery to SAP MaxDB
2143316
Version 7.6

873286 Unloading/loading SQL optimization statistics data

1014782 FAQ: SAP MaxDB system copy

86859 INST: 4.0A/B R/3 Inst. - Homogeneous System Copy

389366 Relocation of documents

1013441 Upgrade required: Advantages for MaxDB on 64-bit platforms

893506 Parameter change with change from HP-UX PA-RISC to IPF

864650 Homogeneous system copy with DBMGUI 7.5

101215 INST: 3.1I R/3 Inst. - Homogeneous System Copy

489615 SAP DB or liveCache system copies via remote pipe

387583 SAP DB : Use of external backup IDs with dbmcli

Attachments

File Name File Size Mime Type

initialize_ccms_tables.zip 1 application/x-zip-compressed

© 2019 SAP SE or an SAP affiliate company. All rights reserved 8 of 8