Co-ordinated Replicat in 12c

Co-ordinated Replicat in 12c is compatible for all databases from all vendors
Co-ordinated replicat will help us to reduce the use of filter and @range parameters
when we configure co-ordinated replicat

Goldengate replicat file with filter @range parameters 
-- Handles all tables WITHOUT PK /UI
-- GGSCI> add replicat rtecve_1, exttrail /u01/app/goldengate/remotetrail/zz, checkpointtable ggsuser.ckpt
—- ALTER rtecve_1, extseqno 4 extrba 2292 
replicat rtecve_1
assumetargetdefs
sourcedefs ./dirdef/teacher.def
------structure of source table and target table is same 
userid ggsuser, password oracle
reportcount every 24 hours, rate
discardfile /u01/app/goldengate/discardtrail/rtecve_1.dsc, megabytes 10, append
discardrollover at 06:00
map nspdba.teacher, target nspdba.teacher, FILTER(@RANGE(1,4));

we can follow same strategy in 12c to split replicat but we can use Co-ordinated Replicat in 12c 
In order to create Co-ordinated Replicat the syntax is as follows, we are going to add replicat with co-ordinated and Maxthreads params 

Adding co-ordinated replicat as follows 
ggsci> add replicat rtecve, Coordinated, exttrail u01/app/goldengate/remotetrail/zz, MaxThreads 5

For this replicat "rtecve",  5 co-ordianted threads are create by default or Max threads is not specified by default max threads allocated in 25 

--Nikhil Tatineni--
--Oracle in memory--