tivoli data warehouse implementation...

IBM Tivoli Storage Area Network Manager, Version 1.3.1

Warehouse Enablement Pack, Version 1.2.0 Implementation Guide for Tivoli Data Warehouse, Version 1.2

SC32-9078-01

Note:

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

Second Edition (September 2004)

This edition applies to IBM Tivoli Storage Area Network Manager, Version 1.3.1, and to all subsequent releases and modifications until otherwise indicated in new editions.

Order publications through your sales representative or the branch office serving your locality.

Your feedback is important in helping to provide the most accurate and high-quality information. If you have comments about this book or any other IBM Tivoli Storage Area Network Manager documentation, please see “Contacting Software Support” on page 5.

© Copyright International Business Machines Corporation 2004. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM Tivoli Storage Area Network Manager Warehouse Pack Implementation Guide iii

Contents

1 About This Guide ....................................................................................................... 1 1.1 Who Should Read This Guide ..............................................................................................................................1 1.2 Publications ............................................................................................................................................................2

1.2.1 IBM Tivoli SAN Manager Library...................................................................................................................2 1.2.2 Tivoli Data Warehouse Library ........................................................................................................................2 1.2.3 Related Publications .........................................................................................................................................3 1.2.4 Accessing Publications Online .........................................................................................................................4 1.2.5 Ordering Publications .......................................................................................................................................4

1.3 Accessibility............................................................................................................................................................5 1.4 Contacting Software Support ...............................................................................................................................5 1.5 Participating in Newsgroups.................................................................................................................................5 1.6 Typeface Conventions ...........................................................................................................................................5

2 Overview ..................................................................................................................... 7 2.1 Overview of Tivoli Data Warehouse ....................................................................................................................7 2.2 Overview of Tivoli SAN Manager Warehouse Pack...........................................................................................8 2.3 Archive Table Processing....................................................................................................................................10

3 Reports...................................................................................................................... 12 3.1 Sample Report for SAN Switch/Port Availability.............................................................................................20

3.1.1 Main Report....................................................................................................................................................20 3.1.2 Report Navigation...........................................................................................................................................21

3.2 Sample Report for SAN Manager LUN/Host Availability...............................................................................22 3.2.1 Main Report....................................................................................................................................................23 3.2.2 Report Navigation...........................................................................................................................................24

3.3 Sample Report for Monitored by More Than One SAN Manager..................................................................24 3.3.1 Main Report....................................................................................................................................................25 3.3.2 Report Navigation...........................................................................................................................................26

3.4 Sample Report for Switches Monitored by SAN Manager ..............................................................................27 3.4.1 Main Report....................................................................................................................................................27 3.4.2 Report Navigation...........................................................................................................................................28

3.5 Sample Report for LUNs Monitored by SAN Manager ...................................................................................29 3.5.1 Main Report....................................................................................................................................................29 3.5.2 Report Navigation...........................................................................................................................................30

4 Installing and Configuring the Warehouse Pack................................................... 31 4.1 Prerequisite Hardware and Software ................................................................................................................32 4.2 Product Notes and Limitations...........................................................................................................................32

4.2.1 Tivoli SAN Manager Repository....................................................................................................................32 4.2.2 Restarting Process Steps .................................................................................................................................32 4.2.3 Support for Multiple Tivoli SAN Manager Servers........................................................................................33 4.2.4 Tivoli SAN Manager Repository....................................................................................................................33

4.3 Database-Sizing Considerations .........................................................................................................................33 4.3.1 Tivoli SAN Manger Repository......................................................................................................................33 4.3.2 Central Data Warehouse Storage....................................................................................................................34 4.3.3 Data Mart Storage...........................................................................................................................................35 4.3.4 Summarize Total Space Required...................................................................................................................37

4.4 Pre-installation Procedures.................................................................................................................................37 4.5 Installation of the Warehouse Pack ...................................................................................................................38 4.6 Post-installation Procedures ...............................................................................................................................39

IBM Tivoli Storage Area Network Manager Warehouse Pack Implementation Guide iv

4.7 Migration from a Previous Release of the Warehouse Pack............................................................................40 4.8 Uninstall of the Warehouse Pack .......................................................................................................................40 4.9 Multiple Data Centers .........................................................................................................................................41 4.10 Multiple Customer Environments....................................................................................................................42

5 Maintenance and Problem Determination.............................................................. 43 5.1 Scheduling ETL Processes ..................................................................................................................................43

5.1.1 Configuring a Process Dependency................................................................................................................43 5.1.2 Schedule Set Up..............................................................................................................................................46

5.2 Backing Up and Restoring ..................................................................................................................................48 5.3 Pruning Data ........................................................................................................................................................49

5.3.1 Central Data Warehouse .................................................................................................................................49 5.3.2 Data Mart........................................................................................................................................................50

5.4 Extraction Control (table Extract_Control)......................................................................................................50 5.5 Problem Determination.......................................................................................................................................52

5.5.1 Key Information to Provide when You have a Problem.................................................................................52 5.5.2 The Steps in the BTA_C10_ETL1_Process Already has the Mode Set to Production...................................53 5.5.3 Why Are My Reports Empty? ........................................................................................................................53 5.5.4 Uninstall of Warehouse Pack Never Completes .............................................................................................54 5.5.5 Debug Scenarios .............................................................................................................................................54 5.5.6 Crystal Reports Still Listed in Web Browser after Warehouse Pack Uninstall .............................................55 5.5.7 BTA_m05_s050_Mart_Prune Fails After Reinstall of Warehouse Pack........................................................55 5.5.8 BTA_m05_s040_Mart_Rollup Fails on os390...............................................................................................56

6 ETL Processes.......................................................................................................... 58 6.1 BTA_C05_Initialize_Process ..............................................................................................................................58 6.2 BTA_C10_ ETL1_Process ..................................................................................................................................58 6.3 BTA_m05_Mart_Process ....................................................................................................................................60

7 Central Data Warehouse Information ..................................................................... 61 7.1 Component configuration ...................................................................................................................................62

7.1.1 Component Type (table CompTyp) ................................................................................................................62 7.1.2 Component Extension (table Comp_ext)........................................................................................................63 7.1.3 Component (table Comp) ...............................................................................................................................63 7.1.4 Component Relationship Type (table RelnTyp) .............................................................................................65 7.1.5 Component Relationship Rule (table RelnRul) ..............................................................................................66 7.1.6 Component Relationship (table CompReln) ...................................................................................................67 7.1.7 Component Type Keyword (table CompTyp_Keyword) ...............................................................................68 7.1.8 Attribute Type (table AttrTyp) .......................................................................................................................68 7.1.9 Attribute Rule (table AttrRul).........................................................................................................................70 7.1.10 Attribute Domain (table AttrDom) ...............................................................................................................72 7.1.11 Component Type Relationship (table CTypReln) ........................................................................................74 7.1.12 Component Attribute Type Relationship (table ATypReln).........................................................................74

7.2 Component Measurement...................................................................................................................................74 7.2.1 Measurement Group Type (table MGrpTyp)..................................................................................................74 7.2.2 Measurement Group (table MGrp) .................................................................................................................75 7.2.3 Measurement Group Member (table MGrpMbr) ............................................................................................75 7.2.4 Measurement Unit Category (table MUnitCat) ..............................................................................................76 7.2.5 Measurement Unit (table MUnit) ...................................................................................................................76 7.2.6 Measurement Alias Names (table MTypReln) ...............................................................................................77 7.2.7 Time Summary (table TmSum) ......................................................................................................................78 7.2.8 Measurement Source (table MSrc) .................................................................................................................78 7.2.9 Measurement Source History (table MSrcHistory) ........................................................................................79 7.2.10 Measurement Type (table MsmtTyp) ...........................................................................................................79

IBM Tivoli Storage Area Network Manager Warehouse Pack Implementation Guide v

7.2.11 Component Measurement Rule (table MsmtRul) .........................................................................................79 7.2.12 Measurement (table Msmt)...........................................................................................................................80 7.2.13 Threshold Measurement Objective (table Mobj) ..........................................................................................82 7.2.14 Threshold Measurement Objective Range (table MobjRng) ........................................................................82 7.2.15 Threshold Severity Level (table SevLvl) ......................................................................................................82

7.3 Component Events...............................................................................................................................................82 7.4 Helper Tables .......................................................................................................................................................82 7.5 Exception tables ...................................................................................................................................................83 7.6 Incremental Extraction .......................................................................................................................................84

8 Data mart Schema Information ............................................................................... 85 8.1 BTA Data mart ....................................................................................................................................................85 8.2 Star Schemas........................................................................................................................................................86 8.3 Metric Dimension Tables ....................................................................................................................................94

8.3.1 BTA.D_SANM_METRIC..............................................................................................................................94 8.4 Dimension Tables.................................................................................................................................................96

8.4.1 Dimension Table BTA.D_SANM_SRVR......................................................................................................96 8.4.2 Dimension Table BTA.D_SANM_SWCH.....................................................................................................96 8.4.3 Dimension Table BTA.D_SANM_PORT ......................................................................................................97 8.4.4 Dimension Table BTA.D_SANM_LUN ........................................................................................................98 8.4.5 Dimension Table BTA.D_SANM_HOST ......................................................................................................98 8.4.6 Report Table BTA.R_SANM_SRV2LDEV...................................................................................................99 8.4.7 Report Table BTA.R_SANM_HOST2LUN...................................................................................................99 8.4.8 Report View BTA.V_HOST_UNASSIGN ..................................................................................................100 8.4.9 Report View BTA.V_LUN_ASSIGN ..........................................................................................................100 8.4.10 Report View BTA.V_LUN_UNASSIGN...................................................................................................101

9 Notices .................................................................................................................... 102

IBM Tivoli Storage Area Network Manager Warehouse Pack Implementation Guide vi

1 About This Guide This document describes the warehouse enablement pack, version 1.2.0.0 for IBM Tivoli Storage Area Network Manager, Version 1.3.1. This warehouse enablement pack is designed to work with Tivoli Data Warehouse, Version 1.2. This version of the Tivoli Storage Area Network Manager warehouse enablement pack (herinafter referred to as Tivoli SAN Manager) is a replacement for the previous version.

With this warehouse enablement pack (hereafter referred to as warehouse pack), you can extract historical statistics about switch/port and Logical Unit Number (LUN) availability and inventory. Information on device availability is available for analysis through the central data warehouse. The first release, version 1.1 of the warehouse pack, loads switch and port information into the central data warehouse; these statistics can be used by Tivoli products like IBM Tivoli Service Level Advisor.

Building on the enhancements provided in Tivoli Data Warehouse version 1.2 this warehouse pack introduces two new data marts and a set of five reports addressing switch/port and LUN availability for the SAN Manager.

The reports included in the warehouse pack are:

Monitored by more than one SAN Manager

Check this report if you notice discrepancies in availability status and you are extracting data from more than one Tivoli SAN Manger. This report identifies any Switch, LUN or Host whose status is being reported by more than one Tivoli SAN Manager in your Tivoli Data Warehouse.

SAN LUN/Host Availability

View the list for LUNs reporting availability incidents. This report identifies down time and percent availability of a device.

LUNs Monitored by SAN Manager

This inventory report will identify LUNs monitored by the Tivoli SAN Manger.

SAN Manager Switch/Port Availability

View the list for switches and ports reporting availability incidents. This report identifies down time and percent availability of a device.

Switches Monitored by SAN Manager

This inventory report will identify switches monitored by the Tivoli SAN Manger.

Other enhancements in this version of the warehouse pack include:

• Specific Identification of the IBM Tivoli SAN Manager server

• Information regarding LUNs and Hosts registered with the Tivoli SAN Manager

• Addition of LUN/Host data collection in central data warehouse ETL processing

• Data mart ETL processing for two sets of data marts about Switch/Port and LUN/Host information

• Extraction of data from multiple data source repositories

• Support of central data warehouse and data mart database configurations on Solaris, AIX and z/OS platforms

1.1 Who Should Read This Guide This guide is for people who do any of the following activities:

IBM Tivoli Storage Area Network Manager Warehouse Pack Implementation Guide 1

• Plan for and install the warehouse pack • Use and maintain the warehouse pack and its reports • Create new reports • Create additional warehouse packs that use data from this warehouse pack

Administrators and installers should have the following knowledge or experience:

• Basic system administration and file management of the operating systems on which the components of Tivoli Data Warehouse are installed

• An understanding of the basic concepts of relational database management • Experience administering IBM DB2 Universal Database

Additionally, report designers and warehouse pack creators should have the following knowledge or experience:

• An understanding of the source data and application • Data warehouse information and design, extract, transform, and load (ETL) processes, and online

analytical processing (OLAP)

1.2 Publications 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:

• IBM Tivoli Storage Area Network Manager • Tivoli Data Warehouse • IBM DB2, DB2 Data Warehouse Center, and DB2 Warehouse Manager • IBM Redbooks

1.2.1 IBM Tivoli SAN Manager Library The following documents are available in the Tivoli Data Warehouse library:

• Tivoli Storage Network Manager Getting Started Guide, Version 1 Release 1 Provides explanation on how to use Tivoli Storage Network Manager and intended for Storage Area Network (SAN) administrators and network operators.

• Tivoli Storage Network Manager Planning and Installation Guide, GC26-7380 Provides explanation on how to plan for, install, and configure Tivoli Storage Network Manager and intended for Storage Area network (SAN) administrators and network operators.

1.2.2 Tivoli Data Warehouse Library The following documents are available in the Tivoli Data Warehouse library. The library is available on the Tivoli Data Warehouse Documentation CD as well as online, as described in “Accessing Publications Online” on page 4.

• Tivoli Data Warehouse Release Notes, SC32-1399

Provides late-breaking information about Tivoli Data Warehouse and lists hardware requirements and software prerequisites.


• Installing and Configuring Tivoli Data Warehouse, GC32-0744

Describes how Tivoli Data Warehouse fits into your enterprise, explains how to plan for its deployment, and gives installation and configuration instructions. It contains maintenance procedures and troubleshooting information.

• Enabling an Application for Tivoli Data Warehouse, GC32-0745

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 experts 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.

• Tivoli Data Warehouse Messages, SC09-7776

Lists the messages generated by Tivoli Data Warehouse, and describes the corrective actions you should take.

1.2.3 Related Publications The following sections describe additional publications to help you understand and use Tivoli Data Warehouse.

1.2.3.1 IBM Redbooks 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:

• Introduction to Tivoli Enterprise Data Warehouse, SG24-6607-00

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.

• Planning a Tivoli Enterprise Data Warehouse Project, SG24-6608-00

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.

• Implementing Tivoli Data Warehouse 1.2, SG24-7100 Focuses on planning, installation, customization, use, maintenance, and troubleshooting topics related to the new features of Tivoli Data Warehouse, Version 1.2. This is done using a number of case study scenarios and several warehouse packs.

1.2.3.2 IBM DB2, DB2 Data Warehouse Center, and DB2 Warehouse Manager Library

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 IBM Web site:

http://www-3.ibm.com/software/data/db2/library/

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:


http://www-3.ibm.com/software/data/db2/library/

• IBM DB2 Universal Database for Windows Quick Beginnings, GC09-2971

Guides you through the planning, installation, migration (if necessary), and setup of a partitioned database system using the IBM DB2 product on Microsoft Windows.

• IBM DB2 Universal Database for UNIX Quick Beginnings, GC09-2970

Guides you through the planning, installation, migration (if necessary), and setup of a partitioned database system using the IBM DB2 product on UNIX.

• IBM DB2 Universal Database Administration Guide: Implementation, SC09-2944

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.

• IBM DB2 Universal Database Data Warehouse Center Administration Guide, SC26-9993

Provides information on how to build and maintain a data warehouse using the DB2 Data Warehouse Center.

• IBM DB2 Warehouse Manager Installation Guide, GC26-9998

Provides information on how to install the following Warehouse Manager components: Information Catalog Manager, warehouse agents, and warehouse transformers.

• IBM DB2 Universal Database and DB2 Connect Installation and Configuration Supplement, GC09-2957

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® AS, distributed installation, the configuration of distributed requests, and accessing heterogeneous data sources.

• IBM DB2 Universal Database Message Reference Volume 1, GC09-2978 and IBM DB2 Universal Database Message Reference Volume 2, GC09-2979

Lists the messages and codes issued by DB2, the Information Catalog Manager, and the DB2 Data Warehouse Center, and describes the actions you should take.

1.2.4 Accessing Publications Online 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

Note: If you print PDF documents on other than letter-sized paper, select the Fit to page check box in the Adobe Acrobat Print dialog. This option is available when you click File Print. Fit to page ensures that the full dimensions of a letter-sized page print on the paper that you are using.

1.2.5 Ordering Publications 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:

• In the United States: 800-879-2755


http://publib.boulder.ibm.com/tividd/td/tdprodlist.htmlhttp://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

• In Canada: 800-426-4968 • In other countries, for a list of telephone numbers, see the following Web site:

http://www.ibm.com/software/tivoli/order-lit/

1.3 Accessibility 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.

1.4 Contacting Software Support If you have a problem with a Tivoli product, refer to the following IBM Software Support Web site:

http://www.ibm.com/software/sysmgmt/products/support/

If you want to contact customer support, see the IBM Software Support Guide at the following Web site:

http://techsupport.services.ibm.com/guides/handbook.html

The guide provides information about how to contact IBM Software Support, depending on the severity of your problem, and the following information:

• Registration and eligibility • Telephone numbers, depending on the country in which you are located • Information you must have before contacting IBM Software Support

1.5 Participating in Newsgroups 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. You can use Web browsers like Netscape Navigator or Microsoft Internet Explorer to view these newsgroups:

Tivoli Data Warehouse

news://news.software.ibm.com/ibm.software.tivoli.enterprise-data-warehouse

1.6 Typeface Conventions This guide uses the following typeface conventions:

Bold

• Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text

• Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip and Operating system considerations)

• Column headings in a table • Keywords and parameters in text

Italic

• Citations (titles of books, diskettes, and CDs) • Words defined in text • Emphasis of words (words as words)


http://www.ibm.com/software/tivoli/order-lit/http://www.ibm.com/software/sysmgmt/products/support/http://techsupport.services.ibm.com/guides/handbook.htmlnews://news.software.ibm.com/ibm.software.tivoli.enterprise-data-warehouse

• Letters as letters • New terms in text (except in a definition list) • Variables and values you must provide

Monospace

• Examples and code examples • File names, programming keywords, and other elements that are difficult to distinguish from

surrounding text • Message text and prompts addressed to the user • Text that the user must type • Values for arguments or command options


2 Overview The following sections provide an overview of Tivoli Data Warehouse and the warehouse pack for IBM Tivoli SAN Manager.

2.1 Overview of Tivoli Data Warehouse Tivoli Data Warehouse provides the infrastructure for the following:

• Extract, transform, and load (ETL) processes through the IBM DB2 Data Warehouse Center tool • Schema generation of the central data warehouse • Historical reports

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.

Figure 1. Tivoli Data Warehouse basic architecture


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 database objects 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. If an ETL encounters data that it cannot correctly transform, it creates an entry in an exception table. Exception tables are described on page 83.

2.2 Overview of Tivoli SAN Manager Warehouse Pack IBM Tivoli SAN Manager provides customers with the ability to monitor a SAN environment and view the SAN topology graphically. This function is based on the Tivoli SAN Manager Version 1.3.1 product and includes the manager and agent components to collect SAN information, graphically display the SAN topology, and generate SNMP events when a change is detected in the SAN fabric.

The warehouse pack for IBM Tivoli SAN Manager delivers:

• Availability status of Switch/Ports

• Availability status of LUNs

• Updated central data warehouse ETL to support multi-data source extracts

• Updated central data warehouse ETL to collect LUN and Host data

• New data mart ETL

• Data mart for switch/port measurements

• Data mart for LUN measurements

• Report for Switch/Port Status

• Report LUN Status

• Asset reports on Switches and LUNs

The central data warehouse ETL process transforms source data so it conforms to the data warehouse format, and then loads it into the central data warehouse repository of Tivoli Data Warehouse. The warehouse pack also provides a set of data marts for Switch/Port and LUN information. These data marts contain information supporting the reports provided by the Tivoli SAN Manager warehouse pack.

A set of archive tables and triggers must be installed in the IBM Tivoli SAN Manager repository when the warehouse pack is installed. The archive tables and triggers enable tracking of switch, port, and LUN availability status between scheduled runs of the data extraction.

Collection of data from IBM Tivoli SAN Manager into a central data warehouse lets you see trends in storage area network operation. Tivoli Service Level Advisor and Tivoli Storage Manager can also use the historical data from IBM Tivoli SAN Manager. Refer to Figure 2 to see the interaction between the IBM Tivoli SAN Manager and the central data warehouse.


In the case of Tivoli Service Level Advisor, it pulls data from the central data warehouse into data marts that it designed to use with its reports. For information about use, installation, and configuration of Tivoli Service Level Advisor, consult the documentation for that product.

Tivoli Data Warehouse, Version 1.2, introduces the reporting tool Crystal Enterprise; five reports are available in this warehouse pack.

• Monitored by more than one SAN Manager

• SAN LUN/Host Availability

• LUNs Monitored by SAN Manager

• SAN Manager Switch/Port Availability

• Switches Monitored by SAN Manager

Using Tivoli Data Warehouse and the IBM DB2 Data Warehouse Center, the ETL processes are scheduled to do data collection at least once a day. Collection of data on a less frequent basis affects the database space required for the archive tables on the data source and may result in excessive time to process information during central data warehouse ETL and data mart ETL processing.

IBM Tivoli SAN Manager provides:

Discovery of resources and collection of data and events

Analysis and correlation of collected information

Presentation of information:

• Reporting (historical and current) • Topology display (physical and logical resources)


Tivoli Storage Area Network Manager consists of the following major components:

• Management Server - agents collect data about the SAN and send that information to the Management Server

• Managed Host - host machines, with Fibre channel cards, that are discovered and managed

• Netview Console - this console displays the SAN topology and the current state of the SAN

Note: The Tivoli Netview product is loaded as part of the IBM Tivoli SAN Manager installation.

Agents collect statistics about the SAN and send that information to the management server. Agents are used to do the following:

• Gather information about the SAN by querying switches and devices for attribute and topology information

• Gather host level information, such as file systems and volume groups

• Gather event information detected by Host Bus Adapters (HBA)

• Performs zone control functions

2.3 Archive Table Processing Three archive tables are created in the Tivoli SAN Manager Repository to track changes on LUN, switch, and port states. A switch that is not available will automatically generate a not available record for each port on that switch.

Several triggers have been created to monitor the changes for device states, when a device is added, or when a device is deleted. Adding a device will create a new record in the appropriate archive table with its current state and setting the start time to the current time. When a device is deleted or there is a change in state, the existing record in the archive table has the end time stamp updated to the current time. A new record is also created when a device state changes reflecting the new state and the start time is set to the current time. The following diagram outlines the basic processing flow related to a port:


After the extract step is run from the Tivoli Data Warehouse for the Tivoli SAN Manager, extracted records with a start and end timestamp are deleted from the archive table.


3 Reports

This section provides information about the predefined historical reports provided by the warehouse pack. Report data appears in the language used for the source database; this data cannot be converted to the language of the system where the report is requested. Report titles, parameter prompts and static column headers will appear in the language set for the platform where the report is scheduled or viewed.

Scheduling reports in the Crystal Enterprise Server to run after the Tivoli Data Warehouse extraction, insures reports containing a large amount of data will not be requested as runtime reports. Scheduling reports also produces an historical library of reports over time.

The following information is provided to summarize IBM Tivoli Storage Area Network Manager warehouse pack:

• A list of the reports • A description of the information contained in the report • The name of the table or tables used to create the report • SQL queries for modifying this report or creating a new report based on this one

Report name Description Table names SQL queries

SAN Manager Switch/Port Availability

The report lists ports that reported incidents with availability for SAN Manager since the last warehouse extract. The incident information contains timestamp outage occurred, length of outage, and percent uptime. The report summarizes detail for the switch,by port; drilldown on port displays the detail about availability incidents. The parameters permit viewing of all data or selection by a specified server, switch, time period, or percent of time available < 100%.

BTA.D_SANM_SRVR

BTA.D_SANM_SWCH

BTA.D_SANM_PORT

BTA.F_PORT_HOUR

select * from BTA.D_SANM_SRVR A, BTA.D_SANM_SWCH B, BTA.D_SANM_PORT C, BTA.F_PORT_HOUR D where D.D_SRVR_ID = A.D_SRVR_ID and D.D_SWCH_ID = B.D_SWCH_ID and D.D_PORT_ID = C.D_PORT_ID;

SAN Manager LUN/Host Availability

The report lists LUNs by SAN Manager that reported anomalies with availability since the last warehouse extract. Reports incidents about time outage occurred, length of outage, and percent uptime.

BTA.D_SANM_SRVR

BTA.D_SANM_HOST

BTA.D_SANM_LUN

BTA.F_PORT_HOUR

LUNs with Hosts select * from BTA.D_SANM_SRVR A, BTA.D_SANM_LUN B, BTA.D_SANM_HOST C, BTA.F_LUN_HOUR D Where D.D_SRVR_ID = A.D_SRVR_ID And D.D_LUN_ID = B.D_LUN_ID and D.D_HOST_ID -1 AND D.D_HOST_ID =


Parameters permit viewing of all data or selection by a specified server, time period, or percent of time available < 100%.

C.D_HOST_ID;

Monitored by more than one SAN Manager

The report lists switches or LUNs monitored by more than one SAN Manager.

BTA.V_SANM_DUPLICATES

SELECT DEVICE, DEV_NM, SAN_MGR FROM BTA.V_SANM_DUPLICATES;

Switches Monitored by SAN Manager

This asset report identifies all switches monitored by the SAN Manager. Parameters are available to customize the report output for SAN Manager servers and switches.

BTA.D_SANM_SRVR

BTA.D_SANM_SWCH

BTA.D_SANM_PORT

SELECT SRVR.SRVR_NAME, SWCH.SWCH_LOGNAME, SWCH.SWCH_VENDOR, SWCH.SWCH_TYPE, SWCH.SWCH_WWN, SWCH.SWCH_MODEL, SWCH.SWCH_RELCODE, PORT.PORT_PHY FROM (BTA.D_SANM_SWCH SWCH INNER JOIN BTA.D_SANM_PORT PORT ON SWCH.SWCH_WWN=PORT.PORT_SWCHWWN) INNER JOIN BTA.D_SANM_SRVR SRVR ON SWCH.SWCH_SRVR=SRVR.SRVR_NAME;

LUNs Monitored by SAN Manager

This asset report identifies all the LUNs known to the managed host operating system. LUNs without hosts are LUNs not configured by either the windows administrator device manager or the AIX cfgmgr tool. The report is in three sections. The source of each section is a view in the data mart. Parameters are available to customize the report output for LUNs only.

BTA.V_LUN_UNASSIGN

BTA.V_LUN_ASSIGN

BTA.V_HOST_UNASSIGN

View LUNs with Hosts: select * from bta.v_lun_assign; View LUNs with No Hosts: select * from bta.v_lun_unassign; View Hosts not assigned to any LUN: select * from bta.v_host_unassign;

Working with Report Parameters At the beginning of each report is the Report Criteria table that lists the value of preset parameters utilized in processing the report and the value of any user entered selection for the Crystal Parameters associated with an individual report.


The report information listed in the example above is the default provided on every report in the Report Criteria section. When a specific report also has parameters that the user can input to customize or limit the data in the report, those criteria would also be listed in this section.

• Report Print Date – identifies the current date the report was requested.

• Report Print Time – identifies the current time the report was requested.

• Current Time Zone – identifies the time zone used for displaying the date and time related to SAN Manager incidents. The Current Time Zone used is for the Crystal Viewer that displays the report or the time zone where the reports are scheduled. This display includes the displacement plus or minus hours from GMT, a string displaying whether the time zone uses Daylight Saving Time (DST), one or two location identifiers within that region, and a key word for the time zone preceded by the letters 'ce' (i.e. ceTimeZoneDefault).

These criteria are helpful to identify exactly when a report was generated or scheduled to run. The current time zone value also identifies the selection for the time zone that is set in the Crystal ePortfolio preferences. The viewer of a non-scheduled report can set the time zone they want used for the report or specify using the system default time zone of the web server. The report generated from the data mart will have current time and incident time set in relation to the specified time zone.


When incident information is extracted from a SAN Manager server the date and time in the records is converted to Universal Time Coordinated (UTC) and then recorded in the central data warehouse. The records in the data mart retain the UTC time so that when a report is displayed the date and time can be presented relative to the specified time zone in Crystal ePortfolio preferences. The following example specifies that the time zone should be the one local to the web server; in the Current Time Zone section of the Report Criteria the value presented is ‘System Default – ceTimeZoneDefault’. This is set from the Crystal ePortfolio interface after login by selecting Preferences.


Report Selection Parameters

The selection parameters for a report are presented after right clicking on the report title in ePortfolio and designating that you want to View the report or Schedule the report. Each method uses a different interface for collecting the parameter data.

.

For a scheduled report you click on Schedule in the drop down menu and set the report parameters by selecting Parameters in the Customize your options: drop-down menu. After the parameters are set, select Schedule to set the time you want the report to run.


When View is selected, a new report will be generated at the current time based on the parameters selected. When you are using a large database using the View selection may take a long time to process the report. As the database is extracted daily, check to see if a scheduled report already exists by selecting History list. This list will identify already existing reports, the time the report was generated and the parameters used.

Below is the sample interface for the parameter entry when View is selected.

When using the View function you must enter the value you want to use and click Select. The value is moved to the selection window. Or use the Select button to move * into the selection window. Scroll to the bottom of the page and click OK to initiate the report processing.


Below is the sample interface for the parameter entry when Schedule is selected.

Note: When using the Schedule function you must always click the ‘Add’ or ‘Add Range’ button for each parameter or the value will not be recorded.

Parameter Description Server Name – enter the server name exactly as it is recorded in the SAN Manager repository or use ALL to see all ITSANM server data.

Switch Name – enter the switch name exactly as it is recorded in the SAN Manager repository or use ALL to see everything. This parameter uses the user assigned name (i.e. switch1 or Austin); if this is not available the world wide name for the switch will be used. Note: The availability reports contain information on device anomalies if a device has not been down it will not be listed in the report.

Time Range – you must enter a start date or specify No lower bound. This will select all records until the end date. If the end date is set to No upper bound, the current date and time is utilized. This field requires both entries. Entering the date entered as the end date will select records until 00:00:00 resulting in records only until the entered date.

Note: The start and end time for the time range are used in the query to select records from the data mart tables. Because the timestamps in the data mart tables use Universal Time Coordinated (UTC) for timestamps, records will be selected that match the start and end time. When the data is displayed in the report however, it is converted to the current time zone therefore you may see records that are a day earlier or a day later that the specified criteria. This occurs due to the conversion of the timestamps to the current time zone.

Example: Start time range: 07/14/2004 00:00:00

Time zone offset: GMT –6:00, DST

Data mart timestamp: 07/14/2004 01:00:00

Report date and time: 07/13/2004 19:00:00

Percent Available – The default value for the field is less than 100%. All records with less than 100% availability will be included in the report. The data warehouse only records incidents where a switch, port, or LUN has been detected as not available.


3.1 Sample Report for SAN Switch/Port Availability This report presents Switch/Port availability status for ports reporting problems. Switches will not be listed in this report when they never reported a problem or have not reported a problem since the last prune date. Use the asset report for monitored switches to view all switches known to the Tivoli Storage Area Network Manager.

Incidents for the ports with anomalies are summarized and also provide drill down to detail by hour. SAN Manager server, switch identification and port number group the report data.

Drill down from the summarized port data presents port totals summarized by day. Drilling down on the date will display the individual incidents by hour for that day.

The time period specified by the selection parameters provide the boundary for the summary of incident day count and the total down time. Within the summarized data the shortest and longest outage is for all the incidents included in the report selection. The percent availability is calculated for the time period specified above the column.

Percent Available is calculated on a full 24 hour day. The start date used is either the specific date set in the date range parameter or else the oldest date from the incident reporting data. The time period for the calculation is listed with the Percent Available column header.

3.1.1 Main Report


3.1.1.1 Drill Down Port Summary by Date

3.1.1.2 Drill Down Port Incident Detail by Hour for Day

3.1.2 Report Navigation

3.1.2.1 Parameters Display Text Enter the ITSANM server hostname Data Type Text Allow multiple values? Yes Server Name

Default Value(s) All servers Display Text Enter the switch name Data Type Text Allow multiple values? Yes

Switch Name

Default Value(s) All switches Display Text Enter the start time and end time Data Type Datetime Allow multiple values? Specify date range

Time Period

Default Value(s) Not applicable Display Text View ports with availability under Data Type Numeric Allow multiple values? No Availability Threshold

Default Value(s) Availability under 100%


3.2 Sample Report for SAN Manager LUN/Host Availability This report presents the LUN status for devices reporting problems. Hosts, if available for a LUN, are listed below the summarization. LUNs will not be listed in this report when they never reported a problem or have not reported a problem since the last prune date. Use the asset report for monitored LUNs to view all LUNs known to the Tivoli Storage Area Network Manager.

Incidents for the LUNs reporting anomalies are summarized and provide drill down to detail by hour. SAN Manager server and LUN identification group the report data.

Drill down from the summarized data identifies LUN totals by day. Drilling down on the LUN identifier will display the summary by date. Drill down on the date, will display the individual incidents by hour.

The time period specified by the selection parameters provide the boundary for the summary of incident day count and the total down time. Within the summarized data the shortest and longest outage is for all the incidents included in the report selection. The percent availability is calculated for the time period specified above the column.

Percent Available is calculated on a full 24 hour day. The start date used is either the specific date set in the date range parameter or else the oldest date from the incident reporting data. The time period for the calculation is listed with the Percent Available column header.


3.2.1 Main Report

IBM T

3.2.1.1 Drill Down LUN ID Summary by Date

ivoli Storage Area Network Manager Warehouse Pack Implementation Guide 23

3.2.1.2 Drill Down LUN ID Detail Summary by Date by Hour

3

Av

3

IBM T

.2.2 Report Navigation

Display Text Enter the ITSANM server hostname Data Type Text Allow multiple values? Yes Server Name

Default Value(s) All servers Display Text Enter the start time and end time Data Type Datetime Allow multiple values? Specify date range

Time Period

Default Value(s) Not applicable Display Text View LUNs with availability under Data Type Numeric Allow multiple values? No ailability Threshold

Default Value(s) Availability under 100%

.3 Sample Report for Monitored by More Than One SAN Manager This report presents a list of any switches, LUNs, or hosts that may be monitored by more than one Tivoli Storage Area Network Manger. When multiple SAN Managers are rolled up into the central data warehouse, the status of a device is reported in relation to the Tivoli SAN Manager monitoring it. This can result in ambiguous status; two different Tivoli SAN Managers will show different relationships to that device. This report summarizes devices that are reporting under more than one Tivoli SAN Manager.


3.3.1 Main Report Sample report when no device is monitored by more than one SAN Manager.

IBM T


Sample report with switches and hosts monitored by more than one SAN Manager.

3.3.2 Report Navigation None.


3.4 Sample Report for Switches Monitored by SAN Manager This report lists all the switches monitored by the Tivoli SAN Manager. Information related to each switch is listed by the user given switch name. Other information about the switch include switch worldwide name, vendor, model, revision, and total number of ports.

The switch worldwide name is preceded by the Tivoli SAN Manager two character identifier ‘E3’.

Data is organized by Tivoli SAN Manager server and alphabetically by the user-assigned switch name.

3.4.1 Main Report




Default Value(s) All servers Display Text Enter the switch name Data Type Text Allow multiple values? YRs Switch Name

Default Value(s) All switches


3.5 Sample Report for LUNs Monitored by SAN Manager This report lists all the LUNs monitored by the Tivoli SAN Manager. Information related to each logical unit, abbreviated as LUN in the report, includes LUNID, LUN type, vendor, model, product id and revision. This report provides basic volume information; the Tivoli Storage Resource Manager product provides detailed reports on current status.

Tivoli SAN Manager server followed by three groupings organizes data on the report:

• LUNs assigned to Hosts includes any LUN that has been associated with a managed host (agent). The entry will include a list of managed hosts historically associated to the LUN.

• Unassigned LUNs are not being used by a managed hosts operating system however, a database can be utilizing the LUN directly and bypassing the operating system. See Tivoli Storage Resource Manager reports on database volume utilization for more information.

• Unassigned Hosts are managed hosts that do not have a LUN configured using either the Windows Administrator device manager or the AIX cfgmgr tool.

3.5.1 Main Report




Default Value(s) All servers


4 Installing and Configuring the Warehouse Pack Use the Tivoli Data Warehouse installation wizard (provided with the product) to install the warehouse pack. See Installing and Configuring Tivoli Data Warehouse for specific installation steps.

Installation of this warehouse pack requires the following actions:

• Make sure all the prerequisite products are installed (see section 4.1).

• Read sections 2.2 through 4.6 to learn about important information that may impact your Tivoli Data Warehouse environment.

• When installing for the DB2, create an administrator login that is not the same as the administrator login used for the system running the database. Using the same login will cause problems with the Data Warehouse center access if the password changes on the system administrator login.

• Make sure you have the database connection and login information for the Tivoli SAN Manager repository. Do not use the login created by the Tivoli SAN Manager installation as your data warehouse login. It is recommended you create a login specifically for data warehouse access.

The data warehouse login defined to access the repository for Tivoli SAN Manager must be configured with the following general permissions:

Process: BTA_c05_Initialize_Process

Step: BTA_c05_s010_CREATE_ARCHIVE

Set default database to the Tivoli SAN Manager repository.

Make sure you have user permission to create tables, create indexes, create sequences and create triggers.

Process: BTA_c10_ ETL1_Process

Step: BTA_c10_s010_EXTRACT

Set default database to the Tivoli SAN Manager repository;

Make sure you have user permission to select from tables and delete records from tables.

Consult the documentation for the database platform regarding configuration.

• Use the Microsoft Control Panel to verify or configure the ODBC data source information about the Tivoli SAN Manager repository and Tivoli Data Warehouse databases. Check with the database vendor regarding ODBC installation and configuration.

• Use the installation wizard for Tivoli Data Warehouse to install the warehouse pack.

• Follow these post installation instructions as described further in section 4.6:

1. Verify the control database is set for the DB2 Data Warehouse Center if this is the initial warehouse installation.

2. Run the initialize step to create a set of triggers and archive tables in the Tivoli SAN Manager database if this is a new install. For an upgrade to the 1.2 warehouse pack, you can continue to use the existing archive tables and triggers created in the Tivoli SAN Manager repository.

3. Schedule the central data warehouse ETL processes to run. Instructions for setting up the scheduling feature are covered in the document, Installing and Configuring Tivoli Data Warehouse.

4. Adjust the prune parameters for the SAN Manager warehouse pack in the central data warehouse and data mart tables (section 4.2.3).


4.1 Prerequisite Hardware and Software Before installing the warehouse pack for IBM Tivoli SAN Manager, you must install all prerequisite software:

• IBM Tivoli SAN Manager, Version 1.3.1 • IBM DB2 Universal Database, Version 7.2 • Fix pack 8e, 9, 10, or 10a for IBM DB2 Universal Database, Version 7.2 • IBM DB2 Universal Database for z/OS and OS/390, Version 7 • Tivoli Data Warehouse, Version 1.2 • TDW 1.2 Fix Pack 02 • Crystal Enterprise and its prerequisites • Crystal Enterprise 9 SP2

This warehouse pack supports central data warehouses on DB2 UDB for z/OS and OS/390, DB2 UDB for Windows and UNIX systems. Also, this warehouse pack supports data marts on DB2 UDB for z/OS and OS/390, DB2 UDB for Windows and UNIX systems.

IBM Tivoli SAN Manager, Version 1.3.1, added a table to identify the host name of the SAN Manager. This table is required by the warehouse pack.

Note: When installing the SAN Manager release it is important that you use the fully qualified host name for the SAN Manager system.

Refer to the Tivoli Data Warehouse Release Notes and IBM Tivoli Storage Area Network Manager product documents (section 1.2.1) for specific information about hardware prerequisites, database and operating system support, and product prerequisites.

For late-breaking news about prerequisites, refer to the following IBM Software Support Web site:


4.2 Product Notes and Limitations

4.2.1 Tivoli SAN Manager Repository

The archive tables and triggers created in the SAN manger repository, as part of the warehouse pack installation retain a history of changes to a switch, port, LUN, or host availability during the period between data warehouse extracts. Records for resolved availability issues will be deleted from the archive tables on completion of the data warehouse extract step. Records with resolved availability have both a start and end time for the record.

If the archive tables have not been successfully created on the Tivoli SAN Manager repository using the BTA_s05_s010_Create_Archive step during installation, the warehouse pack ETL processes will fail.

4.2.2 Restarting Process Steps The Tivoli SAN Manager warehouse pack is designed to run with one or more data sources when adding data to the central data warehouse. Each step is designed to be restarted if a failure occurs.

If an ETL step fails while running the BTA_c010_ETL_Process or the BTA_m05_ETL2_Process, always restart the step that failed after the problem is resolved. Resuming at the pre-extract step will result in lost data.

Section 5 of this document identifies problem-solving scenarios.



4.2.3 Support for Multiple Tivoli SAN Manager Servers Tivoli SAN Manager Version 1.3 warehouse enablement pack version 1.2 is designed to work with Tivoli Data Warehouse Version 1.2 and allow scheduling of the source data extract from multiple Tivoli SAN Manager repositories in the enterprise.

The Tivoli Data Warehouse Version 1.2 document, Installing and Configuring Tivoli Data Warehouse, presents the procedure and the steps to follow in order to configure your environment.

To collect data from multiple servers you will need to define a unique ODBC connection to each separate Tivoli SAN Manager repository. Configure each source repository during the warehouse pack installation procedure.

Contact the IBM Tivoli Support Center for more information on setting this up in your environment. Some limitations may apply for your enterprise configuration.

4.2.4 Tivoli SAN Manager Repository The Tivoli SAN Manager repository is the data source for the warehouse pack ETL processing. One or more repositories for Tivoli SAN Manager servers can deposit data into the warehouse. The Tivoli Data Warehouse Version 1.2 provides the means to automatically schedule the extraction processing from multiple data sources for one application.

To maintain accurate warehouse data related to Tivoli SAN Manager, the warehouse processing requires that during warehouse pack installation several archive tables and triggers be created in each source database repository. When a record about switch, port or LUN availability status changes, a copy is inserted, updated, or deleted in a Tivoli SAN Manager repository. A copy of that record will be retained in the archive table until a data warehouse extract is run. In the data source extraction process, the ETL collects records from the archive tables about down time conditions so the central data warehouse measurements reflect availability since the last extract.

The archive tables and triggers require very little additional space for the Tivoli SAN Manger repository. Calculating the space is covered in section 4.3.1.

4.3 Database-Sizing Considerations

4.3.1 Tivoli SAN Manger Repository Ensure that you have sufficient space in the Tivoli SAN Manager for the historical records collected by the triggers in the archive tables. Archive tables include a record for Available status on each LUN, switch, and port, as well as historical records reflecting changes since the last extraction by the warehouse ETL. A switch changing state will generate one record for the switch and one record for each port. A port changing state will generate one record for each change to the port state.


To estimate how much space is required for the archive tables, complete the following worksheets.

Enter an approximate count of the devices on your SAN network.

For switches, multiply by the number of ports per switch.

Total column 4.

Approximate Count Devices Monitored by SAN Manager Number of Devices Port Factor

(column 2 x column 3)

Device Count

LUN -

Switch/Ports=8 8

Switch/Ports=16 16

Switch/Ports=256 256

Total Device Count - -

To compute the amount of history you expect your environment to generate on a daily basis, compute the percent of change activity you expect daily by using a percentage of the Total Device Count.

Enter the Total Device Count from the previous table.

Multiply the estimated percentage of change per day for all devices. Thirty percent is used for a default.

Add the Total Daily Changes to Total Device Count.

Based on average record size of (100 bytes) divide the number of records in Total Daily Usage by 10 for the Average Space Required in KB or by 10,485 for total in MB.

Total Device Count

Estimated percentage of

change


Total daily changes

(column 1 + column 3)

Total Daily Usage

Average Record

(column 4 /column 5)

Average Space Required

.30 10 for KB or

10,485 for MB

4.3.2 Central Data Warehouse Storage Ensure that you have sufficient space in the central data warehouse for the historical data collected by the warehouse pack. To estimate how much space is required for the warehouse pack, complete the following worksheets.


Central Data Warehouse Fixed Storage

Fill in the device count for your environment from the table in section 4.3.1.

Calculate Device Count x Warehouse Record Count = Total KB

Add the Total KB to get the Total central data warehouse estimated fixed storage requirement.

Tivoli SAN Manager Device Device Count Warehouse Record Size

(column 2 x

column 3)

Total KB

Switch/Ports=8 13 KB



LUN 1 KB

Host 1 KB

Fixed Storage Requirement -

Central Data Warehouse Variable Storage

Enter from section 4.3.1, the value computed for Total daily changes. Only records with not available status are extracted daily from the Tivoli SAN Manager archive tables.

Based on the size of a measurement record size (86 bytes), approximately 12 records use 1 KB of memory and 12,192 records use 1 MB of memory.

Records are retained in the central data warehouse based on the number of days to prune value. The default of 180 is used in this table. Multiply the daily variable storage requirement by the number of days to prune.

Total Daily Changes

Number of Msmts

records

(column 1 / column 2)

Daily Variable Storage

Requirement Number of days to

Prune


Variable Storage Requirement

12 for KB or

12,192 for MB

180

4.3.3 Data Mart Storage The data mart uses approximately two times the estimated central data warehouse fixed storage requirement plus space for the fact tables on an hourly, daily, weekly and monthly granularity.

Data Mart Fixed Storage

The data mart uses approximately two times the estimated central data warehouse fixed storage requirement.


Central Data Warehouse Fixed Storage Requirement

Multiply value by Fixed Storage Requirement

2

Data Mart Variable Storage

A hourly fact table entry is created for each device for each hour that it is down. Multiple entries for the same device within one hour will be accumulated as minutes not available for the hour. Sixty minutes or less equates to one hourly fact while a device not available for a day will create twenty-four hourly fact records. The multiple record factor represents how many hours you want to approximate for each record.

A daily fact table entry is created for each device for the accumulated time it is down during that day.

A weekly fact table entry is created for each device for the accumulated time it is down during that week.

A monthly fact table entry is created for each device for the accumulated time it is down during that month.

The number of records retained in each fact table for a device is determined by the data mart prune control defined.

Enter from section 4.3.1, the value computed for Total daily changes. Only records with not available status are extracted daily from the Tivoli SAN Manager archive tables and result in a measurement in the central data warehouse.

The multiple record factor only changes for the hourly fact table. Enter the approximate number you think most devices will be down (1 to 24 hours).

The purge days is from the MART_PURGE table and represents the default values set at installation.

Fact Table

Total Daily Changes

Multiple Record Factor

(Column 2 x

Column 3)

Device Daily

Changes

Purge Days

(Column 4 x

Column 5)

Estimated Records

Hourly 2 90

Daily 1 180

Weekly 1 365

Monthly 1 365

Total Estimated Records


Total Estimated Records

Number of

Records for Space

(column 1 / column 2)


12 for KB or

12,192 for MB

4.3.4 Summarize Total Space Required Move totals from central data warehouse and data mart sections.

Database Fixed Storage Requirement


Estimated Total Storage (Fixed + Variable)

Central data warehouse

Data mart database

Control database 1

4.4 Pre-installation Procedures Before installing the IBM Tivoli SAN Manager warehouse pack, Version 1.2, install IBM Tivoli SAN Manager, Version 1.3.1. Follow the instructions for installation of the IBM Tivoli SAN Manager product and its database platform.

If you have previously installed IBM Tivoli SAN Manager, Version 1.2 and are doing an upgrade to the IBM Tivoli SAN Manager, Version 1.3.1, the data currently in the storage area network manager database repository will not be affected by the software upgrade.

If you are also using the IBM Tivoli SAN Manager Warehouse Pack, Version 1.1, the archive tables and triggers created in the SAN Manager repository will not be removed nor the data in those tables affected by upgrading to IBM Tivoli SAN Manager, Version 1.3.1. When you upgrade to the IBM Tivoli SAN Manager Warehouse Pack, Version 1.2 a set of new tables and triggers will be added to support LUN and host information.

Contact your database administrator to secure the connection information about the ITSANMDB database created in the installation of IBM Tivoli SAN Manager application and the login information that Tivoli Data Warehouse requires.

Note: All Tivoli SAN Manager server repositories are assumed to use the same name for the database – ITSANMDB.

Your database administrator can provide connection and login information for the repository created during the Tivoli SAN Manager installation.

• You will need the database name or schema name for the Tivoli SAN Manager repository. This is required for the ODBC configuration.

• You need to have your database administrator identify the database login information you will use to access the data source. During warehouse pack installation you will set up the warehouse source names to use based on the ODBC configurations defined in the pre-installation.

• Your database administrator needs to provide source database login access for data warehouse processing with permission to do the following during the installation for the BTA_c05_s010_Create_Archive step:


Create table Create index Create trigger Create sequence

• For daily central data warehouse ETL operation, the Tivoli SAN Manager login permissions require:

Select Delete

Configure the ODBC connection for your source repositories. You must have the client for your Tivoli SAN Manager DB2 platform installed on the system where you install the warehouse pack.

• Set up the ODBC connection using the ODBC Data Source Administrator found for Windows under Administrative Tools of the Control Panel.

• Consult the Installing and Configuring Tivoli Data Warehouse documentation for the list of ODBC drivers to use for your source database vendor platform.

• Each source database ODBC connection must be configured under the System DSN Tab of the ODBC Data Source Administrator.

4.5 Installation of the Warehouse Pack Record the user IDs, passwords, and ITSANM server name in the following table before installing the warehouse pack.


You need this information to follow the installation procedures that are described in Installing and Configuring Tivoli Data Warehouse.

Name to use in warehouse install for data source

User ID Password Database type Server name or alias

BTA__Source

The default data source name for the ODBC connection is ITSANM

Source database login

Source database password

Tivoli SAN Manger v1.3.1 supports a DB2 UDB on Windows or AIX

Alias is the name of the system data source defined in the ODBC Source Administrator

IMPORTANT: When defining the data source names in the TDW install always use upper case for the name of the data source.

Example: ITSANM_SRC1 not ITSANM_Src1

Install the warehouse pack as described in Installing and Configuring Tivoli Data Warehouse, using the installation properties file (twh_install_props.cfg file). The location of the twh_install_props.cfg file is on the IBM Tivoli Storage Area Network Manager, Warehouse Pack Version 1.2 CD , in the directory :\TDW_WEPS\bta.

4.6 Post-installation Procedures Use the DB2 Data Warehouse Center interface to access the data warehouse extract, transform and load processes and steps under the BTA_IBM_Tivoli_SAN_Manager_v1.2_Subject_Area subject area.

Before you can run the ETL processes you must create the archive tables and triggers for the Tivoli SAN Manger repository.

Initialization process BTA_c05_Initialize_Process Process dependencies Run the BTA_c05_s010_Create_Archive step before you use the central

data warehouse ETL process. The create archive process is designed to run once against each defined data source for your warehouse pack. This step only needs to be run once as part of the warehouse pack install unless a new data source is configured or a data source is restored from a backup that was made prior to the warehouse pack installation. Rerunning this process against a data source with existing records in the archive tables will result in lost status. Verify the creation of the archive tables on each SAN Manager database by checking for the existence of the following four tables: BTA.T_ARC_DEVSTATE BTA.T_ARC_BIGDEVSTATE BTA.T_ARC_STATE BTA.TEMP_EXTCTL

After you complete the warehouse pack install and the create archive step successfully completes, you must determine how you want to schedule the ETL steps. See the information about scheduling warehouse packs in Installing and Configuring Tivoli Data Warehouse. Schedule the SAN Manager warehouse pack ETL steps using these processes:


ETL process BTA_c10_ETL1_Process

Process dependency Initialization Process must have successfully run for each data source as part of the installation procedure before the steps in central data warehouse ETL can be started. If you will use a shortcut to link the central data warehouse ETL and data mart ETL processes, link to the BTA_c20_m10_Mart_Pre_Extract step in the BTA_c20_ETL2_Process. ETL process BTA_c20_ETL2_Process Process dependency All BTA_c10_ETL1_Process steps must have successfully run. Set ETL1 step BTA_c10_s050_Load_Msmt to start on successful completion step BTA_c20_s010_Mart_Pre_Extract.

4.7 Migration from a Previous Release of the Warehouse Pack The following database objects are changed since the previous release of the warehouse pack. The procedure to upgrade to version 1.2 of the warehouse pack first requires upgrading your current Tivoli Data Warehouse, Version 1.1, installation to IBM Tivoli Data Warehouse, Version 1.2. Follow the procedure in the Installing and Configuring Tivoli Data Warehouse document. This process will migrate existing data in the central data warehouse to the new table formats. You can then uninstall the warehouse pack version 1.1 and install the new warehouse pack; this does not remove the existing data in the central data warehouse.

Added objects:

• New central data warehouse tables; see on page 61. • New data mart tables; see on page 85. • New data mart ETL steps; see on page 60. • Pruning information remains the same; see on page 49. • Reports; see on page 12.

Changed objects:

• The central data warehouse component attribute STORAGE_GUID is replaced by the common attribute name SYSTEM_GUID. The format of the value has changed from dotted-hex to an 8-4-4-4-12 character display (i.e. ea7c76d0-01db-11d7-a42d-00062999bda2). During the warehouse pack installation, this change will be migrated for existing Tivoli SAN Manager attributes in the central data warehouse. If you did not have the warehouse pack version 1.1 previously installed, the attribute name will now be SYSTEM_GUID.

Removed objects:

• Not applicable

4.8 Uninstall of the Warehouse Pack Perform the following steps to uninstall the warehouse pack:

1. Only remove the archive tables and triggers from a SAN Manager data source if you will not be continuing with the extraction of data to the data warehouse. Removing the archive tables and triggers does not remove any information in the central data warehouse. To remove the archive tables and triggers from the SAN Manager data source, run the following command using the SQL editor of your choice.


DROP TRIGGER BTA.PHYICELT_TRIG1;



DROP TRIGGER BTA.PHYPORT_TRIG1;



DROP TRIGGER BTA.DEVSTATE_TRIG1;



DROP TRIGGER BTA.BIGDEVSTATE_TRIG1;



DROP TABLE BTA.temp_extctl;

DROP TABLE BTA.t_arc_STATE;;

DROP TABLE BTA.t_arc_DEVSTATE;

DROP TABLE BTA.t_arc_BIGDEVSTATE;

2. Uninstall the warehouse pack as described in Installing and Configuring Tivoli Data Warehouse.

When the warehouse pack is uninstalled, the BTA staging tables are removed, but the data in the central data warehouse remains and is still useable by other applications.

If you are upgrading a Tivoli SAN Manager warehouse pack version 1.1 to the version 1.2 level, you will need to install the Tivoli Data Warehouse version 1.2. As part of the data warehouse version 1.2 upgrade, any currently installed warehouse pack will be migrated to the version 1.2 environment. Allowing the migration to complete for a currently installed warehouse pack insures that existing central data warehouse data gets moved to new tables for processing. After this data warehouse upgrade is complete you will need to uninstall the Tivoli SAN Manager warehouse pack version 1.1 and then install the latest version which provides the data marts and reports.

4.9 Multiple Data Centers After you install the warehouse pack, you can configure T

tivoli data warehouse implementation...

Documents