Veritas Storage Foundation 5.1 SP1: Storage and Availability Management for Oracle (5900-1504, April 2011)

To add caching advisories to the cachemap

Add a caching advisory to the cachemap:

# /opt/VRTS/bin/odmadm setcachemap data/data_read_seq=cache,readahead

With this example command, ODM uses caching and readahead for I/O to

online log files (data) that have the data_read_seq I/O type. You can view

the valid file type and I/O type values from the output of the odmadm

getcachemap command.

See the odmadm(1M) manual page.

The cachemap is local on each node. To make the same caching decisions on

each node in a cluster, keep the cachemap settings consistent by running the

same /opt/VRTS/bin/odmadm setcachemap commands on each node in a

cluster.

Making the caching settings persistent across mounts

By default, the Cached ODM settings are not persistent across mounts. You can

make the settings persistent by addng them to odmadm configuration files.

To make the caching setting persistent across mounts

Cachemap settings can be added to /etc/vx/odmadm:

setcachemap data/read_data_header=cache

setcachemap all/datapump=cache,readahead

The cachemap is local on each node. To keep the cachemap consistent in a

cluster, the contents of /etc/vx/odmadm must be the same on each node.

Per-file settings can be manually added to the lost+found/odmadm file in the

file system.

For example, to disable caching for oradata/file1 each time the filesystem is

mounted, enter the following in the lost+found/odmadm file in the file system.

setcachefile oradata/file1=off

The per-file settings in lost+found/odmadm file may also be managed using

Cached ODM Manager. The file should not be edited manually while using

the Cached ODM Manager.

See “Enabling and disabling Cached ODM on datafiles” on page 81.

Improving database performance with Veritas Cached Oracle Disk Manager

Configuring Cached ODM