Bug 877034 - [RHQ] Cannot delete a package in a new created Repositories
[RHQ] Cannot delete a package in a new created Repositories
Status: NEW
Product: RHQ Project
Classification: Other
Component: Content (Show other bugs)
4.4
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-15 10:06 EST by bkramer
Modified: 2012-11-15 10:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 877032
: 877032 (view as bug list)
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description bkramer 2012-11-15 10:06:55 EST
Description of problem:
When Oracle is used as a backend database, attempt to delete newly created package in a repository fails with the following Exception:

Failed to delete packages: [I@7d7cec2f from repository: 10051 Error: javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not execute query

In the rhq-server-log4j.log file the following is logged:

2012-11-15 14:49:19,381 WARN  [org.hibernate.util.JDBCExceptionReporter] SQL Error: 920, SQLState: 42000
2012-11-15 14:49:19,382 ERROR [org.hibernate.util.JDBCExceptionReporter] ORA-00920: invalid relational operator


Version-Release number of selected component (if applicable):
RHQ 4.4
Oracle 

How reproducible:
always

Steps to Reproduce:
1. Navigate to Administration -> Content -> Repositories and create new repository;
2. In the new repository, create new package;
3. Attempt to delete newly created package;
  
Actual results:
Newly created package is not deleted with above Exception

Expected results:
Newly created package is successfully deleted.

Additional info:
Tested the same on Postgres - works fine.

Note You need to log in before you can comment on or make changes to this bug.