Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Qlik Exam QREP Topic 1 Question 20 Discussion

Actual exam question for Qlik's QREP exam
Question #: 20
Topic #: 1
[All QREP Questions]

When running a task in Qlik Replicate (From Oracle to MS SQL), the following error message appears: Failed adding supplemental logging for table "Table name" Which must be done to fix this error?

Show Suggested Answer Hide Answer
Suggested Answer: C

The ODBC drivers in Qlik Replicate are located in the Replicatebin directory. This is supported by the documentation from Qlik, which indicates that when installing required clients such as the Microsoft ODBC Driver for SQL Server, the working directory should be changed to /bin1. Additionally, for other prerequisites involving driver locations, the instructions also refer to changing the working directory to <Replicate-Install-Dir>/bin23. This consistent reference to the bin directory across different parts of the Qlik Replicate documentation verifies that the ODBC drivers are indeed located in the Replicatebin directory.


by Olive at Mar 04, 2025, 08:52 AM

Limited Time Offer

25%

Off

Get Premium QREP Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Janessa
2 months ago
The answer is clearly C, but I'm just wondering if the Oracle DBA is going to be as helpful as a hungry bear in a beehive. Maybe I should just enable the logging and run for the hills.
upvoted 0 times
Ashley
21 days ago
I agree, enabling supplemental logging seems like the best solution.
upvoted 0 times
...
Tula
28 days ago
C) Enable supplemental logging
upvoted 0 times
...
Mabel
1 months ago
A) Contact the Oracle DBA
upvoted 0 times
...
...
Vashti
2 months ago
C, no question. Though I do have to wonder, who came up with the term 'supplemental logging' anyway? Sounds like something straight out of a bad sci-fi movie.
upvoted 0 times
Nickolas
18 days ago
C) Enable supplemental logging
upvoted 0 times
...
Jamey
20 days ago
B) Check the permission on the target endpoint
upvoted 0 times
...
Shakira
21 days ago
A) Contact the Oracle DBA
upvoted 0 times
...
...
Nadine
2 months ago
C is the way to go, no doubt. Though I'm tempted to go with D just to see what kind of chaos that would unleash. Where's the fun in taking the easy route, am I right?
upvoted 0 times
...
Coral
2 months ago
Hmm, this one's a tricky one. I'd go with C, but maybe I should also contact the Oracle DBA just to be safe. You know, cover all my bases.
upvoted 0 times
Lawanda
9 days ago
Definitely, let's cover all our bases.
upvoted 0 times
...
Jacquline
21 days ago
Yeah, better safe than sorry.
upvoted 0 times
...
Lenna
1 months ago
I agree, but it wouldn't hurt to contact the Oracle DBA just in case.
upvoted 0 times
...
Billy
2 months ago
I think enabling supplemental logging is the way to go.
upvoted 0 times
...
...
Daron
2 months ago
Ah, the old Oracle to SQL Server migration dance! Always a fun one. I'd say go with C - enable that supplemental logging and get this party started!
upvoted 0 times
Alyssa
2 months ago
I think contacting the Oracle DBA might also be a good idea just to cover all bases.
upvoted 0 times
...
Tish
2 months ago
I agree, enabling supplemental logging should do the trick.
upvoted 0 times
...
...
Dominga
3 months ago
I'm not sure, but I think contacting the Oracle DBA could also help.
upvoted 0 times
...
Micheline
3 months ago
I agree with Noah, enabling supplemental logging should fix the error.
upvoted 0 times
...
Noah
3 months ago
I think the answer is C) Enable supplemental logging.
upvoted 0 times
...

Save Cancel