Notes 6.0.3 returning every second record from SQL query via ODBC

Hi all

Since upgrading one of my servers to 6.0.3 from 6.0.2 CF1, I’ve been experiencing an unusual issue with an agent that pulls records from an AS/400 via an ODBC connection.

When the agent is run on the server (ODBC driver is Client Access Express 8.00.02.00 - I am looking into upgrading to an iSeries Access driver), the ODBC result set appears to be returning every second record. No errors are returned.

If I run the same query in, say, WinSQL (also from the server, using the same DSN) it returns all the correct records from the query, so I am pretty sure it’s Notes causing the problem.

I have tried playing with resultset.CacheLimit and .FetchBatchSize but neither have helped. The agent is still running fine on one of the 6.02CF1 servers.

Has anyone else experienced this type of issue? Any thoughts? Thanks in advance for any help

–Lachie

Subject: RE: Notes 6.0.3 returning every second record from SQL query via ODBC

Another person asking a question about code that they don’t bother to post.

Don’t know about any problem with this, but perhaps you could try a rewrite using the LC LSX.

Subject: RE: Notes 6.0.3 returning every second record from SQL query via ODBC

My apologies for the incomplete post. I read your guidelines to posting a technical question before I posted mine and thought I had everything covered. I didn’t post code as I didn’t feel that any was relevant - the only variable in this situation that had changed was the server version. Thanks for the tip re: LC LSX, I will look into it.

Subject: RE: Notes 6.0.3 returning every second record from SQL query via ODBC

Lachie,

we are facing the same problem. Any news ?

Thanks,

Frank

Subject: RE: Notes 6.0.3 returning every second record from SQL query via ODBC

I recently started experiencing the same issue with an agent. The agent has been running for two years without any problems. Now it is skipping rows in our table. I am using lotuscript and LSXODBC to access the data on the As400. Supposely nothing changed on the server or on the As400. We are running Domino 6.5 on the server. Did you ever resolve your issue?