We have seen Ignite customers getting the error "ORA-03137: TTC protocol internal error" in either the Ignite log files or appearing in Oracle trace files. This only seems to occur when using Oracle 11.1 as the repository and does not cause severe issues, only problems with the Ignite module receiving the error.

Based on some Oracle Support articles, namely:

"ORA-03137: TTC Protocol Internal Error : [12333] Using JDBC Driver [ID 752297.1]"

this appears to be related to Bug #7445550 related to JDBC connections to the database, which Ignite uses.  The solution in this bug is to do one of two things:

1. Upgrade to Oracle 11.1.0.7

2. Set "_optim_peek_user_binds"=false.  We have experienced good success with customers choosing option 2.

However, the following note in the article suggest the problem can still happen after upgrading to 11.1.0.7:

Note: Although upgrading to database version 11.1.0.7 has been confirmed to have solved this issue in a high number of cases, error ORA-3137 [12333] accompanied by Protocol Violation messages may still occur intermittently in database versions prior to 11.2, including database 10.2.0.4 and 11.1.0.7.  This has been reported in unpublished bug:8625762 ORA-3137 [12333] due to bind data not read from wire, in which case ORA-3137 [12333] can occur intermittently for SQL which uses user binds due to bind data being left unread on the Net connection. The bug suggests the workaround of setting "_optim_peek_user_binds"=false to avoid this problem (workaround to be used with caution as it can affect execution plans chosen by CBO), and also provides the fix by the application of Patch:8625762.