SAP AS ABAP Administration · System Monitoring & Troubleshooting

You broadcast an SM02 shutdown warning, then immediately stop the instance. Why might users still be cut off mid-transaction?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in System Monitoring & Troubleshooting

The SAP system is running but you can't log on to it at all, so every in-system transaction is off the table. Which OS-level tool do you use for the message server versus the gateway versus the work processes?

The database won't come up and neither will the SAP system, so no SM21 or ST22. Where do the developer traces live, and why are they the right thing to read in this exact situation?

You accidentally deleted a local system log file at the OS level. You recreate it or restart, but SM21 still misbehaves. What did deleting the file alone leave behind, and how do you fix it?

You need to start and stop several instances across the landscape from one place and manage operation modes. Which transaction, and what's the OS-specific catch that bites you on UNIX?

A security review asks you to prove that operating-system and database accounts are visible in the global user overview AL08. Why can't you deliver that from AL08?

A colleague opens SM13 to hunt for a user's failed update from last week, sees an empty list, and concludes there are no cancellations. What did the default selection do to them?

Start learning today

Free to start — download the app or use it in your browser.