Dear experts,
Am experiencing below issue in one of our environment.
One of extract(regstered with below command) is STARTING status forever and nothing moving.
>> ADD EXTRACT <PROC_NAME>, SOURCEISTABLE
Source GG version: 12.2 (Database: 12.1 non-containarized)
Target GG version: 12.3(Database: 12.2 containerized)
The same environment was working fine earlier without any issues.
Observations:
-------------
- No errors in ggserr.log, mgr.rpt, extract process report.
- Able to telnet the goldengate vip along with target manager & collector port from source.
- Collector process at target is keep spanning from 50001 to 50004 ports(not sure if its expected behavior)
- Timeout error at target mgr report file, but no errors.
- Remote Trail file is getting created when extract started, but not updating(keep showing 0 bytes).
- There is another process(PM003AP) which is connecting to same target is in RUNNING status; But the problematic extract(PPM006AX-doing full load) is in STARTING state and not updating.
What we tried:
--------------
- Restarted XAG goldengate at target
- Restarted source single node goldengate server(restart manager, jagent)
- Re-registered process
- Append "TIMEOUT 600" with RMTHOST parameter in extract
Another important observation: Trails stored under dirdat is configured with DBFS. If I use non-DBFS directory to write the trails from extract(using rmthost) then atleast it turning into RUNNING state for moment and trail sizes increase, but fails with below error finally.
2020-01-21 17:02:48 ERROR OGG-01224 TCP/IP error 111 (Connection refused), endpoint: 100.78.249.108:7809.
Not much information in suppot or on web, any inputs from you will be helpful in this critical issue.
Thanks in advance.!
--
Regards,
KK.