We recently started using Invantive Data Hub to sync data from Exact Online to our SQL Server database (in Azure). We want to sync ~4 years of historic data, specifically the transaction lines from Exact Online.
During setup with one of the engineers from Invantive everything went well, but something unexpected started happening a few days later. The first few iterations of the sql script are executed without any problems. For the first few days the transaction lines are synced (script syncs based on calender dates), but after 6 days an error occurs:
itgenclr096
Cannot insert the value NULL into column ‘actions’, table ‘EH-Exact-Invantive.dbo.EOL_SYNC_LOGS’; column does not allow nulls. INSERT fails.
Of course I can make this actions column nullable, but I would like to address the root cause (assuming an ‘action’ should always be defined for the log). Six successfull days synced might not be a random number, as the ‘sync window’ is set to 7 days in this script.
I was unable to find a similar post on this forum.
More info on the error:
2024-10-08 13:28:31.349 Warning itgendhb173: Context: c:\jobs\sql\eol2dwh.sql: --
-- Incrementele kopie van TransactionLinesBulk.
--
-- Er...l')
, sys_context('USERENV', 'SESSIONID', 'eol')
);
end;
2024-10-08 13:28:31.363 Error itgencun016: Error itgenclr096: External error in Invantive Data Hub.
Cannot insert the value NULL into column 'actions', table 'EH-Exact-Invantive.dbo.EOL_SYNC_LOGS'; column does not allow nulls. INSERT fails.
The statement has been terminated.
...
2024-10-08 13:28:33.385 Information itgendhb221: End program execution with exit code 6.