Home
CONTINUOUS_MINE option is desupported in DBMS_LOGMNR.START_LOGMNR
Description
As of Oracle Database 12.2 and later (including 19c), the CONTINUOUS_MINE option is desupported in the DBMS_LOGMNR.START_LOGMNR procedure. This option was previously used to enable continuous mining of redo logs, but it is no longer supported and will cause runtime errors if used.
Oracle recommends using supported alternatives such as DICT_FROM_ONLINE_CATALOG, NO_ROWID_IN_STMT, or COMMITTED_DATA_ONLY depending on your use case.
Review your usage of DBMS_LOGMNR.START_LOGMNR and remove any reference to CONTINUOUS_MINE to ensure compatibility with current and future Oracle versions.
Key Benefits
- Compliance: Prevents runtime errors in Oracle 19c and future versions by removing desupported options.
- Stability: Ensures log mining procedures run with supported configurations.
- Maintainability: Aligns your PL/SQL code with current Oracle standards and avoids deprecated features.
Non-compliant Code Example
BEGIN
DBMS_LOGMNR.START_LOGMNR(
STARTSCN => 123456,
OPTIONS => DBMS_LOGMNR.CONTINUOUS_MINE --Non compliant code (CONTINUOUS_MINE option is desupported in DBMS_LOGMNR.START_LOGMNR)
);
END;
Compliant Code Example
BEGIN
DBMS_LOGMNR.START_LOGMNR(
STARTSCN => 123456,
OPTIONS => DBMS_LOGMNR.DICT_FROM_ONLINE_CATALOG + DBMS_LOGMNR.NO_ROWID_IN_STMT --Compliant code
);
END;
