You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2015/02/10 21:45:11 UTC
[jira] [Resolved] (AMBARI-9537) Ambari is dead after upgrade
1.4.4->2.0.0 OracleDB
[ https://issues.apache.org/jira/browse/AMBARI-9537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmytro Sen resolved AMBARI-9537.
--------------------------------
Resolution: Fixed
Committed to trunk
> Ambari is dead after upgrade 1.4.4->2.0.0 OracleDB
> --------------------------------------------------
>
> Key: AMBARI-9537
> URL: https://issues.apache.org/jira/browse/AMBARI-9537
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Environment: HDP Stack: 2.0
> Ambari DB: :Oracle
> Oozie/Hive DB: /
> Security:no
> HA: no
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Fix For: 2.0.0
>
>
> Multiple errors after ambari upgrade, like:
> {code}
> Error Code: 904
> Call: SELECT cluster_id, cluster_info, cluster_name, desired_cluster_state, desired_stack_version, provisioning_state, security_type, resource_id FROM clusters
> Query: ReadAllQuery(name="allClusters" referenceClass=ClusterEntity sql="SELECT cluster_id, cluster_info, cluster_name, desired_cluster_state, desired_stack_version, provisioning_state, security_type, resource_id FROM clusters")
> at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:333)
> at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:646)
> at org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:537)
> at org.eclipse.persistence.internal.sessions.AbstractSession.basicExecuteCall(AbstractSession.java:1805)
> at org.eclipse.persistence.sessions.server.ServerSession.executeCall(ServerSession.java:566)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)