User Guide Near Zero Downtime Maintenance for SAPNetWeaver Process Integration 7.3 on Windows Oracle

User GuideNear Zero Downtime Maintenance forSAP NetWeaver Process Integration 7.3on Windows: Oracle

Target Audience• Technology Consultants• System Administrators

Document version: 1.1 ‐ January 23, 2013

Near Zero Downtime Maintenance for SAP Process Integration ‐ User Guide

Document History

CAUTION: Before you start the implementation, make sure you have the latest version of this document.The following table provides an overview of the most important document versions:

Table 1: Document versions

Version Date Description

1.0 November 27, 2012 First version

1.1 January 22, 2013 Updated version ‐ minor changes


Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.1 About This Document . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.2 SAP Notes for the nZDM‐PI Procedure . . . . . . . . . . . . . . . . . . 10

1.3 Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.4 Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.5 Meeting the Requirements of the Production System . . . . . . . . . . . 11

1.6 Meeting the Requirements of the Additional Hardware . . . . . . . . . . 11

1.7 Meeting the Requirements of Support Packages . . . . . . . . . . . . . 12

1.7.1 Meeting the Requirements of the ABAP Support Packages . . . . . . . . . 12

1.7.2 Meeting the Requirements of the Java Support Packages . . . . . . . . . . 12

1.8 Required Passwords During the nZDM‐PI Procedure . . . . . . . . . . . . 12

Chapter 2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.1 Downloading the Required Software . . . . . . . . . . . . . . . . . . 13

2.1.1 Downloading SAP Support Packages . . . . . . . . . . . . . . . . . . . 13

2.1.2 Downloading the Latest SAP Support Package Manager Update . . . . . . . 13

2.1.3 Downloading the nZDM‐PI Software. . . . . . . . . . . . . . . . . . . 14

2.1.4 Making Preparations for the Database . . . . . . . . . . . . . . . . . . 14

2.1.5 Downloading Additional Software . . . . . . . . . . . . . . . . . . . . 14

2.1.6 Downloading the SAP NetWeaver Installation Master . . . . . . . . . . . 15

2.2 Preparing Mounts/Shares in the File System . . . . . . . . . . . . . . . 15

2.2.1 Preparing Mounts/Shares of the nZDM‐PI Procedure . . . . . . . . . . . 15

2.2.1.1 Windows Operating Systems . . . . . . . . . . . . . . . . . . . . . . 16

2.2.2 Making the Central Transport Directory Accessible on the Update Host. . . . 16

2.2.2.1 Windows operating systems . . . . . . . . . . . . . . . . . . . . . . 16

2.3 Unpacking the nZDM‐PI Software . . . . . . . . . . . . . . . . . . . . 17

2.4 Oracle Only: Checking the Undo Management of the Database . . . . . . . 17

2.4.1 Checking Basic Settings of Undo Management . . . . . . . . . . . . . . 17

2.4.2 Checking the Required Undo Retention for the nZDM‐PI Procedure . . . . . 17

2.5 Oracle only: Check tablespace mapping of ABAP data classes . . . . . . . . 19

2.6 Executing ABAP Report SMIGR_CREATE_DDL . . . . . . . . . . . . . . . 19

2.7 Updating CR Content on the Central SLD System . . . . . . . . . . . . . 21

2.8 Creating Database Backup . . . . . . . . . . . . . . . . . . . . . . . 21

2.9 Checking for ABAP Dictionary Inconsistencies . . . . . . . . . . . . . . . 21

2.10 Applying SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.11 Checking Web Services Runtime . . . . . . . . . . . . . . . . . . . . 22

Chapter 3 Setting the System into Business‐Only Mode. . . . . . . . . . . . . . 22

3.1 Releasing the ABAP Workbench Requests Containing Modifications . . . . . 22


3.2 Handling Imports of ABAP Transport Requests and Import Jobs . . . . . . . 24

3.3 Adapting the TMS Configuration . . . . . . . . . . . . . . . . . . . . 24

3.4 Disconnecting the PI System from External User Management Systems. . . . 25

3.5 Locking Dialog Users . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.6 Deactivating the PMI Monitoring . . . . . . . . . . . . . . . . . . . . 26

3.7 Stopping the Redwood Scheduler Application. . . . . . . . . . . . . . . 28

3.8 De‐Scheduling ABAP Background Jobs of PMI . . . . . . . . . . . . . . . 31

3.9 Deactivating Message and BPM Tracing . . . . . . . . . . . . . . . . . 33

3.10 Locking the PI Design Time . . . . . . . . . . . . . . . . . . . . . . . 34

3.11 Setting the SLD into Read‐only Mode . . . . . . . . . . . . . . . . . . 37

3.12 De‐Scheduling ABAP Archiving . . . . . . . . . . . . . . . . . . . . . 39

3.13 De‐Scheduling Java Archiving . . . . . . . . . . . . . . . . . . . . . . 43

3.13.1 De‐Scheduling Java Archiving and Deletion Jobs . . . . . . . . . . . . . . 43

3.13.2 Disabling Security Archiving . . . . . . . . . . . . . . . . . . . . . . 47

3.14 De‐Scheduling Java Jobs . . . . . . . . . . . . . . . . . . . . . . . . 48

3.15 De‐Scheduling SAP and Customer‐Specific Background Jobs. . . . . . . . . 49

3.16 De‐Scheduling Other Customer‐Specific Activities . . . . . . . . . . . . . 51

Chapter 4 Running the nZDM‐PI Procedure . . . . . . . . . . . . . . . . . . . 51

4.1 Steps of the nZDM‐PI Procedure . . . . . . . . . . . . . . . . . . . . 51

4.2 Starting SAPinst . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

4.2.1 Starting SAPinst with the GUI Running on the Server . . . . . . . . . . . . 53

4.2.2 Starting SAPinst with the GUI Running on a Remote Desktop . . . . . . . . 53

4.3 Step 1: Export of the Production System . . . . . . . . . . . . . . . . . 54

4.3.1 Oracle Only: Preparing Flashback Query on the Oracle Database. . . . . . . 54

4.3.1.1 Granting Right for Flashback Query to SAP Database Users . . . . . . . . . 54

4.3.1.2 Adapting Parameter undo_retention . . . . . . . . . . . . . . . . . . 55

4.3.2 Starting Step 1 (SAPinst) . . . . . . . . . . . . . . . . . . . . . . . . 55

4.3.3 Oracle only: Exporting Terminates with Error “snapshot too old” . . . . . . 60

4.3.4 Oracle Only: Modifying the Value of Parameter “undo_retention” . . . . . . 61

4.4 Step 2: Installation of the Update System . . . . . . . . . . . . . . . . 61

4.4.1 Preparing Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

4.4.2 Setting Parameters in SAPinst Dialogs . . . . . . . . . . . . . . . . . . 62


4.4.4 Oracle Only: Installation of Database Software . . . . . . . . . . . . . . 71

4.4.5 Windows Only: Procedure Interruption in Case of Local Windows Users . . . 72

4.4.6 Performing Follow‐Up Activities of Step 2 . . . . . . . . . . . . . . . . 73

4.4.6.1 Logging on OS Level . . . . . . . . . . . . . . . . . . . . . . . . . . 73

4.4.6.2 Stopping the Update System . . . . . . . . . . . . . . . . . . . . . . 73

4.4.6.3 Setting DB Log Mode to “Overwrite” and Restarting the Database . . . . . . 73

4.4.6.4 Changing the Number of AS Java Nodes for the Update System . . . . . . . 74


4.4.6.5 Changing the Gateway Host of Jco Adapters to localhost . . . . . . . . . . 75

4.4.6.6 Deactivating the Connection to Central SLD . . . . . . . . . . . . . . . 77

4.4.6.7 Restarting the SAP Services of the Update System . . . . . . . . . . . . . 79

4.4.7 Do not migrate ABAP Secure Store on update system . . . . . . . . . . . 79

4.5 Step 3: Applying SAP Support Packages on the Update System . . . . . . . 79


4.5.2 Applying SAP Support Packages on the Update System . . . . . . . . . . . 82

4.5.2.1 Applying SAP Java Support Packages on Update System (JSPM) . . . . . . . 82

4.5.2.2 Importing the Latest Support Package Manager Update . . . . . . . . . . 83

4.5.2.3 Applying ABAP Support Packages on the Update System . . . . . . . . . . 83

4.5.2.4 Manual Modification Adjustments and Additional SAP Notes . . . . . . . . 83

4.5.3 Regenerating Existing ABAP Loads on the Update System. . . . . . . . . . 84

4.5.4 Running Report SMIGR_CREATE_DDL on the Update System . . . . . . . . 84

4.5.5 Continuing Step 3 (SAPinst) . . . . . . . . . . . . . . . . . . . . . . 84

4.5.6 Follow‐Up Activities of Step 3 . . . . . . . . . . . . . . . . . . . . . 87

4.5.6.1 Restoring the Default Value of Gateway Host of Jco Adapters . . . . . . . . 87

4.5.6.2 Removing the J2EE Instance . . . . . . . . . . . . . . . . . . . . . . 91

4.6 Step 4: Export of the Update System . . . . . . . . . . . . . . . . . . 92


4.7 Step 5, Uptime: Shadow Import into the Production System . . . . . . . . 98

4.7.1 Preparing Step 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

4.7.1.1 Checking Available DB Space of the Production Database . . . . . . . . . . 98


4.7.3 Preparing Manual Update of the SAP Java Virtual Machine . . . . . . . . 103

4.7.4 High Availability Systems Only: Disabling Failover Capabilities . . . . . . . 104

4.8 Downtime Part of the NZDM‐PI Procedure . . . . . . . . . . . . . . . 104

4.8.1 Checking the PI Alerts . . . . . . . . . . . . . . . . . . . . . . . . 104

4.8.2 Shutting Down the Production System . . . . . . . . . . . . . . . . . 104

4.8.3 Step 5, Downtime: Switching off the Production System . . . . . . . . . 104

4.8.4 Activating the New Version of the SAP Java Virtual Machine . . . . . . . 106

4.8.5 Starting the Production System . . . . . . . . . . . . . . . . . . . . 106

4.8.6 Exiting SAPinst (SAPinst) . . . . . . . . . . . . . . . . . . . . . . . 107

Chapter 5 Follow‐Up Activities . . . . . . . . . . . . . . . . . . . . . . . . 108

5.1 High Availability Systems Only: Enabling Failover Capabilities . . . . . . . 108

5.2 Checking the Missing Secondary Indexes on ABAP tables . . . . . . . . . 108

5.3 Checking the Web Service Environment . . . . . . . . . . . . . . . . 111

5.4 Invalidating the Transport Buffer . . . . . . . . . . . . . . . . . . . 111

5.5 Checking Number Ranges for Tables ADRP and SOFD . . . . . . . . . . 111

5.6 Performing Support Package Stack Post‐Installation Steps . . . . . . . . 112


Chapter 6 Setting the System into Unrestricted Production Mode . . . . . . . . . 112

6.1 Scheduling ABAP Archiving . . . . . . . . . . . . . . . . . . . . . . 112

6.2 Schedule Java Archiving . . . . . . . . . . . . . . . . . . . . . . . 115

6.2.1 Schedule Java archiving and deletion jobs . . . . . . . . . . . . . . . 115

6.2.2 Enabling Security Archiving. . . . . . . . . . . . . . . . . . . . . . 118

6.3 Setting SLD into Default Mode . . . . . . . . . . . . . . . . . . . . 120

6.4 Unlocking the PI Design Time. . . . . . . . . . . . . . . . . . . . . 120

6.5 Activating the Monitoring of PMI . . . . . . . . . . . . . . . . . . . 123

6.6 Scheduling Java Jobs . . . . . . . . . . . . . . . . . . . . . . . . 127

6.7 Scheduling SAP and Customer‐Specific Background Jobs . . . . . . . . . 128

6.8 Scheduling Customer‐Specific Activities . . . . . . . . . . . . . . . . 130

6.9 Unlocking Dialog Users . . . . . . . . . . . . . . . . . . . . . . . 130

6.10 Connecting the PI System to External User Management Systems . . . . . 130

6.11 Adapting the TMS Configuration After the nZDM‐PI Procedure . . . . . . 130

6.12 Rescheduling Import Jobs of ABAP Transport Requests . . . . . . . . . . 130

Chapter 7 Final Cleanup Activities . . . . . . . . . . . . . . . . . . . . . . . 130

7.1 Step 6: Cleaning the Production System . . . . . . . . . . . . . . . . 130

7.1.1 Starting Step 6 (SAPinst) . . . . . . . . . . . . . . . . . . . . . . . 131

7.1.2 Invalidating the Buffer of Table TFDIR . . . . . . . . . . . . . . . . . 134

7.2 Uninstalling the Update System. . . . . . . . . . . . . . . . . . . . 134

7.2.1 Uninstalling the Update System Using the SAP Uninstall Procedure . . . . 134

Chapter 8 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . 140

8.1 Resetting the nZDM‐PI Procedure . . . . . . . . . . . . . . . . . . . 140

8.1.1 Terminating the Procedure. . . . . . . . . . . . . . . . . . . . . . 141

8.1.1.1 Terminating the Procedure in Case of Critical Changes . . . . . . . . . . 141

8.1.1.2 Terminating the Procedure in Other Cases . . . . . . . . . . . . . . . 142

8.1.2 Starting SAPinst for Resetting the nZDM‐PI Changes on the Production System . 142

8.1.3 Performing Manual Actions After the Reset. . . . . . . . . . . . . . . 146

8.2 Contacting SAP Support . . . . . . . . . . . . . . . . . . . . . . . 146

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.com

© Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permis‐sion of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distribu‐tors contain proprietary software components of other soft‐ware vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, Sys‐tem p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, Batch‐Pipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Cor‐poration.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massa‐chusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer and other SAP prod‐ucts and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessOb‐jects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trade‐marks or registered trademarks of SAP France in the United States and in other countries.

All other product and service names mentioned are the trade‐marks of their respective companies. Data contained in this document serves informational purposes only. National prod‐uct specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without repre‐sentation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional war‐ranty.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohib‐ited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

Terms for Included Open Source SoftwareThis SAP software contains also the third party open source software products listed below. Please note that for these third party products the following special terms and condi‐tions shall apply.1. This software was developed using ANTLR.2. gSOAPPart of the software embedded in this product is gSOAP soft‐ware. Portions created by gSOAP are Copyright (C) 2001‐2004 Robert A. van Engelen, Genivia inc. All Rights Reserved.THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY GENIVIA INC AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PUR‐POSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABIL‐ITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARIS‐ING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.3. SAP License Agreement for STLport SAP License Agreement for STLPort between SAP Aktiengesellschaft Systems, Applica‐tions, Products in Data Processing Neurottstrasse 16 69190 Walldorf, Germany (hereinafter: SAP) and you (hereinafter: Customer)a) Subject Matter of the AgreementA) SAP grants Customer a non‐exclusive, non‐transferrable, royalty‐free license to use the STLport.org C++ library (STL‐port) and its documentation without fee.B) By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws, and to all of the terms and conditions of this Agreement.C) The Customer may distribute binaries compiled with STL‐port (whether original or modified) without any royalties or restrictions.D) Customer shall maintain the following copyright and per‐missions notices on STLport sources and its documentation unchanged:Copyright 2001 SAP AGE) The Customer may distribute original or modified STLport sources, provided that:o The conditions indicated in the above permissions notice are met;

o The following copyright notices are retained when present, and conditions provided in accompanying permission notices are met:Coypright 1994 Hewlett‐Packard CompanyCopyright 1996,97 Silicon Graphics Computer Systems Inc.Copyright 1997 Moscow Center for SPARC Technology.Copyright 1999,2000 Boris FomitchevCopyright 2001 SAP AGPermission to use, copy, modify, distribute and sell this soft‐ware and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett‐Packard Company makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.Permission to use, copy, modify, distribute and sell this soft‐ware and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitabil‐ity of this software for any purpose. It is provided “as is” with‐out express or implied warranty.Permission to use, copy, modify, distribute and sell this soft‐ware and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC makes no representations about the suitability of this software for any purpose. It is provided “as is” without express or implied warranty.Boris Fomitchev makes no representations about the suitabil‐ity of this software for any purpose. This material is provided "as is", with absolutely no warranty expressed or implied.Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, pro‐vided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice.Permission to use, copy, modify, distribute and sell this soft‐ware and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. SAP makes no representations about the suitability of this software for any purpose. It is provided with a limited war‐

ranty and liability as set forth in the License Agreement dis‐tributed with this copy.SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications.b) Support and Maintenance SAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore shall be not included.All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions and shall be subject to a separate contract.c) Exclusion of warrantyAs the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the STLport is error‐free, without material defects or suitable for a specific application under third‐party rights. Technical data, sales bro‐chures, advertising text and quality descriptions produced by SAP do not indicate any assurance of particular attributes.d) Limited LiabilityA) Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this (i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or (iii) if based on the failure of a guaranteed attribute.B) If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall depend on the

extent to which its occurrence ought to have anticipated by SAP when concluding the contract, due to the circumstances known to it at that point in time representing a typicaltransfer of the software.C) In the case of Art. 4.2 above, SAP shall not be liable for indi‐rect damage, consequential damage caused by a defect or lost profit.D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR 5,000.E) The Customer shall take adequate measures for the protec‐tion of data and programs, in particular by making backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and its recovery, not‐withstanding the other limitations of the present Art. 4 if this loss could have been avoided by observing this obligation.F) The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees or agents of SAP.4. Adobe Document Services Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries. For information on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer, see SAP Note 854621


Chapter 1: Introduction

1.1 About This Document

This document describes how to apply SAP Support Packages with a significantly reduced down‐time on SAP NetWeaver for Process Integration systems.NOTE: The screenshots in the document are examples. Details displayed on the screenshots such as users f.e. are not valid in every case.

1.2 SAP Notes for the nZDM‐PI Procedure

You must read SAP Note 1435235 (Central nZDM‐PI Note) before you read this documentation as it may contain corrections to this document and further important information about the nZDM‐PI procedure.

1.3 Naming Conventions

1.4 Constraints

User administration

Table 1: Naming Conventions

Term Definition

Production system The PI system that you want to updateThis term is used independently of the system role within your PI sys‐tem landscape (Dev, Test/QA, Prod)

Update system A separate SAP system that is temporarily created during the nZDM‐PI procedure as a copy of the production system and used for the import of the Support Packages

Central instance (CI) host

Host on which the central instance DVEBMGS<no> of the production system is installed

Database (DB) host Host on which the database instance of the production system is installed

Update host Host on which the temporary update system will be installed during the nZDM‐PI procedure

SAP system ID <SID> Three‐character SAP system identifier of the production system

<sid>adm The operating system user from the production system


While the nZDM‐PI procedure is running the user administration on the production system is restricted to business‐critical actions such as changing the password of a user or locking a user. Nevertheless, after the nZDM‐PI procedure has finished you still need to repeat these actions as follow‐up steps.

Production systemDo not restart your production system during the entire nZDM‐PI procedure unless the SAP sys‐tem or the SAP Support asks you to do so.File systemDo not move the DVD in the file system during the execution of the nZDM‐PI procedure steps, unless the procedure asks you to do so.

1.5 Meeting the Requirements of the Production System

NOTE: The production system can be only used for NW usage type PI.Supported release and start SP levels:• SAP NetWeaver 7.30 SP02 or higherSupported SAP Kernel versions:SAP Kernel720 Patch Level 62 or higher Supported operating systems:• Windows ServerFor supported database versions and patch levels, see the Product Availability Matrix (PAM) on the SAP Service Marketplace at http://service.sap.com/pam and SAP Note 1435235.

1.6 Meeting the Requirements of the Additional Hardware

A separate update host is required for the nZDM‐PI procedure. The update host must have the same operating system version as the central instance host of the production system.CAUTION: No instance of the production system must be installed on this host at the beginning of the nZDM‐PI procedure.Memory and local disk space requirements for the update host:• Memory as required for the installation of a small NW WebAS ABAP + JAVA sandbox system is

fully sufficient.• 20 GB disk space for swap files• 10 GB disk space for SAP and database software• 50 GB disk space for the databaseAdditional local disk space on the database host of the production system:• 40 GB space in the database for shadow tables of the nZDM‐PI procedure.• PI archiving and deletion jobs have to be switched off for the duration of the nZDM‐PI proce‐

dure (2 ‐ 4 days). Appropriate additional space is needed in the database depending on your PI archiving volume.

Additional space in the SAP global directory /usr/sap/<SID>/SYS/exe/uc of the production sys‐tem:• 1.5 GB for a temporary directory containing the new SAP kernelAdditional disk space is needed for temporary shares/mounts, which are needed for data exchange between the CI host, DB host and the update host. For the required sizes and possible


physical locations, see section “Preparing Mounts/Shares of the nZDM‐PI Procedure” on page 15.

1.7 Meeting the Requirements of Support Packages

The nZDM‐PI procedure can only be used to apply Support Packages and additional patches for the standard SAP NetWeaver components.

1.7.1 Meeting the Requirements of the ABAP Support PackagesUsing the nZDM‐PI procedure, you can apply ABAP Support Packages and additional patches for the following software components:• SAP_BASIS• PI_BASIS• SAP_ABA• SAP_BW• Modification adjustment transports containing modification adjustments for these compo‐

nents only• Additional SAP Notes for these components• ABAP kernel patchesSupport Packages for additional AddOn components, e.g. Solution Manager Plugins ST_PI or ST_A/PI, have to be applied before or after usage of the nZDM‐PI procedure using the standard procedure. Support Packages for the Solution Manager Plugins ST_PI and ST_A/PI can be applied online without business interruption.

1.7.2 Meeting the Requirements of the Java Support PackagesUsing the nZDM‐PI procedure, you can apply Java Support Packages and additional patches for the SAP NetWeaver usage type “Process Integration”, which are shipped as SCA archives. CAUTION: Do not import the following content during the nZDM‐PI procedure:• Any kind of PI content (neither SAP content nor customer‐specific content)• CR content of the SLD• SPs or updates for any third party software, f.e. third party adapters

1.8 Required Passwords During the nZDM‐PI Procedure

During the entire nZDM‐PI procedure, authentication via passwords is required on different lev‐els (operating system, database, SAP system). Here we provide a list of all required passwords, so


that you can check in the planning phase, whether all passwords are available and which people within your company need to be contacted.

Chapter 2: Preparation

2.1 Downloading the Required Software

You can download the required software, with the exception of the unlimited Java Cryptography extension, from the SAP Service Marketplace (SMP).To access the SMP download area, go to http://service.sap.com/swdc.

2.1.1 Downloading SAP Support Packages

As of SAP NetWeaver 7.3, you need the SAP Solution Manager Maintenance Optimizer to down‐load Support Package Stacks from the SMP. Perform the default steps to download the support package stacks including stack xml.

2.1.2 Downloading the Latest SAP Support Package Manager Update

The nZDM‐PI procedure calls functions of the SAP Support Package Manager (transaction SPAM). Therefore, you need to import the latest SPAM update into your system.1. To download the latest version of the SAP Support Package Manager, go to: http://ser‐

vice.sap.com/swdc ‐>Support Packages and Patches ‐> Browse Our Download Catalog ‐>

Table 2: Required passwords during nZDM‐PI procedure

Level User for OS for DB Additional information

OS key phrase of secure store

http://help.sap.com/saphelp_nw73/helpdata/en/cd/14c93ec2f7df6ae10000000a114084/frameset.htm for details

OS <sid>adm on CI host

OS ora<sid> Oracle on DB host

OS Administra‐tor

Windows on update host (or another user from Adminis‐trators group)

DB SAPSR3 Oracle

DB SAPSR3DB Oracle

DB SYSTEM Oracle

SAP DDIC Client 000

SAP PISUPER PI‐Client (or another user with equivalent per‐missions)

SAP J2EE_ADMIN PI‐Client


Additional Components ‐>SAP SPAM/SAINT UPDATE ‐> SPAM/SAINT UPDATE <rel> ‐> Support Packages.

2. Download file SPAM/SAINT update with the highest version.CAUTION: Do not use SPAM/SAINT version 35, since it cannot be used on the update system due to missing maintenance license. Use version 34; 36 or higher.

2.1.3 Downloading the nZDM‐PI Software

To download the nZDM‐PI software from the SAP Service Marketplace, proceed as follows:1. Go to http://service.sap.com/swdc ‐>Support Packages and Patches ‐> Search for Support

Packages and Patches ‐> A‐Z Index ‐> S ‐> SL Toolset ‐> SL Toolset <release> ‐> Entry by Com‐ponent ‐> nZDM‐PI.

2. Download the following SAR archive:<SAR_NZDM_PI_operating_system>

2.1.4 Making Preparations for the Database

To install the update system, you need to download and extract the database installation

software.1. Download the database installation software and additional patches for your database plat‐

form from the SAP Service Marketplace. For more information, see the database‐specific sec‐tions in the document Installation Guide – <SAP NetWeaver / SAP application> <Technology> on <Operating System>: <Database> at http://service.sap.com/instguidesNW ‐> <Release> ‐> Installation.

2. For Oracle Only: Extract the Oracle installation packages that are provided as self‐extracting rar‐archives on a Windows desk top by double‐clicking the *_part1.exe file. Locate the other *_part<n>.rar files in the same directory. Follow the instructions and specify an empty extraction directory. Make the subdirectory of this extraction directory available on the update host during the installation of the update system. We refer to the path of the direc‐tory on the update host as <DVD_RDBMS_Install> later in this document.Extract the downloaded Oracle Client package in an empty directory. Make this extraction directory available on the update host during the installation of the update system. We refer to the path of this directory on the update host as <DVD_RDBMS_Client> later in this docu‐ment.

2.1.5 Downloading Additional Software

You can download the following additional software updates from the SMP:• SLD component repository content (For more information, see SAP Note 669669)• Third party updates, e.g. updates of third party adaptersCAUTION: These additional software updates cannot be applied during the nZDM‐PI procedure. SLD component repository content can be updated before starting the ZDM‐PI procedure online on the production system without business interruption. For more information, see section “Updating CR Content on the Central SLD System” on page 21.

http://service.sap.com/instguidesNW


2.1.6 Downloading the SAP NetWeaver Installation Master

To uninstall the update system after completion of the nZDM‐PI procedure, you can use the dein‐stallation option of the SAP NetWeaver Installation Master. For different de‐installation options, see “Uninstalling the Update System” on page 134. If you plan to reuse the update system within the nZDM‐PI procedure for another PI system, we recommend that you use the de‐installation option of the SAP NetWeaver Installation Master. This de‐installation option will not un‐install the database software, and so re‐installation of the database software will not be required during the next run of the nZDM‐PI procedure.To download the SAP NetwWeaver Installation Master from the SMP download area, proceed as follows:1. Go to http://service.sap.com/swdc ‐> Installations and Upgrades ‐> Browse Our Download

Catalog ‐> SAP NetWeaver and complementary products ‐> SAP NETWEAVER .2. Select your release.3. Choose Installation or Upgrade.4. Select your operation system.5. Select your database platform.6. Download all components of the Installation Master package.

2.2 Preparing Mounts/Shares in the File System

2.2.1 Preparing Mounts/Shares of the nZDM‐PI Procedure

During execution of the nZDM‐PI procedure data of the file system has to be exchanged between the CI host and the update host. All of this data resides within dedicated directories, which are empty at the beginning of the procedure and which are read and written both from the CI host and the update host:

We recommend that you make these directories available both on the CI host and the update host via fast (at least 100 Mbits/sec) and reliable network file systems. The physical devices, on which these directories are located, may be chosen arbitrarily, as long as fast and reliable access from both the CI host and the update host can be provided.

Table 3: Mounts/Shares of the nZDM‐PI Procedure

Identifier used in this document

Content descriptionRequired

size

Typical physical location

<DVD_NZDM_PI> n software, process control data and logs 3 GB CI host or update host

<Export1> Export data from the production system 10 GB CI host or update host

<Export2> Export data from the update system after SP update

10 GB Update host


For a suggestion on which host the physical devices may be located. see column “Typical physical location”. This suggestion also corresponds to the disk space requirements described in section “Meeting the Requirements of the Additional Hardware” on page 11.CAUTION: The path length for <DVD_NZDM_PI> must not exceed 26 characters on both the CI host and the update host due to some length restriction in the SAP kernel. Choose intermediate exports/shares, if necessary.

1. On the corresponding devices, create the following empty directories:• DVD_NZDM_PI• Export1• Export2

2.2.1.1 Windows Operating Systems

1. Choose appropriate devices for the three required directories.2. On the corresponding devices, create the following empty directories:

• DVD_NZDM_PI• Export1• Export2

3. Grant full file permissions for group administrators on these three directories.Share either these directories or some appropriate parent directory/ies in the network.

4. For the DVD directory, make sure that you have SAP_<SID>_GlobalAdmin permissions added to allow read access for the ABAP tools. Missing access might cause remote function call error when the update system is prepared for applying support packages.

5. Log on as user <sid>adm to the CI host. Map the shares on drive letters. Verify user <sid>adm has full permissions on the three directories on the CI host.

6. Log on as domain user <sid>adm to the update host. Map the shares on drive letters. Verify user <sid>adm has full permissions on the 3 directories on the update host.

7. Only if you do not use Windows domains: Log on as user from Administrators group to the update host. Map the shares on drive letters. Verify this administrator user has full permis‐sions on the three directories on the update host. Use the same user, when later starting step 2 of the procedure.

CAUTION: It is required, that the directory <DVD_NZDM_PI> is accessible from a drive letter on both the CI host and the update host. You cannot use an UNC path for the directory <DVD_NZDM_PI>.

2.2.2 Making the Central Transport Directory Accessible on the Update Host

For all SAP systems in a system landscape use a common central transport directory. This central transport directory needs to be accessible on the update host in order to store transport logs from the ABAP Support Package import here and make these available on the production system at the end of the nZDM‐PI procedure.

2.2.2.1 Windows operating systems

Verify members of Administrators group can access and have full permissions on the follwoing directory and its sub directories on the update host:


\\<SAPTRANSHOST>\sapmnt\trans

2.3 Unpacking the nZDM‐PI Software

To unpack the downloaded SAR archives, proceed as follows:1. Log on as user <sid>adm on the central instance host.2. Extract archive <SAR_NZDM_PI_operating_system> to folder <DVD_NZDM_PI>.CAUTION: The DU directory below folder <DVD_NZDM_PI> which is created on archive extrac‐tion is required as a container for the data unit subdirectories NZDM_PI and SAPINST_<operating_system>. The content of the directory <DVD_NZDM_PI> will be modified during the nZDM‐PI procedure and cannot be reused for a second system. Create a new directory <DVD_NZDM_PI> for each system you want to update using the nZDM procedure and copy the initial content of <SAR_NZDM_PI_*> to <DVD_NZDM_PI>, as described in this section.

2.4 Oracle Only: Checking the Undo Management of the Database

Within the nZDM‐PI procedure parts of the database of the PI production system are exported in parallel with running production processes. In order to export a consistent state of the database, the nZDM‐PI procedure uses Oracle flashback query, which allows to select the content from tables, which did exist at a well‐defined point‐in‐time in the past. The Oracle database uses undo data to reconstruct the content of tables from the past. Such a flashback view back into the past is only possible, if all required undo data is still available.So for the nZDM‐PI procedure it is essential that undo data from the beginning of the export is still available at the end of the export, since the choosen point‐in‐time for the flashback query is the beginning of the export.To check the undo management of the database, log on to the database host as OS user ora<sid>, and type in a terminal window:

sqlplus /nologconnect /as sysdba

Keep this sqlplus window open to execute the sql statements of the following sub‐chapters in this window.The sql statements of the following sub‐chapters can also be found in the file:<DVD_NZDM_PI>/DU/NZDM_PI/prepare/oracle/CheckUndoManagement.sql

2.4.1 Checking Basic Settings of Undo Management

1. Check, if automatic undo management is turned on.

Select value from v$parameter where name = 'undo_management';

2. Contact your database administrator if the database is running with manual undo manage‐ment.The returned value must be ‘AUTO’ before you can start the nZDM‐PI procedure.

2.4.2 Checking the Required Undo Retention for the nZDM‐PI Procedure

As first step define the time, you want to reserve for the nZDM export without loss of undo infor‐mation. Denote this time in seconds as required_ur (required undo retention):• If you run the procedure for the first time on a test system, where you typically will not have

very high database activity during the export, choose a value of at least 43200 seconds (12


hours). Though the export will take much less than 12 hours, you will have time buffer in case the export is interrupted for any reason, and can be restarted.

• When you run the procedure on your production system, use your experiences from test sys‐tems, on how long the export takes on your hardware. Usually a value of 7200 seconds (2 hours) will be sufficient, but it may be significantly less on powerful hardware.

Next determine the current undo retention time, and possible values for the undo retention time, based on the current size of tablespace PSAPUNDO and on pessimistic (high) or optimistic (average) assumptions on the database activity during the nZDM‐PI export. Statistical info on database activity during the last 4 days is used here. If the database was down during the last 4 days or was used in an untypical way, the result will be less reliable:

select to_number(par.ur) as "current_ur [sec]",round(df.undo_size/(ts.block_size*pess.rate))as "pessimistic_ur [sec]",round(df.undo_size/(ts.block_size*opt.rate))as "optimistic_ur [sec]" from(select value as ur from v$parameterwhere name = 'undo_retention') par,(select sum(bytes) as undo_size from dba_data_fileswhere tablespace_name = 'PSAPUNDO') df,(select block_size as block_size from dba_tablespaceswhere tablespace_name = 'PSAPUNDO') ts,(select max(undoblks/((end_time - begin_time)*3600*24))as rate from v$undostat) pess,(select sum(undoblks)/(sum(end_time - begin_time)*3600*24)as rate from v$undostat) opt;

The result may look like this (in this example for a test system with low database activity):current_ur [sec] pessimistic_ur [sec] optimistic_ur [sec]---------------- -------------------- ------------------- 43200 582443 1108310

Write down the values for current_ur, pessimistic_ur, and optimistic_ur. They may be needed by the SAP support in case of any questions.As final step decide whether any measures are required:• If pessimistic_ur < required_ur:

You first may decrease your choice of required_ur, if you have choosen a large time buffer for the export duration in the first step. If pessimistic_ur is still less than required_ur, contact your database administrator:• If tablespace PSAPUNDO is set to auto‐extensible, make sure that you have enough disk

space on the DB server to auto‐extend tablespace PSAPUNDO in the ratio required_ur/pessimistic_ur and the MAXBYTES settings of the data files of tablespace PSAPUNDO allow this auto‐extension.

• If tablespace PSAPUNDO is fixed‐sized, extend tablespace PSAPUNDO in the ratio required_ur/pessimistic_ur.

• If current_ur < required_ur:The database parameter undo_retention needs to be changed before and after step 1 of the nZDM‐PI procedure. This is described in detail in chapter “Step 1: Export of the production


system”. Make sure that you have the values for current_ur and required_ur available. Con‐tact your database administrator, if necessary.

2.5 Oracle only: Check tablespace mapping of ABAP data classes

During the database export steps within the nZDM‐PI procedure, information on the appropriate tablespace in the target database is retrieved for each ABAP data class. To make sure that no invalid tablespace names are used in this mapping, perform the following steps:1. Log on to the ABAP system in client 000 as user with system administrator authorizations,

and start TA SE162. For each of the tables TAORA, IAORA, TSORA enter the table name, and choose Table con‐

tents (F7) and then Execute (F8)3. Check whether the tablespace names in columns TABSPACE (for each of the tables TAORA,

IAORA, TSORA) and INDSPACE (for TSORA) are existing tablespaces on the databaseUsually only the following values are shown in columns TABSPACE and INDSPACE:PSAPSR3PSAPSR3<current_release>PSAPSR3USRIf you find any invalid tablespace names, contact the SAP support on how to fix the mapping.

NOTE: Make sure that you have enough disk space for the log archives or an appropriate log

archive housekeeping.

2.6 Executing ABAP Report SMIGR_CREATE_DDL

ABAP report SMIGR_CREATE_DDL checks for DB specific adaptations of database tables, which do not match the standard way, how database tables are created from the SAP data dictionary. Such tables have to be treated in a special way in the nZDM‐PI procedure.Though such adaptations are rather untypical for PI systems, We recommend that you check the system before starting the nZDM‐PI procedure. In case, you are not absolutely sure, that no such adaptations exist in your system, proceed as follows.Log on to the ABAP system in client 000 as user with system administrator authorizations, and start TA SE38.


Enter “SMIGR_CREATE_DDL” in the field program and choose Execute.

On the selection screen in section “Target Database” select the database type of your PI system, and in section “Additional Parameters” in field “Installation Directory” enter a valid path to an existing empty directory on the application server, you are logged on to. Choose Execute.After a successful execution, check whether files have been created in the “Installation Direc‐tory” or not.Depending on the result, select one the following options:


• If the directory is empty or contains just a single file SQLFiles.LST containing comment lines only, no DB specific adaptations of database tables do exist in your system. You can run the nZDM‐PI procedure as described in this document.

• If the directory contains files other than SQLFiles.LST, further checks are required. In this case, contact the SAP Support and send all the files in the directory (including SQL-Files.LST) for analysis.

2.7 Updating CR Content on the Central SLD System

On the new SP level your PI system may require updates of the CR content on your central SLD system. Updating CR content is not included within the nZDM‐PI procedure, even if your central SLD is running on your PI system.We recommend that you perform all required updates of CR content before starting the nZDM‐PI procedure. This can be done in any case and without interruption of the productive use of your PI system, since CR content always is completely downward compatible.For more information about the required versions of the CR content and for documentation of the update procedure, see SAP Note 669669.

2.8 Creating Database Backup

Before you start the nZDM‐PI procedure make sure that you can perform a fast point‐in‐time recovery of the production database in emergency cases.We recommend that you create a full online database backup shortly before starting the nZDM‐PI procedure. Also make sure that all database log files that are required for a point‐in‐time recovery based on this backup can be easily accessed in emergency cases.CAUTION: It is not sufficient to make sure that a recovery is possible to only that point‐in‐time, when the nZDM‐PI procedure was started, since this would not include subsequent production changes on the database that still occur in parallel with the running nZDM‐PI procedure.

2.9 Checking for ABAP Dictionary Inconsistencies

Before starting the nZDM‐PI procedure, you need to make sure that no DB tables or indexes are missing. Proceed as follows:1. Call transaction DB02.2. Choose Missing Tables/Indexes.3. Check if any tables or indexes are missing in the database.

If this is the case, you need to create these tables using the Database Utility option of trans‐action SE11.

2.10 Applying SAP Notes

Before starting the nZDM‐PI procedure, you need to apply specific SAP Notes in order to avoid known issues. The following list contains these SAP Notes:

• SAP Note 1604658: Preventing RFC during mass conversion


2.11 Checking Web Services Runtime

Before starting the nZDM‐PI procedure, you need to make sure that there are no unprocessed designtime object changes for web service runtime. Proceed as follows:1. Call transaction WSUPDATECHECK.2. Choose Execute.3. Check and make sure that there are no entries left.

Chapter 3: Setting the System into Business‐Only Mode

During the overall nZDM‐PI procedure, the production system can only be used in a restricted production mode.All standard PI scenarios are fully available during in this Business‐Only mode. See the following examples:• Synchronous/asynchronous messages• EOIO (Exactly Once in Order), ccBPM (Cross‐Component Business Process Management)• IDOC, PlainHTTP, file adapter etc.)• Mapping (including value mapping)• Partner adapters (Seeburger, Atos, iWay etc.)• PI monitoring and alertingSystem restrictions during the nZDM‐PI procedure are f.e.:• Supported systems may run PI functionality only• System access is restricted to selected users• Archiving jobs are de‐scheduled during the nZDM‐PI procedure• No configuration and design time changes• No transports/deployments into the PI system

3.1 Releasing the ABAP Workbench Requests Containing Modifications

If any SAP Notes have been installed on your system or modifications of the SAP standard have been made, the corresponding ABAP workbench requests must be released, before you can import Support Packages.CAUTION: It will not be possible, to release workbench requests on the update system later in the nZDM‐PI procedure. So it is essential to execute this section on the production system, before you start the nZDM‐PI procedure.Log on to the ABAP system in the PI client and run transaction SE03.


Choose Transport Organizer Tools ‐‐> Requests/Taks ‐‐> Find Requests.

Enter the following values on the Requests (Free Selection) screen:Owner: *Request Status

Select Modifiable and Release Started.Open the drop‐down list of field “Request Type”.


Choose Deselect All, then select the Workbench request checkbox and choose Continue.Back on the selection screen, choose Execute.If any requests are found, these have to be released, if they contain any objects owned by SAP. Contact the owners of the found requests, to release these.Finally run the selection again to make sure that no further open workbench requests containing objects owned by SAP do exist.

3.2 Handling Imports of ABAP Transport Requests and Import Jobs

NOTE: Contact your transport administration to follow the directions described in this section.Before starting the nZDM‐PI procedure, make sure that all ABAP imports into the production sys‐tem have been finished. Make also sure that there are no broken import jobs caused by termi‐nated tp processes that have not yet been restarted and completed.If you have scheduled any automatic import jobs into the production system, you need to de‐schedule these before starting the nZDM‐PI procedure.

CAUTION: During the nZDM‐PI procedure, do not use transaction STMS in the production sys‐tem. In particular, do not perform any actions within this transaction such as checking the trans‐port tool.

3.3 Adapting the TMS Configuration

NOTE: Do not configure the production system as TMS domain controller or backup controller during the nZDM‐PI procedure.Before starting the nZDM‐PI procedure, proceed the following steps:1. Make sure that the TMS configuration is distributed in the whole TMS domain.


2. If the production system is configured as domain controller, first exchange the roles of domain controller and backup controller.

3. If the production system is configured as backup controller, configure a different system as backup controller

Only exceptions:• 1 system landscape: The production system remains in the role of domain controller• 2 system landscape: Configure the production system as backup controllerCAUTION: You must not perform the following actions during the execution of the nZDM‐PI pro‐cedure:• Changing the TMS configuration even not for systems different from the production system

If configuration changes are necessary for any reason, re‐distribute the TMS configuration into all systems of the TMS domain after finishing the nZDM‐PI procedure.1 system landscape: Configuration changes get lost after the nZDM‐PI procedure ends. All configuration changes have to be repeated manually as a follow‐up activity of the nZDM‐PI procedure.

• Changing the TMS configuration during execution of the nZDM‐PI procedure in your nZDM‐PI update system.

3.4 Disconnecting the PI System from External User Management Sys‐tems

If you are using an external user management system for maintaining user master data in your PI system, the PI system must be disconnected from this external system during the nZDM‐PI pro‐cedure.CAUTION: User master data, authorizations and user roles must not be changed, while the nZDM‐PI procedure is running.The following security sensitive operations can be executed without restrictions while the nZDM‐PI procedure is running:• Change user passwords• Lock/unlock users

3.5 Locking Dialog Users

We recommend that you restrict system access to those system dialog users, who are needed for running PI scenarios, and named administrator users, who are involved into the execution of the nZDM‐PI procedure or require system access for system monitoring.Lock any unneeded dialog users in all system clients within the ABAP user management.CAUTION: Dialog users, who login to the PI system during the nZDM‐PI procedure and run arbi‐trary transactions within the system, may cause unexpected change operations. These unex‐pected change operations will be detected by the nZDM‐PI procedure before the downtime phase, and require investigation by the SAP support. In case these unexpected change opera‐tions do not comply with the nZDM‐PI procedure, the nZDM‐PI procedure must be terminated and re‐started from the beginning.


3.6 Deactivating the PMI Monitoring

If you have configured the Process Monitoring Infrastructure (PMI) for your production system, the monitoring must be deactivated.CAUTION: PMI use requires table size housekeeping according to SAP Note 1450445. In particu‐lar, tables SSPICSTRHEAD and SSPICSTRPL might grow significantly and must be therefore kept to a limited size.During deactivation an ABAP background job “$SPI_TRANSPORT” is scheduled, which must be finished, before the nZDM‐PI procedure may be started. For this reason you can already deacti‐vate PMI some hours before the planned start of the nZDM‐PI procedure.Start the PI Runtime Workbench:

http://<ci_host>:5<instance_no>00/rwb

Log on as user with full administration permissions in the PI Runtime Workbench, choose OK and then Configuration.


If Single‐Sign‐On is not set up for your user, enter the log‐on data again.Choose Display.

If there is an active configuration, choose Deactivate Monitoring above section “Configuration Of ...”.


3.7 Stopping the Redwood Scheduler Application

For the business‐only mode, you need to stop the Redwood Scheduler Application. This applica‐tion is not used by any of the PI scenarios but accesses database tables when it is running.Start the SAP NetWeaver Administrator:

http://<ci_host>:5<instance_no>00/nwa


Log on as a user with system administration permissions.

Choose Operation Management, choose Systems, and then choose Start& Stop.


Choose tab Java EE Application, enter redwood.com in the filter row of column Vendor, and hit the Enter key.

Select scheduler‐ear, and choose Stop ‐> On All Instances and Set “Stopped” as Initial State.Finally, log off from the SAP NetWeaver Administrator.


3.8 De‐Scheduling ABAP Background Jobs of PMI

Even if you did not configure the Process Monitoring Infrastructure (PMI), there may be sched‐uled ABAP background jobs of PMI. We recommend that you process this chapter in any case, even if you had never configured PMI on your production system.Log on to the ABAP system in the PI client and run transaction SM37.

Enter the following values on the Simple Job Selection screen:Job Name: *User Name: *Job status

Select Released, Ready, ActiveJob start condition

From: <current_date> To: 31.12.9999or after event: *

Job step

ABAP program name: SPI_*Choose Execute.


Select all jobs in status released, except the job with name “$SPI_TRANSPORT”, choose Job ‐‐> Released ‐‐> Scheduled.CAUTION: Do not change the status of job “$SPI_TRANSPORT” (with a dollar‐sign as first charac‐ter), if it is listed. This job has been scheduled while deactivating PMI and must be finished, before you start the nZDM‐PI procedure.

Repeat the selection in SM37 periodically, to check wheather job $SPI_TRANSPORT is still run‐ning or has finished.


3.9 Deactivating Message and BPM Tracing

Log on to the ABAP system in the PI client and run transaction SXMS_TRC.

If there are any active trace catalog entries, deactivate these from the menu “Trace”.Next run transaction SWF_TRC.


If there are any active trace catalog entries, deactivate these from the menu “Trace”.

3.10 Locking the PI Design Time

Open the PI Exchange Profile: http://<ci_host>:5<instance_no>00/exchangeProfile

Log on as user with full PI design time permission. When prompted, whether you want to use the


old or the new user interface, choose the one you prefer. The following screenshots show the old user interface, but the navigation steps are identical in both user interfaces.

Expand the node “Integration Builder”, and scroll down to parameterscom.sap.aii.ib.server.upgrade_modecom.sap.aii.ib.server.upgrade_users

Choose the com.sap.aii.ib.server.upgrade_mode parameter.


Enter True and save your entry.Next choose the com.sap.aii.ib.server.upgrade_users parameter.

Enter the name of an PI‐administrator user who shall be permitted to do design time changes in emergency cases during the nZDM‐PI procedure and save your entry.


3.11 Setting the SLD into Read‐only Mode

Only applicable, if your SLD resides within the PI system.http://<ci_host>:5<instance_no>00/sld

Log on as user with role SAP_SLD_ADMINISTRATOR (e.g. J2EE_ADMIN).

Choose Administration.


Choose Settings.

Choose Section Server Settings.


Choose Write Protection “Read‐Only”.Save your entry.

Check and deactivate SLD content sync Jobs: Administration ‐> Synchronization ‐> Select all sync subscriptions ‐> Deactivate

3.12 De‐Scheduling ABAP Archiving

ABAP archiving and deletion jobs must be de‐scheduled during the nZDM‐PI procedure.Log on to the ABAP system in the PI client and run transaction SXMB_ADM.


Choose Integration Engine ‐‐> Administration ‐‐> Schedule Archiving Jobs.

Choose Job Overview.


Adapt the following data on the selection screen:Job name: SAP_BC_XMB_ARCHIVE* Job status: Select Released, Ready, ActiveJob start condition

From: <current_date> To: 31.12.9999 Choose Execute.

Select all jobs in status Released and choose Job ‐‐> Delete.


CAUTION: Make sure, no job is in status “Ready” or “Active”, before you start the nZDM‐PI proce‐dure. If you still can see jobs in status “Ready” or “Active”, wait for them to finish.In all cases repeat the steps above until no jobs are found matching the selection criteria.Again run transaction SXMB_ADM and choose Schedule Delete Jobs.

Choose Jobs.

Adapt the following data on the selection screen:Job name: SAP_BC_XMB_*DELETE_*


Job status: Select Released, Ready, ActiveJob start condition

From: <current_date> To: 31.12.9999 Choose Execute.

Select all jobs in status Released and choose Job ‐‐> Delete.CAUTION: Make sure, no job is in status “Ready” or “Active”, before you start the nZDM‐PI proce‐dure. If you still can see jobs in status “Ready” or “Active”, wait for them to finish.In all cases repeat the steps above, until no jobs are found matching the selection criteria.

3.13 De‐Scheduling Java Archiving

Java archiving and deletion jobs and security archiving must be de‐scheduled during the nZDM‐PI procedure.

3.13.1 De‐Scheduling Java Archiving and Deletion Jobs

Start the PI Runtime Workbench:http://<ci_host>:5<instance_no>00/rwb


Log on as user with full PI runtime administration permissions and choose Component Monitor‐ing.

Choose Display.


Choose Integration Server ‐‐> Adapter Engine <SID> and scrolls down to the Status tab page.

Choose Background Processing.In the Popup “Background Processing: Job Configuration”, there will be displayed an overview of all jobs, which are available on the chosen Adapter Engine. In the column “Job Type”, you will find the type of the respective job. As it is possible to configure multiple Jobs of one kind, it is possible, that there is more than one job of the type “Archive” or “Delete” available.


CAUTION: It is important to keep the right order while switching these jobs OFF. FIRST deactivate all deletion jobs, THEN deactivate all archiving jobs.Select the first job of type “Delete” and choose Edit.

Deselect the Active checkbox, enter a valid start date/time and save your entries.Repeat this action for each job of type “Delete”, and then for each job of type “Archive”.CAUTION: Make sure, that you have deactivated all jobs of type “Delete”, before you deactivate any job of type “Archive”.


Finally close the Popup “Background Processing: Job Configuration”.

3.13.2 Disabling Security Archiving

In the still open “Adapter Engine” view

choose Security Archiving.The Popup “Message Security Archiving Monitor” opens.

In the field “Start Archiving Session” enter: 31.12.9999


For “Archiving Interval” select 1 day.Choose Update Archiving Settings.

The Next Archiving Session text box now displays, that no archiving is scheduled.CAUTION: Do not manually repeat any stopped archiving session, while the nZDM‐PI process is running.

3.14 De‐Scheduling Java Jobs

Any Java jobs, which are not essential for running PI scenarios and can be omitted for a period of one to two days, must be de‐scheduled.CAUTION: Java jobs that run during the nZDM‐PI procedure may cause unexpected change oper‐ations. These unexpected change operations will be detected by the nZDM‐PI procedure before the downtime phase, and require investigation by the SAP support. In case these unexpected change operations do not comply with the nZDM‐PI procedure, the nZDM‐PI procedure must be terminated and re‐started from the beginning.To de‐schedule Java jobs, perform the following steps:1. Open the NetWeaver Administrator at http://<host>:<instance number>00/nwa.2. Log on as AS Java administrator.3. Choose Operation Management ‐> Jobs.4. Choose Java Scheduler.5. Select tab Tasks.


6. De‐schedule the following Java jobs by choosing Hold:

3.15 De‐Scheduling SAP and Customer‐Specific Background Jobs

Any background jobs, which are not essential for running PI scenarios and may be omitted for a period of one to two days, must be de‐scheduled.CAUTION: Background jobs running during the nZDM‐PI procedure may cause unexpected change operations. These unexpected change operations will be detected by the nZDM‐PI proce‐dure before the downtime phase, and require investigation by the SAP support. In case these unexpected change operations do not comply with the nZDM‐PI procedure, the nZDM‐PI proce‐dure must be terminated and re‐started from the beginning.To de‐schedule background jobs, log on to the ABAP system in the PI client and run transaction SM37.

Enter the following values on the selection screen:Job Name: *User Name: *Job status

Check “Released”, “Ready”, “Active”Job start condition

From: <current_date> To: 31.12.9999

Table 4: Java Jobs to be De‐Scheduled

Job Name Default Job Frequency

CleanupJobTask_Default Weekly


or after event: *ABAP program name:Choose Execute.

Investigate the found background jobs by double‐clicking on the job. Typically periodic back‐ground with a daily or even longer period can be de‐scheduled for 1 – 2 days.The following table displays the SAP default background jobs to be de‐scheduled (this list may not be complete):

Table 5: SAP Standard Background Jobs to be De‐scheduled

Job nameSAP default job frequency (double‐click on

job)

EU_PUT daily

EU_REORG daily

DBA:CHECKDB* weekly

DBA:CLEANUPLOGS* weekly

DBA:VALIDSTRUCT* weekly

SAP_CCMS_CPH_REORG weekly

SAP_REORG_JOBS weekly

SAP_REORG_XMILOG weekly

SAP_REORG_JOBSTATISTIC monthly


CAUTION: Do not de‐schedule any job RDDIMPDP*, since these are needed while running the nZDM‐PI procedure.For jobs identified for de‐scheduling proceed as follows:• If the job has status “Released”, mark it and choose from the menu “Job” ‐> “Released ‐>

Scheduled”.• If the job has status “Ready” or “Active”, wait until it has finished, before you start the nZDM‐

PI procedure

3.16 De‐Scheduling Other Customer‐Specific Activities

During the entire nZDM‐PI procedure avoid any activities on the system that are not essential for running PI scenarios. We recommend that you deactivate or de‐schedule all customer‐specific activities.NOTE: To avoid data inconsistencies, do not perform deployment or customer configuration activities in transaction SM53. For the same reason, do not refresh your cache while the nZDM‐PI procedure is running.

Chapter 4: Running the nZDM‐PI Procedure

4.1 Steps of the nZDM‐PI Procedure

The nZDM‐PI procedure consists of the following six steps:1. Step 1 ‐ Export of the production system2. Step 2 ‐ Installation of the update system3. Step 3 ‐ Applying Support Packages on the update system4. Step 4 ‐ Export of the update system5. Step 5 ‐ Uptime part: Shadow import into the production system

Downtime part: Switch to the production system6. Step 6 ‐ Clean‐up of the production systemNOTE: Each step must be executed on a specific host that is indicated in this document.The following figure gives an overview of the six steps of the nZDM‐PI procedure:

SAP_XMB_PERF_AGGREGATE hourly

SAP_XMB_PERF_REORG hourly

Table 5: SAP Standard Background Jobs to be De‐scheduled

Job nameSAP default job frequency (double‐click on

job)


During the execution of steps 1 to 4 and of the uptime part of step 5, you change your PI produc‐tion system to the Business‐Only mode, which means that your production system is still up and running and all PI scenarios are executable. During the uptime part of step 5, the shadow import takes place to prepare the switch to the updated PI production system.At the end of step 5, the nZDM‐PI procedure stops and waits for your confirmation to execute the downtime phase. This requires a shutdown of the PI production system before the nZDM‐PI procedure switches it to the new SP level.After step 5 has finished, the PI production system is available on the new SP level. You need to perform some additional activities to set it from the Business‐Only mode to the standard mode. During the run of the step 6, the nZDM‐PI procedure removes temporary data from the system in order to free space in the database and in the file system.NOTE: Do not execute step 6 before your updated PI system has been running productively for at least seven days without issues. The temporary nZDM‐PI data may be needed by SAP support in case you encounter any issues with your PI system running on the new SP level. We recommend that you create a full online backup of the database of the production system before executing this step.

4.2 Starting SAPinst

Most parts of the nZDM‐PI procedure are executed in an automated way controlled by SAP’s installation and update program SAPinst. SAPinst consists of a server component, which has to be started on a dedicated host, and a GUI component, which can be started either on the same server or on remotely on a Windows desktop or a UNIX/Linux workstation.Sapinst runtime is self extracted to a temporary folder, which might be affected by temporary folder cleanup jobs. To avoid this set environment variable TEMP to the path to an existing folder


which is not being cleaned up automatically. Sapinst evaluates environment variables TEMP, TMP and TMPDIR in this sequence to identify the preferred temporary directory folder.

4.2.1 Starting SAPinst with the GUI Running on the Server

To start a step with the GUI running on the server, proceed as follows:1. Log on as user <sid>adm on the host, where the step has to be executed and open a com‐

mand prompt/shell. Only for some steps a log on as a different user is required, see the doc‐umentation of the steps below.

2. Go to the directory <DVD_NZDM_PI>/DU/SAPINST_<OperatingSystem>_<ProcessorFamily>3. If your PI system is installed on physical hosts (standard SAP installation), execute the follow‐

ing command to start the SAPinst server and GUI components:sapinst.exe

4. If your PI system is installed on virtual hosts (SAP High Availability installation) execute the following command to start the SAPinst server and GUI components:sapinst.exe SAPINST_USE_HOSTNAME=<SAPLOCALHOST>where <SAPLOCALHOST> has to be replaced by the virtual host name, the corresponding SAP instance is installed on, which is the value of the SAP profile parameter SAPLOCALHOST.CAUTION: It is essential that the current working directory is <DVD_NZDM_PI>/DU/SAPINST_<OperatingSystem>_<ProcessorFamily> when you start SAPinst.

4.2.2 Starting SAPinst with the GUI Running on a Remote Desktop

To start a step with the GUI running remotely on a desktop, proceed as follows:1. Log on as user <sid>adm on the host, where the step has to be executed, and open a com‐

mand prompt/shell. Only for some steps a log on as a different user is required, see docu‐mentation of the steps below.

2. Go to the directory <DVD_NZDM_PI>/DU/SAPINST_<OperatingSystem>_<ProcessorFamily>3.4. If your PI system is installed on physical hosts (standard SAP installation), execute the follow‐

ing command to start the SAPinst server component:sapinst.exe –nogui

5. If your PI system is installed on virtual hosts (SAP High Availability installation), execute the following command to start the SAPinst server component:sapinst.exe –nogui SAPINST_USE_HOSTNAME=<SAPLOCALHOST>where <SAPLOCALHOST> has to be replaced by the virtual host name, the corresponding SAP instance is installed on, which is the value of the SAP profile parameter SAPLOCALHOST.CAUTION: It is essential, that the current working directory is <DVD_NZDM_PI>/DU/SAPINST_<OperatingSystem>_<ProcessorFamily> when you start SAPinst.

6. Copy SAPinst GUI or sapinstgui.exe from the directory <DVD_NZDM_PI>/DU/SAPINST_<OperatingSystem>_<ProcessorFamily> matching the operating system of your desktop to a local directory on your desktop

7. Open a command prompt on your desktop from this directory and execute the following command to start the SAPinst GUI componentOn Windows desktops:sapinstgui.exe -standalone -port 21212 -host <IP-adress of server>


On UNIX/Linux workstations:./sapinstgui -standalone -port 21212 -host <IP-adress of server>

8. In dialog window “Server Authentication”, choose Accept.

9. Log on as the same OS user, which was used to start the SAPinst server component, and choose Next.

4.3 Step 1: Export of the Production System

This step must be executed on the host where the central instance of your PI system is installed.

4.3.1 Oracle Only: Preparing Flashback Query on the Oracle Database

The export of the production system occurs in parallel to the production processes. In order to export a consistent state of the database, the nZDM‐PI procedure uses Oracle flashback query where the flashback timestamp is set to the beginning of the export.

4.3.1.1 Granting Right for Flashback Query to SAP Database Users

The Oracle database system uses a special rigth for flashback queries. In order to grant this right to the SAP database users, connect to the database server as OS user ora<sid> and execute:

sqlplus /nologconnect /as sysdbagrant execute on dbms_flashback to sapconn;exit


4.3.1.2 Adapting Parameter undo_retention

If the value of current_ur is less than the value of required_ur (see “Checking the Required Undo Retention for the nZDM‐PI Procedure” on page 17.), connect to the database server as OS user ora<sid> and execute:

sqlplus /nologconnect /as sysdbaalter system set undo_retention = <required_ur>;exit

(Replace <required_ur> by the corresponding value in the alter system statement.)

4.3.2 Starting Step 1 (SAPinst)

Choose Next.


Verify that all previously started ABAP imports into the production system have been completed. Choose OK.Some tools including RFC enabled function modules will be imported into your production sys‐tem, which are required for the communication between the nZDM‐PI software and the system.NOTE: During the import only new ABAP functionality is imported into the system, which does not affect the system functionality at all. The import is absolutely uncritical, and can be done, while the system is productively used.


Enter the central instance number and password of ABAP user DDIC in client 000.Choose Next.

Enter the path of the profile directory of the PI system and choose Next.


Enter the password of user <sid>adm and choose Next.

Enter the path of the <Export1> directory, which was created in “Preparing Mounts/Shares of the nZDM‐PI Procedure” on page 15..Make sure field “Stop running system” is unchecked.CAUTION: If field “Stop running system” is checked, this may cause an interruption of the pro‐ductive usage of your PI system.Choose Next.


Enter a number of parallel jobs for the database export. If you choose a larger number of parallel jobs, the export will be finished faster, but it will also consume more system resources.We recommend that you do not exceed the number of the default value of three jobs on perfor‐mance critical systems.Do not change any other value and choose Next.

All entered parameter values are shown on the Parameter Summary screen. If you want to make a change, select the relevant parameter and choose Revise.


If all values are correct, choose Next.

Step 1 is now being executed.

Choose OK to finish the step.

4.3.3 Oracle only: Exporting Terminates with Error “snapshot too old”

If required undo information is no longer available during the export, the export will fail with SQL error


ORA‐01555: snapshot too oldPossible causes are:• The export was interrupted and continued later than required_ur seconds after the start of

the export• Database activity during the export was significantly higher than before, when the required

undo retention time for the nZDM‐PI procedure was estimated, see section “Checking the Required Undo Retention for the nZDM‐PI Procedure” on page 17.

Proceed as follows:1. Do not try to use Retry in SAPinst GUI. You only would run into the same error again.2. Choose Stop in the SAPinst GUI and exit SAPinst. Make sure, no more SAPinst processes are

running.3. Identify the cause of missing undo information.4. If necessary, re‐execute the calculations from section “Checking the Required Undo Reten‐

tion for the nZDM‐PI Procedure” on page 17..5. Contact the SAP support, if the cause is unclear.After measures have been taken, to avoid the issue this time, restart the nZDM‐PI procedure as follows:1. Delete the content of the directory <Export1> completely (sub folders ABAP and JAVA, and

file LABELIDX.ASC)2. Start “Step 1: Export of the production system” from the very beginning according to this

document.3. After starting SAPinst, select Run a new option and choose Next on the first screen.CAUTION: Only use “Run a new option” after restarting SAPinst, when this is expicitely men‐tioned in this document or it is recommended by the SAP support.CAUTION: Do not alter tablespace PSAPUNDO using the RETENTION GUARANTEE clause, since this may cause a production standstill.

4.3.4 Oracle Only: Modifying the Value of Parameter “undo_retention”

If you have changed the parameter undo_retention before starting step 1 (see “Adapting Param‐eter undo_retention” on page 55.), change it back to the old value after successful execution of step 1 as follows:1. Connect to the database server as OS user ora<sid> and execute:

sqlplus /nologconnect /as sysdbaalter system set undo_retention = <current_ur>;exit

2. Replace <current_ur> by the old value in the alter system statement.

4.4 Step 2: Installation of the Update System

This step must be executed on the update host. CAUTION: Make sure that your production system and the update system do not share directory <drive>:\sapmnt\<SID>. In particular, make sure that your production system and the update sys‐tem do not use the same profiles located in directory <drive>:\sapmnt\<SID>\SYS\profile.


4.4.1 Preparing Step 2

Make sure that the directories containing the export data from step 1 and the database installa‐tion software are accessible on the update host. To do so, see the following table:

4.4.2 Setting Parameters in SAPinst Dialogs

It is important to set some parameters correctly, which might have incorrect default values.Follow the descriptions in this document accurately to avoid any wrong parameter settings.All of the parameters may be checked again on the summary dialog (end of dialog phase), and corrected if necessary.


1. Log on as an user with sufficient permission on the update host. The following cases might occur:• If <sid>adm is already available on the update host as domain user, log on as <sid>adm• If <sid>adm is not yet available on the update host, log on as user of the “Administrators”

group2. Start SAPinst.

Table 6: Required Directories for Installation of Update System

Identifier DB platformOnly required, if DB software is not yet installed

See

<DVD_NZDM_PI> all page 15

<Export1> all page 15

<DVD_RDBMS_Install> Oracle X page 14

<DVD_RDBMS_Client> Oracle page 14


Choose Next.CAUTION:

Enter the system id of your PI system in field SAP System ID (SAPSID), and select an appropriate drive for the installation of the SAP software. Choose .CAUTION: It is essential for the nZDM‐PI procedure, that the SAP System ID of the update system and the production system are identical.


Enter <DVD_RDBMS_Client> and choose Next.

Enter a master password for users of the update system, confirm it, and choose Next.There will follow addional dialogs, which request passwords for specific users. If these users do already exist, you have to enter the correct passwords. If these users do not yet exist and you do not enter new passwords, these users will be created using the master password.


For the installation of the update system enter the same domain model, which is also used for the production system.Choose Next.

Enter the database id of your PI system in field Database ID (DBSID), and choose Next.CAUTION: It is essential for the nZDM‐PI procedure that the Database ID of the update system and the production system are identical.


In case some prerequisites are not fulfilled by the update host, the following screen appears. The appearing messages may differ.A message on “Minimum Saplocales Version” can be ignored, since it is only relevant for Non‐Unicode systems.Messages on swap or memory sizes may be ignored, if the current values are not very much lower than the recommended values, since the update system will not be used in a way compa‐rable to a standard SAP system.A corresponding file prerequisite_checker_results.html containing the check results can be found in the SAPInst work directory <DVD_NZDM_PI>/DU/NZDM_PI/work/<update_host_name>/sapinst_instdir/ZDMPI.

If you did resolve any issues, choose Yes to run the check again.If you decided to ignore the remaining messages, choose No.


Keep the suggested memory values.If you do not change the passwords, the DB users will be created using the master password. Choose Next.

Check the production database server and client versions. Use the same versions for the update host. CAUTION: The default version might not match and might have to be adapted here.Choose Next.


Enter <DVD_RDBMS_Install> and choose Next.

Make sure, you enter the correct key phase from the production system. Choose Next.


Enter the password of ABAP user DDIC in client 000 of the production system, and choose Next.

Enter <DVD_RDBMS_Client> and choose Next.


All entered parameter values are shown on the Parameter Summary screen. If you want to make a change, select the relevant parameter and choose Revise.If all values are correct, choose Next.



Choose OK to finish step 2.

4.4.4 Oracle Only: Installation of Database Software

If the Oracle database software is not yet installed on the update host, the SAPinst process will stop after a couple of minutes. The following message appears:

Keep the SAPinst GUI window open, while you install the database software.


Install the database software and additional patches for your database platform as described in the database‐specific sections in the document Installation Guide – <SAP NetWeaver / SAP applica‐tion> <Technology> on <Operating System>: <Database> at http://service.sap.com/instguidesNW ‐> <Release> ‐> Installation.For information about version limitations, see SAP Note 1435235.

4.4.5 Windows Only: Procedure Interruption in Case of Local Windows Users

This section only applies under the following conditions:• Operating system is Windows• Step 2 was not started as <sid>adm, but as different user from group “Administrators”The procedure will be interrupted in phase “Unpack SAP archives” with the following error dia‐log.

In this case proceed as follows:• Choose Stop and exit SAPinst• Log off from Windows• Log on to Windows as user <sid>adm. This user had been created before with the password

you entered in the corresponding dialog.• Mount the directory <DVD_NZDM_PI> on the same drive letter, as it was mounted before for

the Administrators user.• Mount the directories <Export1>, <RDBMS_install_dir> on the same drive letters, as these

were mounted before for the Administrators user. If you did not use drive letters before, this is also not required now.

Start SAPinst again.

http://service.sap.com/instguidesNW


Select Continue with the old option and choose Next.The procedure will now continue as described above.

4.4.6 Performing Follow‐Up Activities of Step 2

After step 2 has been finished, perform the following activities.

4.4.6.1 Logging on OS Level

The following activities on the update host must be executed as user <sid>adm.Log off the update host and log on again as user <sid>adm.Even if you have executed the previous activities as user <sid>adm on Windows platforms, log off and log on again. During the installation of the update system some environment variables on operating system level have been changed, which only become effective after logging on.

4.4.6.2 Stopping the Update System

Use the SAP Management Console SAPMMC to stop the update system.

4.4.6.3 Setting DB Log Mode to “Overwrite” and Restarting the Database

During the SP import the database writes plenty of DB logs. In order to avoid archiving all this temporary data, we recommend that you switch the log mode off the DB of the update system to “overwrite” or “noarchivelog”.As a consequence the redo log files will be overwritten, after they are full. A recovery of the database will not be possible any more in case of a disk crash. In case of a disk crash the nZDM‐PI procedure has to be restarted with step 2. For more information, contact the SAP support.We recommend that you do not switch off the DB logging completely, since this could disrupt the database even in case of an abrupt termination of database processes.CAUTION: Do not use log mode "noarchivelog" or "overwrite" for the production DB.


Oracle

• Open a console window and switch to user ora<sid>:su - ora<sid>

• Connect to sqlplus as sysdba:sqlplus / as sysdba

• Enter the following sqlplus statements:shutdown immediatestartup mountalter database noarchivelog;alter database open;select log_mode from v$database;exit

4.4.6.4 Changing the Number of AS Java Nodes for the Update System

The update system has been installed using the settings from the production system, for which in general more than one server node is configured. For the update system one java server node is sufficient. Additional java server nodes will only require more resources without providing any benefit.To adapt the setting, open the Config Tool on the update system and identify the update instance below “cluster‐data” ‐> “template” by comparing the instance’s host names with the name of the update host.

Select the update instance, change the value of field Custom number of server nodes to 1 and choose Set.Save the configuration by choosing Apply Changes.


4.4.6.5 Changing the Gateway Host of Jco Adapters to localhost

CAUTION: It is essential to execute this step on the host of the update system. If Jco adapters of the update system connect to the gateway of the production system, this may cause loss of data on the production system.Open the Config Tool on the update system.

Change to the view “Configuration Editor”.

Switch into “Edit mode” and expand the configuration folder “rfcengine_global”.


Select the first entry Propertysheet... in folder rfcengine_global and choose Change.

Check, whether the value of property “gateway.host” is different from “localhost”. If it has a dif‐ferent value, double‐click on property “gateway.host”.


Enter custom value “localhost” and choose Apply custom and then OK.Next change the other property sheets located in folder “rfcengine_global” in the same way.CAUTION: Make sure that the value of property “gateway.host” is “localhost” for each of the property sheets located in folder “rfcengine_global” before you continue.The original values will be reactivated in a later step of the nZDM‐PI procedure as described in section “Restoring the Default Value of Gateway Host of Jco Adapters” on page 87.

4.4.6.6 Deactivating the Connection to Central SLD

In order to avoid that the update system connects itself to the central SLD, the configuration has to be adapted.To adapt the setting, open the Config Tool on the update system and identify the update instance under “cluster‐data” ‐> “template” by comparing the instance’s host names with the name of the update host.


Expand “services” below the update instance, scroll down, and click on service “com.sap.aii.af.cpa.svc”.

Click on key “SLDAccess”, enter custom value “false”, and choose “Set Custom Value”.Save the configuration by choosing Apply Changes.Finally exit the Config Tool.


4.4.6.7 Restarting the SAP Services of the Update System

Restart the SAP services of the update system. This can be done in the SAP Management Console SAPMMC. Right click on each of the SCS and central instance, and choose “All Tasks” ‐> “Restart Service”.Start the update system.Windows: Use the SAP Management Console SAPMMC to start the system.

4.4.7 Do not migrate ABAP Secure Store on update system

When the update system is running, some system generated ABAP users (e.g. WF‐BATCH) may not be able to log on to the update system. You may find corresponding messages in the ABAP Syslog (SM21).This is not an issue at all and will not affect the production system at the end of the procedure. Operations of these users are not needed on the update system.CAUTION: Do not migrate the ABAP Secure Store on the update system. Do not follow the instructions of SAP Note 816861 on the update system. Otherwise the data of the ABAP Secure Store will not fit to the production system after this has been switched to the new SP level, and will require an additional migration.

4.5 Step 3: Applying SAP Support Packages on the Update System

This step must be executed on the update host as user <sid>adm.


Choose Next.


During the application of the Support Package Stack later on a stack XML file is required. The file has to be generated using the Solution Manager. The Solution Manager creates the stack XML file for the production system. To be able to use the stack XML file on the update system it has to be adapted. This will be done automatically via the nZDM‐PI procedure. Therefore, if not done so far, it is necessary to create the stack XML file now and locate it within the EPS/in box of the con‐figured transport directory.Choose the generated stack XML file. If the file is not located in the provided EPS/in directory copy it there, choose Rescan Directory, choose NEXT to reread the content of the directory and select the file. CAUTION: The provided list of stack XML files does only list the stack XML files according to the host name of the production system or the update system. stack XML files generated for other systems will be ignored.CAUTION: As of now, do not modify the selected stack XML file manually.Choose Next.



The first part of step 3 is now being executed.


Then the nZDM‐PI procedure stops for application of Support Packages on the update system.You have two options:• Leave the window open, and continue from here after application of Support Packages• Choose “Cancel” to stop SAPinst here. After application of Support Packages you can restart

SAPinst.

4.5.2 Applying SAP Support Packages on the Update System

The Support Package update has to be done according to the procedure, but has to be executed on the update system instead of the production system.SAP strongly recommends, not to use any “downtime minimization” option of the standard pro‐cedure, since such options typically increase the total duration of the procedure, but have no effect on the downtime within the nZDM‐PI procedure.CAUTION: The Support Packages must be applied with the classical tools JSPM/SPAM. The “Soft‐ware Update Manager” (SUM) and the “Enhancement Package Installer” (EhPI) must not be used on the update system.

We recommend that you apply ABAP and Java Support Packages in the order described in the fol‐lowing sub‐sections, since this does not require a manual kernel update.

4.5.2.1 Applying SAP Java Support Packages on Update System (JSPM)

Use the standard procedure. If required, you can also install additional patches.For more information, see the JSPM documentation on the SAP Service Marketplace.JSPM will update the ABAP kernel automatically. If a new version of the ABAP kernel has been dowloaded, proceed as described in section “Downloading SAP Support Packages” on page 13.


4.5.2.2 Importing the Latest Support Package Manager Update

To apply the latest SPAM/SAINT update, enter transaction SPAM in your SAP system. For more information, see the documentation of transaction SPAM.CAUTION: Make sure that you import the latest SPAM/SAINT version on the update system. Do not start the import on the production system.CAUTION: Update SPAM/SAINT to version 36 or higher. Using SPAM/SAINT version 35 may cause issues during checks for a valid maintenance license key.CAUTION: Do not change TMS settings or migrate the ABAP Secure Store. For more information, see section “Do not migrate ABAP Secure Store on update system” on page 79.

4.5.2.3 Applying ABAP Support Packages on the Update System

To apply SAP ABAP Support Packages, proceed as described in the documentation of transaction SPAM.If you have applied additional SAP Notes on the old SP level, or you have modified any SAP objects, you have to perform modification adjustments on the update system. You can include a transport request from your development system, which contains modification adjustments, as described in chapter “Including Modification Adjustment Transports” of the documentation of transaction SPAM. We recommend that you use adjustment transports during the nZDM‐PI procedure instead of manual modification adjustments.CAUTION: Do not change TMS settings or migrate the ABAP Secure Store. For more information, see section “Do not migrate ABAP Secure Store on update system” on page 79.

4.5.2.4 Manual Modification Adjustments and Additional SAP Notes

In case you do not include a modification adjustment transport or this transport does not contain adjustments for all modifications, SPAM will prompt you to perform the modification adjust‐ments manually when required during the procedure.The update system is set to “Not Modifiable” during the procedure. In order to perform modifi‐cation adjustments manually, you have to set the update system to “Modifiable” first:• Run transaction SE03 on the update system• Select Transport Organizer Tools ‐> Administration ‐> Set System Change option, and choose

Execute• In the field Global Setting, select “Modifiable” from the drop‐down list and save your entry.

When the import of ABAP support packages is completed, you also may install additional SAP Notes in transaction SNOTE, if required. For this purpose, the system has to be set to “Modifi‐able”, too.Set the system back to “Not Modifiable” after the import of ABAP support packages and the installation of additional SAP Notes are completed.CAUTION: Do not release any change request on the update system, which was created during manual modification adjustments or installation of additional SAP Notes. Release of change requests is not possible on the update system. You may safely release such change requests later in the production system, after the nZDM‐PI procedure has been finished.


4.5.3 Regenerating Existing ABAP Loads on the Update System

We recommend that you regenerate the existing ABAP loads on the update system using transac‐tion SGEN. This ensures that no loads need to be regenerated after starting the production sys‐tem on the new SP level.In transaction SGEN choose option Regenerate Existing Loads and then Only regenerate Objects with Invalidated Load. For more information, see the documentation of transaction SGEN.In transaction SGEN you may also choose option Generate all objects of selected software com‐ponents and then select software component SAP_BASIS. This will take more time for the gener‐ation, which happens during uptime of the production system, but you will benefit from faster response times immediately after the switch of the production system to the new SP level.

4.5.4 Running Report SMIGR_CREATE_DDL on the Update System

This is applicable only if report SMIGR_CREATE_DDL created files on the production system. In this case it is necessary to execute report SMIGR_CREATE_DDL also in the update system. Proceed as described in section Executing ABAP Report SMIGR_CREATE_DDL [page 19].

4.5.5 Continuing Step 3 (SAPinst)

If you have stopped SAPinst before applying Support Packages as described in section “Starting Step 3 (SAPinst)” on page 79. , restart SAPinst now.

Select Continue with the Old Option and choose Next.CAUTION: Make sure that option Continue with the Old Option is checked.


If you are sure, all Support Packages have been applied correctly, choose OK.

To double confirm your decision, choose Yes.


The final part of step 3 is now being executed.

Choose OK to confirm, that the update system will be stopped now. This has no effect on the run‐ning production system!



4.5.6 Follow‐Up Activities of Step 3

4.5.6.1 Restoring the Default Value of Gateway Host of Jco Adapters

If the gateway host of the RFC engine has been set to localhost as described in section “Changing the Gateway Host of Jco Adapters to localhost” on page 75., the default value now has to be reactivated again.Open the Config Tool on the update system.


Change to the view Configuration Editor.

Switch into Edit mode and expand the configuration folder rfcengine_global.


Select the first entry Propertysheet... in folder rfcengine_global and choose Change.

Check, whether property gateway.host is marked in column custom. In this case double‐click on property gateway.host.


Choose Restore default and then OK.Next change the other property sheets located in folder rfcengine_global in the same way.CAUTION: Make sure that the property gateway.host has its default value for each of the prop‐erty sheets located in folder rfcengine_global before you continue.Finally exit the configtool.


4.5.6.2 Removing the J2EE Instance

Open the Config Tool on the update system.Identify j2ee instance of update host.

Change to the view Configuration Editor.


Switch into Edit mode and expand the configuration folder cluster_config/system/instances.

Delete j2ee instance of update host. CAUTION: It is essential to remove j2ee instance registration of update host only.

4.6 Step 4: Export of the Update System

This step must be executed on the update host.



Choose Next.

Enter the path of the profile directory of the update system and choose Next.


Enter the password of user <sid>adm and choose Next.

Enter <Export2> in the field Export Location.Make sure that the Stop running system checkbox is selected.Choose Next.


Proceed as described in section “Executing ABAP Report SMIGR_CREATE_DDL” on page 19.If no DB specific adaptations of database tables had been found in your system, choose Ok.If DB specific adaptations of database tables had been found in your system, follow the instruc‐tions, you have received from SAP Support.CAUTION: Never copy any files to the mentioned directory without consulting the SAP Support. Files created by program SMIGR_CREATE_DDL must not be used without adaptation in the nZDM‐PI procedure.


Enter a number of parallel jobs for the database export. You can choose a large number of pro‐cesses here, since the activities do not affect the production system.We recommend that you use at least 8 parallel jobs.CAUTION: Choose Next.

Select the No radio button for update statistics and choose Next.



4.7 Step 5, Uptime: Shadow Import into the Production System

This step must be executed on the CI host, where the central instance of your PI system is installed.

4.7.1 Preparing Step 5

4.7.1.1 Checking Available DB Space of the Production Database

The content of the database of the update system will be imported as “shadow” tables into the production database in step 5. For this purpose additional disk space is required in the produc‐tion database.Check the used disk space of the database of the update system, and make sure, this space is additionally available in the database of the production system, by either adding additional data files or by configuring the database to auto‐extend data files or add additional data files auto‐matically.CAUTION: If the production database runs out of space during the shadow import, all database operations will be blocked until additional disk space is available. This will result in production downtime.


Log on as <sid>adm user.


Choose Next.

Enter a number of parallel processes for the database import, which will be started during uptime of the production system. If you choose a larger number of parallel processes, the import will be finished faster, but it will also consume more system resources.We recommend that you do not increase the default value of 3 parallel import jobs on systems used for production or other performance critical systems.


Enter a number of parallel switch processes, which will be started during downtime of the pro‐duction system. A large number of switch processes occupying the whole system resources can be used in order to reduce the downtime duration.We recommend that you choose the number of switch processes roughly 4 times larger than the number of CPUs on the database server, but no more than 20 processes.

Enter <Export2> in the field Export of update sytem and choose Next.



The uptime part of step 5 is now being executed.


The uptime part of step 5 is finished.The procedure has checked the system for critical changes on database tables, which will be exchanged during the switch, and tells the result.In case critical changes are found, the details are written into a file in the directory:

<DVD_NZDM_PI>/DU/NZDM_PI/log/triggerresultsThe full path of the file is displayed on the screen.In this case contact SAP Support and send this file for analysis. Do not continue with the down‐time part of step 5, before SAP has confirmed the changes may be overwritten without risk of loss of data or data inconsistency.CAUTION: If critical changes have been found, and you start the downtime phase without confir‐mation from SAP, this may result in loss of data or data inconsistencies on the production system. SAP will not take over responsibility for any possible damages in this case.To update the check results, scroll down ‐ if necessary.


Select the Perform a Delta Check radio button and choose Next.The same screen will be displayed again telling, whether new critical changes have been found since the last check. Also send newly created result files to SAP.We recommend that you perform a new Delta Check every couple of hours, if there is still time left till the planned start of the downtime phase, and immediately before you plan to start the downtime phase.Option Terminate and reset procedure is offered to allow procedure restart from the beginning. If required select this radio button and follow reset steps in chapter “Troubleshooting” on page 140.

4.7.3 Preparing Manual Update of the SAP Java Virtual Machine

The current version of nZDM‐PI provides an update of the SAP Java Virtual Machine (SAP JVM).

However, you need to perform the following manual steps without the need for an additional

restart of the production system:1. Log on to the ABAP system, run transaction RZ11, and memorize the current value of profile

parameter DIR_CT_SAPJVM. It will typically have a value of the pattern <drive>:\usr\sap\<SID>\SYS\exe\jvm\<plat-form>\sapjvm_<old_version>.

2. Go to the parent directory of the path mentioned under point 1.), identify the subdirectory with suffix _tmp and open the file sapjvmmanifest.mf in this directory. Memorize the num‐ber assigned to sapjvm version (f.e. 5.1.040).

3. Go to the profile directory of the production system:cd <drive>:\usr\sap\<SID>\SYS\profile


4. Identify the instance profiles of the central instance and of all dialog instances of the produc‐tion system that have the following name pattern:<SID>_D*<instance-number>_<instance-host>

5. Create a copy of each of the following profiles:copy <instance-profie> <instance-profile>.new

6. Edit each of the created copies <instance‐profile>.new with a text editor.7. Search for parameter SAPJVM_VERSION, and change its value from <old_version> into

<new_version>The update of the SAP Java Virtual Machine will be activated during downtime by activating the new instance profiles, and restarting the SAP services. We recommend that you do not activate the new instance profiles before the downtime, since this may impact production instances in case, they need to be restarted before the downtime for any operational reason.

4.7.4 High Availability Systems Only: Disabling Failover Capabilities

If your system is installed in a high availability switchover environment, make sure that the failover capabilities of the cluster switchover software are disabled during the downtime. This is to prevent unwanted failover actions during stop actions of the nZDM process.For more information, see SAP Note 1528974.

4.8 Downtime Part of the NZDM‐PI Procedure

If no unexpected changes have been found, or SAP has confirmed, these changes may be over‐written, you can start the downtime part of step 5.The downtime consists of some manual actions for starting the downtime, of the system switch controlled by SAPinst, and some manual actions for starting production again.

4.8.1 Checking the PI Alerts

We recommend that you check the production system for any alerts e.g. on failed messages, and resolve the errors accordingly to your business policies, before continuing.

4.8.2 Shutting Down the Production System

Shut down all instances of your PI production system.

4.8.3 Step 5, Downtime: Switching off the Production System

Go back to the still open SAPinst GUI.


Select the Perform a Delta Check and proceed with Downtime radio button and choose Next.

If all instances of the production system are shutdown, choose OK.CAUTION: Before continuing make sure that your database is still up and running.The switch of the production system to the new SP level is being executed. While the switch is executed, activate the new version of the SAP Java Virtual Machine in parallel as described in section “Activating the New Version of the SAP Java Virtual Machine” on page 106.


4.8.4 Activating the New Version of the SAP Java Virtual Machine

To activate the new version of the SAP JVM, log on as user <sid>adm to the CI host and proceed as follows:1. Go to the parent directory of the SAP JVM directory that you have identified in section Pre‐

paring Manual Update of the SAP Java Virtual Machine [page 103]. 2. Rename the SAP JVM directory to the new version as identified in section Preparing Manual

Update of the SAP Java Virtual Machine [page 103]:rename sapjvm_<old_version> sapjvm_<new_version>

3. Go to the profile directory of the production system:cd <drive>:\usr\sap\<SID>\SYS\profile

4. Identify the instance profiles of the central instance and of all dialog instances of the produc‐tion system that have the name following pattern:<SID>_D*<instance-number>_<instance-host>

5. Activate the new version of each of following instance profiles:rename <instance-profie> <instance-profile>.bakNZDMrename <instance-profie>.new <instance-profile>NOTE: You may choose a suffix different from bakNZDM for the backup of the old profile ver‐sions.

6. Restart the SAP services of the central instance and of all dialog instances of the production system in the SAP Management Console SAPMMC. Right click on each of the central dialog instances and choose All Tasks ‐> Restart Service.

4.8.5 Starting the Production System

Start up all instances of your PI production system.


There is no need to wait, until all instances are running. You can finish the SAPinst process imme‐diately. Since the WebAS ABAP starts up faster than the WebAS Java, you can continue with the following activities in the WebAS ABAP, as soon as login is possible.

4.8.6 Exiting SAPinst (SAPinst)

In the still open SAPinst GUI choose OK.

The final completion activities are executed. Note that you may in parallel continue with the sub‐sequent activities in the WebAS ABAP as soon as the login is possible.



Chapter 5: Follow‐Up Activities

Some follow‐up activities are required, which are not yet fully automated in the current version of the nZDM‐PI procedure.

5.1 High Availability Systems Only: Enabling Failover Capabilities

If your system is installed in a high availability switchover environment, make sure that the failover capabilities of the cluster switchover software are enabled after the downtime.

5.2 Checking the Missing Secondary Indexes on ABAP tables

Log on to any client of the ABAP system.Call transaction DB02.


Expand “Diagnostics” and double‐click “Missing tables and Indexes”.

Choose “Refresh”. T


Do not investigate section “Unknown objects in ABAP dictionary”. Roughly 20000 objects will be displayed in this section before the cleanup of the production system has been executed (see “Step 6: Cleaning the Production System” on page 130.).Expand section “Objects missing in the database” ‐> “Secondary indexes”.

For each missing index choose the button “Create on DB” in column “Action”.


Select the Direct Processing radio button and choose Create.After having processed all shown indexes, choose Refresh again, to verify that no more indexes are missing.

5.3 Checking the Web Service Environment

1. Log on to any client of the ABAP system.2. Execute report SRT_ADMIN_CHECK.3. If a log on data retrieval error is listed on the check result screen, restore the data as

described in SAP Note 1043195. To do so, execute report SRT_ADMIN for each affected cli‐ent, eventually starting with a technical reset before performing the technical setup.

5.4 Invalidating the Transport Buffer

1. Log on to any client of the ABAP system.2. Execute report RSDBBUFF.3. From the menu choose Edit ‐> Reset Buffer ‐> Single Key Buffer.4. In the dialog box, enter table TFDIR and choose Invalidate.

5.5 Checking Number Ranges for Tables ADRP and SOFD

To avoid a user creation issue, you need to perform the following steps for the PI client and the system client (000):1. Identify highest PERSNUMBER entry stored in table ADRP.2. Check counter for PERSNUMBER in transaction SNRO for object type ADRNR and raise it

above the highest PERSNUMBER entry identified before.


3. Identify highest FOLNO entry for the current FOLTY stored in table SOFD (for FOLTY use year number ‐ 1975, for example 2012 ‐ 1975 = 37).

4. Check entry for current year exists in transaction SNRO for object type SO_OBJ_FOL. For example for year 2012 and highest FOLNO = 6 an entry like this one is required:01 2012 000000000001 999999999999 7.

5.6 Performing Support Package Stack Post‐Installation Steps

After applying Support Packages to your PI system, you need to perform post‐installation steps for PI systems that are described in the Support Package Stack Guide. For more information about the procedure, see document Support Package Stack Guide NetWeaver <Release><Support Package Stack> on SAP Service Market Place at http://ser‐vice.sap.com/instguides ‐> SAP NetWeaver <Release> ‐> Maintenance ‐> <Support Package Stack>.

Chapter 6: Setting the System into Unrestricted Production Mode

6.1 Scheduling ABAP Archiving

Log on to the ABAP system in the PI client and run transaction SXMB_ADM.

Double‐click “Schedule Archiving Jobs”


Enter the user name, which shall be used as runtime user for the archiving jobs, and choose Start Date.

Maintain the start date, start time and the periodicity conditions (e.g. daily or weekly) and save your entries.Then choose Spool Parameter.


Choose the output device and choose “Continue”.

Choose “Schedule Archiving”Again run transaction SXMB_ADM, and double‐click on “Schedule Delete Jobs”


Select the Delete Job for XML messages and Delete Job for History Entries checkboxes. Enter appropriate values for start date and time and periodicity. Choose Dispatch.

6.2 Schedule Java Archiving

6.2.1 Schedule Java archiving and deletion jobs

Start the PI Runtime Workbench:http://<ci_host>:5<instance_no>00/rwb


Lock on as user with full PI runtime administration permissions, and click on “Component Moni‐toring”.

Choose “Display”.


Click on “Integration Server” ‐> “Adapter Engine” and scroll down to the tabs with details.

Click “Background Processing”.In the Popup “Background Processing: Job Configuration”, there will be displayed an overview of all jobs, which are available on the chosen Adapter Engine. In the column “Job Type”, you will find the type of the respective job. As it is possible to configure multiple Jobs of one kind, it is possible, that there is more than one job of the type “Archive” or “Delete” available.


CAUTION: It is important to keep the right order while switching these jobs ON. FIRST activate all archiving jobs, THEN activate all deletion jobs.Select the first job of type “Archive”, and click “Edit”.

Select the Active checkbox, enter a valid start date/time, and save your entries.Repeat this action for each job of type “Archive”, and then for each job of type “Delete”.CAUTION: Make sure, that you have activated all jobs of type “Archive”, before you activate jobs of type “Delete”.Finally close the Popup “Background Processing: Job Configuration”.

6.2.2 Enabling Security Archiving

In the still open “Adapter Engine” view:


Choose “Security Archiving”.The Popup “Message Security Archiving Monitor” opens.

Enter appropriate values in the fields “Start Archiving Session” and “Archiving Interval”.Choose “Update Archiving Settings”.


The Next Archiving Session text box now displays the start time of the next scheduled archiving.

6.3 Setting SLD into Default Mode

Proceed as described in section “Setting the SLD into Read‐only Mode” on page 37., but select None in field Write protection.Reactivate SLD content sync jobs, which have been deactivated as described in section “Set SLD into read‐only mode”.

6.4 Unlocking the PI Design Time

Open the PI Exchange Profile:

http://<ci_host>:5<instance_no>00/exchangeProfile


Log on as user with full PI design time permission. When prompted, whether you want to use the old or the new user interface, choose the one you prefer. The following screenshots show the old user interface, but the navigation steps are identical in both user interfaces.

Expand the node “Integration Builder”, and scroll down to parameterscom.sap.aii.ib.server.upgrade_modecom.sap.aii.ib.server.upgrade_users


Choose the com.sap.aii.ib.server.upgrade_mode parameter.

Enter False and save your entry.Next choose the com.sap.aii.ib.server.upgrade_users parameter.


Optionally you can now remove the name of the administrator user, who was permitted to do design time changes in emergency cases during the nZDM‐PI procedure and save your entries.

6.5 Activating the Monitoring of PMI

If you have configured the Process Monitoring Infrastructure (PMI) for your production system before the SP update, you may now activate the monitoring again.CAUTION: SAP does not recommend to activate the PMI after the SP update, if you did not yet already use it before the SP update. PMI requires considerable system resources, and may lead to performance issues, if the system layout is not sufficient.Log on to the ABAP system in the PI client and run transaction SM37.


Enter the following values on the selection screen:Job Name: *User Name: *Job status

Select ScheduledJob start condition

From: <date_of_deactivation_of_PMI>To:31.12.9999or after event: *

Job stepABAP program name: SPI_*Choose “Execute”


You have to release each of the shown jobs. This has to be done separately for each job.Select the first job, and choose Release.

Adapt the scheduled start date to a valid date in the future (today or tomorrow) and save your entries. Do not change any other fields, in particular do not change period values.Repeat this for all of the other jobs shown in the list.Next start the PI Runtime Workbench:

http://<ci_host>:5<instance_no>00/rwb


Log on as user with full administration permissions in the PI Runtime Workbench, choose OK and than Configuration.

If Single‐Sign‐On is not set up for your user, enter the log‐on data again.Choose “Display”.


Choose “Activate Monitoring”.

6.6 Scheduling Java Jobs

Re‐schedule the Java jobs that you have de‐scheduled, when setting the system into Business‐Only mode as described in section De‐Scheduling Java Jobs [page 48].To re‐schedule Java jobs, perform the following steps:


1. Open the NetWeaver Administrator at http://<host>:<instance number>00/nwa.2. Log on as AS Java administrator.3. Choose Operation Management ‐> Jobs.4. Choose Java Scheduler.5. Select tab Tasks.6. Re‐schedule the Java jobs that you have de‐scheduled by choosing Release.

6.7 Scheduling SAP and Customer‐Specific Background Jobs

Re‐schedule the background jobs, which had been de‐scheduled, when setting the system into Business‐Only mode. For more information, see section “De‐Scheduling SAP and Customer‐Spe‐cific Background Jobs” on page 49.To re‐schedule background jobs, log on to the ABAP system in the PI client and run transaction SM37.

Enter the following values on the selection screen:

Job Name: *User Name: *Job status

Select ScheduledJob start condition

From: <current_date> To: 31.12.9999or after event: *

ABAP program name:Choose “Execute”.


Only release those jobs, which had been de‐scheduled, when setting the system into Business‐Only mode. This has to be done separately for each job.Select the first job and choose Release.

Adapt the scheduled start date to an appropriate valid date in the future and save your entries. Do not change any other fields, in particular do not change period values.Repeat this for all of the other jobs, which shall run again.


6.8 Scheduling Customer‐Specific Activities

Reschedule the activities that had were de‐scheduled when setting the system into Business‐Only mode. For more information, see section “De‐Scheduling Other Customer‐Specific Activi‐ties” on page 51.

6.9 Unlocking Dialog Users

Unlock the dialog users that were locked when setting the system into Business‐Only mode. For more information, see section “Locking Dialog Users” on page 25.

6.10 Connecting the PI System to External User Management Systems

If you disconnected the PI system from external user management systems, re‐establish the con‐nection again. For more information, see section “Disconnecting the PI System from External User Management Systems” on page 25.

6.11 Adapting the TMS Configuration After the nZDM‐PI Procedure

If any changes were made in the TMS configuration during the nZDM‐PI procedure, re‐distribute the TMS configuration into all systems of the TMS domain from the current TMS domain control‐ler.Next undo all changes for the roles of the domain controller and the backup domain controller that you did during the preparation phase as described in section Adapting the TMS Configura‐tion [page 24] of this document.

6.12 Rescheduling Import Jobs of ABAP Transport Requests

If you have de‐scheduled any automatic import jobs before starting the nZDM‐PI procedure, these now can be scheduled again. For more information, see section “Handling Imports of ABAP Transport Requests and Import Jobs” on page 24.

Chapter 7: Final Cleanup Activities

The production system is already fully available on the new SP level after the previous chapters have been executed. Some additional activities are required, in order to remove temporary data from the production system, which still occupies file system ressources.

7.1 Step 6: Cleaning the Production System

CAUTION: Do not execute this step before your PI system has been running productively for at least seven days without issues. The temporary nZDM‐PI data may be needed by SAP support in case you encounter any issues with your PI system running on the new SP level. CAUTION: We recommend that you create a full online backup of the database of the production system before executing this step.This step has to be executed on the CI host.In this step the following actions are executed:


• Database tables of the old SP level that have been renamed during the system switch are dropped from the database.

• Database tables containing the trigger results are dropped from the database.• An ABAP transport request is imported that removes the nZDM‐PI ABAP tools from the sys‐

tem. • Directories containing data of the old SP level are removed from the file system.CAUTION: Make sure that all ABAP imports into the production system are completed, before you start this step. Make sure, no ABAP imports into the production system are started in parallel with the running step. If this is not possible for any reason, contact the SAP support for an alter‐nate proceeding.Execution of this step in parallel to productive usage of the system will not affect the database performance considerably. Depending on the database platform, the database system may de‐allocate the space occupied by the dropped tables in a delayed way in the background in order to minimize the required resources. For this reason you may not see the decrease of used disk space in a DB admin tool immediately after execution of this step. Indeed it may take several hours, before you can see the final values of used disk space.If you do not observe any decrease of used space or increase of free space in tablespaces PSAPSR3, PSAPSR3710 and PSAPSR3DB even hours after execution of step 6, this may be caused by activated Oracle Recycle Bin feature. For more information, see SAP Note 838982.


Start SAPinst for execution of step 6.

Choose Next.


Choose Next.CAUTION: If you deselect the transport request to be imported, you cannot use SAPinst later to import this transport request. Instead you have to import this transport request manually.




Choose OK to finish step 6.The directories <Export1>, <Export2> and <DVD_NZDM_PI> have not been removed within this step. They must be deleted manually after the data is not needed any more.CAUTION: Do not remove the directory <DVD_NZDM_PI> before step 6 of the procedure has fin‐ished successfully. SAP strongly recommends to keep a backup of the directory


<DVD_NZDM_PI>, so that the logs of the nZDM‐PI procedure are accessible in case of any later questions.

7.1.2 Invalidating the Buffer of Table TFDIR

Due to an issue of ABAP table buffer synchronization during transports it is required to invalidate the single key buffer of ABAP table TFDIR on all ABAP instances after the cleanup of the produc‐tion system. A fix will be provided with the subsequent SP level.CAUTION: If the buffer of table TFDIR is not invalidated on all instances of the production system, subsequent imports of ABAP transport requests may hang. In this case you will find terminated background jobs RDDDIS0L in transaction SM37. In this case you can still solve the issue by inval‐idating the buffer of table TFDIR without interrupting the import. Another symptom is termina‐tion of ABAP menu function System ‐> Status with a short‐dump.Proceed as follows:• Log on to the ABAP system in any client• Run transaction SM51 to get a list of all ABAP instances• Select the first instance• Open a new session (System ‐> Create Session) and run transaction AL12• From the menu choose: Edit ‐> Reset Buffer ‐> Single Key Buffer• On the popup in section “Single table” enter table name TFDIR and choose “Invalidate” (Do

not choose the “Invalidate” button in section “Whole buffer”)• Close the session• Go back to the list of all ABAP instances, and continue with the next instance

7.2 Uninstalling the Update System

CAUTION: Do not unistall the update system before you get the approval from SAP to do so. The update system may be needed by SAP support in case you encounter any issues with your PI sys‐tem running on the new SP level. Do not unistall the update system before your PI system has been running productively for a couple of days without issues.CAUTION: We recommend that you create a full file system backup of the update host including the update database before you execute this section. SAP points out, that such backup may be required for legal reasons or by your company’s policy.The update host is not needed any more for the PI system, and may be used for other purposes. You may select one of the following options for uninstalling the update system:• Uninstall the update system and database using SAP uninstall procedure. This procedure is

the recommended way, if you want to re‐use the update host within the nZDM‐PI procedure for another system running on the same database platform. The database software will not be uninstalled, which will simplify step 2 for the next system.

• Reset the host to some previously created full backup.• Install a new operating system from scratch.

7.2.1 Uninstalling the Update System Using the SAP Uninstall Procedure

To uninstall the upadate system, proceed as follows:Log on as user with root permission (Unix/Linux) or user from the Administrators group (Win‐dows) on the update host.


CAUTION: Make sure that you are logged on to the update host. Do not run this procedure on any other host.Create an empty folder and extract the downloaded zip file "NW <rel> Inst.Master" into this folder as described in section “Downloading the SAP NetWeaver Installation Master” on page 15.Change to subdirectory SAP_NW_AS_ABAP_<rel>_Inst._Master/DU/IM_<operating_system>_<db_platform> and start SAPinst from that direc‐tory.

On the “Welcome” screen choose SAP NetWeaver Process Integration<rel> ‐> Software Life‐Cycle Options ‐> Uninstall and select “Uninstall – SAP Systems or Single Instances”. Choose Next.


Check whether the profile directory of the update system is suggested and choose Next.

Keep the checked items. You may additionally select the Remove OS users checkbox. If you also want to remove the operating system users <sid>adm and ora<sid>. Choose Next.


Choose Next.

Choose Next.



The de‐installation of the update system is now being executed.


Choose OK to finish the de‐installation.The update host is now ready for being used as update host for a different system on the same operating system and database platform.

Chapter 8: Troubleshooting

8.1 Resetting the nZDM‐PI Procedure

CAUTION: Procedure reset can not be requested anymore as soon as Step 5 downtime has been started.Situations and reasons to reset and restart the procedure from the beginning might be:

• “Check for critical changes” action has raised changes that must not be discarded or can not be reapplied after the procedure.

• SP import on update host is incomplete (for example requiring to include another SP version) or failed with severe errors

Several steps are required to perform the reset. First terminate the current procedure, then restart SAPinst for undoing changes on production system and finally perform remaining manual cleanup actions.


8.1.1 Terminating the Procedure

8.1.1.1 Terminating the Procedure in Case of Critical Changes

Select the Terminate and reset procedure radio button and choose Next.


Choose OK to stop the current step.

8.1.1.2 Terminating the Procedure in Other Cases

It is possible to terminate SAPinst using it’s default termination option. .

Choose SAPinst menu and Cancel.

8.1.2 Starting SAPinst for Resetting the nZDM‐PI Changes on the Production Sys‐tem

Start sapinst.exe on production system from the following path:


<DVD_NZDM_PI>/DU/SAPINST_<OperatingSystem>_<ProcessorFamily>.

Select the Run a new option radio button and choose Next.

Select Reset the NZDM‐PI procedure to a previous consistent state and choose Next.


Select the Confirm to reset the NZDM‐PI procedure checkbox and choose Next.



Choose OK to finish.


8.1.3 Performing Manual Actions After the Reset

The automatic undo of changes caused by the nZDM‐PI procedure on production system does not include the procedure DVD, the update system and export data. The following actions might have to be done for a full cleanup and restart preparation:• Delete all content from directory <Export1>• Delete all content from directory <Export2>• Deinstall update system as described in chapter “Uninstalling the Update System” on

page 134..• Backup and delete all content from procedure DVD directory <DVD_NZDM_PI>• To restart the NZDM‐PI procedure unpack the NZDM‐PI software according to chapter

“Unpacking the nZDM‐PI Software” on page 17.

8.2 Contacting SAP Support

If none of the measures described in chapter Troubleshooting solves your problem and you

encounter problems that are specific to the nZDM‐PI procedure, contact SAP Support. To do so, proceed as follows:1. Create an error message in SAP Support Portal (http://service.sap.com/support) and assign it

to component BC‐UPG‐OCS‐ZDM. 2. Attach all relevant files to the message.

User Guide Near Zero Downtime Maintenance for SAPNetWeaver Process Integration 7.3 on Windows Oracle

Documents

Transcript of User Guide Near Zero Downtime Maintenance for SAPNetWeaver Process Integration 7.3 on Windows Oracle