ora-600 error caused by Cursor_sharing=force

1, in the Alert_lxdb.log log report 600 errors

Errors in FILE/U01/APP/ORACLE/ADMIN/LXDB/UDUMP/LXDB_ORA_50379.TRC:

Ora-00600:internal error code, arguments: [Kkslhsh1], [101], [], [], [], [], [], []

Note that this problem may result in a very large TRC file and cause the file system to be full!

2, the root cause of the problem: Set the cursor_sharing = Force

At present it seems that although the system does not have this setting, it is highly possible to set the application: Alter session Set cursor_sharing = Force.

Because the SQL that is extracted from the V$sqlarea can be seen, the maximum value of the query V$sqlarea.version_count now is 485, as shown in the Metalink bug list, which can cause problems when the number is greater than 100.

Sql> select Max (version_count) from V$sqlarea;

MAX (Version_count)

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

485

3. There are three kinds of solutions for the time being:

(1) Upgrade the database to 9.2.0.6 version, if set cursor_sharing = similar will cause Inser ... select. If there is a problem, you need 9.2.0.8 to resolve it.

(2) Modify the application to remove the alter session and use the binding variable.

(3) Periodic temporary alter system flush Shared_pool, which may be temporarily resolved in a few hours at a time.

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/database/Oracle/