Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-4148

Support connecting to Oracle with SID or TNS name

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Database - Oracle
    • None
    • 13
    • We collect Bitbucket 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.

      Currently Stash supports connecting to an Oracle DB only using a service name. It would be nice to allow a TNS name or a SID to be specified.

            [BSERV-4148] Support connecting to Oracle with SID or TNS name

            James Brown added a comment -

            Just updated database from Oracle 12.1.0.2 to Oracle 12.2.0.1 and was unable to connect to database because of this issue. If the best pratice is to provide this configuration by Oracle, then please support this configuration.

            James Brown added a comment - Just updated database from Oracle 12.1.0.2 to Oracle 12.2.0.1 and was unable to connect to database because of this issue. If the best pratice is to provide this configuration by Oracle, then please support this configuration.

            thomas cogswell added a comment -

            the Atlassian stack should be consistent in deployment models, filing names, drivers, configs.. seems like each product has its own model for configuring the DB, app and web tiers..

            thomas cogswell added a comment - the Atlassian stack should be consistent in deployment models, filing names, drivers, configs.. seems like each product has its own model for configuring the DB, app and web tiers..

            Peter Koczan (Inactive) added a comment -

            Agreed, but as long as we support versions of the DB that offer this method, we should also include it. Moreover, such is not causing any pain for JIRA and Confluence for example, so Stash should be able to deal with it, as many people would go for multiple Atlassian products. Just for the sake of universal handling of them, I think we should provide this.

            Peter Koczan (Inactive) added a comment - Agreed, but as long as we support versions of the DB that offer this method, we should also include it. Moreover, such is not causing any pain for JIRA and Confluence for example, so Stash should be able to deal with it, as many people would go for multiple Atlassian products. Just for the sake of universal handling of them, I think we should provide this.

            jhinch (Atlassian) added a comment -

            SIDs as considered deprecated in Oracle in favour of service names. SIDs only exist in Oracle for backwards compatibility.

            jhinch (Atlassian) added a comment - SIDs as considered deprecated in Oracle in favour of service names. SIDs only exist in Oracle for backwards compatibility.

              Unassigned Unassigned
              pkoczan Peter Koczan (Inactive)
              Votes:
              13 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated: