Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.8K Databases
- 221.5K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.8K SQL & PL/SQL
- 21.2K SQL Developer
- 295.3K Development
- 17 Developer Projects
- 138 Programming Languages
- 292K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 27 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 390 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1K Español
- 1.9K Japanese
- 230 Portuguese
Is it possible to analyze transaction ( all IUD clauses during one commit time ) based on one IUD c

Hello,
Is there a way to find all IUD clauses in one transaction* based on the identitiy of one IUD SQL clause which is located in V$% dictionary views?
For example:
1. Transaction is consisted from
1.1
Insert Into T1
Update T2
Delete from T3
1.2 In V$ dictionary view we locate Update T2 set , ..where ...with host variables and constants
And on basis of this internal identification I would find
other two SQLs ( Insert, Delete ) on presumptions there is somewhere in the system recorded that
those 3 clauses happened in one commit operation.
2. Other example:
2.1 Insert Into T1...
Loop
Update T2
exit when...
End Loop;
commit;
Here also able to reverse engineer that find that with Insert Into T1 is related also Update T2.
3. IS this also possible to manage same way in
distributed db environments ( multiple instances ) or cluster environment?