See ->

https://gerardnico.com/dat/obiee/jobid_inconsistent

it looks like there is an inconsistency between the agents and the metadata in the DB RCU tables. Quickest way to resolve this would be to delete the jobs and recreate them. Alternatively, you could look at job ids and ensure via the job manager and update the RCU tables but this isn't a straightforward task as there are several tables that would need to be aligned.

The article that Robert refers to mentions that you should check the job id via the catalog manager (look at the XML) and compare it with the job id in the RCU tables - S_NQ_JOB & S_NQ_JOB_PARAM

I have faced this issue before. In my case there were two jobs with same id. If you check in your S_NQ_JOB you should be able to figure out something wrong there.

If you go through all the above you find how to get rid of message.

The question is: is that message really related to your issue?

Farrukh Nasir wrote:

 

Yesterday what happens that some of the users didnt get the email.

Does this mean that for one given agent only some of the recipients got the email? Because that would be totally unrelated to the error message you posted. If it's the case you maybe want to either use the Job Manager tool to check the logs of the agent or look into the table S_NQ_ERR_MSG directly (that's where the Job Manager is going).

And there you will find the real reason of why some users got their email and others not.

For your inconsistent ID message you maybe want to find out the root cause of it: OBIEE generally manage to keep the ID in sync in a weak but working way. Even with a duplicate ID into the XML of the agent etc. when you save it, it will replace the ID and update the scheduler tables as required. So you maybe want to make sure you don't have a cowboy-style process moving agents around environments or things like that.