In SQL Developer 23.1, the SET LONG nnnn command, if the argument is higher than 0.1% of the maximum Java heap size, causes SQL Developer to print the following warning in the script output:
Warning: This LONG setting may cause Java memory problems.
It is recommended to reduce the setting and/or increase the memory available to Java.
This warning was introduced in SQLcl 22.4, as reported in this post. And now it's also present in SQL Developer 23.1.
Is it possible to silence this warning, or turn it off?
Reason: some of my reports need to fetch a single CLOB value, e.g., as returned by functions such as
DBMS_SQLTUNE.REPORT_SQL_MONITOR, or DBMS_AUTO_REPORT.REPORT_REPOSITORY_DETAIL, which can return large documents, especially if in XML format.
Therefore, SET LONG must be used with a generously high-enough value, in order to prevent the returned CLOB value from being truncated in the readout. I've been using SET LONG 5000000 for years, without any memory issue ever, using the default Java heap settings of SQL Developer on Windows, i.e. with the maximum Java heap size set to 2 Gb.
And it's a little bit annoying to see this warning on top of each of my reports now: I have nothing against the idea of spreading the awareness that using high values of SET LONG may cause Java heap memory issues, if one carelessly fetches large CLOB values, but I still find that the above message is neither useful, nor welcome, in my reports.
Thanks & regards,