Home > Veritas Storage Foundation™ for DB2 Manual Pages

DBDST_ADMIN (1)

User Commands

NAME
SYNOPSIS
AVAILABILITY
DESCRIPTION
OPTIONS
Real Application Clusters (RAC) Considerations
EXAMPLES
NOTES
ENVIRONMENT
EXIT STATUS
SEE ALSO

NAME

dbdst_admin - admin volumes in a DBDST ready filesystem into storage classes.

SYNOPSIS

dbdst_admin -D DB2DATABASE \[ -I DB2INSTANCE

-o { setup_parameters | storage_class_operations }

AVAILABILITY

This command is part of Veritas Storage Foundation for DB2. To determine whether this product is installed on an \1 system, type:

lslpp -L VRTSdb2ed

DESCRIPTION

The dbdst_admin command is used to define DBDST configuration parameters for the database. This command allows DBA to define maximum number of classes for a filesystem, minimum number of classes for a filesystem, statistics collection interval for datafiles, when and what time of day to enforce DBDST policies, and how long to keep statistics data in the DBED repository. This command also allows to add, update and remove storage class names for the database. The dbdst_admin command must be run atleast once before using rest of DBDST commands. The storage class PRIMARY, SECONDARY and BALANCE are predefined and DBA need not add these classes. The Storage class, BALANCE is reserved for load balancing file system only. The storage classes CHECKPOINT and METADATA are reserved for futue use. The configuration parameters, once defined, can be changed anytime and can be changed when database is online. The parameters maxclass and minclass are advisory only and not enforced in this release.

OPTIONS

The following options are supported:

.\" $Id: dbdst_options.inc,v 1.1 2006/02/16 01:33:08 susanl Exp $: -D DB2DATABASE Specifies the name of the DB2 database for which information will be retrieved.
-I DB2INSTANCE: Specifies the name of the DB2 instance. If the instance is not specified, the current user will be used as the instance name.
-o list: This option lists all the setup parameters and storage_classes defined for the database so far.
setup_parameters[,setup_parameters]

The following setup parameters are supported.

-o maxclass=<n>: Specifies the upper limit for the number of storage classes for a given DBDST filesystem. In this release, this parameter is not enforced. The default value is 4.
-o minclass=<n>: Specifies the lower limit for the number of storage classes for a given DBDST filesystem. In this release, this parameter is not enforced. The default value is 2.
-o statinterval=<n>: This parameter specifes how often in minutes statistics need to be collected for the datafiles. DBDST framework periodically collects the statistics for datafiles and stores in SFUA repository. For each datafile, the statistics collected include total read operations, total write operations, total IO operations, total blocks read, total blocks written, total IO blocks, average read time in msec and average write time in msec. The blocksize used is 4096 bytes. The default value is 30 minutes. If statinterval is zero, then statistics collection is stopped.
-o sweepinterval=<n>: This parameter specifies how often in days DBDST policies are enforced. The default value is one day. DBDST enforces the policies by scheduling policy task. If sweepinterval is set to zero, then sweeping (policy task) is stopped.
-o sweeptime=<HH:MM>: This parameter specifies the time of the day when the policy enforcement task is run. The HH:MM is specified in 24 Hour format.
-o purgeinterval=<n>: This parameter specifies how long in days, the statistics data need to be kept in SFUA repository. To prevent growing of statistics data, DBA need to specify the purgeinterval. Any statistics older that purgeinterval days will be purged. The default value is 30 days. DBDST purges the statistics using purge task. If purgeinterval is set to zero, purging (purge task) is stopped.
-o purgetime=<HH:MM>: This parameter specifies the time of the day when the purge task is run. The HH:MM is specified in 24 Hour format.
storage_class_options[,storage_class_options]

The following storage_class options are supported.

-o addclass=<classname>:<description>: This option adds a storage class by name classname. The description allows DBA to store some reference text along with classname. The classname may have upto 30 characters and can have letters A-Z and numbers 0-9. Special Characters are not allowed. Storage classnames are case insensitive.
-o rmclass=<classname>: This option removes the specified storage class from repository.
-o definechunk=<classname>:{128k|256k|512k|1m}\fp: This option defines a chunksize in bytes for the given storage class. The valid chi`unksizes are 128k, 256k, 512k or 1m bytes. When a chunksize is specified for a storage class, then the files in this storage class will be extent balanced. Each chunks of the file will be in a separate volumes of the storage class. A given file will have appraximately equal number of chunks on each component volumes of the stortage class. Whenever a new volume is added or an existing volume is removed from the storage class (using dbdst_addvol or dbdst_rmvol), then the files are automatically balanced again.

Real Application Clusters (RAC) Considerations

This command is supported in a RAC environment. This command can be run on any node of the RAC. This command can be run when RAC database is online of offline.

EXAMPLES

This example shows how to add sweeptime, statinterval, purgeinterval and maxclass.


$ /opt/VRTS/bin/dbdst_admin -D PROD    -o statinterval=60,sweepinterval=1,purgeinterval=60,maxclass=3

This example shows how to add storage class FAST and remove storage class JBOD

$ /opt/VRTS/bin/dbdst_admin -D PROD    -o addclass=FAST:"fast emc storage"
$ /opt/VRTS/bin/dbdst_admin -D PROD  -o rmclass=JBOD

NOTES

This command must be run as DB2 instance owner. This command can be executed when the database is online. db2ed_update must be run at least once before this command to ensure an up-to-date repository.

ENVIRONMENT

Please set LIBPATH to include /opt/VRTSdbms3/lib32

EXIT STATUS

0: Command executed successfully.
1: An Error Occured.
101: Licence check failed.
102: No license to execute this command.
103: Invalid Storage Class
104: The device or mount point is not owned by user

DBDST_ADMIN (1)

Table of contents