RDBPROD: JDBC for Rdb 188.8.131.52 and Rdb Data Provider For .Net 184.108.40.206 Query Performance Bug
(Doc ID 1366052.1)
Last updated on MAY 03, 2018
Applies to:Oracle Rdb Developer Tools for Visual Studio - Version 220.127.116.11 to 18.104.22.168 [Release 7.3]
Oracle JDBC for Rdb - Version 22.214.171.124 to 126.96.36.199 [Release 7.3]
Information in this document applies to any platform.
JDBC for Rdb V188.8.131.52.
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:
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 184.108.40.206 but executed on the JDBC server on OpenVMS.
The bug was noticed after upgrading to ORDT 220.127.116.11 and JDBC 18.104.22.168.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document