Select Fails With ORA-600 [736] When CURSOR_SHARING Are SIMILAR Or FORCE (Doc ID 1202505.1)

Last updated on FEBRUARY 07, 2014

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.4 to 11.2.0.2 [Release 10.2 to 11.2]
Oracle Database - Enterprise Edition - Version 10.2.0.5 and later
Information in this document applies to any platform.

Symptoms

In a database with literal replacement enabled (CURSOR_SHARING=FORCE or SIMILAR) when executing a query having:
1. a "WAIT n" clause
and
2. an inline SELECT which uses either a UNION ALL or UNION clauses
getting:
ORA-00600: internal error code, arguments: [736], [<x>], [<y>], [128], [128], [], [], [], [], [], [], []
where x and y differ by one.

For example:
ORA-00600: internal error code, arguments: [736], [3], [2], [128], [128], [], [], [], [], [], [], []
or
ORA-00600: internal error code, arguments: [736], [9], [8], [128], [128], [], [], [], [], [], [], []

Call Stack includes: .... kxsmbb <- kxsBindBufferSetUp <- kxsPeekBinds <- opitca <- kksSetBindType ...

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