How to control on database logging (.lg) verbosity and errors or messages to include/exclude? - Progress Community

Loading

Skip to Main Content

How to control on database logging (.lg) verbosity and errors or messages to include/exclude?

How to control on database logging (.lg) verbosity and errors or event messages to include/exclude to search database logs for to indicate errors or unwanted situations that need further attention

Nov 29, 2021
Knowledge

Title

How to control on database logging (.lg) verbosity and errors or messages to include/exclude?

URL Name

parse-database-lg-file-for-errors

Article Number

000188807

Environment

Product: Progress OpenEdge Version: All supported versions OS: All supported platforms

Question/Problem Description

Implement control on database logging (.lg) verbosity and type of events to include/exclude
Which database lg messages to include/exclude in database logs
What errors and messages to filter out of a database logfile
Advice on parsing the database lg file for errors or unwanted situations that need further attention
Error codes to parse database lg files for events needing attention
A set of error codes or messages to search database logs for to indicate issues or unwanted situations that need further analysis

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

Resolution

The subject of database lg files was approved by our Product Management under the following IDEAS section, which is available since OpenEdge 11.7.3, OpenEdge 12.1

Implement control on database logging (.lg) verbosity and type of events to include/exclude?
https://openedge.ideas.aha.io/ideas/OPENEDGE-I-552

1. "-omitLgMsgs" which takes a list of messages to omit from the .lg file (for SQL and ABL connections).

Can database logging be disabled?
Manage the OpenEdge Database: Database Startup Parameters - Omit Log Messages (-omitLgMsgs) https://docs.progress.com/bundle/openedge-database-management/page/Omit-Log-Messages-omitLgMsgs.html

2. "-limitLgPayload" to remove private information from messages that are printed.

Manage the OpenEdge Database: Database Startup Parameters - Limit log file payload (-limitLgPayload) https://docs.progress.com/bundle/openedge-database-management/page/Limit-log-file-payload-limitLgPayload.html

3. "-lgArchiveEnable" .lg file management, provides a flexible mechanism beyond PROLOG to:

Automatically archive to a required location ( -lgArchiveDir) and
Truncate the .lg file based on size ( -lgTruncateSize) and/or based on time ( -lgTruncateTime), (-lgTruncateFrequency) daily, day of week, end of month.
Manage the OpenEdge Database: Logged Data, Log file archive and truncate - Log file truncate and archive startup parameters https://docs.progress.com/bundle/openedge-database-management/page/Log-file-truncate-and-archive-startup-parameters.html

Progress does not publish a specific set of error codes or messages to parse database logs for 'areas of concern'.

A customizable logging level and log entry types, is not a feature in the DB logging: DB log file size threshold, logging level and log entry types

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 while 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 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 set of text files for finding common key words in promsgs to search for.

How to view promsgs contents

Workaround

Notes

Progress Articles:

4GL/ABL: How to programmatically get the description of an error message based on its number?
Where can I find the documentation for errors in DBANALYS
Error messages and keywords that could indicate a failed PROBKUP

Keyword Phrase

Last Modified Date

11/29/2021 2:29 PM

OpenEdge DeploymentOpenEdge ArchitectureOpenEdge DevelopmentOpenEdge General DiscussionsOpenEdge Pro2OpenEdge RDBMS

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

How to control on database logging (.lg) verbosity and errors or messages to include/exclude? - Progress Community