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

Bug 1082871

Summary: JDBC Importer fails when importing Access 2013 metadata via JDBC ODBC bridge
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Anu Saji <asaji>
Component: ToolingAssignee: Barry LaFond <blafond>
Status: CLOSED NOTABUG QA Contact: Andrej Smigala <asmigala>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: atangrin, mbaluch, mmakovy, vhalbert
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-05 08:03: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
Image file showing tables not being listed while importing the DB(MS-ACCESS) using JDBC none

Description Anu Saji 2014-04-01 02:32:34 UTC
Created attachment 881187 [details]
Image file showing tables not being listed while importing the DB(MS-ACCESS) using JDBC

Description of problem:
Unable to import metadata from MS-ACCESS in to the Teiid designer.


Version-Release number of selected component (if applicable):
-Tooling
  JBDS 7.x
- Customer has tested this on MS-Access 2000, MS-Access 2010 and MS-Access 2013
- Windows 7 Professional on Desktop, 
- Windows Server 2008 R2 Standard on server.


How reproducible:

1. Create a JDBC ODBC bridge connection profile (class: sun.jdbc.odbc.JdbcOdbcDriver)
2.   Try  importing using JDBC importer, no tables are shown



Actual results:
****************
Attaching No_ODBC_metadata.pdf (from client sent file)
No tables listed.

Expected results:
*****************
While importing the database via JDBC, there should be a list of tables created in MS-ACCESS

Additional info:

Comment 3 Barry LaFond 2015-03-25 11:08:08 UTC
The work-around should be the suggested path for users connecting to MS Access since Teiid exposes applicable importer properties to properly import desired tables.  Recommend we cover this in the doc, if we haven't already and close this issue as resolved?

Comment 4 Marek Baluch 2015-06-11 06:00:08 UTC
Barry, given comment #2 - Documenting the workaround should in my opinion be sufficient.

Comment 5 Matus Makovy 2016-02-05 08:03:57 UTC
Closing this since we are tracking issues for tooling only in JIRA from now on.

Comment 6 JBoss JIRA Server 2016-02-16 15:05:17 UTC
Barry LaFond <blafond> updated the status of jira TEIIDDES-2097 to Resolved

Comment 7 JBoss JIRA Server 2016-09-12 12:42:41 UTC
Matus Makovy <mmakovy> updated the status of jira TEIIDDES-2097 to Closed