Siebel Incremental Repository Merge – errors that we faced

Incremental Repository Merge is the new feature that has been introduced from Siebel 8.1.1.10 onward. It makes the Siebel repository upgradation process faster and easier without going through major upgrade project. Recently we have performed IRM for one of our clients. During the process, we have faced many errors/issues. Here we have discussed few major, frequently occurred errors during IRM.

Error Message:
Importing file “D:Siebel8.1Tools_1tempIRM_PRIOR_CUST.dat”.22001: [DataDirect][ODBC Oracle driver][Oracle]ORA-12899: value too large for column “SIEBEL”.”S_ACCELERATOR”.”INACTIVE_FLG”  (actual: 4, maximum: 1) 
Reason n Solutions:
This error comes up because of incorrect registry settings on ODBC data source. 
To fix this issue, follow below steps:
Step 1: Start the Microsoft ODBC Administrator 
Step 2: On the ODBC Data Source Administrator dialog box, select System DSN tab and copy the DSN name
Step 3: In Windows registry, locate following registry entry  [HKEY_LOCAL_MACHINESOFTWAREODBCODBC.INISiebel_DSN_Name]

Step 4: Verify following registry keys are set properly or not. These keys are required in order for the ODBC driver to behave correctly. If keys are not present, then add new key like below
                                      PacketSize = 0
                                      EnableScrollableCursors=0
                                      ColumnsAsChar=1
                                      ColumnSizeAsCharacter=1

Error Message:
ERROR::SBL-DEV-62155: CommitCopyInstance EXITING with error – The same values for ‘Column Name’ already exist
Reason n Solutions: 
This error comes up when the database is not running in binary sort order mode. During Incremental Repository Merge, it is mandatory to set the parameter NLS_SORT to BINARY which helps database to in Binary mode.

Error Message:
ERROR::c: MAP ENTRY with same id exists
ERROR::BUT strNamePath and ParentId are different
ERROR::SBL-DEV-62252: Could not create HASH entry
ERROR::Type – Workflow Process, strNamePath – eMail Response – Create Activity: 0
Reason n Solutions:
This behavior typically occurs when an object already exists in the New Customer Repository but the workflow process which is trying to insert, has a different set of attributes. This is due to one particular workflow, could be ignored.

Error Message:
ERROR::SBL-DEV-62111: NON-REQUIRED FKey not found in ‘New Standard Repository’
ERROR::Type – WF Branch Connector, strNamePath – ABO Bulk Request – ApplyProductPromotion
Reason n Solutions:
This is because of one/more non-required foreign keys from the ‘Prior Customer Repository’ are not present in the workflow definition and that’s why the particular workflow object was inserted into the ‘New Customer Repository’ with a NULL value during IRM process. This is also one of those generic errors which can be ignored.

Error Message:
ERROR::SBL-DEV-62155: CommitCopyInstance EXITING with error – 1-3ZGTMC.
ERROR::SBL-DEV-62194: INSERTION FAILED. Type View, NamePath – SWLS Technician Breaks View
ERROR::SBL-DEV-62194: INSERTION FAILED. Type Applet, NamePath – SWLS Technician Breaks Display Applet
Reason n Solutions:
This error occurs when a new Siebel object is added to the standard Siebel repository but it has the same key details as a custom object that already exists in the ‘Prior Customer Repository’. This error also can be ignored.

Error Message:
Failure: 161782 rows of EIM_EMPLOYEE had NULL in STATUS_CD 
Reason n Solutions:
This error comes up when IRM process tries to populate siebel base table using interface tables. So before staring IRM process, clear all interface tables from siebel database (part of siebel best practice during repository merge or upgrade) to avoid this error.

Error Message:
ERROR::SBL-DEV-62102:  -> aborted with error: The same values for ‘Sequence’ already exist.
Reason n Solutions:
When repository merge process starts to re-sequence objects automatically, this error may occur. It is an acceptable error message which doesn’t need any fix, can be ignored.

Error Message:
ORA-00942: table or view does not exist
Reason n Solutions:
This error occurs when table/view definition exists in logical schema but not in physical schema. So run DDL sync utility to create new tables/views in physical database. 

Error Message:
ORA-00904: “JOB_TYPE_CD”: invalid identifier  
Reason n Solutions:
This is also because of mismatch between Siebel physical database and logical database. Here also we just need to run DDL Sync utility to sync both databases.

These are few major issues/errors that we generally face during Siebel Incremental Repository Merge in Siebel. If you have faced any other issue, please let us know. We will try our best to help you.
To get more updates on recent activities, follow ‘TechOneStop‘ on Facebook/Twitter/LinkedIn or join our website as followers.

Check our Youtube videos on Siebel Open UI training, you will like it.