How do we configure Replicate Log Reader on Qlik Replicate when there is no ASM Build for Archive Log

[pavan_peri]

Hi Team,

How do we configure Replicate Log Reader on Qlik Replicate when there is no ASM Build for Archive Log. In our case we have enabled Archive Log Mode and capturing Logs for Qlik to read and process for CDC.

Guide us the steps to configure "Replicate Log Reader" Option for better CDC

[pavan_peri]

Hi Hein,

To answer you point:

I guess that's deliberate? RAC? Leftover? -- Our Oracle is an Enterprise Database but not RAC. This Json we got it when we created a task and exported it. Haven't modified any. (Original Export of Task as Json)

Maybe there is something odd about the source DB, do you have an other one to connect to , just an Express edition if you have to? -- Migration & Replication works fine when LogMiner is selected as an option for which we have attached the logs for reference. As there is no ASM we have left all options which you have also acknowledged as correct.

Next time, maybe run with LOGGING SOURCE_CAPTURE VERBOSE to hopefully get relevant details. Kill after first errors. -- We will try and test this and share the logs as suggested

Finally, but I suppose that has effectively already happened while trying. Start a fresh endpoint and task from scratch, using simple short names. Same thing? -- Tried all these as couple of TEST Tasks and played with it. No use when used "Replicate Log Reader" and work fine when selected "LogMiner"

Hope this helps

[pavan_peri]

Hi Hein,

The version what we use is "V2023.5.0.152". Hope there are no issues with this version?

[pavan_peri]

Hi Hein,

Attached are the logs with SOURCE_CAPTURE VERBOSE and Diagnostics Pack for reference

[Heinvandenheuvel]

>>> Attached are the logs with SOURCE_CAPTURE VERBOSE and Diagnostics Pack for reference

Thanks. That helps.

[SOURCE_CAPTURE ]V: Going to retrieve online REDO log with sequence '30' RLID '1135785205', thread '1' (ora
[SOURCE_CAPTURE ]T: Going to open Redo Log with original name '+DATA_A/oradata/gwdtst01/log02a.dbf', thread
[SOURCE_CAPTURE ]T: Connect ASM: Connecting to Oracle ASM server (user '', Redo thread '1' OCI Thread '0' o
[SOURCE_CAPTURE ]T: OCI error 'ORA-12560: TNS:protocol adapter error' [1022307] (oradcdc_redoutil.c:518)

So while you topic text mentions that the ARCHIVE is not on ASM, the REDO actually is on ASM as the +DATA indicates.   WTF!?   So give it proper ASM access!   Or maybe some renaming must take place? : Use path as it appears in the database Replace path prefix

I suppose you could try switch your task to 'Use archived redo logs only' but that doesn't sit right to me, and you would likely not like the LATENCY that you get with that.

Hein.

[john_wang]

Hello @pavan_peri ,

Besides @Heinvandenheuvel comment, I'd like to remind you that you are running an incompatible Oracle client and Oracle server versions. See the task log file lines #37-39:

2023-10-04T06:39:06 [SOURCE_CAPTURE ]I: Oracle source database version is 11.2.0.4.0
2023-10-04T06:39:06 [SOURCE_CAPTURE ]I: Oracle Client version: 21.10.0.0.0
2023-10-04T06:39:06 [SOURCE_CAPTURE ]I: Oracle compatibility version is 11.2.0.4.0

Oracle does not support these versions combination:

Oracle client versions 12.2/18c/19c are recommended.

Maybe this is not the root cause of the error message, however an uncertified version may lead to unpredictable results.

Regards,

John.

[pavan_peri]

Hi Hein,

Thanks a lot for your inputs and observations. We are internally checking with DBA to get back to us with possible output so that can test and update you.

[pavan_peri]

Hi John,

Thanks a lot for your inputs. Will check with client and see what best can be done. Will keep you posted on the same.