Uploaded image for project: 'Red Hat Data Grid'
  1. Red Hat Data Grid
  2. JDG-1461

INVM JDBC CacheStore failing upsert on DB2 105

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • JDG 7.2 ER3
    • JDG 7.2 ER1, JDG 7.2 ER3
    • Core
    • None
    • ER3
    • Reopened by mistake
    • Hide

      1. Clone https://github.com/infinispan/jdg-functional-tests (branch master)
      2. Allocate DB using this link: http://dballocator.mw.lab.eng.bos.redhat.com:8080/Allocator/AllocatorServlet?operation=allocate&expression=db2_105%26%26geo_BOS&expiry=1440&requestee=GUI (keep open for later reference)
      3. Download driver from http://www.qa.jboss.com/jdbc-drivers-products/EAP/7.1.0/db2-105/jdbc4/db2jcc4.jar
      4. Download and unpack EAP server 7.0.7 into a folder from http://download.eng.brq.redhat.com/released/JBEAP-7/7.0.7/jboss-eap-7.0.7-full-build.zip
      5. Go to jdg-functional-tests/invm/jdbc-cache-store/
      6. Fill in appropriate values into command and run:

      mvn clean verify -U -Dmaven.test.failure.ignore=true -Ddatabase=db2-105 -Ddriver.dir={DRIVER_DIRECTORY}  -Ddriver.jar=db2jcc4.jar -Ddriver.class=com.ibm.db2.jcc.DB2Driver -Dconnection.url={CONECTION_URL_FROM_DB_ALLOCATOR(do not forget to remove "\")} -Ddb.username={DB_USERNAME} -Ddb.password={DB_PASSWORD} -Dfile.log.level=INFO  -Peap7 -Deap.home={EAP_INSTALLATION_PATH} -Ddb.schema={DB_SCHEMA}
      Show
      1. Clone https://github.com/infinispan/jdg-functional-tests (branch master) 2. Allocate DB using this link: http://dballocator.mw.lab.eng.bos.redhat.com:8080/Allocator/AllocatorServlet?operation=allocate&expression=db2_105%26%26geo_BOS&expiry=1440&requestee=GUI (keep open for later reference) 3. Download driver from http://www.qa.jboss.com/jdbc-drivers-products/EAP/7.1.0/db2-105/jdbc4/db2jcc4.jar 4. Download and unpack EAP server 7.0.7 into a folder from http://download.eng.brq.redhat.com/released/JBEAP-7/7.0.7/jboss-eap-7.0.7-full-build.zip 5. Go to jdg-functional-tests/invm/jdbc-cache-store/ 6. Fill in appropriate values into command and run: mvn clean verify -U -Dmaven.test.failure.ignore= true -Ddatabase=db2-105 -Ddriver.dir={DRIVER_DIRECTORY} -Ddriver.jar=db2jcc4.jar -Ddriver.class=com.ibm.db2.jcc.DB2Driver -Dconnection.url={CONECTION_URL_FROM_DB_ALLOCATOR( do not forget to remove "\" )} -Ddb.username={DB_USERNAME} -Ddb.password={DB_PASSWORD} -Dfile.log.level=INFO -Peap7 -Deap.home={EAP_INSTALLATION_PATH} -Ddb.schema={DB_SCHEMA}

    Description

      JDBC CacheStore Passivating data into Oracle 12c RAC DB will fail with following error (Full stacktrace in attachment):

      org.infinispan.persistence.spi.PersistenceException: Error while storing string key to database; key: 'k1'
      at org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore.write(JdbcStringBasedStore.java:128)
      at org.infinispan.persistence.manager.PersistenceManagerImpl.lambda$writeToAllNonTxStores$9(PersistenceManagerImpl.java:514)
      ...
      at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
      Caused by: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-203, SQLSTATE=42702, SQLERRMC=DATUM, DRIVER=4.19.66
      at com.ibm.db2.jcc.am.kd.a(kd.java:747)
      ...
      at infinispan.com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeUpdate(NewProxyPreparedStatement.java:1423)
      at org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore.executeUpsert(JdbcStringBasedStore.java:160)
      at org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore.write(JdbcStringBasedStore.java:145)

      This particular test was ran on EAP modules, however I have reasons to believe the issue affects all connections to DB2 databases

      Attachments

        Issue Links

          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ISPN-8758 DB2 Upsert and Indexing errors

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              remerson@redhat.com Ryan Emerson
              zhostasa_jira Zdenek Hostasa (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: