Today, the customer said there are several data tables misuse import a new batch of data, these data now need to find out.
If there is no obvious fields can be identified, then ora_rowscn can be used as a reference, the following query can identify data by SCN and will later increase the record to find out:
The latter SCN clock, and happens to be misuse of time:
The former comes from SCN historical time, you can rely on:
If there is no obvious fields can be identified, then ora_rowscn can be used as a reference, the following query can identify data by SCN and will later increase the record to find out:
SQL> select gro_id,ora_rowscn from bms_group;
GRO_ID ORA_ROWSCN
---------- ----------
284 584845289
322 584845289
302 584845289
1 584845289
3 584845289
8 584845289
5 584845289
6 584845289
7 584845289
282 584845289
362 584845289
GRO_ID ORA_ROWSCN
---------- ----------
262 584845289
342 584845289
284 612073346
322 612073346
302 612073346
1 612073346
3 612073346
8 612073346
5 612073346
6 612073346
7 612073346
GRO_ID ORA_ROWSCN
---------- ----------
282 612073346
362 612073346
262 612073346
342 612073346
The latter SCN clock, and happens to be misuse of time:
SQL> select scn_to_timestamp(612073346) from dual;
SCN_TO_TIMESTAMP(612073346)
---------------------------------------------------------------------------
07-SEP-09 05.11.11.000000000 PM
The former comes from SCN historical time, you can rely on:
SQL> select scn_to_timestamp(584845289) from dual;
SCN_TO_TIMESTAMP(584845289)
---------------------------------------------------------------------------
03-SEP-09 04.45.13.000000000 PM
-The End-
转自:http://www.eygle.com/archives/2009/09/ora_rowscn.html