Homogeneous System Copy or Refresh Database Content on IBM i with SWPM using an Existing SAP Database Library
On January 20th, 2019 SL Toolset 1.0 SPS 28 has been released for customers. There is a new feature in the SWPM for SAP on IBM i: You now can do an SAP System Copy or a Refresh Database Content using an already existing SAP database library. So far, you had the option to use the Standard System Copy(R3load-based) method or the Homogeneous System Copy(SAVLIB/RSTLIB-based) method to build up the new SAP database library for your SAP system. Starting with SWPM 1.0 SP28, you can reuse also an already existing SAP database library.
In an earlier blog entry, I already discussed the IBM i-specific Homogeneous System Copy(SAVLIB/RSTLIB-based) method. This method supports the use of a save file to build up the SAP database library when performing a System Copy or a Refresh Database Content. For more information, see the following blog entry: Homogeneous System Copy or DB Refresh on IBM i with SWPM using a save file.
Alternatively, instead of a save file you now can use an already existing SAP database library. In general this SAP database library is a copy of an SAP database library of an existing SAP system like an SAP production system. The new method to use an existing SAP database library was created to help customers with big SAP database libraries. Saving a big library and later restoring this library within an SWPM run can require a lot of space and time. Some customers can use a FlashCopy or other preparation options to provide an SAP database library upfront on the target host. The reuse of the already existing big SAP database library on the target host can save time and space compared to using a save file or an SAP export.
The reuse of the existing SAP database library is straight forward. It is quite similar to using a save file of an SAP DB lib. The recommended steps of a system copy or refresh database content are described in the SAP System Copy documentation. In general, you must do the following steps:
- Prepare the SAP database library on the target host where you plan to do the system copy or refresh database content. It is up to you how you create or copy the SAP database library. For example, when you use the FlashCopy for IBM i, the copied SAP database library will be located on an IASP. For more information about how to prepare the SAP DB lib after a FlashCopy, see the SAP Note 2805638.
Note: Do not change manually the name of the SAP database library on the target host. The SAP database library must keep the original name. Only the SWPM will change the name of the SAP database library, if required.
- Use the SAP system copy guide for IBM i to prepare the Homogeneous System Copy or the Refresh Database Content. Afterwards, start the SWPM as described in the section Running the Installer.
- In the SWPM Welcome screen, choose the option you want to use:
a) <SAP_Product_Name> → IBM Db2 for i → System Copy → Target System or
b) Generic Options → IBM Db2 for i → Refresh Database Content
- Fill the parameter values in the dialog phase of the SWPM as described in the system copy guide. In the dialog SAP System Database, you must select the database copy method Homogeneous System Copy, Use Existing DB Library.
- In the dialog IBM Db2 for i Reuse Existing ABAP|Java Database Library, provide the source <SAPSID> of the SAP database library. (Later the SWPM will use this source <SAPSID> to locate and to check the SAP DB lib.)
- Review all parameters in the Summary screen of the SWPM at the end of the dialog phase and click Next to execute the SAP System Copy Import or the Refresh Database Content.
In the execution phase, the SWPM will adjust the existing SAP database library to the target SAP system. For example, this can be the rename of the SAP database library and the recreation of database objects of type *PGM and *SRVPGM.
SAP recommends that you use the latest SWPM. Currently, this is SWPM 1.0 SP 28 patch level 1. For more information about the latest SWPM, see SAP Note 1680045.
Note: Currently, there is a restriction for the SAP Rename of an SAP System on IBM i. The SAP Rename does not support the IASP. But there is no restriction for the SAP System Copy or the SAP Refresh Database Content on IBM i when reusing an existing SAP database library on an IASP.