Obviously, if your application requires those types of updates, this guideline wouldn't necessarily apply to you. ll delete a row, commit the operation, and try to recover the deleted record.
Being able to flashback DML operations has greatly reduced the frequency of how often you hear a DBA say, ? FLASHBACK TABLE CITY_OFFICES 2 TO TIMESTAMP (SYSTIMESTAMP - INTERVAL '05' minute); FLASHBACK TABLE CITY_OFFICES *ERROR at line 1: ORA-08189: cannot flashback the table because row movement is not enabled The error message in this case is much clearer as to the nature of the failed statement.
As far back as Oracle 8.1.5 documentation, row movement applied to updatable partition keys.
A list partition where the partition key is a specific value is a good example of this.
Does a row move to another table, or is row movement constrained to the row's container (i.e., a table)?
Its online knowledge sharing hub and the best platform for learner and Experience holder as OAG makes easy to do your assignment in Oracle Apps R12 and 11i.
You may have expected office_number 4's ROWID to change, but not office_number 1's, but it too changed location after the shrink.
The moral of the story here supports what the documentation says (in more than one place): Before you use rowids in DML statements, they should be verified and guaranteed not to change.
The landmark book "Advanced Oracle SQL Tuning The Definitive Reference" is filled with valuable information on Oracle SQL Tuning.
This book includes scripts and tools to hypercharge Oracle 11g performance and you can buy it for 30% off directly from the publisher.
The intended rows should be locked so they cannot be deleted.