Home > Veritas Storage Foundation™ for Oracle Manual Pages

DBED_CKPTPLAN (1)

User Commands

NAME
SYNOPSIS
AVAILABILITY
DESCRIPTION
OPTIONS
NOTES
SEE ALSO

NAME

dbed_ckptplan - utility for managing capacity planning with Storage Checkpoints

SYNOPSIS

dbed_ckptplan -m -s -l

-r scheduleID y | n -p [ listfile ] -d scheduleID=xxxxx listfile=filename -a scheduleID=xxxxx start_date=yyyyy-mm-dd end_date=yyyy-mm-dd y | n listfile=yyy -f scheduleID=xxxxx start_date=yyyy-mm-dd end_date=yyyy-mm-dd y | n listfile=filename -c [ listfile ] [ scheduleID ]

AVAILABILITY

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

lslpp -L VRTSdbed

DESCRIPTION

The dbed_ckptplan command is used to obtain estimates on space usage for Storage Checkpoints. It does this by managing scheduled Storage Checkpoint creation and summarizing statistics from these Storage Checkpoints.

After an estimated schedule has completed, the output will be stored in the /etc/vx/vxdba/logs directory.

OPTIONS

The following options are supported:

-m: Displays the main menu for capacity planning operations.
-s: Displays the Schedule Creation menu.
-l: Lists all schedules created by the current user ID.
-r scheduleID y | n: Sets removal of a schedule identified by the five-digit schedule ID and a yes (y) or no (n) flag. The output is stored under the /etc/vx/vxdba/logs/planscheduleID.out directory in a file named plan followed by the five-digit schedule ID.
-p [ listfile ]: Displays the current Storage Checkpoint space usage on all VxFS file systems. If the listfile argument is supplied, the display will be limited to the mount points specified in the file listfile.
-d scheduleID=xxxxx listfile=filename: Removes Storage Checkpoints created by the schedule specified by its five-digit schedule ID on all mount points specified in the file listfile.
-a scheduleID=xxxxx start_date=yyyy-mm-dd end_date=yyyy-mm-dd y | n listfile=filename: Creates a Storage Checkpoint for the schedule specified by its five-digit schedule ID on all VxFS file systems, where start_date and end_date are specified in yyyy-mm-dd format. If you would like Storage Checkpoints to be removed when the schedule is complete, set the y | n flag to y. If you do not want Storage Checkpoints to be removed with the schedule is complete, set the y | n flag to n.
-f scheduleID=xxxxx start_date=yyyy-mm-dd end_date=yyyy-mm-dd y | n listfile=filename: Creates a Storage Checkpoint for the schedule specified by its five-digit schedule ID on mount points designated in the file listfile. start_date and end_date are specified in yyyy-mm-dd format. If you would like Storage Checkpoints to be removed when the schedule is complete, set the y | n flag to y. If you do not want Storage Checkpoints to be removed with the schedule is complete, set the y | n flag to n.
-c [ listfile ] [ scheduleID ]: Creates a capacity planning Storage Checkpoint. '00000' will be used as the schedule ID if no scheduleID is provided.

NOTES

dbed_ckptplan must be run as the Oracle DBA user. The superuser cannot run this command, since there is no guarantee that the database status can be determined correctly. When creating Storage Checkpoints, it is important to know whether or not the Oracle database is running.

The schedule operates from a user's cron job, so you must have permission to create cron jobs to use the capacity planning tool.

The capacity planning tool creates Storage Checkpoints that have no data associated with them. These types of Storage Checkpoints should not be created on file systems that have Storage Checkpoints containing data. The capacity planning tool checks for this situation and will prevent further use on file systems that contain data-full Storage Checkpoints.