-
Suggestion
-
Resolution: Fixed
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:
- High-availability clusters can only be connected to using the service name using a newer URL syntax
- 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
- relates to
-
JRACLOUD-29755 Configuration tool should generate thin-style service name Oracle JDBC URLs
- Closed
[JRASERVER-29755] Configuration tool should generate thin-style service name Oracle JDBC URLs
Workflow | Original: JAC Suggestion Workflow [ 3057750 ] | New: JAC Suggestion Workflow 3 [ 3686038 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2612296 ] | New: JAC Suggestion Workflow [ 3057750 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2573894 ] | New: Confluence Workflow - Public Facing v4 [ 2612296 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2354588 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2573894 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2121912 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2354588 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2083316 ] | New: JIRA Bug Workflow w Kanban v6 [ 2121912 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 884791 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2083316 ] |
Description |
Original:
The current JIRA configuration tool generates old-style Oracle JDBC URLs that specify a SID. This can be problematic for two reasons:
# High-availability clusters can only be connected to using the service name using a newer URL syntax # 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 |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-29755]. {panel} The current JIRA configuration tool generates old-style Oracle JDBC URLs that specify a SID. This can be problematic for two reasons: # High-availability clusters can only be connected to using the service name using a newer URL syntax # 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 |
Link |
New:
This issue relates to |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 712246 ] | New: JIRA Bug Workflow w Kanban v6 [ 884791 ] |