5.3 Troubleshooting Reporting Database

To troubleshoot the reporting database, you need to clear the reporting database on Role Based Provisioning Dashboard (RBPM). To clear the reporting database, perform the following steps:

  1. Stop the DCS and the MSGW drivers. Perform the following steps to stop the drivers:

    1. Login to the iManager.

    2. Go to Identity Manager Administration > Identity Manager Overview.

    3. Select root in the search field and click the search button.

      NOTE:If your tree contains a large number of objects, change the value of the container to where your driver set is located to avoid long search time.

    4. On the Driver Sets tab, select the driver set where DCS and MSGW drivers are running.

    5. Click Overview tab on the Driver Set Overview page.

      1. Right-click the upper right corner of the DCS driver icon and select Stop driver.

      2. Right-click the upper right corner of the DCS driver icon and select Edit properties.

      3. On the Identity Manager tab, select Driver Configuration.

      4. Scroll down to the Startup Options section and select the radio button next to Disabled, and press OK.

    6. Repeat Step 1.e.a to Step 1.e.b for the MSGW driver.

    7. Logout of the iManager server.

  2. Suspend Data Collection in the reporting module. Perform the following steps to suspend data collection:

    1. Open a new browser and login to the Reporting Module.

    2. Select Identity Vaults from the left-hand navigation.

    3. Under Data Collection Service Driver, uncheck Enable event collection.

    4. Under the Managed System Gateway Driver, press the stop button in the Collection state area.

    5. Press the Save button.

    6. Select Applications from the left-hand navigation.

      NOTE:Suspend any non-managed applications which is defined.

      1. Press the stop button in the Application state section.

    7. Press the Save button to save the configuration settings.

    8. Logout of the Reporting Module and close the browser.

  3. Issue the clean-up/purge request using REST. Perform the following steps to issue the clean-up/purge request

    1. Get the Authorization Token from the OSP module. You can use any browser tool to get an authorization token, such as Poster (Firefox) or Advanced REST Client (Chrome). Perform the following steps to get an authorization token:

      1. Enter the following parameters in the browser tool:

        • URL: http://myserver.novell.com:8180/osp/a/idm/auth/oauth2/grant

        • Method/Action: POST

        • Headers: Select any of the following parameters:

          • Name: Content-Type

          • Value: application/x-www-form-urlencoded

          • Name: Authorization

          • Value: BASIC (b64string in the format cn:password, using the SSO parameters from the DCS driver). For example:

            BASIC ZGNzZHJ2OmRyaXZlcgAA

        • Body Content: grant_type=password&username=<FDN in URLencode format>&password=<password>

          For example: 

          grant_type=password&username=cn%3Duaadmin%2Cou%3Dsa%2Co%3Ddata&password=novell

      2. Press the Execute/Send Request button.

      3. You should see a status message 200 Success, along with the token. A sample status message along with the token is displayed below:

        {
"access_token":"eHwAIEb42ZjiO4qTQM1G1sRshoy3SfaiGnSl6RCEdAxkyGYwVplLjetsKo6ComvKgOpF8N@mHf9hv3VuSxEOjiDjQdeiUv@RiERfa8qiOoZxtF1w9gf8ceVDfxGBAAWpDpCeS9NeYEM4nyoHT6QxgZQIzD4f5fAr@yOsyHTu5A@10HwNO8bIogd/KvwbkTR84pPG6um4hIbcUKaMLO7HVOhnOcA~",
"token_type":"bearer",
"expires_in":120,
"refresh_token":"eHwAIC9STVVKIDBDSNi3/yaCafvY5caU6iQPDYZNk9sSNtE55zlXdpfeJfdkPjTLEQ9ovPbM705DkdNkiOD9NJYEa5CJTP7snqYV0Eijq8NHUFg39gf8ceVDfxGBAAWpDpCeS9NeYEM4nyoHT6QxgZQIzD4f5fAr@yOsyHTu5A@10HwNO8bIogd/KvwbkTR84pPG6jzW4Os8NPmfRab0lyXKrOdI4hVLNAUuXSkTO88@I1@Ro5DZYqf2fzrKIATu14znlw~~"
}
0

    2. Now issue the database clear request using any Browser tool, such as Poster (Firefox) or Advanced REST Client (Chrome). Performing the following steps to issue the database clear request:

      1. Enter the following parameters in the browser tool:

        • URL: http://myserver.novell.com:8180/IDMDCS-CORE/rpt/collectors/data

        • Method/Action: DELETE

        • Headers: Select any of the following parameters:

          • Name: Authorization

          • Value: bearer %Token-value-from-above%

            For example:

            bearer eHwAIEb42ZjiO4qTQM1G1sRshoy3SfaiGnSl6RCEdAxkyGYwVplLjetsKo6ComvKgOpF8N@mHf9hv3VuSxEOjiDjQdeiUv@RiERfa8qiOoZxtF1w9gf8ceVDfxGBAAWpDpCeS9NeYEM4nyoHT6QxgZQIzD4f5fAr@yOsyHTu5A@10HwNO8bIogd/KvwbkTR84pPG6um4hIbcUKaMLO7HVOhnOcA~

      2. Press the Execute/Send Request button.

      3. You should see a status message 200 OK. A message is displayed in the server.log. We have shown a sample message below: 

        <date> <time> INFO  [com.novell.idm.rpt.core.server.logging.naudit.LogEvent] (http-0.0.0.0-8180-6) [RPT-CORE] [Data_Cleanup_Requested] Initiated by cn=uaadmin,ou=sa,o=data; Data Collector UUID ALL

  4. Now wait until the table idm_rpt_data.idmrpt_identity has 0 records. This may take a few minutes.

    1. You can check the table content by issuing the SQL request. Run the following command to check the table content:

      1. SELECT count(*) FROM idm_rpt_data.idmrpt_identity

    2. If you see 0 records after the clean up, jump to the next step.

  5. Using the iManager plugin, remove all processed associations from the DCS driver.

    1. Open a new browser and login to iManager.

    2. Go to Identity Manager Administration > Driver Inspector.

    3. In the Driver to Inspect field, click the search icon.

    4. On the pop-up window, browse and click on the DCS driver. Click OK.

    5. Click on the Actions menu, change the option to Filter for Processed' associations.

    6. Select all associations and click Delete. Repeat this step until there are no processed associations left.

    7. Click on the Actions menu, change the option to Show all associations.

  6. Start DCS and MSGW Drivers. Perform the following steps to start the DCS and MSGW drivers:

    1. Login to the iManager.

    2. Go to Identity Manager Administration > Identity Manager Overview.

    3. Select root in the search field and click on the search button.

      NOTE:If your tree contains a large number of objects, change the value of the container to where your driver set is located to avoid long search time.

    4. On the Driver Sets tab, select the driver set where DCS and MSGW drivers are running.

    5. Click on Overview tab on the Driver Set Overview page.

      1. Right-click on the Red circle on the DCS driver and select Edit properties.

      2. On the Identity Manager tab, select Driver Configuration.

      3. Scroll down to the Startup Options section and select the radio button next to Auto Start, and press OK.

      4. Check the Do not automatically synchronize the driver option. The driver migrates all the objects only for the time interval when the driver was disabled. If you wish to migrate all the data, goto Step 8.

      5. Right-click on the Red circle on the DCS driver and select Start Driver.

    6. Repeat Step 6.e.a to Step 6.e.e for the MSGW driver.

    7. Logout of the iManager server and close the browser.

  7. Enable Data Collection in the reporting module. Perform the following steps to enable data collection:

    1. Open a new browser and login to the Reporting Module.

    2. Select Identity Vaults from the left-hand navigation.

    3. Under Data Collection Service Driver, check the Enable event collection checkbox.

    4. Under the Managed System Gateway Driver, press the start button in the Collection state area.

    5. Press the Save button.

    6. Select Applications from the left-hand navigation.

      NOTE:Enable any non-managed applications which is defined.

      1. Press the start button in the Application state section.

    7. Press the Save button to save the configuration settings.

    8. Logout of the Reporting Module and close the browser.

  8. Perform Migrate from the Identity Vault in the DCS Driver.

  9. Perform Data Collection.