Bug 1205110

Summary:	Wrong "name-in-source" property value for imported tables in Source model (JDBC importer, Sybase 15 Database)
Product:	[JBoss] JBoss Data Virtualization 6	Reporter:	Juraj Duráni <jdurani>
Component:	Tooling	Assignee:	Barry LaFond <blafond>
Status:	CLOSED DEFERRED	QA Contact:	Andrej Smigala <asmigala>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	asmigala, atangrin, blafond, dlesage, jdurani, jolee, mmakovy, vhalbert
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	If you try to import a source model from Sybase 15, the "name-in-source" property value will be wrong.	Story Points:	---
Clone Of:		Environment:	JBDS: 8.0.2GA TD: 9.0.1.Final OS: Fedora 20 java: oracle 1.7 JDBC driver: jconn4-26502 - jConnect (TM) for JDBC(TM)/7.00(Build 26502) Sybase DB: ASE 15.0.3/EBF
Last Closed:	2016-02-05 09:10:37 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:

Description Juraj Duráni 2015-03-24 09:14:24 UTC

Description:
I am trying to import a Source model from Sybase database. But imported tables have wrong "name-in-source" property values.

Steps to reproduce:
Use JDBC importer and import a source model from Sybase database.
In my case, every table has "name-in-source" property like "bqt2"."<table-name>", but it should be "bqt2"."dbo"."<table-name>". As result every query ends with an exception: "Error: bqt2.SmallA not found. Specify owner.objectname..."

I have tried this using JTDS driver and all tables had correct "name-in-source". But this driver in neither tested nor supported for teiid.

Comment 1 Barry LaFond 2015-03-31 15:25:26 UTC

Juraj... see my comments and questions in TEIIDDES-2458

Comment 2 Juraj Duráni 2015-04-01 05:26:11 UTC

Hi Barry,

I have added the comment in jira.

Comment 3 Barry LaFond 2015-07-06 12:55:23 UTC

See last comments on jira.  Basically the Sybase test DB we have set-up isn't providing the expected schema/catalog in the JDBC metadata. Not sure how to fix that in order to dig deeper into this issue.

Comment 4 Juraj Duráni 2015-07-07 05:51:00 UTC

I have added a comment in JIRA.

Comment 6 Barry LaFond 2015-08-25 14:44:42 UTC

Per the referenced JIRA, we still haven't discovered the source of the issue. Last comment indicated it may be a driver issue. Pushing back to reporter

Comment 7 Barry LaFond 2015-08-25 15:00:50 UTC

Push to DV 6.3/Designer 9.0.4 to allow time for more investigation

Comment 8 Juraj Duráni 2015-09-07 11:57:23 UTC

Ok, we can postpone it to DV 6.3. This is not a blocker as user can modify "name-in-source" manually. Do you need any additional info?

Comment 9 JBoss JIRA Server 2015-11-02 09:17:35 UTC

Andrej Šmigala <asmigala> updated the status of jira TEIIDDES-2458 to Resolved

Comment 10 Matus Makovy 2016-02-05 09:10:37 UTC

Closing this since we are tracking issues for tooling only in JIRA from now on.

Comment 11 JBoss JIRA Server 2016-07-06 14:26:05 UTC

Tom Johnston <tljohnst> updated the status of jira TEIIDDES-2458 to Reopened