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

Issue with Nuxeo 5.6 release database connectivity using ojdbc url connection string

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Duplicate
    • Affects Version/s: 5.6-RC1
    • Fix Version/s: 5.6-RC2, 5.6
    • Component/s: Core
    • Tags:
    • Impact type:
      Configuration format change

      Description

      Below issue is occuring for Nuxeo 5.6 Release Candidate

      nuxeo.conf
      =========
      #nuxeo.db.name=
      nuxeo.db.user=RECM_VWA_OWNER
      nuxeo.db.password=RECM_VWA_OWNER
      #nuxeo.db.host=
      nuxeo.db.port=1521
      nuxeo.db.jdbc.url=jdbc:oracle:thin:@//${nuxeo.db.host}:${nuxeo.db.port}/${nuxeo.db.name}
      #nuxeo.db.driver=

      2012-07-26 14:10:21,261 INFO [org.nuxeo.launcher.config.ConfigurationGenerator] Configuration files generated.
      2012-07-26 14:10:21,392 ERROR [org.nuxeo.launcher.config.ConfigurationGenerator] java.sql.SQLException: Listener refused the connection with the following error:
      ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

      However when we updated nuxeo.defaults in templates/oracle and change 'nuxeo.db.jdbc.url=jdbc:oracle:thin:@${nuxeo.db.host}:${nuxeo.db.port}:${nuxeo.db.name}'
      to nuxeo.db.jdbc.url=jdbc:oracle:thin:@${nuxeo.db.host}:${nuxeo.db.port}/${nuxeo.db.name} it works.

      We were not having this issue in Nuxeo 5.5 release

      Please note that we have to use SERVICE NAME and not SID in JDBC URL

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

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