Troubleshooting for the Data Collection Component (Data Collection Component)

You can use this troubleshooting information to help you understand, isolate, and resolve problems with your installation of the Data Collection Component (Data Collection Component).

Here are three possible problems you might run into:

Data warehouse records are missing for a project area
After upgrading from a version 5 release, resource groups aren't added automatically
Data warehouse reports are showing links to deleted artifacts

Tip: To log in to the Data Collection Component: The URL is https://<server>:<port>/dcc/web, where <server> is the fully qualified domain name or localhost and the context root is /dcc/web. For example, in a web browser, type the address: https://localhost:9443/dcc/web. For more information, see Collecting data with the Data Collection Component.

User records are missing from a Jazz Team Server resource group

If project data is missing from the data warehouse, you can force a full reload of a data source. Several symptoms can indicate this problem:

You don't see your project listed in the Limit the scope section of Report Builder.
The Data Collection Job Status administration page doesn't include your project.
User records are missing from a Jazz® Team Server resource group.

To force a data source to load fully:

Go to https://<server>:<port>/dcc/web#action=com.ibm.rational.datacollection.manageResources.configureDeltaLoad.
Change the load type for the resource group to Full and save.
Make a small change to the Jazz Team Server resource group, such as an edit to the project area summary. This action causes the read access information for the project area to reload.
The next time the Data Collection Component jobs run, data from the resource group is reloaded into the data warehouse.

After you upgrade from a Version 5 release of the Data Collection Component, resource groups aren't added automatically

If your Version 5 release manually defined friend relationships between the Data Collection Component application and otherIBM® Engineering Lifecycle Management applications, existing friend relationships might keep resource groups from being added to the data warehouse. You need to remove all friend relationships in both directions: from Data Collection Component to other applications except the Jazz Team Server, and from other applications to Data Collection Component.

To fix the issue after an upgrade:

Remove the manually defined friend relationships from both the application's administration page and the Data Collection Component administration page, leaving only the Jazz Team Server For more information about removing friend relationships, see Deleting friends from the friends list.
Rerun dcc/setup to migrate the application data to the current data warehouse.

Data warehouse reports are showing links to deleted artifacts

The data warehouse reports from IBM Engineering Requirements Management DOORS® Next are displaying links that were deleted since the last successful data collection job runs by Data Collection Component. Data collection jobs are also known as ETL (extract, transform, and load) jobs.

Important: Before you begin, you must make a backup of the data warehouse database.

Run the following SQL queries against the data warehouse database:
1. ```
SELECT DISTINCT SOURCE_ID FROM RIODS.REQUIREMENT
```
  If only one ID is returned (aside from a row that contains a value of -1), proceed by running the UPDATE SQL command in the next step.
  If multiple IDs are returned, you must identify the SOURCE_ID for each of the Engineering Requirements Management DOORS Next repositories that needs repair. To identify the SOURCE_ID, run the following SQL command against the data warehouse by using a known requirement URL for each Engineering Requirements Management DOORS Next data set that needs repair:
```
SELECT SOURCE_ID FROM RIODS.REQUIREMENT WHERE URL = '<DNG Resource URL>'
```
  Example
```
SELECT SOURCE_ID FROM RIODS.REQUIREMENT WHERE URL = 'https://clmweb.ibm.com/rm/resources/_sTCYASD_EeaxLPLal_NU8'
```
  After you identify the SOURCE_ID, run the UPDATE SQL command in the next step with the SOURCE_ID.
2. The following UPDATE SQL commands temporarily mark all Engineering Requirements Management DOORS Next artifacts as deleted in the data warehouse until the full ETL load completes.
  Remember: The data warehouse reports do not show the Engineering Requirements Management DOORS Next artifacts until the ETL load is complete.
```
UPDATE RIODS.REQUIREMENT SET ISSOFTDELETED=1, REC_DATETIME = CURRENT_TIMESTAMP WHERE SOURCE_ID = '<ID FROM ABOVE QUERY>'
UPDATE RIODS.REQUIREMENT_COLLECTION SET ISSOFTDELETED=1, REC_DATETIME = CURRENT_TIMESTAMP WHERE SOURCE_ID = '<ID FROM ABOVE QUERY>'
```
  Example
```
UPDATE RIODS.REQUIREMENT SET ISSOFTDELETED=1, REC_DATETIME = CURRENT_TIMESTAMP WHERE SOURCE_ID = '_ZsMvUqgXEeW4wNRvJ2fzagRRC'
UPDATE RIODS.REQUIREMENT_COLLECTION SET ISSOFTDELETED=1, REC_DATETIME = CURRENT_TIMESTAMP WHERE SOURCE_ID = '_ZsMvUqgXEeW4wNRvJ2fzagRRC'
```
After the UPDATE SQL command is complete, you must run a full ETL load for Engineering Requirements Management DOORS Next:
1. In a web browser, open and log in to Data Collection Component, following the tip earlier in this topic.
2. In the left pane, select Delta Load Configuration.
3. Select the Engineering Requirements Management DOORS Next repository for reload.
4. Under the Load Type column, select Full Load.
5. To apply the changes, click Save.
You can choose to run the data collection job on schedule, or run the Requirement Management job manually. But strongly consider running this job off hours when possible.