ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (AMBARI-6446) ambari upgrade fails in postgresql if dbname and schemaname are different.
Date Thu, 10 Jul 2014 00:00:09 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Siddharth Wagle reassigned AMBARI-6446:
---------------------------------------

    Assignee: Myroslav Papirkovskyy  (was: Siddharth Wagle)

[~mpapirkovskyy] Can you take a look at this ?

> ambari upgrade fails in postgresql if dbname and schemaname are different. 
> ---------------------------------------------------------------------------
>
>                 Key: AMBARI-6446
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6446
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.6.0
>         Environment: centos6, postgresql 8.4
>            Reporter: Ravi Mutyala
>            Assignee: Myroslav Papirkovskyy
>
> ambari-server upgrade fails with error "schema ambari141 does not exist". DBName in this
setup is ambari141 but schema name is ambari. 
> ambari.properties had 
> server.jdbc.dbname=ambari141
> server.jdbc.schema=ambari
> Workaround: I altered all ambari tables from schema ambari to ambari141



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message