Changing from LogMiner to LogReader

[gchaika]

We currently replicate from Oracle to Oracle (both running in AWS/RDS) using LogMiner but want to switch to Replicate Log Reader.

The task currently works in LogMiner but when we try to switch to Log Reader it throws errors about not being able to create a directory name.  

Cannot create Oracle directory name 'ATTUREP_36091813AWS_PSTEST' with path '/rdsdbdata/db/CORCSTST_A/onlinelog'

OCI error 'ORA-04088: error during execution of trigger 'RDSADMIN.RDS_DDL_TRIGGER2'

ORA-00604: error occurred at recursive SQL level 1

ORA-20900: Invalid path used for directory: /rdsdbdata/db/CORCSTST_A/onlinelog

ORA-06512: at "SYS.RDS_SYS_TRIGGER_UTIL107", line 782

ORA-06512: at line 1

ORA-06512: at "SYS.RDS_SYS_TRIGGER_UTIL2", line 285

ORA-06512: at line 1

ORA-06512: at "RDSADMIN.RDSADMIN_TRIGGER_UTIL2", line 27

ORA-06512: at line 1

ORA-06512: at line 33'

What permissions do I need to grant this user? Again, this works just fine using LogMiner.

[john_wang]

Hello @gchaika ,

You’re correct — the required permissions for LogReader differ from those for LogMiner. Please refer to “Access privileges when using Replicate Log Reader to access the redo logs” for details.

For additional information on directory usage, see “What’s the usage of Oracle directories in Replicate Oracle source.”

By the way, I’m not entirely sure how the cutover from LogMiner to LogReader was performed. Simply changing the option in the endpoint and then selecting Resume is not supported, as the internal format and stream position differ between these two access methods.

The supported restart options are:

1. Start from SCN
2. Start from Timestamp
3. Reload task

Hope this helps.

John.

[gchaika]

Thanks John.  No we did not try to resume the task and did try a FULL reload once we changed the source.  That is when we encountered the errors.  I am not the DBA on the source side, but I am on the destination side. I'm working with a 3rd party vendor to get this to work.

[john_wang]

Thank you for the update and support! @gchaika 

[gchaika]

I tried this again this morning, even with DBA granted to our Replicate user it still spits out errors about creating a directory in AWS/RDS.  It does push through these errors and starts to process the full RELOAD, but it still spits out this error every few minutes. So it appears to be half working but I do not get a good feeling about this error.

ERROR:

ORA-00604: error occurred at recursive SQL level 1
ORA-20900: Invalid path used for directory: /rdsdbdata/db/CORCSTST_A/onlinelog
ORA-06512: at "SYS.RDS_SYS_TRIGGER_UTIL107", line 782
ORA-06512: at line 1
ORA-06512: at "SYS.RDS_SYS_TRIGGER_UTIL2", line 285
ORA-06512: at line 1
ORA-06512: at "RDSADMIN.RDSADMIN_TRIGGER_UTIL2", line 27
ORA-06512: at line 1
ORA-06512: at line 33' [1022307]  (oradcdc_bfilectx.c:164)
00000400: 2026-04-03T09:48:17 [SOURCE_CAPTURE  ]E:  Cannot create Oracle directory name 'ATTUREP_36091813AWS_PSTEST' with path '/rdsdbdata/db/CORCSTST_A/onlinelog' [-1]  (oradcdc_bfilectx.c:165)
00000400: 2026-04-03T09:48:17 [SOURCE_CAPTURE  ]I:  Failed to open Redo log '/rdsdbdata/db/CORCSTST_A/onlinelog/o1_mf_13_nw1vczb2_.log' (sequence 4068, thread 1), retry till Redo log with this sequence could be opened successfully  (oradcdc_redo.c:821)

[john_wang]

Hello @gchaika ,

Please check the User Guide relative chapter for the RDS setup, it's different than On-Premise Oracle. (I'm pasting it here)

Using Replicate Log Reader to access the redo logs

The following steps are relevant only when using Replicate Log Reader to access the redo logs.

Create directories for online and archived logs

Before you can use Replicate Log Reader, you need to create directories for the online and archived logs.

To create the directories, run the following commands:

exec rdsadmin.rdsadmin_master_util.create_archivelog_dir;

exec rdsadmin.rdsadmin_master_util.create_onlinelog_dir;

To remove the directories (if there are no ongoing replication tasks), run the following commands:

exec rdsadmin.rdsadmin_master_util.drop_archivelog_dir;

exec rdsadmin.rdsadmin_master_util.drop_onlinelog_dir;

Good luck,

John.