isql ( i.e. odbcUNIX Layer ) don't return Data Content

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

isql ( i.e. odbcUNIX Layer ) don't return Data Content

Jens-Peter C. Hillers
Hi all,

I have installed unixODBC with the drivers for maxdb AND oracle.

in both cases I get the folowing effect :

isql -v db01dcw DCW EGAL
+---------------------------------------+
| Connected!                            |
|                                       |
| sql-statement                         |
| help [tablename]                      |
| quit                                  |
|                                       |
+---------------------------------------+
SQL> select TIMESTAMP FROM DUAL
+---------------------------+
| EXPRESSION1               |
+---------------------------+
|                           |
+---------------------------+
SQLRowCount returns 1
1 rows fetched
SQL> quit

It seens that the table names and colum names get through but NO Data Content.

the SQL-Trace is :

-------------------------------
cat /tmp/sql.log
[ODBC][19130][__handles.c][447]
                Exit:[SQL_SUCCESS]
                        Environment = 0xcfc2c0
[ODBC][19130][SQLAllocHandle.c][359]
                Entry:
                        Handle Type = 2
                        Input Handle = 0xcfc2c0
[ODBC][19130][SQLAllocHandle.c][477]
                Exit:[SQL_SUCCESS]
                        Output Handle = 0xcfc8c0
[ODBC][19130][SQLConnect.c][3587]
                Entry:           
                        Connection = 0xcfc8c0           
                        Server Name = [db01dcw][length = 7 (SQL_NTS)]           
                        User Name = [DCW][length = 3 (SQL_NTS)]           
                        Authentication = [*******][length = 7 (SQL_NTS)]
                UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE 'UCS-2LE'

[ODBC][19130][SQLConnect.c][4161]
                Exit:[SQL_SUCCESS]
[ODBC][19130][SQLAllocHandle.c][524]
                Entry:
                        Handle Type = 3
                        Input Handle = 0xcfc8c0
[ODBC][19130][SQLAllocHandle.c][1059]
                Exit:[SQL_SUCCESS]
                        Output Handle = 0xd1eb70
[ODBC][19130][SQLPrepare.c][192]
                Entry:           
                        Statement = 0xd1eb70           
                        SQL = [select TIMESTAMP FROM DUAL ][length = 27 (SQL_NTS)]
[ODBC][19130][SQLPrepare.c][367]
                Exit:[SQL_SUCCESS]
[ODBC][19130][SQLExecute.c][183]
                Entry:           
                        Statement = 0xd1eb70
[ODBC][19130][SQLExecute.c][344]
                Exit:[SQL_SUCCESS]
[ODBC][19130][SQLNumResultCols.c][149]
                Entry:           
                        Statement = 0xd1eb70           
                        Column Count = 0x7fff2657c9d6
[ODBC][19130][SQLNumResultCols.c][234]
                Exit:[SQL_SUCCESS]               
                        Count = 0x7fff2657c9d6 -> 1
[ODBC][19130][SQLNumResultCols.c][149]
                Entry:           
                        Statement = 0xd1eb70           
                        Column Count = 0x7fff2657c6ae
[ODBC][19130][SQLNumResultCols.c][234]
                Exit:[SQL_SUCCESS]               
                        Count = 0x7fff2657c6ae -> 1
[ODBC][19130][SQLColAttribute.c][280]
                Entry:           
                        Statement = 0xd1eb70           
                        Column Number = 1           
                        Field Identifier = SQL_DESC_DISPLAY_SIZE           
                        Character Attr = (nil)           
                        Buffer Length = 0           
                        String Length = (nil)           
                        Numeric Attribute = 0x7fff2657c50c
[ODBC][19130][SQLColAttribute.c][651]
                Exit:[SQL_SUCCESS]
[ODBC][19130][SQLColAttribute.c][280]
                Entry:           
                        Statement = 0xd1eb70           
                        Column Number = 1           
                        Field Identifier = SQL_DESC_LABEL           
                        Character Attr = 0x7fff2657c510           
                        Buffer Length = 301           
                        String Length = (nil)           
                        Numeric Attribute = (nil)
[ODBC][19130][SQLColAttribute.c][651]
                Exit:[SQL_SUCCESS]
[ODBC][19130][SQLColAttribute.c][280]
                Entry:           
                        Statement = 0xd1eb70           
                        Column Number = 1           
                        Field Identifier = SQL_DESC_LABEL           
                        Character Attr = 0x7fff2657c6b0           
                        Buffer Length = 301           
                        String Length = (nil)           
                        Numeric Attribute = (nil)
[ODBC][19130][SQLColAttribute.c][651]
                Exit:[SQL_SUCCESS]
[ODBC][19130][SQLNumResultCols.c][149]
                Entry:           
                        Statement = 0xd1eb70           
                        Column Count = 0x7fff2657c6ba
[ODBC][19130][SQLNumResultCols.c][234]
                Exit:[SQL_SUCCESS]               
                        Count = 0x7fff2657c6ba -> 1
[ODBC][19130][SQLFetch.c][158]
                Entry:           
                        Statement = 0xd1eb70
[ODBC][19130][SQLFetch.c][340]
                Exit:[SQL_SUCCESS]
[ODBC][19130][SQLColAttribute.c][280]
                Entry:           
                        Statement = 0xd1eb70           
                        Column Number = 1           
                        Field Identifier = SQL_DESC_DISPLAY_SIZE           
                        Character Attr = (nil)           
                        Buffer Length = 0           
                        String Length = (nil)           
                        Numeric Attribute = 0x7fff2657c52c
[ODBC][19130][SQLColAttribute.c][651]
                Exit:[SQL_SUCCESS]
[ODBC][19130][SQLColAttribute.c][280]
                Entry:           
                        Statement = 0xd1eb70           
                        Column Number = 1           
                        Field Identifier = SQL_DESC_LABEL           
                        Character Attr = 0x7fff2657c530           
                        Buffer Length = 301           
                        String Length = (nil)           
                        Numeric Attribute = (nil)
[ODBC][19130][SQLColAttribute.c][651]
                Exit:[SQL_SUCCESS]
[ODBC][19130][SQLGetData.c][230]
                Entry:           
                        Statement = 0xd1eb70           
                        Column Number = 1           
                        Target Type = 1 SQL_CHAR           
                        Buffer Length = 301           
                        Target Value = 0x7fff2657c6c0           
                        StrLen Or Ind = 0x7fff2657c6bc
[ODBC][19130][SQLGetData.c][494]
                Exit:[SQL_SUCCESS]               
                        Buffer = []               
                        Strlen Or Ind = 0x7fff2657c6bc -> 26
[ODBC][19130][SQLFetch.c][158]
                Entry:           
                        Statement = 0xd1eb70
[ODBC][19130][SQLFetch.c][340]
                Exit:[SQL_NO_DATA]
[ODBC][19130][SQLRowCount.c][166]
                Entry:           
                        Statement = 0xd1eb70           
                        Row Count = 0x7fff2657c94c
[ODBC][19130][SQLRowCount.c][237]
                Exit:[SQL_SUCCESS]               
                        Row Count = 0x7fff2657c94c -> 1
[ODBC][19130][SQLMoreResults.c][158]
                Entry:           
                        Statement = 0xd1eb70
[ODBC][19130][SQLMoreResults.c][313]
                Exit:[SQL_NO_DATA]
[ODBC][19130][SQLFreeStmt.c][140]
                Entry:           
                        Statement = 0xd1eb70           
                        Option = 1
[ODBC][19130][SQLFreeHandle.c][368]
                Entry:
                        Handle Type = 3
                        Input Handle = 0xd1eb70
[ODBC][19130][SQLFreeHandle.c][465]
                Exit:[SQL_SUCCESS]
[ODBC][19130][SQLDisconnect.c][204]
                Entry:           
                        Connection = 0xcfc8c0
[ODBC][19130][SQLDisconnect.c][341]
                Exit:[SQL_SUCCESS]
[ODBC][19130][SQLFreeHandle.c][271]
                Entry:
                        Handle Type = 2
                        Input Handle = 0xcfc8c0
[ODBC][19130][SQLFreeHandle.c][320]
                Exit:[SQL_SUCCESS]
[ODBC][19130][SQLFreeHandle.c][206]
                Entry:
                        Handle Type = 1
                        Input Handle = 0xcfc2c0
-------------------------------------------
A previous trace of the driver itself showed The data is only copied internally but I could not find a call where isql retrives the data fetched.
-------------------------------------------
SQLFetch 2014-06-19 10:20:05.168182
 --> SQLExtendedFetch
::GET RESULT SET [0x0xfe49b0]
CURSOR NAME: 'SQLCURS_2' [0x0xfe1d40]

SQLExtendedFetch 2014-06-19 10:20:05.168251
StatementHandle  [in]    : 0xfe1310
FetchOrientation [in]    : SQL_FETCH_NEXT
FetchOffset      [in]    : 0

::SET ROWSET SIZE 'SQLCURS_2' [0x0xfe1d40]
SIZE: 1

::SET BINDING TYPE 'SQLCURS_2' [0x0xfe1d40]
BINDING TYPE: 0

::FETCH NEXT 'SQLCURS_2' 2014-06-19 10:20:05.168397
DATA:
APPLICATION
I   T          AT L          I           DATA
ROW: 1

::GET ROWS AFFECTED [0x0xfe1d40]
ROWS: 1

::GET ROWS AFFECTED [0x0xfe1d40]
ROWS: 1
RowCountPtr      [out]   : (null)
RowStatusArray   [out]   : (null)
SQLRETURN                : SQL_SUCCESS
 <-- SQLExtendedFetch

SQLColAttribute 2014-06-19 10:20:05.168551
StatementHandle  [in]    : 0xfe1310
ColumnNumber     [in]    : 1
FieldIdentifier  [in]    : SQL_COLUMN_DISPLAY_SIZE
BufferLength     [in]    : 0
NumericAttrPtr   [out]   : 26
NumericAttrPtr   [out]   : 0x7fff81d03d7c
StringLengthPtr  [out]   : (null)
SQLRETURN                : SQL_SUCCESS

SQLColAttribute 2014-06-19 10:20:05.168664
StatementHandle  [in]    : 0xfe1310
ColumnNumber     [in]    : 1
FieldIdentifier  [in]    : SQL_COLUMN_LABEL
BufferLength     [in]    : 301
CharacterAttrPtr [out]   : 0x7fff81d03d80
StringLengthPtr  [out]   : (null)
SQLRETURN                : SQL_SUCCESS

SQLGetData 2014-06-19 10:20:05.168754
StatementHandle  [in]    : 0xfe1310
ColumnNumber     [in]    : 1
TargetType       [in]    : SQL_C_CHAR
TargetValuePtr   [out]   : 0x7fff81d03f10
BufferLength     [in]    : 301
ValuePtr         [out]   : SQL_UB_OFF

::GETOBJECT 'SQLCURS_2' 2014-06-19 10:20:05.168851 [0x0x1015dc0]
COLUMN
I   T          AT L          I                  D                  P
1   ASCII       T 301        0x00007FFF81D03B20 0x00007FFF81D03F10 0x0000000000000000
DATA
I   T          AT L          I           DATA
1   ASCII       T 301        26          '2014-06-19 10:19:33.218298'
StrLen_or_IndPtr [out]    : 26
SQLRETURN                : SQL_SUCCESS

SQLFetch 2014-06-19 10:20:05.189504
 --> SQLExtendedFetch
SQLExtendedFetch 2014-06-19 10:20:05.189529
StatementHandle  [in]    : 0xfe1310
FetchOrientation [in]    : SQL_FETCH_NEXT
FetchOffset      [in]    : 0

::SET ROWSET SIZE 'SQLCURS_2' [0x0xfe1d40]
SIZE: 1

::FETCH NEXT 'SQLCURS_2' 2014-06-19 10:20:05.189663

::GET ROWS AFFECTED [0x0xfe1d40]
ROWS: 1

::GET ROWS AFFECTED [0x0xfe1d40]
ROWS: 1
RowCountPtr      [out]   : (null)
RowStatusArray   [out]   : (null)
SQLRETURN                : SQL_NO_DATA
 <-- SQLExtendedFetch

SQLRowCount 2014-06-19 10:20:05.189780
StatementHandle  [in]    : 0xfe1310

::GET RESULT COUNT [0x0xfe1d40]
COUNT: 1
RowCountPtr      [out]   : 1
SQLRETURN                : SQL_SUCCESS

SQLMoreResults 2014-06-19 10:20:05.189864
StatementHandle  [in]    : 0xfe1310
 --> SQLFreeStmt
SQLFreeStmt 2014-06-19 10:20:05.189894
StatementHandle  [in]    : 0xfe1310
Option           [in]    : SQL_CLOSE
SQLRETURN                : SQL_SUCCESS
 <-- SQLFreeStmt
SQLRETURN                : SQL_NO_DATA
-------------------------------------------------

I've installed on :

----------------------------------------------
openSUSE 12.3 "Dartmouth" ( x86_64 GNU/Linux )
# isql --version
unixODBC 2.2.12
# rpm -qa | grep unixODBC
unixODBC-devel-2.2.12-219.1.1.x86_64
unixODBC-2.2.12-219.1.1.x86_64
unixODBC-gui-qt-2.2.12-219.1.1.x86_64
---------------------------------
I hope somebody has some helping Idea.

regards
jph

P.S.:

The reason why I dont use 2.3 is

2.2 is packaged in the nearly current SuSe 12.3

I would only try 2.3 if there are features that might cause this effect.




-- 
------------------------
Remote Web Services GmbH
Jens-Peter C. Hillers

Humboldtstraße 55
22083 Hamburg

Tel:  +49 (0) 40 - 20 93 41 75 - 0
Mobil:  0163 / 354 24 61 
Mail: [hidden email]
web: www.remoteweb.de
------------------------

_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support
Reply | Threaded
Open this post in threaded view
|

Re: isql ( i.e. odbcUNIX Layer ) don't return Data Content

Nick Gorham-2
On 30/06/14 11:14, Jens-Peter C. Hillers wrote:
Hi all,

I have installed unixODBC with the drivers for maxdb AND oracle.

in both cases I get the folowing effect :

isql -v db01dcw DCW EGAL
+---------------------------------------+
| Connected!                            |
|                                       |
| sql-statement                         |
| help [tablename]                      |
| quit                                  |
|                                       |
+---------------------------------------+
SQL> select TIMESTAMP FROM DUAL
+---------------------------+
| EXPRESSION1               |
+---------------------------+
|                           |
+---------------------------+
SQLRowCount returns 1
1 rows fetched
SQL> quit

What would you expect to get back?

unixODBC is not involved in those calls much, its just past from the app to the driver, so I suspect whats coming back is not what you expect.

--
Nick


_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support
Reply | Threaded
Open this post in threaded view
|

Re: isql ( i.e. odbcUNIX Layer ) don't return Data Content

Jens-Peter C. Hillers
Ok what I expected to get back ?

something like :
----------------
Welcome to the SAP MaxDB interactive terminal.
                                          
Type:  \h for help with commands         
       \q to quit                        

sqlcli MAXDB=> select TIMESTAMP FROM DUAL
| EXPRESSION1                |
| -------------------------- |
| 2014-07-01 10:21:58.062480 |
1 row selected (1309 usec)
----------------

I took this simple select to make it easy to track down the Problem regardless what the real data in the table is.

Querying through the Oracle driver to a differnt server its the same effekt:

----------------
SQL> select SYSDATE FROM DUAL
+--------------------+
| SYSDATE            |
+--------------------+
|                    |
+--------------------+
SQLRowCount returns -1
1 rows fetched
---------------------

Querying "Real"-Tables have the same effekt:

---------------
sqlcli MAXDB=> select * from BFTYP
| BFMTD | NAME                             | WANN                       | WER         | STATE |
| ----- | -------------------------------- | -------------------------- | ----------- | ----- |
| F     | DC900 Software                   | 2011-02-17 15:32:36.190803 | ?           | ?     |
| J     | DC910 Software                   | 2012-12-05 15:52:02.858546 | ?           | ?     |
| P     | PEX Software                     | 2012-12-05 15:52:02.512886 | ?           | ?     |
3 rows selected (1865 usec)
----------------

via isql I get:

--------------------
SQL> select * from BFTYP
+------+---------------------------------+---------------------------+------------+------+
| BFMTD| NAME                            | WANN                      | WER        | STATE|
+------+---------------------------------+---------------------------+------------+------+
|      |                                 |                           |            |      |
|      |                                 |                           |            |      |
|      |                                 |                           |            |      |
+------+---------------------------------+---------------------------+------------+------+
SQLRowCount returns 3
3 rows fetched
----------------------

The SAP Guys told me, that out of the driver trace I Postet in my first mail one could see that the Data arrives in the Driver but is not fetched.

---------

My real Problem is that all applications that use unixodbc can't access data ( in my case LibeBASE of LibreOffice )

But I guess if it's runnung in isql it will also do in the other Apllications.

regars
jph





Out of the Driver trace in my last Mail we could see that thae adte


Am 30.06.2014 20:37, schrieb Nick Gorham:
On 30/06/14 11:14, Jens-Peter C. Hillers wrote:
Hi all,

I have installed unixODBC with the drivers for maxdb AND oracle.

in both cases I get the folowing effect :

isql -v db01dcw DCW EGAL
+---------------------------------------+
| Connected!                            |
|                                       |
| sql-statement                         |
| help [tablename]                      |
| quit                                  |
|                                       |
+---------------------------------------+
SQL> select TIMESTAMP FROM DUAL
+---------------------------+
| EXPRESSION1               |
+---------------------------+
|                           |
+---------------------------+
SQLRowCount returns 1
1 rows fetched
SQL> quit

What would you expect to get back?

unixODBC is not involved in those calls much, its just past from the app to the driver, so I suspect whats coming back is not what you expect.

--
Nick



_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support


-- 
------------------------
Remote Web Services GmbH
Jens-Peter C. Hillers

Humboldtstraße 55
22083 Hamburg

Tel:  +49 (0) 40 - 20 93 41 75 - 0
Mobil:  0163 / 354 24 61 
Mail: [hidden email]
web: www.remoteweb.de
------------------------

_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support
Reply | Threaded
Open this post in threaded view
|

Re: isql ( i.e. odbcUNIX Layer ) don't return Data Content

Nick Gorham-2
On 01/07/14 09:47, Jens-Peter C. Hillers wrote:
Ok what I expected to get back ?

something like :
----------------
Welcome to the SAP MaxDB interactive terminal.
                                          
Type:  \h for help with commands         
       \q to quit                        

sqlcli MAXDB=> select TIMESTAMP FROM DUAL
| EXPRESSION1                |
| -------------------------- |
| 2014-07-01 10:21:58.062480 |
1 row selected (1309 usec)
----------------

I took this simple select to make it easy to track down the Problem regardless what the real data in the table is.

Querying through the Oracle driver to a differnt server its the same effekt:

----------------
SQL> select SYSDATE FROM DUAL
+--------------------+
| SYSDATE            |
+--------------------+
|                    |
+--------------------+
SQLRowCount returns -1
1 rows fetched
---------------------

Querying "Real"-Tables have the same effekt:

---------------
sqlcli MAXDB=> select * from BFTYP
| BFMTD | NAME                             | WANN                       | WER         | STATE |
| ----- | -------------------------------- | -------------------------- | ----------- | ----- |
| F     | DC900 Software                   | 2011-02-17 15:32:36.190803 | ?           | ?     |
| J     | DC910 Software                   | 2012-12-05 15:52:02.858546 | ?           | ?     |
| P     | PEX Software                     | 2012-12-05 15:52:02.512886 | ?           | ?     |
3 rows selected (1865 usec)
----------------

via isql I get:

--------------------
SQL> select * from BFTYP
+------+---------------------------------+---------------------------+------------+------+
| BFMTD| NAME                            | WANN                      | WER        | STATE|
+------+---------------------------------+---------------------------+------------+------+
|      |                                 |                           |            |      |
|      |                                 |                           |            |      |
|      |                                 |                           |            |      |
+------+---------------------------------+---------------------------+------------+------+
SQLRowCount returns 3
3 rows fetched
----------------------

The SAP Guys told me, that out of the driver trace I Postet in my first mail one could see that the Data arrives in the Driver but is not fetched.

---------

My real Problem is that all applications that use unixodbc can't access data ( in my case LibeBASE of LibreOffice )

But I guess if it's runnung in isql it will also do in the other Apllications.

regars
jph

How odd. What platform are you on and what version of unixODBC. It goes without saying that I have never seen that before.

--
Nick

_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support
Reply | Threaded
Open this post in threaded view
|

Re: isql ( i.e. odbcUNIX Layer ) don't return Data Content

Jens-Peter C. Hillers
Am 01.07.2014 11:04, schrieb Nick Gorham:
On 01/07/14 09:47, Jens-Peter C. Hillers wrote:
Ok what I expected to get back ?

something like :
----------------
Welcome to the SAP MaxDB interactive terminal.
                                          
Type:  \h for help with commands         
       \q to quit                        

sqlcli MAXDB=> select TIMESTAMP FROM DUAL
| EXPRESSION1                |
| -------------------------- |
| 2014-07-01 10:21:58.062480 |
1 row selected (1309 usec)
----------------

I took this simple select to make it easy to track down the Problem regardless what the real data in the table is.

Querying through the Oracle driver to a differnt server its the same effekt:

----------------
SQL> select SYSDATE FROM DUAL
+--------------------+
| SYSDATE            |
+--------------------+
|                    |
+--------------------+
SQLRowCount returns -1
1 rows fetched
---------------------

Querying "Real"-Tables have the same effekt:

---------------
sqlcli MAXDB=> select * from BFTYP
| BFMTD | NAME                             | WANN                       | WER         | STATE |
| ----- | -------------------------------- | -------------------------- | ----------- | ----- |
| F     | DC900 Software                   | 2011-02-17 15:32:36.190803 | ?           | ?     |
| J     | DC910 Software                   | 2012-12-05 15:52:02.858546 | ?           | ?     |
| P     | PEX Software                     | 2012-12-05 15:52:02.512886 | ?           | ?     |
3 rows selected (1865 usec)
----------------

via isql I get:

--------------------
SQL> select * from BFTYP
+------+---------------------------------+---------------------------+------------+------+
| BFMTD| NAME                            | WANN                      | WER        | STATE|
+------+---------------------------------+---------------------------+------------+------+
|      |                                 |                           |            |      |
|      |                                 |                           |            |      |
|      |                                 |                           |            |      |
+------+---------------------------------+---------------------------+------------+------+
SQLRowCount returns 3
3 rows fetched
----------------------

The SAP Guys told me, that out of the driver trace I Postet in my first mail one could see that the Data arrives in the Driver but is not fetched.

---------

My real Problem is that all applications that use unixodbc can't access data ( in my case LibeBASE of LibreOffice )

But I guess if it's runnung in isql it will also do in the other Apllications.

regars
jph

How odd. What platform are you on and what version of unixODBC. It goes without saying that I have never seen that before.

--
Nick
Hi Nick,

I've installed on :

----------------------------------------------
openSUSE 12.3 "Dartmouth" ( x86_64 GNU/Linux )
# isql --version
unixODBC 2.2.12
# rpm -qa | grep unixODBC
unixODBC-devel-2.2.12-219.1.1.x86_64
unixODBC-2.2.12-219.1.1.x86_64
unixODBC-gui-qt-2.2.12-219.1.1.x86_64
---------------------------------

Version 2.2.12 ist what ist packaged by SuSe so it is easyser to deploy.

I'm currently trying 2.3.2 from source.

regards 
jph




_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support


-- 
------------------------
Remote Web Services GmbH
Jens-Peter C. Hillers

Humboldtstraße 55
22083 Hamburg

Tel:  +49 (0) 40 - 20 93 41 75 - 0
Mobil:  0163 / 354 24 61 
Mail: [hidden email]
web: www.remoteweb.de
------------------------

_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support
Reply | Threaded
Open this post in threaded view
|

Re: isql ( i.e. odbcUNIX Layer ) don't return Data Content

Jens-Peter C. Hillers
Hi all,

Installing Version 2.3.2

solved the Problem at least with isql.

rgards
jph

      Am 01.07.2014 11:09, schrieb Jens-Peter C. Hillers:
Am 01.07.2014 11:04, schrieb Nick Gorham:
On 01/07/14 09:47, Jens-Peter C. Hillers wrote:
Ok what I expected to get back ?

something like :
----------------
Welcome to the SAP MaxDB interactive terminal.
                                          
Type:  \h for help with commands         
       \q to quit                        

sqlcli MAXDB=> select TIMESTAMP FROM DUAL
| EXPRESSION1                |
| -------------------------- |
| 2014-07-01 10:21:58.062480 |
1 row selected (1309 usec)
----------------

I took this simple select to make it easy to track down the Problem regardless what the real data in the table is.

Querying through the Oracle driver to a differnt server its the same effekt:

----------------
SQL> select SYSDATE FROM DUAL
+--------------------+
| SYSDATE            |
+--------------------+
|                    |
+--------------------+
SQLRowCount returns -1
1 rows fetched
---------------------

Querying "Real"-Tables have the same effekt:

---------------
sqlcli MAXDB=> select * from BFTYP
| BFMTD | NAME                             | WANN                       | WER         | STATE |
| ----- | -------------------------------- | -------------------------- | ----------- | ----- |
| F     | DC900 Software                   | 2011-02-17 15:32:36.190803 | ?           | ?     |
| J     | DC910 Software                   | 2012-12-05 15:52:02.858546 | ?           | ?     |
| P     | PEX Software                     | 2012-12-05 15:52:02.512886 | ?           | ?     |
3 rows selected (1865 usec)
----------------

via isql I get:

--------------------
SQL> select * from BFTYP
+------+---------------------------------+---------------------------+------------+------+
| BFMTD| NAME                            | WANN                      | WER        | STATE|
+------+---------------------------------+---------------------------+------------+------+
|      |                                 |                           |            |      |
|      |                                 |                           |            |      |
|      |                                 |                           |            |      |
+------+---------------------------------+---------------------------+------------+------+
SQLRowCount returns 3
3 rows fetched
----------------------

The SAP Guys told me, that out of the driver trace I Postet in my first mail one could see that the Data arrives in the Driver but is not fetched.

---------

My real Problem is that all applications that use unixodbc can't access data ( in my case LibeBASE of LibreOffice )

But I guess if it's runnung in isql it will also do in the other Apllications.

regars
jph

How odd. What platform are you on and what version of unixODBC. It goes without saying that I have never seen that before.

--
Nick
Hi Nick,

I've installed on :

----------------------------------------------
openSUSE 12.3 "Dartmouth" ( x86_64 GNU/Linux )
# isql --version
unixODBC 2.2.12
# rpm -qa | grep unixODBC
unixODBC-devel-2.2.12-219.1.1.x86_64
unixODBC-2.2.12-219.1.1.x86_64
unixODBC-gui-qt-2.2.12-219.1.1.x86_64
---------------------------------

Version 2.2.12 ist what ist packaged by SuSe so it is easyser to deploy.

I'm currently trying 2.3.2 from source.

regards 
jph




_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support


-- 
------------------------
Remote Web Services GmbH
Jens-Peter C. Hillers

Humboldtstraße 55
22083 Hamburg

Tel:  +49 (0) 40 - 20 93 41 75 - 0
Mobil:  0163 / 354 24 61 
Mail: [hidden email]
web: www.remoteweb.de
------------------------


_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support


-- 
------------------------
Remote Web Services GmbH
Jens-Peter C. Hillers

Humboldtstraße 55
22083 Hamburg

Tel:  +49 (0) 40 - 20 93 41 75 - 0
Mobil:  0163 / 354 24 61 
Mail: [hidden email]
web: www.remoteweb.de
------------------------

_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support
Reply | Threaded
Open this post in threaded view
|

Re: isql ( i.e. odbcUNIX Layer ) don't return Data Content

Kevin Adler
Hi Jens-Peter,

As an FYI, unixODBC 2.3.1 is packaged for openSUSE 13.1 and I submitted an update to 2.3.2 for Factory, so it will be included with openSUSE 13.2 in November.

I was going to suggest you could use the server:database repository on OBS instead of building from source, but they seem to have disabled building for openSUSE 12.3 and 13.1 for some reason (Strangely enough, 12.2 is enabled there). You could always fork the package in OBS and enable 12.3 if you want or just continue building from source.

Regards
Kevin Adler
Software Development - DB2 for i, Database Access for IBM i





From:        "Jens-Peter C. Hillers" <[hidden email]>
To:        [hidden email]
Date:        07/01/2014 07:56 AM
Subject:        Re: [unixODBC-support] isql ( i.e. odbcUNIX Layer ) don't return Data Content
Sent by:        [hidden email]




Hi all,

Installing Version 2.3.2

solved the Problem at least with isql.

rgards
jph



Am 01.07.2014 11:09, schrieb Jens-Peter C. Hillers:
Am 01.07.2014 11:04, schrieb Nick Gorham:
On 01/07/14 09:47, Jens-Peter C. Hillers wrote:
Ok what I expected to get back ?

something like :

----------------
Welcome to the SAP MaxDB interactive terminal.
                                         
Type:  \h for help with commands          
      \q to quit                        

sqlcli MAXDB=> select TIMESTAMP FROM DUAL
| EXPRESSION1                |
| -------------------------- |
| 2014-07-01 10:21:58.062480 |
1 row selected (1309 usec)
----------------


I took this simple select to make it easy to track down the Problem regardless what the real data in the table is.

Querying through the Oracle driver to a differnt server its the same effekt:

----------------

SQL> select SYSDATE FROM DUAL
+--------------------+
| SYSDATE            |
+--------------------+
|                    |
+--------------------+
SQLRowCount returns -1
1 rows fetched

---------------------

Querying "Real"-Tables have the same effekt:

---------------

sqlcli MAXDB=> select * from BFTYP
| BFMTD | NAME                             | WANN                       | WER         | STATE |
| ----- | -------------------------------- | -------------------------- | ----------- | ----- |
| F     | DC900 Software                   | 2011-02-17 15:32:36.190803 | ?           | ?     |
| J     | DC910 Software                   | 2012-12-05 15:52:02.858546 | ?           | ?     |
| P     | PEX Software                     | 2012-12-05 15:52:02.512886 | ?           | ?     |
3 rows selected (1865 usec)

----------------

via isql I get:

--------------------

SQL> select * from BFTYP
+------+---------------------------------+---------------------------+------------+------+
| BFMTD| NAME                            | WANN                      | WER        | STATE|
+------+---------------------------------+---------------------------+------------+------+
|      |                                 |                           |            |      |
|      |                                 |                           |            |      |
|      |                                 |                           |            |      |
+------+---------------------------------+---------------------------+------------+------+
SQLRowCount returns 3
3 rows fetched

----------------------

The SAP Guys told me, that out of the driver trace I Postet in my first mail one could see that the Data arrives in the Driver but is not fetched.

---------

My real Problem is that all applications that use unixodbc can't access data ( in my case LibeBASE of LibreOffice )

But I guess if it's runnung in isql it will also do in the other Apllications.

regars
jph

How odd. What platform are you on and what version of unixODBC. It goes without saying that I have never seen that before.

--
Nick

Hi Nick,

I've installed on :

----------------------------------------------

openSUSE 12.3 "Dartmouth" ( x86_64 GNU/Linux )
# isql --version
unixODBC 2.2.12
# rpm -qa | grep unixODBC
unixODBC-devel-2.2.12-219.1.1.x86_64
unixODBC-2.2.12-219.1.1.x86_64
unixODBC-gui-qt-2.2.12-219.1.1.x86_64
---------------------------------

Version 2.2.12 ist what ist packaged by SuSe so it is easyser to deploy.

I'm currently trying 2.3.2 from source.

regards
jph





_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support



--
------------------------
Remote Web Services GmbH
Jens-Peter C. Hillers

Humboldtstraße 55
22083 Hamburg

Tel:  +49 (0) 40 - 20 93 41 75 - 0
Mobil:  0163 / 354 24 61
Mail:
jph@...
web:
www.remoteweb.de
------------------------



_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support



--
------------------------
Remote Web Services GmbH
Jens-Peter C. Hillers

Humboldtstraße 55
22083 Hamburg

Tel:  +49 (0) 40 - 20 93 41 75 - 0
Mobil:  0163 / 354 24 61
Mail:
jph@...
web:
www.remoteweb.de
------------------------
_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support


_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support
Reply | Threaded
Open this post in threaded view
|

Re: isql ( i.e. odbcUNIX Layer ) don't return Data Content

Nick Gorham-2
On 01/07/14 17:05, Kevin Adler wrote:
Hi Jens-Peter,

As an FYI, unixODBC 2.3.1 is packaged for openSUSE 13.1 and I submitted an update to 2.3.2 for Factory, so it will be included with openSUSE 13.2 in November.

I was going to suggest you could use the server:database repository on OBS instead of building from source, but they seem to have disabled building for openSUSE 12.3 and 13.1 for some reason (Strangely enough, 12.2 is enabled there). You could always fork the package in OBS and enable 12.3 if you want or just continue building from source.

Regards
Kevin Adler
Software Development - DB2 for i, Database Access for IBM i

It may be worth not making to much effort for 2.3.2 at this point, as 2.3.3 will be along soon. I have no real reason not to release it if its of help.


--
Nick

_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support
Reply | Threaded
Open this post in threaded view
|

Re: isql ( i.e. odbcUNIX Layer ) don't return Data Content

Kevin Adler
As soon as I hear of its release, I'll try to get it pushed to Factory for openSUSE 13.2.


Regards
Kevin Adler
Software Development - DB2 for i, Database Access for IBM i




From:        Nick Gorham <[hidden email]>
To:        Support for the unixODBC project <[hidden email]>
Date:        07/01/2014 11:16 AM
Subject:        Re: [unixODBC-support] isql ( i.e. odbcUNIX Layer ) don't return Data Content
Sent by:        [hidden email]




On 01/07/14 17:05, Kevin Adler wrote:
Hi Jens-Peter,

As an FYI, unixODBC 2.3.1 is packaged for openSUSE 13.1 and I submitted an update to 2.3.2 for Factory, so it will be included with openSUSE 13.2 in November.


I was going to suggest you could use the server:database repository on OBS instead of building from source, but they seem to have disabled building for openSUSE 12.3 and 13.1 for some reason (Strangely enough, 12.2 is enabled there). You could always fork the package in OBS and enable 12.3 if you want or just continue building from source.


Regards
Kevin Adler
Software Development - DB2 for i, Database Access for IBM i


It may be worth not making to much effort for 2.3.2 at this point, as 2.3.3 will be along soon. I have no real reason not to release it if its of help.


--
Nick
_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support


_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support