Bug 1175304 - Database Logging: Problems with DB2
Summary: Database Logging: Problems with DB2
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Van Halbert
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-17 13:20 UTC by Jan Stastny
Modified: 2014-12-22 14:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-19 06:12:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
stacktrace (10.84 KB, text/plain)
2014-12-17 13:20 UTC, Jan Stastny
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-3262 0 Major Closed Database Logging: Problems with DB2 2017-11-21 09:31:47 UTC

Description Jan Stastny 2014-12-17 13:20:38 UTC
Created attachment 970106 [details]
stacktrace

When during installation I chose to install DB2 driver and enable db logging, installation completed fine.

When I attempted to start the server an error occurs when deploying dashboard builder war:

13:02:15,237 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 56) HHH000389: Unsuccessful: create table commandlog (id bigint not null, applicationname varchar(255), executionid varchar(50), modelname varchar(255), principal varchar(50), queryplan blob(255), requestid varchar(50), row_count integer, sessionid varchar(50), sourcecommand smallint, sourcerequestid bigint, sqlcmd varchar(8196), eventtype varchar(10), logtime timestamp, transactionid varchar(256), translatorname varchar(50), vdbname varchar(255), vdbversion integer, primary key (id))
13:02:15,238 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (ServerService Thread Pool -- 56) DB2 SQL Error: SQLCODE=-286, SQLSTATE=42727, SQLERRMC=16384;DBALLO00, DRIVER=4.12.55

Furthermore, when command logging is turned on, with each query on a vdb, a long stacktrace is produced. The snippet of the stacktrace is in the attached file.

Comment 1 JBoss JIRA Server 2014-12-19 06:18:27 UTC
Jan Stastny <jstastny> updated the status of jira TEIID-3262 to Closed


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