SAP System Logs : Part 3 The Actual Troubleshooting

In the SAP landscape, tracking down the relevant logs associated with a specific process can be a critical task for troubleshooting and analysis. When armed with the process ID, knowledge of the relevant transaction codes, and appropriate OS level commands, you can efficiently locate and access the logs needed to investigate issues. In this blog, we will provide a step-by-step guide on finding the relevant logs using process IDs, along with the corresponding transaction codes and OS level commands.

Step 1: Identify the Process ID (PID)

To begin, you need to determine the process ID of the SAP process for which you want to find the logs. This can be obtained from the SAP system Here's how to obtain the PID in different scenarios:

SAP System Level:

Transaction code: SM50 (Work Process Overview)

Navigate to the "Work Process Overview" screen and locate the specific process. Note down the process ID (PID) associated with it.

Refer here

Finding background Jobs process id 

Step 2: Finding the Relevant Logs

Once you have the process ID (PID), you can use it to identify and access the corresponding logs. Here's how to find the logs using transaction codes and OS level commands:

Different logs :

dev_w<X>: Use the PID to identify the work process number (X). For example, if the PID is associated with work process 5, the relevant log will be dev_w5.

dev_server<X>: Use the PID to determine the application server number (X). The corresponding log will be dev_serverX.

dev_disp.log: This log captures the activities of the SAP dispatcher. It is not specific to a process ID but provides an overview of the system's dispatching activities.

OS Level Commands:

cd <work_directory> && tail -f dev_disp.log

There are also logs written on OS level that can help in deep diving in the issue 

The exact location of the System Log may vary depending on the operating system and its configuration. However, it is typically found in one of the following locations:

Linux: /var/log/syslog, /var/log/messages, /var/log/kern.log

Unix (AIX, HP-UX, Solaris): /var/adm/syslog, /var/adm/messages, /var/adm/syslog/syslog.log

Windows: Event Viewer (Event Logs)

The System Log captures a broad range of system-related events and messages. It is designed to centralize and store critical system information, making it easier to monitor and troubleshoot system issues. The key purposes of the System Log include:

Kernel Events: The System Log records messages related to the operating system kernel, such as boot messages, device driver issues, hardware errors, and system initialization events. These messages provide insights into low-level system activities and can help identify hardware or driver-related problems.

Network Events: The syslog may contain network-related messages, including network configuration changes, IP address assignments, network device failures, firewall activity, and network connectivity issues. Monitoring network events in the System Log can help diagnose network-related problems affecting the SAP system.

System Errors and Warnings: The log captures various system errors, warnings, and informational messages generated by the operating system. These messages can include file system errors, disk failures, memory allocation issues, permission problems, and other system-level anomalies. Monitoring the System Log helps identify potential system-wide issues that may impact SAP system performance and stability.

Security Events: Some security-related events, such as failed login attempts, authentication failures, intrusion detection alerts, and access control violations, may also be logged in the System Log. These messages provide an overview of security-related activities on the system and can assist in identifying potential security breaches or unauthorized access attempts.

Part 1

Part 2