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 |
|---|---|
| 1 | Prerequisites |
| 1.1 | Run FULL online backup in Source system before export and also backup File system of source system before export. |
| 1.2 | SIDADM and ORASID – create user for this, mention the users should belong to ‘sapsys’ and ‘dba’ group. |
| 1.3 | Install 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 |
| 2 | Preparation |
| 2.1 | General Techinical preparation |
| 2.2 | Before you start a system copy, check the minimum kernel patch level required by the support package level of the source system. |
| 2.3 | Call 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.4 | Make 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.5 | If 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.6 | Check 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.7 | Before you run the export and after you have performed several checks, delete QCM tables on the source system. |
| 2.8 | Call 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.9 | To avoid stopping the database due to a log directory being full, make sure that the log backup is enabled during the import. |
| 2.10 | Check the requirment and users for export |
| 2.11 | Create Migration key |
| 3 | Database Independent System Copy |
| 3.1 | System Copy Procedure |
| 3.2 | Generating DDL Statements |
| 3.3 | Preparing the Table Split(Optional) |
| 3.4 | Preparing Export and Import |
| 3.5 | Running the Software Provisioning Manager to Perform the Export |
| 3.6 | Montoring R3load and Jload |
| 3.7 | Setting Up the Target System |
| 3.8 | Transferring the Export Files to the Target Host |
| 3.9 | Installing the Target System |
| 4 | Follow-Up Activities |
| 4.1 | Performing Follow-Up Activities in the Source System |
| 4.2 | Performing Follow-Up Activities in the Target System |
| 4.3 | Installing the License Key |
| 4.4 | SAP Solution Manager: Connection Between System Landscape Directory and Landscape Management Database |
| 4.5 | Activities at Operating System Level-Target system |
| 4.6 | Activities at Database Level |
| 4.7 | Activities at SAP System Level |
| 4.8 | Checking the Target System |
| 7.2.4.1 | General Follow-Up Activities |
| 7.2.41.1 | Configuration Steps for the SAP Java Connector |
| 7.2.4.1.2 | Generating Public-Key Certificates |
| 7.2.4.2.1 | AS Java: Adobe Document Services |
| 7.2.4.2.5 | Enterprise Services Repository: Connecting to the SLD |
| 7.2.4.2.6 | Process Integration (PI) |
| 7.2.4.6.1 | System Landscape Directory |
| 7.2.4.2.6.2 | PI: Integration Server |
| 7.2.4.2.6.3 | PI: Changes in the Exchange Profile |
| 7.2.4.2.6.4 | PI: Refresh Caches |
| 7.2.4.2.6.5 | PI: Switching Addresses |
| 7.2.4.2.6.6 | PI: Connection Checks |
Reference SNOTE & Link:
SNOTE: 1738258, 82478 - SAP system OS/DB migration,1345600 - System Copy GuideLines for XI & 1680045 - Release Note for Software Provisioning Manager 1.0 SP05
Link
https://websmp105.sap-ag.de/~sapidb/011000358700000877172012E
http://scn.sap.com/docs/DOC-8324
http://service.sap.com/sltoolsetSoftware Logistics Toolset 1.0DocumentationSoftware
Help from SAP : If you have problems during the system copy, create a customer message using the application area BC-INS-MIG.
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.