does a single session suport concurrent transactions?

what circumstances does a single session have multiple concurrent transactions?

thanks.

Vince

no circumstances directly, but you can use DBMS_JOB to submit multiple jobs in parallel. They actually execute in a different session though.

Sort of: autonomous transactions.

When using autonomous transaction your session actaully executse two concurent transactions: a normal transaction and inside it (kind of "wrapped") a totaly separate autonomous transaction.

Are autonomous transactions sequential, or parallel?

Jurij :

Still than it cannot be called concurrent, as I belive its SEQUENTIAL ...

Abhay.

Autonomous transactions ar not sequential, they are parallel. When you open an autonomous transaction from within a "normal" transaction, you have two concurent transactions opened. They are totaly independant one from another. And once you are inside an autonomous transaction, you can again open yet another autonomous transaction. There are no actual limits on this nesting of autonomous transactions, other than available resource limits.

So again, it is not serializable proces (like the start of one transaction implicitely ends the previous transaction), it is parallel - at the same time you can have N number of opened transactions (one "normal" transaction and N-1 autonomous transactions). However it is true that at any one time you have control of closing only one transaction - the one that was opened the last. With each new autonomous transaction you implicitely suspend the execution of its outer transaction. Once you commit or rollback the innermost autonomous transaction you gat back the control over its outer transaction.

i think AUTONOMOUS TRANSACTIONS is what you are looking for.
From within a PL/SQL you may be in middle of tranx and start an AUTONOMOUS transaction involving other tables...
It all happens from within the same session.
Best luck...

Quote:

---

Originally posted by and
i think AUTONOMOUS TRANSACTIONS is what you are looking for.

---

Hm, I wonder what we have been discussing in last few posts of this thread..... :rolleyes:

Quote:

---

Originally posted by jmodic
However it is true that at any one time you have control of closing only one transaction - the one that was opened the last. With each new autonomous transaction you implicitely suspend the execution of its outer transaction. Once you commit or rollback the innermost autonomous transaction you gat back the control over its outer transaction.

---

Ah, that's the kind of serialization i meant, not the transaction-control serialization -- shall we call it "temporal serialization"?

Quote:

---

Originally posted by slimdave
shall we call it "temporal serialization"?

---

Fair enough.

And BTW, as far as the original question is concerned ("what circumstances does a single session have multiple concurrent transactions?"): it's not only explicit authonomous transactions that kind-of cause this - there are also "implicit" autonomous transactions, so called "recursive transactions". Even before the autonomous transactions were made available in 8i, RDBMS could still implicitely execute recursive (implicitely autonomous) transactions from within "normal" transactions. So even if you never use autonomous transactions, strictly speaking there are still moments when your session actually owns two concurrent transactions. That's also the reason why the default value of the parameter TRANSACTIONS is 10% greater than the parameter SESSIONS.