MENU
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?
34 comments · newest first
WH
Whitney
10 months ago
Checking permissions might help too, but C is key.
TA
Tanja
10 months ago
Wait, why would you need supplemental logging for that?
KA
Kasandra
10 months ago
You definitely need to enable supplemental logging.
LA
Latrice
10 months ago
I thought contacting the DBA was the first step?
CA
Carey
11 months ago
I agree, C is the right choice!
CA
Carey
11 months ago
I definitely think enabling supplemental logging is key here. It seems like the most direct solution to that error message.
MA
Ma
11 months ago
I recall a practice question where we had to check permissions, but I can't remember if it was for the source or target. This is tricky!
RA
Raymon
11 months ago
I'm not entirely sure, but I feel like we discussed contacting the DBA in class for issues like this. Could be option A?
WA
Wava
11 months ago
I think I remember something about supplemental logging being important for capturing changes in Oracle. Maybe it's option C?
GE
Gerri
12 months ago
I'm feeling pretty confident about this one. The error message is clear, and enabling supplemental logging is the obvious solution.
AL
Allene
12 months ago
This seems straightforward - the error message is telling us that we need to enable supplemental logging, so I'll go with option C.
OW
Owen
12 months ago
Okay, based on the options, it seems like we need to enable supplemental logging on the Oracle side to fix this issue. I'll make sure to double-check that.
DE
Demetra
1 year ago
I'm a bit confused by this error message. I'll need to review my notes on Qlik Replicate and Oracle to figure out the best approach.
CA
Cassandra
1 year ago
Hmm, this looks like a tricky one. I think the key is to figure out what supplemental logging is and how to enable it.
JA
Janessa
1 year 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.
AS
Ashley
1 year ago
I agree, enabling supplemental logging seems like the best solution.
TU
Tula
1 year ago
C) Enable supplemental logging
MA
Mabel
1 year ago
A) Contact the Oracle DBA
VA
Vashti
1 year 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.
NI
Nickolas
1 year ago
C) Enable supplemental logging
JA
Jamey
1 year ago
B) Check the permission on the target endpoint
SH
Shakira
1 year ago
A) Contact the Oracle DBA
NA
Nadine
1 year 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?
CO
Coral
1 year 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.
LA
Lawanda
1 year ago
Definitely, let's cover all our bases.
JA
Jacquline
1 year ago
Yeah, better safe than sorry.
LE
Lenna
1 year ago
I agree, but it wouldn't hurt to contact the Oracle DBA just in case.
BI
Billy
1 year ago
I think enabling supplemental logging is the way to go.
DA
Daron
1 year 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!
AL
Alyssa
1 year ago
I think contacting the Oracle DBA might also be a good idea just to cover all bases.
TI
Tish
1 year ago
I agree, enabling supplemental logging should do the trick.
DO
Dominga
2 years ago
I'm not sure, but I think contacting the Oracle DBA could also help.
MI
Micheline
2 years ago
I agree with Noah, enabling supplemental logging should fix the error.
NO
Noah
2 years ago
I think the answer is C) Enable supplemental logging.