Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
Brindavan_M
Contributor
0 Kudos
3,702

SAP Heterogeneous system copy-Plan for PI 7.1

(AIX to SUSE Linux OS)

Summary:-

This document contain only the plan for doing heterogeneous system copy database independent method. form AIX to Linux Operating system  using SAP Software provisional manager tool. This tool can be downloaded in service market place.

Created by: Brindavan Mookaiah

Designation: SAP BASIS Consultant



Table of Content


1) Software..............................................................................................................

2) Prerequisites.........................................................................................................

3) Preparation...........................................................................................................

4) Database Independent System Copy.......................................................................

5) Follow-Up Activities................................................................................................

Step 1


Software need to be download

1) Software provisional manager 1.0

2) java components

3) kernel

4) JDK


S/NO                                                                    Heterogeneous system copy-Plan
1Prerequisites
1.1Run FULL online backup in Source system before export and also backup File system of source system before export.
1.2SIDADM and ORASID – create user for this, mention the users should belong to ‘sapsys’ and ‘dba’ group.
1.3Install JDK:
1.4

Processing Steps of a System Copy (Oracle only)

With the settings in the property file listed in the examples above and an Oracle database as source and target database, the following prerequisites must be fulfilled:

The following directories must exist on the export host (parameter: exportDirs):

\temp\export_dump\ABAP\DATA

\temp\export_dump\ABAP\DB

\temp\export_dump\ABAP\DB\ORA

The \temp\export_dump\ABAP\DATA directory must contain the STR files generated by R3ldctl.

The \temp\export_dump\ABAP\DB directory must contain the DDL<DBTYPE>.TPL files generated by R3ldctl.

The \temp\export_dump\ABAP\DB\ORA directory must contain the EXT files generated by R3szchk.

The following directories must exist on the import host (parameter: importDirs):

/install_dir/export_dump/ABAP/DATA

/install_dir/export_dump/ABAP/DB

/install_dir/export_dump/ABAP/DB/ORA

2Preparation
2.1General Techinical preparation
2.2Before you start a system copy, check the minimum kernel patch level required by the support package level of the source system.
2.3Call transaction SM13(Check if canceled or pending update requests exist in the system. If canceled or pending updates exist, you must update these again or delete them from all clients)
2.4Make sure that the tables TATGPC and TATGPCA are empty. To do so, use your database utility and delete the contents of these tables with the following statements:DELETE from TATGPCDELETE from TATGPCA
2.5If the tables are not empty and you do not delete the contents of these tables you encounter problems while importing the data to your target system because of non-NULL capable fields in these tables.
2.6Check if table VBDATA contains any entries. If there are entries, update or delete the corresponding update requests. check whether this action was successful, call transaction SE16 for table VBDATA.
2.7Before you run the export and after you have performed several checks, delete QCM tables on the source system.
2.8Call T-code SE14 Before you delete the QCM tables, The tables are consistent – no restart log or conversion procedure termination must be displayed.Choose ExtrasInvalid temp. table,Mark the tables and delete them.
2.9To avoid stopping the database due to a log directory being full, make sure that the log backup is enabled during the import.
2.10Check the requirment  and users for export
2.11Create Migration key

3Database Independent System Copy
3.1System Copy Procedure
3.2Generating DDL Statements
3.3Preparing the Table Split(Optional)
3.4Preparing Export and Import
3.5Running the Software Provisioning Manager to Perform the Export
3.6Montoring R3load and Jload
3.7Setting Up the Target System
3.8Transferring the Export Files to the Target Host
3.9Installing the Target System

4Follow-Up Activities
4.1Performing Follow-Up Activities in the Source System
4.2Performing Follow-Up Activities in the Target System
4.3Installing the License Key
4.4SAP Solution Manager: Connection Between System Landscape Directory and Landscape Management Database
4.5Activities at Operating System Level-Target system
4.6Activities at Database Level
4.7Activities at SAP System Level
4.8Checking the Target System
7.2.4.1General Follow-Up Activities
7.2.41.1Configuration Steps for the SAP Java Connector
7.2.4.1.2Generating Public-Key Certificates
7.2.4.2.1AS Java: Adobe Document Services
7.2.4.2.5Enterprise Services Repository: Connecting to the SLD
7.2.4.2.6Process Integration (PI)
7.2.4.6.1System Landscape Directory
7.2.4.2.6.2PI: Integration Server
7.2.4.2.6.3PI: Changes in the Exchange Profile
7.2.4.2.6.4PI: Refresh Caches
7.2.4.2.6.5PI: Switching Addresses
7.2.4.2.6.6

PI: Connection Checks

Reference SNOTE

SNOTE: 1738258, 82478 - SAP system OS/DB migration,1345600 - System Copy GuideLines for XI &   1680045 - Release Note for Software Provisioning Manager 1.0 SP05

Note : Download the documnet from SAP while doing any installation, migration and upgarde. Also touch with SAP before doing any migration,upgarde and new installation  of SAP appliaction to get their suggestion & recommendation.  Please find the following link https://websmp201.sap-ag.de/instguides to download the installation guide,upgrade or migration. You need the OSS user login-ID and password.

Every SAP customer or partner is issued a S-User, in order to login to the SAP Service Marketplace, you have to hit the URL: www.service.sap.com

In order to login to the SAP Support Portal, you will need your login credentials i.e.:

• S-User

• Password

To download any available version of SAP Sourcing, you should follow the following path. First go to Software Downloads (in case that is not already your landing page). Afterwards perform the following path: Installations and Upgrades --> A-Z Index

Please find the screen shot below to download the guide.

7 Comments
Labels in this area