Ora-00600 Internal Error Code Ora-01001 Invalid Cursor
Contents |
in the No. 31 09:11. Dear All: The Instance xxx' alert log occured the ora errors ,please see the detail blow and take action for it. many ora-01001 invalid cursor ora-06512 thanks! ----------------------------------------- The errors is blow----------------------------------------------- 56 | Mon Mar 31 invalid cursor exception example in oracle 09:11:33 2014 | ORA-00600: internal error code, arguments: [17281], [1001], [0x1FF863EE8], [], [], [], [], [] 57 | ora-01001 invalid cursor ref cursor Mon Mar 31 09:11:33 2014 | ORA-01001: invalid cursor ---------------------------------------------end of errors-------------------------------------------------- From Oracle metalink to check the following: Applies to: Oracle Database - Enterprise Edition - Version 9.2.0.1 to
Sql Error Invalid Cursor Halt Application
11.2.0.0. [Release 9.2 to 11.2] Information in this document applies to any platform. *** Checked for relevance on 5-Jun-2013 *** Symptoms You are seeing the following error message when running queries.: ORA-00600: internal error code, arguments: [17281], [1001], [0x18E3EE690], [], [], [], [], [] You may or may not see this error message as well.: ORA-01001: invalid cursor Cause This ora-01001 invalid cursor for loop issue can be related to running SQL through TOAD. You can check if TOAD was the client that resulted in the error from the process state dump in the trace file, it will show: program: TOAD.exe / application name: TOAD.exe Solution You can also overcome this by patching the Oracle Client software as follows.: 1. Fix unpublished Bug 4359111, if the Oracle software is 10.1.0.4 or below. Patches for this bug can be found on My Oracle Support under Patch:4359111. 2. Fix unpublished bug 5910901 by applying Patch:5910901 if the Oracle software is 10.1.0.5 or above, 3. Apply the 10.2.0.4 patch set or above on the client. 4. You can change the non-Oracle client software being used, 5. You can just ignore the error as it is non-corruptive. 6. Run the queries directly through SQLPLUS instead of using TOAD. Note: Ensure that your version of TOAD is compatible with the version of the database as well. If the errors continue when using TOAD, but not with SQL*Plus, contact TOAD support to request a fix. Database error fo
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! Oracle PostersOracle Books Oracle Scripts invalid cursor sql Ion Excel-DB Don Burleson Blog
Java.sql.sqlexception: Ora-01001: Invalid Cursor
ORA-01001: invalid cursor tips Oracle Error Tips by Burleson Consulting
Maxopencursors
The Oracle docs note this on the ora-01001 error*: ORA-01001 invalid cursor Cause: Either a host language program call specified an invalid cursor or the value of http://www.programering.com/a/MDNzkDNwATk.html the MAXOPENCURSORS option in the precompiler command were too small. All cursors must be opened using the OOPEN call before being referenced in any of the following calls: SQL, DESCRIBE, NAME, DEFINE, BIND, EXEC, FETCH, and CLOSE. The Logon Data Area (LDA) must be defined by using OLON or OLOGON. If the LDA is not defined, this message http://www.dba-oracle.com/t_ora_01001_invalid_cursor.htm is issued for the following calls: OPEN, COM, CON, ROL, and LOGOFF. Action: Check the erroneous call statement. Specify a correct LDA area or open the cursor as required. If there is no problem with the cursor, it may be necessary to increase the MAXOPENCURSORS option value before precompiling. The ORA-01001 error occurs when: a host language program call gave an invalid cursor for use the value of the MAXOPENCURSORS option in the precompiler command was too small You can fix the ORA-01001 error by: Check your problematic call statement for any issues Specify a correct LDA area or open the cursor as required As a last resort, increase the MAXOPENCURSORS option value before precompiling As a note, the ORA-01001 error does not exist in Oracle 10g, according to the Oracle documentation. OraFaq.com has the following to say about the ORA-01001 error: This is 100% a program logic problem. You have either forgotten to code an open statement before using a cursor, or have not noticed that the cursor has b
25 15:42:35 2010
Errors in file /orabin/product/admin/lsdb/udump/lsdb_ora_18285.trc:
ORA-00600: internal error code, arguments: https://jeanwan.wordpress.com/2010/11/26/ora-0060017281-1001/ [17281], [1001], [0x38A97F1C0], [], [], [], [], []
ORA-01001: invalid cursor In the trace file: *** SESSION ID:(379.13320) 2010-11-25 15:42:35.984
*** 2010-11-25 15:42:35.984
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [17281], [1001], [0x38A97F1C0], [], [], [], [], invalid cursor []
ORA-01001: invalid cursor
Current SQL statement for this session:
declare cursor NlsParamsCursor is SELECT * FROM nls_session_parameters;begin SELECT Nvl(Lengthb
(Chr(65536)), Nvl(Lengthb(Chr(256)), 1)) INTO :CharLength FROM dual; for NlsRecord in NlsParamsC
ursor loop if NlsRecord.parameter = 'NLS_DATE_LANGUAGE' then :NlsDateLanguage := ora-01001 invalid cursor NlsRecord.v
alue; elsif NlsRecord.parameter = 'NLS_DATE_FORMAT' then :NlsDateFormat := NlsRecord.value;
elsif NlsRecord.parameter = 'NLS_NUMERIC_CHARACTERS' then :NlsNumericCharacters := NlsRecord
.value; elsif NlsRecord.parameter = 'NLS_TIMESTAMP_FORMAT' then :NlsTimeStampFormat := NlsRe
cord.value; elsif NlsRecord.parameter = 'NLS_TIMESTAMP_TZ_FORMAT' then :NlsTimeStampTZFormat
:= NlsRecord.value; end if; end loop;end; SQL> select s.sid,s.serial#,s.program,s.username,p.spid from v$session s, v$process p 2 where s.paddr = p.addr 3 and p.spid = 18285; SID SERIAL# PROGRAM USERNAME SPID
---------- ---------- -------------------- ---------- ------------
379 13320 OEUSER 18285 SQL> select sid,serial#,process,machine,osuser from v$session 2 where sid = 379; SID SERIAL# PROCESS MACHINE OSUSER
---------- ---------- ------------ -------------------- ------------
379 13320 2456:476 SMIC-SH\1FP07599 E007599 SQL> select event,p1text,p1raw,p2text,p2raw,state 2 from v$session_wait where sid = 379; EVENT P1TEXT P1RAW P2TEXT P2RAW STATE
---------------- ------------ -------------------- ---------- -------------------- ----------
SQL*Net