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

ORA-03137: TTC protocol internal error : [12333] [7] [120] [108] [] [] [] []
----- Current SQL Statement for this session (sql_id=c0czhbm4hcz98) -----
DELETE FROM PORTAL_CONCURRENT_USER_SCRATCH
WHERE LAST_LOGIN < :intervalStartDate


----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
skdstdst()+002c bl 105e2771c
ksedst1()+0064 bl 101fad134
ksedst()+0028 bl ksedst1() 60000B8104C4A30 ?
600000002050032 ?
dbkedDefDump()+07fc bl 101fae954
ksedmp()+0048 bl 101fad130
opiierr()+0168 bl ksedmp() 000000000 ?
opitsk()+1344 bl 103ec9a5c
opiino()+09a0 bl opitsk() 110098B40 ? 000000000 ?
opiodr()+0b48 bl 103ec7a30
opidrv()+0440 bl opiodr() 3C61672F72 ? 41032E668 ?
FFFFFFFFFFFF7E0 ? 073702F74 ?
sou2o()+0090 bl opidrv() 3C05C04AEC ? 4A09A9924 ?
FFFFFFFFFFFF7E0 ?
opimai_real()+01b0 bl 101face8c
main()+0090 bl opimai_real() 000000000 ? 000000000 ?
__start()+0098 bl main() 000000000 ? 000000000 ?

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 .