Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Oracle Source SQL Sever Target
We're running a task in Replicate that has been running for multiple years but started to fail on Saturday morning and we can't establish why - this is impacting our business wide update processes so need some urgent assistance to identify and help us fix the issue
We're not aware of any changes to this existing process
The error messages we are seeing are along these lines
RetCode: SQL_ERROR SqlState: 42000 NativeError: 11501 Message: [Microsoft][SQL Server Native Client 11.0][SQL Server]The batch could not be analyzed because of compile errors. Line: 1 Column: -1
RetCode: SQL_ERROR SqlState: 42000 NativeError: 264 Message: [Microsoft][SQL Server Native Client 11.0][SQL Server]The column name 'F_CUS_AMOUNT_OS' is specified more than once in the SET clause or column list of an INSERT. A column cannot be assigned more
more than one value in the same clause. Modify the clause to make sure that a column is updated only once. If this statement updates or inserts columns into a view, column aliasing can conceal the duplication in your code. Line: 1 Column: -1 [1022502] (ar_odbc_stmt.c:4011)
Hi,
From past experience we've seen this error when the ODBC driver version did not match the Replicate version (in your case version V2022.11.0.746) . Please check that the ODBC driver vesion of ms-sql meets the prerequisite for this release - here is a link to product documentation:
https://help.qlik.com/en-US/replicate/November2022/Content/Replicate/Main/SQL%20Server/prereqs_sql_s...
In addition - please note that you are running an old version that is out of support. We strogly recommend you to upgrade to latest Replicate version. FYI here is a link to product lifecycle information:
https://community.qlik.com/t5/Product-Lifecycle/Qlik-Replicate-Product-Lifecycle/ta-p/1837201
Regards,
Orit
Hello @robterry ,
Agree with @OritA .
In addition, it’s not only the column F_CUS_ID — all columns appear more than once in the apply SQL statements, which is quite unusual.
I’d suggest trying the following steps:
Stop and resume the task.
If the issue persists, stop the task, restart the Replicate services, and then resume the task.
As a further step, stop all tasks, restart the OS, and resume the task again to see if that helps.
However, as Orit mentioned, upgrading to a supported Replicate version is strongly recommended.
Hope this helps.
John.
Thanks - we don't believe it will be ODBC connected as the processes were running without any issues and nothing has changed in relation to them
We've stopped tasks and restarted replicate services and then resumed tasks, its working on other processes its just the one process relating to the T_SH_Customer table that is causing the issue / failures
Are there any other things we can try ahead of the OS restart as this will have an impact on other processes outside of Replicate
Hello @robterry ,
Could you please share the SQL Server ODBC driver version you’re using?
Personally, I don’t think there’s a better approach than performing an OS restart in this case.
By the way, were there any recent changes in the environment? For example, OS patches or related software upgrades?
Good luck with resolving the issue,
John.
We applied cumulative patching on the Oracle OCI environment that the process links to on Friday evening (finished by 20:15) but have seen no impacts to any other process that we run via Qlik Replicate (as per the snapshot added to the chat)
It is only the specific update process LD-FULL-APPLY-CRM-TASK that is erroring and then only when hitting a specific table T_SH_Customers that it is causing an error
After the patching was applied this process ran for 12 hours without any issue until it failed on Saturday morning
Because we've seen successful process elsewhere and also this process ran for a period of time without issue we don't believe it is linked to the cumulative patching applied in OCI
Hi @robterry ,
Thanks for the clarification.
I’d suggest opening an urgent support ticket and including the attachment mentioned above.
Our support team will be more than happy to assist you further.
Regards,
John.
Hi John - can you advise on how we raise an "urgent support ticket"?
we've tried the Qlik Help section but that isn't very helpful
we've tried "ask a question" but the "support" section of location does allow for any selection of a support area
All in all a very poor user experience