Hi Blackswan/michel,

Is it not possible to remove one day post data that was wrongly loaded into table without backup ?

Regards,
Srini

Have you looked at Flashback Query?

You first post used the word "updated"; which means to me changed data.
If existing data was changed, it is not possible to know the previous old values.

This post uses the word "loaded", which can mean new rows were added.
Can you post SQL SELECT that returns only these "loaded" rows? If so, then you can DELETE these rows.

I am thing perhaps they truly do mean 13th of July instead of 13th of June.

The database itself is not being backed up then why worry about the data in the table at all. If you are not backing up your database then the data is not valuable to begin with.

Scenario: Using Flashback Data Archive to Recover Data
An end user recovers from erroneous transactions that were previously committed in the database. The undo data for the erroneous transactions is no longer available, but because the required historical information is available in the Flashback Data Archive, Flashback Query works seamlessly.

Lisa manages a software development group whose product sales are doing well. On November 3, 2007, she decides to give all her level-three employees who have more than two years of experience a salary increase of 10% and a promotion to level four. Lisa asks her HR representative, Bob, to make the changes.

Using the HR web application, Bob updates the employee table to give Lisa's level-three employees a 10% raise and a promotion to level four. Then Bob finishes his work for the day and leaves for home, unaware that he omitted the requirement of two years of experience in his transaction. A few days later, Lisa checks to see if Bob has done the updates and finds that everyone in the group was given a raise! She calls Bob immediately and asks him to correct the error.

At first, Bob thinks he cannot return the employee table to its prior state without going to the backups. Then he remembers that the employee table has Flashback Data Archive enabled.

First, he verifies that no other transaction modified the employee table after his: The commit time stamp from the transaction query corresponds to Bob's transaction, two days ago.

Next, Bob uses these statements to return the employee table to the way it was before his erroneous change:

DELETE EMPLOYEE WHERE MANAGER = 'LISA JOHNSON';
INSERT INTO EMPLOYEE
SELECT * FROM EMPLOYEE
AS OF TIMESTAMP (SYSTIMESTAMP - INTERVAL '2' DAY)
WHERE MANAGER = 'LISA JOHNSON';
Bob then reexecutes the update that Lisa had requested.

Actualy this issue happend during peak hours in the morning and backup is taken everyday in the night.
So could not use backup to restore the data.

How to ensure Flashback Data Archive is enable in database

the former relies on the DB_FLASHBACK_RETENTION_TARGET parameter

Actualy this issue happend during peak hours in the morning and backup is taken everyday in the night.
So could not use backup to restore the data.

Sorry to say by mistake i used the word 'updated'.Actually its 'data added into table'.

can you post any actual logfile showing what was really done & when it was done and not just your uncertain recount of what you think you saw?

post CREATE TABLE statement(s) for any/every table that was adversely affected by the incorrect data load