Kbase P112066: Oracle DataServer client crashes with memory violation program when running find current exclusive
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/03/2007 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1x
OpenEdge 10.x
Oracle DataServer
SYMPTOM(s):
Progress crashes with memory violation
find current exclusive lock query is executed from 2 different sessions
Persistent procedures have been loaded in memory when starting the session
The connection is performed via the _probrkr broker
The following error messages appear depending on the context:
** Error : Unable to allocate more memory for records or variables. (4)
** Error 0: Unable to allocate more memory for records or variables. (4)
** Attempt to expand record beyond the maximum allowed size. (444)
The crash also occurs when connecting via the unified DataServer broker
The problem does not occur when using ORACLE Networking (Net*8)
CAUSE:
Bug# OE00129926
FIX:
Upgrade to 10.1A02 or later.
If upgrading is not an option as a workaround, connect to the ORACLE database via the ORACLE networking instead of using the _probrkr DataServer broker.
This configuration requires that the ORACLE client product is installed on the remote client machine.
In the connection parameters, all parameters related to the DataServer broker (-H, -N, -S) has to be removed, and the name of the ORACLE instance should be added to the User ID:
-U <User ID>@<Instance Name>