TxnMerge error SBL-MRG-00151 when processing 00000001.DX file for a user
(Doc ID 881114.1)
Last updated on MAY 05, 2021
Applies to:Siebel Remote - Version 18.104.22.168 SIA  and later
Information in this document applies to any platform.
Transaction Merger (TxnMerge) component fails when processing a Mobile Client user's 00000001.Dx file!
This is the very 1st file that this user is sending to server, considering sequence is used for file names - so this indicates the Remote user was extracted (DbXtract) and its local database was initialized recently (initial deployment of Remote users or newly added Mobile client).
Errors in TxnMerge_*.log file:
GenericLog GenericError 1 0 2009-08-01 08:23:47 (mrgmain.cpp (625) err=2500151 sys=0) SBL-MRG-00151: Unable to insert a row because a row with the same ROW_ID already exists in the database (case 1.2).
GenericLog GenericError 1 0 2009-08-01 08:23:47 Error with operation: Error with Txn:
Trans RowId: ...
GenericLog GenericError 1 0 2009-08-01 08:23:47 Message: Rollback to the database.,
Additional Message: File: D:\sea77\siebsrvr\docking\NEWUSER\inbox\00000001.dx. Number of txns successfully read and committed: 0.
Getting the result of SQL query suggested in related note: "What Information Should You Gather if Transaction Merger Fails with the Error Message: SBL-MRG-00151?" (<Note 475507.1>) proved that indeed record with same ROW_ID existed in that table.
Temporary workaround exists (as documented in: "What should be done when Transaction Merger fails?" (<Note 475974.1>): to rename only affected user's INBOX folder on server - that allows Merger to process other users' folders and DX files.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document