Skip to content Skip to sidebar Skip to footer

Pyodbc Cursor.fetchall() Causes Python To Crash (segfault)

I am using Python 2.7 on Windows XP. I have a simple python script on a schedule that uses pyodbc to grab data from an AR database which has worked perfectly until today. I get a

Solution 1:

Q: You're on Windows/XP (32-bit, I imagine), Python 2.7, and BMC Remedy AR. Correct?

Q: Is there any chance you (or perhaps your client, if they purchased Remedy AR) can open a support call with BMC?

Q: Can you isolate which column causes the segfault? "What's different" when the segfault occurs?

Please do the following:

1) Try different "select a,b,c" statements using Python/ODBC to see if you can reproduce the problem (independent of your program) and isolate a specific column (or, ideally, a specific column and row!)

2) Enable ODBC tracing: http://support.microsoft.com/kb/274551

3) Post back the results (including the log trace of the failure)

4) If that doesn't work - and if you can't get BMC Technical Support involved - then Plan B might be to debug at the ODBC library level:

Solution 2:

for any one else who might get this error, check the data type format returned. in my case, it was a datetime column. used select convert(varchar, getdate(), 20) from xxx, or any convert formats to get your desired result.

Post a Comment for "Pyodbc Cursor.fetchall() Causes Python To Crash (segfault)"