Defining database parameters for Database Dynamic Storage Tiering using dbdst_admin

Running the dbdst_admin command defines parameters for the entire database. You must run this command at least once to define the database parameters for Database Dynamic Storage Tiering. Three pre-defined storage classes will be created (PRIMARY, SECONDARY, and BALANCE). Parameter values are stored in the SFDB repository.

Set at least one of the parameters in maxclass, minclass, statinterval, sweeptime, sweepinterval, purgetime, or purgeinterval, to enable default values. Add at least one class to enable the default classes.

Before defining your database parameteres using the dbdst_admin command, review the following information:

Prerequisites

  • An Oracle database must be up and running.

  • Run the dbed_update command before running any of the Database Dynamic Storage Tiering commands. You should also run the dbed_update command if any of the database files change.

    Because the Database Dynamic Storage Tiering commands retrieve database information from the repository, the repository must be up to date.

  • Change the owner of the mount point on which you want to implement Database Dynamic Storage Tiering to oracle.

Usage notes

  • Only the Oracle database administrator can run Database Dynamic Storage Tiering commands.

  • If you are using any of the Database Dynamic Storage Tiering commands in a high availability (HA) environment, the time on each system in the cluster must be synchronized.

  • Create the volumes that you want to add to the multi-volume file system in the same disk group as the file system volume. As root, use the following command to change the owner of each volume:

    # /opt/VRTS/bin/vxedit -g disk_group \
    set user=oracle volume

Define the LD_LIBRARY_PATH environment variable as follows:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/VRTSdbed/common/lib; \
export LD_LIBRARY_PATH

Table: Oracle dbdst_admin command options lists the options for the Oracle dbdst_admin command.

Table: Oracle dbdst_admin command options

Option

Description

-S $ORACLE_SID

Specifies the ORACLE_SID, which is the name of the Oracle instance.

list

Lists all the Database Dynamic Storage Tiering parameters of the database, including class name and description. This option should be used exclusively from the other options.

maxclass=

Maximum number of storage classes allowed in the database. Default value is 4.

minclass=

Minimum number of storage classes allowed in the database. Default value is 2.

sweepinterval=

Interval for file sweeping for file relocation. Default value is 1, which means one per day. If this value is set to 0, all scheduled sweep tasks will become unscheduled.

sweeptime=

Time per day for the file sweep to take place. Times are entered in 24-hour periods and should list hour: minute. For example, 8:30 AM is represented as 08:30 and 10:00 PM is represented as 22:00. Default value is 22:00.

statinterval=

Interval in minutes for gathering file statistics. Default value is 30, which represents every 30 minutes. If this value is set to 0, all scheduled tasks will become unscheduled.

purgeinterval=

Number of days after which the file statistics in the repository will be summarized and purged. Default value is 30. It is recommended that you set your purge interval sooner because you will not be able to view any statistics until the first 30-day interval is over, if you use the default.

purgetime=

Time per day for the file purge to take place. Times are entered in 24-hour periods and should list hour: minute. For example, 8:30 AM is represented as 08:30 and 8:00 PM is represented as 20:00. Default value is 20:00.

addclass=

Parameter that allows you to add a class to a database. The information should be entered as class:"description", where class represents the class name and description is a string of up to 64 characters enclosed by double quotes used to describe the class.

rmclass=

Parameter that allows you to remove a class from a database. Enter the class name as it appears in the database.

definechunk=

Defines a chunksize in bytes for a specific storage class to extent balance the files in this storage class. The information should be entered as classname: valid chunksize value. Valid chunksizes are 128k, 256k, 512k or 1m bytes.

To define database parameters

For example, to add a class called tier1 for database PROD, and to set up a purge interval of one, meaning that the file statistics will be gathered for one day and then summarized and purged, use the dbdst_admin command as follows:

$ /opt/VRTS/bin/dbdst_admin -S PROD -o addclass=tier1:"Fast Storage",\
purgeinterval=1