A ORA-1461 error was found today in the alert file of a 10203 database. ___ Database

A ORA-1461 error was found today in the alert file of a 10203 database.

Error all information is as follows:

ORA-1461 encountered when generating server alert SMG-3500

Oddly enough, this error number does not exist in the official documentation error manual for 10G, and has to be queried for metalink and found to be a bug in Oracle.

The cause of this problem is that the Smon process raised a ORA-1461 error when updating the Smon_scn_time table.

If event:1461 TRACE NAME errorstack level 10 is set, the following information can be seen from the background Smon process log:

Ora-01461:can bind a Long value only as insert into a long column

Current SQL statement for this session:

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 = (select min (SCN) from Smon_scn_time where thread=0)

Based on the search results on Metalink, this bug can occur on multiple platforms and is currently found to be affected by 10.2.0.3.

Oracle did not give a workaround, and the issue is not mentioned in any version. Fortunately, the problem has little impact on the system.

Thanks to netizens "Blue ocean" reminder, after 1 years or so, Oracle finally released a fix for this bug, fixed the bug in Patch set patch 6602742, more description of this bug can refer to Metalink doc ID: note:461911.1.