SAP on DB2 Universal Database for OS/390 and z/OS: Multiple Components in One Database (MCOD)

Chapter 3. MCOD installation and merge using SAP tools 33

3.3.1 SAP Basis Releases 4.6C and 4.6D

We describe here how to merge an SAP component based on SAP Basis

Release 4.6x into an MCOD landscape. In particular, we show how to upgrade

both R3SETUP and its templates.

Description of the scenario

In this scenario, we have the MCOD landscape created in the previous phase

with two components: YEL and WHT. Now, we want to merge into that MCOD

landscape the SAP component BLU based on Basis Release 4.6C. See

Figure 3-4 on page 34.

Figure 3-3 Merging components with SAP tools: Initial configuration

The merge consists of the following steps:

1. Export the source system (in our case, BLU).

2. Set up the target application server (in our case, GRE).

3. Load the exported data into the target database.

4. Post-installation steps.

YEL (4.6D)

Linux 9

DB2-SAP

Database

SC42

ICLI (6040)

DB7X

Linux 7

DB7XU

(a)

ICLI Client

WHT (6.20)

ICLI (6020)

ICLI Client

DB2-SAP

Database

SAPWHT

(b)

DB2-SAP

Database

BLU (4.6C)

ICLI Client

DB7S

ICLI (6010)

SAPBLU

34 SAP on DB2 UDB for OS/390 and z/OS: Multiple Components in One Database (MCOD)

Figure 3-4 shows the final configuration after the merge. We now have one

MCOD landscape consisting of three SAP components: YEL, WHT, and GRE.

Note that the three components are based on different SAP Basis Releases.

Figure 3-4 Merging components with SAP tools: Final configuration

Export the source system

The export has to be performed using standard 4.6D migration tools. For details,

refer to the guide

SAP R/3 Homogeneous System Copy, Release 4.6C SR2,

material number 51013678

,

available on the SAP Service Marketplace quick link

INSTGUIDES at:

http://service.sap.com/instguides

The steps are as follows:

1. Set up the export and work directory.

2. Go to the work directory and call:

/<CDMOUNT>/UNIX/INSTTOOL.SH

EXPORT / IMPORT

YEL (4.6D)

Linux 9

DB2-SAP

Database

SC42

ICLI (6040)

DB7X

Linux 7

DB7XU

(a)

ICLI Client

WHT (6.20)

ICLI (6020)

ICLI Client

DB2-SAP

Database

SAPWHT

(b)

DB2-SAP

Database

BLU (4.6C)

ICLI Client

DB7S

ICLI (6010)

SAPBLU

DB2-SAP

Database

SAPGRE

(c)

GRE (4.6C)

ICLI (6030)

ICLI Client

Chapter 3. MCOD installation and merge using SAP tools 35

3. Only Linux for zSeries:

a. Retrieve the file DBEXPORT.R3S from sapservX.

b. Obtain latest R3SETUP patch from SAP Service Marketplace quick link

PATCHES at:

http://service.sap.com/patches

4. Shut down the source SAP system:

stopsap r3

5. Start R3SETUP:

./R3SETUP -f DBEXPORT.R3S

6. Specify all parameters as usual.

7. Continue and finish the export as usual.

Set up the target application server

The following list describes how to set up the target application server.

The target application server is installed as follows:

1. Set up the installation directory.

2. Go to the installation directory and execute:

/<CDMOUNT>/UNIX/INSTTOOL.SH

3. Copy MCOD-specific R3SETUP templates from sapservX to the installation

directory. For details, see

DB2/390: MCOD installation tools,

SAP Note

580665.

Important: It is highly recommended when migrating with SAP tools that you

reinstall the SAP instance or instances using R3SETUP, even if you are

reusing the same application server hardware with SAP instances already

installed. This ensures that all required MCOD settings are correctly

implemented in the environment and instance profile variables, as well as

plans bound and grants executed.

To preserve any changes you have made in SAP profiles, take a copy of the

files from /usr/sap/<SID>/system/profile, as well as the .dbenv_xxxx files from

the $HOME directory of <sid>adm user, prior to starting the install. Upon

completion of the migration, you will need to integrate the parameters in the

new instance and those in the files you have saved. A complete backup of the

application server is highly recommended prior to reinstalling to allow a point

of return in case of unforeseen error.

36 SAP on DB2 UDB for OS/390 and z/OS: Multiple Components in One Database (MCOD)

4. Retrieve the latest 4.6D R3SETUP patch from SAP Service Marketplace

quick link PATCHES, copy it to the installation directory, and execute:

./R3SETUP -v

Check that the output is VERSION: 20020504 or later.

5. Modify MCODCE_UNIX_db2.BASE.R3S:

a. Specify/add CREATOR=<SCHEMA> in section

[DBCOMMONPARAMETERS_IND_xxx].

b. Specify as 1_LABEL (in most cases located in section

[CDSERVERKERNELBASE_IND_xxx]) the content of LABEL.ASC of the

Kernel CD, for example:

DB2forOS/390:BASIS:46D:KERNEL:Kernel:CD51017309

6. Start R3SETUP:

./R3SETUP -f MCODCE_UNIX_db2.BASE.R3S

7. Specify the input as usual.

8. Check BIND and GRANT JCLs. The plan name should be F<SID>46D.

9. Continue and finish the installation.

10.Modify the plan name (from step 8) and, optionally, the port number in the

ICLI procedure or shell script. Start the ICLI server on the host.

11.Apply the latest 4.6D Kernel patches from the SAP Service Marketplace quick

link PATCHES, in particular for the DBSL library.

12.Log on as <sid>adm and check whether the connection works using:

R3trans -x

13.Check that DBS_DB2_SCHEMA is set to <SCHEMA>, using the echo

command.

14.Specify dbs/db2/schema=<SCHEMA> in the profile DEFAULT.PFL.

Load data into the target database

To load the exported SAP component into the target database, proceed as

follows:

1. Go to the installation directory.

2. Modify MCODMIG_UNIX_db2.BASE.R3S:

Specify CREATOR=<SCHEMA> in one of the following sections:

– [DBCOMMONPARAMETERS_ADD_IND_DB2] (non-z/OS)

– [DBCOMMONPARAMETERS_ADD_IBM390_DB2] (z/OS)