Core dump when concurrent allocate context in different threads
From: Chen Weiwen <chenww_at_hpsgns1.sgp.hp.com>
Date: Wed, 5 Jan 2000 13:30:43 +0800
Message-ID: <84uku4$rv$1_at_news.vcd.hp.com>
I am implementing a corba server with the PRO*C+OCI interface to the back-end ORACLE DB. thus it will initialize a pool of oracle contexts by the main threads at the start up phase, and another particlar thread(child) will initialize a dedicated context for itself. However the two allocations can not run concurrently. the svr will core dump. Only after the child thread is delayed for sometime, the svr is all right! so i would like to know whether there is such restriction in ORACLE to allocate context. How can i avoid the core dump while allow the concurrent allocate context?
Date: Wed, 5 Jan 2000 13:30:43 +0800
Message-ID: <84uku4$rv$1_at_news.vcd.hp.com>
I am implementing a corba server with the PRO*C+OCI interface to the back-end ORACLE DB. thus it will initialize a pool of oracle contexts by the main threads at the start up phase, and another particlar thread(child) will initialize a dedicated context for itself. However the two allocations can not run concurrently. the svr will core dump. Only after the child thread is delayed for sometime, the svr is all right! so i would like to know whether there is such restriction in ORACLE to allocate context. How can i avoid the core dump while allow the concurrent allocate context?
here is my platform:
OS: HP/UX 11.0
ORACLE: 8.0.5
Compiler: aCC1.21
thanks ahead
urs
hanson chen
Received on Wed Jan 05 2000 - 06:30:43 CET