Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 974186

Summary:	SQLSyntaxErrorException while installing/upgrading jon to 4.8 with oracle db
Product:	[JBoss] JBoss Operations Network	Reporter:	Armine Hovsepyan <ahovsepy>
Component:	Installer	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED WORKSFORME	QA Contact:	Mike Foley <mfoley>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	JON 3.2	CC:	jshaughn, mfoley
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-06-18 15:52:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	951619

Description Armine Hovsepyan 2013-06-13 15:21:35 UTC

Description of problem:
It is not possible to install/upgrade jon to rhq 4.8 for oracle db

Version-Release number of selected component (if applicable):
rhq master build  741

How reproducible:
always

Steps to Reproduce:
1. install jon 3.1.2 (server and agent) with oracle db
2. unzip rhq4.8 master version
3. run rhqcrl install or upgrade (with corresponding params)

Actual results:
SQLSyntaxErrorException while installing/upgrading jon to 4.8 with oracle db

Expected results:
rhq4.8 installed/upgraded

Additional info:
exception log here -> http://d.pr/f/na3e

Comment 1 Jay Shaughnessy 2013-06-17 16:37:46 UTC

Asking Armine to re-test as there is no evidence that the current code would cause  an issue.  It may have been environmental or the result of a temporary issue with the schema-spec version.

Comment 2 Armine Hovsepyan 2013-06-18 15:52:53 UTC

Re-tested with the same environment and another environment with default oralce xe db and with altered table-spaces.
Both worked. Don't know the issue (last time 2 envs were failing).
Closing bug as works-for-me.