Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1ECE117C4D for ; Sun, 17 May 2015 07:54:00 +0000 (UTC) Received: (qmail 5187 invoked by uid 500); 17 May 2015 07:54:00 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 5153 invoked by uid 500); 17 May 2015 07:53:59 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 5141 invoked by uid 99); 17 May 2015 07:53:59 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 May 2015 07:53:59 +0000 Date: Sun, 17 May 2015 07:53:59 +0000 (UTC) From: "Jeff Sposetti (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-6446) ambari upgrade fails in postgresql if dbname and schemaname are different. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Sposetti updated AMBARI-6446: ---------------------------------- Fix Version/s: (was: 2.1.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 > > 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)