This documentation supports the 20.02 version of BMC CMDB.

To view an earlier version, select the version from the Product version menu.

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 nameField ID
InstanceId179
ClassId400079600
RelLeadClassId400131300
ReconciliationIdentity;MarkAsDeleted;DatasetId;RequestId400129200,400129100,400127400,1
RelLeadInstanceId400131200
ReconciliationMergeStatus;ModifiedDate;MarkAsDeleted;ReconciliationIdentity530060100,6,400129100,400129200
ReconciliationMergeStatus;ModifiedDate;ReconciliationIdentity

530060100,6,400129200

ReconciliationIdentity;MarkAsDeleted400129200,400129100
Model240001002
ADDMIntegrationId;DatasetId530060200,400127400
TokenId;DatasetId

530010100,400127400

ClassId;NormalizationStatus;InstanceId400079600,530041601,179
Name200000020 
ManufacturerName 240001003
SerialNumber 200000001

ComponentAliases

Important: Use Remedy Developer Studio to create an index on ComponentAliases.

 301220200
BMC.CORE:BMC_BaseRelationship
Field NameField ID
InstanceId179
ClassId400079600
RelLeadClassId400131300
DatasetId;ReconciliationIdentity;MarkAsDeleted;RequestId400127400,400129200,400129100,1
RelLeadInstanceId400131200
ReconciliationMergeStatus;ModifiedDate;MarkAsDeleted;ReconciliationIdentity530060100,6,400129100,400129200
ReconciliationMergeStatus;ModifiedDate;ReconciliationIdentity530060100,6,400129200
ReconciliationIdentity;MarkAsDeleted400129200,400129100
Destination.ReconciliationIdentity;Source.ReconciliationIdentity400131000,400130900
Source.InstanceId;Destination.ClassId490008000,490009100
Destination.InstanceId;Source.ClassId490009000,490008100
ReconciliationMergeStatus;ModifiedDate;DatasetId;ReconciliationIdentity530060100,6,400127400,400129200
Source.InstanceId;Source.ClassId;RequestId490008000,490008100,1 
Destination.InstanceId;Destination.ClassId;RequestId490009000,490009100,1
InstanceId;ReconciliationIdentity;ClassId;Destination.InstanceId;Source.InstanceId; RequestId179,400129200,400079600,490009000,490008000,1
ReconciliationIdentity;Source.InstanceId400129200,490008000
Source.ClassId;Source.DatasetId490008100,400128800
DatasetId;ImpactSourceId;ImpactDestinationId400127400, 530060400, 530060500
Source.ReconciliationIdentity400130900
ClassId;NormalizationStatus;InstanceId400079600;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 Open link .

To create missing system indexes

Use this procedure to add missing out-of-the-box system indexes and custom indexes. 

  1. Log in to the computer where Remedy Developer Studio is installed.

  2. Open Remedy Developer Studio.
  3. Select File > Switch Mode > Base Development

  4. In the AR System Navigator, double-click Forms.
  5. 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.
  6. In the Forms window, double-click BMC.CORE:BMC_BaseElement to open it.
  7. Click the Definitions tab at the bottom of the form window.
  8. On the Definitions tab, click Indexes.

    The existing indexes and the fields used in the indexes are listed.

  9. Click New.
  10. 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.

    Important

    • You can combine multiple fields into a composite index.
    • You can enter as many as 16 fields.
    • You should add the fields in the order you want them indexed, or you can use the Up and Down buttons to put them in the correct order.
    • Each indexed field must be less than or equal to 255 characters, but the composite Index can have a total length greater than 255.
  11. Save the form.

Similarly, you can add the missing indexes to the BMC.CORE:BMC_BaseRelationship form.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Heliodoro Alvarez

    For Index on "ComponentAliases" please mention that this needs to be created using the Class Manager it is not possible to create this Index through Dev Studio because "ComponentAliases" is heir by BMC.SIM namespace, from Dev Studio you only can use the attributes from BMC.CORE and BMC.AM

    Nov 11, 2021 10:29
    1. Maithili Deshpande

      Hi Heliodoro,

      Thank you for pointing out this issue with the content. We have corrected the topic with your feedback.

      Regards,
      Maithili

      Nov 12, 2021 12:25
      1. Dieter Bertram

        Hi, creating an index via Dev Studio will violate the data consistency of the CMDB data model. Never update the CMDB by using the Dev Studio, the overlay will be discovered during the update check and will not allow to upgrade.

        Nov 15, 2021 02:40
        1. Maithili Deshpande

          Hi Dieter, 

          That's right, updating the core forms in Dev Studio creates an overlay, and Class Manager is the best place to make changes to the data model. However, an overlay is created if we use the Best Practice mode in Dev Studio.

          In this topic, we have mentioned that users must switch to Base Development mode before making changes in Dev Studio. This step ensures that there is no overlay.

          Hope this is useful.

          Regards,
          Maithili


          Nov 22, 2021 08:33