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

Bug 1118463

Summary: Database Logging: Problems with Oracle
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Thomas Hauser <thauser>
Component: TeiidAssignee: Van Halbert <vhalbert>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: dlesage, jstastny, vhalbert
Target Milestone: ER2Keywords: QA-Closed
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Attempting to use Oracle as the backing database for the logging datasource resulted in errors during table creation. This was fixed by changing the ID generation type from IDENTITY to AUTO. As a result, you can now use Oracle as your logging database.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-10 08:48:57 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:
Attachments:
Description Flags
Full server.log of failed startup none

Description Thomas Hauser 2014-07-10 19:15:57 UTC 
Created attachment 917163 [details]
Full server.log of failed startup

Description of problem:
Attempting to use Oracle as the backing database for the logging datasource results in errors during table creation.

Version-Release number of selected component (if applicable):
6.1.0 DR1

How reproducible:
Always

Steps to Reproduce:
1. Install DV using the (upcoming) DR2 DV installer.
2. Elect to install an oracle JDBC driver and to configure database logging
3. Enter details for the oracle database in the following panel.
4. Install will complete successfully.

Actual results:
The following stacktrace is received during DV startup: 
http://pastebin.test.redhat.com/220854

Expected results:
The tables are created in the database and commands are logged.

Additional info:
The driver used was the following: 
http://www.qa.jboss.com/jdbc-drivers-products/jdbc/EAP/6.3.0/oracle11gR2/jdbc4/ojdbc6.jar
MD5: f382d7d3332ba400a644244923b47c66

Note that this driver is 11gR2, and the Hibernate Dialect used is 10g. This could be the source of the issue.