Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-9732

JDBC store - ORA-00972: identifier is too long

    XMLWordPrintable

Details

    • User Experience
    • Blocks Testing
    • Hide
      git clone git://git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git
      cd eap-tests-hornetq/scripts/
      git checkout f1860bef3e523ad4ef25499554cfb7508f464c53
      groovy -DEAP_VERSION=7.1.0.DR17 PrepareServers7.groovy
      export WORKSPACE=$PWD
      export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap
      export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap
      export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap
      export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap
      
      cd ../jboss-hornetq-testsuite/
      
      mvn clean test -Dtest=JGroupsClusterTestCase#clusterTestWithNetworkFailures -DfailIfNoTests=false -Deap=7x -Dprepare.param.JDBC_STORE=true -Dprepare.param.DATABASE=oracle12c | tee log
      
      Show
      git clone git: //git.app.eng.bos.redhat.com/jbossqe/eap-tests-hornetq.git cd eap-tests-hornetq/scripts/ git checkout f1860bef3e523ad4ef25499554cfb7508f464c53 groovy -DEAP_VERSION=7.1.0.DR17 PrepareServers7.groovy export WORKSPACE=$PWD export JBOSS_HOME_1=$WORKSPACE/server1/jboss-eap export JBOSS_HOME_2=$WORKSPACE/server2/jboss-eap export JBOSS_HOME_3=$WORKSPACE/server3/jboss-eap export JBOSS_HOME_4=$WORKSPACE/server4/jboss-eap cd ../jboss-hornetq-testsuite/ mvn clean test -Dtest=JGroupsClusterTestCase#clusterTestWithNetworkFailures -DfailIfNoTests= false -Deap=7x -Dprepare.param.JDBC_STORE= true -Dprepare.param.DATABASE=oracle12c | tee log

    Description

      Artemis generates identifiers for paging tables using pattern TABLE_NAME + GENERATED ID. Oracle database allows to use only identifiers of maximal length of 30 characters. Generated ID is type of long so it can have size up-to 20 characters what means that maximum length of table name can be only 10 characters. Otherwise error [1] may arises.

      This issue is dangerous because it arises after some time and admin is not advised at start of EAP. EAP/Artemis should do some checks at start and at configuration of these parameters.

      [1]

      SQL STATEMENTS:
      CREATE TABLE NODE2_PAGE_STORE_TABLE6442455442(ID NUMBER(19) GENERATED BY DEFAULT ON NULL AS IDENTITY, FILENAME VARCHAR(255), EXTENSION VARCHAR(10), DATA BLOB, PRIMARY KEY(ID))
      SQL EXCEPTIONS:
      SQLState: 42000 ErrorCode: 972 Message: ORA-00972: identifier is too long
      

      Customer impact: Paging may stop working after some time depending on length of page table name and number of queues.

      Attachments

        Issue Links

          Activity

            People

              mtaylor1@redhat.com Martyn Taylor (Inactive)
              eduda_jira Erich Duda (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: