ODBC stops after ~2000 records

[Roger D]

Im using SQL Server DTS 7 with Merant ODBC to get my data from PROGRESS 8.3E into SQL Server 7 SP3.

Now the problem is, Progress is cutting off the transformation after only about 2 seconds or 2000 records.

Is there a typical setting in the ODBC that has to be changed ?
Or is there a Progress server-side setting that is not set correctly for these data retrieval actions?

I have tried all kind of settings on SQL Server
- with and without fastload
- high and low fetch and commit sizes

I have tried different tools, but they all get the same error, and they all depend on the Merant 32Bit ODBC driver (3.70) IVPRO16.dll

 

[Roger D]

Error code 915

Originally posted by Roger D
Im using SQL Server DTS 7 with Merant ODBC to get my data from PROGRESS 8.3E into SQL Server 7 SP3.

Now the problem is, Progress is cutting off the transformation after only about 2 seconds or 2000 records.

Is there a typical setting in the ODBC that has to be changed ?
Or is there a Progress server-side setting that is not set correctly for these data retrieval actions?

I have tried all kind of settings on SQL Server
- with and without fastload
- high and low fetch and commit sizes

I have tried different tools, but they all get the same error, and they all depend on the Merant 32Bit ODBC driver (3.70) IVPRO16.dll

Here is the exact error reported by the client-side applications:

[MERANT][ODBC PROGRESS driver][PROGRESS]Lock table overflow, Increase -L on server (915)
[MERANT][ODBC PROGRESS driver][PROGRESS]Transaction backout completed. (2253)

The error also occurs when changing an SQL statement from
SELECT colum1 FROM table1
into
SELECT DISTINCT column1 FROM table1

 

[bendaluz2]

It seems that your query is locking the records you are getting. In progress you would get the records "NO-LOCK" to stop this from happening, but I dont know if there is an SQL equivalent to do this. There may also be a way of configuring the Merrant driver so that select operations are no-lock. If all else fails, just do what the error message suggests and increase -L on the server. On the command line that starts the Progress Database, you may (or may not have) the following parameter:
<pre>-L value</pre>
Simply increase the value until you no longer get the problem. If the parameter is not there, then add it (I think the default value is 500). Of course this is not the ideal solution, becuase really these records should not be locked as you are not updating them at this point. Also, increasing the -L parameter will increase memory overhead for the Progress database and it could be also true that you want to query more records than the maximum value of -L will permit.

Originally posted by Roger D
Here is the exact error reported by the client-side applications:

[MERANT][ODBC PROGRESS driver][PROGRESS]Lock table overflow, Increase -L on server (915)
[MERANT][ODBC PROGRESS driver][PROGRESS]Transaction backout completed. (2253)

The error also occurs when changing an SQL statement from
SELECT colum1 FROM table1
into
SELECT DISTINCT column1 FROM table1