Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a global temp table which is set as delete on commit. How does it behave on concurrency issue? I mean what happens if another session wants to use that global temporary table? The answer will probably not be “they share the same data”.
Now, if my guess is correct :), is the table locked until the first connection commits, or does the dbms create a global temp table for each connection? ( something like an instance of the table? )
From the documentation:
Each session will have its logical independent copy of the temporary table.
Since you can not see other sessions’ data and since Oracle deals with locks at the row level, you can not be blocked by other sessions’ DML. Concurrent DML (Insert, Delete, Update) won’t affect other sessions.
Only DDL will need a lock on the table (ie: ALTER TABLE…)