Using PowerExchange DBMOVER Statements to Tune Bulk Data Movement Sessions
Using PowerExchange DBMOVER Statements to Tune Bulk Data Movement Sessions
To tune PowerExchange bulk data movement sessions, you can include the following statements in the DBMOVER configuration file:
APPBUFSIZE=
bytes
Defines the maximum size, in bytes, of the buffer that PowerExchange uses to read or write data. This data buffer can exist on a source or target system.
PowerExchange writes bulk data to its application data buffer on the source system until the buffer is full. PowerExchange then sends the data to a sending TCP/IP buffer on the source system. TCP/IP transports the bulk data to a receiving TCP/IP buffer on the target system. PowerExchange on the target system reads the bulk data from the TCP/IP buffer into its application data buffer. PWXPC then reads the bulk data and passes it to PowerCenter. PowerCenter processes the data and applies it to the targets.
Enter an APPBUFSIZE value that is greater than the maximum size of any single data row to be sent.
Valid values are from 34816 through 8388608. Default is 256000.
If the target system is remote, enter the same APPBUFSIZE value in the DBMOVER configuration files on the source and target systems.
If the APPBUFSIZE value is not optimal, PowerExchange writes the PWX-01295 message in the PowerExchange log file on the source system. This message includes a recommended value.
If dynamic application buffer sizing is enabled, the APPBUFSIZE statement defines the initial size of the application data buffer for all connections made during a PowerExchange Listener run. PowerExchange resizes the application data buffer dynamically for individual connections as needed. Dynamic application buffer sizing is enabled by default. You can explicitly enable it by specifying Y for the APPBUFSIZEDYN statement in the DBMOVER configuration file.
APPBUFSIZEDYN={N|
Y
}
Specifies whether to enable dynamic application buffer sizing.
The DBMOVER APPBUFSIZE statement defines the initial size of the application buffer for all connections made during a PowerExchange Listener run. If APPBUFSIZEDYN=Y, PowerExchange resizes the application buffers for individual connection as needed.
The APPBUFSIZEDYN statement applies to PowerExchange connections to data sources with either fixed-length or variable-length records. A variable-length record is a record with at least one variable-length field. A variable-length field has a datatype of VARCHAR or VARBIN.
For each connection to a data source with variable-length records, PowerExchange resizes the application buffer when it encounters a record that is too large to fit into the buffer. PowerExchange increases the size of the application buffer to a value of ten times the size of the record that has overflowed, up to the maximum application buffer size of 8 MB. The new size remains in effect for the duration of the Listener run or until the application buffer is resized again. PowerExchange never decreases the application buffer size for a connection after the Listener run has started.
For each connection to a data source with fixed-length records, PowerExchange determines the record length when the connection is opened and resizes the application buffer once, up to the maximum application buffer size of 8 MB, as needed.
COMPRESS={
Y
|N}
Defines whether PowerExchange uses its proprietary compression algorithm to compress data before PowerExchange sends data to TCP/IP for transmission to the remote system.
Default is Y.
PowerExchange uses the COMPRESS setting in the DBMOVER configuration file on the remote system that contacts the PowerExchange Listener. On PWX NRDB Batch application connections and PWX relational connections, you can override the compression setting in the DBMOVER configuration file. If you enable compression, the CPU consumption of the PowerExchange Listener on the source system might increase.
To avoid unnecessary CPU consumption, set COMPRESS to N in the PowerExchange DBMOVER configuration file on the PowerCenter Integration Service machine.
LISTENER=(
node_name
,TCPIP,
port
,
send_bufsize
,
receive_bufsize
,
send_size
,
receive_size
, ...)
A TCP/IP port on which a named PowerExchange Listener process listens for work requests.
The
send_bufsize
and
receive_bufsize
positional parameters define the data portion of the TCP/IP send and receive buffer sizes that PowerExchange uses. If you do not specify these values, PowerExchange uses the operating system defaults.
To increase throughput, try increasing the
send_bufsize
and
receive_bufsize
values in the LISTENER statement in the DBMOVER configuration file on the source system. For help in determining the best values to use, contact your network administrator.
NODE=(
node_name
,TCPIP,
host_name
,
port
,
send_bufsize
,
receive_bufsize
,
send_size
,
receive_size
, ...)
A TCPIP host name and port that PowerExchange uses to contact a PowerExchange Listener process.
The
send_bufsize
and
receive_bufsize
positional parameters define the data portion of the send and receive buffer sizes that PowerExchange uses. If you do not specify these values, PowerExchange uses the operating system defaults.
To increase throughput, try increasing the
send_bufsize
and
receive_bufsize
values in the NODE statement in the DBMOVER configuration file on the target system. For help in determining the best values to use, contact your network administrator.
TRACE=(
trace_id
,
trace_level
,99)
Activates PowerExchange diagnostic traces that Informatica Global Customer Support uses to solve problems with PowerExchange code.
TRACE statements can severely impact PowerExchange performance. Use these statements only at the direction of Informatica Global Customer Support.
After Informatica Global Customer Support diagnoses the problem, remove or comment out all TRACE statements in the DBMOVER configuration files on all systems.