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
Files to use to reproduce
Attachment: Added: isqlWork.sql Attachment: Added: odbc.ini Attachment: Added: RunIsqlSol Attachment: Added: .odbc.ini
Still no progress. Now trying to compile the package locally on my VM instance with some more debugging options.
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.
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.
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
Link: Added: This issue relates to SOA-2986
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.
Link: Added: This issue is a dependency of SOA-2946
Is there more testing still to be done to determine the issue?
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.
Paul, Is the Doc Text I have provided sufficient information for customers? It seems there is no definitive workaround. Cheers, Ben
I don't think this issue is applicable any more. If that is true, please close as will not fix.
Assuming this will be set to VERIFIED before GA - setting requires_doc_text- accordingly.
Dropping support for Solaris 10.