Siebel Remote and Replication Manager Administration Guide > Siebel Remote Concepts > Siebel Remote Server Components >

Transaction Processor

The Transaction Processor component scans the master transaction log on the Siebel database server and prepares transactions for visibility checking and routing by a transaction router. Transaction Processor leaves the last log entry on DB2 and leaves 1000 on MS SQL to avoid deadlock problems.

You can run only one transaction processor on each Siebel Remote server. Upon start-up, the transaction processor verifies that another transaction processor is not running on the same Siebel Remote server.

CAUTION:  VARCHAR data handled by Siebel Remote must not be larger than 16,350 bytes. VARCHAR data that exceeds this size will cause a Transaction Processor error and stop Siebel Remote operations. If this occurs, contact Siebel Technical Support for assistance in resolving the situation. To prevent this from occurring, configure your implementation to enforce the size restriction for LONG data at the business component layer or use file attachments to store the data.