Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We are currently running a Qlik replicate server that takes data from an iSeries database, processes it, and propagates it into an Azure database. Its been running fine without issues for some time.
This morning we ran into the error below with one of our Qlik tasks. This is happening with only 1 of the 4 tasks and continues to error out and remain in 'recovering' status as it continued to retry. Each time it retries it has a new Cursor ID that its complaining about, the one noted below is just from one of the attempted recovery attempts.
The below solutions have been tried without success:
1. Fully restarted the replicate server and services on the host/server machine.
2. Restarted all the IBM ODBC/JDBC jobs.
3. Ensured all reliant Journals and receivers were present on the IBM side.
4. Fully stopped and resumed the effected Qlik task.
5. Attempted a Full reload of the target task.
Any help with resolving this or any clues to what could be causing it would be greatly appreciated.
Error Details:
===============================================================
Hi @RBarkerEV ,
Fully restarting Qlik Replicate should normally drop the ODBC connection and release all cursors.
To narrow this down, please try running the same SELECT query (QSYS2.Display_Journal) directly to see if the error reproduces outside of Replicate. It may also help to review the IBM job log for the relevant host job to check for any open cursors or related messages.
In addition, please confirm you are using the ODBC driver version we recommend in the user guide.
If the issue continues after these checks, please open a support ticket with us so we can investigate further.
Regards,
Desmond