Home » Developer & Programmer » Precompilers, OCI & OCCI » OCIStmtExecute gets locked (merged)
OCIStmtExecute gets locked (merged) [message #314660] Thu, 17 April 2008 07:30 Go to next message
vaishalikatarki
Messages: 43
Registered: April 2008
Location: Bangalore
Member

Hi,

In my application the OCIStmtExecute gets locked when a statement is execute.Please find the stack dump below.

current thread: t@4
[1] __lwp_park(0x0, 0x0, 0x0, 0x0, 0x1, 0x0), at 0xff365994
[2] mutex_lock_queue(0xff378b44, 0x0, 0x709660, 0xff378000, 0x0, 0x0), at 0xff36166c
[3] slow_lock(0x709660, 0xfe1f0600, 0x70a1b8, 0x1, 0xfc7d3afc, 0x4), at 0xff36206c
[4] kpuexec(0x64f554, 0x8ff600, 0x70a1b8, 0x1, 0x0, 0x0), at 0xfc9c0704
[5] OCIStmtExecute(0x64f554, 0x8ff600, 0x70a1b8, 0x1, 0x0, 0x0), at 0xfc96f434

Wanted to know what is the reason for lock and how can we avoid this.
OCIStmtExecute() gets locked for more than 30-50 seconds [message #315378 is a reply to message #314660] Mon, 21 April 2008 05:58 Go to previous message
vaishalikatarki
Messages: 43
Registered: April 2008
Location: Bangalore
Member

Hi,

The OCIStmtExecute() gets locked for more than 30-50 seconds and then returns back. Please check the stac k dump below:

fdbc0594 lwp_park (0, 0, 0)
fc9c070c kpuexec (6ef914, 9d4134, 752218, 1, 0, 0) + 2dc
fc96f43c OCIStmtExecute (6ef914, 9d4134, 752218, 1, 0, 0) + 30
fe8157e8 __1cNCOCIStatementHExecute6M_b_ (fc6d4220, 1, fc6d470c, 0, fc6dc17c, 8b68
38) + b8
fe75dba4 __1cLAcctRDMS_DBLcheckHealth6M_b_ (662290, fc6d77c0, 0, da388, 456ce8, 0)
+ c4
fe7c91cc __1cRCommonDBClientAPINcheckDBHealth6M_b_ (457450, 1, 465340, 0, fc6dc17c
, 8b6838) + 124
000d1b20 __1cRAcctClientRequestOacctClientMain6M_v_ (456ce8, 0, 45f290, da388, 456
ce8, 0) + 4460
000da3c0 __1cRAcctClientRequestQacctClientThread6Fpv_v_ (456ce8, 1, 0, 0, 395d84,
0) + 38
feb4306c __1cVACE_OS_Thread_AdapterGinvoke6M_pv_ (45f290, 0, 45f290, da388, 456ce8
, 0) + c4
feb42d5c ace_thread_adapter (45f290, fc6fc000, 0, 0, 395d84, 45f290) + 3c
fdbc04f4 _lwp_start (0, 0, 0, 0, 0, 0)

Can anyone help how can we avoid such situations?



Previous Topic: ORA-24343: user defined callback error
Next Topic: PRO*C
Goto Forum:
  


Current Time: Thu Dec 08 12:51:31 CST 2016

Total time taken to generate the page: 0.06908 seconds