[ https://issues.apache.org/jira/browse/AMBARI-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yusaku Sako updated AMBARI-6446: -------------------------------- Fix Version/s: (was: 1.7.0) 2.0.0 > 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 > Fix For: 2.0.0 > > > 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.3.4#6332)