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

Administering Cached ODM settings with Cached ODM Advisor in SFHA environment

The Cached ODM Advisor simplifies the task of managing the cached ODM settings for database administrators:

Cached ODM Advisor enables you to manage and configure cached ODM on database files without requiring root privileges.
The settings applied with the Cached ODM Advisor are automatically persistent and common across all the cluster nodes.
While the Cached ODM Advisor does not provide an interface to the ODM cachemap, it enables setting the cached ODM setting to ON/ OFF (and not to DEF).
ODM Advisor lets you generate a variety of reports that help you determine which datafiles are suitable for enabling Cached ODM.

The Cached ODM Advisor command dbed_codm_adm should be run by the DBA user.

Note:

If you are using Cached ODM Advisor for clone databases, a clone database will not have the cached ODM settings enabled when it is enabled for the primary database. You must manually enable cached ODM by setting odm_cache_enable = 1 for the clone database.

The Cached ODM Advisor command dbed_codm_adm syntax is illustrated below and its options are listed in Table: Cached ODM Advisor command options.

Cached ODM Administration
dbed_codm_adm
Usage:
-S ORACLE_SID -H ORACLE_HOME -o display [ -n num -c col -t tbs ]
-S ORACLE_SID -H ORACLE_HOME -o display [ -n num ] [ -t tbs ] [-p] [-a]
                            [ -d start_date end_date
                              -m start_time end_time ]
                            [ -b blacklist_file ]
                      						[ datafile ]
-S ORACLE_SID -H ORACLE_HOME -o display [ -n num ] [ -t tbs ] [-p] [-a]
                            [ -u snapshot_range [ -u snapshot_range ] ]
                            [ -b blacklist_file ]
                            [ datafile ]
-S ORACLE_SID -H ORACLE_HOME -o display [ -n num ] [ -u num_snapshots]
						                      [ -t tbs ]
                            [ -b blacklist_file ]
                            [ datafile ]
-S ORACLE_SID -H ORACLE_HOME -o [ on | off | odmstats ] datafile | -f filelist
-S ORACLE_SID -H ORACLE_HOME -o add-to-blacklist { datafile | -f filelist }
-S ORACLE_SID -H ORACLE_HOME -o remove-from-blacklist { datafile | -f filelist }
-S ORACLE_SID -H ORACLE_HOME -o print-blacklist
-S ORACLE_SID -H ORACLE_HOME -o filestate [ datafile | -f filelist ]
-o iostats

Table: Cached ODM Advisor command options

Option	Use
-S ORACLE_SID	Specify the ORACLE_SID. ORACLE_SID is the SID of the Oracle database to be used.
-H ORACLE_HOME	Specify the ORACLE_HOME. ORACLE_HOME is the HOME of the Oracle instance to be used.
-o display	Generate a report of read activity on datafiles.
-o filestate	Diaplay whether datafiles have Cached ODM turned on or not.
-o on	Enable Cached ODM.
-o off	Disable Cached ODM.
-o odmstats	Displays Cached ODM I/O statistics for datafiles.
-o iostats	Displays cumulative I/O statistics for file-type and I/O-type combinations.
-c column_index	Specify the column on which the basic report is sorted. This is an optional field. By default I/O statistics would be sorted on number of physical reads (PHYRDS).
-n num	Change the default number of files included in the report. Use this option together with -o display to show the top num files which are candidates for enabling Cached ODM.
-f filelist	Specify a filename that has the list of datafiles to operate on with one file name on each line. If you do not provide a list, all of the datafiles will be processed, except in the case of the -o on or -o off option.
-t tbs	Specify the tablespace name for which the report is to be generated.
filename	Specify a single file name to be processed.
-d start_date end_date	Specify a date range for which the report is to be generated. The dates are inclusive and they must be specified in yyyy/mm/dd format.
-m start_time end_time	Specify a time range for which the report is to be generated. The start time and end time must be specified as the hour of day in 24-hour format.
-u snapshot_specification	Specify the range of AWR (Automatic Workload Repository) snapshots to consider for the report.
-b blacklist_file	Specify an alternate file to use as a blacklist.
-o add-to-blacklist	Add a file to the default blacklist.
-o remove-from-blacklist	Remove a file from the default blacklist.
-o print-blacklist	Display the blacklisted files.
-a	Include files that have Cached ODM enabled in generated reports.
-p	Suppress tabular formatting to generate output suitable for programmatic processing.