Home > Veritas Storage Foundation™ for DB2 Manual Pages

DB2ED_CKPTDISPLAY (1)

User Commands

Table of contents


NAME

db2ed_ckptdisplay and db2ed_ckptdisplay_all - display Storage Checkpoint(s) and fileset quota values for a DB2 database

SYNOPSIS

db2ed_ckptdisplay [ -I DB2INSTANCE ] -D DB2DATABASE

     [ -c CKPT_NAME ] [ -o dbed | other | all ]
     [ -Q ] [ -n ] [ -h ]

or

db2ed_ckptdisplay_all [ -I DB2INSTANCE ] -D DB2DATABASE


     [ -c CKPT_NAME ] [ -o dbed | other | all ]
     [ -Q ] [ -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_ckptdisplay command displays Storage Checkpoints associated with the current DB2 Database. One or all of the Storage Checkpoints may be displayed, depending on whether the -c option is used.

Quotas limit the use of two principal resources: files and data blocks. Each quota consists of two limits for each resource:

Storage Checkpoint information is displayed with the following columns of output:

Storage Checkpoint            Creation Time             Status
----------------------------  ------------------------  -------
Checkpoint_975876659          Sun Dec  3 12:50:59 2004  P+R
Checkpoint_974424522_wr002    Thu Nov 16 17:28:42 2004  C+W+M
Checkpoint_974424522_wr001    Thu Nov 16 17:28:42 2004  C+W
Checkpoint_974424522          Thu Nov 16 17:28:42 2004  C+W+M

The Status column of the db2ed_ckptdisplay output can contain the following fields:

C
Indicates that the Storage Checkpoint is complete. That is, every file system that the DB2 database resides on contains the Storage Checkpoint.
P
Indicates that the Storage Checkpoint is partial. That is, some file systems on which the DB2 database resides do not contain the Storage Checkpoint. This can occur under three different circumstances: (1) When a file system runs out of space, one or more of the Storage Checkpoint components can be removed. See the db2ed_ckptremove command for more information. (2) When the DB2 database changes shape (that is, has tablespaces and containers added or deleted), more file systems may be added to the configuration. Since these file systems were not present when the Storage Checkpoint was created, the Storage Checkpoint appears to be only a partial image of the DB2 database. (3) Storage Checkpoint elements can be removed at any time by a database administrator.
R
Indicates that the Storage Checkpoint is read only. It has not been modified and therefore is a consistent point-in-time image of the DB2 database and file systems.
W
Indicates that the Storage Checkpoint is writable. It has been mounted read/write and potentially modified. Modified Storage Checkpoints are not valid for Storage Rollback operations, since the data is in an unknown state.
M
Indicates that the Storage Checkpoint is mounted. If it is Read Only, it can be used with either the db2ed_ckptrollback or db2ed_clonedb commands.
I
Indicates that the repository information for the Storage Checkpoint is incomplete.

OPTIONS

The following options are supported:
-I DB2INSTANCE
Specifies the name of the DB2 instance. If the instance name is not specified, the current user will be the instance owner.
-D DB2DATABASE
Specifies the name of the DB2 database for which Storage Checkpoints will be displayed.
-c CKPT_NAME
Specifies a specific Storage Checkpoint to display.
-o dbed | other | all
Specifies which Storage Checkpoints will be displayed. The default is to display only Storage Checkpoints created by Veritas Storage Foundation for DB2. The display format of the other types of Storage Checkpoints is different than the output of Storage Checkpoints created by Veritas Storage Foundation for DB2.
-Q
Displays fileset quota values. The hard limit, soft limit, and current usage are displayed for each underlying file system in the Storage Checkpoint. All values are given in file system blocks. Note that the current usage of any file system with the fileset quota feature disabled will be displayed as zero. Fileset quotas are supported with the Version 6 disk layout introduced in Veritas File System 4.0.
-n
Disables VxDBA repository refresh. By default, db2ed_ckptdisplay will refresh the VxDBA repository if this option is not used.
-h
Shows command usage.

EXAMPLES

This example shows the Storage Checkpoint information that is displayed for the DB2 database, PROD:

$ /opt/VRTS/bin/db2ed_ckptdisplay -D PROD 

Storage Checkpoint            Creation Time             Status
----------------------------  ------------------------  -------
Checkpoint_975876659          Sun Dec  3 12:50:59 2004  P+R
Checkpoint_974424522_wr002    Thu Nov 16 17:28:42 2004  C+W+M
Checkpoint_974424522_wr001    Thu Nov 16 17:28:42 2004  C+W
Checkpoint_974424522          Thu Nov 16 17:28:42 2004  C+W+M

This example shows the output when the -Q option is used to display fileset quota values:

$ /opt/VRTS/bin/db2ed_ckptdisplay -D PROD -Q Checkpoint_1048093940

Checkpoint_1048093940               Wed Mar 19 9:12:20 2004      C+R
 Filesystem                         HardLim   SoftLim    CurrentUse
 /udb_home/inst01_home/indx1_1       100000     50000          2028 
 /udb_home/inst01_home/user1_1       100000     50000          2028 
 /udb_home/inst01_home/temp          150000     80000          2142 
 /udb_home/inst01_home/system1       150000     70000          3092 


NOTES

The db2ed_ckptdisplay can be run as either the DB2 instance owner or the superuser. If you are running the command as root, use the -n option.

If neither the -c nor the -o options are supplied, then all the Storage Checkpoints created by db2ed_ckptcreate are displayed.


SEE ALSO

db2ed_ckptcreate(1M), db2ed_ckptmount(1M), db2ed_ckptpolicy(1M), db2ed_ckptquota(1M), db2ed_ckptremove(1M), db2ed_ckptrollback(1M), db2ed_ckptumount(1M), db2ed_update(1M), db2ed_ckptcreate_all(1M), db2ed_ckptdisplay_all(1M), db2ed_ckptmount_all(1M), db2ed_ckptremove_all(1M), db2ed_ckptrollback_all(1M), db2ed_ckptumount_all(1M), db2ed_clonedb(1M), db2ed_update_all(1M), db2_edition(7)

Veritas Storage Foundation for DB2 Administrator's Guide

Last updated: 3 Nov 2004
Copyright ©2009 Symantec Corporation
All rights reserved.