Monday, Aug. 21, 2017

How to solve EIM errors

Written By:

|

October 15, 2012

|

Posted In:

This article contains solutions to all the errors and problems you can possible face during or after the EIM run.

1. EIM job in Queued state: If your EIM job is in queued state for a very long time, then the only possible reason could be your Server Request Broker component. Go to Server Administration -> Server -> Server Components and query for “Server Request Processor” OR “Server Request Broker” and check if any of them are in shutdown state or the tasks are going in error. If yes, then click shutdown button and then startup the component again. If this doesn’t help, bounce your Siebel gateway server and Siebel server where this component is running.

2. Invalid Configuration File: If your EIM job fails with error “Invalid Configuration File”, then open your IFB file and check for syntax errors. There must be a syntax error like wrong parameter name or invalid parameters which is causing EIM to throw this error.

3. EIM job in Active State: If the EIM job is in active state for a very long period of time or fails with IF_ROW_STAT value as IN_PROGRESS, then there is a lock on table which you are trying to access via your IFB file. For e.g. someone inserted or updated some records and forgot to COMMIT. In that case your IFB will get failed or will remain in “Active” status for a very long period of time. So you should ask your database admin to release the locks on the table and then you can run your IFB file again.

4. Insufficient Space: Sometimes you might an error like “Insufficient Space” which means that there’s no space to accommodate anymore data either on your server disk or on your database tablespace. Check if “Auto Extent” option was enabled during database creation. If not, then enable it.

5. IF_ROW_STAT errors: If any of the above reasons were not responsible for your EIM job fail, you’ll have to check IF_ROW_STAT value for your failed batch and lookup the reason here:

http://docs.oracle.com/cd/E14004_01/books/EIMAdm/EIMAdm_ImportData48.html

 To identify the table where the fail happened (in case your are populating or updating a lot of tables through a single IFB), you can check the IF_ROW_STAT_NUM column. Every base table related to your EIM interface table will have a temporary column with name like T_(table name without “S_” prefix)_STA.For e.g. in EIM_ACCOUNT, for S_ORG_EXT table there’ll be a column with name T_ORG_EXT_STA which will contain a number. If your IF_ROW_STAT_NUM value matches this number, you can conclude that the error happened with the table data of S_ORG_EXT. So in that way, you can find the table where the fail occurred and remove the problem.

6. Error LOGS: If you are still unable to find your problem, then run the EIM job again with these parameters set:

Trace Flags : 1

SQL Trace Flags : 1

Error Flags : 1

After your EIM fails, it will generate a detailed error information in form of log files in your LOGS folder. You can use that information to do detailed diagnosis on every single step of your EIM process execution.



Share This Article

About Author

Rohit

Siebel Technical Consultant

Comments are closed.

Leave A Reply