Siebel Business Process & Functionality (MOSC)

MOSC Banner

Different behavior of EIM process in our environments

edited Mar 18, 2014 10:38AM in Siebel Business Process & Functionality (MOSC) 4 commentsAnswered ✓

Hello everyone,

We faced a strange issue that one EIM process doesn't work in one our environment. We tested it in 2 other environments and there is no issue with process. But for some reason it doesn't work in our third environment. I checked repositories, tables, IFB files, everything is the same. I rebuilded diccache.dat file. Nothing helps. There is one difference that we try to update a few millions records testing performance. Previously in another environments we did it for a few thousands records only testing the solution.

The process updates many records in S_MDF table and single record in S_SRC. We use only vanilla columns in EIM_MDF and EIM_SRC interface tables. Comparing detailed logs, for some reason Siebel doesn't generate one important UPDATE query that updating Organization ID columns in EIM_MDF table. The query provided below. At the end we've got SBL-EIM-00425 and all records are in state "NOT_ALLOWED".

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center