Most Collector parameters are entered in the Extract parameter file, using the PARAMS collector_params option of the RMTHOST parameter. The Manager automatically sends some of these parameters when it starts the Collector, such as -k and ENCRYPT key and KEYNAME options entered by the user.
The Collector parameters discussed here are for a Collector running on a remote NonStop system. For Collector parameters that run on other platforms, see Collector Parameters.
PROCESS process_nameThe name of the NonStop TCP/IP process.
-BULKIOResults in Collector writing data in 28K blocks, rather than 4K. Setting -BULKIO can increase total throughput of the Collector and reduce overhead significantly.
-BULKIOLENUse BULKIOLEN to customize the block size Collector should use when writing data. Increasing the block size used by Collector can contribute a net performance gain by increasing total throughput. Block sizes may be indicated in bytes or kilobytes, but the Collector only recognize sizes that are multiples of 2. If you choose a block size between 2 and the next multiple, BULKIOLEN automatically rounds your specification down.
b backup_cpuRuns the Collector backup process started in backup_cpu. This option is only for static servers. It is not valid for dynamic servers, which are persistent processes that will be restarted if the process has a failure.
-B-DEBUGStarts the Collector in DEBUG mode to allow the user to analyze the actions of the program code.
-EMSEMPHASIS typeControls whether or not emphasis will be turned on for certain types of messages coming from EMSCLNT on open systems.
type can be one of the following:
CRITICALTurns emphasis on for CRITICAL or WARNING messages as well as FATAL messages.
FATAL or ERRORTurns emphasis on only for FATAL messages.
The default is CRITICAL.
ENCRYPT encrypt_typeThe type of encryption being passed from the Extract process, as specified with the RMTHOST parameter in the Extract parameter file.
Valid values:
GGS
BLOWFISH
If using BLOWFISH, also specify the -KEYNAME option. For more information about Oracle GoldenGate security, see Using Encryption.
-fAlways forces file writes to be flushed to disk before returning a success status to the Extract process.
By default, the file system buffers the I/O because it is more efficient than flushing to disk with every operation. Generally, the performance benefits outweigh the small risk that data could be lost if the system fails after an I/O is confirmed successful, but before the buffer actually is flushed to disk. Use -f if this risk is unacceptable, with the understanding that it can compromise the performance of Oracle GoldenGate.
HOMETERM terminalIdentifies the home terminal for the Collector.
-kDirects Collector to terminate when the Extract process that it is serving disconnects. This option is used by the Manager process when starting the Collector process.
KEYNAME nameSpecifies a key name defined in the local ENCKEYS lookup file. name is the name of a key in a lookup file on the target system. For more information about Oracle GoldenGate security, see Using Encryption.
l file_nameDirects the Collector to log to file_name. The name should be fully qualified.
-m numberSpecifies the maximum number of files to allocate.
NOFLUSHCACHE | FLUSHCACHETurns on or off the flushing of the disk cache.
-p port_numberA TCP/IP port number on which the Collector listens for connections from the Extract process. The default is port 7819.
-tTurns on TCP tracing to write detail to EMS on socket operations. It is recommended that you use this parameter only when requested by Oracle GoldenGate Support.
-TCPSTATSSpecifies that TCP statistics should be printed at file rollover.
-vSpecifies that NonStop Collector processes use EMS logging.