Skip to main content
Announcements
See what Drew Clarke has to say about the Qlik Talend Cloud launch! READ THE BLOG
cancel
Showing results for 
Search instead for 
Did you mean: 
marcioribeiro
Contributor II
Contributor II

Getting "RAC captured instances list does not include RAC instances configured in Oracle" error in standalone environment

Hi,

I´m trying to connect Qlik Replicate to Oracle standby database, however I´m getting following issue:

Failed to set stream position on context '2022-10-25T08:46:37'
RAC captured instances list does not include RAC instances configured in Oracle

I´m not using RAC environment. Both primary and standby Oracle databases are running in standalone. Standby is opened as Active DataGuard.

How to fix this issue ?

 

Qlik Replicate version is 

  • November 2020 (7.0.0.555)
Labels (1)
1 Solution

Accepted Solutions
Bill_Steinagle
Support
Support

Hi,

Thank you for the post to the forums. On  the Oracle Source Endpoint with the new 2022.5 version you can set the below internal parameter and the DEST ID on the Source to 1 if this is the Thread the Standby is using for Replicate to read from. Even though this says RAC this should be set for the Standby you are pointing Replicate to use.

add internal parameter capturedRacThreads and value should 1.

 

Thank you!

Bill

View solution in original post

3 Replies
SwathiPulagam
Support
Support

Hi @marcioribeiro ,

 

Can you share your task log keeping the source_capture in Trace and let the task fail again with the same error?

 

Thanks,

Swathi

Heinvandenheuvel
Specialist III
Specialist III

Did it ever work? What changed? Which Oracle version? PDB?

Hmm, your wording does not match the Replciate Userguide terminology. This might not be a supported configuration according to : "8.21 Using Oracle as a source" - "Supported Standby configurations". 

If it is supported you might want to first try again with the latest (May 2022 (2022.5.0.499)? ) version but this kind of code has been very stable (after PDB's were introduced 🙂

The messages comes from Replicate - The reptask_xxx.log file may already have detailed logging including the statement attempted in its error handling phase. If not, re-run with source_capture VERBOSE as @SwathiPulagam  suggested.

You also may want to check LOG_ARCHIVE_DEST settings and execute the query :  select thread#, instance from v$thread order by thread# ASC

See what it tells you.

hth,

Hein.

Bill_Steinagle
Support
Support

Hi,

Thank you for the post to the forums. On  the Oracle Source Endpoint with the new 2022.5 version you can set the below internal parameter and the DEST ID on the Source to 1 if this is the Thread the Standby is using for Replicate to read from. Even though this says RAC this should be set for the Standby you are pointing Replicate to use.

add internal parameter capturedRacThreads and value should 1.

 

Thank you!

Bill