Академический Документы
Профессиональный Документы
Культура Документы
1.1 Check that All Application Servers are Up and Work Process Analysis - SM51
Transaction SM51 allows you to look at all the servers in your system (for example, the
PRD database server and all of its application servers). You do not have to log into each
server individually.
If one of your dialog application servers is not up, the users who normally log on to
that application server will not have a server to log on to.
If the batch application server is down, batch jobs that are specified to run on that
server will not run.
1. In the Command field, enter transaction SM51 and choose Enter (or choose
ToolsAdministration, then MonitorSystem monitoringServers).
2. Review the list of instances under Server name. Verify that all your instances are
listed. If it is listed, it is up and running.
2
Process overview transactions allow users to view the status of work processes and
monitor for problems. Transaction SM51 is a central transaction from which you can
select the instance to monitor. SM51 starts transaction SM50 for each application server.
Transaction SM50 is used for a system without application servers.
Transaction SM51 is one place to look for jobs or programs that may be hung, which
would be indicated by long run times. If batch jobs are not running, transaction SM50 may
provide a hint of the problem, if all the batch work processes are in use.
1. In the Command field, enter transaction SM51 and choose Enter (or choose
ToolsAdministration, then MonitorSystem monitoringServers).
2. Select the instance you want to view.
3. Choose Processes.
4. This is the Process Overview transaction (SM50) for that instance.
1.2
1.3
1.4
1.5
To clear a lock, complete these steps on the systems application and the database servers:
1. Check that the user is not logged on any of the servers with transaction SM04 (no
application servers) or AL08 (with application servers).
If the user is not on the system, but transaction SM04 shows them on the system,
delete their sessions. This step, by itself, may clear the lock.
2. Check that there are no processes running under the user ID using transaction SM50 or
SM51.
3. Check that there are no batch jobs running under the user ID using transaction SM37.
4. Check that there are no updates in process for that user ID using transaction SM13.
5. Once you know that there is no activity using the users ID, select the lock entry for
deletion.
6. Choose Lock entriesDelete.
1.6
A failed update or an update terminate is an update to the database that failed. These
failed updates occur when a user entry or transaction is not entered or updated in the
database.
You should check the system for failed updates several times a day.
The longer you wait after the update terminate has occurred, the more difficult it is for
users to remember what they did when the update terminate occurred.
1. In the Command field, enter transaction SM13 and choose Enter (or choose
ToolsAdministration, then MonitorUpdate).
2. Enter * in Client.
3. Enter * in User.
4. Under Status, select All.
5. Change the date to a year ago in From date.
These options allow you to view the system log in the following priority layers:
Problems
Problems and warnings
All messages
2
3
1.8
Incorrect
These selections display only the batch jobs that need to be processed and those
with errors that need to be resolved.
4. Choose Enter.
5. Contact the responsible user to notify them or determine why these jobs are in:
a. Sessions still to be processed
b. Errors in sessions
1.9
1. In the Command field, enter transaction SM37 and choose Enter (or choose
SystemService, then JobsJob overview).
2. Enter * to get all jobs in Job name.
3. Enter either * (for all users) or the user ID that the batch jobs run under (to limit the
display to those scheduled under a specific user ID in User name).
4. Enter a start date in From.
5. Enter an end date in To.
6. Under Only jobs with status, select:
Active
Finished
Terminated
7. Choose Enter.
8. Check for failed or cancelled jobs.
Analyze why jobs failed or were cancelled and make the necessary corrections.
9. Check critical jobs.
You need to know the job name that they run under to do this.
10
1.10
Transaction DB02
This task involves monitoring the growth of the database and projecting future growth to
Determine when to plan to expand the database.
1. In the Command field, enter transaction DB02 and choose Enter (or choose
ToolsCCMS, then Control/MonitoringPerformance Menu, and then
DatabaseTable/Indexes).
2. Choose Space statistics under Database system
3. Check %-Used
Drill down on Tablespaces or Tables and indexes if issues are discovered.
A
1.11
1.12
1.13
Performance Checks
2.1
An alert indicates a potentially serious problem that should be quickly resolved. If not
contained, these problems could degenerate into a disaster.
1. In the Command field, enter transaction RZ20 and choose Enter (or choose
ToolsCCMS, then Control/MonitoringAlert Monitor 4.0).
2. Click the node next to the server to expand the server options.
3. Double-click on the monitor.
4. Look for any alerts, which are indicated in red.
5. Click the node next to the <sid> to drill down for additional details.
6. Select the alert
7. Choose Display alerts.
To get detail for the alert:
8. Select the alert item.
9. Choose Choose detail (magnifying glass icon).
10. Review the details.
11. Choose Back
To acknowledge the alert:
12. Select the alert item(s).
Alert (red)
Warning (yellow)
13. Choose Complete alerts.
You still have to perform a task based upon the alert.
Acknowledging the alert only means you received the alert notification,
nothing else.
14. When all alerts and warnings are acknowledged, the alert will change to green.
To get more details on the alert, you can start the analysis tool.
From the previous screen:
1. Select the alert (for example, Page_Out)
2. Choose Start Analysis tool.
2.2
Transaction ST02
The buffer tune summary transaction displays the R/3 buffer performance statistics. It is
used to tune buffer parameters of R/3 and, to a lesser degree, the R/3 database and
operating system.
The buffer is important because significant buffer swapping reduces performance. Look
under Swaps for red entries.
1. In the Command field, enter transaction ST02 and choose Enter The two important
things to review are:
Hit Ratio, for which the target value is 95 percent and higher
Soon after starting the system, this value is typically low, because certain buffers are
empty. The hit ratio will increase as the system is used and the buffers are loaded. It
usually takes a day to load the buffers that are normally used.
Swaps, for which the target value is less than 1,000
Swaps occur when the necessary data is not in the buffer. The system has to retrieve
the data from the database. The swap value is reset to zero (0) when the system is
restarted.
Buffer swaps may be due to:
Buffer too small, out of space
Out of buffer directory entries
Fragmentation in buffer, particularly the program buffer
If program buffer exceeds 10,000, it should be investigated
Generic table buffer
Sometimes very large buffered objects should be unbuffered (over 2MB)
2.3
2.5