| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: core dump in oracle
I think i found out the problem that caused this core dump ...
in the init.ora we are setting one parameter
event='10235 trace name context forever, level 2'
why we use it in first place .....
thats because of following explanation
"ora-60 deadlock detected"
This occurs when using the LOB storage type for the logical network.
Additional information is present in the sde.errlog: S_update_attr_LOBS::OCILobWrite error (-51)
Additional information is also present in the Oracle alert log: ORA-000060 Deadlock detected. More info in file <path>/<name>.trc
Cause
The cause of the problem is Oracle bug '3166756 Self deadlock (ORA-60)
possible on LOB index update'.
See Oracle's Metalink for additional information.
The problem is present in releases 9.2.0.3, 9.2.0.4 and 9.2.0.5 and reported as being fixed in releases 9.2.0.6 and 10.1.0.3.
Solution or Workaround
Select an option below:
Upgrade to Oracle release 9.2.0.6/10.1.0.3 Set the following Oracle event in the init.ora file:
event='10235 trace name context forever, level 2'
Once enabled the geometric network builds successfully
it is a work around for geometric network builds but some how it fails the normal select query.
any idea what could be the reason .... Received on Wed Oct 19 2005 - 02:23:25 CDT
 |
 |