Bug 780616 (SOA-3054)

Summary: ODBC Driver fails on Solaris with [IM005][unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_DBC failed
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Paul Nittel <pnittel>
Component: TeiidAssignee: Van Halbert <vhalbert>
Status: CLOSED NOTABUG QA Contact: Filip Nguyen <fnguyen>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: atangrin, fnguyen, ldimaggi, mturk, pnittel, vhalbert
Target Milestone: ER5   
Target Release: 6.0   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-3054
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Some users are encountering problems when using the ODBC driver on Solaris 10.
Story Points: ---
Clone Of: Environment:
Solaris 10
Last Closed: 2014-03-10 20:28:56 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:
Bug Depends On:    
Bug Blocks: 780516, 1054244    
Attachments:
Description Flags
isqlWork.sql
none
odbc.ini
none
RunIsqlSol
none
.odbc.ini none

Description Paul Nittel 2011-05-04 15:58:51 UTC
Steps to Reproduce: See description.
project_key: SOA

I'm using the isql tool we provide with our kit. (It's working on other platforms.) When I try to simply connect to the DSN, the error results. I'll attach the odbc.ini, my own .odbc.ini, the script I run, and the SQL queries I'm attempting.

It goes like this when run manually:
$ isql -v eds pnittel mm
[IM005][unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_DBC failed
[ISQL]ERROR: Could not SQLConnect

Comment 1 Paul Nittel 2011-05-04 16:04:04 UTC
Files to use to reproduce

Comment 2 Paul Nittel 2011-05-04 16:04:04 UTC
Attachment: Added: isqlWork.sql
Attachment: Added: odbc.ini
Attachment: Added: RunIsqlSol
Attachment: Added: .odbc.ini


Comment 3 Mladen Turk 2011-05-11 07:45:12 UTC
Still no progress.
Now trying to compile the package locally on my VM instance with some more debugging options.



Comment 4 Mladen Turk 2011-05-11 10:12:07 UTC
Can someone check the console on the PostgreSQL server.
I'm wondering if this is related to:
http://archives.postgresql.org/pgsql-odbc/2007-09/msg00000.php
In which case when a isql attempt is tried an error should
be displayed as explained in that link.

Someone can check that? I don't have access to a DB box.

Comment 5 Paul Nittel 2011-05-11 16:05:35 UTC
I'll see what I can learn from this. While it's the same error message, I'm not sure how our different scenario will affect the outcome. As soon as I get my SOA-P server working again, I'll give it a shot.

Comment 6 Mladen Turk 2011-05-11 20:43:48 UTC
Trying on the FC14 with RHEL6 binaries I have
$ ./isql rhel32eds -vvv
[38000][unixODBC]ERROR: org.teiid.core.TeiidException
org.teiid.jdbc.TeiidSQLException: org.teiid.core.TeiidException
[ISQL]ERROR: Could not SQLConnect

This is with the .odbc.ini provided

 

Comment 7 Len DiMaggio 2011-05-12 17:29:16 UTC
Link: Added: This issue relates to SOA-2986


Comment 8 Paul Nittel 2011-05-12 19:25:27 UTC
I finally got QM27 running SOA-P/EDS again. I tried executing isql several times and non of them produced any kind of log file. Even the EDS server log shows nothing, which leads me to believe it dies before it tries to log onto the EDS server.

The TeiidException you received may have been from the server being down. It's back up now, so please try it again.

Comment 9 Van Halbert 2011-06-02 19:54:47 UTC
Link: Added: This issue is a dependency of SOA-2946


Comment 10 Van Halbert 2012-03-05 18:15:20 UTC
Is there more testing still to be done to determine the issue?

Comment 11 Mladen Turk 2012-03-05 19:17:06 UTC
Nope. Have no clue why is this happening.
Since I'm not familiar with the unixODBC and I see no obvious reason in solaris build files why would this happening, I'm afraid I can't be of much help here.

Comment 14 belong 2013-11-15 04:59:46 UTC
Paul,

Is the Doc Text I have provided sufficient information for customers? It seems there is no definitive workaround.

Cheers,
Ben

Comment 15 Anne-Louise Tangring 2013-12-04 00:11:36 UTC
I don't think this issue is applicable any more. If that is true, please close as will not fix.

Comment 16 belong 2013-12-10 00:52:30 UTC
Assuming this will be set to VERIFIED before GA - setting requires_doc_text- accordingly.

Comment 17 Filip Nguyen 2014-02-11 09:09:49 UTC
Dropping support for Solaris 10.