[unixODBC-support] unicODBC 2.03 Redhat Linux 64 bit machine

Nithesh Shetty knitheshshetty at yahoo.com
Fri Sep 9 06:27:25 BST 2011


Hi Neha,
 
Its RHEL 6 and i have tried with int64_t 
 
it gives the same segmentation fault.
 
Regards,
 
Nithesh

From: Neha Avasthy <neha.avasthy at gmail.com>
To: Nithesh Shetty <knitheshshetty at yahoo.com>; Support for the unixODBC project <unixodbc-support at mailman.unixodbc.org>
Sent: Friday, September 9, 2011 9:16 AM
Subject: Re: [unixODBC-support] unicODBC 2.03 Redhat Linux 64 bit machine


Hey Nithesh, 

You need to refer to the ODBC specs for 64 bit platforms.

http://msdn.microsoft.com/en-us/library/ms716287(VS.85).aspx

It clearly says that 

SQLSetStmtAttr
When the Attribute parameter has one of the following values, a 64-bit value is passed in *ValuePtr:
..SQL_ATTR_ROW_ARRAY_SIZE

You may have to change the datatype for maxrows (use an 8 byte type) in your SQLSetStmtAttr call.




Thanks
-Neha

On Thu, Sep 8, 2011 at 7:01 PM, Nithesh Shetty <knitheshshetty at yahoo.com> wrote:

Driver is oracle 11 g
>
>
>
>From: Nick Gorham <nick at lurcher.org>
>To: Nithesh Shetty <knitheshshetty at yahoo.com>; Support for the unixODBC project <unixodbc-support at mailman.unixodbc.org>
>Sent: Thursday, September 8, 2011 6:15 PM
>Subject: Re: [unixODBC-support] unicODBC 2.03 Redhat Linux 64 bit machine
>
>
>
>On 08/09/11 13:39, Nithesh Shetty wrote: 
>Hi,
>>
>>when i set the attribute in SQLSetStmtAttr to SQL_ATTR_ROW_ARRAY_SIZE then it gives segmentation fault 
>>at SQLFetchScroll on 64 bit rhel 6.
>>
>>Same call works fine on 32 bit rhel 5.
>>
>>Cal syntax ls
>>
>>SQLHSTMT hstmt;
>>....
>>..
>>SQLINTEGER maxrow = 5000;
>>SQLSetStmtAttr(htmst, SQL_ATTR_ROW_ARRAY_SIZE, (SQLPOINTER)maxrows, SQL_IS_INTEGER);
>>
>>..
>>..
>>..
>>SQLFetchScroll(hstmt, SQL_FETCH_NEXT, 0);
>>
>>skipped the intermediate function calls. since
>> i comemnt SQLSetStmtAttr the function SQLFetchScroll does not give segmentation fault.
>>Awaiting your reply.
>>
>>Regards,
>>Nithesh
>You don't mention what driver you are using as the driver manager passes this directly to the driver. I suspect its a sizeof( SQLLEN ) issue between your ap, the driver manager and your driver.
>
>-- 
>Nick
>
>
>
>_______________________________________________
>unixODBC-support mailing list
>unixODBC-support at mailman.unixodbc.org
>http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.unixodbc.org/pipermail/unixodbc-support/attachments/20110908/f887149a/attachment.html>


More information about the unixODBC-support mailing list