Home > Veritas Storage Foundation™ for DB2 Manual Pages

DB2ED_CHECKCONFIG_ALL (1)

User Commands

Table of contents


NAME

db2ed_checkconfig_all - check the configuration of a partitioned DB2 database in a Veritas Storage Foundation for DB2 environment

SYNOPSIS

db2ed_checkconfig_all [ -I DB2INSTANCE ] -D DB2DATABASE [ -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_checkconfig_all command verifies various elements of the environment for a partitioned DB2 database.

The command attempts to use certain basic rules on DB2 settings, file system parameters, volume parameters, and layout options to verify how resilient and well configured a partitioned DB2 database environment is. The information provided is valid for the supplied DB2 database (DB2DATABASE). All output is sent to stdout.


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 configuration validation. Overrides the environment variable DB2DATABASE.
-h
Shows command usage.

EXAMPLE

This example shows how to check the DB2 configuration environment:

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

rah: primary monitoring process for db2ed_checkconfi is 10137


host1: Examining File System and DB2 Container attributes.

host1: Total of 4 containers over 1 file systems.
host1: All file systems are VxFS.
host1: Examining Quick I/O settings.
host1: Examining Cached Quick I/O settings.
host1: No file systems have Cached Quick I/O enabled.

host1: All file systems are VxFS Version 4 or higher layout.

host1: The database has:
host1: 4 SMS Containers
host1: 0 DMS File Containers
host1: 0 DMS Device Containers

host1: 4 containers are not configured to use Quick I/O.

host1: Examining DB2 container fragmentation.


host1: Could not examine DB2 container fragmentation.

host1: Examining File System tunable settings.

host1: Parameters for all VxFS file system used by PROD.
host1: Filesystem i/o parameters for /testdbhome
host1: read_pref_io = 65536
host1: read_nstream = 1
host1: read_unit_io = 65536
host1: write_pref_io = 65536
host1: write_nstream = 1
host1: write_unit_io = 65536
host1: pref_strength = 10
host1: buf_breakup_size = 1048576
host1: discovered_direct_iosz = 262144
host1: max_direct_iosz = 1048576
host1: default_indir_size = 8192
host1: qio_cache_enable = 0
host1: write_throttle = 0
host1: max_diskq = 1048576
host1: initial_extent_size = 8
host1: max_seqio_extent_size = 2048
host1: max_buf_data_size = 8192
host1: hsm_write_prealloc = 0
host1: read_ahead = 1
host1: inode_aging_size = 0
host1: inode_aging_count = 0
host1: fcl_maxalloc = 32537600
host1: fcl_keeptime = 0
host1: fcl_winterval = 3600
host1: oltp_load = 0

host1: Examining DB2 Volume layout and attributes.

host1: Data for database PROD is contained in one volume group.

host1: SFDB2 db2ed_checkconfig WARNING V-81-3418 File system /testdbh is not mirrored using VxVM.

host1: Examining Volume Group versions.
host1: Volume Group version for db2dg is:
host1: 140

host1: See the vxdg(1M) man page for more information on Volume Group

host1: Examining DB2 internal information.

host1: DB2 Version is 8.2.
host1: DB2COMM=tcpip

host1: Examining DB2 logging mode.

host1: The database has transaction logs in directory /testdbhome/db2inst2/NODE0000/SQL00001/SQLOGDIR/.
host1: SFDB2 db2ed_checkconfig WARNING V-81-3422 Transaction log directory is not mirrored using VxVM.

host1: The database is running in archivelog mode.

host1: The database has a user-exit defined for archiving logs.
host1: Cannot determine where logs are archived to.

host1: Examining DB2 Database Free Space.

host1: DB20000I  The SQL command completed successfully.

host1: Name                                 = SYSCATSPACE
host1: Type                                 = System managed space
host1: Total pages                          = 5567
host1: Used pages                           = 5567
host1: Free pages                           = Not applicable
host1: Page size (bytes)                    = 4096

host1: Name                                 = TEMPSPACE1
host1: Type                                 = System managed space
host1: Total pages                          = 1
host1: Used pages                           = 1
host1: Free pages                           = Not applicable
host1: Page size (bytes)                    = 4096

host1: Name                                 = USERSPACE1
host1: Type                                 = System managed space
host1: Total pages                          = 1
host1: Used pages                           = 1
host1: Free pages                           = Not applicable
host1: Page size (bytes)                    = 4096

host1: Tablespace name                            = SYSCATSPACE
host1: File system caching                      = Yes

host1: Tablespace name                            = TEMPSPACE1
host1: File system caching                      = Yes

host1: Tablespace name                            = USERSPACE1
host1: File system caching                      = Yes

host1: /opt/VRTSdb2ed/bin/db2ed_checkconfig  completed ok


host1: Examining File System and DB2 Container attributes.


host1: Total of 2 containers over 1 file systems.
host1: All file systems are VxFS.
host1: Examining Quick I/O settings.
host1: Examining Cached Quick I/O settings.
host1: No file systems have Cached Quick I/O enabled.

host1: All file systems are VxFS Version 4 or higher layout.

host1: The database has:
host1: 2 SMS Containers
host1: 0 DMS File Containers
host1: 0 DMS Device Containers

host1: 2 containers are not configured to use Quick I/O.

host1: Examining DB2 container fragmentation.


host1: Could not examine DB2 container fragmentation.

host1: Examining File System tunable settings.

host1: Parameters for all VxFS file systems used by PROD.
host1: Filesystem i/o parameters for /testdbhome
host1: read_pref_io = 65536
host1: read_nstream = 1
host1: read_unit_io = 65536
host1: write_pref_io = 65536
host1: write_nstream = 1
host1: write_unit_io = 65536
host1: pref_strength = 10
host1: buf_breakup_size = 1048576
host1: discovered_direct_iosz = 262144
host1: max_direct_iosz = 1048576
host1: default_indir_size = 8192
host1: qio_cache_enable = 0
host1: write_throttle = 0
host1: max_diskq = 1048576
host1: initial_extent_size = 8
host1: max_seqio_extent_size = 2048
host1: max_buf_data_size = 8192
host1: hsm_write_prealloc = 0
host1: read_ahead = 1
host1: inode_aging_size = 0
host1: inode_aging_count = 0
host1: fcl_maxalloc = 32537600
host1: fcl_keeptime = 0
host1: fcl_winterval = 3600
host1: oltp_load = 0

host1: Examining DB2 Volume layout and attributes.

host1: Data for database PROD is contained in one volume group.

host1: SFDB2 db2ed_checkconfig WARNING V-81-3418 File system /testdbh is not mirrored using VxVM.

host1: Examining Volume Group versions.
host1: Volume Group version for db2dg is:
host1: 140

host1: See the vxdg(1M) man page for more information on Volume Group

host1: Examining DB2 internal information.

host1: DB2 Version is 8.2.

host1: Examining DB2 logging mode.

host1: The database has transaction logs in directory /testdbhome/db2inst2/NODE0002/SQL00001/SQLOGDIR/.
host1: SFDB2 db2ed_checkconfig WARNING V-81-3422 Transaction log directory is not mirrored using VxVM.

host1: The database is running in archivelog mode.

host1: The database has a user-exit defined for archiving logs.
host1: Cannot determine where logs are archived to.

host1: Examining DB2 Database Free Space.

host1: DB20000I  The SQL command completed successfully.

host1: Name                                 = TEMPSPACE1
host1: Type                                 = System managed space
host1: Total pages                          = 1
host1: Used pages                           = 1
host1: Free pages                           = Not applicable
host1: Page size (bytes)                    = 4096

host1: Name                                 = USERSPACE1
host1: Type                                 = System managed space
host1: Total pages                          = 1
host1: Used pages                           = 1

host1: Free pages                           = Not applicable
host1: Page size (bytes)                    = 4096

host1: Tablespace name                            = TEMPSPACE1
host1: File system caching                      = Yes

host1: Tablespace name                            = USERSPACE1
host1: File system caching                      = Yes

host1: /opt/VRTSdb2ed/bin/db2ed_checkconfig  completed ok


NOTES

db2ed_checkconfig_all must be run as the DB2 instance owner in order to retrieve information from a partitioned DB2 database.

SEE ALSO

db2ed_saveconfig_all(1M), db2ed_update_all(1M), db2_edition(7)

Veritas Storage Foundation for DB2 Administrator's Guide

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