How to identify deltas

Question

Hi,
create table t1(no number primary key, name varchar2(10), email varchar2(100));
I don't have who columns(last_udpate_date, last_updated_by, creation_date, created_by) in my table t1
I want to send records to my other team on a daily basis,
assume on day 1 I have 10 records in my table t1 and today am sending all 10 records as it is a day1
on day 2 I have 20 records in my table t1
meaning below are the scenarios for 20 records
a) 10 records newly added -> send only newly added 10
b) 10 records added + 5 records updated -> send only newly added 10 and 5 updated
c) 14 records added + 3 records updated + 4 records deleted -> send only 14 newly added + 3 updated + 4 records deleted

Answer 1

>
create table t1(no number primary key, name varchar2(10), email varchar2(100));
I don't have who columns(last_udpate_date, last_updated_by, creation_date, created_by) in my table t1
I want to send records to my other team on a daily basis,
>
Create a MATERIALIZED VIEW LOG on your table and let Oracle do all of the work of capturing which rows changed.
That way you don't have to modify your table at all and the MV log will also capture DELETEs (you didn't mention how to tell the other site about rows that have been deleted).
See CREATE MATERIALIZED VIEW LOG in the SQL Language doc
http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_6003.htm
>
When DML changes are made to master table data, Oracle Database stores rows describing those changes in the materialized view log
>
Try this example in the scott schema
drop materialized view log on emp_copy
create table emp_copy as select * from emp
alter table emp_copy add constraint pk_emp_copy primary key (empno)
create materialized view log on emp_copy
with sequence (ename, job, mgr, hiredate, sal, comm, deptno)
including new values
update emp_copy set job = 'TEST1' where empno = 7654Then take a look at the MV LOG (MLOG$_EMP_COPY) records and you will see all of the information you were wanting to capture.
For your use case you just need the distinct ROWID or PRIMARY KEY values from the log. Use those to grab the rows from your table and then delete the log rows.