J
James Palmer
Guest
Looking for what you're asking for and found the following which I didn't find earlier: [2016/10/31@16:26:54.816+0000] P-14908 T-15416 I RPLS 18: (-----) Connection timeout for host cmlsql03 port 38140 transport TCP. [2016/10/31@16:27:44.818+0000] P-14908 T-15416 I RPLS 18: (-----) Connection timeout for host cmlsql03 port 38140 transport TCP. [2016/10/31@16:27:52.819+0000] P-14908 T-15416 I RPLS 18: (10396) The Fathom Replication Server cannot connect to the database broker on cmlsql03 at the port -27396. [2016/10/31@16:27:52.819+0000] P-14908 T-15416 I RPLS 18: (10397) The connection attempt to the Fathom Replication Agent l_idx41_pctrl failed. [2016/10/31@16:27:52.819+0000] P-14908 T-15416 I RPLS 18: (11241) The Replication Server will continue to attempt Agent connections until Mon Nov 07 16:21:12 2016. [2016/10/31@16:28:14.838+0000] P-6496 T-7964 I SRV 10: (742) Login usernum 90, userid PSLAdmin4 client type ABL , on CMLSQL01 using TCP/IP IPV4 address 127.0.0.1. We have 9 databases in the application and 10.2B suffers from that horrible 'feature' where database connect/disconnect messages are written for all databases in the session to each db log file, so there's a lot of noise. Easy to miss stuff! 
Continue reading...
Continue reading...