There are many ways to find the source of the replicat process by looking at the trail files, the easiest way would be to read the details from the trail file directly.
For example, lets find the source for the Replicat Process REPLICAT1
GGSCI (sev1) 4> info REPLICAT1
REPLICAT REPLICAT1 Last Started 2018-11-10 23:36 Status RUNNING
Checkpoint Lag 00:00:00 (updated 00:00:00 ago)
Log Read Checkpoint File /usr/app/db2/ggs/trails/a1036633
2018-12-06 09:42:42.013255 RBA 136840037
Use the trail file given above, and open it using strings
GGSCI (sev1) 5> sh strings /usr/app/db2/ggs/trails/a1036633 | head -20
!uri:sev2::opt:app:db1:ggs5 <<----- Source Server Name (sev2) and DB name (DB1)
!uri:sev2::opt:app:db1:ggs6
%/usr/app/db2/ggs/trails/a10366337
15610950306357
Linux1
sev22 <<-------- Source Server Name
2.6.32-696.10.3.el6.x86_643
##1 SMP Thu Sep 21 12:12:50 EDT 20174
x86_642
db12
db13
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
PL/SQL Release 11.2.0.4.0 - Production
CORE 11.2.0.4.0 Production
TNS for Linux: Version 11.2.0.4.0 - Production
NLSRTL Version 11.2.0.4.0 - Production
11.2.0.4.09
EXTRACT11 <------- Source Extract Name
HVersion 11.2.1.0.3 14400833 OGGCORE_11.2.1.0.3_PLATFORMS_120823.1258_FBO4
15610950306357
Hope this helps you finding the source of Replicat process and troubleshoot the issues easily.
thanks for this post, quite helpful for my case in finding the source of the replicat process.
ReplyDeleteBuddy! This article saved my life. Awsome! hats off!
ReplyDelete