Feedback
Did this article resolve your question/issue?

   

Article

Calls using getImportedKeys() and getExportedKeys() are slow with the Connect for JDBC Oracle driver

Information

 
TitleCalls using getImportedKeys() and getExportedKeys() are slow with the Connect for JDBC Oracle driver
URL NameCalls-using-getImportedKeys-and-getExportedKeys-are-slow-with-the-Connect-for-JDBC-Oracle-driver
Article Number000182615
EnvironmentProduct: Connect for JDBC Oracle driver
Version: All supported versions
OS: JAVA
Database: Oracle
Application: All supported applications
Question/Problem Description
Calls using getImportedKeys() and getExportedKeys() are slow with the Connect for JDBC Oracle driver
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
The query is slower is because by default the CatalogOptions is configured with a value of 2. This means that synonyms are included in catalog calls. 
Resolution
Set CatalogOptions=0 so that result sets will not contain synonyms or remarks. A significant increase in performance of these catalog calls will be noticed. 

For more details about the CatalogOptions connection option, please review this option in the Connect for JDBC User's Guide. 
Workaround
Notes
Last Modified Date1/5/2016 3:30 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.