Variable is not valid in the context where it is used after 200 lines of rows

[igor2x]

Description

Creating variable and executing SELECT statement with variable and SQL executes just fine. But if I scroll down past the 200 lines new SQL is executed which returns error:
SQL Error [42703]: "TEMP.VAR_USERNAME" is not valid in the context where it is used.. SQLCODE=-206, SQLSTATE=42703, DRIVER=4.32.28

And this error is displayed where data were displayed before. So not only I have got an error, but also data are not visible anymore.

DBeaver Version

Community Edition 24.3.5

Operating System

Windows 11

Database and driver

1. Database name and version: IBM Db2 v11.5.8.0
2. Driver name and version: jcc-11.5.8.0.jar

Steps to reproduce

1. Copy the following SQLs into SQL Editor:

CREATE OR REPLACE VARIABLE temp.var_username VARCHAR(128);
SET temp.var_username = 'PUBLIC';
SELECT * FROM SYSIBMADM.PRIVILEGES WHERE AUTHID = temp.var_username;
DROP VARIABLE temp.var_username;

2. Select all of the statements and Execute SQL script.
3. SQL runs successfully. Now in SQL result windows scroll down past the 200 row and error appears:

SQL Error [42703]: "TEMP.VAR_USERNAME" is not valid in the context where it is used.. SQLCODE=-206, SQLSTATE=42703, DRIVER=4.32.28

There are actually two issues:
a) Error appears
b) Error is displayed inside SQL result window where from step above where data displayed, so after error I don't even see the data from step 1.

Additional context

If I increase row limit to e.g. 300, now error appears after 300 row is scrolled down. I don't know how this another really works. Just assumption:
a) variable is created
b) select with variable is executed
c) variable is dropped
d) when I scroll down past the line 200 only SELECT is executed again, but because there is no variable anymore (step c - dropped it) now SELECT returns error. It looks like DBeaver was not designed to work with variables.

---

If step c) is commented out and re-executing the statements and scroll down and now SQL is displayed past the 200 rows.

---

I don't know if this works as designed (I hope not), but at least error message should not override the data in SQL result.

[E1izabeth]

You're dropping a variable right after the select query is executed. Why?
To fetch more rows, DBeaver executes the query that returned the result set - it's only the select. But the variable is dropped. So, select can't be correctly executed anymore.

[igor2x]

I agree droping variable is the cause of the main issue. But...

Picture after steps 2 from Steps to reproduce section. This is fine data are displayed in PRIVILEGES tab (name PRIVILEGES is because of table name from where SELECT gets the data):

Picture after step 3 (scrolling down past the 200 row): Now the issue I am talking about. The error message is displayed inside the same PRIVILEGES tab where is place for data to appear. Errors should not be displayed inside this tab.

What I expect instead is error to be displayed in new error dialog and inside "Error log" tab like this (Don't look at the text of error, I just produced some other error to demonstrate).