The concatenation of the smallfile relative datafile number (FFF) and
the smallfile datablock number (BBBBBB) results in a new construct called an encoded block
number. Therefore, the format for a bigfile ROWID consists of only three parts:
OOOOOO LLLLLLLLL RRR
Table 16-3 defines each part of a bigfile ROWID.
DBMS_ROWID and Bigfile Tablespaces
Because two different types of tablespaces can now coexist in the database along with their
corresponding ROWID formats, some changes have occurred to the DBMS_ROWID package.
The names of the procedures in the DBMS_ROWID package are the same and operate as
before, except for a new parameter, TS_TYPE_IN, which identifies the type of tablespace to which
a particular row belongs: TS_TYPE_IN can be either BIGFILE or SMALLFILE.
Smallfile ROWID Component Definition
OOOOOO Data object number identifying the database segment
(such as table, index, or materialized view)
FFF Relative datafile number within the tablespace of the
datafile that contains the row
BBBBBB The data block containing the row, relative to the datafile
RRR Slot number, or row number, of the row inside a block
TABLE 16-2 Smallfile ROWID Format
Bigfile ROWID Component Definition
OOOOOO Data object number identifying the database segment
(such as table, index, or materialized view)
LLLLLLLLL Encoded block number, relative to the tablespace and
unique within the tablespace
RRR Slot number, or row number, of the row inside a block
TABLE 16-3 Bigfile ROWID Format
548 Oracle Database 11g DBA Handbook
For an example of extracting ROWIDs from a table in a bigfile tablespace, we have a table
called OE.
Pages:
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820