10g log miner's CONTINUOUS_MINE working on RAC?

We have a 10.2.0.3 two-node rac setup on windows.

It would appear that the log miner's CONTINUOUS_MINE option does not work on 
Oracle RAC.

Searching the Oracle 9 documentation I found a statement that said it did not 
work.

Searching the Oracle 10 documentation I did not find the statement (I suspect 
it got lost in the re-write).

I setup my log miner as follows:

sys.DBMS_LOGMNR.add_logfile (
                options => sys.dbms_logmnr.new,
                logfilename => 'G:\ORADATA\WINRACDB\REDO01.LOG')

sys.DBMS_LOGMNR.add_logfile (
                options => sys.dbms_logmnr.addfile,
                logfilename => 'G:\ORADATA\WINRACDB\REDO02.LOG')

sys.DBMS_LOGMNR.add_logfile (
                options => sys.dbms_logmnr. addfile,
                logfilename => 'G:\ORADATA\WINRACDB\REDO03.LOG')

sys.DBMS_LOGMNR.add_logfile (
                options => sys.dbms_logmnr. addfile,
                logfilename => 'G:\ORADATA\WINRACDB\REDO04.LOG')

Then I start logging with: 

SYS.DBMS_LOGMNR.START_LOGMNR( 
    STARTSCN => 100462200,
    OPTIONS => 
        SYS.DBMS_LOGMNR.DICT_FROM_ONLINE_CATALOG+
        SYS.DBMS_LOGMNR.SKIP_CORRUPTION+
        SYS.DBMS_LOGMNR.COMMITTED_DATA_ONLY )

And I see all of my changes:

If I then call:

SYS.DBMS_LOGMNR.START_LOGMNR( 
    STARTSCN => 100462200,
    OPTIONS => 
        SYS.DBMS_LOGMNR.CONTINUOUS_MINE+
        SYS.DBMS_LOGMNR.DICT_FROM_ONLINE_CATALOG+
        SYS.DBMS_LOGMNR.SKIP_CORRUPTION+
        SYS.DBMS_LOGMNR.COMMITTED_DATA_ONLY )

My changes disappear and the only entries I see have SEG_OWNER's of null, SYS, 
and SYSMAN.

Is there some way I can get CONTINUOUS_MINE to work the same way as it does on 
a non-RAC system?

Thanks.
Guang
--
http://www.freelists.org/webpage/oracle-l


Other related posts:

  • » 10g log miner's CONTINUOUS_MINE working on RAC?