ORA-1461 encountered when generating server alert SMG-3500

ORA-1461 encountered when generating server alert SMG-3500

[@more@]

今天的警告檔案上有錯誤產生：

Fri Sep 5 00:18:19 2008

ORA-1461 encountered when generating server alert SMG-3500

但是這個錯誤在官方的文件上居然沒有。查詢Metalink發現：

Subject: Ora-1461 Encountered When Generating Server Alert Smg-3500

Doc ID: Note:461911.1 Type: PROBLEM

Last Revision Date: 09-JUL-2008 Status: MODERATED

In this Document

Symptoms

Cause

Solution

References

--------------------------------------------------------------------------------

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

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

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 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.

References

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

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

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

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

--------------------------------------------------------------------------------

Help us improve our service. Please email us your comments for this document. .

解決方法：

這個錯誤的產生是更新SMON_SCN_TIME或者是插入資料到WRI$_ALERT_HISTORY表的時候產生的問題。應該說對系統的影響不大，雖說oracle給出了bug的patch，不建議打。