Chaper 11

System Administration Made Easy 111
Chapter 11: Nonscheduled 8pecial

Maintenance
Contents
Overview................................................................................................................112
Setting the Production System to Not Modifiable..........................................112
Using Transaction SE03 for Client-Independent Changes.....................................113
Client-Independent and Client-Dependent Changes..............................................115
Changing System Profile Parameters (Transaction RZ10) ...............................118
Hot Packages and Legal Change Patches (LCP).............................................1116
Strategy.................................................................................................................1117
High-Level Process of Applying Hot Packages ....................................................1117
Determining What Hot Packages Have Been Applied..........................................1118
Getting Information on the Hot Package from the Online Service System...........1120
Requesting SPAM or a Hot Package from the Online Service System................1128
Downloading SPAM or a Hot Package.................................................................1130
Uploading the Hot Package from a CD.................................................................1132
Updating SPAM.....................................................................................................1134
Applying the Hot Package.....................................................................................1136
Object Conflicts.....................................................................................................1142
Regression Testing ...............................................................................................1143
Useful Online Service System Notes....................................................................1143
Kernel Upgrade ...................................................................................................1144
Production Refresh Strategies ..........................................................................1146
Database Copy of Production System..................................................................1147
Client Copy of the Production System..................................................................1147
Client Copy ..........................................................................................................1148
Creating a Client ...................................................................................................1151
Copying a Client....................................................................................................1155
Post-Client Copy Tasks ........................................................................................1159
Deleting a Client....................................................................................................1160
Changing System Passwords............................................................................1163
Recording System Passwords..............................................................................1163
Operating System Level........................................................................................1166
Databases.............................................................................................................1168
Chapter 11: Nonscheduled Special Maintenance

Overview
Release 4.0B
112
Overview
Special maintenance is a category of tasks that are rarely or infrequently done. We have
chosen to include them, with limited coverage, in case you need to perform them.
Even experienced consultants sometimes lack the necessary specific knowledge and skills
required to perform certain special maintenance tasks. If you need help to do any
complicated or potentially dangerous task, then by all means get help.
In the world of system administration, there are many land mines (dangers). Stepping on
one can be painfulpossibly even fatal to your company and/or employment.
Murphy says: A wise person is cautious; a fool charges ahead.
8etting the Production 8ystem to Not Modifiable
What
There are switches that prevent changes from being made in the system. In the production
system, these should be set to Not modifiable.
The purposes of setting the production system to not modifiable is to make sure that
changes are made using the development pipeline. In the development pipeline, changes
are:
1. Made in the development system
2. Tested in the development system
3. Transported from the development system to the test system
4. Tested in the test system
5. Transported from the test system to the production system
Using this procedure, changes are properly tested and applied to the systems in the
pipeline.
Why
Objects should not be modifiable in the production system. This rule is to protect the
production system from object and configuration changes being made, without first being
tested. By setting the production system to Not modifiable, you preserve the integrity of the
pipeline.
Setting the Production System to Not Modifiable
R/3 System Administration Made Easy
113
An Exception to the Rule
There are occasions when a change cannot be transported. In such casesand only in such
casesthe following procedure should be used:
1. Verify that the change cannot be transported.
Some objects may use an ABAP to transport the object.
2. Unlock the system (that is, make it modifiable).
3. Make the change.
4. Immediately lock the system.
5. Make the same changes to all other systems.
How
There are two transactions (SE03 and SCC4) that you will use to set the system to Not
modifiable. (These transactions can also be used for other tasks).
Using Transaction 8E03 for Client-ndependent Changes
Guided Tour
1. In the Command field, enter transaction SE03 and choose Enter
(or choose Tools ABAP Workbench, then Overview Workbench organizer, and then Goto Tools.)
2. Click on the Administration node.
2
Release 4.0B
114
3. Double-click Set system change
option.
4. Choose Global setting.
5. To lock the system, select Not
modifiable.
6. To unlock the system, select
Modifiable (selected in this
example).
7. Choose OK.
4
7
6
3
5
115
Client-ndependent and Client-Dependent Changes
Guided Tour
Note: This method also locks the client-dependent changes.
1. In the Command field, enter transaction SCC4 and choose Enter
(or choose Tools Administration, then Administration Client admin Client maintenance.)
2. Choose Change.
3. Choose Continue/Enter.
4. Select the client number (for
example, 100).
5. Choose Details.
2
3
4
5
Release 4.0B
116
To Lock a Client (Not modifiable):
6. Select No changes allowed.
7. From possible entries, choose No
changes to Repository and client-
independent custom objects.
8. From possible entries choose
Protection level 2: No overwriting, no
external availability.
9. Choose Save.
To Unlock a Client (Modifiable):
6. Select Automatic recording of changes.
7. From possible entries, choose Changes
to Repository and client-ind.
customizing allowed.
8. From possible entries, choose
Protection level 0: No restriction.
9. Choose Save.
6
7
9
6
7
8
9
8
117
This screen shows available entries for
Client-independent object changes.
This screen shows available entries for
Protection: Client copier and comparison
tool.
Changing System Profile Parameters (Transaction RZ10)
Release 4.0B
118
Changing 8ystem Profile Parameters {Transaction RZ10}
What
The system profile parameters are what R/3 uses when it starts up. Parameters may define
things such as how many of each work process to create, the minimum length of the user
password, etc.
The system uses the following three parameters:
< Start
Defines which R/3 services are started.
< Default
Defines the profile for all instances in the system.
< Instance
Defines the profile for the specific instance, which allows individual application servers
to be configured differently for specific tasks and users.
Why
Changing any of these values should only be done for a specific purpose and only with
proper knowledge of what is being changed and why it is being changed.
If a parameter is incorrectly changed, R/3 may not start.
Changing system profile parameters should only be done under the instruction of the SAP
Hotline, SAP EarlyWatch, or an experienced consultant.
Before making changes to the system profiles, make certain that you have a recent, usable
copy of the system profile files. This backup is your last line of defense if a profile change
is made that results in R/3 not being able to start.
Use RZ10 to maintain your profile parameters.
Do not modify the files at the operating system level. This process could lead to
inconsistency and confusion.
119
Guided Tour
1. In the Command field, enter transaction RZ10, and choose Enter
(or choose Tools CCMS, then Configuration Profile maintenance).
2. In the Profile field, choose possible
entries.
3. Select the instance profile (for
example, RW6_DVEBMGS00_
NSPALSS1).
4. Choose Enter.
The profiles used by the system work in the following order:
1. Start profile
2. Default profile (for all instances in the system)
3. Instance profile (specific to the instance you are on)
Use the instance profile to make the parameters of a specific application server different
than the other servers for specific reasons (for example, batch application servers).
2
3
4
Release 4.0B
1110
Under Edit profiles, there are three selections, two of which are maintenance modes:
< Administration data
This selection is not a maintenance mode. It is used to change the name of the file where the profile
should be activated.
< Basic maintenance
This mode allows you to set the buffers, work processes, and directories in the system profiles. It also
allows you to specify the SAP components to be started (for example, message server, application
server, SNA gateway, etc.) in start-up profiles.
This form of maintenance protects most profile parameters from being changed by potentially incorrect
settings.
< Extended maintenance
This mode allows you to access all system profile parameters or start-up profile entries.
5. Note the Version number of the
instance profile. The last step in
this procedure shows the version
incremented.
6. Under Edit profile, select Extended
maintenance.
7. Choose Change.
8. Click on the line above which you
want the entry to be inserted (for
example, PHYS_MEMSIZE).
9. Choose Create Parameter.
5
6
8
9
7
1111
The point where you insert the new profile parameter has no effect on what is done. But
you may want to group or order the parameters to make it easier to read (for example,
group the login parameters together).
Once you enter the profile parameter, it cannot be easily moved to another location.
Therefore, be careful where you choose to insert it.
10. Click in the Parameter name field,
and choose possible entries.
11. The list that appears is a long list.
You need to page or scroll down
to find the profile parameter you
want to add.
12. Select the parameter (for example
login/min_password_lng).
13. Choose Enter.
10
12
13
Release 4.0B
1112
14. A default value appears in the
Unsubstituted standard value field.
15. Enter the new value in Parameter
val. (for example, enter 5 to
increase the minimum length to
five).
16. In Comment, document your
change by entering a description
of why the change was made.
The system attaches your user ID
and date to your comment.
17. Choose Copy.
18. This screen shows that the system
inserted your user ID and the date
and time of the change into the
Comment.
In this way, you can determine
who made a profile change, and
when this change was made.
19. Choose Back.
14
15
16
17
18
19
1113
20. This screen shows the new
parameter login/min_password_lng
with a value of 5 inserted above
PHYS_MEMSIZE.
21. Choose Copy.
22. The message at the bottom of the
screen indicates that the profile
was changed.
23. Choose Back.
24. Note the profiles version number
in the Version field.
25. Choose Save.
20
21
23
24
25
22
Release 4.0B
1114
26. Choose Yes.
27. Choose Enter.
28. Choose Enter.
If you have operation modes
configured, this screen may appear.
If you do not have operation modes
configured, this screen will not
appear. Skip to step 32.
29. Double-click on Yes.
26
27
28
29
1115
30. Review the check log.
31. Choose Enter.
32. Note that the profiles version
number has changed.
Use transaction RZ11 to get the details of a specific profile parameter.
32
31
Hot Packages and Legal Change Patches (LCP)
Release 4.0B
1116
Hot Packages and Legal Change Patches {LCP}
What
A Hot Package is a collection of corrections addressing serious errors in the ABAP
repository. These corrections affect the Basis areas and various functional areas. There are
defined rules of what kind of fixes should be (and are) included in a Hot Package. Some of
these rules are technical and others are policy.
A Hot Package is not a cumulative fix for application modules. You must still get and apply
the notes for the functional modules. However, since Hot Packages do contain patches for
the various functional areas, some of the notes may be applied within the Hot Package. The
Packages are not supposed to contain functional enhancements, but this is not always the
case.
Why
The purpose of a Hot Package is to fix problems before they arise and become a problem.
When
There is a conflict about when Hot Packages should be (and are) applied:
< SAPs position is that the customers should apply all Hot Packages as they are released
to prevent serious problems from occurring.
< The position of many customers is that all changes to the system must be regression
tested.
This stance, coupled with the frequency of Hot Package releases, results in Hot
Packages not being applied. This is because the amount of required testing cannot be
done on a continuous basis.
This customer position is not unique to SAP and has been taken by many customers
since the early days of computing.
Note: SAP development is working on methods to make the applying of Hot Package
easier for their customers.
Note: If you are using the HR module, SAP recommends that you use the HR Legal
Change Patch (HR LCP) instead of using Hot Packages. HR LCP provides the corrections
contained in Hot Packages. In addition, it provides the HR-related corrections and
changes due to legal changes. Because of the link to legal changes, these patches should
be applied as soon as possible for legal compliance.
1117
8trategy
Obtain the notes related to the Hot Package, and review what it fixes:
< If there is nothing in the Hot Package that applies to you, then do not apply it.
< If there is something in the Hot Package that applies to you:
Determine if the entire Hot Package, or just the note, must be installed.
If it is determined that the Hot Package is to be installed, the application of the Hot
Package is treated as a mini-upgrade.
High-Level Process of Applying Hot Packages
Applying Hot Packages
1. Determine what Hot Packages have been applied to your system.
2. Get and review the Online Service System notes for the Hot Package(s).
3. Determine if the Hot Package should be or needs to be applied.
The following steps assume that the Hot Package is to be applied.
4. Obtain the latest version of the update programs:
SAP Patch Manager (SPAM) (from the Online Service System)
tp (from SAPSERV4, install in the kernel directory)
R3trans (from SAPSERV4, install in the kernel directory)
Steps 5 through 8 are repeated for all Hot Packages that are to be applied at the current
time.
5. Obtaining the Hot Package
Depending on the size of the Hot Package it can be obtained two ways:
< Download it from the Online Service System or SAPNet, or
< Retrieve it from the Hot Package collection on CD-ROM.
The Hot Package collection is the only way to get large Hot Packages.
The Hot Package collection contains all Hot Packages available at that point in time.
Download from the Online Service System Hot Package collection on CD-ROM
6. Request the Hot Package from the
Online Service System.
6. Request the Hot Package collection.
7. Download the Hot Package. 7. Upload the Hot Package.
8. Apply the Hot Package.
9. Execute the regression test.
10. When successful, confirm the Hot Package.
Release 4.0B
1118
Determining What Hot Packages Have Been Applied
Guided Tour
Method 1
1. Choose System Status.
2. Under Hot Package and Name is the
last Hot Package.
3. Hot Package Package status values
are:
4 N The patch has not yet been
applied
4 I Patch has been successfully
applied
4 ? Patch application has been
aborted
In this example, the patch has
successfully been applied as
indicated by I in Package status.
The name of a Hot Package is interpreted as follows:
< SAPKH<release><sequence_number>
< SAPKH40B01 is interpreted as SAPKH / 40B / 01, and is for Release 4.0B and is the first Hot Package.
2
3
1119
Method 2
1. In the Command field, enter transaction SPAM and choose Enter
(or choose Tools ABAP Workbench, then Utilities Maintenance Patches).
2. In the Patch queue field appears the
name of the last Hot Package.
3. Under Hot Package, the Status
indicator shows the status of that
Hot Package:
4 Green Hot Package is installed
4 Yellow Hot Package
application is not complete
(This usually indicates that the
confirm step has not been
performed.)
4 Red Hot Package application
was aborted
Method 3
The following is an alternate method of determining which Hot Packages have been applied and also what
version of SPAM is installed.
1. In the Command field, enter transaction SPAM, and choose Enter
2. Select All patches.
3. Choose Display.
3
2
3
2
Release 4.0B
1120
This screen shows:
4. Under Applied patches.
A. SPAM update version level.
B. Hot Packages applied.
Getting nformation on the Hot Package from the Online 8ervice 8ystem
1. When you log on to the Online
Service System from the System
News window, scroll down to the
Hot Packages section.
2. In this example, Hot Package no. 09
for Release 4.0B is now available.
3. Choose Continue.
4. Choose Service.
1
2
A
B
4
4
3
1121
5. Choose SAP Patch Service.
6. Choose SAP Hot Packages.
7. Search the extended list for your
release.
8. Click the plus (+) node to the left
of your release to select it.
9. Choose Expand.
5
6
8
9
Release 4.0B
1122
From this screen, you can view the:
A. SPAM update
This is the SAP Patch Manager.
Download and apply the current
version before applying any Hot
Package.
B. Hot Packages
Note the comment Extra Large,
which indicates that the Hot
Package may not be
downloadable.
10. To display the notes for a specific
Hot Package, select it, then choose
Notes for patch.
This screen shows Release 3.1H
Hot Packages. Note that some Hot
Packages are delivered via CD.
A
B
10
1123
11. To view all notes, click the minus
() node to the left of Application
areas.
12. Choose Expand.
From here there are two options:
< Option 1: View all notes.
(proceed to step 15).
< Option 2: View a specific note.
(proceed to step 27).
To View All Notes
1. Right-click anywhere on the
screen.
2. Select Download list from the
popup menu (not shown).
11
12
Release 4.0B
1124
3. Select unconverted.
4. Enter the
<drive\path\filename>
where you want to save the notes
in the File name field.
5. This screen shows the saved notes
as read by a text editor or word
processor.
3
4
1125
To create a file of all notes (in case
there are too many notes to go
through individually on the screen):
6. Choose Select all.
7. Choose List selected notes.
8. Choose Download to download the
notes to a file.
9. Choose No related copy.
8
9
6 7
Release 4.0B
1126
10. Choose No.
Here you only want to review the
notes, you do not want to register
the object for change. After
reviewing the notes, you may
decide not to install the hot
package.
Note: Depending on the number of notes addressed by the Hot Package, it could take a long time to
download the notes to a file.
11. Enter the path to your local PC
and create a name for the file.
12. Choose OK.
To View a 8pecific Note
1. Double-click the plus (+) node to
expand an individual branch (for
example, BC).
2. Double-click the plus (+) node for
BC-CTS, and BC-CTS-CCO.
3. Under BC-CTS-CCO, select note
0069444.
4. Choose Choose.
12
11
10
1
2
3
4
5
1127
This screen shows the Online Service
System note.
Release 4.0B
1128
Requesting 8PAM or a Hot Package from the Online 8ervice 8ystem
1. From the Hot Packages screen,
select either the:
< SPAM update
< Hot Package
2. Choose Request patch.
This popup window appears if the
patch is too large to download. In
this case, you need to obtain the
Hot Package from a CD.
3. Select the installation that the Hot
Package is for.
4. Enter the <SID> for the system
(for example, RW6).
5. Choose Continue.
1
2
3
4
5
1129
6. Note the message at the bottom of
the screen that indicates the patch
request has been generated.
7. The next step is to download the
patch (see the next section,
Downloading SPAM or a Hot
Package).
6
Release 4.0B
1130
Downloading 8PAM or a Hot Package
< Always first plan to apply the Hot Package on a test server to assure it will not create a
problem.
< Back up the test server before applying the Hot Package.
Prerequisite
The patch(es) must have been requested via the Online Service System for the system/<sid>
to which you are downloading it.
Guided Tour
1. Log on to client 000, under user ID DDIC. In this case, the special user ID DDIC is required.
3. Choose Download.
From this window you can specify
which Hot Packages to download.
4. Select the Hot Package (if not
already selected).
5. Choose Enter.
4
5
3
1131
This screen shows the EPS
Transmission (download) monitor:
A. Progress bar with the Size
[MB] of the Hot Package.
B. Transmission time (or elapsed
time) for the download.
C. Remaining time (or estimated
time to completion) for the
download.
6. A message at the bottom of the
screen indicates that the Hot
Package download has finished.
7. Choose Back.
Make sure that the directory /usr/sap/trans/EPS/in has enough free space to download the
Hot Package into.
A
B
C
6
7
Release 4.0B
1132
Uploading the Hot Package from a CD
Why
Periodically SAP releases a Hot Package Collection CD which contains all the released Hot
Packages up to that point.
Large Hot Packages (that is, those too large to download from the Online Service System)
are only available via CD.
How
1. Mount the CD with the patches.
2. Log on to the operating system as:
< UNIX: <sid>adm
< NT: <SID>adm
3. Change to the transport directory.
< UNIX: /usr/sap/trans
< NT: <drive>:\usr\sap\trans
4. Unpack the patch archive.
< UNIX: CAR xvf /<CD_DRIVE>/<PATH>/<ARCHIVE>.CAR
< NT: CAR xvf <CD_drive>:\<PATH>\<ARCHIVE>.CAR
5. Log on to Client 000, under user ID DDIC.
Note: The following example requires the use of the special user ID DDIC.
1133
Guided Tour
2. Choose Patch Upload.
3. Choose Enter.
4. Note the Hot Packages that have
successfully uploaded.
5. Choose Back.
5
4
3
1
Release 4.0B
1134
Updating 8PAM
Prerequisites
< The R/3 System should not be active. This means:
No users logged in
No jobs running
< All application servers should be shut down.
< The SPAM update should have been downloaded from the Online Service System.
If a SPAM update is available, apply it first, before any hot packages.
Guided Tour
1. Log on to client 000, under user ID DDIC.
3. Choose Patch Apply SPAM
update.
3
1135
4. Choose Enter.
5. Choose Enter.
4
5
Release 4.0B
1136
Applying the Hot Package
Prerequisites
< The R/3 System should not be active, which means:
No users logged on
No jobs running
< All application servers should be shut down.
< The current SPAM update should have been downloaded from the Online Service
System and applied.
< The Hot Package should have been downloaded from the Online Service System or
uploaded from the CD.
Guided Tour
1. Log on to client 000 under user ID DDIC.
Adding the Hot Package to the Patch Oueue
3. In Patch queue, choose possible
entries.
3
1137
4. Select the Patch (for example,
SAPKH40B05 and SAPKH40B06).
5. Choose Check Consistency.
The message Patch queue is
consistent appears in the message
bar (not shown).
6. Choose Specify queue.
7. The message Patch queue set up
indicates that the Hot Packages
have been added to the patch
queue.
8. The Patch queue field indicates
what patches loaded in the queue
are ready to be applied.
If you only have one (1) patch to
apply, the To field does not appear
on the screen.
9. The red x indicates that patches in
the patch queue have not been
applied.
4
5
6
7
8
9
Release 4.0B
1138
Applying the Hot Package
1. From the SAP Patch Manager
[SPAM] screen, choose Apply.
2. Choose Enter.
Note: Depending on the size of the Hot Package, the patch application process could run for a long time.
3. Choose Enter.
11
2
3
1139
4. Checking the status is
recommended. However, the
screen that you arrive at is the
same as in step 3 above.
5. Choose Log, to review the patch
queue log.
5
4
Release 4.0B
1140
6. Expand the node for the patch(es).
7. Review the return codes. Values
greater than 4 indicate failure.
8. Choose Back.
9. At this point regression testing on
the Hot Package should be
performed.
If several Hot Packages are going
in as a group, the option is to
confirm them after applying, then
perform the regression testing.
10. Choose Confirm.
Note: You cannot apply the next Hot
Package until the prior hot package is
confirmed.
11. Choose Yes.
6
7
8
6
7
10
11
1141
12. Check the bottom of the screen to
see if the patch queue was
confirmed.
12
Release 4.0B
1142
Object Conflicts
What
Object conflicts occur when SAP objects (such as programs, tables, etc.) that have been
modified by you are included in a Hot Package.
Why
If an object has been modified by you and that object is being changed in the Hot Package,
you could lose the modifications you made. This problem is typically occurs with an
advanced correction where a fix is incorporated in a future release of the R/3 System, and
an advanced correction is available before the future release. For example, you are on
Release 4.0B, and experience a problem. Your problem has already been fixed in a higher
release (for example, Release 4.5B). You do not have to wait for the upgrade. The fix is
available now for you to make as an advanced correction to your system.
In some instances, the Hot Package may not include the advanced correction. Thus, after
applying it, you may have to reapply the advanced correction.
How
< Determine if the change is or is not included in the Hot Package by:
Reviewing the code comparison (transaction SPAU)
Checking to see if the advanced correction is from a future release
If so, it probably will not be included in the Hot Package.
Checking to see if the change is your own modification
< If the change is included in the Hot Package:
Go back to SAP standard, thus making future maintenance simpler.
< If the change is not included in the Hot Package:
1. Check to see what needs to be done to reapply the modification.
2. Apply the modification.
3. Test the modification.
This process is the same as that performed during an upgrade.
1143
Regression Testing
Regression testing is absolutely necessary because many objects in many functional areas
may be potentially 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.
Useful Online 8ervice 8ystem Notes
Online
Service
System
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
73510 Problems during upgrade of patched source releases
82264 Important information about SAP patches >= 3.1H
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
97623 Patch types
97630 Known problems with patches >= 3.1H
104664 Applying patches from CD
119738 Problems during upgrade with too new Hot Packages
Kernel Upgrade
Release 4.0B
1144
Kernel Upgrade
What
A kernel upgrade is essentially the replacing of operating system level files (the kernel files)
with updated versions of those files.
Why
Kernel upgrades are normally done to fix bugs or other problems in the kernel. Some
kernel upgrades provide enhanced functionality.
How
< Review all applicable documentation:
Kernel instructions
Online Service System notes
Upgrade manual
< Special notes on the kernel version:
The kernel version is now independent of the R/3 release.
The kernel is backward compatible, meaning a user could be running a 3.0F database
(R/3 Release) with a 3.1I kernel.
If you are on a release prior to 3.1I, please review documentation to determine what
kernel version is applicable to your release.
You must remember what R/3 release the database and version the kernel are running on.
After the kernel is upgraded, you must apply kernel patches for the upgraded version of
the kernel. Do not apply kernel patches for the old version of the kernel.
When getting database patches, keep in mind that your database release stays the same,
regardless of what version your kernel changes to.
On rare occasions, an Online Service System note instructs you to apply a fix based on the
database release of the system; not the kernel version.
All servers in a system must be on the same version of the kernel .
Kernel Upgrade
1145
< Always first perform the upgrade on a test server to assure it does not create a problem.
< 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)
< The kernel files are:
dw1_nnn.CAR
dw2_nnn.CAR
If available, the optional optimized kernel files are:
dwopt1_nnn.CAR
dwopt2_nnn.CAR
The optimized kernel is not available for all releases.
< Unpack the kernel files (see chapter 13, Retrieving files from SAP, SAPSERV4 for the
procedure for unpacking the files).
< Back up the system at the database and operating system levels.
< Stop the R/3 System.
< Stop the SAP services that are using the kernel files (NT).
< Backup the kernel directory
UNIX: /usr/sap/<sid>/sys/exe/run
NT: <drive>:\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.
< Copy the new kernel files into the kernel directory
This replaces the old programs with the new programs.
< Perform any special instructions contained in:
Kernel instructions
Online Service System notes
Upgrade manual
Restart Option 1
1. Restart the SAP services that are using the kernel files (NT).
2. Start the R/3 System.
Check the logs
3. Monitor the system and system logs for problems.
Production Refresh Strategies
Release 4.0B
1146
Restart Option 2
1. Restart the server.
2. Check all logs for:
Operating System
Database
3. Start the R/3 System
Check the logs
4. Monitor the system and system log for problems.
Production Refresh 8trategies
Because data in the target system is being replaced, refreshing a system is an inherently
dangerous subject.
What
Production refresh is where the other systems are refreshed with data from the
production system.
After the copy, Real production data exists in the test system. Real production data
poses data security issues which must be addressed by the various data owners. It is more
critical if the HR system is installed, as personnel records are sensitive. Financial, sales and
other data may also be company sensitive.
Why
Refreshing a system from the production system helps to:
< 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.
< To prepare for an upgrade
You want the test system to exactly mirror the production system so that the upgrade in
the test system mirrors everything you will encounter into in the production system.
How
There are two ways to refresh a system:
< Database copy of the production system
< Client copy of the production client
Production Refresh Strategies
1147
Database Copy of Production 8ystem
A database copy is done by copying the entire production database.
Benefits
< 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, thus there is no impact to the
Production system. Making a copy also tests your backup/restore process.
Disadvantages
< All revision history of the refreshed system is lost.
Usually okay for the test/QA system
Usually not desired for the development system because version history is lost.
< The target database needs to be as large as the production 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 production system. Thus, 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.
Client Copy of the Production 8ystem
A client copy is done by performing a client copy of the active client from the production
system (instead of copying the entire database, like a database copy).
Benefits
< The target system does not have to be reconfigured, as with a database copy.
< The target system does not lose its client configuration.
Disadvantages
< A client copy requires that the source and target systems are not in use during the copy.
Having both 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 that follow).
Client Copy
Release 4.0B
1148
Client Copy
What
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, either within the same system (instance) or to another system.
Tables are selected based on their delivery class.
Client copy does not 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, the
table change is not copied to the target system. Thus, the data in the additional field is not
copied.
8pecial Notes
Read the current online documentation on client copy. The client copy programs and
functionality improve and change significantly with each new release.
The online help documentation on client copy is quite good. To access this documentation,
choose R/3 Library BC-Basis Components Change and Transport System Client Copy and
Transport, then Client Copy and Transport Client Copy and Transport
At this branch of the menu, is the client copy documentation:
Copying Clients Within the Same System
Copying Clients Between Systems
Copying Transport Requests
Transporting Clients Between Systems
Postprocessing After Client Import
Maintaining Clients
Deleting Clients
Viewing Copy Logs
Restarting Client Copy
Error Handling.
Client Copy
1149
You cannot separate master data from transaction data.
The developer of client copy maintains several informational Online Service System notes.
Do an Online Service System note search on component BC-CTS-CCO and search for notes
beginning with CC*.
Useful Online 8ervice 8ystem Notes
Online
Service
System
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
Processing Notes
During the copy process, you should 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 Online Service System 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 archive logs. Monitor the freespace in the saparch
directory. If this directory runs out of space, the database will stop.
Client Copy
Release 4.0B
1150
8ecurity
To perform a client copy, the user ID of the person doing the copy must have the same
authorizations in the source client as in the target client.
A system administrator with the same authorizations as user SAP* will have all the required
authorizations.
Client Copy
1151
Creating a Client
Guided Tour
(or choose Tools Administration, then Administration Client admin Client maintenance).
2. Choose Change.
3. Choose Enter.
4. Choose New entries.
2
3
4
Client Copy
Release 4.0B
1152
5. In Client, enter the client number
(for example, 101) and name (for
example, Test Client for
Docu).
Do not use clients: 000,001,or
066.These clients are reserved for
SAP.
6. In City, enter the city name (for
example, Palo Alto).
7. In Std. Currency, enter the
standard currency for the client
(for example, USD).
8. In Client role, choose possible
entries.
9. Select the role for the client you
are creating.
10. Choose Enter.
9
10
8
7
6
5
Client Copy
1153
11. Under Changes and transports for
client-independent objects,
select Automatic recording of
changes.
12. In Client-independent object changes,
choose possible entries.
From this screen you can finetune
what client-independent changes
will not be permitted.
13. Select the desired option.
14. Choose Enter.
13
14
11
12
Client Copy
Release 4.0B
1154
15. Choose Save.
16. Choose Back.
17. The new client is listed.
In later steps, this new client may
be referred to as the target
client.
18. Log on to the new client as user SAP* using password PASS.
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 done,
verify that the passwords for all system user IDs in the new client are secure.
17
15 16
Client Copy
1155
Copying a Client
Guided Tour
Copying on the 8ame 8ystem/8D
To copy a client on the same system/<sid>, you do a local client copy.
1. Log in to the target client as user ID sap* with the password pass.
Be sure you are logged in 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 choose Tools Administration, then Administration Client admin Client copy Local copy).
3. In Selected profile, choose possible
entries to select a copy profile that
matches your requirements.
4. Select the appropriate profile.
5. Choose Choose.
4
5
3
Client Copy
Release 4.0B
1156
6. Enter the Source client number (for
example, 500).
7. If your user masters are to come
from a specific client, then in the
Source client user masters field enter
the client number that the user
masters are to be copied from.
8. Choose Execute in background.
9. You are taken to the background
scheduling screens to complete the
task.
10. Complete the scheduling as you
would any other background job.
6
8
7
Client Copy
1157
Copying to a Different 8ystem/8D
To copy a client to a different system/<sid> you do a remote client copy.
Prerequisite
< In the target system, the source system needs to be set up in SM59.
< The client must have been created in the target system.
Copying from one system to another using remote client copy uses the RFC interface. Thus
there is no intermediate storage on disk.
1. Log in to the target system and client.
Be sure you are logged in to the correct target client.
(or choose Tools Administration, then Administration Client admin Client copy Remote copy).
3. Choose possible entries to select a
profile that matches your
requirements.
4. Select the appropriate profile that
matches what you want to copy.
5. Choose Choose.
4
6
3
4
5
Client Copy
Release 4.0B
1158
6. Choose possible entries to get a list
of available RFC destinations.
7. Select the source system.
8. Choose Choose.
9. Choose Execute in background.
task.
6
9
7
8
Client Copy
1159
Post-Client Copy Tasks
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.
Whenever 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.
Create an administrative user ID, which is a copy of the user SAP*.
Client Copy
Release 4.0B
1160
Deleting a Client
There are two ways to delete a client. You can use either:
< A specific Delete Client transaction SCC5.
< The R3TRANS program (see Online Service System note 13391).
We recommend that you use the Delete Client transaction to delete the client.
Before deleting a client, make certain you have a usable backup of the system in the event of a
major problem with the client delete (for example, deleting the wrong client).
Delete Client Transaction
Guided Tour
1. Log on to the client to be deleted.
Be sure you are logged in to the client you want to delete.
(or choose Tools Administration, then Administration Client admin Special functions
Delete client).
3. Verify the Client to be deleted (for
example, 101).
The Client to be deleted field is a
nonchangeable field and is the
client that you log on to. If the client
number is not correct, you logged in
to the wrong client.
4. Select Delete entry from T000.
5. Choose Background.
task.
5
4
3
Client Copy
1161
Reviewing the Client Copy Log
1. Log in to another client.
2. In the Command field, enter
transaction SM37 and choose Enter.
3. This screen in SM37 shows the client
delete job waiting to execute.
4. Enter transaction SCC3 then choose
Enter.
5. Select the run line (for example,
Target Client 101).
6. Choose Choose.
7. Select the run.
8. Choose Choose.
3
6
5
8
7
Client Copy
Release 4.0B
1162
9. The Client Copy Log Analysis screen
shows the summary statistics on the
client delete.
10. To get details, choose Details.
11. Choose Details to get more detailed
information for the table group (for
example Number of local tables (to
delete).
10
11
Changing System Passwords
1163
Changing 8ystem Passwords
Recording 8ystem Passwords
The normal recommendation is to never write down passwords. There are, however, three
major reasons to record them.
These reasons are due to the:
< Critical nature of SAP.
< Many systems and clients and all the other places where passwords are required.
< Need to access the system if the SAP system administrator(s) is not available.
Recommended Process
< All passwords for all system IDs should be recorded, placed in a sealed envelope, and
put in a company safe (possibly both an onsite and offsite safe) that has restricted access.
Only a select list of company personnel should have access to this information.
< User IDs that are used/needed to maintain the R/3 System include:
SAP*
DDIC
SAPCPIC (see note 29276)
Earlywatch (client 066)
All user created administrative IDs
Any other non-SAP user ID that is required to operate the system:
Operating system
Database
Other related applications
< The password list should be updated and replaced whenever passwords are changed.
Two people prepare the list, change the password, and verify the new passwordone user
ID at a time. If the recorded password is wrong, those keys are lost, and you may not be
able to log on to the system.
Release 4.0B
1164
Following are sample password tables:
Server SID Client User ID Password
SAPR3T TST 000 SAP* Newpass
DDIC Newpass
USRADM Newpass
SAPCPIC Newpass
001 SAP* Newpass
DDIC Newpass
USRADM Newpass
SAPCPIC Newpass
066 SAP* Newpass
DDIC Newpass
USRADM Newpass
SAPCPIC Newpass
Earlywatch Newpass
100 SAP* Newpass
DDIC Newpass
BATCH1 Newpass
USRADM Newpass
SAPCPIC Newpass
All systems should have entries for clients 000 and 001. In addition, the production system
should have an entry for client 066. Clients 000 and 001 are default clients in all systems.
Client 066 is the EarlyWatch client and may not exist in every system.
1165
Where User ID Password
UNIX root Newpass
<SID>ADM Newpass
Oracle system Newpass
SYS Newpass
OPS$<SID>ADM Newpass
OPS$SAPSERVICE<SID> Newpass
SAPR3 Newpass
NT Finance/DEVADM Newpass
Finance/PRDADM Newpass
SQLserver sa Newpass
sapr3 Newpass
Guided Tour
To change the password for a user ID:
1. In each instance and each client in use, log on under the user ID to change the password.
From the main SAP R/3 screen:
2. Enter the client number (for
example, 500) in Client.
3. Enter the user ID you want to
change (for example, sap*).
4. Enter the existing password.
5. Choose New password.
5
2
3
4
Release 4.0B
1166
6. Enter the new password twice in
the popup window.
Be very careful as you enter the new
password, so that you enter it
correctly. It is too easy to type one
thing when you think you have typed
another, or to make the same
typographical error twice (for
example, user versus users and
the versus teh).
7. Choose Transfer.
At this point the logon will
proceed as normal.
8. Record the new password in the password table.
9. Log on using the new password to verify it.
At this point, if the new password fails, you should have other administrative user IDs that can be used
to reset the password. For this reason, password changes should be done one user ID at a time.
10. This process must be repeated for every system and client in which the user ID has an entry. Currently,
there is no way to globally complete this process.
Operating 8ystem Level
At the operating system level, the following user IDs should have their passwords changed.
UNX
User IDs:
< <sid>adm
< root
Services:
< ora<sid>
NT
Note that in some places NT is case sensitive (for example, at the initial login screen).
User IDs:
< <SID>ADM
< SAPService<SID>
6
7
1167
Services:
< SAP
These services will either use user ID <SID>ADM or SAPService<SID>
SAP<SID>_<instance>
SAPOsCol
SAProuter
< Oracle
OracleService<sid>
OracleTNSListener80
The default user that the Oracle services runs under is system
< SQLserver
MSSQLServer
SQLServerAgent
The user ID that they run under is either <SID>ADM or SAPService<SID>
< Informix
INFORMIX-OnLineDynamicServer
INFORMIX-OnLineMessageService
< DB2
DB2-DB2DA400
Release 4.0B
1168
Databases
For the databases, the following user IDs should have their passwords changed.
Oracle/UNX
User IDs:
< SAPR3
< SYS
< SYSTEM
Useful Online 8ervice 8ystem Notes for Oracle/UNX
Online Service
System Note #
Description (Release)
117736 4.5A
101318 4.0B
086857 4.0A
Use the program chdbpass to change the passwords; chdbpass automatically updates the
SAPUSER table. This enables the user <sapsid>adm to access the database.
Oracle/NT
< system
< sys
< op$<sid>adm
< ops$sapservice<sid>
< sapr3
M8 8OL 8erver
< See Online Service System note 28893
< sa
< sapr3
nformix
See Online Service System note 15399
DB2
NT/DB2 See Online Service System note 80292

Chaper 11

Загружено:

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

Оригинальное название

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

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

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

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

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

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

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

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

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

Chaper 11

Загружено:

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

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

System Administration Made Easy 111

Chapter 11: Nonscheduled 8pecial

Chapter 11: Nonscheduled Special Maintenance

Вам также может понравиться