Creating and Working with Storage Checkpoint Allocation Policies Using dbed_ckptpolicy

You can use the VERITAS Storage Foundation for Oracle dbed_ckptpolicy command to create and administer Storage Checkpoint allocation policies for Multi-Volume File Systems (MVSs). Storage Checkpoint allocation policies specify a list of volumes and the order in which to allocate data to them.

Prerequisites

• You must be logged on as the database administrator (typically, the user ID oracle).

Usage Notes

• All volumes must be MVSs.
• 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 policy 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.
• 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.
• See the dbed_ckptpolicy(1M) manual page for more information.

  To create a Storage Checkpoint allocation policy

Use the dbed_ckptpolicy command as follows:

Output similar to the following is displayed. This example assumes the following:

• Two MVS file systems /mvsfs/v1 and /mvsfs/v2 are used for datafiles.
• File system /mvsfs/v1 is created on volume set mvsvset1.
• File system /mvsfs/v2 is created on volume set mvsvset2.
• Volume set mvsvset1 contains volumes mvsv1, mvsv2, and mvsv3.
• Volume set mvsvset2 contains volumes mvsv4 and mvsv5.

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_policy [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), separated by space, for the policy ckpt_policy [skip,quit]: mvsv2

The following information will be used to create policy ckpt_sample
ckpt_sample             /mvsfs/v2                        mvsv4
ckpt_sample             /mvsfs/v1                        mvsv2

  To display Storage Checkpoint allocation policy within the database

Use the dbed_ckptpolicy command as follows:

If -p ckpt_policy and -c storage_ckpt options are not specified, output similar to the following is displayed:

If -p ckpt_policy option is specified, output similar to the following is displayed:

If the -c storage_ckpt option is specified, output similar to the following is displayed:

  To update a Storage Checkpoint allocation policy

Use the dbed_ckptpolicy command as follows:

Output similar to the following is displayed:

  To assign a Storage Checkpoint allocation policy

Use the dbed_ckptpolicy command as follows to assign an allocation policy to a specified Storage Checkpoint:

  To remove a Storage Checkpoint allocation policy

Use the dbed_ckptpolicy command as follows to remove an allocation policy from a specified Storage Checkpoint: