Dropping a table [message #53570] |
Sun, 29 September 2002 22:15 |
bmishra
Messages: 1 Registered: September 2002
|
Junior Member |
|
|
Suppose I am running a query on a big table which takes
some time.If another session drops this table while my
query is running, what exactly happens?
When we tried to simulate the above scenario,we observed that we could easily drop the table while the query was running in the other session.We know that our buffer size is much lesser than the table.
We feel that probably oracle has only deleted the table
entry from the data dictionary and the data still exists on the disk so that the other session could access it.
|
|
|
Re: Dropping a table [message #53576 is a reply to message #53570] |
Mon, 30 September 2002 04:10 |
|
Mahesh Rajendran
Messages: 10708 Registered: March 2002 Location: oracleDocoVille
|
Senior Member Account Moderator |
|
|
oracle's default TRANSACTION CONSISTENCY deal with this.
untill the session2 commits, session1 will not see any changes.
there are methods, with which, you can LOCK the table, for consistency.
|
|
|