java.sql.SQLException: ORA-00600: internal error code: [evapls1], []

數據庫報ORA-00600: internal error code, arguments: [evapls1]錯誤，如下：
2009-04-02 16:02:31,253 WARN [org.jboss.resource.connectionmanager.TxConnectionManager] Connection error occured: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@675320[state=NORMAL mc=org.jboss.resource.adapter.jdbc.xa.XAManagedConnection@b9109 handles=1 lastUse=1238659348103 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@1de2ea4 context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@1c82eaa xaResource=org.jboss.resource.connectionmanager.xa.JcaXAResourceWrapper@15f161b txSync=null]
java.sql.SQLException: ORA-00600: internal error code, arguments: [evapls1], [], [], [], [], [], [], []
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:213)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:952)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1054)
at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:836)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1124)
at
……
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:595)
2009-04-02 16:02:31,257 INFO [STDOUT] 16:02:31,256 ERROR [select] Execute sql failed

UI操作：點擊SYSTEM SETTING：CODE TABLE和SYSTEM PARAMETER時拋如上的錯誤

上網搜了一下，SHIT，又可能是ORACLE的一個BUG，說明如下：
Predicate pullup does not typecheck operands properly leading
to dumps / internal errors (eg: ORA-600 [evapls1]) at execution time.

Workaround:
alter session set "_optimizer_filter_pred_pullup"=false;

This is Oracle Bug 4626732, and there is no information from the bug on db version 9i. I don't think you will be able to find a workaround here. Contact Oracle and ask them to provide a backport patch.

我靠，由於是使用的ORACLE EXPRESS版，所以還沒辦法應用PATCH。我將下面的語句：

alter system set "_optimizer_filter_pred_pullup"=false;
一放到數據庫執行，然後叫QA再執行同樣的操作，這個錯誤不再拋出。這只是改了數據庫的一個隱含參數。