SAP System Administration Made Easy009

Chapter 23: Special Maintenance
Support Packages
5HJUHVVLRQ7HVWLQJ
Regression testing is necessary because many objects in many functional areas may be
affected by changes from a Hot Package. All functional areas must perform regression tests
to verify that a Hot Package does not create new problems as it fixes old ones. A Hot
Package is a “mini-upgrade,” especially if it is large (for example, Release 4.0B, Hot Package
10).
All existing processes should continue to function as they did before the Hot Package was
applied. A review of the notes related to a Hot Package indicates what specific tests need to
be performed by the technical and functional team. As during the implementation, the
functional teams should have a script of test procedures to test the system. This script could
also be used in the regression test.
8VHIXO6$31HW²5)URQWHQG1RWHV
SAP Note # Description
19466 Downloading a patch from SAPSERVx

33525 Important information about SAP patches < 3.1H
53902 Conflicts between Hot Packages/LCPs and Add-ons
62119 Obtaining extra large patches
73510 Problems during upgrade of patched source releases
82264 Important information about SAP patches >= 3.1H
83458 OCS Info: Downloading patches from SAPNet
84962 Info: SPAM update
85820 Patch is not displayed in patch queue
86241 HR Legal Change Patches for the HR component
87432 Contents of and applying LCPs
89089 Configuration of R/3 Systems for LCPs
97620 OCS Info: Overview of Important OCS Notes
97621 OCS Info: Online Correction Support (OCS)
97623 Patch types
97630 Known problems with patches >= 3.1H
104664 Applying patches from CD
119738 Problems during upgrade with too new Hot Packages
173814 Known problems with patches Release 4.6
System Administration Made Easy

23–39
Kernel Upgrade
.HUQHO8SJUDGH
:KDW
The kernel upgrade process is the replacing of operating system level files (the kernel files)
with updated versions of these files.
< Special notes on the kernel version:
It is now independent of the R/3 release.
The kernel is backward compatible, which means that a user could be running a
Release 3.0F with a 3.1I kernel.
If you are on a release before 3.1I, review documentation to determine which kernel
version is applicable to your release.
You must remember the R/3 release and kernel version you are running. After the kernel
is upgraded, apply kernel patches for the upgraded version of the kernel. Do not apply
kernel patches for the old version of the kernel.
When getting which patches, remember that your R/3 release stays the same, regardless of
which version your kernel changes to. On rare occasions, a SAP note instructs you to apply
a fix based on the R/3 release of the system; not the kernel version.
All servers in a system must be on the same version of the kernel.
:K\
Kernel upgrades are normally done to fix “bugs” or other problems in the kernel. Some
kernel upgrades provide enhanced functionality.
+RZ
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.

3. Obtain the new kernel from:
< SAPSERV4
This route is more current than getting the kernel via CD (see chapter 13, Retrieving
files from SAP, SAPSERV4).
< Distribution CD (if provided)
Release 4.6A/B
23–40
Kernel Upgrade
< The kernel files are:

dw1_nnn.CAR
dw2_nnn.CAR
In this filename, nnn is the patch level (for example, dw1_114.CAR.)
4. Unpack the kernel files (see chapter 13, Retrieving files from SAP, SAPSERV4 for the
unpacking procedure).
5. Back up the system at the database and operating system levels.
6. Stop the R/3 System.
7. Stop the SAP services that are using the kernel files (NT).
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 the event that you
need to restore back to the old version if a problem occurs with the new version.
9. Copy the new kernel files into the kernel directory
This 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.
5HVWDUW2SWLRQ
1. Restart the SAP services that are using the kernel files (NT).
2. Start the R/3 System
3. Check the R/3 logs.
4. Monitor the system and system logs for problems.
5HVWDUW2SWLRQ
1. Restart the server.
2. Check all logs for:
< Operating system
< Database
3. Start the R/3 System
4. Check the R/3 logs
5. Monitor the system and system log for problems.

23–41
Client Copy
&OLHQW&RS\
:KDW
The client copy function copies client-dependent customizing and data. Client copy allows
the copy or transport of the complete customizing environment from a source client to a
target client within the same system (instance) or to another system.
Tables are selected based on their delivery class.
Client copy is not meant to copy client-independent objects, such as ABAP programs 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 not copied to the target system. Thus, the data in
the additional field is not copied.
6SHFLDO1RWHV
Read the current online documentation on client copy. The client copy programs and
functionality improve and change significantly with each new release.
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.
7. Click the node (+) next to Client Copy and you will see the following list 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 Request within the Same System
< Deleting Clients
< Displaying Copy Logs
Release 4.6A/B
23–42
Client Copy
< Restarting Client Copy

< Error Handling
You cannot separate “master” data from “transaction” data.
The developer of client copy maintains several informational SAP notes. Do a SAP note
search on component BC-CTS-CCO and search for notes beginning with CC*.
8VHIXO6$31RWHV
SAP Note # Description
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
69556 CC-TOPIC: Missing tables and data
70643 CC-TOPIC: Delete client
84504 CC-TOPIC: SM29 transfers data in spite of Cancel
3URFHVVLQJ1RWHV
During the copy process, do not work in the source client or the target client. The target
client is locked for all users except SAP* and DDIC.
Since large volumes of data are involved, copying a client could take several hours. If you
are copying a large productive client, the copy time could take upwards of a day. For client
copy of a large client, see SAP note 67205. Due to the long run time, the probability of an
abnormal termination due to external factors is high.
A client copy produces a large amount of log activity. If this directory runs out of space,
the database will stop. Turn off logging (i.e., truncate on checkpoint) or monitor the
filespace in the directory where the log file(s) is located.

23–43
Client Copy
6HFXULW\
To perform a client copy, the user ID of the person doing the copy must have the same authorizations in
the source client and in the target client. A system administrator with the same authorizations as user SAP*
will have all the required authorizations.
&UHDWLQJD&OLHQW
*XLGHG7RXU

1. In the Command field, enter transaction SCC4 and choose Enter

(or from the SAP standard menu, choose Tools → Administration, then Administration → Client admin →
Client maintenance).
2. Choose .
3. Choose .
Release 4.6A/B
23–44
Client Copy
4. Choose New entries.
5. In Client, enter the client number

(for example, 100) and name (for 13
example, test client for
docu).
7
Do not use clients: 000,001, or 8
066. These clients are reserved for
SAP. 9
6. In City, enter the city name (for

example, Palo Alto).
7. In Std. Currency, enter the
standard currency for the client 10
(for example, USD).
8. In Client role, choose to select the
role for the client.
11
9. Under Changes and transports for
client-dependent objects, select the
appropriate option.
12
In this case we selected Automatic
recording of changes.
10. Under Client-independent object
changes, choose and select the
appropriate option.
In this screen, we selected Changes
to Repository and client-ind.

23–45
Client Copy
Customizing allowed.
11. Under Protection: Client copier and
comparison tool, choose and select
the appropriate entry.
In this screen, we selected
Protection level 0: No restriction.
12. Under Restrictions, if CATTs are
allowed to be executed, select
Allows CATT processes to be started.
13. Choose Save.
14. The new client is listed.
In later steps, this new client may
be referred to as the “target
client.”
14
15. To log on to the “new client,” enter SAP* for the user and PASS for the password.
SAP* with the default password PASS is a known user ID password. Do not leave the
client in this condition for longer than absolutely needed. Once the client copy is
complete, verify that the passwords for all system user IDs in the new client are secure.
Release 4.6A/B
23–46
Client Copy
&RS\LQJD&OLHQW
*XLGHG7RXU

&RS\LQJRQWKH6DPH6\VWHP6,'
To copy a client on the same system/<sid>, do a “local client copy.”
1. To log on to the “target client,” enter sap* for the user ID and pass for the password.
Be sure you are logged on to the correct target client. If you are on the wrong client, you
will destroy that client.
2. In the Command field, enter transaction SCCL and choose Enter

(or from the SAP standard menu, choose Tools → Administration, then Administration → Client admin →
Client copy → Local copy).
3. In Selected profile, choose to

select a copy profile that matches
your requirements.
4. In Source client, enter the source
client number (for example, 001). 6
5. If your user masters will be copied 3

from a specific client, in the Source 4
client user masters field, enter this 5
client number (for example, 001).
6. Choose Schedule as background job.
You will be taken to the

background scheduling screen to
complete the task.
7. In Background server, choose to

select the server on which to run
the client copy.

23–47
Client Copy
8. Select the server to run the client

copy on.
9. Choose . 8
10. Choose Schedule job.
10
11. Choose Continue.
11
Release 4.6A/B
23–48
Client Copy
At this point, the scheduling

proceeds as in scheduling any
other background job.
12
12. To begin the copy immediately,
select Immediate.
13. Choose Check.
14. Choose Save.
13 14
15. In Output device, enter the printer

name (for example, dcba). 15
16. Choose .
16

23–49
Client Copy
17. Choose .
17
18. The displayed message indicates

the job was successfully 18
scheduled.
19. Choose .
19
&RS\LQJWRD'LIIHUHQW6\VWHP6,'
To copy a client to a different system/<sid>, do a “remote client copy.”
3UHUHTXLVLWH
In the target system, the:

< Source system needs to be set up in transaction SM59.
< Client must have been created.
Copying from one system to another using remote client copy uses the RFC interface,
therefore, there is no intermediate storage on disk.
*XLGHG7RXU

1. Log in to the target system and client.
Be sure you are logged in to the correct target client. If you are on the wrong client, you
will destroy that client.

(or from the SAP standard menu, choose Tools → Administration → Administration → Client admin →
Client copy → Remote copy).
Release 4.6A/B
23–50
Client Copy
3. In Selected profile, choose to

select a profile that matches your
requirements.
4. In Source destinat., use for a list

of available RFC destinations, and 3
choose the source system.
5. Verify the source System name and 4
Source client. 5

select a background server.
7
8. Choose Continue.

23–51
Client Copy
9. From this point, schedule the job

as you would any other
background job.
10. When you have finished

scheduling the client copy, this
message window will appear.
3RVW&OLHQW&RS\7DVNV
< Secure the passwords for SAP* and DDIC in the new client.
If you copied the user master, the user IDs and passwords for those users have been
copied from the source client. When you create a new client, immediately change the
default passwords for user SAP*. The default password is well known and has been
posted on the Internet.
< Always have at least two administrative user IDs for each client, so you do not lock
yourself out of the client.
SAP* and DDIC should only be used for tasks that require those user IDs be used. A
better solution is to create an administrative user ID, which is a copy of the user SAP*.
'HOHWLQJD&OLHQW
To delete a client, there are two options:
< The Delete Client transaction, SCC5.
< The R3TRANS program (see SAP note 13391).
We recommend that you use SCC5 to delete the client.
Release 4.6A/B
23–52
Client Copy
Before deleting a client, in the event of a major problem (for example, deleting the wrong
client), make certain you have a usable backup of the system.
'HOHWH&OLHQW7UDQVDFWLRQ
*XLGHG7RXU

1. Log on to the client that will be deleted.
Be sure you are logged in to the client you want to delete. If you are on the wrong client,
you will destroy that client.

(or from the SAP standard menu, choose Tools → Administration→ Administration → Client admin →
Special functions → Delete client).
3. Verify the Client to be deleted (for
example, 500).
The Client to be deleted field is a
“nonchangeable” field and is the
5
client onto which you log. If the
client number is incorrect, you are 3
logged onto the wrong client. 4
4. Select Delete entry from T000.

5. Choose Background.

select the server to run the delete
job.
7

23–53
Client Copy
8. Select Continue.
From this point, the process is the
same as scheduling a background
job.
5HYLHZLQJWKH&OLHQW&RS\/RJ
1. Log on to another client.
2
2. In the Command field, enter
transaction SM37 and choose Enter.
4
3. In User name, enter the user ID that
the client copy job was run under 3
(for example, garyn).
4. Choose Execute.
Release 4.6A/B
23–54
Client Copy
5. Select the client copy entry.

6. Choose Job log.
Review the log.
7. At the bottom of the log is the

message that the job has successfully
finished.

23–55
Production Refresh Strategies
3URGXFWLRQ5HIUHVK6WUDWHJLHV
Because data in the target system is being replaced, refreshing a system is an inherently
dangerous.
:KDW
Production refresh is where the other systems are refreshed with data from the production
system.
After the copy, actual production data exists in the test system. This data poses data
security issues which must be addressed by the various data owners. It is more critical if
the HR system is installed, because personnel records are sensitive. Financial, sales, and
other data may also be company sensitive.
:K\
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 the production system.
Over time, the configuration of the various systems could drift apart and not match the
production system.
< Prepare for an upgrade.
You want the test system to mirror the production system, so that the upgrade in the test
system mirrors everything you will encounter into in the production system.
:K\1RW
In the recent past, the standard procedure was to create your own test data. One major
reason was that disk storage space was expensive. Here are some are reasons for not to
refresh the system:
< Data storage is expensive
Even with cheaper disks, the volume of data more than makes up any savings.
With several copies of the entire production database, the total of all the databases
could approach a hundred gigabytes for a small company to a terabyte (or more) for
a large company.
< Data security
Data from the production system is “real.”
Even if it is old, it could be confidential and sensitive. The development and test
systems are, then, subject to the same high level of security as the production system.
Created test data is “fake” and everyone knows that.
There is much less issue with data confidentiality or sensitivity.
Release 4.6A/B
23–56
+RZ
There are two ways to refresh a system:

< Database copy of the production system
< Client copy of the production client
'DWDEDVH&RS\RI3URGXFWLRQ6\VWHP
A database copy is done by copying the entire production database.
%HQHILWV
< The “refreshed” system will be a duplicate of the production system.
Client-independent changes will also be captured and copied to the target system.
< The copy can be made using standard backup tapes, so there is no impact on the
production system.
Making a copy also tests your backup and restore process.
'LVDGYDQWDJHV
< 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 the client structure
of the PRD system.
If the PRD system has one client and the QAS system has three clients, after the database
copy, the QAS system will have one client. The other two clients are lost.
&OLHQW&RS\RIWKH3URGXFWLRQ6\VWHPZLWK'DWD
A client copy is done by performing a client copy of the active client from the PRD system
(instead of copying the entire database, like a database copy).
$GYDQWDJHV
< Unlike a database copy, the target system does not have to be reconfigured.
< The target system does not lose its client configuration.
'LVDGYDQWDJHV
< A client copy requires that the source and target systems are not in use during the copy.
Having both systems out of use may not be a practical action for many companies
because the amount of time required to do the copy could be significantly greater than
the amount of time that the production system can be “down.”
< If there are any client-independent objects (programs, table structures, etc.) that have
been changed and are not the same in the two systems, these objects will not be copied
(refer to the sections on Client Copy below).

23–57
&OLHQW&RS\RIWKH3URGXFWLRQ6\VWHP²:LWKRXW'DWD
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
$GYDQWDJHV
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 specific items.
Real data may (or may not) have the appropriate data to test specific test items.
In this case, test data has to be created anyway.
'LVDGYDQWDJHV
These are the same as for a client copy with data above.
Release 4.6A/B
23–58
$SSHQGL[$8VHIXO7UDQVDFWLRQV
&RQWHQWV
Useful Transactions............................................................................................... A–2
System Administration Made Easy A–1

Appendix A: Useful Transactions
Useful Transactions
8VHIXO7UDQVDFWLRQV
System administrators may find the following transactions useful. Although many of the
transactions are not discussed in this guidebook, we are listing them for your convenience.
Many of these transactions are for more “advanced” functions than targeted in the scope of
this guidebook.
7UDQVDFWLRQ&RGH6ZLWFKHV
/n<trans code> /nspad Exit the current transaction and
start the new transaction
/o<trans code> /ospad Open a new session (window) and
start the new transaction
7UDQVDFWLRQ&RGH7DEOH
The following are definitions of two of the column headers.
< Dangerous
These transactions are potentially damaging or fatal to the system if executed
incorrectly.
As a general rule, most of the Basis transactions are potentially damaging. Access to
these transactions should be restricted in all systems. Access to some of these
transactions should be even further restricted in the production system.
< Performance Impact

These transactions could have a potentially adverse impact to system performance if
executed. Traces and table display are the transactions of concern here.
The problem with a table display occurs when the query does a “full table scan” for data.
When done on a large table, this query has serious impact on performance because the
system searches every record in the table to find those that meet the search criteria.
Release 4.6A/B
A–2
Useful Transactions
Transaction Description Dangerous Performance

impact
AL02 Database Alert Monitor

(not supported for MS SQL Svr 7.0)
AL03 Operating System Alert Monitor
AL05 Workload Alert Monitor
AL08 Current active users (in system)
AL11 Display operating system file from CCMS
AL12 Display table buffer (buffer synchronization)
BALE ALE administration and monitoring
DB01 Exclusive waits in Oracle database
DB02 Database performance; tables and index
DB03 Parameter changes in database
DB05 Analysis of table with respect to indexed fields
DB12 Backup logs
DB13 DBA planning calendar
DB14 DBA logs
DB20 Generate table statistics
OSS1 Online Service System logon
RZ01 Graphical background job scheduling monitor
RZ02 Network graphical display of instance
RZ03 Server status, alerts, maintain operations mode
RZ04 Maintain operations mode and instance
RZ06 Maintain alert threshold
RZ08 CCMS Alert Monitor
RZ10 Maintain system profiles X
RZ11 Display profile parameter attributes
RZ20 Alert Monitor 4.0
RZ21 Maintain settings for Alert Monitor 4.0
SA38 ABAP reporting
SCAM CATT management

A–3
Useful Transactions

impact
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 – post processing
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 Dictionary tables 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 holiday calendar
SFT3 Maintain factory calendar
SICK Installation check
Release 4.6A/B
A–4
Useful Transactions

impact
SM01 Lock transactions X

SM02 System messages
SM04 Overview of users
SM12 Database locks X
SM13 Update terminates X
SM18 Security Audit: Delete Old Audit Logs
SM19 Security Audit: Administer Audit Profile (for
SM20)
SM20 System (Security) Audit Log
SM21 System log
SM30 Maintain tables (not all tables can use SM30) X
SM31 Maintain tables X
SM35 Batch input monitoring
SM36 Schedule background jobs
SM37 Overview of background jobs
SM39 Job analysis
SM49 External operating system commands, execute
(see related SM69)
SM50 Work process overview
SM51 Instance overview
SM56 Reset or check number range buffer X
SM58 Error log for asynchronous RFC
SM59 RFC connection, maintain
SM63 Operations mode, maintain
SM64 Event trigger
SM65 Background processing analysis tool
SM66 Global work process overview
SM69 External operating system commands, maintain
(see related SM49)
SMLG Maintain logon groups

A–5
Useful Transactions

impact
SMX Display own jobs

SNRO Maintain number range objects X
SP00 Spool
SP01 Spool control
SP02 Display output requests
SP11 TemSe (temporary sequential objects) contents
SP12 TemSe administration
SPAD Spool administration (printer setup)
SPAM SAP Patch Manager
SPAU Intersection SAP transport/customer
modifications
SPCC Spool; consistency check
SPDD Intersection SAP transport/customer
modifications, DDIC
SPIC Spool; installation check
ST01 SAP system trace X
ST02 Buffer statistics
ST03 Workload analysis
ST04 Database performance analysis
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 business
document volume
ST22 ABAP dump analysis
Release 4.6A/B
A–6
Useful Transactions

impact
ST4A Oracle: analyze the shared cursor cache

STAT Local transaction statistics
STMS Transport Management System X
STUN Performance monitoring menu
STZAC Customizing Time Zones
SU01 User maintenance X
SU01D Display users
SU02 Maintain authorization profiles 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 in transactions
SU3 Maintain own user parameters
SU53 Display authorization checked values
TU02 Parameter changes – display active parameters
and history of changes

A–7
Useful Transactions
Release 4.6A/B
A–8
$SSHQGL[%8VHIXO5HVRXUFHVDQG3URGXFWV
&RQWHQWV
Other System Administration Resources............................................................ B–2

Other Helpful Products: Contributed by Users................................................. B–13
System Administration Made Easy B–1

Appendix B: Useful Resources and Products
Other System Administration Resources
2WKHU6\VWHP$GPLQLVWUDWLRQ5HVRXUFHV
The references cited by no means represent an all inclusive listing of resources because SAP
training classes, guidebooks, white papers, and internet sites are constantly being created
and updated.
6$35HVRXUFHV
SAP books and CDs can be ordered from the SAP online store (http://shop.sap.com) or for
items with an SAP part number, from your SAP account executive. Books with ISBN
numbers can be ordered from Fatbrain (www.fatbrain.com/sap), Amazon (www.amazon.com)
or Barnes & Noble (www.bn.com).
Release 4.6A/B
B–2
%RRNV
Title SAP Part Number ISBN Number
Complementary Software Program 50-018-672

Directory
R/3 System Getting Started 50-018-896

SAP Dictionary R/2 System Release 5000-5296
5.0: English–German
SAP Wörterbuch System R/2 Release 5000-5295
5.0: Deutsch–English
(SAP Dictionary R/2 System Release
5.0: German–English)
Authorizations Made Easy 1-893570-21-5 (3.1G/H)
500-23994 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) 500-32525 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) 500-22337 1-893570-12-6 (3.1H)
SAPscript Made Easy (4.x) 500-32527 1-893570-13-4 (4.0B)
ISBN: 1-893570-14-2 (4.6B)
Reporting Made Easy (4.0B) (3-vol set) 500-32445 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)
500-32525 1-893570-42-8 (4.0B)
1-893570-43-6 (4.6A/B)

B–3
&'V
< Accelerated SAP (ASAP)
While ASAP is an implementation project management methodology, production
system administration information is available on this CD.
< Knowledge Products
Knowledge products must be registered and a license installed (similar to saplicense),
before they can be used.
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 SQL server 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
< Computer Based Training (CBT)
Archiving CBT 500-20297
< R/3 Online Documentation
< Report Navigator (pre-Release 4.0)
See SAP Simplification Group’s web site, www.saplabs.com/simple
7UDLQLQJ&ODVVHV
In the U.S., call central registration at (888)-777-1SAP(1727) or visit SAP America’s training
web site, www.sap.com/usa/trainsupp for the most current class list.
/HYHO
SAP50 – R/3 Basis Technology
/HYHO²7HFKQLFDO&RUH&RPSHWHQFH
< BC310 – Windows NT/Oracle
< BC314 – Windows NT/MS SQL Server
< BC317 – Windows NT/DB2
< BC360 – UNIX/Oracle
< BC361 – UNIX/Informix
Release 4.6A/B
B–4
< BC370 – AS/400-DB2/400

/HYHO
BC340 – Going Live
/HYHO²$GYDQFHG
< BC305 – Advanced R/3 System Management
< BC325 – Software Logistics
< BC315 – R/3 Workload Analysis
< BC505 – Database Administration - Oracle
< BC511 – Database Administration – Informix
< BC520 – Database Administration – MS SQL Server
< BC525 – Database Administration – DB2/400
/HYHO²&URVV$SSOLFDWLRQ
< BC601 – Build and Use SAP Business Workflow
< BC615 – Archiving Technology
< BC630 – SAP Business Communication
< CA940 – SAP R/3 Security Concepts
2WKHU
< R/3 Security Guide; see SAP note 39267
www.sapnet.sap.com/securityguide
:KLWHSDSHUV
< System Landscape
“The R/3 System Landscape, System and Client Deployment Strategy” can be
downloaded from www.saplabs.com/simple.
6$31HW6HOHFWHG,WHPVRI,QWHUHVW
“Explore” SAPNet at www.sapnet.sap.com, to see what is available. The amount of
information that is obtainable is extensive and is growing.
We selected a few items that we think would be of particular interest to you in the
abbreviated tree structure that follows. Please be aware that SAPNet will change over time
and the specific path to an item may change.
1HZV (YHQWV
< Press Release
< SAP INFO magazine
< Events (SAPPHIRE, TechEd, etc.)
< Media Library
SAP Knowledge Store
Media by Type
R/3 Online Documentation

B–5
R/3 Documentation Info Center for Customers & Partners
6HUYLFHV
< Consulting Services
Individual Consulting Services, such as remote consulting, going live check, going live
functional upgrade, EarlyWatch, remote upgrade, conversion services, OS/DB
migration service, remote Euro conversion service, and remote archiving
< Education Services
Advanced Training Solution
SAP Standard Training
R/3 Knowledge Products
Computer Based Training
SAP TechNet, including software logistics, system management, system monitoring,
technical SD/CO/PP, DB Admin Oracle/Informix/MS SQL Server, ABAP
Development Workbench, data archiving, etc.
< SAP Team SAP Support Services
Release Information
• Release strategy
• Release notes
SAP Methodology & Tools
• ASAP
• Ready to Run R/3
• Sizing
• Interface Advisor
• Outsourcing
• Legacy System Migration Workbench
< Online Services
Installation/Upgrades
• License keys
• Installation/Upgrade guides
• Sizing
Customer data
• User Administration
Modifications
• SSCR (SAP Software Change Registration)
• Object registration
• Developer registration
SAP Online Correction Support
• Download
• SPAM
Release 4.6A/B
B–6
• R/3 Support Packages

< Customers & Partners
SAP Users Groups
Partners
7KLUG3DUW\5HVRXUFHV
The following list of books is not all inclusive. There are good books that are not listed here.
Also, no one book will provide you with all the information you need. You will typically
need several books in each category in your library.
A listing of these books does not constitute an endorsement by SAP. This listing is provided,
as a starting point, for your convenience. We recommend you check with your vendors
(hardware, operating system, database, and other) and the various book sources (both
online and in stores) and for additional titles.
%RRNV
5
%\6$3
Brand, Hartwig. 1999. SAP R/3 Implementation with ASAP, The Official SAP Guide. 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, A Client/Server
Technology. Addison-Wesley. (ISBN: 0-201-40350-1)
McFarland, Sue and Susanne Roehrs. 1999. SAP R/3 Software Logistics, The Official SAP Guide.
Sybex. (Release 4.0/4.5) (ISBN: 0-7821-2564-6)
Schneider, Thomas. 1999. SAP R/3 Performance Optimization: The Official SAP Guide. 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)
7KLUG3DUW\$XWKRUV
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, and UNIX)
(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)

B–7
Will, Liane; Christiane Hienger, Frank Strassenburg, and Rocco Himmer. 1998. SAP R/3
Administration Addison-Wesley. (Release 3.x) (ISBN: 0-201-92469-2)
81,;
Arick, Martin. 1995. Unix for DOS Users. John Wiley & Sons. (ISBN: 0471049883)
Frisch, Æleen. 1998. Essential Systems Administration: Help for Unix System Administrators.
O’Reilly. (ISBN: 1-56592-127-5)
Nemeth, Evi., [et al.]. 1995. Unix System Administration Handbook. Prentice Hall.
(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)
17
Enck, John (Editor). 1998. Windows NT Magazine, Administrator’s Survival Guide, 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, etal (PW Coopers). 1999. Microsoft Windows NT4.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 NT Backup & 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. Microsoft Windows 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: for Windows NT
Server Verison 4.0. Microsoft Press. (ISBN: 1-57231-3447)
 1997. Microsoft Windows NT Server Resource Kit Verison 4.0, Supplement Two. Microsoft
Press. (ISBN: 1-57231-6268)
 1994. Windows NT 3.5 Guidelines for Security, Audit, and Control. Microsoft Press.
(ISBN: 1-55615-814-9)
Minasi, Mark. 1997. Mastering Windows NT Server 4, 5th Edition. Sybex. (ISBN 0-7821-2163-2)
Release 4.6A/B
B–8
Pearce, Eric; Robert Denn (Editor), and Beverly Scherf. 1997. Windows NT in a Nutshell: A
Desktop Quick Reference for Systems Administrators. O’Reilly. (ISBN: 1-56592-251-4)
Rutstein, Charles. 1997. Windows NT security: A Practical Guide to Securing Windows NT
Servers and Workstations , McGraw-Hill (ISBN: 0-07-057833-8)
Siyan, Karanjit. 1997. Windows NT Server 4: Professional Reference. New Riders Publishing.
(ISBN: 1-56205-805-3)
Sutton, Stephen. 1997. Windows NT Security Guide. Addison-Wesley. (ISBN: 0-201-41969-6)

26
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 and Recovery. IBM.
(ISBN: 0-73840-038-6) (part# : SG24-2161-00)
0LFURVRIW64/6HUYHU
Baird, Sean; Chris Miller, and Michael Hotek. 1998. SQL Server System Administration.
Macmillan. (ISBN: 1-562059556)
Dalton, Patrick. 1997. SQL Black Book (v6.5). Coriolis Group Books. (ISBN: 1-57610-149-5)
Microsoft Corporation. 1998. Microsoft SQL Server 7.0 System Administration Training Kit.
Microsoft Press. (ISBN: 1572318279)
Prathak, Paritosh. 1998. Administering SQL Server 7. Osborne McGraw-Hill.
(ISBN: 0-07-134168-4)
Rankins, Ray., [et al.]. 1998. SQL server 6.5 unleashed (3rd edition). Sams. (ISBN: 0-672-31190-9)
Soukoup, Ron; Kalen Delaney. 1999. Inside Microsoft SQL Server 7.0. Microsoft Press.
(ISBN 0-735605173)
Spenik, Mark; and Orryn Sledge. 1998. Microsoft SQL Server 7 DBA Survival Guide. Sams.
(ISBN: 0-672-31226-3)
 1996. Microsoft SQL Server 6.5 DBA Survival Guide. Sams. (ISBN: 0-672-30959-9)
Talmage, Ron. 1999. Microsoft SQL Server 7 Administrator’s Guide. Prima. (ISBN: 0-7615-1389-2)
,QIRUPL[
Doe, Charleton. 1997. Informix OnLine Dynamic Server Handbook, 1/e. Prentice Hall.
(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 Robert Donat. 1997.
Informix Unleashed. Sams. (ISBN: 0-672-30650-6)

B–9
'%
Bullock, Diane; Jonathan Cook; et al. 1999. DB2 Universal Database and SAP R/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)
2UDFOH
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 Advanced Tuning &
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)
2WKHU7RSLFV
< Disaster Recovery
Corrigan, Patrick. 1994. LAN: Disaster Prevention and Recovery. Prentice Hall.
(ISBN: 0-13-015819-4)
Rothstein, Philip. 1995. Disaster Recovery Testing: Exercising Your Contingency Plan.
Rothstein Associates. (ISBN: 0-964164809)
Schreider, Tari. 1998. Encyclopedia of Disaster Recovery, Security & Risk Management.
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 on Win32
Systems. O’Reilly. (ISBN: 1-56592-324-3)
Srinivasan, Sriram. 1997. Advanced Perl Programming. O’Reilly. (ISBN: 1-56592-220-4)
Release 4.6A/B
B–10
Vromans, John. 1996. Perl 5 Desktop Reference. O’Reilly. (ISBN: 1-56592-187-9)

Wall, Larry; Tom Christansen, and Randal Schwartz. 1996. Programming Perl, 2nd
edition. O’Reilly. (ISBN: 1-56592-149-6)
0DJD]LQHV
SAP Info: The Magazine of the SAP Group, www.press@sap-ag.de
SAP Technical Journal, www.saptechjournal.com
+HOSIXO7KLUG3DUW\,QIRUPDWLRQ
6$36HUYLFH&RQQHFWLRQ
SAP service connection to SAP (rcPack):
HS Network Technologies
950 Tower Lane, 12th floor
Foster City, CA 94404 USA
Tel.: (650)-286-3018, FAX: (650)-287-3372
%XVLQHVV&RQWLQXDWLRQ
< 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
2UJDQL]DWLRQV
< Americas’ SAP Users’ Group (ASUG), www.asug.com
For customers in the Americas, ASUG is the only vehicle to submit requests for
upgrades and enhancement to SAP.
:HE6LWHV
6$3
< SAP, www.sap.com
< mySAP.com, www.mySAP.com
< SAPNet, www.sapnet.sap.com
Note: 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, www.saplabs.com/simple
< SAP Online Store, www.sap.com/store_index.htm
< SAP Complementary Software Program, www.sap.com/CSP

B–11
6$3$IILOLDWHG
Americas’ SAP Users’ Group (ASUG), www.asug.com
7KLUG3DUW\
< SAP Fans, www.sapfans.com
< SAP Club, www.sapclub.com
< SAP Assist, www.sapassist.com
< ERP site, www.erpsupersite.com
< ERP central, www.erpcentral.com
,QWHUQHW1HZV*URXSV
< 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.*
DB2
comp.databases.ibm-db2
Informix
comp.databases.informix
MS SQL server
microsoft.public.sqlserver.*
comp.databases.ms-sqlserver
Release 4.6A/B
B–12
Other Helpful Products: Contributed by Users
2WKHU5HVRXUFHV
2SHUDWLQJ6\VWHP
< UNIX
Digital Unix, www.unix.digital.com
HP UX, www.datacentersolutions.hp.com/2_2_index.html
IBM AIX, www.austin.ibm.com/software/aix_os.html
Siemens Reliant, www.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
'DWDEDVH
< Oracle
Oracle, www.oracle.com
< SQL server
Microsoft, www.microsoft.com/sql
< Informix
Informix, www.informix.com
< DB2
IBM, www.software.ibm.com/data/
2WKHU+HOSIXO3URGXFWV&RQWULEXWHGE\8VHUV
The products listed here have been recommended by users and consultants and 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 features and prices,
which meet different requirements. It is your responsibility to test their compatibility with
your requirements and needs, and to select the product that is appropriate to your
installation. For products which have been certified by SAP to work with R/3, see
Complementary Software Program at www.sap.com/CSP.
As a precaution, you should test all third-party software for compatibility and stability on a
test system before installing them in a production environment. There are cases where a
program many conflict with another program(s) or the hardware, and crashes the system.
Testing software applies to both the server and workstation that the system administrator
uses.

B–13
In an NT environment, if a particular task is “mission critical,” use a dedicated system to

perform that task. A dedicated system eliminates much of the potential for conflict.
81,;
%DFNXS
< Networker, Legato, www.legato.com
< OmniBack II, HP, www.hp.com/solutions/storage
0RQLWRU
< Performance monitor
Stopwatch, Envive, www.envive.com
< System monitor
OpenView, HP, www.openview.hp.com
6FKHGXOHU
< AutoSys, Platinum, www.platinum.com
< Maestro, Tivoli, www.tivoli.com
6SRRO0DQDJHPHQW
< Dazel for R/3, Dazel, www.dazel.com
2WKHU
< Messaging:
TopCall, Topcall Intl., www.topcall.com
17
%DFNXS
< ARCserve, Computer Associates, www.cai.com/arcserveit
< Backup Exec, Seagate, www.seagatesoftware.com
< OmniBack II, HP, www.openview.hp.com
< Ultraback, BEI Corp, www.ultrabac.com
0RQLWRU
< Log monitor
ELM, TNT software, www.tntsoftware.com
Provision Network Monitor (formerly AlertPage), Computer Associates
www.platinum.com/products/provis/po/nmon_pv.htm
< System monitor
LANDesk Server Manager, Intel, www.intel.com/network/products
NetIQ, NetIQ, www.netiq.com
Release 4.6A/B
B–14
OpenView ManageX, HP, www.openview.hp.com

RoboMon, Heroix, www.robomon.com
5HPRWH&RQWURO
< Compaq Carbon Copy 32, Compaq,
www.compaq.com/products/networking/software/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
6FKHGXOHU
< 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)
6SRRO0DQDJHPHQW
< Dazel for R/3, Dazel, www.dazel.com
2WKHU
< Anti-virus
See SAP note 106267 for known problems with certain anti-virus programs.
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
&RPPRQ%RWK81,;DQG17
< UPS control
Powerchute, APC, www.apcc.com
< Scripting
Perl, www.perl.com

B–15
< Time sync

Network Time Protcol, www.eecis.udel.edu/~ntp
1HWZRUN
< Network Analyser
Sniffer, Network Associates, www.nai.com
Release 4.6A/B
B–16
$SSHQGL[&8VHIXO6$31RWHV
In this chapter you will learn:

&RQWHQWV
{Enter here} Objective 1 of
this chapter is to
Overview ................................................................................................................. C–2 {Enter here} Objective 2 of
this chapter is to blah blah
R/3 Notes................................................................................................................. C–2 blah
Operating System Notes ....................................................................................... C–6 {Enter here} Objective 3 of
Database Notes ...................................................................................................... C–9 this chapter is to blah blah
blah blah
{Enter here} Objective 3 of
this chapter is to blah blah
blah
System Administration Made Easy C–1

Appendix C: Useful SAP Notes
Overview
2YHUYLHZ
The SAP notes are grouped by major area:

< R/3
< Operating System
< Database
Within each group, the notes are grouped by category. As we assembled this book, these are
the notes we found important or useful. Many more notes exist for each group, many of
which are also important. You are encouraged to explore the SAP notes to see what other
notes would be of interest or importance to you.
Over time, some of these notes may become “obsolete” and get removed.
* SAP Notes used to be known as OSS notes.
** The Online Service System (OSS) is now known as SAPNet.
51RWHV
Category SAP Note # Description
11886 Central syslog cut off

15466 Customer name range
21559 Examination of SAPgui problems
31557 The multi-client concept of R/3 – overview
42074 Using the 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 application servers
Batch 31503 FAQ: Background jobs
Batch 36280 Background work processes reserved for job class A
Batch 37104 Error analysis: Background processing system
Release 4.6A/B
C–2
R/3 Notes
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 changability 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 of cancel
Config 21636 RAM extension: Which changes to profile?
Config 31395 System parameters: Defined where? Displayed how?
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 background processes
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 and Add-Ons
Patches 63786 FAQ – Frequently Asked Questions: sapservX
Patches 63845 Corrections on SAPSERVx – searching for files
Patches 73510 Problems during upgrade of patched source release
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

C–3
R/3 Notes
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 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 hot packages
Patches 169142 Online Correction Support (OCS)
Patches 173814 OCS: Known problems with Support Packages Rel. 4.6
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 R/3 does not run?
SAPNet 26740 Online Service System registration form, North America (for
customers without existing Online Service System accounts)
SAPNet 29501 Search procedure for notes and messages in Online Service System
SAPNet 31515 Service connections
SAPNet 32411 The priority of your Online Service System message 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 Service System for
customer
SAPNet 69224 Access to the SAPNet server with Online Service System user id
SAPNet 69378 Inbox BIBO in OSS/O01
SAPNet 74313 New customer messages in Online Service System
Release 4.6A/B
C–4
R/3 Notes
SAPNet 75002 Confirmation of Online Service System registration

SAPNet 75686 Changing/Deleting Online Service System users and installations
SAPNet 80618 Access to Online Service System services via the internet
SAPNet 81908 Change to Online Service System user data
SAPNet 169296 Integrating service connections into maintain system 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 data maintenance
SAProuter 30289 SAProuter documentation
SAProuter 30374 SAProuter installation
SAProuter 87388 Download SAProuter by FTP from sapserv#
Security 23611 FAQ concerning R/3 security
Security 39267 R/3 Security Guide
Security 48018 Data security in 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) size increasing
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 R/3 does not find host name
Spool 26009 R/3 does not print, first steps
Spool 27831 Priority of output requests?
Spool 29666 Authorizations for spool requests

C–5
Operating System Notes
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 R/3
Spool 78401 Download a list from SAP spool
Start/stop 00387 Problems when starting up a DB
Start/stop 17108 Shared memory still present, startup fails
TMS/CTS 5668 Transporting report writer ojbects
TMS/CTS 11599 Reversing transports (not possible to do)
TMS/CTS 13807 Analyzing Correction & Transport System problems
2SHUDWLQJ6\VWHP1RWHV
&RPPRQWR0XOWLSOH2SHUDWLQJ6\VWHPV
80266 Installation of NT application servers in a UNIX environment

28781 Central transport directory NT/UNIX
17
28665 Central syslog under NT

89510 Installation notes for pcANYWHERE
Backup 71440 Problems when restoring DLT tapes with NTBackup
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
Release 4.6A/B
C–6
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 of 4.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 space fragmentation
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 starting R/3
Start/stop 35388 Problems on STOP/START of R/3 via NT scheduler
TMS/CTS 28781 Central transport directory NT/UNIX
TMS/CTS 62739 Configuring a central transport host
Virus 106267 Problems with certain anti-virus software

C–7
81,;
21960 Two instances/systems on one UNIX computer

28781 Central transport directory NT/UNIX
80266 Installation of NT application servers in a UNIX environment
AIX 48689 IBM service, fixes and patches
AIX 64885 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 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-UX 10.01
SUN 64887 R/3 relevant operating system patches for Solaris
SUN 71479 Solaris recommended patches
SUN 101883 R/3 relevant patches for Solaris 2.6
SUN 172524 Time stamp is incorrect
SUN 182552 Y2K patches for SOLARIS
$6
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
Release 4.6A/B
C–8
Database Notes
Performance 107104 4.0B kernel performance

Problem 125705 R/3 hangs in STARTSAP
Problem 154599 R/3 cannot be started/shmget fails
Problem 162580 Roll memory leak & SYSTEM_CORE_DUMPED
Problem 163022 Work process terminate abnormally
SAProuter 65600 SAProuter
'DWDEDVH1RWHV
0664/VHUYHU
62849 “news,” compilation of notes

This 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 R/3 4.0x/4.5x MS SQL Server
95901 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
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

C–9
Database Notes
7.0 conv 129122 Conversion SQL Server 6.5/7.0 consultant companies

7.0 conv 130689 Conversion of multiple R/3 systems from 6.5 to 7.0
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 36637 SAP database monitor for MS SQL Server 6.5
CCMS 77434 New sched. Calendar in CCMS (DB13) SQL Server 6.5
CCMS 139945 SAP database monitor for MS SQL Server 7.0
CCMS 141118 New scheduling calendar in the CCMS (DB13) SQL Server
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 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
Release 4.6A/B
C–10
Database Notes
Problems 79883 Incorrect database freespace alert displayed

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
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
'%8'%
80625 Released operating systems R/3 3.x/4.x DB2 for OS/390

85842 Released operating systems R/3 4.0x DB2/CS
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

C–11
Database Notes
Performance 107123 400: Performance improvement on the database server

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 R/3 under NT
,QIRUPL[
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 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 R/3 database
Backup 167878 Informix: Copying and renaming an R/3 database
CCMS 66322 CCMS Database administration (DB13)
Config 12825 Installation of two R/3 systems on one host
Config 41360 Database configuration via onconfig parameter
Config 141054 Informix environment parameter for 7.3x
Release 4.6A/B
C–12
Database Notes
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 Reogranization of table and dbspaces
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
2UDFOH
85838 Released operating systems R/3 4.0x Oracle

112325 End of “Cust Care Support” Oracle 7.3.*
01039 Problems with ORACLE TWO_TASK linking
01042 ORACLE TWO_TASK connect failed
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

C–13
Database Notes
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
Release 4.6A/B
C–14
Database Notes
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

C–15
Database Notes
Release 4.6A/B
C–16
$SSHQGL['8SJUDGH'LVFXVVLRQ
&RQWHQWV
Upgrade Discussion .............................................................................................. D–2

Upgrade Issues ...................................................................................................... D–3
Other Considerations ............................................................................................ D–3
System Administration Made Easy D–1

Appendix D: Upgrade Discussion
Upgrade Discussion
8SJUDGH'LVFXVVLRQ
:KDW
An upgrade is an updating of your R/3 System.
:K\
The question of whether to upgrade 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
5HDVRQV1RWWR8SJUDGH
Some reasons not to upgrade include the following:
< Cost—the following items could increase the cost of your upgrade.
You need to:
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 for them.
< Diversion of resources (Company resources that could be applied to other tasks would
be assigned to upgrading the 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.)
:KHQWR8SJUDGH
In deciding to upgrade your system, ask yourself the following questions:
< Have the reasons for upgrading and not upgrading been analyzed?
< Has the “business need” criteria been met?
< If you installed any Industry Solution (IS), are IS patches available for the new
release?
If the patches are not available, you cannot upgrade.
Release 4.6A/B
D–2
Upgrade Issues
8SJUDGH,VVXHV
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 and business 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 upgrade process.
The technical downtime is 6–12 hours. In addition, many other tasks are performed
around the backup that could increase this “downtime” significantly. System downtime
could significantly impact the operations of the business during this period.
< Upgrade changes could require changing configuration, testing, training, and
documentation.
< Changes require regression testing:
Do business processes function as they did before?
Does custom code need to be changed due to changes from the upgrade?
2WKHU&RQVLGHUDWLRQV
6RIWZDUH,VVXHV
The following software has to be compatible with the R/3 release you plan to upgrade to:
< Database
< Operating system
< Third-party applications that compliment the R/3 System (for example, external tax
packages, job schedulers, system monitors, spool managers, etc.)
+DUGZDUH
< 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 permanently used.
< As each release adds functionality, the required disk space, processing power and
memory required generally tends to increase.
A system configuration that was adequate for one release may be inadequate for a later
release. This is especially apparent when jumping release levels; example upgrading
from 3.1H to 4.6B. The following table is compiled from SAP notes:

D–3
Other Considerations
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
3HUIRUPDQFH
Upgrade performance is difficult to predict. Performance is sensitive to a variety of
variables, some of which can have significant impact. Therefore, an upgrade of the test
system should be done to determine timing values for your configuration.
The following are a few of the factors that affect the performance of an upgrade:
< 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 channel contention)
< Data volume for changes to tables that contain data
Release 4.6A/B
D–4
,QGH[
parameters, 15–16
A threshold, changing, 15–9
views, 10–5, 10–12
ABAP Annual tasks checklists
dump analysis database, 8–3
free selection, 10–49 notes, 8–4
in general, 4–15, 10–48 operating system, 8–3
performing, 4–5 other, 8–4
simple selection, 10–49 Application server, 1–14, 9–4, 16–2
dump definition, 4–15, 10–48 Audit Information System (AIS)
editor, 10–55, 10–56, 11–56 business, 11–41
execute, 8–2, 11–55 complete, 11–38
Active processes, 9–15 in general, 11–37
Active users, 10–43, 12–34 system, 11–39
Adding additional systems user defined, 11–42
in general, 12–15 Audits
SAP logon, 12–15 business, 11–41
Administrator check for validity, 11–57
access key, 20–16, 20–20, 21–23, 21–27 complete, 11–38
guidelines. See System guidelines considerations, 11–5
requirements of, 1–4 different users, 11–53
roles financial, 11–4
external to R/3, 1–3 in general, 11–4
factors that determine, 1–2 information system. See Audit Information System
within R/3, 1–2 (AIS)
AIS. See Audit Information System (AIS) security, 11–5, 11–25
Alert monitor security logs
accessing, 10–4 filter group 1, 11–49
acknowledge alerts, 10–14 filter group 2, 11–50
adding a monitor, 10–24 in general, 11–44
alert threshold, 15–9 parameters, 11–47
alert, finding, 10–7 running, 11–46
analyze alerts, 10–13 specific reports, 11–56
checking, 4–4, 5–3, 5–4 system, 11–39
create new monitor set, 10–23 tasks, 11–57
hiding SAP standard monitor sets, 10–19 tools, 11–37
in general, 4–11, 10–2 user defined, 11–42
maintaining thresholds, 10–17 user security jobs, 11–54
views, 10–5, 10–12
Alerts B
acknowledge, 10–14
analyze, 10–13 Background jobs
database, 4–6 batch, 16–3
finding, 10–7 creating, 16–8
maintaining thresholds, 10–17 housekeeing, 16–4
messages, 15–15 incorrect, 16–20
operating system, 4–6 new, 16–20

I–1
Index
others, 16–5 tracking and documenting tapes, 3–13, 3–15

performance, 16–4 transaction logs, 3–5, 3–12
performance factors, 16–5 types, 3–6
regularly scheduled jobs, 16–4 UNIX level, 16–40
scheduling, 16–8 verify, 4–9
select, 4–4, 4–8, 4–11, 7–2, 7–5, 16–15 Batch input, 4–5, 4–13, 16–20
user ID, 16–4 Batch jobs, 9–11, 10–10, 16–3, 16–5, 16–20, 16–21
Backup Books, B–3, B–7
archive procedures and policies, 3–13 Buffers
checking, 16–38 definition, 19–8
checklist, strategy, 3–12 hit ratio, 19–9
database, 3–3, 3–12, 13–15, 13–19, 16–36, 16–38 importing, 17–18
dedicated drives, 3–23 performance, 4–14, 19–8
design strategy, 3–9 special transport, adding into import buffer, 17–25, 17–
differential, 3–7 34
frequency, 3–3 swaps, 19–9
full, 3–7, 16–36 tune summary, 4–5, 4–14, 19–8
in general, 3–1, 3–3, 16–36 Business requirements, disaster recovery. See
incremental, 3–7
Disaster recovery, business requirements
initalizing tapes, 13–18
NTBackup, 16–40, 16–41
offline, 3–8, 13–24, 16–36 C
on-demand, 3–9
CAR files, 22–13
online, 3–8, 13–19
operating system level, 3–6, 3–12, 16–40
Cascade failures, minimizing, 2–19
performance CCMS alert monitor. See Alert monitor
database restore options, 3–23 Central instance, 9–3
factors affecting, 3–20 Change control
faster devices, 3–21 in general, 17–9
in general, 3–20 managing transports, 17–12
options, 3–21 Checklists
parallel backup, 3–22 annual tasks
recovery, 3–23 database, 8–3
periodic archivals, 16–36 notes, 8–4
procedures operating system, 8–3
archiving, 3–10 other, 8–4
database check, 3–11 backup strategy, 3–12
in general, 3–10 daily tasks
monitoring/controlling, 3–11 database, 4–6
verifying backups, 3–10 notes, 4–7
scheduled, 3–9 operating system, 4–6
sites, 2–18 other, 4–7
storage R/3 System, 4–4, 4–8
in general, 3–18 monthly tasks
offsite, 3–18 database, 6–2
onsite, 3–19 notes, 6–5
strategy, 3–2 operating system, 6–3
supplementary, 3–10 other, 6–4
tape label, 13–13 quarterly tasks
tape management database, 7–3
handling tapes, 3–16 notes, 7–4
in general, 3–13 operating system, 7–3
labeling tapes, 3–13 other, 7–4
retention requirements, 3–17 stopping R/3, 9–5
2 Release 4.6A/B
I–2
Index
weekly tasks restricted access table, 11–21

database, 5–3 Database (DB)
notes, 5–4 administration. See Database administration (DBA)
operating system, 5–3 alert, 4–6
other, 5–3 backup, 3–3, 3–12, 13–15, 16–36
Cleaning tape drive, 15–12 checking backup, 3–11, 16–38
Client copy checklists
copy to different system/SID, 23–50 annual tasks, 8–3
copy to same system/SID, 23–47 daily tasks, 4–6
copying, 23–47 monthly tasks, 6–2
create, 23–44 quarterly tasks, 7–3
deleting a client, 23–52, 23–53 weekly tasks, 5–3
in general, 23–42 passwords, 11–36
log, 23–54 performance, 5–4, 6–5, 13–4, 19–11
post-client copy tasks, 23–52 performance analysis, 4–6, 4–15
processing notes, 23–43 performance tables, 5–2, 6–2
production system, 23–57, 23–58 server, 1–14, 9–3
SAP notes, 23–43 TemSe. See Temporary Sequential (TemSe)
security, 23–44 Database administration (DBA). See also Database
Client-dependent changes, 11–15 (DB)
Client-independent changes, 11–14, 11–15 activity, 13–4
Consumable supplies allocation, 13–7
checking, 16–42 backup tape label, 13–13
critical, 16–42 backups with Microsoft tools, 13–19
other considerations, 16–44 checking backup, 13–15
Contracts, maintenance, 15–14 deleting planning calendar entry, 13–14
Correction support, online, 20–24 error logs, 13–28
in general, 13–1
Crash kit
initializing backup tapes, 13–18
in general, 2–12
Microsoft SQL server, 13–28
inventory list, 2–13
online backup, 13–19
location, 2–13
passwords, 13–30
Critical tasks performance, 5–4, 6–5, 13–4
daily tasks, 4–9 performance monitor, 13–4
database, 16–38 scheduling, 13–9
operating system level backups, 16–40 starting the database, 13–2
verify backups, 4–9 statistics, 13–29
verify R/3 is running, 4–9 stopping the database, 13–2, 13–3
Customer messages, 20–8. See SAPNet – R/3 verify consistency, 13–29
Frontend, customer messages DB. See Database (DB)
SAPNet-Web, 20–8 DDIC, 11–26, 12–5
Defragmentation, memory, 19–10
D Deleting user session, 12–32
Daily tasks Deleting users. See Locking, users
checklists Disaster
database, 4–6 definition, 2–2
notes, 4–7 minimizing opportunities
operating system, 4–6 cascade failures, 2–19
other, 4–7 human error, 2–18
R/3 System, 4–4, 4–8 in general, 2–18
Dangerous transactions single points of failure, 2–19
in general, 8–5, 11–17 Disaster recovery
recommended lock table, 11–18 applications, up or downstream, 2–17
System Administration Made Easy 3

I–3
Index
backup sites, 2–18 Guidelines. See System guidelines

business continuation, 2–15
business requirements
defining, 2–4
H
in general, 2–4 Hardware
performance, 3–2 central processing unit, 19–15
who provides, 2–4 disk, 19–15
crash kit. See Crash kit in general, 19–15
disaster, minimizing. See Disaster, minimizing memory, 19–15
opportunities review, 15–15
downtime, 2–5 Help. See System guidelines
integration, 2–16 High availability (HA) options, 2–3
offsite, 2–7, 2–16 Hit ratio, 19–9
onsite, 2–7
Hot packages. See Support Packages
other considerations, 2–17
planning, 2–3, 2–4
Housekeeing jobs, 16–4
recovery Human error, minimizing, 2–18
groups, 2–6
process, 2–11 I
scripts, 2–11, 2–15
time, 2–6 Insider trading, 11–3
scenarios Instance
corrupt database, 2–8 definition, 1–14
hardware failure, 2–8 operation mode, 16–25
in general, 2–8
loss or destruction of server facility, 2–9 K
staffing, 2–6
testing, 2–16 Keep it short and simple (KISS), 1–7, 3–10
types, 2–7 Kernel upgrade, 23–40
when to begin, 2–5 KISS. See Keep it short and simple (KISS)
Downstream applications, 2–17
L
E LCP. See R/3 HR Support Packages
EarlyWatch session, 22–14 Legal change patches (LCP). See R/3 HR Support
External interfaces, 9–15 Packages
Lock entry list, 4–4, 4–12
F Locking
client
Failed updates. See Update terminates modifiable, 11–17
File space permanent, 11–16
old transport files, 15–11 dangerous transactions table, 11–18, 11–21
usage, 15–6 logon, 12–27
Forms prohibited password table, 11–30
Detailed Online Service System Note Record, 17–11 service connection, 21–30
General Note Record, 17–10 transaction codes, 8–3
R/3 User Change Request, 12–6 transactions, dangerous, 11–17
Sample Transport Request, 17–14 users, 7–5, 8–4, 11–29
Free space. See File space Locks
Frontend software. See SAP GUI definition, 4–12, 10–41
deleting, 10–42, 10–43
in general, 10–41, 11–11
G
Graphical job monitor, 4–8, 4–11, 16–19
4 Release 4.6A/B
I–4
Index
M in general, 11–9, 11–25

management change, 11–27
Maintenance passwords, 11–28
basic, 23–4 sharing of user IDs, 11–27
contracts, 15–14 Operations
extended, 23–4 consumable supplies, 16–42
special, 23–1 critical supplies, 16–42
table. See Table maintenance in general, 16–1
user, 7–2, 7–5, 12–24 modes
Management, change adding new, 16–26
change control, 17–9 assigning, 16–32
in general, 11–27, 17–1 assigning instance definition, 16–25
Memory define, 16–23
defragmentation, 19–10 generate instance, 16–25
hardware, 19–15 in general, 16–21
Microsoft SQL server, 13–28 other considerations, 16–44
in general, 13–1 work processes defining distribution, 16–29
online backup, 13–19 OS. See Operating system (OS)
Modes. See Operations, modes OSS notes. See SAP notes
Monthly tasks checklists Output management
database, 6–2 in general, 14–1
notes, 6–5 output printing, 14–15
operating system, 6–3 printer setup, 14–2
other, 6–4 printing screen, 14–18
Multi-role tasks checklist, stopping R/3, 9–5 spool check
mySAP, B–11 consistency, 14–21
deletion, for, 14–12
printing problems, for, 14–9
N
New user setup. See Users, new user setup P
NTBackup, 13–24
Paging system, 15–15
Passwords. See also Security, passwords
O changing, 11–34
Operating system (OS) database, 11–36
alert threshold, 15–9 database administration, 13–30
alerts, 4–6, 15–2 eliminating easy, 11–29
checklists expiration time, 7–4, 11–29
annual tasks, 8–3 in general, 11–28
daily tasks, 4–6 length, 7–4, 11–29
monthly tasks, 6–3 lockout, 7–4, 11–29
quarterly tasks, 7–3 maintaining table of prohibited, 11–30, 17–2
weekly tasks, 5–3 operating system level, 11–35
file space usage, 15–6 purpose, 7–5
full server backup, 16–36 recording, 11–31
monitor, 4–6, 4–11, 19–11 resetting, 12–26
NT event log, 15–5, 15–15, 15–16 sample tables, 11–32
old transport files, 15–11 security parameters, 7–4, 11–29
system logs, 15–3 standards, 11–29
tasks, 15–2 system administration, 12–5
transporting method, 17–34 Patch
Transporting objects, 17–16 application verification, 23–37
Operational security confirmation, 23–36
level, 18–5

I–5
Index
logs, 23–35 extended, 23–4

queue, 23–32, 23–33 Profile, definition, 23–10
Performance
background jobs, 16–4 Q
backup
database restore options, 3–23 Quarterly tasks checklists
factors affecting, 3–20 database, 7–3
faster devices, 3–21 notes, 7–4
in general, 3–20 operating system, 7–3
options, 3–21 other, 7–4
parallel backup, 3–22
recovery, 3–23 R
to disks then tapes, 3–22
buffers, 4–14, 19–8 R/3 HR Support Packages, 23–11
critical assumption, 19–2 R/3 System. See also System
database, 5–4, 6–5, 13–4, 19–11 active processes, 9–15
evaluation priority, 19–3 administration. See System administration; User
in general, 19–1, 19–3 administration
memory defragmentation, 19–10 batch jobs. See Batch jobs
R/3, 19–4 checking for users, 9–9
workload analysis, 4–14 with application servers, 9–10
Permission creep, 11–58 without application servers, 9–9
Policies checklists
backup frequency, 3–3 daily tasks, 4–4, 4–8
supplementary backups, 3–10 stopping R/3, 9–5
system adminstration, 12–5 definition, 1–14
user administration, 12–3 external interfaces, 9–15
Printer setup guidelines. See System guidelines
in general, 14–2 performance. See Performance
Procedures starting, 9–2
backup stopping, 9–5, 9–16
archiving, 3–10 R/3 system administrator. See Administrator
database check, 3–11 Recovery. See Disaster recovery
in general, 3–10 Recovery groups, 2–6
monitoring/controlling, 3–11 Recovery scripts
roles and responsibilities, 3–11 business continuation, 2–15
verifying backups, 3–10 creating, 2–11
system administration, 12–5 definition, 2–11
user administration, 12–3 Regression testing, 23–39
Production refresh strategies Remote services
client copy with data, 23–57 CAR files, 22–13
client copy without data, 23–58 downloading files, 22–9
database copy of production system, 23–57 EarlyWatch, 22–14
in general, 23–56 FTP client example, 22–4
Production system in general, 22–1
not modifiable, 11–13 SAP, retrieving files, 22–2
preventing changes, 8–4 SAPSERV4
Profile Generator, 12–2 connecting using a GUI (NT), 22–3
Profile parameters, system connecting using command prompt, 22–6
administration data, 23–4 navigating, 22–6
editing, 7–2, 7–4, 23–2 partial organization, 22–10
maintenance retrieving files, 22–2
basic, 23–4 unpacking files, 22–13
6 Release 4.6A/B
I–6
Index
Restore problem solving, 20–5

reasons for, 3–2 Support Package Manager (SPAM). See Support
strategy, 3–2 Package Manager (SPAM)
testing, 3–3 SAPSERV, 22–2
Retrieving files, 22–2 SAPSERV4, 22–2, 22–3. See also Remote services,
Return codes, transport, 17–38 SAPSERV4
Scenarios, disaster
S corrupt database, 2–8
hardware failure, 2–8
SAA. See System Administration Assistant (SAA) in general, 2–8
SAP GUI loss or destruction of server facility, 2–9
adding additional systems, 12–15 Scheduling
installing database tasks, 13–9
file server, from, 12–8 Security. See also Security administration
presentation CD, from, 12–14 access, 11–7
software, 12–8 administration. See Security administration
SAP notes, 3–24, 17–9, 20–31, 21–3, 21–31, 22–14, 23– application, 11–9
39, 23–43 audit log
SAP Patch Manager. See Support Package Manager filter group 1, 11–49
(SPAM) filter group 2, 11–50
SAP resources, B–2 in general, 11–44
SAP*, 11–26, 12–5 parameters, 11–47
review, 5–2
SAPNet, B–5
running, 11–46
SAPNet – R/3 Frontend authorization maintenance, 8–2
action log, 21–16 auto logout, 10–41
confirm, 21–21 client copy, 23–44
connecting to, 21–3 client-dependent changes, 11–15
customer messages client-independent changes, 11–14, 11–15
component, 20–10, 21–11 controlling access, 11–11
in general, 21–10 data, 11–10
problem description, 20–10, 21–11 DDIC, 11–26
finding notes, 21–6 definition, 11–2
in general, 21–1 layers, 11–6
long text, display, 21–17 multiple user logins, prevent, 11–11
message status, 21–15 network, 11–8
notes. See SAP notes NT audit function, 15–5
prerequisites, 21–2 operational, 11–25
problem researching, 21–6 operational security, 11–9
reopen, 21–18 passwords. See also Passwords
service connection, 21–30 changing, 11–34
SAPNet – R/3 Web Frontend database, 11–36
developer eliminating easy, 11–29
deletion, 20–19 expiration time, 7–4, 11–29
registration, 20–15, 20–17, 21–22 in general, 11–28
in general, 20–1 length, 7–4, 11–29
installation note searching, 20–7 lockout, 7–4, 11–29
logging on, 20–3 maintaining table of probibited, 11–30
note searching, 20–5 operating system level, 11–35
object parameters, 7–4, 11–29
deletion, 20–23 purpose, 7–5
registration, 20–15, 20–19, 21–22, 21–26 recording, 11–31
online correction support, 20–24 sample tables, 11–32
online services, 20–4 standards, 11–29

I–7
Index
permission creep, 11–58 object conflicts, 23–37

physical, 11–7 patch
production system changes, preventing, 11–11 application verification, 23–37
profile maintenance, 8–2 confirmation, 23–36
R/3, 11–11 log, 23–35
SAP*, 11–26 queue, 23–33
security reports, 11–54 regression testing, 23–39
segregation of duties, 11–25 SAPNet – R/3 Frontend (OSS), 23–22
sharing of user IDs, 10–44, 11–27, 12–34 strategy, 23–12
user audit jobs, 11–54 updating SPAM, 23–29
Security administration, 11–1. See also Security uploading
audits, 11–4 CD, from, 23–26
data protection, 11–3 in general, 23–25
insider trading, 11–3 web, from, 23–26
other requirements, 11–3 Swaps, 19–9
Server System. See also R/3 System
application, 9–4 audits, 11–39
database, 9–3 backup. See Backup
Service connection, 21–30 confirmation information, 10–15
Session logs
delete user, 12–32 in general, 4–13, 10–38, 15–3
terminate, 12–33 NT, 4–6, 15–5, 15–15, 15–16
Short dump. See ABAP, dump R/3, 4–4, 4–8, 4–15, 9–2, 15–15
Single points of failure, minimizing, 1–13, 2–19 messages
creating, 9–6, 10–52
SPAM. See Support Package Manager (SPAM)
defining, 9–6
Spool, 4–5, 4–14, 5–2, 5–4, 14–9, 14–12, 14–21 editing, 10–54
Starting R/3, 9–2 in general, 10–51
Stopping R/3, 9–5, 9–16 monitor, 15–15
Super user monitoring tools, 10–2
DDIC, 12–5 multi-instance, 10–45, 12–36
SAP*, 12–5 preventing changes, 8–4
Supplies profile parameters, 23–2. See Profile parameters,
checking consumable, 16–42 system
critical, 16–42 R/3 definition, 1–14
other considerations, 16–44 single-instance, 12–35
Support Package Manager (SPAM) System administration. See also User administration
after download, 20–31 DDIC, 12–5
download, 20–27, 20–30 in general, 10–1
notes, 20–28 passwords, 12–5
updating, 20–25 SAP*, 12–5
Support Packages System administration assistant (SAA), 10–28
adding to patch queue, 23–32 System Administration Assistant (SAA), 10–2
applying, 23–31, 23–34 System administrator. See Administrator
applying, high-level process of, 23–12 System guidelines
determining which applied, 23–13 changes, making, 1–10, 1–11
downloading checklists, 1–8
SAPNet – R/3 Frontend, from, 23–24 database access, 1–12
in general, 18–6, 23–11 help, 1–5
information, getting from SAPNet – R/3 Frontend, 23– in general, 1–4, 1–13
15 networking, 1–6
notes non-SAP activity, 1–12
view all, 23–17 preventive maintenance, 1–9
view specific, 23–21 protecting the system, 1–5
8 Release 4.6A/B
I–8
Index
recordation, 1–7 RZ01, 4–8, 4–11, 16–19

single points of failure, 1–13 RZ04, 16–22, 16–23, 16–25, 16–26, 16–29
System performance. See Performance RZ10, 7–2, 7–4, 11–29, 23–2, 23–3
RZ11, 23–10
RZ20, 4–4, 4–11, 5–3, 5–4, 10–2, 10–3, 10–4, 10–15, 10–
T 17, 10–39, 15–6, 15–7, 15–9
Table maintenance RZ21, 10–10
deleting entry, 17–6 SA38, 8–2, 8–4, 11–55, 11–56
in general, 17–2 SCC4, 8–2, 8–4, 11–13, 11–15, 23–44
review, 7–2 SCC5, 23–52
table entry, create, 17–2 SCC9, 23–50
Tape drive, cleaning, 15–12 SCCL, 23–47
Tasks SE03, 8–2, 8–4, 11–13, 11–14
annual, 8–1 SE09, 17–36
monthly, 6–1 SE10, 17–19, 17–35, 17–36
multi-role, 9–1 SE38, 8–2, 8–4, 10–55, 11–56
operating system (OS), 15–2 SECR, 11–24, 11–37, 11–38
other, 15–12 SM01, 8–3, 8–5, 11–22
post-client copy, 23–52 SM02, 4–8, 9–5, 9–6, 9–7, 10–51, 10–52, 10–54
quarterly, 7–1 SM04, 4–5, 4–11, 9–5, 9–9, 10–43, 10–44, 12–32, 12–33,
scheduling database, 13–9 12–34, 12–35
weekly, 5–1 SM12, 4–4, 4–12, 10–41, 10–42
Temporary Sequential (TemSe), consistency check, SM13, 4–4, 4–8, 4–12, 10–32, 10–34, 10–43
SM19, 11–47, 11–48
5–2, 5–5, 14–23
SM20, 5–2, 11–44, 11–46
TemSe. See Temporary Sequential (TemSe) SM21, 4–4, 4–8, 4–13, 4–15, 9–2, 10–38, 10–48
Time SM30, 17–2, 17–6
daylight savings, end, 16–8 SM31, 7–2, 17–2, 17–6
daylight savings, start, 16–7 SM35, 4–5, 4–13, 16–20
master clock, 16–6 SM36, 16–8, 16–9
zone conversion table, 16–6 SM37, 4–4, 4–8, 4–11, 7–2, 7–5, 9–5, 9–11, 10–43, 12–4,
TMS 16–15, 16–16, 23–54
documentation, 17–16 SM50, 4–4, 4–5, 4–14, 9–5, 10–43, 10–46, 10–47
import SM51, 4–4, 4–5, 4–14, 9–5, 9–15, 10–43, 10–46, 16–2, 16–
all requests, 17–30 3, 18–5
selected requests, 17–28 SM63, 16–22, 16–32
transport request, 17–27 SP01, 4–5, 4–14, 5–2, 5–4, 14–9, 14–12, 14–15
main screen, 17–24 SP12, 5–2, 5–5, 14–23, 14–24
method, 17–16, 17–24 SPAD, 14–2, 14–21, 14–22
system, 5–5 SPAM, 23–14, 23–22, 23–24, 23–27, 23–29, 23–32
tp, 17–17 SSAA, 10–28
Training classes, B–4 ST02, 4–5, 4–14, 19–8, 19–9, 19–10
Transaction ST03, 4–5, 4–14, 19–4, 19–7
AL02, 4–6 ST04, 4–6, 4–15, 13–4, 13–5, 13–28
AL08, 4–5, 4–8, 4–10, 9–5, 9–9, 9–10, 10–43, 10–45, 12– ST22, 4–5, 4–15, 10–40, 10–48, 10–49
34, 12–36 STMS, 5–2, 5–5, 17–24
AL16, 4–6, 15–2 SU01, 7–2, 7–5, 11–57, 12–4, 12–16, 12–17, 12–21, 12–24,
DB02, 5–2, 5–4, 6–2, 6–5, 13–7 12–25, 12–26, 12–27, 12–28, 12–30
DB12, 3–9, 4–3, 13–9, 13–15, 13–16, 16–38 SU02, 8–2, 11–59
DB13, 3–9, 3–12, 13–9, 13–10, 13–18, 13–29, 16–38, 16–39 SU03, 8–2, 11–59
OS06, 4–6, 4–11, 15–3 TP, 5–2
OS07, 19–11, 19–12 useful, A–2
OSS1, 21–3 VA01, 19–8
PA30, 19–8 VA02, 19–8

I–9
Index
VA03, 19–8 logon, 12–27

VF01, 19–8 password resetting, 12–26
VL01, 19–8 service connection, 21–30
Transaction logs, backup, 3–5, 3–12 transaction codes, 8–3
Transactions users, 7–5
dangerous Update terminates
in general, 8–5, 11–17 in general, 4–12, 10–32
recommended lock table, 11–18 looking for, 4–4, 4–8
restricted access table, 11–21 managing, 10–35
locked, listing, 11–24 problems with short dumps, 10–37
Transport files user training, 10–37
cleaning out old, 15–11 Uploading Support Packages
directory check, 15–11 CD, from, 23–26
Transporting objects in general, 23–25
importing web, from, 23–26
all requests, 17–30 UPS. See Uninterruptible power supply (UPS)
buffer, 17–18 Upstream applications, 2–17
in general, 17–34 User administration. See also System administration
selected requests, 17–28 active users, 12–34
transport request using TMS, 17–27 adding users, 12–3
in general, 17–15 change request form, 12–6
log, 17–32, 17–35, 17–36 changing jobs, users, 12–3
managing transports, 17–12 changing users, 12–3
operating system (OS) method, 17–16, 17–34 deleting user session, 12–32
problem, if occurs, 17–23 ID naming, 12–3
production system, 17–15 in general, 12–1
releasing requests, 17–19, 17–21 leaving, users, 12–3
special transports, 17–18, , 17–34
17–25 maintaining user, 7–2, 7–5, 12–24
standard process, 17–17 new user setup. See Users, new user setup
TMS policies and procedures, 12–3
documentation, 17–16 terminated employees, 12–4
main screen, 17–24 terminating session, 12–33
method, 17–16, 17–24 user groups. See User groups
Troubleshooting Users. See also User administration
basic techniques active, 10–43
document changes, 18–3 AL08, 4–5, 4–8, 4–10
error messages, 18–4 groups, 12–2, 12–29, 12–30
evaluate alternatives, 18–3 IDs, 10–43, 11–27
gather data, 18–2 locking, 7–5, 8–4, 12–27
in general, 18–2 maintenance, 7–2, 7–5, 12–24
making changes, 18–3 new user setup
problem, analyze, 18–3 copying an existing user, 12–16
SAP patch level, 18–5 creating new user, 12–21
Support Packages, 18–6 in general, 12–7, 12–16
in general, 18–1 installing SAP GUI. See SAP GUI, installing
Tune summary. See Buffers, tune summary prerequisites, 12–7
SM04, 4–5, 4–8, 4–11
U unlocking, 7–5, 12–27
Uninterruptible power supply (UPS) W

check, 15–13
program log, 4–7 Web sites, B–11
shutdown process, 15–13 Weekly tasks checklists
Unlocking database, 5–3
10 Release 4.6A/B
I–10
Index
notes, 5–4 in general, 4–14, 10–46

operating system, 5–3 with application servers, 10–46
other, 5–3 without application servers, 10–47
Work processes Workbench organizer tools, 8–2
checking, 4–4, 4–5 Workload analysis, 4–5, 4–14, 19–4
defining distribution, 16–29

I–11

SAP System Administration Made Easy009

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

SAP System Administration Made Easy009

Загружено:

Авторское право:

Доступные форматы

Chapter 23: Special Maintenance

19466 Downloading a patch from SAPSERVx

System Administration Made Easy

To upgrade the kernel:

2. Always first perform the upgrade on a test server.

< The kernel files are:

System Administration Made Easy

Tables are selected based on their delivery class.

To access the online help documentation on client copy:

< Restarting Client Copy

You cannot separate “master” data from “transaction” data.

7312 Create client 066 for EarlyWatch

System Administration Made Easy

1. In the Command field, enter transaction SCC4 and choose Enter

4. Choose New entries.

5. In Client, enter the client number

6. In City, enter the city name (for

System Administration Made Easy

2. In the Command field, enter transaction SCCL and choose Enter

3. In Selected profile, choose to

5. If your user masters will be copied 3

You will be taken to the

7. In Background server, choose to

System Administration Made Easy

8. Select the server to run the client

10. Choose Schedule job.

11. Choose Continue.

At this point, the scheduling

15. In Output device, enter the printer

System Administration Made Easy

18. The displayed message indicates

In the target system, the:

1. Log in to the target system and client.

2. In the Command field, enter transaction SCC9 and choose Enter

3. In Selected profile, choose to

4. In Source destinat., use for a list

6. In Background server, choose to

System Administration Made Easy

9. From this point, schedule the job

10. When you have finished

1. Log on to the client that will be deleted.

2. In the Command field, enter transaction SCC5 and choose Enter

4. Select Delete entry from T000.

6. In Background server, choose to

System Administration Made Easy

5. Select the client copy entry.

Review the log.

7. At the bottom of the log is the

System Administration Made Easy

Refreshing a system from the production system helps:

There are two ways to refresh a system:

System Administration Made Easy

Useful Transactions............................................................................................... A–2

System Administration Made Easy A–1

< Performance Impact

Transaction Description Dangerous Performance

AL02 Database Alert Monitor

System Administration Made Easy

Transaction Description Dangerous Performance

SCAT Computer Aided Test Tool

Transaction Description Dangerous Performance

SM01 Lock transactions X

System Administration Made Easy

Transaction Description Dangerous Performance

R/3 Documentation Info Center for Customers & Partners

Vromans, John. 1996. Perl 5 Desktop Reference. O’Reilly. (ISBN: 1-56592-187-9)

OpenView ManageX, HP, www.openview.hp.com