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 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

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.

To check the database configuration environment

VRTSodm              5.0.31.5.%20090524 Veritas Oracle Disk Manager
Examining file system attributes. 
All file systems are VxFS. 
Examining Quick I/O settings.

0 files are configured to use Quick I/O files.
It appears that your system is ODM enabled.
0 Quick I/O files should be converted to regular
files to use ODM feature.
Examining Cached Quick I/O settings. 
No file systems have Cached Quick I/O enabled. 
Examining File System tunable settings.

Parameters for all VxFS file systems used by FLAS11r1.
Filesystem i/o parameters for /snap_data11r1
read_pref_io = 2097152
read_nstream = 1
read_unit_io = 2097152
write_pref_io = 2097152
write_nstream = 1
write_unit_io = 2097152
pref_strength = 10
buf_breakup_size = 2097152
discovered_direct_iosz = 262144
max_direct_iosz = 1048576
default_indir_size = 8192
qio_cache_enable = 0
write_throttle = 0
max_diskq = 33554432
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 = 317750272
fcl_keeptime = 0
fcl_winterval = 3600
fcl_ointerval = 600
oltp_load = 0
Examining Oracle volume and file system layout.

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

Oracle Version is 11.1.0.6.0.
Control file /snap_data11r1/FLAS11r1/control01.ctl is on file system
/snap_data11r1.
SFORA dbed_checkconfig WARNING V-81-999 Control file is on a VxVM 
volume set

Control file /snap_data11r1/FLAS11r1/control02.ctl is on file system
/snap_data11r1.
SFORA dbed_checkconfig WARNING V-81-999 Control file is on a VxVM 
volume set

Control file /snap_data11r1/FLAS11r1/control03.ctl is on file system
/snap_data11r1.
SFORA dbed_checkconfig WARNING V-81-999 Control file is on a VxVM 
volume set
Total of 3 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 1009 datafiles are configured to auto extend. 
Total of 1015 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

VRTSodm               5.0.31.5.%20090524 Veritas Oracle Disk Manager 
Examining file system attributes.

All file systems are VxFS.

Examining Quick I/O settings.

0 files are configured to use Quick I/O files.
It appears that your system is ODM enabled.

Examining Cached Quick I/O settings.

No file systems have Cached Quick I/O enabled.

Examining File System tunable settings.

Parameters for all VxFS file systems used by FLAS11r1.
Filesystem i/o parameters for /snap_data11r1
read_pref_io = 2097152
read_nstream = 1
read_unit_io = 2097152
write_pref_io = 2097152
write_nstream = 1
write_unit_io = 2097152
pref_strength = 10
buf_breakup_size = 2097152
discovered_direct_iosz = 262144
max_direct_iosz = 1048576
default_indir_size = 8192
qio_cache_enable = 0
write_throttle = 0
max_diskq = 33554432
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 = 317750272
fcl_keeptime = 0
fcl_winterval = 3600
fcl_ointerval = 600
oltp_load = 0

Examining Oracle volume and file system layout.

Data for database FLAS11r1 is contained in one volume group.

Examining Oracle internal information.

Oracle Version is 11.1.0.6.0.
Control file /snap_data11r1/FLAS11r1/control01.ctl is on file system
/snap_data11r1.
SFORA dbed_checkconfig WARNING V-81-999 Control file is on a 
VxVM volume set

Control file /snap_data11r1/FLAS11r1/control02.ctl is on file system 
/snap_data11r1.
SFORA dbed_checkconfig WARNING V-81-999 Control file is on a 
VxVM volume set

Control file /snap_data11r1/FLAS11r1/control03.ctl is on file system
/snap_data11r1.
SFORA dbed_checkconfig WARNING V-81-999 Control file is on a 
VxVM volume set

Total of 3 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 1009 datafiles are configured to auto extend.
The following datafiles are not configured to autoextend:
/snap_data11r1/FLAS11r1/test_big.dbf
/snap_data11r1/FLAS11r1/undotbs02.dbf
/snap_data11r1/FLAS11r1/tde_tbs1.dbf
/snap_data11r1/FLAS11r1/tde_tbs2.dbf
/snap_data11r1/FLAS11r1/16k_file.dbf
/snap_data11r1/FLAS11r1/32k_file.dbf

Total of 1015 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