ROWID_BLOCK_NUMBER function.
Using DBVERIFY with Bigfile Tablespaces
The DBVERIFY utility, available since Oracle version 7.3, checks the logical integrity of an offline
database. The files can only be datafiles; DBVERIFY cannot analyze online redo log files or archived
redo log files. In previous versions of Oracle, DBVERIFY could analyze all of a tablespace??™s datafiles
in parallel by spawning multiple DBVERIFY commands. However, because a bigfile tablespace has
only one datafile, DBVERIFY has been enhanced to analyze parts of a bigfile tablespace??™s datafiles
in parallel.
Using the dbv command at the Unix or Windows prompt, you can use two new parameters:
START and END, representing the first and last block, respectively, of the file to analyze. As a
result, you need to know how many blocks are in the bigfile tablespace??™s datafile; the dynamic
performance view V$DATAFILE comes to the rescue, as you can see in the following example:
SQL> select file#, blocks, name from v$datafile;
FILE# BLOCKS NAME
---------- ---------- --------------------------------------------------
1 96000 +DATA/dw/datafile/system.256.630244579
2 109168 +DATA/dw/datafile/sysaux.257.630244581
3 7680 +DATA/dw/datafile/undotbs1.258.630244583
4 640 +DATA/dw/datafile/users.259.632441707
5 12800 +DATA/dw/datafile/example.265.630244801
6 64000 +DATA/dw/datafile/users_crypt.267.630456963
7 12800 +DATA/dw/datafile/inet_star.268.632004213
8 6400 +DATA/dw/datafile/inet_intl_star.
Pages:
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823