Johnson printing service SAP r3 system administration made easy release 4 6 AB feb 2000 ISBN 1893570436 pdf

6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\ 0LFURVRIW 64/ 6HUYHU ® à R/3 System Release 4.6A/B SAP Labs, Inc Palo Alto, California TM &RS\ULJKW  2000 by SAP AG All rights reserved Neither this documentation nor any part of it may be copied or reproduced in any form or by any means or translated into another language, without the prior consent of SAP AG SAP AG makes no warranties or representations with respect to the content hereof and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose SAP AG assumes no responsibility for any errors that may appear in this document The information contained in this document is subject to change without notice SAP AG reserves the right to make any such changes without obligation to notify any person of such revision or changes SAP AG makes no commitment to keep the information contained herein up to date 7UDGHPDUNV SAP, the SAP logo, R/2, R/3, ABAP, and other SAP-related products mentioned herein are registered or unregistered trademarks of SAP AG All other products mentioned in this document are registered or unregistered trademarks of their respective companies Simplification Group SAP Labs, Inc 3475 Deer Creek Road Palo Alto, CA 94304 www.saplabs.com/simple simplify-r3@sap.com Printed in the United States of America ISBN 1-893570-43-6 This book uses EcoFLEX lay-flat binding With this lay-flat feature—developed by and exclusively available at Johnson Printing Service (JPS)—you can open this book and keep it open without it snapping shut on you You need not worry about breaking the spine EcoFLEX makes books like this one easier to use &RQWHQWV DW D *ODQFH ,QWURGXFWLRQ  [[L &KDSWHU  5 6\VWHP $GPLQLVWUDWLRQ %DVLFV ² &KDSWHU  'LVDVWHU 5HFRYHU\² &KDSWHU  %DFNXS DQG 5HFRYHU\ ² &KDSWHU  6FKHGXOHG 'DLO\ 7DVNV² &KDSWHU  6FKHGXOHG :HHNO\ 7DVNV ² &KDSWHU  6FKHGXOHG 0RQWKO\ 7DVNV² &KDSWHU  6FKHGXOHG 4XDUWHUO\ 7DVNV ² &KDSWHU  6FKHGXOHG $QQXDO 7DVNV ² &KDSWHU  0XOWL5ROH 7DVNV² &KDSWHU  5 6\VWHP $GPLQLVWUDWLRQ ² &KDSWHU  6HFXULW\ $GPLQLVWUDWLRQ ² &KDSWHU  8VHU $GPLQLVWUDWLRQ ² &KDSWHU  'DWDEDVH $GPLQLVWUDWLRQ ² 0LFURVRIW 64/ 6HUYHU² &KDSWHU  2XWSXW 0DQDJHPHQW ² &KDSWHU  1HWZRUN266HUYHU $GPLQLVWUDWLRQ² &KDSWHU  2SHUDWLRQV ² &KDSWHU  &KDQJH 0DQDJHPHQW ² &KDSWHU  7URXEOHVKRRWLQJ ² &KDSWHU  3HUIRUPDQFH ² &KDSWHU  6$31HW³:HE )URQWHQG² &KDSWHU  6$31HW²5 )URQWHQG ² &KDSWHU  5HPRWH 6HUYLFHV ² &KDSWHU  6SHFLDO 0DLQWHQDQFH ² $SSHQGL[ $ 8VHIXO 7UDQVDFWLRQV $² $SSHQGL[ % 8VHIXO 5HVRXUFHV DQG 3URGXFWV  %² $SSHQGL[ & 8VHIXO 6$3 1RWHV  &² $SSHQGL[ ' 8SJUDGH 'LVFXVVLRQ  '² ,QGH[ ,² System Administration Made Easy iii Contents at a Glance iv Release 4.6A/B 'HWDLOHG 7DEOH RI &RQWHQWV $FNQRZOHGJHPHQWV [L[ ,QWURGXFWLRQ  [[L What Is This Guidebook About? xxii Who Should Read This Book? xxii Prerequisites xxiii User xxiii System xxiv How to Use This Guidebook xxv Organization xxv What’s New xxv Content xxv Conventions xxvi Special Icons xxvii &KDSWHU  5 6\VWHP $GPLQLVWUDWLRQ %DVLFV ² Overview 1–2 Roles of an R/3 System Administrator 1–2 Within R/3 1–2 External to R/3 1–3 Traits of an R/3 System Administrator 1–4 R/3 System Guidelines 1–4 Protect the System 1–5 Do Not Be Afraid to Ask for Help 1–5 Network with Other Customers and Consultants 1–6 Keep It Short and Simple (KISS) 1–7 Keep Proper Documentation 1–7 Use Checklists 1–8 Use the Appropriate Tool for the Job 1–9 Perform Preventive Maintenance 1–9 Do Not Change What You Do Not Have To 1–10 Do Not Make System Changes During Critical Periods 1–11 Do Not Allow Direct Database Access 1–12 Keep all Non-SAP Activity Off the R/3 Servers 1–12 Minimize Single Points of Failure 1–13 Corollaries to Murphy’s Law 1–13 Special Definitions 1–14 Database server 1–14 Application server 1–14 Instance 1–14 System 1–14 &KDSWHU  'LVDVWHU 5HFRYHU\² System Administration Made Easy v Detailed Table of Contents Overview 2–2 What Is a Disaster? 2–2 Why Plan for a Disaster? 2–3 Planning for a Disaster 2–4 Creating a Plan 2–4 What Are the Business Requirements for Disaster Recovery? 2–4 Who will provide the requirements? 2–4 What are the requirements? 2–4 When Should a Disaster Recovery Procedure Begin? 2–5 Expected Downtime or Recovery Time 2–5 Expected Downtime 2–5 Recovery Time 2–6 Recovery Group and Staffing Roles 2–6 Types of Disaster Recovery 2–7 Onsite 2–7 Offsite 2–7 Disaster Scenarios 2–8 Three Common Disaster Scenarios 2–8 A Corrupt Database 2–8 A Hardware Failure 2–8 A Complete Loss or Destruction of the Server Facility 2–9 Recovery Script 2–10 Creating a Recovery Script 2–10 Recovery Process 2–10 Major Steps 2–10 Crash Kit 2–11 Business Continuation During Recovery 2–14 Offsite Disaster Recovery Sites 2–15 Integration with your Company’s General Disaster Planning 2–15 When the R/3 System Returns 2–15 Test your Disaster Recovery Procedure 2–15 Other Considerations 2–16 Other Upstream or Downstream Applications 2–16 Backup Sites 2–17 Minimizing the Chances for a Disaster 2–17 Minimize Human Error 2–17 Minimize Single Points of Failure 2–18 Cascade Failures 2–18 &KDSWHU  %DFNXS DQG 5HFRYHU\ ² Overview 3–2 Restore 3–2 Strategy 3–2 Testing Recovery 3–3 Backup 3–3 What to Backup and When 3–3 Database 3–3 Transaction Logs 3–5 Operating System Level Files 3–6 Backup Types 3–6 What Is Backed Up 3–7 How the Backup Is Taken 3–8 vi Release 4.6A/B Detailed Table of Contents When the Backup Is Made 3–9 Backup Strategy Design 3–9 Supplementary Backups 3–10 General Procedures 3–10 Backup 3–10 Transaction Log Backup 3–10 Verifying Backups 3–10 Monitoring/Controlling 3–11 Database Integrity 3–11 Roles and Responsibilities 3–11 Design Recommendations 3–12 A Strategy Checklist 3–12 Backup Procedures and Policies 3–13 Tape Management 3–13 Tracking and Documenting 3–13 Labeling 3–13 Tracking 3–15 Handling 3–16 Retention Requirements 3–17 Recommendations 3–18 Storage 3–18 Offsite 3–18 Onsite 3–19 Performance 3–20 Backup 3–20 Backup Options 3–21 Back Up to Faster Devices 3–21 Parallel Backup 3–22 Backing Up to Disks, Then to Tape 3–22 Recovery 3–23 Restore Options 3–23 Useful SAP Notes 3–24 &KDSWHU  6FKHGXOHG 'DLO\ 7DVNV² Overview 4–2 Critical Tasks 4–3 The R/3 System 4–4 Database 4–6 Operating System 4–6 Other 4–7 Notes 4–7 The R/3 System 4–8 Critical Tasks 4–9 Verify that R/3 Is Running 4–9 Verify that the Backups Ran Successfully 4–9 Users (Transaction AL08) 4–10 OS Monitor (Transaction OS06) 4–11 Select Background Jobs/Graphical Job Monitor (Transaction SM37/RZ01) 4–11 CCMS Alert Monitor (Transaction RZ20) 4–11 Users (Transactions SM04) 4–11 Lock Entry List (Transaction SM12) 4–12 System Administration Made Easy vii vii Detailed Table of Contents Update Records (Transaction SM13) 4–12 System Log (Transaction SM21) 4–13 Batch Input (Transaction SM35) 4–13 Work Processes (Transactions SM50 and SM51) 4–14 Spool (Transaction SP01) 4–14 Tune Summary (Transaction ST02) 4–14 Workload Analysis of (Transaction ST03) 4–14 Database Performance Analysis (Transaction ST04) 4–15 ABAP Dump Analysis (Transaction ST22) 4–15 &KDSWHU  6FKHGXOHG :HHNO\ 7DVNV ² The R/3 System 5–2 Database 5–3 Operating System 5–3 Other 5–3 Notes 5–4 Database Performance (Transaction DB02) 5–4 CCMS Alert Monitor (Transaction RZ20) 5–4 Spool (Transaction SP01) 5–4 TemSe (Transaction SP12) 5–5 Transaction STMS (TMS System) 5–5 &KDSWHU  6FKHGXOHG 0RQWKO\ 7DVNV² The R/3 System 6–2 Database 6–2 Operating System 6–3 Other 6–4 Notes 6–5 Database Performance (Transaction DB02) 6–5 &KDSWHU  6FKHGXOHG 4XDUWHUO\ 7DVNV ² The R/3 System 7–2 Database 7–3 Operating System 7–3 Other 7–4 Notes 7–4 Edit System Profile Parameters (Transaction RZ10) 7–4 Select Background Jobs (Transaction SM37) 7–5 User Maintenance (Transaction SU01) 7–5 &KDSWHU  6FKHGXOHG $QQXDO 7DVNV ² The R/3 System 8–2 Database 8–3 Operating System 8–3 Other 8–4 Notes 8–4 Transaction SA38/SE38 8–4 Transaction SE03/SCC4 8–4 Transaction SM01 8–5 viii Release 4.6A/B Detailed Table of Contents &KDSWHU  0XOWL5ROH 7DVNV² Starting the R/3 System 9–2 Start R/3—NT 9–3 Stopping the R/3 System 9–5 Tasks to Be Completed Before Stopping the System 9–6 System Message (SM02) 9–6 Check that No Active Users Are on the System (AL08/SM04) 9–9 Check for Batch Jobs Running or Scheduled (SM37) 9–11 Check for Active Processes on All Systems (SM51) 9–15 Check for External Interfaces 9–15 Stopping R/3 9–16 STOP R/3—NT 9–16 &KDSWHU  5 6\VWHP $GPLQLVWUDWLRQ ² Overview 10–2 Major System Monitoring Tools 10–2 CCMS Central Alert Monitor (Transaction RZ20) 10–2 Accessing the CCMS Alert Monitor (RZ20) 10–4 Current View and Alert View 10–5 Switching Between the Current and Alert Views 10–6 Finding an Alert 10–7 Configuring the Batch Job to Collect Historical Data (RZ21) 10–10 View the Alerts 10–12 Analyze the Alert 10–13 Acknowledge the Alert 10–14 Provide System Configuration Information (Transaction RZ20) 10–15 Maintaining The Alert Thresholds for RZ20 10–17 Hiding SAP Standard Monitor Sets 10–19 Create a New Monitor Set 10–23 Add a Monitor to the Monitor Set 10–24 System Administration Assistant (Transaction SSAA) 10–28 Specific Transaction Monitoring Overview 10–32 Failed Updates (Transaction SM13) 10–32 Managing Update Terminates 10–35 User Training 10–37 System Log (Transaction SM21) 10–38 Locks (Transaction SM12) 10–41 Active Users (Transactions SM04 and AL08) 10–43 Single-Instance System (Transaction SM04) 10–44 Multi-Instance System (Transaction AL08) 10–45 Work Processes (Transactions SM50 and SM51) 10–46 For a System with Application Servers 10–46 For a System Without Application Servers 10–47 ABAP Dump Analysis (Transaction ST22) 10–48 Simple Selection 10–49 Free Selection 10–49 System Message (SM02) 10–51 Creating a Message 10–52 Editing a Message 10–54 ABAP Editor (SE38) 10–55 For Information About a Program or Report 10–56 System Administration Made Easy ix ix Detailed Table of Contents &KDSWHU  6HFXULW\ $GPLQLVWUDWLRQ ² Overview 11–2 What is Security? 11–2 Keeping Unauthorized People out of the System 11–2 Keeping People out of Places Where They Should Not Be 11–2 Safeguarding the Data from Damage or Loss 11–3 Complying with Legal, Regulatory, and Other Requirements 11–3 Audits 11–4 Financial Audit 11–4 Security Audit 11–5 Audit Considerations 11–5 Security Layers 11–6 Access Security 11–7 Physical Security 11–7 Network Security 11–8 Application Security 11–9 Operational Security 11–9 Data Security 11–10 Application or R/3 Security 11–11 Controlling Access to R/3 11–11 Prevent Multiple User Logins 11–11 Preventing Changes in the Production System 11–11 Setting the Production System to “Not Modifiable” (Transactions SE03, SCC4)11–13 Client-Independent Changes (Transaction SE03) 11–14 Client-Independent and Client-Dependent Changes (SCC4) 11–15 Verifying that Dangerous Transactions Are Locked 11–17 To List Locked Transactions 11–24 Operational Security 11–25 Segregation of Duties 11–25 Restricting Access to SAP* or DDIC 11–26 Change Management 11–27 Sharing of User IDs 11–27 Password Issues and Tasks 11–28 Setting Password Standards Using Transaction RZ10 11–29 Eliminating Some Easy Passwords 11–29 Maintaining a Table of Prohibited Passwords 11–30 Recording System Passwords 11–31 Operating System Level 11–35 NT 11–35 UNIX 11–36 Databases 11–36 DB2 11–36 Informix 11–36 Microsoft SQL Server 11–36 Oracle/UNIX 11–36 Oracle/NT 11–37 Audit Tools 11–37 Audit Information System (Transaction SECR) 11–37 Complete Audit 11–38 User Defined Audit 11–42 Security Audit Log (SM20) 11–44 Running the Audit Log 11–46 Setting Security Audit Log Parameters (SM19) 11–47 x Release 4.6A/B &KDSWHU  6SHFLDO 0DLQWHQDQFH &RQWHQWV Overview 23–2 Changing System Profile Parameters (Transaction RZ10) .23–2 Support Packages .23–11 Kernel Upgrade 23–40 Client Copy 23–42 Production Refresh Strategies 23–56 System Administration Made Easy 23–1 Chapter 23: Special Maintenance Overview 2YHUYLHZ In this chapter, the reader will learn about special maintenance This topic includes the following: < Kernel upgrade < Client copy < Production refresh strategies &KDQJLQJ 6\VWHP 3URILOH 3DUDPHWHUV 7UDQVDFWLRQ 5= :KDW The system profile parameters are what R/3 uses when it starts up Parameters may define how many of each work process to create, the minimum length of the user password, etc The system uses the following three parameters: < Start This parameter defines which R/3 services are started < Default This parameter defines the profile for all instances in the system < Instance This parameter defines the profile for the specific instance, which allows individual application servers to be configured differently for specific tasks and users :K\ Change a value only for a specific purpose and only with proper knowledge of what is being changed and why it is being changed < If a parameter is incorrectly changed, R/3 may not start Changing system profile parameters should only be done under the instruction of the SAP Hotline, SAP EarlyWatch, or an experienced consultant < Use RZ10 to maintain your profile parameters < Do not modify the files at the operating system level This process could lead to inconsistency and confusion Before making changes to the system profiles, make certain that you have a recent, usable copy of the system profile files This backup is your last line of defense if a profile change is made that results in R/3 not being able to start 23–2 Release 4.6A/B Chapter 23: Special Maintenance Changing System Profile Parameters (Transaction RZ10) *XLGHG 7RXU In the Command field, enter transaction RZ10, and choose Enter (or from the SAP standard menu, choose Tools → CCMS → Configuration → RZ10 - Profile maintenance) In the Profile field, choose Select the instance or default profile as appropriate (for example, the instance profile, SAS – DVEBMGS00 – PA100767) 4 Choose The profiles used by the system work in the following order: < Start profile < < Default profile (for all instances in the system) Instance profile (specific to the instance you are on) System Administration Made Easy 23–3 Chapter 23: Special Maintenance Changing System Profile Parameters (Transaction RZ10) Use the instance profile to make the parameters of a specific application server “different” than the other servers for specific reasons (for example, a batch application server) Under Edit profiles, there are three selections: < Administration data < This selection is not a maintenance mode It is used to change the name of the file where the profile should be activated Basic maintenance (maintenance mode) This mode allows you to set the buffers, work processes, and directories in the system profiles It also allows you to specify the SAP components to be started (for example, message server, application server, SNA gateway, etc.) in start up profiles This form of maintenance protects most profile parameters from being changed by potentially incorrect settings < Extended maintenance (maintenance mode) This mode allows you to access all system profile parameters or start up profile entries Note the Version number of the instance profile Step 32 in this procedure shows the version number has changed Under Edit profile, select Extended maintenance Choose Change 23–4 Release 4.6A/B Chapter 23: Special Maintenance Changing System Profile Parameters (Transaction RZ10) Click on the line above which you want the entry to be inserted (for example, abap/buffersize) Choose Parameter The point where you insert the new profile parameter has no effect on the process But, to make it easier to read, you may want to group or order the parameters (for example, group the logon parameters together) Once you enter the profile parameter, it cannot be easily moved to another location Therefore, be careful where you choose to insert it 10 Click in the Parameter name and choose 10 System Administration Made Easy 23–5 Chapter 23: Special Maintenance Changing System Profile Parameters (Transaction RZ10) 11 The list that appears is long To find the profile parameter you want 13 to add, scroll down 12 Select the parameter 13 Choose 12 14 A default value appears in Unsubstituted standard value 15 Enter the new value in Parameter val (for example, enter to increase the minimum length to five) 17 16 In Comment, document your change by entering a description of why the change was made The system attaches your user ID and date to your comment 15 17 Choose Copy 14 16 23–6 Release 4.6A/B Chapter 23: Special Maintenance Changing System Profile Parameters (Transaction RZ10) 18 This screen shows that the system inserted your user ID and the date and time of the change into the Comment 19 In this way, you can determine who made a profile change, and when this change was made 19 Choose Back 18 20 This screen shows the new parameter login/min_password_lng with a value of inserted above abap/buffersize 21 Choose Copy 21 20 System Administration Made Easy 23–7 Chapter 23: Special Maintenance Changing System Profile Parameters (Transaction RZ10) 22 The message at the bottom of the screen indicates that the profile was changed 23 23 Choose Back 22 24 In Version, note the profile’s version number 25 25 Choose Save 24 26 Choose Yes 26 23–8 Release 4.6A/B Chapter 23: Special Maintenance Changing System Profile Parameters (Transaction RZ10) 27 Choose 27 28 Choose 28 Only if you have operation modes configured, will this screen appear If this screen does not appear, skip to step 32 29 Double-click on Yes 29 System Administration Made Easy 23–9 Chapter 23: Special Maintenance Changing System Profile Parameters (Transaction RZ10) 30 Review the check log 31 Choose 31 32 Note that the profile’s version number has changed 32 Use transaction RZ11 to get the details of a specific profile parameter 23–10 Release 4.6A/B Chapter 23: Special Maintenance Support Packages 6XSSRUW 3DFNDJHV :KDW 1RWH < Hot Packages are now known as R/3 Support Packages < Legal Change Patches (LCP) are known as R/3 HR Support Packages A Support Package is a collection of corrections that address serious errors in the ABAP repository These corrections affect the Basis and functional areas There are defined rules about what kind of fixes should be (and are) included in a Support Package Some rules are technical while other rules are policy A Support Package is not a cumulative fix for application modules You must still get and apply the notes for the functional modules However, since Support Packages contain patches for the various functional areas, some of the notes may be applied in the Support Package The Support Package is not supposed to contain functional enhancements, but this is not always the case :K\ The purpose of a Support Package is to fix problems before they become problems :KHQ There is a conflict about when Hot Packages should be (and are) applied: < To prevent serious problems, SAP’s position is that customers should apply all Support Packages as they are released < The position of many customers is that all system changes must be regression tested Œ This stance, with the frequency of Support Package releases, results in the Support Packages not being applied The reason is that the amount of testing required cannot be done continuously Œ This customer position is not unique to SAP and has been taken by many customers since the early days of computing SAP development is working on ways to make Support Package application easier 1RWH As of Release 4.5, Hot Packages have been separated from the HR Legal Change Patch (HR LCP) This separation allows LCPs to be applied quickly, to be in legal compliance, and not applying Support Packages before they are scheduled to be applied Before Release 4.5, the LCP contained the Hot Packages; applying a LCP also meant applying the Hot Package System Administration Made Easy 23–11 Chapter 23: Special Maintenance Support Packages 6WUDWHJ\ Obtain the notes related to the Support Package, and review what it fixes: < If there is nothing in the Support Package that applies to you, not apply it < If there is something in the Support Package that applies to you: Œ Determine if the entire Support Package (or just the note) must be installed Œ If the Support Package is to be installed, treat the installation as a “mini-upgrade.” +LJK/HYHO 3URFHVV RI $SSO\LQJ 6XSSRUW 3DFNDJHV Applying Support Packages Determine what Support Packages have been applied to your system Get and review the notes for the Support Package(s) Determine if the Support Package should be or needs to be applied Steps through assume that the Support Package is to be applied and are repeated for all Support Packages that are to be applied at the current time Obtaining the Support Package Depending on the size of the Support Package, it can be obtained three ways: < Download it from the SAPNet–R/3 (formerly OSS) This option is size limited, so large Support Packages cannot be downloaded via SAPNet–R/3 < Download it from SAPNet–Web < Upload it from the Support Package collection on CD The Support Package collection contains all Support Packages available at that point in time Download from SAPNet – R/3 (OSS) Download from SAPNet –Web Support Package collection on CD Request the Support Package from the SAPNet–R/3 Download the Support Package Request the Hot Package collection Download the Support Package N/A Upload the Hot Package Apply the Support Package Execute the regression test When successful, confirm the Support Package 23–12 Release 4.6A/B Chapter 23: Special Maintenance Support Packages 'HWHUPLQLQJ :KDW 6XSSRUW 3DFNDJHV +DYH %HHQ $SSOLHG *XLGHG 7RXU 0HWKRG  From the menu bar, choose System → Status On the right-hand side of this screen, under SAP System data, for additional choose component information Choose the Patches tab System Administration Made Easy 23–13 Chapter 23: Special Maintenance Support Packages In this example, the following patches have been applied: < SPAM update 17-Sept-99 < Support Package 01 for 4.6A Patch status values are: < N – The patch has not yet been applied < I – Patch has been successfully applied < ? – Patch application has been aborted The Support Package name is interpreted as follows: < SAPKH < SAPKH46A01, interpreted as SAPKH / 46A / 01, is for Release 4.6A and is the first Support Package 0HWKRG  In the Command field, enter transaction SPAM and choose Enter (or from the SAP standard menu, choose Tools → ABAP Workbench → Utilities → Maintenance→ SPAM - Patches) Select Applied patches Choose Display 23–14 Release 4.6A/B ... 4? ??3 The R/3 System 4? ? ?4 Database 4? ? ?6 Operating System 4? ? ?6 Other 4? ??7 Notes 4? ??7 The R/3 System 4? ??8 Critical Tasks... the users, 800 × 60 0 < For the system administrator, 10 24 × 768 and a minimum color depth of 2 56 colors The Release 4. 6 GUI displays better with 64 K colors xxiv xxiv Release 4. 6 A/B Introduction... xxvii System Administration Made Easy xxi Introduction What Is This Guidebook About? :KDW ,V 7KLV *XLGHERRN $ERXW" 3KLORVRSK\ Release 4. 6 of the System Administration Made Easy Guidebook