My Oracle Support Banner

ORA-600 KPOAL8-1 During A Select Statement With WHERE Clause Via DG4MSQL (Doc ID 1304916.1)

Last updated on FEBRUARY 05, 2019

Applies to:

Oracle Database Gateway for SQL Server - Version to [Release 11.2]
Oracle Database Gateway for DRDA - Version to [Release 11.2]
Oracle Database Gateway for Sybase - Version to [Release 11.2]
Oracle Database Gateway for Informix - Version to [Release 11.2]
Information in this document applies to any platform.


When a SELECT statement is used with a  WHERE clause via DG4MSQL, it hangs.
Same SELECT without WHERE clause is successful.

SELECT * FROM dbo.mytable@dblink  WHERE "account_number" = '$$$$$$$'

In the database trace files, a dump file is generated with the error :

Incident 9811 created, dump file: /opt/oracle/admin/diag/diag/rdbms/w539d/w539d/incident/incdir_9811/w539d_ora_25102_i9811.trc
ORA-00600: internal error code, arguments: [kpoal8-1], [], [], [], [], [], [], [], [], [], [], []
SELECT * FROM dbo.mytable@dblink WHERE "account_number" = :"SYS_B_0"

----- Call Stack Trace -----
ksedst1() -->ksedst() -->dbkedDefDump() -->dbgexPhaseII() -->dbgexProcessError() -->dbgePostErrorKGE() --> dbkePostKGE_kgsf() -->kgerinv_internal() -->


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.