I know this is about 6 years too late, but in case anyone (like me) stumbles upon this error - it looks like this is an Oracle bug related to the CURSOR_SHARING database parameter. The workaround for this bug is to change the parameter to EXACT. It's listed as bug # 9877980 on Oracle's support website. They claim they've fixed the issues on 11.2.0.3, but I have seen this error occur on 11.2.0.3 databases, so it's not completely resolved in that version...