Using the CORA Cleanup Utility

This article contains the following topics: 
casm172
This article contains the following topics:
 
Introduction
The CORA Cleanup utility allows the administrator to determine the action required on the unregistered assets. 
In certain circumstances, the data within the CORA cache gets corrupt or inconsistent. This results in the inability to edit the Configuration Items (CI) that exist in the CMDB or create new CIs. In such scenarios, it is recommended you contact the CA Support.
It is recommended to use the CORA cleanup utility only under the guidance of CA support.
How the CORA Cleanup Utility Works
CORA Cleanup utility enforces the CORA rules to rebuild its internal tables: ca_asset_source; ca_logical_asset; ca_logical_asset_property; ca_asset. CORA Cleanup utility does not delete or update any Configuration Item or Asset data, it only uses the data available in ca_owned_resource, ca_discovered_hardware tables and uses it to rebuild the internal cache. The utility creates a log file that can be reviewed to identify the assets that are not registered due to various reasons. In most scenarios, CORA considers the Configuration Item and Asset as a duplicate of another already registered item.
The utility provides the following real-time statistics:
  • Number of total objects to be processed
  • Number of objects processes successfully
  • Number of objects that failed to process
  • Time Estimate to complete objects processing
Based on the log file and the real-time progress report, the Administrator can take further actions to manually clean up the data for the product on which it is executed.
Stop the CA SDM or CA APM services before executing the CORA Cleanup utility. Stopping the services improves the utility performance and prevents any erroneous creation or update of Configuration Items or Assets while the CORA cache is being rebuilt.
Prerequisite
  • Set JAVA_HOME environment variable.
  • Ensure that the required product version from where you want to execute the utility is installed: CA SDM 17.1 and / or CA ITAM 17.1
Perform Cleanup
Follow these steps:
  1. Navigate to the location that contains the CORA Cleanup utility.
    1. For CA SDM:
      NX_ROOT\bin
    2. For CA APM:
      <ITAM installation folder>\SC\CORA
  2. Execute the utility:
    • Windows:
      coracleanup.cmd
    • Linux/Solaris: 
      coracleanup.sh
  3. Define the following parameters:
    • Database server name
    • Database type
      : MSSQL or Oracle
    • Username
      : database username
    • Password
      : database password
    • Scope
      : Define the product scope against which the Cora cleanup runs. For example, select
      USD
      to execute the cleanup on CA Service Desk Manager.
      • USD
        : CA Service Desk Manager
      • ALL
        : Select the option to execute the cleanup utility on all supported products.
    • Method
      : Define the action that the utility takes on the results:
      • REINIT
        : Select this option to refresh the CORA data.
      • DELETE
        : Select this option to delete the data from the following tables: ca_asset_source; ca_logical_asset; ca_logical_asset_property; ca_asset
        The utility does not delete any data from the product(s) defined in the scope.
      • APITEST
        : Select this option to test the API threads.
      • PRODTEST
        : Select this option to test the production setup.
      • UPDTEST
        : Select this option to execute the various database queries to select, update, insert, and so on. To perform this action, CORA utility establishes a JDBC connection with the database.
         Note:
        Use the
        APITEST
        ,
        PRODTEST
        ,
        UPDTEST
        options only upon request from Support, typically for debugging the connectivity issues.
      • REPAIR
        : Select this option to restart the CORA cleanup from where the REINIT failed. We recommend that you use the option after a REINIT and if it fails for any reason.
    • MSSQL database name
      : If you are using MSSQL database, provide the corresponding database name.
    • Oracle server instance
      : If you are using Oracle database, provide the corresponding database name.
    • Database owner
      : Define the database owner if it is different from the default database owner.
    • Port number
      : Define the port number if it is different from the default JDBC port number.
    • Following is the Oracle syntax for CoraCleanup utility
      CORACLEANUP /SERVER <servername>  /TYPE 3 /USERNAME mdbadmin /PASSWORD <password> /SCOPE <scope> /METHOD reinit /INSTANCE <instance>
    • Following is the SQL syntax for CoraCleanup utility
      CORACLEANUP /SERVER <servername>  /TYPE 2 /USERNAME <dbuser> /PASSWORD <password> /SCOPE <scope> /METHOD reinit /DATABASE mdb
  4. Navigate to the location that contains the output log file.
    1. For CA SDM: 
      NX_ROOT/log
    2. For CA APM: 
      <ITAM installation folder>\SC\CORA\corautil.log
Additional Information
For additional information about CORA Cleanup and performance, see Troubleshooting and CORA Cleanup Performance .