The following restrictions exist for the LogMiner for Rdb
    feature:

    o  Temporary tables cannot be extracted. Modifications to
       temporary tables are not written to the after-image journal
       file and, therefore, are not available to LogMiner for Rdb.

    o  Optimized after-image journal files cannot be used as input
       to the LogMiner for Rdb. Information needed by the RMU Unload
       After_Journal command is removed by the optimization process.

    o  Records removed from tables using the SQL TRUNCATE TABLE
       statement are not extracted. The SQL TRUNCATE TABLE statement
       does not journal each individual data record being removed
       from the database.

    o  Records removed by dropping tables using the SQL DROP TABLE
       statement are not extracted. The SQL DROP TABLE statement does
       not journal each individual data record being removed from the
       database.

    o  Tables that use the vertical record partitioning (VRP) feature
       cannot be extracted using LogMiner for Rdb. LogMiner software
       currently does not detect these tables. A future release
       of Oracle Rdb will detect and reject access to vertically
       partitioned tables.

    o  Segmented string data (BLOB) cannot be extracted using
       LogMiner for Rdb. Because the segmented string data is
       related to the base table row by means of a database key,
       there is no convenient way to determine what data to extract.
       Additionally, the data type of an extracted column is changed
       from LIST OF BYTE VARYING to BIGINT. This column contains the
       DBKEY of the original BLOB data. Therefore, the contents of
       this column should be considered unreliable.

    o  COMPUTED BY columns in a table are not extracted. These
       columns are not stored in the after-image journal file.

    o  VARCHAR fields are not space padded in the output file. The
       VARCHAR data type is extracted as a 2-byte count field and a
       fixed-length data field. The 2-byte count field indicates the
       number of valid characters in the fixed-length data field. Any
       additional contents in the data field are unpredictable.

    o  You cannot extract changes to a table when the table
       definition is changed within an after-image journal file.
       Data definition language (DDL) changes to a table are not
       allowed within an .aij file being extracted. All records in an
       .aij file must be the current record version. If you are going
       to perform DDL operations on tables that you wish to extract
       using the LogMiner for Rdb, you should:

       1. Back up your after-image journal files.

       2. Extract the .aij files using the RMU Unload After_Journal
          command.

       3. Make the DDL changes.

    o  Do not use the OpenVMS Alpha High Performance Sort/Merge
       utility (selected by defining the logical name SORTSHR to
       SYS$SHARE:HYPERSORT) when using LogMiner for Rdb. HYPERSORT
       supports only a subset of the library sort routines that
       LogMiner requires. Make sure that the SORTSHR logical name
       is not defined to HYPERSORT.