Siebel Remote and Replication Manager Administration Guide > Troubleshooting Remote and Replication Manager >

What to Do When Transaction Merger Fails

This section describes a temporary workaround to restart Transaction Merger until the root cause has been found.

To work around a Transaction Merger's failure

  1. Check out the log file (TxnMerge*.log) to find the mobile Web client and the *.dx-file this is happening for. In the example following, the mobile Web client is SADMIN and the *.dx is 00000009.dx.

    2. CAUTION:  Renaming or deleting the DX files in siebsrvr\Docking\Client\Inbox directory is not allowed. If you rename or delete DX files you will lose the transactions and will have to reextract the mobile Web client.

    [TRC35] >>> Processing Client: SADMIN

    [TRC35] File: c:\Sea704\Siebsrvr\docking\SADMIN\inbox\00000009.dx

    [TRC33] 2000-10-06 12:09:51 Client: SADMIN, File: c:\Sea704\Siebsrvr\docking\SADMIN\inbox\00000009.dx.

    [DBG33] 2000-10-06 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 (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)

    NOTE:  In the log file, following the line with the series of question marks, you can find the actual values, which are bound to each by the question mark.

    For example:

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

    [DBG33] 2000-10-06 12:09:51 Message: Error: An ODBC error occurred,

    Additional Message: Function: DICInsRowExecStmt; ODBC operation: SQLExecute

  2. If the error is specific to one mobile Web client, rename the INBOX directory for this mobile Web client (that is, from C:\Sea704\SiebSrvr\Docking\Sadmin\Inbox to C:\Sea704\SiebSrvr\Docking\Sadmin\Inbox_Old) and restart Transaction Merger.
  3. If Transaction Merger runs after that, this is only affecting one mobile Web client. If Transaction Merger fails again, you can expect that the failure applies to the mobile Web clients.
  4. Open a Service Request on the SupportWeb and send the related *.dx-file and the trace file for further analysis.

    5. NOTE:  This is a temporary workaround because the specific mobile Web client will not be able to synchronize.


 Siebel Remote and Replication Manager Administration Guide, Version 7.5, Rev. A 
 Published: 18 April 2003