Last updated on NOVEMBER 28, 2016
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 10.2.0.3 [Release 9.2 to 10.2]
Information in this document applies to any platform.
***Checked for relevance on 10-Jan-2014***
This issue was observed on a Oracle 10.1.0.5 64-bit RDBMS on a AIX5L 64-bit server. It also occurs on 10gR2
It could occur on any platform and would be on an environment where JDBC clients are used instead of an Oracle client.
The alert log shows these errors:
ORA-01001: invalid cursor
A failing statement may or may not be shown in the trace file.
The Call stack will show that a cursor is being closed when the error occurs, and may take a few forms. Commonly, it could look like one of these:
- ksedst ksedmp ksfdmp kgeriv kgeasi kgiCloseCursor
kgiCloseCachedCursors kgiccc kgicls pevm_EXECC pfrinstr_EXECC pfrrun_no_tool
- ksedst ksedmp ksfdmp kgeriv kgeasi
kgicli kgiscl ksuxds ksudel opilof opiodr ttcpip . . .
- ksedmp ksfdmp kgeriv kgeasi
kgicli kgidlt kgidel perabo perdcs peidcs kkxcls2 kxtcln
- ksedmp kgeriv kgeasi kgicli kgiscl ksuxds ksudel opilof opiodr . . .
- ksedst ksedmp ksfdmp kgeriv
kgeasi kgicli kgiscl PGOSF441_ksuxds kssdch_stage kssdch ksudlp opidcl
The function stack is indicating the error occurred when closing cursors and doing cleanup.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms