ORA - 1461 encountered when generating
server alert SMG-3500
METALINK中，说是Oracle的一个bug。 METALINK, said Oracle is a bug.
造成这个问题的原因SMON进程在更新SMON_SCN_TIME表时，引发了ORA-1461错误。 The reason for this update process Beginning SMON_SCN_TIME table, ORA - 1461 triggered a mistake.
如果设置了EVENT：1461 TRACE NAME ERRORSTACK LEVEL 10，从后台SMON进程日志中可以看到下面的信息： If the installation of EVENT: 1461 TRACE NAME ERRORSTACK LEVEL 10, switched from the background process can log in to see the following information:
ORA-01461: can bind a LONG value only for insert into a LONG column ORA - 01461: can bind a LONG value only for insert into a LONG column
Current
SQL statement for this session: Current SQL statement for this session:
update smon_scn_time set orig_thread=0, time_mp=:1, time_dp=:2, scn=:3, Update smon_scn_time set orig_thread = 0, time_mp =: 1, time_dp =: 2, scn =: 3,
scn_wrp=:4, scn_bas=:5, num_mappings=:6, tim_scn_map=:7 where thread=0 and Scn_wrp =: 4, scn_bas =: 5, num_mappings =: 6, tim_scn_map =: 7 = 0 and where thread
scn = (select min(scn) from smon_scn_time where thread=0) Scn = (select min (scn) from smon_scn_time where thread = 0)
根据METALINK上的搜索结果，这个bug在多个平台上都可能出现，目前发现受影响的版本都是10.2.0.3。 METALINK based on the search results, this bug on multiple platforms are likely to happen now that all the affected version 10.2.0.3.
Oracle并没有给出解决方法，这个问题在什么版本会修正也没有提到。 Oracle did not give a solution to this problem in what will be amended version also not mentioned. 好在问题对系统的影响不大。 Fortunately, the issue little impact on the system.
