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): JON 3.1.1 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.
This seems to work fine with Oracle 11g, which is the minimum supported version for JON 3.3. Tested both with RHQ 4.12.0-SNAPSHOT and JON 3.2.1.
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993
Created attachment 924197 [details] before-deletion
Created attachment 924198 [details] delete-button-click
Created attachment 924199 [details] after-deletion
verified in jon 3.3 dr1 screen-shots attached
Looks like this shouldn't have made it this far. Based on comment 2 I believe this BZ should have been CLOSED WONTFIX as it applies to 3.1 and earlier. If anyone disagrees, please re-open the bug with your logic/reasoning. For clarity: WONTFIX: This issue does not occur in Oracle Database 11g which is the earliest supported Oracle Database version beginning with JBoss ON 3.2. Oracle Database 10g was deprecated in JBoss ON 3.0 and support for it was removed in JBoss ON 3.2. As 3.2 is the latest maintenance version of JBoss ON, this issue will not be fixed for previous releases of JBoss ON.