Attributes to Configure in the Comm-Port Point

Attribute Name Description
oracle login

The Oracle login string. This is the string that is passed for logging into the Oracle database. For example `judyck/judyck@db'; where the first value is the user login name (judyck), the second value (i.e. after the /) is the password for the given user (judyck), and the third value (i.e. after the @) is the machine the Oracle database resides (either an alias from /etc/sqlnet or full path; see Oracle SQL-NET User's Manual for further information). If the machine name is too long, create an alias in /etc/sqlnet (see Oracle SQL-NET User's Manual for further information). If a full path is given, the following format must be used:

judyck/judyck@T:esso4:ORACLE,1024:Z

where:

T        use TCP protocol
esso4    hostname as defined in /etc/hosts
ORACLE    database id
  1. buffer size
[note] For SQL*Net V2, use the following format: 
user/passwd@db

where:

user        user name
passwd    password

dbOracle database name from the TNSNAMES.ORA file (see "Understanding SQL-NET" for version two).
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 "/dev/ptyqf". In addition to a device file, the following key words are recognized: "stdout" and "stderr"; which send debug information to the specified file pointer.

[warning] If a pseudo-terminal device is to be used, specify the master device; otherwise the driver will be hung on the open waiting for the master side of the pseudo-terminal to be opened.

 

[caution] If a pseudo-terminal device is used, the scan task must be started before any process tries to open the slave device; otherwise no debug information will be printed.
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.

[warning] Depending on the network connection speed, some debug data may be lost. Tests here, show that for a full 10 Mbit/sec connection, no data is lost.