here's what I have changed. The thought process was the following:
even in case of this ORA-01007 exception the query was processed well by DBMS_SQL, the l_report.desc_tab contained the appropriate number of column
the exception ORA-01007 should come only later at calling the dbms_sql.column_value procedure, not at dbms_sql.define_column
so I decided to run the dbms_sql.describe_columns2 procedure before every define_column call, and it turned out that this exception does not happen anymore, possibly because describe_columns2 changes/fixes some inner states in DBMS_SQL
Hi Pavel,
here's what I have changed. The thought process was the following:
Best regards, István