Last updated on JANUARY 18, 2017
Applies to:
Oracle Database Gateway for SQL Server - Version 11.2.0.1 to 11.2.0.2 [Release 11.2]Oracle Database Gateway for DRDA - Version 11.2.0.1 to 11.2.0.2 [Release 11.2]
Oracle Database Gateway for Sybase - Version 11.2.0.1 to 11.2.0.2 [Release 11.2]
Oracle Database Gateway for Informix - Version 11.2.0.1 to 11.2.0.2 [Release 11.2]
Information in this document applies to any platform.
Symptoms
When a SELECT statement is used with a WHERE clause via DG4MSQL, it hangs.
Same SELECT without WHERE clause is successful.
Example:
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() -->
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms