SAP OSS Notes
11911 SAP OSS Note - ST04: Display of DB alert log does not work
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.
Note 11911 Details:
When does this problem occur
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
Various:
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.
Solution instructions
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
the database).
4. and 5.: Adjust Reports LSTUNF01 and LSTUNTOP. Make the enclosed
corrections.
Description of problem
Solution instructions
Please import the corrections attached to this OSS note into your SAP system using SNOTE.
You can also view the full details of this OSS note and download it to your SAP system ready for implementation using transaction code SNOTE. Once it has been downloaded you can read the full details, check out any installation instructions including manual changes and see if there are any pre-requisites.
You can also check if a new version of note 11911 has been released as well as see if the note is valid for your current SAP system landscape.
Check if SAP OSS note 11911 has already been downloaded and is valid
To check if this note has already been download, what status it has and if it is valid for your system first execute t-code SNOTE and click on the SAP Note Browser icon
From here you can just enter the note number 11911 and press execute. If the note already exists it's details will be displayed. See here for full step by step instructions on how to check if an SAP note has been downloaded and is valid for your system.
If note 11911 does not exist on your system you will receive the message "Unable to find SAP Note that meets specified criteria"
If this is the case you will need to download the note to you SAP system also using transaction SNOTE. For further details see Download note using SNOTE. Even if it does exist you may still want to check if you have downloaded the latest version of the note.
Alternatively you can find full details of this note on the SAP service market place(SNumber / Service market place login will be required)