dvz,
Thanks for the insight. We're investigating your solution today and were running some traces. We have one discrepancy though... We are using dedicated servers. We found a similar bug in Metalink - bug 4648039 which details the problem above in a dedicated environment. Anyway, I'll accept your solution and assign points. If you can provide any more information, we would appreciate it.
Based on your late posting time, my team was curious of your location. We're in Florida
Main Topics
Browse All Topics





by: dvzPosted on 2008-07-01 at 20:19:17ID: 21913185
You didn't mention that your instance is crashing with ORA-600, so I'm going to go with the advice from Metalink that you may be affected by bug #4627237, which is patched in 10.2.0.3.
If an autonomous procedure which accesses a remote database is invoked
inside a distributed transaction which itself accesses the remote
database, then if the remote instance uses shared servers a
deadlock can occur.
Workaround:
Use dedicated servers