13.2 Issue: Reports Are Missing Identity Vault Data

If you notice that some of your reports are missing Identity Vault data, you should look at the following list of possible causes:

  • Report definition is out of date.

  • The Data Collection Service driver or the Reporting Module is not started.

  • The Data Collection Service driver was not migrated. If the driver has not been migrated, the objects are not synchronized into the Identity Information Warehouse.

  • The timeout setting on the Data Collection Service driver is set too high and the events are not immediately propagated into the database. This could appear to be a problem if you don’t wait until the event is sent and processed.

  • The Data Collection Service driver is not configured correctly. Here are some things to look at:

    • Objects are missing from the Filter Policy.

    • Objects are not under the Data Collection Service scope.

Here are troubleshooting tips:

  • Verify that the data missing from the reports is present in the idm_rpt_data schema tables:

    • If the data is present in the database, verify that you have the latest report definitions installed. On the detail page of each report is a field showing the data it was built or customized. You need to compare the date on the detail for that report with the data on the download page http://cdn.novell.com’cached/designer/idmrpt/.

    • If the data is missing from the database, verify that the Data Collection Service driver is sending events to the REST services and that they are being processed correctly:

      1. Make sure there are no errors in event processing. View the JBoss console log (server.log) and look for errors (for example, grep -i "error" server.log)

      2. If there are no errors, make sure that the events are being received from the Data Collection Service driver.

        Add the following trace to the idmrptcore_logging.xml file and tail the console log (by using tail -f server.log). You should see trace messages with recognizable DNs, names, and so forth. 

        <logger name="com.novell.idm.rpt.core.server.events.rptdriver" level="TRACE" additivity="true"/>

  • Verify that the Data Collection Service driver is configured and running:

    • Check in iManager to see that the driver was deployed and the driver state is Running.

    • Check the following settings for the Data Collection Service driver in iManager:

      • Reporting connection information

      • Reporting access account

      • Data Collection Service driver filter policy

      • Data Collection Service driver scope

      • Data Collection Service driver event processing settings

        Look at the Time interval between submitting events and the Number of events to be sent in batch. Set these to lower values for more immediate results.

When you are confident that your configuration is correct, and you still don’t see the expected data populated, you need to check for Data Collection Service driver errors. Check the DS Trace from the driver to see if there are errors:

  • Check the DS Trace from the driver to see if there are any errors.

  • Enable the driver trace at level 5.

  • Delete the old trace file (if one exists) and restart the Data Collection Service driver. (The trace file can become very large.)