Bug 722298 - dbreset Not Implemented for Oracle Databases
Summary: dbreset Not Implemented for Oracle Databases
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Database
Version: 4.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Stefan Negrea
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: rhq41beta
TreeView+ depends on / blocked
 
Reported: 2011-07-14 20:51 UTC by Stefan Negrea
Modified: 2012-02-07 19:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-07 19:20:50 UTC
Embargoed:


Attachments (Terms of Use)

Description Stefan Negrea 2011-07-14 20:51:36 UTC
Currently dbreset is not implemented for Oracle databases. This functionality is required in clear the entire database (remove all the tables and data) in one single step at build time.

Comment 1 Charles Crouch 2011-08-03 16:25:02 UTC
Marking this as urgent, since its required to get our dbupgrade integration tests running consistently on oracle

Comment 2 Stefan Negrea 2011-08-04 21:59:41 UTC
Updated dbreset code to support Oracle and PostgreSQL. 

dbreset is implemented as follows:
1) PostgreSQL - dropping the database and recreate it with rhq user as the owner.
2) Oracle - drop every single object in the user space. Temporary objects used by Oracle are not dropped.

dbreset throws an exception if the user attempts to use it with any other type of database.

The code successfully passed unit and integration testing for PostgreSQL and Oracle (10g and 11g).

Comment 3 Mike Foley 2011-08-09 20:39:52 UTC
verification criteria is passing hudson job on oracle.

Comment 4 Mike Foley 2012-02-07 19:20:50 UTC
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE


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