Re: MaxDB/SAPDB compatibility

Timo Denis <[email protected]>
Newsgroups gmane.comp.db.maxdb
Message-ID <[email protected]>
Hi,

I've done one more test with a properly displayed result using
RHEL4 - unixODBC 2.2.11 - maxdb-callif-7.6.0.34-1 (all 32bit), the only 
difference to the failing client is 64bit!

OK using RHEL4 - unixODBC 2.2.11 - maxdb-callif-7.6.0.34-1 (all 32bit)
no OK on RHEL4 - unixODBC 2.2.11 - maxdb-callif-7.6.0.34-1 (all 64bit)

Configuration and queried server is still the same, .....

Cheers, Timo




Koetter, Thomas Theodor wrote:
> Hello Timo 
> 
>> -----Original Message-----
>> From: Timo Denis [mailto:[email protected]] 
>> Sent: Mittwoch, 21. März 2007 08:57
>> To: [email protected]
>> Subject: MaxDB/SAPDB compatibility
>>
>> Hi,
>>
>> I'm using SAPDB 7.4.0.35 (32bit linux) on one of our linux 
>> servers, all 
>> clients from Windows and Linux (both 32bit) can access the server w/o 
>> any problem. Now I need to access the server from a 64bit 
>> linux client.
>>
>> I tried to find a 64bit SAPDB client (7.4.x) for 64bit Linux, 
>> but there 
>> is only a iA64 version and no x86_64 version of the SAPDB software at 
>> http://www.sapdb.org/7.4/rpm_linux.htm, so I've installed the 
>> maxdb-callif packages from mysql.com on RHEL4 and Fedora Core 4, ie.
>> maxdb-callif-7.5.0.34-1.x86_64.rpm/maxdb-callif-7.6.0.34-1.x86_64.rpm
> 
> [problem with select]
> 
> Maybe the ODBC-trace might help. Please add
> 
> tracefilename=<your trace file>
> 
> to the DSN-entry.
> 
> 
> FYI, with 64-bit some data types changed in the ODBC interfaces (e.g. SQLLEN is on 64-bit machines a 64-bit integer). See for example SQLGetData:
> 
> SQLGetData(SQLHSTMT StatementHandle,
>            SQLUSMALLINT ColumnNumber, SQLSMALLINT TargetType,
>            SQLPOINTER TargetValue, SQLLEN BufferLength,
>            SQLLEN *StrLen_or_Ind);
> 
> 
> Does the application and the driver manager handle it properly in the 64-bit environment?
> 
> 
> Regards  Thomas
> 
> 
> 
> 
> ----------------------------------------------
> Dr. Thomas Kötter
> SAP AG, Berlin
> NW EIM MLC IFA
> 
> MaxDB: all you need!                   
> www.sdn.sap.com/irj/sdn/maxdb  www.mysql.com/products/maxdb  www.sapdb.org  
> 
> Sitz der Gesellschaft/Registered Office: Walldorf, Germany
> Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, Léo Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke
> Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner 
> Registergericht/Commercial Register Mannheim No HRB 350269
> 
> Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt.
> Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.
> 
> This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation. 
>  
> 


-- 
IEE S.A. International Electronics & Engineering
Zone Industrielle, L-6468 Echternach, Luxembourg
Phone +(352)72 89 89-801, Fax +(352)72 89 89-109

This e-mail may contain trade secrets or privileged, undisclosed
or otherwise confidential information. If you are not the intended
recipient and have received this e-mail in error, you are hereby
notified that any review, copying or distribution of it is strictly
prohibited. Please inform us immediately and destroy the original
transmittal from your system. Thank you for your co-operation.

-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.