Database Schema Reference

(1)

IBM

Tivoli

Configuration

Manager

Database

Schema

Reference

Version

4.2.1

(2)

(3)

IBM

Tivoli

Configuration

Manager

Database

Schema

Reference

Version

4.2.1

(4)

Note

Beforeusingthisinformationandtheproductitsupports,readtheinformationin“Notices”onpage159.

SecondEdition(December2003)

Thiseditionappliestoversion4,release2,modificationlevel1ofIBMTivoliConfigurationManager(program number5724-C06)andtoallsubsequentreleasesandmodificationsuntilotherwiseindicatedinneweditions. ThiseditionreplacesSC23-4783-00.

(5)

About

this

guide

.

. vii

Whoshouldreadthisguide. . . vii

Whatthisguidecontains. . . vii

Publications . . . vii

IBMTivoliConfigurationManagerlibrary. . . viii

Prerequisitepublications. . . viii

Relatedpublications . . . ix

Accessingpublicationsonline . . . ix

Orderingpublications . . . ix

Contactingsoftwaresupport . . . x

Conventionsusedinthisguide . . . x

Typefaceconventions . . . x

Operatingsystem-dependentvariablesandpaths xi

Chapter

1. Introduction

.

. 1

Chapter

2. History

tracking

.

. 3

Usinghistorytablesforthefirsttime . . . 3

Modifyinghistorytrackingforefficiency. . . 4

Customhistorytables . . . 6

Deletinghistorytables . . . 6

Chapter

3. Configuration

repository

views

.

. 9

ActivityPlannerviews . . . 9

V_ACT_ST . . . 9 V_ACT_STATUS . . . 9 V_ACT_STATUS_EX . . . 10 V_PLAN_STATUS . . . 11 V_PLAN_STATUS_EX. . . 13 V_STATUS_FILTER. . . 14 V_STATUS_TGT. . . 16 V_TGT_ACT_DEP_ST. . . 17 V_TGT_ACT_GW_ST . . . 17 V_TGT_ACT_ST. . . 17 V_TGT_GW_FLTR . . . 18 Inventoryviews. . . 19 ASP_VIEW . . . 19 CDROM_VIEW . . . 20 CHECK_PACKAGES . . . 20 COMPUTER_MEM_VIEW . . . 21 COMPUTER_VIEW. . . 21 FLPY_DRV_VIEW . . . 24 HDISK_VIEW . . . 24 HEADER_INFO_VIEW . . . 25 INST_FILE_VIEW . . . 25 INST_SWARE_VIEW . . . 26 INVENTORYDATA. . . 27 IP_ADDR_VIEW . . . 28 IPX_ADDR_VIEW . . . 30 KEYBOARD_VIEW. . . 30 MATCH_SWARE_VIEW . . . 31 MEM_MODULES_TOTAL . . . 31 MEM_MODULES_VIEW. . . 32 MOUSE_VIEW . . . 34 NATIV_SWARE_VIEW . . . 34 NET_CARD_VIEW. . . 35 NOSIG_FILES_VIEW . . . 35 NW_SERVER_VIEW . . . 36 NW_VOLS_VIEW . . . 38 OS_VIEW . . . 38 PACKAGE_FILE_VIEW . . . 39 PARTITION_VIEW. . . 40 PC_BIOS_VIEW. . . 40 PC_PROCESSOR_VIEW . . . 41 PCI_DEV_VIEW. . . 43 PRINTER_VIEW. . . 44 PROCESSOR_NUM_VIEW . . . 45 PROCESSOR_VIEW . . . 45 PTF_INFO_VIEW . . . 45 SIG_PACKAGE_VIEW. . . 46 SMBIOS_DATA_VIEW. . . 47 SOLARIS_CPU_VIEW. . . 48 STORAGE_DEV_VIEW . . . 49 SWARE_MATCH_CRC32. . . 50 SWARE_MATCH_MD5 . . . 50 SWARE_MATCH_QUICK . . . 51 TAPEDRV_VIEW . . . 52 UNIX_SYS_VIEW . . . 52 USB_DEV_VIEW . . . 53 VID_CARD_VIEW . . . 54

Historicalinventoryviews . . . 55

Pervasivedeviceviews . . . 57

BATTERY_VIEW . . . 57 DB_INFO_VIEW. . . 57 DEV_CARD_VIEW. . . 58 DEV_CMSTATUS_VIEW . . . 59 DEV_INFO_VIEW . . . 60 DEV_STATUS_VIEW . . . 61 PALM_AGENT_VIEW. . . 61 PALM_CFG_VIEW. . . 62 PALM_NET_VIEW. . . 63 PERVASIVE_VIEW. . . 64 WINCE_AGENT_VIEW . . . 64 WINCE_CFG_VIEW . . . 65 WINCE_FILE_VIEW . . . 66 WINCE_NATIV_VIEW . . . 67 WINCE_NET_VIEW . . . 67

Historicalpervasivedeviceviews . . . 68

SoftwareDistributionviews. . . 69

SD_CMSTATUS_VIEW . . . 69 SD_LOADED_VIEW . . . 69 SD_WEBUI_VIEW . . . 70 SP_SIG_VIEW . . . 70 SWDISTDATA_VIEW . . . 71 WEBUI_SUB_VIEW . . . 71

Chapter

4. Queries

.

. 73

Inventoryqueries . . . 73 || || || || || || || || || || || || | | | |

(6)

ASP_QUERY. . . 73 CDROM_QUERY . . . 73 CHECK_PACKAGES_QUERY . . . 74 COMPUTER_MEM_QUERY. . . 74 COMPUTER_QUERY . . . 75 FLPY_DRV_QUERY . . . 76 HDISK_QUERY. . . 76 HEADER_INFO_QUERY. . . 77 INST_FILE_QUERY. . . 77 INVENTORY_HWARE . . . 78 INVENTORY_SWARE. . . 78 IP_ADDR_QUERY . . . 79 IPX_ADDR_QUERY . . . 80 KEYBOARD_QUERY . . . 80 MATCH_CRC32_QUERY. . . 80 MATCH_MD5_QUERY . . . 81 MATCH_QUICK_QUERY . . . 82 MEM_MODULES_QUERY . . . 82 MEM_MODULES_TOTAL . . . 83 MODEM_QUERY . . . 83 MOUSE_QUERY . . . 84 NATIV_SWARE_QUERY . . . 84 NET_CARD_QUERY . . . 84 NOSIG_FILES_QUERY . . . 85 NW_SERVER_QUERY. . . 85 NW_VOLS_QUERY . . . 86 OS_QUERY . . . 87 PACKAGE_FILE_QUERY. . . 87 PARTITION_QUERY . . . 88 PC_BIOS_QUERY . . . 88 PC_PROCESSOR_QUERY . . . 89 PCI_DEV_QUERY . . . 90 PRINTER_QUERY . . . 91 PROCESSOR_NUM_QUERY. . . 91 PROCESSOR_QUERY. . . 91 PTF_INFO_QUERY. . . 92 SIG_PACKAGE_QUERY . . . 93 SMBIOS_DATA_QUERY . . . 93 SOLARIS_CPU_QUERY . . . 94 STORAGE_DEV_QUERY. . . 95 TAPEDRV_QUERY. . . 95 UNIX_SYS_QUERY. . . 96 USB_DEV_QUERY . . . 96 VID_CARD_QUERY . . . 97

Historicalinventoryqueries. . . 97

Pervasivedevicequeries . . . 99

BATTERY_QUERY . . . 99 DB_INFO_QUERY . . . 99 DEV_CARD_QUERY. . . 100 DEV_CMSTATUS_QUERY . . . 100 DEV_INFO_QUERY . . . 101 DEV_STATUS_QUERY . . . 101 PALM_AGENT_QUERY. . . 101 PALM_CFG_QUERY. . . 102 PALM_NET_QUERY. . . 102 PERVASIVE_QUERY. . . 103 WINCE_AGENT_QUERY . . . 103 WINCE_CFG_QUERY . . . 104 WINCE_FILE_QUERY . . . 104 WINCE_NATIV_QUERY . . . 105 WINCE_NET_QUERY . . . 105

Historicalpervasivedevicequeries . . . 106

SoftwareDistributionqueries . . . 106

CM_STATUS_QUERY . . . 106 SD_LOADED_COMPONENT_QUERY . . . . 107 SIG_SP_MAP_QUERY . . . 107 SWDISTDATA_QUERY . . . 107 SWDIST_WEBUI_QUERY . . . 108 Subscriptionqueries . . . 108

Historicalsubscriptionqueries. . . 110

Chapter

5. Configuration

repository

tables

.

. 111

ActivityPlannertables . . . 111

ACT_LAYOUT . . . 111 ACT_PARAMETER . . . 111 ACT_PLAN_STATUS. . . 112 ACT_STATUS_TGT . . . 112 ACT_TARGET_SPEC. . . 113 ACTIVITY . . . 113 ACTIVITY_PLAN. . . 113 ACTIVITY_STATUS . . . 115 ACTIVITY_TARGET . . . 115 APPL_ERRLEV. . . 115 APPL_OPERATION . . . 116 EXECUTION_WINDOW . . . 116 PLAN_LOCKS . . . 116 PLAN_TARGET . . . 116 PLAN_TARGET_SPEC . . . 117 PLUGIN_FILE_INFO. . . 117 USER_PARAMETER . . . 117 VARIABLE . . . 118

ChangeManagertables . . . 118

CCM_COMP . . . 118 CCM_PLUGIN. . . 118 CCM_PLUGIN_FILES . . . 119 CCM_REPORT. . . 119 CCM_SYNCH . . . 120 CCM_WEBUI_PACKAGES. . . 120 COMP_ATTRIBUTES. . . 120 DEPENDENCY. . . 121 ELEMENT . . . 121 REFERENCE_MODEL . . . 121 SUBSCRIBER . . . 122 Inventorytables . . . 122 COMPUTER. . . 122 COMPUTER_SYS_MEM. . . 123 FILE_DESC . . . 123 FILE_FILTER . . . 124 FILE_PATH . . . 124 HDISK . . . 124 HEADER_INFO . . . 125 INST_HEADER_INFO . . . 125 INST_MODEM. . . 125 INST_MOUSE . . . 126 INST_NATIV_SWARE . . . 126 INST_PARTITION. . . 126 INST_PRINTER . . . 127 INST_PROCESSOR . . . 127 INST_SMBIOS_DATA . . . 128 INST_USB_DEV . . . 128 INST_VID_CARD. . . 129 || || | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |

(7)

IP_ADDR . . . 129 IPX_ADDR . . . 130 MATCHED_SWARE . . . 130 MEM_MODULES. . . 130 MODEM. . . 131 MOUSE . . . 131 NATIV_SWARE . . . 131 NET_ADAPTER . . . 132 NW_SERVER . . . 132 NW_VOLS . . . 133 PC_SYS_PARAMS. . . 134 PCI_DEV. . . 134 PRINTER. . . 135 PRISTINE_H_INSTALL . . . 135 PROCESSOR . . . 135 PTF_INFO . . . 137 SIG_PACKAGE. . . 138 SMBIOS_SYS_DATA . . . 139 STORAGE_DEV . . . 139 SWARE_SIG. . . 140 UNIX_SYS_PARAMS. . . 140 UNMATCHED_FILES . . . 141 USB_DEV . . . 141 USER_TABLE . . . 142 VID_CARD . . . 142

HistorytablesforInventory . . . 143

Pervasivedevicetables . . . 144

BATTERY . . . 144 DB_INFO. . . 144 DEV_CARD. . . 145 DEV_INFO . . . 145 INST_DB_INFO . . . 145 INST_DEV_CARD. . . 146 PALM_CFG. . . 146 WINCE_CFG . . . 147

Historytablesforpervasivedevices. . . 148

PristineManagertables . . . 149

IMAGE . . . 149 PLUGIN . . . 149 PLUGIN_CREATE_KEYS . . . 150 PLUGIN_ENVIRONMENT. . . 150 PRISTINE_ACTIVITY . . . 150 MACHINE . . . 151 MACHINE_ENV . . . 151 OSELEMENT . . . 151 OSELEMENT_IMAGE . . . 151 PRISTINE_ROLE . . . 152 ROLE_SUBSCRIBER . . . 152 SERVER . . . 152 SERVER_ENVIRONMENT. . . 152 SUPPORTED_OS . . . 153 TMR_NAME . . . 153

SoftwareDistributiontables . . . 153

MOD_SUBSCRIPTS . . . 153 SD_H_INST. . . 154 SD_INST. . . 154 SD_LOADED . . . 155 SD_PACKAGES . . . 155 SD_WEBUI_PACKAGES. . . 156 SIG_SP_MAP . . . 156 SWARE_SUBSCRIPTS . . . 157

TivoliResourceManagertables . . . 157

TRM_TYPES. . . 157 TRM_RESOURCES . . . 157 TRM_GROUPS. . . 158 TRM_DISTRIBUTIONS . . . 158

Notices

.

. 159

Trademarks . . . 161

Index

.

. 163

|| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |

(8)

(9)

About

this

guide

TheIBM TivoliConfigurationManager:DatabaseSchemaReferenceprovides informationabouttheconfigurationrepositorycomponentoftheIBM® Tivoli® ConfigurationManagerproduct. Thisguideincludesdescriptionsoftheviews, queries, andtablesusedintheconfigurationrepository,aswell asanexplanation of historytracking.

Who

should

read

this

guide

Thisguideisforsystemadministratorsand otherusersoftheIBMTivoli ConfigurationManagerproductwhoperform inventorygatheringandreporting operations aboutsystemsina distributedenterprise.

Readers shouldbe familiarwiththefollowing:

v _PC,_UNIX®_,_and_AS/400®_systems_and_pervasive _devices

v _Basic_inventory_control_and_system_{configuration}_management_concepts v _Database_and _SQL_concepts

v _Graphical_user_interfaces

What

this

guide

contains

Thisguidecontainsthefollowingsections: v _Chapter_1,_{“Introduction,”}_on_page₁

Thischapterprovidesanoverview oftheconfigurationrepositoryandthetasks thatyoucanperformonthisdatabase.

v _Chapter_2,_“History_tracking,”_on_page₃

Thischapterprovidesinformationaboutthehistorytrackingfeature,whichcan storedataandchangeinformationfromallpreviousinventoryandpervasive devicescans.

v _Chapter_3,_{“Configuration}_repository_views,”_on_page₉

Thischapterdescribesthepre-defined viewsprovidedwith IBMTivoli ConfigurationManager,includingadescriptionofeachcolumnname,and showstheoperatingsystemsforwhichthecolumnsarepopulated.

v _Chapter_4,_{“Queries,”} _on_page₇₃

Thischapterliststhepre-definedqueries providedwithIBM Tivoli ConfigurationManager andthecolumnsincludedineachquery. v _Chapter_5,_{“Configuration}_repository_tables,”_on_page₁₁₁

ThischapterdescribestheoperationaldatatablespopulatedbyInventoryand SoftwareDistributionintheconfigurationrepositoryandliststhecolumns includedineachtable.

Publications

Thissectionlists publicationsintheIBMTivoliConfigurationManagerlibraryand anyotherrelateddocuments.Italsodescribeshow toaccessTivolipublications online andhow toorderTivolipublications.

(10)

IBM

Tivoli

Configuration

Manager

library

The followingdocuments areavailableintheIBMTivoliConfigurationManager

library:

v _Release_Notes,_GI11-0926

ContainsthelatestinformationaboutthisreleaseofIBM TivoliConfiguration Manager,includinginstallationand upgradenotes;softwarelimitations, problems,andworkarounds;documentationnotes;andinternationalization notes.

v _Planning_and _{Installation,}_GC23-4702

ExplainshowtoplanorupgradeyourdeploymentofIBM TivoliConfiguration ManagerinaTivolienvironment aswell ashowtoinstall,upgrade,and uninstallthecomponentsofIBMTivoliConfigurationManagerusingthe availableinstallationmechanisms.

v _Introducing_IBM_Tivoli_{Configuration}_Manager,_GC23-4703

ExplainstheconceptsofIBM TivoliConfigurationManagerand itscomponents andprovidesa roadmaptotheIBMTivoliConfigurationManager

documentation.

v _User’s_Guide_for_Software_{Distribution,}_SC23-4711

Explainstheconceptsandproceduresnecessarytoeffectively distributesoftware overnetworksusingtheSoftwareDistributioncomponentofIBMTivoli

ConfigurationManager.

v _Reference_Manual_for_Software_{Distribution,}_SC23-4712

Providesin-depthinformationabouttheIBM TivoliConfigurationManager commandsusedbytheSoftwareDistributioncomponentandexplainsadvanced features,concepts,and proceduresnecessarytoeffectivelyusetheSoftware Distributioncomponent.

v _User’s_Guide_for_Inventory,_SC23-4713

Explainstheconceptsandproceduresnecessarytoeffectively usetheInventory componentofIBM TivoliConfigurationManager andprovidesin-depth

informationaboutthecommandsusedbytheInventorycomponent. v _Messages_and_Codes, _SC23-4706

ProvidesdetailsofthemessagesgeneratedbytheIBM TivoliConfiguration Managercomponents.

v _Inventory_Online_Help

ProvidesrelatedinformationaboutusingtheInventorygraphical userinterface (GUI).

Prerequisite

publications

The followingdocuments provideinformationthatyouneedtoset upyourTivoli environment andinstallIBM TivoliConfigurationManager:

v _Tivoli_Management_Framework:_Planning_for_Deployment_Guide, _GC32-0803 Explainshowtoplanfordeployingyour Tivolienvironment.Italsodescribes TivoliManagementFrameworkanditsservices.

v _Tivoli_Management_Framework:_Tivoli_Enterprise_Installation_Guide, _GC32-0804 Explainshowtoinstall andupgradeTivoliEnterprise™softwarewithinyour TivoliregionusingtheavailableinstallationmechanismsprovidebyTivoli SoftwareInstallationServiceandTivoliManagementFramework.Tivoli

(11)

managednodes,gateways, endpoints,andRDBMSinterfacemodule(RIM) objects.Thisguidealsoprovides informationabouttroubleshootinginstallation problems.

v _Tivoli_Management_Framework:_Release_Notes,_GI11-0890

Describesthelatestinstallationinformation,includingsupportedplatforms, defects,andlimitationsforTivoliManagementFramework.

publications

TheTivoliManagementFramework:ReferenceManual,SC32-0806, providesin-depth informationaboutTivoliManagement Frameworkcommands.Thismanualis helpfulwhenwritingscripts thatare laterrunasTivolitasks.Thismanualalso documents defaultandvalidationpolicyscripts usedbyTivoliManagement Framework.

TheTivoliSoftwareGlossary includesdefinitionsformanyofthetechnicalterms relatedtoTivolisoftware.TheTivoliSoftwareGlossaryisavailable,inEnglishonly,at thefollowingWebsite:

http://www.ibm.com/software/tivoli/library/

AccesstheglossarybyclickingtheGlossarylinkontheleft paneoftheTivoli software librarywindow.

Accessing

publications

online

ThedocumentationCDcontainsthepublicationsthatareintheproductlibrary. TheformatofthepublicationsisPDF, HTML,orboth.Refertothereadmefileon theCDforinstructions onhow toaccessthedocumentation.

TheproductCDcontainsthepublicationsthatareintheproductlibrary.The formatofthepublicationsisPDF, HTML,orboth.Toaccessthepublicationsusing a Webbrowser,opentheinfocenter.htmlfile.Thefileisintheappropriate

publicationsdirectoryontheproductCD.

IBM postspublicationsforthisand allotherTivoliproducts,astheybecome available andwhenevertheyareupdated,totheTivolisoftwareinformationcenter Website.AccesstheTivolisoftwareinformationcenterbyfirst goingtotheTivoli software libraryat thefollowingWebaddress:

http://www.ibm.com/software/tivoli/library/

Scrolldownandclick theProduct manualslink.IntheTivoliTechnicalProduct DocumentsAlphabeticalListingwindow,clicktheIBMTivoliConfiguration Manager linktoaccesstheproductlibraryattheTivolisoftwareinformation center.

Note: IfyouprintPDFdocumentsonotherthanletter-sizedpaper,settheoption intheFile” PrintwindowthatallowsAdobeReadertoprintletter-sized pagesonyourlocalpaper.

Ordering

publications

YoucanordermanyTivolipublicationsonline atthefollowingWebsite: http://www.elink.ibmlink.ibm.com/public/

(12)

Youcanalsoorderbytelephonebycallingoneofthese numbers: v _In_the_United_States:_800-879-2755

v _In_Canada:_800-426-4968

Inothercountries,seethefollowingWebsitefora listof telephonenumbers: http://www.ibm.com/software/tivoli/order-lit/

Contacting

software

support

IfyouhaveaproblemwithanyTivoliproduct,refertothefollowingIBMSoftware SupportWebsite:

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

Ifyouwanttocontactsoftwaresupport,seetheIBMSoftwareSupportGuideat the followingWebsite:

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

The guideprovidesinformationabouthowtocontactIBM SoftwareSupport, dependingontheseverityof yourproblem,and thefollowinginformation: v _Registration_and _eligibility

v _Telephone_numbers,_depending_on_the_country_in_which_you_are_located v _Information_you_must_have_before_contacting_IBM _Software_Support

Conventions

used

in

this

guide

Thisguideusesseveralconventionsforspecialtermsandactionsandoperating system-dependent commandsandpaths.

Typeface

conventions

Thisguideusesthefollowingtypefaceconventions: Bold

v _Lowercase_commands_and_mixed_case_commands_that_are_otherwise difficulttodistinguishfromsurroundingtext

v _Interface_controls_(check _boxes,_push_buttons,_radio_buttons,_spin buttons,fields,folders,icons,listboxes, itemsinsidelistboxes,

multicolumnlists,containers, menuchoices,menu names,tabs,property sheets),labels(suchasTip:,andOperatingsystem considerations:) v _Keywords_and_parameters_in_text

Italic

v _Words_defined_in_text

v _Emphasis_of_words_(words_as_words)

v _New_terms_in_text_(except_in_a _definition_list) v _Variables_and _values_you_must_provide Monospace

v _Examples_and_code_examples

v _File_names,_programming _keywords,_and_other_elements_that_are_difficult todistinguishfromsurroundingtext

(13)

v _Message_text_and_prompts _addressed_to_the_user v _Text_that_the_user_must _type

v _Values_for_arguments_or_command_options

Operating

system-dependent

variables

and

paths

ThisguideusestheUNIXconventionforspecifyingenvironmentvariablesandfor directory notation.

WhenusingtheWindows®commandline,replace $variablewith%variable%for environment variablesand replaceeachforwardslash(/) withabackslash(\)in directory paths.Thenamesofenvironmentvariablesarenotalwaysthesamein Windows andUNIX.Forexample,%TEMP%inWindowsisequivalentto$tmpin UNIX.

Note: Ifyouare usingthebashshellonaWindows system,youcanusetheUNIX conventions.

(14)

(15)

Chapter

1. Introduction

IBM TivoliConfigurationManager,Version4.2.1,usesarelationaldatabase

management system(RDBMS)serverwiththeInventoryand SoftwareDistribution componentstostore data.Theconfigurationrepositoryisadatabasein theRDBMS thatcontains theschema(tablesand columns)inwhichinformationisstoredina consistent structure.

Youcanviewor runqueriesonthedataintheconfigurationrepository.For example,youcanquerytheconfigurationrepositoryforallsystemsthathavean outdatedversionof asoftwareproductthatwillneedupgrading inthenext year. Thisbooklistsand describeseachviewand tableincludedintheconfiguration repositoryschema. Thisbookalso listsanddescribesthequeries thatyoucan install whenyouinstall IBMTivoliConfigurationManager,Version4.2.1. Inaddition,thisbookdescribes historytrackingandlists thehistorical views, queries, andtables.

Note: Informationprovidedinthisbookregardingthetable andviewdefinitions oftheconfigurationrepositorycanalso beextractedfromthesystem catalogsofyourRDBMS. Formoreinformation,consultyourRDBMS manualsoryourdatabaseadministrator.

For agraphical representationofthetablesintheconfigurationrepository,seethe

Database Schemaposterenclosedwiththisdocumentation, orcontactyour Tivoli customer supportrepresentativefora copy.Youcanalso createyourowntables and views.

For moreinformationonusingtheconfigurationrepository,seethefollowing sectionsintheUser’sGuideforInventory:

v _To_add_tables_to_the_{configuration}_repository,_see_the_chapter_on_collecting custominformation.

v _To_create_queries,_see_the_chapter_on_querying_inventory_information. v _To_delete_information_from_the_{configuration}_repository,_see_the_commands

(16)

(17)

Chapter

2. History

tracking

IBM TivoliConfigurationManager providesanoptionalhistorytrackingfeatureto store inventorydataand changeinformationfromallpreviousinventoryand pervasive devicescans.Datafromthecurrentscanisstoredinoperationaldata tables. Operationaldatatablesare overwrittenorupdatedduringeachscan, dependingonwhethertheUpdatewithDifferences orReplacewithCurrent Results optionisselectedfortheinventoryprofile.Operationaldatatablesreflect onlythemostcurrentscan.However, ifyouenable historytracking, new,

modified, anddeleteddatafromtheoperationaldatatablesarestored inhistory tablesastheoperationaldatatablesisoverwritten.

Youcanaccesshistoricaldatabyusinghistoryviews,queries,and tables.History views,queries,andtablesaredesignatedwithanuppercase Hand anunderscore character(H_)atthebeginningoftheirnames.FollowingtheH_,thenameofa historyview,query,ortablegenerallyhasthesamenameastheoperationalview, query,ortable withwhichitisassociated.

EachoperationaldatatablethatcontainsthecolumnCOMPUTER_SYS_IDhasa corresponding historytable.Ahistorytablehasallofthecolumnnamesfromthe corresponding operationaldatatable plusthefollowingadditionalcolumns: RECORD_ACTION

TheRECORD_ACTION columntellswhethertherecordisanINSERT (new informationisbeingaddedtotheoperationaldatatable),an

UPDATE(part ofarecord intheoperationaldatatableisbeingmodified), ora DELETE(therecordnolongerexistsintheoperationaldatatable). PRFL_ACTION

PRFL_ACTIONstateswhethertheprofileconfigurationoptionisReplace with CurrentResults(REPLACE)or UpdateWithDifferences

(REPLACE_WITH_DIFF).Also,whilethecolumnRECORD_TIMEin

operationaldatatablescontains thetimethattherecordwasinsertedinto thedatabase,RECORD_TIMEinhistorytablescontains thetimethatthe

endpointwas scanned(theCOMPUTER_SCANTIMEcolumnfromthe

COMPUTERtable).

Toenable historytracking, youmust createhistorytablesintheconfiguration repository.See thePlanningandInstallationformoreinformationaboutcreating these tables.

Note: Dataisneverdeletedfromthehistorytables.Even ifyouremovea system fromtheTivolimanagementregion(Tivoliregion) usingthewinvrmnode command,therecordof thesystem’sexistenceremainsinthehistorytables unlessyoueither manuallydeletethehistorytablesoraddthetablesnames totheINVENTORY_TABLEStableand usethewinvrmnodecommand.See “Deletinghistorytables”onpage6 andthecommandsappendixinthe

User’sGuideforInventoryformoreinformation.

Using

history

tables

for

the

first

time

Whenyouenable historytrackingforthefirsttime, aseriesofhistorytablesis installedintheconfigurationrepository.Afterthehistorytablesareinstalled,you

(18)

Ifyouinstallthehistoricalschemaatthesametimeastheoperationaldata schema, usetheUpdatewith Differencesprofileoptionforallscans. Ifyouinstall thehistoricalschemaaftertheoperationaldataschema,usetheReplacewith CurrentResults profileoptionforthefirst scan,thenuseUpdatewithDifferences for allsuccessivescans.Thisensuresthatonlythechangedataissenttothe historytables.IfyouuseReplacewith CurrentResultsforeachscan,thesize of thehistorytableswillgrowbythesizeofthefullscanforeachscan,anditwillbe more difficulttoquerytheactualchangestotheTivoliregion.

The followingscenarioillustratesthedifferencebetweenthetwooptions.Inthis scenario,theoperationaldatatable MATCHED_SWAREisusedtostoredataabout 100 installedsoftwareapplicationsthatarefoundusingsignaturematching atan endpoint.On theinitialscan,theMATCHED_SWAREtablereturns100entriesfor thescannedsystem,sotheH_MATCHED_SWAREtablealsohas100entries. Before thenext scan,fivesoftwareapplicationsareaddedtoandfiveare deleted fromthesystem.IfyouusetheUpdatewith Differencesoptiononthenext scan, H_MATCHED_SWARE onlyadds10entries, fiveasINSERTentriesforthefive new softwareapplicationsandfiveasDELETEentriesforthefiveapplicationsthat were removed.TheH_MATCH_SWAREtablenow has110totalentries,andthe additional entriesshowwhichsoftwareapplicationswereaddedandwhichwere deleted.

However, ifyouusetheReplacewithCurrentResultsoption,the

H_MATCHED_SWARE tableadds100entries. Combinedwith theoriginal100 entries, theReplacewith CurrentResultsoptionleavesyouwith 200totalentries after thesecondscan,allofwhicharestored asINSERTentries. Thisoption adds 90more entriesthantheUpdatewithDifferences optiondoes,andnoneofthe new entriesexplicitlyshowthatsomesoftwareapplicationsweredeleted.

Modifying

history

tracking

for

efficiency

Without customization,historytrackingcanconsumean enormousamount of database spaceand resources.Thefollowingrecommendations describeswaysto customize historytrackingtousehistorytrackingwhileminimizingthedatabase spaceandresources used:

v _Delete_any_history_tables_for_which_you_do_not_want_to_gather_data.

Bydefault,theh_<database>_schema.sqlscripts createatabletocorrespondto everyinventorytablein theinv_<database>_schema.sql scriptthatcontainsthe attributeCOMPUTER_SYS_ID.Iftherearetablesforwhichyouwillnever want tokeephistorytables,youcanremovethecorrespondingCREATETABLEfrom theh_<db>_schema.sqlscript.Iftheh_<db>_schema.sqlscripthasalreadybeen run,dropthetablesatthedatabaseusingtheDROPTABLE<tablename> statement.

Forexample,youmaynotwanttocollecthistoricalinformationfromthe

H_UNMATCHED_FILEStable.Informationfromabasicfilescanisstoredinthe UNMATCHED_FILEStable,and whenhistorytrackingison,thedataisthen storedintheH_UNMATCHED_FILEStable.Basicfileinformationisthelargest setofdatathatinventorycollects.Dependingonwhichincludedirectoriesand filetypesareselectedintheprofile, basicfileinformationcanbe 95percentor moreofthetotalscan dataforanendpoint.

Inaddition,theACCESSED_TIMEandMODIFIED_TIMEattributescanchange frequently,whichwillcausean updaterecord tobesenttothe

(19)

H_UNMATCHED_FILEStableeverytimea fileisaccessedormodified.Deleting theH_UNMATCHED_FILEStablecansignificantlyreducetheamount ofdata storedinhistorytables.

Pervasivedevicetablesare alsolikelytochangeveryfrequently.Depending upontherequirementsofyourenvironment,youshouldconsiderwhetherto collecthistoricalinformationforpervasivedevices.

v _Use_the_same_software_profile_{configuration}_for_each_scan_of _an_endpoint. Itisrecommended thatyouusetheupdatewithdifferencesoption forprofiles whenhistorytrackingisenabledbecausesoftwareand hardwarescanswork differently.Withhardwarescans,theupdatewithdifferencesoptionrecognizes whenhardwarehasbeendeselectedfromtheprofileconfiguration.For example, ifahardwarecomponentisfound inonescanandthenextscanrunswith that componentdeselectedfromtheprofile, Inventoryrecognizesthatthecomponent hasnotbeendeleted.

Withsoftwarescanning,however,ifadirectory isscannedduring onescanand thendeselectedduring thenext scan,allsoftwareinformationreturnedinthe firstscanshowsupasdeletedinthesecondscan.Topreventtheseerroneous deletesfrombeingsenttothehistorytables,youshouldscanendpointswith profileshavingincludeandexclude directoriesand thesame filetypesselected. Ifyouneedtoscan thesameendpoints fordifferentsoftwareconfigurations overmultiple scans,youcanremovethecorrespondinghistorytablesas describedearlierinthissection.

v _Add_unique_constraints _to_history_tables_to_limit_which_change_data_is_saved. Historytablesarecreatedwithoutprimary keysorconstraints.Beforedatais senttothehistorytables,theconstraints alreadyhavebeenmet inthe

operationaldatatables. Inventoryonlysendsinserts, neverupdatesordeletes,to thehistorytables.Thelackofconstraints providesquickerdatainsertion.Any changeforanycolumnina historytablecausesarecord tobewritten.Ifyou wanta historyrecord tobewritten onlyifcertain columnschange,youcanadd auniqueconstraint.

Forexample,theH_COMPUTER_SYS_MEMtablehastheCOMPUTER_SYS_ID,

PHYSICAL_TOTAL_KB,PHYSICAL_FREE_KB,TOTAL_PAGES,FREE_PAGES,

PAGE_SIZE,VIRT_FREE_KB,RECORD_ACTION,PRFL_ACTION,

RECORD_TIMEcolumns.PHYSICAL_FREE_KB,FREE_PAGES,

VIRT_TOTAL_KB,VIRT_FREE_KB,andRECORD_TIME willprobablychange

everyscan.Toinsert changedataforallthecolumnsexceptthesefive,youcan adda constrainttotheH_COMPUTER_SYS_MEMtable.Allattributesina uniqueconstraintmust benon-null,whichmeansthetableneedstobe

recreated.Ifthetablealreadyhasdatainit thatshouldbe preserved,youneed tocopythedatato atemporarytablefirst,and thenbacktotherecreated H_COMPUTER_SYS_MEMtable.Thefollowingexampleshowhowtodo thisin DB2®:

-- This view selects only the oldest records with the unique attributes we want to save.

create view H_TMP_MEM_VIEW as

select * from

H_COMPUTER_SYS_MEM H where

H.RECORD_TIME = (select MIN(RECORD_TIME) from H_COMPUTER_SYS_MEM

where COMPUTER_SYS_ID = H.COMPUTER_SYS_ID and PHYSICAL_TOTAL_KB = H.PHYSICAL_TOTAL_KB and TOTAL_PAGES = H.TOTAL_PAGES

(20)

and PRFL_ACTION = H.PRFL_ACTION);

-- This temporary table is to store the rows we want to save from the H_COMPUTER_SYS_MEM table.

CREATE TABLE H_TMP_SYS_MEM (

COMPUTER_SYS_ID VARCHAR(64), PHYSICAL_TOTAL_KB INTEGER, PHYSICAL_FREE_KB INTEGER, TOTAL_PAGES INTEGER, FREE_PAGES INTEGER, PAGE_SIZE INTEGER, VIRT_TOTAL_KB INTEGER, VIRT_FREE_KB INTEGER, RECORD_ACTION CHAR(6), PRFL_ACTION VARCHAR(20), RECORD_TIME TIMESTAMP);

-- Copy the rows from H_TMP_MEM_VIEW (the desired subset of H_COMPUTER_SYS_MEM).

INSERT INTO H_TMP_SYS_MEM

select * from H_TMP_MEM_VIEW;

-- Drop and recreate the H_COMPUTER_SYS_MEM table, with the new constraints added.

DROP TABLE H_COMPUTER_SYS_MEM; CREATE TABLE H_COMPUTER_SYS_MEM (

COMPUTER_SYS_ID VARCHAR(64) NOT NULL,

PHYSICAL_TOTAL_KB INTEGER NOT NULL default 0, PHYSICAL_FREE_KB INTEGER,

TOTAL_PAGES INTEGER NOT NULL default 0, FREE_PAGES INTEGER,

PAGE_SIZE INTEGER NOT NULL default 0, VIRT_TOTAL_KB INTEGER,

VIRT_FREE_KB INTEGER, RECORD_ACTION CHAR(6),

PRFL_ACTION VARCHAR(20) NOT NULL, RECORD_TIME TIMESTAMP,

constraint HCOMPUTERSYSMEM_UK unique

(COMPUTER_SYS_ID, PHYSICAL_TOTAL_KB, TOTAL_PAGES, PAGE_SIZE, PRFL_ACTION));

-- Copy the rows from the temporary table to the new H_COMPUTER_SYS_MEM table.

INSERT INTO H_COMPUTER_SYS_MEM select * from H_TMP_SYS_MEM; -- Remove the temporary table and view.

DROP TABLE H_TMP_SYS_MEM; DROP VIEW H_TMP_MEM_VIEW;

Custom

history

tables

Inventory automaticallypopulates customhistorytableswhenthetablesare properlyaddedtotheconfigurationrepository.Seethechapteroncollecting custom informationintheUser’sGuideforInventoryforinformationaboutcreating custom historytables.

Deleting

history

tables

Youcanmanuallydeletehistorytablesbyusingthefollowingmethod,oryoucan usethewinvrmnodecommand.For moreinformationondeletinghistorytables usingwinvrmnode,seethecommandsappendixintheUser’sGuideforInventory.

(21)

Youcanmanuallydeletehistorytableseitherbytimeorbyspecific computerID. Thefollowingexamples showhow todeletehistorytablesforDB2.

Todeletehistorytablesfora specificsystem,enterthefollowingcommand: delete from H_TABLE_NAME where COMPUTER_SYS_ID = ’SYSTEM_ID’;

where:

H_TABLE_NAME

Specifiesthenameof thehistorytable.

SYSTEM_ID

SpecifiesthecomputersystemID.

All historytableswiththenamespecifiedbyH_TABLE_NAMEforthesystemwith this computersystemIDwillbe deletedwhenthiscommandisrun.Todeleteother historytablesforthesystem withthiscomputersystem ID,youmust runthis commandforeachtablenameyouwanttodelete.

Todeletehistorytablesbefore aspecific time,enterthefollowingcommand: delete from H_TABLE_NAME where RECORD_TIME < ’YYYY-MM-DD HH:MM:SS’

where:

H_TABLE_NAME

Specifiesthenameof thehistorytable.

YYYY-MM-DD HH:MM:SS

Specifiesthedateandtimebefore whichyouwanttodeletehistorytables. ThisformatisforDB2;otherplatformsmayrequire differentformats. All historytableswiththenamespecifiedbyH_TABLE_NAMEandcreatedbefore this datewillbedeletedwhenthis commandisrun.

(22)

(23)

Chapter

3. Configuration

repository

views

Thefollowingsectionsdescribethepre-definedviewsprovidedwithIBM Tivoli ConfigurationManager.Theseviewswere createdwhenIBMTivoliConfiguration Manager wasinstalled.Eachsection describesthecolumnsineachview andshows theplatformsonwhichthedataiscollected.

Note: IBMTivoliConfigurationManagerusesthesamenamingconventionsforall databases.Alltableandcolumn namesare18charactersorlessinlength.

Activity

Planner

views

Thefollowingsectionsdescribethepre-definedviewsprovidedwithActivity Planner.Theseviewswerecreatedduring installation.

V_ACT_ST

Displaysinformationaboutactivityplanstatusontargetsystems. Based ontheACTIVITY_STATUStable.

Thecolumns inthisview areasfollows:

ColumnName Description

PLAN_ID ThenumericplanIDgeneratedbythesystem.

REC_NUMBER Therecursionnumberoftheactivityplan.

STATUS Thecurrentstatusoftheactivityplan.

V_ACT_STATUS

Displaysinformationaboutactivityplanstatusontargetsystems. Based ontheACTIVITYandACTIVITY_STATUStables.

NAME Thenameoftheactivity.

CONDITION Alogicalexpressionthatdefineshowthe executionofanactivityisconditionedbythe outcomeoftheexecutionofoneormore conditioningactivities.SeetheIBMTivoli ConfigurationManager:ReferenceManualfor SoftwareDistributionfordetailedinformation.

PRIORITY PrioritygivenbytheActivityPlannerengineto theexecutionoftheactivity.

TIME_ENQUEUED Thetimewhentheactivitywasqueuedtothe ActivityPlannerenginetobeexecuted. | | | | | | | ||| || || || | | | | | ||| || || | | | | | || || | || |

(24)

APPL_SPEC_ACT_ID Identifiersuppliedbytheapplicationthatis trackingtheoperation.Thedistribution_id returnedbyMDIST2.

START_TIME Thetimewhenthesystemstartedtheactivity. COMPLETION_TIME Thetimewhenthesystemcompletedthe

activity.

ACTIVITY_ID ThenumericactivityIDgeneratedbythe system.

REC_NUMBER Therecursionnumberoftheactivityplan.The recursionnumberisapositiveintegerthatis incrementedautomaticallyateachplan recursion.

APPLICATION_TYPE Identifieroftheapplicationthatperformsthe activity.

OPERATION_TYPE Applicationspecificidentifieroftheoperation performedwiththisactivity.Validvaluesare providedbytheapplicationplug-ins. DESCRIPTION Thedescriptionoftheactivity.

SPEC_COMP Thespecificcomputertowhichtheactivityplan isapplied.

PREV_STATUS Thepreviousstatusoftheactivityplan.

V_ACT_STATUS_EX

Displaysinformationaboutactivityplanstatusontargetsystems. Based ontheACT_STATUS_TGTtable.

The columnsinthisview areasfollows:

NAME Thenameoftheactivity.

CONDITION Alogicalexpressionthatdefineshowthe executionofanactivityisconditionedbythe outcomeoftheexecutionofoneormore conditioningactivities.SeetheIBMTivoli ConfigurationManager:ReferenceManualfor SoftwareDistributionfordetailedinformation.

PRIORITY PrioritygivenbytheActivityPlannerengineto theexecutionoftheactivity.

TIME_ENQUEUED Thetimewhentheactivitywasqueuedtothe ActivityPlannerenginetobeexecuted. APPL_SPEC_ACT_ID Identifiersuppliedbytheapplicationthatis

trackingtheoperation.Thedistribution_id returnedbyMDIST2.

START_TIME Thetimewhenthesystemstartedtheactivity. COMPLETION_TIME Thetimewhenthesystemcompletedthe

activity. || || | | || || | || || | || | | | || | || | | || || | || | | | | | ||| || || | | | | | || || | || | || | | || || |

(25)

REC_NUMBER Therecursionnumberoftheactivityplan.The recursionnumberisapositiveintegerthatis incrementedautomaticallyateachplan recursion.

APPLICATION_TYPE Identifieroftheapplicationthatperformsthe activity.

OPERATION_TYPE Applicationspecificidentifieroftheoperation performedwiththisactivity.Validvaluesare providedbytheapplicationplug-ins. DESCRIPTION Thedescriptionoftheactivity.

PREV_STATUS Thepreviousstatusoftheactivityplan.

V_PLAN_STATUS

Displaysinformationaboutactivityplanstatusontargetsystems.

Based ontheACT_PLAN_STATUSandACTIVITY_PLAN tables.

START_TIME Thetimewhenthesystemstartedtheactivity onthetarget.

COMPLETION_TIME Thetimewhenthesystemcompletedthe activityplanonthetarget.

IS_TEMPLATE Thetypeofplan(draft,template,orsubmitted). PRIORITY Controlstheorderinwhichactivitiesarerun

withinagivenexecutionwindow.

NAME Usedtoidentifyactivityplanssavedasdrafts

ortemplatesintheactivityplandatabase. STOP_ON_ERROR Theerrorlevelabovewhichtheplanexecution

willbestopped.

IS_CANC_CUTOFF Whethertheoutstandingactivitiesmustbe canceled.

DESCRIPTION Descriptionoftheactivityplan.

SPEC_COMP Thespecificcomputertowhichtheactivityplan isapplied.

REC_STOP_ON_ERROR Theerrorlevelabovewhichthenthiterationof arecursiveplanwillbestopped.

REC_STOP_OVERLAP Whetherthenthiterationofarecursiveplanis stoppedifitsexecutionoverlapswiththenext iteration.

REC_TYPE Thetypeofrecursionmechanism.

|| || || | || | | | || | || | | || || | | | | | ||| || | || | || || || | || | || | || | || || | || | || | | ||

(26)

DAYS_OF_WEEK Executestheactivityplanonspecificdaysofthe week,representedbyanumberfrom1to7 separatedbyacommaorhyphen.1represents Sunday.Forexample,forarecursionon MondaysandFridaysthiscolumnwouldhave thevalue2,6.

DAYS_OF_MONTH Executestheactivityplanonspecificdaysofthe month,representedbyanumberfrom1

through31separatedbyacommaorhyphen. Forexample,forarecursiononthe1stand16th ofeachmonth,thiscolumnwouldhavethe value1,16.

REC_BY_DATE_INT Specifiesthedateintervalatwhichtheplan recursionmechanismisactivated.Theformatis

yyyymmdd.Forexample,forarecursionevery 10days,thiscolumnwouldhavethevalue 00000010.

REC_BY_TIME_INT Specifiesthetimeintervalatwhichtheplan recursionmechanismisactivated.Theformatis hh:mm:ss.Forexample,forarecursionevery fourandahalfhours,thiscolumnwouldhave thevalue04:30:00.

IS_DYN_RESOLV Indicateswhethertargetsshouldberesolvedat executiontime.

MAIL_ADDRESS Usere-mailaddresstonotifywhenanoperation isperformedontheplan,suchas,whenthe planissubmitted,whentheplanhas

completed,orwhenapause,resume,cancel,or restartoperationisperformedontheplan. IS_POST_NOTICE Whetheranoticemustbepostedtonotifyplan

submissionandcompletion.

REC_NUM Therecursionnumberoftheactivityplan.

NOT_BEFORE_TIME Earliestdateandtimeatwhichtheplancanbe executed.

NOT_AFTER_TIME Latestdateandtimeatwhichtheplancanbe executed.

PREV_STATUS Previousstatusoftheactivityplan.

IS_PAUSED Whethertheplanistobesettothepausedstate whensubmitted.

REC_EXPIRE_TIME Thedateandtimeatwhichtherecursion mechanismwillexpire.

ON_TERMINATION IDoftheactivitythatmustbeexecutedasthe lastactivity,regardlessoftheresultoftheother activities.

CREDENTIALS Usercredentialstobeusedatplanexecution. RELATIVE_NOT_AFTER Therelativetimethenotificationwillnotexpire

after.

RELATIVE_EXP_TIME Therelativetimethenotificationexpires. NOTIFY_DATE Thedateandtimeofthenotification. || || | | | | | || | | | | | || | | | | || | | | | || | || | | | | || | || || || | || | || || | || | || | | || || | || ||

(27)

REL_NOTIFY_DATE Therelativedateandtimeofthenotification.

V_PLAN_STATUS_EX

Displaysinformationaboutactivityplanstatusontargetsystems.

Based ontheACT_PLAN_STATUSandACTIVITY_PLAN tables.

REC_NUMBER Therecursionnumberoftheactivityplan. START_TIME Thetimewhenthesystemstartedtheactivity

onthetarget.

COMPLETION_TIME Thetimewhenthesystemcompletedthe activityplanonthetarget.

IS_TEMPLATE Thetypeofplan(draft,template,orsubmitted). PRIORITY Controlstheorderinwhichactivitiesarerun

withinagivenexecutionwindow.

NAME Usedtoidentifyactivityplanssavedasdrafts

ortemplatesintheactivityplandatabase. STOP_ON_ERROR Theerrorlevelabovewhichtheplanexecution

willbestopped.

IS_CANC_CUTOFF Whethertheoutstandingactivitiesmustbe canceled.

DESCRIPTION Descriptionoftheactivityplan.

REC_STOP_ON_ERROR Theerrorlevelabovewhichthenthiterationof arecursiveplanwillbestopped.

REC_STOP_OVERLAP Whetherthenthiterationofarecursiveplanis stoppedifitsexecutionoverlapswiththenext iteration.

REC_TYPE Thetypeofrecursionmechanism.

DAYS_OF_WEEK Executestheactivityplanonspecificdaysofthe week,representedbyanumberfrom1to7 separatedbyacommaorhyphen.1represents Sunday.Forexample,forarecursionon MondaysandFridaysthiscolumnwouldhave thevalue2,6.

DAYS_OF_MONTH Executestheactivityplanonspecificdaysofthe month,representedbyanumberfrom1

through31separatedbyacommaorhyphen. Forexample,forarecursiononthe1stand16th ofeachmonth,thiscolumnwouldhavethe value1,16. || || | | | | | ||| || || || | || | || || || | || | || | || | || || | || | | || || | | | | | || | | | | |

(28)

REC_BY_DATE_INT Specifiesthedateintervalatwhichtheplan recursionmechanismisactivated.Theformatis

yyyymmdd.Forexample,forarecursionevery 10days,thiscolumnwouldhavethevalue 00000010.

REC_BY_TIME_INT Specifiesthetimeintervalatwhichtheplan recursionmechanismisactivated.Theformatis hh:mm:ss.Forexample,forarecursionevery fourandahalfhours,thiscolumnwouldhave thevalue04:30:00.

IS_DYN_RESOLV Indicateswhethertargetsshouldberesolvedat executiontime.

MAIL_ADDRESS Usere-mailaddresstonotifywhenanoperation isperformedontheplan,suchas,whenthe planissubmitted,whentheplanhas

completed,orwhenapause,resume,cancel,or restartoperationisperformedontheplan. IS_POST_NOTICE Whetheranoticemustbepostedtonotifyplan

submissionandcompletion.

NOT_BEFORE_TIME Earliestdateandtimeatwhichtheplancanbe executed.

NOT_AFTER_TIME Latestdateandtimeatwhichtheplancanbe executed.

PREV_STATUS Previousstatusoftheactivityplan.

IS_PAUSED Whethertheplanistobesettothepausedstate whensubmitted.

REC_EXPIRE_TIME Thedateandtimeatwhichtherecursion mechanismwillexpire.

ON_TERMINATION IDoftheactivitythatmustbeexecutedasthe lastactivity,regardlessoftheresultoftheother activities.

V_STATUS_FILTER

Displaysstatusinformationfora filter.

Based ontheV_PLAN_STATUS_EXandV_ACT_STATUS_EXviews.

PLAN_NAME Thenameoftheplan.

ACTIVITY_NAME Thenameoftheactivity.

|| || | | | | || | | | | || | || | | | | || | || | || | || || | || | || | | | | | | | ||| || || | || ||

(29)

PLAN_STATUS Thecurrentstatusoftheactivityplan.The possiblevaluesareasfollows:

0 WAITING 1 STARTED 2 CANCEL_PENDING 3 CANCELED 4 CANCELED_BY_CONDITION 5 PAUSED 6 SUCCESS 7 FAILED 9 NO_UPD 10 IGNORE 11 HOLD_BY_CONDITION 12 PAUSE_PENDING 13 RESUME_PENDING

ACTIVITY_STATUS Thecurrentstatusoftheactivityonthetarget. Thepossiblevaluesareasfollows:

PLAN_START_TIME Thetimewhenthesystemstartedtheactivity onthetarget.

PLAN_COMPL_TIME Thetimewhenthesystemcompletedthe activityplanonthetarget.

ACT_START_TIME Thetimewhenthesystemstartedtheactivity. ACT_COMPL_TIME Thetimewhenthesystemcompletedthe

activity.

PLAN_REC_NUM Therecursionnumberoftheactivityplan.The recursionnumberisapositiveintegerthatis incrementedautomaticallyateachplan recursion. || || | || || || || || || || || || || || || || || | || || || || || || || || || || || || || || | || | || || | || | | |

(30)

ACT_REC_NUM Therecursionnumberoftheactivitythatis tracked.Therecursionnumberisapositive integerthatisincrementedautomaticallyateach planrecursion.

PLAN_PREV_STATUS Previousstatusoftheactivityplan.

ACTIVITIES Theactivitiesintheplan.

TARGETS Thetargetsintheplan.

GATEWAYS Thegatewaysintheplan.

DEPOTS Thedepotsintheplan.

V_STATUS_TGT

Displaysstatusinformationfora targetthatisaddressedbyanactivitythat belongs toasubmitted plan.

Based ontheACTIVITY,ACTIVITY_PLAN,andACT_STATUS_TGTtables.

TARGET_NAME Thenameofthetargetaddressedbytheactivity plan.

ACTIVITY_NAME Thenameoftheactivity.

PLAN_NAME Usedtoidentifyactivityplanssavedasdrafts ortemplatesintheactivityplandatabase. STATUS Thecurrentstatusoftheactivityonthetarget.

Thepossiblevaluesareasfollows:

REC_NUM Therecursionnumberoftheactivitythatis tracked.Therecursionnumberisapositive integerthatisincrementedautomaticallyateach planrecursion.

START_TIME Thetimewhenthesystemstartedtheactivity onthetarget. || || | | | || || || || || | | | | | | ||| || | || || | || | || || || || || || || || || || || || || || | | | || |

(31)

COMPLETION_TIME Thetimewhenthesystemcompletedthe activityonthetarget.

DEPOT_LABEL Thelabelofthedepotfromwhichthetarget receivesthedistributions.

V_TGT_ACT_DEP_ST

Based ontheACT_STATUS_TGTtable. Thecolumns inthisview areasfollows:

REC_NUMBER Therecursionnumberoftheactivitythatis tracked.Therecursionnumberisapositive integerthatisincrementedautomaticallyateach planrecursion.

STATUS Thecurrentstatusoftheactivityonthetarget.

V_TGT_ACT_GW_ST

Based ontheACT_STATUS_TGTtable. Thecolumns inthisview areasfollows:

GATEWAY_LABEL Thelabelofthegatewaytowhichthetargetis attached.

V_TGT_ACT_ST

Based ontheACT_STATUS_TGTtable. || || | || | | | | | | | ||| || || | || | | | || | | | | | | ||| || || || | || | | | || | | | | | |

(32)

V_TGT_GW_FLTR

Based ontheACT_STATUS_TGTtable. The columnsinthisview areasfollows:

TARGET_NAME Thenameofthetargetaddressedbytheactivity plan.

STATUS Thecurrentstatusoftheactivityonthetarget. Thepossiblevaluesareasfollows:

GATEWAY_LABEL Thelabelofthegatewaytowhichthetargetis attached. | ||| || || | || | | | || | | | | | | ||| || | || | || || || || || || || || || || || || || || || | || | | | || |

(33)

Inventory

views

Thefollowingsection describesthepre-definedviewsprovidedwithInventory. Theseviewswerecreatedduring installation.

Acheck mark(U)indicatesthecolumnmightbepopulated whenaview isrunon thatplatform.

Note: Acheckmarkdoesnotindicatethata columnwillbe populatedeverytime, onlythatit ispossiblefordatatobe collectedonthatplatform.Acolumn maystillremainunpopulatedinsomecircumstances.

Ifnocheck markisprovided,thecolumnnevercontains dataforthatplatform. Exceptions areindicatedwithothersymbolsandexplainedineachtable as necessary.

ASP_VIEW

Displayssystemauxiliarystorage poolinformationfortarget OS/400®_systems.

Based onPARTITION_VIEW.

AIX ® HP-UX Linux (S/390 ® ) Linux (PC) NetW are OS/2 ® OS/400 Solaris W indows 98 W indows NT ® /2000

TME_OBJECT_LABEL Theobjectlabelforthesystem. U

ASP_NAME Thenameoftheauxiliary storagepool.

U

NUM_ASP_DISKS Thenumberofdisksusedinthe auxiliarystoragepool.

U

ASP_SIZE_TOTAL_KB Thetotalsizeoftheauxiliary storagepool,inkilobytes(KB).

U

ASP_FREE_TOTAL_KB Theamountoffreespace availableintheauxiliarystorage pool,inKB.

U |

(34)

CDROM_VIEW

DisplaysinformationaboutCD-ROMdrivesontarget systems.

Based ontheCOMPUTERandSTORAGE_DEVtables.

AIX HP-UX Linux (S/390) Linux (PC) NetW are OS/2 OS/400 Solaris W indows 98 W indows NT/2000

TME_OBJECT_LABEL Theobjectlabelforthesystem. U U U U U U

TME_OBJECT_ID TheobjectIDforthesystem. U U U U U U

COMPUTER_SYS_ID ThecomputersystemID. U U U U U U

MANUFACTURER Themanufacturerofthe installedCD-ROMdrive.

U U U U U

MODEL Themodeloftheinstalled

CD-ROMdrive.

U U U U U U

STORAGE_TYPE ThetypeofCD-ROMdrive installed.

U U U U U U

SER_NUM Theserialnumberofthe

installedCD-ROMdrive.

U U W

RECORD_TIME Thetimethatthedatawas updatedatthedatabase.

U U U U U U

W

ReportedonlyonsystemswiththeWindowsManagementInterface(WMI).

CHECK_PACKAGES

Displaysinformationaboutsignaturepackageswithsignaturesthatare notvalid.

Based ontheSIG_PACKAGEandSWARE_SIGtables.

Note: Thisviewisnotoperating-system-specific. The columnsinthisview areasfollows:

SIG_PACKAGE_ID ThesignaturepackageID.

SWARE_SIG_ID ThesignatureID.

SWARE_DESC Thedescriptionofthesignaturepackage.

SWARE_VERS Theversionofthesignaturepackage.

| | || | | | | | | || | | |||||||||||| |||||||||||| |||||||||||| || | |||||||||| || | |||||||||| || | |||||||||| || | |||||||||| || | |||||||||| | | |

(35)

COMPUTER_MEM_VIEW

Displaysinformationaboutinstalledmemoryontargetsystems.

Based ontheCOMPUTERandCOMPUTER_SYS_MEMtables.

TME_OBJECT_LABEL Theobjectlabelforthesystem. U U U U U U U U U

TME_OBJECT_ID TheobjectIDforthesystem. U U U U U U U U U

COMPUTER_SYS_ID ThecomputersystemID. U U U U U U U U U

PHYSICAL_TOTAL_KB Thetotalamountofinstalled memoryinKB.

U U U U U U U U U

PHYSICAL_FREE_KB Theamountoffreememoryon thesysteminKB.

U U U U U U

TOTAL_PAGES Thenumberofmemorypages availableonthesystem.

U U U U U U U U

FREE_PAGES Thenumberoffreememory pagesonthesystem.

U U U U U

PAGE_SIZE Thesizeofthepageinbytes. U U U U U U U

VIRT_TOTAL_KB Thetotalamountofvirtual memoryonthesysteminKB.

U U U U U U U U

VIRT_FREE_KB Theamountoffreevirtual memoryinthesysteminKB.

U U U U U U U

U U U U U U U U U

COMPUTER_VIEW

Displayscommonsystem informationabouttarget systems. Based ontheCOMPUTERtable.

TME_OBJECT_LABEL Theobjectlabelforthesystem. U U U U U U U U U U

TME_OBJECT_ID TheobjectIDforthesystem. U U U U U U U U U U

COMPUTER_SYS_ID ThecomputersystemID. U U U U U U U U U U

| | |

(36)

ColumnName Description AIX HP-UX Linux (S/390) Linux (PC) NetW are OS/2 OS/400 Solaris W indows 98 W indows NT/2000

COMPUTER_SCANTIME Thetimeofthelastinventory scaninGreenwichMeanTime (GMT).

U U U U U U U U

COMPUTER_MODEL Themodelofthesystem. U U U U U U U

COMPUTER_BOOT_TIME Thetimethesystemwasstarted. U U U U U

COMPUTER_ALIAS Thehostnameofthesystem. U U U U U U U

SYS_SER_NUM Theserialnumberofthesystem. U U U U U U U

OS_NAME Thespecificoperatingsystem (suchasWindows2000 AdvancedServerorWindows 2000Professional)thatis runningatthetimeofthescan.

U U U U U U U U U

OS_TYPE Thetypeofoperatingsystem (suchasOS/2orWindows2000) thatisrunningatthetimeofthe scan.

U U U U U U U U U

OS_MAJOR_VERS Themajorversionnumberofthe operatingsystem.

U U U U U U U U U

OS_MINOR_VERS Theminorversionnumberof theoperatingsystem.

U U U U U U U U U

OS_SUB_VERS Thesubversionnumberofthe operatingsystem.

U U U U U

OS_INST_DATE Thedateonwhichtheoperating systemwasinstalled.

U U

REGISTERED_OWNER Theregisteredownerforthe system.

U U U

REGISTERED_ORG Theregisteredorganizationfor thesystem.

U U U

KEYBOARD_TYPE Thetypeofkeyboardattachedto thesystem.

U U U U

FUNCTION_KEYS Thenumberoffunctionkeyson thekeyboard.

U U

TZ_LOCALE Thelocationofthetimezonein whichthesystemislocated.

U U U U U U U

TZ_NAME Thenameofthetimezonein whichthesystemislocated.

U U U U U U *

TZ_DAYLIGHT_NAME Thenameofthedaylight savingstimezoneinwhichthe systemislocated.

U U U U U U U

ON_SAVINGS_TIME Whetherthesystemison daylightsavingstime.

U U U U U U U

TZ_SECONDS ThesecondsfromGMT. U U U U U U U

| | | | | | |

(37)

TIME_DIRECTION WhetherTZ_SECONDSisbefore orafterGMT.

U U U U U U U

U U U U U U U U U U

*OnsystemswithWMI,thisvalueisthesameasTZ_LOCALE. |

(38)

FLPY_DRV_VIEW

Displaysinformationaboutfloppydiskdrivesontarget systems.

Based ontheCOMPUTERandSTORAGE_DEVtables.

TME_OBJECT_LABEL Theobjectlabelforthesystem. U U U U U

TME_OBJECT_ID TheobjectIDforthesystem. U U U U U

COMPUTER_SYS_ID ThecomputersystemID. U U U U U

MANUFACTURER Themanufacturerofthe installedfloppydrive.

W

MODEL Themodeloftheinstalled

floppydrive.

U W

STORAGE_TYPE Thetypeoffloppydrive installed.

U U U U U

W_Reported_only_on_systems_with_WMI.

HDISK_VIEW

Displaysinformationaboutharddrivesinstalledintarget systems.

Based ontheCOMPUTERHDISK,and STORAGE_DEVtables.

TME_OBJECT_LABEL Theobjectlabelforthesystem. U U U U U U U U

TME_OBJECT_ID TheobjectIDforthesystem. U U U U U U U U

COMPUTER_SYS_ID ThecomputersystemID. U U U U U U U U

MANUFACTURER Themanufacturerofthe installedharddrive.

U U W

MODEL Themodeloftheinstalledhard drive.

U U U U S U

STORAGE_TYPE Thetypeofharddriveinstalled. U U U U U U U

| | | | | |

(39)

SER_NUM Theserialnumberofthe

installedharddrive.

U U U S W

HDISK_CYLINDERS Thenumberofcylindersinthe harddrive.

U U U U U

HDISK_SECTORS Thenumberofsectorsinthe harddrive.

U U U U U

HDISK_HEADS Thenumberofdiskheadsinthe harddrive.

U U U U U

HDISK_SIZE_MB Thesizeinmegabytes(MB)of theharddrive.

U U U U U U U U

W

ReportedonlyonsystemswithWMI. S

ReportedonlyforSCSIdevices.

HEADER_INFO_VIEW

Displaysheaderinformationaboutfilesinstalledontarget systems.

Based ontheCOMPUTERHEADER_INFO,andINST_HEADER_INFOtables.

TME_OBJECT_LABEL Theobjectlabelforthesystem. U U

TME_OBJECT_ID TheobjectIDforthesystem. U U

COMPUTER_SYS_ID ThecomputersystemID. U U

HEADER_NAME Thenameofthesoftware. U U

HEADER_VERS Theversionnumberofthe software.

U U

HEADER_PUBLISHER Thepublisherofthesoftware. U U

U U

INST_FILE_VIEW

Displaysbasicinformationaboutfilesinstalledontargetsystems. |

|

| |

(40)

Based ontheCOMPUTERFILE_DESC,FILE_PATH,andUNMATCHED_FILES tables.

Note: OnNetWare, OS/2,and Windows98systems,theCREATED_TIME,

MODIFIED_TIME,andACCESSED_TIME columnscanallbepopulated

dependinguponhowmanyofthetimevaluesthesystemsupports.

FILE_NAME Thenameofthefile. U U U U U U U U U

FILE_SIZE Thesizeofthefile. U U U U U U U U U

PATH Thepathforthefile. U U U U U U U U U

CREATED_TIME Thetimethefilewascreated. U U U U U U U U U

MODIFIED_TIME Thetimethefilewaslast modified.

U U U U U U U U U

ACCESSED_TIME Thetimethefilewaslast accessed.

U U U U U U U U U

FILE_PERMISSIONS Thepermissionsforthefile. U U U U U U U U U

FILE_OWNER Theownerofthefile. U U U U U

FILE_GROUP Thefilegroupthatcontainsthe file.

U U U U U

CHECKSUM_QUICK The32-bitQuickchecksumvalue. U U U U U U U U U

CHECKSUM_CRC32 The32-bitFullchecksumvalue. U U U U U U U U U

CHECKSUM_MD5 The128-bitMD5checksum value.

U U U U U U U U U

INST_SWARE_VIEW

Displaysbasicinformationaboutsoftwarecomponentsinstalledontargetsystems thatare matchedattheendpointusingasignaturescan.

Based ontheCOMPUTERMATCHED_SWARE,andSWARE_SIGtables.

(41)

SWARE_DESC Thesoftwareassociatedwiththis signature.

U U U U U U U U U

SWARE_VERS Theversionofthesoftware associatedwiththissignature.

U U U U U U U U U

SWARE_NAME Thenameofthefileassociated withthissignature.

U U U U U U U U U

SWARE_SIZE Thesizeofthefileassociated withthissignature.

U U U U U U U U U

INVENTORYDATA

Displaysgeneralhardware,memory,andoperatingsysteminformationfortarget systems.

Note: Youmustcollectprocessor,memory,and operatingsystemdataifyouwant tousethis view.

Based ontheCOMPUTER, COMPUTER_SYS_MEM,,INST_PROCESSOR,,and

PROCESSORtables.

TME_OBJECT_LABEL Theobjectlabelforthesystem. U U U U U U U U U U

TME_OBJECT_ID TheobjectIDforthesystem. U U U U U U U U U U

COMPUTER_SYS_ID ThecomputersystemID. U U U U U U U U U U

COMPUTER_MODEL Themodelofthesystem. U U U U U U U

COMPUTER_ALIAS Thehostnameofthesystem. U U U U U U U

SYS_SER_NUM Theserialnumberofthesystem. U U U U U U

PHYSICAL_TOTAL_KB Thetotalamountofinstalled memoryinKB.

U U U U U U U U U U

PHYSICAL_FREE_KB Theamountoffreememoryon thesysteminKB. U U U U U U | | | |

(42)

TOTAL_PAGES Thenumberofmemorypages availableonthesystem.

U U U U U U U U

FREE_PAGES Thenumberoffreememory pagesonthesystem.

U U U U U U

PAGE_SIZE Thesizeofthepageinbytes. U U U U U U U

VIRT_TOTAL_KB Thetotalamountofvirtual memoryonthesystem.

U U U U U U U U

VIRT_FREE_KB Theamountoffreevirtual memoryinthesystem.

U U U U U U U

PROCESSOR_MODEL Themodelfortheprocessor. U U U U U U U U U

PROCESSOR_SPEED Thecurrentspeedatwhichthis processorisrunning.

U U U U U U U U U

OS_NAME Thespecificoperatingsystem (suchasWindows2000 AdvancedServerorWindows 2000Professional)thatisrunning atthetimeofthescan.

U U U U U U U U U

OS_TYPE Thetypeofoperatingsystem (suchasOS/2orWindows2000) thatisrunningatthetimeofthe scan.

U U U U U U U U U

COMPUTER_SCANTIME Thetimeofthelastinventory scaninGMT.

U U U U U U U U U

IP_ADDR_VIEW

Displaysinformationaboutinternetprotocol(IP)addressesontarget systems.

Based ontheCOMPUTERandIP_ADDR tables.

IP_ADDR TheIPaddressforthesystem. U U U U U U U U U

IP_HOSTNAME TheIPhostnameforthesystem. U U U U U U U U U

| | | | | |

Database Schema Reference

IBM

Tivoli

Configuration

Manager

Database

Schema

Reference

Version

4.2.1

IBM

Tivoli

Configuration

Manager

Database

Schema

Reference

Version

4.2.1

Contents

About

this

guide

.

.

.

.

.

.

.

.

.

. vii

Chapter

1.

Introduction

.

.

.

.

.

.

.

. 1

Chapter

2.

History

tracking

.

.

.

.

.

. 3

Chapter

3.

Configuration

repository

views

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

. 9

Chapter

4.

Queries

.

.