CORACLEANUP performance

Products

• CA IT Asset Manager
• ASSET PORTFOLIO MGMT- SERVER
• CA Service Management - Asset Portfolio Management
• CA Service Management - Service Desk Manager
• CA Service Desk Manager

Issue/Introduction

CORACLEANUP performance. How to speed up CORACLEANUP processing.

Environment

CA Asset Portfolio Management and CA Service Desk Manager 17.x

Resolution

There are many factors that impact CORACLEANUP performance:

• 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
• Load and specifications (memory, cpu speed) of server where CORACLEANUP is executed
• Llad and specifications of the database server
• 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.

resource_name
serial_number
host_name
mac_address
dns_name.
resource_tag (alt asset id

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

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 MDB database. Use either the ITAM data importer or the delete option within the APM graphical interface.