RDBPROD: JDBC for Rdb 7.3.0.2 and Rdb Data Provider For .Net 7.3.2.1 Query Performance Bug (Doc ID 1366052.1)

Last updated on JULY 05, 2017

Applies to:

Oracle Rdb Developer Tools for Visual Studio - Version 7.3.2.1 to 7.3.2.1 [Release 7.3]
Oracle JDBC for Rdb - Version 7.3.0.2 to 7.3.0.2 [Release 7.3]
Information in this document applies to any platform.
ORDT V7.3.2.1
JDBC for Rdb V7.3.0.2.


Symptoms

A specific query consumes a lot of CPU, causes a lot of stalls, and sometimes stops the JDBC for Rdb thinserver process.

From the JDBC trace file:

RDB$CLIENT_ID_00000003 C00000000*O 2011-09-23 13:57:21.001 : rdb.JNI@ce5b1c.traceJNI( "** ERROR FOUND " ) RDB$CLIENT_ID_00000003 C00000000*O 2011-09-23 13:57:21.002 : rdb.JNI@ce5b1c.traceJNI( "** in <rdbjdbcsrv:open_cursor>
Lost connection to executor RDBJDBC00139C61_00000003 SQSNRH100000003 >> status = 0x056EE024 SQLstate = 08006" )

The issue is specific to a table with a large number of columns (249 in one case), but more importantly a high number of metadata field versions, i.e. the field definitions have been modified many many times.

The problem query is generated by ORDT 7.3.2.1 but executed on the JDBC server on OpenVMS.

Changes

The bug was noticed after upgrading to ORDT 7.3.2.1 and JDBC 7.3.0.2.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms