ASSERTION meaning

[MoeyE]

Hi,

I have a task that goes from Oracle to SQL server experiencing a tonne of these assertion messages. Does anyone know what does not contain all key values means?

[ASSERTION ]V: 'UPDATE (3)' event of table 'test'.'TRN511' with id '95' does not contain all key values (1 from 2), stream position '00000000.c4fda5e0.00000002.0001.01.0000:53613.2677947.16' (streamcomponent.c:2976)

I am going to talk with the client to query the ct table for the changes at these stream positions and also check the DDLs. However I'd just like to know if anyone has come across this assertion message before. Thank you.

Kind regards,

Mo

[john_wang]

Hello @MoeyE ,

Thanks for reaching out to Qlik Community!

For quick answer, I'd like to suggest checking if the PK or Unique Index columns were added into supplemental logging correctly. I may come back to help you further if you need additional assistance.

Hope this helps.

Regards,

John.

[Heinvandenheuvel]

[ASSERTION] is a nice way of saying "BUG" - Please submit a support ticket.

An assertion means that the code 100% expected a certain condition, verified it, found the condition not to be present and could not handle it on the fly.  It should NOT be possible to cause an assertion to trigger with bad customer Replicate task settings directly but it could be due to customer environment changes after Replicate started and made sure everything was setup as expected.

Hein.

[Sreekanth_333]

Hi @john_wang , Do we have an update on this issue? I'm facing similar issue and got table suspended

UPDATE (3)' event of table <Table Name > does not contain all key values
Table <Table Name > (subtask 0 thread 1) is suspended. Unable to build WHERE clause, statement:

[DesmondWOO]

Hi @Sreekanth_333 ,

Have you defined transformation rules in your task? It may be necessary to review your task settings and table structures. I would recommend to submit a support ticket.

Regards,
Desmond

[john_wang]

Hello @Sreekanth_333 ,

Agree with @DesmondWOO , please open a support ticket with below information:

1. Task Diag Packages

2. Task log files with SOURCE_CAPTURE/TARGET_APPLY set to Verbose, make sure to decrypt the task log files

3. The source table and target table creation DDL include the PK/Unique Indexes information

Hope this helps.

John.

[MoeyE]

Hi Sreekanth,

This was a long time ago. Looking through my notes for my particular case, there was a probability that this was a table related issue. Perhaps check the table's primary keys. Are there any composite key columns? Are they being updated? Sorry I can't offer any more than that as that is all I know. Someone should be able to help you if you open a ticket with them.

Regards,

Mohammed