CA Support recommend that the following steps be reviewed to diagnose CORA issues.
CORA underpins all integration between different CA products and all data loading via product utilties into CA products.
If CORA is not working, information may be missing, duplicated or otherwise in error.
CORA Integration with Service Desk and CMDB
Overview and Definition:
Note: This information is supplementary to the official product documentation. Where a conflict arises, the product documentation takes precedence.
The key to all integration between CA products is "CORA."
All Unicenter r11/r12 products use the common MDB schema to store and manage their data. The Common Registration API (CORA) is the interface through which these configuration items are registered. It is the only source for updating these tables, ensuring that configuration item data flows consistently, thereby supporting the data and referential integrity of the MDB's master configuration item data model.
CORA's purpose is to prevent the same object from being placed in the MDB multiple times by the many different methods of discovery in use between products that access the MDB. It stands between products and any update to a CA product goes through CORA rules.
It is important to note that CORA rules are not invoked by means that are our outside of the product. For example, a direct database load using native database utilities would not go through CORA. However, a database load using any CA product utilities, such as pdm_load for Service Desk, does go through CORA.
The logic of CORA is to identify each configuration item and map the same configuration item to the products which register with the same attributes.
See the "The MDB, Hardware Configuration items and CORA" for the essential information to understand how CORA works. This document is the foundation of understanding CORA and associated problems. Filename CORA_MDB_and_Assets_SC.pdf
What is a Configuration Item?
While there is a strict definition of a "Configuration Item" within the ITIL methodology, one which is followed closely be many CA products, it is important to note that in common usage the terms Assets and Configuration Items are often used interchangeably. It may be important to understand the context in which these terms are used in order to understand an issue. Here are some of the ways that the terms may be used differently:
Service Desk/CMDB - The role of an configuration item is any resource that provides value to the enterprise, which may not be an IT resource. For example, a server, a Document or a Role.
In most cases an "Asset" or "Configuration Item" in the Service Desk/CMDB world refers to an IT resource, usually a piece of hardware or software.
For Unicenter APM, it may also be a software license, a catalogue of available laptops, desktops for new hires and so on.
DSM and NSM users may define Assets as hardware items to discovered, mapped and monitored.
The CORA API provides a way to link discovered/monitored assets with the same entity on the other side where it is the owned resource for UAPM, CMDB and Service Desk.
See also pdm_reg_assets, pdm_discimp and pdm_nsmimp.
CA Support Troubleshooting Guidelines
If an integration between CA products appears to satisfy other setup requirements, and yet unanticipated results are seen, such as duplicate or missing items, it could be an indication that a review of CORA is required.
The underlying integration method should be reviewed as a preliminary step though. For example, an unchanged integration setup which has been confirmed to have been working in the past which now produces unexpected duplicates could indicate that time may be best spent on analysing around CORA. An integration which has never worked, or which fails on single item test cases may have analysis time better spent on the integration setup within the products.
The Quick Fix Attempt
The following procedure is a common resolution path to many CORA issues.
In particular, it should be followed for all "duplicate" configuration item problems.
Information Gathering and Trouble-Shooting Guide
Export_Tables <SQL SERVER NAME> <SQL USER> <SQL PASSWORD>Replace <SQL SERVER NAME> with the SQL server name of MDB