ORA-00600 [kxttUpdateActiveTTSegsCount] And JDBC Begin Transaction Failed Errors After Upgrade to 19C Database (Doc ID 2776876.1)

Last updated on APRIL 17, 2023

Applies to:

Symptoms

ORA-00600 [kxttUpdateActiveTTSegsCount] and JDBC begin transaction failed errors received after upgrading database to 19C.

The database was upgraded from version 12.1.0.2 to 19.10, and no other changes to the application tech stack, application code, database structures or data, or silent configurations.

Now, one of the applications is encountering problems in certain specific areas.
This is repeatable and consistent.
The user navigates the app and selects specific data to view, and the application reports that the current connection was closed.

Example Weblogic log entry:
ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR c.q.a.v.n.m.q.MetricEntryViewQuery - JDBC begin transaction failed:
org.hibernate.TransactionException: JDBC begin transaction failed:
at org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.doBegin(JdbcTransaction.java:76) ~[hibernate-core-4.3.4.Final.jar:4.3.4.Final]
at org.hibernate.engine.transaction.spi.AbstractTransactionImpl.begin(AbstractTransactionImpl.java:162) ~[hibernate-core-4.3.4.Final.jar:4.3.4.Final]
at org.hibernate.internal.SessionImpl.beginTransaction(SessionImpl.java:1435) ~[hibernate-core-4.3.4.Final.jar:4.3.4.Final]
at sun.reflect.GeneratedMethodAccessor745.invoke(Unknown Source) ~[na:na]

At the same time, the following error is logged in the alert log:

ORA-00600: internal error code, arguments: [kxttUpdateActiveTTSegsCount], [], [], [], [], [], [], [], [], [], [], []

The application is using ojdbc7.jar:12.1.0.2.0.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.