Checking the database configuration environment using dbed_checkconfig
Prev Using Veritas Extension for Oracle Disk Manager Next

Checking the database configuration environment using dbed_checkconfig

You can use the dbed_checkconfig command to verify and report on the database environment from the command line.

Before checking the configuration environment, the following conditions must be met:

Prerequisites

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

Prerequisites

  • You must be logged on as the instance owner (typically, the user ID db2inst1).

Usage notes

  • The dbed_checkconfig command is used to verify various elements of the database environment. The utility attempts to use certain basic rules on database settings, file system and volume parameters and layout options to verify how resilient and well configured a configuration is. The information provided is valid for the supplied database.

  • See the dbed_checkconfig(1M) manual page.

Usage notes

  • The db2ed_checkconfig command is used to verify various elements of the database environment. The utility attempts to use certain basic rules on database settings, file system and volume parameters and layout options to verify how resilient and well configured a configuration is. The information provided is valid for the supplied database.

  • For multiple partitions, use the db2ed_checkconfig_all command. db2ed_checkconfig_all checks the configuration for a partitioned DB2 database.

  • See the db2ed_checkconfig_all(1M) manual page.

  • See the db2ed_checkconfig(1M) manual page.

To check the database configuration environment

Examining file system attributes.
All file systems are VxFS.
All file systems are VxFS Version 4 or higher layout.
All file systems have the same version layout (version 6).
Examining Quick I/O settings.

All datafiles are Quick I/O files.
Examining Cached Quick I/O settings.
No file systems have Cached Quick I/O enabled.
Examining datafiles fragmentation.

5 files are fragmented.
Examining File System tunable settings.

Parameters for all VxFS file systems used by PROD.
Filesystem i/o parameters for /prod_db
read_pref_io = 65536
read_nstream = 1
read_unit_io = 65536
write_pref_io = 65536
write_nstream = 1
write_unit_io = 65536
pref_strength = 10
buf_breakup_size = 1048576
discovered_direct_iosz = 262144
max_direct_iosz = 1048576
default_indir_size = 8192
qio_cache_enable = 0
write_throttle = 0
max_diskq = 1048576
initial_extent_size = 8
max_seqio_extent_size = 2048
max_buf_data_size = 8192
hsm_write_prealloc = 0
read_ahead = 1
inode_aging_size = 0
inode_aging_count = 0
fcl_maxalloc = 65075200
fcl_keeptime = 0
fcl_winterval = 3600
Examining Oracle volume and file system layout.

Data for database PROD is contained in one volume group.
Examining Oracle internal information.

Oracle Version is 9.2.0.4.0.
Control file /prod_db/control1 is on file system /prod_db.
Control file /prod_db/control2 is on file system /prod_db.
Total of 2 control files over 1 file systems.
SFORA dbed_checkconfig WARNING V-81-3122: Control files are not
spread over multiple file systems. Spread control files over multiple
file systems for better redundancy.
Examining Oracle automatic extension of datafiles.

Total of 0 datafiles are configured to auto extend.
Total of 9 datafiles are defined to the database.
Examining Oracle log modes.

The database is running in archivelog mode.
The database is running in automatic log archiving mode.

To check the database configuration environment and not update the repository

Examining file system attributes.
All file systems are VxFS.
All file systems are VxFS Version 4 or higher layout.
All file systems have the same version layout (version 6).
Examining Quick I/O settings.

All datafiles are Quick I/O files.

Examining Cached Quick I/O settings.

No file systems have Cached Quick I/O enabled.
Examining datafiles fragmentation.

5 files are fragmented.
/prod_db/index02.dbf is fragmented.
/prod_db/rolbak1.dbf is highly fragmented.
/prod_db/system.dbf is highly fragmented.
/prod_db/data01.dbf is highly fragmented.
/prod_db/data02.dbf is highly fragmented.
Examining File System tunable settings.

Parameters for all VxFS file systems used by PROD.
Filesystem i/o parameters for /prod_db
read_pref_io = 65536

read_nstream = 1
read_unit_io = 65536
write_pref_io = 65536
write_nstream = 1
write_unit_io = 65536
pref_strength = 10
buf_breakup_size = 1048576
discovered_direct_iosz = 262144
max_direct_iosz = 1048576
default_indir_size = 8192
qio_cache_enable = 0
write_throttle = 0
max_diskq = 1048576
initial_extent_size = 8
max_seqio_extent_size = 2048
max_buf_data_size = 8192
hsm_write_prealloc = 0
read_ahead = 1
inode_aging_size = 0
inode_aging_count = 0
fcl_maxalloc = 65075200
fcl_keeptime = 0
fcl_winterval = 3600
Examining Oracle volume and file system layout.

Data for database PROD is contained in one volume group.

Examining Oracle internal information.

Oracle Version is 9.2.0.4.0.

Control file /prod_db/control1 is on file system /prod_db.

Control file /prod_db/control2 is on file system /prod_db.

Total of 2 control files over 1 file systems.

SFORA dbed_checkconfig WARNING V-81-3122: Control files are not spread
over multiple file systems. Spread control files over multiple file
systems for better redundancy.
Examining Oracle automatic extension of datafiles.

Total of 0 datafiles are configured to auto extend.
The following datafiles are not configured to autoextend:
/prod_db/deflt.dbf
/prod_db/temp.dbf
/prod_db/index02.dbf
/prod_db/index01.dbf
/prod_db/data1.dbf
/prod_db/rolbak1.dbf
/prod_db/system.dbf
/prod_db/data01.dbf
/prod_db/data02.dbf

Total of 9 datafiles are defined to the database.

Examining Oracle log modes.

The database is running in archivelog mode.

The database is running in automatic log archiving mode.
Prev Up Next
Verifying that Oracle Disk Manager is configured Home Disabling the Oracle Disk Manager feature