Failure in associating MetadataManager TABLE_DEF with CDC_TABLE_ENTRY"

[jm32]

One of on our tasks, we periodically get the following error messages:
Unable to get TABLE_DEF for capture table [dbo.TableNAme]
Failure in associating MetadataManager TABLE_DEF with CDC_TABLE_ENTRY"

We are using  SQL Server RDS as an Endpoint - NOT MS-CDC.  

Any help is appreciated!

[john_wang]

Hello @jm32 ,

Thanks for reaching out to Qlik Community!

Understanding the root cause of this error message is proving challenging at the moment. Could you please set SOURCE_CAPTURE to 'Verbose' and reproduce the issue? Then examine the task log file for any potential clues.

Additionally, could you verify whether the table was dropped or if any DDL operations were performed on it

Hope this helps.

John.

[Kent_Feng · Accepted solution]

Hi @jm32 

The error message indicates it is very likely that the metadata of the table is changed, I would suggest a reload of the affected table.

Regards

Kent

[SushilKumar]

Hello @jm32 

Metadata got changes happen on the database when someone re-org the table or by so patch or maintenance which alter the physical Structure of the tables. 

QR gather metadata when FL or task resume by the timestamp. it will not update the metadata until FL or task resume by the timestamp. and above error occurs when QR identify mismatch in the gathered metadata and received metadata in terms of Object_ID 

As transaction logs hold Object_ID not by the table names. Replication require a Coordination between Applicaion developer and Qlik replicate admin. It is requested to inform each other if anything is there if it needs to do on the tables which are participating in any replication task.

Regards,

Sushil Kumar

[jm32]

We dropped the table and are rerunning the task.  However, the table is now stuck in QUEUED.  

How do we get a table out of being stuck in QUEUED?   We have dropped in and readded it and it is stuck. 

[jm32]

The table has loaded now.  However, we do not get any changes.  Is that something to do with the ObjectID in the transaction log?  A column was dropped and re-added on the source a couple of days ago.  We exclude that column in the Qlik task as well.  

[Kent_Feng]

Hi @jm32 

Did you select the affected table and reload it as illustrated?

Thanks

Kent

[DesmondWOO]

Hi @jm32 ,

Make sure your table has been added to article. To verify same objecti_id is used, you can enable TRACE level on SOURCE_CAPTURE. If problem persists, please submit a support ticket.

Regards,
Desmond

[jm32]

This has been resolved.    The task wasn't resumed after we removed the table - just saved.  Once we did these steps:
stopped task ->removed table -> Resumed task -> Stop Task -> Added table (after the target data was cleaned up) -> Resume task

Thanks all for your help

[john_wang]

Thank you so much for your update! @jm32 Glad to hear it's solved.

Best Regards,

John.