SAP Note 825473 Note Language: English

IBM i: Online backup as of V5R3M0
Version: 13 Validity:
Valid Since 24.02.2010

Summary
Symptom
This note describes how the online backup without COMMIT boundary, which is available from i5/OS V5R3M0, may be used for SAP systems. This note describes the new parameter *NOCMTBDY, which enables the online backup and explains which objects must be saved for systems using SAP Application Server ABAP (SAP AS ABAP), SAP Application Server Java (SAP AS Java), or SAP Master Data Management (SAP MDM).

Other terms
OS/400, AS/400, ragged, save, V5R3, CPE3029, 3029, EBUSY, iSeries, V5R4, V6R1, ASP, auxiliary storage pool

Reason and Prerequisites
Starting with i5/OS V5R3M0 the possibility also exists of backing up an online database when the associated work processes are not at a COMMIT boundary. In the same way as for older releases, the online backup is selected via the parameter SAVACT(*SYNCLIB) in the backup command (SAVLIB or SAVOBJ). The parameter SAVACTWAIT (wait time) has three components from V5R3M0 onward. 1. Wait time in seconds for object locks. If a backup is taken while the system is active, then the save operation will attempt to obtain a "Shared read no update" (*SHRNUP) lock for the majority of objects. If it does not succeed within the time given here, the backup will abort. During normal SAP system operation, there should be no locks on database objects which would prevent a backup being taken. Wait time for pending record changes. If this value is set to *NOCMTBDY, then the backup will not wait for open transactions to reach a COMMIT boundary. This includes the SQL statements INSERT, UPDATE and DELETE. The wait time for other pending changes. This limit includes changes made by DDL statements, for example, ALTER TABLE. Transactions which use SQL statements of this type must reach a COMMIT boundary before a backup can be executed.

2.

3.

If DDL-Instructions are executed during a save with the value *NOCMTBDY, then the affected work-process will send a query message CPA8351 to the QSYSOPR message queue. The work-process remains in status MSGW until the message is answered. The reply to the message may be 'C' for Cancel or 'R' for Repeat (after waiting). In order to prevent operator replies being necessary during a save, an entry with reply 'R' should be made for the message-id CPA8351 in the System Reply List. If a backup is taken with *NOCMTBDY, then the saved tables may contain partially changed records from transactions which were incomplete at the time the save was made. In order to ensure that restored data will be consistent, in case of data loss, the journal receivers must also be saved and made available in such a way, that the start of each open transaction may be found in the chain of the journal receivers.
07.03.2011 Page 1 of 6

The names consist of the first five characters of the repository name (without underscores). This description is relevant for SAP systems in Release 6. or system i navigator): SELECT MAINDB FROM A2I_MDMDBS/A2I_CATALOGS The column MAINDB contains the names of the main libraries for the repositories. one underscore. Libraries and directories to be saved After the new installation of an SAP system. the letter "m". as described in the installation guide. the libraries A2I_MDMDBS. for example. Please note that *NOCMTBDY for SAVACTWAIT may only be used when the target release for the backup (TGTRLS) is at least V5R3M0.40 (NetWeaver 04) and higher. "REPOS_z000". the names of the libraries that must be saved are derived from the repository names. including the libraries R3SYS and R3<sid>400 will be saved at this time. The kernel library and. the ABAP part is also relevant for lower SAP Releases. the os_libs library Objects that must be saved during an online backup of SAP AS ABAP: o o Library R3<sid>DATA Library R3<sid>JRN Objects that must be saved during an online backup of SAP AS Java: o o Library SAP<sid>DB Library SAP<sid>JRN Objects that must be saved during an online backup of SAP MDM: For SAP MDM in Release 7. <repository>_m<nnn> and <repository>_z<nnn> must be taken into account.SAP Note 825473 - IBM i: Online backup as of V5R3M0 When database tables which were saved with *NOCMTBDY have to be restored with RSTLIB or RSTOBJ.03. 07. Option 21. under SAP WebAS Java. Objects such as user profiles which do not often change. SQLUTIL. To determine the assignment. each repository has a further library that includes history data and for which "m" is replaced with "z". An attempt to use such tables before the application of the journal entries will result in the error messages CPF428D or SQL7008 with reason code 17. During the backup. In addition to this library. and a three-digit number that ensures that the name is unique. they cannot be used before the application of journal entries via APYJRNCHG or APYJRNCHGX. see Note 1390533.1 or higher. The assignment results from the table A2I_CATALOGS in the schema (or library) A2I_MDMDBS. Solution The following gives a description of the execution of an online backup from release V5R3M0. perform the following query in the interactive SQL (STRSQL. for example. For more information about SAP MDM on IBM i. a full backup should be performed via Menu SAVE. "REPOS_m000".2011 Page 2 of 6 .

and MDM): o o o o Directory /sapmnt/<sid> with its subdirectories Directory /sapmnt/trans with its subdirectories Directory /usr/sap/<sid> with its subdirectories Symbolic Link /usr/sap/trans If an independent ASP (iASP) is used: o o o Directory /<asp>/sapmnt/<sid> with its subdirectories Directory /<asp>/sapmnt/trans with its subdirectories Directory /<asp>/usr/sap/<sid> with its subdirectories Some directories cannot be saved online. since the directories only contain temporary data (for example log files). A backup is not necessary. since the processes of an active SAP system lock them.03.2011 Page 3 of 6 . path name depending on the profile parameter es2/filename_prefix) 07. Java. however. The following directories are affected (preceded by /<asp> if you use an Indepentent ASP): o o o o o o o o o o /sapmnt/<sid>/j2ee/cache/* /usr/sap/<sid>/<instance>/SDM/program/log/* /usr/sap/<sid>/<instance>/igs/log/* /usr/sap/<sid>/<instance>/j2ee/cluster/dispatcher/log/* /usr/sap/<sid>/<instance>/j2ee/cluster/dispatcher/temp/* /usr/sap/<sid>/<instance>/j2ee/cluster/server<n>/log/* /usr/sap/<sid>/<instance>/j2ee/cluster/server<n>/temp/* /usr/sap/<sid>/<instance>/j2ee/cluster/server<n>/sapjms/* /usr/sap/<sid>/<instance>/log/* /usr/sap/<sid>/<instance>/work/* It is unnecessary to back up the following files: o o o /sapmnt/<sid>/global/ABAPPROT /sapmnt/<sid>/global/SLOGJ /usr/sap/<sid>/<instance>/data/SAP_ES2_<nn>_* (<nn> = instance number.SAP Note 825473 - IBM i: Online backup as of V5R3M0 Objects that must be saved for all variants (SAP ABAP.

log /usr/sap/<sid>/<instance>/j2ee/cluster/server<n>/slderror. The value for the sub-parameter "Pending record changes" should be set to *NOCMTBDY if you wish to take backups without considering transaction boundaries. Make sure here as well. Make sure that the field "Retain object detail" is set to either *MBR or *YES for all entries which should be saved while active.log Execution of the backup 1. for example. This applies especially to changes in the data dictionary. you can define the use of option *NOCMTBDY in the backup control group. SQLUTIL. or system i navigator): Use the following SQL statement: SELECT FROM WHERE ORDER SRONAM. Save all libraries with the command: SAVLIB LIB(<library>) DEV(<tape device>) SAVACT(*SYNCLIB) SAVACTWAIT(3600 *NOCMTBDY *LOCKWAIT) Save all directories with the command: SAV DEV(/QSYS. SROLIB. On the third screen you will find the parameter group "Save active wait time". SROJRL <yourlib>/<yourfile> SROPRT = '1' BY SROJRN Using option *NOCMTBDY with BRMS If the backup is performed using the IBM software product "Backup Recovery and Media Services for iSeries" (BRMS). if you are working with V5R3M0).03.* /usr/sap/<sid>/<instance>/j2ee/cluster/server<n>/apps/sap. Ater this use the command WRKCTLGBRM with option 8 (Change attributes).DEVD) OBJ((<directory> *INCLUDE).trc /usr/sap/<sid>/<instance>/j2ee/cluster/server<n>/jarm.SAP Note 825473 - IBM i: Online backup as of V5R3M0 o o o o o /usr/sap/<sid>/<instance>/j2ee/cluster/server<n>/*. that the target release is at least V5R3M0 (*CURRENT. In order to establish which tables were saved while transactions were pending and which journal receivers need to be available so that you can recover completely from the backup. you can use SQL (STRSQL.LIB/<tape device>. 07. importing transports.. Make sure that all transactions which contain DDL satements have been completed. 3. you can use the paramter OUTPUT(OUTFILE) on the SAVLIB command. Use the command WRKCTLGBRM with option 2 (Edit the entries) to do this. To query which tables have pending transactions and which is the oldest journal receiver that must be saved.log /usr/sap/<sid>/<instance>/j2ee/cluster/server<n>/security_audit. SROJRN.) SUBTREE(*ALL) SAVACT(*YES) 2.2011 Page 4 of 6 .com/bi~mm r~browser_ea/servlet_jsp/mmr/root/velocity..

Instructions are available in the "Systems management" section under "Backup and recovery-> Recovering your system". enter the command WRKJRN without parameters. In order to do this. the changes recorded in the journal be applied. perform the following steps: 1. Enter QSQJRN as the journal name and the name of your database library. see the IBM online documentation. 3. To do this. Header Data Release Status: Released on: Master Language: Priority: Category: Primary Component: Secondary Components: BC-DB-DB4 DB2 for AS/400 Released for Customer 25. R3<sid>DATA or SAP<sid>DB). This will preset a screen on which you should enter the name of the journal and the library which contains it.02.SAP Note 825473 - IBM i: Online backup as of V5R3M0 Recovery after data loss For information about the recovery of a system after loss of data. at the link http://publib. If the journal receivers (for example. The next step is to establish which journal receivers are necessary for the recovery. In this case. after the restore of the libraries R3<sid>DATA or SAP<sid>DB and the corresponding journal libraries R3<sid>JRN or SAP<sid>JRN. R3<sid>DATA or SAP<sid>DB) and to then use the function key F15 (shift+F3) to display the receiver directory.ibm.2010 08:06:45 German Recommendations/additional info Consulting BC-OP-AS4 IBM AS/400 07. it is only necessary to associate the journal receivers with the journal. The easiest way to do this is to use the command WRKJRNA for the journal QSQJRN in your database library (for example.com/infocenter/iseries/v6r1m0/index. R3<sid>DATA or SAP<sid>DB as the library name. after you restored the database libraries and the journal receivers.1).03. Based on the attach date you can establish which receivers have been attached since the last backup. Now you can apply the journal entries.jsp (IBM i Information Center for Release 6. Use the following command for this: APYJRNCHGX JRN(<database library>/QSQJRN) FILE(<database library>/*ALL) RCVRNG(<journal libray>/<receiver1> <journal libray>/<receiver2>) FRMENTLRG(*LASTSAVE) TOTIME(<time before data loss>) CMTBDY(*YES) OBJERROPT(*CONTINUE) 2.2011 Page 5 of 6 . The next screen displays the journal QSQJRN in the database library list.Associate receivers with Journal for that journal.boulder. in library R3<sid>JRN or SAP<sid>JRN) are in an ASP that differs from the ASP of the database library (for example. for example. Select 9 . then often only the database library has to be restored because the journal receivers have been retained in the separate ASP. It is important that. for example.

/usr/sap/<SID>/SYS/global iSeries: online backup with SAVR3SYS IBM i: SQL error -7008 07.SAP Note 825473 - IBM i: Online backup as of V5R3M0 The Note is release-independent Related Notes Number 1390533 1278155 1061267 1021310 831678 826449 214369 202593 116192 Short Text IBM i: Recommendations for using MDM syst in operating syst Security audit logs separated from other security logs iSeries: Problem analysis for online data backup iSeries: Short dump in RSDB4BFT and incorrect data in DB12 IBM i: Recovery of damaged objects iSeries: Changing the JDBC driver iSeries: 3029.03.2011 Page 6 of 6 . Resource busy.

Sign up to vote on this title
UsefulNot useful