Kbase P26535: What are common causes for error 893 and error 9874
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
01/12/2010 |
|
Status: Verified
GOAL:
What are common causes for error 893 and error 9874
GOAL:
Troubleshooting 'SYSTEM ERROR: strent request for more than 32K. (893)'
GOAL:
Troubleshooting 'SYSTEM ERROR: strent request for more than 64K. (9874)'
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
FIX:
First, determine if this error occurs on the database side or the client side. If it's database, it should appear in the database log file, if it's client side shouldn't.
Another easy way to spot if the error occurs on the database or on the client side is by taking a look at the protrace file that should have been generated at the time of the error. This will show the executable name used, and thus on which side the error occurred: _mprosrv indicates it's the database side; _progres, _proapsv, prowin32 are all client side.
If it's on the database side, it usually means there are too many queries open at the same time. This can be caused by a bug in the database engine leaving queries open (at the time of writing, there are no such bugs known in the current version 10.1A02), or having large numbers of database queries active at the same time in the application.
Also in older versions of Progress, old instances of a query weren't closed when you open the query a second time. They had to be closed manually before the second open was performed.
On the client side, the error can occur because of a number of causes; the most common are:
- Not properly cleaning up dynamically created objects. This includes the dynamic temp-tables that are implicitly created when a temp-table is passed as an INPUT parameter.
- Not properly cleaning up persistent procedures when they are no longer needed.
- Too many queries being left open on temp-tables. (this is much the same as a database side occurrence of the error)