SYS_OP_C2C Causing Full Table/Index Scans

(Doc ID 732666.1)

Last updated on APRIL 14, 2017

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 10.1 to 12.1]
Information in this document applies to any platform.
This problem can occur on any platform.


1) You are executing a query using bind variables.
2) The binding occurs via an application (eg. .NET, J2EE ) using a "string" variable to bind.
3) The query is incorrectly performing a full table/index scan instead of an unique/range index scan. 
4) When looking at advanced explain plan, sqltxplain or 10053 trace, you notice that the "Predicate Information" shows is doing a "filter(SYS_OP_C2C)".

e.g select * from table(dbms_xplan.display_cursor(&sql_id,null,'ADVANCED'));

Predicate Information (identified by operation id):
1 - filter(SYS_OP_C2C("COL1")=:B1)            <=== filter operation occurring


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