You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2017/10/18 20:50:01 UTC
[jira] [Commented] (AMBARI-22267) Version registration failure
during patch upgrade + Debian + Oracle run
[ https://issues.apache.org/jira/browse/AMBARI-22267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16210004#comment-16210004 ]
Jonathan Hurley commented on AMBARI-22267:
------------------------------------------
{code}
SELECT DISTINCT
t0.repo_version_id, t0.display_name, t0.hidden, t0.legacy, t0.repositories, t0.resolved, t0.repo_type, t0.version, t0.version_url,
t0.version_xml, t0.version_xsd, t0.parent_id, t0.stack_id
FROM repo_version t0, servicedesiredstate t1
WHERE ((t1.desired_repo_version_id IN ?) AND (t0.repo_version_id = t1.desired_repo_version_id))
{code}
I'm guessing that Oracle doesn't like the {{DISTINCT}} on the {{clob}} fields ...
> Version registration failure during patch upgrade + Debian + Oracle run
> -----------------------------------------------------------------------
>
> Key: AMBARI-22267
> URL: https://issues.apache.org/jira/browse/AMBARI-22267
> Project: Ambari
> Issue Type: Bug
> Components: ambari-upgrade
> Affects Versions: 2.6.0
> Environment: ambari-server --version 2.6.0.0-236
> ambari DB : Oracle
> Reporter: Supreeth Sharma
> Assignee: Jonathan Hurley
> Priority: Blocker
> Labels: patch-upgrade
> Fix For: 2.6.0
>
> Attachments: 4th-digit.xml, ambari.log
>
>
> Live cluster :http://172.27.58.135:8080
> Test steps :
> 1) Install ambari 2.5.2 with HDP-2.6.2.0-205
> 2) Upgrade ambari to 2.6.0.0-236
> 3) Run EU and upgrade stack to 2.6.3.0-205
> 4) Now try to register the VDF for PU and version registration is failing.
> read version info api : http://172.27.58.135:8080/api/v1/version_definitions?skip_url_check=true&dry_run=true is throwing 500 server error and failing with below error :
> {code}
> Error Code: 932
> Call: SELECT DISTINCT t0.repo_version_id, t0.display_name, t0.hidden, t0.legacy, t0.repositories, t0.resolved, t0.repo_type, t0.version, t0.version_url, t0.version_xml, t0.version_xsd, t0.parent_id, t0.stack_id FROM repo_version t0, servicedesiredstate t1 WHERE ((t1.desired_repo_version_id IN (?,?)) AND (t0.repo_version_id = t1.desired_repo_version_id))
> bind => [2 parameters bound]
> Query: ReportQuery(name="findByServiceDesiredVersion" referenceClass=ServiceDesiredStateEntity sql="SELECT DISTINCT t0.repo_version_id, t0.display_name, t0.hidden, t0.legacy, t0.repositories, t0.resolved, t0.repo_type, t0.version, t0.version_url, t0.version_xml, t0.version_xsd, t0.parent_id, t0.stack_id FROM repo_version t0, servicedesiredstate t1 WHERE ((t1.desired_repo_version_id IN ?) AND (t0.repo_version_id = t1.desired_repo_version_id))")
> 18 Oct 2017 19:50:10,308 WARN [ambari-client-thread-17969] ServletHandler:561 - Error Processing URI: /api/v1/version_definitions - (javax.persistence.PersistenceException) Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00932: inconsistent datatypes: expected - got CLOB
> {code}
> Attaching the complete log and vdf file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)