Siebel Remote: Synch Failing when Applying Database Changes with errors SBL-MRG-00158 and ORA-30036
(Doc ID 2328027.1)
Last updated on JANUARY 21, 2019
Applies to:Siebel Remote - Version 16.0 [IP2016] and later
Information in this document applies to any platform.
Siebel Remote / Replication / Anywhere - on version: 16.13 [IP2016]
On a SIT Environment, Remote Synchronization session fails at the time of Applying database changes.
DBCLog DBCLogError 1 0000000459e72ea4:0 2017-10-18 10:30:28 [tp][ODBC Oracle driver][Oracle]ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS2'
GenericLog GenericError 1 0000000459e72ea4:0 2017-10-18 10:30:28 Message: Error: An ODBC error occurred,
Additional Message: pfNativeError: 30036; szSQLState: S1000; szErrorMsg: [tp][ODBC Oracle driver][Oracle]ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS2'
GenericLog GenericError 1 0000000459e72ea4:0 2017-10-18 10:30:28 Pessimistic Insert: unable to insert a row. Table S_EVT_ACT, RowId 1-STATSJ.
The row had the following <attribute, value> pairs:
GenericLog GenericError 1 0000000459e72ea4:0 2017-10-18 10:30:28 (mrgsins.cpp (660) err=1638558 sys=2) SBL-MRG-00158: Pessimistic Insert: unable to insert a row.
GenericLog GenericError 1 0000000459e72ea4:0 2017-10-18 10:30:28 Message: GEN-03,
Additional Message: File: C:\sba81\Client\LOCAL_XE\inbox\00007521.dx. Number of txns successfully read and committed: 0.
GenericLog GenericError 1 0000000459e72ea4:0 2017-10-18 10:35:15 (da_txnmerge.cpp (745) err=1114280 sys=0) SBL-DCK-00168: Unable to apply database transactions. Please refer to the detailed log messages elsewhere in this file.
GenericLog GenericDebug 5 0000000459e72ea4:0 2017-10-18 10:37:37 Process Name: Client Docking Session Manager, Status: Completed with Errors, Message Unable to Apply database changes
The issue can be reproduced in customer's environment with the following steps:
1. Setup Siebel Remote user and extract/initialize the LOCAL_XE database;
2. Make some further changes on the data on Server database as well as on the Local Client;
3. Start a Synchronization session;
4. See that ending with error in above mentioned step
The issue has the following business impact:
Due to this issue, Remote users cannot have their LOCAL_XE database synchronized with server changes.
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