SAP Knowledge Base Article - Preview

2579943 - Set commands executed with java.sql.PreparedStatement may not remain in effect - SAP SDK for ASE

Symptom

  • In jConnect, when the DYNAMIC_PREPARE connection property is set to true, executing the set command using java.sql.PreparedStatement does not have a lasting effect.
  • For example, you execute "set transaction isolation level 0" by using PreparedStatement and then execute a SELECT query.
  • The SELECT query should return a result set without being blocked because it's a dirty read, but in fact it can be blocked by another process holding an exclusive lock.
  • This is more likely to occur after you upgrade your jConnect to 7.0 ESD#3 or later.


Read more...

Environment

  • SAP Sybase Software Developer Kit (SDK) 15.7 ESD
  • SAP Sybase Software Developer Kit (SDK) 15.7 SP
  • SAP Adaptive Server Enterprise (ASE) Software Developer Kit (SDK) 16.0 SP
  • jConnect 
    • JDBC 7.x
    • JDBC 16.0 (is version JDBC 7.07)

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0

Keywords

DYNAMIC_PREPARE, PreparedStatement, jconn3, jconn3.jar, jconn4, jconn4.jar , KBA , BC-SYB-SDK , SDK , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.