sap-troubleshootinglisted

# SAP Troubleshooting — method & rules of thumb Applies to any SAP problem: an error, a hang, "slow", an interface that stopped, a job that fails at night. The method matters more than any single command, because the common failure is **concluding too early from one log**. > ## Rule 0 — capture evidence *before* you restart > A restart is the most common first move and it **destroys the evidence** (work-process state, locks, > shared memory, in-flight traces). If the system is up enough to look at, spend two minutes collecting > (§2) first. If you must restart to restore service, say explicitly what evidence was lost. --- ## 1. Establish the facts first (never skip) Before opening any log, pin down: | Question | Why it changes everything | |---|---| | **What exactly happened?** Error text/number, dump name, screenshot | "It doesn't work" is not a symptom | | **When?** First occurrence, last occurrence, frequency | Drives the log time window; "since Tuesday" points at a change | | **Who / how many?** One user, one client, everyone | One user → authorizations/data. Everyone → system/infra | | **Where?** SID, client, instance/host, which app server | Instance-local logs mean you must look on the *right* host | | **Reproducible?** Always / sometimes / once | Intermittent → collect over time, don't chase one trace | | **Scope** — dialog, batch, interface, all? | Tells you which log families apply (§2) | | **PRD or not?** | Sets the guardrails on what you may do next | Then: