Warehouse Summarization and Pruning Agent User's Guide

Warehouse Summarization and Pruning AgentVersion 6.2.3 Fix Pack 1

User's Guide

SC23-9767-02

��

Note

Before using this information and the product it supports, read the information in “Notices” on page 75.

This edition applies to version 6.2.3 Fix Pack 1 of the IBM Tivoli Warehouse Summarization and Pruning Agent andto all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2010, 2012.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Tables . . . . . . . . . . . . . . . v

Chapter 1. Overview of the agent . . . . 1New in this release . . . . . . . . . . . . 1Components of Warehouse Summarization andPruning Agent . . . . . . . . . . . . . . 1Agent Management Services . . . . . . . . . 2User interface options . . . . . . . . . . . 2

Chapter 2. Requirements for themonitoring agent . . . . . . . . . . . 5Requirements for the Summarization and Pruningagent . . . . . . . . . . . . . . . . . 5Disable data warehouse log tables . . . . . . . 6

Chapter 3. Workspaces reference . . . . 7Predefined workspaces . . . . . . . . . . . 8Workspace descriptions . . . . . . . . . . . 8

Warehouse Summarization and Pruning AgentNavigator item . . . . . . . . . . . . 8Configuration Navigator item. . . . . . . . 8Statistics Navigator item . . . . . . . . . 9

Chapter 4. Attributes reference . . . . 11Attribute groups for the Warehouse Summarizationand Pruning Agent . . . . . . . . . . . . 11Attributes in each attribute group . . . . . . . 12

Connectivity attribute group. . . . . . . . 12Node Failures attribute group . . . . . . . 15Summarization Config attribute group . . . . 18Summarization Statistics attribute group. . . . 27Table Statistics attribute group . . . . . . . 30

Disk capacity planning for historical data . . . . 35

Chapter 5. Situations reference . . . . 37Predefined situations . . . . . . . . . . . 38

Chapter 6. Take Action commandsreference. . . . . . . . . . . . . . 39Predefined Take Action commands . . . . . . 39

Chapter 7. Policies reference . . . . . 41

Chapter 8. Troubleshooting . . . . . . 43Trace logging . . . . . . . . . . . . . . 44

Overview of log file management . . . . . . 45Principal trace log files . . . . . . . . . 45Examples: Using trace logs . . . . . . . . 49RAS trace parameters . . . . . . . . . . 50Dynamic modification of trace settings . . . . 53Setting trace parameters for the Tivoli EnterpriseConsole server . . . . . . . . . . . . 56

Problems and workarounds . . . . . . . . . 57Installation and configuration troubleshooting . . 57Agent troubleshooting . . . . . . . . . . 60Workspace troubleshooting . . . . . . . . 64

Support information . . . . . . . . . . . 65

Appendix A. IBM Tivoli EnterpriseConsole event mapping . . . . . . . 67

Appendix B. Documentation library . . 71Prerequisite publications . . . . . . . . . . 71Related publications . . . . . . . . . . . 72Other sources of documentation . . . . . . . 72

Accessibility . . . . . . . . . . . . 73

Notices . . . . . . . . . . . . . . 75Trademarks . . . . . . . . . . . . . . 77

Index . . . . . . . . . . . . . . . 79

© Copyright IBM Corp. 2010, 2012 iii

iv Warehouse Summarization and Pruning Agent User's Guide

Tables

1. Capacity planning for historical data logged bycomponent . . . . . . . . . . . . . 35

2. Information to gather before contacting IBMSoftware Support . . . . . . . . . . 43

3. Trace log files for troubleshooting agents 454. Problems and solutions for installation and

configuration . . . . . . . . . . . . 57

5. General problems and solutions foruninstallation . . . . . . . . . . . . 59

6. Agent problems and solutions . . . . . . 607. Workspace problems and solutions. . . . . 64

© Copyright IBM Corp. 2010, 2012 v

vi Warehouse Summarization and Pruning Agent User's Guide

Chapter 1. Overview of the agent

The Warehouse Summarization and Pruning Agent provides you with thecapability to monitor Summarization and Pruning Agent. IBM® Tivoli® Monitoringis the base software for the Warehouse Summarization and Pruning Agent.

IBM Tivoli Monitoring overview

IBM Tivoli Monitoring provides a way to monitor the availability and performanceof all the systems in your enterprise from one or several designated workstations.It also provides useful historical data that you can use to track trends and totroubleshoot system problems.

You can use IBM Tivoli Monitoring to achieve the following tasks:v Monitor for alerts on the systems that you are managing by using predefined

situations or custom situations.v Establish your own performance thresholds.v Trace the causes leading to an alert.v Gather comprehensive data about system conditions.v Use policies to take actions, schedule work, and automate manual tasks.

The Tivoli Enterprise Portal is the interface for IBM Tivoli Monitoring products.You can use the consolidated view of your environment as seen in the TivoliEnterprise Portal to monitor and resolve performance issues throughout theenterprise.

See the IBM Tivoli Monitoring publications listed in “Prerequisite publications” onpage 71 for complete information about IBM Tivoli Monitoring and the TivoliEnterprise Portal.

New in this releaseFor version 6.2.3 Fix Pack 1 of this monitoring agent, the following enhancementshave been made since version 6.2.3, including the fix packs:v With IBM Tivoli Monitoring v6.2.3, you can now disable the creation of the data

warehouse log tables so that fewer database resources are needed (defaultconfiguration for the Warehouse Summarization and Pruning Agent). Ifupgrading from an existing installation, you can truncate the existing tables inthe database to allow their storage space to be reclaimed.

v Updated Agent Configuration view in the Configuration Workspace to displaythe value of the Database Compression variable.

Components of Warehouse Summarization and Pruning AgentAfter you install and set up the Warehouse Summarization and Pruning Agent,you have an environment that contains the client, server, and monitoring agentimplementation for IBM Tivoli Monitoring

This IBM Tivoli Monitoring environment contains the following components:

© Copyright IBM Corp. 2010, 2012 1

Tivoli Enterprise Portal clientThe portal has a user interface based on Java for viewing and monitoringyour enterprise.

Tivoli Enterprise Portal ServerThe portal server is placed between the client and the Tivoli EnterpriseMonitoring Server and enables retrieval, manipulation, and analysis of datafrom the monitoring agents. The Tivoli Enterprise Portal Server is thecentral repository for all user data.

Tivoli Enterprise Monitoring ServerThe monitoring server acts as a collection and control point for alertsreceived from the monitoring agents, and collects their performance andavailability data. The Tivoli Enterprise Monitoring Server is also arepository for historical data.

IBM Tivoli Enterprise ConsoleThe Tivoli Enterprise Console® is an optional component that acts as acentral collection point for events from a variety of sources, includingevents from other Tivoli software applications, Tivoli partner applications,custom applications, network management platforms, and relationaldatabase systems. You can view these events through the Tivoli EnterprisePortal (by using the event viewer), and you can forward events from IBMTivoli Monitoring situations to the Tivoli Enterprise Console component.

Schema Publication toolThis tool generates DDL scripts that can be used against a databasecapable of compression.

Agent Management ServicesYou can use IBM Tivoli Monitoring Agent Management Services to manage theWarehouse Summarization and Pruning Agent.

Agent Management Services is available for the following IBM Tivoli MonitoringOS agents: Windows, Linux, and UNIX. The services are designed to keep theWarehouse Summarization and Pruning Agent available, and to provideinformation about the status of the product to the Tivoli Enterprise Portal. Formore information about Agent Management Services, see the IBM Tivoli MonitoringAdministrator's Guide, "Agent Management Services" chapter.

User interface optionsInstallation of the base software and other integrated applications provides thefollowing interfaces that you can use to work with your resources and data.

The following interfaces are available:

Tivoli Enterprise Portal user interfaceYou can run the Tivoli Enterprise Portal as a desktop application or abrowser application. The client interface is a graphical user interface (GUI)based on Java on a Windows or Linux workstation. The browserapplication is automatically installed with the Tivoli Enterprise PortalServer. The desktop application is installed by using the Tivoli Monitoringinstallation media or with a Java Web Start application. To start the TivoliEnterprise Portal browser client in your Internet browser, enter the URL fora specific Tivoli Enterprise Portal browser client installed on your Webserver.

2 Warehouse Summarization and Pruning Agent User's Guide

Manage Tivoli Enterprise Monitoring Services windowYou can use the window for the Manage Tivoli Enterprise MonitoringServices utility to configure the agent and start Tivoli services notdesignated to start automatically.

IBM Tivoli Enterprise ConsoleYou can use the Tivoli Enterprise Console to help ensure the optimalavailability of an IT service for an organization. The Tivoli EnterpriseConsole is an event management application that integrates system,network, database, and application management.

Chapter 1. Overview of the agent 3

Chapter 2. Requirements for the monitoring agent

To install and configure the Warehouse Summarization and Pruning Agent, use theprocedures in the IBM Tivoli Monitoring Installation and Setup Guide .

Requirements for the Summarization and Pruning agentIn addition to the requirements described in the IBM Tivoli Monitoring Installationand Setup Guide, the Warehouse Summarization and Pruning Agent has thefollowing requirements:v The monitoring agent runs on these operating systems:

– AIX® 5.2 (32/64 bit)– AIX 5.3 (32/64 bit)– AIX 6.1 (64 bit)– Solaris V9 (SPARC) (32/64 bit)– Solaris V10 (SPARC) (64 bit)– HP-UX 11.23 and 11.31 on Itanium2– Windows 2000 Server– Windows 2000 Advanced Server– Windows 2003 Server SE (32 bit) with Service Pack 1 or higher– Windows 2003 Server SE (64 bit)– Windows Server 2008 SE (32 bit)– Windows Server 2008 EE (32 bit)– Red Hat Enterprise and Desktop Linux 4 for Intel– Red Hat Enterprise Linux 4 for AMD64/EM64T– Red Hat Enterprise Linux 4.0 for z/Series 31-bit– Red Hat Enterprise Linux 4.0 for z/Series 64-bit– Red Hat Enterprise and Desktop Linux 5 for Intel– Red Hat Enterprise Linux 5 for AMD64/EM64T– Red Hat Enterprise Linux 5.0 for z/Series 31-bit– Red Hat Enterprise Linux 5.0 for z/Series 64-bit– SUSE Linux Enterprise Server 9 for Intel– SUSE Linux Enterprise Server 9 for zSeries® 31-bit– SUSE Linux Enterprise Server 9 for zSeries 64-bit– SUSE Linux Enterprise Server 10 for Intel– SUSE Linux Enterprise Server 10 for zSeries 64-bit– SUSE Linux Enterprise Server 11 for Intel– SUSE Linux Enterprise Server 11 for zSeries 64-bit– Asianux 2.0 for Intel (32 bit)– Asianux 3.0 for Intel (32 bit)– Red Flag 4.1 for Intel (32 bit)If running this agent on a Windows operating system, the User ID must haveAdministrator privileges.


v A single computer that hosts the hub monitoring server, portal server, and amonitoring agent requires approximately 300 MB of space. A monitoredcomputer that hosts only the monitoring agent requires approximately 30 MB ofspace, including the specific enablement code for the monitoring agent. Morespace is required for each additional monitoring agent that you deploy on themonitored computer.

After you install the IBM Tivoli Monitoring Version 6.2.3 and the Tivoli EnterprisePortal, you install the following software that is required for WarehouseSummarization and Pruning Agent to operate:v Warehouse Summarization and Pruning Agentv Warehouse Summarization and Pruning Agent Support for Tivoli Enterprise

Monitoring Serverv Warehouse Summarization and Pruning Agent Support for Tivoli Enterprise

Portal Serverv Warehouse Summarization and Pruning Agent Support for Tivoli Enterprise

Portal

Note: If you are upgrading to IBM Tivoli Monitoring Version 6.2.3 from a previousrelease of IBM Tivoli Monitoring and the Warehouse Summarization and PruningAgent is already installed, you might need to install these features to obtain theself monitoring features.

Silent installation: If you are performing a silent installation using a response file,see the IBM Tivoli Monitoring Installation and Setup Guide, "Performing a silentinstallation of IBM Tivoli Monitoring."

To use the search function for this agent's online help, ensure that you haveselected the IBM Eclipse help server check box when installing the TivoliEnterprise Portal Server. The 'Searching Agent Help' topic in this agent's onlinehelp contains a link to the Eclipse help, where the search function is enabled. Fromthe Table of Contents in the left-hand pane of the help, select the 'Searching AgentHelp' topic to find the link to the Eclipse help in the right-hand pane.

Note: When using the itmcmd config command to configure this monitoring agent,note that the command line does not have a validation mechanism like the GUIdoes.

Disable data warehouse log tablesWith IBM Tivoli Monitoring Version 6.2.3 Fix Pack 1, there is now the ability todisable the creation of the data warehouse log tables so that fewer databaseresources are needed. This is the now the default configuration for both theWarehouse Proxy Agent and the Summarization and Pruning Agents. If upgradingfrom an existing installation, you can truncate the existing tables in the database toallow their storage space to be reclaimed.

About this task

If you want to revert to the previous behavior the configuration files need to beedited. For the Summarization and Pruning Agent, edit the Summarization andPruning Agent configuration file (sy.ini on UNIX and Linux systems, KSYENV onWindows systems) and change the variable KSY_WHLOG_ENABLE to Y. Thedefault value is N.


Chapter 3. Workspaces reference

A workspace is the working area of the Tivoli Enterprise Portal applicationwindow. The Navigator tree that is displayed at the left of the workspace containsa list of the workspaces provided by the agent.

About workspaces

A workspace is the working area of the Tivoli Enterprise Portal applicationwindow. Use the Navigator tree that is displayed at the left of the workspace toselect the workspace you want to see. As part of the application window, the rightside of the status bar shows the Tivoli Enterprise Portal Server name and portnumber to which the displayed information applies and the ID of the current user.

When you select an item in the Navigator tree, a default workspace is displayed.When you right-click a Navigator item, a menu that includes a Workspace item isdisplayed. The Workspace item contains a list of workspaces for that Navigatoritem. Each workspace has at least one view. Some views have links to otherworkspaces. You can also use the Workspace Gallery tool as described in the IBMTivoli Monitoring User's Guide to open workspaces.

The workspaces in the Navigator are shown in a Physical view that shows yourenterprise as a physical mapping or a dynamically populated logical view that isagent-specific. You can also create a Logical view. The Physical view is the defaultview.

This monitoring agent provides predefined workspaces. You cannot modify ordelete the predefined workspaces, but you can create new workspaces by editingthem and saving the changes with a different name.

A table view within a workspace corresponds to a group of attributes; the columnsin the table view show some or all of the attributes available in the attribute group.

Additional information about workspaces

For more information about creating, customizing, and working with workspaces,see the IBM Tivoli Monitoring User's Guide

For a list of the predefined workspaces for this monitoring agent and a descriptionof each workspace, see Predefined workspaces and the information about eachindividual workspace.

Some attribute groups for this monitoring agent might not be represented in thepredefined workspaces or views for this agent. For a full list of the attributegroups, see “Attribute groups for the Warehouse Summarization and PruningAgent” on page 11.


Predefined workspacesThe Warehouse Summarization and Pruning Agent provides predefinedworkspaces, which are organized by Navigator item.v Warehouse Summarization and Pruning Agent Navigator item

– Warehouse Summarization and Pruning Agent workspacev Configuration Navigator item

– Configuration workspace– Connectivity workspace

v Statistics Navigator item– Statistics workspace– Work Completed workspace

Workspace descriptionsEach workspace description provides information about the workspace such as thepurpose and a list of views in the workspace.

Workspaces are listed under Navigator items.

Warehouse Summarization and Pruning Agent Navigator itemThe workspace descriptions are organized by the Navigator item to which theworkspaces are relevant.

Warehouse Summarization and Pruning Agent workspaceThis workspace displays the status of the Summarization and Pruningagent.

This workspace contains the following views:

Top Ten Tables by Run LengthDisplays the top 10 tables by run length of the most recent run ofthe Summarization and Pruning Agent.

ConnectivityDisplays the status of the connectivity to the Tivoli EnterprisePortal Server and to the warehouse database.

Errors Details the errors that have occurred during Summarization andPruning. If applicable, the SQL State and SQL Code are provided.The SQL Code is database specific and documented by thedatabase vendor. By default, the most recent 100 errors aredisplayed. The number of errors displayed can be changed via theKSY_NODE_ERROR_UNITS configuration value and can also bechanged via the agent configuration panel "Maximum number ofnode errors to display" setting.

Configuration Navigator itemThe workspace descriptions are organized by the Navigator item to which theworkspaces are relevant.

Configuration workspaceProvides configuration data for the Summarization and Pruning Agent.



Agent ConfigurationDisplays the configuration data for the Summarization andPruning Agent.

Scheduling ConfigurationDisplays the scheduling configuration data for the Summarizationand Pruning Agent.

Log ConfigurationDisplays the log table pruning configuration data for theSummarization and Pruning Agent.

Connectivity workspaceThis workspace provides the connectivity information for theSummarization and Pruning Agent.


TEPS ConnectivityDisplays the Tivoli Enterprise Portal Server connectivityinformation and status.

Database ConnectivityDisplays the database connectivity information and status.

Statistics Navigator itemThe workspace descriptions are organized by the Navigator item to which theworkspaces are relevant.

Statistics workspaceProvides the Summarization and Pruning run length statistics.


Run LengthDisplays the total run length of the last few Summarization andPruning runs on the system. By default, only the last 10 runs aredisplayed. This can be changed via theKSY_SUMMARIZATION_UNITS configuration value and can alsobe configured in the agent configuration panel "Maximum numberof Summarization and Pruning runs to display" setting.

Table Run LengthDisplays the run length for each table of the last Summarizationand Pruning run on the system.

Errors Details the errors that have occurred during Summarization andPruning. By default, only the 100 most recent errors are displayed.This can be changed via the KSY_NODE_ERROR_UNITSconfiguration value and can also be configured in the agentconfiguration panle "Maximum number of node errors to display"setting.

Work Completed workspaceThis workspace provides statistics about the completed work by theSummarization and Pruning Agent.


Rows SummarizedDisplays the total number of rows summarized per run by theSummarization and Pruning Agent over the past few runs. By

Chapter 3. Workspaces reference 9

default, only the most 10 recent runs are displayed. This can bechanged via the KSY_SUMMARIZATION_UNITS configurationvalue and can also be configured via the agent configuration panel"Maximum number of Summarization and Pruning runs todisplay" setting.

Table Rows SummarizedDisplays the total number of rows summarized per table bySummarization and Pruning Agent for the most recent run. Rowsare sorted by the number of rows summarized (tables with norows summarized are excluded).

Rows PrunedDisplays the total number of rows pruned per run by theSummarization and Pruning Agent over the past few runs. Thiscan be changed via the KSY_SUMMARIZATION_UNITSconfiguration value and can also be configured via the agentconfiguration panel "Maximum number of Summarization andPruning runs to display" setting. The number of runs to display, bydefault, is 10. .

Table Rows PrunedDisplays the total number of rows pruned per table bySummarization and Pruning Agent for the most recent run. Rowsare sorted by the number of rows pruned (tables with no rowspruned are excluded).


Chapter 4. Attributes reference

Attributes are the application properties that are being measured and reported bythe Warehouse Summarization and Pruning Agent.

Attributes are organized into groups according to their purpose. The attributes in agroup can be used in the following two ways:v Chart or table views

Attributes are displayed in chart and table views. The chart and table views usequeries to specify which attribute values to request from a monitoring agent.You use the Query editor to create a query, modify an existing query, or applyfilters and set styles to define the content and appearance of a view based on anexisting query.

v SituationsYou use attributes to create situations that monitor the state of your operatingsystem, database, or application. A situation describes a condition you want totest. When you start a situation, the Tivoli Enterprise Portal compares the valuesyou have assigned to the situation attributes with the values collected by theWarehouse Summarization and Pruning Agent and registers an event if thecondition is met. You are alerted to events by indicator icons that are displayedin the Navigator.

Additional information about attributes

For more information about using attributes and attribute groups, see the IBMTivoli Monitoring User's Guide.

For a list of the attribute groups, a list of the attributes in each attribute group, anddescriptions of the attributes for this monitoring agent, see “Attribute groups forthe Warehouse Summarization and Pruning Agent” and “Attributes in eachattribute group” on page 12.

Attribute groups for the Warehouse Summarization and Pruning AgentThe Warehouse Summarization and Pruning agent contains the following attributegroups. The table name depends on the maximum table name limits of the targetdatabase being used for the Tivoli Data Warehouse. If the maximum name is 30characters, then any warehouse table name longer than 30 characters is shortenedto 30 characters.v Attribute group name: Connectivity

– Table name: KSYCONNECT– Warehouse table name: KSYCONNECT or KSY_CONNECTIVITY

v Attribute group name: Node Failures– Table name: KSYNODE– Warehouse table name: KSYNODE or KSY_NODE FAILURES

v Attribute group name: Summarization Config– Table name: KSYCONFIG– Warehouse table name: KSYCONFIG or KSY_SUMMARIZATION CONFIG

v Attribute group name: Summarization Statistics


– Table name: KSYSUMMSTA– Warehouse table name: KSYSUMMSTA or KSY_SUMMARIZATION

STATISTICSv Attribute group name: Table Statistics

– Table name: KSYTABLE– Warehouse table name: KSYTABLE or KSY_TABLE STATISTICS

The remaining sections of this chapter contain descriptions of these attributegroups, which are listed alphabetically. The following information is provided foreach attribute group:

Historical groupWhether the attribute group is a historical type that you can roll off to adata warehouse

Attribute descriptionsDescription, type, and Warehouse name for each attribute in the attributegroup

Some attributes are designated as key attributes. A key attribute is anattribute that is used in warehouse aggregation to identify rows of datathat represent the same object.

Attributes in each attribute groupAttributes in each Warehouse Summarization and Pruning Agent attribute groupcollect data that the agent uses for monitoring.

The descriptions of the attribute groups contain the following information:

Historical groupWhether the attribute group is a historical type that you can roll off to adata warehouse.

Attribute descriptionsDescription, type, and Warehouse name (if applicable) for each attribute inthe attribute group.

Some attributes are designated as key attributes. A key attribute is anattribute that is used in warehouse aggregation to identify rows of datathat represent the same object.

Connectivity attribute groupThis attribute group monitors connectivity of Summarization and Pruning agent tothe Tivoli Enterprise Portal Server and the Warehouse database.

Historical groupThis attribute group is eligible for use with Tivoli Data Warehouse.

Attribute descriptions

The following list contains information about each attribute in theConnectivity attribute group:

Node attribute - This attribute is a key attribute.

DescriptionThe managed system name of the agent.

Type


String

Warehouse nameNODE

Timestamp attribute

DescriptionThe local time at the agent when the data was collected.

Type

String

Warehouse nameTIMESTAMP

TEPS Host Name attribute

DescriptionHost name for the Tivoli Enterprise Portal Server that theagent obtains configuration settings from.

Type

String

Warehouse nameTEPS_HOST_NAME or TEPSHOST

TEPS Port attribute

DescriptionPort number for the Tivoli Enterprise Portal Server that theagent obtains configuration settings from.

Type

Integer (32-bit numeric property) with enumerated values.The strings are displayed in the Tivoli Enterprise Portal.The warehouse and queries return the values shown inparentheses. The following values are defined:v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)

Any other values will display the actual value returned bythe agent in the Tivoli Enterprise Portal.

Warehouse nameTEPS_PORT or TEPSPORT

Database Type attribute

DescriptionType of database being used for warehousing.

Type

Integer with enumerated values. The strings are displayedin the Tivoli Enterprise Portal. The warehouse and queriesreturn the values shown in parentheses. The followingvalues are defined:v Unknown (0)v DB2 (1)v Microsoft SQL Server (2)

Chapter 4. Attributes reference 13

v Oracle (3)v DB2 z/OS (4)


Warehouse nameDATABASE_TYPE or DBTYPE

URL attribute

DescriptionThe JDBC Database URL.

Type

String

Warehouse nameURL

Driver attribute

DescriptionFully qualified driver for database connection.

Type

String

Warehouse nameDRIVER

Driver Version attribute

DescriptionVersion of driver being used.

Type

String

Warehouse nameDRIVER_VERSION or DRIVERVER

Database Version attribute

DescriptionVersion of database being used.

Type

String

Warehouse nameDATABASE_VERSION or DBVERSION

Classpath attribute

DescriptionClasspath used to access database.

Type

String

Warehouse nameCLASSPATH

TEPS Connectivity attribute


DescriptionWhether there is connectivity to the Tivoli Enterprise PortalServer.

Type

Integer with enumerated values. The strings are displayedin the Tivoli Enterprise Portal. The warehouse and queriesreturn the values shown in parentheses. The followingvalues are defined:v No (0)v Yes (1)


Warehouse nameTEPS_CONNECTIVITY or TEPSCONNCT

DB Connectivity attribute

DescriptionWhether there is connectivity to the database. Theinformation is cached by default for 10 minutes. This canbe changed via the KSY_CACHE_MINS configurationvalue and also via the agent configuration panel "DatabaseConnectivity Cache Time" setting.

Type



Warehouse nameDB_CONNECTIVITY or DBCONNECT

Node Failures attribute groupThis attribute group displays node errors occurring during Summarization andPruning runs.


Attribute descriptionsThe following list contains information about each attribute in the agentoutput log attribute group:



Type

String


Warehouse nameNODE

Timestamp attribute


Type

String


Failed System attribute

DescriptionName of failing node.

Type

String

Warehouse nameFAILED_SYSTEM or FAILEDSYS

Product Code attribute - This attribute is a key attribute.

DescriptionProduct code that the failure is occuring on.

Type

String

Warehouse namePRODUCT_CODE or PRODCODE

Timezone Diff attribute

DescriptionTimezone difference for the node (not the agent).

Type



Warehouse nameTIMEZONE_DIFF or TZDIFF

Table Name attribute - This attribute is a key attribute.

DescriptionName of table containing failed node.

Type

String


Warehouse nameTABLE_NAME or TABLENAME

Attribute Group Name attribute

DescriptionName of attribute group containing failed node.

Type

String

Warehouse nameATTRIBUTE_GROUP_NAME or ATTRIBNAME

Error Timestamp attribute

DescriptionTime that exception occurred on Summarization andPruning.

Type

Timestamp

Warehouse nameERROR_TIMESTAMP or ERRORTIME

Error Message attribute

DescriptionDescription of error that occurred.

Type

String

Warehouse nameERROR_MESSAGE or ERRORMSG

SQL Code attribute

DescriptionSQL Code of error, if appropriate. The SQL Code is thedatabase specific error code and is documented by thedatabase vendor. The SQL Code is the RDBMS specificerror code, documented by the RDBMS vendor.

Type



Warehouse nameSQL_CODE or SQLCODE

SQL State attribute

DescriptionSQL State of error, if appropriate.


Type

String

Warehouse nameSQL_STATE or SQLSTATE

Summarization Config attribute groupThis attribute group displays current configuration for the Summarization andPruning agent.


Attribute descriptionsThe following list contains information about each attribute in the agenttrace log attribute group:



Type

String

Warehouse nameNODE

Timestamp attribute


Type

String


Fixed Frequency attribute

DescriptionNumber of days between Summarization and Pruningruns.

Type



Warehouse nameFIXED_FREQUENCY or FIXEDFREQ

Fixed Scheduled Time attribute


DescriptionTime that the summarization and pruning agent will run iffixed scheduling is configured.

Type

String

Warehouse nameFIXED_SCHEDULED_TIME or FIXEDTIME

Fixed Scheduling attribute

DescriptionWhether fixed scheduling is enabled.

Type



Warehouse nameFIXED_SCHEDULING or FIXEDSCHDL

Flexible Scheduling Minutes attribute

DescriptionNumber of minutes between flexible runs.

Type



Warehouse nameFLEXIBLE_SCHEDULING_MINUTES or SCHDLMINUT

Flexible Scheduling Exceptions attribute

DescriptionComma delimited list of exceptions to flexible scheduling.

Type

String

Warehouse nameFLEXIBLE_SCHEDULING_EXCEPTIONS or SCHDLEXCEP

Num Threads attribute


DescriptionNumber of worker threads to use for Summarization andPruning.

Type



Warehouse nameNUM_THREADS or NUMTHREADS

Week Beginning attribute

DescriptionWhether the week starts on Monday or Sunday.

Type

Integer with enumerated values. The strings are displayedin the Tivoli Enterprise Portal. The warehouse and queriesreturn the values shown in parentheses. The followingvalues are defined:v Sunday (0)v Monday (1)


Warehouse nameWEEK_BEGINNING or WEEKBEGIN

Shifts Specified attribute

DescriptionWhether shifts are specified.

Type



Warehouse nameSHIFTS_SPECIFIED or SHIFTS

Vacation Enabled attribute

DescriptionWhether vacation days are specified.


Type



Warehouse nameVACATION_ENABLED or VACENABLED

Weekend Vacation attribute

DescriptionWhether weekend days are considered to be vacation days.

Type



Warehouse nameWEEKEND_VACATION or WEEKENDVAC

Vacation Days attribute

DescriptionA comma-delimited list of the days that are specified forvacation.

Type

String

Warehouse nameVACATION_DAYS or VACDAYS

Peak Shift Hours attribute

DescriptionComma delimited list of peak shift hours.

Type

String

Warehouse namePEAK_SHIFT_HOURS or PEAKSHIFT

Off Peak Shift Hours attribute

DescriptionComma delimited list of off peak shift hours.

Type


String

Warehouse nameOFF_PEAK_SHIFT_HOURS or OFFPKSHIFT

Prune WAREHOUSELOG attribute

DescriptionWhether to prune the WAREHOUSELOG.

Type



Warehouse namePRUNE_WAREHOUSELOG or PRUNEWHLOG

WAREHOUSELOG Time attribute

DescriptionAmount of time to keep WAREHOUSELOG data beforepruning.

Type



Warehouse nameWAREHOUSELOG_TIME or WHLOG

WAREHOUSELOG Units attribute

DescriptionUnits for the time to keep the WAREHOUSELOG.

Type

Integer with enumerated values. The strings are displayedin the Tivoli Enterprise Portal. The warehouse and queriesreturn the values shown in parentheses. The followingvalues are defined:v N/A (0)v Days (1)v Months (2)v Years (3)



Warehouse nameWAREHOUSELOG_UNITS or WHLOGUNITS

Prune WAREHOUSEAGGREGLOG attribute

DescriptionWhether to prune the WAREHOUSEAGGREGLOG.

Type



Warehouse namePRUNE_WAREHOUSEAGGREGLOG or PRUNEAGGLG

WAREHOUSEAGGREGLOG Time attribute

DescriptionAmount of time to keep WAREHOUSEAGGREGLOG databefore pruning.

Type



Warehouse nameWAREHOUSEAGGREGLOG_TIME or WHAGGLOG

WAREHOUSEAGGREGLOG Units attribute

DescriptionUnits for the time to keep the WAREHOUSEAGGREGLOG.

Type

Integer with enumerated values. The strings are displayedin the Tivoli Enterprise Portal. The warehouse and queriesreturn the values shown in parentheses. The followingvalues are defined:v N/A (0)v Days (1)v Months (2)v Years (3)



Warehouse nameWAREHOUSEAGGREGLOG_UNITS or WHAGGUNITS

Max Rows Per DB Transaction attribute

DescriptionNumber of rows per database transaction.

Type



Warehouse nameMAX_ROWS_PER_DB_TRANSACTION or MAXROWS

Timezone Source attribute

DescriptionWhether the agent or warehouse is the source of timezoneinformation.

Type

Integer with enumerated values. The strings are displayedin the Tivoli Enterprise Portal. The warehouse and queriesreturn the values shown in parentheses. The followingvalues are defined:v Agent (0)v Warehouse (1)


Warehouse nameTIMEZONE_SOURCE or TZSOURCE

Hourly Data Summarization attribute

DescriptionSummarize hourly data older than this many hours.

Type




Warehouse nameHOURLY_DATA_SUMMARIZATION or HOURLYDATA

Daily Data Summarization attribute

DescriptionSummarize daily data older than this many days.

Type



Warehouse nameDAILY_DATA_SUMMARIZATION or DAILYDATA

Next Work Time attribute

DescriptionNext time that the Summarization and Pruning agent isscheduled to work.

Type

Timestamp

Warehouse nameNEXT_WORK_TIME or NEXTWORK

Summarization and Pruning Rows attribute

DescriptionNumber of Summarization and Pruning rows shown inworkspace.

Type



Warehouse nameSUMMARIZATION_AND_PRUNING_ROWS orSUMMROWS

Error Rows attribute

DescriptionNumber of errors shown in workspace.

Type




Warehouse nameERROR_ROWS or ERRORROWS

Connectivity Cache Minutes attribute

DescriptionNumber of minutes to cache database connectivity data.

Type



Warehouse nameCONNECTIVITY_CACHE_MINUTES or CONNCACHE

Batch Mode attribute

DescriptionWhether Single System or Multiple System batch mode isin use.

Type

Integer with enumerated values. The strings are displayedin the Tivoli Enterprise Portal. The warehouse and queriesreturn the values shown in parentheses. The followingvalues are defined:v Single Managed System (0)v Multiple Managed Systems (1)


Warehouse nameBATCH_MODE or BATCHMODE

Database Compression attribute

DescriptionDatabase Compression. It can be set using the variableKSY_DB_COMPRESSION. The default value is N.

Type




Warehouse nameDATABASE_COMPRESSION or DBCOMPRESS

Summarization Statistics attribute groupThis attribute group monitors Summarization and Pruning run statistics.


Attribute descriptionsThe following list contains information about each attribute in the controldomain attribute group:



Type

String

Warehouse nameNODE

Timestamp attribute


Type

String


Start Time attribute

DescriptionLocal time that the Summarization and Pruning run began.

Type

Timestamp

Warehouse nameSTART_TIME or STARTTIME

End Time attribute

DescriptionLocal time that the Summarization and Pruning run ended.

Type


Timestamp

Warehouse nameEND_TIME or ENDTIME

Run Length (hour) attribute

DescriptionLength of Summarization and Pruning run in hours.

Type

Real number (32-bit gauge) with 2 decimal places ofprecision with enumerated values. The strings aredisplayed in the Tivoli Enterprise Portal. The warehouseand queries return the values shown in parentheses. Thefollowing values are defined:v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)


Warehouse nameRUN_LENGTH or RUNLENGTH

Thread Pool Size attribute

DescriptionSize of thread pool.

Type



Warehouse nameTHREAD_POOL_SIZE or THREADPOOL

Active Threads attribute

DescriptionNumber of threads active for Summarization and PruningAgent.

Type




Warehouse nameACTIVE_THREADS or ACTVTHREAD

Rows Pruned attribute

DescriptionNumber of rows pruned.

Type

Integer (32-bit gauge) with enumerated values. The stringsare displayed in the Tivoli Enterprise Portal. Thewarehouse and queries return the values shown inparentheses. The following values are defined:v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)


Warehouse nameROWS_PRUNED or PRUNED

Rows Summarized attribute

DescriptionNumber of rows summarized.

Type



Warehouse nameROWS_SUMMARIZED or SUMMARIZED

Failures attribute

DescriptionTotal number of summarization and pruning failures thatoccurred.

Type



Warehouse nameFAILURES


Pruning Failures attribute

DescriptionNumber of failures which occurred during pruning.

Type



Warehouse namePRUNING_FAILURES or PRUNEFAIL

Summarization Failures attribute

DescriptionNumber of failures that occurred during summarization.

Type



Warehouse nameSUMMARIZATION_FAILURES or SUMMFAIL

Table Statistics attribute groupThis attribute group displays individual table statistics for Summarization andPruning runs.


Attribute descriptionsThe following list contains information about each attribute in the host cpuattribute group:



Type

String

Warehouse nameNODE

Timestamp attribute



Type

String


Start Time attribute

DescriptionLocal time that the Summarization and Pruning began forthis table.

Type

Timestamp

Warehouse nameSTART_TIME or STARTTIME

End Time attribute

DescriptionLocal time that the Summarization and Pruning ended forthis table.

Type

Timestamp

Warehouse nameEND_TIME or ENDTIME

Run Length (min) attribute

DescriptionLength of Summarization and Pruning for this table inminutes.

Type

Real number (32-bit gauge) with 1 decimal places ofprecision with enumerated values. The strings aredisplayed in the Tivoli Enterprise Portal. The warehouseand queries return the values shown in parentheses. Thefollowing values are defined:v Value Exceeds Maximum (2147483647)v Value Exceeds Minimum (-2147483648)


Warehouse nameRUN_LENGTH or RUNLENGTH

Product Code attribute - This attribute is a key attribute.

DescriptionProduct code for this table.

Type

String


Warehouse namePRODUCT_CODE or PRODCODE

Rows Updated attribute

DescriptionNumber of summary rows updated.

Type



Warehouse nameROWS_UPDATED or UPDATED

Rows Created attribute

DescriptionNumber of summary rows created.

Type



Warehouse nameROWS_CREATED or CREATED

Managed Systems Processed attribute

DescriptionNumber of managed systems processed.

Type



Warehouse nameMANAGED_SYSTEMS_PROCESSED or MNGSYSTEMS

Table Name attribute - This attribute is a key attribute.


DescriptionName of table being summarized and pruned.

Type

String

Warehouse nameTABLE_NAME or TABLENAME

Attribute Group Name attribute

DescriptionName of attribute group for this table.

Type

String

Warehouse nameATTRIBUTE_GROUP_NAME or ATTRIBNAME

Rows Pruned attribute

DescriptionNumber of rows pruned.

Type



Warehouse nameROWS_PRUNED or PRUNED

Rows Summarized attribute

DescriptionNumber of rows summarized.

Type



Warehouse nameROWS_SUMMARIZED or SUMMARIZED

Failures attribute


DescriptionTotal number of summarization and pruning failures thatoccurred in this table.

Type



Warehouse nameFAILURES

Pruning Failures attribute

DescriptionNumber of failures which occurred during pruning for thistable.

Type



Warehouse namePRUNING_FAILURES or PRUNEFAIL

Summarization Failures attribute

DescriptionNumber of failures which occurred during summarizationfor this table.

Type



Warehouse nameSUMMARIZATION_FAILURES or SUMMFAIL


Disk capacity planning for historical dataDisk capacity planning for a monitoring agent is a prediction of the amount of diskspace to be consumed for each attribute group with historical data that is beingcollected. Required disk storage is an important factor when you are defining datacollection rules and your strategy for historical data collection.

The Capacity planning for historical data table provides the following informationrequired to calculate disk space for this agent:

Table Table name as it is displayed in the warehouse database, if the attributegroup is configured to be written to the warehouse. The table name listedhere corresponds to the table name in “Attribute groups for the WarehouseSummarization and Pruning Agent” on page 11.

Attribute groupName of the attribute group used to create the table in the warehousedatabase if it is short enough to fit in the table naming constraints of thedatabase being used for the warehouse. The attribute group name listedhere corresponds to the Warehouse table name in “Attribute groups for theWarehouse Summarization and Pruning Agent” on page 11.

Bytes per row (agent)Estimate of the record length for each row or instance written to the agentdisk for historical data collection. This estimate can be used for agent diskspace planning purposes.

Database bytes per row (warehouse)Estimate of the record length for detailed records written to the warehousedatabase, if the attribute group is configured to be written to thewarehouse. Detailed records are records that have been uploaded from theagent for long-term historical data collection. This estimate can be used forwarehouse disk-space planning purposes.

Aggregate bytes per row (warehouse)Estimate of the record length for aggregate records written to thewarehouse database, if the attribute group is configured to be written tothe warehouse. Aggregate records are created by the Summarization agentfor attribute groups that have been configured for summarization. Thisestimate can be used for warehouse disk-space planning purposes.

In addition to the information in the tables, you must know the number of rows ofdata that you plan to collect. An attribute group can have single or multiple rowsof data depending on the application environment that is being monitored. Forexample, if your attribute group is monitoring each processor in your computerand you have a dual processor computer, the number of rows is two.

The following table contains capacity planning information for the data logged byWarehouse Summarization and Pruning Agent.

Table 1. Capacity planning for historical data logged by component

Table Attribute group

Bytes perinstance(agent)

Databasebytes perinstance(warehouse)

Aggregatebytes perinstance(warehouse)

KSYCONNECT KSY_CONNECTIVITY 1212 1230 1267

KSYNODE KSY_NODE_FAILURES 1341 1350 1387


Table 1. Capacity planning for historical data logged by component (continued)

Table Attribute group

Bytes perinstance(agent)

Databasebytes perinstance(warehouse)

Aggregatebytes perinstance(warehouse)

KSYCONFIG KSY_SUMMARIZATION_CONFIG 964 992 1029

KSYSUMMSTA KSY_SUMMARIZATION_STATISTICS 140 158 441

KSYTABLE KSY_TABLE_STATISTICS 292 314 714

For more information about historical data collection, see the IBM Tivoli MonitoringAdministrator's Guide.


Chapter 5. Situations reference

A situation is a logical expression involving one or more system conditions.Situations are used to monitor the condition of systems in your network. You canmanage situations from the Tivoli Enterprise Portal by using the Situation Editor orfrom the command-line interface using the tacmds for situations. You can manageprivate situations in the private configuration XML file.

About situations

The monitoring agents that you use to monitor your system environment include aset of predefined situations that you can use as-is. You can also create newsituations to meet your requirements.

Predefined situations contain attributes that check for system conditions commonto many enterprises. Using predefined situations can improve the speed withwhich you can begin using the Warehouse Summarization and Pruning Agent. Youcan change the conditions or values being monitored by a predefined situation tothe conditions or values best suited to your enterprise.

You can display predefined situations and create your own situations using theSituation editor. The left panel of the Situation editor initially lists the situationsassociated with the Navigator item that you selected. When you click a situationname or create a situation, the right panel opens with the following tabs:

FormulaFormula describing the condition being tested.

DistributionList of managed systems (operating systems, subsystems, or applications)to which the situation can be distributed. All the WarehouseSummarization and Pruning Agent managed systems are assigned bydefault.

Expert adviceComments and instructions to be read in the event workspace.

ActionCommand to be sent to the system.

EIF Customize forwarding of the event to an Event Integration Facility receiver.(Available when the Tivoli Enterprise Monitoring Server has beenconfigured to forward events.)

Until Options to close the event after a period of time, or when another situationbecomes true.

Additional information about situations

The IBM Tivoli Monitoring User's Guide contains more information about predefinedand custom situations and how to use them to respond to alerts.

For a list of the predefined situations and information about each individualsituation for this monitoring agent, see “Predefined situations” on page 38.


Predefined situationsThe monitoring agent does not contain predefined situations.


Chapter 6. Take Action commands reference

Take Action commands can be run from the portal client or included in a situationor a policy.

About Take Action commands

When included in a situation, the command runs when the situation becomes true.A Take Action command in a situation is also referred to as reflex automation. Whenyou enable a Take Action command in a situation, you automate a response tosystem conditions. For example, you can use a Take Action command to send acommand to restart a process on the managed system or to send a text message toa cell phone.

In advanced automation, policies are used to take actions, schedule work, andautomate manual tasks. A policy comprises a series of automated steps calledactivities that are connected to create a workflow. After an activity is completed,the Tivoli Enterprise Portal receives return-code feedback, and advancedautomation logic responds with subsequent activities that are prescribed by thefeedback.

A basic Take Action command shows the return code of the operation in a messagebox that is displayed after the action is completed or in a log file. After you closethis window, no further information is available for this action.

Additional information about Take Action commands

For more information about working with Take Action commands, see the IBMTivoli Monitoring User's Guide.

Predefined Take Action commandsNot all agents have predefined Take Action commands. But you can create TakeAction commands for any agent.


Chapter 7. Policies reference

Policies are used as an advanced automation technique for implementing morecomplex workflow strategies than you can create through simple automation. Allagents do not provide predefined policies, but you can create policies for anyagent.

About policies

A policy is a set of automated system processes that can take actions, schedulework for users, or automate manual tasks. You use the Workflow Editor to designpolicies. You control the order in which the policy executes a series of automatedsteps, which are also called activities. Policies are connected to create a workflow.After an activity is completed, the Tivoli Enterprise Portal receives return-codefeedback, and advanced automation logic responds with subsequent activitiesprescribed by the feedback.

Additional information about policies

This monitoring agent does not provide predefined policies. For more informationabout working with policies, see the IBM Tivoli Monitoring User's Guide.

For information about using the Workflow Editor, see the IBM Tivoli MonitoringAdministrator's Guide or the Tivoli Enterprise Portal online help.


Chapter 8. Troubleshooting

Problems can be related to IBM Tivoli Monitoring or the specific agent that you areusing.

See the IBM Tivoli Monitoring Troubleshooting Guide for general troubleshootinginformation. Also see “Support information” on page 65 for other problem-solvingoptions.

You can resolve some problems by ensuring that your system matches the systemrequirements listed in the Prerequisites topic for the agent in the informationcenter, or in the Requirements topic of the agent user's guide.

The following activities can help you find a solution to the problem you arehaving:v “Gathering product information for IBM Software Support”v “Using logging” on page 44v “Consulting the lists of identified problems and workarounds” on page 44

Gathering product information for IBM Software Support

Before contacting IBM Software Support about a problem you are experiencingwith this product, gather the information shown in Table 2.

Table 2. Information to gather before contacting IBM Software Support

Information type Description

Log files Collect trace log files from failing systems.Most logs are located in a logs subdirectoryon the host computer. See “Principal tracelog files” on page 45 for lists of all trace logfiles and their locations. See the IBM TivoliMonitoring User's Guide for generalinformation about the IBM Tivoli Monitoringenvironment.

Operating system Operating system version number and patchlevel

Messages Messages and other information displayedon the screen

Version numbers for IBM Tivoli Monitoring Version number of the following members ofthe monitoring environment:

v IBM Tivoli Monitoring. Also provide thepatch level, if available.

v IBM Tivoli Monitoring for VirtualEnvironments Agent for Citrix XenServer

Screen captures Screen captures of incorrect output, if any

(UNIX systems only) Core dump files If the system stops on UNIX systems, collectthe core dump file from the install_dir/bindirectory, where install_dir is the directorywhere you installed the monitoring agent.


You can use the pdcollect tool to collect the most commonly used information froma system. This tool gathers log files, configuration information, versioninformation, and other data. See the "pdcollect tool" section in the "Tools" chapterof the IBM Tivoli Monitoring Troubleshooting Guide for more information about usingthis tool.

See http://www.ibm.com/support/entry/portal/Open_service_request/Software/Software_support_(general) for information about working with IBM SoftwareSupport.

Using logging

Logging is the primary troubleshooting feature in the Warehouse Summarizationand Pruning Agent. Logging refers to the text messages and trace data generated bythe Warehouse Summarization and Pruning Agent. Messages and trace data aresent to a file.

Trace data captures transient information about the current operating environmentwhen a component or application fails to operate as designed. IBM SoftwareSupport personnel use the captured trace information to determine the source ofan error or unexpected condition. See “Trace logging” for more information.

Consulting the lists of identified problems and workarounds

Known problems have been organized into types such as those in the following listto make them easier to locate:v Installation and configurationv General usage and operationv Display of monitoring datav Take Action commands

Information about symptoms and detailed workarounds for these types ofproblems is located in “Problems and workarounds” on page 57.

See the IBM Tivoli Monitoring Troubleshooting Guide for general troubleshootinginformation.

Trace loggingTrace logs are used to capture information about the operating environment whencomponent software fails to operate as designed.

The principal log type is the RAS (Reliability, Availability, and Serviceability) tracelog. These logs are in the English language only. The RAS trace log mechanism isavailable for all components of IBM Tivoli Monitoring. Most logs are located in alogs subdirectory on the host computer. See the following information to learn howto configure and use trace logging:v “Principal trace log files” on page 45v “Examples: Using trace logs” on page 49v “Setting RAS trace parameters by using the GUI” on page 51

Note: The documentation refers to the RAS facility in IBM Tivoli Monitoring as"RAS1."


http://www.ibm.com/support/entry/portal/Open_service_request/Software/Software_support_(general)

http://www.ibm.com/support/entry/portal/Open_service_request/Software/Software_support_(general)

IBM Software Support personnel use the information captured by trace logging totrace a problem to its source or to determine why an error occurred. Allcomponents in the IBM Tivoli Monitoring environment have a default tracing level.The tracing level can be changed on a per-component level to adjust the type oftrace information collected, the degree of trace detail, the number of trace logs tobe kept, and the amount of disk space used for tracing.

Overview of log file managementLog files have naming conventions.

Log file naming conventions

Table 3 provides the names, locations, and descriptions of RAS1 log files. The logfile names adhere to the following naming convention:

Windows systemshostname_productcode_program_HEXtimestamp-nn.log

Linux and UNIX systemshostname_productcode_HEXtimestamp-nn.log

where:

hostnameHost name of the computer where the monitoring component is running.

productcodeTwo-character product code. For Warehouse Summarization and PruningAgent, the product code is sy.

programName of the program being run.

HEXtimestampHexadecimal time stamp representing the time at which the programstarted.

nn Rolling log suffix.

Principal trace log filesTrace log files are located on various systems.

Table 3 contains locations, file names, and descriptions of trace logs that can helpdetermine the source of problems with agents.

Table 3. Trace log files for troubleshooting agents

System where log is located File name and path Description

On the Tivoli EnterpriseMonitoring Server

v Windows: The file in theinstall_dir\InstallITMpath

v UNIX: Thecandle_installation.logfile in theinstall_dir/logs path

v Linux: Thecandle_installation.logfile in theinstall_dir/logs path

Provides details aboutproducts that are installed.Note: Trace logging isenabled by default. Aconfiguration step is notrequired to enable thistracing.

Chapter 8. Troubleshooting 45

Table 3. Trace log files for troubleshooting agents (continued)



The

Warehouse_Configuration.log

file is in the followinglocation on Windowssystems:install_dir\InstallITM

Provides details about theconfiguration of datawarehousing for historicalreporting.


The name of the RAS log fileis as follows:

v Windows:install_dir\logs\hostname_ms_timestamp-nn.log

v UNIX:

install_dir/logs/hostname_ms_timestamp-nn.log

v Linux:

install_dir/logs/hostname_ms_timestamp-nn.log

Note: File names for RAS1logs include a hexadecimaltime stamp.

Also on UNIX systems, a logwith a decimal time stamp isprovided:

hostname_productcode_timestamp.log

and hostname_productcode_timestamp.pid nnnnn in theinstall_dir/logs path,where nnnnn is the processID number.

Traces activity on themonitoring server.




On the Tivoli EnterprisePortal Server

The name of the RAS log fileis as follows:

v Windows:

install_dir\logs\hostname _cq_HEXtimestamp-nn.log

v UNIX:

install_dir /logs/hostname_cq_HEXtimestamp-nn.log

v Linux:

install_dir /logs/hostname_cq_HEXtimestamp-nn.log

Note: File names for RAS1logs include a hexadecimaltime stamp.

Also on UNIX systems, a logwith a decimal time stamp isprovided:

hostname_productcode_timestamp .log

and hostname_productcode_timestamp.pidnnnnn in theinstall_dir/logs path,where nnnnn is the processID number.

Traces activity on the portalserver.

On the Tivoli EnterprisePortal Server

The teps_odbc.log file islocated in the following path:

v Windows:install_dir\InstallITM

v UNIX:install_dir/logs

v Linux:install_dir/logs

When you enable historicalreporting, this log file tracesthe status of the warehouseproxy agent.




On the computer that hoststhe monitoring agent

The RAS1 log files are asfollows:

v UNIX:

hostname_xi_instance_name_kxiagent_HEXtimestamp-nn.log

in the install_dir/logsdirectory

v Linux:

hostname_xi_instance_name_kxiagent_HEXtimestamp-nn.log

in the install_dir/logsdirectory

These logs are in thefollowing directories:

v UNIX: install_dir/logs

v Linux: install_dir/logs

On Linux systems, thefollowing additional logsare provided:– hostname_xi_timestamp

.log– hostname_xi_timestamp

.pidnnnnn

in the install_dir/logspath, where nnnnn isthe process ID number

Traces activity of themonitoring agent.




On the computer that hoststhe monitoring agent

The agent operations log filesare as follows:

instance_hostnameSY.LG0 isthe current log created whenthe agent was started.

instance_hostname_SY.LG1 isthe backup of the previouslog.

These logs are in thefollowing directorydepending on the operatingsystem that you are using:

v Linux: install_dir/logs

v UNIX: install_dir/logs

Shows whether the agentcould connect to themonitoring server. Showswhich situations are startedand stopped, and showsother events while the agentis running. A new version ofthis file is generated everytime the agent is restarted.

IBM Tivoli Monitoringgenerates one backup copyof the *.LG0 file with the tag.LG1. View the .LG1 tag tolearn the following detailsregarding the previousmonitoring session:

v Status of connectivity withthe monitoring server

v Situations that wererunning

v The success or failurestatus of Take Actioncommands

Definitions of variables:

v timestamp is a time stamp with a format that includes year (y), month (m), day (d), hour(h), and minute (m), as follows: yyyymmdd hhmm

v HEXtimestamp is a hexadecimal representation of the time at which the process wasstarted.

v install_dir represents the directory path where you installed the IBM Tivoli Monitoringcomponent. install_dir can represent a path on the computer that hosts the monitoringsystem, the monitoring agent, or the portal.

v instance refers to the name of the database instance that you are monitoring.

v instance_name refers to the name of the agent instance.

v hostname refers to the name of the computer on which the IBM Tivoli Monitoringcomponent runs.

v nn represents the circular sequence in which logs are rotated. this value includes a rangefrom 1 - 5, by default. The first is always retained because it includes configurationparameters.

v productcode specifies the product code, for example, um for Universal Agent or nt forWindows systems.

See the IBM Tivoli Monitoring Installation and Setup Guide for more informationabout the complete set of trace logs that are maintained on the monitoring server.

Examples: Using trace logsYou can open trace logs in a text editor to learn some basic facts about your IBMTivoli Monitoring environment.

IBM Software Support applies specialized knowledge to analyze trace logs todetermine the source of problems. The following examples are from the TivoliEnterprise Monitoring Server log.


Example oneThis excerpt shows the typical log for a failed connection between amonitoring agent and a monitoring server with the host name server1a:(Thursday, August 11, 2005, 08:21:30-{94C}kdcl0cl.c,105,"KDCL0_ClientLookup") status=1c020006, "location server unavailable",ncs/KDC1_STC_SERVER_UNAVAILABLE(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1157,"LookupProxy")Unable to connect to broker at ip.pipe:: status=0, "success",ncs/KDC1_STC_OK(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1402,"FindProxyUsingLocalLookup")Unable to find running CMS on CT_CMSLIST <IP.PIPE:#server1a>

Example twoThe following excerpts from the trace log for the monitoring server show thestatus of an agent, identified here as "Remote node." The name of thecomputer where the agent is running is SERVER5B:(42C039F9.0000-6A4:kpxreqhb.cpp,649,"HeartbeatInserter")Remote node SERVER5B:XI is ON-LINE. . . .(42C3079B.0000-6A4:kpxreqhb.cpp,644,"HeartbeatInserter")Remote node SERVER5B:XI is OFF-LINE.

See the following key points about the preceding excerpts:v The monitoring server appends the SY product code to the server name

to form a unique name (SERVER5B:XI ) for this instance of theWarehouse Summarization and Pruning Agent. By using this uniquename, you can distinguish multiple monitoring products that might berunning on SERVER5B.

v The log shows when the agent started (ON-LINE) and later stopped(OFF-LINE) in the environment.

v For the sake of brevity, an ellipsis (...) represents the series of trace logentries that were generated while the agent was running.

v Between the ON-LINE and OFF-LINE log entries, the agent wascommunicating with the monitoring server.

v The ON-LINE and OFF-LINE log entries are always available in thetrace log. All trace levels that are described in “Setting RAS traceparameters by using the GUI” on page 51 provide these entries.

On Windows systems, you can use the following alternate method to view tracelogs:1. In the Windows Start menu, click Program Files > IBM Tivoli Monitoring >

Manage Tivoli Enterprise Monitoring Services. The Manage Tivoli EnterpriseMonitoring Services window is displayed.

2. Right-click a component and click Advanced > View Trace Log in the menu.For example, if you want to view the trace log of the WarehouseSummarization and Pruning Agent, right-click the name of that agent in thewindow. You can also use the viewer to access remote logs.

Note: The viewer converts time stamps in the logs to a format that is easier toread.

RAS trace parametersPinpoint a problem by setting detailed tracing of individual components of themonitoring agent and modules


See “Overview of log file management” on page 45 to ensure that you understandlog rolling and can reference the correct log files when you manage log filegeneration.

Setting RAS trace parameters by using the GUIOn Windows systems, you can use the graphical user interface to set trace options.

About this task

The Warehouse Summarization and Pruning Agent uses RAS1 tracing andgenerates the logs described in Table 3 on page 45. The default RAS1 trace level isERROR. The default RAS1 trace level is ERROR.

Procedure1. Open the Manage Tivoli Enterprise Monitoring Services window.2. Select Advanced > Edit Trace Parms. The Tivoli Enterprise Monitoring Server

Trace Parameters window is displayed.3. Select a new trace setting in the pull-down menu in the Enter RAS1 Filters

field or type a valid string.v General error tracing. KBB_RAS1=ERRORv Intensive error tracing. KBB_RAS1=ERROR (UNIT:kqz ALL)

v Maximum error tracing. KBB_RAS1=ERROR (UNIT:kqz ALL) (UNIT:kra ALL)

Note: As this example shows, you can set multiple RAS tracing options in asingle statement.

4. Modify the value for Maximum Log Size Per File (MB) to change the log filesize (changes LIMIT value).

5. Modify the value for Maximum Number of Log Files Per Session to change thenumber of log files per startup of a program (changes COUNT value).

6. Modify the value for Maximum Number of Log Files Total to change thenumber of log files for all startups of a program (changes MAXFILES value).

7. Optional: Click Y (Yes) in the KDC_DEBUGd Setting menu to log informationthat can help you diagnose communications and connectivity problemsbetween the monitoring agent and the monitoring server. The KDC_DEBUG settingand the Maximum error tracing setting can generate a large amount of tracelogging. Use these settings only temporarily, while you are troubleshootingproblems. Otherwise, the logs can occupy excessive amounts of hard diskspace.

8. Click OK. You see a message reporting a restart of the monitoring agent so thatyour changes take effect.

What to do next

Monitor the size of the logs directory. Default behavior can generate a total of 45 -60 MB for each agent that is running on a computer. For example, each databaseinstance that you monitor can generate 45 - 60 MB of log data. See the "Procedure"section to learn how to adjust file size and numbers of log files to prevent loggingactivity from occupying too much disk space.

Regularly prune log files other than the RAS1 log files in the logs directory. Unlikethe RAS1 log files that are pruned automatically, other log types can growindefinitely, for example, the logs in Table 3 on page 45 that include a process IDnumber (PID).


Use collector trace logs as an additional source of troubleshooting information.

Note: The KDC_DEBUG setting and the Maximum error tracing setting can generate alarge amount of trace logging. Use these settings only temporarily while you aretroubleshooting problems. Otherwise, the logs can occupy excessive amounts ofhard disk space.

Manually setting RAS trace parametersYou can manually edit the RAS1 trace logging parameters.

About this task

The Warehouse Summarization and Pruning Agent uses RAS1 tracing andgenerates the logs described in Table 3 on page 45. The default RAS1 trace level isERROR. The default RAS1 trace level is ERROR.

Procedure1. Open the trace options file.

v install_dir\tmaitm6\KSYENV

v install_dir /config/sy.ini

2. Edit the line that begins with KBB_RAS1= to set trace logging preferences. Forexample, if you want detailed trace logging, set the Maximum Tracing option:KBB_RAS1=ERROR (UNIT:kqz ALL) (UNIT:kra ALL)

3. Edit the line that begins with KBB_RAS1_LOG= to manage the generation of logfiles:v MAXFILES: The total number of files that are to be kept for all startups of a

given program. When this value is exceeded, the oldest log files arediscarded. The default value is 9.

v LIMIT: The maximum size, in megabytes (MB) of a RAS1 log file. The defaultvalue is 5.

v IBM Software Support might guide you to modify the following parameters:– COUNT: The number of log files to keep in the rolling cycle of one program

startup. The default is 3.– PRESERVE: The number of files that are not to be reused in the rolling cycle

of one program startup. The default value is 1.

Note: The KBB_RAS1_LOG parameter also provides for the specification of thelog file directory, log file name, and the inventory control file directory andname. Do not modify these values or log information can be lost.

4. Restart the monitoring agent so that your changes take effect.

What to do next

Monitor the size of the logs directory. Default behavior can generate a total of 45 -60 MB for each agent that is running on a computer. For example, each databaseinstance that you monitor can generate 45 - 60 MB of log data. See the "Procedure"section to learn how to adjust file size and numbers of log files to prevent loggingactivity from occupying too much disk space.

Regularly prune log files other than the RAS1 log files in the logs directory. Unlikethe RAS1 log files that are pruned automatically, other log types can growindefinitely, for example, the logs in Table 3 on page 45 that include a process IDnumber (PID).


Use collector trace logs as an additional source of troubleshooting information.

Note: The KDC_DEBUG setting and the Maximum error tracing setting can generate alarge amount of trace logging. Use these settings only temporarily while you aretroubleshooting problems. Otherwise, the logs can occupy excessive amounts ofhard disk space.

Dynamic modification of trace settingsYou can dynamically modify the trace settings for an IBM Tivoli Monitoringcomponent, such as, Tivoli Enterprise Monitoring Server, Tivoli Enterprise PortalServer, most monitoring agents, and other components. You can access thesecomponents, with the exception of a few monitoring agents, from the tracingutility.

Dynamic modification of the trace settings is the most efficient method, becauseyou can do it without restarting the component. Settings take effect immediately.Modifications by this method are not persistent.

Note: When the component is restarted, the trace settings are read again from the.env file. Dynamically modifying these settings does not change the settings in the.env files. To modify these trace settings permanently, modify them in the .envfiles.

ras1

Run this command to modify the trace settings for a Tivoli Monitoring component.

The syntax is as follows:ras1 set|list(UNIT|COMP: class_name ANY|ALL|Detail|ERROR|Flow|INPUT|Metrics|OUTPUT|STATE){(UNIT|COMP: class_name ANY|ALL|Detail|ERROR|Flow|INPUT|Metrics|OUTPUT|STATE)}

You can specify more than one component class to which to apply the tracesettings.

Command options

setTurns on or off tracing depending upon the value of its parameters. If theparameter is ANY, it turns it off. All other parameters turn on tracing based onthe specified type or level.

listDisplays the default level and type of tracing that is set by default.

Parameters

The parameters that determine the component classes to which to apply the tracesettings are as follows:

COMP: class_nameModifies the trace setting for the name of the component class, as specified byclass_name , for example, COMP:KDH. The output contains trace for the specifiedclass.


UNIT: class_nameModifies the trace setting for any unit that starts with the specified class_namevalue, for example, UNIT: kra. The output contains trace for any unit thatbegins with the specified filter pattern.

The parameters that determine the trace level and type are as follows:

ALLDisplays all trace levels, including every trace point defined for thecomponent. This setting might result in a large amount of trace, so specifyother parameters to exclude unwanted trace. You might require the ALLparameter to isolate a problem. It is the equivalent to setting "Error DetailFlow State Input Output Metrics".

ANYTurns off tracing.

DetailDisplays detailed information about each function.

When entered with the list option, the trace is tagged with Det.

ERRORLogs internal error conditions.

When entered with the list option, the trace is tagged with ER. The output canalso be tagged with EVERYE+EVERYU+ER.

FlowDisplays control flow data for each function entry and exit.

When entered with the list option, the trace is tagged with Fl.

INPUTDisplays input data for each function.

When entered with the list option, the trace is tagged with IN.

MetricsDisplays metrics on each function.

When entered with the list option, the trace is tagged with ME.

OUTPUTDisplays output data for each function.

When entered with the list option, the trace is tagged with OUT.

StateDisplays the status for each function.

When entered with the list option, the trace is tagged with St.

Example

If you enter ras1 set (COMP:KDH ALL) (COMP:ACF1 ALL) (COMP:KDE ALL), the traceutility turns on all levels of tracing for all the files and functions for which KDH,ACF1, and KDE are the classes.kbbcre1.c, 400, May 29 2007, 12:54:43, 1.1, *kbbcrn1.c, 400, May 29 2007, 12:54:42, 1.1, *kdhb1de.c, 400, May 29 2007, 12:59:34, 1.1, KDHkdh0med.c, 400, May 29 2007, 12:59:24, 1.1, KDHkdhsrej.c, 400, May 29 2007, 13:00:06, 1.5, KDHkdhb1fh.c, 400, May 29 2007, 12:59:33, 1.1, KDHkdhb1oe.c, 400, May 29 2007, 12:59:38, 1.2, KDH


kdhs1ns.c, 400, May 29 2007, 13:00:08, 1.3, KDHkbbacdl.c, 400, May 29 2007, 12:54:27, 1.2, ACF1kbbaclc.c, 400, May 29 2007, 12:54:27, 1.4, ACF1kbbac1i.c, 400, May 29 2007, 12:54:28, 1.11, ACF1vkdhsfcn.c, 400, May 29 2007, 13:00:11, 1.1, KDHkdhserq.c, 400, May 29 2007, 12:59:53, 1.1, KDHkdhb1pr.c, 400, May 29 2007, 12:59:39, 1.1, KDHkdhsgnh.c, 400, May 29 2007, 12:59:49, 1.1, KDHkdh0uts.c, 400, May 29 2007, 12:59:23, 1.1, KDHkdhsrsp.c, 400, May 29 2007, 13:00:13, 1.2, KDHkdhs1rp.c, 400, May 29 2007, 13:00:12, 1.1, KDHkdhscsv.c, 400, May 29 2007, 12:59:58, 1.9, KDHkdebbac.c, 400, May 29 2007, 12:56:50, 1.10, KDE...

Turning on tracingTo use the tracing utility, you must use a local logon credential for the computer.This tracing method uses the IBM Tivoli Monitoring Service Console. Access theService Console by using a web browser.

About this task

When you start the Service Console, it displays the information about thecomponents that are currently running on that computer. For example, thesecomponents are listed as follows:v Tivoli Enterprise Portal Server: cnpv Monitoring Agent for Windows OS: ntv Tivoli Enterprise Monitoring Server: ms

After you log on, you can type ? to display a list of the supported commands. ras1is the command to modify trace settings. If you type it in the field at the bottom ofthe window, the help for this command is displayed.

Procedure1. Open a web browser and enter the URL to access the Service Console.

http://hostname:1920

where hostname is the IP address or host name of the computer on which theTivoli Monitoring component is running.

2. Click the hyperlink associated with the component for which you want tomodify its trace settings.

Note: In the previous view, if you want to modify tracing for the TivoliEnterprise Monitoring Server, select IBM Tivoli Monitoring Service Consoleunder Service Point: system.your host name_ms.

3. Enter a user ID and password to access the system. This ID is any valid userthat has access to the system.

4. Enter the command to turn on the required level of trace for the specifiedcomponent classes or units.ras1 set(UNIT|COMP: class_name ALL|Flow|ERROR|Detail|INPUT|Metrics|OUTPUT|STATE){(UNIT|COMP: class_name ALL|Flow|ERROR|Detail|INPUT|Metrics|OUTPUT|STATE)}

For example, to turn on the control flow trace for the KDE, the command is:ras1 (COMP:KDE Flow)


Turning off tracingYou can use the IBM Tivoli Monitoring Service Console to run the ras1 commandand dynamically turn off tracing.

Procedure1. Open a web browser and enter the URL to access the Service Console.

http://hostname:1920

where hostname is the IP address or host name of the computer on which theTivoli Monitoring component is running.

2. Click the hyperlink associated with the component for which you want tomodify its trace settings.

3. Enter a user ID and password to access the system. This ID is any valid userthat has access to the system.

4. Enter the command to turn off the required level of trace for the specifiedcomponent classes or units.ras1 set (UNIT|COMP: class_name ANY){(UNIT|COMP: class_name ANY)}

For example, to turn off tracing for the kbbcrcd class of the Windows OS agent,the command is:ras1 set (UNIT:kbbcrcd ANY)

Setting trace parameters for the Tivoli Enterprise Consoleserver

In addition to the trace information captured by IBM Tivoli Monitoring, you canalso collect additional trace information for the Tivoli Enterprise Consolecomponents that gather event server metrics.

About this task

To collect this information, modify the .tec_diag_config file on the TivoliEnterprise Console event server. Use the steps in the following procedure tomodify the event server trace parameters.

Procedure1. Open the $BINDIR/TME/TEC/.tec_diag_config file in an ASCII editor.2. Locate the entries that configure trace logging for the agent components on the

event server. Two entries are included, one for tec_reception and one fortec_rule:# to debug Agent Utilstec_reception Agent_Utils error /tmp/tec_receptionSP# to debug Agent Utilstec_rule Agent_Utils error /tmp/tec_rule

3. To gather additional trace information, modify these entries to specify a tracelevel of trace2:# to debug Agent Utilstec_reception Agent_Utils trace2 /tmp/tec_receptionSP# to debug Agent Utilstec_rule Agent_Utils trace2 /tmp/tec_rule

4. In addition, modify the Highest_level entries for tec_rule and tec_reception:


tec_reception Highest_level trace2SPtec_rule Highest_level trace2

Problems and workaroundsThe known problems and workarounds are organized into types of problems thatmight occur with the Warehouse Summarization and Pruning Agent, for exampleinstallation and configuration problems and workspace problems.

Note: You can resolve some problems by ensuring that your system matches thesystem requirements listed in Chapter 2, “Requirements for the monitoring agent,”on page 5.This appendix provides agent-specific troubleshooting information. See the IBMTivoli Monitoring Troubleshooting Guide for general troubleshooting information.

Installation and configuration troubleshootingProblems can occur during installation, configuration, and uninstallation of theagent.

The problems and solutions in Table 4 can occur during installation, configuration,and uninstallation of the agent.

Table 4. Problems and solutions for installation and configuration

Problem Solution

(UNIX only) During a command-line installation, youchoose to install a component that is already installed,and you see the following warning:

WARNING - you are about to installthe SAME version of "component_name"

where component_name is the name of the componentthat you are attempting to install.Note: This problem affects UNIX command-lineinstallations. If you monitor only Windowsenvironments, you see this problem if you choose toinstall a product component (for example, a monitoringserver) on UNIX.

You must exit and restart the installation process. Youcannot return to the list where you selected componentsto install. When you run the installer again, do notattempt to install any component that is already installed.

A problem can arise when you install and configure anew monitoring agent to a computer where other agentsare running as described in this example:

v Agents are running on computer and communicatingwith a Tivoli Enterprise Monitoring Server, calledTEMS1.

v You install a new agent on the same computer andyou want this agent to communicate with a differentmonitoring server, called TEMS2.

v When you configure the new agent to communicatewith TEMS2, all the existing agents are re-configuredto communicate with TEMS2.

You must reconfigure the previously existing agents torestore their communication connection with TEMS1. Forexample, you can right-click the row for a specific agentin the Manage Tivoli Enterprise Monitoring Services, andselect Reconfigure. See the IBM Tivoli MonitoringInstallation and Setup Guide for more information onreconfiguration.


Table 4. Problems and solutions for installation and configuration (continued)

Problem Solution

Diagnosing problems with product browse settings(Windows systems only).

When you have problems with browse settings, performthe following steps:

1. Click on Start > Programs > IBM Tivoli Monitoring >Manage Tivoli Enterprise Monitoring Services. TheManage Tivoli Enterprise Monitoring Services windowis displayed.

2. Right-click the Windows agent and select BrowseSettings. A text window is displayed.

3. Click Save As and save the information in the text file.If requested, you can forward this file to IBM SoftwareSupport for analysis.

A message similar to Unable to find running CMS onCT_CMSLIST in the log file is displayed.

If a message similar to Unable to find running CMS onCT_CMSLISTis displayed in the Log file, the agent is notable to connect to the monitoring server. Confirm thefollowing points:

v Do multiple network interface cards (NICs) exist on thesystem?

v If multiple NICs exist on the system, find out whichone is configured for the monitoring server. Ensure thatyou specify the correct host name and port settings forcommunication in the IBM Tivoli Monitoringenvironment.

The system is experiencing high CPU usage. Agent process: View the memory usage of the KSYCMAprocess. If CPU usage seems to be excessive, recycle themonitoring agent.

Network Cards: The network card configurations candecrease the performance of a system. Each of the streamof packets that a network card receives (assuming it is abroadcast or destined for the under-performing system)must generate a CPU interrupt and transfer the datathrough the I/O bus. If the network card in question is abus-mastering card, work can be off-loaded and a datatransfer between memory and the network card cancontinue without using CPU processing power.Bus-mastering cards are generally 32-bit and are based onPCI or EISA bus architectures.


Table 4. Problems and solutions for installation and configuration (continued)

Problem Solution

After installing the Summarization and Pruning Agentv6.2.1 on Windows systems, and after installing anyanother monitoring agent, the Summarization andPruning agent is not working anymore.

The C trace file associated with the Summarization andPruning Agent shows the following issue:

"KSZ_CLASSPATH environment variable is not defined."

There is not a java trace file associated with theSummarization and Pruning Agent.

Save the KSYENV file before installing any other monitoringagent, or follow these steps:

1. Edit the KSYENV file ( located in %CANDLEHOME%/TMAITM6)and add this line anywhere in the file: KSZ_CLASSPATH=

2. Reconfigure the Summarization and Pruning Agentwhich will fill up the KSZ_CLASSPATH variable

3. Restart the Summarization and Pruning Agent

There should be a java trace file as well as a C trace filecreated as soon as the Summarization and Pruning Agentstarts. The tables should be summarized and pruned.

Table 5. General problems and solutions for uninstallation

Problem Solution

On Windows, uninstallation ofIBM Tivoli Monitoring fails touninstall the entire environment.

Be sure that you follow the general uninstallation process described in the IBMTivoli Monitoring Installation and Setup Guide:

1. Remove Tivoli Enterprise Monitoring Server Application support bycompleting the following steps:

a. Use Manage Tivoli Enterprise Monitoring Services.

b. Select Tivoli Enterprise Monitoring Server.

c. Right-click and select advanced .

d. Select Remove TEMS application support.

e. Select the agent to remove its application support.

2. Uninstall monitoring agents first, as in the following examples:

v Uninstall a single monitoring agent for a specific database.

-OR-

v Uninstall all instances of a monitoring product, such as IBM TivoliMonitoring for Databases.

3. Uninstall IBM Tivoli Monitoring.

The way to remove inactivemanaged systems (systems whosestatus is OFFLINE) from theNavigator tree in the portal is notobvious.

Use the following steps to remove, but not uninstall, an offline managed systemfrom the Navigation tree:

v Click the Enterprise icon in the Navigator tree.

v Right-click Workspace > Managed System Status.

v Right-click the offline managed system, and select Clear offline entry.

If you also want to uninstall the monitoring agent, use the procedure describedin the IBM Tivoli Monitoring Installation and Setup Guide.

Unique names for monitoring componentsIBM Tivoli Monitoring might not be able to generate a unique name for monitoringcomponents due to the truncation of names that the product automaticallygenerates.


If the agent supports multi-instances, IBM Tivoli Monitoring automatically createsa name for each monitoring component by concatenating the subsystem name, hostname, and product code separated by colons (subsystem_name:hostname:KSY).

Note: When you monitor a multinode system, such as a database, IBM TivoliMonitoring adds a subsystem name to the concatenated name, typically a databaseinstance name.The length of the name that IBM Tivoli Monitoring generates is limited to 32characters. Truncation can result in multiple components having the same32-character name. If this problem happens, shorten the hostname portion of thename as follows:1. Open the configuration file for the monitoring agent, which is located in the

following path:v On Windows: &install_dir;\tmaitm6\Kproduct_codeCMA.INI. For example,

the product code for the Monitoring Agent for Windows OS is NT and thefile name is KNTCMA.INI.

v On UNIX and Linux: itm_home/config/product_code.ini andproduct_code.config. For example, the file names for the Monitoring Agentfor UNIX OS is ux.ini and ux.config.

2. Find the line the begins with CTIRA_HOSTNAME=.3. Type a new name for host name that is a unique, shorter name for the host

computer. The final concatenated name including the subsystem name, newhost name, and KSY, cannot be longer than 32 characters.

Note: You must ensure that the resulting name is unique with respect to anyexisting monitoring component that was previously registered with the TivoliEnterprise Monitoring Server.

4. Save the file.5. Restart the agent.

Agent troubleshootingA problem can occur with the agent after it has been installed.

Table 6 contains problems and solutions that can occur with the agent after it hasbeen installed.

Table 6. Agent problems and solutions

Problem Solution

Log data accumulates toorapidly.

Check the RAS trace option settings, which are described in the IBM TivoliMonitoring Troubleshooting Guide. The trace options settings that you can set onthe KBB_RAS1= and KDC_DEBUG= lines potentially generate large amounts of data.

The Warehouse Summarizationand Pruning Agent workspacesand navigator items are notvisible in the Tivoli EnterprisePortal.

The application support files need to be installed for the Tivoli Enterprise PortalServer, browser Tivoli Enterprise Portal, and desktop Tivoli Enterprise Portal.This problem can occur in IBM Tivoli Monitoring upgrade environments wherethe Warehouse Summarization and Pruning Agent is upgraded from a versionthat did not have the self monitoring capabilities, and the support files were notselected in the upgrade.


Table 6. Agent problems and solutions (continued)

Problem Solution

The agent stops or does notrecord any data.

The agent trace log file should be examined. The log file is located in theHOME\logs directory and is created during the running of the agent. The name ofthe file is HOSTNAME_SY_JAVA_timestamp-01.log. HOSTNAME is the host where theagent runs, and the timestamp is the time the agent started. The timestamp issequential in nature, so it should be the latest log created for the agent.

If you receive the following error, remove the SelectMethod=cursor from theURL used during configuration of the agent:

java.sql.BatchUpdateException:com.microsoft.sqlserver.jdbc.SQLServerException:

This only applies if the agent runs with MSSQL, not DB2®.

When using the F1 key orselecting Help > Contents andIndex, you receive a message inyour Microsoft Internet Explorerbrowser which states, It seemsjavascript is disabled in yourbrowser, please enable it andreload again, or click here toview without javascript. If youselect here, the Tivoli EnterprisePortal V6.1 Help is displayed,but the agent help is not.

Ensure that the local site is added to the browser's trusted site and then enablethe javascript.

The Summarization and PruningAgent hangs or has a workerthread that hangs.

This can be caused (on DB2 at least) if there is another application (DB2 ControlCenter) holding a lock on the table. DB2 by default has LOCKTIMEOUT set to -1,meaning a long wait that causes the Summarization and Pruning Agent toappear to hang. Closing the offending application (or resolving the deadlock)solves the problem.

The Summarization and PruningAgent is logging "Interfaceunknown" messages.

This happens when you have the Warehouse Proxy Agent and some othercomponent on the same system and you shutdown the Warehouse Proxy Agentand start the other component, which may reuse the same port previously usedby the Warehouse Proxy Agent. These messages are benign but end up filling thelogs until the Warehouse Proxy Agent is restarted, and the synchronization of theWarehouse Proxy Agent location is sent to all Tivoli Enterprise MonitoringServers.

Summarization and PruningAgent returns a java exception.

The java exception is

ava.sql.BatchUpdateException: com.microsoft.sqlserver.jdbc.SQLServerException:sp_cursoropen/sp_cursorprepare:The statement parameter can only be a batch or a stored procedure with asingle select,without FOR BROWSE, COMPUTE BY, or variable assignments.

To avoid this problem, remove the SelectMethod=cursor from the URL used inthe Summarization and Pruning configuration. There is also a hotfix availablefrom Microsoft Support website.



Problem Solution

Summarization and PruningAgent runs out of memory.

Modify the jdbc connection string for this monitoring agent, if you receive thefollowing message:

The system is out of memory.Use server side cursors for large result sets

Modify the connection string from this:

jdbc:sqlserver://hostname;databaseName=WAREHOUS

to this:

jdbc:sqlserver://SERVERNAME;databasename=WAREHOUS;SelectMethod=cursor;

There are two select methods - DIRECT and CURSOR. Depending on thedatabase and how it was designed - CURSOR might be required. If you neverneed multiple-statement-execution transactions, or you never have more than oneopen statement at a time, you can use direct. Otherwise, you need cursor mode.



Problem Solution

Summarization and PruningAgent in large environment.

The following index and tuning changes were made to reduce Summarizationand Pruning run time in an environment with 10,000 agents. The database serverwas DB2 running on AIX:

v Async IO changes to AIX

Change Minimum Servers and Maximum Servers from 1 and 10 to 40 and 80.A reboot is required.

v Change the DB2MAXFSCRSEARCH value, using the following command:

db2set DB2MAXFSCRSEARCH=2

v Enable the DB2_USE_ALTERNATE_PAGE_CLEANING value, using thefollowing command:

db2set DB2_USE_ALTERNATE_PAGE_CLEANING=ON

v Enable the DB2_PARALLEL_IO value (with the number of disks in the largestarray):

db2set DB2_PARALLEL_IO=*:9

v Increase the DBHEAP value from 1800 to 3000 by updating the databaseconfiguration for the WAREHOUS database by using the following command:

update database config for WAREHOUS using dbheap 3000

v Increase the LOGBUFSZ value from 1024 to 2048 by updating the databaseconfig for the WAREHOUS database by using the following command:

update database config for WAREHOUS using logbufsz 2048

v Increase the prefetch size from AUTOMATIC (32) to 288 by altering thetablespace userspace1 by suing the following command:

alter tablespace USERSPACE1 prefetchsize 288

v Drop all HX2 and DX2 indexes from aggregate tables.

v Drop all of the indexes on the WAREHOUSELOG table:

drop index "ITMUSER"."WHLOG_IDX1";drop index "ITMUSER"."WHLOG_IDX2";drop index "ITMUSER"."WHLOG_IDX3";

v Create this index on the WAREHOUSELOG table. This index greatly improvesSELECT statements made during pruning of the WAREHOUSELOG.:

CREATE INDEX "ITMUSER "."WHLOG_IDX1" ON "ITMUSER "."WAREHOUSELOG"("ORIGINNODE" ASC, "EXPORTTIME" ASC) ALLOW REVERSE SCANS;

v In the Summarization and Pruning Agent configuration file, increase theKSY_MAX_ROWS_PER_TRANSACTION value from 1000 to 3000 in the file,ksy.ini.

v From the root user, change the Ulimit file parameter by using the followingcommand:

ulimit -f unlimited

v Increased the NUM_IOCLEANERS value from 14 to 24.

If you want to receive multipletrace logs for separateinvocations of the same TakeAction command, leaving thissetting on permanently fills theavailable disk space.

Do not leave this setting permanently. By doing so, you create a new log file foreach invocation of the Take Action command and ALL of them are left on theagent system.



Problem Solution

Online Help Search cannot findany agent online help.

To search the online help for this agent the user must use the IBM Eclipse helpsearch function and not the search function in the web based help online help.

To use the search function for this agent's online help, ensure that you haveselected the IBM Eclipse help server check box when installing the TivoliEnterprise Portal Server. The 'Searching Agent Help' topic in this agent's onlinehelp contains a link to the Eclipse help, where the search function is enabled.From the Table of Contents in the left-hand pane of the help, select the 'SearchingAgent Help' topic to find the link to the Eclipse help in the right-hand pane.

Workspace troubleshootingProblems can occur with general workspaces and agent-specific workspaces.

Table 7 contains problems and solutions related to workspaces.

Table 7. Workspace problems and solutions

Problem Solution

You see the following message: KFWIT083WDefault link is disabled for the selectedobject; please verify link and link anchordefinitions.

You see this message because some links do not have defaultworkspaces. Right-click the link to access a list of workspaces toselect.

The name of the attribute does not display in abar chart or graph view.

When a chart or graph view that includes the attribute is scaledto a small size, a blank space is displayed instead of a truncatedname. To see the name of the attribute, expand the view of thechart until there is sufficient space to display all characters of theattribute's name.

At the bottom of each view, you see thefollowing Historical workspace KFWITM220Eerror: Request failed during execution.

Ensure that you configure all groups that supply data to theview. In the Historical Configuration view, ensure that datacollection is started for all groups that supply data to the view.

You start collection of historical data but the datacannot be seen.

Managing options for historical data collection:

v Basic historical data collection populates the Warehouse withraw data. This type of data collection is turned off by default.See the IBM Tivoli Monitoring Administrator's Guide forinformation on managing this feature including how to set theinterval at which data is collected. By setting a more frequentinterval for data collection you reduce the load on the systemincurred every time data is uploaded.

v You use the Summarization and Pruning monitoring agent tocollect specific amounts and types of historical data. Be awarethat historical data is not displayed until the Summarizationand Pruning monitoring agent begins collecting the data. Bydefault, this agent begins collection at 2 AM daily. At thatpoint, data is visible in the workspace view. See the IBM TivoliMonitoring Administrator's Guide to learn how to modify thedefault collection settings.


Table 7. Workspace problems and solutions (continued)

Problem Solution

Historical data collection is unavailable becauseof incorrect queries in the Tivoli EnterprisePortal.

The column, Sort By, Group By, and First/Last functions are notcompatible with the historical data collection feature. Use ofthese advanced functions makes a query ineligible for historicaldata collection.

Even if data collection has been started, you cannot use the timespan feature if the query for the chart or table includes columnfunctions or advanced query options (Sort By, Group By, First /Last).

To ensure support of historical data collection, do not use theSort By, Group By, or First/Last functions in your queries.

See the IBM Tivoli Monitoring Administrator's Guide the TivoliEnterprise Portal online help for information about the HistoricalData Collection function.

When you use a long process name in thesituation, the process name is truncated.

Truncation of process or service names for situations in theAvailability table in the portal display is the expected behavior.100 bytes is the maximum name length.

Regular (non-historical) monitoring data fails tobe displayed.

Check the formation of the queries you use to gather capturedata. For example, look for invalid SQL statements.

Support informationIf you have a problem with your IBM software, you want to resolve it quickly.

IBM provides the following ways for you to obtain the support you need:

OnlineThe following websites contain troubleshooting information:v Go to the IBM Software Support website and follow the instructions.v Go to the IBM Tivoli Distributed Monitoring and Application

Management Wiki. Feel free to contribute to this wiki.

IBM Support AssistantThe IBM Support Assistant (ISA) is a free local software serviceabilityworkbench that helps you resolve questions and problems with IBMsoftware products. The ISA provides quick access to support-relatedinformation and serviceability tools for problem determination. To installthe ISA software, go to the IBM Support Assistant website.


http://www.ibm.com/support/entry/portal/software

http://www.lotus.com/ldd/tivmonitorwiki.nsf

http://www.lotus.com/ldd/tivmonitorwiki.nsf

http://www.ibm.com/software/support/isa

Appendix A. IBM Tivoli Enterprise Console event mapping

Each event class corresponds to an attribute group in the IBM Tivoli EnterpriseConsole.

A description of the event slots for each event class is provided. For moreinformation about mapping attribute groups to event classes, see the IBM TivoliMonitoring Administrator's Guide.

Generic event mapping provides useful event class and attribute information forsituations that do not have specific event mapping defined. BAROC files are foundon the Tivoli Enterprise Monitoring Server in the installation directory in TECLIB(that is, install_dir/cms/TECLIB for Windows systems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems). IBM Tivoli Enterprise Console eventsynchronization provides a collection of ready-to-use rule sets that you can deploywith minimal configuration. Be sure to install IBM Tivoli Enterprise Console eventsynchronization to access the correct Sentry.baroc, which is automatically includedduring base configuration of IBM Tivoli Enterprise Console rules if you indicatethat you want to use an existing rule base. See the IBM Tivoli Monitoring Installationand Setup Guide for details.

Each of the event classes is a child of KSY_Base and is defined in the ksy.baroc(version 06.02.00) file. The KSY_Base event class can be used for generic rulesprocessing for any event from the Warehouse Summarization and Pruning Agent.

For events generated by situations in the Connectivity attribute group, TivoliEnterprise Console events are sent using the ITM_KSY_CONNECTIVITY class.This class contains the following slots:v node: STRINGv timestamp: STRINGv teps_host_name: STRINGv teps_port: INTEGERv teps_port_enum: STRINGv database_type: INTEGERv database_type_enum: STRINGv url: STRINGv driver: STRINGv driver_version: STRINGv database_version: STRINGv classpath: STRINGv teps_connectivity: INTEGERv teps_connectivity_enum: STRINGv db_connectivity: INTEGERv db_connectivity_enum: STRING

For events generated by situations in the Node Failures attribute group, TivoliEnterprise Console events are sent using the ITM_KSY_NODE FAILURES class.This class contains the following slots:v node: STRING


v timestamp: STRINGv failed_system: STRINGv product_code: STRINGv timezone_diff: INTEGERv timezone_diff_enum: STRINGv table_name: STRINGv attribute_group_name: STRINGv error_timestamp: STRINGv error_message: STRINGv sql_code: INTEGERv sql_code_enum: STRINGv sql_state: STRING

For events generated by situations in the Summarization Config attribute group,Tivoli Enterprise Console events are sent using the ITM_KSY_SUMMARIZATIONCONFIG class. This class contains the following slots:v node: STRINGv timestamp: STRINGv fixed_frequency: INTEGERv fixed_frequency_enum: STRINGv fixed_scheduled_time: STRINGv fixed_scheduling: INTEGERv fixed_scheduling_enum: STRINGv flexible_scheduling_minutes: INTEGERv flexible_scheduling_minutes_enum: STRINGv flexible_scheduling_exceptions: STRINGv num_threads: INTEGERv num_threads_enum: STRINGv week_beginning: INTEGERv week_beginning_enum: STRINGv shifts_specified: INTEGERv shifts_specified_enum: STRINGv vacation_enabled: INTEGERv vacation_enabled_enum: STRINGv weekend_vacation: INTEGERv weekend_vacation_enum: STRINGv vacation_days: STRINGv peak_shift_hours: STRINGv off_peak_shift_hours: STRINGv prune_warehouselog: INTEGERv prune_warehouselog_enum: STRINGv warehouselog_time: INTEGERv warehouselog_time_enum: STRINGv warehouselog_units: INTEGERv warehouselog_units_enum: STRINGv prune_warehouseaggreglog: INTEGER


v prune_warehouseaggreglog_enum: STRINGv warehouseaggreglog_time: INTEGERv warehouseaggreglog_time_enum: STRINGv warehouseaggreglog_units: INTEGERv warehouseaggreglog_units_enum: STRINGv max_rows_per_db_transaction: INTEGERv max_rows_per_db_transaction_enum: STRINGv timezone_source: INTEGERv timezone_source_enum: STRINGv hourly_data_summarization: INTEGERv hourly_data_summarization_enum: STRINGv daily_data_summarization: INTEGERv daily_data_summarization_enum: STRINGv next_work_time: STRINGv summarization_and_pruning_rows: INTEGERv summarization_and_pruning_rows_enum: STRINGv error_rows: INTEGERv error_rows_enum: STRINGv connectivity_cache_minutes: INTEGERv connectivity_cache_minutes_enum: STRINGv batch_mode: INTEGERv batch_mode_enum: STRINGv database_compression: INTEGERv database_compression_enum: STRING

For events generated by situations in the Summarization Statistics attribute group,Tivoli Enterprise Console events are sent using the ITM_KSY_SUMMARIZATIONSTATISTICS class. This class contains the following slots:v node: STRINGv timestamp: STRINGv start_time: STRINGv end_time: STRINGv run_length: REALv run_length_enum: STRINGv thread_pool_size: INTEGERv thread_pool_size_enum: STRINGv active_threads: INTEGERv active_threads_enum: STRINGv rows_pruned: INTEGERv rows_pruned_enum: STRINGv rows_summarized: INTEGERv rows_summarized_enum: STRINGv failures: INTEGERv failures_enum: STRINGv pruning_failures: INTEGERv pruning_failures_enum: STRING

Appendix A. IBM Tivoli Enterprise Console event mapping 69

v summarization_failures: INTEGERv summarization_failures_enum: STRING

For events generated by situations in the Table Statistics attribute group, TivoliEnterprise Console events are sent using the ITM_KSY_TABLE STATISTICS class.This class contains the following slots:v node: STRINGv timestamp: STRINGv start_time: STRINGv end_time: STRINGv run_length: REALv run_length_enum: STRINGv product_code: STRINGv rows_updated: INTEGERv rows_updated_enum: STRINGv rows_created: INTEGERv rows_created_enum: STRINGv managed_systems_processed: INTEGERv managed_systems_processed_enum: STRINGv table_name: STRINGv attribute_group_name: STRINGv rows_pruned: INTEGERv rows_pruned_enum: STRINGv rows_summarized: INTEGERv rows_summarized_enum: STRINGv failures: INTEGERv failures_enum: STRINGv pruning_failures: INTEGERv pruning_failures_enum: STRINGv summarization_failures: INTEGERv summarization_failures_enum: STRING


Appendix B. Documentation library

A variety of publications are relevant to the use of the Warehouse Summarizationand Pruning Agent.

The IBM Tivoli Monitoring, OMEGAMON XE, and Composite Application Managerproducts: Documentation Guide, SC23-8816, contains information about accessing andusing publications. You can find the Documentation Guide in the followinginformation centers:v IBM Tivoli Monitoring and OMEGAMON® XEv IBM Tivoli Composite Application Manager

To open the Documentation Guide in the information center, select Using thepublications in the Contents pane.

To find a list of new and changed publications, click What's new in theinformation center on the Welcome page of the IBM Tivoli Monitoring andOMEGAMON XE Information Center.

To find publications from the previous version of a product, click Previousversions under the name of the product in the Contents pane.

Warehouse Summarization and Pruning Agent library

The documentation for this agent and other product components is located in theproduct information center

One document is specific to the Warehouse Summarization and Pruning Agent:Warehouse Summarization and Pruning Agent User’s Guide. This publicationprovides agent-specific information for configuring, using, and troubleshooting theWarehouse Summarization and Pruning Agent.

Use the information in this guide with the IBM Tivoli Monitoring User's Guide tomonitor Summarization and Pruning Agent resources.

Prerequisite publicationsTo use the information in this publication effectively, you must have someprerequisite knowledge.

See the following publications to gain the required prerequisite knowledge:v IBM Tivoli Monitoring Readme First

v Exploring IBM Tivoli Monitoring

v IBM Tivoli Monitoring Administrator's Guide

v IBM Tivoli Monitoring Agent Builder User's Guide

v IBM Tivoli Monitoring Command Reference

v Configuring IBM Tivoli Enterprise Monitoring Server on z/OS

v IBM Tivoli Monitoring Installation and Setup Guide

v IBM Tivoli Monitoring: Messages


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp



v IBM Tivoli Monitoring, OMEGAMON XE, and Composite Application Managerproducts: Documentation Guide

v IBM Tivoli Monitoring Troubleshooting Guide

v IBM Tivoli Monitoring Universal Agent User's Guide

v IBM Tivoli Universal Agent API and Command Programming Reference Guide

v IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring

v IBM Tivoli Monitoring: Upgrading from V5.1.2

v IBM Tivoli Monitoring: i5/OS Agent User's Guide

v IBM Tivoli Monitoring: Linux OS Agent User's Guide

v IBM Tivoli Monitoring: UNIX OS Agent User's Guide

v IBM Tivoli Monitoring: UNIX Logs OS Agent User's

v IBM Tivoli Monitoring: Windows OS Agent User's Guide

v IBM Tivoli Monitoring User's Guide

Related publicationsThe publications in related information centers provide useful information.

See the following information centers, which you can find by accessing TivoliDocumentation Central:v IBM Tivoli Monitoringv IBM Tivoli Netcool/OMNIbusv IBM Tivoli Application Dependency Discovery Manager (TADDM)v IBM Tivoli Enterprise Console

Other sources of documentationYou can obtain additional technical documentation about monitoring productsfrom other sources.

See the following sources of technical documentation about monitoring products:v IBM Integrated Service Management Library is an online catalog that contains

integration documentation as well as other downloadable product extensions.v IBM Redbook publications ( Redbooks® publications, Redpapers, and Redbooks

technotes) provide information about products from platform and solutionperspectives.

v Technotes, which are found through the IBM Software Support website, providethe latest information about known product limitations and workarounds.

v Tivoli wikisTivoli Wiki Central is the home for interactive wikis that offer best practices andscenarios for using Tivoli products. The wikis contain white papers contributedby IBM employees, and content created by customers and business partners.Two of these wikis are of particular relevance to IBM Tivoli Monitoring:– Tivoli Distributed Monitoring and Application Management Wiki provides

information about IBM Tivoli Monitoring and related distributed products,including IBM Tivoli Composite Application Management products.

– Tivoli System z® Monitoring and Application Management Wiki providesinformation about the OMEGAMON XE products, Tivoli NetView® for z/OS®,Tivoli Monitoring Agent for z/TPF, and other System z monitoring andapplication management products.


http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Home

http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Home

http://www.ibm.com/software/brandcatalog/ismlibrary/

http://www.redbooks.ibm.com/

http://www.ibm.com/support/entry/portal/software

http://www.ibm.com/developerworks/wikis/display/tivoli/Home

http://www-10.lotus.com/ldd/tivmonitorwiki.nsf

http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home

Accessibility

Accessibility features help users with physical disabilities, such as restrictedmobility or limited vision, to use software products successfully.

The major accessibility features in this product enable users in the following ways:v Use assistive technologies, such as screen-reader software and digital speech

synthesizer, to hear what is displayed on the screen. Consult the productdocumentation of the assistive technology for details on using those technologieswith this product.

v Operate specific or equivalent features using only the keyboard.v Magnify what is displayed on the screen.

In addition, the product documentation was modified to include the followingfeatures to aid accessibility:v All documentation is available in both HTML and convertible PDF formats to

give the maximum opportunity for users to apply screen-reader software.v All images in the documentation are provided with alternative text so that users

with vision impairments can understand the contents of the images.

Navigating the interface using the keyboard

Standard shortcut and accelerator keys are used by the product and aredocumented by the operating system. See the documentation provided by youroperating system for more information.

Magnifying what is displayed on the screen

You can enlarge information in the product windows using facilities provided bythe operating systems on which the product is run. For example, in a MicrosoftWindows environment, you can lower the resolution of the screen to enlarge thefont sizes of the text on the screen. See the documentation provided by youroperating system for more information.


Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subjectto change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment to


IBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM‘s application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows:

© IBM 2009. Portions of this code are derived from IBM Corp. Sample Programs. ©Copyright IBM Corp. 2009. All rights reserved.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not be displayed.

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at "Copyright andtrademark information" at www.ibm.com/legal/copytrade.shtml.

Intel, Intel logo, and Intel Xeon, are trademarks or registered trademarks of IntelCorporation or its subsidiaries in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft and Windows are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other company, product, or service names may be trademarks or service marks ofothers.

Notices 77

Index

Aaccessibility 73Active Threads attribute 28additional information

situations 37Take Action commands 39

agentfunctions 1problems and workarounds 60

agent connection status attributegroup 12

Agent Management Services 2agent output log attribute group 15agent trace log attribute group 18attribute group 12Attribute Group Name attribute 17, 33attribute groups

agent connection status 12agent output log 15agent trace log 18control domain 27host cpu 30list of all 11overview 11

attributes 12Active Threads 28agent output log 15agent trace log 18Attribute Group Name 17, 33Batch Mode 26Classpath 14Connectivity 12Connectivity Cache Minutes 26control domain 27Daily Data Summarization 25Database Compression 26Database Type 13Database Version 14DB Connectivity 15Driver 14Driver Version 14End Time 27, 31Error Message 17Error Rows 25Error Timestamp 17Failed System 16Failures 29, 34Fixed Frequency 18Fixed Scheduled Time 19Fixed Scheduling 19Flexible Scheduling Exceptions 19Flexible Scheduling Minutes 19host cpu 30Hourly Data Summarization 24Managed Systems Processed 32Max Rows Per DB Transaction 24Next Work Time 25Node 12, 15, 18, 27, 30Num Threads 20Off Peak Shift Hours 21overview 11

attributes (continued)Peak Shift Hours 21Product Code 16, 31Prune

WAREHOUSEAGGREGLOG 23Prune WAREHOUSELOG 22Pruning Failures 30, 34Rows Created 32Rows Pruned 29, 33Rows Summarized 29, 33Rows Updated 32Run Length (hour) 28Run Length (min) 31Shifts Specified 20SQL Code 17SQL State 17Start Time 27, 31Summarization and Pruning

Rows 25Summarization Failures 30, 34Table Name 16, 33TEPS Connectivity 15TEPS Host Name 13TEPS Port 13Thread Pool Size 28Timestamp 13, 16, 18, 27, 31Timezone Diff 16Timezone Source 24URL 14Vacation Days 21Vacation Enabled 20WAREHOUSEAGGREGLOG

Time 23WAREHOUSEAGGREGLOG

Units 23WAREHOUSELOG Time 22WAREHOUSELOG Units 22Week Beginning 20Weekend Vacation 21

BBatch Mode attribute 26

Ccalculate historical data disk space 35capacity planning

Warehouse Summarization andPruning Agent 35

capacity planning for historical data 35Citrix XenServer

workspacesdescriptions 8

Classpath attribute 14commands

Take Action 39component names, unique 60components 1configuration 5

configuration (continued)problems and workarounds 57

Configurationworkspaces

list 8Configuration workspace 8Connectivity Cache Minutes attribute 26Connectivity workspace 9control domain attribute group 27

DDaily Data Summarization attribute 25data logged


Database Compression attribute 26Database Type attribute 13Database Version attribute 14DB Connectivity attribute 15developerWorks website 72disk capacity planning 35disk capacity planning for historical

data 35documentation

See publicationsDriver attribute 14Driver Version attribute 14

EEnd Time attribute 27, 31Error Message attribute 17Error Rows attribute 25Error Timestamp attribute 17event

mapping 67Events


FFailed System attribute 16Failures attribute 29, 34Fixed Frequency attribute 18Fixed Scheduled Time attribute 19Fixed Scheduling attribute 19Flexible Scheduling Exceptions

attribute 19Flexible Scheduling Minutes attribute 19

Ggathering support information 43


Hhistorical data

calculate disk space 35capacity planning


disk capacity planning 35host cpu attribute group 30Hosts


Hourly Data Summarization attribute 24

IIBM Software Support 43IBM Tivoli Enterprise Console

event mapping 67IBM Tivoli Monitoring

overview 1information

troubleshooting 43installation

problems and workarounds 57Integrated Service Management Library

documentation 72interface, user 2

Llogged data


MManaged Systems Processed attribute 32Max Rows Per DB Transaction

attribute 24

Nnew 1Next Work Time attribute 25Node attribute 12, 15, 18, 27, 30Num Threads attribute 20

OOff Peak Shift Hours attribute 21overview

IBM Tivoli Monitoring 1

PPeak Shift Hours attribute 21policies 41prerequisite publications 71problems and workarounds 57

agent-specific 60agent-specific workspaces 64configuration 57install 57workspaces 64

Product Code attribute 16, 31Prune WAREHOUSEAGGREGLOG

attribute 23Prune WAREHOUSELOG attribute 22Pruning Failures attribute 30, 34publications 71, 72

developerWorks website 72IBM Tivoli Monitoring 71Integrated Service Management

Library 72prerequisite 71Redbooks 72related 72Technotes 72wikis 72

purposestroubleshooting 43

Qqueries, using attributes 11

Rras1 53Redbooks 72requirements 5Rows Created attribute 32Rows Pruned attribute 29, 33Rows Summarized attribute 29, 33Rows Updated attribute 32Run Length (hour) attribute 28Run Length (min) attribute 31

SShifts Specified attribute 20situations

additional informationpredefined, defined 37

overview 37predefined 39Situation Editor 37

situations, using attributes 11SQL Code attribute 17SQL State attribute 17Start Time attribute 27, 31Statistics

workspaceslist 8

Statistics workspace 9Summarization and Pruning Rows

attribute 25Summarization Failures attribute 30, 34support

gathering information for 43

TTable Name attribute 16, 33Take Action commands

additional information 39overview 39predefined 41

Technotes 72

TEPS Connectivity attribute 15TEPS Host Name attribute 13TEPS Port attribute 13Thread Pool Size attribute 28Timestamp attribute 13, 16, 18, 27, 31Timezone Diff attribute 16Timezone Source attribute 24trace

turn off 56turn on 55

trace settings 53troubleshooting 43

agent-specific 60agent-specific workspaces 64installation 57problems and workarounds 57turn off trace 56turn on trace 55uninstallation 57workspaces 64

Uunique component names 60unique names 60URL attribute 14user interfaces options 2

VVacation Days attribute 21Vacation Enabled attribute 20views

Configuration workspace 8Connectivity workspace 9Statistics workspace 9Warehouse Summarization and

Pruning Agent workspace 8Work Completed workspace 9

WWarehouse Summarization and Pruning

Agentcomponents 1workspaces

list 8Warehouse Summarization and Pruning

Agent workspace 8WAREHOUSEAGGREGLOG Time

attribute 23WAREHOUSEAGGREGLOG Units

attribute 23WAREHOUSELOG Time attribute 22WAREHOUSELOG Units attribute 22Week Beginning attribute 20Weekend Vacation attribute 21wikis 72Work Completed workspace 9workarounds 57workspaces 7

Citrix XenServer 8Configuration 8Connectivity 9descriptions 8Events 8


workspaces (continued)Hosts 9list of all 8predefined 8problems and workarounds 64Statistics 9Warehouse Summarization and

Pruning Agent 8Work Completed 9

Index 81

��

Printed in USA

SC23-9767-02

Warehouse Summarization and Pruning Agent User's Guide

Documents

Transcript of Warehouse Summarization and Pruning Agent User's Guide