| Summary: | Schema tool extensions required for Oracle RAC | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Julian Coleman <jcoleman> |
| Component: | Tooling | Assignee: | Zuzana Zoubkova <zzoubkov> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0.0 GA | ||
| Target Milestone: | --- | ||
| Target Release: | 5.0.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-1981 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-05-31 10:32:23 UTC | Type: | Task |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Link: Added: This issue is related to SOA-1970 Extension committed in revision 5612. Verified in CR1 This is the draft text for the Release Notes: https://jira.jboss.org/jira/browse/SOA-1970 Previously, the Schema tool would only support a limited number of databases. It has now been enhanced and, as a result, supports these second-tier databases: • MySQL 5.0 • PostgreSQL 8.2.4 • Microsoft SQL Server 2008 • Oracle 11g Sorry, the note above was for SOA 1971. Draft for SOA 1981 reads: https://jira.jboss.org/jira/browse/SOA-1981 The Oracle RAC required URLs to be presented in a specific format, which the Schema tool was unable to handle. Extensions have been added to the tool to provide compatibility with this format. |
Affects: Compatibility/Configuration Date of First Response: 2010-05-14 10:49:43 project_key: SOA Oracle RAC requires a DB URL of the form: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=ON)(ADDRESS=(PROTOCOL=TCP)(HOST=host1.some.domain)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=host2.some.domain)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=${db}))) where there are multiple instances of (HOST=)(PORT=) pairs. The schema tool needs to be expanded to handle this.