How to start the Oracle GoldenGate Collector Process Manually?

Oracle GoldenGate Server Collector process plays a vital role in the Oracle GoldenGate Replication. But we could not see this process in the INFO ALL command output. Because this process is started internally by the manager process automatically. But we all know that, we can also start the Collector process manually. But How to start it? Searched in google for the document but couldn’t find one. So thought of creating this article.

SERVER COLLECTOR PROCESS

There are two Extract Processes. Primary Extract and Secondary Extract (called DataPump / Extract Pump).The Extract Pump is the process at the Source side which communicates with the Target Manager process and requests manager to open the port for the Server Collector process at the Target Side.
So the Server Collector process will be invoked by the Target Manager process. The Collector process in turn receives the changes from the Extract Pump process and writes the changes to the Remote Trail files.

There are two types of Collector Process,

1. Dynamic Collector Process
2. Static Collector Process

 

Dynamic Collector Process – The collector process is started automatically by the Target Manager process on the request of the Extract Process from the Source. Check the below parameter file,

 

EXTRACT DMP1
PASSTHRU
RMTHOST OGG2, MGRPORT 7979
RMTTRAIL /vol3/ogg/dirdat/et
TABLE scott.emp;

In the above Extract Pump (Datapump) parameter file the below parameter tells the Target Manager process to start the Collector process.

 

RMTHOST OGG2, MGRPORT 7979

 

Static Collector Process In the above Extract Pump (Datapump) parameter file the below parameter tells the Target Manager process to start the Collector process.

 

RMTHOST OGG2, PORT 8080

This tells the Extract Pump (DataPump) process that, the collector process has been started in the Host “OGG2” with the PORT 8080. So the Pump process will not request
manager to open this port and invoke the collector process.

 

Dynamic Collector Parameter RMTHOST OGG2, MGRPORT 7979

Static Collector Parameter RMTHOST OGG2, PORT 8080

 

Example, Modify the Pump Parameter as below,

GGSCI (OGG1.localdomain) 61> VIEW PARAMS DMP1

EXTRACT DMP1
PASSTHRU
–RMTHOST OGG2, MGRPORT 7979
RMTHOST OGG2, PORT 8080
RMTTRAIL /vol3/ogg/dirdat/et
TABLE scott.emp;

I just commented out the RMTHOST parameter with MGRPORT and you can see the new parameter

RMTHOST OGG2, PORT 8080

Save the Parameter file and start the Collector Process with the below command. To start the Collector process execute the below command at the Command Prompt,

./server -p 8080

 

[oracle@OGG2 ogg]$ ./server -p 8080

2015-12-07 18:43:27 INFO OGG-01678 Listening for requests.
2015-12-07 18:44:04 INFO OGG-01229 Connected to OGG1.localdomain:18550.
2015-12-07 18:44:04 INFO OGG-01669 Opening /vol3/ogg/dirdat/et000000 (byte -1, current EOF 1616).
2015-12-07 18:44:04 INFO OGG-01670 Closing /vol3/ogg/dirdat/et000000.
2015-12-07 18:44:04 INFO OGG-01669 Opening /vol3/ogg/dirdat/et000000 (byte 1616, current EOF 1616).
2015-12-07 18:44:04 INFO OGG-01735 Synchronizing /vol3/ogg/dirdat/et000000 to disk.
2015-12-07 18:44:04 INFO OGG-01971 The previous message, ‘INFO OGG-01735’, repeated 1 times.
2015-12-07 18:44:04 INFO OGG-01670 Closing /vol3/ogg/dirdat/et000000.
2015-12-07 18:44:04 INFO OGG-01669 Opening /vol3/ogg/dirdat/et000001 (byte -1, current EOF 0).

 

You can see the collector process has been started and the Extract Pump (DataPump) process from the Source has established a connection with this Collector process at the Target.

Currently the Collector process is running the server.

 

[oracle@OGG2 ~]$ ps -ef |grep server
root 1327 1 0 18:04 ? 00:00:00 /sbin/pppoe-server
root 2368 1 0 18:05 ? 00:00:00 /usr/sbin/cimserver
gdm 2487 1 0 18:05 ? 00:00:00 /usr/libexec/bonobo-activation-server –ac-activate –ior-output-fd=12
oracle 3652 2823 0 18:54 pts/2 00:00:00 ./server -p 8080
oracle 3693 3666 0 18:54 pts/0 00:00:00 grep server

Now I am going to Kill the Server Collector process as below.,

[oracle@OGG2 ~]$ kill -9 3652
[oracle@OGG2 ~]$ ps -ef |grep server
root 1327 1 0 18:04 ? 00:00:00 /sbin/pppoe-server
root 2368 1 0 18:05 ? 00:00:00 /usr/sbin/cimserver
gdm 2487 1 0 18:05 ? 00:00:00 /usr/libexec/bonobo-activation-server –ac-activate –ior-output-fd=12
oracle 3700 3666 0 18:54 pts/0 00:00:00 grep server

 

When this Collector is stopped in the Target server, then you could see the following WARNING messages at the Pump Process,

2015-12-07 18:54:47 WARNING OGG-01223 Oracle GoldenGate Capture for Oracle, dmp1.prm: TCP/IP error 32 (Broken pipe), endpoint: OGG2:8080.
2015-12-07 18:54:52 INFO OGG-01226 Oracle GoldenGate Capture for Oracle, dmp1.prm: Socket buffer size set to 27985 (flush size 27985).
2015-12-07 18:54:52 WARNING OGG-01221 Oracle GoldenGate Capture for Oracle, dmp1.prm: Connect failed to 192.168.0.8:8080, error 111:Connection refused.
2015-12-07 18:54:56 INFO OGG-00987 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (oracle): info all.
2015-12-07 18:55:02 WARNING OGG-01221 Oracle GoldenGate Capture for Oracle, dmp1.prm: Connect failed to 192.168.0.8:8080, error 111:Connection refused.
2015-12-07 18:55:12 WARNING OGG-01221 Oracle GoldenGate Capture for Oracle, dmp1.prm: Connect failed to 192.168.0.8:8080, error 111:Connection refused.
2015-12-07 18:55:22 INFO OGG-01971 Oracle GoldenGate Capture for Oracle, dmp1.prm: The previous message, ‘INFO OGG-01226’, repeated 2 times.
2015-12-07 18:55:22 WARNING OGG-01221 Oracle GoldenGate Capture for Oracle, dmp1.prm: Connect failed to 192.168.0.8:8080, error 111:Connection refused.
2015-12-07 18:55:32 WARNING OGG-01221 Oracle GoldenGate Capture for Oracle, dmp1.prm: Connect failed to 192.168.0.8:8080, error 111:Connection refused.
2015-12-07 18:55:42 WARNING OGG-01221 Oracle GoldenGate Capture for Oracle, dmp1.prm: Connect failed to 192.168.0.8:8080, error 111:Connection refused.
2015-12-07 18:55:52 WARNING OGG-01221 Oracle GoldenGate Capture for Oracle, dmp1.prm: Connect failed to 192.168.0.8:8080, error 111:Connection refused.
2015-12-07 18:56:02 WARNING OGG-01221 Oracle GoldenGate Capture for Oracle, dmp1.prm: Connect failed to 192.168.0.8:8080, error 111:Connection refused.
2015-12-07 18:56:12 WARNING OGG-01221 Oracle GoldenGate Capture for Oracle, dmp1.prm: Connect failed to 192.168.0.8:8080, error 111:Connection refused.
2015-12-07 18:56:22 WARNING OGG-01221 Oracle GoldenGate Capture for Oracle, dmp1.prm: Connect failed to 192.168.0.8:8080, error 111:Connection refused.
2015-12-07 18:56:32 WARNING OGG-01221 Oracle GoldenGate Capture for Oracle, dmp1.prm: Connect failed to 192.168.0.8:8080, error 111:Connection refused.
2015-12-07 18:56:42 INFO OGG-01971 Oracle GoldenGate Capture for Oracle, dmp1.prm: The previous message, ‘INFO OGG-01226’, repeated 9 times.

At last, the DataPump process will get Abended with the below error.,

2015-12-07 18:56:42 ERROR OGG-01224 Oracle GoldenGate Capture for Oracle, dmp1.prm: .
2015-12-07 18:56:42 ERROR OGG-01668 Oracle GoldenGate Capture for Oracle, dmp1.prm: PROCESS ABENDING.

Hope you are very clear about the Server Collector Process after reading this article.

You may also like...

3 Responses

  1. Jamsher says:

    Very nice Article.

    Thanks for sharing

  2. raj says:

    Hi,

    I have one doubt,please clear it,

    RMTHOST OGG2, MGRPORT 7979.

    7979 is manager port in Target? or collector port or both ( manager port and collector port are same ).

    In our environment, target manger port is 9608 ( status mgr ).the same port is mentioned in source pump file in rmthost. It runs fine.

    Is it right configuration?

    • admin says:

      Hi Raj,

      7979 is the Manager Port of the Target server. In the Source, Pump process should know to which Target server it should push the data and the Manager process running over in the Target server.

Leave a Reply

Your email address will not be published. Required fields are marked *