Siebel Remote and Replication Manager Administration Guide > Troubleshooting Siebel Remote > Troubleshooting a Merge Problem >

Troubleshooting a Transaction Merger Problem

This topic describes how to use a temporary solution to restart Transaction Merger until you can determine the root cause for the problem.

CAUTION:  For important caution information about renaming or deleting a DX file, see Requirements for Extracting the Server Database.

To troubleshoot a Transaction Merger problem

1. To identify the remote client and the DX file that is involved with this problem, examine the log file of the Transaction Merger.

   For more information, see Example Log File for Transaction Merger and Naming Conventions for Log Files.

2. If the error is specific to one remote client, then you can rename the INBOX folder for this remote client.

   For example, rename the C:\siebel\ses\siebsrvr\docking\sadmin\inbox folder to C:\siebel\ses\siebsrvr\docking\sadmin\inbox_old.

   This is a temporary solution because the remote client cannot synchronize.

3. Restart the Transaction Merger server component.

   If Transaction Merger runs, then this problem only affects one remote client. If Transaction Merger fails again, then the failure applies to multiple remote clients.

4. Get help.

   For help with a Transaction Merger problem, see Getting Help from Oracle. Be prepared to send the related DX file and the trace file.

Example Log File for Transaction Merger

For the example in this topic, the remote client is SADMIN and the DX file is 00000009.dx. The VALUES line contains a series of question marks and each question mark is bound to a parameter value. The line that displays immediately below the line that contains the question marks includes the value for each question mark. For example:

INSERT INTO dbo.S_EMPLOYEE(NAME, AGE, SEX)
VALUES(?,?,?)
NAME:    Bill
AGE:     40
SEX:      M

Example Log File

The following text is an example of a log file for Transaction Merger:

[TRC35] >>> Processing Client: SADMIN

[TRC35] File: C:\siebel\ses\siebsrvr\docking\SADMIN\inbox\00000009.dx

[TRC33] 2017-03-04 12:09:51 Client: SADMIN, File: C:\siebel\ses\siebsrvr\docking\SADMIN\inbox\00000009.dx.

[DBG33] 2017-03-04 12:09:51 Message: Generated SQL statement:,

Additional Message: SQLExecute: INSERT INTO dbo.S_OPTY_PROD_X (ATTRIB_01, ATTRIB_02, ATTRIB_03, ATTRIB_04, ATTRIB_05, ATTRIB_06, ATTRIB_07, ATTRIB_08, ATTRIB_09, ATTRIB_10, ATTRIB_11, ATTRIB_12, CONFLICT_ID, CREATED, CREATED_BY, LAST_UPD, LAST_UPD_BY, MODIFICATION_NUM, PAR_ROW_ID, ROW_ID)

VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)

[DBG33] 2017-03-04 12:09:51 Message: Error: An ODBC error occurred,

Additional Message: Function: DICInsRowExecStmt; ODBC operation: SQLExecute

For more information, see Naming Conventions for Log Files.