Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

AIM: OS/DB migration of SAP PI 7.0 

Platform:  Source system - OS : AS-400 (IBM i-Series) ; DB: DB2 

   Target System - OS: MS Windows 2008 Enterprise Server(x64) ; DB : MS SQL 2008 (x64)

Challenges:

There will be certain challenges in accomplishing the task, few are addressed below:

  1. SAP recommends presence of an OS/DB migration certified consultant to accomplish a migration project, if not then SAP will no longer provide any support for the new target system and any support from SAP will be billed for the purpose.
  2. Migration Key will be required from SAP to perform the task.
  3. Migration check from SAP is must before we start the project.
  4.  Time factor is required to be taken into consideration.
  5. Resources required for test migration.

Architecting the Target System:

 The design for the target system would be planned as part of the assessment phase includes:

  1. Hardware and networking requirements.
  2.  Database layout, sizing, and storage capacity goals — all permanent and temporary storage requirements supposed to be addressed as part of the overall migration strategy.
  3.  Database management issues (extents, tables, and physical layouts).
  4.  Load balancing requirements.
  5. Information lifecycle management requirements (back-up, recovery, and archiving) 

Prerequisites:

Below are listed the general prerequisites for heterogeneous system copy (which we will be following to accomplish the OS/DB migration):

  1. It is mandatory to get an SAP OS/DB Migration Check performed (SAP charges for this, SAP Note-560499).
  2. Complete backup of Source system (including full DB backup being in consistent state).
  3. Resources should be allocated (Hardware and Software).
  4. Download and apply the latest Kernel patch on the source system.
  5. Migration Tool kit or SAPInst after 6.20(Included with Installation package after 6.0 releases). This tool calls other programs: R3LOAD, R3LDCTL, and R3SZCHK.
    Migration Key will be required from SAP to perform the task. This can be generated via SAPNet http://service.sap.com/migrationkey). For test migration there is no fee but for migrating Production system SAP might charge.

Migration Steps:
The migration involves 5 major steps and their related sub-steps.

    1. Prepare the source system

    2. Export of the source system database

    3. Prepare the target system

    4. Import the database into the target system

    5. Post-migration activities

 Performing Migration (Steps):

We will proceed through below activities to perform the migration (first in test environment):

  1. Download the SAP installation media (Installation master, Java )
  2. Install Migration tool kit (SAPInst from Netweaver 7.0) in both Source and target system.
  3. Execute pending updates, if any.  Delete any canceled updates. Check for pending or cancelled requests in the system. If canceled or pending updates exist, you must update these again, or delete them from all clients. You can find out whether canceled or pending updates exist by checking if table VBDATA contains any entries.
  4. Delete the QCM tables, before the export; delete QCM tables from your system. Before deleting always check:
    1. That the tables are consistent: no restart log or conversion procedure termination must be displayed.
    2. That the data of the original table can be read.
    3. If application programs that use the affected original table do not run correctly, do not delete the QCM table, yet.

Delete QCM tables from your system as follows:

Call transaction *SE14 =>*Choose Extras Invalid temp. Table 

All QCM tables that can be deleted are displayed. Mark the tables and delete them.

   5.  Delete all entries from tables TATGPC and TATGPCA, Check to make sure that the tables TATGPC and TATGPCA are empty before the export of the source system, To do so, use your          database utility and delete the contents of these tables with the following statements:

DELETE from TATGPC

DELETE from TATGPCA

Normally both tables are empty. If you do not delete the contents of these tables you will encounter problems while importing the data to your target system because of non NULL capable fields in these tables.

  6. Update the latest versions of R3load, R3ldctl, and R3czchk in the Kernel directory

 The SAP Migration process uses the following tools. Update these tools to the latest available versions before starting the migration process:

 R3load - Unloads/loads ABAP table data from/into the database

 R3ldctl - Unloads ABAP dictionary structures from the database

        R3czchk - Computes size of ABAP tables and indexes for the target database and computes the ABAP related size for the target database.

   7.  Update the database parameters for sessions and processes. Update the database parameters for sessions and processes on the source system as per SAP recommendations. These are the factors which affect the data export from the source system.

   8.  Increase the table space for PSAPTEMP to avoid any unloads terminations during the export process. PSAPTEMP is the database storage unit that is used for the sorting. R3load exports data in the primary key order. More temporary databases disk space is required for sorting.

   9.  Perform the complete database backup to safeguard the changes made for the export preparation. Regular backup methods are followed.

  10. Run the program SMIGR_CREATE_DDL as batch job to generate DDL statement. Run the SMIGR_CREATE_DDL program as the batch job in the background, a mandatory step before exporting the data from the source system. This program allows the copying of database objects that do not correspond to SAP standards. These objects include partitioned (fragmented) tables and bitmap indexes. Special '<TABART>.SQL' files are generated for these objects. These files contain 'native DDL' (create) statements and can be analyzed by R3load.

  11.Export the database from the source system, to export the source database from AS/400 you have to sign on as user <SID>OFR instead of QSECOFR.

11.1: Prepare a Windows system and create a user as SAPINST with administrator rights and login    with the same.

11.2: Install TMKSVR in windows system. The TMKSVR is the interface between System i and Windows for the installation with SAPinst. SAPinst is running on Windows, but has to install the product on System i. This means that all actions required for System i are initiated remotely on Windows but executed locally using the TMKSVR. The communication is done using TCP/IP. An installation share on the System i host needs to be created and mapped to the Windows installation host, which is done automatically by the TMKSVR.

  Run SETUP.EXE from the directory   IM_OS400_PPC64\TMKSVR => Start Install

  12.  Logon to Windows host system as user SAPINST and now start sapinst.exe from the installation master media.

12.1: The SAPinst/TMKSVR – Session Parameters dialog box appears and prompts you for the target System i parameters. Enter your values.

12.2 : The SAPInst GUI now starts automatically displaying the welcome screen.

  13. Generate the migration structure files (Export) by moving forward with appropriate selection 

13.1:  Software Life-cycle Options =>System Copy =>IBM DB2 for i5/OS => Source system export => Select the relevant option (Central System/Distributed System/HA System).

 13.2: Since ours was High-Availabe system we had chosen "High-Availability System"=>Based on AS ABAP and AS JAVA in our selection (Make sure before moving to DB Instance export, Export preparation and Table splitting (if required) is done).

13.3: Provide the path of Profile directory.

13.4: Uncheck the option of “Use database specific tools”, unless you want to use Database specific procedure=> Next .

13.5: Provide the path to store the Export in the Export Location and uncheck the selection of “Stop running system” => Next.

13.6: It will ask to place the SQL file generated by SMIGR_CREATE_DDL report in the SAPInst_DIR created by SAPinst.

13.7: Find the SQL file and place it in the required directory of SAPInst_dir => now come back to SAPInst screen and click OK => Next.

13.8: Select the target database and select appropriate Export settings.

13.9: Select the characteristic as per the platform; our target platform is Windows (Little-Endian). Number of parallel jobs can be revised provided the resources are sufficient.

13.10: Unselect the option “Target system and source system will remain operational in parallel” in Java system Export phase if no plans for importing parallel => Next. 

13.11: Check if any revision required, if not then move forward => Next 

13.12: Once Database export is finished successfully =>click OK on SAPInst screen.

13.13: Now start export of Central Instance.

13.14: Follow the procedure which is almost similar to DB export and complete the central system export, And once Export phase is over=>click OK on SAPInst screen.

 

PRE-EXPORT CHECKLIST TASK

Completed

Stop all SAP users and set appropriate profile parameters to ensure users cannot access the SAP system


Verify all updates have completed


Stop all active jobs and all scheduled background jobs


Release all SAP locks


Release all transports and open repairs


Stop all operation modes


Clear all ABAP dump files


Clear TemSE (spool database)


Stop all print queues


Stop all cron or OS scheduled background jobs


Stop interfaces and third-party tools


Stop all application instances, CI, and SCS


Stop SAP database

 

SAP Notes can be referred

We can refer below SAP Notes for the purpose:

-  SAP Note 82478 - SAP system OS/DB migration

-  SAP Note 1120872 - Hom./Het.System Copy SAP NetWeaver 7.0

-  SAP Note 784118 - System Copy Java Tools

-  SAP Note 888210 - NW 7.**: System copy (supplementary note)

-   SAP Note 952514 - Using the table splitting feature

-   SAP Note 547314 - FAQ: System Copy procedure

-   Note 628156 - DB6: Cross-Platform System Copy using Backup/Restore (not relevant in case of Win-SQL)

-   Note 9385 - What to do with QCM tables (conversion tables)

  • No labels