ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaimin D Jetly (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14067) wrong DB_JDBC_PATTERNS for Oracle DBs in app.js
Date Wed, 25 Nov 2015 18:17:11 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-14067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15027311#comment-15027311
] 

Jaimin D Jetly commented on AMBARI-14067:
-----------------------------------------

[~mathu]
This was a known issue in Ambari-2.1.1. It was fixed in Ambari-2.1.2 with a refactoring work
in regards to handling database config properties in ambari-web.
I verified that Ambari-2.1.3 has not regressed and this issue does not exist in Ambari-2.1
branch (deb3f33d364bd8d5ce1b99568e1cb7332eb38e80 hash).

I am resolving this issue as already fixed. Feel free to reopen this issue if you can reproduce
it on trunk or branch-2.1



> wrong DB_JDBC_PATTERNS for Oracle DBs in app.js
> -----------------------------------------------
>
>                 Key: AMBARI-14067
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14067
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.0, 2.1.1, Ambari-2.1.3
>         Environment: Oracle JDBC configuration for Hive and Oozie
>            Reporter: Mathias Herzog
>            Priority: Critical
>
> Hi
> The Web configuration page for HIVE, YARN and Oozie doesn't render (remains white) and
the console shows following error:
> Uncaught TypeError: Cannot read property 'replace' of null -> 
> this issue happens because of wrong DB_JDBC_PATTERNS if one of the following configurations
are present for oozie and hive 
> dbType = oracle and dbPort != 1521
> or
> dbTyppe = Oracle-RAC
> In this case, the connection string looks like:
> jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=host1.example.com)(PORT=1532))
(ADDRESS=(PROTOCOL=TCP)(HOST=host2.example.com)(PORT=1532)))(CONNECT_DATA=(SERVICE_NAME=service.X.example.com)))
> suggested fix in database.js
> 1. change port in oracle pattern from 1521 to something generic
> 2. add a new pattern for oracle RAC databases
> 3. maybe fix the port issue for postgres as well (couldn't test that)
> {code:title=app.js|borderStyle=solid}
>   DB_JDBC_PATTERNS: {
>     mysql: 'jdbc:mysql://{0}/{1}',
>     mssql: 'jdbc:sqlserver://{0};databaseName={1}',
>     postgres: 'jdbc:postgresql://{0}:5432/{1}',
>     derby: 'jdbc:derby:{0}/{1}',
>     oracle: 'jdbc:oracle:thin:@(?:\/?\/?)(.*):[0-9]+(:|\/)(.*)',
>     rac: 'jdbc:oracle:thin:@(?:\/?\/?).*HOST=(\\S*?)\\)\\S+PORT=(\\S*?)\\)\\S+SERVICE_NAME=(\\S*?)\\)',
>     sqla: 'jdbc:sqlanywhere:host={0};database={1}'
>   },
> {code}
> kind regards
> Mathias



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message