Windows 7 ODBC 32Bit problem (ORACLE mode)

[former_member924015]

Hi to all,

we're having a problem with the current ODBC drivers.

Environment:

Client - Windows 7 (64Bit), ODBC drivers for both 32Bit & 64Bit (latest installation package maxdb-all-win-64bit-x86_64-7_8_02_37.exe)

Server - Linux 64 Bit with MaxDB version 7.8.01.18

Problem:

With the new ODBC 32Bit drivers it isn't possible to use the mode 'ORACLE'.

Log from trace file:

X 1 -B13249 -M4 1750-1754    EXIT  SQLExecDirectW  with return code -1 (SQL_ERROR)

        HSTMT               0x16BA38E0

        WCHAR *             0x1431EB30 [      41] "SELECT * FROM ADMIN.V_LE WHERE rownum <=1"

        SDWORD                    41

        DIAG [S1000] [SAP AG][SDBODBC DLL][MaxDB] General error;-4005 POS(32) Unknown column name:ROWNUM (-4005)

The driver treats pseudo column ROWNUM as table column. That's why it's producing an error.

With a very old version of ODBC driver for 32 Bit (7.6.0.0, Build 037-121-149-748) it's not producing this error, but the driver is very slow.

With mode 'INTERNAL' the ODBC driver is working fine in the latest build.

Is there something that I'm missig ?

Thanks and best regards,

Stefan

[former_member924015]

Hi Burkhard,

could you tell me please where I can find the updated packages?

As I can see at the PTS, the state of the fixed driver is set to "delivered", since dec. 16th.

MaxDB PTS - Problem Tracking -&amp;nbsp;Error&amp;nbsp;1251276:&amp;nbsp;ODBC

Best regards

[Former Member]

Hello,

the update for 7.8.02.38 was released for SAP customer on SAPService Market Place last week here.

Download the MAXDB 7.8.02.38 Application Runtime Package for the SQLMODE issue.

We are preparing the dowload packages for SCN.

Kind regards,

Burkhard

[former_member924015]

Hello Burkhard,

thanks for the answer, we will wait for the SCN release!

Best regards,

Stefan

[Former Member]

Hello Stefan,

you are right. The SQLMODE=ORACLE mode only works in 7.6. I have created a bug entry for this

http://maxdb.sap.com/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1251276

We will fix this for 7.7, 7.8 and 7.9 with the next version.

Please excuse this inconvenience .

Regards,

Burkhard

[former_member924015]

Hi Burkhard,

thanks for info! Will you leave an answer when the fix is released ?

Thanks and best regards,

Stefan

[Former Member]

Yes I will post it here. But it could take some weeks.

Regards,

Burkhard

[former_member924015]

Hi Burkhard,

any news on this topic ? Maybe it's no time left for this year

Best regards,

Stefan

[david_liu1]

Hello,

You have to use the dbanalyzer from /sapdb/L2P/db/bin.

SAP changed the dbanalyzer from a release independant program to a release dependant program. But the adm user still has the release independant directory in the PATH, so by default, you get
the old 7.7 version of dbanalyzer.

Regards,

David

[former_member924015]

Hi David,

can you give me some hints why to use the dbanalyzer.? As the ODBC trace file told me, the

SELECT ... WHERE ROWNUM <= 1 is causing the problem (ROWNUM is a pseudo, not a table column). What should I discover using the dbanalyzer ?

Thanks in advance and best regards

Stefan