The following are requirements for the source and mining database, the data dictionary, and the redo log files that LogMiner will mine:
Both the source database and the mining database must be running on the same hardware platform.
The mining database can be the same as, or completely separate from, the source database.
The mining database must run the same release or a later release of the Oracle Database software as the source database.
The mining database must use the same character set (or a superset of the character set) used by the source database.
The dictionary must be produced by the same source database that generates the redo log files that LogMiner will analyze.
Must be produced by the same source database.
Must be associated with the same database
Must be from a release 8.0 or later Oracle Database. However, several of the LogMiner features introduced as of release 9.0.1 work only with redo log files produced on an Oracle9i or later database. See "Supported Databases and Redo Log File Versions".
LogMiner does not allow you to mix redo log files from different databases or to use a dictionary from a different database than the one that generated the redo log files to be analyzed.
You must enable supplemental logging before generating log files that will be analyzed by LogMiner.
When you enable supplemental logging, additional information is recorded in the redo stream that is needed to make the information in the redo log files useful to you. Therefore, at the very least, you must enable minimal supplemental logging, as the following SQL statement shows:
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
To determine whether supplemental logging is enabled, query the
V$DATABASE view, as the following SQL statement shows:
SELECT SUPPLEMENTAL_LOG_DATA_MIN FROM V$DATABASE;
If the query returns a value of
IMPLICIT, then minimal supplemental logging is enabled. See "Supplemental Logging" for complete information about supplemental logging.