Tuesday, February 26, 2008

Ora-1461 Encountered When Generating Server Alert Smg-3500

I found below error on alert file.

Tue Feb 26 09:22:08 2008
ORA-1461 encountered when generating server alert SMG-3500
Tue Feb 26 10:34:05 2008

I have found Note:461911.1 on metalink.


Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.3
This problem can occur on any platform.


Symptoms

After applying the 10.2.0.3 patchset the following errors may be reported:

ORA-1461 ENCOUNTERED WHEN GENERATING SERVER ALERT SMG-3500

ORA-01461: can bind a LONG value only for insert into a LONG column


Cause

The issue was discussed in the following bugs

Bug 5887228: ORA-1461 GENERATED BY SMON WHILE IT IS UPDATING SMON_SCN_TIME: ORA-1461 GENERATED BY SMON WHILE IT IS UPDATING SMON_SCN_TIME

Bug 5982820: ORA-1461 INSERT WRI$_ALERT_HISTORY BY MMON

Bug 6145134: ORA-1461 INSERT WRI$_ALERT_HISTORY BY MMON


All these bug were closed as a duplicate to the following bugs:

Bug 6085625 :ORA-01483: INVALID LENGTH FOR DATE OR NUMBER BIND VARIABLE

This bug has the following

Bug 6085625 :ORA-01483: INVALID LENGTH FOR DATE OR NUMBER BIND VARIABLE


This bug has the following regression

unpublished bug 6452485: STAR:NT:RAC:ORA-600: INTERNAL ERROR CODE, ARGUMENTS: [17182]


Solution


1- To fix these Bug 6085625 and unpublished bug 6452485, The fixes for these two bugs are now available as Patch 6602742.

So applying Patch 6602742 will fix the problem.


For some platforms where Patch 6602742 is not available, you can use Patch 6602482 .

If you could not find these patches available for your platform please log an SR with Oracle Support.

2-Also you can use the following workarounds as mentioned in Bug 6085625:

-Flushing the shared pool can help remove the problem cursor from the shared pool.

-Using SESSION_CACHED_CURSORS = 0 can help in some cases.

7 comments:

Jayant Mahishi said...

Hi... Thanks for updating over the ora issue. We came across this error in our RAC instance today. Can you tell me what would be the impact if we ignore it. How would it effect the performance of the database in the long run. I didnt see any impact happening on the DB, it was working normal.

Thanks,
Jayant

HunterX said...

This is oracle bug ,that we can ignore. I have ignored on my RAC.
No impact with oracle DB.

Jayant Mahishi said...

Thank you,
Jayant

Anonymous said...

Is this bug fixed in 10.2.0.4? I could not find any update on metalink about this.

HunterX said...

I'm not sure about update on metalink too.r

Anyway I patched to 10.2.0.4 and I still find this error on alert log.

Muhammad Abdul Halim said...

simply it can be ignore. no impact.

Regards
Halim

Surachart said...

yes.. this can ignore.