Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: 1.1
    • Fix Version/s: 1.4.1
    • Component/s: Data Management
    • Labels:
      None
    • Environment:
      An Oracle DB
    • Complexity:
      Intermediate
    • Patch Submitted:
      Yes
    • Number of attachments :
      2

      Description

      Continuum is not able to run against an Oracle DB.

      I have attached a patch that should be included in next releases in continuum in order to support Oracle DB. Should be packed in continuum-model-x.y.jar

      Workaround till next release with this pacth applied:
      1. copy the attached file into WEB-INF/classes/ dir
      2. edit the application.xml and change the value of javax.jdo.option.Mapping property to oracle (you may have to make available this property)
      <property>
      <name>javax.jdo.option.Mapping</name>
      <value>oracle</value>
      </property>
      3. edit your context.xml file or whatever you use in order to set the oracle settings:
      <Resource name="jdbc/users"
      auth="Container"
      type="javax.sql.DataSource"
      username="continuum"
      password="s3cr3t"
      driverClassName="oracle.jdbc.driver.OracleDriver"
      url="jdbc:oracle:thin:@192.168.1.25:1521:BDD01" />

      <Resource name="jdbc/continuum"
      auth="Container"
      type="javax.sql.DataSource"
      username="continuum"
      password="s3cret"
      driverClassName="oracle.jdbc.driver.OracleDriver"
      url="jdbc:oracle:thin:@192.168.1.25:1521:BDD01" />

      4. copy ojdbc14.jar into the classpath (TOMCAT_HOME/common/lib or WEB-INF/lib)

      Tested with Oracle 10g

      1. package-oracle.orm
        1 kB
        Arun Nachimuthu
      2. package-oracle.orm
        1 kB
        Raul Casado Piqueras

        Issue Links

          Activity

          Hide
          Olivier Dassaud added a comment -

          Hello,

          We had the same problem when using Continuum 1.1 and Oracle 10.2.0 XE.

          FYI we used to solve it changing "stash.maxSize" superior to 4000 bytes to 4000 value, in the following files :

          \src\continuum-data-management\continuum-legacy\src\main\mdo\continuum.xml
          \src\continuum-model\src\main\mdo\continuum.xml
          \src\main\mdo\continuum-service.xml

          But, I think that the way that Raul is a better one.

          Olivier.

          Show
          Olivier Dassaud added a comment - Hello, We had the same problem when using Continuum 1.1 and Oracle 10.2.0 XE. FYI we used to solve it changing "stash.maxSize" superior to 4000 bytes to 4000 value, in the following files : \src\continuum-data-management\continuum-legacy\src\main\mdo\continuum.xml \src\continuum-model\src\main\mdo\continuum.xml \src\main\mdo\continuum-service.xml But, I think that the way that Raul is a better one. Olivier.
          Hide
          Wendy Smoak added a comment -

          Is this still a problem with the latest release?

          Show
          Wendy Smoak added a comment - Is this still a problem with the latest release?
          Hide
          Brett Porter added a comment -

          I believe there have been some patches submitted on list

          Show
          Brett Porter added a comment - I believe there have been some patches submitted on list
          Hide
          Arun Nachimuthu added a comment -

          There is a new table called ProjectScmRoot in version 1.3.x and 1.4.x which has error column greater than 4000 chars in size. Attached is the updated package-oracle.orm file.

          Show
          Arun Nachimuthu added a comment - There is a new table called ProjectScmRoot in version 1.3.x and 1.4.x which has error column greater than 4000 chars in size. Attached is the updated package-oracle.orm file.
          Hide
          Brett Porter added a comment -

          There was an error in the patch - ProjectScmRoot is in a different package. I copied package-mssql.orm instead which is identical. For those on older versions, you could use mssql in application.xml as a workaround.

          Show
          Brett Porter added a comment - There was an error in the patch - ProjectScmRoot is in a different package. I copied package-mssql.orm instead which is identical. For those on older versions, you could use mssql in application.xml as a workaround.

            People

            • Assignee:
              Brett Porter
              Reporter:
              Raul Casado Piqueras
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: