Search <book_title>...

Veritas InfoScale™ 8.0.2 Storage and Availability Management for Oracle Databases - AIX, Linux, Solaris

Last Published: 2023-06-12

Product(s): InfoScale & Storage Foundation (8.0.2)

Platform: AIX,Linux,Solaris

Section I. Storage Foundation High Availability (SFHA) management solutions for Oracle databases
1. Overview of Storage Foundation for Databases
Section II. Deploying Oracle with Veritas InfoScale products
Section III. Configuring Storage Foundation for Database (SFDB) tools
1. Configuring and managing the Storage Foundation for Databases repository database
2. Configuring authentication for Storage Foundation for Databases (SFDB) tools
Section IV. Improving Oracle database performance
Section V. Using point-in-time copies
Section VI. Optimizing storage costs for Oracle
Section VII. Managing Oracle disaster recovery
1. Using Storage Foundation for Databases (SFDB) tools in a replicated environment
2. Using volume snapshots in a replicated environment
Section VIII. Storage Foundation for Databases administrative reference
Section IX. Reference

Defining database parameters

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 SmartTier for Oracle. 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.

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

Table: dbdst_admin command options

Command option	Description
-S $ORACLE_SID	Specifies the ORACLE_SID, which is the name of the Oracle instance.
list	Lists all of the SmartTier for Oracle 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. The default value is 4.
minclass	Minimum number of storage classes allowed in the database. The 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 the 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.
-o definechunk *classname: {128k\|256k\|512k\|1m}*	Defines a chunksize in bytes for the given storage class. Valid chunksizes are 128k, 256k, 512k or 1m bytes. When a chunksize is specified for a storage class, the files in this storage class will be extent-balanced. Each chunk of the file will be in a separate volume of the storage class. A given file will have approximately equal number of chunks on each component volumes of the storage class. When a new volume is added or an existing volume is removed from the storage class (using dbdst_addvol or dbdst_rmvol), the files are automatically balanced again.

Note:

If you do not want to change specific default values, you can omit those parameters when you run the dbdst_admin command. You only need to enter the parameters that need to be changed.

To define database parameters

Use the dbdst_admin command as follows:

dbdst_admin -S $ORACLE_SID -o setup-parameters\
[,storage_class operations]
        setup-parameters
                maxclass=number,minclass=number,\
                        statinterval=minutes
                sweeptime=HH:MM,sweepinterval=days
                purgetime=HH:MM,purgeinterval=days
        storage_class operations
                addclass=classname:"description"
                rmclass=classname
                definechunk=classname:128k | 256k | 512k | 1m
dbdst_admin -S $oracle_sid -o list

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