0

I have a series of rename table ddl statements that I would like to run within a transaction. During this period, there will also be other sessions that will be running as well which might hijack the tables used for the rename above and cause a resource contention/deadlock.

Is it possible to achieve that in Oracle? Understand that each ddl statements will commit after each execution which will free up the tables for other sessions to hijack. How can I ensure that the current session that is executing the DDL statments complete successfully before other sessions can access the tables?

--LOCK TABLE a  
RENAME tbl a to b
--possible contention as commit release the lock on tbl a 

RENAME tbl b to c 

RENAME tbl c to d

--commit
ıllıllı lק ıllıllı
  • 808
  • 2
  • 19
  • 40
user1008697
  • 1,141
  • 2
  • 10
  • 13
  • Maybe: http://stackoverflow.com/a/12193521/14955 – Thilo Jun 20 '14 at 09:27
  • @Thilo Unfortunately the `CREATE SCHEMA` feature only supports a small number of DDL commands and RENAME is not one of them. – Jon Heller Jun 21 '14 at 22:52
  • possible duplicate of [Oracle: DDL and transaction rollback](http://stackoverflow.com/questions/4711447/oracle-ddl-and-transaction-rollback) – podiluska Jul 09 '14 at 14:34

1 Answers1

2

DDL statements in Oracle are each a transaction. Each DDL statement causes few or many changes in the data dictionary, like obj$. I am not sure, but looking at the major work Oracle has gone through to ensure that locking is not an issue with even the early versions of their platform, I think they found it easier to commit per DDL statement to keep the locks short in time and avoiding dead locks within a session or between sessions doing DDL. Under some circumstances, you can still feel that the Oracle kernel doesn't lock dropping and creating to many objects during production use with ORA-600 thrown at your head.

As a workaround, you can either use the datamodel versioning introduced a few years ago. I have no working experience with it since it is too restricted for my work, but you can find more on it by googling on 'Edition-based redefinition' or going to Oracle manual. It might not be available in the licensed edition of Oracle you are working on.

As a workaround, you can execute the statements during uptime. But this will generally break sessions unless the code your users are executing automatically recovers easily. Remember that each object has an ID and a name. Changing the name might not change the ID, so many pointers to the object will need to be refreshed, leading to ORA-4063 or alike. Oracle has no pause/suspend for sessions as far as I know.

Guido Leenders
  • 4,232
  • 1
  • 23
  • 43