Kk wrote:no i didnt "commit "
Did you perform a commit ? If yes , then its not possible to get the old state of the table back ( with 10 rows).
An approach that you should follow if the inserts are so uncertain is that take an export of the table on which DML is expected , and incase of a failed DML ( when committed but need the old data back) either perform a delete or simply drop the table and import it .drop and import? what to import?
Ofcourse you wont be doing these experiments on the Prod setup.no im testing
this would take an export of the table. Post of your analysis you can execute the following :
exp system/<password> owner=yourschema tables=tablename file=check.dmp log=cehck.log
drop table ABC exit; imp system/password owner=yourschema tables=tablename file=check.dmp log=check.log
Hemant K Chitale wrote:hey thanks , but what is Logminer and how to extract undo statement
You can use LogMiner on the ArchiveLogs to extract the Undo statement as an SQL command and then execute it. We assume that the rows in the table haven't again been updated since that update 4 months ago.
Other than that, you'd have to restore the 4 month ago backup to another server and then extract the table out of it.Thanks