Kbase P20585: ODBC Driver error - Lock Table overflow using Access - change isolation level
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/07/2010 |
|
Status: Verified
SYMPTOM(s):
ODBC call failed - Data Direct ODBC driver - lock table is full.
Error occurs when extracting information from Progress into an MS Access database.
Database log file contains Progress error (915).
Lock table overflow, increase -L on server (915)
Using the MS Access make-table query statement.
Promon indicates that the 'Lock Table High Water Mark' has been reached.
FACT(s) (Environment):
Windows
Progress/OpenEdge Product Family
CAUSE:
The MS Access make-table query locks all the records in the table that it is copying. This, combined with other locking activity occurring on the database, results in the Progress lock table being exceeded.
FIX:
To resolve this problem, choose one of the following two methods:
1) Set the default isolation level on the ODBC DSN to READ UNCOMMITTED. This means that no shared locks are issued and no exclusive locks will be honored. When this isolation level is set, it is possible to read uncommitted (dirty) data. This option has the same effect as setting NOLOCK on all tables in all SELECT statements in a transaction.
2) Increase -L database startup parameter to accommodate the increased number of records being locked.