Summary of Bugs On ORA-00600 [17281] [ID 428599.1]

Applies to:

Oracle Server – Enterprise Edition – Version: 8.1 to 10.2
Information in this document applies to any platform.

Purpose

The purpose of this Note is to explain bugs filed for ORA-00600 [17281] error against specific Oracle database versions, and explain the symptoms of each bug, workarounds if any and references the patch available at the time this article was written.

Scope

This article is a consolidated effort to summarize the top bugs reported (error) which have been fixed. It is directed towards Oracle Support Analysts and Oracle Customers to have an overview of various bugs logged for the same error

Error Description:

An error has ocurred while attempting to close all cursors for an instantiation.

Summary of Bugs On ORA-00600 [17281]

Bug 4359111 (Unpublished)

Abstract:OERI [17281] can occur on session switch in UPI mode

Version affected: 9.2.0.7,10.1.0.4 and 10.2.0.2

Fixed in version: 9.2.0.8, 10.1.0.5, 10.2.0.3 & 11.0

Backportable: Yes

Symptoms:

ORA-600[17281] when doing session-switch in UPI mode.

Details:

ORA-600[17281] can occur when doing a session-switch in UPI mode.

Workaround:

None

Patch details:

One-off patch available for few platforms
Check the Metalink for Patch 4359111 availability.

Patch 4359111 is an client side patch.
If Forms 8.0.6.3 is used as a client, then this patch should be applied on Forms 8.0.6.3 client.

 


 

Bug 4447625 (Duplicate of 4456348 but not verified) 

Abstract: ORA-7445 / ORA-19206 / ORA-600 [17148] %26 [17282] & [17281]

Bug 4456348

Abstract: ORA-1001 / ORA-19206 from DBMS_XMLGEN

Version affected: 9.2.0.6.0

Fixed in version: 9.2.0.8.0

Backportable: Yes

Symptoms:

Getting ora-1001 when trying to close cursor;
issue like piggyback, session switch, ORA-600(opiclo):
ORA-600: internal error code, arguments: [opiclo], [83], [], [], [], [],
ORA-600: internal error code, arguments: [1100], [0x2C88C12C],

Details:

ORA-1001 was being raised executing a refcursor in SYS.DBMS_XMLGEN.

eg:
ORA-01001: invalid cursor
ORA-19206: Invalid value for query or REF CURSOR paramete
ORA-06512: at “SYS.DBMS_XMLGEN”, line 83
ORA-06512: at “…”, line …

Workaround:

None

Patch details:

One-off patch available for few platforms on top of 9.2.0.7
Check the Metalink for Patch 4456348 availability.

 


 

Bug 3091541 (Unpublished)

Abstract: ORA-600: [17281], [1001] AND ORA-1001: INVALID CURSOR

Version affected: 8.1.7.4, 9.0.1.4 & 9.2.0.4

Fixed in version: 9.2.0.5, 10.1.0.2

Backportable: Yes

Symptoms:

ORA-00600 [17281] error with ORA-01001
call stack would be similar to

…kgicli kgidlt kgisdl ksuxds ksudel

Details:

ORA-00600 [17281] [1001] / ORA-1001 can occur using PLSQL cursors.

Workaround:

None

Patch details:

One-off patch available for few platforms on top of 8.1.7.4, 9.2.0.3 & 9.2.0.4
Check the Metalink for Patch 3091541 availability.

 


 

Bug 3350337 (Unpublished)

Abstract: OERI[17183] / OERI:17281 can occur

Version affected: < 9.2.0.8 & < 10.1.0.4

Fixed in version: 9.2.0.8 & 10.1.0.4 & 10.2

Backportable: Yes
Symptoms:

If error ORA-600[17183]/[17281] during session cleanup with kokapcl in the stack
trace then you are hitting this bug.

Details:

ORA-600 [17183] / ORA-600 [17281] can occur due to incorrect cursor information in “KOKA pseudo cursor” instantiation objects.

Workaround:

None

Patch details:

One-off patches are not available for any platforms and version.

 


 

Bug 5482174

Abstract: Pick Release Database Error ORA-600 [17281] and ORA-36 After Upgrade to 10G

Version affected: 10.2.0.3 & 10.2.0.4

Fixed in version: 11.1.0.4

Backportable: Yes

Symptoms:

To be seeing this the following must be true:
1. An Ora-600 [17281] [36] is seen.
2. The parameter session_cached_cursors is non-zero and typically high.
3. When session_cached_cursors is 0 the problem does not occur.
4. The call stack shows ‘ksupop->kgiCallStateCleanUp->kgiLRUResize’
repeated within it a number of times.

Details:

Deinstantation of a large number of PSLQL objects that have opened cursors when session_cached_cursors is non-zero might hit an Ora-600 [17281] [36].This has now been resolved.

Workaround:

Set session_cached_cursors to zero

Patch details:

One-off patches are not available for any platforms and version.

 


 

Bug 1818676

Abstract: IDLE SESSIONS ARE CAUSING ORA-600 [17034] OR [17281] ERRORS

Version affected: 8.1.7.2 & 9.0.1.1

Fixed in version: 8.1.7.3, 9.0.1.2 & 9.2.0.1

Backportable:  Yes

Symptoms:

To be seeing this bug the following must be true :
1. Profiles are being used and RESOURCE_LIMIT = TRUE
2. A process dies with ora-600 [17034] and/or [17281]
3. The “Current cursor” in the trace file points to a cursor of the form :
“table_x_x_x_x_x_x” where “x” is a hexadecimal string
4. The process must exceed one of the profile limits

Details:

Processes that exceed PROFILE resource limits and have accessed objects
(Eg CLOB etc) may fail with ORA-600 [17034] and/or [17281].

Workaround:

Either stop the process from exceeding the limit or switch profile use off

Patch details:

One-off patch available for few platforms on top of 8.1.7.2
Check the Metalink for Patch 1818676 availability.

 


 

Bug 3789406 (Unpublished)

Abstract: ORA-600 [17281], [4068] WHEN CLOSING CURSORS FOR INVALID PL/SQL PACKAGES

Version affected: 9.2.0.5

Fixed in version: 9.2.0.6, 10.1.0.4 & 10.2

Backportable: Yes

Symptoms:

ORA-600 [17281][4068]
One-off patch for bug 2747350 applied.

Details: 

This problem is only present with the one-off fix for bug 2747350.
ORA-600 [17281][4068] can occur when closing cursors for
invalid PLSQL packages.

Workaround:

None

Duplicate bugs referring Base bug:

None

Patch details:

Merge patch available for few platforms on top of 9.2.0.5
Check the Metalink for Merge patch availability.

 


 

Disclaimer:

This note contains most frequently hit bugs that can throw the error ORA-600 [17281]. However the above mentioned are not the complete list of bugs that can generate this error.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s