Evaluating Snapshot Information in the Developer Trace

The following information is written to the developer trace when a snapshot is created:

• ** * * * * SERVER SNAPSHOT <id> (Reason: <reason>) - begin * * ******
• Request queue
• Session table
• Work process table
• ** * * * * SERVER SNAPSHOT <id> (Reason: <reason>) - end * * ******

The following information is written to the work process traces when a snapshot is created:

• ** * * * * SERVER SNAPSHOT <id> - begin * * ******
• Current C stack
• Current ABAP stack
• Information about critical segments
• ** * * * * SERVER SNAPSHOT <id> - end * * ******

Each snapshot created has a unique ID that is assigned in ascending order. If you have activated the extended info area in transaction SM50 (default), the number of snapshots created on the application server instance you are currently on is displayed there.

The additional information that can be written to the traces when the snapshots are created can be used by support for analysis purposes at a deeper level.