Jump to: navigation, search

In the Column List:

  • P = Primary key
  • M = Mandatory field
  • F = Foreign key

Table G_LOG_MESSAGES


This table stores messages from the stored procedures about merge operations, purge operations, and stuck calls.

Tip
To assist you in preparing supplementary documentation, click the following link to download a comma-separated text file containing information such as the data types and descriptions for all columns in this table: Download a CSV file.

Hint: For easiest viewing, open the downloaded CSV file in Excel and adjust settings for column widths, text wrapping, and so on as desired. Depending on your browser and other system settings, you might need to save the file to your desktop first.

Column List

Legend

Column Data Type P M F Description

ID

NUMBER(16) X X The unique, autonumbered ID of this record. This is the primary key.

MESSAGE_ID

INTEGER ID of log event. This is the same ID that is documented in Framework Combined Log Events. This is ID recognized by Message Server.

TIMEGENERATED

TIMESTAMP(3) The GMT-equivalent date and time when the message was generated.

TIMEWRITTEN

TIMESTAMP(3) The date and time when the message was written.

PRIORITY

INTEGER Specifies priority of the log message. Refer to G_Dictionary Values for a listing of permissible values.

#DICTIONARY TYPE 32

ORIGIN

INTEGER Specifies the origin of the log message. Refer to G_Dictionary Values for a listing of permissible values.

#DICTIONARY TYPE 34

CATEGORY

INTEGER Specifies category of the log message. One of the following values:
  • 0—Default.
  • 1—Alarm.
  • 2—Audit.

#DICTIONARY TYPE 33

DATALEN

INTEGER Size of the buffer required to get packed attributes associated with this log event.

APPDBID

INTEGER The value for this field is always NULL.

APPTYPE

INTEGER The type of application that is related to this log event.

APPNAME

VARCHAR2(255) Name of the application having APPDBID that is related to this log event. If the application is ICON itself, then this field provides the name of the stored procedure which created this record in the following format:


ICON DB: <stored procedure name>
For example:
ICON DB: GSYSPurge81

HOSTNAME

VARCHAR2(128) Name of the host where the application related to this log event runs.

MESSAGETEXT

VARCHAR2(255) The text of the message. For ICON purge operations, this field stores information about either the name of the table being purged and its purge status or the status of a purge partition; for example:


GSYS_PURGE_PARTITION purge started...
IDB:Purge-table:G_CALL_STAT initiated...
IDB:Purge-table:G_CALL_STAT completed...
...
GSYS_PURGE_PARTITION purge completed

If, for some reason, the purge procedure cannot start, ICON logs "ERROR:wrong parameters" to this field.

   

 

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on October 31, 2016, at 14:34.