Kbase P115486: Memory violation when running a query while the session is not connected to the ORACLE database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/24/2006 |
|
Status: Unverified
FACT(s) (Environment):
Unix
ORACLE DataServer
SYMPTOM(s):
Memory violation when running a query
SYSTEM ERROR: Memory violation. (49)
The session is not connected to the ORACLE database
Connecting via the Unified DataServer broker started from the Progress Explorer
The connection parameters stored in the schema holder are correct
The following errors occur when connecting via the _probrkr broker:
BROKER: Could not spawn a server. (1890)
Failed to connect to ORACLE database orasport. (1451)
Stack trace from _progres reads:
ncsconndll
ncsconn
ncacon
oracon
fdcon
scconx
sccon
rnlksch
crrun_entry
rninterpret
umeDispatchEvent
wvRunDispatcher
iodispatch
rnrq
main
The problem does not occur when the ORACLE database is already connected.
Starting the Progress session like the following:
_progres <schema holder> -1 -db <logical ORACLE database name>
CAUSE:
This is a known issue being investigated by Development.
FIX:
When starting the Progress session, at least the Oracle database name should be specified.
For example:
_progres shsports -1 -db orasports
shsports is the schema holder name, and orasports is the name given to the ORACLE database when creating the schema holder. The connection parameters stored in the schemea holder will be automatically used when establishing the connection.