Tuesday, June 8, 2010

SIEBEL IF_ROW_STAT IN_PROGRESS due to SBL-EIM-00107

Error: IF_ROW_STAT shows IN_PROGRESS after EIM process has completed.

Possible Cause: Unique constraint violated.  Check the EIM log file for the definite cause.  If you don't find anything in the EIM log file, try increasing the log level.  If trying to populate s_loy_txn for example, and we get IF_ROW_STAT IN_PROGRESS, then if the problem is truly because of the unique constraint being violated then we should expect to see the following in the EIM log file:

[DataDirect][ODBC Oracle driver][Oracle]ORA-00001: unique constraint (SIEBEL.S_LOY_TXN_U1) violated
Error SBL-EIM-00107: ODBC error 23000:
[DataDirect][ODBC Oracle driver][Oracle]ORA-00001: unique constraint
(SIEBEL.S_LOY_TXN_U1) violated
(native error 1)
Error SBL-EIM-00107: ODBC error 23000:
[DataDirect][ODBC Oracle driver][Oracle]ORA-00001: unique constraint
(SIEBEL.S_LOY_TXN_U1) violated
(native error 1)
Step 9: inserting new rows S_LOY_TXN 1s
Process [Import EIM_LOY_TXN] had all rows fail
on EIM_LOY_TXN for batch 6020000 in step 9, pass 528:
Import processing aborted due to SQL error. (severity 1, table aborted)
A low-level error occurred during import processing for this table. The error
could not be handled during the step in which it occurred and caused all import
processing for that table to stop.
ODBC error 23000: [DataDirect][ODBC Oracle driver][Oracle]ORA-00001: unique
onstraint (SIEBEL.S_LOY_TXN_U1) violated
This low-level failure caused all processing to halt for the specified
interface table. Check the error messages for more information.
 
Possible Solution: Ensure that you are populating the row_id of the corresponding EIM table with unique values for each rows.

No comments:

Post a Comment