Skip to Content

SAP IdM 8.0 Provisioning queue build up

Hi All

Customer I'm working on is running IdM 8.0 SP3 on an oracle db (Linux OS).

Issue I have is that the provisioning queue (table mxp_provision) is building up and I'm not able to clear it. I have tried restarting the dispatcher and have also gone through the checklist in one of the blogs.

Checking the mxp_provision table there are a number os "Wait for event audit ..." messages as shown below. I have checked most of the audit ids and the provstatus on them is 1000 (Task ok).

Most of the entries in the mxp_provision table have state 33 which I believe is the correct state as per this blog (https://blogs.sap.com/2016/03/25/sap-identity-management-provisioning-monitor-tool/)

But I don't understand why these entries are not clearing from the mxp_provision table.

Please advise.

See below, provstatus is 1000.

Thanks

Ranjit

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Feb 25 at 07:54 PM

    Just wanted to update. Since the queue had millions of records and it was a non-prod system a decision was made to reset the identity store.

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 28, 2017 at 08:50 AM

    Hello Ranjit,

    I can't imagine that the status numbers changed so much from 7.2 to 8.0. In 7.2 "OK" would be "1100" and not "1000".

    In 7.2 "1000" means "Task OK", which is not the same for the provisioning.

    If you used my blog, because you were writing about a checklist, then it's in there, too. You need to set the status to "1100".

    Maybe you misread? :)

    .

    Regards,

    Steffi.

    Add comment
    10|10000 characters needed characters exceeded

    • Hello Ranjit,

      "provstatus" and "state" are different kind of states. They belong to different tables, too. You can check the available "states" in the table "mxp_state".

      "33" means "Ready to process Wait Before task" (in 7.2).

      .

      I would check the other waiting tasks, too, and work on those. Sometimes tasks also get stuck and there is no other way than to delete them from the queue. But this should be the last option and only if all other options are not working.

      Please have a look at the IDM blogs by Former Member. He created a series about the provisioning queue (I think there were 3 blogs), where he explained the tables, states and how it all works together. With SQL statements to check things etc. It's for 7.2, but most of that stuff should also work for 8.0.

      .

      Regards,

      Steffi.