Kbase P133847: Hitting limit to number of temp-tables
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/7/2009 |
|
Status: Verified
SYMPTOM(s):
Hitting limit to number of temp-tables
Unable to assign file number to temp-table <name>. Number of active temp-tables reached limit of 32767. (9287)
FACT(s) (Environment):
All Supported Operating Systems
Progress 8.x
Progress 9.x
OpenEdge 10.x
CAUSE:
The code in question was making repeated calls, in a loop, to a procedure which defined some UNDO-able temp-tables. These temp-tables stay in memory as long as there is a transaction active. Progress doesn't throw away/delete UNDO-able temp-tables if there is an active transaction, since the LBI file could have references to a temp-table that would be gone at the end of the transaction. Since the procedure was deleted between calls the perception was that the objects it defined were also gone but this wasn't the case for the UNDO-able temp-tables.
FIX:
- If possible, limit the scope of the transaction - This will allow Progress to remove temp-tables that are no longer referenced Or... - Define all temp-tables as NO-UNDO Or... - Consider whether the procedure which defines the temp-tables could be run once, persistently, and re-used