ORA-600 [HO Define: Long Fetch]
(Doc ID 2270309.1)
Last updated on JULY 15, 2019
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.2 to 12.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
ORA-600 [HO define: Long fetch] when using an Oracle Database Gateway Product. When performing an analysis on the logs and trace files, it was clarified that the issue only occurs when using 3rd party tools like SQL Developer , Toad, etc... instead of SQL PLUS for particular queries.
Reviewing Document id : 1224783.1 a few points are important:
- The ORA-600 [HO define: Long fetch] occurs when select query is fired from 3rd party tools like PLSQL developer , Toad for oracle.
- This can happen from versions 11.1 to 12.1
- The ORA-600 can happen for several reasons, the root cause of the error with the third party applications depends on the table being selected. The table description contains 2 long or long raw columns , for example –
CURRENCEY DATA LONG RAW
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document