You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Ravi Mutyala (JIRA)" <ji...@apache.org> on 2014/07/10 01:10:04 UTC
[jira] [Created] (AMBARI-6446) ambari upgrade fails in postgresql
if dbname and schemaname are different.
Ravi Mutyala created AMBARI-6446:
------------------------------------
Summary: 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
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)