Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-19373

Allow use of new Oracle JDBC drivers (ojdbc7)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.10-HF24, 8.10-HF04, 9.1
    • Component/s: Core VCS

      Description

      When migrating to a newer version of Oracle (12c), or maybe of its JDBC drive (ojdbc7), more specific SQL types are returned when introspecting the table's columns. What was returned an indeterminate OTHER may now be returned as a specific NVARCHAR or CLOB.

      Because Nuxeo does checks to ensure that the columns are of the proper type, failures may occur, like:

      SQL type mismatch for "CONTENT"."NAME": expected 12, database has -9 / NVARCHAR2 (2000)
      SQL type mismatch for "COMMENT"."TEXT": expected 2005, database has 2011 / NCLOB (4000)
      SQL type mismatch for "RELATION"."TARGETSTRING": expected 2005, database has 12
      SQL type mismatch for "STORY"."VERSION": expected -5, database has 3 / DECIMAL (38)
      

      java.sql.Type has: -9=NVARCHAR, -5=BIGINT, 3=DECIMAL, 12=VARCHAR, 2005=CLOB, 2011=NCLOB

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 30 minutes
                30m

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.