SAP OSS Note 11911 version 0009 contains details of a know issue related to ST04: Display of DB alert log does not work
. This includes any associated symptoms and instructions on how to fix it, see below for full details. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience of this oss note and problem.
...For more information about the SAP support system known as OSS please check out the SAP OSS NOTES SECTION, whih includes how to download & implement them onto your SAP system using transaction code SNOTE.
Key word: DB alert log
The message log is not displayed in transaction st04,
"Detailed analysis menu", "Database message log".
Cause of the problem and Pre-requisites
1. The file (e.g. under Oracle
/oracle/C11/saptrace/background/alert_C11.log), has access privileges
that are too restrictive.
2. An error occurs in rsdb0500 if the computer's name has a "_".
3. Problems with RFC (remote function call). Earlier versions
of the report used RFC.
4. Under Oracle 9i on Windows NT, the file name is no longer
<(><<)>SID>ALRT.LOG but ALERT_<(><<)>SID>.log (identical with Unix).
5. If the application server is an NT server and the database runs
under UNIX, the correct file name is not chosen in Release 4.0B.
1: Open the file for read access, e.g.
chmod 644 /oracle/C11/saptrace/background/alert_C11.log.
2: Error corrected in 2.1G. A copy of the 2.1G version is
available on the sapserv3 server under path:
dist/permanent/rsdb0500.Z. You can fetch the report via ftp,
decompress it, and upload it into a repair correction.
3: RFC problems can occur for any number of reasons.
The new version of the ABAP mentioned above avoids the RFC
all when possible (program then runs on the same computer as
4. and 5.: Adjust Reports LSTUNF01 and LSTUNTOP. Make the enclosed
Description of problem