This content has been marked as final. Show 5 replies
kgronau wrote:I'm seeing this lately too, although in my case it seems to be happening when connected to a database through a VPN with a short (15 minutes maybe) inactivity margin before my session gets terminated. When it happens I shut down SQL*Developer and log in again everything is fine. I wrote a sql_plus program to spool messages to the screen every 10 minutes to keep the connection alive - seems to help me.
SQL Error: Stream has already been closed
I'm connected within the same network and I'm able to select other tables without issues - even when doing nothing for a while. My issue is only happening with this LONG column.
Thanks for reporting this regression. During the 3.1 EA cycle other cases of this error were reported (and fixed) in the object viewer, but no explicit mention was made of LONG columns, so far as I can tell.
As an aside, recall the LONG and LONG RAW data types were deprecated way back in Oracle 8.0. Accordingly some future Oracle release may do away with them entirely. Hopefully customers have been following the recommendation to use CLOB/BLOB instead over the past 15 years or so!
Bug 13834339 - REGRESSION: SQL ERROR: STREAM HAS ALREADY BEEN CLOSED
SQL Developer Team
The problem is that even when LONG and LONG RAW columns were deprecated they are still used AND more important that a couple of Oracle tools like for example the Oracle gateways up to 11.2 are still mapping certain foreign data types to an Oracle long.
Agreed. I read somewhere recently that gateways will continue to map to LONG even in 12, although only for length >= 32K rather than 4000. Clearly a complete phase-out will not happen anytime soon.