Why does DBMS_MVIEW.REFRESH have an implicit commit?

oracle transactions materialized-views
Nick Pierpoint picture Nick Pierpoint · May 6, 2009 · Viewed 7.7k times · Source

I noticed recently that calling dbms_mview.refresh(...), which refreshes materialized views in Oracle, has an implicit commit.

Any ideas - other than "because it does" - why this action has an implicit commit?

Answer

Leigh Riffel picture Leigh Riffel · May 6, 2009

According to Tom Kyte it is because a decision was made at design time to consider refreshing to be a DDL operation. Since all DDL operations implicitly commit, so does this one. Unfortunatly he doesn't answer the resulting question of why they choose to make it DDL.

Related questions

What is the difference between Non-Repeatable Read and Phantom Read?

What is the difference between non-repeatable read and phantom read? I have read the Isolation (database systems) article from Wikipedia, but I have a few doubts. In the below example, what will happen: the non-repeatable read and phantom read? Transaction …

Read More
Do DDL statements always give you an implicit commit, or can you get an implicit rollback?

If you're halfway through a transaction and perform a DDL statement, such as truncating a table, then the transaction commits. I was wondering whether this was always the case and by definition, or is there a setting hidden somewhere that …

Read More
Error on Oracle while using DBLINK

I am Using jboss5.1.x, EJB3.0 ,JPA3. I am trying to do 'select' query from view which is connected via dblink to another database. source database is Oracle 9, destination dabatase is Oracle 8. I am getting this error: 15:27:06,625 WARN [JDBCExceptionReporter] SQL …

Read More