The subject of database lg files has more recently been taken up by our Product Management under the following IDEAS section:Implement control on database logging (.lg) verbosity and type of events to include/exclude? https://community.progress.com/community_groups/products_enhancements/i/openedge_database_enhancements_-_tell_us_what_youd_like_to_see/implement_control_on_database_logging_lg_verbosity_and_type_of_events_to_includeexcludeIdeas Database lg file Enhancement Suggestions:
- For Progress to supply a tool (a bit like prolog except for lg file 'issues), which ties in with also being able to include/exclude event message types.
- For the database lg file to be able to be created in a defined directory (like ubroker log files)
Consider weighing-in on the discussion.
is a very useful tool, the paid version monitors log files and has many other useful features. (https://demo.wss.com/
3. Progress does not publish a specific set of error codes or messages to parse database logs for 'areas of concern'.
The database .lg file has a column to indicate the severity of the message after the Task ID column:
[yy/mm/dd@hh:mm:ss.uuushhmm] P-nnnnnn T-nnnnnn S name nnn: (nnnnn) Message
- I - Information; which can be ignored in initial scans and may be needed later when further investigating logged events.
- W - Warning; these messages are sometimes ignored at peril because some error messages are treated like warnings in certain contexts and errors in other contexts.
- F - Fatal error; are the easiest first parse for bearing in mind that less-critical messages like "cannot disable ai it is not enabled .." are flagged "F" which may or may not be critical depending on the context of the investigation.
Typically customers start with the "Fatal
" Severity and build their list and groups of error messages to parse for up over time. Caution should be exercised when using error numbers as these change between versions . The following case-insensitive key words catch most instances requiring attention as a starting point.
denied, failed, failure, unable, cannot, dbkey, recid, delete, error, complete, exceed, open, index, attempted, bk*, found, semAdd, ABNORMAL, dead, died, lk, socket
Consider reviewing the data in DLC/prohelp/msgdata (essentially the warnings for messages) which provide a more easily parsable set of text files for finding common key words in promsgs to search for.