Skip to main content

Dynamic Sql

  • October 28, 2014
  • 3 replies
  • 0 views
D

I am creating a cursor using dynamic SQL. I can fetch the data with no problem, but whenever I tried to execute another SQL Statement (Dynamic Cursor still open) I get an error message stating "Connection is busy with the results for another hstmt". Any ideas on what may be causing this error? We have other programs where we have open cursors (static SQL) and have no problem performing other SQL statements.

    3 replies

    D

    I am creating a cursor using dynamic SQL. I can fetch the data with no problem, but whenever I tried to execute another SQL Statement (Dynamic Cursor still open) I get an error message stating "Connection is busy with the results for another hstmt". Any ideas on what may be causing this error? We have other programs where we have open cursors (static SQL) and have no problem performing other SQL statements.

    Some past versions of AcuSQL had problems which caused the "Connection is busy with the results for another hstmt" error. Those have already been fixed, so you may need to upgrade.  What version are you running?

    D

    I am creating a cursor using dynamic SQL. I can fetch the data with no problem, but whenever I tried to execute another SQL Statement (Dynamic Cursor still open) I get an error message stating "Connection is busy with the results for another hstmt". Any ideas on what may be causing this error? We have other programs where we have open cursors (static SQL) and have no problem performing other SQL statements.

    We are using version 8.1.3.1 plus some patches ECN-SQL128, 129 and 131

    D

    I am creating a cursor using dynamic SQL. I can fetch the data with no problem, but whenever I tried to execute another SQL Statement (Dynamic Cursor still open) I get an error message stating "Connection is busy with the results for another hstmt". Any ideas on what may be causing this error? We have other programs where we have open cursors (static SQL) and have no problem performing other SQL statements.

    In Version 9.1.2 ECN-SQL138 fixed an issue that could cause the error.  You should raise a support incident to address this issue. Attaching a test program that demonstrates the error to the support incident will help determine the resolution.

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement