![]() |
![]() |
[ Bottom of Page | | Contents | Index ]
Before using this information and the product it supports, read the information in Appendix. Notices.
This edition applies to version 3, release 9 of IBM Tivoli Enterprise Console (product number 5698-TEC) and to all subsequent releases and modifications until otherwise indicated in new editions.
This document describes the warehouse enablement pack, version 1.3.0.0 for IBM(R) Tivoli Enterprise Console(R), Version 3.9. This warehouse enablement pack is created for IBM Tivoli(R) Data Warehouse, Version 1.2.0.2
With this warehouse enablement pack (hereafter referred to as warehouse pack), you can store and maintain information about events. You can also use this information to create reports. Using this reporting function requires that you install and configure Tivoli Data Warehouse and the Tivoli Enterprise Console warehouse pack.
The Installing and Configuring Tivoli Data Warehouse document provides the following information:
This document provides the following information specifically for the Tivoli Enterprise Console warehouse pack:
This guide is for people who do any of the following activities:
Administrators and installers should have the following knowledge or experience:
Additionally, report designers and warehouse pack creators should have the following knowledge or experience:
This section lists publications in the Tivoli Data Warehouse library and other related documents. It also describes how to access Tivoli publications online and how to order Tivoli publications.
The following sets of documentation are available to help you understand, install and manage this warehouse pack
The following documents are available in the IBM Tivoli Enterprise Console library:
Provides information about supported adapters, including how to install and configure these adapters.
Provides details about IBM Tivoli Enterprise Console commands, predefined tasks that are shipped in the task library, and the environment variables that are available to tasks that run against an event.
Describes how to install, upgrade, and uninstall the IBM Tivoli Enterprise Console product.
Provides release-specific information that is not available until just before the product is sent to market.
Describes how to develop rules and integrate them for event correlation and automated event management.
Provides reference information about the IBM Tivoli Enterprise Console rule sets.
Provides an overview of the IBM Tivoli Enterprise Console product and describes how to configure and use the IBM Tivoli Enterprise Console product to manage events.
Describes how to install and configure the warehouse enablement pack for the IBM Tivoli Enterprise Console product and describes the data flow and structures that are used by the warehouse pack.
Describes how to develop your own event adapters that are tailored to your network environment and the specific needs of your enterprise. This reference also describes how to filter events at the source.
The following documents are available in the Tivoli Data Warehouse library. The library is available online, as described in Accessing publications online:
Provides late-breaking information about Tivoli Data Warehouse and lists hardware requirements and software prerequisites.
Describes how Tivoli Data Warehouse fits into your enterprise, explains how to plan for its deployment and gives installation and configuration instruction. It contains maintenance procedures and trobuleshooting information.
Provides information about connecting an application to Tivoli Data Warehouse. This book is for application programmers who use Tivoli Data Warehouse to store and report on their application data, data warehousing expers who import Tivoli Data Warehouse data into business intelligence applications and customers who put their local data in Tivoli Data Warehouse. This document is available only from the IBM Web site.
Lists the messages generated by Tivoli Data Warehouse and describes the corrective actions you should take.
The following sections describe additional publications to help you understand and use Tivoli Data Warehouse.
IBM Redbooks are developed and published by the IBM International Technical Support Organization, the ITSO. They explore integration, implementation and operation of realistic customer scenarios. The following Redbooks contain information about Tivoli Data Warehouse:
Provides a broad understanding of Tivoli Data Warehouse. Some of the topics that are covered are concepts, architecture, writing your own extract, transform, and load processes (ETLs), and best practices in creating data marts.
Describes the necessary planning you must complete before you can deploy Tivoli Data Warehouse. The guide shows how to apply these planning steps in a real-life deployment of a warehouse pack using IBM Tivoli Monitoring. It also contains frequently used Tivoli and DB2 commands and lists troubleshooting tips for Tivoli Data Warehouse.
The DB2 library contains important information about the database and data warehousing technology provided by IBM DB2, DB2 Data Warehouse Center and DB2 Warehouse Manager. Refer to the DB2 library for help in installing, configuring administering and troubleshooting DB2, which is available on the following IBM Web site:
http://www.ibm.com/software/support.
After you install DB2, its library is also available on your system.
The following DB2 documents are particularly relevant for people working with Tivoli Data Warehouse:
Guides you through the planning, installation, migration (if necessary), and setup of a partitioned database system using the IBM DB2 product on Microsoft(R) Windows.
Guides you through the planning, installation, migration (if necessary), and setup of a partitioned database system using the IBM DB2 product on UNIX.
Covers the details of implementing your database design. Topics include creating and altering a database, database security, database recovery, and administration using the Control Center, which is a DB2 graphical user interface.
Provides information on how to build and maintain a data warehouse using the Data Warehouse Center.
Provides information on how to install the following Warehouse Manager components: Information Catalog Manager, warehouse agents, and warehouse transformers.
Provides advanced installation considerations, and guides you through the planning, installation, migration (if necessary), and set up of a platform-specific DB2 client. This supplement also contains information on binding, setting up communications on the server, the DB2 GUI tools, DRDA(R) AS, distributed installation, the configuration of distributed requests, and accessing heterogeneous data sources.
Lists the messages and codes issued by DB2, the Information Catalog Manager, and the Data Warehouse Center, and describes the actions you should take.
The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software. TheTivoli Software Glossary is available at the following Tivoli software library Web site:
Access the glossary by clicking the Glossary link on the left pane of the Tivoli software library window.
http://www.ibm.com/software/tivoli/library/
The publications CD or product CD contains the publications that are in the product library. The format of the publications is PDF, HTML, or both.
IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli Software Information Center Web site. The Tivoli Software Information Center is located at the following Web address:
http://publib.boulder.ibm.com/tividd/td/tdprodlist.html
You can order many Tivoli publications online at the following Web site:
http://www.elink.ibmlink.ibm.com/public/applications/
publications/cgibin/pbi.cgi
You can also order by telephone by calling one of these numbers:
http://www.elink.ibmlink.ibm.com/public/applications/publications/
cgibin/pbi.cgi
Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to use software products successfully. For the warehouse pack, you use the interfaces of IBM DB2 and the reporting tool. See those documentation sets for accessibility information.
IBM Software Support provides assistance with product defects.
Before contacting IBM Software Support, your company must have an active IBM software maintenance contract, and you must be authorized to submit problems to IBM. The type of software maintenance contract that you need depends on the type of product you have:
If you are not sure what type of software maintenance contract you need, call 1-800-IBMSERV (1-800-426-7378) in the United States or, from other countries, go to the contacts page of the IBM Software Support Handbook on the Web (http://techsupport.services.ibm.com/guides/contacts.html) and click the name of your geographic region for phone numbers of people who provide support for your location.
Follow the steps in this topic to contact IBM Software Support:
When you report a problem to IBM, you are asked to supply a severity level. Therefore, you need to understand and assess the business impact of the problem you are reporting. Use the following criteria:
Severity 1 | Critical business impact: You are unable to use the program, resulting in a critical impact on operations. This condition requires an immediate solution. |
Severity 2 | Significant business impact: The program is usable but is severely limited. |
Severity 3 | Some business impact: The program is usable with less significant features (not critical to operations) unavailable. |
Severity 4 | Minimal business impact: The problem causes little impact on operations, or a reasonable circumvention to the problem has been implemented. |
When explaining a problem to IBM, be as specific as possible. Include all relevant background information so that IBM Software Support specialists can help you solve the problem efficiently. To save time, know the answers to these questions:
You can submit your problem in one of two ways:
If the problem you submit is for a software defect or for missing or inaccurate documentation, IBM Software Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Software Support provides a workaround for you to implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the IBM product support Web pages daily, so that other users who experience the same problem can benefit from the same resolutions.
For more information about problem resolution, see Searching knowledge bases and Obtaining fixes.
If you have a problem with your IBM software, you want it resolved quickly. Begin by searching the available knowledge bases to determine whether the resolution to your problem is already documented.
IBM provides extensive documentation that can be installed on your local machine or on an intranet server. You can use the search function of this information center to query conceptual information, instructions for completing tasks, reference information, and support documents.
Tip: Update your information center with the latest support information.
If you cannot find an answer to your question in the information center, search the Internet for the latest, most complete information that might help you resolve your problem. To search multiple Internet resources for your product, expand the product folder in the navigation frame to the left and select Support on the Web. From this topic, you can search a variety of resources including:
A product fix might be available to resolve your problem. You can determine what fixes are available for your IBM software product by checking the product support Web site:
To receive weekly e-mail notifications about fixes and other news about IBM products, follow these steps:
For more information about types of fixes, see the Software Support Handbook (http://techsupport.services.ibm.com/guides/handbook.html).
Information centers typically include one or more support information plug-ins. These plug-ins add IBM technotes and other support documents to the information center. The following steps describe how to update your support information plug-ins:
User groups provide software professionals with a forum for communicating ideas, technical expertise, and experiences related to the product. They are located on the Internet, and are available using standard news reader programs. These groups are primarily intended for user-to-user communication, and are not a replacement for formal support.
To access a newsgroup, use the instructions appropriate for your browser.
IBM Tivoli Enterprise Console
news://news.software.ibm.com/ibm.software.tivoli.enterprise-console
IBM Tivoli NetView(R) for UNIX and IBM Tivoli NetView for Windows
news://news.software.ibm.com/ibm.software.tivoli.netview-unix-windows
The section provides information about terminology, typeface conventions, and operating system-dependent commands that are used in this guide.
This section provides information about terminology that is used in this guide.
This guide uses the following typeface conventions:
This guide uses the UNIX convention for specifying environment variables and for directory notation.
When using the Windows command line, replace $variable with %variable% for environment variables and replace each forward slash (/) with a backslash (\) in directory paths. The names of environment variables are not always the same in Windows and UNIX. For example, %TEMP% in Windows is equivalent to $tmp in UNIX.
This document uses the following special characters to define the command syntax:
The following sections provide an overview of Tivoli Data Warehouse and the warehouse pack for Tivoli Enterprise Console.
Tivoli Data Warehouse provides the infrastructure for the following:
As shown in Figure 1, Tivoli Data Warehouse consists of a centralized data store where historical data from many management applications can be stored, aggregated, and correlated.
The central data warehouse uses a generic schema that is the same for all applications. As new components or new applications are added, more data is added to the database; however, no new tables or columns are added in the schema.
A data mart is a subset of a data warehouse that contains data that is tailored and optimized for the specific reporting needs of a department or team.
The central data warehouse ETL reads the data from the operational data stores of the application that collects it, verifies the data, makes the data conform to the schema, and places the data into the central data warehouse.
The data mart ETL extracts a subset of data from the central data warehouse, transforms it, and loads it into one or more star schemas, which can be included in data marts to answer specific business questions.
A program that provides these ETLs is called a warehouse enablement pack or simply warehouse pack.
The ETLs are typically scheduled to run periodically, usually during non-peak hours.
The Tivoli Enterprise Console product is a rule-based event management application that integrates system, network, database, and application management to help ensure the optimal availability of the IT resources in an enterprise. The Tivoli Enterprise Console product collects, processes, and automatically responds to common management events, such as a database server that is not responding, a lost network connection, or a successfully completed batch processing job. These events are stored in a relational database called the event database.
This warehouse pack stores raw Tivoli Enterprise Console events in the Tivoli Data Warehouse. A raw event is an event that is generated by a source. This warehouse enablement pack stores the raw base slot event information and it maps all of the values to event attributes in the Tivoli Data Warehouse. Except for the fully qualified hostname, fqhostname, extended attribute information is not stored in the Tivoli Data Warehouse.
Event information in the reports can be used for current problem diagnosis and for future problem trend analysis.
When the warehouse pack is installed, the following extract, transform, and load (ETL) processes are installed on the control server in the EC2_Tivoli_Enterprise_Console_v3.9.0_Subject_Area:
For more information, see ETL Processes.
The source of event data for the warehouse pack is the event database. The default name of the ODBC driver connection to the event database is TEC. If your event database is not a DB2 database, see Configuring database client drivers for information about installing and configuring your ODBC driver.
Source event information is contained in the following tables and views in the event database:
The following types of data are stored in the central data warehouse:
This warehouse pack contains predefined reports that provide information about the base event information. For more information about the predefined reports that are provided, see Reports.
A source database contains the information that an ETL uses and a target is the database in which the output data from the ETL is stored.
The Tivoli Enterprise Console warehouse pack the central data warehouse ETL supports multiple event database sources; therefore, the EC2_TEC_Source can point to multiple event databases.
The Tivoli Enterprise Console warehouse pack uses the following data sources and targets:
Name in DB2 Data Warehouse Center | Description |
---|---|
EC2_TEC_Source | This data source points to one or more event databases. |
EC2_TWH_CDW_Source | This data source points to the TWH_CDW database. It is used for data mart ETL processing. |
EC2_TWH_CDW_Target | This data source points to the TWH_CDW database. It is used for central data warehouse ETL processing. |
EC2_TWH_MART_Source | This data source points to the TWH_MART database. It is used for data mart ETL processing. |
EC2_TWH_MART_Target | This data source points to the TWH_MART database. It is used for data mart ETL processing. |
This chapter provides information about the predefined reports that are provided by the Tivoli Enterprise Console warehouse pack. For a description of the predefined reports that are provided, see Table 2.
The following data mart tables are used to create all of the predefined reports:
Figure 2 shows the relationships between the data mart tables:
This section provides general information about the predefined reports. Information in this section applies to all reports unless noted otherwise.
Severity is displayed in the following order:
Table 2 provides a description of the predefined reports that are provided:
Report name | Description |
---|---|
Top Ten Event Classes by Status and Severity |
This report displays the top 10 event classes that received the most events for the time frame that was specified. You can customize the query by specifying the following:
The details section (the text based information at the bottom of the report) of the report displays textual information that is represented by the bar graph. You can display one or more event details that make up any one of the bars by clicking the Event Class name in the details section. When you click the name, a subreport is run and it is displayed. The subreport contains more detailed event information and is grouped by severity and status. The subreport only contains information for one event class, which is determined by the event class that you clicked. |
Events for Event Class by Status |
This report displays all the events in a given time range for a specific event class. The events are categorized by severity. A pie chart displays the total percentage of events by severity. The events used in the pie chart are only the events that match the criteria of this report. You can customize the query by specifying the following:
Note:
You can select only one event class per report.
The breakdown of the events is by severity received for the specified event class, which is shown in a pie chart. The details for the graph are not displayed. However, in the details sections, additional information about the events that were received for this event class is provided. The details section is grouped by severity and status, and ordered according to the report assumptions described in General information about reports. |
Top Ten Sources with Most Events by Event Class, Status and Severity |
This report displays the top 10 systems that have received the most events for the time frame that was specified. You can customize the query by specifying the following:
The details section contains a textual version of the information that is depicted graphically in the graph. You can display more information about a source when you click on the source. This subreport contains more detailed event information and is grouped by event class, severity and status. The subreport only contains information for one source, which is determined by the source you clicked. |
Events for Source by Status |
This report displays all of the events for a specific system and for the time frame that was specified. You can customize the query by specifying the following:
|
Top Ten Hostnames/IP Addresses with Most Events by Event Class, Status and Severity |
This report displays the top 10 hostnames or IP Addresses that have received the most events for the time frame that was specified. You can customize the query by specifying the following:
|
Events for Hostname/IP Address by Status |
This report displays all the events for a hostname or IP Address for the time frame that was specified. You can customize the query by specifying the following:
|
Number of Events by Event Class, Severity, and Status over Time |
This report displays the event volume received for a specified severity for the time frame that was specified. You can customize the query by specifying the following:
|
Number of Events for Hostnames / IP Addresses by Event Class, Severity and Status over Time |
This report displays the event volume received for a specified severity for the specified period of time. You can customize the query by specifying the following:
|
Average Time to Close Events by Severity |
This report displays the average time it takes to close events based on their severity. You can customize the query by specifying the following:
|
Average Time to Close Events by Source |
This report displays the time it takes on average to close events based on their source. You can customize the query by specifying the following:
The details section provides more information about the graph. This report only runs against closed events. |
Average Time to Close Events by Event Class |
This report displays the time it takes on average to close events based on their Event Class. You can customize the query by specifying the following:
|
This section describes the installation and configuration of the warehouse pack.
Before installing the warehouse pack for Tivoli Enterprise Console, you must install the following software:
Fix pack 11 is required if your event database is a Sybase database. Additional tasks must be performed to configure this. For more information, see Product notes and limitations.
The procedure in the How to configure the CGI Web Connector with IBM HTTP Server document to enable Crystal Enterprise to use IBM HTTP Server is incorrect. For the correct information, see Problem determination.
For information about the hardware and software requirements of Tivoli Data Warehouse and Crystal Enterprise, see the Tivoli Data Warehouse Release Notes.
This section provides additional information about the Tivoli Enterprise Console warehouse pack.
db2 connect to twh_mart db2 drop view RPI.ss_joincols db2 create view RPI.ss_joincols as SELECT ss.name as ssname, a1.largedrschemaname as schema, a1.largedrtablename as tabname, a1.largename as colname FROM IWH.AttributeLink at, IWH.Relationship r1, IWH.StarSchema ss, IWH.Relationship r2, IWH.attribute a1 WHERE at.type='JOIN' and at.iwhid = r1.source_iwhid and r1.relation_name = 'StarSchema_TO_AttLnk' and r1.target_iwhid = ss.iwhid and r2.relation_name = 'AttLink1_TO_Attr_Rel' and r2.source_iwhid = at.iwhid and a1.iwhid = r2.target_iwhid UNION SELECT ss.name as ssname, a1.largedrschemaname as schema, a1.largedrtablename as tabname, a1.largename as colname FROM IWH.AttributeLink at, IWH.Relationship r1, IWH.StarSchema ss, IWH.Relationship r2, IWH.attribute a1 WHERE at.type='JOIN' and at.iwhid = r1.source_iwh id and r1.relation_name = 'StarSchema_TO_AttLnk' and r1.target_iwhid = ss.iwhid and r2.relation_name = 'AttLink2_TO_Attr_Rel' and r2.source_iwhid = at.iwhid and a1.iwhid = r2.target_iwhid
Ensure that there is sufficient space in your databases for the data that is collected by this warehouse pack. The information in Table 3 is based on a typical installation. It is important that you analyze your installation to determine your actual requirements.
Database | Assumptions | Disk space |
---|---|---|
Central data warehouse |
|
1 Gigabyte |
Data mart |
|
200 Gigabytes |
The following formula was used to determine the central data warehouse disk space size:
number of events x 10 500 bytes + number of relationships x 40 bytes = total bytes
The following formula was used to determine the data mart disk space size:
number of events x 2 000 bytes + number of statuses x 3 000 bytes + number of severities x 3 000 bytes = total bytes
Review the tasks in this section before you begin to install the warehouse pack.
Information | Description | Record your information |
---|---|---|
ODBC source name 1 | The name for the ODBC connection to Tivoli Enterprise Console. The default value is TEC. | |
User ID | The user name of the DB2 instance owner for the event database. | |
Password | The password for the database user. | Do not record the password. |
Database type | Can be one of the following types:
|
|
Tivoli Enterprise Console event database server name, alias, or file path. | Specifies the server that the instance for the event database is installed on. | |
Tivoli Enterprise Console event database port | The port number that is used by the Tivoli Enterprise Console event database. | |
Notes:
|
From a DB2 command prompt, issue the following SQL statements to create the index:
Install the warehouse pack as described in Installing and Configuring Tivoli Data Warehouse. Use the twh_install_props.cfg installation properties file that is located in the /tdw_weps/ec2/v110/ directory.
You can schedule the time that you want the ETL to run when you install the warehouse pack. If you schedule the ETL at this time, you must specify the time that you want the ETL to run. For more information about scheduling the ETL, see Schedule the ETLs.
After you install the warehouse pack, you must perform the following procedures in the order specified. After you complete each step, return to this section and perform the next procedure that is specified until all of the procedures have been performed.
CDWIW0028W To complete the warehouse pack configuration, manually run the initialization step EC2_m05_s010_mart_initialization as well as any additional steps documented in the warehouse pack implementation guide. The ETL, while scheduled based on the options selected, will not run until these steps have been performed.Use the following procedures to perform this task:
This section provides information about creating the event filter table using the wtdwfilter command. For more information about the wtdwfilter command, see wtdwfilter.
Use the following procedure to create the event filter table:
chmod 750 wtdwfilter
This section provides information about scheduling your ETL to run. Review the information in this section before you schedule the ETL.
If you did not schedule the ETLs to run when you installed the warehouse pack, you must now schedule the EC2_c05_ETL1_Process process to run periodically. Review the following information and then schedule the EC2_c05_ETL1_Process process to run using the procedure in Installing and Configuring Tivoli Data Warehouse.
This Tivoli Enterprise Console warehouse pack is a new version. It does not replace earlier versions of the Tivoli Enterprise Console warehouse packs.
Use the uninstallation procedures in the Installing and Configuring Tivoli Data Warehouse to uninstall the Tivoli Enterprise Console warehouse pack. Once you have finished that procedure, perform the following tasks:
To use the Tivoli Data Warehouse to separate data for multiple data centers, you must use SQL scripts to configure the following values:
Information for scripts | Value or location |
---|---|
Field in source data | The value that matches the hostname base attribute of the raw event. The ETL determines this by comparing the value of this attribute with the values in the EC2.CENTR_LOOKUP table. |
Name of lookup table | EC2.CENTR_LOOKUP table |
Name of center list | TWG.Centr |
For the procedures and example SQL statements that are used to configure Tivoli Data Warehouse to separate data for multiple data centers, see the Installing and Configuring Tivoli Data Warehouse.
After the initial configuration for multiple data centers, you must modify the EC2.CENTR_LOOKUP table to map the hostname to the data center when data centers are added and removed.
You can use the DB2 Data Warehouse Center to view or sample the source event data in the tables if your event database is a DB2 database. However, you must modify the name of the table before you can view or sample the source event data if your event database is not a DB2 database. For the procedure to modify the schema name, see Changing the schema name.
After you install the warehouse pack, you can configure Tivoli Data Warehouse to separate data for the multiple customer environments. To configure this, you must create SQL scripts with the following values:
Information for scripts | Value or location |
---|---|
Field in source data | The value that matches the hostname base attribute of the raw event. The ETL determines this by comparing the value of this attribute with the values in the EC2.CENTR_LOOKUP table. |
Name of lookup table | EC2.CUST_LOOKUP table |
Column to use for lookup | Cust_ID |
Name of customer list | TWG.Cust |
For the procedural instructions and example SQL statements, see the information about warehouse pack installation in the Installing and Configuring Tivoli Data Warehouse guide.
After the initial configuration for multiple customer environment, you must modify the EC2.CUST_LOOKUP table when customers are added and removed.
You can use the DB2 Data Warehouse Center to view or sample the source event data in the tables if your event database is a DB2 database. However, you must modify the name of the table before you can view or sample the source event data if your event database is not a DB2 database. For the procedure to modify the schema name, see Changing the schema name.
This section describes maintenance tasks for the warehouse pack.
See Installing and Configuring Tivoli Data Warehouse for information about backing up and restoring your data. This Tivoli Enterprise Console warehouse pack requires no additional procedures.
This section provides information about pruning data from the central data warehouse database and data mart database.
Parameters are provided to control how often the databases are pruned. The parameter values represent a date duration whose format is yyyymmdd. Preceding zeros are not included in the date duration value. For example, the value 0000300 represents three months. The following are examples of other values that are used:
yyyymmdd | Example value |
---|---|
600 | 6 months |
10000 | 1 year |
0050000 | 5 years |
To manage the high volume of event data, use the Prune_Event_Ctrl table to delete that data. The Prune_Event_Log table keeps a history of data pruning.
By default, the data older than 6 months is pruned when the CDW_c05_Prune_and_Mark_Active process runs. This process is within the CDW_Tivoli_Data_Warehouse_v1.2.0_Subject_Area. By default, this process runs daily at 6:00 a.m.
Tivoli Data Warehouse uses the event age and the event date and time to find aged events. Aged events are ones that are older than the value specified in the Event_Age column. Then, the following data is deleted in this order:
Table 6 shows an example of the values that the Tivoli Enterprise Console specifies in the Prune_Event_Ctrl table.
MSrc_CD CHAR (6) | TmSum_CD CHAR(1) | Event_Age |
---|---|---|
EC2 | P | 600 |
This means that event data is retained by default for 6 months in the central data warehouse. Use the following SQL statement on the control server at the DB2 prompt to change the default value:
update twg.prune_event_ctrl set Event_Age=x where MSrc_Cd='EC2'
The value x is the new value that you want to specify. For an explanation of the value format, see Pruning data.
Pruning data from the fact tables is implemented in the EC2_m10_s010_pre_extract step. The prune mart control table EC2.Prune_Mart_Control specifies which data are pruned and contains a date duration value for the fact table(s). By default, all fact data older than 1 year is pruned when the process step runs.
The record of data pruning is written in the EC2.Prune_Mart_log table.
Specify the data to be pruned by setting the value of the PMARTC_DURATION column of the Prune_MART_Control table. Modify the value using an SQL statement on the control server at the DB2 prompt. For example, modify and then use the following SQL command on the control server at the DB2 prompt on the data mart (EC2_MART) to change the prune values:
UPDATE EC2.PRUNE_MART_Control
SET PMARTC_DURATION =xxx
WHERE TABLE_NAME='EC2.F_EVENT_PIT'
The value xxx is the value you want to change. For an explanation of the value format, see Pruning data.
The extraction control table assists you in incrementally extracting data from a source database. For an example of incremental extraction, see the Enabling an Application for Tivoli Data Warehouse guide. Table 7 and Table 8 provide the extract control information.
ExtCtl_
Source VARCHAR (120) |
ExtCtl_
Target VARCHAR (120) |
ExtCtl_
From_ RawSeq CHAR (10) |
ExtCtl_
To_ RawSeq CHAR (10) |
ExtCtl_
From_ IntSeq BIGINT |
ExtCtl_
To_ IntSeq BIGINT |
ExtCtl_
From_ DtTm TIME STAMP |
ExtCtl_
To_ DtTm TIME STAMP |
MSrc_
Corr_Cd CHAR (6) |
---|---|---|---|---|---|---|---|---|
1x.tec_t_evt_rep | EC2.stage_events | 0 | 0 | 0 | 0 | 1970-01-01-00.00. 00.000000 |
1970-01-01-00.00. 00.000000 |
EC2 |
1 The central data warehouse ETL can be sourced from multiple databases. Each source has a different value specified for x in ExtCtl_Source.
ExtCtl_
Source VARCHAR (120) |
ExtCtl_
Target VARCHAR (120) |
ExtCtl_
From_ RawSeq CHAR (10) |
ExtCtl_
To_ RawSeq CHAR (10) |
ExtCtl_
From_ IntSeq BIGINT |
ExtCtl_
To_IntSeq BIGINT |
ExtCtl_
From_ DtTm TIME STAMP |
ExtCtl_
To_ DtTm TIME STAMP |
MSrc_
Corr_Cd CHAR (6) |
---|---|---|---|---|---|---|---|---|
TWG.EVENTTYP | EC2.D_EVTTYP_
METRIC |
0 | 0 | 0 | 0 | 1970-01-01-00.00. 00.000000 |
9999-01-01-00.00. 00.000000 |
EC2 |
TWG.EVENT | EC2.F_EVENT_PIT | 0 | 0 | 0 | 0 | 1970-01-01-00.00. 00.000000 |
9999-01-01-00.00. 00.000000 |
EC2 |
TWG.EVENTATTR | EC2.F_EVENT_PIT | 0 | 0 | 0 | 0 | 1970-01-01-00.00. 00.000000 |
9999-01-01-00.00. 00.000000 |
EC2 |
This section provides supplemental information about the Tivoli Enterprise Console warehouse pack.
The wtdwfilter command is used to create and modify the event filter. The event filter is used to determine which classes of events are moved from the Tivoli Enterprise Console event database to the central data warehouse database. The event filter is an inclusive filter, which means that only events that belong to the event classes that are specified in the event filter table are moved.
wtdwfilter [option [suboption]]
Use the wtdwfilter command to perform the following tasks:
See Command line syntax for a description of the characters that are used to specify wtdwfilter command syntax.
The user that issues the wtdwfilter command must be authorized to create and delete tables, because the wtdwfilter command issues RDBMS Interface Module (RIM) commands. If an unauthorized user tries to issue the wtdwflter command, it fails when you try to create or delete the associated event filter table.
TEC_DB TEC_Error TEC_Notice TEC_Start TEC_Stop
TEC_DB TEC_Error TEC_Notice TEC_Start TEC_Stop
Use the following procedure to create a file that lists the event classes that belong to any loaded rule base:
wrb -lsrbclass Default > new.fileDefault is the name of your rule base and new.file can be any name you choose.
Class Name ---------------------------------
For more information on the wrb command, see the Tivoli Enterprise Console Command and Task Reference.
The following example creates an event filter table in a table space named yourtablespace:
wtdwfilter -crttb -tblspace yourtablespace
The following example imports into the event filter table the event classes listed in a file named class.list:
wtdwfilter -impclass -file class.list
The following is an example of the default file that lists the classes:
TEC_DB TEC_Error TEC_Notice TEC_Start TEC_Stop
The following example deletes the classes that are loaded in the rulebase named Default from the event filter table. Note that the -debug option is also specified to provide informational messages.
wtdwfilter -delclass -rb Default -debug
This warehouse enablement pack ETL can read data from multiple instances of Tivoli Enterprise Console event databases. However, each of the Tivoli Enterprise Console servers must have a different server ID to differentiate them. The server ID is 1 by default. Use the following procedure to change the server ID:
wstopesvr
wtdbclear -efl -t 0
#tec_server_handle=1
tec_server_handle=6
wstartesvr
During installation of this warehouse pack, the user name that is used to install the warehouse pack is the default schema name for each of the tables that contain the source event information in the event database. Although this does not affect the behavior of the warehouse pack, it prevents you from sampling or viewing the table contents using the DB2 Data Warehouse Center. For more information about the source tables, see Overview of the Tivoli Enterprise Console warehouse pack.
To sample or view the table contents for event databases, perform the following procedure for all data sources with a name similar to EC2_xxx_Source. EC2_TEC_Source is the default name and is used in the following procedure.
Database type | Name | More information |
---|---|---|
1 You cannot sample or view the contents of a table if your event database is a Sybase database. | ||
DB2 | Database administrator name | Specify the name of the database administrator that was used to create the event database and the source tables. |
Informix | None | Do note specify a name. |
Sybase | None | Do not specify a name. 1 |
Oracle | Database administrator name | Specify the name of the database administrator that was used to create the event database and the source tables. |
Microsoft SQL | database administrator name | Specify the name of the database administrator that was used to create the event database and the source tables. |
If your event database is not a DB2 database, the database client for your database must be installed on the control server or the Tivoli Data Warehouse remote agent to enable communication with the events database. To determine which database clients are supported by the Tivoli Data Warehouse and the procedure to install the clients, see the Tivoli Data Warehouse Release Notes. Once the client has been installed, you must configure the control server DB2 drivers as described in this section.
Do one of the following procedures on the control server for your event database type:
If your event database is an Informix database, you must configure the control server DB2 Data Warehouse drivers to communicate with the Informix database.
If your event database is a Sybase database, you must configure the Tivoli Data Warehouse DB2 Data Warehouse drivers to communicate with the Sybase database using the following procedure:
If your event database is a Microsoft SQL database, you must configure the Tivoli Data Warehouse DB2 Data Warehouse drivers to communicate with the Microsoft SQL database using the following procedure:
If your event database is a Oracle database, you must configure the Tivoli Data Warehouse DB2 Data Warehouse drivers to communicate with the Oracle database using the following procedure:
For common problems and solutions, see Installing and Configuring Tivoli Data Warehouse.
If you have a problem with this warehouse pack, review the information in this section.
======================== = Generic file line # : 328 = Script file line # : 110 = Entering xferTable : TEC (IBM DB2) -> TWH_CDW (IBM DB2) = Unaltered SQL Stmt : "insert into EC2.stage_evt_reln ( server_handle, event_handle, date_recpt_orig, cause_date_recep, cause_evt_hndl, src_corr_val, tgt_corr_val ) SELECT a.server_hndl, a.event_hndl, a.date_reception, a.cause_date_receptn, a.cause_event_handle, {fn CONCAT({fn RTRIM(CAST (a.server_hndl as char(10)))}, {fn CONCAT('-', {fn CONCAT({fn RTRIM(CAST (a.cause_event_handle as char(10)))}, {fn CONCAT('-',{fn RTRIM(CAST (a.cause_date_receptn as char(10)))})})})})}, {fn CONCAT({fn RTRIM(CAST (a.server_hndl as char(10)))}, {fn CONCAT('-', {fn CONCAT({fn RTRIM(CAST (a.event_hndl as char(10)))}, {fn CONCAT('-',{fn RTRIM(CAST (a.date_reception as char(10)))})})})})} FROM tec_t_evt_rep a, EC2_src_extctl b, tec_evt_filter c WHERE NOT EXISTS ( SELECT 1 FROM EC2_srcchk_run d WHERE d.db_instance_num = '1' AND d.table_name = 'EC2.stage_evt_reln' ) AND b.extctl_source = '1.tec_t_evt_rep' AND a.last_modified_time <= b.extctl_to_dttm AND a.last_modified_time >= b.extctl_from_dttm AND a.class = c.class" = Select Statement : " SELECT a.server_hndl, a.event_hndl, a.date_reception, a.cause_date_receptn, a.cause_event_handle, {fn CONCAT({fn RTRIM(CAST (a.server_hndl as char(10)))}, {fn CONCAT('-', {fn CONCAT({fn RTRIM(CAST (a.cause_event_handle as char(10)))}, {fn CONCAT('-',{fn RTRIM(CAST (a.cause_date_receptn as char(10)))})})})})}, {fn CONCAT({fn RTRIM(CAST (a.server_hndl as char(10)))}, {fn CONCAT('-', {fn CONCAT({fn RTRIM(CAST (a.event_hndl as char(10)))}, {fn CONCAT('-', {fn RTRIM(CAST (a.date_reception as char(10)))})})})})} FROM tec_t_evt_rep a, EC2_src_extctl b, tec_evt_filter c WHERE NOT EXISTS ( SELECT 1 FROM EC2_srcchk_run d WHERE d.db_instance_num = '1' AND d.table_name = 'EC2.stage_evt_reln' ) AND b.extctl_source = '1.tec_t_evt_rep' AND a.last_modified_time <= b.extctl_to_dttm AND a.last_modified_time >= b.extctl_from_dttm AND a.class = c.class" CDWEX8087E A general SQL error occurred: SQL_ERROR: 'Execute Src Select' 2004.05.18 08:50:21.735 sqlState = 42S02, nativeErr = -204, errorMsg = [IBM][CLI Driver][DB2/NT] SQL0204N "DB2.TEC_EVT_FILTER" is an undefined name. SQLSTATE=42704 . ======== Aborted (16) 2004.05.18 08:50:21.735 ========
The step should be changed as follows:
net stop vwlogger
net start vwkernel
The warehouse pack has the following processes:
This process contains the initialization step that extracts the translated event severity and status values from the TWG.TRANSLATED_TERM tables and loads the data into the EC2.D_SEVERITY and EC2.D_STATUS tables.
The process step must be manually run only once before the EC2_c05_ETL1_Process and EC2_m10_ETL2_Process processes are run.
This process has the following step:
This process contains the steps that are responsible for extracting raw events from the Tivoli Enterprise Console event database, transforming this data to fit into the schema, and loading the data into Tivoli Data Warehouse.
This process should be scheduled to run on a nightly basis. The process steps can run manually also. For information about how to run the steps manually, see Installing and Configuring Tivoli Data Warehouse.
This process has the following steps:
If errors occur in this process, they are displayed in the Work In Progress window in the DB2 Data Warehouse Center. A red X is displayed for the step that failed during this process. To determine more information about the error, see the log files for the step that are located in the $TIVOLI_COMMON_DIR\cdw\logs\etl directory under the root directory of your DB2 installation. For more information about the error information, see Installing and Configuring Tivoli Data Warehouse.
This process contains four steps that extract event data from the central data warehouse, transform the data to fit into the Tivoli Enterprise Console 3.9 data mart schema, and loads the data into the data mart.
This process has the following steps:
If errors occur in this process, they are displayed in the Work In Progress window in the DB2 Data Warehouse Center. A red X is displayed for the step that failed during this process. To determine more information about the error, see the log files for the step that are located in the $TIVOLI_COMMON_DIR\cdw\logs\etl directory under the root directory of your DB2 installation. For more information about the error information, see Installing and Configuring Tivoli Data Warehouse.
Before reading this section, read about the generic schema for the central data warehouse, which is described in Enabling an Application for Tivoli Data Warehouse. That document defines the content of each table and explains the relationships between the tables in this document.
Shaded columns in the following tables are translated. These columns are also marked with an asterisk (*) after the column name.
This section provides a sample scenario that provides an example of how information about Tivoli Enterprise Console events is stored in Tivoli Data Warehouse. The event information in this chapter is based on the following example scenario:
Table 10 provides the event information that was generated in step 1.
Event | Table or view | Column value |
---|---|---|
Event 1 | TEC_T_EVT_REP |
CLASS - TEC_Start DATE_RECEPTION - 1075915924 SERVER_HANDLE - 1 EVENT_HANDLE - 1 SEVERITY - 20 STATUS - 0 LAST_MODIFIED_TIME - Feb. 4, 2004 11:32:04 AM SOURCE - TEC HOSTNAME - ibmuser.ibm.com REPEAT_COUNT - 0 DATE_EVENT - Feb 04 11:32:04 2004 MSG - TEC Event Server Initialized MSG_INDEX - 0 NUM_ACTIONS - 0 CREDIBILITY - 1 ACL-[admin] CAUSE_DATE_RECEPTION - 0 CAUSE_EVENT_HANDLE - 0 |
TEC_T_SLOTS_EVT |
DATE_RECEPTION - 1075915924 SERVER_HANDLE - 1 EVENT_HANDLE - 1 SLOT_NAME - fqhostname SHORT_SLOT_VALUE - ibmuser.ibm.com LONG_SLOT_VALUE - NULL |
|
TEC_T_SEVERITY |
10 - UNKNOWN 20 - HARMLESS 30 - WARNING 40 - MINOR 50 - CRITICAL 60 - FATAL |
|
TEC_T_STATUS_EVENT |
0 - OPEN 10 - RESPONSE 20 - ACK 30 - CLOSED |
|
Event 2 | TEC_T_EVT_REP |
CLASS - TEC_Error DATE_RECEPTION - 1075915941 SERVER_HANDLE - 1 EVENT_HANDLE - 1 SEVERITY - 30 STATUS - 0 LAST_MODIFIED_TIME - Feb. 4, 2004 11:32:21 AM SOURCE - TEC HOSTNAME - ibmuser.ibm.com REPEAT_COUNT - 0 DATE_EVENT - Feb 04 11:32:21 2004 MSG - TEC encountered error processing rule xyz MSG_INDEX - 0 NUM_ACTIONS - 0 CREDIBILITY - 1 ACL-[admin] CAUSE_DATE_RECEPTION - 0 CAUSE_EVENT_HANDLE - 0 |
TEC_T_SLOTS_EVT |
DATE_RECEPTION - 1075915941 SERVER_HANDLE - 1 EVENT_HANDLE - 1 SLOT_NAME - fqhostname SHORT_SLOT_VALUE - ibmuser.ibm.com LONG_SLOT_VALUE - NULL |
|
TEC_T_SEVERITY |
10 - UNKNOWN 20 - HARMLESS 30 - WARNING 40 - MINOR 50 - CRITICAL 60 - FATAL |
|
TEC_T_STATUS_EVENT |
0 - OPEN 10 - RESPONSE 20 - ACK 30 - CLOSED |
|
Event 3 | TEC_T_EVT_REP |
CLASS - TEC_Notice DATE_RECEPTION - 1075915942 SERVER_HANDLE - 1 EVENT_HANDLE - 1 SEVERITY - 30 STATUS - 0 LAST_MODIFIED_TIME - Feb. 4, 2004 11:32:22 AM SOURCE - TEC HOSTNAME - ibmuser.ibm.com REPEAT_COUNT - 0 DATE_EVENT - Feb 04 11:32:22 2004 MSG_INDEX - 0 NUM_ACTIONS - 0 CREDIBILITY - 1 ACL-[admin] CAUSE_DATE_RECEPTION - 1075915941 CAUSE_EVENT_HANDLE - 1 |
TEC_T_SLOTS_EVT |
DATE_RECEPTION - 1075915942 SERVER_HANDLE - 1 EVENT_HANDLE - 1 SLOT_NAME - fqhostname SHORT_SLOT_VALUE - ibmuser.ibm.com LONG_SLOT_VALUE - NULL |
|
TEC_T_SEVERITY |
10 - UNKNOWN 20 - HARMLESS 30 - WARNING 40 - MINOR 50 - CRITICAL 60 - FATAL |
|
TEC_T_STATUS_EVENT |
0 - OPEN 10 - RESPONSE 20 - ACK 30 - CLOSED |
The next group of events provides an example of how updated events are moved into Tivoli Data Warehouse for steps 2 through 6.
There are two classifications of updated events:
The event information in Table 11 provides an example of both types of updates to the original events. The entire event is listed, however, only the highlighted fields have been modified.
Event | Table or view | Column value |
---|---|---|
Event 1 | TEC_T_EVT_REP |
CLASS - TEC_Start DATE_RECEPTION - 1075915924 SERVER_HANDLE - 1 EVENT_HANDLE - 1 SEVERITY - 20 STATUS - 30 LAST_MODIFIED_TIME - Feb. 4, 2004 11:35:05 AM SOURCE - TEC HOSTNAME - ibmuser.ibm.com REPEAT_COUNT - 0 DATE_EVENT - Feb 04 11:32:04 2004 MSG - TEC Event Server Initialized MSG_INDEX - 0 NUM_ACTIONS - 0 CREDIBILITY - 1 ACL-[admin] CAUSE_DATE_RECEPTION - 0 CAUSE_EVENT_HANDLE - 0 DURATION - 181 |
TEC_T_SLOTS_EVT |
DATE_RECEPTION - 1075915924 SERVER_HANDLE - 1 EVENT_HANDLE - 1 SLOT_NAME - fqhostname SHORT_SLOT_VALUE - ibmuser.ibm.com LONG_SLOT_VALUE - NULL |
|
TEC_T_SEVERITY |
10 - UNKNOWN 20 - HARMLESS 30 - WARNING 40 - MINOR 50 - CRITICAL 60 - FATAL |
|
TEC_T_STATUS_EVENT |
0 - OPEN 10 - RESPONSE 20 - ACK 30 - CLOSED |
|
Event 3 | TEC_T_EVT_REP |
CLASS - TEC_Notice DATE_RECEPTION - 1075915942 SERVER_HANDLE - 1 EVENT_HANDLE - 1 SEVERITY - 30 STATUS - 0 LAST_MODIFIED_TIME - Feb. 4, 2004 11:36:56 AM SOURCE - TEC HOSTNAME - ibmuser.ibm.com REPEAT_COUNT - 2 DATE_EVENT - Feb 04 11:32:22 2004 MSG_INDEX - 0 NUM_ACTIONS - 0 CREDIBILITY - 1 ACL-[admin] CAUSE_DATE_RECEPTION - 1075915941 CAUSE_EVENT_HANDLE - 1 |
TEC_T_SLOTS_EVT |
DATE_RECEPTION - 1075915942 SERVER_HANDLE - 1 EVENT_HANDLE - 1 SLOT_NAME - fqhostname SHORT_SLOT_VALUE - ibmuser.ibm.com LONG_SLOT_VALUE - NULL |
|
TEC_T_SEVERITY |
10 - UNKNOWN 20 - HARMLESS 30 - WARNING 40 - MINOR 50 - CRITICAL 60 - FATAL |
|
TEC_T_STATUS_EVENT |
0 - OPEN 10 - RESPONSE 20 - ACK 30 - CLOSED |
The following sections describe the component configuration.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The following sections describe the component measurement.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
TmSum_Cd | *TmSum_Nm |
---|---|
* This column is translated | |
P | Point |
MSrc_Cd | MSrc_Parent_Cd | MSrc_Nm |
---|---|---|
* This column is translated | ||
Tivoli | NULL | Tivoli Application |
EVENTS | NULL | Events |
EC2 | Tivoli | Tivoli Enterprise Console |
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The following section describes the component events.
EGrp_Cd | EGrpTyp_Cd | EGrp_Parent_Cd | *EGrp_Nm |
---|---|---|---|
* This column is translated | |||
EC2EVT | TIVOLI | NULL | Contains Tivoli Enterprise Console events |
EGrp_Cd | EGrpTyp_Cd | EventTyp_ID |
---|---|---|
EC2EVT | TIVOLI | 1 |
EC2EVT | TIVOLI | 2 |
EC2EVT | TIVOLI | 3 |
EC2EVT | TIVOLI | 4 |
EC2EVT | TIVOLI | 5 |
EGrpTyp_Cd | *EGrpTyp_Nm |
---|---|
* This column is translated | |
TIVOLI | Event Group for Tivoli Products |
The Tivoli Enterprise Console warehouse pack does not use this table.
Event_Source_ID | Event_Target_ID | RelnTyp_Cd | MSrc_Cd |
---|---|---|---|
5 | 1 | UPDATE | EC2 |
4 | 3 | UPDATE | EC2 |
2 | 3 | CAUSES | EC2 |
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use this table.
The Tivoli Enterprise Console warehouse pack does not use helper tables.
The Tivoli Enterprise Console warehouse pack does not use exception tables.
The Tivoli Enterprise Console warehouse pack supports incremental extraction. For more information about incremental extraction, see Extraction control (table Extract_Control).
The following sections contain the definition of star schemas, metric dimension tables, and data marts provided with the warehouse pack. This Tivoli Enterprise Console warehouse pack uses one star schema for all of the reports. The following sections contain the definition of the star schema. This chapter is intended primarily for report designers and warehouse pack creators. For information about reports, see Reports.
Although event correlation relationship information is stored in the central data warehouse, this information is not inserted into the Tivoli Enterprise Console 3.9 data mart.
This data mart uses the EC2 event star schema
Before using this section, read about the star schemas in Enabling an Application for Tivoli Data Warehouse. That document defines the content of each table and explains the relationships between the tables in this document.
The warehouse pack provides the following star schemas.
The following table defines the star schema.
Description of star schema (in IWH_STARSCHEMA) | |
---|---|
Name of fact tables |
|
Name of metric dimension table |
|
Name of other dimension tables |
|
The following data mart tables are used to create all of the predefined reports:
The EC2.F_EVENT_PIT table contains all of the events and base event Tivoli Enterprise Console attribute information for all events that are stored in the central data warehouse, except the acl and message attributes.
Column name | Data type | Description |
---|---|---|
Event_ID |
BIGINT |
This is the warehouse identifier for the event record. It is an incrementing counter in the warehouse. |
EventTyp_ID |
INTEGER |
This is a foreign key relationship to the EC2.D_EVTTYP_METRIC table. It references the event class of the event. |
EventStatus_ID |
INTEGER |
This is a foreign key relationship to the EC2.D_STATUS table. It references the event status. |
EventSev_ID |
INTEGER |
This is a foreign key relationship to the EC2.D_SEVERITY table. It references the event severity. |
Server_ID |
INTEGER |
Tivoli Enterprise Console server handle of the event. |
Event_DtTm |
TIMESTAMP |
This is the time the original event occurred. |
Repeat_Cnt |
INTEGER |
Repeat count of the event. |
Source |
VARCHAR(128) |
Base attribute of Tivoli Enterprise Console event |
Origin |
VARCHAR(128) |
Base attribute of Tivoli Enterprise Console event |
Hostname |
VARCHAR(255) |
Base attribute of Tivoli Enterprise Console event |
Adapter_Host |
VARCHAR(255) |
Base attribute of Tivoli Enterprise Console event |
Administrator |
VARCHAR(128) |
Base attribute of Tivoli Enterprise Console event |
Date_Event |
VARCHAR(30) |
Base attribute of Tivoli Enterprise Console event |
Duration |
DOUBLE |
Base attribute of Tivoli Enterprise Console event |
Msg_Index |
INTEGER |
Base attribute of Tivoli Enterprise Console event |
Num_Actions |
INTEGER |
Base attribute of Tivoli Enterprise Console event |
Credibility |
INTEGER |
Base attribute of Tivoli Enterprise Console event |
Sub_Origin |
VARCHAR(128) |
Base attribute of Tivoli Enterprise Console event |
Sub_Source |
VARCHAR(128) |
Base attribute of Tivoli Enterprise Console event |
Msg_Catalog |
VARCHAR(64) |
Base attribute of Tivoli Enterprise Console event |
Fqhostname |
VARCHAR(255) |
Base attribute of Tivoli Enterprise Console event |
Centr_Cd |
CHAR(6) |
Center from where original event came. |
Cust_ID |
INTEGER |
Customer from where original event came. |
The EC2.F_Event_MSG table contains all of the messages for the events that are contained in the EC2.F_EVENT_PIT table.
Column name | Data type | Description |
---|---|---|
Event_ID | BIGINT |
This is the warehouse identifier for the event record. It is an incrementing counter in the warehouse. |
MSG | VARCHAR(3500) |
Base attribute of Tivoli Enterprise Console event |
The EC2.F_Event_ACL table contains all of the access control lists (ACLs) for the events that are contained in the EC2.F_EVENT_PIT table.
Column name | Data type | Description |
---|---|---|
Event_ID | BIGINT |
This is the warehouse identifier for the event record. It is an incrementing counter in the warehouse. |
ACL | VARCHAR(3500) |
Base attribute of Tivoli Enterprise Console event |
This section describes the metric dimension table that is used by the event star schema in the warehouse pack.
The EC2.D_EVTTYP_METRIC table contains the event types for each event class in the EC2.F_EVENT_PIT table. These event types are dynamically loaded into the central data warehouse by the central data warehouse ETL. The event type is the same as the Tivoli Enterprise Console event class in the Tivoli Enterprise Console event database.
Column name | Data type | Description |
---|---|---|
EventTyp_ID |
INTEGER |
This is the internal central data warehouse identifier for the event type, or Tivoli Enterprise Console event class. |
EventTyp_Nm |
VARCHAR(254) |
This is the event type ( event class ) name. |
The following sections describe the dimension tables (other than metric dimension tables) used by the star schemas in the warehouse pack.
The EC2.D_STATUS table contains the status for each of the events in the EC2.F_EVENT_PIT table. These statuses are loaded dynamically by the central data warehouse ETL. The following default status values that are shipped with the Tivoli Enterprise Console product are loaded by the EC2_m05_ETL2_Initialization_Process process:
EventStatus_ID |
INTEGER |
This is an integer value that represents the status of the event. This is used as a foreign key relationship by the EC2.F_EVENT_PIT table to capture the appropriate translated value for the status. |
StatusNm_En |
VARCHAR(255) |
This is the English status value. |
StatusNm_De |
VARCHAR(255) |
This is the German status value. |
StatusNm_Es |
VARCHAR(255) |
This is the Spanish status value. |
StatusNm_Fr |
VARCHAR(255) |
This is the French status value. |
StatusNm_It |
VARCHAR(255) |
This is the Italian status value. |
StatusNm_Ja |
VARCHAR(255) |
This is the Japanese status value. |
StatusNm_Ko |
VARCHAR(255) |
This is the Korean status value. |
StatusNm_Pt |
VARCHAR(255) |
This is the Brazilian Portuguese status value. |
StatusNm_CN |
VARCHAR(255) |
This is the simplified Chinese status value. |
StatusNm_TW |
VARCHAR(255) |
This is the traditional Chinese status value. |
The EC2.D_SEVERITY table contains all of the severities for the events that stored in the EC2.F_EVENT_PIT table. These severities are dynamically loaded by the central data warehouse ETL; however, the severities are rearranged, so that proper sorting can be accomplished by the reports.
Column name | Data type | Description |
---|---|---|
EventSev_ID |
INTEGER |
This is an integer value that represents the severity of the event. This is used as a foreign key relationship by the EC2.F_EVENT_PIT table to capture the appropriate translated value for the severity. |
SevNm_En |
VARCHAR(255) |
This is the English severity value. |
SevNm_De |
VARCHAR(255) |
This is the German severity value. |
SevNm_Es |
VARCHAR(255) |
This is the Spanish severity value. |
SevNm_Fr |
VARCHAR(255) |
This is the French severity value. |
SevNm_It |
VARCHAR(255) |
This is the Italian severity value. |
SevNm_Ja |
VARCHAR(255) |
This is the Japanese severity value. |
SevNm_Ko |
VARCHAR(255) |
This is the Korean severity value. |
SevNm_Pt_BR |
VARCHAR(255) |
This is the Brazilian Portuguese severity value. |
SevNm_Zh_CN |
VARCHAR(255) |
This is the simplified Chinese severity value. |
SevNm_Zh_TW |
VARCHAR(255) |
This is the traditional Chinese severity value. |
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 in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product 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 it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation IBM Corporation 2Z4A/101 11400 Burnet Road Austin, 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 information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.
This information is for planning purposes only. The information herein is subject to change before the products described become available.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate 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 application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. 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 application programs conforming to IBM's application programming interfaces.
If you are viewing this information softcopy, the photographs and color illustrations may not appear.
This publication documents no intended Programming Interfaces that allow the customer to write programs to obtain services of IBM Tivoli Enterprise Console.
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:
IBM, the IBM logo, Tivoli, the Tivoli logo, AIX(R), DB2, DRDA, Informix, Tivoli Enterprise Console, and TME(R) are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.
Intel(TM), the Intel Inside logos, MMX(TM), and Pentium(R) are trademarks of Intel Corporation in the United States, other countries, or both.
Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
![]() |
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. |
Other company, product, and service names may be trademarks or service marks of others.
[ Top of Page | | Contents | Index ]