|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by Jeffreymarcum in Oracle 10.x, Oracle 9.x, PL / SQL
We have a PL/SQL package that calls another package over a database link. The remote packaged procedure is an autonomous transaction that updates some tables and then calls another package back across another database link to the original Oracle instance. That package updates some other data and returns to the remote instance which commits the autonomous transaction and returns to the first package.
Sporadically, the original session then hangs and has to be killed. It's one of those situations where just killing it doesnt work; you have to also kill the Unix process as well.
The process works intermittently with seemingly no consistency as to where it ends up locking. It comes back from the remote process where that DOES consistently work/commit its data - it's after the fact that we get the lock.
We've looked at the V$ tables and it doesn't appear that any row locking is occurring. The local process is not updating any of the data that the remote process (or it's local surrogate) is touching. The session that hangs shows an event "DX - Contention". I don't know whether or not that is significant, but it's consistent.
I'm not even positive that the problem is this convoluted distributed transaction and not something else. Anyone have any ideas?
20100308-EE-VQP-132 / EE_QW_2_20070628