Home > Veritas Storage Foundation™ for Oracle Manual Pages

DBED_CKPTPOLICY (1)

User Commands

Table of contents


NAME

dbed_ckptpolicy - create or administer Storage Checkpoint allocation policies

SYNOPSIS

dbed_ckptpolicy -S ORACLE_SID [ -H ORACLE_HOME ] [-n] [-h ]

     -o create | update | remove -p ckpt_policy_name 

dbed_ckptpolicy -S ORACLE_SID [ -H ORACLE_HOME ] [-n] [-h ]


     -o display [-c ckpt_name | -p ckpt_policy_name] 

dbed_ckptpolicy -S ORACLE_SID [ -H ORACLE_HOME ] [-n] [-h ]


     -o assign -c ckpt_name 
     -p ckpt_data_policy[,ckpt_metadata_policy] 


AVAILABILITY

Veritas Storage Foundation for Oracle. To determine whether this product is installed on an \1 system, enter:

lslpp -L VRTSdbed


DESCRIPTION

You can use the dbed_ckptpolicy command to create and administer Storage Checkpoint allocation policies. Storage Checkpoint allocation policies specify a list of volumes and the order in which to allocate data to them.

You can use Storage Checkpoint allocation policies to:

When allocation policies are assigned to a Storage Checkpoint, the DBA must specify the mapping for both Storage Checkpoint metadata and file data. If no allocation policies are specified for the Storage Checkpoint, the data is allocated randomly within the primary file system. Storage Checkpoint data and metadata can have different allocation policies assigned to them or use the same policy. Moreover, the same allocation policy can be assigned to multiple Storage Checkpoints.

After an allocation policy is assigned to a Storage Checkpoint, the allocation mechanism attempts to satisfy requests from each device in the order specified in the allocation policy. If the request cannot be satisfied from any of the devices in the allocation policy, the request will fail, even if other devices that have space exist in the file system. Only devices listed in the policy can be allocated.


OPTIONS

The following options are supported:
-S ORACLE_SID
Specifies the name of the Oracle database for which a Storage Checkpoint allocation policy will be created.
-H ORACLE_HOME
Specifies the name of ORACLE_HOME.
-n
Disables SFDB repository refresh. By default, dbed_ckptpolicy will refresh the SFDB repository if this option is not used.
-h
Shows command usage.
-o create | update | remove
Specifies whether to create, update, or remove a Storage Checkpoint allocation policy.
-p ckpt_policy_name
Specifies the name of the Storage Checkpoint allocation policy.
-o display
Displays the Storage Checkpoint allocation policy.
-c ckpt_name
Specifies the name of the Storage Checkpoint.
-o assign
Assigns an allocation policy to the specified Storage Checkpoint.
-p ckpt_data_policy[,ckpt_metadata_policy]
The -p ckpt_data_policy option specifies the name of the allocation policy to assign to Storage Checkpoint data. The -p ckpt_metadata_policy option optionally specifies the name of the allocation policy to assign Storage Checkpoint metadata.


EXAMPLES

In examples below assume the following:

This example shows how to create a Storage Checkpoint allocation policy:

$ /opt/VRTS/bin/dbed_ckptpolicy -S PROD -o create -p ckpt_sample 

File System: /mvsfs/v2 (MVS volumes: mvsv4,mvsv5)
Assigned Data Policy: NONE (MVS Volumes: N/A 
Assigned Meta Data Policy: NONE (MVS Volumes: N/A 
Please enter the volume name(s), sperated by space, for the policy ckpt_sample [skip,quit]: mvsv4
File System: /mvsfs/v1 (MVS volumes: mvsv1,mvsv2,mvsv3)
Assigned Data Policy: NONE (MVS Volumes: N/A 
Assigned Meta Data Policy: NONE (MVS Volumes: N/A 
Please enter the volume name(s), sperated by space, for the policy ckpt_sample [skip,quit]: mvsv2
The following information will be used to create policy ckpt_sample
ckpt_sample             /mvsfs/v2                        mvsv4
ckpt_sample             /mvsfs/v1                        mvsv2
A partial policy is allowed in defining the policy for the storage checkpoint.
A partial policy means the policy does not exist on all file system used by database.

This example shows how to display Storage Checkpoint allocation policies within the database:

$ /opt/VRTS/bin/dbed_ckptpolicy -S PROD -n -o display 

Policy Name          File System Coverage
-------------------- --------------------
 ckpt                Complete
 ckpt_data           Complete
 ckpt_metadata       Complete
 new_ckpt            Partial
 ckpt_sample         Complete
"Partial" indicate that one or more of the file systems used by the database does not contain the named policy.

This example shows how to display information for a specific allocation policy:

$ /opt/VRTS/bin/dbed_ckptpolicy -S PROD -n -o display -p ckpt_sample 

Policy Name      File System                      MVS volumes
---------------- -------------------------------- -----------
ckpt_sample      /mvsfs/v2                        mvsv4
ckpt_sample      /mvsfs/v1                        mvsv2

This example shows how to display the allocation policies assigned to a specified Storage Checkpoint:

$ /opt/VRTS/bin/dbed_ckptpolicy -S PROD -n -o display -c Checkpoint_1095125037 

Storage Checkpoint    File System                      Data Policy      Meta Data Policy
--------------------- -------------------------------- ---------------- ----------------
Checkpoint_1095125037 /mvsfs/v2                        ckpt_data        ckpt_metadata
Checkpoint_1095125037 /mvsfs/v1                        ckpt_data        ckpt_metadata

This example shows how to update a Storage Checkpoint allocation policy:

$ /opt/VRTS/bin/dbed_ckptpolicy -S PROD -n -o update -p ckpt_sample

File System: /mvsfs/v2 (MVS volumes: mvsv4,mvsv5)
Policy: ckpt_sample (MVS volumes: mvsv4)
Please enter the volume name(s), sperated by space, for the policy ckpt_sample [skip,quit]: mvsv5

File System: /mvsfs/v1 (MVS volumes: mvsv1,mvsv2,mvsv3)
Policy: ckpt_sample (MVS volumes: mvsv2)
Please enter the volume name(s), sperated by space, for the policy ckpt_sample [skip,quit]: mvsv2,mvsv3

The following information will be used to create policy ckpt_sample
ckpt_sample             /mvsfs/v2                        mvsv5
ckpt_sample             /mvsfs/v1                        mvsv2,mvsv3

This example shows how to assign an allocation policy to an existing Storage Checkpoint:

$ /opt/VRTS/bin/dbed_ckptpolicy -S PROD -n -o assign -c Checkpoint_1096060202 -p ckpt_data,ckpt_metadata

$ /opt/VRTS/bin/dbed_ckptpolicy -S PROD -n -o display -c Checkpoint_1096060202
Storage Checkpoint    File System                      Data Policy      Meta Data Policy
--------------------- -------------------------------- ---------------- ----------------
Checkpoint_1096060202 /mvsfs/v2                        ckpt_data        ckpt_metadata
Checkpoint_1096060202 /mvsfs/v1                        ckpt_data        ckpt_metadata

Note: You can also use the dbed_ckptcreate command with the -p ckpt_data,ckpt_metadata option to assign an allocation policy to a Storage Checkpoint. For more information, see the dbed_ckptcreate(1M) man page.


NOTES

dbed_ckptpolicy must be run as the Oracle DBA.

The dbed_ckptpolicy command can be used only on file systems using disk layout Version 6.

The VxVM volume set and VxFS Multi-Volume File System features must be enabled to use Storage Checkpoint allocation policies.

The status of a Storage Checkpoint allocation is either partial or complete. A partial policy is one that does not exist on all file systems used by the database. A complete policy is one that exists on all file systems.

The maximum length of a Storage Checkpoint allocation policy name is 64 characters.

For VxFS file systems disk layout Version 7, the volumes in a VxFS Multi-Volume File System can be either one of these types: dataonly and metadataok. Only metadataok volume can be used to store checkpoint metadata. By default, only the first volume that is being added to the VxVM volume set is metadataok volume. This means only the first volume that is being added to the VxVM volume set can be specified in the ckpt_metadata_policy by default. Use the following file system command to change the default setting. To check the flags of each volume in a VxFS Multi-Volume File System, execute the following file system command as root:

/opt/VRTS/bin/fsvoladm queryflags mountpoint

To change a dataonly volume to metadataok volume, execute the following file system command as root:

/opt/VRTS/bin/fsvoladm clearflags dataonly mountpoint volname


SEE ALSO

dbed_ckptdisplay(1M), dbed_ckptmount(1M), dbed_ckptplan(1M), dbed_ckptquota(1M), dbed_ckptremove(1M), dbed_ckptrollback(1M), dbed_ckptumount(1M), dbed_update(1M), dbed_clonedb(1M), oracle_edition(7)

Veritas Storage Foundation for Oracle Administrator's Guide

Last updated: 15 Jan 2006
Copyright ©2009 Symantec Corporation
All rights reserved.