CORACLEANUP performance. Ways to speed up CORACLEANUP processing.

book

Article ID: 49232

calendar_today

Updated On:

Products

CA Automation Suite for Data Centers - Configuration Automation CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction

Description:

CORACLEANUP performance. How to speed up CORACLEANUP processing.

Solution:

There are many factors that impact CORACLEANUP performance:

  1. The DATA in the MDB. If there are many duplicate CORA fields, (the same information in the same CORA data fields, for multiple assets), extra processing time is needed for CORACLEANUP to process the data.
  2. The load and specifications (memory,cpu speed) of the CORACLEANUP execution server.
  3. The load and specifications of the database server.
  4. The network connection, speed and traffic load.

Prior to running CORACLEANUP, you can manually check the database for duplicate entries and resolve some of the duplicates manually. To check the mdb for duplicate CORA fields, use the query below and run it once for each of the 6 CORA fields, substituting <fieldName>, for one of the following 6 fields.

  1. resource_name
  2. serial_number
  3. host_name
  4. mac_address
  5. dns_name.
  6. resource_tag (alt asset id

    SELECT <fieldName>, COUNT(*) TotalCount
    FROM ca_owned_resource
    GROUP BY <fieldName>
    HAVING COUNT(*) > 1
    ORDER BY COUNT(*) DESC

    Then where you find the most duplicates, review the duplicate records to determine which record you want to retain, modify to make unique, or remove. For example, if you run the query:

    SELECT resource_name, COUNT(*) TotalCount
    FROM ca_owned_resource
    GROUP BY resource_name
    HAVING COUNT(*) > 1
    ORDER BY COUNT(*) DESC
    and it returns 50 occurrences of the resource_name = 'My Computer', then run a search within APM to view all of these assets and determine which records need modification, correction or deletion.

NOTE: When deleting asset information, do NOT delete records from the backend database. Use either the ITAM data importer or the delete option within the APM graphical interface.

Environment

Release:
Component: BITCM