Attribute Name | Description | |||||
---|---|---|---|---|---|---|
oracle login | The Oracle login string. This is the
string that is passed for logging into the Oracle database. For
example `
where:
|
|||||
trans before commit | This number specifies the number of transactions performed before committing the data. If this value is set to 0 (zero), the OracleScanner will process all transactions destined for an Oracle table before committing the data. | |||||
max recs per trans | This number specifies the maximum number of (scan input) records per transaction. If this value is set to 0 (zero), the whole scan input table will sent as a transaction (Note: that this may cause large amounts of memory to be allocated). This value is only valid for transactions performed to the Oracle database. | |||||
post message | This attribute indicates whether the check for and processing of transaction(s) in the SQL file (see transfer direction) is performed prior to (zero) or after (one) processing of a message to the scan task. | |||||
debug device | UNIX | The device file where debug information is
to be printed. The full path must be provided; for example "
|
||||
Windows | This specifies a "named pipe" that will be created on the server machine. Client applications can then make connections to this "named pipe" to receive debug information. A separate thread is created to handle each client. There is a maximum of six client connections allowed. Additional clients trying to connect will fail. Since this is a "named pipe", clients can connect from other machines on the network. See the tesserNet Scan Debug Utilities for freely distributable client applications.
|