Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Solving the Informatica Dilemma: On-Demand Briefing - Watch On Demand!
cancel
Showing results for 
Search instead for 
Did you mean: 
AIAPHLCDP
Contributor
Contributor

Cannot resume the error task of cursor already open or allocated

Hi team,

We receive the error of task with the AS400 as source system.

The error shows like:

Error executing display_journal statement RetCode: SQL_ERROR SqlState: 07005 NativeError: -502 Message: [IBM][System i Access ODBC Driver][DB2 for i5/OS]SQL0502 - Cursor SQL_CUR22516010 already open or allocated.

Currently we tried to resume the task, advanced run the task and even reload the whole task, but the error still happened. And we also connect to DBA team, but they replied that the cursor is not locked on the source end. Could you please provide any advice or solution? Thank you so much!

Labels (1)
1 Solution

Accepted Solutions
Dana_Baldwin
Support
Support

Hi @AIAPHLCDP 

Looks like you have an active support case open with us, 00385317.

The case was updated early this morning. Here is a condensed version of that update:

"00006240: 2025-06-16T03:42:23 [SOURCE_CAPTURE ]T: RetCode: SQL_ERROR SqlState: 54035 NativeError: -443 Message: [IBM][System i Access ODBC Driver]SQL0443 - Values for RCVRNG parameter not correct; reason code 4. [1022502] (ar_odbc_stmt.c:2816)

The Reason Code returned is 4. The explanation for Reason Code 4 is:
4 - There are more than the maximum number of allowed receivers in the receiver chain for the operation being performed. The maximum supported number is 2045.
According to IBM, for the Retrieve Journal Entry API, There is a limit imposed by IBM on the number of journal receivers that can be accessed by the Journal Retrieve APIs (approximately 2045). This value is passed in the RCVRNG parameter of the API.
Here is the link to IBM's documentation showing the max number of journal receivers:
https://www.ibm.com/docs/en/i/7.2?topic=capacities-journal-limits
Unfortunately, we are not able to modify this limit so you will need to work with the DBA to remove the receivers that have been read to get the task to start running."

Please continue to work with us via the case.

Thanks,

Dana

View solution in original post

1 Reply
Dana_Baldwin
Support
Support

Hi @AIAPHLCDP 

Looks like you have an active support case open with us, 00385317.

The case was updated early this morning. Here is a condensed version of that update:

"00006240: 2025-06-16T03:42:23 [SOURCE_CAPTURE ]T: RetCode: SQL_ERROR SqlState: 54035 NativeError: -443 Message: [IBM][System i Access ODBC Driver]SQL0443 - Values for RCVRNG parameter not correct; reason code 4. [1022502] (ar_odbc_stmt.c:2816)

The Reason Code returned is 4. The explanation for Reason Code 4 is:
4 - There are more than the maximum number of allowed receivers in the receiver chain for the operation being performed. The maximum supported number is 2045.
According to IBM, for the Retrieve Journal Entry API, There is a limit imposed by IBM on the number of journal receivers that can be accessed by the Journal Retrieve APIs (approximately 2045). This value is passed in the RCVRNG parameter of the API.
Here is the link to IBM's documentation showing the max number of journal receivers:
https://www.ibm.com/docs/en/i/7.2?topic=capacities-journal-limits
Unfortunately, we are not able to modify this limit so you will need to work with the DBA to remove the receivers that have been read to get the task to start running."

Please continue to work with us via the case.

Thanks,

Dana