Troubleshooting performance issues caused by missing CMDB indexes
This topic lists the out-of-the-box CMDB indexes that should always exist. If any index listed on this page is missing, it may lead to performance issues. To resolve any performance issue that may occur due to the missing index, you must add the missing index in the system.
List of out-of-the-box indexes
The following tables display the out-of-the-box indexes that must always exist in your system.
BMC.CORE:BMC_BaseElement | |
---|---|
Field name | Field ID |
InstanceId | 179 |
ClassId | 400079600 |
RelLeadClassId | 400131300 |
ReconciliationIdentity;MarkAsDeleted;DatasetId;RequestId | 400129200,400129100,400127400,1 |
RelLeadInstanceId | 400131200 |
ReconciliationMergeStatus;ModifiedDate;MarkAsDeleted;ReconciliationIdentity | 530060100,6,400129100,400129200 |
ReconciliationMergeStatus;ModifiedDate;ReconciliationIdentity | 530060100,6,400129200 |
ReconciliationIdentity;MarkAsDeleted | 400129200,400129100 |
Model | 240001002 |
ADDMIntegrationId;DatasetId | 530060200,400127400 |
TokenId;DatasetId | 530010100,400127400 |
ClassId;NormalizationStatus;InstanceId | 400079600,530041601,179 |
Name | 200000020 |
ManufacturerName | 240001003 |
SerialNumber | 200000001 |
ComponentAliases Important: Use Remedy Developer Studio to create an index on ComponentAliases. | 301220200 |
BMC.CORE:BMC_BaseRelationship | |
---|---|
Field Name | Field ID |
InstanceId | 179 |
ClassId | 400079600 |
RelLeadClassId | 400131300 |
DatasetId;ReconciliationIdentity;MarkAsDeleted;RequestId | 400127400,400129200,400129100,1 |
RelLeadInstanceId | 400131200 |
ReconciliationMergeStatus;ModifiedDate;MarkAsDeleted;ReconciliationIdentity | 530060100,6,400129100,400129200 |
ReconciliationMergeStatus;ModifiedDate;ReconciliationIdentity | 530060100,6,400129200 |
ReconciliationIdentity;MarkAsDeleted | 400129200,400129100 |
Destination.ReconciliationIdentity;Source.ReconciliationIdentity | 400131000,400130900 |
Source.InstanceId;Destination.ClassId | 490008000,490009100 |
Destination.InstanceId;Source.ClassId | 490009000,490008100 |
ReconciliationMergeStatus;ModifiedDate;DatasetId;ReconciliationIdentity | 530060100,6,400127400,400129200 |
Source.InstanceId;Source.ClassId;RequestId | 490008000,490008100,1 |
Destination.InstanceId;Destination.ClassId;RequestId | 490009000,490009100,1 |
InstanceId;ReconciliationIdentity;ClassId;Destination.InstanceId;Source.InstanceId; RequestId | 179,400129200,400079600,490009000,490008000,1 |
ReconciliationIdentity;Source.InstanceId | 400129200,490008000 |
Source.ClassId;Source.DatasetId | 490008100,400128800 |
DatasetId;ImpactSourceId;ImpactDestinationId | 400127400, 530060400, 530060500 |
Source.ReconciliationIdentity | 400130900 |
ClassId;NormalizationStatus;InstanceId | 400079600;530041601;179 |
Before you begin
Before you modify system indexes, you must ensure that you have Remedy Developer Studio installed. For more information, see BMC Remedy Developer Studio.
To create missing system indexes
Use this procedure to add missing out-of-the-box system indexes and custom indexes.
- Log in to the computer where Remedy Developer Studio is installed.
- Open Remedy Developer Studio.
- Select File > Switch Mode > Base Development
- In the AR System Navigator, double-click Forms.
- On the AR System Navigator tab, expand the source server and under All Objects select Forms.
The Forms tab opens, listing all the AR forms. - In the Forms window, double-click BMC.CORE:BMC_BaseElement to open it.
- Click the Definitions tab at the bottom of the form window.
On the Definitions tab, click Indexes.
The existing indexes and the fields used in the indexes are listed.
- Click New.
Select the new index and perform the following steps:
- To add fields to the index, click Add and fill the required information in the Field Selector dialog box for each field.
- To remove fields from the index, click Remove > Remove All buttons.
- Save the form.
Similarly, you can add the missing indexes to the BMC.CORE:BMC_BaseRelationship form.