Help you to understand the snapshot functionality the SAP system.
This page contains information regarding the snapshot functionality delivered as from the kernel 740, aiming to explain its purpose, content and related parameters.
The snapshops in the ABAP server aim to display important information about the current situation of the server, automatically by some error situations like a work processes unexpectedly finished or manually created by using DPMON or SM51 itself.
The snapshot will first dump all the essential information into the developer trace, mainly the dispatcher trace (dev_disp) and second creates a snapshot by using sapcontrol.
You can manually trigger the snapshop creation by using transaction SM51 -> GoTo -> Administration -> Snapshot -> Create.
Automatic Creation of Snapshots
There are several situations where the snapshot is automatically triggered by the server in order to display important information for analysis in the developer traces. These situations are:
- In case a hard shutdown occurs
- In case of exhausted resources.
- In case of a deadlock handling.
- In case a crash occurs in a work process, ICM or gateway.
- In case the eyecatcher of an internal table has been destroyed.
- In case the request processing stops for more than 30 seconds.
Snapshot Section in the Developer Traces
When the ABAP server triggers the snapshot creation, there will be an snapshot section inside the dispatcher trace file. Additionally, the work process developer trace itself will write a special section in its trace file.
In the dispatcher trace file, the snapshot will be displayed in the below format.
- Starts with the trace entry ****** SERVER SNAPSHOT <id> (Reason: <reason>) - begin ********.
- The content of the request queue.
- The content of the session table.
- The conent of the process table
- Ends with the trace entry ****** SERVER SNAPSHOT <id> (Reason: <reason>) - end ********.
In the work process trace file, the snapshot wil be displayed in the below format.
- Starts with the trace entry ****** SERVER SNAPSHOT <id> - begin ********.
- The current C-STACK.
- The current ABAP stack.
- Details about critical sections.
- Ends with the trace entry ****** SERVER SNAPSHOT <id> - end ********.
In the below image you can see an example of the snapshot functionality displayed in the dispatcher trace.
Every snapshot has a server unique id which is a increasing number. If the extended info area of SM50 has been activated, SM50 shows the number of snapshots created by this server. You can find this information by using transaction SM51 -> GoTo -> Administration -> Snapshot -> Administration.
The snapshot list will be displayed in the following format.
Snapshots can be displayed using SAP MC. To enable this, the snapshots must first be downloaded to the local PC by using the following:
- Transaction SM50 (Administration -> Snapshot -> Adminster), comes with 7.40 SP8.
- Transaction SM51 (Goto -> Administration -> Snapshot -> Administer), comes with 7.40 SP8
- Transaction SNAPSHOTS, comes with 7.40 SP7.
- Report RS_DOWNLOAD_SNAPSHOTS, comes with 7.40 SP7.
After downloading the file, a snapshot can be opened with SAP MC (right click -> open with -> Microsoft Management Console).
Configuring the Snapshots
The following parameters can be used to confiure snapshots.
- service/max_snapshots - defines the maximum number of snapshots per server
- rdisp/snapshot - configure the creation of snapshots by the ABAP server with the following sections
- creation: should the server create snapshots due to high load of / exhausted resource?
- period: limitate the number of snapshots for a given time interval
- lines: maximal number of trace file lines included in a snapshot
For more details on the possible values and syntax of the above parameters, refer to the parameter documentation in transaction RZ11.