IBM Tivoli Netcool/Proviso: Database Administraton Guide · 2010. 9. 7. · Preface IBM ®Tivoli Netcool Performance Manager is a bundled product consisting of two main components

Tivoli® Netcool Performance Manager 1.3Wireline Component (Netcool/Proviso 5.2)Document Revision R1E1

Database Administraton Guide

��

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

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

Contents

Preface . . . . . . . . . . . . . . . vNetcool/Proviso components . . . . . . . . . v

Chapter 1. Introduction . . . . . . . . 1

Chapter 2. Registry and spacemanagement. . . . . . . . . . . . . 3Using the dbRegEdit utility . . . . . . . . . 3

Launching dbRegEdit . . . . . . . . . . 3Changing the FIRST_WEEK_DAY registryparameter . . . . . . . . . . . . . . 6

Space management . . . . . . . . . . . . 7Configuring thresholds . . . . . . . . . . 8Monitoring space utilization . . . . . . . . 9Configuring and calling the notifyDBSpace script 12Changing metric tablespace directories . . . . 14Changing the Default Purgeable Window value 15

Gathering Oracle statistics . . . . . . . . . 16

Chapter 3. Database backup andrestore . . . . . . . . . . . . . . . 17Backing Up the DataBase . . . . . . . . . . 17

Terminology and Naming Conventions . . . . 18READ ONLY Tablespaces. . . . . . . . . 20Hot Backups . . . . . . . . . . . . . 21Netcool/Proviso Tablespace Management . . . 21Oracle Recovery Manager (RMAN) . . . . . 21Data Channel Loading Summary . . . . . . 21

Data Channel Reloads . . . . . . . . . . 23Tablespace without Unrecoverable Operations . . . 23Tablespace without Unrecoverable Operations . . . 23

Data Channel Impact . . . . . . . . . . 25Support tools . . . . . . . . . . . . . 26

Recovery . . . . . . . . . . . . . . . 30Sample backup scripts . . . . . . . . . . . 32

Sample script details . . . . . . . . . . 33Estimating space requirements for backup andrecovery . . . . . . . . . . . . . . . 34

Disk or Tape Backups . . . . . . . . . . 34RMAN vs OS Backups . . . . . . . . . 35System . . . . . . . . . . . . . . . 35PROVISO Metadata . . . . . . . . . . 35Metric data . . . . . . . . . . . . . 36Sample Space Queries . . . . . . . . . . 37

Summary . . . . . . . . . . . . . . . 37

Chapter 4. Purging Metric Data . . . . 39Manually Purging Metric Data . . . . . . . . 39Automatically Purging Metric Data . . . . . . 41

Copying and configuring the automatic purgescript . . . . . . . . . . . . . . . 41Using the PV_partition_purge.ksh Purge Script 42

Notices . . . . . . . . . . . . . . 45Trademarks . . . . . . . . . . . . . . 47Additional copyright notices. . . . . . . . . 48

© Copyright IBM Corp. 2010, 2010 iii

iv IBM Tivoli Netcool/Proviso: Database Administraton Guide

Preface

IBM® Tivoli® Netcool® Performance Manager is a bundled product consisting oftwo main components. A wireline component (formerly Tivoli Netcool/Proviso),and a wireless component (formerly Tivoli Netcool Performance Manager forWireless).

This guide assumes that you are a network administrator or operations specialistwho has knowledge of database management.

Audience

The audience for this manual is a database administrator who needs to know howto optimize the use of the Netcool/Proviso database.

Organization

This guide is organized as follows:v Chapter 1, “Introduction,” on page 1v Chapter 2, “Registry and space management,” on page 3v Chapter 3, “Database backup and restore,” on page 17v Chapter 4, “Purging Metric Data,” on page 39

Netcool/Proviso componentsNetcool/Proviso is made up of the following components:v Netcool/Proviso DataMart is a set of management, configuration and

troubleshooting GUIs that the Netcool/Proviso System Administrator uses todefine policies and configuration, as well as verify and troubleshoot operations.

v Netcool/Proviso DataLoad provides flexible, distributed data collection and dataimport of SNMP and non-SNMP data to a centralized database.

v Netcool/Proviso DataChannel aggregates the data collected throughNetcool/Proviso DataLoad for use by the Netcool/Proviso DataView reportingfunctions. It also processes online calculations and detects real-time thresholdviolations.

v Netcool/Proviso DataView is a reliable application server for on-demand,web-based network reports.

v Netcool/Proviso Technology Packs extend the Netcool/Proviso system withservice-ready reports for network operations, business development, andcustomer viewing.

The following figure shows the different Netcool/Proviso modules.

© Copyright IBM Corp. 2010, 2010 v

Netcool/Proviso documentations consists of the following:v Release notesv Configuration recommendationsv User guidesv Technical notesv Online help

The documentation is available for viewing and downloading on the infocenter athttp://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.htm.

vi IBM Tivoli Netcool/Proviso: Database Administraton Guide

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcool_pm.doc/welcome_tnpm.htm

Chapter 1. Introduction

The purpose of this guide is to describe Netcool/Proviso database administrationconcepts and tasks.

This guide covers the following topics:v Registry and space management.v Database backup procedures.v Purging metric data.

© Copyright IBM Corp. 2010, 2010 1

2 IBM Tivoli Netcool/Proviso: Database Administraton Guide

Chapter 2. Registry and space management

This technical note explains how to manage the database registry, tablespace, andfilesystem space.

This section covers the following topics.v Using the dbRegEdit Utility.v Changing the FIRST_WEEK_DAY Registry Parameter.v Space Managementv Gathering Oracle Statistics

Using the dbRegEdit utilityThe dbRegEdit utility is included in your Netcool®/Proviso® distribution and isused to manage the database registry.

The dbRegEdit utility is invoked either from the launchpad or from a commandline. Once invoked, the dbRegEdit utility connects you to the database, then callsthe default text editor to edit the specified registry key.

Note: The Database Registry contains many parameters that can significantlyimpact your Netcool/Proviso environment. Do not make changes to theseparameters unless specifically directed to do so in either the Netcool/Provisodocumentation, or by Netcool/Proviso Technical Support or Professional Services.

Launching dbRegEditThe dbRegEdit utility is invoked either from the launchpad or from a commandline.

About this task

To use the dbRegEdit utility:

Procedure1. Invoke the dbRegEdit utility as follows:

a. Log on to the database server as root.b. Make sure that the Netcool/Proviso distribution is available on the system.c. Set and export the DISPLAY variable. For example:

# export DISPLAY=abcd1:0.0

d. Set and export the BROWSER variable to point to your Web browser. Forexample:On Solaris systems:# BROWSER=/opt/mozilla/mozilla# export BROWSER

On AIX systems:# BROWSER=/usr/mozilla/firefox/firefox# export BROWSER

On Linux systems:


# BROWSER=/usr/bin/firefox# export BROWSER

Note: The BROWSER command cannot include any spaces around theequal sign.

e. Change your working directory to the directory where the launchpadresides.On Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS

On AIX systems:# cd <DIST_DIR>/proviso/AIX

On Linux systems:# cd <DIST_DIR>/proviso/RHEL

Note: <DIST_DIR> is the directory on the hard drive where you copied thecontents of the Netcool/Proviso distribution

f. Enter the following command to start the launchpad:# ./launchpad.sh

g. On the launchpad, click the Netcool/Proviso Configuration Update optionin the list of tasks.

h. On the Netcool/Proviso Configuration Update panel, supply databaseaccess and registry information described in the table:

Table 1. Database access and registry information

Field Name Description

Oracle Home The location of the home directory for Oracle on the database host. Forexample, /opt/oracle/product/10.2.0

User The user name being used to connect to the database. For example,PV_ADMIN.

Password The password for the user name being used to connect to the database.

Oracle TNSName

The name of the Oracle database. For example, PV.

Registry Key The name of the registry key for the Netcool/Proviso component thatwill be updated. The main registry keys are as follows:

v DATABASE — Netcool/Proviso Oracle database

v CHANNELS — Netcool/Proviso DataChannel

v CMGR — Netcool/Proviso DataChannel

v DATALOAD — Netcool/Proviso DataLoad

v DATAMART — Netcool/Proviso DataMart

v DATAVIEW — Netcool/Proviso DataView

Note: For a complete list of registry keys, contact Netcool/Provisocustomer support.

i. Once complete, click on the Netcool/Proviso Configuration Update link.

From the command line:a. Log on to the database server as root.b. Make sure that the Netcool/Proviso distribution is available on the system.c. Set and export the ORACLE_HOME variable. For example:

# export ORACLE_HOME=/opt/oracle/product/10.2.0


d. Change your working directory to the directory where the dbRegedit utilityresides:On Solaris systems:# cd <DIST_DIR>/proviso/SOLARIS/DataBase/SOL10/extraTools/dbRegEdit/

On AIX systems:# cd <DIST_DIR>/proviso/AIX/DataBase/AIX6/extraTools/dbRegEdit/

On Linux systems:# cd <DIST_DIR>/proviso/RHEL/DataBase/RHEL5/extraTools/dbRegEdit/

Note: The extraTools directory is not installed on your disk as part of theNetcool/Proviso installation.

Note: <DIST_DIR> is the directory on the hard drive where you copied thecontents of the Netcool/Proviso distribution

e. Enter the dbRegEdit commands to access the database registry using thefollowing syntax:# ./dbRegEdit User/Password@Oracle_TNS_Name Registry_Key

Table 2. Database access and registry information

Field Name Description

User The user name being used to connect to the database. For example, PV_ADMIN.

Password The password for the user name being used to connect to the database.

Oracle_TNS_Name The name of the Oracle database. For example, PV.

Registry Key The name of the registry key for the Netcool/Proviso component that will beupdated. The main registry keys are as follows:

v DATABASE — Netcool/Proviso Oracle database

v CHANNELS — Netcool/Proviso DataChannel

v CMGR — Netcool/Proviso DataChannel

v DATALOAD — Netcool/Proviso DataLoad

v DATAMART — Netcool/Proviso DataMart

v DATAVIEW — Netcool/Proviso DataView

Note: For a complete list of registry keys, contact Netcool/Proviso customersupport.

2. Once the dbRegEdit utility has been invoked, the parameters associated withthe specified registry key are displayed in your default text editor. For example,if you specified the DATABASE registry key, the following is displayed:# =====================================================================# CONFIGURATION REGISTRY# base key: DATABASE# OPTION: you can add or delete parameters = TRUE# =====================================================================# Lines with ’#’ as first non blank character will be ignored# Hierarchical separators (| and +-) must be strictly used# Only blanks must be used as separators (no Tabs)# End parameters syntax must be NAME : TYPE : "VALUE"# or NAME : TYPE : "VALUE" (FORMAT)# with TYPE in ( BOOLEAN, NUMBER, DATE, STRING, DELETE )# value must be surrounded by double-quotes, format by parenthesis# To delete a parameter, use DELETE as type# Format is either an Oracle date format or a size unit (K, M)# Boolean values must be TRUE or FALSE# Quit editor without saving the file to cancel changes# =====================================================================+- SIZING| +- MAX_FILE_SIZE_MB : NUMBER : "65536"

Chapter 2. Registry and space management 5

| +- ROW_SIZE| | +- BASE : NUMBER : "68"| | +- GA : NUMBER : "62"| | +- RA : NUMBER : "12"| | +- RAW : NUMBER : "2"+- BACKUP| +- READONLY_DELAY : NUMBER : "72"| +- READONLY_TIMEOUT : NUMBER : "1296"+- GENERAL| +- CHECKSUM : STRING : "##unknown##"| +- INSTALL_DIRECTORY : STRING : "/opt/Proviso_setup"| +- VERSION : STRING : "V4.3.1_R2_E1_1297"| +- VLN : STRING : "DB4311297"+- FILESYSTEM| +- THRESHOLD| | +- CRITICAL : NUMBER : "9"| | +- DEADZONE : NUMBER : "95"| | +- WARNING : NUMBER : "8"+- RECORDSCHEMAS| +- THDE| | +- ID : STRING : "THDE42"+- TABLESPACE_THRESHOLD| +- CFGD| | +- CRITICAL : NUMBER : "9"| | +- DEADZONE : NUMBER : "95"| | +- WARNING : NUMBER : "7"| +- CFGI| | +- CRITICAL : NUMBER : "9"| | +- DEADZONE : NUMBER : "95"| | +- WARNING : NUMBER : "7"| +- CFHD| | +- CRITICAL : NUMBER : "9"| | +- DEADZONE : NUMBER : "95"| | +- WARNING : NUMBER : "7"| +- CFHI| | +- CRITICAL : NUMBER : "9"| | +- DEADZONE : NUMBER : "95"| | +- WARNING : NUMBER : "7"| +- LOIS| | +- CRITICAL : NUMBER : "9"| | +- DEADZONE : NUMBER : "95"| | +- WARNING : NUMBER : "7"

To change the settings for a parameter, use your text editor functionality to editthe values that appear between double quotation marks (for example, “95”).

3. When you are satisfied with your edits, write and quit the file.

Changing the FIRST_WEEK_DAY registry parameterThe FIRST_WEEK_DAY registry parameter is used by the DataChannel to determinewhen a new week begins.

Before you begin

You need to do this first.

About this task

By default the FIRST_WEEK_DAY registry parameter is set to MONDAY. If you wish tospecify the alternative value of SUNDAY, you must update the FIRST_WEEK_DAYregistry parameter as described in this section.

To change the FIRST_WEEK_DAY registry parameter:


Procedure1. Perform the steps as described in the “Deploying the Topology” section of the

Netcool/Proviso Installation Guide, selecting Run Next to run each stepindividually.

2. Run each step listed in the deployer step list, stopping when you reach theInstall Database Channel step. Do not run this step.

3. Invoke the dbRegEdit utility as described in Using the dbRegEdit Utility ,specifying CHANNELS as the Registry Key.

4. Search for the following section of the DataChannel registry key:| +- FIRST_WEEK_DAY : STRING : "MONDAY"

5. When you are satisfied with your edits, write and quit the file.6. In the deployer, run the Install Database Channel step and continue running

each remaining step until your Netcool/Proviso environment has beeninstalled.

Space managementNetcool/Proviso provides tools that enable you to configure thresholds andautomatically monitor both tablespace and filesystem space.

When a threshold violation is detected, Netcool/Proviso can then send notificationemail and generate a trap.

The threshold information is stored in the database registry, which you can modifyby using the dbRegEdit utility. For more information on using the dbRegEditutility, see “Launching dbRegEdit” on page 3.

Netcool/Proviso supports the following thresholds for metadata tablespace andfilesystem space:v Warningv Criticalv Dead zone

You can change the value of each threshold type for each tablespace andfilesystem.

By default, when a threshold level is exceeded, the notifyDBSpace shell scriptsends an email to the owner of the script. You can customize the notifyDBSpacescript to send an email notification to any address.

The notifyDBSpace script also supports traps, which you can enable by editing thescript and supplying a hostname for the trap server.

The following sections explain how to configure thresholds, monitor spaceutilization, and configure traps and notification emails.Related concepts

How to configure and call the notifyDBSpace Script.


Configuring thresholdsThresholds are configured for Metadata tablespace and Filesystem space.

About this task

To configure tablespace and filesystem thresholds:

Procedure1. To set the metadata tablespace threshold, invoke the dbRegEdit utility as

described in “Launching dbRegEdit” on page 3, using the following values forthe Registry Key:DATABASE.TABLESPACE_THRESHOLD

The dbRegEdit utility displays the tablespace threshold database file in thedefault editor, as follows:+- TABLESPACE_THRESHOLD| +- CFGD| | +- WARNING : NUMBER : "7"| | +- CRITICAL : NUMBER : "9"| | +- DEADZONE : NUMBER : "95"| +- CFGI| | +- WARNING : NUMBER : "7"| | +- CRITICAL : NUMBER : "9"| | +- DEADZONE : NUMBER : "95"

2. To set the filesystem threshold, invoke the dbRegEdit utility as described in“Launching dbRegEdit” on page 3, using the following values for the RegistryKey:DATABASE.FILESYSTEM

The dbRegEdit utility displays the filesystem threshold database file in thedefault editor, as follows:+- FILESYSTEM| +- THRESHOLD| | +- WARNING : NUMBER : "75"| | +- CRITICAL : NUMBER : "9"| | +- DEADZONE : NUMBER : "99"

3. Reconfigure the threshold limits by editing the numeric values in double quotes(for example, “75”).

Note: These values specify megabytes.4. (Optional: Filesystem-only) Netcool/Proviso allows you to define specific

thresholds for individual filesystems, by creating one or more entries with thefollowing syntax:- SPECIFIC_THRESHOLD_UniqueNumber| | +- WARNING : NUMBER : "Integer"| | +- CRITICAL : NUMBER : "Integer"| | +- DEADZONE : NUMBER : "Integer"| | +- MOUNT_POINT: NUMBER : "MountPoint"

The following shows entries for two SPECIFIC_THRESHOLD filesystemsettings:+- FILESYSTEM| +- THRESHOLD| | +- WARNING : NUMBER : "75"| | +- CRITICAL : NUMBER : "9"| | +- DEADZONE : NUMBER : "99"| +- SPECIFIC_THRESHOLD_1| | +- WARNING : NUMBER : "85"| | +- CRITICAL : NUMBER : "9"| | +- DEADZONE : NUMBER : "95"


| | +- MOUNT_POINT: NUMBER : "/export/home"| +- SPECIFIC_THRESHOLD_2| | +- WARNING : NUMBER : "8"| | +- CRITICAL : NUMBER : "85"| | +- DEADZONE : NUMBER : "9"| | +- MOUNT_POINT: NUMBER : "/export/home"


Monitoring space utilizationNetcool/Proviso allows the monitoring of space utilization using the database API,dbMgr utility and the ProvisoInfo utility.

Netcool/Proviso monitors space utilization in the following ways:v The Database API

The database supports a set of views and procedures that can be calledprogrammatically to determine space utilization.For example, before loading metric data, the DataChannel (LDR/DLDR) callsinto the Database API. The API checks the available space on the destinationmount point.If sufficient space does not exist on the destination mount point, an error isreturned to the load process. The load process will fail and write an errormessage to the proviso log. No data is loaded into the database until the spaceissue is resolved.Note the following:– During regular intervals, the Database API also checks all filesystems against

the user-defined thresholds. If any mount point exceeds the user-definedthreshold, the notifiyDBSpace script is called.

– Metric data tablespaces are automatically monitored and maintained byNetcool/Proviso. If you increase the number of resources collected byNetcool/Proviso, the size of the metric data tablespaces is automaticallyadjusted.

The INFO_TABLESPACE_VW is a view based on a stored procedure, andreturns information about the metadata tablespaces space utilization. Forexample:

The INFO_FILESYSTEM_VW is a view based on a stored procedure, and returnsinformation about the filesystems on the database server.For example, the following is a call to the INFO_FILESYSTEM_VW view:Select * From INFO_FILESYSTEM_VW;

The call returns information like the following:


v The dbMgr utility

The dbMgr command-line utility allows you to analyze the space utilization ofmetadata tablespaces and database filesystems by invoking the utility with themonitorTablespaces or monitorFileSystem option.If any metadata tablespace is found to exceed the user-defined thresholds,dbMgr calls the notifyDBSpace script.

Note: In most cases, rather than running the command manually, you wouldplace an entry in the crontab file to run at a predetermined time each day.For more information on the dbMgr utility, see the Netcool/Proviso dbMgrReference Guide and Chapter 4, “Purging Metric Data,” on page 39.

v The ProvisoInfo utility

The ProvisoInfo utility is made up of two components, a server (theprovisoinfod daemon that runs on the DataMart server) and a GUI that connectsto the server and displays the information that the daemon collects.By default, the provisoinfod daemon collects statistics once a day at 4 AM (thistime can be changed by editing the $PVMHOME/conf/provisoinfo.confconfiguration file). If any metadata tablespace or database filesystem is found toexceed a user defined threshold, the ProvisoInfo utility calls the notifyDBSpacescript.The logic is as follows:– A summary of the database status is collected.– A summary of the database status is collected.– If thresholds are exceeded, the ProvisoInfo utility calls the

$PVMHOME/bin/notifyDBSpace script.The following section explains how to use the ProvisoInfo utility in more detail.

Configuring the ProvisoInfo utilityHow to configure the ProvisoInfo Utility.

About this task

To configure the ProvisoInfo utility:

Procedure1. Log in to the DataMart server.2. Change your working directory to $PVMHOME/conf.3. Make a backup copy of the file provisoinfo.conf by entering the following

command:cp provisoinfo.conf provisoinfo.conf.ORIG

4. Using the text editor of your choice, open the file provisoinfo.conf for editing.

Note: Do not modify ProvisoInfo parameters that are not described in thissection.


5. To change the refresh parameters, search for the key refresh service. The refreshparameters look like the following:#[refresh service]provisoinfo/refresh/time[]=1provisoinfo/refresh/time[1]=day:4::provisoinfo/refresh/timer=1provisoinfo/refresh/alarm=1provisoinfo/refresh/scriptAlarm=notifyDBSpace %statusprovisoinfo/refresh/messageFileAlarm=../log/NotifyDBSpace.log

You can change the following parameters:

time

The time parameter controls how often the ProvisoInfo statistics arerefreshed. To change the time of the refresh, modify the time parameterby doing one of the following:v To refresh the ProvisoInfo statistics more than once per day, add a

new line using syntax like the following:provisoinfo/refresh/time[x+1]=day:HH24:MI:SS

For example, the first line tells ProvisoInfo to refresh statistics at 4:00AM; the second line tells ProvisoInfo to refresh the statistics at 4:00PM:provisoinfo/refresh/time[1]=day:4::provisoinfo/refresh/time[2]=day:16::

v To change the time of an existing refresh, use the following syntax:time[num]=day:HH24:MI:SS

timer

The timer parameter enables or disables the ProvisoInfo server refreshand can be set to one of the following values:v 1 (enabled)v 0 (disabled)

alarm

The alarm parameter enables or disables the call specified by thescriptAlarm parameter, and can be set to one of the following values:v 1 (enabled)v 0 (disabled)

scriptAlarm

The scriptAlarm parameter specifies what action to take if a thresholdhas been exceeded. By default this parameter is set to callnotifyDBSpace. You can modify this entry to perform the action youdesire, for example:proviso/refresh/scriptAlarm=echo `date` "alarm proviso" >> /tmp/alarm.log

messageFileAlarm

The messageFileAlarm parameter tells the ProvisoInfo server where tolog messages. By default, it is set to the proviso.log. You can modifythis parameter to have the ProvisoInfo server log messages anywhereyou desire.

Note: Micromuse recommends that you do not modify this parameter.6. Modify the retention period of the ProvisoInfo utility log files.

The ProvisoInfo utility produces two types of log files:


v Standard ProvisoInfo log files (provisoinfod19881668396.log)v ProvisoInfo summary report (NotifyDBSpace11595514547.log)The ProvisoInfo utility keeps 14 days' worth of Standard ProvisoInfo logs andProvisoInfo summary reports.You can modify these retention periods to meet your own requirements. If youwant to change the default configuration, add the following parameter to theend of the provisoinfo.conf file, replacing Number with the number of daysyou want the log files to be retained:provisoinfo/service/nbDaysLogFilesToKeep=Number

Note: This parameter must be added to the file; it is not already in the file andcommented out.

7. Enable High Availability (HA) hostname.By default, Netcool/Proviso determines the hostname of the ProvisoInfo serverby making a Solaris system call. However, when running the ProvisoInfo serverin an HA cluster, the ProvisoInfo server must use the cluster hostname instead.To configure the ProvisoInfo server to use the cluster hostname, add thefollowing parameter at the end of the provisoinfo.conf file, replacingClusterHostname with the hostname of the cluster:provisoinfo/listener/provisoinfohostname = ClusterHostname


Configuring and calling the notifyDBSpace scriptHow to configure and call the notifyDBSpace Script.

After you have configured thresholds and used the Database API or theNetcool/Proviso utilities to monitor space utilization, you might want to configurethe notifyDBSpace script to change its default notification behavior, which is tosend email to the owner of the script.

By default, the NotifyDBSpace script is configured to do the following:v If there is no status or if the status is NORMAL, NotifyDBSpace does nothing.v If the status is CRITICAL or DEAD_ZONE, NotifyDBSpacean does the following:

– Sends email (by default, to the owner of the script)– Sends an SNMP trap (if the snmpHost is configured)

Note: Two copies of the notifyDBSpace script deliver with Netcool/Proviso, one in$PVMHOME/bin and one in $ORACLE_HOME/bin. The scripts are not identical.

Configuring notifyDBSpace on DataMartHow to configure and call the notifyDBSpace Script.

About this task

To configure the notifyDBSpace script on DataMart:

Procedure1. Log in to the DataMart server.2. Change your working directory to $PVMHOME/bin.3. Make a backup copy of the notifyDBSpace script by entering the following

command:cp notifyDBSpace notifyDBSpace.orig


4. Using the text editor of your choice, open the notifyDBSpace script for editingand carefully edit the script.

5. To change the default email address edit the following section, and change theaddressMail variable to the new email address:################################################################## Mail parameters################################################################## send mail to addressMail : by default script owneraddressMail=`ls -l $scriptName | awk ’{print $3}’`# header of mailheaderMail="NotifyDBSpace - Status: "

You might, for example, define the addressMail variable as follows:[email protected]

6. To enable SNMP traps, uncomment and set the snmpHost variable in thefollowing section:################################################################## Snmp Trap configuration#------------------------# trap manager# snmpHost=<host value># example:# snmpHost="your_trap_manager"#################################################################


Configuring notifyDBSpace on the databaseHow to configure and call the notifyDBSpace Script.

About this task

To configure the notifyDBSpace script on the database:

Procedure1. Log in to the database server.2. Change your working directory to $ORACLE_HOME/bin..3. Make a backup copy of the notifyDBSpace script by entering the following

command:cp notifyDBSpace notifyDBSpace.orig

4. Using the text editor of your choice, open the notifyDBSpace script for editingand carefully edit the script.

5. To change the default email address, edit the following section, and change theSCRIPT_NAME variable to the new email address:SCRIPT_NAME=$0 # Script name

6. To enable SNMP traps, set the SNMP_HOST variable in the following section:## Snmp Trap configuration# -----------------------# Trap manager# SNMP_HOST=<host value>## Example:# SNMP_HOST="your_trap_manager"#SNMP_HOST=""



Calling notifyDBSpaceThe notifyDBSpace script can be called from any script or program.

About this task

The syntax is as follows:notifyDBSpace DatabaseStatus DatabaseMessage

DatabaseStatus can be any of the following:v 0 (Normal)v 1 (Warning)v 2 (Critical)v 3 (Dead zone)

DatabaseMessage can be any string.

Changing metric tablespace directoriesNetcool/Proviso automatically creates tablespaces to store collected metric data inthe directories specified in the CHANNELS registry table.

About this task

You can change these directories using the dbRegEdit utility. As soon as thedirectories are changed, Netcool/Proviso reads the table and begins using the newdirectories. There is no need to move database files or restart components.

To change metric tablespace directories:

Procedure1. To change metric tablespace directories, invoke the dbRegEdit utility as

described in “Launching dbRegEdit” on page 3, using the following values forthe Registry Key:CHANNELS

The dbRegEdit utility invokes your default editor and opens the CHANNELSkey for editing, as follows:| +- NRAW| | +- TABLESPACE| | | +- CURRENT| | | | +- CREATION_PATH : STRING : "/u01/oradata"| | | | +- SIZE : NUMBER : "8240" (M)| | | | +- EXTENT_SIZE : NUMBER : "8192" (K)| | | +- HISTORIC| | | | +- CREATION_PATH : STRING : "/u01/oradata"

2. Change the metric tablespace directories by editing the directory parameterdefined in the CREATION_PATH parameter (for example, “/u01/oradata”).



Changing the Default Purgeable Window valueNetcool/Proviso stores the parameters that specify when metric data is eligible tobe purged in the CHANNELS registry table.

About this task

Netcool/Proviso stores the parameters that specify when metric data is eligible tobe purged in the CHANNELS registry table. The parameters are namedRECENT_KEEP_DAYS, RECENT_KEEP_WEEKS, and RECENT_KEEP_MONTHS.Netcool/Proviso reads the parameters each time it considers whether metric datashould be moved to the purgeable window. If metric data is not in the purgeablewindow, it is not eligible to be purged.

Netcool/Proviso only purges metric data that is older than the sum of theRECENT_KEEP value plus the CURRENT_KEEP value plus 1. If the date suppliedto the purge routine is earlier than this, the purge routine will purge data down tothis value, and then stop. It won't fail, it won't return an error message, and itwon't report that it couldn't delete all the requested data. As far asNetcool/Proviso is concerned, it has successfully purged all eligible partitions.

Procedure1. To change the parameters, invoke the dbRegEdit utility as described in Using

the dbRegEdit utility on page 1, using the following value for the Registry Key:CHANNELS

The dbRegEdit utility invokes your default editor and opens the CHANNELS keyfor editing, as follows:| +- NRAW| | +- CURRENT_KEEP_DAYS : NUMBER : "3"| | +- RECENT_KEEP_DAYS : NUMBER : "32"| +- 1DRA| | +- CURRENT_KEEP_DAYS : NUMBER : "3"| | +- RECENT_KEEP_DAYS : NUMBER : "200"| +- 1DGA| | +- CURRENT_KEEP_DAYS : NUMBER : "3"| | +- RECENT_KEEP_DAYS : NUMBER : "200"| +- 1WRA| | +- CURRENT_KEEP_WEEKS : NUMBER : "2"| | +- RECENT_KEEP_WEEKS : NUMBER : "80"| +- 1WGA| | +- CURRENT_KEEP_WEEKS : NUMBER : "2"| /| +- RECENT_KEEP_WEEKS : NUMBER : "80"| +- 1MRA| | +- CURRENT_KEEP_MONTHS : NUMBER : "2"| | +- RECENT_KEEP_MONTHS : NUMBER : "18"| +- 1MGA| | +- CURRENT_KEEP_MONTHS : NUMBER : "2"| | +- RECENT_KEEP_MONTHS : NUMBER : "18"| +- BASE| | +- CURRENT_KEEP_DAYS : NUMBER : "3"| | +- RECENT_KEEP_DAYS : NUMBER : "32"

Note: While the utility lets you modify each parameter individually, someparameters should remain equal:v 1DRA/1DGA values should matchv 1WRA/1WGA values should matchv 1MRA/1MGA values should match


2. Edit the value of one or more of the RECENT_KEEP parameters (for example,the RECENT_KEEP_DAYS value for 1DRA).


Example

The default RECENT_KEEP_DAYS value for 1DRA data is 200 days, and theCURRENT_KEEP_DAYS value is 3 days. With these value, it is not possible topurge 1DRA data down to less than 204 days. An attempt to purge down to 90days, for example, will not purge data earlier than 204 days.

In order to make 1DRA data eligible for purge after 90 days, theRECENT_KEEP_DAYS parameter for 1DRA should be set to 86 days. The systemwill move the data into a purgeable partition, and then the data can be purged.

If the RECENT_KEEP parameter is reduced, Netcool/Proviso does not immediatelymove data to the purgeable window. Instead, a limited number of partitions aremoved each day until you reach the date specified by the new parameters.

If the RECENT_KEEP parameter is increased, Netcool/Proviso does notimmediately move data out of the purgeable window. Instead, the normal systemoperation will accumulate data in the nonpurgeable window until you reach thenew parameter value.

To change the parameters using the dbRegEdit utility:

Gathering Oracle statisticsNetcool/Proviso uses the Oracle cost-based optimizer to determine the executionplans for the SQL queries that it uses.

Oracle evaluates the relative cost of executing a query using the current size of thetables involved. In order for the optimizer to determine an optimal execution plan,it needs accurate table statistics. Netcool/Proviso, therefore, supports a scheduledOracle statistics-gathering mechanism.

To activate statistics gathering, add the following command to the crontab of theDataMart owner:0 0 * * * [ -f $PVMHOME/dataMart.env ] && . $PVMHOME/dataMart.env && dbMgranalyzeMetaDataTables A N

Note: If you do not add this command to crontab, no statistics will be gathered onthe database metadata and inaccurate execution plans will be generated.

The frequency of the statistics gathering is defined in the CFG_STATS table in theadmin schema. Because there is cost associated with gathering these statistics, thedatabase has an analysis schedule for each Netcool/Proviso table.

Note: After a fresh installation and your initial inventory, Micromuse recommendsthat you manually force a complete statistics gathering using dbMgr with theoption analyzeMetaDataTables and the option force.

For example: dbMgr analyzeMetaDataTables A Y

For more information on the dbMgr command, see the Netcool/Proviso dbMgrReference Guide.


Chapter 3. Database backup and restore

This section explains how to perform backups on the Netcool/ProvisoDataChannel and database components.

This section covers the following topics.v Backing Up the DataBasev Tablespace without Unrecoverable Operationsv Tablespace with Unrecoverable Operationsv Recoveryv Sample Backup Scriptsv Estimating Space Requirements for B&Rv Summary

Backing Up the DataBaseTo reduce backup complexity and enhance reliability, procedures have beendeveloped to assist the user with backup and recovery strategy.

The Netcool/Proviso 5.2 database uses Oracle features that assist loadingperformance (for example, SQL*Loader in direct path mode with the unrecoverableoption.) The use of these features complicates the backup and recovery strategy. Toreduce complexity and enhance reliability, procedures have been developed toassist the user with backup and recovery strategy. These procedures should beconsidered a set of recommendations, requirements and sample code to assist theuser in their environment. Many companies have well defined procedures in placeto perform backup of their databases. With this in mind, we have attempted todevelop a backup procedure that meets IBM requirements with the maximumflexibility for the customer.

In this section, the difference between required steps and sample steps are detailed.

Warnings

Backup and recovery is a complex area of database administration. When coupledwith the use of unrecoverable direct load methods, it becomes significantly morecomplex. Make sure that you understand how the system operates and whatimpact any change will have on the ability to recover the database.

Reference Material

IBM recommends the following reference manuals from Oracle.

Oracle 10g database:v Oracle10gR2 Conceptsv Oracle10gR2 Administrator's Guidev Oracle10gR2 Utilitiesv Oracle10gR2 Backup and Recovery Guidev Oracle10gR2 Recovery Manager User's Guide and Reference


Online versions of these manuals can be found at http://docs.oracle.com/

Concepts

Direct Loading / UNRECOVERABLE

In order to obtain maximum performance, IBM uses the Oracle SQL*Loader utilityin direct path mode with the UNRECOVERABLE option. This use let's loadperformance be as fast as possible but it does have its drawbacks.

One drawback is that direct path loading with the UNRECOVERABLE option doesnot generate redo log information for data being loaded. Objects loaded by thismethod are marked as invalid when a recovery is performed. In order to recoverdata that has been loaded, but not yet backed up as a READ ONLY tablespace, oneof the following two processes must be used:1. Restore the tablespace from a previous intermediate hot backup2. Apply all archive logs3. Revalidate all the objects that were left in an invalid state by the load4. Reload all the data associated with the objects that were revalidated

If the tablespace has not yet been backed up at all:1. Drop the tablespace2. Recreate the tablespace with the same parameters3. Reload all the associated data ( note the load will automatically create the

necessary partitions)

Data must be reloaded in both processes, which means the Netcool/Proviso loadcomponents must be involved with recovery operations. The performance gainsprovided by using direct path with the unrecoverable option far outweigh thecomplexities that an infrequent recovery operation causes. Before attempting arecovery operation, make sure you fully understand how the system operates andwhat the requirements for a complete recovery are.

Terminology and Naming ConventionsThe following Terminology and Naming Conventions are used in this section.

Metric and Meta Data

Meta Data: data used by the system to describe/define the data that is measured.

Examples include:v Formulas (Metrics)v Resources (Subelements)v Hosts (Elements)v Groupingv Thresholds

Metric Data: customer data stored for reporting.

Examples include:v Numeric Raw Datav Baseline Threshold Data


http://docs.oracle.com/

v Resource Aggregationsv Group Aggregationsv Sparse Metrics

DataChannel Components

DataChannel component names include the following:v LDR: Is responsible for merging, remerging and loading hourly raw and

baseline data and all aggregation data, and performing end of period loads foraggregated data.

v DLDR: responsible for sort-merging the 24 individual hourly raw and baselinedata files and loading these merged files into the database.

v CME: Complex Metrics Engine performs resource level data aggregation for asingle Collector.

v BOF: Binary Output File.v Channel: LDR and DLDR operate at the channel level. These components

sort-merge files that arrive from the set of CMEs assigned to that channel andloads them into the database.

Channel Table Set Type

Netcool/Proviso uses the following channel table set types:v NRAW: Numeric Raw valuesv BASE: Baseline Threshold Valuesv 1DRA: Resource aggregated values for one dayv 1WRA: Resource aggregated values for one weekv 1MRA: Resource aggregated values for one monthv 1DGA: Group aggregated values for one dayv 1WGA: Group aggregated values for one weekv 1MGA: Group aggregated values for one monthv SNRW: Sparse Numeric Raw values

Metric Data Tablespaces

FormatC{Chnl}_{Type}_{AggSet}_{TSpace}

with:v {Chnl} The channel set number (from 1 to 8), 2 digits formattedv {Type} The tablespace types (4 characters)v {AggSet} Aggregation Set number - 3 digits formattedv {TSpace} Tablespace identifier defined with a readable date format -

YYYYMMDDHH24 Value 0000000000 is used for working tablespaces.

Examples

Metric Data Tablespace Datafiles

FormatC03_NRAW_000_0000000000

Chapter 3. Database backup and restore 19

The working tablespace containing the raw data for channel three.C02_1WRA_000_2000090400

The historic tablespace containing weekly data for resource aggregates for theweek starting 09-04-2000 at 00.00, aggregation set zero and channel three.{DbId}_C{Chnl}_{Type}_{TSpace}_{file#}.dbf

with:v {DbId}: The Oracle Database namev {Chnl}: The Channel Number (from 1 to 8), 2 digits formattedv {Type}: The Channel Table Set Type (4 characters)v {TSpace}: Tablespace identifier defined with a readable date format -

YYYYMMDDHH24 (0000000000 is defined as a working tablespace) v {File#}: Filenumber of the tablespace

ExamplesTEST_C03_1DGA_0000000000_001.dbf

The first datafile of the C03_1DGA_0000000000 tablespace in the TEST database

READ ONLY TablespacesNetcool/Proviso uses the Oracle READ ONLY tablespace.

Netcool/Proviso uses the Oracle READ ONLY tablespace. When you alter atablespace to READ ONLY, further modifications cannot be made to the datafilesassociated with that tablespace. (Repeated backups of that tablespace becomeunnecessary.) After you alter the tablespace to READ ONLY, perform a finalbackup of the tablespace. You can use that same backup to perform a tablespacerecovery while the tablespace remains READ ONLY.

The tablespace structure is designed to take advantage of the Oracle READ ONLYtablespace. The product creates historical metric data tablespaces based on channelnumber, data type, and date. After all data for the time period indicated is loadedin the tablespace, it can be altered to READ ONLY mode and backed up once. Youdo not have to backup that tablespace again unless data needs to be reloaded forthat time period.

READ ONLY tablespaces issue

When a tablespace is altered to READ ONLY mode, it waits in a transitional stateuntil all transactions in the database started before the command was issued arecompleted. All transactions in the entire database are effected, regardless ofwhether these transactions affect the tablespace you are altering to READ ONLY ornot. Transactions started after the command was issued do not affect the transitionto READ ONLY. Oracle handles these automatically. If an attempt to modify thetablespace in the transitional state is made, it will fail. A change to any othertablespace is allowed and does not affect the edit to READ ONLY transaction.


Hot BackupsA hot backup means that you perform a backup while the database is open andactive.

Hot backups require a database in archivelog mode. The Netcool/Proviso defaultis the database in noarchivelog mode. In order to support backup and recovery, thecustomer must alter the database to archivelog mode. The customer must performthis required step after they create the database. Refer to Oracle Note:69739.1 onthe Oracle support website (http://support.oracle.com) for information on how toenable archivelog mode.

Netcool/Proviso Tablespace ManagementNetcool/Proviso separates the metric and meta data

Netcool/Proviso separates the metric and meta data into two separate schemas:v PV_METRIC schema contains all metric datav PV_ADMIN schema contains all meta data.

Netcool/Proviso has developed tracking tools to monitor and support the system.To support the items above, Netcool/Proviso must be involved in the process.Note that Netcool/Proviso loads data in chronological order. Tablespaces (and thepartitions that reside in them) are date stamped and tied to the date stamps of thedata that resides in them.

Oracle Recovery Manager (RMAN)IBM recommends you use the Oracle-supplied RMAN backup utility to performbackups.

To use RMAN, you must use a RMAN catalog database unless you performbaseline backups on a regular basis. If you decide not to use RMAN, choose amethod that meets the Netcool/Proviso requirements.

Data Channel Loading SummaryThe flow of data through the Data Channel

This following diagram illustrates the flow of data through the Data Channel. Theflow of data within the Data Channel is significantly more complex.1. The Binary Output File (BOF) from a subchannel is placed in the loader “do”

directory. In reality, this could actually be several files from multiplesubchannels that would merged together by the LDR.


2. The corresponding tablespace is created and the file is loaded usingSQL*Loader.

3. After the load is completed, the file is moved to the “state” directory.


4. The file is retained until the tablespace is placed in READ ONLY mode andbacked up. This is done by a asynchronous process. Once the tablespace is inREAD ONLY and backed up, the OS file can then be deleted.

Data Channel ReloadsDataChannel BOF files must remain available for reload.

The DataChannel BOF files must remain available for reload from the time thedata is first loaded into the tablespace, and until the tablespace has been placed inREAD ONLY mode and backed up. These files are used for restoration purposes inthe event of a database failure.

Tablespace without Unrecoverable OperationsTablespaces that do not have UNRECOVERABLE operations performed on themshould be backed up using traditional Oracle backup method.

The tablespaces that do not contain metric data (for example, Netcool/ProvisoMetadata, Rollback, System) should be backed up using a traditional hot backupstrategy. These tablespaces do not have UNRECOVERABLE operations performedon them and should be backed up via this traditional Oracle backup method.Historical Sparse Metric tablespaces also fall into this category.

Tablespace without Unrecoverable OperationsMetric data tablespaces require different backup strategies.

Metric data tablespaces require different backup strategies that are discussed in thesections below. Each of these methods uses a traditional hot backup for metric datatablespaces that have not yet been placed in READ ONLY mode. However, theydiffer in how they approach the backup of READ ONLY tablespaces.

To minimize effort during recovery, backup all metric data tablespaces that havebeen recently placed in READ ONLY mode first, followed by a traditional hotbackup of any metric data tablespaces that are in the process of being loaded.


Traditional Netcool/Proviso Backup Method

The traditional backup method backs up READ ONLY tablespaces once to a morepermanent storage area (i.e. a separate disk location or tape pool), where they areretained until the corresponding data is purged. Backing up the READ ONLYtablespaces once minimizes your regular backup window, as there is less data toprocess on any given backup run. However, this method requires moremanagement overhead, as the backups must be retained and managed using anRMAN catalog database until the data is purged.

Alternative Netcool/Proviso Backup Method

The alternative backup method backs up READ ONLY tablespaces following aperiodic reset of READ ONLY tablespaces. Using this method minimizes yourregular backup window, as there is less data to process until the next reset, andsimplifies management requirements as no RMAN catalog database is required.However, this method requires sufficient backup resources to perform a regularfull backup of all your READ ONLY tablespaces.

Restricting Backups by Set Type

No matter which backup method you select, there are some additional options thatmay help you. There are sample backup scripts that use set types to allow you toreset and backup subsets of the READ ONLY data.

When calling the sample scripts, you can specify the following types as optionsfrom the command line:v individual set type (NRAW, BASE, 1DRA, 1DGA, 1WRA, 1WGA, 1MRA or

1MGA )v a combination of the 1DRA, 1DGA, 1WRA, 1WGA, 1MRA and 1MGA set types

(ALLAGG)v a combination of all the set types (ALL)

The ability to restrict to a particular set type or group of set types is useful inseveral situations:

Scenario 1

You have different data retention requirements for certain set types, and wish tobackup these set types to separate (i.e. different tape pools).v Example 1 - You perform a backup using the sample scripts and the default

value of ALL (a combination of all the set types). This approach requires you toset the tape retention to the set type that has the longest retention requirement.As you are backing up shorter term (NRAW/BASE) and longer term(aggregated) data to the same tape pool, a large number of tapes must beretained whose data will not be used during a recovery operation.

v Example 2 - You perform three backups using NRAW, BASE and ALLAGGoptions. The NRAW and BASE option allows you to allocate the backups to thesame tape pool as they have the same data retention requirements. TheALLAGG option allows you to allocate the backup to a separate tape pool. Thisapproach returns the tapes containing the NRAW and BASE data to their tapepool at the end of their retention window (i.e. 90 days), and the tapes containingthe ALLAGG data to their tape pool at the end of their retention window (i.e. 3years).


Scenario 2

You used the alternative backup method, but do not have sufficient backupresources to complete the backup in the time available. You can reset only aportion of the READ ONLY tablespaces and back up those tablespaces instead.v Example 1 - You have a 10 TB database with roughly 5 TB of raw/base data and

5 TB of aggregated data. Your backup resources allow you to backup 5 TB ofdata during your backup window, and you want to perform a monthly backupof your READ ONLY tablespaces. In this case, you can reset and backup onlythe NRAW and BASE data on the 1st weekend of the month, then perform areset and backup of the aggregation data on the 3rd weekend of the month. Thisapproach allows you to perform full monthly backups of all READ ONLYtablespaces without requiring additional backup resources.

Data Channel ImpactBy default, the Data Channel component of Netcool/Proviso deletes BOF files forspace management.

o enable backups, you must modify the following registry flag:

DATABASE.BACKUP.STATE: The default value of this flag is 0. To enable backups youmust update this flag to 1.

To change this flag:1. Executing the command:

$ dbRegEdit pv_admin/pv DATABASE.BACKUP

Will open the default editor and output the following:+- BACKUP| +- READONLY_TIMEOUT : NUMBER : "129600"| +- READONLY_DELAY : NUMBER : "7200"| +- RESIZE_TIMEOUT : NUMBER : "120"| +- RESIZE_RETRIES : NUMBER : "15"| +- STATE : NUMBER : "0"

2. Change the line:| +- STATE : NUMBER : "0"

To:| +- STATE : NUMBER : "1"

3. And save the file. You should then see a successfully updated message:Configuration updated !

Consult the Registry and Space Management Technote for more information onusing the dbRegEdit utility.

4. After resetting this registry variable, log into sqlplus as PV_ADMIN andexecute the following:SQL> Exec Pvm_Backup.Reinit;

This is a required step that will reinitialize the package variables used by thePVM_BACKUP procedure.


Support toolsA set of tools have been created to support the Netcool/Proviso's backup andrecovery needs

The following components support the product's backup and recovery needs:v TBSP_BACKUP_DESC tablev TBSP_RELOAD_DESC tablev LDR_TBSP_RELOAD_DESC_VW viewv DLDR_TBSP_RELOAD_DESC_VW viewv PVM_BACKUP package

TBSP_BACKUP_DESC tableNetcool/Proviso uses the TBSP_BACKUP_DESC table to track every metric datatablespace created.

Netcool/Proviso uses the TBSP_BACKUP_DESC table to track every metric datatablespace created for the following information:v Currently in READ ONLY mode.v Backup up occurred after being placed in READ ONLY mode.v Last time that an operation was performed on the tablespace.

Name Null? Type-------------------------------- -------- ------------STR_NAME NOT NULL VARCHAR2(32)INT_RO_STATUS NOT NULL NUMBER(1)INT_BU_STATUS NOT NULL NUMBER(1)DTE_DATE NOT NULL NUMBER(10)

When the appropriate Data Channel component (LDR for aggregated data andDLDR for raw data) attempts to load a file after the remerge window is complete,it first calls the ADD_RESIZE_TABLESPACE procedure in the PVM_DATALOADpackage.v If the tablespace does not exist, a row is added to the TBSP_BACKUP_DESC

table with the current date and the ReadOnly (RO) and BackUp (BU) flags areset to zero.

v If the tablespace exists, the record in TBSP_BACKUP_DESC is modified. Thedate is set to current date and the RO/BU flags are set to zero.This table is used by subsequent processes to perform actions such as look forall tablespaces that are ready to be placed into READ ONLY mode and look forall tablespaces that have been placed in READ ONLY mode but that have notbeen backed up yet. This table is also used to prevent BOF files needed forrecovery from being deleted by the flow control process in Data Channel.

TBSP_RELOAD_DESC tableNetcool/Proviso uses the TBSP_RELOAD_DESC table to coordinate activitybetween database recovery and data reloading operations.Name Null? Type--------------------------------- ------- ----------IDX_CHANNEL NOT NULL NUMBER(2)IDX_TABLE_SET_TYPE NOT NULL NUMBER(2)IDX_AGGSET NOT NULL NUMBER(3)DTE_TIMESTAMP NOT NULL NUMBER(10)


LDR_TBSP_RELOAD_DESC_VW viewNetcool/Proviso uses the LDR_TBSP_RELOAD_DESC_VW view to coordinateactivity between database recovery and data reloading operations performed bythe data channel LDR process.

The LDR_TBSP_RELOAD_DESC_VW view is based upon theTBSP_RELOAD_DESC table and is used by Netcool/Proviso to coordinate activitybetween database recovery and data reloading operations performed by the datachannel LDR process. This view is scanned during startup and periodically whilerunning. If the LDR finds rows in this view, it moves the files from the donedirectory to the do directory, deletes the corresponding row fromTBSP_RELOAD_DESC (via an API,) and reloads the data into the database.Name Null? Type------------------------------- -------- --------------CHNL_NUM NOT NULL NUMBER(2)TABLE_TYPE NOT NULL CHAR(4)AGGSET_NUM NOT NULL NUMBER(3)DTE_TIMESTAMP VARCHAR2(4000)

DLDR_TBSP_RELOAD_DESC_VW viewNetcool/Proviso uses the DLDR_TBSP_RELOAD_DESC_VW view to coordinateactivity between database recovery and data reloading operations performed bythe data channel DLDR process.

The DLDR_TBSP_RELOAD_DESC_VW view is based upon theTBSP_RELOAD_DESC table and is used by Netcool/Proviso to coordinate activitybetween database recovery and data reloading operations performed by the datachannel DLDR process. This view is scanned during startup and periodically whilerunning. If the DLDR finds rows in this view, it moves the files from the donedirectory to the do directory, deletes the corresponding row fromTBSP_RELOAD_DESC (via an API,) and reloads the data into the database.Name Null? Type-------------------------------- -------- --------------CHNL_NUM NOT NULL NUMBER(2)TABLE_TYPE NOT NULL CHAR(4)AGGSET_NUM NOT NULL NUMBER(3)DTE_TIMESTAMP VARCHAR2(4000)

PVM_BACKUP packageThe PVM_BACKUP package is used in many different areas of backup andrecovery.

The PVM_BACKUP package is used in many different areas of backup andrecovery. The following information describes the components of the API.

Procedure ALTER_TBSP_TO_READONLY

You can call The Alter_Tbsp_To_Readonly procedure through SQL*Plus or byusing the dbMgr utility. This procedure examines the TBSP_BACKUP_DESC for alltablespaces for the following information:v Tablespace is “full”. All required partitions were placed into the tablespace and

have not been touched for the last X hours as defined byDATABASE.BACKUP.READONLY_DELAY registry parameter (default of 2hours)

v Registry parameter DATABASE.BACKUP.READONLY_TIMEOUT has expired (default is 36 hours ) without any changes to the tablespace.


After the tablespace is set to READ ONLY, the corresponding row inTBSP_BACKUP_DESC has its timestamp updated and the RO flag is set to one.

Procedure BACKUP_COMPLETE_FOR_RO_TBSP

This procedure accepts a tablespace name and updates the TBSP_BACKUP_DESCtable by setting the BU flag to one. This API that lets you notify Netcool/Provisoof a read only tablespace backup.

Function CHECK_BACKUP_OF_EOP

The Data Channel flow control process calls this function to determine if it candelete a BOF file. If the tablespace where the BOF file is destined to reside has boththe RO and BU flags set to one, this function returns a flag to Data Channelindicating an OK to delete the BOF file. If the RO and BU flags are not set to onethe function returns a flag that tells Data Channel not to delete the file.

Procedure CLEANUP_FILE_RELOAD_TABLE

LDR/DLDR calls this procedure as it scans the TBSP_RELOAD_DESC_VW andmoves files for reloading. The API lets LDR/DLDR notify the database that the filehas been moved and will be reloaded.

Procedure REVALIDATE_OBJECTS_IN_TBSP

Use this procedure with care (and only when necessary) during a tablespacerecovery operation. It accepts a tablespace name as an argument and revalidatesthe invalid partitions in the specified tablespace. This procedure is importantbecause of an Oracle problem with invalid objects in a partitioned IOT. When youperform an UNRECOVERABLE direct load into a partitioned IOT and need toperform a subsequent recovery on that tablespace, all partitions that were loadedbut not yet backed up are left in an invalid state. If a table partition in apartitioned IOT is in an invalid state, you cannot truncate the table (as you can ina regular partitioned table.) You can exchange the partition with a stand-alonetable, truncate the stand-alone table, and then exchange it back into the partitionedIOT. The result is the table partition is now empty and valid, and can be reloaded.

The REVALIDATE_OBJECTS_IN_TSP procedure simplifies this operation. Theprocedure identifies the type of table stored in the tablespace you want torevalidate and creates a dummy non-partitioned table of the same definition. Forevery invalid table partition in the tablespace, it exchanges the dummy table withthe partition, truncates the table, and exchanges the non-partitioned table back intothe partitioned IOT. This procedure also populates the TBSP_RELOAD_DESC tablewith one row for every table partition in the tablespace. This procedure has asecond parameter that allows a forced revalidation to be performed. The defaultvalue of the force parameter is FALSE, which means this procedure onlyrevalidates and reloads those partitions currently in an invalid state. If you pass avalue of TRUE to the force parameter, this procedure revalidates every partition inthe tablespace regardless of the partition current state. In most cases, accept thedefault behavior and only revalidate the partitions that are currently invalid.

Procedure DROP_TBSP_AND_RELOAD

Use this procedure with care (when absolutely needed) during a tablespacerecovery operation. It accepts a tablespace name as an argument and drops thespecified tablespace. Use this procedure only when you need to reload a tablespace


that was created since your last backup. This procedure identifies the type of tablestored in the tablespace you want to reload and populates theTBSP_RELOAD_DESC table with one row for every table partition currently in thetablespace. After this process completes, the tablespace is dropped.

Note: The tablespace in question must be offline before running this procedure.Please verify that the tablespace is offline before running this procedure. Ifnecessary, manually take the tablespace offline.

Procedure FORCE_TBSP_DROP_WITHOUT_RELOAD

Use this procedure with care (when absolutely needed) during a tablespacerecovery operation. It is similar to the DROP_TBSP_AND_RELOAD procedure, butdoes not attempt to perform a reload of the tablespace once it drops the tablepartitions. Typically, this procedure is only used in a test or developmentenvironment where backups are not implemented, and data loss is tolerable. Thisprocedure identifies the type of table stored in the tablespace, then drops everytable partition currently in the tablespace. After this procedure completes, thetablespace is dropped.

Procedure UPDATE_BACKUP_STATUS

Use this procedure (a low level API) to update the RO and BU flags in theTBSP_BACKUP_DESC table.

Procedure PURGE_TBSP_BACKUP_DATA

Use this procedure (a low level API) to remove tablespace backup data from theTBSP_BACKUP_DESC table when tablespaces are purged.

Procedure RESET_RO_TBSP_BACKUP_STATUS

This procedure resets the INT_BU_STATUS of all tablespaces back to zero. This, inturn, forces all read-only tablespaces to be backed up again. Use the procedurewhen you want to perform a new baseline backup of all your READ ONLYtablespaces, or you can specify a set type option to this function that limits thereset to a particular set type.

Function DETERMINE_METRIC_PURGE_DATE

Use this function (a low level API) to determine the purge date for a givenchannel, set type, and retention period.

Procedure SYNCHRONIZE_TBSP_BACKUP_DESC

This procedure ensures that the TBSP_BACKUP_DESC table stays synchronizedwith the appropriate Oracle system dictionary view (DBA_TABLESPACES.) Whenrun, the procedure performs the following modifications:v Deletes a row that exists in TBSP_BACKUP_DESC but not in the data dictionaryv Adds a row that exists in the data dictionary but not in TBSP_BACKUP_DESCv Updates TBSP_BACKUP_DESC so the READ ONLY status of the tablespace

matches the data dictionary status


Usually this procedure is not necessary but it is useful in some circumstances (forexample, a tablespace is manually dropped without using the Netcool/Provisotools.)

Function VERSION

This function returns the current version for the PVM_BACKUP package. Theparameter passed indicates whether to return the version for the package spec (0)or the package body (1).

Function REINIT

This function reinitializes package variables. If a modification is made to any of thebackup related registry variables then this procedure must be executed to refreshthe configuration in the running system.

RecoveryRecovery of a Netcool/Proviso database allows you to save critical data should adatabase error occur.

Database Recovery using RMAN

This document does not contain the specifics of how to recover an Oracle databaseusing the RMAN utility. Consult the Oracle documentation for a completedescription of RMAN and how to use it during a database recovery.

Recovery Scenarios

The following information contains basic grouping of recovery scenarios:

Recovery of a meta data or Oracle system related tablespace. Examples include:v SYSTEMv RBSv PV_CFGDv PV_CFGIv PV_CFHDv PV_CFHIv PV_PROHv PV_THRHv PV_REPTv PV_REPMv PV_LOISv PV_VOID

To recover these tablespaces1. Restore the most recent copy of the tablespace using RMAN2. Recover the tablespace by applying all archive logs generated since your

backup was taken.

This scenario shows a recovery after you attempt to startup your database and itreports an error similar to the following:


ORA-01157: cannot identify/lock data file 5 - see DBWR trace fileORA-01110: data file 5: ’/export/home2/PV/PV_PV_CFHD_0001.dbf’

The following information appears in the alert log:Errors in file /export/home/oracle/admin/PV/bdump/pv_dbw0_3051.trc:ORA-01157: cannot identify/lock data file 5 - see DBWR trace fileORA-01110: data file 5: ’/export/home2/PV/PV_PV_CFHD_0001.dbf’ORA-27037: unable to obtain file statusSVR4 Error: 2: No such file or directoryAdditional information: 3ORA-1157 signalled during: ALTER DATABASE OPEN...

Log into RMAN, restore and recover the tablespace and then open the database:RMAN> run2> {3> allocate channel ch1 type disk;4> restore tablespace PV_CFHD;5> recover tablespace PV_CFHD;6> }RMAN-03022: compiling command: allocateRMAN-03023: executing command: allocateRMAN-08030: allocated channel: ch1RMAN-08500: channel ch1: sid=9 devtype=DISKRMAN-03022: compiling command: restoreRMAN-03022: compiling command: IRESTORERMAN-03023: executing command: IRESTORERMAN-08016: channel ch1: starting datafile backupset restoreRMAN-08502: set_count=139 set_stamp=446155924 creation_time=18-NOV-01RMAN-08089: channel ch1: specifying datafile(s) to restore from backup setRMAN-08523: restoring datafile 00005 to /export/home2/PV/PV_PV_CFHD_0001.dbfRMAN-08023: channel ch1: restored backup piece 1RMAN-08511: piece handle=/export/home5/hot_backup/df_PV_1_139 tag=nullRMAN-08024: channel ch1: restore completeRMAN-03022: compiling command: recoverRMAN-03023: executing command: recover(3)RMAN-08054: starting media recoveryRMAN-03022: compiling command: recover(4)RMAN-06050: archivelog thread 1 sequence 11 is already on disk as file /export/home4/PV/arch/PV_1_11.archRMAN-06050: archivelog thread 1 sequence 17 is already on disk as file /export/home4/PV/arch/PV_1_17.archRMAN-03023: executing command: recover(4)RMAN-08515: archivelog filename=/export/home4/PV/arch/PV_1_11.arch sequence=11RMAN-08515: archivelog filename=/export/home4/PV/arch/PV_1_15.arch sequence=15RMAN-08055: media recovery completeRMAN-08031: released channel: ch1RMAN> run2> {3> sql ’alter database open’;4> }RMAN-03022: compiling command: sqlRMAN-06162: sql statement: alter database openRMAN-03023: executing command: sqlRMAN>

Recovery of a tablespace that has been placed into READ ONLY mode and backedup.

While similar to the first scenario, it differs in that you only have to restore thetablespace. No recovery is needed because it has been READ ONLY mode eversince it was backed up.RMAN> run2> {3> allocate channel ch1 type disk;4> restore tablespace C01_NRAW_000_2001111500;5> }

RMAN-03022: compiling command: allocateRMAN-03023: executing command: allocateRMAN-08030: allocated channel: ch1RMAN-08500: channel ch1: sid=9 devtype=DISKRMAN-03022: compiling command: restoreRMAN-03022: compiling command: IRESTORERMAN-03023: executing command: IRESTORERMAN-08016: channel ch1: starting datafile backupset restore


RMAN-08502: set_count=121 set_stamp=446063881 creation_time=17-NOV-01RMAN-08089: channel ch1: specifying datafile(s) to restore from backup setRMAN-08523: restoring datafile 00104 to /export/home3/PV/PV_C01_NRAW_000_2001111500_001.dbfRMAN-08023: channel ch1: restored backup piece 1RMAN-08511: piece handle=/export/home6/readonly_backup/df_PV_1_121 tag=nullRMAN-08024: channel ch1: restore completeRMAN-08031: released channel: ch1RMAN> run2> {3> sql ’alter database open’;4> }RMAN-03022: compiling command: sqlRMAN-06162: sql statement: alter database openRMAN-03023: executing command: sqlRMAN>

Recovery of a tablespace that has data loaded into it but has not been backed up topermanent storage.

How you handle this scenario depends on whether you have intermediatebackups:

If you have an intermediate backup, restore the tablespace and run theREVALIDATE_OBJECTS_IN_TBSP procedure in PVM_BACKUP. (Having the BOFfiles is important.) This procedure populates the TBSP_RELOAD_DESC table.LDR/DLDR then scans the corresponding views and reloads the associated filesinto the table partitions.

If you do not have an intermediate backup and you have not yet created anytablespaces newer then the one you want to restore, run theDROP_TBSP_AND_RELOAD procedure in PVM_BACKUP. This procedure dropsthe tablespace and populates the TBSP_RELOAD_DESC table. LDR/DLDR thenscans the corresponding views, creates the tablespace, and reloads the associatedfiles into the table partitions.

Sample backup scriptsNetcool/Proviso provides sample backup scripts that you can tailor to your systemneeds.

Why use samples?

Every location has a different backup philosophy. Some installations are moremature than others. Some need guidance and some require us to fit into theirstructure. The backup method was developed based on the knowledge that no twolocations are alike. Several sample scripts were developed that can be modified fora specific locationt. Or scripts developed at the lcoation can be used as long asNetcool/Proviso requirements are met.

Sample script list

The samples developed to support Netcool/Proviso backup are located in theextraTools directory of the shipped product. For example, extraTools/conf,extraTools/backup and extraTools/purgepart. These scripts continue to evolve andnewer versions will become available as time goes on. Search the sample scripts for‘# Customize for given environment' to make changes for a given location. The listincludes the following:v logon.infov PV_Tbsp_Alter_ReadOnly.kshv PV_Hot_Skip_Readonly.ksh


v PV_Readonly_Tbsp_Backup.kshv PV_Reset_Backup_Status.kshv PV_partition_purge.ksh

The PV_partition_purge.ksh script needs to be run as the Netcool/ProvisoDataMart owner (i.e. pvuser) but the rest of the scripts should be run as the oraclesoftware owner (i.e. oracle).

Sample script detailsThe backup and recovery scripts discussed in this document are completelyfunctional samples. However, the scripts have been created to perform backup onlya simple environment for the purposes of illustration.

These scripts perform single channel backups to disk using a recovery catalog.Customers will need to add some level of customization to these scripts for thescripts to work in their environment. Examples of common changes include:v Support for multichannel backupsv Support for tape backupsv Backups without using a recovery catalog

The specifics of how to perform these customizations are not covered within thisdocument; however, an experienced Oracle DBA should be familiar with theconcepts and changes that would needed.

If you decide not to use a recovery catalog, you should read the Oracledocumentation concerning the CONTROL_FILE_RECORD_KEEP_TIME parameter.This parameter must be set to a value that is larger then the window of timeneeded for backup retention. The default value of this parameter (14 days) is notsufficient for the typical TNPM Wireline deployment. Most installations will setthis parameter to 40 days (assuming a full backup reset done once a month), butthe actual value for your installation will need to be determined based upon yourrequirements.

logon.info

This file provides a common location of environment information used in thefollowing scripts. It stores information such as usernames and passwords instead ifstoring them in each script. The following scripts extract the necessary informationfrom the logon.info file. Therefore, a copy of this file must exist and be accessibleby the user who is running these scripts.

PV_Tbsp_Alter_ReadOnly.ksh

The ALTER_TBSP_TO_READONLY procedure is called directly through SQL*Plusor through the dbMgr utility. This sample script is a wrapper around the SQL*Pluscall of this stored procedure. The script detects whether the previous iteration ofthe script is still running. As mentioned in an earlier section, an edit to READONLY command can hang if there are open uncommitted transactions on thedatabase. (For example, someone updates a row in SQL*Plus and then goes homefor the weekend. This sample script exits if the previous run is still active. Thescript can be customized for specific locations. Examples of customizations includethe following:v Sending an email if the previous iteration is still running.v Sending a page if the previous iteration is still running.


v Executing another script if the previous iteration is still running.v Changing the number of days worth of logs to keep.

If this script, or one like it, place a call to the associated dbMgr command in thecrontab. The command should normally be called once or twice per day. Forfurther documentation about the dbMgr utility, see QLAB1026D

PV_Hot_Skip_Readonly.ksh

The PV_Tbsp_Alter_ReadOnly.ksh script uses Oracle's RMAN utility to perform ahot backup of all tablespaces that are not in READ ONLY mode.

PV_Readonly_Tbsp_Backup.ksh

The PV_Readonly_Tbsp_Backup.ksh script queries the TBSP_BACKUP_DESC tableand dynamically creates the RMAN commands that will perform a tablespace levelbackup of every tablespace that is in READ ONLY mode but has not been backedup. It also formats the commands that call theBACKUP_COMPLETE_FOR_RO_TBSP procedure. This script then calls thegenerated script to actually perform the backup. By default, this script backs up alleligible tablespaces, but you can restrict the backup to a particular set type byusing the “-st” command line option.

PV_Reset_Backup_Status.ksh

The PV_Reset_Backup_Status.ksh script resets the backup state of the tablespacesstored in the TBSP_BACKUP_DESC table. This script is used in conjunction withthe alternative backup method. The script has a “-st” command line option thatallows you to specify which set type to reset.

PV_partition_purge.ksh

The PV_partition_purge.ksh script automates the managment of metric dataretention in the database. You can call a dbMgr procedure purge data for a givenchannel and set type, which results in the purging of metric data tablespaces.

Estimating space requirements for backup and recoveryThe overhead of back up and recovery requires that the appropriate amount ofdisk space is reserved.

Disk or Tape BackupsThe first decision you will face is whether to backup to disk or to tape.

Each approach has advantages and disadvantages:v disk backups allow for a faster recovery but require the purchase of additional

disk spacev direct to tape backups often require a Media Manager to interface with your

tape drives, which adds additional requirements and complexity to the processunless you are already familiar with this area

v if you backup to disk, often the disks are backed up to tape

Choose a solution that suits your needs. Many locations select a combination ofdisk and tape backups where a disk backup is performed and a subsequent job


backs up those disks to tape. This approach allows you to maintain the most recentbackup on disk for quick recoveries while minimizing the space needed for thatdisk backup.

RMAN vs OS BackupsYou can use RMAN or an OS backup utility to perform backups.

One advantage that RMAN has over traditional OS backups is that it reducesbackup space requirements by “skipping” the portions of the tablespace that areunused, which is sometimes referred to as a compressed backup. RMAN uses thehigh water mark of the file when determining where it can stop the backup. Toillustrate with an example, take a tablespace that is 100M is size but only the first10M has ever been used. In this case, an OS backup utility will backup the entire100M file, while RMAN will backup the first 10M and places a marker in thebackup file indicating that the file is 100M in size, but that the space between 10and 100M is empty. The net result is a significantly smaller backup when usingRMAN instead of the OS utility. However, when the tablespace is completely full,the RMAN and OS backups will produce backup files of similar size.

SystemYou can use RMAN or an OS backup utility to perform backups.

The components that are typically backed up include:v SYSTEM, SYSAUX, UNDO and RBS tablespacesv control filesv archived redo logsv init files

The overhead of backing up these objects is relatively constant once your systemreaches a steady state volume. It is approximated by examining their current sizeand the available free space. When you first start, estimate space requirementsequal to the current size of all objects, plus an estimate of the archived redo logvolume. Archived redo log space requirements are directly proportional to the rateof change in your particular environment. Note that metric data is loaded directlyand will not significantly contribute to the redo volume, while metadata actionscontribute to redo volume. The extent to which metadata actions contributedepends upon several factors, such at the frequency of inventories, size of yournetwork, and the frequency of change in your network. Assuming a nightlybackup, you need this space for each backup you wish to retain.

PROVISO MetadataEstimating the space required to backup the Proviso metadata.

The space required to backup the proviso metadata is relative to the size of themetadata tablespaces.

The metadata tablespaces include:v PV_CFGDv PV_CFGIv PV_CFHDv PV_CFHIv PV_PROH


v PV_THRHv PV_REPTv PV_REPMv PV_LOISv PV_TIDEv PV_TBDEv PV_EVNT

Assuming that you are using RMAN, you can estimate the space required for a fullbackup of these tablespaces using the Oracle data dictionary. Sum up the size ofthe segments in these tablespaces, or subtract the available free space in thesetablespaces from their current size. Refer to the next section for examples of thesequeries. If you are using OS backups, you will require space equivalent to thecurrent size of these tablespaces. Metadata increases over time, and so does thespace required for backups. Similar to archived redo volume, the spacerequirement depends on the size of your network and the frequency of change inyou environment. Assuming a nightly backup, you need this space for each nightlybackup you wish to retain.

Metric dataEstimating the space required to backup the working metric data.

In Process Metric Data

The space required to backup the working metric data is relative to the total size ofall working tablespaces, plus the most recently loaded non-working metrictablespaces. Working metric data tablespaces end with 0000000000. The size ofthese tablespaces is dependent on the size of you network, the frequency ofcollection, the number of collected metrics, how your data and data remergewindows are grouped. An estimate of this volume can be obtained fromNetcool/Proviso when you have an accurate estimate of your collection volumes.Assuming a nightly backup, you need this space for each backup you wish toretain.

READ ONLY Metric Data

You can save a significant amount of space by selecting a particular backupmethod. A traditional backup method backs up the entire database on a regularbasis, and retains a week or two of these backups on tape. As READ ONLYtablespaces are used, these tablespaces only require a single backup once they areplaced into READ ONLY mode (assuming you are using the traditionalNetcool/Proviso backup method). Therefore, the total space required to backup theREAD ONLY metric data is equal to the total size of these tablespaces. An estimateof this volume can be obtained from Netcool/Proviso once you have an accurateestimate of your collection volumes. The amount of space required during eachnightly backup is relatively small, as only the tablespaces that were most recentlyloaded need to be backed up.

If you use the alternative Netcool/Proviso backup method, the space requirementsfor READ ONLY metric data will be slightly higher then the traditionalNetcool/Proviso method. The total requirements depend on how frequently youperform a reset and backup.


Sample Space QueriesEstimating the space required to backup the working metric data.

Determine Tablespace Size

The Dba_Data_Files view provides this information:Select Sum(Bytes)/1048576From Dba_Data_FilesWhere Tablespace_Name = ’<TABLESPACE_NAME>’;

For example:Select Sum(Bytes)/1048576From Dba_Data_FilesWhere Tablespace_Name = ’PV_CFGD’;

Determine Free Space in a Tablespace

The Dba_Free_Space view provides this information:Select Sum(Bytes)/1048576From Dba_Free_SpaceWhere Tablespace_Name = ’<TABLESPACE_NAME>’;

For example:Select Sum(Bytes)/1048576From Dba_Free_SpaceWhere Tablespace_Name = ’PV_CFGD’;

Determine Space Used by Objects in a Tablespace

The Dba_Segments view provides this information:Select Sum(Bytes)/1048576From Dba_SegmentsWhere Tablespace_Name = ’<TABLESPACE_NAME>’;

For example:Select Sum(Bytes)/1048576From Dba_SegmentsWhere Tablespace_Name = ’PV_CFGD’

SummaryA summary of the decisions and steps required to implement backup and recovery.

Backup

Ultimately, the customer is responsible for backing up their data and for ensuringthey can recover it in case of failure. Though Netcool/Proviso has provided severaltools that simplify and assist in the task, an experienced database administratorshould review this document and develop the final backup strategy for theirspecific installation. Backups must be monitored and tested to ensure properrecovery of the database. Even if users decide not to perform backups, they muststill meet the requirements defined above.

Required Steps:v The customer must call dbMgr alterTablespaceReadOnly at least once per day. It

is recommended they use a script similar to PV_Tbsp_Alter_ReadOnly.ksh


v The customer does have flexibility about how to perform their backups andwhat tools they use, but they must notify Netcool/Proviso by using theBACKUP_COMPLETE_FOR_RO_TBSP procedure in PVM_BACKUP. If they failto do this, EOP BOF files will not be deleted and the LDR/DLDR directories willfill up.

v If you use the traditional Netcool/Proviso backup method, then you must use aRMAN catalog database

v When enabling backups, remember to modify the DATABASE.BACKUP.STATEregistry flag so that the DataChannel component will call the begin protectingthe metric data until it no longer needs to be reloaded.

Recovery

The recovery of an Oracle database that is in an inconsistent state is not aneveryday task. But, when the need arises, you must be confident in your backup.This is also not a task that just anyone can perform. Oracle recovery scenarios arequite extensive. An experienced Oracle database administrator should be able toanalyze the situation and perform the appropriate steps to recover your database.


Chapter 4. Purging Metric Data

The purpose of this section is to describe how to free up space in your database bypurging metric data.

Overview

To free up space in the database, it is good practice to purge the database atregular intervals or when certain thresholds are met. Always purge the databasewhen there is 10% or less free space available.

Free space can be monitored in two different ways:v From the DataMart → Monitor → Database Information window. For more

information, see the Netcool/Proviso DataMart Operation Guide.v By issuing the $PVHOME/bin/dbMgr command and selecting the

showPurgeablePartitions option from the character-cell menu. Note that$PVMHOME is defined as /opt/datmart by default.

After you have determined that free space needs to be reclaimed, you can purgemetric data manually. However, once you have determined trends and the types ofrecords that you can purge, you can configure the purge to be done automatically.

The following sections explain these operations in detail.

Note: Netcool®/Proviso® has a default minimum retention period of 32 days forraw and baseline data, 200 days of daily aggregates, 80 weeks of weeklyaggregates, and 18 months of monthly aggregates. If you require a differentminimum retention period, contact IBM support for assistance.

Note: Netcool/Proviso 5.2 introduced a new sparse metric data type called SNRW.This data type has a fundamentally different data storage model than the existingmetric types mentioned in this document. There is no purge mechanism availablefor this data type.

Manually Purging Metric DataFreeing up space in your database by manually purging metric data.

About this task

To purge metric data manually, follow these steps:

Procedure1. Log in as pvuser (or the user name that you specified during installation) on

the system where DataMart is installed.2. Source the DataMart environment using the following command:

. /opt/datamart/dataMart.env

3. Change your working directory to $PVMHOME/bin, by entering the followingcommand. Note that $PVMHOME is defined as /opt/datmart by default.cd $PVMHOME/bin

4. Invoke the Database Manager utility by entering the following command:


./dbMgr

The dbMgr utility displays the following menu:

(c) IBM Database Manager (1.2.1)List of Procedures1. addTablespace2. adjustDataloadsTempTablespace3. alterTablespaceReadOnly4. analyzeMetaDataTables5. deleteOffHoursPeriod6. generateFilesColdBackup7. insertOffHoursPeriod8. monitorFileSystem9. monitorTablespaces10. purgePartitions11. resizeTablespaceFile12. selectOffHoursPeriod13. showDBPackageVersions14. showPurgeablePartitions15. showTablespaceFiles16. versionDeleteBySingleProvisoComp17. versionDeleteProvisoGlobal18. versionRptByProvisoAppQ. Quit P. Previous N. NextChoice:

5. To obtain a list of purgeable partitions, select the showPurgeablePartitionsoption.

6. To initiate a purge of metric data, select the purgePartitions option and purgethe partitions returned by the showPurgeablePartitions option in the previousstep. The dbMgr utility displays a window like the following window:

(c) IBM Database Manager (1.2.1)Procedure: purgePartitionsargument value-------- -----1. Channel# 12. Data type NRAW3. Date 2009.05.01-004. Format YYYY.MM.DD-HH24B. Back P. Previous N. Next E. ExecuteChoice: eprocedure: purgePartitions 1 NRAW 2009.05.01-00 YYYY.MM.DD-HH24Confirmation (y/n): y

You must specify the channel, data type, and date for which you want purge torun.

7. Select E to execute the purge.8. Repeat step 6 for each set type that needs to be purged.

Note: You can also execute a purge directly from the command line, using thedbMgr command with the following syntax:dbMgr purgePartitions <Channel#> <Data type> <Date>


Automatically Purging Metric DataFreeing up space in your database by automatically purging metric data.

Netcool/Proviso supports the ability to purge metric data automatically, by usingthe PV_partition_purge.ksh script and by placing an entry for the script in the/etc/crontab file.

Note: The PV_partition_purge.ksh script resides in the extraTools directory on theNetcool/Proviso CDROM.

To use the PV_partition_purge.ksh script you must first copy it from theNetcool/Proviso CD-ROM and do some initial configuration. The followingsections explain these operations in more detail.

Copying and configuring the automatic purge scriptNetcool/Proviso supports the ability to purge metric data automatically. However,you must first copy and configure the script for your system.

About this task

To copy and configure the automatic purge script, follow these steps:

Procedure1. Log in as root or become superuser on the system where DataMart is

installed.2. Place the Netcool/Proviso CD-ROM in the CD-ROM drive. The CD-ROM

typically automounts into the directory /cdrom/proviso.3. To create an extraTools directory on the DataMart server to hold the conf and

purgepart directories, enter the following command:mkdir $PVHOME/extraTools

4. To copy the conf and purgepart directories from the Netcool/ProvisoCD-ROM to the extraTools directory you created in Step 3, enter the followingcommands:cd $PVHOME/extraToolscp /cdrom/proviso/Datamart/extraTools/conf .cp /cdrom/proviso/Datamart/extraTools/purgepart .

5. To change the ownership of the conf and purgepart directories and theircontents to pvuser, enter the following commands:chown -R pvuser confchown -R pvuser purgepart

6. To change your working directory to the conf directory, enter the followingcommand:cd conf

7. To make a backup copy of the logon.info file, enter the following command:cp logon.info logon.info.bak

8. Using the text editor of your choice, open the logon.info file for editing.The logon.info file contains environment information that thePV_partition_purge.ksh script requires in order to run correctly.Ensure that the following variables have the same values as the values you setduring the installation of Oracle and Netcool/Proviso. The syntax is VARIABLE<SPACE> DEFINITION.

Chapter 4. Purging Metric Data 41

Note: The variables have default settings, as indicated in the following list. Ifthese definitions are incorrect, change them.v The Oracle home directory

ORA_HOME /opt/oracle/product/10.2.0

v The value of the Oracle SID to back up or purge.ORA_SID PV

v The Oracle logon used to run backup and purge scripts.ADMIN_USER pv_admin

v The password of the Oracle logon used to run backup and purge scripts.ADMIN_PASS pv

v The home directory of Netcool/Proviso DataMart (used during purge).DM_DIR /opt/datamart

9. Write and quit the file.10. To change your working directory to the purgepart directory, enter the

following command:cd purgepart

11. To make a backup copy of the PV_partition_purge.ksh file, enter the followingcommand:cp PV_partition_purge.ksh PV_partition_purge.ksh.bak

12. Using the text editor of your choice, open the PV_partition_purge.ksh file forediting and make the following changes:v The PV_partition_purge.ksh script defines the DIRNAME variable as

follows:DIRNAME="/opt/datamart/extraTools/purgepart"

If you elected to install DataMart in a different directory from/opt/datamart (the default), change this variable to the correct path.

v By default, the purge script keeps seven days of logs. To change the default,edit the following variable:DEF_daystokeep="7";

13. Write and quit the file.

Using the PV_partition_purge.ksh Purge ScriptNetcool/Proviso supports the ability to purge metric data automatically. However,you must first copy and configure the script for your system.

About this task

To use the PV_partition_purge.ksh script to purge metric data automatically, followthese steps:

Procedure1. Ensure that you have configured the PV_partition_purge.ksh script as

explained in Copying and Configuring the Automatic Purge Script.2. Log in as root or become superuser on the system where DataMart is installed.3. Change your working directory to $PVMHOME/extraTools/purgepart, by

entering the following command. Note that $PVMHOME is defined as/opt/datmart by default.cd $PVMHOME/extraTools/purgepart

4. Enter the following command to invoke the PV_partition_purge.ksh help:


./PV_partition_purge.ksh -?

Usage: ./PV_partition_purge.ksh[-dmh <Path to datamart home {default:/opt/datamart}>][-dl <Number of days worth of logs to keep {default:7}>][-os <ORACLE_SID {default:PV}>][-oh <ORACLE_HOME {default:/opt/oracle/product/8.1.7}>][-ou <ORACLE user with admin privs {default:pv_admin}>][-oup <ORACLE user’s passwd with admin privs {default:pv}>]<[-dr <how many days to KEEP the data for [RAW]>] ||[-db <how many days to KEEP the data for [BASE]>] ||[-da <how many days to KEEP the data for [1DRA/1DGA]>][-wa <how many weeks to KEEP the data for [1WRA/1WGA]>][-ma <how many months to KEEP the data for [1MRA/1MGA]>]>[-c <what channel to perform the purge for (0 for all channels) {default:0}>][-u]

5. When calling PV_partition_purge.ksh, the first six option arguments are takenfrom the variables defined in PV_partition_purge.ksh and logon.info. Typically,these arguments do not need to be changed on the command line.However, you must specify a value for one or more of the KEEP options. Hereare some examples of how to call PV_partition_purge.ksh:v The following command deletes all data older than 60 days for raw and

baselines, 200 days for daily aggregates, 80 weeks for weekly aggregates, and18 months for monthly aggregates for all channels:PV_partition_purge.ksh -dr 60 -db 60 -da 200 -wa 80 -ma 18

v The following example deletes all data older than 90 days for raw, 120 daysfor baselines, 365 days for daily aggregates, 104 weeks for weekly aggregates,and 24 months for monthly aggregates for channel 1 only.PV_partition_purge.ksh -dr 90 -db 120 -da 365 -wa 104 -ma 24 -c 1

6. When you have determined what metric data to purge, place an entry incrontab so that the script can be run automatically at prescribed intervals. Formore information about using crontab, see the crontab.1 man page.Here are some examples of how to call PV_partition_purge.ksh from thecrontab file:v The following example shows the crontab entries of a sample system that

deletes all data older than 60 days for raw and baselines, 200 days for dailyaggregates, 80 weeks for weekly aggregates and 18 months for monthlyaggregates for channel 1 and all data older than 120 days for raw, 180 daysfor baselines, 200 days for daily aggregates, 80 weeks for weekly aggregatesand 18 months for monthly aggregates for channel 2.0 2 * * * /opt/datamart/extraTools/purgepart/PV_partition_purge.ksh -dr 60 -db 60 -da 200 -wa80 -ma 18 -c 10 3 * * * /opt/datamart/extraTools/purgepart/PV_partition_purge.ksh -dr 120 -db 180 -da 200 -wa 80 -ma 18 -c 2

v The following example shows the crontab entries that deletes all data olderthan 60 days for raw and baselines, 200 days for daily aggregates, 80 weeksfor weekly aggregates and 18 months for monthly aggregates for allchannels.0 2 * * * /opt/datamart/extraTools/purgepart/PV_partition_purge.ksh -dr 60 -db 60 -da 200 -wa80 -ma 18

Chapter 4. Purging Metric Data 43


Notices

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

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

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

COPYRIGHT LICENSE:

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


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

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

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,other countries, or both.

Cell Broadband Engine and Cell/B.E. are trademarks of Sony ComputerEntertainment, Inc., in the United States, other countries, or both and is used underlicense therefrom.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

ITIL is a registered trademark, and a registered community trademark of the Officeof Government Commerce, and is registered in the U.S. Patent and TrademarkOffice.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the United States, other countries,or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

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

Other company, product, and service names may be trademarks or service marksof others.

For trademark attribution, visit the IBM Terms of Use Web site(http://www.ibm.com/legal/us/).

Notices 47

http://www.ibm.com/legal/copytrade.shtml

Additional copyright noticesThe following copyright information is for software used by Tivoli NetcoolPerformance Manager Wireline Component.

Tcl 8.3.3, Combat/TCL 0.7.3, Combat/TCL 0.7.5, TclX 8.3, TK 8.3.3

This software is copyrighted by the Regents of the University of California, SunMicrosystems, Inc., Scriptics Corporation, and other parties. The following termsapply to all files associated with the software unless explicitly disclaimed inindividual files.

The authors hereby grant permission to use, copy, modify, distribute, and licensethis software and its documentation for any purpose, provided that existingcopyright notices are retained in all copies and that this notice is included verbatimin any distributions. No written agreement, license, or royalty fee is required forany of the authorized uses. Modifications to this software may be copyrighted bytheir authors and need not follow the licensing terms described here, provided thatthe new terms are clearly indicated on the first page of each file where they apply.

IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANYPARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIALDAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITSDOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THEAUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANYWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN"AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NOOBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,ENHANCEMENTS, OR MODIFICATIONS.

GOVERNMENT USE: If you are acquiring this software on behalf of the U.S.government, the Government shall have only "Restricted Rights" in the softwareand related documentation as defined in the Federal Acquisition Regulations(FARs) in Clause 52.227.19 (c) (2). If you are acquiring the software on behalf of theDepartment of Defense, the software shall be classified as "Commercial ComputerSoftware" and the Government shall have only "Restricted Rights" as defined inClause 252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the authorsgrant the U.S. Government and others acting in its behalf permission to use anddistribute the software in accordance with the terms specified in this license.

SCOTTY Stack

This software is copyrighted by Juergen Schoenwaelder, the Technical University ofBraunschweig, the University of Twente, and other parties. The following termsapply to all files associated with the software unless explicitly disclaimed inindividual files.

The authors hereby grant permission to use, copy, modify, distribute, and licensethis software and its documentation for any purpose, provided that existingcopyright notices are retained in all copies and that this notice is included verbatimin any distributions. No written agreement, license, or royalty fee is required forany of the authorized uses. Modifications to this software may be copyrighted by


their authors and need not follow the licensing terms described here, provided thatthe new terms are clearly indicated on the first page of each file where they apply.


THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANYWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN“AS IS” BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NOOBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,ENHANCEMENTS, OR MODIFICATIONS.

Various copyrights apply to this package, listed in 3 separate parts below. Pleasemake sure that you include all the parts. Up until 2001, the project was based atUC Davis, and the first part covers all code written during this time. From 2001onwards, the project has been based at SourceForge, and Networks AssociatesTechnology, Inc hold the copyright on behalf of the wider Net-SNMP community,covering all derivative work done since then. An additional copyright section hasbeen added as Part 3 below also under a BSD license for the work contributed byCambridge Broadband Ltd. to the project since 2001.

Part 1: CMU/UCD copyright notice: (BSD like)

Copyright © 1989, 1991, 1992 by Carnegie Mellon University

Derivative Work - 1996, 1998-2000

Copyright © 1996, 1998-2000 The Regents of the University of California

All Rights Reserved

Permission to use, copy, modify and distribute this software and its documentationfor any purpose and without fee is hereby granted, provided that the abovecopyright notice appears in all copies and that both that copyright notice and thispermission notice appear in supporting documentation, and that the name of CMUand The Regents of the University of California not be used in advertising orpublicity pertaining to distribution of the software without specific writtenpermission.

CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIMALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALLIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENTSHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BELIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES ORANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATAOR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OROTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITHTHE USE OR PERFORMANCE OF THIS SOFTWARE.

Part 2: Networks Associates Technology, Inc copyright notice (BSD)

Notices 49

Copyright © 2001, Networks Associates Technology, Inc

All rights reserved.

Redistribution and use in source and binary forms, with or without modification,are permitted provided that the following conditions are met:v Redistributions of source code must retain the above copyright notice, this list of

conditions and the following disclaimer.v Redistributions in binary form must reproduce the above copyright notice, this

list of conditions and the following disclaimer in the documentation and/orother materials provided with the distribution.

v Neither the name of the NAI Labs nor the names of its contributors may be usedto endorse or promote products derived from this software without specificprior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ANDCONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUTNOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Part 3: Cambridge Broadband Ltd. copyright notice (BSD)

Portions of this code are copyright © 2001, Cambridge Broadband Ltd.


Redistribution and use in source and binary forms, with or without modification,are permitted provided that the following conditions are met:v Redistributions of source code must retain the above copyright notice, this list of

conditions and the following disclaimer.v Redistributions in binary form must reproduce the above copyright notice, this

list of conditions and the following disclaimer in the documentation and/orother materials provided with the distribution.

v The name of Cambridge Broadband Ltd. may not be used to endorse or promoteproducts derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER “AS IS” ANDANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THECOPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUTNOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,


STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

BLT 2.4u

Portions (c) 1993 AT&T, (c) 1993 - 1998 Lucent Technologies, (c) 1994-1998 SunMicrosystems, Inc., and (c) 1987-1993 The Regents of the University of California.

Permission to use, copy, modify and distribute this software and its documentationfor any purpose and without fee is hereby granted, provided that the abovecopyright notice appears in all copies and that both that copyright notice and thispermission notice appear in supporting documentation, and that the names ofAT&T, Lucent Technologies Inc., Sun Microsystems, Inc. and The Regents of theUniversity of California not be used in advertising or publicity pertaining todistribution of the software without specific written permission.

THE COPYRIGHT HOLDERS AND OTHER CONTRIBUTORS DISCLAIM ALLWARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALLIMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENTSHALL THE COPYRIGHT HOLDERS OR OTHER CONTRIBUTORS BE LIABLEFOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANYDAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA ORPROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OROTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITHTHE USE OR PERFORMANCE OF THIS SOFTWARE.

CMU-SNMP 1.14

CMU/UCD copyright notice: (BSD like)

Copyright 1989, 1991, 1992 by Carnegie Mellon University

Derivative Work - 1996, 1998-2000 Copyright 1996, 1998-2000 The Regents of theUniversity of California

All Rights Reserved



Notices 51

Scotty 2.8, incrTCL 3.0, [incr TCL] 3.2

Portions Copyright (c) 1987-1994 The Regents of the University of California.Copyright (c) 1994-1995 Sun Microsystems, Inc.

This software is copyrighted by the Regents of the University of California, SunMicrosystems, Inc., and other parties. The following terms apply to all filesassociated with the software unless explicitly disclaimed in individual files.

The authors hereby grant permission to use, copy, modify, distribute, and licensethis software and its documentation for any purpose, provided that existingcopyright notices are retained in all copies and that this notice is included verbatimin any distributions. No written agreement, license, or royalty fee is required forany of the authorized uses. Modifications to this software may be copyrighted bytheir authors and need not follow the licensing terms described here, provided thatthe new terms are clearly indicated on the first page of each file where they apply.


THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANYWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULARPURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN"AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NOOBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES,ENHANCEMENTS, OR MODIFICATIONS.

RESTRICTED RIGHTS: Use, duplication or disclosure by the government is subjectto the restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in TechnicalData and Computer Software Clause as DFARS 252.227-7013 and FAR 52.227-19.

Portions Copyright (c) 1993-1998 Lucent Technologies, Inc.

Permission to use, copy, modify, and distribute this software and its documentationfor any purpose and without fee is hereby granted, provided that the abovecopyright notice appear in all copies and that both that the copyright notice andwarranty disclaimer appear in supporting documentation, and that the names ofLucent Technologies any of their entities not be used in advertising or publicitypertaining to distribution of the software without specific, written priorpermission.

Lucent disclaims all warranties with regard to this software, including all impliedwarranties of merchantability and fitness. In no event shall Lucent be liable for anyspecial, indirect or consequential damages or any damages whatsoever resultingfrom loss of use, data or profits, whether in an action of contract, negligence orother tortuous action, arising out of or in connection with the use or performanceof this software.


UCD SNMP 4.2.5

Portions Copyright 1989, 1991, 1992 by Carnegie Mellon University. DerivativeWork - 1996, 1998-2000, Copyright 1996, 1998-2000 The Regents of the University ofCalifornia All Rights Reserved



Portions Copyright: (c) 2001-2003, Networks Associates Technology, Inc, (c)2001-2003, Cambridge Broadband Ltd, (c) 2003-2005, Sparta, Inc., (c) 2004, Cisco,Inc and Information Network Center of Beijing University of Posts andTelecommunications, (c) Fabasoft R&D Software GmbH & Co KG, [email protected].


Redistribution and use in source and binary forms, with or without modification,are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list ofconditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, thislist of conditions and the following disclaimer in the documentation and/or othermaterials provided with the distribution.

3. Neither the names of Networks Associates Technology, Inc, CambridgeBroadband Ltd., Sparta, Inc., Cisco, Inc, Beijing University of Posts andTelecommunications, Fabasoft R&D Software GmbH & Co KG or any of itssubsidiaries, brand or product names, nor the names of their contributors may beused to endorse or promote products derived from this software without specificprior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ANDCONTRIBUTORS `ÀS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS ORCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

Notices 53

NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IFADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

JDOM 1.0

Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin. All rights reserved.

Redistribution and use in source and binary forms, with or without modification,are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list ofconditions, and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, thislist of conditions, and the disclaimer that follows these conditions in thedocumentation and/or other materials provided with the distribution.

3. The name "JDOM" must not be used to endorse or promote products derivedfrom this software without prior written permission. For written permission, pleasecontact <request_AT_jdom_DOT_org>.

4. Products derived from this software may not be called "JDOM", nor may"JDOM" appear in their name, without prior written permission from the JDOMProject Management <request_AT_jdom_DOT_org>.

In addition, we request (but do not require) that you include in the end-userdocumentation provided with the redistribution and/or in the software itself anacknowledgement equivalent to the following:

"This product includes software developed by the JDOM Project(http://www.jdom.org/)." Alternatively, the acknowledgment may be graphicalusing the logos available at http://www.jdom.org/images/logos.

THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS ORTHE PROJECT CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDINGNEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OFTHIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCHDAMAGE.

This software consists of voluntary contributions made by many individuals onbehalf of the JDOM Project and was originally created by Jason Hunter<jhunter_AT_jdom_DOT_org> and Brett McLaughlin <brett_AT_jdom_DOT_org>.For more information on the JDOM Project, please see <http://www.jdom.org/>.


Regex 1.1a

Copyright (C) 1996, 1999 Vassili Bykov. It is provided to the Smalltalk communityin hope it will be useful.

1. This license applies to the package as a whole, as well as to any component of it.By performing any of the activities described below, you accept the terms of thisagreement.

2. The software is provided free of charge, and `às is'', in hope that it will beuseful, with ABSOLUTELY NO WARRANTY. The entire risk and all responsibilityfor the use of the software is with you. Under no circumstances the author may beheld responsible for loss of data, loss of profit, or any other damage resultingdirectly or indirectly from the use of the software, even if the damage is caused bydefects in the software.

3. You may use this software in any applications you build.

4. You may distribute this software provided that the software documentation andcopyright notices are included and intact.

5. You may create and distribute modified versions of the software, such as portsto other Smalltalk dialects or derived work, provided that:

a. any modified version is expressly marked as such and is not misrepresented asthe original software;

b. credit is given to the original software in the source code and documentation ofthe derived work;

c. the copyright notice at the top of this document accompanies copyright noticesof any modified version.

Notices 55


��

Printed in USA

Documents

IBM Tivoli Netcool/Proviso: Database Administraton Guide · 2010. 9. 7. · Preface IBM ®Tivoli Netcool Performance Manager is a bundled product consisting of two main components