What Information Should You Gather if Transaction Merger Fails with the Error Message: SBL-MRG-00151?
(Doc ID 475507.1)
Last updated on SEPTEMBER 19, 2024
Applies to:
Siebel Remote Server - Version 7.5.3.11 [16199] to 16.0 [IP2016] [Release V7 to V16]Information in this document applies to any platform.
Area(s):Remote/Replication/Anywhere
Release(s):V5 (Siebel 99-Enterprise), V6 (Siebel 2000-Enterprise), V7 (Enterprise), V8 (Enterprise)
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V7 (Enterprise)
Keywords:Merger, case 1.2, row_id, unable to insert, txnmerge, .dx, SBL-MRG-00151, MRG-00151, duplicate
This document was previously published as Siebel FAQ 1157.
Goal
FAQ 1157: What Information Should You Gather if Transaction Merger Fails with the Error Message: SBL-MRG-00151?
Solution
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
| Goal |
| Solution |
| Case 1: Record Already Exists on Server Database |
| Case 2: Record Appears Twice in .dx File |
| Case 3: Additional Investigation Required |
| References |