Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-29755

Configuration tool should generate thin-style service name Oracle JDBC URLs

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      The current JIRA configuration tool generates old-style Oracle JDBC URLs that specify a SID. This can be problematic for two reasons:

      1. High-availability clusters can only be connected to using the service name using a newer URL syntax
      2. The Oracle documentation says that the old syntax is no longer supported as of 10g

      Please update the configuration tool to generate the service name type URLs. Right now customers like us who are using HA configurations are forced to edit dbconfig.xml by hand.

      More info:
      http://docs.oracle.com/cd/E11882_01/java.112/e16548/urls.htm#BEIDHCBA
      http://www.orafaq.com/wiki/JDBC#Thin_driver

            [JRASERVER-29755] Configuration tool should generate thin-style service name Oracle JDBC URLs

            Mark Lassau (Inactive) added a comment -

            Confirmed that the new syntax is suitable for both SID and Service Name.

            Config Tool and web SetupDatabase.jspa both use this new syntax for creating URLs but can read either old or new syntax.

            Mark Lassau (Inactive) added a comment - Confirmed that the new syntax is suitable for both SID and Service Name. Config Tool and web SetupDatabase.jspa both use this new syntax for creating URLs but can read either old or new syntax.

            Lars Hannelius added a comment -

            I admit that the Oracle documentation isn't very clear on this but it does say that

            Starting Oracle Database 10g, Oracle Service IDs are not supported.

            and makes no mention of the old syntax. My guess is that the new syntax will work with all 10g+ versions but of course I understand that you have to verify this.

            Lars Hannelius added a comment - I admit that the Oracle documentation isn't very clear on this but it does say that Starting Oracle Database 10g, Oracle Service IDs are not supported. and makes no mention of the old syntax. My guess is that the new syntax will work with all 10g+ versions but of course I understand that you have to verify this.

            Mark Lassau (Inactive) added a comment - - edited

            My biggest concern is with how to handle legacy customers.
            That is, for existing customers that have configured JIRA to use SID, they need to continue to work even after they run the config tool to make other config changes, and also be able to convert to using Service Name if and when they want to.
            According to the linked FAQ http://www.orafaq.com/wiki/JDBC#Thin_driver , the new syntax allows one to specify either SID or service name.
            This needs to be confirmed, but if it is true then dealing with legacy customers will be relatively easy - we need to read either the old or new syntax but we only write the new syntax.

            The Oracle documentation says that the old syntax is no longer supported as of 10g

            lars.hannelius / lars.hannelius@nordea.com
            Can you please point to where the documentation says this?
            I can't see this stated in either of the URLs you posted.

            Mark Lassau (Inactive) added a comment - - edited My biggest concern is with how to handle legacy customers. That is, for existing customers that have configured JIRA to use SID, they need to continue to work even after they run the config tool to make other config changes, and also be able to convert to using Service Name if and when they want to. According to the linked FAQ http://www.orafaq.com/wiki/JDBC#Thin_driver , the new syntax allows one to specify either SID or service name. This needs to be confirmed, but if it is true then dealing with legacy customers will be relatively easy - we need to read either the old or new syntax but we only write the new syntax. The Oracle documentation says that the old syntax is no longer supported as of 10g lars.hannelius / lars.hannelius@nordea.com Can you please point to where the documentation says this? I can't see this stated in either of the URLs you posted.

            Lars Hannelius added a comment -

            It's been over 1 year and the problem is still there in JIRA 6.1.3. Aren't you going to fix it?

            Lars Hannelius added a comment - It's been over 1 year and the problem is still there in JIRA 6.1.3. Aren't you going to fix it?

              mlassau Mark Lassau (Inactive)
              35ff593b8f05 Lars Hannelius
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: