IBM Tivoli Software IBM Tivoli Software

[ Bottom of Page | Previous Page | Next Page | Contents | Index ]


Maintenance and problem determination

This section describes maintenance tasks for the warehouse pack.

Backing up and restoring data

See Installing and Configuring Tivoli(R) Data Warehouse for information about backing up and restoring your data. This Tivoli Enterprise Console(R) warehouse pack requires no additional procedures.

Pruning data

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 pruning duration whose format is yyyymmdd. Preceding zeros are not included in the pruning duration value. For example, the value 0000300 represents three months. The following are examples of other values that are used:

Table 5. Example pruning values
yyyymmdd Example value
       600 6 months
     10000 1 year
   0050000 5 years

Central data warehouse database

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.

Pruning event data (table Prune_Event_Ctrl)

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:

  1. The parent event that is an aged event (in the EventAttr table)
  2. Either the source or target that is an aged event (in the EventReln table)
  3. The relationship that involves an aged event (in the CEReln table)
  4. The aged event

Table 6 shows an example of the values that the Tivoli Enterprise Console specifies in the Prune_Event_Ctrl table.

Table 6. Prune_Event_Ctrl table example
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(R) 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.

Data mart

Pruning data from the fact tables is implemented in the EC2_m10_s050_mart_prune step. The prune mart control table EC2.Prune_Mart_Control specifies which data are pruned and contains a pruning duration value for the fact tables. 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 run 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.

Extraction control (table Extract_Control)

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.

Table 7. Central data warehouse ETL 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.stg_events 0
99999
99999
99999
999
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.

Table 8. Data mart ETL 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)
TWG.EVENTTYP EC2.D_EVTTYP_
METRIC
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
1970-01-01-00.00.
00.000000
9999-01-01-00.00.
00.000000
EC2
TWG.EVENTATTR EC2.F_EVENT_PIT 0 0
1970-01-01-00.00.
00.000000
9999-01-01-00.00.
00.000000
EC2

Reference information

This section provides supplemental information about the Tivoli Enterprise Console warehouse pack.

Event Class and Extended Attribute filters

The wtdwfilter command is used to create and modify the event filter and the extended attribute filter. These filters are respectively used to determine which classes of events and extended attributes are moved from the Tivoli Enterprise Console event database to the central data warehouse database. Both filters are inclusive filters. Only events that belong to the event classes that are specified in the event filter table are moved. Likewise, only extended attributes that are specified in the extended attribute filter table and that are also related to the specified event classes are moved.

Notes:
  1. You must create these filter tables before you run the ETLs. If you do not create them before you run the ETLs, an error message is displayed. For a description of the problem, see Problem determination.
  2. On Windows(R) systems, the wtdwfilter command must run in the bash shell. Run the script %SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd from the command line, and then enter bash to enter the bash shell environment.

wtdwfilter

Create and modify the event filter table and the extended attribute filter table.

Syntax

wtdwfilter [option [suboption]]

Description

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.

Authorization

The user who 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 wtdwfilter command, it fails when you try to create or delete the associated event filter and extended attribute filter tables.

Options

-crttb [-tblspace tablespace_name] [-debug]
Creates both the event filter table and the extended attribute filter table in the event database.
-tblspace tablespace_name
The name of the table space that these tables should be created in. If this value is not specified, both tables are created in the default table space.
Notes:
  1. The -tblspace option does not create table spaces. Table spaces must be created before they can be specified with the -tblspace option.
  2. The term table space is used by the IBM(R) DB2 and Oracle products. Other RDBMS vendors use different terminology for this concept. See Terminology for information about terminology that is used by other database vendors.
-debug
Run the option in debug mode. Informational messages are displayed.
-deltb [-debug]
Deletes the event filter table from the event database.
-debug
Run the option in debug mode. Informational messages are displayed.
-impclass {-file filename | -rb rule_base} [-debug]
Add event classes to the event filter table.
-file filename
Add event classes that are listed in filename file to the event filter table. The name of the event class is case sensitive. Event class names must be listed on separate lines. The following is an example of a file that lists classes:
TEC_DB
TEC_Error
TEC_Notice
TEC_Start
TEC_Stop
Note:
You can use the wrb command to create a file that lists the event classes that belong to any loaded rule base. For the procedure to create this file, see Usage Notes.
-rb rule_base
Add event classes that are loaded in the rule_base rulebase to the event filter table.
-debug
Run the option in debug mode. Informational messages are displayed.
-delclass {-file filename | -rb rule_base | -all} [-debug]
Delete classes from the event filter table.
-file filename
Delete event classes that are listed in filename file from the event filter table. The name of the event class is case sensitive. Event class names must be listed on separate lines. The following is an example of a file that lists classes:
TEC_DB
TEC_Error
TEC_Notice
TEC_Start
TEC_Stop
Note:
You can use the wrb command to create a file that lists the event classes that belong to any loaded rule base. For the procedure to create this file, see Usage Notes.
-rb rule_base
Delete event classes that are loaded in the rule_base rulebase from the event filter table.
-all
Delete all classes from the event filter table. This option can only be specified with the -delclass option.
-debug
Run the option in debug mode. Informational messages are displayed.
-lsclass [-debug]
List the names of the event classes that are loaded in the event filter table. The output list of names is sorted alphabetically by class name.
-debug
Run the option in debug mode. Informational messages are displayed.
-delextt [-debug]
Deletes the extended attribute filter table from the event database.
-debug
Run the option in debug mode. Informational messages are displayed.
-impattr -file filename [-debug]
Add attribute names to the extended attribute filter table.
-file filename
Add attribute names that are listed in filename file to the extended attribute filter table. The attribute name is case sensitive. Attribute names must be listed on separate lines. The following is an example of a file that lists attribute names:
sql_code
Note:
You can use the wrb command to create a file that lists the attribute names that are defined for any loaded rule base. For the procedure to create this file, see Usage Notes.
-debug
Run the option in debug mode. Informational messages are displayed.
-delattr {-file filename | -all} [-debug]
Delete attribute names from the extended attribute filter table.
-file filename
Delete attribute names that are listed in filename file from the extended attribute filter table. The attribute name is case sensitive. Attribute names must be listed on separate lines. The following is an example of a file that lists attribute names:
sql_code
Note:
You can use the wrb command to create a file that lists the attribute names that are defined for any loaded rule base. For the procedure to create this file, see Usage Notes.
-all
Delete all attribute names from the extended attribute filter table. This option can only be specified with the -delattr option.
-debug
Run the option in debug mode. Informational messages are displayed.
-lsattr [-debug]
List the attribute names that are loaded in the extended attribute filter table. The output list of attribute names is sorted alphabetically.
-debug
Run the option in debug mode. Informational messages are displayed.

Usage Notes

For more information on the wrb command, see the Tivoli Enterprise Console Command and Task Reference.

Examples

The following example creates an event filter table and extended attribute filter 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 class.list file that lists the classes:

TEC_DB
TEC_Error
TEC_Notice
TEC_Start
TEC_Stop

The following example imports into the extended attribute filter table the attribute names listed in a file named attribute.list:

wtdwfilter -impattr -file attribute.list 

The following is an example of the attribute.list file that lists the classes:

sql_code

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

The following example deletes the extended attributes that are listed in the file named classAttr.file from the extended attribute filter table. Note that the -debug option is also specified to provide informational messages.

wtdwfilter -delattr -file classAttr.file -debug

Changing the Tivoli Enterprise Console server ID

This warehouse 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:

  1. Issue the following command to stop the Tivoli Enterprise Console server:
    wstopesvr
  2. Issue the following command to purge the event database:
    wtdbclear -efl -t 0
    Note:
    This command purges your event server database. It is necessary to remove any existing events because they have server ID of 1. To ensure data integrity, the central data warehouse ETL must only read events from this database when it has the new server ID value.
  3. Edit the $BINDIR/TME/TEC/.tec_config file and change server ID as follows:
    1. Uncomment the following line:
      #tec_server_handle=1
    2. Change the server ID. For example, if you are using the server ID 6, change the line as follows:
      tec_server_handle=6
  4. Save the .tec_config file.
  5. Issue the following command to start the Tivoli Enterprise Console server:
    wstartesvr

Changing the schema name

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.

  1. From the DB2 Data Warehouse Center on the control server, click Warehouse Sources.
  2. Do the following for the EC2_TEC_Source data source:
    1. Click the + symbol next to the source name.
    2. Click on the Tables folder.
    3. For the tec_t_evt_req tables listed in the right pane, do the following:
      1. Right click the table name.
      2. From the pop-up menu, click Properties.
      3. Modify the Table Schema value. The name you use depends on the your event database type. For the value to use, see Table 9.
      4. Click OK.

Table 9. Schema names
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(R) None Do not 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(R) SQL Database administrator name Specify the name of the database administrator that was used to create the event database and the source tables.

Configuring database client drivers

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:

Configuring an Informix client

If your event database is an Informix database, you must configure the control server DB2 Data Warehouse drivers to communicate with the Informix database.

  1. Click Start -> Settings ->Control Panel. The Control Panel window is displayed.
  2. From the Control Panel, double-click Administrative Tools. The Administrative Tools window is displayed.
  3. Double-click Data Sources (ODBC). The ODBC Data Source Administrator window is displayed.
  4. From the ODBC Data Source Administrator window, click the System DSN tab.
  5. Click Add. The Create New Data Source window is displayed.
  6. Select the DataWHSE 3.60 32-bit INFORMIX driver.
  7. Click Finish. The ODBC Informix Driver Setup window is displayed.
  8. From the ODBC Informix Driver Setup Window, complete the following:
    1. Click the General tab.
    2. Type TEC in the Data Source Name field.
    3. Type the name of the event database in the Database Name field.
    4. Click the Connection tab.
    5. Type the hostname of the system on which the event database is installed in the Host Name field.
    6. Type onsoctcp in the Protocol Type field.
  9. Click Test Connect to test the connection to your event database.
  10. Click OK.

Configuring a Sybase client

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:

  1. Use the DSEdit utility that was installed with the Sybase client to create a client connection to the event database. Note the text that you type in the server field for your client connection for later use. For more information about the DSEdit Utility, see the Sybase documentation.
  2. Click Start -> Settings -> Control Panel. The Control Panel window is displayed.
  3. From the Control Panel, double-click Administrative Tools. The Administrative Tools window is displayed.
  4. Double-click Data Sources (ODBC). The ODBC Data Source Administrator window is displayed.
  5. From the ODBC Data Source Administrator window, click the System DSN tab.
  6. Click Add. The Create New Data Source window is displayed.
  7. Select the DataWHSE 3.60 32-bit Sybase driver.
  8. Click Finish. The ODBC Sybase Driver Setup window is displayed.
  9. From the ODBC Sybase Driver Setup Window, complete the following:
    1. Click the General tab.
    2. Type the value you specified in the Server field for step 1 in the Server Name field.
    3. Type the name of the event database in the Database Name field.
    4. Type TEC in the Database Source Name field.
  10. Click Test Connect to test the connection to your event database.
  11. Click OK.
DB error:
A DB2 error might occur when using a Sybase database as a data source for operational data. If this happens, see the information about Sybase ETL errors in the chapter that explains problem determination in Installing and Configuring Tivoli Data Warehouse.

Configuring a Microsoft SQL client

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:

  1. Use the SQL Server Client Network Utility that is installed with your MS SQL Server client to configure a connection to the event database as follows:
    1. Click the General tab.
    2. Ensure the TCP/IP is enabled. The Tivoli Data Warehouse does not support any other protocol for connecting to the source database.
    3. Click the Alias tab.
    4. Create a connection to the event database. Note the Server Alias value for later use.
  2. Click Start -> Settings -> Control Panel. The Control Panel window is displayed.
  3. From the Control Panel, double-click Administrative Tools. The Administrative Tools window is displayed.
  4. Double-click Data Sources (ODBC). The ODBC Data Source Administrator window is displayed.
  5. From the ODBC Data Source Administrator window, click the System DSN tab.
  6. Click Add. The Create New Data Source window is displayed.
  7. Select the DataWHSE 3.60 32-bit SQL Server driver.
  8. Click Finish. The ODBC SQL Driver Setup window is displayed.
  9. From the ODBC Informix Driver Setup Window, complete the following:
    1. Click the General tab.
    2. Type the value you specified in the Server Alias field for step 1 in the Server Name field.
    3. Type the name of the event database in the Database Name field.
    4. Type TEC in the Data Source Name field.
  10. Click Test Connect to test the connection to your event database.
  11. Click OK.

Configuring an Oracle client

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:

  1. Use the Net8 Assistant that was installed with the Oracle client to configure a connection to the event database. Note the Net Service Name used to configure the client connection for later use.
  2. Click Start -> Settings -> Control Panel. The Control Panel window is displayed.
  3. From the Control Panel, double-click Administrative Tools. The Administrative Tools window is displayed.
  4. Double-click Data Sources (ODBC). The ODBC Data Source Administrator window is displayed.
  5. From the ODBC Data Source Administrator window, click the System DSN tab.
  6. Click Add. The Create New Data Source window is displayed.
  7. Select the DataWHSE 3.60 32-bit Oracle 8 driver.
  8. Click Finish. The ODBC Oracle Driver Setup window is displayed.
  9. From the ODBC Oracle Driver Setup Window, complete the following:
    1. Click the General tab.
    2. Type the value you specified in the Net Service Name field for step 1 in the Server Name field.
    3. Type TEC in the Database Source Name field.
  10. Click Test Connect to test the connection to your event database.
  11. Click OK.

Problem determination

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.


[ Top of Page | Previous Page | Next Page | Contents | Index ]