Home > Veritas Storage Foundation™ for DB2 Manual Pages

DB2ED_CKPTCREATE (1)

User Commands

NAME
SYNOPSIS
AVAILABILITY
DESCRIPTION
OPTIONS
EXAMPLES
NOTES
SEE ALSO

NAME

db2ed_ckptcreate and db2ed_ckptcreate_all - create a Storage Checkpoint for a DB2 database

SYNOPSIS

db2ed_ckptcreate [ -I DB2INSTANCE ] -D DB2DATABASE

[ -o [ online | offline][,remove | noremove ] ] [ -p ckpt_data_policy[,ckpt_metadata_policy] ] [ -n ] [ -h ]

db2ed_ckptcreate_all [ -I DB2INSTANCE ] -D DB2DATABASE

[ -o [ online | offline][,remove | noremove ] ] [ -p ckpt_data_policy[,ckpt_metadata_policy] ] [ -n ] [ -h ]

AVAILABILITY

This command is part of Veritas Storage Foundation for DB2. To determine whether this product is installed on an \1 system, type:

lslpp -L VRTSdb2ed

DESCRIPTION

The db2ed_ckptcreate command creates a Storage Checkpoint for a DB2 database. Depending on whether or not the database is active, the online or offline option can be specified to take the appropriate steps to ensure a valid Storage Checkpoint.

Storage Checkpoints provide a frozen image of the containers in a DB2 database. They do not provide frozen images for online redo log files.

Frozen database images can be used for data recovery in the event of logical data corruption in the database and for mounting and backing up frozen images. They can also be cloned and made writable for online modification (such as investigative work and debugging).

OPTIONS

The following options are supported:

-I DB2INSTANCE

Specifies the name of the DB2 instance. If the instance is not specified, the current user will be used as the instance owner.

-D DB2DATABASE

Specifies the name of the DB2 database for which a Storage Checkpoint will be created.

-o

Specific options:

online | offline

Specifies the expected behavior at Storage Checkpoint time for the database. If online is specified, the expected behavior is to create a Storage Checkpoint by putting the database into write suspend mode. If offline is specified, the database is expected to be inactive. The default behavior is to expect the database to be active for Storage Checkpoint creation.

-o remove | noremove

Specifies the behavior of the file system when it runs out of space. By default, when a file system containing Storage Checkpoints runs out of space, the older Storage Checkpoints are removed to allow operations to proceed on the main file system. If it is critical to maintain the Storage Checkpoint even if the file system it resides on is out of space, specify the noremove option.

-p ckpt_data_policy[,ckpt_metadata_policy]

Assigns an allocation policy for Storage Checkpiont data. You can also optionally assign an allocation policy for Storage Checkpoint metadata. Before assigning an allocation policy, you must first create it.

-n

Disables VxDBA repository refresh. By default, db2ed_ckptcreate will refresh the VxDBA repository if this option is not used.

-h

Shows command usage.

EXAMPLES

This example shows how to create a Storage Checkpoint while the database is online:

$ /opt/VRTS/bin/db2ed_ckptcreate -D PROD -o online

An online Storage Checkpoint Checkpoint_971672042 is created at GMT 
2004-06-01 -18.22.34.0000.

This example shows how to create a Storage Checkpoint while the database is offline:

$ /opt/VRTS/bin/db2ed_ckptcreate -D PROD -o offline
An offline Storage Checkpoint Checkpoint_971672042 s created at GMT 
2004-06-01 -18.22.34.0000.

This example shows how to assign a Storage Checkpoint allocation policy to Storage Checkpoint data and metadata:

$ /opt/VRTS/bin/db2ed_ckptcreate -D PROD -o online 
-p ckpt_data_policy,ckpt_metadata_policy

Creating online Storage Checkpoint of database mvsdb.
Storage Checkpoint Checkpoint_1096060122 created.

NOTES

The db2ed_ckptcreate command must be run as the DB2 instance owner. The superuser cannot create Storage Checkpoints, since there is no guarantee that the database status can be correctly identified.

DB2ED_CKPTCREATE (1)

Table of contents