$SysAdm Made Easy 46cd (entire book-2002)

ASystem

Administration

Made Easy

for SAP Basis 4.6C/D

SAP Labs, Inc.

Palo Alto, California

Copyright

© 2002 by SAP AG. All rights reserved.

Neither this documentation nor any part of it may be copied or reproduced inany form or by any means or translated into another language, without theprior consent of SAP AG.

Disclaimer

SAP AG makes no warranties or representations with respect to the contenthereof and specifically disclaims any implied warranties of merchantability orfitness for any particular purpose. SAP AG assumes no responsibility for anyerrors that may appear in this document. The information contained in thisdocument is subject to change without notice. SAP AG reserves the right tomake any such changes without obligation to notify any person of suchrevision or changes. SAP AG makes no commitment to keep the informationcontained herein up to date.

Trademarks

SAP, the SAP logo, mySAP.com, R/2, R/3, ABAP, mySAP, mySAP.com, andother SAP-related products mentioned herein are registered or unregisteredtrademarks of SAP AG. All other products mentioned in this document areregistered or unregistered trademarks of their respective companies.

Simplification GroupSAP Labs, Inc.3475 Deer Creek RoadPalo Alto, CA 94304

www.saplabs.com/simple

[email protected]

Printed in the United States of America.ISBN 1-893570-44-4

C O N T E N T S

Acknowledgements ............................................................. xxi

Introduction xxiii

What Is This Guidebook About? ..........................................xxiiiAbout This Guide ................................................................ xxvWho Should Read This Book? .................................................................xxvPrerequisites ...........................................................................................xxv

User .................................................................................................xxviSystem .............................................................................................xxvi

How to Use This Guidebook ..............................................xxviiiOrganization ................................................................................. xxviii

What’s New .....................................................................xxviiiContent .......................................................................................... xxviii

Conventions ....................................................................... xxixSample R/3 Release 4.6 Screen .............................................................xxxSpecial Icons ...........................................................................................xxx

iv System Administration Made Easy | Release 4.6C/D

Part 1: System Administration Overview . . . . . . . . . . . . 1

Part Overview .........................................................................2

Chapter 1: System Administration Basics 3

Overview ................................................................................4Roles of a System Administrator ..............................................4Within the mySAP.com component ............................................................ 5External to the mySAP.com component ..................................................... 5System Administrator Traits ....................................................6System Guidelines ...................................................................6Protect the System ...................................................................................... 7Do Not Be Afraid to Ask for Help .............................................................. 7Network with Other Customers and Consultants ........................................ 8Keep It Short and Simple (KISS) ................................................................ 8Keep Proper Documentation ...................................................................... 8Use Checklists ............................................................................................ 9Use the Appropriate Tool for the Job ......................................................... 9Perform Preventive Maintenance ............................................................... 9Do Not Change What You Do Not Have To ............................................10Do Not Make System Changes During Critical Periods ...........................11Do Not Allow Direct Database Access ....................................................11Keep all Non-SAP Activity Off the mySAP Servers ...................................12Minimize Single Points of Failure .............................................................12Special Definitions .................................................................13

Part 2: Disaster Planning Overview . . . . . . . . . . . . . . . . 15

Part Overview .......................................................................16

Chapter 2: Disaster Recovery 17

Overview ..............................................................................18What Is a Disaster? ...............................................................18Why Plan for a Disaster? .......................................................18Planning for a Disaster ..........................................................19Creating a Plan ........................................................................................19

Contents v

What Are the Business Requirements for Disaster Recovery? ...................20When Should a Disaster Recovery Procedure Begin? ..............................21Expected Downtime or Recovery Time .....................................................21

Expected Downtime ...........................................................................21Recovery Time ...................................................................................21

Recovery Group and Staffing Roles .........................................................22Types of Disaster Recovery ......................................................................23

Onsite ................................................................................................23Offsite ................................................................................................23

Disaster Scenarios .................................................................23Three Common Disaster Scenarios ...........................................................24

A Corrupt Database ...........................................................................24A Hardware Failure ...........................................................................24A Complete Loss or Destruction of the Server Facility ........................24

Recovery Script ......................................................................25Creating a Recovery Script ......................................................................26Recovery Process ...................................................................26Major Steps .............................................................................................26Crash Kit ..................................................................................................27Business Continuation During Recovery ...................................................29Offsite Disaster Recovery Sites .................................................................30Integration with your Company’s General Disaster Planning ...................30When the SAP R/3 System Returns .........................................................30Test your Disaster Recovery Procedure ....................................................30Other Considerations .............................................................32Other Upstream or Downstream Applications .........................................32Backup Sites .............................................................................................32Minimizing the Chances for a Disaster ....................................32Minimize Human Error .............................................................................33Minimize Single Points of Failure .............................................................33Cascade Failures .....................................................................................34

Chapter 3: Backup and Recovery 35

Overview ..............................................................................36Restore ..................................................................................36Strategy ...................................................................................................36

Testing Recovery ................................................................................37Backup ..................................................................................37What to Backup and When ......................................................................37

Database ...........................................................................................37Transaction Logs ................................................................................38Operating System Level Files .............................................................39

Backup Types ...........................................................................................40What Is Backed Up ............................................................................41

vi System Administration Made Easy | Release 4.6C/D

How the Backup Is Taken ...................................................................42When the Backup Is Made .................................................................43

Backup Strategy Design ...........................................................................44Supplementary Backups .....................................................................45

General Procedures .................................................................................45Backup ...............................................................................................45Transaction Log Backup .....................................................................45Verifying Backups ..............................................................................45Database Integrity .............................................................................45Roles and Responsibilities ..................................................................46

Design Recommendations ........................................................................46Database ...........................................................................................46Transaction Logs ................................................................................46Operating System Level Files .............................................................47A Strategy Checklist ...........................................................................47Backup Procedures and Policies .........................................................48

Tape Management .................................................................48Tracking and Documenting .....................................................................48

Labeling .............................................................................................49Tracking .............................................................................................51Handling ............................................................................................51

Retention Requirements ...........................................................................52Recommendations ..............................................................................53Tape Retention Period ........................................................................53

Storage ....................................................................................................53Offsite ................................................................................................53Onsite ................................................................................................54

Performance ..........................................................................54Backup .....................................................................................................55Backup Options .......................................................................................55

Back Up to Faster Devices ..................................................................55Parallel Backup .................................................................................56Backing Up to Disks, Then to Tape .....................................................57

Recovery ..................................................................................................57Restore Options .......................................................................................57Useful SAP Notes ...................................................................58

Contents vii

Part 3: Tasks Overview . . . . . . . . . . . . . . . . . . . . . . . . . .61

Part Overview .......................................................................62

Chapter 4: Scheduled Tasks 63

Overview ..............................................................................64Daily ......................................................................................65Critical Tasks ............................................................................................65The SAP R/3 System ................................................................................65Database .................................................................................................67Operating System ....................................................................................68Other .......................................................................................................68Notes .......................................................................................................68The SAP R/3 System ................................................................................69Critical Tasks ............................................................................................70

Verify that SAP R/3 Is Running ..........................................................70Verify that the Backups Ran Successfully ............................................70

Weekly ..................................................................................74The SAP R/3 System ................................................................................74Database .................................................................................................74Operating System ....................................................................................75Other .......................................................................................................75Notes .......................................................................................................75Monthly .................................................................................77The SAP R/3 System ................................................................................77Database .................................................................................................77Operating System ....................................................................................77Other .......................................................................................................78Notes .......................................................................................................78Quarterly ..............................................................................79The SAP R/3 System ...............................................................................79Database .................................................................................................80Operating System ....................................................................................80Other .......................................................................................................80Notes .......................................................................................................81Annual ...................................................................................82The SAP R/3 System ................................................................................82Database .................................................................................................83Operating System ....................................................................................83Other .......................................................................................................84Notes .......................................................................................................84

viii System Administration Made Easy | Release 4.6C/D

Chapter 5: Multi-Role Tasks 87

Starting the SAP R/3 system ..................................................88Start SAP R/3–NT (SQL Server, Oracle) .................................................88Stopping the SAP R/3 system .................................................90Stop SAP R/3 Checklist ............................................................................91Tasks to Be Completed Before Stopping the System ................................91

System Message (SM02) ...................................................................92Check that No Active Users Are on the System (AL08/SM04) ..........94Check for Batch Jobs Running or Scheduled (SM37) .........................95Check for Active Processes on All Systems (SM51) ...........................99Check for External Interfaces ...........................................................100

Stopping SAP R/3 .................................................................................100STOP SAP R/3–NT ..........................................................................101

Chapter 6: SAP System Administration 105

Overview ............................................................................106Major System Monitoring Tools ...........................................106CCMS Central Alert Monitor (Transaction RZ20) ..................................106

Current View and Alert View ...........................................................109Maintaining The Alert Thresholds for RZ20 .....................................120Hiding SAP Standard Monitor Sets ..................................................124Create a New Monitor Set ...............................................................127

System Administration Assistant (Transaction SSAA) .............................132Specific Transaction Monitoring Overview ...........................136Failed Updates (Transaction SM13) ......................................................136Managing Update Terminates ...............................................................139

User Training ...................................................................................141System Log (Transaction SM21) ............................................................142Locks (Transaction SM12) .....................................................................145Active Users (Transactions SM04 and AL08) ........................................148

Problems ..........................................................................................148Work Processes (Transactions SM50 and SM51) ..................................150ABAP Dump Analysis (Transaction ST22) ..............................................152System Message (SM02) ......................................................155Editing a Message .................................................................................156ABAP Editor (SE38) ...............................................................................158

For Information About a Program or Report ....................................159

Contents ix

Part 4: Security Overview . . . . . . . . . . . . . . . . . . . . . . .161

Part Overview .....................................................................162Central User Administration (CUA) ........................................................162Single Sign-On (SSO) ............................................................................162

Chapter 7: Security Administration 163

Overview ............................................................................164What Is Security? ...................................................................................164

Keeping Unauthorized People Out of the System ............................164Keeping Users out of Prohibited System Areas ................................165Safeguarding the Data from Damage or Loss ..................................165Complying with Legal, Regulatory, and Other Requirements ...........165

Audits ..................................................................................166Financial Audit .......................................................................................166Security Audit ........................................................................................167Audit Considerations ..............................................................................167Security Layers ....................................................................168Access Security ......................................................................................168

Physical Security ..............................................................................168Network Security .............................................................................169Application Security .........................................................................170

Operational Security .............................................................................170Data Security .........................................................................................171Application or SAP R/3 Security ............................................................172

Controlling Access to SAP R/3 .........................................................172Prevent Multiple User Logins ............................................................172

Preventing Changes in the Production System ........................................172Setting the Production System to “Not Modifiable” (Transactions SE03, SCC4) ............................................................................................174

Verifying that Dangerous Transactions Are Locked ...............................178Operational Security ............................................................186Segregation of Duties ............................................................................186

Accounts Receivable and Cash Collection .......................................187Restricting Access to SAP* or DDIC .......................................................187Change Management ............................................................................188

Sharing of User IDs ..........................................................................188Password Issues and Tasks .....................................................................189

Setting Password Standards Using Transaction RZ10 ......................189Eliminating Some Easy Passwords ....................................................189Maintaining a Table of Prohibited Passwords ..................................190Recording System Passwords ...........................................................191

x System Administration Made Easy | Release 4.6C/D

Operating System Level ...................................................................194NT ....................................................................................................194UNIX ................................................................................................195Databases ........................................................................................195DB2 ..................................................................................................195Informix ...........................................................................................195Microsoft SQL Server .......................................................................195Oracle/UNIX ...................................................................................195Useful SAP Notes for Oracle/UNIX .................................................195Oracle/NT .......................................................................................196

Audit Tools ...........................................................................196Audit Information System (Transaction SECR) ........................................196Security Audit Log (SM20) ....................................................................203

Running the Audit Log ......................................................................204Setting Security Audit Log Parameters (SM19) ......................................206User Security Audit Jobs ........................................................................214Audit Tasks ..........................................................................217Review that all Named Users are Valid .................................................217Reviewing Profiles for Accuracy and Permission Creep .........................218

Chapter 8: User Administration 219

Overview ............................................................................220User Groups ..........................................................................................220Profile Generator ...................................................................................220Recommended Policies and Procedures ...............................220User Administration ...............................................................................221System Administration ............................................................................222

Special user IDs ...............................................................................222User passwords ...............................................................................223Sample SAP R/3 User Change Request Form ..................................224

New User Setup ...................................................................225Prerequisites ..........................................................................................225

General Process or Procedure .........................................................225The User’s Desktop ..........................................................................225Network Functionality ......................................................................225For Installation of SAP GUI ..............................................................225

Installing the Frontend Software—SAP GUI ............................................226Installing SAP GUI from a File Server ..............................................226Installing SAP GUI from the Presentation CD ...................................231

Adding Additional Systems ....................................................................232Setting Up a New User (SU01) .............................................................233

Copying an Existing User (SU01) ....................................................233Creating a New User (SU01) ..........................................................237

Maintaining a User (SU01) ...................................................241

Contents xi

Resetting a Password (SU01) ...............................................242Locking or Unlocking a User (SU01) .....................................243Locking a user ........................................................................................244Unlocking a user ....................................................................................244User Groups ........................................................................245Usage ....................................................................................................245How to Create a User Group (SU01) ....................................................246Deleting a User’s Session (Transaction SM04) ......................247Terminate a User Session .......................................................................248Active Users (Transactions SM04 and AL08) ........................................248

Problems ..........................................................................................249

Part 5: Database Overview . . . . . . . . . . . . . . . . . . . . . .251

Part Overview .....................................................................252

Chapter 9: Database Administration - IBM DB2 Universal Database

253

Overview ............................................................................254Starting and Stopping the Database ....................................254DB2 UDB Administration in SAP Systems ..............................255Database Performance (ST04) ..............................................................255Space Allocation ...................................................................................259Backups and Recovery ...........................................................................260Scheduling Database Administration Tasks (DB13) ...............................264Reviewing the DBA Planning Calendar ..................................................266Diagnostics ............................................................................................268Command Line Processor .....................................................269The DB2 UDB Control Center .................................................273

Chapter 10: Database Administration — Microsoft SQL Server 275

Overview ............................................................................276Starting and Stopping the Database ....................................276Database Performance ........................................................278Overview ...............................................................................................278Database Activity (ST04) .......................................................................278Database Allocation (DB02) .................................................................282Scheduling Database Tasks (DB13) ......................................284

xii System Administration Made Easy | Release 4.6C/D

Determining the Tape (Label) Necessary for a Backup ..........................288Deleting an Entry from the Planning Calendar (DB13) ..........................290Checking the Database Backup (DB12) ................................291Initializing Backup Tapes .....................................................293Database Backups with Microsoft Tools ...............................293Online Backup — Using SQLserver 2000 Enterprise Manager ..............294Offline Backup — Using Windows 2000 Backup ....................................298Viewing Database Error Logs ...............................................303SAP R/3 — Database Performance Analysis (ST04) ..............................303Verify Database Consistency ...............................................305Run Update Statistics ...........................................................305System Passwords ...............................................................305SQL server .............................................................................................305

Chapter 11: Database Administration — Informix 309

Overview ............................................................................310Scheduling Database Tasks ..................................................310Initializing the DBA Planning Calendar ..................................................310Scheduling a DBA Task to Run Regularly ...............................................312Checking the Status of DBA Tasks ..........................................................313Changing DBA Tasks .............................................................................315Backing Up the Database .....................................................317Requirements for Backing Up the Database ...........................................317Scheduling Backups of Database Data ..................................................317Backing Up Logical Log Data .................................................................321Checking the Database System ............................................321Viewing the Database Message Log ....................................324Updating Statistics ...............................................................326Checking Database Consistency ...........................................327Checking Database Disk Space ...........................................329Using SAPDBA .....................................................................333What is SAPDBA? ..................................................................................333Getting Started with SAPDBA ................................................................334Starting and Stopping the Database ......................................................334Extending a Dbspace ...........................................................337Further Information .............................................................341

Chapter 12: Database Administration — Oracle Database 343

Overview ............................................................................344Starting and Stopping the Database ....................................344Computing Center Management System (CCMS) ..................349

Contents xiii

Database Performance Monitor .............................................................350Database Tables and Indexes Analysis ..................................................353Scheduling Database Tasks (DB13) ......................................355Scheduling the DBA task ........................................................................355Scheduling Predefined Action Patterns ...................................................356The Database Utility .............................................................360SAPDBA ...............................................................................363Checking the Database ........................................................366Checking the Database System ..............................................................366Database Verification ............................................................................369SAPDBA Backup Tasks .........................................................371Initializing the Backup Tapes ..................................................................371

Initializing the Database Backup (BRBACKUP) Tape .......................371Initializing the Archive Tape ..................................................................374Back Up .................................................................................................378

Determining the Tapes Required to Back Up ....................................378Backing Up the Database ................................................................378Back Up the Archive Logs ................................................................381

Useful Online Service System Notes .....................................384

Part 6: Operations Overview . . . . . . . . . . . . . . . . . . . .385

Part Overview .....................................................................386

Chapter 13: Output Management 387

Overview ............................................................................388Printer Setup (SPAD) ............................................................388Check the Spool for Printing Problems (Transaction SP01) ....394Check that Old Spools are Deleted (SP01) ............................397Printing the Output (SP01) ...................................................401Printing the Screen ...............................................................404Check Spool Consistency (SPAD) ..........................................407Check TemSe Consistency (SP12) ..........................................409

Chapter 14: Network/OS/Server Administration 411

Overview ............................................................................412Operating System Tasks ......................................................412System Logs (OS06) ..............................................................................412

xiv System Administration Made Easy | Release 4.6C/D

Checking File System Space Usage (RZ20) ...........................................414Changing the Alert Threshold (RZ20) ....................................................416Cleaning Out Old Transport Files ..........................................................418Other Tasks .........................................................................419Clean the Tape Drive .............................................................................419Uninterruptible Power Supply ................................................................420

Check the Uninterruptible Power Supply ..........................................420Check your UPS Shutdown Process ..................................................420

Check Maintenance Contracts ...............................................................421Review Hardware or a System Monitor Paging System .........................421

Chapter 15: Operations 425

Overview ............................................................................426Check that All Application Servers Are Up (Transaction SM51) ...426

Background (Batch) Jobs .....................................................427Regularly Scheduled Jobs ......................................................................427

Batch User ID ...................................................................................428Performance ....................................................................................428Housekeeping Jobs ..........................................................................428Others ..............................................................................................428

Performance Factors for Background Jobs .............................................429Creating and Scheduling a Batch Job (SM36) ......................................431Background Jobs (SM37) .....................................................439

Checking the Job Log .......................................................................441Graphical Job Monitor (Transaction RZ01) ...........................................442Batch Input Jobs, New or Incorrect (SM35) ..........................................443Operation Modes ................................................................445Backups ...............................................................................458Periodic Archival ....................................................................................458Backup the Database .............................................................................458Performing a Full Server Backup ............................................................458

Operating System Level Backups .....................................................462UNIX ................................................................................................462NT ....................................................................................................462

Checking Consumable Supplies ............................................462Other Considerations .............................................................................464

Chapter 16: Change Management 465

Overview ............................................................................466Table Maintenance (Transaction SM31) ................................466

Contents xv

Creating an Entry in the Table (SM31) ..................................................466Deleting an Entry from a Table (SM31) .................................................470Change Control ....................................................................472Managing SAP Notes ...........................................................472Sample Forms ........................................................................................473

General Note Record ......................................................................473Detailed Online Service System Note Record ..................................474

Note Assistant .....................................................................475Change Control (Managing Transports) ................................483

Sample Transport Request Form ......................................................485Transporting Objects ............................................................486Transports into the Production System ....................................................486Transporting Objects ..............................................................................486

TMS Method ....................................................................................487Operating System Method ...............................................................487

Standard Transport Process ...................................................................488Importing the Entire Import Buffer ....................................................488

Special Transports from SAP ..................................................................489Releasing a Request (Transport) ............................................................490TMS Method of Transporting .................................................................495

Adding a Special Transport into the Import Buffer ...........................495OS Method of Transporting ...................................................................507

Adding a Special Transport Into the Import Buffer ...........................507Importing the Transport ....................................................................508Checking the Transport Log (Transaction SE10) ..............................509

Part 7: Troubleshooting and Performance Overview .513

Part Overview .....................................................................514

Chapter 17: Troubleshooting 515

Overview ............................................................................516Basic Troubleshooting Techniques ........................................516

Gather Data .....................................................................................516Analyze the Problem .......................................................................517Evaluate the Alternatives .................................................................517Make only One Change at a Time ...................................................517Document the Changes ....................................................................517

Get the Complete Error Message ..........................................................517Get the SAP Patch Level .........................................................................518Determining What Support Packages Have Been Applied .....................520

xvi System Administration Made Easy | Release 4.6C/D

Chapter 18: Performance 523

Overview ............................................................................524Critical Assumption ................................................................................524Priority of Evaluation .............................................................................524General Procedure ..............................................................525SAP R/3 ...............................................................................525Workload Analysis of the System (Transaction ST03N) .........................525Buffers (ST02) ........................................................................................529Memory Defragmentation .....................................................................530Database .............................................................................531Operating System ................................................................531Operating System Monitor (OS07) .......................................................531Hardware ............................................................................535CPU and Disk .........................................................................................535Memory .................................................................................................535

Part 8: Miscellanous Topics Overview . . . . . . . . . . . . . 537

Part Overview .....................................................................538

Chapter 19: SAP Service Marketplace 539

Overview ............................................................................540Logging on to SAPNet ..........................................................540Navigation ..........................................................................542Solving a Problem with SAPNet ...........................................543Customer Messages ...............................................................................547Entering Customer Messages .................................................................547

Priority table ....................................................................................547Component ......................................................................................548Problem Description .........................................................................548

Viewing Customer Messages .................................................................554Registering a Developer or Object .......................................559Registering a Developer ........................................................................560

Enter the Developer Key ..................................................................564Registering an Object ............................................................................565

Enter the Object Key ........................................................................570SAP Software Center ...........................................................571Getting the Latest SPAM version ............................................................573Connecting to SAPNet ..........................................................582

Contents xvii

Prerequisites ...........................................................................................582Opening a Service Connection .............................................585Order of Access to Systems ...................................................................586

Chapter 20: Remote Services 593

Overview ............................................................................594Retrieving Files from SAP, SAPSERV .....................................594

NT ....................................................................................................595UNIX ................................................................................................595

Connecting to SAPSERV Using a GUI (NT) ...........................................595An FTP Client Example ...........................................................................595Connecting to SAPSERV Using the Command Prompt ............................597

Navigating in SAPSERV ...................................................................597Connecting at the Command Prompt .....................................................598Downloading Files .................................................................................600Partial Organization of SAPSERV ..........................................................602

Unpacking a CAR or SAR File ..........................................................603Special SAPNet Notes .....................................................................604

EarlyWatch Service ..............................................................605

Chapter 21: Special Maintenance 607

Overview ............................................................................608Changing System Profile Parameters (Transaction RZ10) .....608Support Packages ................................................................617Strategy .................................................................................................617Applying Support Packages ...................................................................618Determining What Support Packages Have Been Applied .....................619Requesting SPAM or a Support Package from SAPNet .........................630

Downloading a Support Package (Hot Package) — SAPNet ...........633Uploading the Support Package from a CD or SAP Service Marketplace ...

634Support Package Collection CD .......................................................634SAP Service Marketplace ................................................................635

Updating SPAM .....................................................................................640Applying the Support Package ..............................................................643Object Conflicts .....................................................................................649Regression Testing .................................................................................650Useful SAP Notes ...................................................................................650Kernel Upgrade ...................................................................651

Restart Option 1 ..............................................................................653Restart Option 2 ..............................................................................653

xviii System Administration Made Easy | Release 4.6C/D

Client Copy ..........................................................................653Special Notes ..................................................................................653Some Useful SAP Notes ...................................................................654Processing Notes .............................................................................654Security ............................................................................................655

Creating a Client ....................................................................................655Copying a Client ....................................................................................658

Copying on the Same System/SID ...................................................658Copying to a Different System/SID ..................................................662

Post-Client Copy Tasks ...........................................................................664Deleting a Client ....................................................................................665Production Refresh Strategies ..............................................668Database Copy of Production System ....................................................668

Benefits ............................................................................................669Disadvantages .................................................................................669

Client Copy of the Production System with Data ....................................669Advantages .....................................................................................669Disadvantages .................................................................................670

Client Copy of the Production System — Without Data ...........................670Advantages .....................................................................................670Disadvantages .................................................................................670

Part 9: Appendixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

Appendix A: Useful Transactions 673

Transaction Code Switches ....................................................................673Transaction Code Table .........................................................................674

Dangerous .......................................................................................674Performance Impact .........................................................................674

Appendix B: Useful Resources and Products 681

Other System Administration Resources ..............................681SAP Resources .......................................................................................681

Books ..............................................................................................682CDs ..................................................................................................683Training Classes ...............................................................................684Other ...............................................................................................684White papers ...................................................................................685SAPNet, Selected Items of Interest ...................................................685

Third-Party Resources .............................................................................686

Contents xix

SAP R/3 Books Written by SAP Employees .....................................686SAP R/3 Books Written by Third-Party Authors ................................687UNIX Books .....................................................................................687Microsoft Windows NT Books ..........................................................687OS/400 Books ................................................................................688Microsoft SQL Server Books ............................................................689Informix Books .................................................................................689DB2 Books .......................................................................................689Oracle Books ...................................................................................690Books on Other Topics .....................................................................690Magazines .......................................................................................691Helpful Third-Party Information ........................................................691

Web Sites ..............................................................................................692SAP ..................................................................................................692SAP Affiliates ...................................................................................692Third-Party ........................................................................................692

Internet News Groups ...........................................................................692Other Resources ....................................................................................693

Operating System ............................................................................693Database .........................................................................................693

Other Helpful Products: Contributed by Users ......................694UNIX ......................................................................................................694

Backup .............................................................................................694Monitor ............................................................................................694Scheduler .........................................................................................694Spool Management .........................................................................695Other ...............................................................................................695

NT ..........................................................................................................695Backup .............................................................................................695Monitor ............................................................................................695Remote Control ................................................................................695Scheduler .........................................................................................696Spool Management .........................................................................696Other ...............................................................................................696

Common, Both UNIX and NT .................................................................696Network .................................................................................................697

Appendix C: Useful SAP Notes 699

Overview ............................................................................699SAP Notes ............................................................................700Operating System Notes ......................................................704Common to Multiple Operating Systems ................................................704NT ..........................................................................................................704UNIX ......................................................................................................706

xx System Administration Made Easy | Release 4.6C/D

AS-400 ..................................................................................................706Database Notes ...................................................................707MS SQL server .......................................................................................707DB2 / UDB ............................................................................................709Informix .................................................................................................710Oracle ...................................................................................................711

Appendix D: Upgrade Discussion 715

Upgrade Discussion .............................................................715Reasons Not to Upgrade .......................................................................715When to Upgrade ..................................................................................716Upgrade Issues ....................................................................716Other Considerations ...........................................................717Software Issues ......................................................................................717Hardware ..............................................................................................717Performance ..........................................................................................718

Appendix E: Training / Learning 719

Training / Learning ..............................................................719Mini-Basis system ...................................................................................719

Appendix F: Monitoring Multiple SAP R/3 Systems 721

Overview ............................................................................721Configuring the Batch Job to Collect Historical Data (RZ21) ...........726

Index 731

xxi

Acknowledgements

The combined experience in SAP and general systems administration of thosewho contributed to this book is measured in decades. I hope that I am able toshare with you some of their wisdom.

I also wish to express appreciation to the following individuals who providedtime, material, expertise, and resources that helped make the Release 4.6C/Dguidebook possible:

Customers and partners: Michelle Alexander, Pfizer/IBM; Thomas Beam,National Credit Union Administration; Sreeni Challa ; Ronnie Fong, ATI; NazHaji; Patricia Kenny, Sony; Shanell Lowary ; Udesh Naicker, HP/Synopsys;Karen Richmond, Baldor; Vladimir Sytnykov, Optimum; Khanh Vo, Avanti.

SAP: Dieter Babutzka, Sari Bearson, Ronald Binford, Dr. Meinolf Block,Regine Brehm, Dr. Thomas Brodkorb, Eddie Carter, Michael Demuth, Dr.Stefan Fuchs, Andreas Graesser, Christian Graf, Volker Groeschel, RolandHamm, Christian Hiller, Uwe Inhoff, Indradev Kadidal, “Casper” Wai-FuKann, Steven Kerner, Dr. Wulf Kruempelman, Gisbert Loff, Sue McFarland,Dr. Christoph Nake, Lance Pawlikowski, Benjamin Prusinski, SriramRaghunathan, Raj Rathnam, Dr. Gert Rusch, Joerg Schmidt, Dr. Carsten Thiel,Jeffrey Thomas, Fabian Troendle, Jackie Wang, Mark Weber, William WillisJr., “Jody” Honghua Yang, Kitty Yue.

Authors: Agapius Chan, Jim Chen, Aidan Constable, Sven-Uwe Kusche,Gary Nakayama

Documentation, Planning, and Production: Scott Bulloch, Usha Nair,Noelle Wolf

Gary Nakayama, CPASAP Labs, Inc., 2002

xxii System Administration Made Easy | Release 4.6C/D

I N T R O D U C T I O N

1Introduction

What Is This Guidebook About?

The System Administration Made Easy Guidebook, release 4.6C/D,continues in the direction of the 4.0B and 4.6A/B versions. Theprimary focus of this guidebook is the importance of the on-goingnature of system administration. This book is written for a systemwhere all installation tasks have been completed. Installation andrelated tasks, which are usually performed once, are not covered inthis guidebook.

At the application layer, as shown in the following diagram, thevarious mySAP.com components are built on the Basis layer. ThemySAP.com components include:

� Customer Relationship Management (CRM)

� Advanced Planner and Optimizer (APO)

xxiv System Administration Made Easy | Release 4.6C/D

� Business Warehouse (BW)

Because this design uses a common Basis layer, tasks learned in SAP R/3system administration can be leveraged for use with other mySAP.comcomponents. Therefore, as long as the mySAP.com component has a Basislayer, you will be able to manage and administer it the same as all othermySAP.com components with a Basis layer.

Additionally, there may be administrative tasks specific to the component.

Other components do not have a basis layer, such as:

� Internet Transaction Server (ITS)

� CRM, Communication Station (part of the CRM Mobile Sales component)

� CRM, Business Application Studio, Development Server (part of the CRMMobile Sales component)

Because these components do not have a Basis layer, the administration ofthese components is specific to the component itself. The systemadministration of these components will not be discussed in this guidebook.

While we do not go into the specifics of administering the variouscomponents, we will discuss the tasks that are common to them.

Except where there is a significant difference in the transaction (screen),enough to cause confusion, we will not make a distinction between a 4.6Ctransaction and a 4.6D transaction. Because screenshots will come from eithera 4.6C or 4.6D system, the appearance of the screens may be different from thesystem you are on.

You may see other visual differences between the screen shots in theguidebook and what you see on your system. In addition to the versiondifference mentioned above, several other factors will affect how a screenappears to a user, such as:

� The level of the support packages that has been applied to the system.

� The version and patch level of the GUI that is used.

We have tried to group items and tasks in job role categories, which allowsthis guidebook to be a better reference book.

Introduction xxv

Real-world practical advice from consultants and customers has beenintegrated into this book. Because of this perspective, some of the statementsin this book are blunt and direct. Some of the examples we have used mayseem improbable, but many are based on real situations.

Simplifying system administration tasks for a Made Easy guidebook is not asimple task. The material in this guidebook was carefully chosen, but may notbe comprehensive.

Installation tasks are not presented. We assume that your SAP consultant hascompleted these tasks, in keeping with the guidebook philosophy.

Although there are chapters on problem solving and basic performancetuning, these chapters only serve to introduce the subjects. This guidebook isnot meant to be a trouble shooting or performance-tuning manual.

About This Guide

Who Should Read This Book?

The target audience for this guidebook is:

� The customer person or team where:

• The mySAP Technology administrator is from a small to mid-sizecompany with a small (one to three people) technical team.

• Each team member in the team has multiple job responsibilities.

• The system administrator has a basic knowledge of the operatingsystem and database.

� The junior consultant

Senior consultants, experienced system administrators, and databaseadministrators (DBAs) may find portions of this guidebook elementary, buthopefully useful.

Prerequisites

To help you use this guidebook, we defined a baseline for user knowledgeand system configuration. The two sections below (User and System) definethis baseline. Review these sections to determine how you and your systemmatch. This book is also written with certain assumptions about yourknowledge level and the expectation that particular system requirementshave been met.

xxvi System Administration Made Easy | Release 4.6C/D

User

We assume that you have a baseline knowledge of mySAP.com components,the operating system, and the database. If you lack knowledge in any of thefollowing points, we recommend that you consult the many books andtraining classes that specifically address your operating system and database.

You should know how to complete the following tasks at the:

� mySAP.com component level:

• Be able to log on to the mySAP.com component

• Know how to navigate in the mySAP.com component using menusand transaction codesSome screens do not have menu paths and can only be accessed withtransaction codes. Navigating by transaction codes is faster and moreefficient than menus.

� Operating system level:

• Be familiar with the file and directory structure

• Be able to use the command line to navigate and execute programs

• Set up a printer

• Perform a backup using standard operating system tools or third-party tools

• Perform basic operating system security

• Copy and move files

• Properly start and stop the operating system and server

� Database level

• Properly start and stop the database

• Perform a backup of the database

System

For an ongoing productive environment, we assume that the:

� mySAP.com component is completely and properly installed

� Infrastructure is set up and functional

The mySAP.comcomponents run on overfive different versions of

UNIX, in addition to NT, OS400and OS390. In many cases,significant differences existbetween the different versions ofUnix. These differencescontributed to our decision to notgo into detail at the operatingsystem level.

Introduction xxvii

� The following checklist will help you determine if your system is set up tothe baseline assumptions of this book. If you can log on to your mySAPcomponent, most of these tasks have already been completed.

Item Questions

Hardware Is the backup equipment installed and tested?

Infrastructure Is the Uninterruptible Power Supply (UPS) installed?

Is a server or system monitor available?

Software (general) Are the following utilities installed (as appropriate)?

� Backup programs

� Hardware monitors

� System monitors

� UPS control

Software (mySAP.comcomponents)

Is the mySAP.com component installed according to SAP’srecommendation?

Is the TMS/CTS configured?

Is the TPPARAM file configured? (In Release 4.6, TMScreates a file to be used as the TPPARAM file.)

Is the SAProuter configured?

Is the OSS1 transaction configured?

Is the ABAP workbench configured?

Has initial security been configured (default passwordschanged)?

Are the NT sapmnt share or UNIX NFS sapmnt exportsproperly configured?

Is the online documentation installed?

Can users log on to the mySAP.com component from theirdesktops?

Desktop For optimal results, we recommend that the minimum screenresolution be set as follows:

� For users, 1024 x 768

� For the system administrator, 1024 x 768 and a minimumcolor depth of 256 colors (The Release 4.6 GUI displaysbetter with 64K colors)

xxviii System Administration Made Easy | Release 4.6C/D

How to Use This Guidebook

This guidebook is organized in the following fashion:

� Part two (chapters 2 and 3) provide a high-level view of disaster recoveryand backup and recovery.

� Chapter 4 contains checklists that help the system administrator completevarious tasks on a recurring periodic basis.

These chapters also provide helpful transaction codes.

� Chapter 5 discusses how to stop or start the SAP R/3 system.

� Chapters 6 through 12 involve the following topics:

• SAP system administration

• Security administration

• User administration

• Database administration (SQL Server)

The rest of the book covers subjects such as operations, troubleshooting,remote services, change management, and SAP Notes (formerly known asOSS). The four appendices cover useful transactions, other resources, SAPNotes, and a discussion on upgrades.

Organization

All the task procedures are classified in one section by job roles, where relatedtasks are placed together. Regardless of the job schedule, all jobs related to ajob role are grouped in one place.

What’s New

This guidebook has evolved from the previous versions of this guidebook toincorporate customer and consultant comments. Send us your comments, sowe can ensure that future versions better meet your needs.

Content

The new features of the Release 4.6C/D guidebook are:

� Coverage of SAP System Administration with a view of administration forall mySAP components that utilize the Basis 4.6C and 4.6D releases.

� Multiple Databases

• Microsoft SQL Server / Windows 2000

Note

To send us your comments, visithttp://www.saplabs.com/sysadmin.

Introduction xxix

• IBM DB2/UDB

• Infomix

• Oracle / Unix

� New sections on:

• Information on the Note Assistant (chapter 16 )

• Self training/education with the mini-Basis system

� New Terminology

Conventions

The table below explains the text conventions used throughout this guide.

OLD NEW

SAPNet-Web SAP Service Market Place

OSS Note SAP Note

Text Convention Description

Italic fonts Screen names or on-screen objects (buttons, fields, screen text, etc.)

Courier bold User input; text the user types verbatim

Name1 → Name2 Menu selection Name1 is the menu name, and Name2 is an item onthe menu

Arial

monospaceCommand syntax

<XXXXX> Replace the information within the angle brackets (< >) with wordingspecific to your task. We use angle brackets in place of a screenname or other screen text that is derived from steps within an adaptedprocedure (for example, if you were to choose Sold-to party instead ofShip-to party as shown in the screenshot, your resulting screennames would reflect your selection of Sold-to party). Therefore, weuse angle brackets to reflect screen items that may differ from theexample screenshots.

xxx System Administration Made Easy | Release 4.6C/D

Sample R/3 Release 4.6 Screen

Your screens and on-screen icons may look different than those pictured inthis book, depending on your GUI release and the support package level.

♦ Application toolbar:

The screenshots shown in this guide are based on full user authorization(SAP_ALL). Depending on your authorizations, some of the buttons onyour application toolbar may not be available.

♣ Navigation menu:

Depending on your authorizations, your navigation menu may lookdifferent from screenshots in this guide that are based on SAP_ALL. TheUser menu and SAP standard menu buttons provide different views of thenavigation menu.

To learn how to build user menus, see the Authorizations Made Easyguidebook, Release 4.6A/B.

Special Icons

Throughout this guide, special icons indicate important messages. Below arebrief explanations of each icon:

Menu barStandard toolbar

Screen title

♦ Application toolbar

User menu

♣ Navigation menu

SAP standard menu

Status bar

Work area

Exercise caution when performing this task or step. An explanation of why you should becareful is included.

Information within a TechTalk helps you to understand the topic in greater technical detail.You need not know this information to perform the task.

Caution

TechTalk

Introduction xxxi

Note

This information clarifies a statement in the accompanying text.

These messages provide helpful hints and more detailed information to make your workfaster and easier.

Tips & Tricks

xxxii System Administration Made Easy | Release 4.6C/D

P A R T O N E

ASystem Administration Overview

2 System Administration Made Easy | Release 4.6C/D

Part Overview

A system administrator has many roles to perform. This section discusses some generalduties of system administration and talks about important issues.

C H A P T E R

1

1System Administration Basics


Overview

This chapter covers the roles that a system administrator performs. Theseroles cross all functional areas. In a small company, one person can be theentire system administration department. In a larger company, however, ateam of administrators is required. The purpose of this definition is to helpclarify the roles of a system administrator. This chapter presents a list ofcommonly used system administration terms and their definitions.

At the end of this chapter is a list of fourteen mySAP.com guidelines that asystem administrator must be aware of while working with the system.

Sample guidelines include:

� Keep it short and simple (KISS)

� Use checklists

� Do not allow direct database access

Roles of a System Administrator

Depending on the size of the company and available resources, theadministrator(s) may range from one person to several specialized people inseveral departments.

Factors that affect the system administrator’s tasks, staffing, and roles:

� Company size

� Available resources (the size of the Basis group)

� Availability of infrastructure support for:

• Desktop support

• Database

• Network

• Facilities

The system administrator may perform many roles both in or directly relatedto, the mySAP.com component and indirectly or external to the mySAP.comcomponent.


Within the mySAP.com component

Inside the mySAP.com component, system administrators perform multipleroles:

External to the mySAP.com component

The system administrators are also responsible for supporting other, non-SAP, products:

Role Duties

User administrator Set up and maintain user accounts

Security administrator Create and maintain SAP security profiles

Monitor and manage security access andviolations

System administrator Maintain the system’s health

Monitor system performance and logs

Transport administrator Transport changes between system

Manage change requests

Batch scheduler Creates and manages batch job scheduling

Backup operator Schedule, run, and monitor backup jobs of theSAP database and any required system level files

Disaster recovery technical manager Create, test, and execute the SAP disasterrecovery plan

Programmer Apply SAP Note fixes to programs

Data Dictionary (DDIC) manager Change the Data Dictionary when applicable

Database administrator (DBA) Administers the SAP database

Role Duties

Database Administrator Manage database specific tasksMaintain the database’s health and integrity

Operating system (OS) administrator Manage the operating system access and userIDsManage operating system specific tasks

Network administrator Manage network access and user IDsManage network support and maintenance

Server administrator Manage the servers


System Administrator Traits

A system administrator should have a proper attitude, be technicallycompetent, and work well with a team. The system administrator mustsafeguard the system, and should know when to call for help.

System administration can require working outside of a normal schedule.Some tasks may require working later hours or on weekends. Theadministrator must be willing to work the hours required to support thesystem adequately.

Technical competency is of utmost importance for a system administrator. Agood administrator must keep abreast of new techniques and developments,through reading, doing, and training.

System Guidelines

Some guidelines must be followed when working on a system. Theseguidelines are explained in more detail in the following sections.

� Protect the system

� Do not be afraid to ask for help

� Network with other customers and consultants

� Keep it short and simple (the KISS principle)

� Keep proper documentation

� Use checklists

� Use the appropriate tool for the job

� Perform preventive maintenance

Desktop support Supports the user’s desktop PC

Printers Supports the network and desktop printers

Facilities Manages facilities-related support issues, suchas:

� Power/utilities

� Air conditioning (cooling)

� Physical server access

Role Duties


� Do not change what you do not have to

� Do not make changes to the system during critical periods

� Do not allow direct database access

� Keep all non-SAP activity off the SAP servers

� Minimize single points of failure

Protect the System

Everything you do as a system administrator should be focused on protectingand maintaining system integrity. If system integrity is compromised,incorrect decisions could be made based on invalid data. Additionally, if thesystem cannot be recovered after a disaster, your company’s business couldsuffer.

� Very important to this is a positive, professional attitude on the part of thesystem administrator. Also, because the system administrator isresponsible for the informational backbone of the company, they mustmaintain a “my job is on the line” attitude. Mistakes can be costly to thecompany.

� Another consideration is protecting the system from threats. These threatscan be external, such as hackers, or internal, such as employees who are toocurious.

Do Not Be Afraid to Ask for Help

Some of the mySAP components are so large and complex that one personcannot be expected to know everything. Acting without knowledge can betroublesome, and you may make mistakes. Mistakes within the system can beexpensive.

In some cases, mistakes cannot be undone. The only way to learn and avoidmistakes is to ask for help. Bad questions do not exist—only bad reasons fornot asking them.

Help can come in many forms, such as SAP Notes, various web sites andnews groups, and consultants. For more information, see the followingsection.


Network with Other Customers and Consultants

In order to increase your knowledge base, it is a good idea to get to know theBasis people and system administrators in other companies. Other customersmay be able to provide solutions to your problems, as they may have beenthrough similar situations themselves. Also, getting a colleague to answer aquestion can save money in consulting expenses.

Good places to network include training classes, professional organizations,SAP events (such as the SAP TechEd and Sapphire conferences), and usergroups (such as the Americas SAP Users Group (ASUG), regional usersgroups, database users groups, and operating system users groups).

Participation means getting involved in the organization. The more youparticipate, the more people you meet and get to know.

Keep It Short and Simple (KISS)

The KISS principle is an important one. Do not overcomplicate a task if it doesnot require it. By breaking a major or complex task into smaller, easy-to-digest chunks, the learning curve for the task set is reduced.

Keep Proper Documentation

Make sure that you document processes, procedures, hardware changes,configuration changes, checks performed, problems, errors, and so on. If indoubt about what to document, write everything down.

As time passes, you may forget some of the details of a process or problem.Being able to refer to well-documented procedures will be helpful in such acase, and can serve to jog your memory. Complete documentation can alsoassist others if you are not available to perform a task.

Additionally, documentation assists in training new hires. Employeeturnover is a fact of doing business, and maintaining proper documentationeases the transition and training of new employees.

Documentation must grow and develop with the system. As changes aremade in the system, they must also be reflected in the documentation.Inaccuracies in the documentation can lead to costly mistakes.

Documentation needs to be comprehensive. Too much information in adocument is always better than not enough information. The documentationmust also be clear and easy to understand. Maintain older documents to

Whenever you attend an event, carry a stack of business cards. Set the goal of collecting atleast ten business cards, of people in your area of specialty.

Do not forget to ask the old-timers. Decades ago, the mainframe community may have solvedmany of the issues and problems you now face.

Tips & Tricks

Hot projects oremergencies tend to takeprecedence over writing

documentation. Do not postponewriting documentation, or the taskmay never get done. Recordeverything that is done to thesystem—as it is being done.


ensure that they are kept up-to-date with system changes. Where necessary,use graphics, flowcharts, and screenshots to clarify and to provide additionalinformation.

Make sure that documentation is kept in an easily accessible location. Keeplogs (notebooks) on each server, reflecting everything that is done on thatserver.

Use Checklists

Checklists enforce a standardized process and reduce the chance that you willoverlook critical steps. Checklists force you to document events, such as runtimes, which may later become important.

Checklists are especially useful for tasks that are complex or critical. If a stepis missed or done incorrectly, the result could be serious (for example,inability to restore the database).

If you are performing a task for the first time, or a task that is doneinfrequently, a checklist will assist you in performing the task correctly. Formore information, see chapter 4, “Scheduled Tasks” on page 63.

Use the Appropriate Tool for the Job

Sometimes a low-tech solution is best. Depending on the situation, a paper-and-pencil solution may work better and be more cost effective than acomputerized solution.

Perform Preventive Maintenance

Preventive maintenance is the proactive monitoring and maintenance of thesystem. A regular schedule for maintenance can prevent small issues fromdeveloping into big problems. Potential problems are taken care of beforethey negatively impact the system and company operations.

For example, if log file space drops to zero, the database will stop, which alsowill cause SAP R/3 to stop. SAP R/3 will not run until sufficient file space iscleared, and the delay this causes can stop business operations, such asshipping.

Make problem resolution a regular part of your routine. Scheduling tasks tofix a problem should be based on your situation, and when it is leastdisruptive to your users.

� You should monitor the various logs and event monitors for potentialissues. The database should be regularly checked for integrity andconsistency.

� Maintenance also refers to physical maintenance. Make sure the hardwareis kept clean and kept in a cool environment. Additionally, consider whenhardware may require upgrading, such as additional disk storage.


� Make sure your UPS system is in working order.

Do Not Change What You Do Not Have To

One temptation that exists in the world of technology is to have the latest andgreatest in hardware and software. This temptation is not always a goodthing. If your system works, and works well, leave it alone.

Do not upgrade just because you can. Upgrading to new software orhardware can introduce new elements into a previously stable environment,opening the system up to risk. Also, upgrading can be costly in terms of time,resources, money, and potential system downtime to the business.

Changing your system environment should be done if a business need exists,or to comply with legal requirements. If hardware or software is no longersupported by the vendor, moving to those that are supported is a good reasonto upgrade.

If you do plan to change your system environment, ensure that you canrecover the system to a pre-change condition. Perform regression testing withthe functional team and users to make sure that any changes affect nothingelse.

We recommend staging and testing the change in the following order:

� Test system (a “sandbox” system)

� Development system

� Quality Assurance system

� Production system

Even if your company does not have all the above-mentioned systems, thekey is to maintain the general order. For example, if your company does nothave a test system, test the change in the following order:

� Development

� Quality Assurance

� Production

By the time you reach the production system, you should be comfortable thatnothing will break.


Do Not Make System Changes During Critical Periods

We do not recommend making system changes during critical periods. Acritical period is when system disruptions could cause severe operationalproblems and impact business.

Always coordinate potentially disruptive system events with the users.Different user groups in the company, such as Finance and Order Entry, mayhave different quiet periods that must be coordinated. Plan all potentiallydisruptive systems-related activities during quiet periods when a problemwill have minimal user impact.

Do Not Allow Direct Database Access

Direct database access means allowing a user to run a query or updatedirectly to the database without going through a mySAP component.Allowing a user direct access runs the risk of corrupting the database, andcould put the database out of sync with the mySAP component buffers.

mySAP.com components may write to multiple tables in the database. If auser writes directly to the tables, missing a single table may corrupt thedatabase by putting the tables out of sync with each other. With directdatabase access, a user could accidentally execute an update or delete, ratherthan a read.

Example

A system administrator changes a printer in the Shipping department at the end of the month,but neglects to change the printer setting in SAP R/3. As a result, SAP R/3 cannot send outputto the new printer. The users are not able to print shipping documents, which results in thecompany being unable to ship products. As a result, revenue for the month declines.

Other examples include:

� At end of the month, when Sales and Shipping are booking and shipping as much asthey can, to maximize revenue for the month

� At the beginning of the month, when Finance is closing the prior month

� During the last month of the year (calendar or fiscal), when Sales and Shipping arebooking and shipping as much as they can, to maximize the revenue for the year

� During the beginning of the year, when Finance is closing the books for the prior yearand getting ready for the financial audit


Keep all Non-SAP Activity Off the mySAP Servers

The servers that run your mySAP.com components should be dedicated tothose sole tasks. Running services that have nothing to do with themySAP.com components can slow down the servers, and may possibly putdata at risk of change or deletion.

Minimize Single Points of Failure

A single-point failure is when the failure of a single component, task, oractivity causes the system to fail or creates a critical event. Each place where asingle-point failure could occur increases the chances of a system failure orother critical event.

To guard against a single-point failure, consider the following options:

� Systems configured with a built-in backup

� Redundant equipment, such as dual power supplies

� On-hand spares

� Sufficient personnel

� On-call consultants

� Cross-training

� Outsourcing

Do not allow users to directly access the mySAP component servers, using telnet or remoteaccess programs. Disallowing direct access keeps users away from confidential or sensitiveinformation. Do not use the mySAP component server as a general file server. Disallowing thisprevents putting data at risk of deletion or change. Do not run programs that are not directlyrelated to the mySAP component on its server. Disallowing this will keep system resourcesdedicated to mySAP tasks.

Caution

Example

You only have one tape drive and it fails. You cannot back up your database.

You rely on utility line power, and do not have a UPS, the server will crash during a power failureand possibly corrupt the database.

You are the only one who can complete a task, and you are on vacation, the task will not becompleted until you return (or you will be “on call” while on vacation).


Special Definitions

There are terms used in this guidebook that have very specific meanings. Toprevent confusion, they are defined below:

Database server. This server contains the mySAP component and thedatabase. The database server’s system clock is the master clock for themySAP component.

Application server. This server houses the mySAP component application.On a two-tiered system, this server would be combined on the databaseserver. Application servers can be dedicated to online users, batch processingor both.

Instance. An installation of the mySAP component on a server. Instances areeither central or dialog. The central instance contains the database, and onlyexists once in the system landscape. Dialog instances are the applicationservers. Multiple dialog instances are possible in the system landscape. Morethan one instance can exist on a physical server.

System. The complete mySAP installation for a System ID (SID), for examplePRD. A system logically consists of the SAP R/3 central instance and dialoginstances for the SID. This physically consists of the database server andapplication servers for that SID.

A two-tiered configuration combines the application and database layers on asingle server.

Three-tiered SAP R/3 Configuration

Layers Physical Devices SAP R/3Instance

What Runs on Each Layer

Presentation Desktop PC—many N/A SAP GUI

Application Application Server - many Dialog SAP R/3

Database Database server – only one Central Database: SQL Server,DB2, Informix, ADABAS,Oracle

P A R T T W O

ADisaster Planning Overview


Part Overview

Disaster planning is a necessary and critical part of system administration. Businessprocesses happen daily at a fantastic rate, usually without problems. However, thesmallest problem can cause terrific disruption to business, causing a loss of time, money,and resources. Having plans to recover from problems, regardless of their size andcomplexity, is a good business move.

This section covers disaster recovery and backup processes. Chapter 2 covers disasterplanning and recovery. We talk about why you need to plan for disasters, what to do toplan, and how to test your disaster recovery plans.

Chapter 3 discusses backup and recovery. We talk about what to back up and how often.

C H A P T E R

2

2Disaster Recovery


Overview

The purpose of this chapter is to help you understand what we feel is themost critical job of a system administrator—disaster recovery. We includedthis chapter at the beginning of our guidebook for two reasons:

� To emphasize the importance of disaster recovery. Disaster recovery needsto be planned as soon as possible, because it takes time to develop, test, andrefine.

� To emphasize the importance of being prepared for a potential disaster

The earlier you begin planning, the more prepared you will be when adisaster does happen.

What Is a Disaster?

The goal of disaster recovery is to restore the system so that the company cancontinue doing business. A disaster is anything that results in the corruptionor loss of the SAP R/3 system such as database corruption (for example,loading test data into the production system), serious hardware failure, orcomplete loss of the SAP R/3 system and infrastructure (for example, as aresult of natural disaster or a building fire).

The ultimate responsibility of a system administrator is to successfully restoreSAP R/3 after a disaster. To this end, the administrator should act to preventthe system from ever reaching the situation where disaster recovery isrequired.

Disaster recovery planning is a major project. Depending on your situationand the size and complexity of your company, disaster recovery planningcould take more than a year to prepare, test, and refine. The plan could fillmany volumes. This chapter helps you start thinking about and planning fordisaster recovery.

Why Plan for a Disaster?

A system administrator should expect and plan for the worst, and then hopefor the best. During a disaster recovery, nothing should be done for the firsttime. Unpleasant surprises could be fatal to the recovery process.

This chapter is not adisaster recovery how to.It is only designed to get

you thinking and working ondisaster recovery.


Some questions must be asked that will help to develop your disasterrecovery plan:

� If the SAP R/3 system fails, will business operations stop?

� How much lost revenue and cost will be incurred during systemdowntime?

� Which critical business functions cannot be completed?

� How will customers be supported?

� How long can the system be down before the company goes out ofbusiness?

� Who coordinates and manages the disaster recovery?

� What will the users do while SAP R/3 is down?

� How long will the system be down?

� How long will it take before the SAP R/3 system is available for use?

� What minimum component of the SAP R/3 system must be restored ifoffsite recovery is required?

If you plan properly, you will be under less stress, because you know that thesystem can be recovered and how long this recovery will take.

If the recovery downtime is unacceptable, management should look atinvesting in equipment, facilities, and personnel. Another area to explore isHigh Availability (HA) options. HA means to keep the system or componentrunning continuously for a relatively long period of time. This option can beexpensive. There are different degrees of HA, so customers must determinewhich option is right for them. HA is an advanced topic beyond the scope ofthis guidebook. If you are interested in this topic, contact an HA vendor.

Planning for a Disaster

Creating a Plan

Creating a disaster recovery plan is a major project because it can take over ayear and considerable time to develop, test, and document. Also, thedocumentation may be extensive, perhaps thousands of pages long.

If you do not know how to plan for a disaster recovery, get the assistance ofan expert. A bad plan that will fail is worse than no plan, because it provides afalse sense of security.

There are third party disaster recovery consultants and vendors that can assistyou in creating a disaster recovery plan.


What Are the Business Requirements for Disaster Recovery?

Senior management provides strategic requirements and guidelines.Individual business units will drive the specific requirements.

Each requirement should answer the following questions:

� Who is the requestor?

� What is the requirement?

� Are other departments or customers affected by this requirement?

� Why is the requirement necessary?

• When SAP R/3 is offline, what does (or does not) happen?

• What is the cost (or lost revenue) of an hour or a day of SAP R/3downtime?

The justification should be a concrete objective value (such as $20,000 anhour). Define the cost (for example, on an hourly or daily basis) of having theSAP R/3 system down.

Example

No more than one hour of transaction data may be lost. The cost is 1,000 transactions per hourof lost transactions that are entered in SAP R/3 and cannot be recreated from memory.

This inability to recreate lost transactions may result in lost sales and upset customers. If thelost orders are those that the customer quickly needs, this situation can be critical.

Example

The system cannot be offline for more than three hours. The cost (an average of $25,000 perhour) is the inability to book sales

Example

In the event of disaster, such as the loss of the building containing the SAP R/3 data center, thecompany can only tolerate a two-day downtime. At that point, permanent customer loss begins.There must be an alternate method of continuing business.

The individual businessunits must understandthat as recovery time

decreases, the cost for disasterrecovery increases. The unitsshould budget for it, or if the fundscome from an administrative or ITbudget, the units should support it.


When Should a Disaster Recovery Procedure Begin?

Ask yourself the following questions:

� What criteria constitute a disaster?

� Have these criteria been met?

� Who needs to be consulted?

The person must be aware of the effect of the disaster on the company’sbusiness and the critical nature of the recovery.

Expected Downtime or Recovery Time

Expected Downtime

Expected downtime is only part of the business cost of disaster recovery. Fordefined scenarios, this cost is the expected minimum time until SAP R/3becomes productive again. Downtime may mean that no orders can beprocessed and no products shipped. Management must approve this cost, soit is important that they understand that downtime affects potential businesscosts.

To prevent interruption in business, it is important to research alternateprocesses that can be used while the SAP R/3 system is being recovered.

The following costs are involved with downtime:

� The length of time that SAP R/3 is down. The longer the system is down,the longer the catch-up period required when it is brought back up. Thetransactions from the alternate processes that were in place during thedisaster must be applied to the system to make it current. In a high-volumeenvironment, this situation becomes more critical.

� A downed system is more expensive during the business day, because itcauses business activity to stop.

� Customers who cannot be serviced or supported may be lost tocompetitors.

The duration of acceptable downtime depends on the company and thenature of its business.

Recovery Time

Unless you test your recovery procedure, the recovery time is only anestimate. Different disaster scenarios have different recovery times, based onoperational requirements.

Recovery time must be matched to the business requirements. If recoverytime exceeds the time set forth by business requirements, the mismatch mustbe communicated to the appropriate managers or executives.


Resolving this mismatch involves:

� Investing in equipment, processes, and facilities to reduce the recoverytime.

� Changing business requirements to accept the longer recovery time andaccepting the consequences.

Recovery Group and Staffing Roles

Four key roles exist in a recovery group. The number of employeesperforming these roles will vary depending on your company size. In asmaller company, for example, the recovery manager and the communicationliaison could be the same person. Titles and tasks will probably differ basedon your company’s needs.

The four key roles are defined as follows:

� Recovery manager

Manages the entire technical recovery. All recovery activities and issuesshould be coordinated through this person.

� Communication liaison

Handles communication (phone calls, email, and so on) with the usersand keeps top management updated with the recovery status. One role tohandle all user communication allows the group doing the technicalrecovery to proceed without interruption.

� Technical recovery team

Does the actual technical recovery. As the recovery progresses, theoriginal plan may have to be modified. This role must manage thechanges and coordinate the technical recovery.

� Review and certification manager

Coordinates and plans the post-recovery testing and certification withusers.

A final staffing role is to plan for at least one key staff member to beunavailable. Without this person, the rest of the department must be able toperform a successful recovery. This issue may become vital during an actualdisaster.

Example

An extreme (but possible) example: A company cannot afford the cost and lost revenue for themonth it would take one person to recover the system. During that time, the competition wouldtake away customers, payment would be due to vendors, and bills would not be collected. Inthis situation, senior management needs to allocate resources to reduce the recovery time toan acceptable level.

To reduce interruption ofthe recovery staff, werecommend you maintain

a status board. The status boardshould list key points in therecovery plan and an estimate ofwhen the system will be recoveredand available to use.


Types of Disaster Recovery

Disaster recovery scenarios can be grouped into two types:

� Onsite

� Offsite

Onsite

Onsite recovery is disaster recovery done at your site. The infrastructureusually remains intact. The best-case scenario is a recovery done on theoriginal hardware. The worst-case scenario is a recovery done on a backupsystem.

Offsite

Offsite recovery is disaster recovery done at a disaster recovery site. In thisscenario, all hardware and infrastructure are lost as a result of facilitydestruction such as a fire, a flood, or an earthquake. The new servers must beconfigured from scratch.

A major consideration is that once the original facility has been rebuilt andtested, a second restore must take place to the customer’s original facility.While this second restore can be planned and scheduled at a convenient timeto disrupt as few users as possible, the timing is just as critical as the disaster.During system recovery, the system will be down.

Disaster Scenarios

There are many possible disaster scenarios that could occur. It would take aninfinite amount of time to plan for them, and you will never account for all ofthem. To make this task manageable, you should plan for three to five likelyscenarios. In the event of disaster, you would adapt the scenario closest to theactual disaster.

The disaster scenarios consist of:

� Description of the disaster event

� High-level plan of major tasks to be performed

� Estimated downtime

To create your final scenario:

� Use the Three Common Disaster Scenarios section below as a starting point.

� Prepare three to five scenarios that cover a wide range of disasters thatwould apply to you.


� Create a high-level plan (are made up of major tasks) for each scenario.

� Test the planned scenario, by creating different test disasters anddetermining if and how your scenarios would adapt to an actual disaster.

� If the test scenarios cannot be adapted, modify or develop more scenarios.

� Repeat the process.

Three Common Disaster Scenarios

The following three examples range from a best-to-worst scenario order:

A Corrupt Database

A corrupt database could result from accidentally loading test data into theproduction system, or a bad transport into production that results in thefailure of the production system.

Such a disaster requires the recovery of the SAP R/3 database and relatedoperating system files. The sample downtime is eight hours.

A Hardware Failure

The following types of items may fail:

� A system processor

� A drive controller

� Multiple-drives in a drive array, causing drive array failure

Such a disaster scenario requires:

� Replacing failed hardware

� Rebuilding the server (operating system and all programs)

� Recovering the SAP R/3 database and related files

The sample downtime is seven days and comprises:

� Five days to procure replacement hardware

� Two days to rebuild the NT server (one person); 16 hours of actual worktime

A Complete Loss or Destruction of the Server Facility

The following items can be lost:

� Servers

� All supporting infrastructure

The downtimes in theexamples below are onlysamples. Your downtimes

will be different. You must replacethe sample downtimes with thedowntimes applicable to yourenvironment.

Plan and prepare to useyou test (QAS) system asa backup server if the

production (PRD) server fails.


� All documentation and materials in the building

� The building

A complete loss of the facility can result from disasters such as fire,earthquake, flood, hurricane, and man-made disasters.

Such a disaster requires:

� Replacing the facilities

� Replacing the infrastructure

� Replacing lost hardware

� Rebuilding the server and SAP R/3 environment (hardware, operatingsystem, database, and so on)

� Recovering the SAP R/3 database and related files

The sample downtime lasts eight days and comprises:

� At least five days to procure hardware. In a regional disaster, this purchasecould take longer if your suppliers were also affected by the disaster.

� Two days to rebuild the NT server (one person); 16 hours actual work time

� As the hardware is procured and the server is being rebuilt, an alternatefacility is obtained and an emergency (minimal) network is constructed

� One day to integrate into the emergency network

Complete loss or destruction requires a recovery to a new facility.

Recovery Script

A recovery script is a document that provides step-by-step instructions about:

� The process required to recover SAP R/3

� Who will complete each step

� The expected time for long steps

� Dependencies between steps

A script helps you to develop and use a proven series of steps to restore SAPR/3 and prevents missing steps. Missing a critical step may require restartingthe recovery process from the beginning, which delays the recovery.

If the primary recovery person is unavailable, a recovery script helps thebackup person complete the recovery.

Use national vendors withseveral regionaldistribution centers and,

as a backup, have an out-of-areaalternate supplier.


Creating a Recovery Script

Creating a recovery script requires:

� A checklist for each step

� A document with screenshots to clarify the instructions, if needed

� Flowcharts, if the flow of steps or activities is critical or confusing

Recovery Process

To reduce recovery time, define a process by completing as many tasks aspossible in parallel and adding timetables for each step.

Major Steps

During a potential disaster, anticipate a recovery by:

� Collecting facts

� Recalling the latest offsite tapes

� Recalling the crash kit (for more information, see page Crash Kit).

� Calling all required personnel

� These personnel include the internal SAP team, affected keyusers, infrastructure support, IT, facilities, on-call consultants, and so on

� Preparing functional organizations (sales, finance, and shipping) foralternate procedures for key business transactions and processes.

� Also prepare non-SAP systems that interface to and from the SAP system.

Minimize the effect of the disaster by:

� Stopping all additional transactions into the system

� Collecting transaction records that must be manually reentered

Begin the planning process by:

� Analyzing the problem

� Selecting the predefined scenario plans that most closely matches thedisaster

� Modifying the plans as needed

Define when to initiate a disaster recovery procedure.

� What are the criteria to declare a disaster, and have they been met?


� Who will make the final decision to declare a disaster?

Declare the disaster.

� Perform the system recovery.

� Test and sign off on the recovered system.

� Key users should perform the testing. These users will use a criteriachecklist to determine that the system has been satisfactorily recovered.

� Catch up with transactions that may have been handled by alternateprocesses during the disaster. Once completed, this step should require anadditional sign-off.

� Notify the users that the system is ready for normal operations.

� Conduct a post-disaster debriefing session. Use the results from thissession to improve your disaster recovery planning.

Crash Kit

A crash kit contains everything needed to rebuild the SAP R/3 servers,reinstall SAP R/3, and recover the SAP R/3 database and related files.

This kit must contain everything required to recover your SAP R/3environment in one or more containers. If you must evacuate the site, you willnot have the time to run around, gathering the items at the last minute,hoping that you get everything you need.

In a major disaster you may not even have that opportunity.

A periodic review of the crash kit should be performed to determine if itemsmust be added or changed. A service contract is a perfect example of an itemthat requires this type of review.

The crash kit should be physically separated from the servers. If it is locatedin the server room, and the server room is destroyed, the kit may be lost.

Some crash kit storage areas include:

� Commercial offsite data storage

� Other company sites

� Another secure section of the building

The following is an inventory list of some of the major items to put into thecrash kit. You must add or delete items for your specific environment. Thisinventory list is organized into the documentation and software.

Documentation . The inventory list below must be signed and dated by theperson checking the crash kit. The following documentation must be includedin the crash kit:

� Disaster recovery script

When a change is madeto a component (hardwareor software) on the server,

replace the outdated items in thecrash kit with updated items thathave been tested.

The person who seals thekit should take aninventory of the crash kit.

If the seal is broken, items mayhave been removed or changed,making the kit useless in arecovery.


� Test and verification script fro functional user groups

� Installation instructions:

• Operating system

• Database

• SAP R/3 system

� Special installation instructions for:

• Drivers that must be manually installed

• Programs that must be installed in a specific manner

� Copies of:

• SAP license for all instances

• Service agreements (with phone numbers) for all servers

� Instructions to recall tapes from offsite data storage

� List of personnel authorized to recall tapes from offsite data storage. Thislist must correspond to the list maintained by the data storage company.

� A parts list

� If the server is destroyed, this list should be in sufficient detail to purchaseor leasereplacement hardware. Over time, if original parts are no longer available,an alternate parts list must be prepared. At this point, you might considerupgrading the equipment.

� File system layout

� Hardware layout

� You must know which cards go in which slots, and which cables go where(connector-by-connector). Labeling cables and connectors greatly reducesconfusion.

� Phone numbers for:

• Key users

• Information services personnel

• Facilities personnel

• Other infrastructure personnel

• Consultants (SAP, network, and so on)

• SAP hotline

• Offsite data storage

• Security department or personnel

• Service agreement contacts

• Hardware vendors

Ensure that maintenanceagreements are still validand check if the

agreements expired. Theseshould be part of a regularschedule task.


Software.

� Operating system:

• Installation kit

• Drivers for hardware, such as a Network Interface Card (NIC) or aSCSIcontroller, which are not included in the installation kit

• Service packs, updates, and patches

� Database:

• Installation kit

• Service packs, updates, and patches

• Recovery scripts, to automate the database recovery

� For SAP R/3:

• New installation kit of current SAP R/3 release. Not the upgrade kit

• Currently installed kernel

• System profile files

• tpparam file

• saprouttab file

• saplogon.ini

� Other SAP R/3 integrated programs (for example, a tax package)

� Other software for the SAP R/3 installation:

• Utilities

• Backup

• UPS control program

• Hardware monitor

• FTP client

• Remote control program

• System monitor

Business Continuation During Recovery

Business continuation during disaster recovery is an alternate process tocontinue doing business while recovering from a disaster. It includes:

� Cash collection

� Order processing

� Product shipping


� Bill paying

� Payroll processing

� Alternate locations to continue doing business

Without an alternate process, your company ‘s business will suffer or stop.Some of the problems you may encounter include:

� Orders cannot be entered

� Product cannot be shipped

� Money cannot be collected

Alternate processes include:

� Manual paper-based data recording (for example, hand-written purchaseorders)

� Stand alone PC-based products

Offsite Disaster Recovery Sites

Some ideas for offsite disaster recovery sites include other company sites,commercial disaster recovery sites, and sharing or renting space from othercompanies.

Integration with your Company’s General Disaster Planning

Because there are many dependencies, the SAP R/3 disaster recovery processmust be integrated with your company’s general disaster planning. Thisprocess includes telephone, network, product deliveries, mail, and so on.

When the SAP R/3 System Returns

How will the transactions that were handled with the alternate process beentered into SAP R/3 when it is operational?

Test your Disaster Recovery Procedure

Performing a simulated disaster recovery verifies that you can recover thesystem and exercise every task outlined in the disaster recovery plan. Thissimulation determines if:

� Your disaster recovery procedure works

� Something changed, was not documented, or updated

� Steps require clarification. Information that is clear to the persondocumenting the procedure may be unclear to the person reading theprocedure.

Unless you test yourrecovery process, you donot know if you can

actually recover your system.


� Older hardware is no longer available

Here, alternate planning is needed. You may have to upgrade yourhardware to be compatible with currently available equipment.

Because many factors affect recovery time, actual recovery times can onlybe determined by testing. Once you have actual times (not guesses orestimates), your disaster planning becomes more credible. If theprocedure is practiced often, when a disaster occurs, everyone will knowwhat to do. This way, the chaos of a disaster will be reduced.

� Execute your disaster recovery plan on a backup system or at an offsitelocation.

� Generate a random disaster scenario.

� Execute your disaster plan to see if it handles the scenario.

A full disaster recovery should be practiced at least once a year. Howeverbased on the cost the frequency is a business decision.

� The disaster recovery test should be done at the same site that you expectto recover. If you have multiple recovery sites, perform a test recovery ateach site. The equipment, facilities, and configuration may be different ateach site. Document all specific items that must be completed for each site.You do not want to discover that you cannot recover at a site after adisaster occurs. Other options for sites to test your disaster recoveryscenario include:

• A backup onsite server

• Another company site

• At another company where you have a mutual support agreement

• A company that provides disaster recovery site and services

� Primary and backup personnel will do the job during a real disasterrecovery. A provision should be made that some of the key personnel areto be unavailable during a disaster recovery. A test procedure mightinvolve randomly picking a name and declare that person unavailable toparticipate. This procedure duplicates a real situation in which a keyperson is seriously injured or killed.

� Additionally, personnel at other sites should also participate. Integratethese people into the test, because they may be needed to perform therecovery during an actual disaster. These people will fill in for unavailablepersonnel.

During the disasterrecovery test, someonestill must support the real

production system.


Other Considerations

Other Upstream or Downstream Applications

For the company to function, other upstream or downstream applicationsalso must be recovered with SAP R/3. Some of these applications may betightly associated with SAP R/3. The applications should be accounted forand protected in the company-wide disaster recovery planning.

Backup Sites

The emergency backup site may not have equipment of the same performancelevel as your production system. Reduced performance and transactionthroughout must be considered.

Minimizing the Chances for a Disaster

There are many ways to minimize chances for a disaster. Some of these ideasseem obvious, but it is these ideas that are often forgotten.

Applications located on only one person’s desktop computer must be backed up to a safelocation.

Caution

Having a contract with a disaster recovery site does not guarantee that the site will beavailable. In a regional disaster, such as an earthquake or flood, many other companies will becompeting for the same commercial disaster sites. In this situation, you may not have a site torecover to, if others have booked it before you.

Example

� A reduced batch schedule of only critical jobs

� Only essential business tasks will be done while on the recovery system

Caution


Minimize Human Error

Dangerous tasks (such as deleting the test database, moving a file, orformatting a new drive) should be scripted and checkpoints included toverify the steps.

Minimize Single Points of Failure

A single-point failure is when the failure of one component causes the entiresystem to fail.

To minimize single-point failure:

� Identify conditions where a single-point failure can occur

� Anticipate what will happen if this component or process fails

� Eliminate as many of these single points of failure as practical.

Types of single points of failure include:

� The backup SAP R/3 server is located in the same data center as theproduction SAP R/3 server. If the data center is destroyed, the backupserver is also destroyed.

� All the SAP R/3 servers are on a single electrical circuit. If the circuitbreaker opens, everything on that circuit loses power, and all the serverswill crash.

Many disasters are caused by human error, such as a mistake or a tired operator. Do notattempt dangerous tasks when you are tired. If you must do a dangerous task, get a secondopinion before you start.Caution


Cascade Failures

A cascade failure is when one failure triggers additional failures, whichincreases the complexity of a problem. The recovery involves the coordinatedfixing of many problems.

The recovery becomes complex because:

� Fixing one problem may uncover other problems or damaged equipment.

� Certain items cannot be tested or fixed until other equipment isoperational.

In this case, a system that monitors the air conditioning system or thetemperature in the server room could alert the appropriate employees beforethe temperature in the server room becomes too hot.

Example

Cascade Failure

A power failure in the air conditioning system causes an environmental (air conditioning) failurein the server room.

Without cooling, the temperature in the server room rises above the equipment’s acceptableoperating temperature.

The overheating causes a hardware failure in the server.

The hardware failure causes a database corruption.

In addition, overheating can damage many things, such as:

� Network equipment

� Phone system

� Other servers

C H A P T E R

3

3Backup and Recovery


Overview

Establishing an effective backup and recovery strategy is the most importantaspect of a technical implementation. This process entails a full or partialrestore of the database after hardware or software errors and a recoveryduring which the system is updated to a pre-failure status. Other situationsaside from disk failures may require a restore and recovery.

Your backup strategy should be as simple as possible. Unnecessarycomplication in backup strategy creates difficult situations during restorationand recovery. Procedures, problem identification, and handling must be welldocumented so all individuals clearly understand their roles and requiredtasks. This strategy should also not adversely impact daily business.

This chapter discusses backup and restore of your system. The details ofspecific databases are covered in the database administration chapters.

Restore

Usually a restore is done to:

� Recover after a disaster (for more information, see “When Should aDisaster Recovery Procedure Begin?” on page 21.)

� Test your disaster recovery plan (for more information, see “Test yourDisaster Recovery Procedure” on page 30.)

� Copy your database to another system (for more information, see“Database Copy of Production System” on page 668.)

The business requirement for a quick restore is driven by the need to get thesystem operational quickly after a disaster, so the company can continue to dobusiness.

Strategy

Business recovery time is the result of the time needed to, find the problem,repair the damage, and restore the database.

Factors that affect the chosen restore strategy include:

� Business cost of downtime to recover

� Operational schedule

� Global or local users

� Number of transactions an hour

� Budget


The actual process to restore SAP R/3 and the database is not covered in thisbook. This critical task has specific system dependencies, and we leave it to aspecialist to teach. If a restore must be done, contact a specialist or your Basisconsultant. Work with your DBA or consultant to test and document therestore process for your system. With proper training, you should be able todo the restore.

Testing Recovery

Because the restore procedure is one of the key issues of the SAP R/3 system,database recovery must be regularly tested. For more information, seechapter 2, “Disaster Recovery” on page 17.

Backup

Backup is like insurance. You only need a backup if you must restore yoursystem.

What to Backup and When

There are three categories of files to backup:

� Database

� Log files

� Operating system files

Database

The database is the core of the SAP R/3 system and your data. Without thedatabase backup, you cannot recover the system.

The frequency of a full database backup determines how many days back intime you must go to begin the restore:

� If a daily full backup is done, you will need yesterday’s full backup.Only logs since yesterday’s backup must be applied to bring the systemcurrent.

� If a weekly full backup is done, you will need last week’s full backup.All the logs for each day since the full backup must be applied to bring thesystem current.

A daily full backup reduces the number of logs that must be applied to bringthe database current. This backup reduces the risk of not getting a currentdatabase backup because of a bad (unusable) log file. SAP recommends adaily backup of the productive database and to store the last 28 backups.

If the restore is not doneproperly and completely,it could fail and must be

restarted, or be missing otherfiles. You must record special dataabout your database to recover it.Work with your specialist toidentify and document this data.

Note

You may need to use different tools tobackup all the files. Some tools mayonly be able to backup one or two of thethree categories of files that must bebacked up. For example, the SAP DBACalendar DB13 for Microsoft SQLServer can backup the database andthe transaction log, but not theoperating system files.


If a daily full backup were not done, more logs must be applied. This steplengthens the recovery process time and increases the risk of not being able torecover to the current time. A point may be reached when it may take too longto restore the logs, because of the quantity of logs to be applied. For additionalsafety, we recommend that you do a full monthly database backup inaddition to the full daily backups. However, there must be strong reasons notto backup a productive database on daily basis (for example, the database istoo big to back up over night).

These examples show that the time it takes to do a log restore depends on thesize of the logs and how many days back you must go to get to the last fullbackup. With large logs, such as 100MB or more every hour, this quicklybecomes impractical. Increasing the frequency of the full backup (with fewerdays between full backups) reduces the recovery time.

Also consider maintaining two backup cycles of the logs on disk to reduce theneed to restore these logs from tape.

Transaction Logs

Transaction logs are critical to the database recovery. These logs contain arecord of the changes made to the database, which is used to roll forward (orback) operations. It is critical to have a complete chain of valid log backups. Ifyou must restore and one log is corrupted, you cannot restore past the corruptlog.

Example

Weekly Backup

A restore from last week’s full backup that was done four days ago.

There are 10 logs per day.

A total of 40 logs (10 logs per day × 4 days) must be restored.

It takes 120 minutes to restore the log file from tape to disk (40 log x 3 minutes per log).

It takes 200 minutes to restore the log files to the database (40 logs x 5 minutes per log).

The total time to do the restore, excluding database files, is 320 minutes (5.3 hours)

Daily Backup

A restore from last night’s full backup

There are a maximum of 10 logs a day.

It takes 30 minutes to restore the log file from tape to disk (10 log x 3 minutes per log).

It takes 50 minutes to restore the log files to the database (10 logs x 5 minutes per log).

The total time to do the restore, excluding database files, is 80 minutes (1.3 hours).

As you can see in this example, the weekly backup takes four times longer to recover than thedaily backup.

Transaction logs arestored in a directory,which must not be

allowed to become full. If thetransaction log fills the availablefile space, the database stops,and no further processing can bedone in the database and,consequently, in SAP R/3. It isimportant to be proactive andperiodically back up thetransaction logs. Refer to thechapter specific to your databasefor more information.


The frequency of the log backups is a business decision based on:

� Transaction volume

� Critical periods for the system

� Amount of data senior management is willing to lose

� Resources to perform the backups and take them offsite

� Also see the examples in the database section above.

To back up transaction logs, backup the transaction log to disk.

Copy the backup of the transaction log to an offsite backup file server.Backing up your log information over a network should always be done withverification.

This backup file server should ideally be in another building or in anothercity. A separate location increases the chance that the log files will bepreserved if the primary data center (containing the SAP R/3 servers) isdestroyed.

Back up the transaction log backups of both servers (the SAP R/3 server andthe offsite backup file server) to tape each day along with the other operatingsystem-level files.

If you do not have an offsite backup server, back up the transaction logbackups to tape after each log backup and immediately send the tape offsite.

Operating System Level Files

Operating system level files must also be backed up:

� Operating environment (for example, system and network configuration)

� SAP R/3 files

• Spool files, if stored at the operating system level(system profile: rspo/store_location = G)

• Change management transport files located in /usr/sap/trans

� Other SAP R/3 related applications

• Interface or add-on products, such as those used for EDI or taxes,which store their data or configuration outside the SAP R/3 database

The amount of data is small in relation to the SAP R/3 database. Dependingon how your system is used, the above list should only require severalhundred megabytes to a few gigabytes of storage. In addition, some of thedata may be static and may not change for months.

The frequency of the operating system level backup depends on the specificapplication. If these application files must be kept in sync with the SAP R/3System, they must be backed up at the same frequency as the log backup files.

Weekly Full Backups

A log from Tuesdaybecomes corrupt. The systemcrashes two days later onThursday. You can only recover tothe last good log on Tuesday.Everything after that is lost.

If your transactionvolume is high, decreasethe time interval between

log backups. This reduced timeinterval decreases the amount ofdata that could be lost in apotential data center disaster.

Do not back up the logs tothe tape drive in appendmode, which will append

multiple backups on the sametape. If a data center disasteroccurs, the tape with all these logswill be lost.


An example of this situation is a tax program that stores its sales tax data infiles external to the SAP R/3 database. These files must be in sync with thesales orders in the system.

A simple and fast method to back up operating system files is to copy all datafile directories to disk on a second server. From the second server, you canback up those files to tape. This process minimizes file downtime.

Use the sample schedule below to determine your backup frequency:

Backup Types

Backup types is like a three-dimension matrix, where any combination can beused:

� What is backed up: full database vs. incremental of the logs

� How the backup taken: online vs. offline

� When the backup is made: scheduled vs. nonscheduled (ad-hoc)

� The table below shows different backup terminology used by variousdatabase system.

Full DatabaseBackup

PartialDatabaseBackup

Log Backup

DB2 UDB FullDatabaseBackup intoTSM

Offline/Online TablespaceBackup intoTSM

IncrementalDatabasebackup withDB2 UDBv7.2 intoTSM

Archiveinactive logfiles withTSM

Full databasebackup intoDevice

Offline/Online TablespaceBackup intoDevice

IncrementalDatabasebackup withDB2 UDBv7.2 intodevice

Archiveinactive logfiles to device

Full databasebackup withvendor library

OfflineTablespacebackup withvendor library

IncrementalDatabaseBackup withDB2 UDBv7.2 withvendor library

One-steparchiving toStorageSoftware

SQL Server FullDatabaseBackup

DifferentialDatabaseBackup

TransactionLog Backup


What Is Backed Up

Informix Wholesystembackup

Incrementalwholesystembackup

Databasebackup

Incrementaldatabasebackup

Logical LogBackup

Oracle Wholedatabaseoffline + redolog backup)

Wholedatabaseofflinebackup

Partialdatabaseofflinebackup

Redo logbackup

Wholedatabaseonline + redolog backup

Wholedatabaseonlinebackup

Partialdatabaseonlinebackup

Full DatabaseBackup

PartialDatabaseBackup

Log Backup

What Is Backed Up

Backup Type: Full database backup

Content: Entire database

Advantages Disadvantages

The entire database is backed up at once,making the restore of the database easierand faster. Fewer logs must be applied tobring the restored database current.

A full database backup takes longer to runthan an incremental log backup. Because ofthe longer backup window, there is moreimpact on the users while the backup isrunning.

Backup Type: Incremental backup of the transaction logs

Content: A backup of the transaction logs.

A full database backup is still required on a periodic basis. The usual arrangement is a fullbackup on the weekend and incremental backups during the week.


Much faster than a full database backup.Because of the smaller backup window, thereis less impact to the users.

A full backup is needed as a starting point torestore the database.

To restore the database takes significantlylonger and is more complicated thanrestoring a full backup. The last full databasebackup must be restored, then all logbackups since the full backup are restored. Ifdays have passed between the last fullbackup and a system crash, many logs mayneed to be restored.

If one log cannot be restored, all the logsafter that point cannot be restored.


How the Backup Is Taken

Backup Type: Differential backup

Content: Depending on your database and operating system, you may have a third option. Adifferential backup is a backup of only what has changed since the last full backup. A fulldatabase backup is still required on a periodic basis. The usual arrangement is a full backupon the weekend and differential backups during the week.


The exposure to a corrupt log backup isreduced. Each differential backup is backingup all the changes to the database since thelast full backup.

Like the incremental log backup, a fullbackup is needed as the starting point.

The backup window for a differential is longerthan a transaction log backup. It starts asbeing short (just after the full backup) andgets longer as more data is changed.

What Is Backed Up

How the Backup is Taken

Backup Type: Offline

An offline backup is taken when the SAP system is not available for users.


An offline backup is faster than an onlinebackup.

During the backup, there is no issue withdata changing in the database.

If the files are backed up at the same time,the related operating system files will be insync with the SAP R/3 database.

During offline backup you have the possibilityto perform a binary verify operation. Howeverthis will double the backup time.

SAP does not have to be stopped to start anoffline backup. This preserves the SAPbuffer.

SAP is unavailable during an offline backup.

If SAP is stopped, the SAP buffer is flushed.SAP does not have to be stopped to start anoffline backup.

If the database is stopped, the databasebuffer is flushed.

This process will impact performance untilthe buffers are populated.

Backup Type: Online

Note

The definition we use here for offlineand online is likely different from whatyou think. Neither is wrong but viewfrom different point of view, our point ofview is the end user.

If you are using onlinebackups, the transactionlogs are critical to

successfully recovering thedatabase.


When the Backup Is Made

Scheduled. Scheduled backups are those that are run on a regular schedule,such as daily or weekly. For normal operations, configure a scheduledbackup. Automated backups should use the DBA Planning Calendar(transaction DB13). This calendar provides the ability to set up and reviewbackup cycles. It also has the ability to process essential database checks andupdate statistics. You can also set up CCMS to process the backup oftransaction logs.

Depending on the operating platform, backups and other processesconfigured here can be viewed in the Batch Processing Monitors (transactionSM37). In general, the status of the backups can be viewed using Backup Logsoverview (transaction DB12).

On-demand. On-demand backup is done on an ad hoc basis. It is donebefore a major change to the system, such as for an SAP R/3 upgrade or aftera structural change of the database like adding a data file. Backups that arecontrolled directly by an operator, or on-demand, can be performed either bythe DBA Planning Calendar (transaction DB13), at the database, or atoperating system level.

Although the DBA Planning Calendar can schedule backups for periodic use,it can also be used to perform an immediate backup. For an on-demandbackup, it is more common to use tools at the database level such asEnterprise Manager (Microsoft SQL Server) or SAPDBA (Oracle andInformix).

An online backup is taken with the database and SAP R/3 running.


SAP R/3 is available to users during abackup.This is needed where the system is runningand used 24 hours a day and seven days aweek.

The buffers are not flushed.Because buffers are not flushed, once thebackup is complete, there is no impact onperformance after the backup.

An online backup is slower than an offlinebackup (a longer backup time).

Backup time is increased because processessuch as SAP R/3 are running and competingfor system resources. There is additionaloverhead to record information about theupdates being made while the data is beingbacked up.

Online performance is degraded while thebackup is running.

Data may change in the database while it isbeing backed up.Therefore, the transaction logs becomecritical to a successful recovery.

Related operating system level files may beout of sync with the SAP R/3 database.

How the Backup is TakenNote

The definition we use here for offlineand online is likely different from whatyou think. Neither is wrong but viewfrom different point of view, our point ofview is the end user.


Regardless of the chosen backup method, you should achieve the followinggoals:

� Provide a reliable backup that can be restored.

� Keep the backup strategy simple.

� Reduce the number of dependencies required for operation.

� Provide the above items with little or no impact to business units.

Backup Strategy Design

SAP provides tools under CCMS-DB Administration in SAP R/3 to assist inimplementing your strategy. The DBA Planning Calendar (transaction DB13)is designed for scheduling backups. The other tool, the CCMS Monitoringtool (transaction DB12), provides historical information to review backupstatistics and tape management information. At the operating system ordatabase level, there are additional tools you can use to administer backupsand restores. These tools include SQL Enterprise Manager (Microsoft SQLServer) and SAPDBA (Oracle and Informix).

To design your backup procedures:

� Determine the recovery requirements based on an acceptable outage.

It is difficult to define the concept of acceptable outage, because acceptableis subjective and will vary from company to company. The cost of what isan outage includes productivity loss, time, money, and so on spent onrecovery. This cost should be evaluated in a manner similar to insurance.(The more coverage you want, the more the insurance will cost.)Therefore, the faster the recovery time requirements, the more expensivethe solution.

� Determine what hardware, software and process combinations can deliverthe desired solution.

Review the section on performance to decide which method is best.Follow the Keep It Simple rule, but more importantly, make sure yourmethod is reliable.

� Test your backup procedures by implementing the hardware andreviewing the actual run times and test results.

Ensure that you get results from all types of backup that could be used inyour environment, not just the ones you think might be used. Thisinformation will aid further evaluation and capacity planning decisionsand provide useful comparison information as needed.

� Test your recovery procedures by creating various failure situations.

� Document all aspects of the recovery including the process, who shouldperform various tasks, who should be notified, and so on. Remember thata recovery will be needed when you least expect it. Testing should occurregularly, with additional tests as hardware or software componentschange.


Supplementary Backups

Supplementary backups are made on special days (month-end, year-end), sothat you can restore the database to a previous state.

General Procedures

Backup

The unattended backup is performed based on the backup frequency table.The scheduling functionality of the SAP R/3 CCMS is used to schedule thebackup. In CCMS, the required tapes can be listed by choosing the VolumesNeeded button on the backup scheduling screen. Extra backups, such as themonthly and yearly backup, should be performed offline.

Transaction Log Backup

The transaction log backup can be performed during normal systemoperation without impacting the users.

Verifying Backups

Backups must be verified following a regular schedule. To do this verify youmust perform a restore of the system and test that the restore is good. Unlessthe backup is verified, you will not know that you have properly backed upeverything onto tape.

Database Integrity

An integrity check of the database must be performed in one retention periodto ensure that no corrupted blocks exist in the database. These blocks may gounrecognized during backup (see the chapter appropriate to your databasefor more information).

Example

A backup of several files was done, but the append switch was not properly set for second andlater files. Consequently, rather than appending the files one after the other, for each file, thetape was rewound and then backed up. The end result was that only the last backed up file wason the tape.

File verification must bedone after all files havebeen backed up. If it were

done after each file, it would notdetect that the previous file waserased.


To avoid backing up a hidden, inconsistent database, the database must bechecked at least once during a retention period.

Roles and Responsibilities

Design Recommendations

Database

Assuming the size of your database and backup window permits it, werecommend a full database backup be taken every day. For databases that aretoo large for daily full database backup, a full backup should be taken weekly.

Transaction Logs

Backing up the transaction logs is critical. If the file space is used up, thedatabase will stop, which stops SAP R/3.

Between 6:00 a.m. and 9:00 p.m., we recommend that you back up these logsat least every three hours. This time increment defines the maximum amountof data you are willing to loose. A company with high transaction volumecarries higher risk and would increase the frequency accordingly, perhaps toevery hour. Similarly, if you have a Shipping department that opens at 3:00a.m. and a Finance department that closes at 10:00 p.m., you must extend thestart and end times.

System Frequency of DB Checks

DEV Every 2 weeks

QAS Every 2 weeks

PRD Every week

Task Role

Backup Database Operator

Backup Archives Operator

Verifying Backups Operator/DBA

Monitoring/Controlling Operator/DBA

Database check DBA


Operating System Level Files

The frequency of the operating system level backup depends on theapplication. If these files must be kept in sync with SAP R/3, they must bebacked up with the same frequency and at the same time as the database andlog backups. An option for a non-sync-critical situation is to back up theseoperating system level files once a day.

A Strategy Checklist

A proper procedure must be set for backing up valuable system information.Procedures should be defined as early as possible to prevent possible dataloss. Resolve the following list of backup issues before you go live:

� Decide how often to perform complete database backups

� Decide whether partial or differential backups are necessary

� Decide when to perform transaction log backups

� Have the ability to save a day’s worth of logs on the server

� Provide ample disk space for the transaction log directory

� Consider using DBA Planning Calendar (DB13) to schedule transaction logbackups

� Set the appropriate SAP R/3, operating system, and databaseauthorizations

� Create a volume labeling scheme to ensure smooth operations

� Decide on a backup retention period

� Determine tape pool size (tapes needed per day × retention + 20 percent)Allow for growth and special needs.

� Initialize tapes

� Determine physical tape storage strategy

� Decide whether to use unattended operations

If using unattended operations, decide where (in CCMS or elsewhere).

� Document backup procedures in operations manual

� Train operators in backup procedures

� Implement a backup strategy

� Perform a test restore and recovery

� Define an emergency plan and determine who to contact in case of anemergency


Backup Procedures and Policies

Backup policies and procedures should be defined as early as possible toprepare for potential data loss during an implementation.

Some examples of policies and procedures are included below:

� System Environment

In the three-system landscape, CCMS backs up and restores the softwarecomponents. (In the three-system landscape example used in thisguidebook, DEV is a development system, QAS is a quality assurancesystem, and PRD is a production system.)

� Hardware Components

The hardware listed in the table below is to backup and restore thedatabase and transaction logs:

Tape Management

Check with your tape vendor to determine maximum tape life. This isnormally in cycles. Note that a backup with verify is two cycles; one for thebackup and a second for the verify. Tapes should be destroyed after reachingtheir manufacture rated life span to prevent accidental reuse.

Tracking and Documenting

To easily retrieve tapes from storage, you must track and document them.The issues involved with this are:

� Labeling

� Tracking

� Handling

� Retention requirement

System Name Backup Hardware

DEV 1 x DLT 7000 35/70 GB, 1 DDS-3 12/24

QAS 1 x DLT 7000 35/70 GB, 1 DDS-3 12/24

PRD 2 x DLT 7000 35/70 GB, 2 DDS-3 12/24


Labeling

Tapes should be clearly labeled using one of many labeling methods. Threesimple methods are described in the examples below. Two of these methodsare used by SAP R/3 and are important if you use DB13 to schedule yourbackups. Third-party backup management software may assign its owntracking number for the labels. In this case, you must use the label specifiedby the software.

Example

This five-character naming convention is used by DB13 on Microsoft SQL Server 7.0. (See SAPNote 141118). Microsoft SQL server 6.5 used a different naming convention.

Each label has the following data:

� What is backed up:• R = SAP R/3 database or transaction log

• M = msdb database

• S = master database

• C = combination

� Type of backup:• L = transaction log

• D = database

• F = file

• G = file group

• + = differential� Day of the month (01-31)

� Parallel or Sequential backup (P or S)Sample Label: CD06S

C (Combination) + D (database) + 06 (6th day of the month) + S (sequential)


If DB13 is not used, for all of above naming conventions, additional codes canbe used to indicate additional types of files that are backed up. However, incase of BRBACKUP, the label is limited to 8 characters.

In addition to the naming schemes, use a different color label for each system.A color scheme is one more indicator to help identify the tape and reduceconfusion.

An example of a color scheme is:

� PRD = orange

� QAS = green

� DEV = white

Example

This six-character naming convention is used by SAPDBA and BRBACKUP (Oracle).


� System ID <SID>

� What is backed up• B = database

• A = log

• O = operating system files

� Sequence number of the tape (This number is a sequential tape number, starting from1 and is unrelated to the date.)

Sample Label: PRDB25

PRD (Production db) + B (Brbackup/Database) + 25 (tape number 25)

Example

This method is more visual, where the length of the label name is less of a limitation.


� System ID <SID>

� What is backed up:• db = database

• tl = transaction log

• os = operating system files

� Day of the month

� Multiple tape indicator for a single day (can be omitted if only one tape is used)Sample Label: PRD-db-06-a

PRD (Production database) + db (database) + 06 (6th day of the month) + a (tape “a”, the firsttape)


Tracking

Tapes should be logged to track where they are stored, so you can locate themwhen you need them.

In addition to tracking and documenting tapes when tape locations change,tapes should be tracked and documented when they are:

� Used

� Sent to offsite storage

� Returned from offsite storage

� Moved to a new location

To help you track and retrieve the offsite backup, log the:

� Date of backup

� Database

� Tape number

� Tape storage company’s number

Some storage companies label the cartridges with their own trackinglabel, so that they can track them internally to their system and facility.

� OS level backup tape number

� Date sent offsite

� Date returned

The table below is an example:

Handling

When you transport tape cartridges, carry them in a protected box tominimize damage and potential data loss due to mishandling. The box shouldhave foam cutouts for each tape cartridge you use.

We recommend that you use two boxes. One box should collect the tapes tobe sent offsite, and a second box should contain the new backup tapes. Thesecond box should be empty when you finish changing tapes.

To change tapes:

� Remove the tape cartridge from the tape drive.

� Insert it in the collection box.

Date Volume Label Purpose Notes Storage Company Label Out Back

7/15/98 PRDB01 Database X7563 7/15/98 7/30/98

7/15/98 PRDO23 Operating Sys X7564 7/15/98 8/15/98

For a small company, anideal tape collectiondevice is a small or

medium-sized plastic toolbox witha foam insert that has cutouts foreach tape cartridge. Plastic isused because it is nonmagnetic.


� Remove the next tape.

After all tapes have been removed, insert the new tapes in the drive in thesame manner.

If you are using preinitialized tapes, you must use the correct tape for thatday, or the backup program will reject the tape. The backup program readsthe tape header for the initialization information (which includes the tapelabel name) and compares it to the next label in the sequence.

When you initialize a tape, some programs write an expiration date on thetape. That same program cannot overwrite the tape before the expiration date.However, it might be overwritten by another program that ignores the tapeheader.

Retention Requirements

There are legal requirements that determine data retention. Check with yourcompany’s legal department for compliance with federal, state, and local dataretention requirements. Compliance with these requirements should bediscussed with your legal and finance departments, external auditors, andconsultants. The retention requirement should then be documented.

The practical side of data retention is that you may be unable to realisticallyrestore an old backup. If the operating system, database, and the SAP R/3system have each been upgraded twice since the backup, it is unlikely that thebackup can be restored without excessive cost—if at all.

Retention is related to your backup cycle. It is important to have severalgenerations of full backups and all their logs because:

� If the database is corrupted, you must return to the last full backup beforethe database corruption.

� If the last full backup is corrupted, you must return to the previous fullbackup before the corruption or disaster and roll forward using the backupof the logs from that backup until the corruption.

How far back you go depends on the level of corruption.

� Because SAP R/3 is an online real-time system, to recover the databasefrom a full database backup, you must apply all the logs since that backup.If this is a significant amount of time, the number of logs could betremendous. Therefore, the number of logs you must apply is a practicalconstraint to how far back you can recover.

When changing tapes, to avoid confusion:

� Handle one tape cartridge at a time

� Follow the same procedure each time

Keep track which tapecartridges have beenused, are to be sent

offsite, and are to be loaded in thedrives.

It is easy to accidentally put thewrong tape cartridge in a driveand destroy the recent backup orcause the next backup to fail.

Tips & Tricks


Recommendations

� If a full database backup is taken each day, we recommend that you keepat least two weeks of backups and all the logs for these weeks.

� If a full database backup is taken weekly, you should go back at least threegenerations.

� Store selected backup sets (month-end, quarter-end, year-end, and so on)for extended periods, as defined by your legal department and auditors.

Tape Retention Period

Even if a backup or archive tape is damaged or lost, the tape retention periodassures the ability to recover the database.

Storage

Offsite

The offsite storage site is a separate facility (building or campus) from theSAP R/3 data center. Offsite storage safeguards the backups if your facility isdestroyed. The magnitude of the disaster will determine what is consideredadequate protection:

� Sending tapes to a separate location in the building or another building inthe campus will be sufficient.

� If the disaster is confined to the building where the data center is located.

� If the disaster is local or regional (for example, a flood or earthquake)adequate protection means sending tapes to a distant location severalhundred miles away.

Offsite data storage can be at a separate company facility or a commercialdata storage company. The offsite data storage facility or vendor should havea certified data storage site. Data tapes have different handling and storagerequirements than paper.

System administratorscannot determine taperetention periods on their

own.

To determine the retention period,administrators must consult thedepartments that are impacted,such as accounting and legal.There is room for somenegotiation, but the administratormust comply with the finaldecision. As a policy, this decisionmust be written down. SAP’sstandard retention period is 28days. System Name Regular

BackupMonth-EndBackup

Quarter-EndBackup

Year-EndBackup

Archives

DEV 14 days 31 days

QAS 14 days 31 days

PRD 31 days 2 years 2 years 4 years 31 days

Once the backup iscomplete, send the tapesoffsite immediately. If

there is a data center disaster andthe backup tapes are destroyed,you can only recover to the lastfull backup that you have offsite.For log backups, it is critical tosend the tapes offsiteimmediately. If not, everythingsince this backup is lost.


Onsite

Onsite storage means storing your data in the same facility as your datacenter. Tape cartridges should be properly stored, following the tapemanufacturer’s storage requirements.

When storing tape cartridges, keep all related tape cartridges together. Alltapes used in a daily backup should be considered as a set, comprisingbackups for:

� Database

� Logs

� Operating system files

Tapes and files in a set must be restored as a set. For example, if operatingsystem files are not restored with database and log files, the operating systemfiles will not be in sync with the database and critical information will bemissing.

Performance

The most important performance target is the time required to restore thedatabase. This determines how long the SAP R/3 system will be down andnot available for use. With SAP R/3 down, certain company operations maynot occur.

Backup performance is important, especially if the system is global or used 24hours a day. When doing a backup, it is important to minimize the impact onusers. The key is to reduce backup time, which in turn reduces the impact onthe users.

To increase performance:

� Identify the bottleneck or device that is limiting the throughput.

� Eliminate the bottleneck.

� Repeat both steps until the performance is adequate or the additional costis no longer justified.

This iterative process is subject to cost considerations. Additionalperformance can always be purchased, which is almost always a business costjustification exercise.

The most difficult requirement to comply with is magnetic fields. The problem is determining ifthere is a strong magnetic field near the tape storage location. A vacuum cleaner motor or alarge electric motor on the opposite side of the wall from where the data tapes are stored cangenerate a magnetic field strong enough to damage tapes.

Caution


Backup

All of the following backup performance items also apply to restoring thedatabase.

Three major variables affect performance:

� Database size

The larger the database, the longer it will take to back up.

� Backup window

The backup window is the time allocated for you to take the regularsystem backups. This window is driven by the need to minimize impacton the users.

• An online backup

The backup window for this backup type is defined as during non-peak periods of activity on the system and is usually done early in themorning.

• An offline backup

The backup window for this backup type is defined by when and forhow long SAP R/3 can be brought down and is usually done duringthe weekend.

� Hardware throughputThis variable limits how fast the backup can run and is defined by theslowest link in the backup chain such as:

• Database drive array

• I/O channel that is used

• Tape drive

Backup Options

Our backup options assume that the backup device is local to the databaseserver. A backup performed over a network will be affected by networktopology, overhead, and traffic. Rarely is the full capacity of the networkavailable. If a backup is done over the network, it will decrease networkperformance for other users. Although performing a backup over a network istechnically possible, it is beyond the scope of this guidebook. However, third-party products exist that do backup across the network.

Back Up to Faster Devices

All of the backup options attempt to eliminate the bottleneck at the backupdevice. The backup device, usually a tape drive, is the throughput-limitingdevice.

Note

Beware of the local time in othergeographical locations of yourcompany. For example, 1 am PST is 10am CET.


The table below contains capacity and throughput values to help you plantape drive selection:

The compressed capacity values in this table assume the use of hardwarecompression and use a more conservative 1.7x ratio, as opposed to the typical2x compression ratio. The actual compression ratio and rate depends on thenature of the file and how much it can be compressed.

A 20 GB database with only 9 GB of data will only require 9 GB of tape space.The tape space requirement increases as the volume of data in the databaseincreases. However, if you are backing up at the operating system level, theentire file is being backed up. Therefore, you must provide tape space for theentire 20 GB database.

As technology advances, and the capacity and throughput of tape drivesincreases, these values will become obsolete. We recommend that youinvestigate what is currently available at the time of your purchase.

Advantages:

� Faster and larger capacity tape drives allow you to back up an entiredatabase on a single tape cartridge in a reasonable period of time (forexample, a two-hour backup of a 60 GB database to a DLT7000).

Disadvantages:

� A backup to a single tape drive is the slowest option.

� Unless an automated changer or library is used, without manuallychanging the cartridge, you are limited to the maximum capacity of thetape cartridge.

Parallel Backup

Backing up to multiple tape drives uses a RAID-0 (stripe) array, in whichseveral tape drives are written to in parallel. In certain environments, likeOracle, individual tablespaces or files are simultaneously backed up toseparate tape drives. Because you are writing to multiple tape drives inparallel, total performance is significantly faster than if you were using asingle tape drive.

Type Capacity (GB) (native/compressed) Rate (GB/hr.) (native/compressed)

DAT (DDS-3) 12 / 20.4 3.6 / 6.1

DLT 4000 20 / 34 5.4 / 9.2

DLT 7000 35 / 60 18 / 30.6

DLT 8000 40/68 21.6/36.7

Super DLT 110/220 39.6/79.2

Not all databases andbackup tools support tapechangers or libraries;

make certain that these tools arecompatible before purchasingthem. For example, SAPDBAsupports tape changers, butMicrosoft SQL Server EnterpriseManager and NT Backup do not.


With a sufficient number of tape drives in parallel, the bottleneck can beshifted from the tape drives to another component. You must consider theperformance of each subsystem when using tape drives in parallel. Thissubsystem includes the tape drives, controllers, CPU, and I/O bus. In manyconfigurations, a controller or bus is the limiting factor.

Backing Up to Disks, Then to Tape

This method has the advantage of being the fastest option to back up thedatabase. Backing up to disk is usually faster than backing up to tape. You canquickly make multiple identical copies on disk, for example, for onsite andoffsite storage.

Once the backup has been made to disk, the system performance is minimallyaffected. Because the tape backup is made from the disk copy, not the livedatabase, the tape backup does not compete with database activity for systemresources. Also, during an onsite disaster recovery to the same equipment, therecovery can be done from the on-disk backup.

This method does have some disadvantages. Additional disk space, equal insize to the database, is required. For a larger database, this can incur extraexpense.

Also, until the backup to tape is complete, you are vulnerable to a data centerdisaster. In a disaster recovery situation, you must first restore the files todisk, then execute the database recovery from the disk.

Other options exist for faster backups, such as High Availability options, butthese options are beyond the scope of this guidebook.

Recovery

The performance requirement for a recovery is more critical than for backup.Recovery performance determines how quickly the system will be availablefor use and how soon business can continue. The goal is to restore thedatabase and related files to make the system quickly available for generaluse. The longer this restore takes, the greater the impact on your business.

Restore Options

To increase database restore performance, all of the above database backupoptions are valid. You can also restore to a faster disk array with a higherdata-write throughput.

You can perform a restore to a faster disk array by using:

� Dedicated drivesIn conjunction with parallel backups, restoring files and tablespaces toindividually dedicated disk drives speeds up the process. At any one time,only one tablespace or file is written to the drive, avoiding headcontention writing another tablespace to the same drive.

To restore a parallelbackup, all the tapes inthe set must be readable.

If one tape is bad, the entirebackup set will not be usable. Themore tapes you have in a set, thegreater the chance that one tapewill be bad.


� RAID typeMirrored stripe (RAID 0+1) is faster than RAID5, but this speed dependson the specific hardware. In most cases, the task of computing the paritydata for the parity drive (RAID5) takes more time than it would to write allthe data twice (RAID 0+1). This option is expensive because the usablecapacity is 50 percent of the total raw capacity—significantly less thanRAID5:

• RAID 0+1 = [single_drive_capacity × (number_of_drives/2)]

• RAID5 = [single_drive_capacity × (number of drives – 1)]

� Drives with faster write performance

� Drive array system with faster write performance

Useful SAP Notes

SAPNet – R/3 Frontend Note # Description

Microsoft SQL Server

141118 New Scheduling calendar in the CCMS(DB13) SQL Server 7

102467 Online documentation for SQL Server withSAP

50990 DB-Backup/Restore of Microsoft SQL Server

142731 DBCC checks for SQL Server 7

28667 Microsoft SQL Specific Profile Parameters

128126 Database Connect for external tools

111372 Standby Database for Microsoft SQL 7.0

126808 Configuration Parameter for Microsoft SQL7.0

Oracle

68059 SAPDBA - option -next with tablespace list

43499 All collective notes concerning DBA Tools

43491 Collective note: SAPDBA – Command lineoptions

43486 Collective note: General SAPDBA

43484 Collective note: General DBA

42293 SAPDBA - new command line option –analyze


34432 ORA-00020: max number of processesexceeded

31073 SAPDBA - new command lines -next, -analyze

21568 SAPDBA: Warning: only one member ofonline redo

16513 File system is full—what do I do?

15465 SAPDBA - shrinking a tablespace

04754 Buffer synchronization in centralized systems

03807 Tablespace PSAPROLL, rollback segmentstoo small

02425 Function of tablespaces/DBspaces on thedatabase

01042 ORACLE TWO_TASK connect failed

SAPNet – R/3 Frontend Note # Description

P A R T T H R E E

BTasks Overview


Part Overview

As a system administrator, you have tasks that you must perform to ensure the continuedfunctioning of your system.

This section covers scheduled tasks that must be done on a regular basis, as well as ad-hoc tasks that are done as necessary.

Chapter 4 covers regularly-scheduled tasks that occur on a daily, weekly, monthly,quarterly and annual basis.

Chapter 5 covers tasks that require more than one employee to complete.

Chapter 6 talks about general system administration. Tools and methods to monitor yourSAP system are discussed here.

C H A P T E R

4

4Scheduled Tasks


Overview

We have provided sample checklists that you may use and modify dependingupon your specific needs. The checklists provided for your convenienceinclude:

� Critical tasks

� SAP R/3 system

� Database

� Operating system

� Other

� Notes

Please note that just because tasks are listed weekly does not mean youcannot do it daily. The schedule of a task is dependent on the individualinstallation.


Daily

Critical Tasks

System: __________

Date: ____/____/____

Admin: _____________________

The SAP R/3 System

Tasks Transaction Chapter Procedure Check off/Initial

Check that theSAP R/3 systemis up

Log onto theSAP R/3 system

Check that dailybackupsexecutedwithout errors.

DB12 – BackupLogs: Overview

9-12 Check databasebackup.

Databasebackup run time.

Check operatingsystem levelbackup

Operatingsystem backuprun time

Task Transaction Chapter Procedure Check off/Initial

Check that allapplicationservers are up.

SM51 – SAPServers

6 & 15 Check that allservers are up.

Check theCCMS alertmonitor (4.0+).

RZ20 – CCMSMonitor

6 Look for alerts.

Check workprocesses(started fromSM51).

SM50 – ProcessOverview

6 & 15 All workprocesses with a“running” or a“waiting” status


Look for anyfailed updates(updateterminates).

SM13 – UpdateRecords

6 Set date to oneyear ago

Enter * in theuser ID

Set to “all”updates

Check for lineswith “Err.”

Check systemlog.

SM21 – SystemLog

6 Set date andtime to beforethe last logreview.

Check for:

Errors

Warnings

Securitymessages

Abends

Databaseproblems

Any otherdifferent event

Review forcancelled jobs.

SM37 – SelectBackground jobs

15 Enter anasterisk (*) inUser ID.

Verify that allcritical jobs weresuccessful.

Check for oldlocks.

SM12 – Lockentry list.

6 Enter anasterisk (*) forthe user ID.

Check forentries for priordays.

Check for userson the system.

SM04 – Users

AL08 - Users

6 Review for anunknown ordifferent user IDand terminal.This task shouldbe done severaltimes a day.



Database

Check for spoolproblems.

SP01 – Spool:Request Screen

13 Look for spooljobs that havebeen “inprocess” forover an hour.

Check job log. SM35 – Batchinput: InitialScreen

15 Check for:

New jobs

Incorrect jobs

Review andresolve dumps.

ST22 – ABAPDump Analysis

6 Look for anexcessivenumber ofdumps.

Look for dumpsof an unusualnature.

Reviewworkloadstatistics.

ST03N –Workload:Analysis of<SID>

18

Review bufferstatistics.

ST02 – TuneSummary

18 Look for swaps.



Review error logfor problems.

AL02 –Database (DB)alert

ST04 – DBPerformanceAnalysis

10

Checktables/spaceusage

DB12 9-12


Operating System

Other

Notes


Review systemlogs forproblems

OS06 – OSMonitor

14 Reviewoperatingsystem logs


Check theuninterruptiblepower supply(UPS)

UPS programlog

14 Review for:

� Events

� UPS selftest

� Errors

Problems Action Resolution


The SAP R/3 System

System: __________

Date: ____/____/____

Admin: _____________________

These tasks are done several times a day. Previous SAP R/3 tasks are once aday.


Look for anyfailed updates(updateterminates).

SM13 – UpdateRecords

6 Set date to oneyear ago

Enter * in theuser ID

Set to allupdates

Check for lineswith Err

Check SystemLog

SM21- SystemLog

6 Set date andtime to beforethe last logreview.

Check for:

� Errors

� Warnings

� Securitymessages

� Abends

� Databaseproblems

� Any otherdifferentevent


Critical Tasks

Some critical tasks should be completed every morning. These tasks help youdetermine if the SAP R/3 system is running properly, and if backupsexecuted and completed successfully. If these tasks determine that SAP R/3 isnot running properly, or backups did not execute or complete, the situationmust be resolved quickly to prevent downtime or data loss.

Verify that SAP R/3 Is Running

The first task of the day is to perform a high-level check to see if the SAP R/3system is running. If the system is not running, your users will be calling tofind out what happened and when the system will be up again.

At a basic level, if you can connect to the SAP R/3 system, you know that theSAP R/3 system is working, and the network between you and the SAP R/3system is working. To accomplish this, from a workstation, log on with theSAP GUI. If you can log on, the test is successful.

Verify that the Backups Ran Successfully

You must verify that the backups that were supposed to run last night ransuccessfully. Backups of the SAP R/3 database and related non-databaseoperating system level files are essential to recover the SAP R/3 system.

Types of nondatabase files include:

� Database log dumps

Review forcancelled andcritical jobs

SM37 – SelectBackground jobs

15 Enter * in UserID

Verify that allcritical jobs weresuccessful.

Review anycancelled jobs.

RZ01 –Graphical jobmonitor

15 Same as forSM37

Check users onsystem

SM04 – Users

AL08 – Users

6 Review for anunknown ordifferent user IDand terminal.This task shouldbe done severaltimes a day.



� Data files for third-party applications that do not store their data in thesystem

� Examples of such files are external tax files.

� Transport files

� Inbound and outbound interface files

� Externally stored print files

Problems with the backups must be quickly resolved. If a database failureoccurs that requires a restore, and the last backup failed, you will have torecover using the last successful backup. If you do not have a usable backup,you must use an older backup, and apply transaction logs, which willincrease the time required to restore the database and bring it current.

Once the problem has been fixed, execute an online backup if it does notsignificantly impact performance or if policy requires such a backup.

At the operating system level, some of these files may need to be in sync withthe SAP R/3 database. Restoring the SAP R/3 system without these filesresults in an unusable restore (for example, external tax files that must be insync with the system data or the tax systems reports will not match the SAPR/3 reports).

These critical tasks must be done first thing in the morning. If there is anoperations shift that runs between 10:00 p.m. and 7:00 a.m., the backup checkshould be done once the backup job is complete.

In chapters 4 through 8, we have included a list of transactions like the onesbelow. This list contains basic information about selected transactions in thechecklist. For additional information on these transactions, see the chapterreferenced in each checklist.

Any failed backup mustbe immediatelyinvestigated and

resolved. Do not maintain a “wewill just run the backup againtonight and see if it works”attitude. If that backup fails, youhave another day without abackup.

Transaction Name Transaction Code Description Reason for Use

User AL08/SM04 Displays all userscurrently logged ontothe system, with userID and terminal name

Lets administratorsdetect erroneous ormultiple logons

OS Monitor OS06 View system logs Lets administratorsdetect possible OSand hardwareproblems (such as afailing hard drive)

Select BackgroundJobs/Graphical JobMonitor

SM37/RZ01 Select and monitorbackground batchjobs

Determine if criticaljobs have failed toexecute. Other tasksmay depend oncompletion of thesejobs.

We presume that theprofile parameterrdisp/gui_auto_logout

has been set. This parameterdefines an automatic logout of theuser if there is no activity for theset number of minutes.


CCMS Alert Monitor RZ20 Monitor servers(DEV, QA, Testing,PRD, and so on) inyour landscape fromone central program

Alerts are signs ofpotentially seriousproblems in need ofimmediate resolution.

Lock Entry List SM12 Displays a list oflocked transactions.

Locks prevent otherusers from changingthe record on whichyou are working.

Allows theadministrator to clearold and unreleasedlocks

Update Records SM13 Allows theadministrator todisplay, process, test,reset, delete and getstatistics on updates

In the event that anupdate is notprocessed, theadministrator canmanage theprocessing manually.

System Log SM21 Analyze system logs Helps anadministrator detectSAP R/3 systemproblems early

Batch Input SM35 Manage batch inputsessions

Alerts you to new orincorrect batchsessions

Work Processes SM50/SM51 View status of workprocesses (SM50 –used for systemswithout applicationservers) (SM51 –central transactionthat starts SM50 foreach applicationserver)

Allows users tomonitor workprocesses and see ifany have failed or aretaking too long

Spool SP01 SAP R/3 systemoutput manager

Helps to resolvetime-critical print jobproblems

Tune Summary ST02 Displays SAP R/3buffer performancestatistics. Assists intuning SAP R/3buffer parameters, aswell as SAP R/3database andoperating systemparameters

Resolvesperformance issuesrelating to significantbuffer swapping.Look for red entriesin Swaps, andmonitor over time todetermine anytrends.



Workload Analysis of<SID>

ST03 Determines systemperformance

Understanding thesystem while it isrunning well can helpyou determinechanges that mayneed to be madeduring problemtimes.

DatabasePerformanceAnalysis

ST04 High-level databaseperformance monitor

Monitors databasegrowth, capacity,input/output statisticsand alerts. Alsoprovides additionalinformation usingdrilldown, and allowsdatabase monitoringwithout logging intoit.

ABAP DumpAnalysis

ST22 Views logs of ABAPdumps

Assists indetermining why areport or transactionterminated



Weekly

The SAP R/3 System

System: __________

Date: ____/____/____

Admin: _____________________

Database

Tasks Transaction Chapter Procedure Check off/Initial

Check databasefor free space

DB02 – DBPerformance:DatabaseAllocation

9-12 Record free space

Monitor andestimate futuredatabase growth

DB02 – DBPerformance:DatabaseAllocation.

9-12 Record databasespace history

Check spool forproblems and thatspool is properlycleared

SP01 - Spool 13

Transport into PRD STMS

tp at OS level

16 All properlyapprovedtransportsimported into PRD

TemSeConsistency check

SP12 13 Deleteinconsistencies

Review SecurityAudit Log

SM20 7


DBCC 13 Check output fromDBCC job forerrors (SQLServer)

Run MS-SQLserver updatestatistics

10 Check forsuccessfulcompletion ofupdate stats job


Operating System

Other

Notes

In chapters 4 through 8, we have included a list of transactions like the onebelow. This list contains basic information about the transactions in thechecklist. For additional information on these transactions, see the chapterreferenced in each checklist.


Check filesystem foradequate space

RZ20 – CCMSAlert

Files system

10 Review spaceusage and thatsufficient freespace exists inthe file systems


Check systemmonitoringsystems forupdate

System monitor 15 Review for anyevents thatshould be addedor deleted

Check systemmonitor alertmechanisms

System monitor 15 Test e-mail

Test paging

Clean tape drive Tape drive 15 Clean usingcleaningcartridge

Problem Action Resolution



DatabasePerformance

DB02 Examine databaseallocation

Monitor databasespace history andperform databaseanalysis

CCMS Alert Monitor RZ20 Monitor servers(DEV, QA, Testing,PRD, and so on) inyour landscape fromone central program

Alerts are signs ofpotentially seriousproblems in need ofimmediate resolution.

Spool SP01 SAP R/3 systemoutput manager

Helps to resolvetime-critical print jobproblems

TemporarySequential (TemSe)databaseconsistency check

SP12 Compares data inTemSe (TST01)objects and TemSe(TST03) data tables

Relationshipsbetween object anddata in the TemSEcan be destroyed asa result of restoringfrom backups,copying database,copying clientsimproperly, ordeleting client withoutfirst deleting theirobjects)

TMS System STMS Helps you performtransports

Assists in movingobjects andconfigurationbetween systems orclients in theproduction pipeline


Monthly

The SAP R/3 System

System: __________

Date: ____/____/____

Admin: _____________________

Database

Operating System


Defragment thememory

Cycle the SAPR/3 system


Plot databasegrowth

DB02—DBPerformance:Tables

9-12 Record usageand plot


Backup fileserver

Review filesystem usage

14 Perform fullserver backup

Record filesystem usage

Plot usage

Is additionalstorage spaceneeded?

Is housecleaningneeded?


Other

Notes



Checkconsumablesupplies

15 Spare tape cleaning cartridgeavailable for all tape drives(such as DLT, DAT)

Spare tape cartridges availablefor all drive types

Spare data cartridges availablefor removable media devices(such as ZIP, CD-R, and so on)

Preprinted forms (such asshipping documents, invoices,and checks)

Special supplies, such asmagnetic toner cartridge

Normal supplies (such as laserprinter toner, printer paper,batteries, diskettes, pens, andso on)



DatabasePerformance

DB02 Examine databaseallocation

Monitor databasespace history andperform databaseanalysis


Quarterly

The SAP R/3 System

System: __________

Date: ____/____/____

Admin: _____________________


Archive quarterlybackup

Send quarter-endbackup tapes tolong-term offsitestorage

Security review SU01—UserMaintenance

7 Review user ID forterminated usersthat should belocked or deleted

SM31—TableMaintenance

16 Review list of“prohibited”passwords (TableUSR40)

RZ10—Edit SystemProfile

21 Review systemprofile parametersfor passwordstandards

Review scheduledjobs

SM37—Background Jobs

15 Review allscheduled jobs todetermine if theyare still appropriate


Database

Operating System

Other


Archivequarterly backup

3 Send quarter-end backup tapeto long-termoffsite storage.

Review allscheduled jobs

SM37 15 Review allscheduled jobsto determine ifthey are stillappropriate.

Test databaserecoveryprocess

2 & 3 Restoredatabase to atest server.

Test the restoreddatabase.


Archivequarterly backup

3 Send quarter-end backup tapeto long-termoffsite storage.

Archive oldtransport files.

Transportdirectories; log,data, cofiles

Archive the oldtransport files.

CleanupSAPDBA logs(Oracle)

SAPDBAcleanup

Maintaininit<SID>.dba


Checkmaintenancecontacts

Check forexpiration date

Check for usagechanges


Notes

In chapters 4 through 8, we have included a list of transactions like the onesbelow. This list contains basic information about the transactions in thechecklist. For additional information on these transactions, see the chapterreferenced in each checklist.


Transaction Name Transaction Code What Why

Edit System ProfileParameters

RZ10 Allows theadministrator tochange securityparameters, such aspassword length,password changeperiod, user lockout,and so on

Properly assignedparameters make itmore difficult to breakinto the system.

Select BackgroundJobs

SM37 Select and monitorbackground batchjobs

Determine if criticaljobs have failed toexecute. Other tasksmay depend oncompletion of thesejobs.

User Maintenance SU01 Allows anadministrator tochange the status ofa user

Administrators canlock and unlockusers, preventing orallowing access tothe SAP R/3 systemas needed.


Annual

The SAP R/3 System

System: __________

Date: ____/____/____

Admin: _____________________


Archive year-end backup

3 Send year-endbackup tapes tolong-term offsitestorage

Audit usersecurity

7 Review userssecurityauthorizationforms againstassignedprofiles.

Can also bedone with reportRSUSR100

Audit profilesandauthorizations

SU02 – SecurityProfileMaintenance

7 Can also runwith reportRSUSR101

SU03– SecurityAuthorizationMaintenance

7 Can also runwith reportRSUSR102

Reviewsegregation ofduties

Audit user IDsSAP* and DDIC


Database

Operating System

Run SAP useraudit reports

SA38 (or SE38)– Execute ABAPprogram

7 Run user auditreports.RSUSR003,RSUSR005,RSUSR006,RSUSR007,RSUSR008,RSUSR009,RSUSR100,RSUSR101,RSUSR102

Check that thesystem is set toNot modifiable

SE03 –WorkbenchOrganizer Tools

7 Verify thatsystem is set toNot modifiable

SCC4–“Clients”:Overview

7 Checkchangeablestatus forapplicable client

Check lockedtransactions

SM01 –Transactioncodes:Lock/Unlock

8 Check againstyour list oflockedtransactions





Task Transaction Chapter Procedure Column Title




Other

Notes


Perform disasterrecovery.

2 & 3 Restore entiresystem todisasterrecovery testsystem

Test businessresumption





SA38/SE38

SU01

SU02

SU03

All users who haveleft the companyshould have theirSAP R/3 accessterminatedimmediately. Bylocking or deletingthese user IDs, youlimit access to onlythose users whoshould have accessto SAP R/3. Periodicreview assures thetask of locking ordeleting has beencompleted.

Proper audit controlrequires that a userwho no longer has avalid business needto access SAP R/3should not beallowed to keep thataccess.

Deleting or lockingthese user IDs alsoprevents anyone whohad been using theterminated user IDfrom accessing thesystem under that ID.

Change ObjectDirectory Entry ofObjects

SE03/SCC4 Allows theadministrator to testand apply changesproperly

Objects should notbe modifiable in thequality assurance orproduction systems.This rule is to protectthe productionsystem from objectand configurationchanges being made,without first beingtested. By setting theproduction system toNot modifiable, theintegrity of thepipeline is preserved.

SM01 Lock transactionsfrom being used

Prevents users fromdamaging the systemby running certaintransactions

Note

Switches prevent changes from beingmade in the system. In the productionsystem, these should be set to Notmodifiable, to ensure that changes aremade using the development pipeline.

In the development pipeline, changesare:

� Created in the developmentsystem

� Tested in the developmentsystem

� Transported from thedevelopment system to the testsystem

� Tested in the test system

� Transported from the test systemto the production system

Using this procedure, changes areproperly tested and applied to thesystems in the pipeline.


Dangerous transactions are transactions that could do the following:

� Damage or corrupt the system

� Present a security risk

� Adversely impact performanceIf a user accidentally accesses these transactions, they could corrupt or destroy the SAP R/3system. Access to dangerous transactions is more critical in the production system than thedevelopment or test systems. This is because of live data and the fact that the company’soperations are dependent on the SAP R/3 system.

Certain transactions should be locked in the production system, but not in the development, test,or training systems. Standard security normally prevents access to these transactions.However, some administrators, programmers, consultants, and functional key users could haveaccess to the transactions depending on the system they are on. In these cases, the transactionlock provides a second line of defense.

The SAP R/3 system has over 48,000 English transaction codes. To make it manageable, onlythe critical ones must be locked. Your functional consultants should supply you with anyadditional critical transactions in their modules.

Caution

C H A P T E R

5

5Multi-Role Tasks


Starting the SAP R/3 system

To start the SAP R/3 system in a productive environment:

1. Start the operating system (if required).

2. Check the operating system logs to verify a good start.

3. Start any application servers.

4. Start the database.

5. Check the database logs to verify a good start.

6. Start SAP R/3 on the central instance.

7. NT/SQL: Use the SAP Management Console.

8. UNIX: At the command prompt, enter startsap r3.

9. Check the R/3 System log (SM21) to verify a good start.

10. Problems at this point may require you to reset the system.

11. Start SAP R/3 on the application instances.

12. Check the R/3 System log.

Start SAP R/3–NT (SQL Server, Oracle)

The following task describes how to start SAP R/3 from a Windows NTenvironment uf you use an MS SQL Server or Oracle database.

Task

Start SAP R/3 with Microsoft SQL Server or Oracle on a Windows NT system

1. From the taskbar, choose Start → Programs → SAP R3 Management Console.

2. Select the nodes (+) to drill down to the servers.

When you start the SAP R/3 system, wait for 60 seconds. This step makes it easier to read thesystem log. For example, the last stop entry is 19:26:xx and the first start entry is 19:27:xx,where time is reported as hh:mm:ss.

Note

This step is optional because startingthe SAP R/3 system also starts thedatabase. However, manually startingthe database allows you to review thedatabase log before starting the SAPR/3 system.

NT/SQL: If not automatically started,use the SQL Server Service Managerto start the database.

NT/Oracle: If not automatically started,use SAPDBA to start the database.

UNIX: At the command prompt, enterstartsap db.

Tips & Tricks


3. To start the central instance on the database server, right-click on the databaseserver (for example, pa102058), and choose Start.

4. When the status indicators for the database server turn green, the databaseinstance has started and SAP R/3 has completed the start process. Wait a fewminutes because startup activity is still occurring on the server.

The steps below are applicable only if you have an application server:

Task

Start SAP R/3 with an application server

1. Start the dialog instance (on the application server).

Tools such as QuickSliceand Perfmon allow you tomonitor the activity of the

server and know when you canlog on to the system.


2. Select the nodes (+) to drill down to the application server (for example,pal01003). Right-click on the server name and choose Start.

3. The status indicators for the application server change color to green,indicating that the database instance has started and that SAP R/3 hascompleted the start process. Wait a few minutes because startup activity isstill occurring on the server.

Stopping the SAP R/3 system

Reasons to shut down a productive SAP system include:

� Hardware/Software failure (unplanned)


� Hardware/Software maintenance (planned)

� Full server backup (planned)

Stop SAP R/3 Checklist

Tasks to Be Completed Before Stopping the System

Coordinate the shutdown with all effected parties. If a group has planned todo something and expects the system to be operational, they may or may notbe able to reschedule. You may have to reschedule your shutdown tocompensate for their business requirements.

When you stop SAP R/3, coordinate and plan this stoppage with all users or theirrepresentatives. Stopping a system at your convenience is unprofessional and usually causesconsiderable operational issues with users who need (and expect) the system to be up andrunning.

Tips & Tricks

Task Date Initial

The following tasks must be completed well before the SAP R/3 system is stopped:

Coordinate the shutdown with all affected parties, such asFinance, Shipping, Sales, and so on.

Reschedule/cancel jobs that would be running or startingduring the scheduled shutdown (SM37).

Create a system message announcing the planned shutdown(SM02).

Send email notification to affected user

The following tasks must be completed before the SAP R/3 system is stopped:

Check that there are no active users on the system (SM04 andAL08).

Check that there are no active background jobs running(SM37).

Check for active processes (SM50 and SM51).

Check for active external interfaces.

To stop the SAP R/3 system:

Stop the application server instance(s).

Stop the central instance.

Stop the database (optional).


Before stopping the system, there are several checks that must be made. Thepurpose is to determine that there is no activity on the system when thesystem is stopped. Certain activities (such as a large posting job), ifinterrupted, could have some transactions posted and some not yet posted.Recovery could then become an issue.

Reschedule or cancel jobs that will be running or starting during thescheduled shutdown.

� Check SM37 for these jobs and cancel or reschedule them to run after theshutdown.

� Watch for repeating jobs, such as daily or weekly jobs. These jobs are notcreated until the job for the prior period (such as day or week) has run. Inother words, a daily job does not exist several days in advance.

Create a system message announcing the planned shutdown. Emergency orpriority shutdowns (for example, file system full, log full, equipment failure,and so on) are a different matter. In these instances, you must shutdownimmediately and users must accommodate you. There may be little—if any—negotiating.

System Message (SM02)

A system message is a popup that users see when they first log on to the SAPR/3 system. This window appears after a new message has been created orwhen users move between screens.

Task

Send a system message

1. In the Command field, enter transaction SM02 and choose Enter(or from the navigation menu, choose Tools → Administration →Administration → SM02-System messages).

2. On the System Messages screen, choose Create.

If you are the cause of theemergency, be preparedto take the

consequences.An example of an emergency isnot monitoring the file system,having it fill up, which results instopping SAP R/3.


3. In the Create System Messages dialog box:

a. In System message text, enter your message.

b. If you are only shutting down one server, you may also enter text in theServer field. To enter this text, choose and select the server on whichthe message should appear.

c. In Expiry on, enter the message’s expiration date and time.

d. Choose .

4. The message in the status bar indicates that your message has been saved.

5. When the user logs on to the SAP R/3 system, they will see a message dialogbox similar to the screenshot below.

When referencing thetime for the shutdown,always enter the specific

time, time zone, and date (forexample, 0230 PDST-Mon–Jun8,1998). Entering vagueinformation, such as “in 15minutes” creates possibleconfusion as to when and wherean event has been scheduled.


Check that No Active Users Are on the System (AL08/SM04)

All users should log off of the system before you shut down SAP R/3. Youcan perform the following two tasks to check if users are still logged on to thesystem.

Task

Check that no active users are on the system (system without application servers)

1. In the Command field, enter SM04 and choose Enter (or from the navigationmenu, choose Tools → Administration → Monitor → System monitoring →SM04-User overview).

2. Contact the users by phone or email and have them log off.

3. If users cannot be contacted, delete their session as described in “Deleting aUser’s Session (Transaction SM04)” on page 247.

Task

Check that no active users are on the system (systems with application servers)

1. In the Command field, enter AL08 and choose Enter (or from the navigationmenu, choose Tools → CCMS → Control/Monitoring → Performance menu →Exceptions/users → Active users → AL08-Users global).

2. Scroll down the transaction screen to see all the servers in the system and theusers on those servers.

3. Contact the users to have them log off.


4. If the users cannot be contacted, delete their session as described in “Deletinga User’s Session (Transaction SM04)” on page 247. You cannot delete a userfrom transaction AL08. You must log on to the individual instance and usetransaction SM04 to delete the user session.

Check for Batch Jobs Running or Scheduled (SM37)

Check for any batch jobs that are running or are scheduled to run during theshutdown.

Task

Check for batch jobs running or scheduled

1. In the Command field, enter SM37 and choose Enter (or from the navigationmenu, choose Tools → CCMS → Jobs → SM37-Maintenance).

2. On the Simple Job Selection screen:

a. In User name, enter *.

b. Under Job status, select the following checkboxes:

� Sched.

� Released

� Ready

� Active


c. In Fr., enter a date one year ago from today.

d. In To, enter a date in the future beyond the shutdown period (forexample, if the shutdown period is from 07/13/2001 at 23:00 to07/14/2001 at 23:00, use a To date of 07/15/2001).

e. In or after event, choose and select *.

f. Choose Execute.

3. Choose a job within the shutdown period to review (for example,SPOOL_CLEANUP).

4. From the menu bar, choose Job → Change.Change the display to

show the planned startdate and time. From the

menu bar, on the screen above,choose Settings → Displayvariant → Current (ChangeLayout in 46D). On the fieldselection screen, move thescheduled start date andscheduled start time from thehidden fields on the right, to thedisplayed fields on the left.


5. Choose Start condition.

6. In Scheduled start, change the date to a date after the shutdown.

7. Choose .

8. Verify the new start date.


9. Choose .

10. A message indicates that the job was saved.

11. Repeat steps 3-10 for each of the other jobs that must be moved.


12. As a final step, repeat the initial job selection to verify that there are no jobsscheduled during the system shutdown.

Check for Active Processes on All Systems (SM51)

The following task displays processes that are active or running. You can alsodetermine which user is running the process.

Task

Check for active processes on all systems

1. In the Command field, enter transaction SM51 and choose Enter (or from thenavigation menu, choose Tools → Administration → Monitor → Systemmonitoring → SM51-Servers).

2. On the SAP Servers screen:

a. Select an instance.

b. Choose .

Note

The screen that appears is thetransaction SM50 screen for thatserver.


3. Review for activities.

4. Choose and return to the SAP servers transaction (SM51).

5. Repeat steps 2-4 for each instance.

Check for External Interfaces

External interfaces move data to or from the SAP R/3 system. Checking foractive interfaces depends on the specific interface and how it has beendesigned, built, and implemented. The developer or consultant can help youdetermine if the interface is active.

Stopping SAP R/3

Stop SAP R/3 only after all checks have been made and you are certain thatthere is no activity on the system. To stop the SAP R/3 system:

1. If there are application servers in the system, stop the instance on theapplication servers.

2. Stop the instance on the database server.a. NT/SQL:Use the SAP Management Console.b. NT/Oracle:Use the SAP Management Console.c. UNIX/Informix or DB2:At the command prompt, enter stopsap.

This script may also stop the database; check your specific installation.You can also use SAPDBA to stop the instance.

3. If needed, stop the database.The database must be stopped separately. Unlike the start process,stopping the system does not also stop the database.a. NT/SQL:Use SQL Server Service Manager to stop the database.b. NT/Oracle:Use SAPDBA to stop the database.c. UNIX:Use either SAPDBA or the stopsap script to stop the database.

4. If needed, stop the operating system.

You can monitor activeRFC connections usingtransaction SMGW.

When you bring down orstop SAP R/3, coordinateand plan this event with

all the SAP R/3 users or theirrepresentatives.

Stopping a system at yourconvenience is unprofessionaland usually causes considerableoperational issues with users whoneed (and expect) the system tobe up and running.


STOP SAP R/3–NT

Task

Stop SAP R/3 in Windows NT

1. From the taskbar, select Start → Programs → SAP R3 Management Console.

2. Drill down to select an SID (for example, SA1), then a server (for example,pa102058 and pal01003).

Task

Stopping SAP R/3 if you have application servers

1. Stop the SAP R/3 dialog instance (on the application server).

2. Select the nodes (+) to drill down to the application server (for example,pal01003).


3. Right-click on the application server and choose Stop.

4. Choose Yes.

5. When SAP R/3 stops, the status indicators change color to gray.

6. Stop the SAP R/3 central instance (on the database server).

7. Select the nodes (+) to drill down to the database server (for example,pa102058).


8. Right-click on the database server and choose Stop.

9. Choose Yes.

10. When SAP R/3 stops, the status indicators change color to gray.

C H A P T E R

6

6SAP System Administration


Overview

This chapter will help you understand how to monitor your system. It iscrucial that a system administrator gets a quick overview of the system statusand is quickly notified of critical situations. In this chapter, you will learnabout:

� Some Computing Center Management System (CCMS) tools

� Major tasks

� Specific transactions

� System messages

Major System Monitoring Tools

The CCMS Central Alert Monitor and the System Administration Assistant(SAA) perform two different functions. The CCMS Central Alert Monitor isprimarily an alert monitor. The SAA is a control panel from which you candirectly access the specific monitoring tools and be notified of alerts. If youhave time constraints, these tools provide a quick overview of system statusand notify you of critical situations.

CCMS Central Alert Monitor (Transaction RZ20)

Using transaction RZ20, you can monitor the servers in your landscape, suchas development, quality assurance, testing, production, and so on. You nolonger have to individually log into each system to search for alerts. If there isan alert, the monitor will link to many of the other transactions in thisguidebook.

An alert indicates a potentially serious problem that should be quicklyresolved. If not contained, these problems could deteriorate into a disaster.

You can do many of your system monitoring tasks with the Central Alert Monitor.

To view Alert Monitor documentation, from the menu bar, choose:

Help → SAP Library.

SAP Library → Basis Components → Computing Center Management System (BC-CCM) →Computing Center Management System (BC-CCM)

Computing Center Management System (BC-CCM) → CCMS Monitoring → The AlertMonitor.

Tips & Tricks

The Central Alert Monitoris not a replacement forexamining other checklist

tasks. Certain alerts, such asMicrosoft SQL Server and TMShave not yet been integrated intothe Central Alert Monitor.


Task

Access the CCMS Alert Monitor

1. In the Command field, enter transaction RZ20 and choose Enter (or from theSAP standard menu, choose Tools → CCMS → Control/Monitoring → RZ20-Alertmonitor). This screen is the standard display. We will use a modified displaywith most of the monitor sets suppressed.

2. On the CCMS Monitor Sets screen, we displays only two monitor sets:

� SAP-delivered SAP CCMS Monitor Templates

� User-created SystemAdmin docu

3. Select the node (+) to expand the monitor sets. In this example, we copied theEntire System monitor from the SAP CCMS Monitor Template into SystemAdmindocu. This step allows us to modify the monitor.

Under SAP CCMSMonitor Templates, thereare predefined monitors

to use as your starting point.

These monitor templates cannotbe modified. To modify them, copythem into a customer monitor setand modify the monitor there.


4. To load the monitor, select a monitor (for example, Entire system) and choose.

5. The monitor contains the alerts for a single system/SID. In our example, theapplication servers pa102058_SA1_00, (central instance) andpa101003_SA1_00, (application server) are displayed.


Current View and Alert View

The CCMS Alert Monitor display has two modes, the current system status(which shows the current alert situation right now) and open alerts (whichshows alerts that have been generated but not yet acknowledged.)

The recommended process is to address problems in the current system statusfirst, then work on open alerts.

Task

Switch between the current and alert views

1. On the SystemAdmin docu (Entire System) screen:

a. To view alerts, choose Open alerts.


2. To return to the current status view, choose Current status.

Task

Find an alert

1. From the SystemAdmin docu (Entire System) screen:

a. Look for red node text. If a node text is highlighted in red, an alert will bedisplayed below that text.

b. Drill down to the bottom node.


2. In our example, the alert node is Percentage Used of the file system on drive H.

a. Select the node text.

b. Choose .

3. Scroll to the bottom of the screen or choose .


4. At the bottom of the detail screen are two tables. These tables show the alertvalues over the last half-hour and last 24 hours. These tables can be ofsignificant value in troubleshooting.

5. To display a graph of a timetable, select the table to use (for example, last 24hours) and choose .

6. The graphical display shows how the values changed over a 24-hour period.

7. Choose when you have finished.


8. Choose Performance history. The batch job that collects historical data must berunning. The default setting is that the job will not run. Running this job willadd more data to the database and affect database growth. For moreinformation, see “Configuring the Batch Job to Collect Historical Data (RZ21)”on page 726.

9. If the Determine MTE performance history data screen displays, choose User.

10. Enter a time frame in the From and To fields.


11. Choose .

12. Select the history items to display.

13. Choose .


Task

View the alerts

1. Choose Display alerts.

2. The alerts are listed in order of priority (Red at the top and yellow below).

Task

Analyze the alert

1. Select an alert.


2. Choose .

3. The specific analysis tool that is started is node-dependent. These tools areindividually covered in the remainder of this guidebook. If no tool isassigned, a No method assigned message will appear.


Task

Acknowledge the alert

1. From the Monitoring Attributes – Detail Data screen, choose Display alerts.

2. Select the alert to acknowledge.

3. Choose Complete alert.

4. Note the message at the bottom of the screen.

You still must perform atask based on the alert.Acknowledging the alert

only means that you received thealert notification.


5. One less alert is displayed.

6. When all alerts and warnings are acknowledged, the alert will change color togreen.


Task

Provide system configuration information (transaction RZ20)

1. Under the SAP CCMS Monitor Templates, select System Configuration.

2. Choose .

3. The various nodes will provide information about clients, database, and yourSAP license.


4. As shown here, a monitor can be configured to display multiple systems.Note that this monitor has been configured to monitor the following systems:

Maintaining The Alert Thresholds for RZ20

The alert threshold is the point where the alert indicator changes color from:

� Green to yellow

� Yellow to red

� Red to yellow

� Yellow to green

Each installation is different, so the point at which an alert changes colordepends on the individual installation.

RZ20 Configuration. Toconfigure to monitormultiple systems, see the

SAP R/3 online documentation:SAP Library → BasisComponents → ComputingCenter Management System (BC-CCM) → Computing CenterManagement system (BC-CCM)

Computing Center Managementsystem (BC-CCM) → CCMSMonitoring → The Alert Monitor→ The Monitoring Architecture:Concept → What is Predefinedin the Alert Monitor?

In the right frame, choosemonitoring multiple R/3 systems.

System SID Basis

SAP R/3 SA1 46C

SAP R/3 DI2 46C

CRM C2B 46D

BW BW2 46D


Sample situations where you would want to change the threshold levelswhen:

� A high amount of paging is a cause for concern on the production system,but it is expected on the development system.

� The only file on a drive may be the database file, which is completely fillingthe drive.

� A file system full alert on that particular drive is of no concern, becausethe database would have been configured to take up the whole drive.

Task

Maintain alert thresholds

1. Select the node (+) for the specific alert that you want to change the threshold.

2. Select an alert.

3. Choose Properties.

4. If the displayed values are for a group, an indicator field will appear in thescreen. The group indicator means that the values displayed apply to alldrives, not just the selected drive.


5. To switch to group or individual:

a. Group: From the menu bar, choose Edit → Properties → Use from MTEclass/group.

b. Individual: From the menu bar, choose Edit → Properties → Use forindividual Monitoring Tree Element (MTE).

6. If you choose group, the Monitoring: Properties and Methods dialog boxappears. Choose .

7. Choose .


8. The threshold value field will change color from gray to white.

9. If the transaction is set to group mode, a message appears in the status bar.

10. Enter new values for when the alerts will change (for example, 98). Thesethreshold values are specific to the alert you indicated.

11. Choose .


Hiding SAP Standard Monitor Sets

The monitor sets that are being hidden are not usually needed.

Task

Hide SAP standard monitor sets

1. On the CCMS Monitor Sets screen, from the menu bar, choose Extras →Activate maintenance function.

2. Expand all the monitor sets.

3. Under Public sets, select a monitor set (for example, SAP BusinessCommunication).

4. Choose .


5. Deselect Public (visible for all users).

6. Choose .

7. The monitor set will disappear from My favorites and Public sets.

8. The set still exists under SAP. If necessary, this set could be made visible tothe public again.


9. Repeat the steps until the only SAP standard set remaining is SAP CCMSMonitor Template.

10. Once the extra monitor sets have been removed, your screen should look likethe screenshot below.


Create a New Monitor Set

The following task shows you how to create a new monitor set.

Task

Create a new monitor set

1. On the CCMS Monitor Sets screen, from the menu bar, chooseExtras → Activate maintenance function.

2. Select Public sets.

3. Choose .

4. Under Monitor set, enter a name for the new monitor set (for example,SysAdmin 2).

5. Select Public (visible for all users).


6. Choose .

7. The new monitor set appears in Public sets and My favorites.

8. To turn off maintenance, from the menu bar, choose Extras → Deactivatemaintenance function.

9. The new monitor set (SysAdmin 2) appears on the screen.


Task

Add a Monitor to the Monitor Set

1. From the menu bar, choose Extras → Activate maintenance function.

2. Select the Monitor set (for example, SysAdmin 2).

3. Choose .

4. Expand the monitor design tree.

5. Select the nodes (+) that you want to include in the monitor (for example,Background under both SA1 and DI2).


6. Choose .

7. In Monitor, enter a relevant name for the new monitor (for examplebackground-SA1+DI2).

8. To save the monitor definition, choose .


9. The monitor definition is saved.

10. To turn off maintenance, from the menu bar, choose Extras → Deactivatemaintenance function.

11. Select the new monitor.

12. Choose .


13. Expand the monitor tree.

14. This new monitor shows only the nodes you selected. This monitor tracksbackground service on two different systems (SA1 + DI2).

System Administration Assistant (Transaction SSAA)

The System Administration Assistant (SAA) was developed as part of theReady-to-Run-R/3 project. The core of the SAA has been brought intostandard SAP R/3 and is now available to everyone. The SAA lists all the SAPR/3 administrative tasks and tracks tasks that must be done, and providesdocumentation on each task and displays critical and non-critical alerts.

The SAA helps the system administrator track work by providing a point ofreference for all relevant system administration transactions.

Task

Run the System Administration Assistant

1. In the Command field, enter transaction SSAA and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → SSAA-SystemAdministration Assistant).


2. On the R/3 Administrative Activities screen:

a. Choose Entire View tab. The Entire View tab is chosen by default.

b. Choose .

3. Choose .


4. From the menu bar, choose View → Transaction code/module to display thetransaction codes on the right side.

5. If a task needs to be performed, a red square appears next to it.

6. To execute the task, choose on that line (for example, R/3: CheckingBackground Jobs).


7. The associated transaction is started. The specific transaction code selected isnode-dependent. The task to execute the transaction will be specific to thestarted transaction.

8. When you have finished, choose .

9. The list is updated, and a green circle appears next to the task, indicating thatit has been performed.

10. To see if there are any alerts in each task, choose List Current Alerts.


11. Critical and noncritical alerts in each task are displayed.

Specific Transaction Monitoring Overview

Failed Updates (Transaction SM13)

An update terminate (or failed update) is an update to the database thatfailed. These terminates occur when a user entry or transaction is not enteredor updated in the database. The following example should help clarify thisconcept:

Example

The accountant gives a file clerk a folder (similar to saving a transaction).

The file clerk gives the accountant a receipt (similar to the SAP R/3 document number).

On the way to the file cabinet, the clerk falls and gets hurt.The folder in not filed in the cabinet (the failed update).

The end result is that the folder is not in the cabinet—even though the accountant has thereceipt.

This same end result occurs in an update environment, the document is not in the SAP R/3system—even though the user has a document number.

For performance reasons,the database update isdone in an asynchronous

mode. In this mode, the usercontinues to work while the systemtakes over the update process andwaits for the database update tocomplete.

In synchronous mode, users mustwait until the database hassuccessfully updated before theycan continue to work.


Users assume that when they receive a document number, the entry has beenrecorded in the system. However, if the update has terminated, even if theusers received a document number, no trace of it exists in the system.

Check the system for failed updates several times a day.

During normal business hours, the checks can be distributed:

� First thing in the morning

� Late morning

� Early afternoon

� Late afternoon

If you have a global operation, your schedule should be adjusted to accountfor other time zones and someone in that time zone should participate in themonitoring.

Task

Check the system for failed updates

1. In the Command field, enter transaction SM13 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → SM13-Update).

Example

Even though a sales order document number is generated, the order does not exist. Therefore,customers would not receive their order, and no trace of the order would exist in the system.

On Windows NT, from SAP R/3 release 3.0F and higher, system log entries are written to theNT event log. You might consider configuring an event log monitor to page you when an updateterminate occurs. This step reduces the need to constantly check transaction SM13. It alsoreduces the exposure between the time the update terminate occurs, when you find out aboutit, and when you can get to the user.

The following message appears: “You have express mail in your inbox.” This message meansthat an update terminate has occurred on the user’s transaction. Users should be trained tostop when they get this message.

The longer you wait afterthe update terminate hasoccurred, the more

difficult it is for users to rememberwhat they did when the updateterminate occurred. Also, promptaction should be taken to preventhaving multiple update terminatesthat must be addressed.

Tips & Tricks


2. On the Update Records: Main Menu screen:

a. In Client, enter *.

b. In User, enter *.

c. Under Status, select All.

d. In From date, change the date to a year ago (for example, 07/13/2000).

e. Choose .

3. In the Status column, look for entries with an Err. These entries are failedupdates or update terminates. You may also see other entries listed withoutthe Err status. If you have no failed updates, stop here. If you have failedupdates, continue with the next section, Managing Update Terminates.


Managing Update Terminates

Some of the problems that can occur with an update terminate include:

� No short dumpIn this case, the only clues you have are the:

• User ID

• Date

• Time

• Transaction

� Difficulty reading the short dumpShort dumps can be difficult to read or understand. Some of the content isonly useful to the developer. You may recognize a pattern of characters asa part number, document number, vendor code, and so on.

� Short dump with little usable information

� Update terminate occurring “downstream” from the actual transactionThe data in the short dump may be of little value in finding the root of theupdate terminate. (For example, if the terminate occurred in the FI postingof an SD transaction, you will not know which SD transaction documentcaused the problem.)

� Update terminate occurring in a batch jobThere is no indication of which batch job (by job name) caused the updateterminate. SAP is aware of the inability to identify the batch job which wasthe source of an update terminate.

Task

Manage update terminates

1. Double-click on an entry with an Err status.

2. The Update Modules screen shows the module (Mod.name) and the process(Mod.ID) where the update terminate occurred.


3. Double-click on the entry with an Err status.

4. Choose ABAP short dump. If a short dump exists, it will appear.


5. After choosing ABAP short dump, you will see one of the following screens:

a. If you have an ABAP dump, you will see the ABAP runtime errors screen.

b. If a short dump does not exist, you will see:

� The Update Status dialog box

� The message No ABAP/4 short dump exists which appears either in theinactive Update Modules window or a separate dialog box.

6. The users must be contacted.

7. The users should check for the missing entry and reprocess the missingtransaction.

User Training

When a user receives the following message, “You have express mail in yourinbox,” this usually signals a problem. The user should immediately stop andget assistance to determine what happened. SAP R/3 uses express mail tonotify the user of a failed update. It is during this time frame (immediatelyafter the error has occurred) that the user has the best chance of correcting theproblem.

Do not attempt to reapplythe failed update! Thereare conditions under

which this reapplication can leadto corruption of the database.Always advise users to reenterthe transaction.


System Log (Transaction SM21)

The system log is the SAP R/3 system’s log of events, errors, problems, andother system messages. The log is important because unexpected or unknownwarnings and errors could indicate a serious problem. You should check thesystem log several times a day.

The ability to properly monitor the system log comes with experience. Overtime, you will become familiar with what log entries normally appear in yoursystem log, and recognize the unusual ones that need investigation.

Task

View system log

1. In the Command field, enter transaction SM21 and choose Enter(or from the SAP standard menu, choose Tools → Administration → Monitor →SM21-System Log).

2. In From date, change the date to a week ago (for example, 07/09/2001 andchoose Reread system log.)

3. If you select Problems only, you will see this screen.


4. You can get more information on certain entries. In this example, double-clickon the short dump.

5. If you select All messages, you will see this screen. Notice that the warningmessages on this screen (indicated by the yellow highlight under the columnMNo, and the text Perform rollback) did not appear in the previous screen.

What to look for:

�Unusual entriesBefore you can

recognize the unusualentries, you must becomefamiliar with normal entries.

� Column MNo for the errorstatusErrors are in red and pink,and warnings are in yellow.These entries may havebeen examined when youdid the Alert Monitor(RZ20).


6. Choose Analyze runtime errors.

7. This screen is the short dump. You can access this screen using transactionST22.

Task

Display remote system logs

1. From the menu bar, choose System log → Choose → All remote system logs.

To minimize the video-processing overhead,many NT servers are

configured with a video colordepth of 16 colors. On theseservers, increase the video colordepth to 256 colors to see thealerts in color, or view the log froma computer that has the video setto at least a color depth of 256colors.


2. Choose Reread system log.

3. The system logs for all remote systems are shown.

Locks (Transaction SM12)

A lock prevents other users from changing the record on which you areworking. The example below illustrates the importance of using this function.

Example

You are changing a customer mailing address, while someone is simultaneously changing thecustomer’s telephone number. You first save your change; then the other person saves his orher change. The other person’s change overwrites your change, and your change will be lost.


There may be old locks still in place from transactions that did not release, orfrom when the user was cut off from the network. Unless cleared, these locksprevent access or change to the record until the system is cycled. The easiestway to locate these locks is to look for locks from prior days.

Task

View locks

1. In the Command field, enter transaction SM12 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → SM12 - LockEntries).

2. In Client, enter *.

3. In User name, enter *.

4. Choose .

5. In the Time column, look for locks from previous days. The presence of a lockfrom a previous day could mean that the user was disconnected from thenetwork and the SAP R/3 system.

We assume that theprofile parameterrdisp/gui_auto_logouthas

been set. This parameter definesan automatic logout of the user ifthere is no activity for a setnumber of minutes.

Setting the auto_logoutparameter isrecommended for

security and auditing. Theparameter is a global setting thatapplies to all users on theinstance. You cannot havedifferent logout times for differentgroups of users on the sameinstance.

The only way to have differentlogout times for different groups ofusers is to have specific groups(for example, Finance) log in tospecific instances (for example,the Finance application server)where this parameter is set in theinstance profile of that instance.


The following process should be followed before deleting a lock:

6. Once you know that there is no activity using the user’s ID:

a. Select the lock entry for deletion.

b. From the menu bar, choose Lock entries→ Delete.

Task Transaction Code that Completes this Task

Is the user logged onto any of the servers? Transaction SM04 (without applicationservers)Transaction AL08 (with application servers)If the user is not on the system, buttransaction SM04 shows them on thesystem, delete their sessions as described inchapter 9, Deleting a User’s Session. Thisstep, alone, may clear the lock.

Are there are processes running under theuser ID?

Transaction SM50Transaction SM51Also see the Processes section later in thischapter.

Are there batch jobs running under the userID?

Transaction SM37Also see the Background Jobs section in thischapter.

Are there updates in process for that userID?

Transaction SM13Also see Failed Updates section in thischapter.

Deleting a lock is adangerous task.

Do not delete a lockwithout checking first to see if it isbeing used. If you delete a lockthat is in use, you risk corruptingthe database.

Double-check the user ID of the entry that you selected to delete. If you delete the wrong lock,you could corrupt the database.

Clear only one lock entry at a time.

Do not use the mass delete option. This option will delete all the locks, not just the ones forthe user you have selected.

Caution


Active Users (Transactions SM04 and AL08)

These transactions display all the users who are currently logged on to thesystem, displaying both the user ID and terminal name.

In a smaller company, the administrator can recognize user IDs logged on tounfamiliar terminals. An unfamiliar terminal may indicate that someoneother than the designated user is using that user ID.

A user logged on to more than one terminal may indicate that the ID is beingused:

� Used by someone else

� Used/shared by several people

Problems

Transaction SM04 may show a user as active, when the user has actuallylogged off. Because the user session was not properly closed, the system“thinks” that the user is still logged on.

This condition can be caused by one of the following:

� A network failure, which cuts off the user.

� Users who turn off their computer without logging off from the SAP R/3system.

Task

View active users in a single-instance system

1. In the Command field, enter transaction SM04 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → Systemmonitoring → SM04 - User Overview).

2. Select the user ID (for example, DAVIDM) to view the session the user hasopened.

Reasons not to share user IDs include:

� If a problem arises, you will not know who created the problem.This situation makes the problem difficult for you to fix and prevent from happeningagain.

� Prudent security practices do not allow for the sharing of user IDs.

� Your external auditors may also perform this test to test your security.

Tips & Tricks

Release 4.6 allows you toprevent concurrentsharing of user IDs by

activating thedisable_mult_gui_login systemprofile. We recommend that youactivate this parameter.

If you have severalinstances in your system,using AL08 is easier,

because you can simultaneouslysee all users in all instances onthe system.


3. Choose Sessions.

4. The Overview of Sessions screen shows what sessions the user has opened.

5. Choose .

Task

View active users in a multi-instance system

1. In the Command field, enter transaction AL08 and choose Enter (or from theSAP standard menu, choose Tools → CCMS → Control/Monitoring, double-clickon SM66-Work Process Overview, then from the menu bar, choose Goto →Global users overview.)

2. The Current Active Users screen shows all the instances in your system.


3. For each instance, a list of the users logged onto that instance (applicationserver) is also provided.

Work Processes (Transactions SM50 and SM51)

Process overview transactions allow users to view the status of workprocesses and monitor for problems. Transaction SM51 is a central transactionfrom which you can select the instance to monitor. SM51 starts transactionSM50 for each application server. Transaction SM50 is used for a systemwithout application servers.

Transaction SM51 is one place to look for jobs or programs that may be hung,usually indicated by long run times. If batch jobs are not running, transactionSM50 may provide a hint of the problem, if all the batch work processes are inuse.

Task

View work processes for a system with application servers

1. In the Command field, enter transaction SM51 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → Systemmonitoring →SM51-Servers).

2. Select the instance you want to view (for example, pa102058_SA1_00).


3. Choose .

4. The Process Overview transaction (SM50) for that instance is displayed.

Task

View work processes for a system without application servers

1. In the Command field, enter transaction SM50 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → Systemmonitoring → SM50-Process overview).

2. Look for:

a. Dialog work processes (DIA) that have long Time values. These valuescould indicate a problem or a long running step in batch programs, whichsometimes start dialog work processes.

b. In the Status column, work processes that say stopped, can sometimes be aproblem because a process may have stalled or failed.


c. Some of the columns are defined in the table below.

ABAP Dump Analysis (Transaction ST22)

An ABAP dump (also known as a short dump) is generated when a report ortransaction terminates as the result of a serious error. The system records theerror in the system log (transaction SM21) and writes a snapshot (dump) ofthe program termination to a special table. This transaction can also be calledfrom the system log (transaction SM21).

An ABAP dump is used to analyze and determine why the error occurred andenables you to take corrective action.

Column Text Definitions

No Work process number

Ty Type of work process

PID OS PID (Process ID) number

Status Current status of the work process

Err Number of detected errors in the work process

CPU Cumulative CPU time that the current process is taking

Time Cumulative “wall” time that the current process is taking

Program Name of the ABAP program

Clie Client number

User User ID that is using the work process

Table Table that the action is being performed on


Task

View ABAP dump analysis

1. In the Command field, enter transaction ST22 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → ST22-Dumpanalysis).

The list of dumps can be displayed using two selection methods:

� For a simple selection, Today or Yesterday (proceed to step 2)

� For a free selection (proceed to step 5)

For a simple selection

2. Under No. of short dumps, if you see a value other than zero (0) in Today orYesterday, dumps have occurred that must be examined.

3. Select Today.

4. Choose . Proceed to step 8.

For a free selection

5. Choose Selection.

6. Enter your selection criteria in the ABAP Dump Analysis screen.


7. Choose .

8. Double-click on the dump you want to analyze.

9. The short dump is displayed.

Despite being called ashort dump, ABAPdumps may be more than

75 pages long. We recommendyou save the dump locally andprint out only the portion youneed.If the SAP hotline asks for a copyof the short dump, e-mail orupload the file (see SAP Note40024).


System Message (SM02)

A system message is a popup that users see when they first log on to the SAPR/3 system and move between screens.

System messages are useful to send a broadcast message to everyone on thesystem (for example, “SAP will be down for scheduled maintenance from 6:00 p.m.PST Friday, October 23 to 12:00 p.m. PST Saturday, October 24.”), or to informthe user about the system.

This information is recommended for systems other than the productionsystem, such as development, test, sandbox, training, and so on (for example,“You are logging into QAS, copy of PRD as of Nov-1-98 at 0100 PST”).

Task

Creating a system message

1. In the Command field, enter transaction SM02 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Administration → SM02-System messages).

2. Choose Create.

3. In System message text, enter your message.

4. Optionally, you may also enter text in the following fields:

a. In Server, choose and select the instance on which the message shouldappear.

b. In Client, enter the client number for a client specific message.

5. In Expiry on, enter the message’s expiration date and time.

To prevent the messagefrom expiring, enter adate several years in the

future. When referencing the timefor an event, always enter thespecific time, time zone, and date(for example, 0230 PDST-Tue–Jun 26,2001). Entering vagueinformation (such as in 15minutes), creates confusion asto when and where an event hasbeen scheduled.


6. Choose .

7. The message in the status bar indicates that your message has been saved.

8. The System Messages popup window will appear.

Task

Edit a message

1. In the Command field, enter transaction SM02 and choose Enter(or from the SAP standard menu, choose Tools → Administration →Administration → SM02-System messages).


2. Select the message.

a. Choose Change to edit.

b. Choose Delete to delete the message from the screen.

3. Enter your changes.

4. If necessary, change the following:

a. ServerName

b. Client

c. Expiry on

5. Choose .

6. The message in the status bar indicates that your message has been changed.


7. Review the changed message.

ABAP Editor (SE38)

An SAP R/3 system administrator must execute certain reports and programsto apply a note or in relation to everyday duties and tasks.

Task

Display profile parameters

1. In the Command field, enter transaction SE38 and choose Enter (or from theSAP standard menu, choose Tools→ ABAP workbench → Development → SE38-ABAP Editor).

2. In Program, enter the report or program name (for example, RSPARAM).

3. Choose .

4. This program has a variant screen where you can indicate whether you wantparameters that cannot be substituted to also be listed.

Be careful whenexecuting reports andprograms because it may

affect and change your system.Make sure you are executing thecorrect program, and you knowwhat the program is going to do.


5. Choose .

6. The report runs.

7. In this case, the report displays the profile parameters.

8. Choose .

Task

Display information about a program or report

1. In Program, enter the program/report name, (for example, RSPO0041.)

2. Select Documentation.


3. Choose Display.

4. The screen displays information about the program RSPO0041.

P A R T F O U R

CSecurity Overview


Part Overview

This security section is just a small part of the general subject of security. Security iscomprised of many components and subjects, enough to more than fill a bookshelf. Wehave chosen to select but a small portion of the subject that is appropriate for thisguidebook.

Other security subjects are of particular interest to a mySAP.com installation that are notincluded in this guidebook, such as Single Sign On, Central User Administration andNetwork Security. The first two, being SAP products, are mentioned briefly below.

Central User Administration (CUA)

Before 4.5A, maintenance of individual users had to be done in every system. As of 4.5A,users can be created and maintained in one single central system and then distributed todifferent client systems. This ensures consistent users in all systems and makes the taskof administrating multiple systems much easier. For more information, please go toservice.sap.com/security or refer to SAP Note 159885.

Single Sign-On (SSO)

Users often need to access a variety of services and information within an intranet portal,meaning that a user would need to access different systems (SAP or others) with differentuser management policies. SSO can provide an environment for users to move aroundwithin the portal without having to repeatedly enter their user information forauthentication, even as they access different systems. For more information, please go toservice.sap.com/security or refer to SAP Note 318515.

For additional information related to SAP security, please go to the CCMS-Security webpage at service.sap.com/security. Of special interest is the SAP security guide, in threevolumes.

C H A P T E R

7

7Security Administration


Overview

The purpose of this chapter is to make you aware of your securityresponsibilities as the SAP R/3 system administrator. These responsibilitiesinclude protecting the SAP R/3 system and preparing for a computer securityaudit.

When an audit is performed on an SAP R/3 system, the administrators areresponsible for responding to the audit findings. This chapter prepares youfor these audits. However, each auditing firm has its own audit proceduresand may look at many different items. Therefore, the information in thischapter tries to prepare you for the core group of items that all firms usuallyaddress. For more information, see www.service.sap.com/security.

What Is Security?

Security is more than the SAP R/3 authorization (or keeping undesirables outof the system). Security is concerned with the following issues regarding data:

� Protecting data from hardware problems

� Maintaining data integrity

� Restoring data in the event of a disaster

Some security topics covered in this chapter include:

� Keeping unauthorized people out of the system

� Keeping people out of places that they should not be

� Safeguarding the data from damage or loss

� Complying with legal, regulatory, and other requirements

Keeping Unauthorized People Out of the System

This area is what we usually think about as security and includes the SAP R/3authorization concept, operating system and network logon security, andphysical security.

This chapter is only an introduction to computer security and its importance. Although an entirebook can be written on this subject, even that would be insufficient. We recommend youcontact and work with all parties (external auditors, internal auditors, finance department, legaldepartment, and others) who might be affected by system security.

Caution


Keeping Users out of Prohibited System Areas

This area covers users having access to more parts of the system and to moredata than they need to perform their job. The data may not be damaged butaccessing and revealing this data could be equally damaging.

Examples of this sensitive data include:

� Your company’s customer list, contacts, and sales volume. A competitorcould use this information.

� Your employees’ personnel data. Privacy laws protect this type of data.

� Financial performance data, such as quarterly financial statements. StrictSEC rules govern insider trading (see “Complying with Legal, Regulatory,and Other Requirements” on page 165 for a definition of insider trading).

� Items specified in contracts with customers, vendors, or other parties.

Safeguarding the Data from Damage or Loss

There are two major sources of damage:

� Accidental, such as:

• Loading test data into the production system

• A hardware failure

• A fire that destroys the data center

• A flood, hurricane, earthquake, tornado, or other regional naturaldisasters

� Deliberate, such as:

• A disgruntled employee who deletes or damages files from thesystem

• A hacker who deletes or damages files from the system

Complying with Legal, Regulatory, and Other Requirements

Laws, contracts and other parties define other reasons for security.

Security is a sensitive issue with legal implications. A good example of asecurity issue is insider trading. Before defining insider trading, we have tofirst define insider knowledge or inside information. Insider knowledge orinside information means you have information that is not known oravailable to the general public. If the general public knows the information, itcould affect the stock price. Insider trading is using inside information to buy


or sell stock and make a profit or reduce a loss. Even if you yourself do notprofit from the sale, you could be held liable. In cases involving insidertraining, consult your legal department.

Audits

As a system administrator, two audits affect you:

� Financial audit

� Security audit

Financial Audit

A financial audit is a review of your company’s financial statements by aCertified Public Accountant (CPA) in the U.S., or the equivalent in othercountries. The purpose of the audit is to issue an opinion on the company’sfinancial statements. This opinion essentially states that the financialstatement fairly represents the financial position of the company. A financialaudit is usually not optional. If your company’s stock is traded on the stockmarket, the Securities and Exchange Commission (SEC) in the U.S., or itsequivalent in other countries requires the audit. If your company is private,creditors could require a financial audit.

Example

In one company, an employee’s spouse passed on inside information to a relative, whopurchased the stock, then sold the stock at a profit after the earnings announcement. Thatrelative made a profit by buying the stock before the earnings announcement (insider trading).The SEC fined the spouse and the relative. The spouse was guilty of providing insiderinformation to the relative, who then made the profit on the sale of the stock. Both, therefore,were guilty of insider trading.

Example

The IS director of a company asked for authorization to log into the production SAP R/3 system.This request raised the concern of the accounting/finance department. Access to financialinformation is typically on a “need-to-know” or “need-to-access” basis, and the IS director didnot need to access the production SAP R/3 system. Concerns were raised when he startedasking about financial performance information (quarterly earnings), well before this informationwas made public. He was asking for insider information.


As a part of the financial audit, the CPA typically does a security audit of SAPR/3 and any associated systems. The purpose of the security audit is todetermine how much reliance can be placed on the data in the SAP R/3system. Your external auditors evaluate your system security to determinewhat audit tests to perform and how much testing they must do.

If their evaluation results are not good, they may need to increase the scope oftheir audit. This increased scope also increases the cost of the audit, and theextra work could delay the completion of the audit. In a worst-case scenario,they could determine that the security is so weak they cannot issue an opinionon the company’s financial statements.

Because of the negative effect on the stock price that this inability to issue anopinion will probably cause, the chief financial officer (CFO), and likely thepresident, will be quite upset.

Security Audit

A security audit is performed specifically to test the security of the SAP R/3environment. This audit is usually done as a part of the financial audit or tocomply with government or other regulatory agencies. Your company’sinternal audit group can also perform a security audit.

The audit is done to test the security of confidential data, such as:

� Financial information

� Customer data

� Product information

� Company personnel data (from the HR module)

Audit Considerations

Audit considerations are what auditors will look at when they do a financialor computer security audit.

Some of these considerations are:

� Physical security

� Network security

� User administration procedures

• Adequate segregation of duties

• Proper training

• Passwords

� Data security

• Protection from hardware failure; mirrored drives, RAID, fail-over,High Availability (HA), and so on.


• Backup and recovery procedures

• Protecting the production system from unauthorized changes

• Locking dangerous transactions

These tasks support the financial or security audit. Without knowing what theauditors will look for, you cannot properly prepare yourself and protect thesystem.

Security Layers

To make security more manageable, we have chosen to use the security layermodel, one of many existing security models. This model uses the followingthree major layers of security:

Access Security

Physical Security

Physical security controls the physical access to SAP R/3 and networkequipment. Like the graphic on the previous page, to get to the inner circle, anintruder must penetrate onto the property or site, into the building, and intothe areas of the building where the users are or where the equipment islocated (such as Finance, MIS, or Computer Operations) or into the specificequipment rooms within these areas of the building (such as the server room,wiring closet, or network room).

This layer is probably the most important. If an intruder can physically accessyour equipment, all other security layers can be bypassed.

Note

This section is not an all-inclusive SAPsecurity audit. It is only to make youaware of some of the things that couldbe reviewed as part of a security audit.We recommend that you work with yourauditors before the financial audit, toreview your system and bring it up toacceptable standards for the audit.

Access security

� Physical security

� Network security

� Application security

Operational security

Data security


When physical security is bypassed:

� Equipment can be physically damaged or destroyed

� The system can be accessed from the operator’s console (perhaps allowingbypass of strong network security)

� Equipment can be removed

� Data could be hacked

Without physical access to the equipment, the intruder must electronicallyaccess the system through the network.

The SAP R/3 equipment should be located in a secured room. Access to theroom should be only through a locked door. It is crucial to control who isallowed access to the server room.

Network Security

Network security also has sub-layers of security. The goal of this security typeis to control external access and logon access to the network. Logon accesscontrols on-site and remote access and where on the network users can goonce they gain access.

If intruders access your network, they could have an electronic link to yourcomputers.

Use network security specialists to properly configure the various accesspoints into your network and, once users are on the network, control theirmovements.

Some of these points of control are:

� Outside access

• Dial-in access

• Internet access

• Other remote access methods, such as VPN

� Network login access

This access method is the actual logon to the network (for example, the NTdomain).

� Access to portions of the network.

• NT domains

• Router tables

This table can be used to control (by IP address) which users can access theSAP servers.

If you have electroniccard key access,periodically audit the

access log for the server room.The periodic review of the accesslog may be an item for whichauditors will test.

Note

For NT we recommend that you have:

� A dedicated SAP domain whereonly the administrators areallowed to directly log on

� Other domains where users willlog onto, trust the SAP domain,but the SAP domain does nottrust other domains


Application Security

Like the other layers, application security has sub-layers of security, whichcontrol:

� The ability to log into the application, such as logging into SAP R/3

� Where a user can go in the application

� What a user can do in the application

� What a user can do based on the system data in the application (such as theSAP R/3 system [for example, limiting the user to company 001 and costcenter 200)

� SAP R/3 security functions at this layer

This layer provides the fine or specific security of what a user can do (forexample, read [not change] accounting data for only cost center 200 incompany 001).

� Using SAP R/3 application tools such as:

• Profile Generator (transaction PFCG; for more information, see theAuthorizations Made Easy guidebook)

• Audit Information System (transaction SECR; see page AuditInformation System (Transaction SECR))

• Security Audit Log (transaction SM19/SM20; see page SecurityAudit Log (SM20))

• Delete Old Audit Logs (transaction SM18)

Operational Security

This layer is security at the operational or user level. Because it is primarilyprocedural and control-related, there are few computer or systems issuesrelated at this level.

These are organizational and people issues, which can be problematic,because people must comply with guidelines and rules. The problem is, ofcourse, that some people never want to comply with guidelines.

Some of the methods of operational control are:

� Division of duties

� Preventing sharing of user IDs

� Password standards

� Log off when away from the computer, such as during lunch or at the endof day


Data Security

This layer is closely tied to the material in chapter 2, because disaster recoveryis an integral part of data security. Data security protects:

� Data on the servers

We protect the data on the server from damage or loss. This protection isaccomplished in various ways. The goal is to prevent or minimize loss of datain a disaster.

� Backup data

The goal of this security layer is to preserve application data (usually on tape)so that the system can be recovered.

The backup tapes must be stored safely to:

• Preserve the backup tapes in the event of a disaster

• Protect the backup tapes from theft

� Disaster Recovery

For more information on disaster recovery, see chapter 2.

A proactive approach can prevent a problem. To remain proactive:

� Reduce the chances of losing data.

� The server is the first place to safeguard your data.

� Protect backup data from damage or loss.

� Ensure that, if there is a disaster, the system be completely recovered.

Secure data on the servers:

You must prevent or minimize data loss in a disaster. Some of theitems below can be referred to as High Availability (HA) items:

• RAID arrays for drives

• Redundant equipment

• Using reliable equipment and vendors

• Premium hardware support agreements for the production system

The following are facilities-related items:

• Uninterruptible Power Supplies (UPS)

• Fire detection and prevention devices

• Intrusion alert

• Environmental alerts

� Backups


• Backup tapes should be sent to a secure, off-site data storage facility.

This step protects the backup data from damage or destruction a disaster.

• Tapes at both the off-site backup and the on-site tape storage facilitiesmust be secured to prevent the theft of the backup tapes.

If the backup tapes are stolen, the data can be restored and hacked. Usingdatabase tools, most SAP R/3 security could be bypassed by directlyreading the tables.

Application or SAP R/3 Security

Controlling Access to SAP R/3

For more information, see “Password Issues and Tasks” on page 189.

Prevent Multiple User Logins

This process prevents users from logging onto the system multiple times.Multiple user logons is when several users are sharing a user ID, or someoneis using a user’s ID without the user’s knowledge. Preventing multiple userlogons is not allowing more than one SAP R/3 logon from one user ID.

If several people share a user ID:

� You do not know who created a problem.

� This situation is an audit security issue.

Set the disable multi-login parameter (login/disable_multi_gui_login) in thesystem profile. For more information, see “Sharing of User IDs” on page 188.

Preventing Changes in the Production System

The production system should be set to Not modifiable. The locks on thesystem should be set so that configuration changes (client-independent andclient-dependent) cannot be made directly into the production system. Thepurpose for this setting is to ensure that all changes are completed in acontrolled manner.

In the development pipeline, changes are:

� Made in the development system

� Tested in the development system

� Transported from the development system to the test system

� Tested in the test system

� Transported from the test system to the production system


This procedure ensures that changes are properly tested and applied to thesystems in the pipeline. (A pipeline is the environment where development ismoved from the development system to the quality assurance system, andfinally to the production system.)

Configuration changes should not be made directly into the productionsystem. This restriction maintains the integrity of the production system. Ifchanges are made directly into the production system, it may break becausethe change was not tested, or is not the same as the one made in thedevelopment system.

The production system should be protected from changes until the changesare properly tested to preserve the integrity of the pipeline. If changes aremade into the production system, the development and testing pipeline maybecome out of sync with the production system. If the pipeline is out of sync,it is difficult to develop and test with any certainty that things will not bedifferent in the production system.

All changes should be made in the development system and then transportedthrough the pipeline into production. In this way, all systems get the samechanges. A common excuse is that making changes directly into theproduction system takes too long to transport the fix.

By making changes directly into the production system, you create an out-of-sync landscape, where the change made to the production system do notmatch changes made to development or test systems. Additionally, you allowemergency transports to occur at any time, with coordination.

Exceptions. Infrequent exceptions occur when no mechanism is available totransport the changes, or an SAP Note requires the direct change.

When a change cannot be transported, the following procedure should beused:

� Verify that the change cannot be transported.

� Some objects may use an ABAP program to transport the object.

� Unlock the system (to make it modifiable).

� Make the change.

� Immediately re-lock the system.

� Make the same changes to all other systems.

Use this procedure only if a change cannot be transported.

Manual entry alwaysincreases the chance ofmaking an error.


Setting the Production System to “Not Modifiable”

(Transactions SE03, SCC4)

Switches can prevent changes from being made in the system. In theproduction system, these switches should be set to Not modifiable. Settingthese switches in the production system ensures that changes are made usingthe development pipeline. With this procedure, changes are properly testedand applied to the systems in the pipeline.

Objects should not be modifiable in the production system. This rule protectsthe production system from object and configuration changes before beingtested. By setting the production system to Not modifiable, before the integrityof the pipeline is preserved.

Two transactions (SE03 and SCC4) let you set the system to Not modifiable.These transactions can also be used for other tasks.

Task

Prevent client-independent changes (Transaction SE03)

1. In the Command field, enter transaction SE03 and choose Enter.

2. Select Set System Change Option.

3. Choose .


4. Under Global setting, select the dropdown:

a. To lock the system, select Not modifiable.

b. To unlock the system, select Modifiable (selected in this example).

c. Choose .

Task

Prevent client-independent and client-dependent changes (Transaction SCC4)

1. In the Command field, enter transaction SCC4 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Administration →Client administration → SCC4-Client maintenance).

Note

This method also locks the client-dependent changes.


2. Choose .

3. To continue, choose .

4. Select the client number (for example, 100).

5. Choose .

Task

Lock a client (not modifiable)

1. Under Changes and transports for client-dependent objects, select No changesallowed.


2. Under Client-independent object changes, choose the dropdown and select Nochanges to Repository and cross-client Customizing objs.

3. Under Protection: Client copier and comparison tool, choose the dropdown andselect Protection level 2: No overwriting, no external availability.

4. Choose .

Task

Unlock a client (modifiable)

1. Under Changes and transports for client-specific objects, select Automaticrecording of changes.

2. Under Client-independent object changes, choose the dropdown and selectChanges to Repository and cross-client Customizing allowed.

3. Under Protection: Client copier and comparison tool, choose the dropdown andselect Protection level 0: No restriction.


4. Choose .

Verifying that Dangerous Transactions Are Locked

Dangerous transactions can damage or corrupt the system, present a securityrisk, or adversely impact performance.

In a production system, access to dangerous transactions is a more criticalissue than in development or test systems. This criticality is because of livedata and the company’s operational dependency on the SAP R/3 system.

Certain transactions should be locked in the production system, but not in thedevelopment, test, or training systems. Standard security normally preventsaccess to these transactions, but some administrators, programmers,consultants, and functional key users could access them depending on whichsystem they access. In these cases, the transaction lock provides a second lineof defense.

The SAP R/3 system contains over 51,000 English transaction codes. Tomanage such a large number of transactions, lock only the critical ones. Yourfunctional consultants should notify you of any additional criticaltransactions in their modules.

The table below is organized with input from Basis consultants and users andlists transactions that we recommend you lock. The transactions arecategorized by the following risk categories:


� Dangerous

� Security-related

� Performance impact

Transaction Description Dangerous Security Performance

F040 Document Archiving X

F041 Bank Master DataArchiving

X

F042 G/L Accounts Archiving X

F043 Customer Archiving X

F044 Vendor Archiving X

F045 Document Archiving X

F046 Transaction FiguresArchiving

X

GCE2 Profiles: Initial screen X

GCE3 Maintain Authorizations:Object Classes

X

KA10 Archive Cost Centers(all)

X

KA12 Archive cost centers(plan)

X

KA16 Archive cost centers(line items)

X

KA18 Archive admin:completely cancelleddoc

X

KA20 Archive admin: costcenters (all)

X

O001 Maintain Users: InitialScreen

X

O002 Profiles: Initial Screen X

O016 Maintain Authorizations:Object Classes

X

OBR1 Reset Transaction Data(delete transaction data)

X

OBZ7 Maintain Users: InitialScreen

X

OBZ8 Profiles: Initial screen X


OBZ9 Maintain Authorizations:Object Classes

X

OD02 Maintain Authorizations:Object Classes

X

OD03 Profiles: Initial screen X

OD04 Maintain Users: InitialScreen

X

OIBA Maintain Authorizations:Object Classes

X

OIBB Maintain Users: InitialScreen

X

OIBP Profiles: Initial Screen X

OMDL Maintain Users: InitialScreen

X

OMDM Profiles: Initial Screen X

OMEH Maintain Users: InitialScreen

X

OMEI Profiles: Initial Screen X

OMG7 Maintain Authorizations:Object Classes

X

OMI6 Maintain Authorizations:Object Classes

X

OML0 Maintain Users: InitialScreen

X

OMM0 Profiles: Initial Screen X

OMNP Maintain Authorizations:Object Classes

X

OMSN Maintain Users: InitialScreen

X

OMSO Profiles: Initial Screen X

OMSZ Maintain Authorizations:Object Classes

X

OMWF Maintain Users: InitialScreen

X

OMWG Profiles: Initial Screen X

OMWK Maintain Authorizations:Object Classes

X

OOPR Profiles: Initial Screen X



OOSB Change View "UserAuthorizations":Overview

X

OOSP Change View"Authorization Profiles":Overview

X

OOUS Maintain Users: InitialScreen

X

OP15 Profiles: Initial Screen X

OP29 Maintain Users: InitialScreen

X

OPCA Maintain Users: InitialScreen

X

OPCB Profiles: Initial Screen X

OPCC Maintain Authorizations:Object Classes

X

OPE9 Profiles: Initial Screen X

OPF0 Maintain Users: InitialScreen

X

OPF1 Maintain Authorizations:Object Classes

X

OPJ0 Maintain Users: InitialScreen

X

OPJ1 Profiles: Initial Screen X

OPJ3 Maintain Authorizations:Object Classes

X

OSSZ Maintain Authorizations:Object Classes

X

OTZ1 Maintain Users: InitialScreen

X

OTZ2 Profiles: Initial Screen X

OTZ3 Maintain Authorizations:Object Classes

X

OVZ5 Maintain Users: InitialScreen

X

OVZ6 Profiles: Initial Screen X

OY20 Maintain Authorizations:Object Classes

X

OY21 Profiles: Initial Screen X



OY22 Maintain Users: InitialScreen

X


X


X


X


X

SARA Archive Management:Initial Screen

X

SCC5 Client delete X

SE01 Transport Organizer

SE06 Post-InstallationMethods for TransportOrganizer

X X

SE09 Transport Organizer(Workbench)

SE10 Transport Organizer(Customizing)

SE11 Data Dictionarymaintenance

X

SE13 Dictionary: TechnicalSettings

X

SE14 Utilities for dictionarytables

X

SE15 Data DictionaryInformation System

SE16 Data Browser X

SE17 General Table display X

SE38 ABAP workbench X

SM49 External OS commands X X

SM59 Maintain RFCdestinations

SM69 External OS commands X X

ST05 SQL trace X

SU12 Delete All Users X X



The following table shows dangerous transactions that probably cannot belocked because they may be used regularly. These transactions may haveother valid reasons for use in a production system. However, because of thepotential danger, these transactions should have restricted access.

Create and maintain a list of the following information:

� Which transactions were locked?

� Why are they locked?

� Who locked them?

� When were they locked?

Task

Lock a transaction

1. In the Command field, enter transaction SM01 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Administration →SM01 Transaction Code Administration).

2. Enter the transaction code you want to lock (for example, SE14) in the searchfield at the bottom of the TCode column.

Table TSTCT containsthe transaction codes andthe name of the

transaction. The current content isover 98,000 entries in the table(for an English installation), withover 51,000 in English.


RZ10 Edit System Profiles X

SA38 ABAP Workbench X

SM04 User Overview X

SM12 System Locks X

SM13 Update Terminates X

SM30 Table Maintenance X

SM31 Table Maintenance X

STMS Transport ManagementSystem

X

SU01 User Maintenance X

SU02 Profiles: Initial Screen X

SU03 Maintain Authorizations:Object Classes

X

Maintaining the above-mentioned information isimportant, because

someone will invariably want toknow who locked the transactionand why it was locked.


3. Choose .

4. In the Locked column:

a. To lock a transaction, select the checkbox to the left of the transaction.

b. To unlock a transaction, deselect the checkbox to the left of thetransaction.

5. Choose .

6. Choose .

Task

List locked transactions

1. In the Command field, enter transaction SECR and choose Enter.

2. Select Complete audit.

Check which transactionsyou are locking. Youcould accidentally lock

yourself out of a key transaction,which would prevent you fromunlocking this or othertransactions.

Building securityauthorizations on thesecurity object

S_TCODE under Cross-application authorization objectscan also control access totransactions.


3. Choose .

4. Expand the following menu path: Audit Information System (AIS) → SystemAudit → Development / Customizing → Transactions → Blocked Transactions.

5. Choose next to Blocked Transactions.

6. Verify that the following are selected:

� Locked

� Transactions

� Menu transactions

� Parameter transactions

� Report transactions


7. Choose .

8. This screen shows the list of locked transactions.

Operational Security

This section describes selected operational security issues.

Segregation of Duties

Standard audit guidelines cover job or task combinations that are consideredrisky or that reduce internal controls. Some of these combinations are:

� Accounts Payable and Check Generation

� Accounts Receivable and Cash Receipts

� ABAP development and transport control

Your external auditorsshould help you definethese risky combinations.

Testing for segregation of duties isa standard audit procedure.


Accounts Receivable and Cash Collection

The person who collects and handles cash should not be the same person whokeeps records of what the customer owes. In this combination, the cashreceived from the customer could be pocketed and the amount written off thecustomer’s account.

The review of segregation of duties should be completed with the varioususer owners (key users of each functional area).

Restricting Access to SAP* or DDIC

SAP* and DDIC are system user IDs that have restricted uses for specificpurposes.

Certain functions can only be performed by SAP* or DDIC. If an SAP R/3user requires similar functionality, they should have a copy of the SAP*profile. These users should be grouped as power users, with the appropriatesecurity approvals.

Log on using SAP* and DDIC to determine if someone has changed thepassword.

Periodically change the password for these users in all systems and theirclients. This step prevents a person who knows the password from accessingthe system.

Update the secured password list.

Verify that the system profile parameter login/no_automatic_user_sapstar hasbeen configured, to prevent the use of the automatic user sap*.

If the user ID has been deleted, this step prevents the backdoor usage of usersap*.

Out of necessity, smaller companies must assign multiple functions to a single person. Beaware of the potential security risks in this situation. If you must combine functions, combinethem in a way that minimizes risk.Caution

A user with user administration rights cannot change the password to gain access to a user IDand then change it back to the original password. Passwords are not visible to theadministrators, so they cannot restore the original password if they do not know it. At the nextlogon, the owner of the user ID will know that the password has been altered because they willbe unable to log on with their current password.

The security profile forSAP* is SAP_ALL. Thisprofile is extremely

powerful because it grants theuser complete access to thesystem. For more information, seechapter 8, “User Administration”on page 220.

Tips & Tricks


Change Management

Change management is the process of controlling what changes are made tothe system. In this context, system refers to the entire system environment,not just SAP R/3.

One aspect of security is to control and know what changes are made to thesystem. Items of concern include:

� Is there a change management procedure for changes being made to theSAP R/3 system?

� Is a QA testing process in place?

� Are reviews and approvals required to move changes into the productionsystem?

Sharing of User IDs

This process occurs when more than one person uses a single user ID. Thisissue is a security concern because:

� There is no way to tell who is doing the activity.

� If there is a training problem, you do not know who needs training.

� If there is a deliberate security breach, there is no way to track theresponsible party.

Other. Despite the cautionary statements above, there are a few situationswhere it is not practical to have individual user IDs. These situations must betreated individually and with management and internal audits review andapproval.

To prevent a user ID from being shared, the system profile parameter(login/disable_multi_gui_login) can (and should) be set.

Parameter values are:

� 1 (to block multiple logins)

� 0 (to allow multiple logins)

We recommend that this value be set to 1 to prevent multiple logins under thesame user ID.

Example

In a warehouse, several employees use one computer to post their warehouse transactionssuch as goods issued, goods received, and so on. This process occurs because the user ID isused to log on, not at the individual transaction level, but to the SAP R/3 system. For eachtransaction that the warehouse employees access, it is impractical to log on to SAP R/3individually, access the transaction, and then log off from SAP R/3. The alternative is to have acomputer for each warehouse person, although this step may not be cost-effective.


To allow specific users to log on multiple times, you can enter their user IDsin the parameter login/multi_login_users separated by commas and no spaces.

Password Issues and Tasks

The password is the user’s key to accessing SAP R/3. Like the key to yourhouse, safeguarding this key is important to keep undesirables out. Yourcompany should have a clear and practical company password policy thatshould be distributed to all users informing them not to use easy-to-guesspasswords.

Setting Password Standards Using Transaction RZ10

Security parameters exist for the user’s password (for example, the minimumpassword length, the time interval that the user must change their password,and so on.)

The following is a list of the most important password parameters:

� Minimum password length: login/min_password_lngA longer password is more difficult to break or guess, so the standard isusually five characters.

� Password expiration time: login/password_expiration_timeThis time period is the limit before users must change their password.Auditors usually recommend 30 days. A practical number that customersuse is 90 days.

� Password lockout: login/fails_to_user_lockThis parameter locks out users who, after a specified number of times, tryto logon with an incorrect password. Users are usually locked out afterthree failed attempts.

Properly assigned parameters will make it more difficult to break into thesystem.

To set up password parameters, maintain system profiles with transactionRZ10 (for more information on this transaction, see “Changing System ProfileParameters (Transaction RZ10)” on page 608.)

Eliminating Some Easy Passwords

Certain passwords (for example, 123, QWERTY, abc, sap, <your companyname>) are well known or easy to guess. You can prevent these passwordsfrom being used by loading them into a table (USR40) that the system checkswhen the user attempts to save a new password.

A password policy that istoo restrictive or difficult tocomply with could defeat

the purpose of this policy. Userswill write their passwords downand leave it in an easily seenplace, which means you have lostyour security.

Your external auditorsmay check to see if youhave set the security

parameters.

Table USR40 is only abasic level of passwordsecurity and is maintained

manually. There are third-partypassword security programs thatcan be integrated into SAP R/3.


A password is the key to enter the system, similar to the key you use to enteryour home. If users choose easy-to-guess or well-known passwords, securityis compromised and your system is potentially at risk.

Maintaining a Table of Prohibited Passwords

A table of prohibited passwords is a user-defined list of passwords that areprohibited from being used in the SAP R/3 system. This table is not asubstitute for good password policies and practices by the users. Interactionoccurs between a system profile parameter and the table of prohibitedpasswords.

If the minimum password length is set to five characters, there is no reason toprohibit passwords like “123” or “SAP,” because these passwords would failthe minimum length test. However, if company security policy requires it,you could include all passwords that are considered “risky” in the table.

The following is a list of easily guessed passwords that cannot be put into anytable:

� Your name

� Your spouse’s name

� Your child’s name

� Your pet’s name

� Your car’s license plate

� Your driver’s license number

� Your social security number

There are many lists circulating of commonly used user passwords. If one ofthese passwords is used, the chances of an unauthorized person accessing auser’s account increases.

Changes are made to table USR40 using transaction SM31, the general tablemaintenance transaction. (For more information on this transaction, see“Table Maintenance (Transaction SM31)” on page 466.). This change creates atransport that can then be transported throughout the landscape.

A few suggestions for table entries are:

� SAP

� GOD

� ABC

� QWERTY

Your external auditors may check to see if you have a mechanism to secure against users witheasy-to-guess passwords.

Tips & Tricks

Keep a log of changesmade to this table in yoursecurity log.


� XYZ

� PASSWORD

� 123

� 12345*

� 54321*

� *12345*

Other table entries include:

� Days of the week

� (Monday*, Tuesday*, Mon*, Tue*, and so on)

� Months of the year

� (January*, February*, Jan*, Feb*, and so on)

� Your company name

� Your product names

� Competitors names

� Competitors products names

Recording System Passwords

We recommend that you never write down passwords, except for the:

� Critical nature of the SAP R/3 system.

� Many systems, clients, and all the other areas where passwords arerequired.

� Need to access the system if the SAP system administrator(s) is notavailable.

Recommended Process. All passwords for all system IDs should be:

• Recorded

• Placed in a sealed envelope

• Put in a company safe (possibly both an onsite and offsite safe) withrestricted access. Only a select list of company personnel should haveaccess to this information.

� User IDs that are used or needed to maintain the SAP R/3 system include:

• SAP*

• DDIC

• SAPCPIC (see note 29276)

• EarlyWatch (client 066)

Two people shouldprepare the list, changethe password, and verify

the new password—one user IDat a time. If the recordedpassword is wrong, those “keys”are lost, and you may not be ableto log on to the system.


• All user-created administrative IDs

• Any other non-SAP user ID that is required to operate the system,such as for the operating system, the database, and other relatedapplications.

� The password list should be updated and replaced whenever passwordsare changed.

Following are sample password tables:

All systems should haveentries for clients 000and 001. In addition, the

production system should have anentry for client 066. Clients 000and 001 are default clients in allsystems, and client 066 is theEarlyWatch client and may notexist in every system.

Server SID Client User ID Password

SAPR3T TST 000 SAP* Newpass

DDIC Newpass

<SID>ADM Newpass

SAPCPIC Newpass

001 SAP* Newpass

DDIC Newpass

<SID>ADM Newpass

SAPCPIC Newpass

066 SAP* Newpass

<SID>ADM Newpass

EarlyWatch Newpass

100 SAP* Newpass

DDIC Newpass

BATCH1 Newpass

<SID>ADM Newpass

SAPCPIC Newpass

Where User ID Password

NT Finance/DEVADM Newpass

Finance/PRDADM Newpass

SQLserver sa Newpass

sapr3 Newpass

UNIX root Newpass

<SID>ADM Newpass

Oracle system Newpass

SYS Newpass


Task

Change the password for a user ID:

1. In each instance and each client, log on under the user ID to change thepassword.

2. In Client, enter the client number (for example, 100).

3. In User, enter the user ID you want to change (for example, sap*).

4. In Password, enter the current password.

5. Choose New password.

6. Enter the new password twice in the popup window.

7. Choose . At this point, the logon will proceed as normal.

8. Record the new password in the password table.

9. Log on using the new password to verify it.

OPS$<SID>ADM Newpass

OPS$SAPSERVICE<SID> Newpass

SAPR3 Newpass

Where User ID Password

Be careful when youenter the new password.It is easy to enter the

password incorrectly or to makethe same error twice (for example,user versus users and theversus teh).

At this point, if the newpassword fails, useanother administrative

user ID to reset the password.This reason is why passwordchanges should be made oneuser ID at a time.


This process must be repeated for every system and client in which the userID has an entry. With Central User Management, you can manage users acrossall systems (for more information, see Authorizations Made Easy, Release 4.6).

Operating System Level

At the operating system level, the following user IDs should have theirpasswords changed:

NT

NT is case-sensitive when dealing with passwords.

User IDs.

� <SID>ADM

� SAPService<SID>

Services.

� SAP

These services will either use user ID <SID>ADM or SAPService<SID>

• SAP<SID>_<instance>

• SAPOsCol

• SAProuter

� Oracle

• OracleService<sid>

• OracleTNSListener80

The default user that the Oracle services runs under is system.

� SQLserver

• MSSQLServer

• SQLServerAgent

The user ID that they run under is either <SID>ADM orSAPService<SID>

� Informix

• INFORMIX-OnLineDynamicServer

• INFORMIX-OnLineMessageService

� DB2

• DB2-DB2DA400


UNIX

User IDs.

� <sid>adm

� root

Services.

� ora<sid>

Databases

For the databases, the following user IDs should have their passwordschanged:

DB2

NT/DB2 (see SAP Note 80292)

Informix

See note 15399.


� See SAP Note 28893

� sa

� sapr3

Oracle/UNIX

User IDs:

� SAPR3

� SYS

� SYSTEM

Useful SAP Notes for Oracle/UNIX

SAP Note # Description (Release)

117736 4.5A

101318 4.0B

086857 4.0A


Use the program chdbpass to change the passwords. This programautomatically updates the SAPUSER table and enables the user <sapsid>admto access the database.

Oracle/NT

� system

� sys

� op$<sid>adm

� ops$sapservice<sid>

� sapr3

Audit Tools

Audit Information System (Transaction SECR)

The Audit Information System (AIS) is designed for system and businessaudits. Auditors will likely request to run AIS. AIS collects many of the SAPR/3 security tools, centering around the Audit report tree. AIS is a standardcomponent in Release 4.6A, and uses standard SAP R/3 reports andtransactions to conduct the review. However, AIS can be imported into earliersystems, starting with Release 3.0D or higher. AIS also provides an interfaceto export data to an external auditing system that analyzes financialstatements.

Auditors examine the results of automated and manual financial and systemprocedures to ensure that checks and balances exist to prevent fraud. AISenables the auditors to test transactions and run reports during theinspection.

Audits can be conducted in either a complete or user-defined manner.

Task

Perform a complete audit

1. In the Command field, enter transaction SECR and choose Enter (or from theSAP standard menu, choose Information Systems → SECR-Audit Info System).

2. Select Complete audit.


3. Choose .

A complete audit consists of a system audit and business audit. The structureon this screen is Audit_All with a standard view.

4. Click the node (+) to expand the following:

� System Audit

� Business Audit


Task

Perform a system audit

The following example shows how to use the AIS.

1. Under System Audit, click the node (+) next to Repository / Tables.

2. Click the node (+) next to Table Information.

3. Choose next to Data Dictionary display.

4. When the transaction executes, the ABAP Dictionary: Initial Screen appears.


5. Choose .

Task

Perform a business audit

1. Under Business Audit, select the node (+) next to Financial Statement OrientedAudit.

2. Select the node (+) next to Closing (FI-GL).

3. Select the node (+) next to Balance Sheet/ P&L/ Balances.

4. Select the node (+) next to Balance Sheet/ P&L. You can execute differentreports to inspect the financial balances.

5. Choose next to Profit and Loss Projection.

6. On this screen, you can enter criteria for your report then choose .


7. Choose .

Task

Perform a user-defined audit

You can also conduct a user-defined audit by creating a view or subset of acomplete audit.

1. In the Command field, enter transaction SECR and choose Enter(or from the SAP standard menu, choose Information Systems → SECR-Audit InfoSystem)

2. Select User-defined audit.

3. Under User-defined audit, enter a view name (for example, ZVUE).

4. Choose .

View names must startwith “Y” or “Z.”


5. In Name, under New view, enter the name of the view (for example, ZVUE).

6. Under Select using:, select Manual selection. You will select the procedures thatwill be included in the view.

7. Choose . We want to include all the procedures for a system audit in thisview.

8. Select System Audit.

9. Choose .

10. Choose .

11. The message in the status bar indicates that the generation was successful.


12. Choose .

13. Choose Display to check the view of this structure.


14. Select the System Audit node (+) to expand it.

15. The following screenshot lists all the procedures for the Audit_All structurewith a ZVUE view.

Security Audit Log (SM20)

The Security Audit Log records the security-related activities of users in thesystem. These activities include successful and failed:

� Dialog logon attempts

� Report and transaction starts

� RFC/CPIC logons

Other events written into the log are:

� Locked transactions or users

� Changed or deleted authorizations, authorization profiles, and usermaster records

� Changes to the audit configuration


The log is created each day, and previous logs are not deleted or overwritten.The log files can become numerous and large, so we recommend that the logsbe periodically archived before being manually purged. An audit analysisreport can be generated from the audit logs. You can analyze a local server, aremote server, or all the servers in an SAP R/3 system.

Based on certain criteria, the information in the security audit files can bemanipulated to tailor the audit analysis report.

The report assists the administrator:

� Reconstruct or analyze incidents

� Improve security by recognizing inadequate measures

� Trace unusual user activities

� Understand the impact of changes to transactions or users

To start a security audit, you can use transaction SM19 to start recording datainto the security log. Alternately, you can set the profile parameter rsau/enableto 1. For more information, see “Changing System Profile Parameters(Transaction RZ10)” on page 608.

The number of audit logs created by the system depends on certain settings.You may choose to set the maximum space for the security audit file inparameter rsau/max_diskspace/local. When the limit has been reached, loggingwill end. Alternatively, you can define the size of an individual security logfile to fit in the chosen archiving media. This definition means that the systemproduces several log files each day and these files can be, for example,archived periodically into CDs. The profile parameter isrsau/max_diskspace/per_file, and the maximum size per file is 2 GB.

Running the Audit Log

This procedure assumes that the audit has been running for some time andthat audit logs have been created.

Task

Run the audit log

1. In the Command field, enter transaction SM20 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → SecurityAudit log → SM20-Analysis).

2. On the Security Audit Log: Local Analysis at <XXXXX> screen:

3. In From date/time, enter a time and a date (for example, 10:00).

4. Under Audit classes, select:

� Dialog logon

� Transaction start

Note

You cannot set both parameters. Youhave to choose the method by which theaudit files are created.


� Report start

5. Choose Re-read audit log to read a log for the first time.

6. The security report is displayed.

7. To view the details of an audit message, select a line and choose .


8. Documentation for the message and technical details are displayed. Thisscreen is useful when displaying negative messages such as failed logins orlocked transactions.

Setting Security Audit Log Parameters (SM19)

The audit log parameters are the criteria used to write the types of auditmessages into the audit log file. The parameters are grouped into auditprofiles that can be activated at the next system startup (configuration status)or applied dynamically.

Audit profiles must be first created before audit logs can be written. Theseprofiles limit the amount and type of data written into the security audit files,which makes the subsequent security reports more meaningful to theadministrator.

Decide what to audit and set selection criteria at the database level ordynamically at the application server level. If the audit configuration ispermanently stored at the database level, all application servers use theidentical criteria to save events in the audit log. The settings take effect at thenext application server start. At the application server level, however,dynamic changes can be set to individual application servers and distributedto the entire system. The new criteria will remain in effect until the server isbrought down.


You can define up to five sets of selection criteria or filters. The systemparameter, rsau/selection_slots, defines the number of filters has a default valueof 2. You can activate an audit in the dynamic configuration using transactionSM19.

Task

Set security audit log parameters

1. In the Command field, enter transaction SM19 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → SecurityAudit log → SM19-Configuration).

2. Configuration status refers to the storage of the parameters in the database.

3. Choose .

4. Enter a profile name (for example, audprof1).

5. Choose .


6. In this screen, you may specify two filter groups and define the types of auditmessages that will be written into the log.

Task

Define filter group 1

1. Choose Filter 1.

2. Under Selection criteria:


b. In User Names, enter *.

3. In Audit classes, select:

� Dialog Logon

� Transaction Start

4. Under Events, select All.


5. Select Filter active.

Task

Define filter group 2

1. Choose Filter 2.

2. This filter traces the reports started by one user.



b. In User Names, enter a user ID (for example, GARYN).

4. In Audit Classes, select Report start.

5. Under Events, select Important and critical.

6. Deselect Filter active. This setting allows you to save the filter settings butdoes not activate them.


7. Choose Detail configurat to drill down the audit class and event classcategories.

8. Under Filter 2, scroll down to Report start. Notice that the category isautomatically chosen based on the earlier selection of Event type and Auditclass type.

9. Choose .


10. The general categories are cleared indicating that settings were browsed ordefined at the detail level.

11. Choose .

12. A message at the bottom of the screen notifies the user that the profile wassuccessfully saved.

13. Choose .


14. The profile name is now in the Active profile field, and the message in thestatus bar indicates that the profile will be activated when the applicationserver is restarted.

15. To dynamically change the selection criteria for one or more applicationservers in a running system, choose the Dynamic configuration (Dynamicconfiguration) tab.

16. Choose .

Note

In this example, the audit has beenrunning for some time (indicated by thecurrent file size greater than zero)before being stopped briefly. The redsquare indicates that the audit isinactive.


Running an Audit on a Different User.

In this procedure, we will run an audit on a different user and check on all thereports that were started.

Task

Run an audit on a different user



b. In User names, enter a user ID (for example, Gerds).

2. Under Audit classes, select Report start.

3. Under Events, select All.

4. Under Filter 1, select Filter active.

5. Choose .


6. Choose Yes.

7. A green appears in the Stat (Status) column and the message at thebottom of the screen indicates that the configuration was activated.

User Security Audit Jobs

Many of these reports are included as part of the AIS. There are severalpredefined SAP security reports, including:

Report Description

RSUSR003 Checks for default password on user IDs SAP* and DDIC

RSUSR005 Lists users with critical authorizations

RSUSR006 Lists users who are locked due to incorrect logonThis report should be scheduled to run each day, just before midnight.

RSUSR007 Lists users with incomplete address data


Some of these reports have parameter tables that must be properlymaintained. Review and analyze these reports based on your knowledge ofthe company. However, be aware that security issues may exist. If you have asmall company, these issues cannot be avoided because one person oftenmust perform multiple tasks.

You can use either of the following transactions:

� SA38 (ABAP: Execute Program)

This transaction only allows the program to be executed.

� SE38 (ABAP Editor)

With this transaction, if the user has the security authorization, the usercan execute and change the program.

Task

Execute an ABAP program (Transaction SA38)

1. In the Command field, enter transaction SA38 and choose Enter.

2. In Program, enter the report name.

3. Choose .

RSUSR008 Lists users with critical combinations of authorizations or transactions

RSUSR009 Lists users with critical authorizations, with the option to select thecritical authorizations

RSUSR100 Lists change documents for users and shows changes made to auser’s security

RSUSR101 Lists change documents for profiles and shows changes made tosecurity profiles

RSUSR102 Lists change documents for authorizations and shows changes madeto security authorizations

Report Description

Your external auditorsmay require some ofthese reports to be

executed as part of the annualfinancial audit.


Task

Edit SE38 — ABAP Editor


2. In Program, enter the report name.

3. Choose .

Notes for Specific Reports.

RSUSR008 (lists critical combinations of authorizations or transactions):

� These combinations are maintained on table SUKRI.

� Dangerous combinations include the following transactions:

• RZ02 (with anything)

• RZ03 (with anything)

• SE14 (with anything)

• SU01 (with security, users, and profiles)

• SU02 (with security, users, and profiles)


Audit Tasks

Review that all Named Users are Valid

All users who have left the company should have their SAP R/3 accessterminated immediately. By locking or deleting these user IDs, you limitaccess to only those users who require SAP R/3 access. Periodic reviewassures that the task of locking or deleting has been completed.

Proper audit control requires that a user who no longer has a valid businessneed to access SAP R/3 should not be allowed to do so.

Deleting or locking these user IDs also prevents anyone who had been usingthe terminated user ID from accessing the system with that ID.

Task

Ensure that all named users are valid

1. In the Command field, enter transaction SU01 and choose Enter (or from theSAP standard menu, choose Tools → Administration → User maintenance →SU01-Users).

2. Choose .

One of the auditprocedures that yourexternal auditors will use

is to test whether a person whodoes not need to access SAP R/3has a live user ID.


3. Review the active users and verify that these users are valid.

Reviewing Profiles for Accuracy and Permission Creep

A permission creep is an incremental increase in permission given to a userover time. If left unchecked, increased permissions may grant a user moreauthority in the system than is required or intended.

Users may have undesirable authorization(s) or combinations.

You can conduct a spot audit of individuals.

1. Review the security forms for a user.

2. Compare these forms to the activity groups and profiles assigned to thatuser.

3. Investigate inconsistencies.

4. Review the activity groups and profiles assigned to the individual forsensibility.

5. Review the individual profiles assigned for content and check to see if theprofile has been recently changed, using transaction SU02 (Profiles) andtransaction SU03 (Authorizations).

You can also execute the following audit reports:

� RSUSR100 (user changes)

� RSUSR101 (profile changes)

� RSUSR102 (authorization changes)

For additional information on these reports, see “User Security Audit Jobs”on page 214.

In a large company, youshould do a random auditon at least 20 users. Your

auditors should determine theminimum number.

Note

For additional information on how tolock a user, see “Locking or Unlocking aUser (SU01)” on page 243.

Your external auditorsmay have an audit stepto check for permission

creep.

C H A P T E R

8

8User Administration


Overview

User administration is a serious function, not just a necessary administrativetask. Security is at stake each time the system is accessed. Because thecompany’s financial and other proprietary information is on the system, theadministrator is subject to external requirements from the company’s externalauditors, regulatory agencies, and others. Customers should consult withtheir external auditors for audit-related internal control user administrationrequirements. For example, human resources should be consulted if the HRmodule is implemented or if personnel data is maintained on the system.

A full discussion on security and user administration is beyond the scope ofthis guidebook. For example, manually creating and maintaining securityprofiles and authorizations is also not covered. Our discussion is limited to ageneral introduction and a list of the major issues related to security. The twosections below affect all aspects of security, which is why we begin with them.

User Groups

User groups are created by an administrator to organize users into logicalgroups, such as:

� Basis

� Finance

� Shipping

For additional information, see “User Groups” on page 245.

Profile Generator

The Profile Generator is a tool used to simplify the creation and maintenanceof SAP security. It reduces (but does not eliminate) the need for specializedsecurity consultants. The value of the Profile Generator is more significant forsmaller companies with limited resources that cannot afford to havededicated security administrators. For more information on the ProfileGenerator, see the Authorizations Made Easy guidebook.

Recommended Policies and Procedures

Some of the tasks in this guidebook are aimed at complying with commonaudit procedures. Obtaining proper authorization and documentation shouldbe a standard prerequisite for all user administration actions.


User Administration

User administration tasks comprise the following:

� User ID naming conventions

• The employee’s company ID number (for example, e0123456)

• Last name, first initial, or first name, last initial

In a small company where names are often used as ID, it is common touse the employee’s last name and first initial of the first name or theemployee’s first name and first initial of the last name (for example,doej or johnd, for John Doe).

• Clearly identifiable user IDs for temporary employees andconsultants (for example, T123456, C123456).

� Adding or changing a user

• The user’s manager should sign a completed user add-or-changeform.

• The form should indicate the required security, job role, and so on,that defines how security is assigned in your company.

• If security crosses departments or organizations, the affectedmanagers should also give their approval.

• If the user is not a permanent employee, or if the access is to be for alimited time, the time period and the expiration date should beindicated.

• The forms should be filed by employee name or ID.

• A periodic audit should be performed, where all approvedauthorizations are verified against what was assigned to the user.

� Users leaving the company or changing jobs

• This event is particularly sensitive.

• The policies and procedures for this event must be developed inadvance and be coordinated by many groups. As an example, see thetable below.

Group Responsibility

Human resources Legal or personnel matters

External auditors Internal control issues related to financialaudit

IT Procedures to terminate network access

Senior management Policy approval

Employee’s manager “Handover” or training period for theemployee’s replacement


To manage terminated employees:

� The user’s manager or HR should send a form or e-mail indicating that theemployee is leaving.

� The user’s ID should be locked and the user assigned to the user group“term” for terminated.

• If the user’s ID is not required as a template:

• The activity groups assigned to the user should be deleted. (usetransaction SU01, under the Activity Group tab, delete the activitygroups).

• The security profiles assigned to the user should be deleted (usetransaction SU01 and under the Task profile and Profile tabs, delete theprofiles).

� Check Background Jobs (transaction SM37) for jobs scheduled under thatuser ID.

The jobs will fail when the user ID is locked or deleted.

� If the user leaves one job for another and needs to maintain access forhandover, this handover should be documented.

The duration of the handover access must be defined and the expiration(Valid to) date entered in the SAP R/3 system.

� All temporary employees or consultants should have expiration (Valid to)dates on their user IDs.

System Administration

Special user IDs

The two user IDs (SAP* and DDIC) should only be used for tasks thatspecifically require either of those user IDs. A user who requires similar“super user” security rights should have a copy of the SAP* user security.

The user ID SAP* should never be deleted. Instead:

� Change the password.

� Lock the user ID.

If the user ID SAP* is deleted, logon and access rights are gained by rightsprogrammed into the SAP R/3 system. The user ID SAP* then gainsunknown and uncontrollable security rights.

For medium- and large-size companies, granting developers SAP* equivalentsecurity rights in the development and test systems is usually inappropriate.SAP* equivalent security in the production system is a security and auditissue and should be severely limited.

For privacy reasons donot use “mothers maidenname” as this is a

common one used by banks.

Similar to banks, thereshould be a “secret word”that users could use to

verify their identity over the phone.This word would be used whenthe user needs their passwordreset or their user ID unlocked.But, realize that others can“overhear” this secret word andrender it useless.

The security rights ofSAP* and DDIC areextensive, dangerous,

and pose a security risk. Anyonewho requires or requests similarsecurity rights should have anextremely valid reason for therequest. Convenience is not avalid reason. The security profilesthat serves as the “master key”are SAP_ALL, and to a lesserdegree, SAP_NEW.


User passwords

Parameters that define and restrict the user password are defined by entriesin the system profiles.

� Passwords should be set to periodically expire.

� The recommended expiration date is no more than 90 days, but auditorswill usually want this date to be set at 30 days.

� Minimum password length of five (5) characters should be set.

� User should be locked after three unsuccessful logon attempts.

The table of prohibited passwords (USR40) should be maintained.

The user IDs SAP* andDDIC should have theirdefault passwords

changed to prevent unauthorizeduse of these special user IDs.

An external audit procedurechecks the security of these twouser IDs.


Sample SAP R/3 User Change Request Form

SAP R/3 User ChangeRequest

Company ID:

System/Client No PRD 300

QAS 200 210 220

DEV 100 110 120

Employee: Type of Change � Change User

� Delete User

� Add User

Department Name/Cost Center Number:

User ID:

Position: Expiration Date (mandatory fortemporary employees)

Secret Word: Request Urgency � High

� Medium

� Low

Requester:

Requester’s Position:

Requester’s Phone:

Employee’s Job Function (If similar to others in department, name and user ID of a person with similar job function):

Special Access/Functions:

Requester Signoff

Name Signature Date Signed

Manager Signoff


Owner Signoff




Security


In addition to security approval (above), is a signed copy of computer security and policy statement attached?

� Yes � No


New User Setup

Prerequisites

To set up a new user, certain prerequisites must be met.

General Process or Procedure

Before you set up a new user, have available the user add form, with all therequired information and approvals.

The User’s Desktop

The user’s desktop should meet the following criteria:

� Does the system configuration meet the minimum requirements for SAP?

� Is the display resolution set to a minimum of 800 x 600?

� Is there sufficient space on the hard disk to install the SAP GUI withsufficient room for desktop application to run?

For Windows, a minimum of 50MB free space should remain after installingSAP GUI. A practical minimum however, is at least 100MB of free space.

Network Functionality

Can the user log on to the network?

From the user’s computer:

� Can you ping the SAP application server(s) that the user will be loggingonto?

� If the SAP GUI will be loaded from a file server, can you access the fileserver from the user’s computer where the SAP GUI will be installed?

For Installation of SAP GUI

Before you install the SAP GUI, you should have the SAP R/3 server nameand the SAP R/3 system (instance) number (for example, xsysdev and 00).You must enter this information during the installation.

Recommended Prerequisite for the GUI Installation:

The online documentation should be installed according to the instructions in the SAPdocument Installing the Online documentation. The online documentation installation andaccess method has changed since Release 3.x.

Tips & Tricks


Installing the Frontend Software—SAP GUI

The SAP GUI or frontend installation instructions are in the installation guide,Installing SAP Frontend Software for PCs. The SAP GUI can be installed froma copy of the presentation CD on a file server, or the presentation CD or acopy of the CD.

Installing SAP GUI from a File Server

The preferred method is to install SAP GUI from a file server because you donot need to carry the presentation CD around. Also, remote installations canbe completed without shipping out and potentially losing the original CD.

The following is a list of the prerequisites to install SAP GUI from a file server:

� Copy the SAP GUI load files from the presentation CD to a shared directoryon a file server.

� Have access to the shared directory from the user’s PC.

Task

Install the SAP GUI

1. Map a drive to the shared drive on the network where the presentation CDhas been copied.

2. Select the mapped drive to the presentation CD software (for example, sapgui-win-46d-comp4 on ‘Pa101003’ (F:)).

3. Drill down to the directory for the SAP GUI (for example, sapgui-win-46d-comp4 on ‘Pa101003’ (F:) → GUI → Windows → Win32).

4. Double-click on setup.exe. The installation program starts.

In most situations, acceptthe installation defaults.


5. Choose Next.

6. Select Local installation.

7. Choose Next.

8. Choose Next.

9. Select SAPgui.

Steps 10–13 are optional.

10. Click on Desktop Interfaces.


11. Choose Change option.

12. From this screen, select the components you want (for example, selectGraphical Distribution Network). This component is required if systemadministrators wish to view specific screens.

13. Choose OK.


14. Choose Next.

15. Select English.

16. Choose Next.

17. Choose Next.

18. This parameter is set within the SAP R/3 system when the onlinedocumentation is installed (Release 4.0B+).


19. Choose Next.

20. Enter the following information:

a. In Application server, enter your application server name (for example,pa102058).

b. In System number, enter your system number (for example, 00).

21. Choose Next.

22. Choose Next.


23. Choose Install.

24. The SAPSetup window appears to show you how the installation isprogressing.

25. The installation is now complete. Choose OK.

26. To add systems to the SAP Logon see section Adding Systems in the SAPLogon.

Installing SAP GUI from the Presentation CD

When the network connection between the SAP GUI files on the network andthe user is too slow to permit installation, install SAP GUI from thepresentation CD.

The SAP GUI files can be either loaded onto a local file server for installationor installed directly from the delivery media. The prerequisites for such aninstallation is that the user has a CD drive or other drive compatible with thedelivery media (ZIP®, optical, and so on) on which the SAP GUI files aredelivered.

Task

Install SAP GUI from a CD

1. Insert the CD into the drive.

A copy should be madeof the originalpresentation CD and the

copy shipped to the user site. Youthen maintain control of theoriginal CD and reduce thechance of loss. The SAP GUIinstallation files can also becopied to other high-capacityremovable media such as ZIP® oroptical disk, as appropriate foryour company.


2. In Windows Explorer:

a. Choose the CD-ROM drive (for example, D:).

b. Choose Gui → Win32.

c. Double-click on Setup.exe.

3. Follow the same procedure as when loading from a file server.

4. Test your connection

5. Log on to the system.

Adding Additional Systems

The SAP R/3 system can accommodate multiple systems in the SAP Logondialog box. You can add numerous systems, such as systems for reporting,human resources, and so on.

Task

Add additional systems to SAP Logon

1. On the SAP Logon window, choose New.

2. In the New Entry dialog box:

a. In Description, enter a short description of the system (for example, SA1).

b. In Application Server, enter the name of the server (for example,pa102058).

c. The SAP Router String field is usually blank.

d. In SAP System, select R/3.


e. In System Number, enter the system (instance) number for the instance inwhich you are creating the logon (for example, 00).

f. Choose OK.

3. The new system appears in the SAP Logon.

4. Test your connection.

5. Log on to the additional system.

Setting Up a New User (SU01)

The procedural prerequisite is to check that all documentation andauthorizations required to set up a new user are present.

New users can be created by copying an existing user, or creating a new userfrom scratch.

Copying an Existing User (SU01)

You can copy from an existing user if you have a good match. The new userwill have the same security profiles as the existing user. This process is theeasiest and is the recommended method for a small company. Before you dothis task, make sure that a valid user ID to copy is identified on the user setupform.

Create template users forthe various job functionsthat can be copied to

create new users.


Task

Copy an existing user (SU01)


2. In User, enter the user ID that you want to copy (for example, GERDS).

3. Choose .

4. In the Copy Users dialog box:

a. In To, enter the new user ID (for example, GERDSC).

b. Choose .

5. Under the Password section, in Initial password, enter an initial password (forexample, initi).

6. Reenter the same password in Repeat password. You may choose to let thesystem generate a random password.

7. In User group for authorization check, enter the user group (for example,SUPER) to which the user is to be assigned.

8. Check to select from a list of user groups.

9. In Valid from and Valid to, enter dates to limit the system access duration forusers.

Follow your company’snaming convention forcreating user IDs.

Note

Your company may have a passwordpolicy where a random initial passwordis to be used.

A user group must existbefore a user can beassigned to it.


10. Choose the Address tab to change the user’s address data.

11. On the Address tab:

a. Enter the user’s personal information (name, job function, department,and so on).

b. Choose the Defaults tab.

Entering valid to/fromdates is usually requiredfor contractors and other

temporary personnel.


12. Check that the Logon language is set correctly (for example, EN for English). Ifthe system default language has been set (for example, to English), then thisfield is only used to enter a default logon language for the individual user (forexample, DE for German).

13. Under Output Controller:

a. For OutputDevice, enter a default printer or choose to select a printer.

b. Select:

• Output immediately

• Delete after output

14. Check that the Personal time zone is correct, or choose to select a time zone.

15. Under Decimal notation, select the appropriate notation (for example, Point forUnited States).

16. Under Date format, select the appropriate date format (for example,MM/DD/YYYY).

17. Choose . The message on the status bar indicates that the user was saved.

A telephone numbershould be a requiredentry field. If there is a

system problem identified with theuser, you must contact that user.

The Decimal notationaffects how numbers aredisplayed. Setting it

correctly is critical to preventconfusion and mistakes.


Creating a New User (SU01)

Sometimes it becomes necessary to create a completely new user. You mayneed to create a new user when you do not have another user from which tocopy.

Task

Create a new user (SU01)

1. In the Command field, enter transaction SU01 and choose Enter(or from the SAP standard menu, choose Tools → Administration → Usermaintenance → SU01-Users).

2. Enter the user ID (for example, GERDSC) that you want to create.

3. Choose .


4. On the Address tab:

a. Enter the user’s personal information (name, job function, and so on).

b. Choose the Logon data tab.

5. Enter an initial password (for example, initi). Reenter the same password inthe second field. You may choose to let the system generate a randompassword.

6. In User group for authorization check, enter the user group (for example, SUPER)to which the user is to be assigned or choose to select a user group.

7. Enter dates in the Valid from and Valid to fields to limit the duration that theusers will have access to the system.

A telephone numbershould be a requiredentry field. If there is a

system problem identified with theuser, you must contact that user.

A user group must existbefore a user can beassigned to it


8. Choose the Defaults tab.

9. As an option, in Logon language, enter the appropriate language code (forexample, EN for English). If the system default language has been set (to forexample, English), this field is only used to enter a default logon language forthe individual user (example, DE for German).

10. Under Output Controller:

a. For OutputDevice, enter a default printer or choose to select a printer.

b. Select:

• Output immediately

• Delete after output

11. Under Personal time zone, enter a time zone or choose to select a time zone.

12. Under Decimal notation, select the appropriate notation (for example, Point, forUnited States).

13. Under Date format, select the appropriate date format (for example,MM/DD/YYYY).

Entering valid to/fromdates is usually requiredfor contractors and other

temporary personnel.

The Decimal notationaffects how numbers aredisplayed. Setting it

correctly is important to preventconfusion and mistakes.


14. Choose .

15. The message indicates that the user was saved.

16. Assign security to the user by using the Profile Generator (see theAuthorizations Made Easy guidebook).


Maintaining a User (SU01)

Before maintaining a user, have a properly completed and approved userchange form.

You must maintain a user to manage job changes to an existing job orposition, new jobs or positions, and user data changes, such as name, address,phone number, and so on.

Task

Maintain a user (SU01)


2. Enter the user ID (for example, GERDSC) to be maintained.

3. Choose .

The user changedocumentation is auditedin a security audit.

Note

The Maintain User screen allows youto change a user’s:

� Address

� Logon data

� Defaults

� Password

� User group

� Other


4. When you finish making the changes, choose .

Resetting a Password (SU01)

The most common reason to reset a password is that users forget theirpassword. In this situation, the user has probably attempted to log on toomany times with an incorrect password. The user has probably also lockedtheir user ID, which also needs to be unlocked.

Ensure that the personwho requests theirpassword to be reset is

indeed the valid user.


You should maintain a security log of password resets. This log should beperiodically audited to look for potential problems.

1. In the Command field, enter transaction SU01 and choose Enter(or from the SAP standard menu, choose Tools → Administration → Usermaintenance → SU01-Users).


3. Choose .

4. In the Change Password popup window, enter a new password in Newpassword and reenter this password in Repeat password.

5. You may choose to let the system regenerate a random password.

6. Choose .

Locking or Unlocking a User (SU01)

The lock/unlock function is part of the logon check, which allows the user tolog on (or prevents the user from logging on) to the SAP R/3 system.

A basic user verification method is to have a telephone with a display so that the displayedcaller’s phone number can be compared to the user’s phone number, which is stored in thesystem or can be found in the company phone directory.

We recommend that you use a method similar to what banks use where the user has a secretword that verifies their identity on the phone. However, this method is not foolproof becausesomeone can overhear the secret word.

Tips & Tricks

For security, you can onlyset an initial value for theuser’s password. Users

are then required to change thepassword when they log on. Youcannot see what the users currentpassword is, nor can you set apermanent password for the user.


Locking a user

SAP R/3 access should be removed if a user leaves the company, is assignedto a different group, or is on leave.

The lock function allows the user ID and the user’s security profile remains onthe system but does not allow the user to log on. This function is ideal fortemporary personnel or consultants where the user ID is locked unless theyneed access.

Unlocking a user

Users are automatically locked out of the system if they attempt to incorrectlylog on more than a specified number of times. The administrator must unlockthe user ID and may need to reset the user’s password.

Task

Unlocking a user

1. In the Command field, enter transaction SU01 and choose Enter (or chooseSAP standard menu → Tools → Administration → User maintenance → SU01-Users).


3. Choose .

4. A popup window appears. In this example, an administrator has manuallylocked the user ID.

5. Choose . In this example, this step will unlock the user.

Before unlocking a user,determine if the request isvalid. Do not unlock a user

who has been manually lockedwithout first finding out why thiswas done. There may be animportant reason why the usershould not access the system.

Maintain a security log ofunlocked users, whichshould be periodically

audited for potential problems.

If the system managerlocks a user, alwayscheck why. A valid reason

may exist for not unlocking a user.


6. A message at the bottom of the screen indicates that the user has beenunlocked (or locked).

User Groups

A user group is a logical grouping of users, such as shipping, order entry, andfinance.

The following restrictions apply to user groups:

� A user can belong to only one user group.

� A user group must be created before users can be assigned to it.

� A user group provides no security until the security system is configuredto use user group security.

The purpose of a user group is to provide administrative groups for users sothey can be managed in these groups, and apply security.

Usage

Following are a few recommended special groups:

Create the group term forterminated users. Lockall users in this group

and, for most of these users,delete the security profiles. Thisprocess maintains the userinformation for terminated users,and prevents the user ID frombeing used to log on.

Group Definition

TERM Terminated users. This way, user records can be kept in the system foridentification.

� All users in this group should be locked.

� If it is not being used as a template, all security profiles should beremoved from the user.

SUPER Users with SAP* and DDIC equivalent profiles.

TEMPLATE Template users to be used to create real users.


How to Create a User Group (SU01)

You must first set up user groups before you can administer security.

Task

Create a user group (SU01)


2. From the menu bar choose Environment → User groups → Maintain.

3. Enter the name of the user group you would like to create (for example,purchasing).

4. Choose .

5. In Text, enter a description of the user group.

6. Under User Assignment, in User, choose to add users to the group.


7. Choose .

8. The message indicates the new user group was created.

Deleting a User’s Session (Transaction SM04)

Use transaction SM04 to terminate a user’s session. Transaction SM04 mayshow a user as being active when the user has actually logged off. Thiscondition is usually caused by a network failure or an improper system logoff(for example, the user turned the PC off without logging off the system).

A user may be on the system and needs to have their session terminated. Theuser’s session may be hung and terminating the session is the only way toremove the user’s session. Alternately, the user may have gotten into a one-way menu path without an exit or cancel option. This situation is dangerous,and the only safe option is to terminate the session.


Terminate a User Session

You must log on to the specific server that the target user is logged on.

Task

Terminate a user session

1. Verify that the user is actually logged off from SAP R/3 and that there is noSAP GUI window minimized on the desktop. Verification is done byphysically checking the user’s computer, if possible.

2. In the Command field, enter transaction SM04 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → Systemmonitoring → SM04-User overview).

3. Select the user ID to delete.

4. Choose Sessions.

5. Select the session to be deleted.

6. Choose End session. It may take a while to actually delete the session so bepatient.

7. Repeat steps 5 and 6 until all sessions for that user are deleted.

Active Users (Transactions SM04 and AL08)

These transactions display all the users who are currently logged on to thesystem. They show both the user’s ID and terminal name.

Verification is importantbecause users may haveforgotten that they

minimized a session.

In step 3 above, double-check that the selecteduser is the one you really

want to delete. It is very easy toselect the wrong user.


In a smaller company, the administrator can recognize user IDs logged on to“unfamiliar” terminals. This recognition may indicate that someone—otherthan the designated user—is using that user ID.

A user logged on to more than one terminal indicates that the user ID is being:

� Used by someone else

� Used or shared by several people

Problems

Transaction SM04 may show a user as active, when in fact the user hasactually logged off. Because the user session was not properly closed, thesystem shows the user as still logged on.

The following can cause this condition:

� A network failure, which cuts off the user from the network or SAP R/3.

� The user turning off their computer without logging off from the SAP R/3system.

Task

Display active users on a single-instance system

1. In the Command field, enter transaction SM04 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → Systemmonitoring → SM04-User overview).

2. Select the user ID to view the session the user has open.

3. Choose Sessions.

4. The Overview of Sessions screen shows what sessions the user has open.

User IDs should not beshared for severalreasons.

If a problem arises, you will notknow who created the problem.This situation makes the problemdifficult to fix and prevent areoccurrence.

Prudent security practices do notallow for sharing of user IDs. Setthe system profilelogin/disable_multi_gui_login.

Your external auditors may alsoperform this test to test yoursecurity.


5. Choose .

Task

Display users on a multi-instance system

1. In the Command field, enter transaction AL08 and choose Enter (or from theSAP standard menu, choose Tools → CCMS → Control/Monitoring →Performance menu→ Exceptions/Users→ Active users→ ALO8-Users, global).

2. The Current Active Users screen shows all the instances in your system andthe number of active users.

3. For each instance, the users logged into that instance/application server arelisted.

If you have severalinstances in your system,using AL08 is easier,

because you can simultaneouslysee all users in all instances.

P A R T F I V E

DDatabase Overview


Part Overview

In the database section of the System Administration Made Easy Guidebook, we have forthe first time included coverage of more than one database. The goal that was envisionedwith the reorganization of the 4.0B edition, of covering more than one database in theguidebook is nearing completion. For the 4.6C/D edition we will cover DB2/UDB,Microsoft SQL Server, Informix, and Oracle.

The guidebook has been arranged so that the tasks specific to individual databases arelocated in the database chapters. All other chapters are mostly database-independent.

The various mySAP.com components run on several databases. At present, these are IBMDB2/UDB, IBM Informix, Microsoft SQL Server, Oracle, and SAPDB. The tasks that needto be performed on all the databases are the same. How they are done is specific to theindividual databases.

For example, you must take a backup on all databases, but the method of taking a backupdiffers for the different databases, similarly with other tasks such as starting and stoppingthe SAP instance.

C H A P T E R

9

9Database Administration - IBM

DB2 Universal Database


Overview

An IBM DB2 database server can be managed in several ways, such as with acommand line interface, DB2’s GUI tool (DB2 UDB Control Center), and SAPsystems.

IBM’s DB2 Universal Database runs on the following operating systemplatform:

� OS390

� AS400

� Unix

� Windows NT

Because of this diverse base, and for simplicity, we will use the command lineinterface in this chapter. The command line interface is always available, andyou can telnet to every host, including NT servers that have telnet servicesinstalled.

Starting and Stopping the Database

The following tasks show you how to start and stop the database.

Task

Start the database

1. Start the DB2 instance db2<dbname>:

a. Open a telnet connection to the database server.

b. Logon as user <dbname>adm (for example 16dadm).

c. Enter db2start.

Note

We will use <sid>, <sapsid> and<dbname> interchangeably when wetalk about the name of the SAPdatabase in this administration chapter.

Chapter 9: Database Administration - IBM DB2 Universal Database 255

2. Activate the DB2 database db<sid> (for example, db2 activate db16d).

3. Your DB2 database is now active, with all buffers allocated and ready for use.

Task

Stop the database

1. The SAP R/3 system must be stopped before the database is stopped. At thecommand prompt, enter stopsap r3 to stop the SAP R/3 instance.

2. To shut down the DB2 database <dbname> and stop the DB2 instancedb2<dbname>:

a. a.Open a telnet connection to the database server.

b. b.Logon as user <dbname>adm (for example, l6dadm).

c. c.Enter db2stop and choose Enter.

DB2 UDB Administration in SAP Systems

With Release 4.6C, SAP has implemented an improved database monitor,known as DB6COCKPIT for DB2 UDB servers. This monitor replaces legacyscreens and can be called using transaction ST04. Transaction ST04 is a centraltransaction for all DB2-related tasks. Transaction ST04 simplifies databasemonitoring for consultants unfamiliar with DB2 UDB. Also, it offersfunctionality that is not available on other database platforms. Because SAPsoftware is able to run on massive parallel DB2 database servers, the databasemonitor allows you to monitor multiple database partitions residing onseparate physical servers.

Database Performance (ST04)

The transaction ST04 can be used to analyze the following databasecomponents:

� DB2 Memory and buffer usage

� DB2 catalog and package cache usage

Alternately, you can startthe SAP componentusing the startsap

command. Using this command,the above steps are performedautomatically.

Familiarize yourself withthis database monitortool. For more

information, see IBM’s DB2 UDBSystem Monitor Guide andReference available at http://www-4.ibm.com/software/data/db2/library/.


� DB2 I/O Performance data

� Locks and Deadlocks

� Connected Applications

� SQL Cache

� Table usage

To manage your database server, you must use the Database Performancetransaction (ST04) on a regular basis. You should monitor the buffer pool hitratio and messages in the DB2 database diagnostic log files.

Task

Monitor database performance

1. In the Command field, enter transaction ST04 and choose (or from the SAPstandard menu, choose Tools → Administration → Monitor → Performance →Database → ST04 – Activity).

2. In the DB2 UDB screen, choose Performance → SQL Cache.

3. The Selection Criteria dialog box appears. Enter any necessary information inthe fields (for example, to select all statements, in Executions, enter 1).

Note

The following tabs on the DB2 UDBscreen are important:

� Header InformationGeneral information about theDB2 Release, Partition selectedand the Start Time of DatabaseManager.

� Buffer PoolThis tab displays an overview ofthe buffer pools. A buffer qualityover 98% means that buffering ofdata and indexes is very good.


4. Choose OK.

5. The DB2 UDB screen displays all SQL statements that were executed in theDB2 server. The header information contains the timestamp of the lastsnapshot.

6. To retrieve a current snapshot, choose REFRESH.

7. The Selection Criteria dialog box appears. Enter your selections and chooseOK.


8. The entries in the SQL statement cache display.

9. Select an entry.

10. Choose Explain.

11. The Display Execution Plan for SQL statement screen displays. If you aremissing indexes, you will see operation TBSCAN on tables. This is anindication for performance problems.


Space Allocation

A mission critical task is the monitoring of the database growth. If yourdatabase runs out of space during use, you will experience downtime untilthe database has been expanded. The database expansion can be performedusing the DB2 CLP or the DB2 UDB Control Center.

Task

Determine database space allocation

1. In the Command field, enter transaction db02 and choose (or from SAPStandard menu, choose Tools → Administration → Monitor → Performance →Database → Tables/Indexes)

2. The Database Performance: Tables and Indexes displays the tablespace allocatedby the database in the following fields:

� Total number

� Total size

� Total free

3. To retrieve current information, choose REFRESH. A dialog box appears toinform you that the process may take a long time.

4. Choose OK.

5. Choose Detailed analysis.

Note

The tablespace column displays thetablespace names.

The Type column displays the type oftablespace:

� DMS: pre-allocated space in adatabase file (in DB2, this spaceis known as a container)

� SMS: pages will be allocated andde-allocated dynamically duringruntime using files in a directory

� RAW: space managed like DMS,but in a raw device

The percent used column is the mostimportant entry. If any value is largerthan 95%, you may want to consider theexpanding your table space.


6. The Database Performance: Tablespaces screen appears.

Backups and Recovery

You can also use transaction ST04 to view this information. This transactiontakes you to the Space: Container Configuration screen. In the left frame of thescreen, choose Space → Tablespaces. (If you are running 4.6D, choose Space →Tablespaces → Containers to show the space information on a tablespace level.)

Important information is contained in the following fields:

� Pages total: the number of pages available in a container

� Accessible: information about the accessibility of the database container. Ifthere is an access problem, you will see NO and the tablespace will beoffline.

Task

View backup and recovery information

1. In the Command field, enter transaction ST04 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → Performance→ Database → ST04 – Activity).


2. In the left frame, choose Backup and recovery and double-click on Backupoverview.

3. On the Overview of Backup Status screen:

a. Choose Refresh.

b. Choose Overview of all database backup.


4. The backup overview displays. The task color indicates the status, readmeaning failure, and green meaning success.

5. Select a backup log.

6. Choose Display.

7. The detailed information on the backup selected is shown.


8. Choose Back. on this screen and the next two screens.

9. To display information about the DB2 database server logging status, chooseBackup and recovery and double-click on Logging Parameters.

10. For a production SAP system using DB2 UDB, you must ensure that thefollowing two parameters are set:

� Log retain enable = RECOVERY

� User exit enable = ON


Scheduling Database Administration Tasks (DB13)

This section explains the basics of planning DBA tasks.

The DBA Planning Calendar (DB13) is used for scheduling DBA tasks withinSAP systems. Using the calendar, the DBA can schedule the following:

� Archive log files

� Reorganization

� Update Statistics

� Back up the database

� Initialize Tapes

Managing and scheduling tasks inside an SAP system is easier than using thecommand line interface.

Task

Schedule database administration tasks (DB13)

1. In the Command field, enter transaction DB13 and choose Enter (or from theSAP Standard menu, choose Tools → CCMS → DB Administration → DBAPlanning Calendar)

2. The DBA Planning Calendar screen appears. To Plan a DBA Action, select adate on the calendar.

3. Choose Create.

To schedule a backuptask, the backup must beable to run unattended.

Your tape drive must havesufficient capacity to back up thedatabase without changing tapes,or you must have multiple tapedrives with sufficient total capacity.


4. On the Schedule an Action for <XXXXX> dialog box:

a. In StartTime, enter your starting time (for example, 01:10:00).

b. Under Action, select an action category to perform (for example Archiveinactive log files onto device).

c. Choose .

5. On the Tape Name dialog box, enter the required parameters. Choose .

6. Choose .

To use tape devices inparallel, enter the fullyqualified device names

separated by commas.


7. The task displays on the selected date. The Action scheduled message displaysat the bottom of the screen.

Reviewing the DBA Planning Calendar

The following task shows you how to display the job logs to ensure propertask execution.

Task

Review the DBA Planning Calendar

1. In the Command field, enter transaction DB13 and choose Enter (or from SAPStandard menu, choose Tools → CCMS → DB Administration → DBA PlanningCalendar)

2. Review the scheduled tasks. The color indicates the status:

� Red: Failure

� Yellow: Warning

� Green/Blue: Success

3. If there are more jobs to be displayed, a scroll bar appears.

4. Select a task.


5. Choose Job logs for more information.

6. Select the task.

7. Choose .


8. The Job Log Display screen appears.

Diagnostics

The diagnostics section includes information about possible databaseproblems. To analyze and solve the problem you should review the output ofDB2 UDB’s diagnostic log file db2diag.log.

Task

Run diagnostics

1. In the Command field, enter transaction DB13 and choose Enter(or choose Basic Tools → Administration → Monitor → Performance → Activity→ Diagnostics).

2. On the DB2 UDB screen, in the left frame, choose Diagnostics and double-clickon DB2 UDB diag log. This process may take some time to run.


3. The right frame displays the contents of the db2diag.log file.

Command Line Processor

The DB2 command line processor (DB2 CLP) can be used to administer a DB2UDB database. The tool is supported on all DB2 platforms.

The tool can be used to:

� Start and stop the database (see section starting and stopping)


� Back up the database log files

� Restore the database

� Check and update the database configuration

� Check and update the database manager configuration

� Resize or extend the tablespace containers

� Other

Most SAP software interfaces to DB2 use the DB2 CLP. If there are problemswith the database, you are always in a good position if you know how to usethe DB2 CLP.

Task

Start the command line processor

1. Open a telnet connection to the database server.


2. Log on as user <dbname>adm (for example, l6cadm)

3. To start the DB2 CLP, enter db2.

4. Enter connect to l6cadm and press Enter.

5. The connection information is shown.

Note

You can always enter DB2 commandsfrom a shell prompt by entering the DB2command prefixed by db2. Forexample, you can enter db2connect to <dbname> toconnect to your DB2 database. If youneed more information about acommand you can use the ? token (forexample, db2 “?” backupshows all options of DB2’s BACKUPcommand).

DB2 UDB distinguishes between DB2 command and SQL statements. A statement is andatabase operation that will be logged and is recoverable. For example, changes to thestructure of the database are made using the db2 alter tablespace statement. During databaserecovery, these changes are re-applied.

A command is issued against the DB2 database server or a database, or other DB2infrastructure elements. You will find information about DB2 command in the CommandReference. Details on SQL statements are in the SQL Reference. Both of these references areavailable at http://www-4.ibm.com/software/data/db2/library/.

TechTalk


Task

Check and update the Database Manager Configuration

1. To check the Database Manager Configuration from the command lineprocessor, enter the following DB2 command:get database manager configurationorget dbm cfg

2. To update a parameter in the Database Manager Configuration, enter:update database manager configuration using <parameter><value>orupdate dbm cfg using <parameter> <value>

Task

Check and update the Database Configuration

1. To check the Database Manager Configuration in the command lineprocessor, enter:get database configuration for <dbname>orget db cfg for <dbname>


2. To change a parameter, enter:update database configuration for <dbname> using <parameter><value>orupdate db cfg for <dbname> using <parameter> <value>

Task

Extending or resizing a tablespace

1. To extend all containers of a tablespace by a specified number of additionalpages, enter the following command in the DB2 CLP:

alter tablespace <tablespace name> extend (all <additionalpages>)

2. Alternatively, to specify a new size for the tablespace, you can use the RESIZEcommand. Enter:

alter tablespace <tablespace name> resize (all <newcontainer pagesize>)

Task

Back up a database using DB2 CLP

1. To back up the database <dbname> using online backup, two tape drives,four backup buffers, and three tablespaces backed up in parallel, enter on oneline:db2 backup db <dbname> online


to <dev1>, <dev2>with 4 buffersparallelism 3

The DB2 UDB Control Center

The DB2 UDB Control Center is a graphical tool for management of DB2 UDBdatabases. Because it is based on the Java Runtime Environment (JRE), thetool is supported on all platforms. The DB2 UDB Control Center can be usedto:

� Start and stop the database (see section starting and stopping)

� Back up and restore the database

� Back up the database log files

� Check and update the database configuration

� Check and update the database manager configuration

� Update passwords for sapr3 and <sid>adm

� Other

To start the DB2 UDB Control Center, you must follow OS-specific guidelines.For example, on the NT platform, use Start→ Programs→ IBM DB2→ ControlCenter.

The DB2 UDB Control Center uses a GUI to manage DB2 databases.


To perform SAP-specific tasks, you must install the SAP Control CenterExtensions on top of the DB2 UDB Control Center. The most currentinformation about installing the SAP Control Center Extensions tools can befound in SAP Note 410252.

C H A P T E R

10

10Database Administration —



Overview

Microsoft SQL Server is a low maintenance database that also supports verylarge databases in excess of 1TB in size.

This chapter reviews the database administrative tasks that can beaccomplished within the SAP R/3 system with associated tasks utilizing theMicrosoft administrative tools.



Task

Start the database

1. From the Windows taskbar, choose Start → Programs → Microsoft SQL Server→ Service Manager.

2. Choose Start/Continue.

3. Check that Microsoft SQL Server is started by checking the color and shape ofthe status icon (the green arrow), and the status message at the bottom of thewindow.

Chapter 10: Database Administration – Microsoft SQL Server 277

4. Select the Services drop down list and choose SQL Server Agent.

5. Check that Microsoft SQL Server Agent is started by checking the color andshape of the status icon (the green arrow), and the status message at thebottom of the window. If it is at the Stopped status, choose Start/Continue.

Task

Stop the database

1. Verify that SAP R/3 has been stopped. If SAP R/3 has not been stopped, stopSAP R/3 now.

2. From the NT desktop, choose Start→ Programs→ Microsoft SQL Server →Service Manager.

3. Choose Stop.

4. Choose Yes.

5. Choose Yes.

Follow the properprocedure to stop SAPR/3.


6. Check that Microsoft SQL Server is stopped by checking the color and shapeof the status icon (a red square), and the status message at the bottom.

Database Performance

Overview

The Computing Center Management System (CCMS) has tools available forSAP R/3 administrators to monitor the database for growth, capacity, I/Ostatistics, and alerts. This section discusses the initial transactions that canhelp the database administrator.

Database Activity (ST04)

The Database Performance Monitor (transaction ST04) provides a database-independent tool to analyze and tune the following components:

� Memory and buffer usage

� Space usage

� CPU usage

� SQL requests

� Detailed SQL items

To manage your system performance, the database must be monitored. Animportant item is the ability to view the database error log from within SAPR/3. This view saves the extra effort of logging into the database to view thislog.

Do not use NT services orissue command: netstop

mssqlserver to stop the SQLserver database. This will notproperly flush the DB buffers todisk when stopping and maycause database startup problems.


Task

View database activity

1. In the Command field, enter transaction ST04 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor →Performance → Database → ST04 - Activity).

2. The SQL Server Performance Analysis screen appears, displaying a summaryof database activity pertaining to the database, operating system, CPU, andmemory. Microsoft SQL Server allows the analysis of specific attributespertaining to memory, space, I/O, and quality of table reads and writes. Thisinformation can signal adjustments necessary to improve performance of thedatabase.

3. The Database Performance Analysis: SQL Server Database Overview screen isthe Detailed analysis menu (option 2D).

a. This screen is composed of the following three sections:

• Analyze database activity

• Analyze exceptional conditions

• Additional functions

Determine the frequencyto reboot the system toclear memory

fragmentation.

Memory Usage

� Procedure cache and data cachehit ratio can reflect memoryproblems. For optimal usage,these values should approach99%.

Server Engine/Elapsed

� Shows how hard the CPU isworking on MS SQL Serverprocesses. Pay attention to theratio of busy time to idle time

SQL Requests

� Shows how SQL queries areutilizing table access for full tableor index scans. A high ratio of fulltable scans to index scans canindicate performancebottlenecks.

DB startup

� Indicates the last time the SQLserver was restarted


b. Areas of common interest are:

• Server details

• SQL processes

• Error logs (see the following screen)

c. Additional functions are links to transactions that will be discussed in latersections.

4. The SQL Error Logs Overview screen appears.

5. Select an entry in the Log name column.


6. Choose .

7. The Display Selected SQL Log screen appears.

Refer to SAP Note425763 (German) if errorlogs are not seen.


Database Allocation (DB02)

The Database Allocation transaction is used to analyze:

� Database growthUsing the growth rate you could project the growth to determine whenyou may need to get additional disk storage for the database.

� Database index, consistency, and so on

� Tables

Task

View database allocation

1. In the Command field, enter transaction DB02 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → Performance→ Database → DB02-Tables/Indexes).

2. An initial review identifies the database type, name, size, file systems, andtotals for database objects.

a. The following describes some of the information on the screen:

• Database information indicates space used for data and loginformation.

• DB space history takes you to the View database history screen.

• DB analysis takes you to an analysis menu screen.

b. To determine attributes for a specific database object, use Detail analysis tomake decisions for an individual object.

Note

This transaction can also be accessedwith transaction ST04. Choose Detailanalysis menu → State on disk.


3. This screen is the DB space history display. A spreadsheet allowing analysisbased on calendar scenarios exists with the ability to sort on columninformation.

4. To view by file, choose Files.

5. You can analyze the physical file information.

6. The Database Analysis screen appears. The administrator can use theinformation on this screen to:

� Analyze the database for missing indexes, conflicts between ABAPDictionary and database, and SAP R/3 Kernel integrity

� Perform a database consistency check


Analysis can be done for table specific objects to determine the largest tables,and tables that are modified.

Scheduling Database Tasks (DB13)

The DBA Planning Calendar (DB13) is the scheduling tool for DBA tasks inSAP R/3. Using the Calendar, the DBA can schedule many of the DBA tasksthat must be performed, such as:

� Database and transaction log backup

� Differential database backup

� Check database consistency

These tasks can be conveniently managed and scheduled without going to thedatabase. The DBA Planning Calendar works with transaction DB12 (Backuplogs). For more information on transaction DB12, see page Checking theDatabase Backup (DB12).

Task

Schedule database tasks

1. Enter transaction DB13 and choose Enter (or from the SAP standard menu,choose Tools → CCMS → DB Administration → DB13-DBA PlanningCalendar).

To schedule a backuptask using the DBAPlanning Calendar, the

backup must be able to rununattended, meaning that youmust have one of the following:

� A single tape drive withsufficient capacity to backup the database withoutchanging tapes.

� Multiple tape drives withsufficient total capacity toback up the databasewithout changing tapes.


2. Double-click on the date. If a task exists for that day, this window appears.

3. On the Actions for <XXXXX> dialog box, choose Insert to add a new task.

4. In StartTime, enter the time to begin the backup.

5. Under Action, select a task (for example, Full Database Backup).The start time is the timeon the database server.


6. Choose Continue.

7. Select the database to be backed up. In this example, we select all thedatabases.

8. Choose OK.

9. Select the backup device (for example, R3DUMP0).

10. Choose OK.


11. In the Log backup tape options dialog box, select the following options asappropriate:

a. Unload tapeTo eject the tape after the backup is completed

b. Initialize tapeTo overwrite existing data, rather than appending to last backup

c. Verify backupTo verify the backup after it has run

If you are doing an online backup when transactions are being performed,selecting this option is not useful because the database changes duringthis time will cause this test to fail.

d. Format tapeTo erase the entire tape and write a new tape label

This option is selected when using a brand new tape, or a tape that waspreviously used with a different application, or backing up to disk whensame device is loaded.

12. In Expiration period for backup volumes, enter the number of days to protectthe tape.

13. Choose OK.

14. Choose .


15. The task will be listed in the day.

Determining the Tape (Label) Necessary for a Backup

Using the correct tape is important. If the wrong tape is used, the backup willfail. For more information on tape labeling, see “Tape Management” onpage 48.

Task

Determine the tape (label) necessary for backup

1. Double-click on the desired day.


2. If more than one entry is shown, select the backup entry.

3. To see what tape (label name) is required for that backup, choose Volumesneeded.

4. The required tape is displayed (for example, CD15S).


Deleting an Entry from the Planning Calendar (DB13)

Occasionally, you may find entries in the DBA Planning Calendar that are nolonger needed. The following task show you how to delete them.

Task

Delete an entry from the Planning Calendar

1. On the DBA Planning Calendar, double-click on the date.

2. Select the item to delete.

3. Choose Delete.

4. Choose Yes.

5. The item has been deleted.

Note

You can also choose Change to changethe options you originally selected forthe job.


6. Choose .

Checking the Database Backup (DB12)

The Backup Logs transaction (transaction DB12) provides backup and restoreinformation, such as:

� Log file size and free space in the log file

� Date and time of last successful restore for:

• SAP R/3 database

• Transaction log

• Master database

• Msdb database

� Backup history

� Restoration history

� Backup device list

� SQL Server jobs

� Tapes needed for restore

It is a convenient collection of backup information.

Some of the important backup information such as tape label name is passedto DB12 from DB13. The tapes needed for restore option is important.

The only missing information is the run time (duration) of the backup job.This is a problem indicator, when compared to the expected duration of thebackup.

Do not be overly relianton the tapes needed forrestore feature. You must

have a method that does not relyon SAP R/3 being available to tellyou what tapes you must do arestore of the SAP R/3 system. Ifthere is a severe disaster, and theSAP R/3 system is lost, SAP R/3is not available for you to look atthis report.


Task

Check the database backup

1. In the Command field, enter transaction DB12 and choose Enter (or from theSAP standard menu, choose Tools → CCMS → DB Administration → DB12-Backup logs).

2. On the CCMS Monitoring Tool – DB12 (Backup/Restore Information) screen,review log space information to analyze growth.

3. Review backup information and notice the date and time of success orfailures.

Note

The following is a list of the available buttons and their functions:

Backup historyA spreadsheet summary of each backup is listed. Each backup type can be reviewed withdetailed log information available using History info.

Restoration historyA spreadsheet of detailed restoration information is listed.

Backup device listEach logical device name is listed with the appropriate physical device name

SQL Server jobsA spreadsheet listing of all scheduled jobs with options for CCMS, Database and History Infois listed. History Info lists the specifics of the job that pertain to success or failure of the job.

Tapes needed for restoreA listing of the tapes that are needed to restore the various databases. Scroll to the bottom ofthe screen, for the instructions to restore the database.


Initializing Backup Tapes

Initializing the tape writes a label on the tape header. This label is the same asthe physical label of the tape (for example, CD26S).

The tape label and the expiration date are additional safety levels to preventbacking up to the wrong tape, and possibly destroying needed data. Whenusing the DBA Planning Calendar (DB13) for backups, the tape must beproperly labeled to execute a backup to tape, because the transaction expectsa specific tape to be in the drive. If the tape label does not match the requiredlabel, the backup will fail.

Initializing and labeling is an option when executing the backup using DB13,SQL Server Enterprise Manager, or NT Backup.

Database Backups with Microsoft Tools

Backing up SAP R/3 on the SQL Server involves backing up the followingSAP-specific and database-related directories:

� \usr\sap

� \usr\sap\trans

� <homedirectory> of <sid>adm

� \<sid>data (might have multiple files)

The SAP R/3 database files

� \<sid>log

The SAP R/3 log file

Additionally, you should back up the following Microsoft SQL Serverdatabases:

� Master

In case of failures or hardware or software disasters, the Master databasecontains the data necessary to recover the database.

� MSDB

The MSDB database contains the data for the SQL Server job schedulerand the database backup history.

To make the backup process easier, and to reduce errors, we recommend thatyou backup the entire server and not just specific directories and files.

For SQL Server, see SAPNote 141118 for adescription of the tape

label naming convention used byDB13.

If the log is allowed togrow to capacity and useall available file space on

the drive, SQL Server will stop.This event is critical, becausewhen SAP R/3 stops, so does thebusiness processes that requireSAP R/3 to be running.

Note

There is no need to backup the \tempdbdirectory, because it will be rebuilt onserver cycling.


Online Backup — Using SQLserver 2000 Enterprise Manager

The SQL 2000 Enterprise manager is Microsoft SQL Server’s general tool. Inconjunction with the SAP R/3 system, it is used to backup the following whileSAP R/3 is running:

� The SAP R/3 database

� The SAP R/3 log

To clear the log, the log backup must periodically be done in the initializationmode.

You must also backup the following SQL Server databases:

� Master

If there is a hardware or software disaster, the master database containsthe data necessary to recover the database.

� MSDB

The MSDB database contains the data for the SQL Server job schedulerand the database backup history.

An online backup allows you to backup the databases when SAP R/3 and thedatabase are running, to reduce impact to system users.

Task

Backup your databases

1. On the Windows taskbar, choose Start → Programs → Microsoft SQL Server→ Enterprise Manager.

2. In the Enterprise Manager, expand the SQL Server Group under which yourserver is located. (You may have a different group name.)

3. Expand the server that you want to look at. (You will have a different servername.)

4. Choose Management.

5. Choose Backup.

If the log is allowed togrow to capacity and useall available file space on

the drive, SQL Server will stop.This event is critical, becausewhen SAP R/3 stops, so does thebusiness processes that requireSAP R/3 to be running.


6. On the toolbar, choose Tools → Backup Database.

7. In Database, choose the dropdown arrow to select the database to backup.

8. Under Backup, select the type of backup to perform (for example, Database -complete).

9. Under Destination:

a. Select the media (for example, Disk).

b. Select the device (for example, logdisk1).

10. Under Overwrite, select Overwrite existing media.

11. Choose the Options tab.

Note

Select Database – complete to do a fullbackup of the database. SelectTransaction log to backup only thetransaction log.

Note

To select another device as thedestination, choose Add → Backupdevice.


12. Under Options, select:

� Verify backup upon completion

� Backup set will expire

13. Under Backup set will expire, select one of the following options and completethe entry field:

a. After (a defined number of days), then enter the number of days.

b. On (a specific date), then enter the date.

On the screens below, you have three options:

� Backup without checking the tape label.

� Backup checking the tape label.

� Initialize the tape and writing a new tape label, before backing up.

Task

Backup without checking the tape label

1. Leave the following options deselected:

� Check media set name and backup set expiration

� Initialize and label media

This step will overwriteand destroy any data onthe tape. Be certain that

the correct tape is in the drive.


2. To begin the backup, choose OK.

Task

Check the tape label before backing up

1. Select Check media set name and backup set expiration.

2. Enter the tape label in Media set name (for example, RD26S).

3. To begin the backup, choose OK. If the label of the tape does not match thename entered in Media set name, the backup will fail.


Task

Initialize the tape before backing up

1. Select Initialize and label media.

2. Enter the tape label name in Media set name (for example, RD26S).

3. Choose OK to begin the backup.

Offline Backup — Using Windows 2000 Backup

The offline backup is done when SAP R/3 and the database are down. Theoffline backup also backs up other files that are needed to restore SAP R/3.Because high-capacity tape drives are now more common, it is simpler andsafer to backup the entire server. A full server backup eliminates thepossibility of missing an important file during a backup.

At a minimum, backing up SAP R/3 on SQL Server involves backing up thefollowing SAP- specific and database-related directories:

� \usr\sap

� \usr\sap\trans

� <homedirectory> of <sid>adm

� \<sid>data (the SAP R/3 database files)

� \<sid>log (the SAP R/3 log file)

In addition to these directories, you must back up any directories and files forthird-party products, interfaces, and so on that store data outside the SAPR/3 database. Because getting all the required files and directories can bedifficult, we recommend that you backup the entire server.

This step will relabel,overwrite, and destroyany data on the tape. Be

certain that the correct tape is inthe drive.

For smaller customers,the entire server could bebacked up to a single DLT

cartridge.


The data in the database does not change while the backup is being made,which means that you have a static picture of the database and do not have todeal with the issue of data changing while the backup is being run. With somethird-party applications, you cannot back up the files unless they are closed,and this is not possible unless SAP R/3 and the application are shut down.Therefore, an offline backup needs to be done. A full server offline backupalso gives you the most complete backup in the event of a catastrophicdisaster. One tape contains everything on the server.

To do an offline backup, we use Windows 2000 Backup interactively.

Task

Perform an offline backup

1. Shut down SAP R/3.

2. Shut down the database.

3. Shut down any other applications.

4. Insert the appropriate tape into drive.

5. On the Windows 2000 taskbar, choose Start → Programs → Accessories→System Tools → Backup.

6. Choose Backup.

7. Select the drive and the appropriate directories, (for example, C:) on theserver.

Due to system limitationson the documentationsystem, the location of

the files in this example ispresented differently from therecommendations in the SAPinstallation manual.


8. Choose Start Backup.

9. In the Backup Job Information dialog box:

a. In Backup description, enter a description.

b. Under If the media …, select Replace the data on the media with this backup.

c. In If the media is …, enter the same description as in step 8.

d. Choose Advanced.


10. In the Advanced Backup Options dialog box:

a. Select Verify data after backup.

b. If your tape drive supports hardware compression, select If possible,compress … space.

c. Under Backup Type, select Normal.

d. Choose OK.

11. The backup will run. The Selection Information dialog box displays the backupprogress.

12. The Replace Data dialog box appears to verify that the correct tape is in thedrive. Even if the tape name you entered in the previous screen matches thetape label, this window will appear.

13. Choose Yes.


14. The Backup Progress dialog box displays the backup progress. Depending onthe size of the database, the backup may run for a period of time.

15. When the backup has successfully completed, choose Close.

16. From the menu bar, choose Job → Exit.


17. Remove the tape from the tape drive and store properly.

Viewing Database Error Logs

SAP R/3 — Database Performance Analysis (ST04)

You can view the database error logs from within SAP R/3 using transactionST04. For more information on database error logs, see the DatabasePerformance Analysis (ST04) section earlier in this chapter.

Task

Perform database analysis using Microsoft SQL Server 2000 - Enterprise Manager

1. From the NT desktop, choose Start → Programs → Microsoft SQL Server →Enterprise Manager.


2. In the Enterprise Manager:

a. Expand the SQL Server Group under which your server is located.

b. Expand the server where the SAP R/3 system is installed.

c. Expand Management.

d. Expand the SQL Server Logs.

3. Select the Current log. You can also look at the six previous error logs.

4. Read the log in the right frame.


Verify Database Consistency

In a database management system, consistency can be represented from thelogical and physical levels. SAP R/3 must ensure a logical consistency whencommunicating with the SQL Server engine, and SQL Server must ensure aphysical consistency for the database.

Sometimes a physical inconsistency can occur in the database’s internalstructures. This problem occurs when SAP R/3 and the database show thesame piece of data in different locations.

SQL Server uses the DBCC CHECKDB command to correct and repair thedatabase to a consistent state. This is executed using:

� CCMS Scheduling calendar (transaction DB13)

� The SQL Server Enterprise Manager

The consistency checks should be done during non-peak hours or when SAPR/3 users are offline.

Run Update Statistics

Database objects statistics help make data access more efficient. The optimizerof the database engine will perform better if the table index’s statisticalinformation is current. This information helps SAP R/3 find an item in thedatabase faster.

By default, SQL Server 2000 has automatic statistics turned on. The possibilityof manually scheduling update statistics using the CCMS scheduling calendarstill exists. This scheduling might be necessary after large data insertions ordeletions from a given table (for example, client copy, BDC sessions, andarchiving).

System Passwords

SQL server

For additional information, see SAP Note 28893.

User IDs to change:

� sa

� sapr3

Note

NOTE: For those coming from SQLServer 7.0 environments, SQL Server2000 executes the DBCC CHECKDBjob much faster than SQL Server 7.0.


Task

Change passwords in SQL Server

1. From the NT desktop, choose Start → Programs → Microsoft SQL Server 2000→ Enterprise Manager.

2. In the SQL server Enterprise Manager:

a. Expand the SQL Server Group.

b. Expand the server.

c. Expand Security.

d. Choose Logins.

3. On the right side of the screen, double-click sa (or sapr3, if sapr3 was created).

4. Choose the General tab.

During the installation, bydefault:

�SQL server does notask for or set a password foruser sa. Once theinstallation is complete, thesystem administrator mustmanually create apassword.

� For user sapr3, a defaultpassword is created. Youmust change the password.Beginning with release 4.5,user sapr3 is no longer usedby SAP R/3.

These loopholes must be closedmanually.


5. In Password, enter a new password.

6. Choose OK.

7. Reenter the password in Confirm New Password.

8. Choose OK.

9. For user sapr3, up through release 4.0, in the SQL Server Enterprise ManagerConsole, choose Tools → SQL Query Analyzer.


10. Enter the following SQL commands:

use <SAPSID>

go

sap_change_password

‘<OLD_PASSWD>’,

‘<NEW_PASSWD>’

11. Choose Execute Query (or choose Query → Execute Query).

C H A P T E R

11

11Database Administration —

Informix


Overview

This chapter describes SAP database administration for Informix. You learnabout routine administration tasks to help ensure that the database runssmoothly. You can perform database administration tasks for Informix:

� In the SAP R/3 system

� Using SAPDBA

We recommend that you use the SAP R/3 system to schedule tasks forregular execution. However, the database must be up and running for you touse the SAP R/3 system. Certain tasks – such as starting and stopping thedatabase server – must be performed using SAPDBA, which does not requirethe database to be running. Additionally, certain tasks – such as extending adbspace – can only be performed with SAPDBA.

Scheduling Database Tasks

Many Informix database tasks can be scheduled in the SAP R/3 system usingthe DBA Planning Calendar. Tasks are automatically executed at user-specified intervals. You must only meet any requirements for the tasks (suchas providing tapes for a backup) and check the results.

Initializing the DBA Planning Calendar

Before you can use the DBA Planning Calendar with the Informix backup toolON-Bar, you must do a one-time conversion.

Task

Initialize the DBA Planning Calendar

1. In the Command field, enter transaction SE37 and choose .

2. In Function module, enter INFDBA_SWITCH_TOOL.

Example

You can specify a database backup to run every evening at 22:00. You only need schedule thebackup once. After that, all you need do is to make sure the tapes are loaded and then checkthe results the following morning.

Note

You normally only need run thisconversion once after databaseinstallation.

Chapter 11: Database Administration – Informix 311

3. To run the conversion, choose .

4. On the Test Function Module: Initial Screen, to perform the conversion, choose.

5. To check the conversion, in the Command field, enter transaction DB13 andchoose .

6. The DBA Planning Calendar (onbar) screen appears, indicating that the DBAPlanning Calendar is now set to onbar.If you see DBA Planning

Calendar (onarchive),run the conversion again

to set the calendar to onbar.


Scheduling a DBA Task to Run Regularly

This section tells you how to schedule a new DBA task to run regularly, forexample, weekly.

Task

Schedule a DBA task to run regularly

1. In the Command field, enter transaction DB13 and choose .

2. Select the day on which you want to run the action (for example, Thu Sep 06).

3. Choose .

4. Select the task you want to perform. This example shows a Databaseconfiguration check.

5. In StartTime, enter the start time.

6. To have the task executed weekly (for example), in Period, enter 1.

7. Choose .

Note

The current day, Tue Sep 04 in thisexample, is shown by default in white.

Note

This date already has a scheduled taskat 23:00, WS BU (Inc).

If you want the taskexecuted only once,leave Period empty.


8. The new task, 22:00 DB Check, is created on the chosen day and weeklythereafter.

9. A New action added message is displayed at the bottom of the screen.

Checking the Status of DBA Tasks

This section tells you how to check the status of a DBA task using the DBAPlanning Calendar. For example, you can use this to check whether a task hascompleted successfully.

Task

Check the status of DBA tasks


2. The tasks are color-coded. For example, tasks marked in red did not completesuccessfully.


3. Double-click the day header to review the completed or scheduled tasks forthe day. The example shows a completed task from a previous day, Sun Sep02.

4. Select the action you are interested in and choose Action logs to check theaction log.

5. The system displays the action log for the Database configuration check.

6. Choose .

7. To display the job log for the task, choose Job Logs. The system displays thejob log list.

Note

Some tasks, such as the first one in thisexample, do not have action logs. In thiscase, the Logs box is not checked.

Note

The format of the action log variesaccording to the action.


8. To see the contents of the log, select the log and choose .

9. This screen shows the contents of the job log.

Changing DBA Tasks

For any task that has not yet been executed, you can change the taskparameters or delete the task.

Task

Modify DBA tasks


2. On the DBA Planning Calendar (onbar) screen, double-click the day header toreview the scheduled tasks for a day, either today or a future day. Thisexample uses Sun Sep 09.

3. To change an action, select the action and choose . This example usesUpdate optimizer statistics (all tables). State SCHED means that the action isscheduled to run at the StartTime 01:00.


4. Select different parameters for the action, then choose .

5. Select different parameters for the action, then choose .


Backing Up the Database

This section discusses backing up the Informix database by schedulingbackup tasks in the DBA Planning Calendar. The backup tool we use is ON-Bar. You must back up the following data on your Informix database:

� Database data – that is, mainly data in the dbspaces of the database

� Logical-log data – that is, ongoing transaction data

The following procedures show you how to schedule a weekly whole-systembackup plus incremental backups on the remaining days of the week. Finally,we show you how to start a continuous logical-log backup.

If your database crashes, you can restore the database using the whole-systembackup (which restores the database to a consistent state). You can then rollthe database forward to the point of failure using the incremental backupsand the logical logs.

Requirements for Backing Up the Database

Before you start to back up database data or logical-log data, install andconfigure a storage manager, such as Informix Storage Manager (ISM). Ifpossible, use separate storage devices for database and logical-log data.Ensure that the storage devices in the ONCONFIG file are not set to /nul(Windows) or /dev/null (UNIX). Make sure that you have the correct tapesmounted on the correct tape devices and that there is enough space availableto complete the backup. Perform a physical consistency check from time totime before a whole-system backup.

Scheduling Backups of Database Data

This procedure shows you how to schedule the following database backupsin the DBA Planning Calendar:

� Whole-system backups once a week (on Saturday in the example)

� Incremental backups once a day on the remaining six days of the week

Task

Schedule database backups


2. Select the day on which you want to run whole-system backups.

Write essential information on your tapes, such as the date and time of backup to ease yourrestore process. Also, keep tapes for the length of your backup cycle (for example, 28 days)before overwriting them.

Be sure to back up thedata in your Informixdatabase regularly,

preferably daily. Otherwise, yourisk losing data and endangeringyour business. Follow theprocedures below carefully so thatyou can recover your database inthe event of failure.

Tips & Tricks

Keep backups for at least28 days beforeoverwriting them. You

can restore the database to thestate it was in during the previous28 days, which might benecessary in the event of anapplication error.


3. Choose .

4. On the Create a New Action dialog box:

a. Select Whole system backup (serial).

b. In StartTime, enter the time to start (for example, 20:00).

c. In Period, enter a number (for example, 1). This means that the backup isrepeated weekly at the same time.

d. Choose to schedule the action.

5. The new task, 22:00 WS BU L0, is created on the chosen day and weeklythereafter.

6. Select the day on which you want to run incremental backups.

7. Choose .

Note

We recommend that you runincremental backups on the remainingsix days of the week, that is, Sundaythrough Friday. Therefore, you have toperform the remainder of this procedureonce for each day.


8. On the Create a New Action dialog box:

a. Select Incremental whole system backup (serial).

b. In StartTime, enter 23:00.

c. In Period, enter 1 (this means that the backup is repeated weekly at thesame time).

d. To schedule the action, choose .

9. On the Database Backup Level dialog box:

a. Select Incremental (level 1).

b. Choose .


10. The new task, 23:00 WS BU (Inc), is created on the chosen day and weeklythereafter.

11. The following screenshot shows how the calendar looks after you havescheduled all the required backups:

� On Sunday through Friday, there is an incremental backup scheduled:23:00 WS BU (Inc)

� On Saturday, there is a whole system backup scheduled:20:00 WS BU L0

� All backups are repeated weekly.


Backing Up Logical Log Data

A continuous logical log backup means that the logical-logs are backed up assoon as they fill. When you back up logical log data (in addition to databasedata), you have the best protection against database failure because thismeans that you can restore data right up to the point of failure.

Task

Back up logical log data

1. Using your normal text editor, open the ONCONFIG file, located in thedirectory %INFORMIXDIR%\etc (Windows) or $INFORMIXDIR/etc(UNIX).

2. Amend the line with ALARMPROGRAM so that it looks as follows:� ALARMPROGRAM = %INFORMIXDIR%\log_full.sh(Windows)

� ALARMPROGRAM = $INFORMIXDIR/log_full.sh(UNIX)

3. Restart the database server for the changes to take effect.

4. Make sure that the tape drive always contains a tape with sufficient space tostore the logical log data.

After you have processed this change, when the database starts, continuouslogical log backup is activated. Each logical log is automatically backed up assoon as it fills.

Checking the Database System

We recommend that you run a database check regularly, because it warns youof situations that might cause database operational problems, and allow youto take preventative action.

For example, the database check highlights incorrect configuration settingsand lack of disk space. These issues might lead to performance problems oreven downtime if not corrected promptly.

Task

Schedule a database check


2. Select the day on which you want to run the database check.

3. Choose .


4. On the Create a New Action for <XXXXX> dialog box:

a. Select Database configuration check.

b. In StartTime, enter 18:00.

c. In Period, enter 1 ( the check is repeated weekly at the same time).

d. Choose .

5. The new task, 18:00 DB Check, is created on the chosen day and weeklythereafter.

Task

View the results of a database check



2. Double-click the entry for the database check that you want to look at. In thisexample, we look at the entry for 22:00 DB Check on Sun Sep 02.

3. The log for the database check appears.

4. Drill down to look at details for the marked <Error> or <Warning>.

5. This example shows the error message for the LTAPEDEV parameter, whichis set incorrectly.

6. Follow the recommendation to fix the problem.

Note

This entry is highlighted, indicating thatan error has occurred.

To find more informationif there is a problem withthe database, look at the

message log. See "Viewing theDatabase Message Log" below.


Viewing the Database Message Log

If there is a problem with the database – for example, an alert generated bythe database check – you can use the database message log to help you solvethe problem.

Task

View the database message log

1. In the Command field, enter transaction ST04 and choose .

2. Choose Detail Analysis Menu.


3. On the Database Performance Analysis: INFORMIX Database Overview screen,under Analyze exceptional conditions, choose Database Message Log.

4. On the Database Messages dialog box:

a. Depending on what kind of messages you want to view, select either Onlyalerts or All messages.

b. Choose Display.

5. The Database Messages screen appears, displaying details of the databasealerts. Scroll down to see the most recent entries.


Updating Statistics

We recommend you update statistics regularly (for example, weekly) toimprove database performance. Up-to-date statistics mean that the queryoptimizer can choose the best query plan, reducing the time taken by yourSAP applications to access data.

Task

Update statistics


2. Select the day on which you want to run update statistics.

3. Choose .


a. Select Update optimizer statistics (all tables).

b. In the StartTime, enter the time to start the job (for example, 01:00:00).

c. To have the task executed weekly, in Period, enter 1.

d. Choose .If you want the taskexecuted only once,leave Period empty.


5. On the Parameters for Update Statistics dialog box:

a. If required, change the parameters. However, the default values areusually acceptable.

b. Choose .

6. The new task, 01:00 Update sta, is created on the chosen day and weeklythereafter.

Checking Database Consistency

Database consistency should be checked on occasion (for example, once amonth) before a full system backup. This check ensures that the backupcontains valid data, so it can be reliably used in the event of a restore.


Task

Check database consistency


2. Select the day on which you want to run the consistency check.

3. Choose .


a. Select Physical consistency check.

b. In StartTime, enter the start time (for example, 18:00:00).

c. In Period, enter the period in number of weeks (for example, to executethe task every four weeks, enter 4).

d. Choose .


a. Select for all tables of database.

b. Choose .

If you want the taskexecuted only once,leave Period empty.


6. The new task, Cons. Check is scheduled on the chosen day and every fourweeks thereafter.

Checking Database Disk Space

By regularly checking database disk space, you ensure that the database doesnot run out of space. If the database runs out of space, it stops and normaloperation cannot continue until you have provided more space.

Task

Check database disk space

1. In the Command field, enter transaction ST04 and choose .


2. On the Database Performance Analysis: INFORMIX Database Overview screen,choose Detail Analysis Menu.

3. On the Database Performance Analysis: INFORMIX Database Overview screen,under Additional functions, choose State on disk.

Note

This screen can also be called fromtransaction DB02.


4. On the Database Performance: Tables screen, under Tables/Indexes, chooseSpace-critical objects.


5. The screenshot shows that objects in the psapprot dbspace require more space.If one of these objects needs extending, there is not enough space in thedbspace. In the column Next extent, each object requires 10,240 KB for a newextent. However, there is only 9,230 KB available, as shown in columnFreespace in Dbspace, Total.

6. Be sure to extend the psapprot dbspace as soon as possible. For moreinformation on how to do this, see “Extending a Dbspace” on page 337.

We recommend you toschedule the databasecheck for regular

execution in order to identifyspace problems early. However, ifyou are loading a large amount ofdata, or if you suspect a spaceproblem, we recommend you touse this one-off procedure.

Note

The database check procedure also alerts you to space problems. Here is a warning from thedatabase check that the psapprot dbspace needs extending.

For more information on how to check the database system, see “Checking the DatabaseSystem” on page 321.


Using SAPDBA

This section describes how you can use SAPDBA to administer your Informixdatabase.

What is SAPDBA?

SAPDBA is an integrated database administration tool for Informix databasesrunning with SAP systems. You can use it without detailed knowledge of thedatabase and its tools. SAPDBA filters information about the database,showing you only what you need, and uses complex database statements tolet you confidently manipulate the data while ensuring security and integrity.SAPDBA offers a character-based menu interface and a command line mode.

You can perform the following database administration tasks with SAPDBA:

� Change server mode (that is, start and stop the database)

� Administer dbspaces

� Reorganize the database

� Check database consistency

� Update statistics

� Change logging mode

� Check the database system

� View system information

Where possible, we recommend you to perform database administration in the SAP system.This is because you can use the DBA Planning Calendar in the SAP system to schedule manyroutine tasks – such as database backup – for automatic execution. In addition, the SAP systemoffers a modern graphic user interface (GUI) for easy operation.

Tips & Tricks

Some of the above tasks – such as database reorganization – require considerable experience.If you are uncertain about these tasks, seek support before attempting to perform them. We donot explain the full functionality of SAPDBA in this documentation.

Use SAPDBA in menumode, unless you areexperienced.

Caution


Getting Started with SAPDBA

SAPDBA is set up to run with the users informix and <sid>adm, where <sid>is your system ID in lowercase. For these users, the required environmentvariables are set during the installation.

Task

Start SAPDBA

1. Log on to the database server as user informix (for example, su informix).

2. On the command line, enter sapdba.

3. The SAPDBA start screen appears.


The following task shows you how to start and stop the database usingsapdba.

Task

Start and stop the database using sapdba

1. Log on to the database server as the user informix or <sid>adm.

2. To start SAPDBA, enter sapdba.

Note

Certain advanced SAPDBA functions are not available if you log on as user <sid>adm. Forfull functionality, log on as user informix.

You can log on to thedatabase server using aremote session – for

example, with Telnet (UNIX) orpcAnywhere (Windows).

The top of the screendisplays useful statusinformation about the

database server, such as ServerMode and the number of 'sapr3'User(s) logged on.


3. The SAPDBA start screen appears. In this example, the database server is inOFFLINE mode.

4. Choose Server Mode.

5. Choose Switch to Online Mode.


6. The server switches to online mode.

7. The server is in ONLINE mode. You can now start the SAP System.

8. The screen displays the number of SAP users connected (1 user, the SAPDBAuser).

9. You can also see that Logging Mode is turned on.

10. To stop the database server, choose Server Mode.

11. Choose Switch to Offline Mode.

Before stopping thedatabase, make sure thatall users are

disconnected. Also be sure to stopthe SAP R/3 system. If there arestill users connected to thedatabase or the SAP System isstill running, SAPDBA warns youwith a message


12. The server switches to offline mode.

Extending a Dbspace

This section describes how to make extra disk space available for databasedata. The database consists of dbspaces that contain the data. You must makesure that there is always enough space in the dbspaces to extend databaseobjects, such as tables, that are growing due to new data. As they grow,database objects within the dbspaces are extended automatically, but youmust extend the dbspaces yourself when required.

Task

Extending a dbspace

1. Log on to the database server as the user informix.

2. To start SAPDBA, enter sapdba.

Note

You can identify when a dbspace needs extending using either of the following procedures:

� Checking disk space, as described in "Checking Database Disk Space" above.

� Checking the database system, as described in "Checking the Database System"above. One of the alerts produced by this check indicates when a dbspace is runningout of space.

You do not need to stop the database server to extend a dbspace.

Note

You cannot extend a dbspace as user<sid>adm.


3. Choose Dbspaces.

4. Choose Add a Chunk.

5. Choose a.

6. In Dbspace, enter the dbspace name (for example, psapprot).

7. Choose Enter.


8. Choose s.

9. Choose a.

10. In Size, enter the size of the new chunk.

11. Choose Enter.

12. Choose Select 'primary' gap to find a physical gap on the device for the newchunk.

13. Select a gap with enough space for the new chunk (for example, 2).


14. Choose Enter.

15. Choose Execute to add the new chunk.

16. The message tells you that the new chunk has been added to the psapprotdbspace.


17. Choose o.

Further Information

More information about database administration with Informix can be foundat the following web sites:

� www.service.sap.com/dbainf

� www.informix.com/documentation

For support information about Informix with SAP, see service.sap.com/notes.For information on Informix database administration relating to, for example,SAP Release 4.6C, enter the following search criteria and choose Submit:

Release: 46c; Application Area: bc-db-inf; Database: Informix

C H A P T E R

12

12Database Administration — Oracle

Database


Overview

The Oracle Relational Database has the ability to support large databases. Theamount of work involved in managing the Oracle database largely dependson the size and the workload. Despite the complexity of the database, SAPsupplies several database administration tools in the standard SAP Systempackage to help you manage the database more easily.

The database administration tasks discussed in this chapter are those notcovered in other sections.



Task

Start the database

1. To start the SAPDBA:

a. Log on as user ora<sid> (for example, su – oraarc).

b. At the command prompt, enter sapdba and choose Enter.

Note

The SAPDBA discussed in this chapter is documented on Unix platform. The NT version issimilar.

Press the Enter key each time the program asks you to Press <return> to continue.

The database should be started before SAP R/3 is started and the SAP R/3 should be stoppedbefore the database is stopped.

Chapter 12: Database Administration – Oracle Database 345

2. On the SAPDBA screen:

a. In Please select, enter a startup or shutdown instance.

b. Choose Enter.

3. In Please select, enter a and choose Enter.



5. Choose Enter.

6. The INSTANCE STATUS of open indicates that the database has been started.


7. In Please select, enter q and choose Enter.

8. To return to the main SAPDBA menu screen, in Please select, enter q andpress Enter.

Task

Stop the database

1. Stop SAP R/3.

2. From the main SAPDBA screen, in Please select, enter a and choose Enter.To stop SAP R/3, youmust log on as user<sid>adm. In this

example, enter su – arcadmand stopsap to stop SAP R/3.Enter exit to switch back touser ora<sid> to start theSAPDBA administration tool.


3. In Please select, enter b and choose Enter.



5. Choose Enter.

6. The INSTANCE STATUS indicates that it has been shut down.


8. In Please select, enter q and choose Enter to return you to the main SAPDBAmenu screen.

Computing Center Management System (CCMS)

The Computing Center Management System (CCMS) has tools available forSAP R/3 administrators to monitor and maintain the database. This sectionwill discuss the transactions that are available for SAP R/3 administrators toperform database administration from within the SAP R/3 system.


The database administration tools within CCMS include:

� Database Performance Monitoring

� Database Tables and Indexes (Allocation)

� The DBA Planning Calendar

� Backup Status Logs

� Database Alert Monitor

� Others

To simplify the administration of the SAP R/3 system, SAP has built indatabase administration tasks into the CCMS framework. This enables theSAP R/3 administrator to perform routine system tasks from one locationfrom within the SAP R/3 system.

Database Performance Monitor

The Database Performance Monitor (transaction ST04) assists you inmonitoring the health of your database server.

Task

Monitor database activity

1. In the Command field, enter transaction ST04 and choose Enter (or chooseTools → CCMS → Control/Monitoring → Performance Menu → Database →Activity).

2. The Database Performance Analysis: Oracle Database Overview screen appears.

Note

Some DBA functions can only beperformed outside of the SAP R/3system. In theses cases, you must usean external tool supplied by thedatabase manufacturer or a productrecommended or designed by SAP (forexample, SAPDBA).


3. Choose Detail analysis menu.

Data buffer

� The data buffer contains the Oracledata blocks in shared memory. On aproduction system, SAPrecommmends that you maintain adata buffer quality of at least 97%.

Shared Pool

� The shared pool holds severalmemory structures, such as the datadictionary cache and the shared SQLstatements.

Log buffer

� The log buffer contains informationabout changes being made to thedatabase before the bufferinformation is written to the redo logfiles.

Calls

� Calls display the number and type ofcalls that the SAP processes requestto the Oracle database.


4. The Database Performance Analysis: Oracle Database Overview screen appears.

5. Choose Database message log.

6. On the Database Messages dialog box:

a. Select the Only alerts option.

b. Choose Display.

Oracle session

� This monitor displays informationabout the various databaseprocesses and the SAP R/3 workprocesses associated to the session.

SQL request

� This monitor provides an analysis ofthe shared cursor cache used forperformance tuning.

Exclusive lock waits

� This function analyzes if a process isexclusively holding a lock, causingother processes to lock while waitingfor the held resource.

Database message log

� This log displays the Oracle alert log,alert_<SID>.log.


7. The Database Messages screen appears. The log displays all messages writtento the Oracle alert log. To monitor for problems with the database, you cansearch for the errors that are generated and written to the log. The errors aretypically displayed with a referencing Oracle error message number (ORA-XXXX).

Database Tables and Indexes Analysis

The database performance monitor performs extensive checks on thedatabase system and stores this information into database statistics tablesused for analysis. SAP R/3 administrators can utilize this resource to monitorand analyze the system for potential database problems.

Administrators should routinely use the performance monitor for thefollowing tasks:

� Checking for space-critical objects

� Looking for lost indexes

� Analyzing database growth

Task

Analyze database allocation

1. In the Command field, enter transaction DB02 and choose Enter (or chooseTools → Administration → Monitor → Performance → Database →Tables/Indexes).


2. On the Database Performance: Tables and Indexes screen:

a. If the time of the analysis is out of date, you must first refresh the data andcall the performance collector to publish new information.

b. Choose Refresh.

3. On the Refresh Database Statistics dialog box, choose Perform database checks.

4. To refresh the database statistics, choose Yes. The report RSORAT0D isscheduled to run in the background.

Refresh button


Scheduling Database Tasks (DB13)

The DBA Planning Calendar can be used to schedule and execute certaindatabase administration (DBA) tasks, such as backups, updating statistics forthe cost-based optimizer, database system checks, and so on.

Scheduling the DBA task

The following tasks shows you how to schedule a DBA task.

Task

Schedule a DBA task

1. In the Command field, enter transaction DB13 and choose Enter (or chooseTools → CCMS, then DB Administration → DBA Planning Calendar).

2. On the DBA Planning Calendar: Maintain screen:

a. Select a date (for example, Monday August 28).

b. Choose Create.

3. On the Schedule an Action for <XXXXX> dialog box:

a. Select the task you want to perform (for example, Check database).

b. Enter the start time in StartTime.


c. Choose .

4. The task is created in the day and the Action scheduled message displays in thestatus bar.

Scheduling Predefined Action Patterns

An action pattern implements a backup strategy and other databaseadministration activities that must be regularly performed. Once you choose apredefined action pattern, the system adds the corresponding activities to theDBA Planning Calendar, and plans the background jobs that will execute theactivities.

Using a predefined action pattern ensures that you are following the SAPstandards for database activities, and also provides an easy alternative tomanually setting up the backup schedules.

Note

To schedule a backup task, the backupmust be able to run unattended. Thismeans that you must have a tape drivewith sufficient capacity to back up thedatabase without changing tapes, ormultiple tape drives with sufficient totalcapacity.

Note

If you use an external backup solution tomanage the backup of the databasethese predefined action patterns maynot apply to your environment.


Task

Schedule a predefined action pattern


2. On the DBA Planning Calendar: Maintain screen, choose Calendar → ActionPattern.

3. On the Schedule an Action Pattern dialog box:

a. Select the appropriate backup cycle.

b. Choose Enter.

Task

Review the DBA Planning Calendar


2. On the DBA Planning Calendar screen:

a. Review the scheduled tasks for the day. The color of the task indicatesstatus:

• Red – Failure

• Yellow – Problem/warning

• Green – Success

• Purple – Started


b. If there are more jobs than can be displayed, a scroll bar appears.

c. Select a task.

d. Choose Job logs.

3. On the Job Logs screen:

a. Select the job.

b. Choose Display log.

4. On the Job Log screen:

a. Choose .

b. Choose .


5. On the DBA Planning Calendar screen:

a. Select the job.

b. Choose Action logs.

6. Choose Detail log.

7. The SAPDBA Detail Log screen displays the detail log for the job. In thisexample, the log from the DB System Check is displayed.


The Database Utility

The database utility is the interface between the ABAP Dictionary and therelational database underlying the SAP R/3 system. The database utilityallows you to edit database objects that are generated from objects of theABAP Dictionary.

This utility allows the database administrator more flexibility in managingand controlling database-related objects. By including this into the SAP R/3system, this centralizes maintenance of database objects to within the SAPR/3 system.

Storage parameters can be set for database tables using the Database Utility.These parameters affect the way in which tables are handled in the database.As the database grows and the tables are extended, the storage parameters ofthese tables may need to be modified.

Task

Modify storage parameters


2. On the ABAP Dictionary: Database Utility screen:

a. In Obj. name, enter an object name to be modified (for example, S120).This is usually reported from the SAPDBA –check report or fromanalyzing the tables and indexes report.

b. Choose Edit.


3. On the ABAP Dictionary: Utility for Database Tables screen, to view andmodify the storage parameters for this table, choose Storage parameters.

4. Information about the storage parameters for the table is displayed.Additional information about the indexes that access this table is alsodisplayed.

5. To switch to change mode, choose .


6. Modify the parameters, NEXT EXTENT and MAXIMUM EXTENTS asappropriate.

7. Administrators have different policies of how they modify database storageparameters, though as a rule of thumb SAP recommends that you provideenough storage space to allow the object to take no more than 2 extents amonth.

8. To apply the changes to the database, choose Apply.


9. A message appears in the taskbar to confirm that changes were applied to thedatabase.

SAPDBA

SAPDBA is a tool that SAP created to assist the user in managing an Oracledatabase specifically for an SAP installation. SAPDBA is supported on bothUNIX and Windows NT platforms.

SAPDBA’s uses include:

� Start and stop the database


� Back up the archive logs

� Restore the database

� Reorganize tables

� Check the database

� Other

Note

SAPDBA is also available for Informix.


Database tasks specific to SAP have been implemented in SAPDBA. SAPDBAtasks specific to backups are discussed in “Backup” on page 37.

SAPDBA’s parameter file init<SID>.sap is important. This file should beconfigured as part of the implementation. If things change (such asreplacing a tape drive), you may need to modify the file.

Task

Set the parameter file

1. Open the file init <SID>.sap using a text editor.

NT: use sappad<drive>:\orant\database

UNIX: use vi/oracle/<sid>/dbs

This file contains the system parameters that configure the database.

2. Edit the parameters as appropriate.

3. You can reference SAP Note 124361 for SAP recommendations for Oracle DBparameters for SAP R/3 release 4.x.

Some other parameter files that control the database operation are:

� init<sid>.dba

These parameters describe the values that are defined for use by the SAPDBAutility.

� init<sid>.sap

Note

The init<sid>.ora file is a very important file for the correct functioning of the database andshould be frequently backed up.


These parameters describe the values that are defined for use by the SAPbackup utility.

Task

Start SAPDBA

1. To start SAPDBA, in a Telnet application, log on as user ora<sid> (forexample, su – oraarc).

2. At the Command prompt, enter sapdba and press Enter.

3. The main SAPDBA screen appears.


Checking the Database

There are two database checks—database system check and databaseverification. The database system check performs a system health check,which monitors the following:

� Space is checked (free space and fragmentation)

� Oracle alert messages are monitored

� init.ora profile parameters are checked

� Physical consistency is checked

The database verification checks the Oracle database internal block structure.

Checking the Database System

Ensure that the database is running. Also, update to the latest version ofSAPDBA and the related BR files (BRARCHIVE, BRBACKUP,BRCONNECT, BRRESTORE, and BRTOOLS). Note that the checking of thedatabase system can also be scheduled using the DBA Planning Calendar(DB13) to check the database structure.

Task

Check the database

1. On the main SAPDBA screen, in Please select, enter k and choose Enter.



3. A list of database checks to be performed appears. Once you have read themessage, choose Enter. This step may occurs many times.

4. When requested, enter y and choose Enter to start the check process.

5. When requested, choose Enter to continue the check process. This step occursmany times.

6. When the check completes, choose Enter.


7. To return to the main SAPDBA screen, enter q and choose Enter.

8. The log from the verification run is found in:

NT: <drive>:\oracle\<sid>\sapcheck

UNIX:/oracle/<sid>/sapcheck

The filename is in the following format:

YYMMDDHHMM.chk


9. You can view log file in a text editor, such as Notepad in the screenshotbelow.

Database Verification

Database verification checks the Oracle internal block structure. Ensure thatSAP R/3 is stopped and that the database is running.

Task

Verify the database

1. On the main SAPDBA screen, in Please select, enter k and choose Enter.



3. In Please select, enter s and choose Enter.

4. When the job finishes, press Enter.

5. Check the verification log.The log from the verification run is found in:

NT:<drive>:\oracle\<sid>\sapcheck

UNIX:/oracle/<sid>/sapcheck


The filename is in the following format:

YYMMDDHHMM.dbv

6. The file can be viewed with a text editor, such as Notepad below.

SAPDBA Backup Tasks

SAPDBA is a tool provided by SAP to perform Oracle databaseadministration tasks, such as setting the parameter file, initializing backuptapes, and performing backups of the database and archive logs.

Initializing the Backup Tapes

Initializing the Database Backup (BRBACKUP) Tape

Backup tape initialization can be done using SAPDBA, or using BRBACKUP.

Task

Using SAPDBA to initialize a database backup tape

1. Log on as user ora<sid> (for example, su - arcadm).

2. At the Command prompt, enter SAPDBA and choose Enter.


3. In Please select, enter h and choose Enter.




7. Note the description on the line Backup function showing InitializeBRBACKUP tape.

8. If you only have one tape to initialize, go to step 11. If you have more thanone tape to initialize, in Please select, enter d and choose Enter.


9. Enter the number of tapes to initialize and choose Enter.

10. The number of tapes to initialize should appear on the line d – Number oftapes.

11. In Please select prompt, enter s and choose Enter.

12. When the program prompts Your reply, enter cont to continue.

13. Press Enter.

Volume name used by BRBACKUP toinitialize tape (from init<SID>.sap file)

Initialization completion


Task

Use BRBACKUP to initialize a database backup tape

1. To force tape initialization, at the Command prompt, enter brbackup –iforce –n 1 –v <volname>

2. When the program prompts Your reply, enter cont to continue and chooseEnter.

3. When initialization has finished successfully, the message BRBACKUPterminated successfully displays.

4. Remove the tape from the drive and label it matching the specified name.

Initializing the Archive Tape

Archive tape initialization can be done using SAPDBA or usingBRARCHIVE.

Note

–n (Number of tapes parameter) is required to initialize a pool of tapes.

–v <volname> (Volume name parameter) is optional. Use this option only if you must initializea tape with a specific volume name (for example, when replacing a damaged tape). If –v<volname> is omitted, the command will use the name table in the init<SID>.sap file.

The entry cont is case-sensitive.


Task

Initialize an archive tape using SAPDBA


2. In Please select, enter i and choose Enter.

3. In Please select, enter a (Archive function) and choose Enter.

4. In Please select, enter k and choose Enter.



6. Note the message to the right of Archive function, showing InitializeBRARCHIVE tape. The number of tape to be initialized can be changed in thesame way as BRBACKUP.

7. To change the number of tapes to be initialized:

a. In Please select, enter d and choose Enter.

b. Enter the number of tapes to initialize and choose Enter.

8. To start BRARCHIVE, in Please select, enter s and choose Enter.

9. When the initialization finishes, the message BRARCHIVE executedsuccessfully displays.

10. Remove the tape and label it to match the label name.


11. Choose Enter.

Task

Initialize an archive tape using BRARCHIVE

1. Log on as user ora<sid> (for example, su – oraarc).

2. At the Command prompt enter brarchive –i force –n 1 –v <volname>

Initializing parameters are the same as for BRBACKUP. For moreinformation, see “Use BRBACKUP to initialize a database backup tape” onpage 374.

3. When the program prompts Your reply, enter cont to continue.

4. Choose Enter.

5. When initialization has finished successfully, the message BRBACKUPterminated successfully displays.

6. Remove the tape from the drive and label it matching the initialized label.


Back Up

To back up both the database and archive logs:

� Determine the tapes required to do the backup.

� Gather the required tapes.

� Load the tape drive with the tapes.

� Execute the appropriate backup process.

Determining the Tapes Required to Back Up

The following process applies to both database and archive log backups usingSAPDBA, BRBACKUP, or BRARCHIVE.

Task

Determine the tapes required to back up

1. At the command prompt:

� For database, enter brbackup –q and choose Enter.

� For archive logs, enter brarchive –q and choose Enter.

2. The volume labels that will be used are displayed (in this example, SAOB04and SAOB01).]

Backing Up the Database

For an offline backup, stop SAP R/3. Also, make sure you have the required,initialized and labeled, tape(s) as specified by brbackup –q.

We will use SAPDBA to perform the backup. SAPDBA executes BRBACKUPto perform the backup. BRBACKUP can be executed directly, which allows itto be executed by a cron job and scheduled.


Task

Back up the database

1. Log on as user ora<sid> (for example, su – oraarc).


3. In Please select, enter h and choose Enter.

4. Verify that Normal backup appears on Backup function.

5. Review line e (Backup type) to determine what type of backup is configured,online or offline.


6. If the type of backup needs to be changed, in Please select, enter e and chooseEnter.

7. From this screen, you have two options:

� a (online backup)

� b (offline backup)

8. In Please select, enter your option choice (for example, b) and choose Enter.

9. In Please select, enter q (Return) and choose Enter.

10. In Please select, enter f and choose Enter.

11. Enter the volume name of the taped used to backup the database. If there ismore than one tape, separate the name by comma (for example, ARCB01,ARCB02).

12. Choose Enter.

13. In Please select, enter S and choose Enter.


14. The program prompts you to replace the tape when it needs changing.Replace the tape with the new tape and volume name specified.

15. Enter cont, when the program prompts you to enter ‘cont’ to continue.

16. Choose Enter.

17. When the backup has finished successfully, the message BRBACKUPterminated successfully appears.

18. Remove the tape and store properly.

Back Up the Archive Logs

Make sure you initialize and label sufficient tapes, and have the required,initialized and labeled, tapes as specified by brarchive –q.

We will use SAPDBA to perform the backup. SAPDBA executesBRARCHIVE to perform the backup. BRARCHIVE can be executed directly,which allows it to be executed by a cron job and scheduled.

Task

Back up the archive logs

1. At the command prompt, enter SAPDBA and choose Enter.


2. In Please select, enter i and choose Enter.

3. To enter some of the parameters of archiving, enter a (Archive function) at theprompt and choose Enter.

4. Enter the letter for the type of archive log backup you want to do (forexample, a).

5. Choose Enter.


6. Enter q and choose Enter.

7. Enter e and choose Enter.

8. Enter the volume name of the tape used to backup the archive logs (forexample, ARCA01) and choose Enter.

9. Enter s and choose Enter.

10. When the archive logs have been backed up successfully, the messageBRARCHIVE executed successfully appears.

11. Choose Enter.

We recommend that youmake two copies of theOracle Archive Logs.


Useful Online Service System Notes

Online Service System Note # Description

68059 SAPDBA - option -next with tablespace list

43499 All collective notes concerning DBA Tools

43491 Collective note: SAPDBA - Command line options

43486 Collective note: General SAPDBA

43484 Collective note: General DBA

42293 SAPDBA - new command line option –analyze

34432 ORA-00020: max number of processes exceeded

33307 Cost-Based - Rule Based Optimizer (ORACLE)

31073 SAPDBA - new command lines -next, -analyze

21568 SAPDBA: Warning: only one member of online redo

16513 File system is full—what do I do?

15465 SAPDBA - shrinking a tablespace

04754 Buffer synchronization in centralized systems

03807 Tablespace PSAPROLL, rollback segments too small

02425 Function of tablespaces/DBspaces on the database


01039 Problems with ORACLE TWO_TASK linking

109521 SAPDBA: Termination of check run on WinNT

P A R T S I X

EOperations Overview


Part Overview

Operations, as a topic, is composed of various system-related topics that can be looselycalled data center operations.

Chapter 13 discusses the printing and spooling processes of your SAP system. We talkabout setup and management of the SAP printing system.

Chapter 14 talks about administration of secondary systems relating to the SAP system,such as the network, operating system, and servers.

Chapter 15 covers general system operation. Background jobs are covered here, as well asoperational modes and backups.

Chapter 16 discusses the management of change. Over time, your system may requirepatches and fixes. We talk about how to manage them effectively in this chapter.

C H A P T E R

13

13Output Management


Overview

This chapter covers the setup and management of the SAP R/3 printingsystem. To accommodate the open client/server architecture concept, SAPhas its own spool system that provides a uniform interface independent of thesystem platform.

Printer Setup (SPAD)

Before you set up a printer in SAP R/3:

� Set up the printer at the operating system level.

� Know the printer name. This name is the network name of the printer (forexample, FIN3 or \\FINANCE\ACCT2; not HP Laser Jet 5si).

� Know the type of printer. This information is the manufacturer and modelof the printer (for example, HP Laser Jet 5si).

Task

Set up the printer in the SAP R/3 system

1. In the Command field, enter transaction SPAD and choose Enter (or from theSAP standard menu, choose Tools → CCMS → Spool → SPAD-Spooladministration).

2. In the Device/servers tab, choose Output devices.


3. Choose to switch to change mode.

4. Choose .

5. In Output device, enter a descriptive name for the printer (required).

6. Optionally, in Short name, enter a short name. The system can define it foryou. In our example, we will let SAP R/3 define the short name.

7. Choose the Device Attributes tab.

8. On the Device Attributes tab:

a. In Device type, choose to select the appropriate device type for yourprinter (required).

b. In Spool server, choose to select the appropriate server where yourprint requests will be processed.

c. In Model, enter the printer’s make and model.

d. In Location, enter the printer’s location.

The Model and Locationfields are importantbecause you cannot use

a printer if you do not know itslocation and its model name. Thekey is to make your description asprecise as possible. If the printerhas been moved, remember toupdate this field.


e. The message field is used for a temporary message that replaces theLocation text. Messages are useful if a printer is offline for repair, forexample.

9. Choose the HostSpoolAccMethod tab.

10. In Host spool access method, choose to select the appropriate accessmethod.

11. In Host printer, enter the printer name as defined in your network (required).

12. Select the Output Attributes tab.

At this point, things canget complicated. Ingeneral, use the following

local access methods to reducenetwork problems in the system.For:

� NTSelect C – Direct operatingsystem call.

� UNIXSelect L – Print locally viaLP/LPR


13. On the Output Attributes tab:

a. In this section, you can specify a cover page (optional).

b. Select Monitor using monitoring architecture. If you have a large number ofprinters, do not select this option.

c. Choose .

14. In our example, to let SAP R/3 create the short name, choose Yes.

15. If we had entered a short name, and there is a name conflict with an existingprinter, this conflict message would appear. If this name conflict exists, at thisdialog box, choose Yes.

16. A message indicates that the printer was created.


17. Choose the Tray info tab.

18. Under Active, select the paper tray to activate it for automatic selection.

19. Under Page format, enter the page format or choose .

Note

Automatic selection means that thecorrect tray is selected based on thepaper format (such as letter). Thisselection applies only to the paperformat, not the type of paper (forexample, letter head, invoice, blank,and so on.)


20. On the Page Formats dialog box:

a. Select the proper paper format. Scroll down to see the Letter and Legalpaper formats.

b. Choose .

21. Repeat steps 18–20 for all printer trays.

22. Choose .

23. Choose .

24. A message in the status bar indicates that the paper tray information wassaved.


25. Choose .

26. The new printer (Finance GL) is now in the printer list.

27. To test the printer, from the menu bar, choose Output device → print this list.

Check the Spool for Printing Problems (Transaction SP01)

The spool is the SAP R/3 system’s output manager. Data is first sent to theSAP R/3 spool and then to the operating system for printing.

There may be problems with the printer at the operating system level. Theseproblems must be resolved immediately for time-critical print jobs (forexample, checks, invoices, shipping documents, and so on) to avoidoperational impact.

Note

For frontend printing please see SAPNote 114426.


You should check for active spool jobs that have been running for over anhour. These long-running jobs could indicate a problem with the operatingsystem spool or the printer.

Task

Check the Spool for printing problems

1. In the Command field, enter transaction SP01 and choose Enter (or choose SAPstandard menu → Tools→ CCMS→ Spool→ SP01-Output Controller).

2. On the Output controller: Spool request selection screen:

a. In Created by, delete any information.

b. In Date created, set the date (for example, a week ago, or to any other daterange to check for other problems).

c. In Client, delete any information.

d. Choose .

3. Look for jobs with an error in the Output Status column.

Note

The range of data will depend on yourinstallation. If you generate hundreds orthousands of spools a day, you wouldchoose every day. This data rangewould be much shorter, possibly onlytwo days.


4. Double-click on the error.

5. Select the checkbox next to the error.

6. Choose .

7. Review and troubleshoot the error.

8. Choose .


9. Select the error.

10. Choose .

11. Use the log to investigate the problem (for example, The printer name isinvalid).

Check that Old Spools are Deleted (SP01)

The SAP spool is the output manager for SAP R/3. From the SAP spool, theprint job goes to the operating system’s print spooler or manager. You mustcheck that old spool jobs are being properly cleared by the daily batch job.

Depending on how the spool system has been configured, old spools will usedatabase space or file system space. Whether it is database or file systemspace, these spools are using potentially available space. Look for any errorsthat may indicate problems in the printing process.


Task

Check that old spools are deleted

1. In the Command field, enter transaction SP01 and choose Enter (or from theSAP standard menu, choose Tools→ CCMS→ Spool→ SP01-Output Controller).

2. Clear the following fields:

� Created by

� Date created (date)

� to (date)

� Client

3. Choose .

4. After the system has been operating for some time, check whether old jobs arebeing purged.

5. Scroll down to find the oldest date. This date should be within the time framedefined for the job that runs RSPO0041 program (see SAP Note 16083). If thespool requests beyond the minimal age are found, the job may not beproperly deleting the old jobs and needs to be analyzed.


6. To view the attributes of a spool request, highlight a request and choose .

7. From this screen, the spool attributes, output, and temporary sequentialdatabase (TemSe) attributes can be conveniently accessed.

8. Notice that information on the Number of pages generated, the Recipient, andthe Delete date of the spool request are displayed.

9. Choose the Output attributes tab.

Two reasons for failure ofthe job that runs theRSPO0041 program are:

The user ID under which the job isrun does not have the propersecurity authorization to executethe program.

The job is routed to an invalidprinter.

RSPO0041 has been replaced byRSPO1041. See SAP Note130978.


10. You can set the priority of the output request. The priority levels are from 1–9with 1 being the highest priority.

11. Select the TemSe attributes tab.

12. The name and size of the object as stored in the TemSe database aredisplayed. This information is useful when there are inconsistencies in thespool and TemSe databases.

Note

For more information, see “Check SpoolConsistency (SPAD)” on page 407.


Printing the Output (SP01)

There are two types of requests:

� Spool

� Output

The spool request contains the printed document that has not been sent to theoutput device. The output data of this document is partially formatted andstored in the TemSe database. The output request tells SAP R/3 to format therequest to a particular device and contains attributes such as target printer,number of copies, and so on. Each time you select the printer icon, an outputrequest is created for the spool request.

Task

Print the contents of a spool request immediately or at another date and time using different parameters

1. Select a spool request.

2. Choose to print directly. This step creates an output request and printsthe contents of the spool request immediately on the printer.

3. A message appears on the status bar stating that an output request wascreated.


4. The Status column displays the status of the print job. If the output wasprinted successfully, the status is Compl (complete). Otherwise, a status ofWaiting or Error will be displayed.

5. To print a spool request with a different printer or change the start date andtime:

a. Select a spool request.

b. To print with changed parameters, choose .

6. On the Output controller: Print spool request <XXXXX> screen, you can:

� Change to another output device

� Increase the number of copies

� Change the priority

� Change the start date and time

In our example, we change the printer to DCBZ.


7. Choose to print directly.

8. The system displays a message that an output request was created.

9. Choose .


10. Under the Status column, the request is scheduled for printing.

Printing the Screen

You can quickly and easily print the contents of most screens or do a “printscreen” by choosing the printer icon. Using this procedure also generates aspool request and an output request, which can be useful in testing that a newprinter was setup correctly.

Continue from the prior step or any screen with a printer icon.

On some screens, there are two printer icons. The one to choose is usuallylocated just under the menu bar. (When the cursor is passed over this button,Print Ctrl+P appears.)

Task

Print the screen

1. Choose .


2. On the Output Controller: List of Spool Requests screen, you can specify orchange the:

� Output device

� Number of copies

� Pages to print

� Spool request name

� Start time

� Change the priority

� Number of days you wish to keep the spool request

� Print format

3. In Spool retention per., choose .


4. In the Spool Retention Period dialog box:

a. Selecting Do not delete keeps the spool request indefinitely. Therefore, thisrequest will not be purged by program RSPO0041 that deletes old spools.

b. Choose a spool retention period (for example, Delete after 8 days).

c. Choose Save.

5. On the Output Controller: List of Spool Requests screen, choose Continue.

6. In the status bar, a message stating that a spool request was created isdisplayed.

7. Choose .


8. The new output requested now appears.

Check Spool Consistency (SPAD)

A spool consistency check compares data in the spool and output requesttables (TSP01 and TSP02), with the entries in the TemSe tables (TST01 andTST03), TSP0E (archive) and TSP02F (frontend print request) tables. It alsodisplays a list of obsolete write locks that should be deleted.

If you delete table entries manually from the spool and TemSe tables or deletespool and TemSe objects from the directories, inconsistencies can occur. Othercauses of inconsistencies are report and transaction terminations or anincorrectly executed client copy.

Task

Check spool consistency

1. In the Command field, enter transaction SPAD and choose Enter (or from theSAP standard menu, choose Tools → CCMS → Spool → SPAD-Spooladministration).


2. Choose the Admin. tab.

3. Choose Consistency check of spool database.


4. The system checks the spool tables and the TemSe tables to make sure thateach spool object has corresponding entries in each of the tables.

Check TemSe Consistency (SP12)

A TemSe consistency check compares data in TST01 [Temporary SequentialDatabase (TemSe) objects] and TST03 (TemSe data) tables. The TemSecontains objects that are temporary such as job logs, spool requests, tests forworkflow, batch input logs, and personnel administration temporary data.The report RSTS0020 performs the consistency check.

The relationship between the object and data in the TemSe may be destroyeddue to the following activities:

� Restore from backups

� Copying databases

� Copying clients using improper tools

� Deleting clients without first deleting their objects

Note

Another report, RSPO1043, can beused for the spool consistency check. Itshould be scheduled as a periodic batchjob (see SAP Note 98065).


Task

Check TemSe Consistency

1. In the Command field, enter transaction SP12 and choose Enter (or from theSAP standard menu, choose Tools→ CCMS→ Spool→ SP12-TemSeAdministration).

2. From the menu bar, choose TemSe database → Consistency check.

3. The TemSe objects and data were checked. If there are inconsistencies:

a. Select the item.

b. Choose Delete Selection.

C H A P T E R

14

14Network/OS/Server

Administration


Overview

This chapter is about using SAP transactions to get to the operating systemlog, regardless of the platform.

Operating System Tasks

The following tasks allow you to modify how SAP R/3 interacts with theoperating system.

System Logs (OS06)

The system logs contain operating system and application write eventrecords. Depending on the operating system, multiple logs may exist. Thelogs may contain indications of a developing problem (for example, a harddrive that generates errors may indicate that it is failing and needs to bereplaced).

Task

View system logs

1. In the Command field, enter transaction OS06 and choose Enter (or from theSAP standard menu, choose Tools → CCMS → Control/Monitoring →Performance menu → Operating System → Local → OS06-Activity).


2. Choose Detail analysis menu.

3. Choose OS Log.

Configuring the securityaudit function is a trade-offamong the following:

� The need to log securityevents.

� System resources to trackand maintain the log. Themore detailed you make thelog, the more the systemperformance will degrade.This degradation is due tothe extra processingrequired to track and log theitems.

� Effort required auditing thelog (dependent on the sizeof the log).


4. The Operating System Log screen appears. In this example, the NT event logappears.

Checking File System Space Usage (RZ20)

The file system should have sufficient free space for normal operations. Overtime, various activities will write files that will use up file space. These filesmust be periodically reviewed and moved or backed up and deleted.

A few of the items that consume file space when monitoring file space usageinclude:

� Transports

� Support packages

� Extract files from the SAP R/3 system

� Program logs

� Backup logs

� Error logs

� Inbound interface files

� Third-party programs that store their data outside the SAP R/3 database

� Trace files

� Spool files (if stored at the OS level)

In addition to these items, check to see that the house cleaning programs arerunning properly (see SAP Note 16083).

Note

There may be indications of adeveloping problem. If the security auditparameters have been properly set, youcould detect unauthorized attempts toaccess files.


If your file system fills up, the SAP R/3 system may stop because the databasecannot write to a file. If SAP R/3 stops, any business operations that use thesystem will also stop.

For example, note the following sequence of events:

1. The SQL Server transaction log fills up the file system.

2. SQL Server cannot write any more entries into the log.

3. SQL Server will stop.

4. SAP R/3 will stop.

Your user will not be able to perform activities such as entering orders orgenerating shipping documents.

To plan for such a situation:

� Anticipate and plan for disk space needs.

� Determine if storage space expansion is needed. If storage space expansionis needed, purchase and installation plans must be made. The expansionshould be planned to minimize operational disruption.

� Determine if file system cleaning is needed. If archiving is required fordata files, archive to quality storage media such as an optical disk, CD-ROM, or other long-term storage media.

You can use the SAP R/3 Alert Monitor or go to the operating system to checkfile system space usage. In this section, we use the SAP R/3 Alert Monitor,because we can set alert points.

Task

Check file system space usage

1. In the Command field, enter transaction RZ20 and choose Enter (or from theSAP standard menu, choose Tools → CCMS → Control/Monitoring → RZ20-Alert Monitor).

2. Select the node (+) to expand the monitor set.

3. Select the monitor set (for example, Entire System).

4. Choose .


5. Drill down to get to the following starting node:<SID>\<host>_<SID>_<Instance> (for example, SA1\pa102058_SA1_00).

6. Drill down to the drives OperatingSystem → Filesystems.

The drives are color-coded to indicate alert status:

� Green (OK)

� Yellow (Warning)

� Red (Critical)

7. Select a drive (for example, C:) and drill down to see its statistics (Freespaceand Percentage_Used). These are statistics at the drive (not directory) level. Asyou view these statistics, keep your system in mind. For example, on yoursystem, drive H may contain the database that takes up all the space on thatdrive. Keeping this in mind, you can expect and ignore the warning message,or change the alert threshold for that specific drive. For more information onchanging the alert threshold, see the next task.

Changing the Alert Threshold (RZ20)

For more information about the Alert Threshold, see “Maintaining The AlertThresholds for RZ20” on page 120.


Task

Customize alert threshold

1. Select the node of the drive for which you want to change the threshold (forexample, drive C:).

2. Select an alert (for example, Freespace).

3. Choose Properties.

4. On the Monitoring: Properties and Methods screen:

a. To change the values, choose .

b. Under Threshold values, select a threshold change point (for example,Change from GREEN to YELLOW).

c. Enter the new value for when the alert will change color (for example,500). These threshold values are specific to your system and even tospecific drives in your system.


d. Choose . A message appears in the status bar indicating that the newproperties were saved.

Cleaning Out Old Transport Files

Transport files are used to transport or move SAP objects and customizingchanges between clients and systems. If left unchecked, transport files couldgradually fill up the file system. If the file system fills, operations may beaffected because:

� Outbound SAP R/3 system files may not be created.

� Transport export may fail.

� Inbound files may not be created.

In an extreme situation, if you run out of file system space, SAP R/3 may stop,or you may have other failures because SAP R/3 or other applications cannotwrite to the necessary files. The transport directory check is importantbecause:

� After a major implementation where many transports have been createdthat take up a lot of space

� Immediately before (or after) performing a database copy, if you do notuse a central transport directory, most (if not all) files dated before the copybecome irrelevant to the system

� After installing a large support package


Task

Perform a transport directory check

1. Check the following directories under /usr/sap/trans:

� Data

� Cofiles

� Log

2. Sort the directory by date to determine file age.

3. Archive any obsolete files, such as those created before a database refresh orthose that have been applied successfully to all target systems.

4. Optionally, archive old transports to a backup media such as tape, opticaldisc, or CD.

Other Tasks

Clean the Tape Drive

To minimize a backup failure due to a dirty head, clean the tape drive as partof a preventive maintenance program. To keep your tape drive clean:

� Follow the tape drive manufacturer’s instructions for your tape drive.

� Use the manufacturer’s approved cleaning cartridge for the tape drive.

� Use the cleaning cartridge according to the manufacturer’s instructions.

Check the following:

Support packagedirectory

/usr/sap/trans/EPS/in

Transport data directory/usr/sap/trans/data

Support package files can bereloaded if needed and can belarge (for example, supportpackage 15 for Release 4.6C isover 100 MB).

Note

Some drives specify a specific interval of use for cleaning, typically based on hours of use.Adjust your cleaning frequency to account for your usage. Remember, that these arerecommendations, not rules. If you consistently have recording errors or head dirty messages,decrease the time between cleanings. If you have to clean your tape drives more or lessfrequently, this task should be moved to the appropriate interval. Some drives (for example,DLT) do not require regular cleaning. They only need cleaning when the clean head indicatorlight is activated.


� Between uses, store the cleaning cartridge according to the manufacturer’sinstructions.

Uninterruptible Power Supply

Check the Uninterruptible Power Supply

The uninterruptible power supply (UPS) that you use should be monitored bya control program. This program, when triggered by a power event, recordsthe event and initiates a shutdown process of the SAP R/3 environment (SAPR/3, database, related applications, and operating system), and finally theserver. In addition, most UPSs have a self-test and capacity calibrationfunction. The results of these tests are logged. Specific data logged dependson the program and the UPS. You must review the power events thattriggered the UPS control program.

You must verify that:

� The UPS is functioning

� The self-tests completed successfully

� There is sufficient capacity in the batteries

Review the log for the UPS control program.

Check your UPS Shutdown Process

Verify that your UPS shutdown process works. A shutdown process is anautomated script for the UPS to shut down SAP R/3, the database, otherapplications, the operating system, and the UPS.

This check verifies that the entire shutdown process works as planned anddocumented. When there is a power failure, the SAP R/3 environment shouldbe shut down in an orderly manner. There should be sufficient reserve in the

Keep your server room clean. A dusty or dirty environment will not only make you clean yourtape drive more often, but will also coat the inside of the server with dust and cause a coolingproblem.Tips & Tricks

While the UPS protects the server, the control program should be recording power events suchas power dips, brown outs, power failures, and so on. This recording could help you or thefacilities person solve electrical problems in the facility. For example, a pattern of power dips oroutages may indicate a problem elsewhere in the building.

The batteries in the UPS must be periodically replaced. If the batteries are low, the capacity testwill indicate that the batteries do not have sufficient capacity to shut down the system beforefailing.

Tips & Tricks

Caution


UPS to reach the end of the shutdown process. Something might havechanged since your last test to cause the shutdown process to fail. If thisprocess fails, you must find out why and fix the problem.

Check Maintenance Contracts

Many of the servers and related equipment should be under maintenance orservice contracts with the manufacturer or distributor.

� The production system and critical equipment should be under a premium24 hour / 7 day (with 2 hour response) support agreement.

� Less critical equipment can be under a next-business-day supportagreement.

If you need support or service and the service contract has expired, theconfusion and time to reestablish the service contract could be critical.

The support level should be selected based on equipment use. If a piece ofequipment becomes critical to the company’s operation, its support levelshould be upgraded to reflect the critical nature of that equipment.Conversely, equipment could become noncritical or be replaced. In thissituation, the service contracts could be downgraded or dropped asappropriate.

� Keep a list of service contracts.Include what these contracts are for and the expiration date in the list.

� Review equipment usage to determine if the support level for equipmentshould be upgraded, downgraded, or dropped.

� Review the list for expiration dates each quarter.How long in advance of the expiration date to do this review depends onthe time it takes to go through the purchase requisition and approvalprocess in your company.

� Renew service contracts.

Review Hardware or a System Monitor Paging System

A hardware or system monitor paging system generates alert messages(including e-mail) and pages based on your predefined parameters.Depending on the software, the following can be monitored:

� Hardware items (such as servers, routers, and printers)

� Logs (such as operating system, applications, and database)

The stopsap command does not work within all UPS control programs. You must verify thatyour UPS control program will properly stop SAP R/3 and the database before shutting downthe server.Caution


By monitoring the NT event logs, you can monitor events from the SAPsystem log. This way, critical events such as an Update Terminate can bedetected and acted on as soon as they happen.

The following screen is courtesy of TNT Software.

The screenshot above shows that the monitor has three functional windows:

� Notification Rules

This mechanism passes or filters events, and determines what action willbe taken on the events that are passed.

� Events

These are the events that have been passed to the monitor program. (Theygot through the filters in Notification Rules.)

� Monitored device

These are the monitored servers and IP devices.

This example, however, has not been configured to pick up and report onSAP events. Initially, there will be a lot of tuning as the system parameters areadjusted. Over time, the need for parameter adjustments will decline.

You may must change alert parameters to filter noncritical events and togenerate alerts for critical events. The key to remember is that this process isdynamic. Some of these tasks are as follows:

� Account for new events that have not previously occurred

• Critical (you must generate a page)

• Important (you must generate a message (for example, e-mail))

� Determine if a previously filtered event now needs to generate an alert


� Filter out events (both old and new) that should not generate alertmessages

Filtering is necessary to manage the messages that are reviewed. If toomany irrelevant messages get through the filter, it becomes difficult toreview the alert message log.

� Adjust for personnel changes

Other events may require action (for example, shift or duty changes fororganizations with several people on-call).

� Test that all alert mechanisms are functional

The paging/messaging function must be tested regularly. If themonitoring program is unable to send a page, you will not receive thepage when a critical alert occurs.

The inability to send a page can be caused by:

� Someone changing something in the e-mail or phone system that preventsalert messages from being sent

� A phone patch cable that has disconnected from the modem

To review the paging system:

� Review the various monitored logs (such as the NT event logs) to look forevents that should generate an alert message (e-mail or page)

The monitor program needs to be configured to pick these events up andproperly process them.

� Review the alert monitor log for alert events that should be filtered out

The monitor program needs to be configured to filter or ignore suchevents.

� Test all alert mechanisms, such as pager, e-mail, and so on to make surethat they are functional

If you receive regular daily e-mail messages, the e-mail testing is beingdone for you.

Note

RZ20 can also be configured to generate a page.

C H A P T E R

15

15Operations


Overview

Operations refers to the tasks performed by a computer operations group.These are the tasks that the people in a data center’s glass room do. If you donot have a data center, these tasks must be assigned to the appropriateemployees.

Operations is a crucial part of system administration. While learning tomanage operations, readers will learn how to perform:

� Batch jobs

� Background jobs

� Operation modes

� Backups

Check that All Application Servers Are Up (Transaction SM51)

Transaction SM51 allows you to look at all the servers in your system (forexample, the PRD database server and all of its application servers). You donot have to log into each server individually.

The ability to look at the servers is important because:

� If one of your dialog application servers is not up, the users who usuallylog on to that application server cannot log on.

� If the batch application server is down, batch jobs that are specified to runon that server will not run.

Task

Check that all application servers are running

1. In the Command field, enter transaction SM51 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → Systemmonitoring → SM51 - Servers).


2. Review the list of instances under Server name. Verify that all instances arelisted. If it is listed, it is up and running.

Background (Batch) Jobs

In the SAP R/3 system, a batch job is referred to as a background job. This jobruns independently of a user being logged on.

There are two kinds of background jobs:

� Regular

These are jobs that are run on a regular schedule.

� Ad hoc

These are jobs that are run as needed or required.

Background jobs are used for the following reasons:

� Users have the flexibility of scheduling jobs to run when they are out of theoffice.

� The program can be run without locking a user session.

� Jobs that run for a long time would time out if executed online.

Regularly Scheduled Jobs

Regularly scheduled jobs are background jobs that run on a schedule (forexample, daily at 11:00 a.m., Sundays at 5:00 a.m., and so on).

Regularly schedule jobs are run to:

� Collect performance statistics

� Populate an information system, such as the Special Ledger

� Generate a report


� Generate output for an outbound interface

� Process an inbound interface

� Perform housekeeping tasks, such as deleting old spool requests

The job is scheduled like any other background job, but with a few additionalconsiderations.

Batch User ID

Create a special user ID to be used only for scheduling batch jobs, such asBATCH1.

� Consider multiple-batch user IDs when batch jobs are scheduled by or fordifferent organizations or groups. This method has the disadvantage ofhaving to manage multiple accounts. For example:

• BATCH1 System Jobs

• BATCH2 Finance

• BATCH3 Accounts Payable

• BATCH4 Warehouse

• BATCH5 Material Planning/Inventory

Performance

For more information on performance, see “Performance Factors forBackground Jobs” on page 429.

Housekeeping Jobs

These background jobs must be run regularly to perform administrative tasks,such as:

� Deleting old spools

� Deleting old batch jobs

� Collecting statistics

See SAP Note 16083 for the required SAP housekeeping jobs, and to schedulethe spool consistency check, see SAP Note 98065.

Others

Various modules and functions may require their own regularly scheduledjobs. For example, the Special Ledger requires a regular job to copy data fromthe FI/CO modules and to regenerate sets in Special Ledger. There may bevarious database and operating system-level housekeeping jobs that alsomust run.

The reason for specialuser IDs is to keepscheduled jobs

independent of any user. Thisway, when a user leaves thecompany, the jobs will not failwhen the user ID is locked, shutdown, or deleted.

Program RSPO0041 issometimes troublesome;see SAP Note 48400.

There is a replacement programRSPO1041. See SAP Note130978.


Performance Factors for Background Jobs

Background jobs consume a significant amount of system resources. As aresult, they could adversely affect online system performance. There areseveral ways to improve system performance while running background jobs.These methods benefit both online users and other background jobs.

To reduce the system impact from background jobs:

� Run batch jobs on a dedicated batch application instance/server.

This step separates the processing requirements of the background jobfrom the processing requirements of online users and of the database.Even with as few as 10 users on a small central instance (no applicationservers), two batch jobs can significantly slow down the online systemresponse. Therefore, even for a small installation, application servers mayneed to offload the batch processing from the central instance. Theinstance profile for this application server would be tuned for backgroundjobs rather than dialog (online) performance (for example, fivebackground work processes and only two dialog work processes).

Specifying a target host is problematic. If you specify the target host, loadbalancing is not performed. There may be the situation where all thebatch work processes on the batch application server are in use, and otherapplication servers are idle. However, by specifying that the job is to runon the batch application server, it will not run on any of the otheravailable application servers. This job will wait until a batch work processis available on the specified batch application server.

� Schedule background jobs to run during non-peak periods, such as atnight or during lunch.

If no one is on the system, slow system performance does not matter.

� Minimize job contention.

Two background jobs are running at the same time and contending forthe same files, possibly even the same records. Minimizing this conflict isone reason to coordinate background job scheduling (for example, by notsimultaneously running two AR aging reports). In such cases, the reportsmay finish sooner if they are run sequentially, rather than in parallel.

� For global operation, consider the local time of your users.

For example, scheduling a resource intensive background job to start at1:00 a.m. PST in California (0900 GMT) corresponds to 10:00 a.m. CET inGermany. This time may be good for Americans who are not working, butit is the middle of the workday morning in Germany.

When these jobs run is critical, for tasks such as backing up operatingsystem-level files, because of the following:

• A backup of these files may require that the file not be changed orused during the backup, or the backup will fail.

• Programs attempting to change the file will fail because the backuphas the file locked.

A general guideline istwice the number ofCPUs as the number of

background processes.

Make a chart thatconverts your local timeto the local time for all

affected global sites. With thischart you can quickly see what thelocal time is for locations thatwould be affected by a job (seefollowing example):

A corporate master clock (or time)should be defined for a companywith operations in multiple timezones.

Two common methods are:

� The time zone where thecorporate office is located.For SAP in Walldorf,Germany this is CentralEuropean Time (CET).For United Airlines inChicago, IL, this is CentralStandard Time (CST).

� Coordinated Universal Time(UTC), formerly known asGreenwich Mean Time(GMT).This common time is usedby global operations, suchas the airlines.


The time conversion table (based on a 24-hour clock) below shows selectedtimes around the world.

The Microsoft Excel file for the table above is included on this guide’scompanion disk, which is located inside the back cover of this book.

If you use daylight savings time, you must be aware of the days when thetime changes:

The change to and fromdaylight savings timedoes not occur on the

same day in all countries. Duringthat interim time, the offset timecould be different.

Site Hawaii Calif Denver Chicago Philly London Walldorf Israel Singapore

Timezone

HST PST MST CST EST UTC CET

Offsetfrom UTC

-10 -08 -07 -06 -05 0 01 03 08

14 16 17 18 19 00 01 03 08

15 17 18 19 20 01 02 04 09

16 18 19 20 21 02 03 05 10

17 19 20 21 22 03 04 06 11

18 20 21 22 23 04 05 07 12

19 21 22 23 00 05 06 08 13

20 22 23 00 01 06 07 09 14

21 23 00 01 02 07 08 10 15

22 00 01 02 03 08 09 11 16

23 01 02 03 04 09 10 12 17

00 02 03 04 05 10 11 13 18

01 03 04 05 06 11 12 14 19

02 04 05 06 07 12 13 15 20

03 05 06 07 08 13 14 16 21

04 06 07 08 09 14 15 17 22

05 07 08 09 10 15 16 18 23

06 08 09 10 11 16 17 19 00

07 09 10 11 12 17 18 20 01

08 10 11 12 13 18 19 21 02

09 11 12 13 14 19 20 22 03

10 12 13 14 15 20 21 23 04

11 13 14 15 16 21 22 00 05

12 14 15 16 17 22 23 01 06

13 15 16 17 18 23 00 02 07Highlight the column foryour local time zone, sothat you do not

accidentally read the wrongcolumn. Using a 24-hour clockeliminates the common am/pmconfusion.


� Daylight savings time starts

A one-hour time period will disappear. Jobs scheduled to run in thismissing hour may either not run or run as a late job. Any tasks followingthis change that rely on a job scheduled to run during the missing hourmust be reviewed.

� Daylight savings time ends

This period creates a problem where a one-hour period of time repeatsitself. For example, at 3:00 a.m., the clock resets back to 2:00 a.m. This timeperiod will occur twice.

One way to avoid problems when daylight savings time is switched on andoff is to use UTC (formerly known as GMT) as your master clock. If you are ina U.S. state that does not use daylight savings time, such as Hawaii, it is not aconcern.

See the following SAP Notes:

� 7417 - Changing to daylight savings time and back

� 102088 - End of daylight savings time: the double hour

Creating and Scheduling a Batch Job (SM36)

Background jobs are used for the following reasons:

� Users have the flexibility of scheduling jobs when they are not in the office.

� The program can be run without locking a user session.

� Jobs that run for a long time would time out if run online.

As a prerequisite, a batch job may require that a variant be created to executethe job.

Note

The job class determines the start priority of the job. For example, a “class A” job would startbefore a “class B” job, and a “class B” job would start before a “class C” job.

Once started, all job classes have equal priority. A “class A” job will not take processingresources away from a “class B” job to finish faster.

Jobs in the start queue do not affect running jobs. A “class A” job in the start queue will notreplace a currently running “class C” job.

Alternately, you can choose Job wizard to go through the above procedures with step by stepdescription.

Avoid playing prioritygames with the job class.If you make every job a

“class A” job, there is no priority,because every job will be at thesame priority level.

The recommended method is toassign all jobs to job “class C”.The exceptions to thisrecommendation are those jobsthat need the priority. This priorityincrease should be properlyjustified and can be controlled bySAP authorization concept.

Tips & Tricks


Task

Create and schedule a batch job

1. In the Command field, enter transaction SM36 and choose Enter (or from theSAP standard menu, choose Tools → CCMS → Jobs → SM36-Definition).

2. On the Define Background Job screen:

a. In Job name, enter a job name.

b. In the Job class, enter C. Class C is the standard job class.

c. Choose Start condition.

3. Choose Date/Time.

Using a standard namingconvention makes iteasier to manage jobs.


4. For Schedule start, in Date and Time, enter the start date and time.

5. On the Start Time dialog box:

a. In No start after, enter the date and time by which time the program muststart. If the program does not start by the specified date and time, then itwill not start at all.

b. If you have a job that will run periodically, perform steps 5c–6c. If not,choose Immediate and skip to step 7a.

c. Select Periodic job.

d. Choose Period values.

6. On the Period Values dialog box:

a. Choose the appropriate period button (for example, Daily).

b. Choose Check.

c. Choose .

The Schedule start is thedate and time on thedatabase server, not the

local time.


7. On the Start Time dialog box:

a. Choose Check.

b. Choose .

8. Choose Step.


9. On the Create Step dialog box:

a. To schedule an ABAP program, choose ABAP program.

b. In the ABAP program section, in Name, enter the name of the program (forexample, rspo0041).

c. Choose Check.

10. If the program has variants, the ABAP: Variant Directory of Program <XXXXX>dialog box appears. On the dialog box:

a. Select the appropriate variant.

b. Choose .


11. Choose Print specifications.


12. On the Background Print Parameters dialog box:

a. Enter the printer name or choose to select the printer.

b. Select the appropriate Spool control options.

c. Under Print settings, Lines and Columns values are generated by thereport.

d. For Format, choose to select the value that most closely matches theLines and Columns value.

e. Choose .


13. Choose .

14. Choose .

15. A message will appear in the status bar indicating that the batch job has beencreated.


16. Choose .

Background Jobs (SM37)

Background jobs are batch jobs scheduled to run at specific times during theday.

If you are running critical jobs, you must know if the job failed because theremay be other processes, activities, or tasks that depend on these jobs.

You should have a list of all the critical jobs that are scheduled to run. Foreach of these jobs, you should have a list that shows:

� When the jobs are scheduled to run

� The expected run time

� An emergency contact (names and phone numbers) for job failure orproblems

� Restart or problem procedures

Task

View background jobs

1. In the Command field, enter transaction SM37 and choose Enter (or from theSAP standard menu, choose Tools→ CCMS→ Jobs→ SM37 - Maintenance).



a. In Job name, enter * to get all jobs.

b. In User name, enter one of the following options:

• * (for all users)

• User ID that the batch jobs run under (to limit the display to thosescheduled under a specific user ID in User name).

c. Under Job status, select:

• Active

• Finished

• Canceled

d. In Fr., enter a start date.

e. In To, enter an end date.

f. In after event, choose and select *.

g. Choose Execute.

3. Check for failed or cancelled jobs. Analyze why jobs failed or were cancelledand make the necessary corrections.

4. Check critical jobs such as MRP, check payment jobs, and so on. To do thischeck, you must know the job name.

5. From this point, you may do one of the following tasks:

� Check the job log


� Get basic job information

Checking the Job Log

You may want to regularly check the job log for job performance and recordrun times. Deviations from normal run times on a job may indicate a problemrequiring further investigation.

Task

Check a job log

1. On the Job Overview screen:

a. Select the job.

b. Choose Job log.


2. On the Job Log Entries for <XXXXX> screen:

a. Check job performance and record run times (The difference between theJob started and Job finished times).

b. Choose .

Graphical Job Monitor (Transaction RZ01)

The graphical job monitor is useful when coordinating many background jobsbecause it allows you to see individual job statistics. The graphical jobmonitor is a visual format where status is indicated by the following colors:

� Aborted job (red)

� Active job (blue)

If a job ran past its expected end time, and other jobs are scheduled to start,the graphical job monitor lets you see the conflict.

Task

View Grapical Job Monitor

1. In the Command field, enter transaction RZ01 and choose Enter (or from theSAP standard menu, choose Tools → CCMS → Control/Monitoring → RZ01-Job Scheduling Monitor).

2. Choose Time unit → Hour to get a more usable time scale.

3. Choose Legend to get a popup legend of the colors or patterns used.


4. Choosing Timer ON will update the display every three minutes.

Batch Input Jobs, New or Incorrect (SM35)

This transaction shows jobs that must be processed or started, and jobs witherrors that must be resolved.

This transaction is important because it alerts you to batch input jobs that are:

� New

These are jobs that are waiting to be processed (for example, a postingfrom an interface file). If not processed, the data will not post to thesystem.

� Incorrect

These are jobs that have failed due to an error. The danger is that only aportion of the job may have posted to the system. This partial postingincreases the potential for data corruption of a different sort, because onlypart of the data is in the system.

Task

View batch input jobs

1. In the Command field, enter transaction SM35 and choose Enter (or from theSAP standard menu, choose Tools→ Administration→ Monitor→ SM35-BatchInput).


2. On the Batch Input: Session Overview screen:

a. In From, enter a start date of at least a week ago.

b. Choose .

3. Choose the New tab. A list of batch input sessions that must be processedappears.

4. Choose the Incorrect tab. A list of incorrect batch input sessions are displayed.

5. Contact the responsible user to notify them or determine why these jobs are innew or incorrect sessions.


Operation Modes

Operation modes allow the SAP R/3 system configuration to be adapted todifferent requirements. The configuration is the mix of the number of dialog(online) and batch processes at different times of the day.

A batch job runs on a batch work process until it is completed and does nottime-share the work process. Therefore, to increase the number of batch jobsthat are processed during a given period, you must increase the number ofbatch work processes. To achieve this increase, you must also decrease thenumber of dialog work processes by the same amount.

This process is usually done to increase the number of batch sessionsavailable to process batch sessions at night, when most of the online usershave gone home and you have many batch jobs to run. During the day, theopposite situation occurs. The number of batch work processes is reduced,and the number of dialog work processes is increased to accommodate thenumber of online users.

For example:

To set up and use the operations modes:

1. Define the operation mode (RZ04).

When switching operation modes, the SAP R/3 work processes are automatically redistributed,without stopping and restarting the instance. Only the work process type changes. For example,a dialog work process can be switched to a background process. The total number of workprocess remains the same.

The new process type is not activated until the process is free, meaning that a process may notswitch immediately. Instead, it is set for switching at the earliest possible time. For example, ifall background processes to be switched to dialog processes still have jobs running, theprocesses are individually switched when the jobs are completed. Processing is not interruptedand normal system operation continues uninterrupted during the operation mode switch.

Operation mode switches are recorded in the system log. The old process type and the newprocess type are recorded for each switched work process.

TechTalk

There must always be aminimum of two dialogprocesses. Do not reduce

the value below two.

There must be at least two batchwork processes on the system. Anindividual instance, such as adialog application server, could beconfigured without a batch workprocess. But there must be batchwork processes to usesomewhere on the system, or atask (such as a transport) can failif it needs a batch work process toexecute.

Mode Dialog WP Batch WP

Day 5 2

Night 2 5

For small clients with little or no batch processing at night, the additional process of configuringand maintaining operation modes may not be necessary. Not using operation modes reducesthe level of administration required to maintain the system. However, once configured andrunning, there is little maintenance required.

Tips & Tricks


2. Assign the instance definition to an operation mode (RZ04).a. The first time the CCMS: Maintain Operation Modes and Instances

screen is opened, there are no operation modes.

3. Define the distribution of work processes for the operation modes (RZ04).This distribution is the mix of dialog and batch work processes.

4. Assign the operation modes (SM63). Define or set the schedule of whenthe modes will switch and to what mode it will switch.

Task

Define the operation mode

1. In the Command field, enter transaction RZ04 and choose Enter (or from theSAP standard menu, choose Tools → CCMS → Configuration → RZ04 - OPModes/instances).

2. Choose .

3. On the CCMS: Maintain Operation Modes and Instances screen:

a. In the Operation Mode field, enter a name or title description.

b. In Description, enter a short description for the mode.

c. Choose .

Make the name anddescriptions meaningful,such as day mode and

night mode, which makes iteasier to select them later.


4. The Operation mode (for example, day) is created.

5. Repeat the above steps for any additional needed operation modes (forexample, afternoon and night).

Task

Assign an instance definition to an operation mode (Initial instance)


Productive OperationModes are for normalSAP R/3 operation. Test

Operation Modes are used forsystems where development workor testing is being done. TestOperation Mode can be switchedmanually or by using thetimetable.


2. Choose Instances/operation modes.

3. To generate an instance definition for our host, from the menu bar, chooseSettings → Based on current status → New instances → Generate.

4. The instances are populated.

5. Choose .


6. Choose . If you add another application server later, repeat steps 3 –5.

Task

Adding additional operation modes



3. Choose an operation mode.


4. Choose .

5. On the CCMS: Maintain Work Process Distribution dialog box:

a. Choose Other operation mode.

b. Choose to select an operation mode.

6. Choose the new Operation Mode (for example, morning).


7. Choose .

8. At this point, you can also define the work process distribution (see DefiningDistribution of Work Processes on page Defining distribution of workprocesses).

9. Choose .

10. Under Op Mode, the new operation mode, morning, appears.


11. Choose .

Task

Defining distribution of work processes


2. Select the operation mode you wish to define (for example, night).


4. Select an OP Mode (for example, night).


5. Choose .

6. Select the Background field.

a. Use the minus (-) or plus (+) buttons to reduce or increase the number ofBackground work processes. This step automatically changes the numberof Dialog work processes by the opposite amount, to keep total number ofwork processes the same.

b. In this example, we increased the number of background work processesfrom 2 to 4.

c. Choose .

Do not change any otherfield.


7. The changes now appear on this screen.

8. Choose .

9. Repeat for all the other operation modes.

10. Choose .

Task

Assign operation modes

1. In the Command field, enter transaction SM63 and choose Enter (or from theSAP standard menu, choose Tools → CCMS → Configuration → SM63 –Operation mode calendar).

Remember that thereshould always be aminimum of:

� Two dialog processes on aninstance

� Two batch work processeson a system


2. Select Normal operation (24hr).

3. Choose Change.

4. This screen shows the timetable. The dashed arrow (= =>) indicates thecurrent time.

5. Double-click on the beginning and ending times when the operation modeshould be in effect.

6. Choose Assign.


7. In Op. mode, choose .

8. Choose the mode to assign (for example, day).

9. Choose .

10. Choose .

11. The operation mode name is next to the time periods you assigned.


12. Repeat steps 5–11 for the other operation mode(s).

13. Choose .

14. The message on the status bar indicates that the assigned operation mode issaved.


15. When the Operation Mode switches, entries appear in the system log(transaction SM21).

Backups

Periodic Archival

At the end of the quarter, make certain you get a usable backup at the end ofthe quarter. Also, send quarter-end backup tapes offsite for an extendedperiod.

At the end of the year, ensure that you get a usable backup at year-end andsend the backup tapes offsite for an extended period.

Be aware that you may have two year-end backup dates:

� End of the calendar or fiscal year

� After the financial books are closed for the year

� This period may be several months after the end of the fiscal year.

Backup the Database

See the procedures in chapters 3 and 9 through 12 based on the database youare using.

Performing a Full Server Backup

An offline backup of the entire server is done at the operating system level.This process requires that the SAP R/3 system and the database be down sothat no files are open.

Your legal and financedepartments, externalauditors, and others

should determine the length of theextended period as appropriate inthe company (for moreinformation, see chapter 3).


Performing an offline backup is necessary for files that cannot be backed up ifthe SAP R/3 system or the database is active. With this full-server backup,you know you have everything on the server. If you experience major systemproblems, you will have a defined point from where everything is backed upand from where you can begin a restore.

A full-server backup should be performed before and after major changes onthe server, such as:

� Installing new software

� Upgrading installed software

� Changing hardware

If a change has a catastrophic effect, you must recover the server to its before-the-change state.

To perform a full server backup:

1. Stop the SAP R/3 system.

2. Stop the database.

3. Stop all SAP services (saposcol, saprouter, sap<sid>-<sysnum>).

4. Execute the backup using your backup program (database and filesystem).

5. Check backup times and logs.

6. Cycle the server.

Task

Check the backups (DB12 & DB13): Database

1. In the Command field, enter transaction DB12 and choose Enter (or from theSAP standard menu, choose Tools → CCMS → DB Administration → DB12-Backup logs).

In NT, there is atechnique where asecond instance of the

OS is installed in a dual bootconfiguration. The backup is takenfrom this second instance.


2. On the CCMS Monitoring Tool - <XXXXX> screen:

a. Record the date and time that appears next to Full R/3 backup.

b. If the backup failed, there is no indication on this screen, except thatthe last successful backup date was not the expected date. You mustreview DB13 to see the indication that the job failed.

c. Choose Backup history to get more detail on the backups.

3. This screen shows the backup. For the backup that ran, you can see thefollowing info:

a. Start date and time.

b. DB name

c. Media name or tape label

d. Position on the backup tape


Task

Checking the backup using the DBA Planning Calendar

1. In the Command field, enter transaction DB13 and choose Enter (or from theSAP Standard Menu, choose Tools → CCMS → DB Administration → DB13-DBA Planning Calendar).

2. On the DB Administration in the SAP Environment screen:

a. Look for the backup job that is listed under each data square.

b. If the backup failed, the job will be indicated in red.

c. Select the entry for the backup.

d. Choose Action logs.In Release 4.6, red-textjobs could also mean thatthe job log is unavailable,

or the job could still be running.


3. The job log from the backup displays.

Operating System Level Backups

The general process is as follows:

1. Record the usual or expected run time for the backup.

2. Compare the actual backup time to the expected run time for the backup.If the backup takes longer or shorter than this time, there may be aproblem that needs to be investigated.

UNIX

For your UNIX-level backup, review the results using the appropriate UNIXbackup application.

NT

We assume that you are using the Windows 2000 Backup application. If youare using another program, use that program’s documentation to determineits status after backup.

Windows 2000 Backup records some log information in the event logs. Amore specific log is written to a file as specified when Windows 2000 Backupis run.

Checking Consumable Supplies

Consumable supplies are those that you use regularly, such as:

� Cleaning cartridges

Any failed backup mustbe immediatelyinvestigated and

resolved.


� Data cartridges (tape and disk)

� Laser printer toner

� Ink cartridges

� Batteries

� Forms

� Envelopes

Within the group of consumable supplies are critical supplies. If thesesupplies run out, your business operations could be affected or stopped.Examples are preprinted forms with your company’s name or other specialprinting and magnetic toner cartridges. The amount of spare suppliespurchased and available on-hand should be enough to accommodate varyingusage levels and to allow for time to purchase replacements.

Running out of supplies will create an inconvenience, or even an operationalproblem.

To check consumable supplies:

� Check the expiration date on supplies that are subject to aging. This checkapplies to supplies currently being used and those in inventory.

� Check supplies that have time-in-service expiration, such as hours, cycles,and so on.

� Keep in touch with your purchasing agent and the marketplace. Marketconditions may make certain supplies difficult to purchase. In suchconditions, the lead time and quantities to be purchased must be increased.For example, at one time, 120-meter DAT tapes cartridges were difficult tofind and purchase.

� Track usage rates and adjust stocking levels and purchasing plans asneeded.

Example

If you run out of the magnetic toner cartridge for the check printer, you will not be able togenerate checks out of the system. At this point, either you cannot print checks to pay yourvendors, or you have to manually type the checks (if you have blank manual check stock onhand).

Special or custom supplies such as the following require special consideration:

� Special magnetic ink toner cartridges to print the MICR characters on checks. Notevery computer supplier will stock these special cartridges.

� Preprinted forms (with company header, instructions, or other custom printing). Dueto the customized nature of these items, there is usually a significant lead time torestock these items.

If it is a critical item, make sure you have extra stock.

Example

Certain DAT tapes are rated for 100 fullbackups. After that they should bediscarded and replaced with new tapes.This usage limit can be entered into theSAPDBA control file for Oracle.



Certain supplies may have long lead times for purchase, manufacture, orshipping.

C H A P T E R

16

16Change Management


Overview

Change management involves the management of changes to your system,including table maintenance, note application, and transportation of changesfrom one system to another. The table maintenance section shows you how tomake changes directly to SAP tables. The new tool, Note Assistant, shows youhow to automatically apply SAP Notes to the system. This chapters alsocovers methods of transporting changes from one system to another, anddiscusses how to manage the transport process.

Table Maintenance (Transaction SM31)

If no transaction is available to maintain a table, it can be directly maintainedusing transaction SM31.

Creating an Entry in the Table (SM31)

This procedure shows how to create new entries in the Prohibited Passwordtable, USR40.

Task

Create an entry in a table

1. In the Command field, enter transaction SM31 or SM30 and choose Enter (orfrom the menu bar, choose System → Services → Table maintenance →Extended table maintenance).

Use this method if, and only if, there is no transaction to maintain the table. Directly maintaininga table circumvents all edits and validations in the system.

When a change is made directly to a table and the table is saved, the change is immediate.There is no undo function.

Caution


2. In Table Views:

a. Enter the table name (for example, USR40).

b. Choose Maintain.

3. If the table you are changing is client-independent, the Information dialog boxappears. Choose .

4. On the Change View <XXXXX>: Overview screen, choose New entries.

5. In the column (the name depends on the table selected), enter the new entry(for example, password).

Client independentchanges will affect allclients on a system, not

just the client on which you areworking.


6. Choose .

7. If the Prompt for Workbench request dialog box appears, create a request bychoosing .

8. On the Create Request dialog box:

a. In Short description, enter text that describes what change you are makingto the table and why you are making the change.

b. Choose .

Note

If the client is not configured to recordchanges for transport, this dialog boxdoes not appear.


9. On the Prompt for Workbench request dialog box:

a. Record the request number. This number is needed to transport the tablechanges to the other systems.

b. Choose .

10. The message in the status bar indicates that the entries have been saved.

11. Choose .

12. The new entry password appears in the table.

13. Choose .


Deleting an Entry from a Table (SM31)

The following task deletes an entry from table USR40.

Task

Delete an entry from a table.

1. In the Command field, enter transaction SM31 or SM30 and choose Enter (orfrom the menu bar, choose System → Services → Table maintenance →Extended table maintenance).

2. On the Maintain Table Views: Initial Screen screen:

a. In Tableview, enter the table name (for example, USR40).

b. Choose Maintain.

3. If the table is client-independent, the Information dialog box appears. Choose.

Client-independentchanges affect all clientson a system, not just the

client you are working in.


4. On the Change View <XXXXX> screen:

a. Navigate to the password by scrolling up or down to go through the tableor choose Position to go directly to the entry.

b. Select the password to delete (for example, password).

c. Choose .

5. The message in the status bar indicates that the password was deleted.

6. Choose .


7. The message in the status bar indicates the change was saved.

Change Control

Change control is the managing of the changes, modifications andcustomizing made to your system. This control allows you to be aware of andcontrol what changes are made. These changes must be made in a controlledmanner to avoid problems.

The process is:

� Managing the changes:

• SAP Notes that are applied to the system

• Authorization process for moving the changes from one system toanother

� Making the changes to the SAP R/3 system

� Moving the changes from one system to another

Managing SAP Notes

Managing SAP Notes means tracking the notes that you have reviewed andapplied. These notes are release- and configuration-specific and may relate toyour system’s configuration. Some of these notes may actually be specific toindividual systems in your environment.

Reasons to track SAP Notes applied to your system include:

The SAP training classBC325 (SoftwareLogistics) covers change

management and transports. Alsosee Software Logistics by SueMcFarland.

Note

SAP Notes were formerly known asOSS notes.


� If a problem arises, SAP may ask if a specific note has been applied. If youdo not have a record of what notes you have applied, then you mustmanually investigate your system. This process can be difficult and timeconsuming.

� When the system is upgraded, for conflict resolution, you must know whatnotes have been applied. You must know what notes:

• Are included in the upgrade, so you can go back to SAP standardcode

• May need reapplying because they are not included in the upgrade

� Document all SAP Notes applied to your systems, and specify whichsystem and instance to which it is applied.

� Document all code changes with the SAP Note number that applies. Thisdocumentation is especially important if a program is changed by anupgrade or support package. It helps you determine if your code change isincluded in the upgrade or patch and, therefore, whether the program canrevert back to SAP standard.

� In addition to a high-level tracking table, detailed records should be kepton the individual notes. The record should include the problem to be fixed,objects changed, release in which the note was fixed (important forupgrades), and other applied or recommended notes (see the sample formin “Detailed Online Service System Note Record” on page 474).

� Document all SAP Notes that are noted and do not require actual changesto be made to the system (for example, procedural or informational notes).

� Document SAP Notes that have not been applied to your systems. Theremay be cases in which you review a note and determine that it does notapply. You should document the reasons. If SAP asks why a specific notewas not applied, you will have an answer.

Sample Forms

General Note Record

Note # Description Noted DEV QAS PRD

12345 xxx 11/06/98 11/15/98 11/30/98

36987 yyy 2/06/99 2/13/99 2/28/99


Detailed Online Service System Note Record

Note - Applied

Note #:

Short text:

Module:

Problem to solve:

Objects changed:

Fixed in release:

Comments:

Other notes applied withthis problem:

Applied to:

System Client Transportnumber

Date importedor applied

Return code Sign-off/Initial

DEV 100

110

QAS 200

210

PRD 300


Note Assistant

Note Assistant is an add-on installation tool for the quick implementation ofspecific SAP Notes. It checks for dependencies on any Support Packages, SAPNotes, or modifications that you have already implemented. The toolstreamlines the implementation of note-based corrections in a consistent anduser-friendly manner. Because it applies code changes in SAP Notesautomatically, the Note Assistant helps to reduce errors.

The Note Assistant logs all your processing steps automatically. You candisplay an overview of all the SAP Notes that have been implemented in yoursystem. It also displays the processing status of the SAP Notes and anycorrections that have already been made to the source code. You can see atanytime which SAP Notes you have already implemented successfully andwhich you still must process.

The Note Assistant is available for download through the SAPNet-Web.There are minimum preconditions of Support Packages applied for systemswith Basis releases before 6.10:

For information on how to determine what support packages have beenapplied, please refer to Special Maintenance – Support Packages in chapter 22.

Not all available notes have been updated or converted for use with the NoteAssistant. To find out more about Note Assistant, see the SAPNet-Web underthe Quick Links NOTEASSISTANT.

The SAP Service connection must be open through transaction OSS1.

Task

Loading an SAP Note

1. In the Command field, enter transaction SNOTE.

Release Minimum Precondition

4.6D SAPKB46D05 (or higher)

4.6C SAPKB46C15 (or higher)

4.6B SAPKB46B25 (or higher)

4.5B SAPKB45B38 (or higher)


2. Choose SAP Note Download.

3. In the Note Assistant Download Note dialog box:

a. In Note number, enter the SAP Note number (for example, 414452).

b. Choose .

4. On the Note Assistant: Worklist for User <XXXXX> screen:

a. The note is shown under the New status.

b. Select the note.

c. Choose Display SAP Note.

5. The Implementation status shows whether the Note Assistant can implementthe note automatically.


6. Choose .

Task

Implementing an SAP Note

1. Choose .


2. Choose Yes.

3. Choose .

4. To create a transport request, choose .

5. On the Create Request dialog box:

a. In Short description, type a short description.

b. Choose .


6. Choose .

7. Choose .

8. On the Note Assistant: Worklist for User <XXXXX> screen:

a. The note is now under In process status and the icon next to the note ischanged.

b. Select the note.

c. Choose .

9. The Implementation status has changed to Implemented completely.


10. Choose .

Task

Setting processing status of SAP Notes

1. Select the note that has just been implemented.

2. Choose .


3. In the Set Processing Status for Note <XXXXX> dialog box:

a. Select Completed.

b. Choose .

4. The note is removed from the screen.

Task

Viewing Log File

1. Choose .


2. On the Note Assistant: Note Browser screen:

a. In Note number, enter the note number.

b. Choose .

3. Choose .


4. The log file is shown. You can add your own comments to the log file bychoosing .

Change Control (Managing Transports)

Change control is the process of managing changes, modifications andcustomizing made to the system. Change control also manages the transportof those changes through the pipeline from the development to the testsystem, and finally to the production system. One of the most importantchange management tasks involves notifying the appropriate people of thechanges and getting their approval.

Because SAP R/3 is an integrated system, some items may impact many othermodules or groups. Ensure that you contact the appropriate people beforechanging a module that will impact the performance of other modules. Ifsomething stops functioning in the production system, business may stopuntil the problem is resolved.

In change control, there is a review and approval process. You should notmake a change and apply it to the system without a review and approval ofthe changes. These changes apply to changes to SAP objects and systemconfiguration.

In the past, mostapplication systems wereindependent, so changes

in one system were insulated fromthe other systems. Because of thisindependence, users may not beused to consulting with otherorganizations when makingchanges to what they considertheir systems.


The following steps demonstrate a change control process:

� Document all code, configuration, and other changes.

� Test by developer and functional analyst

� Get the following signoffs (see sample Transport Request Form on pageSample Transport Request Form)

• By all functional groups:

•Review and be aware of changes that might affect their functionalareas.

•If needed, perform additional tests by and with other functionalgroups, where there is possible interaction from the change.

• Operations review

•Review any changes that may affect the operations staff

•Schedule new jobs

•Program error or problem procedure

Document the program restart procedure. Is it safe for the operator to restartthe job, if it fails or hangs?

� Verify the change in the target system. Change control should also containa recovery plan that includes:

� What to do if the import to the production system creates a problem?

� How to roll back? Will it be possible to roll back?

� Will a problem require a database restore?

A transport cannot beundone.


Sample Transport Request Form

Request to Transport

Transport number:

Transport title/description:

Objects:

SAP Notes applied:(SAP Note formrequired for eachnote)

Effect on other functional areas:

Special transport instructions:

Specific order Need quiet time: Yes/No

Request for transport by:

Tested by:

Functional area review and approval:

FI MM Computer Operations

SD

Approved for transport by:

Transport details:

System Client Date Start time End time Return code Sign-off/Initial

QAS 200

210

PRD 300


Transporting Objects

Transports into the Production System

A transport is the mechanism that the SAP R/3 system uses to move changes:

� Within a system from one client to another client

� From one system to another system on the same client

� From one system to another system and from one client to another client

Complete the transport in the production system during a quiet period (forexample, Sunday afternoon or evening) when users are not logged on thesystem.

Ideally, a full system backup should be completed before transports areimported.

During a transport, objects may be overwritten. If an object is being used inthe target system when a transport is performed, the transport may causeinconsistent results or terminate the transaction. In the worst-case scenario, atransport may break the production system and you must restore the system.

Transports are only done when necessary (when you have a transport thatneeds to be moved). You may also have the occasional emergency transportthat must be moved at a time other than at your normal weekly transporttime.

Transporting Objects

The transport system has been significantly changed in Release 4.x. (It wasformerly known as Correction and Transport System.) It is still CTS, but is nowcalled the Change and Transport System. CTS contains the TransportManagement System (TMS) and Change and Transport Organizer (CTO).

The purpose of transports is to move objects and configuration from onesystem to another in the production pipeline. This pipeline is defined in athree-system landscape as systems comprising development, qualityassurance, and production. A transport starts in the development system, istransported to the quality assurance system where is tested, and finally intothe production system.

To transport objects, use one of the following methods:

� Transport Management System (TMS)

� Operating System (OS)

Transports are taught inBC325 (SoftwareLogistics).


TMS Method

The TMS method uses transaction, STMS, to perform the transports.

Benefits:

� The user does not have to go into the operating system to do the transport.

� The user selects the transport from a GUI to do the import. There is no riskof incorrectly typing the wrong command or transport number.

� Because the import is done from within SAP R/3, there is no need tophysically go down to the server or use a remote connection (for NT) to theserver to do the import.

� The transport route can be specific to clients. With one export, the TMSsystem is set up to import into several combinations of system and clientas defined in the transport route. (This functionality is new in Release 4.6.)

� Transport requests can be grouped into projects, and the transport requestselected and moved by these projects. This grouping reduces the chancesof transporting the wrong transport request when there are many activitiesand projects going on. (This functionality is new in Release 4.6.)

� Advanced quality assurance prevents transports from being imported intothe production system until they are released after successful testing in thequality assurance system. (This functionality is new in Release 4.6.)

� The import of transport requests can be scheduled. You no longer have tomanually import the transport requests or write scripts to do the import.(This functionality is new in Release 4.6.)

TMS documentation. The TMS documentation (including configuration)can be found in the SAP R/3 online documentation by choosing Help→ SAPLibrary → Basis Components → Change and Transport System (BC-CTS) →Transport Management System (BC-CTS-TMS).

Operating System Method

The operating system (OS) method requires you to go down to the OS level toexecute the transport program (tp) at the command line.

Disadvantages:

� The user must go into the operating system to do the transport. This actionis a security issue in companies that restrict which employees can have thislevel of access.

� The import is done from the command line. There is the risk of incorrectlytyping and importing the wrong transport.


Standard Transport Process

This section describes the standard transport process from your developmentsystem to your production system.

The following steps are part of your company’s change management process:

� Obtain proper authorization to transport the objects.

Obtaining this authorization is the responsibility of the person requestingthe transport move. The required authorizations and approval processdiffer based on the company. Some companies require the approval ofonly one person, while other companies require the approval ofnumerous people.

� Define other necessary transport management related information, suchas:

• Who to contact in case of problems

The person doing the transport typically is not a programmer. If thereis a problem with the transport, that person will need assistance todetermine what failed.

• What recovery process to follow if the transport fails

• Who will test the transport in the target system to determine that itworks as intended

• The transport number

• The source system

• The target system(s)

• Relationship to other transports, such as sequence order, and so on

� Use transactions SE01, SE09, or SE10 as necessary to release the transport.

� First release the task, and then release the request or transport.

� Import the request into the target system.

� Check the transport log.

Importing the Entire Import Buffer

If you import the entire import buffer, everything in the buffer will beimported into the target system, regardless of whether all the transports areready. The problem with importing the entire buffer is that the varioustransports may be in different stages of testing. Some may be finished, whileothers may still be in the process of being tested. An import all imports all theobjects in the buffer, regardless of whether they are ready to be transported.

A new feature in Release 4.6 is the Advance Quality Assurance. This featurerequires that requests imported into the quality assurance system must beapproved in the quality assurance system to be transported to the productionsystem. This process helps prevent the accidental transport of a request that

A major purpose of theapproval process is togive other functional

groups notice as to what you aremoving.

If the move affects any of thefunctional groups, and they areaware of it, they can take theappropriate action: review, test,and so on. If necessary, yourtransport is delayed until theaffected functional groups aresatisfied.

The TMS (normal) importand one of the OS importoptions, tp import

all, will import all transports inthe import buffer. The assumptionis that all objects released into theimport buffer have been tested andapproved for transport into thetarget system. If you use eithermethod, it is important to notrelease the objects until they havebeen tested and approved fortransport.

Up to, and including Release 4.5,in a three-system landscape, oncethe transport is imported into thequality assurance system, it isadded into the production systemimport buffer, and there is nosecond release out of the qualityassurance system.


has not completed quality assurance testing in this system. This change is animportant change management enhancement and should be used byeveryone with a standard three-system landscape.

Before Release 4.6, when a transport was imported into the quality assurancesystem, it was automatically added to the import buffer of the productionsystem. Therefore, an import all would import everything, regardless ofreadiness.

To manage the import buffer in the:

� Source system, do not release the transport until the testing is complete.

� Production system:

• Using the TMS method, use preliminary import to select the individualtransport to import

• Using the TMS method, use the project method to manage thetransport requests

• Using the OS method, import the requests (transports) individually

• Do an import all only when the entire buffer is ready to be imported

Special Transports from SAP

Special manual transports fix specific problems, add features, or addfunctionality from third-party software vendors. U.S. customers candownload the transport files from SAPSERV4. These files are usually a singlefile that you have to unpack using the CAR program. The downloading andunpacking procedure is described in chapter 22.

Get the files from SAP or the delivery media, such as a CD. Two files(sometimes there is a third file) are normally combined as a set (for example,K174511.P30, R174511.P30, and D174511.P30).

Copy the files into the appropriate transport directories:

Copy files beginning with K into:

� NT <drive>:\usr\sap\trans\cofiles\\<host>\sapmnt\trans\cofiles

� UNIX /usr/sap/trans/cofiles

Copy files beginning with R and D into:

� NT <drive>:\usr\sap\trans\data\\<host>\sapmnt\trans\data

� UNIX usr/sap/trans/data

Add the special transport to the import buffer (process described in “Addinga Special Transport into the Import Buffer” on page 495).

Note

D files do not always exist.


Import the transport (process described in “Using TMS to import a transportrequest” on page 498 and “OS Method of Transporting” on page 507).

Releasing a Request (Transport)

To release a request, release all tasks associated with the request and thenrelease the request.

Task

Release a request (transport)

1. In the Command field, enter transaction SE10 and choose Enter (or from theSAP standard menu, choose Tools → Accelerated SAP → Customizing → SE10 -Transport Organizer).

2. On the Transport Organizer screen:

a. In User, enter the user ID of the person who owns the request.

b. Select the following categories:

• Customizing

• Workbench

c. To verify the Request status, select Modifiable. As an option, you maydeselect Released.

d. Choose Display.

Note

Over time, the released list will be large.


3. On the Transport Organizer: Requests screen:

a. Select the task to release.

b. Choose .

4. On the Change Request/task: <XXXXX> screen:

a. Document the content of the transport.

b. Choose .

5. A message appears on the message line indicating the task was released.

6. Choose .


7. A message indicates that the task was released into the specified request.

Task

Release the request

1. On the Transport Organizer: Requests screen:

a. Select the request.

b. Choose .

2. As the export is running, the In process Requires update line appears.

Note

All of the tasks associated with arequest must be released, before therequest can be released.


3. Choose .

4. When the export is finished, the above message changes to a status message.

5. Check the export return code and text message. This screen shows that theexport Ended OK and has a return code of 0.

6. Check the test import return code and text message. This screen shows thatthe import Ended OK and has a return code of 0.

The return codes are:

� 0 – Successful

� 4 – Warnings occurred

� 8 – Performed with errors

� 12+ - Transport was terminated

7. Choose .

A return code of 8 orhigher is a failedtransport.


8. A message appears indicating that the request was released and exported.

9. The request is now in the Released section. You can see this request only if youselected to view released requests in step 1 of releasing a task.

If there is a problem, review the transport log. For more information, see thetransport log later in this chapter.


TMS Method of Transporting

Adding a Special Transport into the Import Buffer

Adding a special transport into the import buffer is usually not done. Therelease process adds the transport into the appropriate input buffer. This taskis only performed for special transports that are downloaded from SAP.

Prerequisite. The transport files have been moved into the appropriatedirectories.

Task

Add a special tranport into the import buffer

1. In the Command field, enter transaction STMS and choose Enter (or from theSAP standard menu, choose Tools → Administration → Transports → STMS-Transport Management System).

2. The Transport Management System (TMS) screen appears. This screen is thetransaction that all the following TMS processes will start from.

3. From the Transport Management System screen, choose .

4. Position cursor on the <SID> of the SAP R/3 system to which you want toadd the transport.

To access TMS’s onlinedocumentation, choose:

�SAP Library → BasisComponents → Changeand Transport System (BC-CTS) → TransportManagement System(BC-CTS-TMS)

� Transport ManagementSystem(BC-CTS-TMS)

Under Transport ManagementSystem, there are five majortopics:

� Configuring TMS

� Performing Transports

� Approving or RejectingRequests

� Transport Workflow

� Troubleshooting


5. Choose .

6. From the menu bar, choose Extras → Other requests → Add.

7. On the Add Transport Request to Import Queue dialog box:

a. Enter the transport number.

b. To continue, choose .


8. Choose Yes.

9. The progress is shown on the status bar.

10. The special transport is now in the system buffer.


Task

Using TMS to import a transport request

1. From the TMS screen, choose .

2. Select the <SID> of the system into which the request will be imported.

3. Choose .

4. From this screen, you have two options:

� Preliminary ImportSelectively import requests one at a time


� Import AllImport all the requests in the queue for the selected system

Task

Import a selected request

1. Choose .Be careful to choose thecorrect icon. The two aresimilar in appearance.


2. On the Import Transport Request dialog box:

a. In Target client, enter the target client.

b. Select the Execution tab.

3. Select Execute synchron.


5. The Options tab allows you to select special import options. These optionscorrespond to the unconditional codes used when transporting at the OSlevel.


6. Choose .

7. Choose Yes.

8. Under Remote logon, enter the correct Client number, User and Password.

9. Choose .


10. The import process begins and may run for a while. You can monitor theprogress of the import by watching the process indicators.

11. The Request number now appears with a green check, indicating that it wasimported as a “preliminary import.”


Task

Import all requests

1. At this point, all the requests shown in the input buffer will be imported andindicated in the Request column. Choose .

2. Enter the target client number.

3. Choose the Execution tab.

4. Select Execute synchron.



6. Choose .

7. Choose Yes.

8. The import process begins and may run for a while. You can monitor theprogress of the import by watching the process indicators.


9. To refresh the screen periodically, choose .

10. When completed, the message Import queue is empty appears.

11. Choose .

Task

Check the transport log

1. From the TMS screen, choose .

2. Select the <SID> of the SAP R/3 system for which you want to check thetransport log.


3. From the menu bar, choose Goto → tp system log.

4. Choose (or from the menu bar, choose Edit → Refresh).

5. Check the final return code:

� 0 (Successful)

� 4 (Warning)

� 8 (Error)

� 12 (Fatal)-6

Anything other than a 0 or 4 is considered a failed transport.

6. From the menu bar, choose Goto → Transport steps (this was formerly knownas alog).


7. From this screen, you can verify the request number and the return code forthat request.

8. The return code (indicated in column RC) is the same as in step 5 above.

By using TMS to review the transport logs, the inconsistency encountered inthe OS method of viewing the transport log does not occur. The inconsistencyis when the tp return code (received when the import is done) does not matchthe return code in the transport log. The following line would appear in theabove screen:

OS Method of Transporting

Adding a Special Transport Into the Import Buffer

Adding a special transport into the import buffer is normally not done. Thistask is only performed for special transports that are downloaded from SAP.

The transport files have been moved into the appropriate directories. Youmust be on the target system. For example, if it is from development (DEV) totest (QAS) system, you must be on QAS.

Task

Add a special transport into the import buffer

1. Go to the transport program directory:

� NT: <drive>:\usr\sap\trans\bin

Request SID S RC

ALL SAS S 0008


� UNIX: /usr/sap/trans/bin

2. Check if file tpparam exists. If no, copy file tp_domain_<sid>.pfl into a new fileand rename it tpparam.

3. Load the transport into the import buffer with the following command:

tp addtobuffer <transport> <target sid>

tp addtobuffer P30K174511 DEV

Where:

� Target system is DEV

� File is K174511.P30

� Transport number is P30K174511

� The transport number is derived from the transport file number, where thefirst three characters are the file extension (P30), and the rest of the nameis the base name of the file (K174511).

4. Import the transport.

Importing the Transport

You must be on the target system. For NT, on the target system, you musthave mapped a drive to the shared directory (\sapmnt) on the source system(for example, where drive S: is mapped to \\devsys\sapmnt).

Task

Import the transport

1. Go to the transport directory.

NT: <drive>:\trans\bin

UNIX: /usr/sap/trans/bin

2. Test your connection to the target system with the following command:

tp connect <target sid>

tp connect PRD

3. Enter the transport command. To specify an individual transport, enter:

tp import <transport> <target sid> client=<target client>

tp import devk900023 PRD client=100

Where the:

• Transport number is devk900023


• Target system is PRD

• Target client number is 100

� To import the entire import buffer, enter:

tp import all <target sid>

tp import all PRD

4. Record the start and finish time for the transport on the transport log or thetransport form.

5. Check the exit code. If you receive an exit code of 8 or higher, the importfailed. You must resolve the problem and reimport the transport. If you get areturn code of 8, there is a known condition where this return code does notmatch the transport log. This condition is described in Checking the TransportLog section below.

6. Check the transport log.

Checking the Transport Log (Transaction SE10)

The transport log indicates why a transport failed.

The information in this chapter is only a portion of the first half of the process,that is, determining if the transport succeeded or failed. The second half of theprocess, investigating why the transport failed, is not covered. If the transportinvolves an object such as an ABAP program or SAPscript layout, you willneed the assistance of your programmers to determine why it failed and howto fix it.

After the transport is completed, check the transport’s exit code:

� 0 = OK

� 4 = Warning

� 8 = Error

� 12 = Severe Error

If you receive an exit code of 8 or higher, the import failed. You must resolvethe problem and re-import the transport.

Task

Check the Transport Log

1. In the Command field, enter transaction SE10 and choose Enter (or from theSAP standard menu, choose Tools → Accelerated SAP → Customizing → SE10-Customizing Organizer).

You may be instructed inan SAP Note or by theSAPNet hotline to use

Unconditional codes or U codes.These are special program optionswitches that the tp program usesduring the import process.

In NT, use QuickSlice, anapplication included withthe NT resource kit, and

the CPU activity in the NTPerformance Monitor to monitorthe import process. After a fewtimes, you will recognize theactivity pattern of a transport.

In UNIX, use the utilities top orxload to monitor the importprocess.

The transport could stillhave failed even if youdid not receive a failed

return code. The final test is toverify in the target system that thetransport arrived properly. Thedeveloper and functional areaowner are responsible for thisverification.

Note

Note: You must check the transport logfrom the transaction that released thetransport (SE09 or SE10).


2. On the Transport Organizer screen:

a. Under Request type, select Customizing and Workbench

b. Under Request status, deselect Modifiable, and select Released.

c. Enter a date range in the Last changed From and To fields to limit theamount of requests to review.

d. Choose Display.

3. Select the request.

4. Choose .


5. On the Import line, check the return message and code:

� 0 – Successful

� 4 – Warnings occurred

� 8 – Performed with errors

� 12+ – Transport was terminated

6. If you see a warning in step 5, choose for the line with the warning.

7. Choose to drill down for additional details.

8. The status bar indicates how many levels you have drilled down.

A return code of 8 orhigher is a failedtransport.

You may run into a rareinconsistency betweenthe return code in this log

and the return code when you ranthe tp import program. Thiscondition occurs when the tpprogram ends with a return code 8(Error) and the log above shows amaximum return code of 4(Warning). This inconsistency iscaused by a step in the import thatis not associated with the transportnumber (in the exampleRW6K9000079). Thus when thelog is reviewed, the maximumreturn code of 4 [(and not 8)(Warning)] appears. However, it isstill a failed transport.

The TMS method does not havethis inconsistency.

P A R T S E V E N

FTroubleshooting and Performance Overview


Part Overview

This section discusses basic system troubleshooting and performance issues. In the eventthat problems do occur, this section gives you general ideas of things to look for.

This is a light section and does not replace the specialized books and classes that SAP hasfor this topic. It is meant to provide the basics to begin working from.

C H A P T E R

17

17Troubleshooting


Overview

This chapter is a basic troubleshooting chapter, presenting you with sometools and techniques to help you solve the problem yourself. We do not gointo advanced troubleshooting techniques. Troubleshooting is learned bydoing; the more experience you have, the better you become.

The next chapter is on performance tuning. Performance tuning is specializedtroubleshooting. Troubleshooting techniques are also relevant forperformance tuning.

Basic Troubleshooting Techniques

The general procedure when working on troubleshooting is not new. It is thestandard problem solving procedure that has been in use for years by manyprofessions. Your auto mechanic would follow the same procedure whenrepairing your car:

� Gather data

� Analyze the problem

� Evaluate the alternatives

� Make a change

� Remember to make only one change at a time.

� Document the changes

� Evaluate the results

Gather Data

Ask the following questions:

� What is the problem?

� What error messages, dumps, or other diagnostic aids are available fromthe problem?

� What conditions caused the problem?

� Is the problem repeatable?

To analyze the problem, use your available tools, such as:

� System Log (SM21)

� Update Failure (SM13)

� ABAP Dump (SM22)


� Spool (SP01)

Analyze the Problem

What are the resources you have to help solve the problem:

� Online documentation

� Reference books

� SAP Notes

� Other customers (this is your network)

If necessary, call consultants or the SAPNet help desk for assistance.

Evaluate the Alternatives

Are there any possibilities or resources you may not have considered?

Make only One Change at a Time

If there is a problem and you made several changes at once, you will notknow which change caused or fixed a problem.

There are times where several changes must be made to fix a problem. Unlessthey must be done together, such as related program changes, make thechanges separately.

Document the Changes

If a change causes a problem, you must undo the change. To do that you mustknow what the configuration was before the change and what you did.

If the change needs to be applied to multiple systems, you must know exactlywhat changes to make and how to do it. This process must be repeatedexactly the same on all systems.

Get the Complete Error Message

When you get an error message in an SAP R/3 transaction, you need all theinformation on the error to forward to SAP. To get the complete errormessage, perform the following task.

Task

Get the complete error message

1. When an error occurs, the field with the error is highlighted.


2. Select the error message.

3. The error message appears in the dialog box.

4. Record the relevant information from the screen to send to SAP.

Get the SAP Patch Level

This level is the SAP R/3 kernel patch level that is being used.


This patch level is needed when submitting problem messages to SAP. It tellsthe hot line personnel your kernel patch level. Different problems are fixed indifferent patch levels.

Task

Get the SAP patch level

1. In the Command field, enter transaction SM51 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → Systemmonitoring → SM51-Servers).

2. Select the central instance (for example, pa102058_SA1_00).

3. Choose Release notes.

4. Record the Patch level (for our example, we chose Patch level 620).

Example

You are on patch level 50 and have a particular problem. The fix to your problem may havebeen done in patch level 61. This level identifies that the problem is an older kernel thatcontains the problem. The solution is to upgrade to the current kernel, at least patch level 61.


Determining What Support Packages Have Been Applied

A support package is an SAP-provided R/3 fix and is similar to an NT ServicePack. As with the SAP Patch level, problems you have may be related to thelevel of the applied support package.

Task

Display applied support packages

1. From the menu bar, choose System → Status.

2. On the System: Status dialog box, under SAP System data, choose .

3. Choose the SupPack tab.

4. In this example, the following patches have been applied:


� SPAM update 06/29/2001, 4.6C ver 0028.

� Support Package:

� ABA – sp20

� Basis – sp16

� R/3 – sp16

� Others listed offscreen

� Patch Status values are:

• N – The patch has not yet been applied

• I – Patch has been successfully applied

• ? – Patch application has been aborted

The name of a Support Package is interpreted as follows:

� SAPK<component><release><sequence_number>

� SAPKH46C01 is interpreted as SAPK/H / 46C / 01, and is for SAP R/3 4.6Cand is the first Support Package.

C H A P T E R

18

18Performance


Overview

This chapter discusses performance issues in SAP R/3. We provide onlygeneral guidelines, not detailed performance tuning instructions. It is notpossible in one chapter to provide the breadth and depth of informationavailable in the SAP training class or the Performance Optimization book. Formore detailed performance tuning, we recommend the following resources:

� BC315 – R/3 Workload Analysis (the SAP Performance Tuning class)

� SAP R/3 Performance Optimization, by Thomas Schneider, SAP’s TCCorganization.

� Performance tuning is specialized troubleshooting. Because you are tryingto solve performance issues, all troubleshooting techniques are alsorelevant.

Rather than using database and operating system-specific details, we will beusing SAP R/3 transactions to access relevant database and operating systemdata where possible. This approach makes the information database andoperating system independent.

Critical Assumption

The hardware, operating system, database, and SAP R/3 have been properlyinstalled based upon SAP’s recommendations.

As with the design of this book, performance tuning must have a startingpoint. This point is the SAP-recommended configuration for hardware,database, operating system, network, and so on.

A real example of a non-recommended configuration is where the operatingsystem, the database, and SAP R/3 has been installed on a single logicaldrive. In this situation, all the drives in the server were configured in a singleRAID5 array and treated as a single, huge drive. This situation created aclassic condition known as head contention, where SAP R/3, the database,and the operating system all simultaneously competing for the same diskdrive head.

This is an example of a problem that is not new. Head contention existed inthe early days of computing. The solution now is essentially the same as itwas back then, to spread the data over multiple drives.

Priority of Evaluation

The SAP EarlyWatch group has determined that the majority of theperformance issues and gains are from within SAP R/3. This gain is followedfirst by database issues, then operating system, and then hardware. We willprimarily discuss SAP R/3 performance issues.


General Procedure

The general procedure when working on performance issues is not new. It isthe standard problem-solving procedure:

� Gather data

� Analyze the problem

� Evaluate the alternatives

� Make only one change at a time

If a problem exists, you will not know which change caused a problem.There are times where several changes must be made to fix a problem.Even so, unless they must be done together, such as related programchanges, make the changes one at a time.

� Document the changes.

• If a change causes a problem, you must undo the change.

• To do that you must know what the configuration was before thechange and what you did.

• If the change needs to be applied to multiple systems, you must knowexactly what changes to make, and how to do it.

• This process must be repeated exactly the same on all systems.

SAP R/3

As a prerequisite, SAPOSCOL (SAP OS collector) service must be running.Also, periodic job SAP_COLLECTOR_FOR_PERFMONITOR must berunning. Finally, wait at least 1 week to collect sufficient data for statistics tobe useful.

Workload Analysis of the System (Transaction ST03N)

Workload analysis is used to determine system performance. You shouldcheck statistics and record trends to get a feel for the system’s behavior andperformance. Understanding the system when it is running well helps youdetermine what changes may need to be made when it is running poorly.

Task

Analyze system workload

1. In the Command field, enter transaction ST03N and choose Enter.

Note

One of the most common causes ofSAP R/3 performance problems ispoorly written custom (or modifiedstandard) ABAP programs.


2. On the Administrator tab, to change to Expert mode, choose .

3. To select a time period to analyze:

a. Choose Detailed analysis → Last minutes load.

b. Double-click on pa102058_SA1_00.


4. On the Last Minutes Load on <XXXXX> screen:

a. Under Analysis Interval, enter the Date and Time period to be analyzed.

b. Under Analysis parameters, enter how many minutes back to analyze.

c. Choose .

5. The different task types are shown. The task types are:

� AutoABAP

� Background

� Buffer synchr.

� Dialog

� RFC

� Spool

6. Choose a task type.


7. Choose to view performance values for that Task type.

8. In the Details dialog box:

a. Examine Average response time per step (ms). If the dialog value is less than1,000 ms (1 second), the response time meets the target standard responsetime. For more information on Av. response time, see notes below.

b. Choose .

9. Under Analysis views, select Transaction profile.

10. Double-click on Standard.

Apply judgment whenreviewing statisticalvalues. If you just started

the SAP R/3 system, the bufferswill be empty and many of thestatistics will be unfavorable.Once the buffers are loaded(takes approximately 1 week),values can be properly evaluated.

The SAP R/3 user defaultfor a decimal point is acomma. If your default

profile for decimal point (point orcomma) is not appropriately set,the display may be misread. Forexample, rather than 476.5 ms, itwould read 476,5 ms.


11. Select the column heading Average response time (φRes…).

12. Choose .

13. The programs and transactions are now sorted in average response timeorder.

A few standard functional transactions will exceed the one-second guideline.They include, but are not limited to the following:

Buffers (ST02)

The buffer tune summary transaction displays the SAP R/3 bufferperformance statistics. This transaction helps in tuning SAP R/3 bufferparameters. The buffer is important because significant buffer swappingreduces performance. Look under Swaps for red entries. Regularly check theseentries to establish trends and get a feel for buffer behavior.

Analysis of transactionST03N is covered inBC315 (the Workload

Analysis and Tuning class). Werecommend you take this class.

Type Transaction

Create Sales Order VA01

Change Sales Order VA02

Display Sales Order VA03

Create Billing Document VF01

Create Delivery VL01

Maintain Master HR data PA30


Task

Display buffer performance statistics

1. In the Command field, enter transaction ST02 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → Performance→ Setup/Buffers → ST02-Buffers).

2. The two important things to review on the above screen are:

� Hit Ratio

The target value is 95 percent and higher. Soon after starting the system,this value is typically low, because buffers are empty. The hit ratio willincrease as the system is used and the buffers are loaded. It usually takestwo hours to a day to load the buffers that are normally used.

� Swaps

The target value for the program buffer is less than 1,000. All other buffershave a target of 0. When the necessary data is not in the buffer, the systemretrieves the data, but it cannot fit into the buffer because of filling level orfragmentation. Other objects are thrown out of the buffer to make roomfor the new data, which is called a swap. The swap value is reset to zero (0)when the system is restarted. If swaps exist, increase amount of memoryallocated to the buffer. See SAP Note 103747.

Memory Defragmentation

A computer’s memory for program execution (PXA) behaves similar to a harddisk. As different programs execute, they are loaded into, and later deletedout of, memory. Over time, like a hard disk, the usage of the computer’smemory becomes fragmented with unused spaces scattered throughout.

Analysis of transactionST02 is covered inBC315 (the Workload

Analysis and Tuning class). Werecommend you take this class.


At a certain point you may have sufficient free memory (the total of all theunused spaces), but not a contiguous (single) piece of memory large enoughto allow certain programs to execute. At that point, those types of programsattempting to run that need contiguous memory will fail because they cannotbe loaded into memory.

To defragment the system’s memory:

1. Stop SAP R/3.

This step requires stopping only SAP R/3 on all application and databaseservers. (For more information, see “Starting the SAP R/3 system” onpage 88. )

2. Restart SAP R/3.

You only need to restart SAP R/3, you do not need to cycle the server.

Database

See chapters 9 through 12 (Database Administration) for the database-relatedperformance tuning transactions:

� Activity - ST04

� Tables/Indexes - DB02

Operating System

Operating System Monitor (OS07)

The operating system monitor allows you to view relevant operating systemand hardware details.

The operating system-related detail shows information such as:

� Memory paging

� Operating system log

When SAP R/3 is restarted, the buffers are refreshed. This process means that the first personwho accesses the buffered object will have a long response because the system must get thedata from the database and load it into the buffer. The second person who accesses the samedata will have a normal (quick) response time. This process repeats until all normally usedobjects are loaded into the buffer, which usually takes up to a day to accomplish. The programbuffer is filled without fragmentation with the programs that were in the buffer during shutdown.

To defragment the PXAbuffer, stopping SAP R/3is sufficient. You do not

need to restart the database topreserve the database cache.

TechTalk


In addition, the following hardware details are available:

� CPU utilization

� Free space on disks

Certain operating system items will impact SAP R/3 performance.

To view the Operating System Monitor, ensure that SAPOSCOL service isrunning.

Task

View the Operating System Monitor

1. In the Command field, enter transaction OS07 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Monitor → Performance→ Operating System → Remote → OS07-Activity).

2. Select the appropriate server.

3. Choose .

4. The following screenshot is a snapshot of the CPU, Memory, Swap, and Diskresponse data.

CPU idle average shouldbe > 20% during workingdays. Otherwise CPU

contention probably exists.

Paging:

� Unix: paging OUT ratesshould be less than 300MB/hr.

� NT: paging IN rate shouldbe less than 500 MB/hr.


5. To analyze, choose Detail analysis menu.

6. Under Performance database, choose Compare recent days.


7. This screen shows recent days value of the server.

8. This window shows the memory paging and free memory over time.


9. This is the Operating System Log.

Hardware

CPU and Disk

Also see Operating System – Operating System Monitor (OS07) to get data on:

� CPU utilization

� Free space on disks

Memory

The hardware item that has the largest effect on SAP R/3 performance ismemory. The SAP R/3 system uses memory extensively. By keeping data inbuffer, physical access to the drives is reduced. Thus, in general, the morememory you have, the faster SAP R/3 will run.

Physical access to thedrives is the slowestactivity.

P A R T E I G H T

GMiscellanous Topics Overview


Part Overview

This section discusses the SAP Service Marketplace, SAP’s remote services (SAPserv andEarlyWatch) and special maintenance items. The special maintenance items are importanttasks which would normally be performed infrequently, but that you may be called uponto perform them.

C H A P T E R

19

19SAP Service Marketplace


Overview

SAP Service Marketplace is the Internet access to SAP resources and SAPService Marketplace (formerly known as SAPNet–R/3 and OSS) functionssuch as:

� Registering developers and objects

� Searching for SAP Notes

� Downloading support packages

Most of the OSS functions have been migrated to the SAP ServiceMarketplace. However, not all OSS functions will be migrated. The openingand use of the SAP service connections for EarlyWatch and SAP hotline accessto customer systems are available from your SAP R/3 system’s Commandfield, with transaction OSS1. We will demonstrate how to open the serviceconnection in SAPNet-R/3 at the end of this chapter.

The prerequisites to use SAP Service Marketplace are:

� An internet connection

� A browser. SAP Service Marketplace works better with Microsoft InternetExplorer.

� A valid SAPNet/OSS user ID and password

Logging on to SAPNet

The following task outlines how to log on to SAPNet.

Task

Log on to SAPNet

1. In your web browser, in the Address field, enter service.sap.com.

Note

The SAP Service Marketplace has gone by different names in the past, such as SAPNet,www.sap.com, and service.sap.com. Be aware that the name may change in the future.

We recommend that youuse SAP ServiceMarketplace as your

primary SAPNet access method.For most companies with anexisting (flat fee) internet accessline, the cost of the internetaccess is already paid for. TheSAP service connection requiredfor the SAPNet-R/3 transaction(OSS1), if using ISDN, is anadditional per-minute cost.


2. Choose Enter Now.

3. In User Name, enter your OSS/SAPNet user ID.

4. In Password, enter your OSS/SAPNet password.

5. Choose Quick Links.

Note

If this is your first time using the SAPService Marketplace, you can choosewhether to see a standard page or apersonalized page. Choose your optionand choose the Access now! button.For our example, we are using thestandard page.


6. From here you can select the topic you are interested in and go directly there,without having to navigate a menu that would change.

Navigation

This task gives you a basic overview of navigation in SAPNet.

Task

Navigating SAPNet

1. On the main window of the market place page, choose Support.

2. The Support main screen appears.


3. Most of the SAPNet functions used by systems administrators are grouped inthis screen.

Solving a Problem with SAPNet

If you have a particular problem or question, you should search:

� The online documentation

� SAP Notes

This large database contains problem notes.

Note

SAP Notes were formerly known asOSS Notes.


Task

Search for SAP Notes

1. Scroll down the Quick Links window to choose NOTES.

2. The search can be done in one of many different ways:

� You can use a text search with the following options:

• AND – the note must contain all of the words in the search text field

• OR – the note must contain at least one of the words in the search textfield

• PHRASE – the note must contain the words in the exact orderspecified in the field.

� You can also specify the specific:

• Note Number

• R/3 Release

• Application Area

• Database

Note

You cannot simultaneously specify aNote Number and Search Text.


3. On the SAP Notes Search screen, in each of the following fields, enter thefollowing text:

a. In Search Text, enter the text to search for (for example spool system).

b. In Search Mode, select all given words (AND).

c. In Release, enter the relevant release number (for example 46C).

d. In Database, enter a database name.

e. Choose Submit.

4. The results from the criteria are displayed. Each page contains 20 hits.


5. Choose the first note.

6. Review the note.

7. Close this window and return to the SAP Notes list.


Customer Messages

If you have searched both the online documentation and SAP Notes and notfound the answer to your question or problem, then you should submit aSAPNet message for assistance.

Entering Customer Messages

Include as much information as possible in your message, so the SAPNetHotline consultants can help you. Indicate where in the online documentationyou have searched and which SAP Notes you have reviewed.

Priority table

Assign your message a priority from the following table below:

Note

The SAPNet customer message function is not meant to replace consulting. Messages enteredinto SAPNet are for reporting and getting resolution on SAP problems or bugs. If a message isinterpreted as a request for consulting information, it will be returned to you, and you will beadvised to seek consulting assistance.

Priority Situation

Very High � In your production system, only forsystem or application shutdown

� In your nonproductive system, during acritical project phase

An Online Service System/SAPNet consultantreviews these messages within 30 minutes ofarrival. If the problem does not fall within thedefined description for a “very high” priorityproblem, the priority is immediately reduced.

Do not assign a message this priority if youcannot be available to receive a call back fromSAP. If SAP attempts to call you and you cannotbe reached, your message may be downgraded.

High When important applications or subprogramsfail in function, or for a system shutdown in anonproductive system.

Medium For errors with less serious consequences thanthe above two cases, where the operation of theproductive system is not seriously affected.

Low For minor errors, such as documentation errors,typographical mistakes, and so on


The following list contains hints that can improve total problem resolutiontime:

Component

If you know the specific component, assign it.

If you do not know it, do not assign to a detailed component level (forexample, assign it to level 3, BC-CCM-PRN rather than a level 4, BC-CCM-PRN-DVM). The Online Service System Hotline consultant can assign aspecific component. If you assign the message to a wrong component, and itis forwarded to the incorrect person, time is lost. It will take that much moretime to resolve your problem.

Be aware that the cause of the problem may be in an area other than themodule you are working on.

Problem Description

Be clear and descriptive. The better the information you provide, the betterthe results. Information that is clear to you may not be clear to the hotlineconsultant.

Provide enough data so that SAPNet Hotline personnel will not have to askadditional questions before beginning work on your problem.

� Examples of complete data includes:

� If there is an error message, enter it exactly as it appears.

� Provide the transaction or menu path describing where the error orproblem occurred.

� Indicate if the problem can be duplicated on your test system.

� Describe the circumstances that created the problem.

� Describe anything unique about the data entered in the transaction wherethe problem occurred.

� List which problem-related SAP Notes that have been reviewed and whichnotes have been applied.

� List which actions and research you have already performed.

The following examples are messages in which the SAPNet hotline requiresmore information before beginning on the problem:

� “FB01 does not work.”

� “The system is slow.”

Use care when assigninga priority to yourmessage. If the problem

does not meet the Very Highcriteria, assigning the messagethis priority will not guarantee youa quicker response time.

Keep your systemtechnical information inSAPNet current and

correct. This information is usedby hotline personnel when theywork on your problem.


Task

Enter customer messages

1. Scroll down the Quick Links window to choose MESSAGE.

2. Choose Start Message Wizard.


3. On the next screen:

a. Under Reporter, check that the values in the fields are correct. If it is not,you must use SAPNet-R/3 to correct your user information.

b. In System type, select the type of your system:

� Development

� Production

� Test

c. In Installation, choose the installation that your message is for.

d. In Release, choose the SAP R/3 release of your system from displayoptions.

e. In Add-on, choose the add-on that you are running.

f. In Add-on release, choose the release of the add-on.

g. Choose continue.



a. In Per system (operating system), click the down arrow and choose youroperating system.

b. In Database, click the down arrow and choose your database.

c. In Frontend, click the down arrow and choose your frontend.

d. Choose continue.



a. Under Classification, in Priority click the down arrow and choose theappropriate priority for your message.

b. Use the table on page Entering Customer Messages to determine theproper priority level.

c. In Components, entering the fields in order (from 1 to 3), click the downarrow and choose the component for the message.

d. Choose continue.



a. In Language, click the down arrow and choose the language for themessage.

b. In Short text, enter a short (one line) problem description.

c. In Long text, enter a complete description of the problem. See “ProblemDescription” on page 548.

d. Choose Send to SAP.

7. The message on the top indicates the message is sent to SAP successfully

To control access to yoursystem and mange howlong the service

connection is open, request thatyou be contacted to:

� Get the password

� Open the SAP serviceconnection


Viewing Customer Messages

The response to your message is often in the form of an electronic message,rather than a telephone call. It is, therefore, important to monitor the status ofyour messages. Make sure your SAP user id has your correct email addressand phone number. You may get an email when SAP support response.

Task

View customer messages

1. On the SAP Service Marketplace screen, on the menu bar, choose Inbox.

2. Click on the message under Customer messages – customer action.

3. Here you can view the response from SAPNet consultant underCommunication. In this example, we must provide the password for theconsultant to access the system


4. Scroll down to the bottom and choose Access data.

5. Choose Create.

6. Enter system access data such as User-ID and Password in the field.


7. Choose Save changes.

8. In the Customer message wizard window, choose Info for SAP.


9. Scroll down to the bottom and type in any information in the Memo box.

10. Choose Send to SAP.

11. The message on the top indicates the message is sent to SAP successfully.


Task

Confirm customer messages

1. Under Customer message wizard window, scroll down to the bottom.

2. Choose Message is not relevant anymore.

3. Choose OK.


4. The Status of the message is changed to Confirmed.

Registering a Developer or Object

To modify an SAP object, both the developer and the object that will bemodified must be registered with SAP. A developer, once registered for theinstallation, does not have to register again. Similarly, an SAP object onceregistered for the installation, does not have to be registered again. It is forthis reason that on the registration screen either or both the developer orobject access key would be required.

� Only an SAP-registered developer can make changes to SAP objects.

� Restricting access to registered developers provides a record of who hasmade changes to the system.

� Registering an SAP object provides a record of which SAP objects havebeen modified by the customer.

� The assumption is that if you requested an object access key, you will bemodifying the object.

See the following sections for registering a developer and an SAP object.


Registering a Developer

To modify an SAP object, the developer needs to be registered with SAP.Once registered for the installation, the developer does not have to registeragain.

Only an SAP-registered developer can make changes to SAP objects.Restricting access to registered developers provides a record of who has madechanges to the system.

In the following procedure:

� The developer requests a developer key

� The system administrator obtains the key

� The developer enters the key

Task

Developer requests developer key

1. This screen is seen by the developer when a developer key is required.

a. If the Access key for developers is blank, you must obtain a developeraccess key.

b. Give the developer’s User name (2) to the system administrator to get adeveloper access key.


Task

System administrator gets the access key

1. Scroll down the Quick Links window to choose SSCR.

2. On the SSCR screen, you can register and get keys for:

� Developers

� SAP objects that will be changed

Note

From this window you can also find outwhat developers you have registered.


Task

Register a developer

1. Choose Registration.

2. Select Register Developer.

3. If your site has several SAP R/3 installations, select the one for which youwish to perform registrations.

4. In Developer, enter the developer’s user ID.


5. Choose Register.

6. The registration information for the developer is displayed.

If the registration date is not today’s date and the registration name is not thename of the user who just submitted the request to register a developer, thedeveloper has been previously registered.

7. Record the Registration key either on paper, or copy and paste into an email.

The generated key enables the user to create or change customer objects andchange SAP objects. The registration is done only once for each developer.

8. Send the registration key to the developer.


Enter the Developer Key

The following task must be done in the development system.

Task

Enter the developer key

1. In the first Access Key field, the developer enters the key received from thesystem administrator.

Task

Delete a developer

1. On the same screen that was used to register a developer:

a. In Developer, enter the user ID of the developer to delete.

b. Choose Delete.


2. A message appears on the screen showing the developer was deleted. Tocheck if the deletion is successful, choose Show, which displays a list ofdevelopers.

Registering an Object

Registering an SAP object provides a record of which SAP objects have beenmodified by the customer. The assumption is that if you requested an objectaccess key, you will be modifying the object. If the customer modifies anobject and problems arise, resolving the problem may be the customer’sresponsibility. If an object is not modified and problems arise, resolving theproblem is SAP’s responsibility.

In the following procedure:

� The developer requests a developer key

� The system administrator obtains the key

� The developer enters the key


Task

Developer requests object key

1. This screen is seen by the developer when an object key is required:

a. If the object Access key is blank, you must obtain an object access key.

b. Give the three object fields to the system administrator (for example,R3TR, PROG, RSPARAM).

All three fields are required to obtain the object key.

c. If you are in a mixed release environment, also give the systemadministrator the SAP Release for the system.


Task

System administrator gets the access key

1. Scroll down the Quick Links window to choose SSCR.

2. On the SSCR screen, you can register and get keys for:

� Developers

� SAP objects that will be changed

3. Choose Registration.

Note

From this screen, you can also see whatobjects you have registered.


Task

Register an object

1. Select Register Object.

2. If your site has several SAP R/3 installations, select the one for which youwish to perform registrations.

3. TADIR is the table that contains SAP R/3 repository objects. Informationmust be entered in the following fields:

� Program ID

� Object

� Object name

In this example, we wish to change a program (PROG) named RSPO0041. Theentry is R3TR / PROG / RSPO0041.

4. Select Advance correction to apply an SAP Note, and this note is an advancecorrection.


5. Choose Register.

6. Registration information for the object is displayed. If the registration date isnot today’s date and the registration name is not the name of the user whologged onto SAPNet, the object has been previously registered in thisinstallation.

7. Record the Registration key.

8. Return to the Online Services main screen.


Enter the Object Key

The following task must be done in the development system.

Task

Enter the object key

1. In the second Access key field, the developer enters the object key receivedfrom the system administrator.

Task

Delete an object

1. From the Register Object Screen:

a. In TADIR Object, enter the Program ID/Object/Object name for the object todelete.

b. Choose Delete.


2. Delete information for the object is displayed.

3. To check whether the deletion is successful, choose Show, which displays a listof developers.

SAP Software Center

The SAP Software Center is formerly known as Online Correction Support(OCS). It provides information and tools to retrieve support packages, legalchange packages, SPAM updates, and so on.


Task

Enter the SAP Software Center

1. Scroll down the Quick Links window to choose SWCENTER.

2. This screen shows the main page of the software center.


Getting the Latest SPAM version

Make sure that you have the latest version of the SAP Patch Manager orSPAM on your SAP R/3 system before you apply any support packages.

Task

Get the latest SPAM version

1. To get the latest SPAM version, in the right frame, expand Download SupportPackages → SPAM/SAINT Updates.


2. Choose SPAM Updates.

3. Choose the SPAM update for your release.

Use the version (for example, Version 46C/0028) to determine if the SPAMupdate is a newer version than what you have.

The transport number for an SAP R/3 release (example SAPKD00040) doesnot change.


4. Choose Download.

5. Select Save this file to disk.

6. Choose OK.

7. On the Save As dialog box:

a. Specify the directory where you want the update to be saved.

b. Choose Save. The downloading process begins.


8. Choose Close.

Task

Download support packages

1. On the download screen, from the right frame, expand R/3 Support Packages.


2. Select the appropriate release (for example, select R/3 4.6C on the right frame).

3. Under the Title column, choose the appropriate support package.

The file size column tells you how large the patch file is.

4. From this screen, you have the following options:

� Download the support package

� View the related SAP Notes that apply to the support package

Make sure that yoursystem has enough filespace to:

� Download the patch

� Upload the patch intousr/sap/trans/EPS/in

� Create the transport file inusr/sap/trans/da


� View the objects that are affected by the support package

Task

View notes related to the specific support package

1. On the Option screen, choose R/3 Note.


2. The listed notes appear. To display a note, choose the note.

3. You can print the note or save it, using the browser menus.


Task

Download the support package

1. On the Option screen, choose Download.

2. On the File Download dialog box:

a. Select Save this file to disk.

b. Choose OK.


3. On the Save As dialog box:

a. Specify the directory.

b. Choose Save.

4. The downloading process begins.

5. After the download has completed, choose Close.

After downloading the support packages (whether SPAM update or supportpackage), there are two ways to upload the support packages into the SAPsystem:

� Upload from frontend

� Upload from application server

1. Unpack the patch archive file (see Unpacking a CAR file in chapter 22).


2. Copy the resulting *.ATT and *.PAT files to the /usr/sap/trans/EPS/insubdirectory.

Connecting to SAPNet

Prerequisites

The SAP Service connection must be set up and working, the SAProuter mustbe installed and configured, and the OSS1 technical settings must beconfigured.

You must have a valid SAPNet/OSS user ID and password for your company

Task

Connect to SAPNet

1. In the Command field, enter transaction OSS1 and choose Enter.

Useful SAP Notes Description

83458 OCS Info: Downloading patches fromSAPNet

97621 OCS Info: Online Correction Support (OCS)

169142 Online Correction Support (OCS)

36579 Questions and answers on the topic: SSCR

152170 Migration of support functions to SAPNet-Web frontend

169329 New functions in the SAPNet as of 09/05-06/99

86161 Registering developers and objects

69224 Access to the SAPNet server via OSS UserID

173814 OCS: Known problems with SupportPackages Rel. 4.6

If you have an ISDNconnection, thetelephone bill can

become high. ISDN is normallybilled “by the minute” of connecttime. Manage the time that you areconnected to SAPNet-R/3, or youcould get a large phone bill for yourSAP service connection.

Check with your networkingperson or company about howyour SAP service connection isconfigured. Some will hold theISDN connection open even ifthere is no traffic, which couldresult in an even larger phone bill.


2. Choose Logon to SAPNet.

3. On the Select a Group dialog box:

a. Select 1_PUBLIC.

b. Choose Continue.

Once you pass thisscreen, the SAP serviceconnection is open, and

the ISDN “billing meter” is running.



a. In User, enter your OSS/SAPNet user ID.

b. In Password, enter your password.

c. In Language, enter your language preference (for example, EN for English).The default language is English.

d. Choose .

5. This screen shows System News. We recommend that you periodically reviewthese headlines to see if any apply to your system’s configuration. ChooseContinue.


6. The Inbox is the main SAPNet–R/3 screen.

Opening a Service Connection

A service connection allows SAPNet/OSS Hotline and EarlyWatch personnel toremotely access your system.

� SAPNet Hotline personnel use the connection to remotely examine anddiagnose your system while investigating your question or problem.

Note

For security reasons:

� The customer opens thisconnection.SAP cannot access thecustomer’s system until thecustomer opens the connection.

� The service connectionfunctionality is not available viaSAPNet-web.


� EarlyWatch consultants use the connection to remotely reviewperformance and system configuration.

Order of Access to Systems

Try to first duplicate the problem in your development or test server, andhave SAP access that server first. As a last resort, and only if the problemcannot be duplicated on the development or test server, grant access to theproduction server.

Problem solving may require making an entry into the system to observe theproblem. Testing is not an activity that should be done in the productionsystem. Entering test data, even if reversed, could affect operational statistics.If the problem is basis related, an accident could result in a disaster.

Review the following SAP Notes for further information:

Note

You can only specify the length of time for a connection to remain open, not the start time.

To schedule the time when a service connection will open, you must apply SAP Note 170102.This note is valid back to Release 3.1G.

To manage your telephone expense:

Request that SAPNet consultants call to request that the connection be opened at a specifictime for a specified duration.

Open the connection at the time they request.

Tips & Tricks

SAP Note Description

31515 Service connections

169296 Integrating service connections into maintainsystem data

169329 New functions in the SAPNet as of 09/05-06/99

170102 Automatic opening of a service connection

171569 Maintaining service connection in systemdata maintenance


Task

Open a service connection

1. On the main SAPNet–R/3 screen, choose Service.

2. Under Service, choose Service connection.

3. Under Service Connection, choose Service connection.


4. Scroll down to find your system. Depending on your installation, this screenwill be different.

5. Select the <SID> of the system to open the connection to(for example, SA1).

6. Choose .

7. Expand Service selection by clicking the + sign next to it.

8. Under Service selection, select R/3 Support.


9. Choose .

10. To select the user contact, choose .

11. Choose .

12. Choose .

13. The success message is shown in status bar.

14. Under Connections, select the appropriate type of connection. (It is usuallyR/3 Support).


15. Choose .

16. Enter the duration of the connection (in Days and Hours).

17. Choose .

To schedule the timewhen a serviceconnection will open, you

must apply SAP Note 170102.This note is valid back to Release3.1G.


18. The connection status is shown.Note

Note: To manually close the connection,select the open connection and choose

delete. Choose Yes whenprompted for confirm action.

C H A P T E R

20

20Remote Services


Overview

This chapter tells you about SAPSERV and EarlyWatch. The information inthis chapter should help the user understand how to:

� Retrieve files from SAP and SAPSERV

� Connect to SAPSERV

� Download files

� Arrange for an EarlyWatch session

Retrieving Files from SAP, SAPSERV

SAPSERV is a series of servers that contain patches and other downloadablefiles for customers (for example, the U.S. server is SAPSERV4). The differencebetween the various SAPSERV servers is the name, the IP address, and thelocation (see table below). Many of the functions previously available onlyon SAPSERV are now available on the SAP Service Marketplace.However there are still functions that are only available on SAPSERV.

The following types of files are retrieved from SAPSERV:

� Updates to the SAP R/3 system kernel.

� Various patches, such as:

• SAP R/3 system

• Database

• SAP GUI

� Miscellaneous downloadable files.

Location Host IP Address Long Hostname

Walldorf sapserv3 147.204.2.5 sapserv3.wdf.sap-ag.de

Foster City sapserv4 204.79.199.2 sapserv4.sfo.sap-ag.de

Tokyo sapserv5 194.39.138.2 sapserv5.tyo.sap-ag.de

Sydney sapserv6 194.39.139.16 sapserv6.syd.sap-ag.de

Singapore sapserv7 194.39.134.35 sapserv7.sin.sap-ag.de

If you cannot connect toSAPSERV, you maynot be on the

machine where SAProuter isinstalled.

The SAProuters at SAP areconfigured to only recognize theircounterpart SAProuter on thecustomer’s side. Therefore, youmust connect from the computerwhere the SAProuter is installedand running.


You can connect to, navigate within, and download files from SAPSERV4using:

� Command prompt

� Windows FTP GUI client

� Internet browser

NT

You must either be physically on the NT server where the SAProuter isinstalled, or use a remote control program to take over the server where theSAProuter is installed.

UNIX

You must either be physically on the UNIX server where the SAProuter isinstalled, or telnet to the server where the SAProuter is installed.

Connecting to SAPSERV Using a GUI (NT)

Using an GUI-based FTP client is much easier than using the commandprompt.

Before attempting a connection to SAPSERV using a GUI, make certain that:

� The SAP service connection to SAPSERV has been established, tested, andis functional

� An FTP client is installed on the computer where the SAProuter is located

� The FTP client has been configured with the following parameters:

• IP address of SAPSERV, 204.79.199.2

• Login user ID, FTP

• User password <your e-mail address>

• Directory to download files to on the client PC (optional)

An FTP Client Example

The following example of an FTP client is courtesy of Van Dyke Technologies.

Task

Connect to SAPSERV with an FTP client

1. Start the FTP client program.

For ease of use andnavigation, use an FTPGUI client to access

SAPSERV.

In this guidebook, we useonly one of the manyavailable FTP clients.

Other FTP clients are listed in theresources section of appendix A.SAP does not endorse anyparticular product.

Also, it is your responsibility toperform compatibility testing todetermine if the software youselect functions on your systemwithout conflict (for example,without crashing the system).


2. Connect to SAPSERV.

3. Navigate down the tree structure to the directory that contains the file(s) youneed.

4. In some directories, you may want to download and read informational files(.message and *.info).

5. Select the file(s) you want to download.

Note

The directory and file that you need willbe in the SAP Note or other documentthat instructs you to get it fromSAPSERV.


6. *.CAR (program) files must be downloaded in binary format.

Connecting to SAPSERV Using the Command Prompt

Navigating in SAPSERV

SAPSERV is a UNIX server. If you usually use Windows-based systems,UNIX has some important differences:

� UNIX is a case-sensitive operating system, whereas Windows NT is not.When navigating in SAPSERV or downloading a file, enter the directoryor filename exactly as it is displayed (for example, in UNIX, Rel40B is notthe same as rel40b).

� UNIX commands differ from NT commands. For example, in NT, you typedir to get a list of files in a directory. In UNIX, you type ls.


Important UNIX commands:

Connecting at the Command Prompt

Both UNIX and NT use a command prompt window, and the commandsentered are the same. The NT command prompt window is shown in thefollowing example.

Task

Connect to an FTP server from a command prompt

1. Open a Command Prompt window.

2. As an option, you can change to your download directory.

3. Enter ftp 204.79.199.2

4. Enter ftp at the User prompt.

5. Enter your e-mail address at the Password: prompt.

Command Definition

ls List (similar to dir in NT and DOS)

cd Change directory

get Get or download a file

bin Switch to binary mode to download programs

bye Log off

Note

In this example, the file(s) will downloadto the root directory of the C drive.

The directory you arecurrently in is thedirectory into which file

will be downloaded. To downloadthe file to a different directory,change to that directory after youopen the command promptwindow and before you enter theFTP command.

If your network personnelput sapserv4 into thehosts file or DNS, you

can enter ftp sapverv4after the prompt.


6. From this screen, use the cd command to navigate through the directorystructure.The navigation commands are cd and ls.

7. This is the directory for Release 4.0b HPUX Oracle

8. We recommend that you download and read informational files (.message and*.info).

9. Remember the name file you want to download, because you will enter thefilename later. The files indicated are only for example.

A portion of theSAPSERV directorystructure is provided at

the end of this chapter to help younavigate within SAPSERV.

In NT, to increase thescreen buffer size andprevent the text from

scrolling off the screen:

On the NT desktop, choose MyComputer → Control Panel →Console → Layout tab. (InWindows 2000, open thecommand prompt and place thecursor on the title bar. Right clickon the mouse and chooseProperties → Layout tab.)

Under screen buffer size,increase the height to 100.


Downloading Files

Make sure that you download patches, kernels, transports, and other files inbinary format. Also, many of the files are in *.CAR archives. To unpack thesefiles, use the CAR program (see Unpacking a CAR file on page Unpacking aCAR or SAR File).

Task

Download a file

1. If the file is a text file, go to step 2. If the file is a binary file (such as a patch,kernel, or a .CAR transport):

a. At the ftp prompt, enter bin.

b. Choose Enter.

2. To download the file, enter get <filename> (for example, getsapdba_123.CAR). Filenames are case sensitive.

3. Choose Enter.

4. Wait for the download to finish and the ftp prompt to appear.

5. This screen shows an example of an information file, in this case dw.info (atext file that contains the patch level of the kernel).


6. Scroll down to view a listing (by patch level) of what is fixed in the kernelpatch.


Partial Organization of SAPSERV

Not all directories on SAPSERV are listed or expanded. For those that aresimilar (release, database, operating system), only one is expanded in detail.Over time, the directory structure may change or be reorganized. See belowfor the SAPSERV structure.

general ----------------------------------------------------------for all corrections that generally apply to customers3rdparty --------------------------------------------database and hardware specific

adabascompaqdatageneraldb2informixmssqloraclesni (Seimens)

frontendpatches ----------------------------------patches to the SAPGUI

rel31Hrel31Irel40Arel40B

windowswin16win32

rel45Asapgui -----------------------------------released SAPGUI

applent

30f30f_r231G31H40Apre _release

os2win

saplpd (spool)barcode

NTWIN

LPRINTalphaosfhpNTrm600rs6000sunWIN

NTrel30Frel31Grel31Hrel40Arel40Brel45Arel45B

WINR3server

abapnote .*-------------------------corrections specific to a note number

binaries


Unpacking a CAR or SAR File

A CAR file is a packaged file similar to a ZIP file. Like a ZIP file, a CAR or filemay contain multiple files. SAP delivers transports, patches, and otherprograms and files in CAR files. To use the contents of these files, you mustunpack them using car.exe.

As of Release 4.6C, SAP offers a new archiving tool SAPCAR.exe. Accordingto the replacement of CAR, the extension of the archive files delivered by SAPchanges from ‘.CAR’ to ‘.SAR’. The command line interface of SAPCAR isdownward compatible with the command line interface of CAR. For moreinformation, see SAP Note 212876. Please note that ‘.SAR’ files can only beunpacked by the SAPCAR program.

To get car.exe or SAPCAR.exe:

1. Get car.exe or SAPCAR.exe from SAPSERV (for the latest version):

SAPSERV4/general/R3server/patches/COMMON/NT//<hardware>

SAPSERV4/general/R3server/patches/COMMON/<OS>/<hardware>

2. From the directory :

NT: \usr\sap\<sid>\sys\exe\run\

UNIX: /usr/sap/<sid>/SYS/exe/run

3. Create an installation directory where you unpack files (for example,d:\sap\unpack).

4. Copy the file car.exe or SAPCAR.exe into this directory.

NTsupport

i386UNIX

languagesNote .*-------------------------specific note numbers

patches -----------------------------------R/3 patches, where most of the downloads will beCOMMON ------------------Kernel, release-independent pr ograms

NTi386 ---this dir has car.exe, sappad.exe, tar.exe

OS400UNIX

NTALPHAI386 ---------------this dir has car.exe, sappad.exe, tar.exe

MSSQLrel31Hrel31Irel40Arel40B -----------------------Kernel release, OS, hardware, db specific programs

NTI386

MSS --------------MS SQLserverORA --------------Oracle

OS400UNIX

AIXDECHPUX

ORAHPUX_SHMRELIANTSOLARIS

rel45A

If your version of theSAPCAR program isolder than six months,

replace it with the latest version.Check the following directory:SAPSERV4/general/R3server/patches/<rel>/<OS>/<hardware>


Task

Unpacking a file

1. Copy the file to be unpacked into the unpacking directory (for example,sapdba_123.car).

2. Open a command prompt window.

3. Change to the unpacking directory.

4. Execute the unpack command,car –xvf <file-name>(for example,car –xvf sapdba_123.CAR).

5. The file will be unpacked into the unpacking directory.

6. Move the unpacked files to where you need them.

7. Clean the unpacking directory by deleting all files except the car.exe file.

Special SAPNet Notes

To reduce confusion:

Begin the “unpacking”session with only the

SAPCAR.exe program in theunpacking directory.

Handle only one CAR or SAR fileat a time.Complete everything for that filebefore proceeding to the next file.

Note # Function

29372 Unpacking CAR archives

63786 FAQ – Frequently Asked Questions: sapservX

63845 Corrections on SAPSERV4 – searching for files

96885 Downloading a front-end patch from SAPSERVx

212876 The new archiving tool SAPCAR


EarlyWatch Service

The underlying concept of EarlyWatch is to prevent problems before theyoccur or escalate. EarlyWatch diagnoses a system’s potential problems andresource bottlenecks so they can be resolved in advance.

During an EarlyWatch session, performance experts log on to your system(into client 066) to monitor its performance, review performance-relatedconfiguration settings, and recommend system changes.

Analysis is done in five areas:

� SAP R/3 configuration

� SAP R/3 application

� Server

� Workload

� Database

EarlyWatch applies only to the production system, not the developmentsystem. The goal is for satisfactory online performance, not backgroundperformance. A system, other than the production system, is difficult to tuneto a moderate degree and is almost impossible to tune optimally. Thisdifficulty is because the activity in a development or test environment is notregular or consistent; development activity can vary greatly from week toweek.

EarlyWatch’s primary function is to improve the online performance of theproduction system. EarlyWatch should be used:

� A couple of months after going live

� After implementing significant changes to your system, such as:

• New modules

• Expansion of existing modules

• Addition of significant numbers of users to the system

• Hardware upgrade

• SAP release upgrade

These and similar items change the workload to the system. This changecould render the existing EarlyWatch parameters inapplicable. As yoursystem or company conditions change, we recommend that you request anew EarlyWatch session.

� After experiencing significant degradation of online performance. Thiscondition should be a steady condition and not an intermittent spike.

To use EarlyWatch:

1. The customer contacts SAP to arrange for an EarlyWatch session at:

You do not have to do anEarlyWatch session ifyour system or company

conditions have remained thesame.

Note

The target response is “less than 1second,” which excludes the networkdelay from the user’s PC to the SAP R/3system. This delay is outside the scopeand control of SAP.


SAP America, Inc. EarlyWatch

600 East Las Colinas Blvd, Ste. 2000

Irving, TX 75039

Tel.: (800) 677-7271 or (972) 868-2094

FAX: (972) 868-2108

2. There are prerequisites to an EarlyWatch session and you will be advisedof them. These prerequisites may require technical assistance to apply.

3. The customer opens the SAP service connection to the production systemfor EarlyWatch.

4. EarlyWatch connects to client 066 on the production system via SAPservice connection to gather data and record configuration. Client 066 isreserved exclusively for EarlyWatch.

5. Once the customer’s system is analyzed, a report is generated and sent tothe customer. Recommendations may be at any of three levels:a. SAP R/3 systemb. Databasec. Operating system

6. The customer reviews the report and recommendations.

7. After the review, apply the recommendations to your system.

8. Monitor your system for signs of problems.

If you have any questionsabout the report, discussthem with the EarlyWatch

analyst. If a recommended changeseems drastic or does not makesense, discuss it with the analystbefore proceeding. Mistakes havebeen made.

Try to understand therecommendations made byEarlyWatch. As a systemadministrator, the SAP R/3 systemis your responsibility.

C H A P T E R

21

21Special Maintenance


Overview

In this chapter, the reader will learn about special maintenance. This topicincludes the following:

� Kernel upgrade

� Client copy

� Production refresh strategies

Changing System Profile Parameters (Transaction RZ10)

The system profile parameters are what SAP R/3 uses when it starts up.Parameters may define how many of each work process to create, theminimum length of the user password, and so on The parameters are alsostored in ASCII profiles on OS level.

The system uses the following three parameters:

� Start profile

This profile defines which SAP R/3 services are started.

� Default profile

This profile defines the setup, which must be the same for all instances inthe system.

� Instance profile

This profile defines the setup of the specific instance, which allowsindividual application servers to be configured differently for specifictasks and users.

Change a value only for a specific purpose and only with proper knowledgeof what is being changed and why it is being changed.

1. In the Command field, enter transaction RZ10, and choose Enter (or from theSAP standard menu, choose Tools → CCMS → Configuration → RZ10 - Profilemaintenance).

Before making changes to the system profiles, make certain that you have a recent, usable copyof the system profile files. This backup is your last line of defense if a profile change is madethat results in SAP R/3 not being able to start.

NT: \user\sap\<sid>\sys\profile

UNIX: /user/sap/<sid>/sys/profile

If a parameter isincorrectly changed, SAPR/3 may not start.

Changing system profileparameters should only be doneunder the instruction of the SAPHotline, SAP EarlyWatch, or anexperienced consultant.

Use RZ10 to maintain your profileparameters.

Do not modify the files at theoperating system level. Thisprocess could lead toinconsistency and confusion.

Tips & Tricks


2. In the Profile field, choose .

3. Select the instance or default profile as appropriate (for example, theinstance profile, SA1 – DVEBMGS00 – PA102058).

4. Choose .

The profiles used by thesystem work in thefollowing order:

� Start profile

� Default profile (for allinstances in the system)

� Instance profile (specific tothe instance you are on)

Use the instance profileto make the parametersof a specific application

server different than the otherservers for specific reasons (forexample, a batch applicationserver).

Note

Under Edit profiles, there are three selections:

� Administration dataThis selection is not a maintenance mode. It is used to change the name of the filewhere the profile should be activated.

� Basic maintenance (maintenance mode)This mode allows you to set the buffers, work processes, and directories in the systemprofiles. It also allows you to specify the SAP components to be started (for example,message server, application server, SNA gateway, and so on) in startup profiles. Thisform of maintenance protects most profile parameters from being changed bypotentially incorrect settings.

� Extended maintenance (maintenance mode)This mode allows you to access all system profile parameters or start up profileentries.


5. Note the Version number of the instance profile. A later step in this procedureshows the version number has changed.

6. Under Edit profile, select Extended maintenance.

7. Choose Change.

8. Select the line above which you want the entry to be inserted (for example,abap/buffersize).

9. Choose Parameter.


10. Choose the Parameter name and choose .

11. The list that appears is long. To find the profile parameter you want to add,scroll down.

12. Select the parameter. For example, login/min_password_lng.

13. Choose .

14. A default value appears in Unsubstituted standard value.

15. In Parameter val, enter the new value (for example, enter 5 to increase theminimum length to five).

The point where youinsert the new profileparameter has no effect

on the process. But, to make iteasier to read, you may want togroup or order the parameters (forexample, group the logonparameters together).

Once you enter the profileparameter, it cannot be easilymoved to another location.Therefore, be careful where youchoose to insert it.


16. In Comment, document your change by entering a description of why thechange was made. The system attaches your user ID and date to yourcomment.

17. Choose Copy.

18. This screen shows that the system inserted your user ID and the date and timeof the change into the Comment. You can determine who made a profilechange and when this change was made.


19. Choose .

20. This screen shows the new parameter login/min_password_lng with a value of5 inserted above abap/buffersize.

21. Choose Copy.


22. The message at the bottom of the screen indicates that the profile waschanged.

23. Choose .

24. In Version, note the profile’s version number. It will increment later.

25. Choose .


26. Choose Yes.

27. Choose .

28. Choose .

29. Double-click on Yes.

30. Review the check log.

Note

Note: If you have operation modesconfigured, this screen will appear. Ifthis screen does not appear, skip to step32.


31. Choose .

32. Note that the profile’s version number has changed.

Use transaction RZ11 toget the details of aspecific profile parameter.


Support Packages

A Support Package is a collection of corrections that address serious errors inthe ABAP repository. These corrections affect the Basis and functional areas.Defined rules exist for what kind of fixes should be (and are) included in aSupport Package. Some rules are technical while other rules are policy.

A Support Package is not a cumulative fix for application modules. You muststill get and apply the notes for the functional modules. However, becauseSupport Packages contain patches for the various functional areas, some notesmay be applied in the Support Package. The Support Package is not supposedto contain functional enhancements, but this is not always the case.

The purpose of a Support Package is to fix problems before they becomeproblems.

There is a conflict about when Support Packages should be (and are) applied:

� To prevent serious problems, SAP’s position is that customers shouldapply all Support Packages as they are released.

� The position of many customers is that all system changes must beregression tested.

• This stance, with the frequency of Support Package releases, results inthe Support Packages not being applied, because the amount oftesting required cannot be done continuously.

• This customer position is not unique to SAP and has been taken bymany customers since the early days of computing.

SAP development is working on ways to make Support Package applicationeasier.

Strategy

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, do not applyit.

� If there is something in the Support Package that applies to you:

Note

As of Release 4.5, Support Packages have been separated from the HR Support Packages.This separation allows HR Support Packages to be applied quickly for legal compliance.

Before Release 4.5, the HR Support Packages contained the Hot Packages. Applying an HRSupport Package also meant applying the Hot Package.

As of Release 4.6, Support Packages have also been separated into the Basis SupportPackages, ABAP (ABA) Support Packages, and SAP R/3 Support Packages.

Note

Hot Packages are now known asSupport Packages. HR Legal ChangePatches (LCP) are known as HRSupport Packages.


• Determine if the entire Support Package (or just the note) must beinstalled.

• If the Support Package is to be installed, treat the installation as amini-upgrade.

Applying Support Packages

1. Determine what Support Packages have been applied to your system.

2. Get and review the notes for the Support Packages.

3. Determine if the Support Package should be or needs to be applied. Steps4 through 9 assume that the Support Package must be applied and arerepeated for all Support Packages that are to be applied at the currenttime.

4. Obtaining the Support Package

Depending on the size of the Support Package, it can be obtained threeways:

• Download it from SAPNet–R/3 (formerly OSS). This option is size-limited, so large Support Packages cannot be downloaded usingSAPNet–R/3.

• Download it from the SAP Service Marketplace.

• Upload it from the Support Package collection on CD. The SupportPackage collection contains all Support Packages available at thatpoint in time.

5. Apply the Support Package (See table below) in the development system(DEV).

6. Execute the regression test.

7. When successful, confirm the Support Package.

The determination of whether the support packages must be applied requires the consultationof the application support team. It is not a Basis decision.

Caution

Download from SAPNet – R/3(OSS)

Download from SAPNet –Web Support Package collection onCD

Request the SupportPackage from SAPNet–R/3.

Download the SupportPackage.

Request the SupportPackage collection.

Download the SupportPackage.

N/A Upload the Support Package.

Do not download thesupport package for eachsystem. Use the same file

that was downloaded for allsystem.


After testing and determining that it is stable on the DEV, repeat steps 7 –9 ontest system (QA), then production system (PRD).

Determining What Support Packages Have Been Applied

Task

Method 1

1. From the menu bar, choose System → Status.

2. On the System Status dialog box, on the right side of this screen, under SAPSystem data, choose for additional component information.

package/task getpatch

unpack move file upload define queue import

support package,frontend upload

x.car n/a n/a upload fromfront-end

define packagequeue

importqueue

support package,app svr upload

x.car x.ptt,x.att

move toeps\indirectory

upload fromapp svr

define packagequeue

importqueue

SPAM/SAINTupgrade

spam.car x.pat,x.att

move toeps\indirectory

upload fromapp svr

n/a importSPAMupdate


3. Choose the SupPack tab.

4. In this example, the following patches have been applied:

� SPAM/SAINT Update version 28

� ABA Support Package for 4.6C

Not Shown on the screen:

� R/3 Support Package

� Basis Support Package

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 Packagename is interpreted asfollows:

SAPK<component><release><sequence_number>

SAPKA46C03, interpreted asSAPK/A / 46C / 03, is forRelease 4.6C and is the thirdABAP Support Package.


Task

Method 2

1. In the Command field, enter transaction SPAM and choose Enter (or from theSAP standard menu, choose Tools → ABAP Workbench → Utilities →Maintenance→ SPAM – Support Packages).

2. On the Support Package Manager: Version <XXXXX> screen:

a. Select Applied Support Packages.

b. Choose Display.

3. The Support Package Directory: Imported Packages screen appears.

a. Important information is shown under Imported Packages:

� SPAM/SAINT Update version level

� Hot Packages / Support Packages applied

b. In this example, the following patches have been applied:

� SPAM/SAINT update version 28

� ABA Support Package <n> for 4.6C

� Not shown on the screen:

� R/3 Support Package

� Basis Support Package


Task

Get information on the support package from SAPNet

1. Connect to SAPNet using transaction OSS1. For more information, seechapter 19, “SAP Service Marketplace” on page 540.

2. Choose Service.

3. Choose SAP Patch Service.

4. Choose R/3 support packages.

For ABAP and Basis Support packages, choose SAP component supportpackages.


5. On the List of R/3 support packages screen:

a. Search the extended list for your release.

b. Select the node (+) to the left of your release to select it.

c. Choose .

6. From the List of R/3 support packages screen, you can view the:

a. SPAM/SAINT UpdateThis is the SAP Support Package Manager (formerly Patch Manager).Download and apply the current version before applying any SupportPackage.

b. R/3 Support PackagesExtra Large indicates that the Support Package may not be downloadablefrom SAPNet-R/3. In this case you must use the SAP Service Marketplaceto download. See Ch.19 – Downloading Support Packages.


7. To display the notes for a specific Support Package:

a. Select the note.

b. Choose Notes for patch.

8. To view all notes, select the node (-) to the left of Components.

9. Choose Expand. From this screen, you may view one of the following:

� All notes

� A specific note


Task

View all notes

1. Right-click anywhere on the screen, and select Download list from the popupmenu.


2. On the Save list in file… dialog box:

a. Select unconverted.

b. Choose .

3. In the Transfer Lists to a Local File dialog box:

a. In File name, enter the <drive\path\filename> where you want to savethe notes.

b. Choose Transfer.

4. This screen shows the saved note list as read by a text editor or wordprocessor.

Note

At present you cannot get this listingfrom SAP Service Marketplace.


5. To create a file of all notes (in case there are too many notes to go throughindividually on the screen):

a. Choose Select all.

b. Choose List selection.

6. Choose Download to download the notes to a file.


7. Choose Do not copy.

8. Choose No. You only want to review the notes, not to register the object forchange. After reviewing the notes, you may decide not to install theSupport Package.

9. Enter the path to your local PC and create a name for the file.

10. Choose Transfer.

Task

View a specific note

1. Double-click the node (+) to expand an individual branch (for example, BC).

2. Double-click the node (+) for BC-CUS, BC-CUS-TOL and BC-CUS-TOL-ECP.

3. Under BC-CUS-TOL-ECP, select note 0408749.

Note

The duration of the download dependson the number of notes addressed bythe Support Package.


4. Choose .

5. This screen shows the SAP Note.


Requesting SPAM or a Support Package from SAPNet

The following task shows you to to request SAP or Support Packages fromSAPNet.

Task

Request SPAM/Support Packages from SAPNet

1. Choose Service.

2. Choose SAP Patch Service.

3. Choose R/3 support packages.


4. From the List of R/3 support Packages screen:

a. Select one of the following:SPAM updateR/3 Support Package

b. Choose Request patch.


5. On the Request Support Package dialog box:

a. Select the installation for the patch.

b. Enter the <SID> for the system (for example, SA1).

c. Choose Continue.

6. The message in the status bar indicates that the patch request has beengenerated.

7. The next step is to download the patch (see the next section, DownloadingSPAM or a Support Package).


Downloading a Support Package (Hot Package) — SAPNet

Always plan to first apply the Support Package on a test server to assure itwill not create a problem. Back up the test server before applying the SupportPackage. The Support Packages must have been requested for thesystem/<sid> to which you are downloading it.

Task

Download a support package

1. Log on to client 000, under any user that has the SAP* equivalentauthorizations.

2. In the Command field, enter transaction SPAM and choose Enter (or from theSAP standard menu, choose Tools → ABAP Workbench → Utilities →Maintenance → Support Packages).

3. Choose .

4. The Electronic Parcel Service Confirm Transmission dialog box allows you tospecify which Hot Packages to download. On this dialog box:

a. Select the Support Package (if not already selected).

b. Choose .


5. This screen shows the EPS Transmission monitor:

a. Progress bar with the Size [MB] of the Support Package.

b. Elapsed Transmission time for the download.

c. Remaining time to complete for the download.

6. A message Upload successfully indicates that the SPAM or Support Packagehas transferred to the SAP R/3 system.

7. Choose .

Uploading the Support Package from a CD or SAP Service Marketplace

Large Support Packages (those too large to download from SAPNet–R/3) areavailable through the following two methods:

� Support Package Collection CD

� SAP Service Marketplace

SAP periodically releases a Support Package Collection CD that contains all thereleased Support Packages up to a certain date.

Support Package Collection CD

Load the CD containing the patches.

Log on to the operating system as:

� NT: <SID>adm

Make sure that thedirectory/usr/sap/trans/EPS/in

has enough space to downloadthe Hot Package.


� UNIX: <sid>adm

Change to the transport directory.

� NT: <drive>:\usr\sap\trans

� UNIX: /usr/sap/trans

Unpack the patch archive.

� NT: SAPCAR –xvf <CD_drive>:\<PATH>\<ARCHIVE>.CAR

� UNIX: SAPCAR –xvf /<CD_DRIVE>/<PATH>/<ARCHIVE>.CAR

SAP Service Marketplace

Log on to the operating system as:

� NT: <SID>adm

� UNIX: <sid>adm

Copy the downloaded patch files (example kh46a02.car) into an “unpack”directory.

Unpack the patch file by entering:

� SAPCAR –xvf <patch-file>

Copy the unpacked files from the EPS\in directory to the directory to uploadpatches:

� NT: <drive>:\usr\sap\trans\eps\in

� UNIX: /usr/sap/trans/eps/in

The next step is to upload the patch from the operating system into SAP R/3.

Task

Upload the support package

1. Log on to client 000, under any user that has SAP*-equivalent authorizations.

2. In the Command field, enter transaction SPAM and choose Enter (or from theSAP standard menu, choose Tools → ABAP Workbench → Utilities →Maintenance → Support Packages).


3. From the menu bar, choose Support Package → Load packages → Fromapplication server.

4. Choose .

5. Check that the Support Packages have successfully uploaded.

6. Choose .

7. Select All Support Packages.


8. Choose Display.

9. The patch is under New Support Packages.


Task

Upload the support package from the front end (< 20 MB)

1. From the menu bar, choose Support Package→ Load packages→ From front end.

2. Select the file.

3. Choose Open. The status displays at the bottom of the screen.


4. In 4.6D, the Content of the compressed file <XXXXX> dialog box appears.Choose .

5. A message on the status bar shows the process is completed successfully.

6. Select New Support Packages.

7. Choose Display.

8. The patch is under New Packages.


9. Choose .

Updating SPAM

To prepare for updating SPAM, the SAP R/3 system should not be active,which means that no users are logged on and no jobs are running. Also, allapplication servers should be shut down. Make sure that the r3trans and tpprograms are updated to the latest version. For more information, see theKernel Upgrade section.

The current SPAM update should have been downloaded from eitherSAPNet-R/3 or from SAPNet–Web. When using SAPNet–Web, the unpackedSPAM update files (.ATT and .PAT) should have been moved to the/usr/sap/trans/EPS/in subdirectory.

Task

Update SPAM

1. Log on to client 000, under any user that has SAP*-equivalent authorizations(not SAP*).

2. In the Command field, enter transaction SPAM and choose Enter (or from theSAP standard menu, choose Tools → ABAP Workbench → Utilities →Maintenance→ Support Packages).

If a SPAM update isavailable, apply it beforeany Support Packages.

Some Support Package changesrequire the new SPAM program toproperly update the system.


3. To upload the SPAM update file, from the menu bar, choose SupportPackage → Import SPAM update.

4. Choose .

5. The status of importing is shown on the bottom of the screen.


6. After applying the SPAM update, SPAM must restart to use the latestversion.

7. Choose .

8. Restart the transaction. In the Command field, enter /nSPAM.

9. Note the version number change.

10. Select All Support Packages.

11. Choose Display.


12. You will see the SPAM update under Applied Support Packages.

Applying the Support Package

The SAP R/3 system should not be active, so make sure that no users arelogged on and no jobs are running. Also, all application servers should beshut down.

Make sure that the r3trans and tp programs are updated to the latest version.For more information, see the Kernel Upgrade section of this chapter.

The current SPAM update should have been downloaded from SAPNet andapplied. The Support Package should have been downloaded from SAPNet,uploaded from the CD or front end.

Task

Define the patch queue

1. Log on to client 000 under any user that has SAP*-equivalent authorizations(not SAP*).

2. In the Command field, enter transaction SPAM and choose Enter (or from theSAP standard menu, choose Tools → ABAP Workbench → Utilities →Maintenance→ Support Packages).

In a CRM system, entertransactionSP_MANAGER instead

of SPAM. If you enter SPAM, goto menu Environment →Support Package Manager forBBPCRM. A PerformanceAssistant window will pop up. Youcan either close or minimize itafter reading it. A wizard windowwill guide you through the processand call SPAM automatically.


3. Choose Display/define to define a patch queue.

4. On the Component Selection dialog box:

a. Select the component to import. In this case, the Support Package isunder SAP_ABA.

b. Choose .

5. Verify that the patch is selected.

6. Choose .


Task

Apply the support package

1. The name of the first support package appears in Patch queue.

2. Choose to apply the patch queue.

3. Choose .

You must read the note.Some patches must beinstalled together and

others separately.


4. The status is shown on the bottom of the screen.

5. Choose .

Task

Check the Queue Log

1. Choose .

Note

Depending on the size of the SupportPackage, the queue application processcould run for a long time.


2. Review the return codes.

a. Select the component to import. In this case, the Support Package isunder SAP_ABA. Values greater than 4 indicate a failure.

b. Choose .

3. At this point, regression testing should be performed on the Support Package.If several Support Packages are going in as a group, one option is to confirmthem after applying and then perform the regression testing.

Task

Confirm the queue

1. Choose . The next Support Package cannot be applied until the previousone is confirmed.


2. Check the status bar to see if the patch queue was confirmed.

Task

Verify the package application

1. On the Support Package Manager screen:

a. Select All Support Packages.

b. Choose Display.


2. The support packages are found in the Applied Support Packages section.

Object Conflicts

Object conflicts occur when SAP objects (such as programs, tables, and so on)that you modified are included in a Support Package.

If an object has been modified by you and is being changed in the SupportPackage, you could lose your modifications. This problem usually occurswith an advanced correction, where a fix is incorporated in a future release ofthe SAP R/3 system, and the advanced correction is available before thefuture release.

Determine if the change is (or is not) included in the Support Package by:

� Reviewing the code comparison (transaction SPAU)

� Checking if the advanced correction is from a future releaseIf so, it probably will not be included in the Support Package.

� Checking if the change is your own modification

If the change is included in the Support Package, return to the SAP standardto simplify future system maintenance. If the change is not included in theSupport Package:

� Check to see what needs to be done to reapply the modification.

� Apply the modification.

� Test the modification.

Example

If you are on Release 4.0B and experience a problem, your problem has already been fixed ina higher release (for example, Release 5.0). You do not have to wait for the upgrade. The fix isavailable now for you to make as an advanced correction to your system. Support Packagesmay not always include this correction. Thus, after applying the package, you may have toreapply the correction.


This process is the same as that performed during an upgrade.

Regression Testing

Regression testing is necessary because many objects in many functional areasmay be affected by changes from a Support Package. All functional areasmust perform regression tests to verify that a Support Package does not createnew problems as it fixes old ones. A Support Package is a mini-upgrade,especially if it is large (for example, Release 4.6C R/3 Support Package 10).

All existing processes should continue to function as they did before theSupport Package was applied. A review of the notes related to a SupportPackage indicates what specific tests must be performed by the technical andfunctional team. As during the implementation, the functional teams shouldhave a script of test procedures to test the system. This script could also beused in the regression test.

Useful SAP Notes

SAP Note # Description

19466 Downloading a patch from SAPSERVx

33525 Important information about SAP patches <3.1H

53902 Conflicts between Hot Packages/LCPs andAdd-ons

62119 Obtaining extra large patches

73510 Problems during upgrade of patched sourcereleases

82264 Important information about SAP patches >=3.1H

83458 OCS Info: Downloading patches fromSAPNet

84962 Info: SPAM update

85820 Patch is not displayed in patch queue

86241 HR Legal Change Patches for the HRcomponent

87432 Contents of and applying LCPs

89089 Configuration of SAP R/3 systems for LCPs

97620 OCS Info: Overview of Important OCS Notes

97621 OCS Info: Online Correction Support (OCS)

97623 Patch types


Kernel Upgrade

The kernel upgrade process is the replacing of operating system level files(the kernel files) with updated versions of these files.

Kernel upgrades are normally done to fix bugs or other problems in thekernel. Some kernel upgrades provide enhanced functionality.

To upgrade the kernel:

1. Review all applicable documentation:

� Kernel instructions

� SAP Notes

� Upgrade manual

2. Always first perform the upgrade on a test server.

97630 Known problems with patches >= 3.1H

104664 Applying patches from CD

115372 Patches forwarded by mistake to targetsystem

119738 Problems during upgrade with too new HotPackages

135041 Separation LCPs HR / Hot Packages as ofRel. 4.5B

173814 Known problems with patches Release 4.6

329242 Import prerequisites for Support Packages inBasis Rel. 4.6D

339927 Performance problems with SupportPackages


Note

Special notes on the kernel version:

� It is now independent of the SAP R/3 release.

� The kernel is backward compatible, which means that a user could be running aRelease 3.0F with a 3.1I kernel.

� If you are on a release before 3.1I, review documentation to determine which kernelversion is applicable to your release.

You must remember theSAP R/3 release andkernel version you are

running. After the kernel isupgraded, apply kernel patches forthe upgraded version of the kernel.Do not apply kernel patches for theold version of the kernel.

When getting patches, rememberthat your SAP R/3 release staysthe same, regardless of yourversion of the kernel. On rareoccasions, an SAP Note instructsyou to apply a fix based on theSAP R/3 release of the system, notthe kernel version.

All servers in a system (centralinstance and application servers)must be on the same version ofthe kernel.


3. Obtain the new kernel from:

� SAP Service Marketplace

� SAPSERV

This route is more current than getting the kernel via CD (see chapter 20,Retrieving files from SAP, SAPSERV).

� Distribution CD (if provided)

� The kernel files include:

• dw1_nnn.CAR

• dw2_nnn.CAR

• enq_nnn.CAR

• tp_nnn.CAR

• r3trans_nnn.CAR

In this filename, nnn is the patch level (for example, dw1_114.CAR.)

4. Unpack the kernel files (see chapter 20, Retrieving files from SAP,SAPSERV for the unpacking procedure).

5. Back up the system at the database and operating system levels.

6. Stop the SAP R/3 system.

7. Stop the SAP services that are using the kernel files (saposcol, saprouter,sap<sid>_<sysnum>).

8. Backup the kernel directory:

NT: <drive>:\usr\sap\<sid>\sys\exe\run

UNIX: /usr/sap/<sid>/sys/exe/run

Copy the current kernel files to a backup directory, to be prepared in theevent that you must restore back to the old version if a problem occurswith the new version.

9. Copy the new kernel files into the kernel directoryThis step replaces the old programs with the new programs.

10. Perform any special instructions contained in:

• Kernel instructions

• Online Service System notes

• Upgrade manual

11. Restart.

12. Run transaction SGEN.

13. Test the system.

14. Repeat steps 5 – 13 for each server in the landscape.


Restart Option 1

1. Restart the SAP services that are using the kernel files (saposcol,saprouter, sap<sid>_<sysnum>).

2. Start the SAP R/3 system.

3. Check the SAP R/3 logs.

4. Monitor the system and system logs for problems.

Restart Option 2

1. Restart the server.

2. Check all logs for:

• Operating system

• Database

3. Start the SAP R/3 system.

4. Check the SAP R/3 logs.

5. Monitor the system and system log for problems.

Client Copy

The client copy function copies client-dependent customizing and data. Clientcopy allows the copy or transport of the complete customizing environmentfrom a source client to a target client within the same system (instance) or toanother system.

Client copy is not meant to copy client-independent objects, such as ABAPprograms and table structures. If a table is changed to add an additional field,and the added field is then populated with data, the table change is notcopied to the target system. Thus, the data in the additional field is notcopied.

Special Notes

To access the online help documentation on client copy:

1. From the menu bar, choose SAP Library

2. In the left frame, click the node (+) next to SAP Library.

3. Click the node (+) next to Basis Components.

4. From the list that appears, choose Change and Transport System (BC-CTS)

5. Choose Client Copy and Transport.

6. In this screen, click the node (+) next to Client Copy and Transport.

Tables are selectedbased on their deliveryclass.

Read the current onlinedocumentation on clientcopy. The client copy

programs and functionalityimprove and change significantlywith each new release.


7. Click the node (+) next to Client Copy and you will see the followinglist of files:

• Technical Background

• Copy Profiles

• Authorizations

• Maintaining Clients

• Copying Clients Within the Same System

• Copying Clients Between Systems

• Transporting Clients Between Systems

• Copying Transport Requests Within the Same System

• Deleting Clients

• Displaying Copy Logs

• Restarting Client Copy

• Error Handling

Some Useful SAP Notes

Processing Notes

Because large volumes of data are involved, copying a client could takeseveral hours. If you are copying a large productive client, the copy timecould take upwards of a day. For client copy of a large client, see SAP Note67205. Due to the long run time, the probability of an abnormal terminationdue to external factors is high.

You cannot separatemaster data fromtransaction data.

The developer of clientcopy maintains severalinformational SAP Notes.

Do a SAP Note search oncomponent BC-CTS-CCO andsearch for notes beginning withCC*. As of this guidebook iswriting, there over 50 such notesavailable.


7312 Create client 066 for EarlyWatch

13391 Deleting/resetting a client (up to 3.0F)

24853 CC info: Client copy, functionality in 3.0, 4.0

47502 CC-TOPIC: Remote Client copy

67205 CC-INFO: Copying large and productiveclients

69556 CC-TOPIC: Missing tables and data

70643 CC-TOPIC: Delete client

84504 CC-TOPIC: SM29 transfers data in spite ofCancel

118823 CC-ADMIN: Size of a client

191207 CC-TOPIC: Client copy and central useradmin

During the copy process,do not work in the sourceclient or the target client.

The target client is locked for allusers except SAP* andDDIC.


Security

To perform a client copy, the user ID of the person doing the copy must havethe same authorizations in the source client and in the target client. A systemadministrator with the same authorizations as user SAP* will have all therequired authorizations.

Creating a Client

The following task shows you how to create a client.

Task

Create a client

1. In the Command field, enter transaction SCC4 and choose Enter (or from theSAP standard menu, choose Tools → Administration, then Administration →Client admin → Client maintenance).

At the OS level, log on as <sid>adm to lock the system so users cannot log on during the copy:

cd /usr/sap/trans/bin

tp locksys <sid>

After the client copy is finished:

tp unlocksys <sid>

A client copy produces a large amount of log activity. If this directory runs out of space, thedatabase will stop. Turn off logging (i.e., activate truncate on checkpoint in MS-SQL, turn offarchive mode in Oracle) or monitor the file space in the directory where the log file(s) islocated.

Tips & Tricks

Caution


2. Choose .

3. Choose .

4. Choose New entries.


5. On the New Entries: Details of Added Entries screen:

a. In Client, enter the client number (for example, 200) and name (forexample, test client for docu).

b. In City, enter the city name (for example, Palo Alto).

c. In Std. Currency, enter the standard currency for the client (for example,USD).

d. In Client role, choose to select the role for the client.

e. Under Changes and transports for client-dependent objects, select theappropriate option (for example, Automatic recording of changes).

f. Under Client-independent object changes, choose and select theappropriate option (for example, Changes to Repository and client-ind.Customizing allowed).

g. Under Protection: Client copier and comparison tool, choose and select theappropriate entry (for example, Protection level 0: No restriction).

h. Under Restrictions, if CATTs are allowed to be executed, select AllowsCATT processes to be started.

i. Choose .

6. A message shows on the bottom of the screen.

Do not use clients:000,001, or 066.These clients are

reserved for SAP.


7. Choose .

8. The new client is listed.

9. In later steps, this new client may be referred to as the target client.

10. To log on to the new client, enter SAP* for the user and PASS for thepassword.

Copying a Client

Copying on the Same System/SID

To copy a client on the same system/<sid>, do a local client copy.

To log on to the target client, enter sap* for the user ID and pass for thepassword.

SAP* with the defaultpassword PASS is aknown user ID password.

Do not leave the client in thiscondition for longer thanabsolutely needed. Once theclient copy is complete, verify thatthe passwords for all system userIDs in the new client are secure.

Be sure you are loggedon to the correct targetclient. If you are on the

wrong client, you will destroy thatclient.


Task

Copy a client on the same system

1. In the Command field, enter transaction SCCL and choose Enter (or from theSAP standard menu, choose Tools → Administration, then Administration →Client admin → Client copy → Local copy).

2. On the Client Copy – Copy a Client screen:

a. In Selected profile, choose to select a copy profile that matches yourrequirements.

b. In Source client, enter the source client number (for example, 100).

c. If your user masters will be copied from a specific client, in the Sourceclient user masters field, enter this client number (for example, 100).

d. Choose Schedule as background job.

3. On the Schedule Client Copy in Background screen:

a. If you have multiple application servers, in Background server, chooseto select the server on which to run the client copy.


b. Select the server to run the client copy on.

c. Choose .

4. Choose Schedule job.

5. Choose Continue. The scheduling proceeds as in scheduling any otherbackground job.

6. To begin the copy immediately, select Immediate.

7. Choose Check.


8. Choose .

9. In Output device, enter the printer name (for example, dcbd).

10. Choose .

11. Choose .

12. The displayed message indicates the job was successfully scheduled.


13. Choose .

Copying to a Different System/SID

To copy a client to a different system/<sid>, do a remote client copy. Beforeyou do this, in the target system, the source system needs to be set up intransaction SM59, and the client must have been created.

Task

Copy a client to a different system

1. Log in to the target system and client.

2. In the Command field, enter transaction SCC9 and choose Enter (or from theSAP standard menu, choose Tools → Administration → Administration →Client admin → Client copy → Remote copy).

3. On the Client Copy – Copy a Client screen:

a. In Selected profile, choose to select a profile that matches yourrequirements.

b. In Source destinat., use for a list of available RFC destinations, andchoose the source system.

c. Verify the source System name and Source client.

d. Choose Schedule as background job.

Copying from one systemto another using remoteclient copy uses the RFC

interface, therefore, there is nointermediate storage on disk.

Be sure you are logged into the correct target client.If you are on the wrong

client, you will destroy that client.


4. On the Schedule Client Copy in Background screen:

a. In Background server, choose to select a background server.

b. Choose Schedule job.

5. Choose Continue.


6. From this point, schedule the job as you would any other background job.

7. When you have finished scheduling the client copy, this message windowwill appear.

Post-Client Copy Tasks

Secure the passwords for SAP* and DDIC in the new client. If you copied theuser master, the user IDs and passwords for those users have been copiedfrom the source client. When you create a new client, immediately change thedefault passwords for user SAP*. The default password is well known andhas been posted on the Internet.

Always have at least two administrative user IDs for each client, so you donot lock yourself out of the client.

SAP* and DDIC should only be used for tasks that require those user IDs beused. A better solution is to create an administrative user ID, which is a copyof the user SAP*.


Deleting a Client

To delete a client, there are two options:

� The Delete Client transaction, SCC5 (recommended)

� The R3TRANS program (see SAP Note 13391).

Task

Delete client transaction

1. Log on to the client that will be deleted.

2. In the Command field, enter transaction SCC5 and choose Enter (or from theSAP standard menu, choose Tools → Administration→ Administration →Client admin → Special functions → Delete client).

3. On the Delete Client screen:

a. Verify the Client to be deleted (for example, 200). The Client to be deletedfield is an unchangeable field and is the client that you log onto. If theclient number is incorrect, you are logged onto the wrong client.

b. Select Delete entry from T000.

c. Choose Background.

4. Choose Schedule job.

Before deleting a client,in the event of a majorproblem (for example,

deleting the wrong client), makecertain you have a usable backupof the system.

Be sure you are logged into the client you want todelete. If you are on the

wrong client, you will destroy thatclient.

Optionally, inBackground server,choose to select

the server to run the delete job.


5. Select Continue. From this point, the process is the same as scheduling abackground job.

Task

Review the client copy log

1. Log on to another client.

2. In the Command field, enter transaction SM37 and choose Enter.


a. In User name, enter the user ID that the client copy job was run under(for example, SAP*).

b. Choose Execute.

You can monitor theclient copy usingtransaction SCC3.

Status text will be “processing …”Choose the Refresh button untilclient copy is completed.


4. On the Job Overview screen:

a. Select the client copy entry.

b. Choose Job log.

5. Review the log.

6. At the bottom of the log is the message that the job has successfully finished.


Production Refresh Strategies

Production refresh is where the other systems are refreshed with data fromthe production system.

Refreshing a system from the production system helps:

� Get production data into the test environment.

� Sync the configuration in the test and development systems with theproduction system.Over time, the configuration of the various systems could drift apart andnot match the production system.

� Prepare for an upgradeYou want the test system to mirror the production system, so that theupgrade in the test system mirrors everything you will encounter into inthe production system.

In the recent past, the standard procedure was to create your own test data.One major reason was that disk storage space was expensive. Reasons not torefresh the system include:

� Version management history is only stored in the development system(DEV). A refresh will destroy this versioning history.

� Data storage is expensive

• Even with cheaper disks, the volume of data more than makes up anysavings.With several copies of the entire production database, the total of allthe databases could approach 100 gigabytes for a small company to aterabyte or more for a large company.

� Data security

• Data from the production system is actual data.Even if it is old, it could be confidential and sensitive. Thedevelopment and test systems are, then, subject to the same high levelof security as the production system.

• Created test data is fake and everyone knows that.There is much less issue with data confidentiality or sensitivity.

There are two ways to refresh a system:

� Database copy of the production system

� Client copy of the production client

Database Copy of Production System

Copying the entire production database does a database copy.

Because data in thetarget system is beingreplaced, refreshing a

system is an inherentlydangerous.

After the copy, actualproduction data exists inthe test system. This data

poses data security issues thatmust be addressed by the variousdata owners. It is more critical ifthe HR system is installed,because personnel records aresensitive. Financial, sales, andother data may also be companysensitive.


Benefits

� The refreshed system will be a duplicate of the production system.Client-independent changes will also be captured and copied to the targetsystem.

� The copy can be made using standard backup tapes, so there is no impacton the production system. Making a copy also tests your backup andrestore process.

Disadvantages

� All revision history of the refreshed system is lost, which is usually:

• Acceptable for the test/QA system

• Not acceptable for the DEV system because version history is lost.

� The target database needs to be as large as the PRD database.

� After the copy, the target system must be reconfigured.

� The target system loses its client structure and become a duplicate of theclient structure of the PRD system. If the PRD system has one client and theQAS system has three clients, after the database copy, the QAS system willhave one client. The other two clients are lost.

Client Copy of the Production System with Data

A client copy is done by performing a client copy of the active client from thePRD system (instead of copying the entire database, like a database copy).

Advantages

� Unlike a database copy, the target system does not have to bereconfigured.

Example

Before the database copy:

� PRD – 000, 001, 066, 400

� QAS – 000, 001, 100, 200, 300, 400, 500After the database copy:

� QAS – 000, 001, 066, 400

QAS has lost 100, 200, 300, 400


� The target system does not lose its client structure.

Disadvantages

� A client copy requires that the source and target systems are not usedduring the copy. Having both systems out of use may not be practical formany companies because the amount of time required to do the copy couldbe significantly greater than the amount of time (days, perhaps weeks) thatthe production system can be down.

� Client-independent objects (programs, table structures, and so on) thathave been changed and are not the same in the two systems will not becopied (refer to the sections on Client Copy below).

Client Copy of the Production System — Without Data

In this option, only a basic client copy is performed (including customizing),but no master or transactional data, and possibly no user data.

All test data is loaded into the new client using the following tools:

� Computer Assisted Test Tools (CATT)

� Data Transfer Workbench

� Application Link Enabling (ALE)

Advantages

In addition to the benefits of the client copy above:

� You can control the data being loaded into the new client.

• Data can be created to test specific items.

• You are not subject to the randomness of real data to test specificitems.

• Real data may have the appropriate data to test specific test items. Inthis case, test data has to be created anyway.

Disadvantages

These are the same as for a client copy with data above.

EXAMPLE: Before the client copy –

PRD – 000, 001, 066, 400

QAS – 000, 001, 100, 200, 300, 400, 500

After the client copy –

QAS – 000, 001, 100, 200, 300, 400, 500

P A R T N I N E

HAppendixes

A P P E N D I X

A

IUseful Transactions

System administrators may find the following transactions useful. Althoughmany of the transactions are not discussed in this guidebook, we list themhere for your convenience. Many of these transactions are for more advancedfunctions than targeted in the scope of this guidebook.

Transaction Code Switches

Transaction Code Switch Transaction Code Description

/n<trans code> /nspad Exit the current transaction and startthe new transaction

/o<trans code> /ospad Open a new session and start thenew transaction


Transaction Code Table

The following table contains two columns that require further explanation.

Dangerous

Dangerous transactions are potentially damaging or fatal to the system ifexecuted incorrectly.

Performance Impact

These transactions could have a potentially adverse impact to systemperformance if executed. Traces and table display are the transactions ofconcern here.

As a general rule, most Basis transactions are potentially damaging. Access to thesetransactions should be restricted in all systems. Access to some of these transactions shouldbe even further restricted in the production system.Caution

A table display problemoccurs when the querydoes a full table scan for

data. When done on a large table,this query has a serious systemperformance impact because thesystem searches every record inthe table to find those that meetthe search criteria.

Transaction Description Dangerous Performance impact

AL02 Database Alert Monitor(not supported for MS SQLSvr 7.0)

AL03 Operating System AlertMonitor

AL05 Workload Alert Monitor

AL08 Current active users (insystem)

AL11 Display operating system filefrom CCMS

AL12 Display table buffer (buffersynchronization)

BALE ALE administration andmonitoring

DB01 Exclusive waits in Oracledatabase

DB02 Database performance;tables and index

DB03 Parameter changes indatabase

DB05 Analysis of table with respectto indexed fields

DB12 Backup logs


DB13 DBA planning calendar

DB14 DBA logs

DB20 Generate table statistics

OSS1 Online Service System logon

RZ01 Graphical background jobscheduling monitor

RZ02 Network graphical display ofinstance

RZ03 Server status, alerts,maintain operations mode

RZ04 Maintain operations modeand instance

RZ06 Maintain alert threshold

RZ08 CCMS Alert Monitor

RZ10 Maintain system profiles X

RZ11 Display profile parameterattributes

RZ20 Alert Monitor 4.0

RZ21 Maintain settings for AlertMonitor 4.0

SA38 ABAP reporting

SCAM CATT management

SCAT Computer Aided Test Tool

SCC1 Client copy transport X

SCC3 Client copy log

SCC4 Client copy administration X

SCC5 Delete clients X

SCC6 Client import X

SCC7 Client import – postprocessing

SCC8 Client export

SCC9 Remote client copy X

SCCL Local client copy X

SCMP Table comparison

SCU3 Table history



SE01 Transport organizer

SE03 Workbench organizer: tools

SE06 Set up workbench organizer

SE09 Workbench organizer

SE10 Customizing organizer

SE11 Data Dictionary maintenance X

SE12 Data Dictionary display

SE14 Utilities for ABAP Dictionarytables

X

SE15 Repository Info System

SE16 Display table content X X

SE17 General table display X

SE38 ABAP editor X

SECR Audit Information System

SEU R/3 Repository Browser

SFT2 Maintain public holidaycalendar

SFT3 Maintain factory calendar

SICK Installation check

SM01 Lock transactions X

SM02 System messages

SM04 Overview of users

SM12 Database locks X

SM13 Update terminates X

SM18 Security Audit: Delete OldAudit Logs

SM19 Security Audit: AdministerAudit Profile (for SM20)

SM20 System (Security) Audit Log

SM21 System log

SM30 Maintain tables (not alltables can use SM30)

X

SM31 Maintain tables X

SM35 Batch input monitoring



SM36 Schedule background jobs

SM37 Overview of backgroundjobs

SM39 Job analysis

SM49 External operating systemcommands, execute (seerelated SM69)

SM50 Work process overview

SM51 Instance overview

SM56 Reset or check numberrange buffer

X

SM58 Error log for asynchronousRFC

SM59 RFC connection, maintain

SM63 Operations mode, maintain

SM64 Event trigger

SM65 Background processinganalysis tool

SM66 Global work processoverview

SM69 External operating systemcommands, maintain (seerelated SM49)

SMLG Maintain logon groups

SMX Display own jobs

SNRO Maintain number rangeobjects

X

SP00 Spool

SP01 Spool control

SP02 Display output requests

SP11 TemSe (temporarysequential objects) contents

SP12 TemSe administration

SPAD Spool administration (printersetup)

SPAM SAP Patch Manager



SPAU Intersection SAPtransport/customermodifications

SPCC Spool; consistency check

SPDD Intersection SAPtransport/customermodifications, DDIC

SPIC Spool; installation check

ST01 SAP system trace X

ST02 Buffer statistics

ST03 Workload analysis

ST04 Database performanceanalysis

ST05 SQL trace X

ST06 Operating system monitor

ST07 Application monitor

ST08 Network monitor

ST09 Network Alert monitor

ST10 Table call statistics –statistics on table accesses

ST11 Display developer trace X

ST12 Application monitor

ST14 Application analysis –statistics related to businessdocument volume

ST22 ABAP dump analysis

ST4A Oracle: analyze the sharedcursor cache

STAT Local transaction statistics

STMS Transport ManagementSystem

X

STUN Performance monitoringmenu

STZAC Customizing Time Zones

SU01 User maintenance X

SU01D Display users



SU02 Maintain authorizationprofiles

X

SU03 Maintain authorizations X

SU10 Mass change to user records X

SU12 Delete ALL Users X

SU2 Maintain user parameters

SU22 Authorization object check intransactions

SU3 Maintain own userparameters

SU53 Display authorizationchecked values

TU02 Parameter changes –display active parametersand history of changes


A P P E N D I X

B

JUseful Resources and Products

Other System Administration Resources

The cited references do not represent an all-inclusive listing of resources. SAPtraining classes, guidebooks, white papers, and web sites are constantly beingcreated and updated.

SAP Resources

SAP books and CDs can be ordered from the SAP online store(www.mysap.com/company/shop) or, for items with an SAP part number, fromyour SAP account executive. Books with ISBN numbers can be ordered fromthe SAP online store (www.mysap.com/company/shop) or Amazon(www.amazon.com).


Books

Title SAP Part Number ISBN Number

Complementary Software ProgramDirectory

50-018-672

R/3 System Getting Started 50-018-896 1-400524-02-4

SAP Dictionary R/2 SystemRelease 5.0: English–German

5000-5296

SAP Wörterbuch System R/2Release 5.0: Deutsch–English(SAP Dictionary R/2 SystemRelease 5.0: German–English)

5000-5295

Authorizations Made Easy 1-893570-21-5 (3.1G/H)

1-893570-22-3 (4.0B)

1-893570-23-1 (4.5A/B)

1-893570-24-X (4.6A/B)

Data Transfer Made Easy (English) 1-893570-04-5 (4.0B/4.5x)

Data Transfer Made Easy(German)

1-893570-05-3 (4.0B/4.5x)

Printout Design Made Easy (3.x) 1-893570-12-6 (3.1H)

SAPscript Made Easy (4.x) 1-893570-13-4 (4.0B)

1-893570-14-2 (4.6B)

Reporting Made Easy (4.0B) (3-volset)

1-893570-65-7 (4.0B)

Fundamentals of Reporting 1-893570-60-6

Report Development Tools 1-893570-61-4

Commonly Used Reports 1-893570-62-2

System Administration Made Easy 1-893570-41-X (3.1H)

1-893570-42-8 (4.0B)

1-893570-43-6 (4.6A/B)

BW Reporting Made Easy2.0B/2.1C

1-893570-66-5

mySAP Workplace –Administration and Tools

3-980773-20-5

Online Store Made Easy Guide 1-893570-88-6


CDs

Accelerated SAP (ASAP). Because ASAP is an implementation projectmanagement methodology, production system administration information isavailable on this CD.

Knowledge Products. Knowledge products must be registered and alicense installed (similar to saplicense), before they can be used.

Computer Based Training (CBT). Archiving has CBT available, under SAPOrder Number 500-20297.

SAP R/3 Online Documentation . The SAP R/3 online documentationcontains useful information.

Report Navigator (pre-Release 4.0). See the SAP Simplification Group’sweb site, www.saplabs.com/simple for more information.

Title SAP Order Number

Technical Implementation and Operation Mgt 500-27903

SAP System Management 500-27391

SAP System Monitoring 500-25694

SAP Software Logistics 500-27393

SAP Database Administration – MS SQLserver

500-25696

SAP Database Administration – Oracle 500-27392

SAP Database Administration – Informix 500-25695

SAP Database Administration – DB2-400 500-25697

SAP Database Administration – Adabas 500-29389

SAP Integration Technologies 500-25698

R/3 Interface Advisor 500-21636

SAP Terminology Database 500-30826

SAP Business Information Warehouse 500-29281

SAP Interface Advisor, Rel 4.5 500-26902


Training Classes

In the U.S., call central registration at (888)-777-1SAP(1727) or visit SAPAmerica’s training web site, www.sap.com/usa/trainsupp for the most currentclass list.

Other

SAP R/3 Security Guide; see SAP Note 39267service.sap.com/securityguide

Level 1

SAP50 SAP R/3 Basis Technology

Level 3 - Technical Core Competence

BC310 Windows NT/Oracle

BC314 Windows NT/MS SQL Server

BC317 Windows NT/DB2

BC360 UNIX/Oracle

BC361 UNIX/Informix

BC370 AS/400-DB2/400

Level 3

BC340 Going Live

Level 3 - Advanced

BC325 Software Logistics

BC315 SAP R/3 Workload Analysis

BC505 Database Administration - Oracle

BC511 Database Administration - Informix

BC520 Database Administration - MS SQL Server

BC525 Database Administration - DB2/400

Level 3 - Cross-Application

BC601 Build and Use SAP Business Workflow

BC615 Archiving Technology

BC630 SAP Business Communication

CA940 SAP R/3 Security Concepts


White papers

System Landscape

The SAP R/3 System Landscape, System and Client Deployment Strategy whitepaper can be downloaded from www.saplabs.com/simple.

SAPNet, Selected Items of Interest

Explore SAPNet at service.sap.com to see what is available. The amount ofavailable information is extensive and growing. We selected a few items thatwe think would be of particular interest to you. Please be aware that SAPNetwill change over time.

� Media Center

• SAP R/3 Documentation Info Center for C & P

• SAP Knowledge Shop

• Media by Type

• Installation/Upgrade Guides

• SAP Online Documentation

� Service Catalog

Remote Services, such as solution optimization, upgrade, euro, archiving,OS/DB migration, and conversion

� Education Services

• SAP Standard Training

• SAP Industry Solutions Training

• mySAP.com Components Training

� Release Information

• Release strategy

• Release notes

� Customer data

• Customer Master

• Customer Installations

• Customer Project Information

• Live Dates

• License Auditing Services

� SAP Software Change Registration (SSCR)

• Registration

• Objects registration


• Developer registration

• Registrations overview by installation

� SAP Software Center

• SAP maintenance

• SAP Installations

• Note Assistant

• Customer Information

• Download Support Packages

• Download mySAP.com Workplace Packages

• Download Kernel/Frontend Patches

• Download Service Procedures

Third-Party Resources

The following list of books is not all-inclusive. Also, no single book canprovide you with all the information you need. You will typically needseveral books in each category in your library.

This listing of books does not constitute an endorsement by SAP. This listingis provided as a starting point for your convenience. We recommend youcheck with your vendors (hardware, operating system, database, and so on)and the various book sources (both online and in stores) and for additionaltitles.

SAP R/3 Books Written by SAP Employees

Brand, Hartwig. 1999. SAP R/3 Implementation with ASAP, The Official SAPGuide. Sybex. (Release 4.0) (ISBN: 0-7821-2427-5)*This book is about technical/Basis implementation.*

Buck-Emden, Rüdiger; and Jürgen Galimow. 1996. SAP R/3 System, AClient/Server Technology. Addison-Wesley. (ISBN: 0-201-40350-1)

McFarland, Sue and Susanne Roehrs. 1999. SAP R/3 Software Logistics, TheOfficial SAP Guide. Sybex. (Release 4.0/4.5) (ISBN: 0-7821-2564-6)

Schneider, Thomas. 1999. SAP R/3 Performance Optimization: The Official SAPGuide. Sybex. (Release 4.x) (ISBN: 0-7821-2563-8)

Will, Liane. 1998. SAP R/3 System Administration: The Official SAP Guide.Sybex. (Release 4.0) (ISBN: 0-7821-2426-7)


SAP R/3 Books Written by Third-Party Authors

Hernandez, Jose. 1999. SAP R/3 Administrator’s Handbook, Second Edition.Osborne. (Release 4.x) (ISBN: 0-07-135413-1)

––– 1997. The SAP R/3 Handbook. McGraw-Hill. (Release 3.x, Oracle, andUNIX)(ISBN: 0-07-033121-9)

Hirao, Joey; and Jim Meade. 1999. SAP R/3 Administration for Dummies. IDG.(Release 3.x) (ISBN: 0-7645-0375-8)

Parkinson, Robert; Johan Marneweek. 1999. Basis Administration for SAP.Prima.(Oracle, and UNIX) (ISBN: 0-7615-1887-8)

Prince, Dennis. 1998. Supporting SAP R/3. Prima. (ISBN: 0-7615-1750-2)

Will, Liane; Christiane Hienger, Frank Strassenburg, and Rocco Himmer.1998. SAP R/3 Administration Addison-Wesley. (Release 3.x) (ISBN: 0-201-92469-2)

UNIX Books

Arick, Martin. 1995. Unix for DOS Users. John Wiley & Sons. (ISBN:0471049883)

Frisch, Æleen. 1998. Essential Systems Administration: Help for Unix SystemAdministrators. O’Reilly. (ISBN: 1-56592-127-5)

Nemeth, Evi., [et al.]. 1995. Unix System Administration Handbook. PrenticeHall. (ISBN: 0-13-151051-7)

Pugh, Kenneth. 1994. Unix for the MS-DOS User. Prentice Hall. (ISBN: 0-13-146077-3)

Siegert, Andreas. 1996. The AIX Survival Guide. Addison-Wesley. (ISBN: 0-201-59388-2)

Microsoft Windows NT Books

Microsoft Corporation. 2001. Microsoft Windows 2000 Server Resource Kit.Microsoft Press. (ISBN: 1-57231-805-8)

Minasi, Mark. 2000. Mastering Windows 2000 Server. Sybex. (ISBN 0-78212-774-6)

Microsoft Corporation. 2001. MCSE Migrating from Microsoft Windows NT 4.0to Microsoft 2000 with CD-ROM. Microsoft Press. (ISBN 0-73561-239-0)

Cox, Philip; Sheldon Thomas. 2000. Windows 2000 Security Handbook.McGraw-Hill. (ISBN 0-07212-433-4)


Enck, John (Editor). 1998. Windows NT Magazine, Administrator’s SurvivalGuide, Volume 1. Duke Communications. (ISBN: 188241988X)

Frisch, Æleen. 1998. Essential Windows NT System Administration. O’Reilly.(ISBN: 1-56592-274-3)

––– 1998. Windows NT Desktop Reference. O’Reilly. (ISBN: 1-56592-437-1)

Ivens, Kathy. 1998. Windows NT Troubleshooting. Osborne. (ISBN: 1-07882471-0)

Jumes, James; Neil Cooper, [et. al.] (PW Coopers). 1999. Microsoft WindowsNT4.0 Security, Audit, and Control. Microsoft Press. (ISBN: 1-57231-818-X)

Lambert, Nevin; Manish Patel. 1999. Microsoft Windows NT Security. ZD Press.(ISBN: 1-56276-457-8)

Leber, Jody; Jody Schivley, and Robert Denn (Editor). 1998. Windows NTBackup & Restore. O’Reilly. (ISBN: 1-56592-272-7)

McMains, John; and Bob Chronister. 1998. Windows NT Backup & Recovery.Osborne McGraw-Hill. (ISBN: 0-07-882363-3)

Jumes, James (Editor); Neil F. Cooper, and Todd M. Feinman. 1998. MicrosoftWindows NT 4.0 Security, Audit, and Control (Microsoft Technical Reference).Microsoft Press.(ISBN: 1-57231-818X)

Microsoft Corporation. 1996. Microsoft Windows NT Server Resource Kit: forWindows NT Server Version 4.0. Microsoft Press. (ISBN: 1-57231-3447)

––– 1997. Microsoft Windows NT Server Resource Kit Version 4.0, SupplementTwo. Microsoft Press. (ISBN: 1-57231-6268)

Minasi, Mark. 1997. Mastering Windows NT Server 4, 5th Edition. Sybex. (ISBN0-7821-2163-2)

Pearce, Eric; Robert Denn (Editor), and Beverly Scherf. 1997. Windows NT in aNutshell: A Desktop Quick Reference for Systems Administrators. O’Reilly. (ISBN:1-56592-251-4)

Rutstein, Charles. 1997. Windows NT security: A Practical Guide to SecuringWindows NT Servers and Workstations, McGraw-Hill (ISBN: 0-07-057833-8)

Siyan, Karanjit. 1997. Windows NT Server 4: Professional Reference. New RidersPublishing.(ISBN: 1-56205-805-3)

Sutton, Stephen. 1997. Windows NT Security Guide. Addison-Wesley. (ISBN: 0-201-41969-6)

OS/400 Books

IBM. 1994. An Implementation Guide for AS/400 Security and Auditing. IBM.(ISBN: 0-73840-573-6) (part# : GG24-4200-00)


IBM. 1998. The System Administrator’s Companion to AS/400 Availability andRecovery. IBM. (ISBN: 0-73840-038-6) (part# : SG24-2161-00)

Microsoft SQL Server Books

Microsoft Corporation. 2001. Microsoft SQL Server 2000 Resource Kit with CD-ROM. Microsoft Press. (ISBN 0-73561-266-8)

Deluca, S. Adrien. 2001. Microsoft SQL Server 2000 Performance TuningTechnical Reference. Microsoft Press (ISBN 0-73561-270-6)

Baird, Sean; Chris Miller, and Michael Hotek. 1998. SQL Server SystemAdministration. Macmillan. (ISBN: 1-562059556)

Microsoft Corporation. 1998. Microsoft SQL Server 7.0 System AdministrationTraining Kit. Microsoft Press. (ISBN: 1572318279)

Prathak, Paritosh. 1998. Administering SQL Server 7. Osborne McGraw-Hill.(ISBN: 0-07-134168-4)

Soukoup, Ron; Kalen Delaney. 2000. Inside Microsoft SQL Server 7.0.Microsoft Press. (ISBN 0-735609985)

Spenik, Mark; and Orryn Sledge. 1998. Microsoft SQL Server 7 DBA SurvivalGuide. Sams. (ISBN: 0-672-31226-3)

Talmage, Ron. 1999. Microsoft SQL Server 7 Administrator’s Guide. Prima.(ISBN: 0-7615-1389-2)

Informix Books

Doe, Charleton. 1997. Informix OnLine Dynamic Server Handbook, 1/e. PrenticeHall. (ISBN: 0-13-605296-7)

Informix Software, Inc. 1996. Evolution of the High Performance Database, 1/e.Prentice Hall. (ISBN: 0-13-594730-8)

––– 1996. Informix Performance Tuning, 2/e. Prentice Hall. (ISBN: 0-13-239237-2)

Lumbley, Joe. 1999. Informix DBA Survival Guide, Second Edition. Prentice-Hall.(ISBN: 0-13-079623-9)

McNally, John (Editor); Glenn Miller, Jim Prajesh, Jose Fortuny, and RobertDonat. 1997. Informix Unleashed. Sams. (ISBN: 0-672-30650-6)

DB2 Books

Bullock, Diane; Jonathan Cook; et al. 1999. DB2 Universal Database and SAPR/3, Version 4. Prentice-Hall. (ISBN: 0-13-082426-7)

IBM. 1997. IBM DB2 for AIX and SAP R/3 Administration Guide. IBM. (ISBN: 0-73840-990-1) (part# : SG24-4871-00)


Oracle Books

Adkoli, Anand, and Rama Velpuri. 1998. Oracle NT handbook. Osborne. (ISBN:0-07-211917-9)

Ault, Michael. 1997. Oracle8 Administration & Management. Wiley & Sons.(ISBN 0471192341)

Corey, Michael., [et al.]. 1997. Oracle8 Tuning. Osborne McGraw-Hill. (ISBN:0-07-882390-0)

Koch, Loney. 1997. Oracle8: The Complete Reference. Osborne McGraw-Hill.(ISBN: 0-07-882396-X)

Loney, Kevin. 1997. Oracle8 DBA Handbook. Osborne McGraw-Hill. (ISBN: 0-07-882406-0)

Loney, Kevin; Noorali Sonawalla, and Eyal Aronoff. 1998. Oracle8 AdvancedTuning & Administration. Osborne McGraw-Hill. (ISBN: 0-07-882534-2)

Spence, Greg. 1999. SAP R/3 and Oracle Backup and Recovery. Addison Wesley.(ISBN: 0-201-59622-9)

Velpuri, Rama; and Anand Adkoli. 1998. Oracle8 Backup & Recovery Handbook.Osborne McGraw-Hill. (ISBN: 0-07-882389-7)

––– 1997. Oracle Troubleshooting. Osborne McGraw-Hill. (ISBN: 0-07-882388-9)

Books on Other Topics

Disaster Recovery

� Corrigan, Patrick. 1994. LAN: Disaster Prevention and Recovery. PrenticeHall. (ISBN: 0-13-015819-4)

� Rothstein, Philip. 1995. Disaster Recovery Testing: Exercising YourContingency Plan. Rothstein Associates. (ISBN: 0-964164809)

� Schreider, Tari. 1998. Encyclopedia of Disaster Recovery, Security & RiskManagement. Crucible. (ISBN: 0-966272900)

� Toigo, Jon. 1995. Disaster Recovery Planning. John Wiley & Sons. (ISBN: 0-471121754)

Security

� Russell, Deborah; GT Gangemi Sr. 1992. Computer Security Basics; O'Reilly.(ISBN: 0-937175-71-4)

Scripting

� Perl, www.perl.com

� Hoffman, Paul. 1997. Perl 5 for Dummies. IDG. (ISBN: 0-7645-0044-9)

� Schwartz, Randal; Tom Christiansen, and Larry Wall. 1997. Learning Perl,2nd edition. O’Reilly. (ISBN: 1-56592-284-0)


� Schwartz, Randal; Erik Olson, and Tom Christiansen. 1997. Learning Perl onWin32 Systems. O’Reilly. (ISBN: 1-56592-324-3)

� Srinivasan, Sriram. 1997. Advanced Perl Programming. O’Reilly. (ISBN: 1-56592-220-4)

� Vromans, John. 1996. Perl 5 Desktop Reference. O’Reilly. (ISBN: 1-56592-187-9)

� Wall, Larry; Tom Christansen, and Randal Schwartz. 1996. ProgrammingPerl, 2nd edition. O’Reilly. (ISBN: 1-56592-149-6)

Magazines

sapinfo.net, http://www.sapinfo.net/

Intelligent Enterprise, http://www.intelligenterp.com (formerly known as SAPTechnical Journal)

SAP Professional Journal, http://www.sappro.com/

SAP insider, http://www.sapinsideronline.com

Helpful Third-Party Information

SAP Service Connection

SAP service connection to SAP (rcPack):

� HS Network Technologies950 Tower Lane, 12th floorFoster City, CA 94404 USATel.: (650)-286-3018, FAX: (650)-287-3372

Business Continuation

� Comdisco, www.comdisco.com

� Disaster Recovery Journal, www.drj.com

� DRI International, www.dr.org

� IBM Business Recovery Services

� SunGard Recovery Services, www.recovery.sungard.com

Organizations

� Americas’ SAP Users’ Group (ASUG), www.asug.com

• For customers in the Americas, ASUG is the only vehicle to submitrequests for upgrades and enhancement to SAP.


Web Sites

SAP

� SAP, www.sap.com

� mySAP.com, www.mySAP.com

� SAPNet, service.sap.comNote: you need a SAPNet user ID to access SAPNet

� SAP America, www.sap.com/usa

� SAP America, training, www.sap.com/usa/trainsupp

� SAP Labs, Simplification Group, http://wwwtech.saplabs.com

� SAP Online Store, www.sap.com/store_index.htm

� SAP Complementary Software Program, www.sap.com/CSP

SAP Affiliates

Americas’ SAP Users’ Group (ASUG), www.asug.com

Third-Party

� SAP Fans, www.sapfans.com

� SAP Club, www.sapclub.com

� SAP Tools, http://sap.ittoolbox.com

� ERP site, www.erpsupersite.com

� ERP central, www.erpcentral.com

Internet News Groups

� SAP-related

• comp.soft-sys.business.sap

� Other

• comp.client-server

� Operating Systems

• UNIX

• comp.os.unix

• comp.unix.*


• NT

• comp.ms-windows.nt.*

� Databases - Oracle

• comp.databases.oracle.*

� Databases - DB2

• comp.databases.ibm-db2

� Databases - Informix

• comp.databases.informix

� Databases - MS SQL server

• microsoft.public.sqlserver.*

• comp.databases.ms-sqlserver

Other Resources

Operating System

� UNIX

• Compaq Unix, www.tru64unix.compaq.com

• HP UX, www.hp.com/products1/unixservers/

• IBM AIX, http://www-1.ibm.com/servers/aix/os/index.html

• Fujitsu Siemens Reliant, www.fujitsu-siemens.com/servers/rm/rm_us/reliant.htm

• Sun Solaris, www.sun.com/solaris

� NT

• Microsoft, www.microsoft.com/ntserver

• Microsoft TechNet, www.microsoft.com/technet

Database

� Oracle

• Oracle, www.oracle.com

� SQL server

• Microsoft, www.microsoft.com/sql/default.asp

� Informix

• Informix, www-4.ibm.com/software/data/informix


� DB2

• IBM, www-4.ibm.com/software/data/

Other Helpful Products: Contributed by Users

The products listed here have been recommended by users and consultantsand are provided as a starting point for your research.

A listing of these products does not constitute an endorsement by SAP.

The following list is not all-inclusive. These products have different featuresand prices, which meet different requirements. It is your responsibility to testtheir compatibility with your requirements and needs, and to select theproduct that is appropriate to your installation. For products that have beencertified by SAP to work with SAP R/3, see Complementary Software Programat www.sap.com/CSP.

UNIX

Backup

� Networker, Legato, www.legato.com

Monitor

� Performance monitor

• Stopwatch, Envive, www.envive.com

� System monitor

• OpenView, HP, www.openview.hp.com

Scheduler

� AutoSys, Computer Associates, ww.cai.com

� Maestro, Tivoli, www.tivoli.com

As a precaution, you should test all third-party software for compatibility and stability on a testsystem before installing them in a production environment. There are cases where a programmany conflict with another program or the hardware and crash the system.

Testing software applies to both the server and workstation that the system administrator uses.

In an NT environment, ifa particular task ismission-critical, use a

dedicated system to perform thattask. A dedicated systemeliminates much of the potentialfor conflict.

Caution


Spool Management

� Dazel for R/3, Dazel, www.dazel.com

Other

� Messaging:

• TopCall, Topcall Intl., www.topcall.com

NT

Backup

� ARCserve, Computer Associates, www.cai.com/arcserveit

� OmniBack II, HP, www.openview.hp.com

� Ultraback, BEI Corp, www.ultrabac.com

Monitor

� Log monitor

• ELM, TNT software, www.tntsoftware.com

• Provision Network Monitor (formerly AlertPage), ComputerAssociates www.platinum.com/products/provis/po/nmon_pv.htm

� System monitor

• LANDesk Server Manager, Intel,www.intel.com/network/products/landesk/

• NetIQ, NetIQ, www.netiq.com

• OpenView ManageX, HP, www.openview.hp.com

• RoboMon, Heroix, www.robomon.com

Remote Control

� Compaq Carbon Copy 32, Compaq, www.compaq.com/services/carboncopy

� LapLink for Windows NT, Traveling software, www.travsoft.com

� pcANYWHERE32, Symantec, www.symantec.com/pca

� Remote Desktop 32, Network Associates, www.nai.com

� Timbuktu Pro 32, Netopia, www.netopia.com


Scheduler

� Auto Task 2000, Cypress Technologies, www.cypressnet.com

� Event Control Server, Vinzant, www.vinsoft.com

� Launch Pad, Cypress Technologies, www.cypressnet.com

� crondSys, # ifdef Software, www.ifdef.com

� Schedule Wizard 98 (shareware)

Spool Management

� Dazel for R/3, Dazel, www.dazel.com

Other

� Anti-virusSee SAP Note 106267 for known problems with certain anti-virusprograms.

• InocuLAN, CA, www.cheyenne.com

• Norton AntiVirus, Symantec, www.symantec.com

• NT shield, Network Associates, www.nai.com

� FTP client

• AbsoluteFTP, Van Dyke Technologies, www.vandyke.com

• CuteFTP, GlobalSCAPE, www.cuteftp.com

• WS_FTP, Ipswitch, Inc., www.ipswitch.com

� NT monitor

• Quick slice, NT Resource Kit

� Time sync

• TimeServ, NT Resource Kit

Common, Both UNIX and NT

� UPS control

• Powerchute, APC, www.apcc.com

� Scripting

• Perl, www.perl.com

� Time sync

• Network Time Protocol, www.eecis.udel.edu/~ntp


Network

� Network Analyser

• Sniffer, Network Associates, www.nai.com

A P P E N D I X

C

KUseful SAP Notes

Overview

The SAP Notes are grouped by major area:

� SAP R/3

� Operating System

� Database

Within each group, the notes are grouped by category. These notes are theones that we found important or useful during this book’s creation. Morenotes exist for each group. We encourage you to explore the SAP Notes to seewhat other notes would be of interest or importance to you. Over time, someof these notes may become obsolete and get removed.

Note

SAP Notes were formerly known asOSS notes. The Online Service System(OSS) is now known as SAPNet.


SAP Notes

Category SAP Note # Description

11886 Central syslog cut off

15466 Customer name range

21559 Examination of SAPgui problems

31557 The multi-client concept of SAP R/3 – overview

42074 Using the SAP R/3 dispatcher monitor “dpmon”

45580 How are syslog files deleted?

86985 Release of SAP Releases for SAP add-ons (IS)

Batch 06604 Deleting job logs at the operating system level

Batch 11728 Background jobs with low priority

Batch 16083 Standard jobs, reorganization jobs

Batch 18307 Batch input logs and reorganization

Batch 24092 Distribution of background jobs on applicationservers

Batch 31503 FAQ: Background jobs

Batch 36280 Background work processes reserved for jobclass A

Batch 37104 Error analysis: Background processing system

Batch 70639 How are batch jobs scheduled

CCMS 71364 Collective note: monitoring ST04, DB02, ST10,ST03 (30c-31h)

Client 07312 Create client 066 for EarlyWatch

Client 13391 Deleting/resetting a client (up to 3.0f)

Client 35952 Client deleted, space still filled in database

Client 40672 System changeability and client control

Client copy 4010 Tables missing after client copy

Client copy 24853 CC info: Client copy, functionality in 3.0, 4.0

Client copy 47502 CC-TOPIC: Remote Client copy

Client copy 69556 CC-TOPIC: Missing tables and data

Client copy 70643 CC-TOPIC: Delete client

Client copy 84504 CC-TOPIC: SM29 transfers data in spite ofcancel

Config 21636 RAM extension: Which changes to profile?


Config 31395 System parameters: Defined where? Displayedhow?

Config 33576 Memory management (as of 3.0c, Unix and NT)

Config 39412 How many work processes to configure?

Config 44695 Memory management (as of 3.0c, AS400)

Ops mode 16845 Operation mode switch without backgroundprocesses

Patches 19466 Downloading a patch from SAPSERVx

Patches 29372 Unpacking CAR archives

Patches 33525 Important information about SAP patches < 3.1H

Patches 37617 Online Correction Support (OCS)

Patches 53902 Conflicts between Hot Packages / LCPs andAdd-Ons

Patches 63786 FAQ – Frequently Asked Questions: sapservX

Patches 63845 Corrections on SAPSERVx – searching for files

Patches 73510 Problems during upgrade of patched sourcerelease

Patches 74545 Problems when unpacking CAR archives

Patches 79376 Installation of the 3.1H kernel

Patches 80117 Admin functions in Online Service System

Patches 82264 Important information about SAP patches >=3.1H

Patches 85820 Patch is not displayed in patch queue

Patches 86241 HR Legal Change Patches for the HR component

Patches 87432 Contents of and applying LCPs

Patches 89089 Configuration of SAP R/3 systems for LCPs

Patches 96885 Downloading a front-end patch from SAPSERVx

Patches 97621 OCS Info: Online Correction Support (OCS)

Patches 97623 Patch types

Patches 97630 Known problems with patches >= 3.1H

patches 104664 OCS info: applying patches from CD

Patches 119738 Problems during upgrade with too new hotpackages

Patches 169142 Online Correction Support (OCS)



Patches 173814 OCS: Known problems with Support PackagesRel. 4.6

Patches 212876 The new archiving tool SAPCAR

Problems 15374 Checklist: Performance analysis

Problems 16513 File system is full – what do I do

SAPNet 15641 Print/download in Online Service System

SAPNet 22235 OSS1: What to do if SAP R/3 does not run?

SAPNet 26740 Online Service System registration form, NorthAmerica (for customers without existing OnlineService System accounts)

SAPNet 29501 Search procedure for notes and messages inOnline Service System

SAPNet 31515 Service connections

SAPNet 32411 The priority of your Online Service Systemmessage is changed

SAPNet 32789 OSS – Quick reference sheet

SAPNet 33221 Easy to use guide for transaction OSS1(SAPSERV4)

SAPNet 40024 Transferring customer files to sapservX via FTP

SAPNet 40866 Information required for registration keys

SAPNet 45027 User maintenance and creation in Online ServiceSystem for customer

SAPNet 69224 Access to the SAPNet server with Online ServiceSystem user id

SAPNet 69378 Inbox BIBO in OSS/O01

SAPNet 74313 New customer messages in Online ServiceSystem

SAPNet 75002 Confirmation of Online Service Systemregistration

SAPNet 75686 Changing/Deleting Online Service System usersand installations

SAPNet 80618 Access to Online Service System services via theinternet

SAPNet 81908 Change to Online Service System user data

SAPNet 169296 Integrating service connections into maintainsystem data

SAPNet 169329 New functions in the SAPNet as of 09-05-06/99



SAPNet 170102 Automatic opening of a service connection

SAPNet 171569 Maintaining service connection in system datamaintenance

SAProuter 30289 SAProuter documentation

SAProuter 30374 SAProuter installation

SAProuter 87388 Download SAProuter by FTP from sapserv#

Security 23611 FAQ concerning SAP R/3 security

Security 39267 SAP R/3 Security Guide

Security 48018 Data security in SAP R/3

Spool 02510 Printer off: What happens to the data?

Spool 03255 Spool log with “bad print control Sxxxx”

Spool 06427 How do you transport a printer definition

Spool 08462 Performance problems – spool output

Spool 09876 Cannot read my hostname

Spool 10551 Table TST03 (tablespace PSAPPROTD) sizeincreasing

Spool 10743 Name of PC longer than 8 characters

Spool 10755 Long name for routing computer

Spool 11070 Space requirements of TemSe and spooler

Spool 12550 Problems with remotely connected printers(WAN)

Spool 18706 Tuning the spooler

Spool 23389 Transporting printer definitions

Spool 25941 SAP R/3 does not find host name

Spool 26009 SAP R/3 does not print, first steps

Spool 27831 Priority of output requests?

Spool 29666 Authorizations for spool requests

Spool 30187 Viewing completed print data for output device.

Spool 48914 Output requests are partially delayed

Spool 64333 Change default value for spool retention period

Spool 64337 Transport output devices (printer)

Spool 64628 Using network printers from SAP R/3

Spool 78401 Download a list from SAP spool

Start/stop 00387 Problems when starting up a DB



Operating System Notes

Common to Multiple Operating Systems

NT

Start/stop 17108 Shared memory still present, startup fails

TMS/CTS 5668 Transporting report writer objects

TMS/CTS 11599 Reversing transports (not possible to do)

TMS/CTS 13807 Analyzing Correction & Transport Systemproblems



80266 Installation of NT application servers in a UNIXenvironment

28781 Central transport directory NT/UNIX


28665 Central syslog under NT

89510 Installation notes for pcANYWHERE

Backup 71440 Problems when restoring DLT tapes withNTBackup

Config 22240 Windows NT Control Panel settings

Config 28392 Two systems on one NT machine

Config 31559 Setting environment variables for NT kernel

Config 31563 Setting environment variables for NT kernel

Config 33772 The correct configuration of Dr.Watson

Config 65761 Configuration problems under Windows NT

Config 68544 Memory management under Windows NT

Config 74810 Notes on SAP services and NT registry

Config 75354 Multiple SAP instances on NT


Config 88416 Zero Administration Memory Management as of4.0A/NT

Eventlog 72616 Syslog messages in the NT event log

Patches 29372 Unpacking .car archives

Patches 74545 Problems when unpacking CAR archives

Perfmon 102390 Use of NT performance monitor

Perfmon 110529 Professional use of the NT performance monitor

Problems 10616 Saposcol or collector not running

Problems 21790 WinNT: problems with notepad.exe

Problems 44803 Connection reset by peer

Problems 49776 Evaluating Dr.Watson log file

Problems 51781 Problems with SAPPAD

Problems 53211 Win NT appears to hang, SAP service problems

Problems 70572 SAP R/3 background problems on Win NT

Problems 100972 Help for analyzing a Win NT “blue screen”

Problems 122288 Win 3.51/4.0 no longer responds (hangs)

Problems 129813 NT: Problems due to address spacefragmentation

SAProuter 41054 SAProuter as a service

Security 36462 Note for Oracle security on WinNT

Service pack 30478 Service Packs on Windows NT

Service pack 85582 High memory requests under NT 4.0 SP 3 fail

Start/stop 32182 Windows NT: Event log message when startingSAP R/3

Start/stop 35388 Problems on STOP/START of SAP R/3 via NTscheduler

TMS/CTS 28781 Central transport directory NT/UNIX

TMS/CTS 62739 Configuring a central transport host

Virus 106267 Problems with certain anti-virus software



UNIX

AS-400


21960 Two instances/systems on one UNIX computer

28781 Central transport directory NT/UNIX

80266 Installation of NT application servers in a UNIXenvironment

AIX 48689 IBM service, fixes and patches

AIX 64885 SAP R/3 relevant operating system patches for AIX

Digital 72984 Release of Digital UNIX 4.0B for Oracle

Digital 39698 cpio generated when restoring “sparse files”

Digital 136653 Performance problems on Digital UNIX 4.0D and 4.0E

HPUX 06599 Sudden performance decrease, in UNIX too

HPUX 41596 HP-UX: problem solving using HP-UX patches

HPUX 64884 SAP R/3 relevant OS patches for HP-UX

HPUX 99224 HP-UX Operating System patches

HPUX 99527 Problems with MC Service Guard

HPUX 101229 Informix: HPUX 10.20 patches

HPUX 143527 End of support for HP-UX 10.20, HP-UX 10.10, HP-UX10.01

SUN 64887 SAP R/3 relevant operating system patches for Solaris

SUN 71479 Solaris recommended patches

SUN 101883 SAP R/3 relevant patches for Solaris 2.6

SUN 172524 Time stamp is incorrect

SUN 182552 Y2K patches for SOLARIS


Config 44695 Memory management as of 3.0C, AS/400

Copy 49023 Client copy

CTS 37987 Importing transports

Patches 60856 OSS1 and hot packages

Performance 49201 Performance settings

Performance 107104 4.0B kernel performance


Database Notes

MS SQL server

Problem 125705 SAP R/3 hangs in STARTSAP

Problem 154599 SAP R/3 cannot be started/shmget fails

Problem 162580 Roll memory leak & SYSTEM_CORE_DUMPED

Problem 163022 Work process terminate abnormally

SAProuter 65600 SAProuter


62849 “news,” compilation of notesThis note is important for SQL server installations.

28667 MS SQL Server specific profile parameters

67320 Basic knowledge of MS SQL Server

85846 Released operating systems SAP R/3 4.0x/4.5x MS SQLServer

95901 SAP R/3 on MS SQL Server – release strategy

126131 Installing add-on on MS-SQL svr 3.x

159171 Recompilation of Stored Procedures

163315 MS SQL 6.5 – end of support

201075 Additions upgrading to 4.6C ... MSSQL Server

302312 Additions to upgrade to 4.6D MSSQL Server

7.0 82035 Improvements for MS SQL Server 7.0

7.0 95600 Installation of SAP R/3 on SQL Server 7.0

7.0 138392 SQL Server 7 and Vertex database

7.0 153802 Deleting transaction log files in MSSQL 7

7.0 160178 MSSQL 4.6A minimum corrections

7.0 conv 92410 DB conversion from MS SQL 6.5 to 7.0

7.0 conv 104392 Additional info: conversion 6.5/7.0 MS SQL Server

7.0 conv 107471 Special SQL Server 7.0 conversion methods

7.0 conv 107483 SQL Server 7.0: conversion on Alpha



7.0 conv 129122 Conversion SQL Server 6.5/7.0 consultant companies

7.0 conv 130689 Conversion of multiple SAP R/3 systems from 6.5 to 7.0

2000 209596 Setting up Microsoft SQL Server 2000

2000 327494 Configuration Parameters for SQL Server 2000

2000 377430 SQL Server 2000 installation CD of SAP

Backup 37152 SQL Server backup to a dump file

Backup 44449 Backup strategies with MS SQL Server

Backup 48585 Database copy

Backup 50990 DB – Backup/Restore of Microsoft SQL Server

Backup 68818 Error in SQL Server backup/restore

Backup 70300 Backup/restore (compilation of notes)

Backup 151603 Copying a SQL Server 7.0 database

Backup 153763 Sub-optimal tape backup performance

Backup 166588 File backup with SQL server 7.0

CCMS 139945 SAP database monitor for MS SQL Server

CCMS 141118 New scheduling calendar in the CCMS (DB13) SQLServer

Client copy 85443 Client copy

Config 67071 Moving database devices

Config 70517 Restructuring a SQL Server installation

Config 80102 Device management for MS SQL Server

Config 97066 Running two SAP R/3 systems on one sever

Config 126808 Configuration parameter for SQL Server 7.0

HA 111372 Stand-by database for MS SQL Server

Kernel 77012 Spool, batch enhancements in kernel

Maint 67437 DBCC checks

Maint 142731 DBCC checks for SQL server 7.0

Performance 38657 Slow performance of SAP R/3 on MS SQL Server

Performance 61340 Update statistics on MS SQL Server system tables

Performance 76052 Update statistics on database tables

Problems 67297 Error 1105 trans/db log full

Problems 79262 Incorrect database and log size in DB02 and ST04

Problems 79883 Incorrect database freespace alert displayed



DB2 / UDB

Problems 81692 Suspect database

Problems 87027 Fill level database logs

Problems 87029 Fill level of the database and log

Problems 111291 Analysis and avoidance of deadlocks

Problems 129190 Problems with Performance Monitor and SQL Server 7.0

Problems 150495 Deadlocks with MS SQL 7

Problems 155402 Analysis of hanging situations

Problems 166861 Analysis of DB13 problems

Problems 168408 R3load process dies directly during a start

Problems 425763 No error log generated when an instance profile is missing(This note is in German)

Recovery 50745 Database restore for SQL Server

Recovery 70161 SQL error 916 and 4001 after restore

Recovery 82699 Rebuild master database

Recovery 94213 Point-in-time-recovery fails

Security 28893 Changing password of users sapr3

Security 116225 Password change for database user sapr3

Service pack 62988 Service Packs for MS SQL Server

Service pack 66365 Windows NT service packs (problems caused by)

Service packs 159069 SQL Server 7.0 service pack 1 install terminates

Service packs 159268 Service Pack installation on MS SQL server 7.0


80625 Released operating systems SAP R/3 3.x/4.x DB2 forOS/390

85842 Released operating systems SAP R/3 4.0x DB2/CS

410252 Installing the latest 4.6D DB2 UDB Admin Tools

Copy 111206 390: Homogeneous System Copy

Performance 92795 390: R3trans performance improvements

Performance 97014 390: R3trans performance improvement

Performance 122599 390: Performance of the update

Performance 107123 400: Performance improvement on the database server



Informix

Problems 54028 400: Overflow in SQL package. SQL0904, SQL0901

Problems 84270 390: Deadlocks on TPFBA and TPFID

Problems 97449 390: Unspecified core dumps with HPDT UDP

Problems 98306 390: Tablespace name not set

Problems 141527 390: Generation of matchcode objects fail

Problems 149292 UDB: DB2adut1 displays no journals

Problems 151085 CS: Some work process end with SQL1403

Problems 163356 390: Signal 11 during DDIC operations

Restore 78332 CS: Database crash/core in restore from ADSM

Restore 163731 CS: Restore Terminates with SQL0973

Security 80292 Security DB2 with SAP R/3 under NT


93264 Informix: Important News

53746 Use of correct Informix versions

62340 INFCFGCHECK: ‘Download’ and ‘First steps’

64001 INFCFGCHECK: Detailed messages of single checks

71776 INFCFGCHECK: Automate database checks

85840 Released operating systems SAP R/3 4.0x Informix

93868 BC511 Instructors contributions

AIX 102204 AIX 4.3 patches necessary with Informix

Backup 11462 Informix: Copying and renaming an SAP R/3 database

Backup 167878 Informix: Copying and renaming an SAP R/3 database

CCMS 66322 CCMS Database administration (DB13)

Config 12825 Installation of two SAP R/3 systems on one host

Config 41360 Database configuration via onconfig parameter

Config 141054 Informix environment parameter for 7.3x

Document 154895 Ordering additional Informix documentation

HPUX 41596 HP-UX Problem solving using HP-UX patches

HPUX 101229 Informix: HPUX 10.20 patches

Maint 22941 Reorganization of table and dbspaces



Oracle

Maint 29155 Consistency check of an Informix database

NT 126175 Service Pack 4 on NT4.0 with Informix IDS 7.X

Performance 38307 Reducing shared memory consumption

Performance 156766 Performance problems with Informix 7.3x

Performance 184760 Update Statistics: SAPDBA Rel.>=4.6A old strategy

Problems 31171 DB start/stop brings warnings

SOLARIS 48338 Problem solution through SOLARIS/SUN patches

Y2K 187183 Downloading the ON-Archive Y2K patch



85838 Released operating systems SAP R/3 4.0x Oracle

112325 End of “Cust Care Support” Oracle 7.3.*

01039 Problems with ORACLE TWO_TASK linking


96397 OS06: Unable to open file os_sys.log

125242 Do not alter MAXEXTENTS on dictionary tables

128221 Increased memory consumption with Oracle 8

AIX 51396 Kernel extensions on AIX SMP computer

BR 02239 cpio with BRBACKUP and BRARCHIVE

BR 12593 BRBACKUP on several different tape drives

BR 13550 Using BRBACKUP and BRARCHIVE

BR 43494 Collective note: BRBACKUP, BRARCHIVE, BRRESTORE

BR 43499 Collective notes concerning DBA tools

CBO 93098 Changes to the upgrade to 4.0 – CBO Oracle

CBO 93256 CBO: changes for installation of 4.0

CBO 127715 CBO: Optimal parameters for performance

CCMS 85609 Offline backup via CCMS/DB13 not possible

Config 03809 Changing the size of the redo log files

Config 09705 Mirroring the ONLINE REDO LOG FILES

Config 94801 Environment variables for Windows NT


HPUX 92788 HP-UX/Oracle: hanging LGWR

Patches 127395 Current patch set for Oracle release 8.0.5

Patches 181195 Current patch set for Oracle release 8.1.5

Performance 33868 Performance problems NT 3.51 / Oracle / TCP/IP

Performance 72638 Performance problems with SQL*Net V2

Performance 102042 System hang on AIX SMP computers under high load

Performance 114716 Performance problems Oracle 8.0.4/all entries

Problems 33735 Archiver stuck in Windows NT

Problems 38006 Ora-1631 max extents reached. Which table?

Recovery 03804 Restoring from a full backup

Recovery 04157 General flowchart for Oracle recovery

Recovery 04160 Tape management for recovery

Recovery 04161 Complete recovery

Reorg 12921 Reorganization of SYSTEM tablespace

Reorg 40521 Reorganization (external tools)

Reorg 43487 Collective note: SAPDBA – reorganization

SAPDBA 12621 SAPDBA – speeding up reorganization

SAPDBA 15465 SAPDBA – shrinking a tablespace

SAPDBA 19193 SAPDBA – size and reorg of table space PSAPTEMP

SAPDBA 29348 SAPDBA – reorganization of single table; PSAPTEMP

SAPDBA 42293 SAPDBA – new command line option – analyze

SAPDBA 43486 Collective note: General SAPDBA

SAPDBA 43490 Collective note: SAPDBA – Recovery

SAPDBA 43491 Collective note: SAPDBA command line options

SAPDBA 44395 SAPDBA: missing indexes after reorg run

SAPDBA 44595 SAPDBA: general procedure for reorganizations

Security 36462 Note for Oracle security on WinNT

Start/stop 02775 Oracle cannot be started

SUN 44361 Sun Solaris: database does not start after patch

SUN 116453 Backup via DB13 on Solaris Oracle 7.3.3

SUN 183292 Oracle crash because of kernel AIO bug on Sun

Tablespaces 02425 Function of tablespaces/Dbspaces on the database



Tablespaces 03807 Tablespace PSAPROLL, rollback segments too small

Tablespaces 09321 Next-extents in ORACLE system tables are too large

Tablespaces 39650 Maximum number of extents per tablespace

Upgrade 89691 Additional info: migrating to Oracle 8.0.3

Upgrade 98507 Additional info: migrating to Oracle 8.0.4

Upgrade 111922 NT/Oracle >= 7.3.3.4 necessary

Upgrade 126137 Additions Oracle upgrade to 8.0.5 UNIX 64 bit

Y2K 172380 Oracle Y2K bugs and fixes


A P P E N D I X

D

LUpgrade Discussion

Upgrade Discussion

An upgrade is an update to your SAP R/3 system. The question of whether toupgrade your system to a new release depends on many complex factors.Most importantly, the decision to upgrade should be based on business need.Some of these factors are outlined below:

� Desired functionality in new release

• This can be found in the release note for the specific release.

� Problem fixes and resolutions

� The need to be on a supported release

Reasons Not to Upgrade

Some reasons not to upgrade include the following:

� Cost—the following items could increase the cost of your upgrade.

� You must:

• Upgrade the database and operating system (if required)

• Purchase and install additional hardware (if required)


• Test to find problems with the upgrade

• Upgrade the SAPgui on the users computers

• Find the time to do all the above

� Disruption for users, especially if there is no functional enhancement forthem.

� Diversion of resources (Company resources that could be applied to othertasks would be assigned to upgrading the SAP R/3 system.)

� Desire to be on the latest release (While desirable for a personal resume,this reason is not a valid business reason to upgrade your system.)

When to Upgrade

In deciding to upgrade your system, ask yourself the following questions:

� Have the reasons for upgrading or not upgrading been analyzed?

� Has the business need criteria been met?

� If you installed any Industry Solution (IS), are IS patches available for thenewrelease?

� If the patches are not available, you cannot upgrade.

Upgrade Issues

An upgrade can be more complex than a new implementation because:

� There is real data on the system that is being upgraded.If the upgrade fails, the company’s operations could be affected andbusiness could stop. This failure would require you to recover the database(refer to the section on disaster recovery).

� The system is unavailable for users during a portion of the upgradeprocess.The technical downtime is six to twelve hours. In addition, many othertasks are performed around the backup that could increase this downtimesignificantly. System downtime could significantly impact the operationsof the business during this period.

� Upgrade changes could require changing configuration, testing, training,and documentation.

Appendix D: Upgrade Discussion 717

� Changes require regression testing:

• Do business processes function as they did before?

• Does custom code need to be changed due to changes from theupgrade?


Software Issues

The following software has to be compatible with the SAP R/3 release youplan to upgrade to:

� Database

� Operating system

� Third-party applications that compliment the SAP R/3 system (forexample, external tax packages, job schedulers, system monitors, spoolmanagers, and so on)

Hardware

The upgrade requires free working space on disks to run.

� The amount of space required differs with operating system and database.

� Some of the space is released after the upgrade; other space is permanentlyused.

As each release adds functionality, the required disk space, processing powerand memory required generally tends to increase.

A system configuration that was adequate for one release may be inadequatefor a later release. This is especially apparent when jumping release levels;example upgrading from 3.1H to 4.6B. The following table is compiled fromSAP Notes:

SAP Release CPU increase % Memory increase %

3.1H to 4.0B 30 30

4.0B to 4.5B 20 20

4.5B to 4.6A 10 30

4.5B to 4.6B 20 10

4.5B to 4.6C 10 30


Performance

Upgrade performance is difficult to predict. Performance is sensitive to avariety of variables, some of which can have significant impact. Therefore, anupgrade of the test system should be done to determine timing values foryour configuration.

The following are a few of the factors that affect the performance of anupgrade:

� Database and operating system

� Hardware

• Processor (number of processors and speed of each)

• Memory (amount available)

• Drive array

• – Performance factor (especially for writes)

• – Configuration (minimize or eliminate drive or channel contention)

• – Other I/O hardware (minimize or eliminate data channelcontention)

� Data volume for changes to tables that contain data

� For more information, see:

� http://wwwtech.saplabs.com/sysadmin to download the SAP R/3 UpgradeGuide

� service.sap.com/upgrade

A P P E N D I X

E

MTraining / Learning

Training / Learning

Mini-Basis system

For the Basis System Administrator, new tools will make your ability to learneasier. One of the most exciting is the mini-Basis system:

� The mini-basis system is a Basis-only system that will provide you aplatform to learn the various system administration functions in a safeenvironment. What we mean by this is the following:

� There are only Basis transactions in the system. Functional applications(i.e. FI, CO, SD, and so on) are not part of the system. This restriction allowsthe system to be installed in significantly less disk space than a full SAPR/3 system.

� The safe environment comes by your ability to install it on a workstationor PC, so anything you do on the mini-basis system does not affect any ofyour live systems. In this way doing anything dangerous or destructivewill not damage a live system.

As of this writing, there are two versions of the mini-basis system:

� NT/SQLserver 4.6D


� Linux/SAPDB 4.6B

As they require much less hardware to install than a full SAP R/3 installation,they can even be installed on a suitably equipped workstation. Fordemonstration purposes, the NT version has been installed on a notebookcomputer.

For more information on the mini basis systems please see the appropriateweb pages:

� NT/SQLserver 4.6D

• www.sap.com/technology/minisap

� Linux/SAPDB 4.6B

• service.sap.com/linux

They can both be ordered from the SAP shop at www.mysap.com/company/shop.

A P P E N D I X

F

NMonitoring Multiple SAP R/3 Systems

Overview

With CCMS, you now can monitor multiple SAP R/3 systems from a singlealert monitor. To do this you must first have established a RFC connection toa remote SAP R/3 system that you wish to monitor remotely. Therefore thisappendix is divided into two parts:

� Defining an RFC connection to a Remote SAP R/3 System

� Monitoring an Additional SAP R/3 System

Task

Define an RFC connection to a remote SAP R/3 system

1. In the Command field, enter transaction SM59 and choose Enter.


2. On the Display and maintain RFC destinations screen:

a. Expand the R/3 connections tree.

b. If there is not a RFC connection that you want to monitor, choose Create.

3. On the RFC Destination screen:

a. Under RFC destination, enter a name for the RFC connection, (for example,hspal008).

b. Under Connection type, enter the type of connection, (for example, 3 forSAP R/3 system).

c. Under Description, enter the identifying text, (for example, Connectionto DC2 system).


d. Under Logon, enter the user logon data (such as Client, User, and Password)that has authorization for the alert monitor and for system administrationin the target system.

e. Choose .


4. On the RFC Destination <XXXXX> screen:

a. Under Target host, enter the host name of the message server, (forexample, hspal008.pal.sap-ag.de).

b. Choose . A message is shown in the status bar.

c. Choose .

To find out the name ofthe message server, logonto the target system

and call Transaction RZ03. Themessage server is the SAP R/3instance with the M in theServices column.


5. The new RFC connection is shown under R/3 connections.

Task

Monitor an additional SAP R/3 system

1. In the Command field, enter transaction RZ21 and choose Enter.

2. Choose Technical infrastructure → Create remote monitoring entry.


3. On the Monitoring: Registering New Contexts screen:

a. Under Target system ID, enter the name of the SAP R/3 system to bemonitored, (for example, DC2).

b. Under for data coll., choose to select the RFC connection to the remoteSAP R/3 system.

c. Choose .

4. A success message is shown in the status bar.

Configuring the Batch Job to Collect Historical Data (RZ21)

The batch job that collects historical data must be running. As a default, thejob will not run. Running this job will add more data to the database andaffect database growth. The batch jobs provide the data for the performancehistory option above.

Task

Configure the batch job to collect historical data

1. In the Command field, enter transaction RZ21 and choose Enter (or from theSAP standard menu, choose Tools → CCMS → Configuration → RZ21-AlertMonitor).

Do not run this batch jobunless you wantperformance history data

(RZ20).


2. From the menu bar, choose Technical infrastructure → Performance Database →Define Background Job.

3. This user is the user ID that was used to log in.

4. Enter the date and time to run the job. The job will run every day.

5. Choose .


6. Choose .

7. Choose the Step2-Reorganizing database tab.

8. Enter the date and time to run the job. The job will run every week.

9. Choose .


10. Choose .

11. Choose .

12. In SAP R/3 release 4.6D, the system displays an additional selection tab.Repeat steps 8 and 9 to complete the configuration.


13. Choose .

14. The Status is now set to Released.

I N D E X

1Index

A

ABAPdump analysis

definition 152free selection 153in general 152performing 67, 73simple selection 153

editor 158, 159, 216execute 83, 215

Active processes 99Active users 148Adding additional systems

in general 232SAP logon 232

Administration basicsR/3 system 3

Administratoraccess key 561, 567guidelines 7requirements of 6roles

external to R/3 5factors that determine 4within R/3 5

Advanced quality assurance 488

AIS 196Alert monitor

acknowledge alerts 117adding a monitor 129alert threshold 416analyze alerts 115checking 65, 72, 75, 76create new monitor set 127finding alerts 110hiding SAP standard monitor sets 124in general 106maintaining thresholds 120views 109, 115

Alertsacknowledge 117analyze 115current 109database 67finding 110maintaining thresholds 120messages 421open 109paging system review 423parameters 422threshold, changing 416views 109, 115

Annual tasks


checklists 82database 83notes 84operating system 83other 84

Application serverdefinition 13in general 89, 426

Audit Information System (AIS)business 199complete 196in general 196system 198user defined 200

Auditsbusiness 199check for validity 217complete 196considerations 167different users 213financial 166in general 166information system 196security 167, 186security logs

filter group 1 208filter group 2 209in general 203parameters 206running 204

specific reports 216system 198tasks 217tools 196user defined 200user security jobs 214

B

Background jobsbatch 427creating 431housekeeing 428incorrect 443new 443others 428

performance 428, 429regularly scheduled jobs 427scheduling 431select 66, 70, 71, 79, 81, 439user ID 428

Backuparchive logs 381checking 459checking tape label 297checklist, strategy 47database 37, 46, 171, 293, 378, 458dedicated drives 57design strategy 44determine the number of tapes required 378determining correct tape label for 288differential 42frequency 37full 458IBM DB2 Universal Database 260in general 35, 37, 458incremental 41Informix 317initializing tapes 293, 298, 371Microsoft SQL server 291NTBackup 462offline 42, 298, 458on-demand 43online 42, 294operating system level 39, 47, 462overview 36performance

database restore options 57disk to tape 57factors affecting 55faster devices 55in general 54options 55parallel backup 56recovery 57

periodic archivals 458procedures

database check 45in general 45preparation 48verifying backups 45

RAID systems 58scheduled 43

Index 733

strategy 36supplementary 45tape management

handling tapes 51in general 48labeling tapes 49number to backup 378retention requirements 52tracking and documenting tapes 48, 51

tape storagein general 53offsite 53onsite 54

transaction logs 38, 45, 46types 40UNIX level 462using command line processor (DB2 CLP) 272verification 70without checking tape label 296

Batch input 67, 72, 443Batch jobs 95, 427, 429, 443, 445Books

IBM DB2 689Informix 689Microsoft SQL Server 689NT 687Oracle 690OS/400 688other topics 690SAP 682, 686third-party authors 687UNIX 687

BRARCHIVE 377BRBACKUP 374Buffers

definition 529hit ratio 530importing 488performance 529special transport, adding into import buffer 495,

507swaps 530tune summary 67, 72, 529

C

CAR files 603Cascade failures, minimizing 34CCMS alert monitor 65CDs 683Central instance

stopping 102Central processing unit (CPU) 535Central User Administration (CUA) 162Change and transport system (CTS) 486Change control

in general 472managing transports 483

Checking the database 366Checklists

annual tasks 82database 83notes 84operating system 83other 84

backup strategy 47daily tasks

critical 65, 70database 67notes 68operating system 68other 68R/3 System 65, 69

locked transactions 183monthly tasks 77

database 77notes 78operating system 77other 78

quarterly tasks 79database 80notes 81operating system 80other 80

stopping R/3 91weekly tasks 74

database 74notes 75operating system 75other 75


Cleaning tape drive 419Client copy

copy to different system/SID 662copy to same system/SID 658creating a client 655deleting a client 665log 666overview 653post-client copy tasks 664processing notes 654production system 669, 670SAP Notes 654security 655target client 658

Client-dependent changes 175Client-independent changes 174, 175Command Line Processor (DB2 CLP) 269Consumable supplies

check 462other considerations 464

Contracts, maintenance 421Crash kit

in general 27inventory list

documentation 27software 29

location 27Critical tasks

daily 70operating system level backups 462verify backups 70verify R/3 is running 70

CTS 486

D

Daily taskschecklists

critical 65, 70database 67notes 68operating system 68other 68R/3 System 65, 69

Dangerous transactionsin general 86, 178

recommended lock table 178restricted access table 183

Data security 171Database (DB)

administration 275backup 37, 46, 291, 458checking backup 45checklists

daily tasks 67consistency check 74passwords 195performance analysis 73, 76, 78, 531server

definition 13starting 88stopping 100stopping an instance 100TemSe 74

Database administration (DBA) 275IBM DB2 Universal Database 253Informix 309Microsoft SQL Server 275

Datesentering 96

DB2See IBM DB2 Universal Database 253DBA Scheduling 355DBCC 74DDIC

in general 222restricting access 187

Defragmentation, memory 530Deleting user session 247Deleting users 85Disaster

definition 18minimizing opportunities

cascade failures 34human error 33in general 32single points of failure 33

Disaster recoveryapplications, up or downstream 32backup sites 32business continuation 29business requirements

in general 20performance 36

Index 735

crash kit 27disaster, minimizing 32downtime 21high availability (HA) options 19integration 30offsite 30other considerations 32planning 18, 19recovery

groups 22process 26scripts 25, 26, 29time 21

reintegration to R/3 30scenarios

corrupt database 24hardware failure 24in general 23, 24loss or destruction of server facility 24

staffing 22testing 30types

offsite 23onsite 23

when to begin 21Downstream applications 32

E

EarlyWatch session 605, 608External interfaces 100

F

Failed updates 66File space

archiving 415expansion 415old transport files 418usage 414

File, retrieval 594Forms

Detailed Online Service System Note Record 474General Note Record 473R/3 User Change Request 224Sample Transport Request 485

Free space 414Frontend software 226

G

Graphical job monitor 70, 442Guidebook

how to use xxviiinew features xxviiiorganization of xxviiiprerequisites xxvtarget audience xxv

Guidelines 6

H

Hardwarecentral processing unit (CPU) 535disk 535in general 535memory 535review 421

Head contention 524Help 6High availability (HA) options 19, 171Hit ratio 530Hot packages 617Housekeeing jobs 428Human error, minimizing 33

I

IBM DB2 Universal Databaseadministration in SAP systems 253, 255backups and recovery 260books 689command line processor (DB2 CLP)

backing up 272overview 269resizing tablespace 272starting 269update database configurations 271update manager configurations 271

control center 273diagnostics 268


overview 254performance 255review planning calendar 266SAP Notes 709scheduling tasks 264space allocation 259starting 254stopping 255

Informixbacking up

logical-log 321overview 317requirements 317scheduling 317

checking the databaseconsistency 327overview 321reviewing results 322scheduling 321

DBA planning calendarchanging tasks 315checking status 313initializing 310scheduling tasks 312

disk space 329extending Dbspace 337further information 341overview 310SAP Notes 710SAPDBA 333scheduling database tasks 310starting and stopping 334updating statistics 326viewing message log 324

Initializingarchive tapes 374

Insider trading 165Instance

definition 13operation mode 447stopping 100

Internet news groups 692

K

Keep it short and simple (KISS) 8, 44

Kernel upgradeoverview 651restart options 653

KISS 8

L

Lock entry list 66, 72Locking

checklist 183client

modifiable 177permanent 176

dangerous transactions table 178logon 243prohibited password table 190restricted dangerous transactions table 183service connection 585transaction codes 83transactions, dangerous 178users 85, 189

Locksdefinition 145deleting 147in general 145, 172

M

Maintenancebasic 609contracts 421extended 609overview 608special 607table 466user 79, 241

Management, changechange control 472in general 188, 465managing transports 483, 486note assistant 475SAP Notes 472standard transport process 488table maintenance 466transportation methods 495

Memory

Index 737

defragmentation 530hardware 535

Microsoft SQL serverbackup

checking results 291checking tape label 297determining correct tape label 288initializing tapes 293, 298offline 298online 294with Microsoft tools 293without checking tape label 296

database activity 278database allocation 282deleting planning calendar entry 290Enterprise Manager 303error logs 303overview 275, 276passwords 305performance 278performance monitor 278run update statistics 305SAP Notes 707scheduling tasks 284starting 88, 276statistics update 74stopping 100, 276, 277verify consistency 305

Mini-basis system 719Modes 445Monthly tasks

checklistsdatabase 77notes 78operating system 77other 78R/3 system 77

Multi-role tasks checklist, stopping R/3 91mySAP

components xxiii

N

Network administartion 411New user setup 225Note assistant 475

O

Online Correction Support (OCS) 571Online Service System notes 384Operating system

SAP Notes 704Operating system (OS)

administration 411alert threshold 416checklists

annual tasks 83daily tasks 68monthly tasks 77quarterly tasks 80weekly tasks 75

file space archiving 415file space expansion 415file space usage 414full server backup 458monitor 68, 71, 531NT event log 422, 423old transport files 418passwords 194system logs 412tasks 412transporting method 507transporting objects 487

Operational securityin general 170, 186management change 188passwords 189sharing of user IDs 188

Operationsapplication server check 426background jobs 427consumable supplies 462definition 426distribution of work processes 452graphical job monitor 442in general 425modes

adding new 449assigning 454definition 446generate instance 447in general 445


other considerations 464system backup 458

OracleSAP Notes 711

OSS notes 472Output management

in general 387output printing 401printer setup 388printing screen 404spool check

consistency 407deletion, for 397printing problems 394

TemSe check 409

P

Paging system 421Passwords 189

changing 193database 195eliminating easy 189expiration time 189in general 189length 189lockout 189maintaining table of prohibited 190, 466Microsoft SQL server 305operating system level 194recording 191resetting 242sample tables 192security parameters 189standards 189system administration 222, 223

Patchapplication verification 648confirmation 647level 518logs 646

Performancebackground jobs 428backup

database restore options 57factors affecting 55

faster devices 55in general 54options 55parallel backup 56recovery 57to disks then tapes 57

buffers 529critical assumption 524database 531defining an RFC connection 721evaluation priority 524hardware 535IBM DB2 Universal Database 255in general 523, 525, 719memory 535memory defragmentation 530Microsoft SQL server 278monitoring multiple systems 721R/3 525resources 524training 719workload analysis 525

Permission creep 218Policies

backup frequency 37supplementary backups 45system adminstration 222user administration 220

Prerequisites xxvuser xxvi

Printer setupchecking the spool 394in general 388

Proceduresbackup

database check 45in general 45roles and responsibilities 46verifying backups 45

system administration 222user administration 220

Production refresh strategiesclient copy with data 669client copy without data 670database copy of production system 668overview 668

Production system

Index 739

not modifiable 174preventing changes 85

ProductsCDs 683contributed by users 694

Profile Generator 220Profile parameters, system

administration data 609editing 79, 608maintenance

basic 609extended 609

PXASee Memory 530

Q

Quarterly taskschecklists

database 80notes 81operating system 80other 80R/3 system 79

QuickSlice 509

R

R/3 Alert Monitor 415R/3 System 88

active processes 99administration 105administration basics 3annual tasks 82batch jobs 95checking for users 94

with application servers 94checklists

daily tasks 65, 69stopping R/3 91

definition 13external interfaces 100guidelines 6monthly tasks 77performance 523, 719, 721printer setup 388

quarterly tasks 79security 172starting 88status verification 70stopping 90, 91, 100, 101three-tiered configuration 13weekly tasks 74

R/3 system administrator 4Records

update 72Recovery 17Recovery scripts

business continuation 29creating 26definition 25

Regression testing 650Remote services

CAR files 603downloading files 600EarlyWatch 605overview 593SAPSERV 594

Resourcesinternet news groups 692magazines 691other 693SAP 681third-party information 686, 691web site 692

Restorereasons for 36strategy 36testing 37

Return codes, transport 511

S

SAASee System Administration Assistant (SAA) 106

SAP database administration 80SAP GUI

adding additional systems 232installing

file server, from 226prerequisites 225presentation CD, from 231


software 226SAP Notes

databaseIBM DB2 Universal Database 709Informix 710Microsoft SQL server 707Oracle 711

for further informationl 586implementing 477loading 475log file 481managing 472note assistant 475operating system 704

AS-400 706multiple system 704NT 704UNIX 706

OSS notes 472processing status 480searching 544special 604useful 58, 582, 650, 654, 699viewing 625, 628

SAP online store 681SAP products and resources 681SAP Service Marketplace 539SAP Software Center 571SAP* 222

restricting access 187SAPCAR.exe 603SAPDBA

backup 371cleanup 80Computing Center Management (CCMS) 349definition 333, 363getting started 334starting 88, 334stopping 100, 334to administer Informix 333using 375

SAPNet 685connecting to R/3 system 582customer messages 547

component 548confirming 558entering 547, 549

prioritizing 547problem description 548viewing 554

developerdeletion 564developer key request 560key entry 564object key request 566registration 559, 560, 562

logging on 540notes 650object

deletion 570key entry 570registration 559, 565

prerequisites 582problem solving 543SAP Software Center 571service connection 585

SAProuter 594SAPSERV 594

connect using a GUI 595connect using command prompt 597navigating 597partial organization 602retrieving files 594server specifics 594

SAR files 603Scenarios, disaster

corrupt database 24hardware failure 24in general 23, 24loss or destruction of server facility 24

Scheduling 63DBA planning calendar 312, 357IBM DB2 tasks 264Informix tasks 310Microsoft SQL tasks 284

Screen resolutionoptimal setting xxvii

Security 163access 168application 170audit log

filter group 1 208filter group 2 209in general 203

Index 741

parameters 206review 74running 204

authorization maintenance 82auto logout 146backups 171change management 188client copy 655controlling access 172data 171DDIC 187definition 164different user audit 213electronic card key access 169facility related items 171high availability (HA) options 171issues not covered in guidebook 162layers 168multiple user logins, prevent 172network 169operational 170, 186overview 161passwords 189

changing 193database 195eliminating easy 189expiration time 189in general 189length 189lockout 189maintaining table of probibited 190operating system level 194parameters 189recording 191sample tables 192standards 189

permission creep 218physical 168production system changes, preventing 172profile generator 220profile maintenance 82R/3 172router tables 169SAP* 187security reports 214segregation of duties 186sensitive data 165

sharing of user IDs 148, 188, 249user audit jobs 214

Security administration 163audits 166

considerations 167financial 166security 167

data protection 165insider trading 165other requirements 165

See IBM DB2 Universal Database 253See Performance 523, 719, 721See System administration 105Server

administration 411application 89

Service connection 585Session

delete user 247terminate 248

Short dumpSee ABAP, dump analysis 152

Single points of failure, minimizing 12, 33Single-Sign On (SSO) 162Software

R/3 System xxviiusers logging on xxvii

Software, Prerequisiteutility software installation xxvii

Spoolconsistency check 407deleting old 397in general 72, 76printing problems 67, 74, 394

Starting R/3 88Stopping R/3 90, 91, 100, 101Super users

DDIC 222SAP* 222

Supplieschecking consumable 462other considerations 464

Support Package Manager (SPAM)application server upload 581download 576, 580frontend upload 581notes 578


Support packagesapplying 643, 645downloading from SAPNet 633getting information from SAPNet 622high level application 618in general 520, 617notes

view all 625view specific 628

object conflicts 649overview 617patch

application verification 648confirmation 647log 646

regression testing 650strategy 617updating SPAM 640uploading

from CD 634from web 635front end 638in general 634

Swaps 530System xxvi, 4

assumptions xxviaudits 198backup 458change management 188confirmation information 119logs 72

display remote system logs 144in general 142, 412NT 422, 423R/3 66, 69, 88, 422

messagescreating 92, 155defining 92, 155editing 156in general 155

monitor 421monitoring tools 106multi-instance 149preventing changes 85profile parameters 79, 608R/3 definition 13single instance 148, 249

with application servers 150without application servers 151

System administration 222DDIC 222in general 105passwords 222, 223SAP* 222

System Administration Assistant (SAA) 106, 132System administrator 4System guidelines

changes, making 10, 11checklists 9database access 11documentation 8help 7in general 6networking 8non-SAP activity 12preventive maintenance 9protecting the system 7single points of failure 12

System performanceSee Performance 523, 719, 721

System, Prerequisitesoftware xxvii

T

Table maintenancedeleting entry 470in general 466review 79table entry, create 466USR40 190

Tape drive, cleaning 419Target audience xxv

customer person xxvSAP R/3 administrator xxvteam xxvthe junior consultant xxvthe system administrator xxv

Taskscheck maintenance contracts 421check uninterruptible power supply (UPS) 420cleaning tape drive 419multi-role 87

Index 743

operating system (OS) 412post-client copy 664review hardware or system monitor paging system

421scheduled 63scheduling IBM DB2 database 264scheduling Microsoft SQL database 284

Temporary Sequential (TemSe)consistency check 74, 76

Temporary Sequential (TemSe) consistency check 409TemSe 74Time

daylight savings, end 431daylight savings, start 431master clock 429zone conversion table 430

TMS 76, 487tp import all 488Training classes 684Transaction

AL02 67AL08 66, 70, 71, 91, 94, 147, 148, 149, 248, 250DB02 74, 76, 77, 78, 259, 282, 531DB12 44, 65, 260, 284, 291, 292, 459DB13 43, 44, 47, 49, 264, 266, 268, 284, 293, 305,

311, 312, 315, 317, 321, 322, 326, 328, 355,360, 459, 461

OS06 68, 71, 412OS07 531, 532OSS1 582PA30 529RZ01 70, 71, 442RZ04 445, 446, 447, 449, 452RZ10 79, 189, 608RZ11 616RZ20 65, 72, 75, 76, 106, 107, 119, 120, 143, 414,

415, 416RZ21 726SA38 83, 85, 215SCC4 83, 85, 174, 175, 655SCC5 665SCC9 662SCCL 659SE01 488SE03 83, 85, 174SE09 488, 509SE10 488, 490, 509

SE37 310SE38 83, 85, 158, 215, 216SECR 184, 196, 200SM01 83, 85, 183SM02 70, 91, 92, 155, 156SM04 66, 71, 91, 94, 147, 148, 247, 248, 249SM12 66, 72, 145, 146SM13 66, 69, 72, 81, 136, 137, 147, 190, 516SM19 206, 207SM20 74, 203, 204SM21 66, 69, 72, 88, 142, 152, 516SM22 516SM30 466, 470SM31 79, 466, 470SM33 71SM35 67, 72, 443SM36 431, 432SM37 66, 70, 79, 80, 81, 91, 92, 95, 147, 222, 439,

666SM50 65, 72, 91, 99, 147, 150, 151SM51 65, 72, 91, 99, 147, 150, 426, 519SM63 446, 454SP01 67, 72, 74, 76, 394, 395, 397, 398, 401, 517SP12 74, 409, 410SPAD 388, 407SPAM 621, 630, 633, 635, 640, 643SSAA 132ST02 67, 72, 529, 530ST03 67, 73, 525, 529, 725ST04 67, 73, 255, 278, 279, 303, 324, 329, 531ST22 67, 73, 144, 152, 153ST59 721STMS 74, 76, 495SU01 79, 81, 217, 222, 233, 234, 237, 241, 243,

244, 246SU02 82SU03 82TP 74VA01 529VA02 529VA03 529VF01 529VL01 529

Transaction logs, backup 38, 46Transactions

code switches 673code tables 674


dangerous 674in general 86, 178recommended lock table 178restricted access table 183

locked, listing 184monitoring 136performance impact 674useful 673

Transport filescleaning out old 418directory check 419

Transport Management System (TMS)documentation 487import

all requests 503selected requests 499transport request 498

in general 76main screen 495method 487, 495, 498transport log 505

Transporting objectsimporting

all requests 503buffer 488in general 508selected requests 499transport request using TMS 498

in general 486managing transports 483operating system (OS) method 487, 507problem, if occurs 494production system 486releasing requests 490, 492special transports 489, 495, 507standard process 488TMS

documentation 487main screen 495method 487, 495, 498

transport log 505, 509Troubleshooting

analyze problems 517basic techniques 516document changes 517error messages 517evaluate alternatives 517

gathering data 516in general 515making changes 517SAP patch level 518support packages 520

Tune summary 67

U

Uninterruptible power supply (UPS)check 420shutdown process 420

Unlockinglogon 243password resetting 242service connection 585transaction codes 83

Update terminatesin general 136looking for 66, 69managing 139problems with short dumps 139user training 141

Upgradehardware issues 717performance 718software issues 717when not to 715when to 716

Uploading support packagesfrom CD 634from web 635in general 634

Upstream applications 32User

assumptions xxvidatabase level xxvioperating system level xxvisystem xxvithe R/3 System level xxvi

User administration 105, 219active users 248adding users 221Central User Administratio (CUA) 162change request form 224changing jobs, users 221

Index 745

changing users 221deleting user session 247ID naming 221in general 219leaving, users 221maintaining user 79, 241new user setup 225password resetting 242policies and procedures 220terminated employees 222terminating session 248user groups 220

Users 66active 148AL08 66, 70, 71, 94check for validity 217groups

creating 246in general 220, 245recommendations 245

IDs 148, 188, 249locking 85, 243maintenance 79, 81, 241new user setup

copying an existing user 233creating new user 237in general 225, 233installing SAP GUI 226prerequisites 225

password resetting 242Single-Sign On (SSO) 162SM04 66, 70, 71, 94SU01 79super-users 222unlocking 243update terminates 141

Users,active 248

W

Web sites 692Weekly tasks

checklistsdatabase 74notes 75operating system 75

other 75R/3 system 74

Work processeschecking 65, 72defining distribution 452in general 150with application servers 150without application servers 151

Workbench organizer tools 83Workload analysis 67, 73, 525

IF A TAX COMPLIANCE SYSTEM WORKS, BUT DOESN’T WORK WITH YOUR SYSTEM, DOES IT STILL WORK?Unfortunately, not every tax compliance solution is guaranteed

to work well with your system. Vertex integrations, however,

not only work with your system, but they’re also certified by

SAP. And that provides a level of comfort and peace of mind that

others can’t. These integrations also allow you to be up and running

faster and easier. And by automating the compliance process,

you’ll save time so you can focus on more important things, such

as strategic tax planning. We can’t alleviate all your stress, but

this is definitely a start. To find out more and to receive

a free SAP Toolkit, visit www.vertexinc.com/sap.asp.

SALES AND USE TAX • PROPERTY TAX • PAYROLL TAX • TELECOMMUNICATIONS TAXwww.vertexinc.com© 2001 Vertex Inc.

10508-3 1/31/02 2:28 PM Page 1

BEST PRACTICES FOR mySAP.comHit the ground running with a prepackaged implementation and built-in competitive business expertise.

Visit us at: http://www.sap.com/bestpractices or at http://service.sap.com/bestpractices.

Easy Guidebook Ads_vert2.qxd 28.01.02 17:23 Seite 1

BETTER IMPLEMENTATIONS USE SAP MADE EASY GUIDEBOOKS!

Made Easy Guidebooks, Format: 280 x 210 mm, Anschn., 4c

©20

01 S

AP

AG

; SA

P is

a re

gist

ered

trad

emar

k of

SA

P A

G in

Ger

man

y an

d se

vera

l oth

er c

ount

ries.

Written for SAP customers and consultants, the SAP Made Easy guidebooks show a

clear, task-oriented approach to implementing your SAP solution, allowing you to cut costs

and jumpstart your implementation. Whether you are a novice or experienced user,

Made Easy guidebooks provide the step-by-step procedures and reference information

you need. Available at www.sap.com/shop.

Authorizations Made Easy SAPscript Made Easy

System Administration Made Easy Data Transfer Made Easy

R/3 Reporting Made Easy Preconfigured Client Guide

SAP BW Reporting Made Easy Online Store Made Easy

Check out www.saplabs.com/simple to learn more about the SAP Made Easy guidebooks

and other implementation accelerators.

THE BEST-RUN E-BUSINESSES RUN SAP

MadeEasyguidebooks.qxd 3/30/01 1:27 PM Page 1

$SysAdm Made Easy 46cd (entire book-2002)

Documents

Transcript of $SysAdm Made Easy 46cd (entire book-2002)