Ask Your Question
0

JDBC_601 - Could not find a valid LogMiner dictionary: no dictionary found before SCN

asked 2020-09-30 20:28:07 -0500

sudhiriyer gravatar image

I am testing StreamSets for a POC with Oracle 11g as origin. Each time I stop my Pipeline and restart, I run into the following error :

Caused by: com.streamsets.pipeline.api.StageException: JDBC_601 - Could not find a valid LogMiner dictionary: no dictionary found before SCN 9297297106 at com.streamsets.pipeline.stage.origin.jdbc.cdc.oracle.LogMinerSession.findDictionary(LogMinerSession.java:928) at com.streamsets.pipeline.stage.origin.jdbc.cdc.oracle.LogMinerSession.preloadDictionary(LogMinerSession.java:673) at com.streamsets.pipeline.stage.origin.jdbc.cdc.oracle.LogMinerSession.preloadDictionary(LogMinerSession.java:662) at com.streamsets.pipeline.stage.origin.jdbc.cdc.oracle.OracleCDCSource.startLogMiner(OracleCDCSource.java:460)

The SCN number varies in every failed started after it had a sucessfull run for sometime. As this just a POC, I don't care what SCN it starts from, I would just want the pipeline to start. How do I make StreamSets not persist the SCN number for a new start? I tried the option by specifying the current SCN number from v$database. ANd yet StreamSets would want to look for an old SCN.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2020-10-01 14:50:29 -0500

KateF gravatar image

When you start, try choosing "Reset Origin and Start" instead of a plain start. This will cause the pipeline to start from the change as specified in the current configuration instead of whatever is saved as the stopping point from the last run.

edit flag offensive delete link more
Login/Signup to Answer

Question Tools

2 followers

Stats

Asked: 2020-09-30 20:28:07 -0500

Seen: 78 times

Last updated: Oct 01