Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Team,
we are getting null values while processing delta records from Oracle using Qlik Replicate specific to update operation.
we are using archive redo logs using Oracle logminer.
we are getting all the commits specific to transaction but the latest commit has all columns null except the primary key.
any idea on this?
Thanks,
Pooja
quetions: Do we still need to enable supplemental logging on all the columns at the Oracle side?
ans: if you are getting null, best is to try to put supplemental logging on all columns.
some article that maybe related
check to see if the table have supplemental logging on all column .. notes all column not just logging on PK only.
Thanks Steve
how the supplemental logging is linked with change processing using Qlik Replicate?
see this article.
Hi Steve,
Automatically add supplemental logging is enabled at the source endpoint in Qlik Replicate.
Do we still need to enable supplemental logging on all the columns at the Oracle side?
Thanks,
Also, can we put not null condition on the columns replicated by Qlik using Qlik Replicate/Compose.
As noticed Oracle table has put not null condition on the columns when replicating them using Qlik,I don't see any not null condition on those columns.
quetions: Do we still need to enable supplemental logging on all the columns at the Oracle side?
ans: if you are getting null, best is to try to put supplemental logging on all columns.
some article that maybe related
Thanks Steve
As per Oracle team, enabling supplemental logs on all columns seems to be overhead and difficult to manage.
Any other approach for this issue?
Hi @puja
Is there a primary key or a unique index on the source table? If not you need supplemental logging on all columns. Also, if there are columns involved in a transformation or filter, those columns need supplemental logging enabled.
Prerequisites ‒ Qlik Replicate
Thanks,
Dana
Thanks Steve
Null value issue is resolved by enabling the supplemental logs on all the columns.
Just 1 another ques.,regarding changed table created by Qlik replicate.
I have noticed that Qlik Replicate changed table has records wherein header__timestamp is Feb 1,2023 or Feb 3,2023 , so on.
Qlik compose is being used to process the changed records and qlik compose has not processed the records.
We cannot see the records in qlik compose table though the records are processed a week back.
any idea on this?