Command Syntax
dbv { FILE=filename | {START|END}=block | BLOCKSIZE=integer | LOGFILE=filename | FEEDBACK=integer | PARFILE=filename | HELP={Y|N} }
Examples
dbv file=system01.dbf dbv file=system01.dbf blocksize=8192 feedback=1000
To validate the physical integrity of an Oracle database's data files on demand, you can use the DBVERIFY utility. DBVERIFY can validate data files of an open or closed database as well as data file backups.
DBVERIFY is a simple command-line utility that accepts a few runtime parameters to control its behavior.
The FILE parameter indicates the name of a data file or data file backup.
When the target data file's block size is not 2048 bytes (2K), use the BLOCKSIZE parameter to indicate the proper data block size, in bytes; otherwise, DBVERIFY returns an error.
By default, DBVERIFY analyzes all data blocks of the target data file. Optionally, you can use the START and END parameters to indicate a range of data blocks to validate.
By default, DBVERIFY prints its log to your terminal. Optionally, you can record output in a file by indicating a filename with the LOGFILE parameter.
By default, DBVERIFY does not display any type of feedback as it validates the blocks of a data file. Optionally, you can indicate the FEEDBACK parameter to display a dot every n number of data blocks that DBVERIFY checks. This feature is useful to see DBVERIFY progress through the data blocks of a large data file.
The PARFILE parameter indicates the name of a parameter file that contains one or more runtime parameters.
The HELP parameter indicates that you want to display help for the DBVERIFY utility – use this parameter without any other runtime parameters.
Understanding DBVERIFY Output
After DBVERIFY finishes validating a data file, it outputs a table of its results. The key results of interest are:
Total Pages Failing (Data)
Total Pages Failing (Index)
Total Pages Marked Corrupt
If one or more of the statistics above is non-zero for a data file, contact Oracle Corporation's technical support staff for aid in correcting your problem. If any of these statistics is non-zero for a backup copy of a data file, the backup media might be faulty rather than the source data file. Immediately make a new data file backup and then verify it.
Hopes this helps
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.