Chat now with support
Chat with Support

Spotlight on DB2 6.10 - Release Notes

Diagnostic Log drilldown

The Diagnostic Log drilldown captures diagnostic log, event, and notification messages (also called records) generated for the current database or for databases within the current DB2 instance. Because a database can generate a large volume of records, you can define filters that limit the number of records that Spotlight retrieves. Once Spotlight retrieves the records, you can manage the scope of the record list by defining filters on column values.

The Diagnostic Log drilldown is based on the PD_GET_DIAG_HIST table function.

Click one of these links for more information about this drilldown:

Open the Diagnostic Log drilldown

Use the Diagnostic Log drilldown

Limit the number of records retrieved

Filter the information displayed on the drilldown

Diagnostic information available on the drilldown

Open the Diagnostic Log drilldown

To open the Diagnostic Log drilldown

On the home page for the selected DB2 database or on the home page for the DB2 instance, click in the Spotlight toolbar.

Use the Diagnostic Log drilldown

The steps below outline the basic workflow involved in using the Diagnostic Log drilldown.

To use the Diagnostic Log drilldown

  1. On the Diagnostic Log tab of the drilldown, define predicates that limit the number of records that Spotlight retrieves.

  2. Once Spotlight retrieves the records and displays them in the lower pane of the Diagnostic Log tab, use the Criteria tab to refine the list of records by defining filters based on column values.

  3. On the Diagnostic Log tab, browse details about the diagnostic records captured on the drilldown. For a description of the information shown for each record, see Diagnostic Log information available on the drilldown.

Limit the number of records retrieved

Databases can generate a high volume of diagnostic records at a given time. To limit the number of diagnostic records that the PD_GET_DIAG_HIST table function retrieves, use the procedure below to define predicates for the function. These predicates control the type of diagnostic information retrieved and help limit the amount of time required for retrieval.

To define predicates

  1. In the Diagnostic Log Fetching Predicates pane on the Diagnostics Log tab, complete the one or more of the following fields to define predicates that filter the diagnostic records:

Facility

Select the option that determines the general record grouping to retrieve:

  • ALL - Retrieve records containing optimizer statistics and records from all DB2 general diagnostic logs and

  • MAIN - Retrieve records from all DB2 general diagnostic logs only--db2daig.log, admin notification log, and event logs.

  • OPTSTATS - Retrieve records containing optimizer statistics only.

Event types

Select one or both types of event records to retrieve:

  • Internal - All internal event records. IBM support uses these records to troubleshoot issues.

  • External - All external event records. These records are directed to users.

Diagnostic types

Select one or both types of diagnostic records to retrieve:

  • Internal - All internal diagnostic records. IBM support uses these records to troubleshoot issues.

  • External - All diagnostic notification records, used to provide information to the user.  

Minimum impact

To retrieve records containing messages that have a degree of impact on the user, specify the minimum level of this impact.

For example, select POTENTIAL to retrieve records that contain messages of POTENTIAL, IMMEDIATE, or CRITICAL value. Select NONE to retrieve all records.

From, To

Select the To or From fields or both to specify a finite range of time in which to capture log information.

Then enter the time range in which to capture log information. All records generated after the To timestamp and before the From timestamp are captured.

To change the date or time, use the arrows to move the times backward or forward; or select and type over any element in the date or time entry.

  1. Click Fetch to retrieve the records and display them in lower pane of the Diagnostic Log tab.

Filter information displayed on the drilldown

Once Spotlight retrieves the records, you can filter the list of records as needed.

To filter the list of diagnostic records

  1. On the Criteria tab, define the filters based on the column values of the retrieved rows.

  2. Return to the Diagnostic Log tab, and click Fetch. The list of records is refreshed, based on the current Criteria tab filters.

  3. Repeat steps 1 and 2 to define or remove filters to continue to adjust the record display, depending on the information you want to browse.

Diagnostic information available on the drilldown

The following information can display for each record on the Diagnostic Log drilldown. For a complete description of the record information, refer to the IBM DB2 for Linux, Unix, and Windows documentation describing the PD_GET_DIAG_HIST table function.

Initially, by default, the drilldown shows a subset of all columns. available for this drilldown However, you can right-click in the column header area to perform a variety of column-customization activities. For example, you can display hidden columns and hide currently displayed columns as needed. Additionally, you can reorganize the displayed columns. For more information, see the Organize Columns topic.

Column

Description

TimeStamp

The time that the diagnostic message was generated.

DBName

The database for which the diagnostic message was generated.

Facility

The general group of records from which Spotlight retrieved the diagnostic message:

  • ALL - Records retrieved from all DB2 general diagnostic logs and records containing information about optimizer statistics.

  • MAIN - Records retrieved from all DB2 general diagnostic logs only, including db2diag.log, admin notification log, and event logs.

  • OPSTATS - Records containing optimizer statistic information

Type

The type of record:

  • DI -Internal diagnostic record. IBM support uses this record type to troubleshoot issues.

  • DX - External diagnostic record, intended to provide user information.

  • EI - Internal event record. IBM support uses this record type to troubleshoot issues.

  • EX - External event record, intended to provide user information.

Partition

The number of the partition on which the record was generated.

Level

The severity level of message:

C -Critical

E - Error

I - Information

S - Severe

W - Warning

Impact

From the user's point of view, the degree to which the condition denoted by the message affects the DB2 business process.

EDU ID

The ID of the engine dispatched unit that generated the message.

EDU Name

The name of the engine dispatched unit that generated the message.

PID

ID of the operating system process that generated the message.

Process Name

The name of the operating system process that generated the message.

Thread ID

The ID of the thread that generated the message.

Appl Name

The name of the application that connected to the database.

Appl ID

The ID of the application that connected to the database.

Appl Handle

The agent ID assigned to the application that connected to the database.

Auth ID

The system authorization ID for the process.

Product

The name of the product that generated the record.

Component

The name of the component that generated the record.

Function

The name of the function that generated the record.

Probe

The number of the probe point at which the function generated the message.

Called Prod

The name of the product that is the error source (if the error source is not the product the generated the message).

Called Comp

The name of the component that is the error source (if the error source is not the component that the generated the message).

Called Func

The name of the function that is the error source (if the error source is not the function that the generated the message).

OS Error

The number identifying the operation system error.

Ret Code

The code returned by the product.

Msg Num

The number identifying the message.

Msg Type

The type of message associated with the message number.

Message

An abbreviated version of the message text.

Obj Type

The type of object to which the event applies.

Obj Name

The name of the object to which the event applies.

Obj Qual

Qualifying information for the object to which the event applies.

Event Type

The action associated with the event that caused the message.

Event Desc

An abbreviated list of the key fields associated with the event.

1st Event Qual Type

The type of the event's first qualifier. (A qualifier helps to describe what the event affects.) If Facility is OPSTATS , this value must be AT.

1st Event Qual

The event's first qualifier.

2nd Event Qual Type

The type of the event's second qualifier. (A qualifier helps to describe what the event affects.) If Facility is OPSTATS , this value must be BY.

2nd Event Qual

The event's second qualifier.

3rd Event Qual Type

The type of the event's second qualifier. (A qualifier helps to describe what the event affects.) If Facility is OPSTATS , this value must be DUE TO.

3rd Event Qual

The event's third qualifier.

Event State

The result of the event on the object or action. A percentage value shows the progress that the effect of the event has had on the object or action.

Event Attr

One or more attributes relating to the event.

Event Stack

The event stack that was current when the message was added to the log.

Call Stack

The operating system stack dump that was current when the thread generated the message.

Dump File

The full path and file name of the secondary dump file connected to the logged record.

 

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating