[
https://issues.apache.org/jira/browse/AMBARI-17622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15367926#comment-15367926
]
Hadoop QA commented on AMBARI-17622:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12816814/AMBARI-17622_2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServicePropertiesTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7740//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7740//console
This message is automatically generated.
> Ambari server schema upgrade failed from 2.1.1 with ORA-12516 error
> -------------------------------------------------------------------
>
> Key: AMBARI-17622
> URL: https://issues.apache.org/jira/browse/AMBARI-17622
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
> Affects Versions: 2.4.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Blocker
> Fix For: 2.4.0
>
> Attachments: AMBARI-17622_2.patch
>
>
> Steps
> Deploy HDP-2.3.0.0 cluster with Ambari 2.1.1 (Oracle DB, unsecure, HA
> cluster). Note - the DB instance is dedicated for this cluster and Ambari
> server and not shared
> Upgrade Ambari to 2.4.0.0-726.x86_64
> Result
> Error during Ambari DB schema upgrade. Logs show the below
> {code}
> 01 Jul 2016 11:47:17,686 ERROR [main] DBAccessorImpl:107 - Error while
> creating database accessor
> java.sql.SQLException: Listener refused the connection with the following
> error:
> ORA-12516, TNS:listener could not find available handler with matching
> protocol stack
>
> at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:419)
> at
> oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:536)
> at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:228)
> at
> oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
> at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)
> at java.sql.DriverManager.getConnection(DriverManager.java:571)
> at java.sql.DriverManager.getConnection(DriverManager.java:215)
> at
> org.apache.ambari.server.orm.DBAccessorImpl.<init>(DBAccessorImpl.java:87)
> 01 Jul 2016 11:47:17,697 ERROR [main] DBAccessorImpl:107 - Error while
> creating database accessor
> java.sql.SQLException: Listener refused the connection with the following
> error:
> ORA-12516, TNS:listener could not find available handler with matching
> protocol stack
>
> at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:419)
> at
> oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:536)
> 01 Jul 2016 11:47:17,699 ERROR [main] SchemaUpgradeHelper:369 - Unexpected
> error, upgrade failed
> com.google.inject.ProvisionException: Guice provision errors:
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
