|
|
|
причины ORA-02064: distributed operation not supported
|
|||
|---|---|---|---|
|
#18+
есть такая штука Код: plsql 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. в rep_R@uo следующее: Код: plsql 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. Валится на commit; ORA-02064: distributed operation not supported. нужно ли оно там, данных в мердж попадает многа, сегмент отката увеличивать не вариант. ХЗ, причина ли в этом? Удаленная БД Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production. ... |
|||
|
:
Нравится:
Не нравится:
|
|||
| 04.09.2017, 09:33 |
|
||
|
причины ORA-02064: distributed operation not supported
|
|||
|---|---|---|---|
|
#18+
http://www.cyberforum.ru/oracle/thread703518.html Попробуйте перенести commit из 2 в 1 процедуру. ? ... |
|||
|
:
Нравится:
Не нравится:
|
|||
| 04.09.2017, 09:53 |
|
||
|
причины ORA-02064: distributed operation not supported
|
|||
|---|---|---|---|
|
#18+
saxarockпричины ORA-02064... https://asktom.oracle.com/pls/apex/f?p=100:11:::NO:RP:P11_QUESTION_ID:9534655900346492970 and we said... In a distributed transaction -- one in which "DATABASE A" calls "DATABASE B", only "DATABASE A" may commit. The reason is "database B" has no mechanism for co-ordinating with "database a" on the commit. We need to do a 2 phase commit to ensure that when the transaction commits any work performed on DATABASE A is committed *as well as* any work on database b. Because the problem is more complex in general when database A calls both database B and database C. Here, if database B (which has NO IDEA that database C is even involved) attempted to commit -- it would not be able to coordinate with database A and having no knowledge of the existence of database C in the transaction -- could not coordinate it either. A common workaround is an optional parameter to the existing routine -- a commit flag (make it be something like: p_do_not_commit boolean in default FALSE ); You will then seek out all commit and rollback statements in the affected routine and rewrite them as: if ( NOT p_do_not_commit ) then commit; end if; so the routine can be called locally or remotely, and the parameter set accordingly. ... |
|||
|
:
Нравится:
Не нравится:
|
|||
| 04.09.2017, 10:06 |
|
||
|
причины ORA-02064: distributed operation not supported
|
|||
|---|---|---|---|
|
#18+
Viewer, Код: plsql 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. ... |
|||
|
:
Нравится:
Не нравится:
|
|||
| 04.09.2017, 11:42 |
|
||
|
|

start [/forum/topic.php?fid=52&fpage=147&tid=1885317]: |
0ms |
get settings: |
6ms |
get forum list: |
20ms |
check forum access: |
3ms |
check topic access: |
3ms |
track hit: |
47ms |
get topic data: |
11ms |
get forum data: |
2ms |
get page messages: |
51ms |
get tp. blocked users: |
1ms |
| others: | 216ms |
| total: | 360ms |

| 0 / 0 |
