PUBLIC. System Copy Guide. System Copy for SAP Systems Based on SAP ABAP. Target Audience. System administrators Technology consultants

Transcription

1 PUBLIC System Copy Guide System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 ABAP Target Audience System administrators Technology consultants Document version: /28/2008

2 Document History Caution Before you start the implementation, make sure you have the latest version of this document. You can find the latest version on SAP Service Marketplace The following table provides an overview on the most important document changes: Version Date Description 1.0 3/28/2008 Initial Version 2/136 PUBLIC 03/28/2008

3 Table of Contents Chapter 1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR Terminology Online Information from SAP System Architecture Restrictions Constraints Chapter 2 Planning Chapter 3 Preparations General Technical Preparations Installing the Java Runtime Environment Chapter 4 Database Independent System Copy System Copy Procedure Generating DDL Statements Preparation for Table Splitting Preparing the Export Exporting the Source System Using SAPinst Running SAPinst on UNIX or Windows to Perform the Export Running SAPinst on System i to Perform the Export Preparing the Windows Host for the SAP System Installation Preparing a Windows User Account and System i User Profile Installing TMKSVR and Creating an Installation Share Starting SAPinst on System i Restarting R3load Processes Setting Up the Target System Installing the Target System Chapter 5 Database-Specific System Copy Oracle-Specific Procedure Generating the Control File Structure Creating an Offline Backup Preparing the Target System /28/2008 PUBLIC 3/136

4 5.1.4 Restoring the Database Files on the Target System SAP MaxDB-Specific Procedure MS SQL Server-Specific Procedure IBM DB2 for Linux, UNIX, and Windows Specific Procedures IBM DB2 for i5/os Procedure IBM DB2 for z/os Specific Procedure Step 1: Check Consistency Step 2: Stop and Restart the Source System Step 3: Run SQL Statements in the Source System SQL Statement Number SQL Statement Number SQL Statement Number SQL Statement Number SQL Statement Number SQL Statement Number SQL Statement Number SQL Statement Number SQL Statement Number Step 4: Capturing View Definitions with DB2 V9 (if the Schema Name is to be Changed) Step 5: Stop the Source System Step 6: Making Copies of Source Data Sets Step 7: Creating the Target System Step 8: Printing the Bootstrap Data Sets Step 9a: Changing the Bootstrap Data Sets (BSDS) Step 9b: Start the Target System Step 9c: Creating a New STOGROUP Using the HLQ of the Target System Step 9d: Stopping Index Spaces Step 9e: Changing the User-Defined Indexes in the DB2 Catalog Step 9f: Restart the Index Spaces Step 9g: Creating the Temporary Files for the DB2 Target System Step 9h: Implementing HLQ of the Target System in the Work File Database Step 9i: Adjusting the DDF Location Name and Port Number Step 10 (DB2 V8 and Lower): Changing the VCAT of the Target System Step 10 (DB2 V9): Changing the VCAT of the Target System Step 11 (DB2 V9): Changing the Schema of the Target System Step 12: Adapting WLM Application Environments for DB2 Stored Procedures 94 Chapter 6 Follow-Up Activities Performing Follow-Up Activities in the Source System Performing Follow-Up Activities in the Target System Performing Follow-Up Activities for ABAP /136 PUBLIC 03/28/2008

5 6.2.2 Performing Jobhead Correction after Homogeneous System Copy Chapter 7 Additional Information R3load Procedures Using the Migration Monitor Configuration Assigning DDL Files to Packages Defining Groups of Packages Processing Split Tables Starting the Migration Monitor Output Files Installing the Target System Using the Migration Monitor Using SAPinst GUI Interrupted Installation with SAPinst Performing a Remote Export Using SAPinst Performing a Remote Installation with SAPinst (Optional) Starting SAPinst GUI Separately (Optional) /28/2008 PUBLIC 5/136

6 6/136 PUBLIC 03/28/2008

7 1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 As of SAP NetWeaver 7.0, you can copy ABAP systems, ABAP+Java systems and Java systems in one run using either database-specific methods or database-independent methods. 1.1 Terminology Homogeneous System Copy During the system copy you use the same operating system and database platform as the original system. Heterogeneous System Copy During the system copy, you change either the operating system or the database system, or both. Heterogeneous system copy is a synonym for migration. Source System and Target System The SAP system containing the original database is called the source system and the system to which the database copy is to be imported is called the target system. Their SAP system names are abbreviated to SOURCE_SAPSID and TARGET_SAPSID (System i: source_<sid> and target_<sid>). The terms source database and target database are also used in this description. System Copy Duplication of an SAP system. Certain SAP parameters might change in a copy. When you perform a system copy, SAPinst installs all the instances again, but it uses a copy of the source system database to set up the database. Database Copy Database-dependent part of the system copy. Placeholders Placeholders such as <SAPSID> are used in commands. They are used in the same way as in the SAP system installation documentation. You must replace them with the values valid for your site. The following additional placeholders are used: Placeholder Meaning How to find out <SAPSID> SAP system ID <S_HOST> System name of the source host Command hostname 03/28/2008 PUBLIC 7/136

8 1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 1.2 Online Information from SAP Placeholder Meaning How to find out <T_HOST> System name of the target host Command hostname <S_SAPSID> SAP system ID of the source system <SAPSID> of the original system <T_SAPSID> SAP system ID of the target system <SAPSID> of the target system <S_DBSID> Database ID of the source system <DBSID> of the original system <T_DBSID> Database ID of the target system <DBSID> of the target system 1.2 Online Information from SAP More information about system copy is online available as follows: SAP System Copy & Migration page at SAP OS/DB Migration page at Additionally to the information contained on this page, check the SAP OS/DB Migration Planning Guide that is available in the Media Library. SAP Caution Only perform a system copy if you have experience in copying systems and good knowledge of the operating system, the database, and the ABAP Dictionary. Only perform a heterogeneous system copy if you are a certified system support consultant or a certified SAP Technical Consultant. If you encounter problems during the system copy, create a customer message using the application area BC-INS-MIG. 1.3 System Architecture 1.4 Restrictions The target system installation consists of both the target database and target instances/application servers installations. For the scenarios below, the following holds: Only valid for: IBM DB2 for Linux and UNIX and Windows The option Deferred Table Creation is not supported for load-based system copies for SAP systems that are not based on SAP NetWeaver 7.0 SR3. End of: IBM DB2 for Linux and UNIX and Windows 8/136 PUBLIC 03/28/2008

9 1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 1.5 Constraints Refresh of the database is not supported. A refresh of the database means that only the database is loaded with the content of a database of a different system. As in this scenario no migration controller is invoked, this is not supported. Copying the database only is not supported. Copying the central instance only is not supported. The migration controller deletes all dialog instances in the database, so the system is not complete any longer. Reinstalling the central instance without the database is not supported. The migration controller deletes all dialog instances in the database, so the system is not complete any longer. 1.5 Constraints SAP does not support client transport as a system copy method. Transporting production clients is not supported at all. You can use client transport for the initial setup of an SAP system infrastructure. This documentation does not cover the client copy procedure. This documentation does not describe how to export and import a database with the installation tools for reorganization purposes. Use the appropriate tools for database reorganization, as SAP does not support this installation option. If you have made modifications in your development system and want to copy your quality assurance or production system onto the development system, see SAP This documentation describes how to copy data from one SAP system to another SAP system based on SAP NetWeaver Application Server. This documentation does not describe how to copy data from non-sap systems to SAP systems. If you want to convert a non-unicode system to a Unicode system or perform the system copy of a Unicode system, see SAP For the development of Java applications, we strongly recommend that you follow the rules mentioned below. Otherwise, we cannot guarantee that you can copy your Java engine later with the SAP tools to change your underlying operating system and/or database system. SAP does not generally support all Data Archiving operations after a system copy. If you used Data Archiving in the source or in the target system, access to the created archive file(s) from the target system may not always be possible. For more information, see SAP and System Landscape Optimization at Access to archived files from the target system without a dedicated archive migration project is only supported in the following cases: Your system copy clones a source system for nonproductive purposes, only read-access to the previously archived data is intended from the target system (no reloading), and you do not store archive files using ArchiveLink/CMS. You can either copy all archive files to file systems that are not shared between the source and the target system, or you arrange network access for appropriate archive file sharing. 03/28/2008 PUBLIC 9/136

10 1 Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 1.5 Constraints The system copy is done to replace a productive system by a new productive system (for example, hardware migration), assuming that the target system did not exist before and the source system s operation is discontinued after the system copy. You must not change the system ID during system copy, but arrange for file access and/or ArchiveLink/CMS connectivity. In all other cases, contact SAP SLO at or slo.consulting@sap.com. When you perform a system copy, all software units or usage types in the source system are copied to the target system. This means that none of the usage types in the target system can be excluded from the system copy, nor can you select usage types. Dos and Don ts for system copy: Do: Save configuration data and runtime data in the Java database only. If you absolutely need to save this data to the file system level, you must use the Software Deployment Manager (SDM) to save the data. Follow the Open SQL standard. Make sure that all communication runs through the database pool. Don t: Save any system and infrastructure-specific data in business objects. Use a pointer to the central storage of such information, for example: SAP SystemID and SID (SAPSID =SID=system name) Host name IP addresses Services and Ports Logical destinations and logical system names Other technical infrastructure names Use file system persistency. Set up dependencies between Java and ABAP. 10/136 PUBLIC 03/28/2008

11 2 Planning 2 Planning This section describes how to plan your system copy. You can apply the system copy for: Setting up system landscapes (where the SAP systems have different SAPSIDs). Creating systems for testing, demonstration, training, and standby. Depending on the purpose of the system, it might be advisable to use the same SAP system ID, even though this prevents you from including the system in a system group for transports. Only valid for: Oracle You cannot create standby systems with a system copy. End of: Oracle You should perform upgrades in a test system first. This way you can identify customer-specific problems that might result from modifications. You can set up the SAP system infrastructure (development, quality assurance, and production system) without making a system copy as follows: Install all SAP systems, starting with the development system. Customize the development system as described in the implementation documentation. Transport the client-dependent and client-independent data to the quality assurance and production systems. However, if you do not follow this concept, you can also install a system, customize it and then perform a system copy. When copying a system that contains production data it is important to choose the right moment for the copy. This could be a month-end or year-end closing. Caution Do not use NFS-mounted file systems because writing to NFS-mounted file systems might cause corrupted dumps. 03/28/2008 PUBLIC 11/136

12 2 Planning Required Documentation Read the following SAP for up-to-date information: SAP (Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3) The documentation System Copy for SAP Systems Based on SAP NetWeaver 7.0 SR3 only describes the export of the source system in detail. For the installation of the target system, you also need the installation guide for your SAP application: SAP NetWeaver 7.0: Installation Guide SAP NetWeaver 7.0 SR3 ABAP on <OS> : <DB> at Installation SAP NetWeaver Systems. SAP ERP 6.0: Installation Guide SAP ERP 6.0 SR3 ABAP on <OS> : <DB> at SAP ERP 6.0 Installation. SAP CRM 5.0: Installation Guide SAP CRM 5.0 SR3 ABAP on <OS> : <DB> at SAP CRM 2005 CRM Core and Standalone Components. SAP SRM 5.0: Installation Guide SAP SRM 5.0 SR3 ABAP on <OS> : <DB> at Using SAP SRM Server 5.0. SAP SCM 5.0: Installation Guide SAP SCM 5.0 SR3 ABAP on <OS> : <DB> at SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP SCM 5.0 Server. Required DVDs, Tools, and Other Software Make sure that all required DVDs for the system copy are available: Required DVDs Installation Master DVD The DVD names are abbreviated. You can find the full names of all media shipped with SAP NetWeaver 7.0 in Media Information for SAP NetWeaver 7.0 at Order the right version of the installation kit before starting the system copy. Make sure that the versions of the SAP system and the installation tools are the same on the target and source systems. Exceptions are only allowed if they are described in an SAP. You can operate several SAP systems on a single host without encountering any problems. Nevertheless, we recommend that you use a separate host for each system because an SAP system upgrade might depend on an OS upgrade. If the SAP systems are on separate hosts, you can upgrade them at different times. 12/136 PUBLIC 03/28/2008

13 2 Planning Caution The source system must be in a consistent state before you can copy it. Check that you have the appropriate tool versions for your SAP kernel. For a heterogeneous system copy you need to get a migration key by generating it at Creating A System Copy Plan Create a plan to perform the system copy. 1. Consider the downtime of the source system (for preparations and copying) when planning the system copy. 2. Perform a test run of the system copy. You can use the time taken by the test run to calculate the system downtime: If your target system will replace your source system, try to perform a complete test run. This means that the entire database is exported from the source system, transferred to the target system and imported there. System downtime is approximately equal to the total test time (that is, time for export, transport, and import). If you do not want to replace your source system, a partial test run (export of the entire database or parts of it) can be sufficient to calculate the system downtime. The source system is only down for the time of the export. Calculating the system downtime is particularly important for very large databases (VLDB) or when tapes are being used. The test run is also to determine the amount of export data. Choose the best data transfer method (for example, FTP or tape). We recommend that you perform read/write actions only on local file systems. 3. Define a schedule for the test migration and the final migration. Miscellaneous In the event of a major change in hardware configuration (for example, new machine type, new hard disk configuration, new file system type), consult your SAP-authorized hardware partner. Decide which system copy procedure you want to use: The database-independent procedure using SAP tools. Use this method if database-specific methods are either not available or not suitable. For more information, see, Database-Independent System Copy [page 25]. For a heterogeneous system copy, only the database-independent method is available. The database-specific procedure using tools provided by the database vendor Some database vendors offer specific tools for copying a database. These tools let you: 03/28/2008 PUBLIC 13/136

14 2 Planning Restore a backup of one database (source database) in another one (target database) (backup method) Unload the source database and load the data into the target database For more information, see Database-Specific System Copy [page 57]. Choosing an SAP system ID You can choose the new SAP system ID <TARGET_SAPSID> freely during a new installation. Caution To meet the requirements of the Workbench Organizer, you must choose different SAP system IDs for different SAP systems. SAP license Once the installation is completed and the SAP system copy has been imported, you will require a new license key for the target system. The license key of the source system is not valid for this system. For more information about ordering and installing the SAP license, see SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management SAP Licenses. For more information about SAP license keys, see Archiving files Data that has been archived in the source system (data that does not reside in the database but was moved to a different storage location using SAP Archive Management) must be made accessible in the target system. Adapt the file residence information in the target system. For more information, see SAP NetWeaver 7.0 Library English SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management Data Archiving. Access to archive files is platform-independent. Configuration analysis and hardware analysis You need to determine the: Number of application servers Expected size of the database Additional disks or other hardware required Required memory See the section on hardware and software requirements in the SAP system installation documentation to determine the system requirements. These methods are not supported for all database systems. See the following table to check which copy methods are available for your database system: 14/136 PUBLIC 03/28/2008

15 2 Planning Database OS Platform Available Methods SAP MaxDB UNIX Use one of the following: System copy procedure on UNIX using R3load For more information, see System Copy Procedure [page 26]. System copy procedure for a homogeneous system copy only For more information, see SAP MaxDB-specific procedure [page 68]. SAP MaxDB Windows Use one of the following: System copy procedure on Windows using R3load For more information, see System Copy Procedure [page 26]. System copy procedure for a homogeneous system copy only For more information, see SAP MaxDB-specific procedure [page 68]. IBM DB2 for i5/os IBM DB2 for Linux, UNIX, and Windows IBM System i UNIX or Windows Use one of the following: System copy procedure on System i using R3load For more information, see Starting SAPinst on System i [page 47]. System i-specific procedure for a homogeneous system copy only For more information, see IBM DB2 for I5/OS Procedure [page 74]. For more information, see SAP Use one of the following: Only valid for: UNIX System copy procedure on UNIX using R3load For more information, see System Copy Procedure [page 26]. End of: UNIX Only valid for: Windows System copy procedure on Windows using R3load For more information, see System Copy Procedure [page 26]. End of: Windows The backup method of IBM DB2 for Linux, UNIX, and Windows is supported for SAP systems based on SAP NetWeaver 7.0 SR3. For more information, see IBM DB2 for Linux, UNIX, and Windows Specific Procedures [page 71]. 03/28/2008 PUBLIC 15/136

16 2 Planning Database OS Platform Available Methods IBM DB2 for z/os IBM System z Use one of the following: Only valid for: UNIX System copy procedure on UNIX using R3load For more information, see System Copy Procedure [page 26]. End of: UNIX Only valid for: Windows System copy procedure on Windows using R3load For more information, see System Copy Procedure [page 26]. End of: Windows Additional Information: For more information about the IBM DB2 for z/os specific procedure for a homogeneous system copy only, see IBM DB2 for z/os Specific Procedure [page 74]. When R3ta is used to split tables, DELETE with WHERE is not performed if import errors occur in the target system. For more information, see SAP Oracle UNIX Use one of the following: Only valid for: UNIX System copy procedure on UNIX using R3load For more information, see System Copy Procedure [page 26]. End of: UNIX R3load method with Export/Import Monitors For more information, see R3load Procedures Using the Migration Monitor [page 101]. Oracle-specific procedure for a homogeneous system copy only For more information, see Oracle-Specific Procedure [page 59]. Oracle Windows Use one of the following: Only valid for: Windows System copy procedure on Windows using R3load For more information, see System Copy Procedure [page 26]. End of: Windows R3load method with Export/Import Monitors For more information, see R3load Procedures Using the Migration Monitor [page 101]. Homogeneous system copy only: Oracle backup/restore method For more information, see Oracle-Specific Procedure [page 59] and SAP MS SQL Server Windows Use one of the following: Only valid for: Windows System copy procedure on Windows using R3load For more information, see System Copy Procedure [page 26]. End of: Windows R3load method with Export/Import Monitors 16/136 PUBLIC 03/28/2008

17 2 Planning Database OS Platform Available Methods For more information, see R3load Procedures Using the Migration Monitor [page 101]. Homogeneous system copy only: Backup/Restore or Detach/Attach Method For more information, see MS SQL Server-Specific Procedure [page 70] and SAP s and /28/2008 PUBLIC 17/136

18 This page is intentionally left blank.

19 3 Preparations 3 Preparations Before you start the system copy, you must perform the following preparation steps: 3.1 General Technical Preparations To make a consistent copy of the database, you need to prepare the source system and perform some subsequent actions on the target system. This is not necessary when performing a test run. The following describes important preparations. For more information about SAP system administration, see the SAP Online Documentation. Before you start a system copy, check the minimum kernel patch level required by the support package level of the source system. It might be necessary to replace the SAP kernel delivered with the kernel DVD of the installation kit and installed during the installation of the target system by a newer kernel patch level before starting the target system. If you have to replace the delivered SAP kernel, you can do this after the installation of the central instance. Before you start the export on your source system, check that your JAVA_HOME environment points to a valid JDK version. No canceled or pending update requests should be in the system. Check this by choosing Tools Administration Monitor Update (transaction SM13). If canceled or pending updates exist, you must update these again or delete them from all clients. You can see whether canceled or pending updates exist by checking if table VBDATA contains any entries. Find the canceled or open updates as follows: 1. Call transaction SM Delete the default values for the client, user, and time. 3. Choose all update requests. If canceled or pending records exist, you must update these again or delete them. Check whether this action was successful using transaction SE16 for table VBDATA. Set all released jobs from Released to Scheduled: Tools CCMS Background Processing Jobs - Overview and Administration (transaction SM37) You also need to do this for jobs that must run periodically (see SAP 16083). Select all jobs (include start after event) as follows: Job Released Scheduled Adapt the operation mode timetable to make sure that no switching of operating modes takes place while a system is being copied as follows: 03/28/2008 PUBLIC 19/136

20 3 Preparations 3.1 General Technical Preparations Tools CCMS Configuration Operation mode calendar (transaction SM63) Write down the logical system names of all clients: 1. If you plan to overwrite an existing system with a system copy (for example, the source and target systems will both exist after the system copy), make sure you write down the logical system names of all clients in the system that will be overwritten (transaction SCC4). As the logical system names will be overwritten, in the event of differences, you must change them back to their original names (as they existed in the system that is overwritten) in the follow-on actions after the system copy. 2. If you create a new system with a system copy (that is, create an upgrade test system), make sure that the logical naming strategy for this new system is consistent with your existing logical system naming convention. If you are still planning your BI (formerly BW) system landscape, see SAP If your system copy is used to replace hardware for the DB server, migrate to a different database system or operating system (that is, source system for the copy is the same as the copy target), no changes to logical system names are required. Before the export, delete QCM tables from your system as follows: 1. Before deleting you must always check That the tables are consistent no restart log or conversion procedure termination must be displayed That the data of the original table can be read If application programs that use the affected original table do not run correctly, do not delete the QCM table yet. 2. Call transaction SE Choose Extras Invalid temp. table All QCM tables that can be deleted are displayed. 4. Mark the tables and delete them. FI customers: You can perform an additional consistency check by running the job SAPF190 before copying the source system, as well as after copying the target system, and then compare the results. Make sure that no customer data is changed in the meantime. You can do this as follows: Accounting Financial Accounting General ledger Periodic Processing Closing Check/count Comparison FI customers: You can further check consistency by running the jobs RFUMSV00 (tax on sales/purchases), RAGITT01 (asset history sheet), RAZUGA01 (asset acquisitions), RAABGA01 (fixed asset retirements) before copying the source system, as well as after copying the target system, and then compare the results. Make sure that no customer data is changed in the meantime. CO customers: You can perform an additional consistency check by running the report group 1SIP before copying the source system, as well as after copying the target system, and then compare the results. Make sure that no customer data is changed in the meantime. 20/136 PUBLIC 03/28/2008

21 3 Preparations 3.2 Installing the Java Runtime Environment Caution Prerequisites for an export: Before performing an export, make sure that no incremental conversion is in progress. To test if an incremental conversion is in progress, run transaction ICNV. If there are any table entries in table TICNV, an incremental conversion is in progress. In this case, you have the following options: 1. Defer the migration until the incremental conversion has finished. 2. Try to finish the incremental conversion by performing the following steps: If the tables are in state For conversion or in state Done, delete the entries by choosing Control Delete Entry. If the tables are in any other state, you have to finish the incremental conversion. Choose Assistant and proceed according to the online documentation. Caution Heterogeneous System Copy only: Before you start the export of your source system, 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 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. Prepare the system for SAPinst. For more information, see Installing the Java Runtime Environment [page 21]. 3.2 Installing the Java Runtime Environment You need to prepare your system for SAPinst. This includes the installation of a Java Runtime Environment (JRE), which is required both for SAPinst and the SAPinst GUI. 03/28/2008 PUBLIC 21/136

22 3 Preparations 3.2 Installing the Java Runtime Environment Only valid for: UNIX;Windows If required, you can perform a remote installation using a standalone SAPinst GUI on a separate Windows or UNIX host. This lets you perform the installation on a remote host, controlling it with the SAPinst GUI from a local host. If you want to perform a remote installation, see Performing a Remote Installation with SAPinst [page 123]. In this case, you need at least a JRE on the local host to start the SAPinst GUI there. End of: UNIX;Windows Procedure 1. Check the JRE versions that are released for SAP systems in the Product Availability Matrix (PAM): a) Go to b) Only valid for: SAP NetWeaver On the right-hand panel, choose SAP NetWeaver SAP NetWeaver 7.0 (2004S). End of: SAP NetWeaver c) Only valid for: SAP CRM;SAP ERP;SAP SCM;SAP SRM On the right-hand panel, choose SAP Application Components <your product>. End of: SAP CRM;SAP ERP;SAP SCM;SAP SRM d) Choose tabstrip JSE Platforms. For more information about the recommended JRE version for your operating system and about how to download it, see SAP Make sure a valid JRE version is installed, as follows: If the JRE is not already installed, you need to download and install it. If the JRE is not already installed Since the JRE is not part of the SAP shipment, you need to download and install it. The JRE is part of the JDK (Java Development Kit). If the JRE is already installed Check the installed version of the JRE by entering: java -version SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime environment. If SAPINST_JRE_HOME is not found, SAPinst also checks JAVA_HOME. 22/136 PUBLIC 03/28/2008

23 3 Preparations 3.2 Installing the Java Runtime Environment Only valid for: UNIX Linux If you use a Sun Java VM, you have to perform the following: Edit the configuration file $JAVA_HOME/jre/lib/security/java.security and replace entry securerandom.source=file:/dev/random with securerandom.source=file:/dev/urandom. End of: UNIX Linux 03/28/2008 PUBLIC 23/136

24 This page is intentionally left blank.

25 4 Database Independent System Copy 4 Database Independent System Copy With the SAP installation tool SAPinst, you can export and import your database in a database-independent format. SAPinst uses the R3load tool. R3load generates a database export of all SAP objects that are defined in the ABAP Dictionary and archives the configuration and components in the file system. Constraints R3load and Jload Restrictions SAPinst generates a database dump of all SAP objects that are defined in the ABAP Dictionary (R3load). Other objects are not exported by SAPinst. For a consistent database the SAP system must be shutdown (excluding the database!). The database must still be running. R3load only: Changes to database objects that cannot be maintained in the ABAP Dictionary (transaction SE14), such as the distribution of tables over several tablespaces or dbspaces, are lost after the system copy. R3load only: Indexes longer than 18 characters are not allowed on the database to be exported. System Copy Tools Every installation service (dialog instance installation, for example) must have its own separate installation directory whenever you start SAPinst. If the target system already exists and if you do not plan to perform an MCOD installation, delete the database on the target system before the import according to the corresponding description in section Additional Information of the installation documentation for your SAP component. If the database configuration of your database is stored in the file system, we recommend you to back up these configuration files before deleting the database. Splitting STR Files During the standard system copy process, all tables of the SAP system are grouped into packages, whereby all tables with the same data class belong to the same package. The processing unit for one unload/load process is a package. The packages usually differ in number and size of contained tables, resulting in varying unload/load runtimes. The overall runtime can be reduced by creating packages of the same size, that is, creating packages with a similar processing time. You can achieve this by splitting the default packages (one package per data class) into more and smaller pieces. 03/28/2008 PUBLIC 25/136

26 4 Database Independent System Copy 4.1 System Copy Procedure There are several options of how to split packages. For a detailed description of the options, see the F1 help about the parameters prompted on the screen Split STR Files while running SAPinst to export the database. The options can be used separately or when using the new Java based splitting tool combined. Splitting of STR Files is part of the Advanced Export Parameters and is disabled by default. If you select the splitting option and unless you did not already perform some tests, using the splitting tool parameters selected by SAPinst is a good starting point. Caution If you want to split STR files, you must first create the EXT files for the target database system. You can find the EXT files in your export dump directory, subdirectory DB/<DBTYPE>, for example DB/ORA. Process Flow For UNIX, Windows, or System i, see System Copy Procedure [page 26]. 4.1 System Copy Procedure This section describes the system copy procedure using R3load. Process Flow on the Source System (Export) When performing the export you create a MIGRATION EXPORT CD image, which contains the data of the exported system, and which you use to install the target system. Follow the sequence of steps described in the process flows below for a: Central System Distributed System and High-Availability System Central System To perform the export for a central system, you need to proceed as follows on the central system host: 1. Heterogeneous system copy: Generate the migration key at Enter the installation number of your source system when prompted. 2. Perform the export on the central system host: a) Only valid for: UNIX;Windows Make sure that the QCM tables are deleted from your system. For more information, see General Technical Preparations [page 19]. End of: UNIX;Windows 26/136 PUBLIC 03/28/2008

27 4 Database Independent System Copy 4.1 System Copy Procedure b) c) d) Only valid for: IBM i5/os Prepare the Windows host for the SAP system installation. For more information, see Preparing the Windows Host for the SAP System Installation [page 41]. End of: IBM i5/os Only valid for: IBM i5/os Prepare a Windows user account and a System i user profile. For more information, see Preparing a Windows User Account and System i User Profile [page 42]. End of: IBM i5/os Only valid for: IBM i5/os Install TMKSVR and create an installation share. For more information, see Installing TMKSVR and Create an Installation Share [page 44]. End of: IBM i5/os e) Generate DDL statements. For more information, see Generating DDL Statements [page 29]. f) Prepare the system for table splitting (optional). For more information, see Preparation for Table Splitting [page 30]. g) Run SAPinst on UNIX, Windows, or System i to prepare the source system for parallel export or parallel import (optional). For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 34] or Running SAPinst on System i to Perform the Export [page 41]. In SAPinst, choose the installation service Export Preparation. h) Run SAPinst on UNIX, Windows, or System i to export the database instance and the central instance. In SAPinst, choose the installation service Database Instance Export. For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 34] or Running SAPinst on System i to Perform the Export [page 41]. If R3load processes fail due to an error, solve the problem and perform a restart. For more information, see Restarting R3load Processes [page 51]. Result You have finished this part of the system copy. To complete the system copy, you set up the target system using SAPinst. For more information, see Setting Up the Target System Using SAPinst [page 53]. Distributed System or High-Availability System To perform the export for a distributed system or a high-availability-system, you need to proceed as follows: 03/28/2008 PUBLIC 27/136

28 4 Database Independent System Copy 4.1 System Copy Procedure 1. Heterogeneous system copy only: Generate the migration key at Enter the installation number of your source system when prompted 2. Perform the export on the database instance host: a) Only valid for: UNIX;Windows Make sure that the QCM tables are deleted from your system. For more information, see General Technical Preparations [page 19]. End of: UNIX;Windows b) Generate DDL statements. For more information, see Generating DDL statements [page 29]. c) Prepare the system for table splitting (optional). For more information, see Preparation for Table Splitting [page 30]. d) Run SAPinst on UNIX, Windows, or System i to prepare the source system for parallel export/import (optional). In SAPinst, choose the installation service Export Preparation. For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 34] or Running SAPist on System i to Perform the Export [page 41]. e) Run SAPinst on UNIX, Windows, or System i to export the database instance. In SAPinst, choose the installation service Database Instance Export. For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 34] or Running SAPinst on System i to Perform the Export [page 41]. If R3load processes fail due to an error, solve the problem and perform a restart. For more information, see Restarting R3load Processes [page 51]. Caution If your database instance is running on HP PA-Risc, you must proceed as described in SAP Result You finished this part of the system copy. To complete the system copy, you set up the target system using SAPinst. For more information, see Setting Up the Target System Using SAPinst [page 53]. 28/136 PUBLIC 03/28/2008

29 4 Database Independent System Copy 4.2 Generating DDL Statements Overview on Export Options Figure 1: 4.2 Generating DDL Statements To migrate nonstandard database objects, you need to generate DDL statements using the ABAP report SMIGR_CREATE_DDL. You must perform this procedure before starting SAPinst. Procedure 1. Log on to the system as a system administrator in the productive BI-ABAP-client. 2. Call transaction SE38 and run the program SMIGR_CREATE_DDL. 3. Select the target database. Depending on the database manufacturer, you might need to select the database version. The value help supports you in selecting the database version. In general, you only should enter a database version that is available in the value help. 4. You are able to select Unicode Migration if you also wish to perform a Unicode system copy (from Unicode to Unicode) or a Unicode conversion (from non-unicode to Unicode). 5. Specify an empty working directory to which the files generated by the report are to be written. 6. If required, you can restrict the generation of DDL statements to specific table types or individual tables. 7. Execute the program. 03/28/2008 PUBLIC 29/136

30 4 Database Independent System Copy 4.3 Preparation for Table Splitting The DDL statements are generated and are written to the specified directory. Caution If no database-specific objects exist in the database, no SQL files will be generated. As long as the report terminates with status successfully, this is not an error. 8. Before starting the export, the generated SQL files have to be copied from the specified directory to the <instdir> directory of the export. For additional database-specific information, see also SAP Preparation for Table Splitting The tool R3ta processes large tables. Instead of exporting/importing one table with one R3load process, the table is processed in, for example, 10 entities. Each entity can be processed by different R3load processes. The advantages of splitting the tables are: Large tables are processed in smaller packages. If the export or import of a table aborts with an error, only the processing of the package where the error occurred has to be repeated and not for the complete table. The export and import of one table can be performed in parallel by starting several R3load processes to work on some packages in parallel. Prerequisites The export and import has to be performed with the Migration Monitor when the table splitting feature is used. For the following databases, we recommend that you create an index on the column listed in the hints file for the table you want to split before starting R3ta: DB2 for z/os (Only create a temporary index if you want to perform an unsorted unload.) Oracle For more information, see paragraph Creating a Temporary Index. Restrictions Only tables that are described in the SAP dictionary can be split. The following tables cannot be split: DDNTF DDNTF_CONV_UC DDNTT DDNTT_CONV_UC DDLOG (is never copied, but created empty in the target system) 30/136 PUBLIC 03/28/2008

31 4 Database Independent System Copy 4.3 Preparation for Table Splitting 1. Update the R3ta, R3ldctld and the db<dbtype>slib.* in the kernel directory. You can find a version of these files on the Installation Master DVD in the directory IM_<OS>/<DBTYPE>/{UC/NUC}. 2. Create a file that contains lines of the form <table>%<nr of splits> for all tables to be split. Caution The tables listed in this file have to appear in alphabetical order! 3. Start SAPinst. 4. Choose SAP NetWeaver System Copy Source System ABAP System <Database> <Unicode or Non-Unicode> Table Splitting Preparation. 5. Specify SAPSID, <sidadm> password, the file that contains the split information, the export directory, and the number of parallel R3ta jobs. Caution The specified path to the export directory must not contain blanks! 6. Continue with Next. Now the *.WHR files and the whr.txt file are created in the export directory. Caution When doing a code page conversion (non-unicode fi Unicode; 4102 «4103), make sure not to use a WHERE condition with the column PAGENO included. If the column PAGENO is included in the WHERE condition, repeat the table splitting - either with different splitting parameters or by defining a suitable column for this table, using the R3ta_hints.txt. 7. If required, create the temporary index on the source system s tables to be split. For more information, see paragraph Creating a Temporary Index. Parallel data export of a table is supported by all database platforms but not parallel data import. When the target database platform does not support the parallel data import, the Migration Monitor has to be configured in the way that the data import processes the packages are sequentially. For more information, see Processing Split Tables. Using Hints With the file R3ta_hints.txt, you can instruct R3ta to use specific columns of a table to create a WHERE condition. The file has to be located in the directory in which you start R3ta. With one line in the file R3ta_hints.txt, you specify the table name followed by one or more column names, separated by a blank. The columns have to be part of the primary key of the table. These specifications are used by R3ta to create the WHERE condition. A file R3ta_hints.txt with column hints for several tables is delivered with the Installation Master DVD. After the Table Splitting Preparation, make sure you select the Split predefined tables checkbox and add 03/28/2008 PUBLIC 31/136

32 4 Database Independent System Copy 4.3 Preparation for Table Splitting the R3ta_hints.txt file in the Split STR Files dialog box. If you want to modify this file, copy it from the directory <IM_OS>/COMMON/INSTALL to the installation directory and adapt it according your requirements as soon as the Parameter Summary dialog appears and before starting the processing phase. Creating a Temporary Index Only valid for: IBM DB2 for z/os IBM DB2 z/os only: Create the corresponding temporary index on the database with database tools. Only create a temporary index if you want to perform an unsorted unload. This is the case when you use a DDLDB2.TPL file with no ORDER_BY_PKEY and the R3load does not overrule this setting. Which tables cannot be unloaded unsorted is described in SAP End of: IBM DB2 for z/os Only valid for: IBM DB2 for z/os Example 1. Use the DEFER YES parameter to create the index. 2. Afterwards, use the REBUILD INDEX job to speed up the index creation process. End of: IBM DB2 for z/os Only valid for: Oracle Oracle only: For further information and for alternatives, see SAP End of: Oracle For each table to be split, R3ta creates the following files to facilitate the creation of the temporary index: File <table>_idx.str <table>_idx.tsk <table>_idx.cmd DRP_<table>_IDX.TSK DRP_<table>_IDX.cmd Description Contains the description of the temporary index; the default index name is <table>~img. Contains the task to create the temporary index. R3load command file for creating the temporary index. Contains the task to drop the temporary index. R3load command file for dropping the temporary index. You can use the R3load cmd, STR and TSK files created by R3ta to create the index. 32/136 PUBLIC 03/28/2008

33 4 Database Independent System Copy 4.4 Preparing the Export 1. Only valid for: IBM DB2 for i5/os;ibm DB2 for Linux and UNIX and Windows;IBM DB2 for z/os;maxdb;ms SQL Server Make sure that you do not lock the table while creating the temporary index. Depending on your database platform it might be necessary to modify the create index statement in the DDL<DBTYPE>.TPL file. End of: IBM DB2 for i5/os;ibm DB2 for Linux and UNIX and Windows;IBM DB2 for z/os;maxdb;ms SQL Server 2. Only valid for: Oracle Make sure that you do not lock the table while creating the temporary index. Depending on your database platform it might be necessary to modify the create index statement in the DDL<DBTYPE>.TPL file. Edit the file DDLORA.TPL and add the highlighted key words to the creind statement: creind: INDEX &ind name& ON &tab name& CREATE &unique& ( /{ &fld name& /-, /} ) TABLESPACE &tablespace& STORAGE (INITIAL &init& NEXT &next& MINEXTENTS &minext& MAXEXTENTS &maxext& PCTINCREASE &pctinc& ) NOLOGGING COMPUTE STATISTICS PARALLEL ONLINE; End of: Oracle 3. Call R3load as user <sapsid>adm with the following parameters: R3load dbcodepage <source system s dbcodepage> i <table>_idx.cmd l <table>_idx.log If your source system is a non-unicode system, the dbcodepage is If your source system is a Unicode system, the dbcodepage is 4102 (Big Endian) or 4103 (Little Endian). 4.4 Preparing the Export Optionally you can prepare the source system for the export using R3load and Jload, so as to enable parallel export/import. For this purpose you need to create certain files. The following steps are performed: Creating the export directory structure Creating database structure files (*.STR) Updating database statistics ( ) 03/28/2008 PUBLIC 33/136

34 4 Database Independent System Copy 4.5 Exporting the Source System Using SAPinst Size calculation for the target database (*.EXT,DBSIZE.XML) These export preparations are required, if: You want to build up the target system to the point where the database load starts, before the export of the source system has finished. Export and import processes should run in parallel during the system copy process. Procedure 1. You run SAPinst to perform the service Export Preparation. For more information, see Running SAPinst on UNIX or Windows to Perform the Export [page 34]. 2. As soon as the export preparations have finished successfully, the complete export directory with its structure and the generated files, which are required for building up the target system, have to be transferred to the target host. You can choose one of the following methods: Use the migration monitor with the FTP Copy Option to transfer the files to the target instance. Copy the export dump directory manually to the target host. The export dump directory can be shared and thus made accessible on the target host. In any case make sure that the dump directory and its subdirectories and files are accessible for user <sapsid>adm of the target system. For more information, see the documentation Migration Monitor User s Guide in the MIGMON.SAR archive on the SAP Installation Master DVD. 4.5 Exporting the Source System Using SAPinst Here you can find information about how to run SAPinst to perform the export on the source system: Running SAPinst on UNIX or Windows to Perform the Export [page 34] Running SAPinst on System i to Perform the Export [page 47] Running SAPinst on UNIX or Windows to Perform the Export This procedure tells you how to run SAPinst to export the database of your SAP system. SAPinst includes a SAPinst GUI and a GUI server, which both use Java. This section describes a standard export where SAPinst, SAPinst GUI, and the GUI server are running on the same host. If required, you can instead perform a remote system copy with SAPinst, where SAPinst GUI is running on a separate host from SAPinst and the GUI server. For more information, see Performing a Remote Installation with SAPinst [page 123]. 34/136 PUBLIC 03/28/2008

35 4 Database Independent System Copy 4.5 Exporting the Source System Using SAPinst the following about SAPinst: When you start SAPinst, SAPinst GUI and the GUI server are also started. SAPinst GUI connects using a secure SSL connection to the GUI server and the GUI server connects to SAPinst. Only valid for: UNIX SAPinst normally creates the installation directory sapinst_instdir directly below the temporary directory. SAPinst finds the temporary directory by checking the value of the environment variables TEMP, TMP, or TMPDIR. If no value is set for these variables, SAPinst uses /tmp as default installation directory. The SAPinst Self-Extractor extracts the SAPinst executables to the temporary directory. These executables are deleted again after SAPinst has stopped running. If required, you can terminate SAPinst and the SAPinst Self-Extractor by pressing Ctrl+C. End of: UNIX Only valid for: Windows SAPinst normally creates the installation directory sapinst_instdir, where it keeps its log files, and which is located directly below the Program Files directory. If SAPinst is not able to create sapinst_instdir directly below the Program Files directory, SAPinst tries to create sapinst_instdir in the directory defined by the environment variable TEMP. SAPinst creates a subdirectory for each installation service, called <sapinst_instdir>\<installation_service> which is located below %ProgramFiles%\sapinst_instdir. The SAPinst Self-Extractor extracts the executables to a temporary directory (TEMP, TMP, TMPDIR, or SystemRoot). These executables are deleted after SAPinst has stopped running. Directories with the name sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You can safely delete them. In the temporary directory, you can also find the SAPinst Self-Extractor log file dev_selfex.out, which might be useful if an error occurs. End of: Windows Caution If SAPinst cannot find a temporary directory, the installation terminates with the error FCO Only valid for: Windows If you want to terminate SAPinst and the SAPinst Self-Extractor, do one of the following: Right-click the icon for the SAPinst output window located in the Windows tray and choose Exit. Click the icon for the SAPinst output window located in the Windows tray and choose File Exit. End of: Windows 03/28/2008 PUBLIC 35/136

36 4 Database Independent System Copy 4.5 Exporting the Source System Using SAPinst Prerequisites Caution Make sure that you shut down all SAP Application Servers before the export. The database must still be running. Otherwise, the target system might be inconsistent. Only valid for: UNIX You are logged on to your host as user root. End of: UNIX Only valid for: Windows You are logged on to your host as user with the required rights and privileges that authorize you to install the SAP system with the SAPinst tool. For more information, see section Required User Authorization for the Installation in your installation guide. End of: Windows Make available the Master Installation DVD. You need at least 60 MB of free space in the installation directory for each ABAP installation option, and at least 130 MB of free space in the installation directory for each Java installation option. In addition, you need MB free space for the SAPinst executables. Only valid for: UNIX If you cannot provide 200 MB free space in the temporary directory, you can set one of the environment variables TEMP,TMP, or TMPDIR to another directory with 200 MB free space for the SAPinst executables. End of: UNIX Only valid for: Windows Before starting the export steps on the central instance of the source system, make sure that you have at least the same amount of disk space available in \\SAPLOC\<SAPSID>\<InstanceName>\SDM\program as is used in \\SAPLOC\<SAPSID>\<InstanceName>\root\origin. During the export some archives are written to the program subdirectories and SAPinst aborts if there is not enough space. End of: Windows Only valid for: DB2 UDB for UNIX and Windows Before you start the export of the existing SAP System, you have to download the current version of R3szchk at and copy it to directory /usr/sap/<>/sys/exe/run/. End of: DB2 UDB for UNIX and Windows 36/136 PUBLIC 03/28/2008

37 4 Database Independent System Copy 4.5 Exporting the Source System Using SAPinst Only valid for: UNIX Before starting the export, make sure that you have at least the same amount of disk space available in /sapmnt/<sapsid>/<instancename>/sdm/program as is used in /sapmnt/<sapsid>/<instancename>/sdm/root/origin. During the export, some archives are written to the program subdirectories and SAPinst aborts if there is not enough space. Make sure that the DISPLAY environment variable is set to <host_name>:0.0, where <host_name> is the host where the SAPinst GUI is displayed. Make sure that your SAPINST_JRE_HOME environment variable is set to a valid Java Runtime Environment (JRE). Only valid for: AIX If the operating system is AIX 64-bit, make sure that the PATH variable points to a JDK/JRE for AIX 64-bit. End of: AIX End of: UNIX For more information about SAPinst, see Using SAPinst GUI [page 119], Interrupted Installation with SAPinst [page 119], and Performing a Remote Export Using SAPinst [page 122]. 1. Start SAPinst from the SAP Installation Master DVD as follows: Only valid for: UNIX Choose one of the following ways: End of: UNIX Only valid for: UNIX Using the default installation directory (recommended) Enter the following commands: cd <Installation_Master_DVD>/IM_<OS>./sapinst SAPinst creates a directory called sapinst_instdir, which is the current working directory for your installation, below the temporary directory of your operating system. Using an alternative installation directory If you want to use an alternative installation directory, set the environment variable TEMP, TMP, or TMPDIR. Make sure that your operating system does not delete the contents of the temporary directory /tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for example, by using a crontab entry. Make sure that your current working directory is not an IM_<OS> directory belonging to another operating system. 03/28/2008 PUBLIC 37/136

38 4 Database Independent System Copy 4.5 Exporting the Source System Using SAPinst Example For example, the following causes an error: $ cd /sapcd2/im_hpux_ia64 $ /sapcd2/im_hpux_parisc/sapinst To correct this, enter the following: $ cd /sapcd2/im_hpux_parisc $ /sapcd2/im_hpux_parisc/sapinst End of: UNIX Only valid for: Windows Double-click sapinst.exe from the following path: <DVD_drive>:\DATA_UNITS\IM_WINDOWS_<platform> SAPinst GUI normally starts automatically by displaying the Welcome screen. End of: Windows During the installation, the default ports and are used for communication between SAPinst, GUI server, and SAPinst GUI. SAPinst uses port to communicate with the GUI server. The GUI server uses port to communicate with SAPinst GUI. You get an error message if one of these ports is already in use by another service. In this case, open a command prompt and change to the required directory as follows: <DVD drive>:\im_windows_<platform>. Enter the following command in a single line: sapinst.exe SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server> GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to_sapinst_gui> For a list of all available SAPinst properties, enter the following command: sapinst p. 2. On the Welcome screen, choose Software Life-Cycle Options System Copy <database> Source System <Distribution option> Based on <technical stack>. 3. Select the corresponding system copy option from the tree structure according to the sequence of the process flow for the database-specific or the database-independent system copy procedure. For more information, see Database-Specific System Copy procedure [page 57] or Database-Independent System Copy [page 25]. Caution Make sure that you choose the system copy options exactly in the order they appear for each system variant. 38/136 PUBLIC 03/28/2008

39 4 Database Independent System Copy 4.5 Exporting the Source System Using SAPinst The following table provides an overview about the available installation options available for the export: Export Services for a Central System Export Service Export Preparation You do not perform this step if you use the database-specific method. Database Instance Export You do not perform this step if you use the database-specific method. Remarks Optional step for preparing the export. SAPinst performs the following steps: Creates the export directory structure Creates database structure files (*.STR) Updates database statistics ( ) Calculates the size of the target database (*.EXT,DBSIZE.XML) Mandatory step for database-independent system copy procedure. SAPinst performs the following steps: Creates the export directory structure Creates database structure files (*.STR) Updates database statistics ( ) Calculates the size of the target database (*.EXT,DBSIZE.XML) Exports the ABAP database content 4. After you have selected the required option, choose Next. If you generated SQL files with DDL statements (see Generating DDL Statements [page 29]), copy the generated files into the SAPinst installation directory as soon as it has been created by SAPinst. The installation directory will have been created as soon as the first input screen appears. 5. Follow the instructions in the SAPinst input dialogs and enter the required parameters. Caution You must choose Typical when performing a system copy with database tools. For more information about input parameters in SAPinst, position the cursor on the parameter field and choose F1. 6. Database-specific procedures only: On the screen SAP SystemDatabase Export choose option System Copy Method Use database specific tools. After you have entered all required input parameters, SAPinst starts the export and displays the progress during the processing phase. 03/28/2008 PUBLIC 39/136

40 4 Database Independent System Copy 4.5 Exporting the Source System Using SAPinst Troubleshooting If an export process aborts due to a hardware failure (for example, file system full, power outage, operating system crash), you have to repeat the export of the complete package. Remove the dump files <package>.<nnn>, the TOC file <package>.toc, the log file <package>.log and make sure that all tables in the TSK file <package>.*tsk* have the status flag xeq or err set. If there is not enough disk space in the export directory, the R3load database export fails. You can then find error messages in the log files SAP*.log. You can subsequently move the dump files that have been created from the file system in which the export directory is located to a different file system during the export. Currently there is no possibility to automatically distribute the export over different file systems. If an error occurs during the dialog phase, SAPinst: Stops the export. Displays a dialog that informs you about the error. You can now directly view the log file by choosing View Logs. Finally you must abort the export with OK and try to solve the problem. If an error occurs during the processing phase, SAPinst: Stops the export. Displays a dialog that informs you about the error. You can now: Directly view the log file by choosing View Logs. Try to solve the problem. Continue the export by choosing Retry. Abort the export by choosing OK. Only valid for: UNIX System Copy - export on UNIX (especially for upgraded systems) Symptom: Processes started as <sid>adm or ora<sid> OS users cannot create or open files in the installation directory. Reason: Only members of sapinst UNIX group can access the installation directory. This group is created first by SAPinst starting from NW 7.0 SR1. Solution: Associate <sid>adm and ora<sid> OS users with sapinst group manually if this association is missing. Verify /etc/group file and check if sapinst group exists and OS users are members of this group. If sapinst group does not exist yet, start SAPinst. SAPinst will create this group during startup before product catalog list will be displayed. Edit /etc/group file and associate OS users with sapinst group. 40/136 PUBLIC 03/28/2008

41 4 Database Independent System Copy 4.5 Exporting the Source System Using SAPinst Continue with the export. End of: UNIX For more information, see Using SAPinst GUI [page 119], Interrupted Installation with SAPinst [page 119], and Performing a Remote Export Using SAPinst [page 122]. Only valid for: IBM i5/os Running SAPinst on System i to Perform the Export Preparing the Windows Host for the SAP System Installation The Java-based SAPinst graphical user interface (SAPinst GUI) requires a Java Development Kit (Java 2 SDK, Standard Edition) with graphical capabilities (AWT, Swing). Since System i does not provide a graphical user interface, you must install the JDK on a Windows host to perform the installation with SAPinst. Prerequisites To prepare the system for SAPinst and SAPinst GUI you need to do the following: Necessary operating system versions: Windows NT/2000/2003/XP Check your Java Runtime Environment (JRE) on the host where SAPinst GUI runs, because the JRE cannot be integrated into the SAPinst GUI executable for all platforms due to licensing issues. Set the system path if you install on Windows. Procedure The SAP J2EE Engine requires a Java Development Kit (Java 2 SDK, Standard Edition). Therefore, make sure a valid JDK version is installed on every host on which you want to install an SAP instance including the SAP J2EE Engine. For more information about the JDK versions that are released for the SAP Web Application Server, SAP components based on SAP Web AS and the SAP J2EE Engine, see Product Availability Matrix SAP NetWeaver SAP NetWeaver 04 JSE Platforms 03/28/2008 PUBLIC 41/136

42 4 Database Independent System Copy 4.5 Exporting the Source System Using SAPinst JDK is not part of the SAP shipment. If necessary, you need to download and install it. To check the version of an already installed JDK, enter: java -version If you have more than one Java Virtual Machine (JVM) installed on your system (for example, you have two JDKs with different versions installed), make sure that the JAVA_HOME environment variable is set to the valid <JAVA_HOME> directory. Make sure that %JAVA_HOME%\bin is included in your system path. Only valid for: IBM i5/os IBM i5/os IBM DB2 for i5/os Preparing a Windows User Account and System i User Profile For the installation you need to create a user account on your Windows installation host and a user profile on the System i you want to install. The following requirements apply: The System i user profile and the Windows user account must have the same name and password. Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM The System i user profile must have user class *SECOFR and all special authorities that belong to user QSECOFR. End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM Only valid for: SAP SCM The System i user profile must be the user QSECOFR. This is different to other installations on System i. For other installations, we recommended that you create user SAPINST or SAPINSTUSR. However for SCM, you need to use the user QSECOFR because the livecache client software has to be installed by this special user. End of: SAP SCM The Windows user account must have administrator rights on the Windows installation host. 42/136 PUBLIC 03/28/2008

43 4 Database Independent System Copy 4.5 Exporting the Source System Using SAPinst Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM The user name SAPINSTUSR and the password SAP are used as examples in the procedures. In former installation documentation, we used the user SAPINST. However, in future releases SAP has introduced a group called SAPINST on System i which conflicts with the previously recommended user SAPINST. End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM Windows: 1. Create a local user. 2. Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM In the field User name, enter your installation user name, for example, SAPINSTUSR. End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM 3. Only valid for: SAP SCM In the field User name, enter your installation user name QSECOFR. End of: SAP SCM 4. Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM In the fields Password and Confirm password, enter the password SAP. End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM 5. Only valid for: SAP SCM In the fields Password and Confirm password, enter the password of the user QSECOFR on your System i. End of: SAP SCM 6. Deselect User must change password at next logon. 7. Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM Assign the new user SAPINSTUSR to the group Administrators. End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM 8. Only valid for: SAP SCM Assign the new user QSECOFR to the group Administrators. End of: SAP SCM System i: Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM Enter the command CRTUSRPRF USRPRF(SAPINSTUSR) PASSWORD(SAP) USRCLS(*SECOFR) TEXT( Test User for SAP Installation ) SPCAUT(*USRCLS) LANGID(ENU) CNTRYID(US) CCSID(500). End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM 03/28/2008 PUBLIC 43/136

44 4 Database Independent System Copy 4.5 Exporting the Source System Using SAPinst Only valid for: SAP SCM To change the user QSECOFR, enter the command CRTUSRPRF USRPRF(QSECOFR) LANGID(ENU) CNTRYID(US) CCSID(500). After the installation, you can revert the user profile QSECOFR back to the old values. End of: SAP SCM Caution You should not set the system variable QIBM_PASE_CCSID. You should leave this variable empty! End of: IBM i5/os IBM i5/os IBM DB2 for i5/os Only valid for: IBM i5/os IBM i5/os IBM DB2 for i5/os Installing TMKSVR and Creating an Installation Share 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. In addition, 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. The TMKSVR has to be installed and an installation share has to be created on all System i hosts where instances of an SAP system should be installed. Prerequisites An FTP server running on System i You must prepare a user. For more information about how users are prepared, see Preparing a Windows User Account and System i User Profile [page 42]. The Installation Master DVD must be inserted in the DVD drive of your Windows host. Make sure there is no system variable LANG defining a LOCAL. Otherwise, code page problems might prevent TMKSVR processes from starting. Procedure 1. Log on to your Windows host as the installation user. For more information, see Preparing a Windows User Account and System i User Profile [page 42]. 44/136 PUBLIC 03/28/2008

45 4 Database Independent System Copy 4.5 Exporting the Source System Using SAPinst Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM This user must have the same user ID and password as the user that you are using for the installation on System i (a user with administrator rights similar to QSECOFR). End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM Only valid for: SAP SCM This user must have the same user ID and password as the user that you are using for the installation on System i. For SCM, this user must be QSECOFR). End of: SAP SCM 2. Run SETUP.EXE from the directory IM_OS400_PPC64\TMKSVR on the DVD containing the installation package. You can start the setup program by double-clicking on it in the Windows Explorer. The following dialog box appears: Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM Figure 2: End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM 03/28/2008 PUBLIC 45/136

46 4 Database Independent System Copy 4.5 Exporting the Source System Using SAPinst Only valid for: SAP SCM Figure 3: End of: SAP SCM 3. Enter the following values: System i Hostname: Enter the name of the System i host where you want to install TMKSVR. Only valid for: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM System i Administrator (QSECOFR or similar): Enter the System i user. For more information, see Preparing a Windows User Account and System i User Profile [page 42]. End of: SAP CRM;SAP ERP;SAP NetWeaver;SAP SRM Only valid for: SAP SCM System i Administrator (QSECOFR): Enter the System i user. For more information, see Preparing a Windows User Account and System i User Profile [page 42]. End of: SAP SCM TMKSVR instance number: Leave the value at 0. TMKSVR Instance Port (also referred to as the Dispatcher Port): Leave the value at 59975, if possible. Only change this port number if you encounter problems during installation because the port is in use. Result The installation uses FTP to install and starts the TMKSVR on System i. During installation, a library named TMKSVR<nn> is created, with <nn> being the instance number (for example, TMKSVR00). A NetServer share named ROOTBIN is created on the System i host. You can map the share now to your Windows PC or let SAPinst map it during the installation. 46/136 PUBLIC 03/28/2008

47 4 Database Independent System Copy 4.5 Exporting the Source System Using SAPinst For more information, see the documentation INSTALL.PDF on the DVD in directory IM_OS400_PPC64\TMKSVR. End of: IBM i5/os IBM i5/os IBM DB2 for i5/os Only valid for: IBM i5/os Starting SAPinst on System i Caution This section refers to installation of an instance, which is a synonym for export an SAP system. This procedure tells you how to run SAPinst to install one or more SAP instances. It describes an installation where SAPinst GUI and SAPinst server are running on the same Windows host. SAPinst creates the installation directory \usr\sap\sapinst on System i. Prerequisites Caution Make sure that you shut down all SAP Application Servers before the export. The database must still be running. Otherwise, the target system might be inconsistent. TMKSVR is up and running: WRKACTJOB SBS (TMKSVR00) (there must be a DISPATCH job). For more information, see Installing TMKSVR and Creating an Installation Share [page 44]. The Windows host is set up. For more information, see Preparing the Windows Host for the SAP System Installation [page 41]. The users required for the installation are prepared. For more information, see Preparing a Windows User Account and System i User Profile [page 42]. Make sure that the JAVA_HOME environment variable is set correctly on your Windows host. 1. Log on to the Windows host as the installation user. For more information, see Preparing a Windows User Account and System i User Profile [page 42]. 2. Start SAPinst from the SAP Installation Master DVD in one of the following ways: If using the default installation directory (recommended) by double-clicking sapinst.exe from the following path: <Mapped drive>:<copied... DVD>\IM_OS400_PPC64 03/28/2008 PUBLIC 47/136

48 4 Database Independent System Copy 4.5 Exporting the Source System Using SAPinst During the installation, the default ports SAPinst and are used for communication between SAPinst, GUI server and SAPinst GUI. SAPinst uses port to communicate with the GUI server. You get an error message if one of these ports is already in use by another service. In this case, open a command prompt and change to the required directory as follows: <Mapped drive>:<copied... Enter the following command in a single line: sapinst.exe DVD>\IM_OS400_PPC64 SAPINST_DIALOG_PORT=<free_port_number_sapinst_gui_to_gui_server> GUISERVER_DIALOG_PORT=<free_port_number_gui_server_to sapinst_gui> For a list of all available SAPinst properties, enter the following command: sapinst -p 3. The SAPinst/TMKSVR Session Parameters dialog box appears and prompts you for the target System i parameters. Enter your values. Figure 4: The SAPinst GUI now starts automatically by displaying the Welcome screen. 4. In the Welcome screen, choose Software Life-Cycle Options System Copy <your database> Source System <System Variant> Based on <AS ABAP and AS Java AS Java AS ABAP>. 48/136 PUBLIC 03/28/2008