Confirm that BMC Atrium Integrator correctly transferred the data into BMC Atrium CMDB source dataset, BMC.IMPORT.BL.
If you cannot perform this task successfully, perform the following tasks to isolate the issue:
| | Description and reference |
|---|
Verify that the job ran to pull computer systems from BMC Decision Support for Server Automation into BMC Atrium CMDB. | | Jobs are scheduled to run periodically, and can be configured in BMC Atrium Integrator.
The BL_LOAD_SRVR_PROPS job runs first. It triggers the BL_PULL_COMPUTERSYSTEM transformation, which populates computer systems in BMC Atrium CMDB. When this transformation completes, it triggers other transformations that transfer components and relationships.
Check the status of the job by clicking the View Job Run Status link in the BMC Atrium Integrator Console. When the job run is complete, on the History tab, view the job run details and logging details. These details indicate when the job run started and completed, and report issues such as failure to connect to a database. |
| | Use the following procedure to test the connection to BMC Server Automation database or BMC Atrium CMDB: - Log on to Atrium Integrator Spoon.
- From the Tools menu, choose Repository > Explore.
- In the right pane, double-click the BL2ATRIUM_REPO repository.
- Double-click the BL_LOAD_SRVR_PROPS job.
- In the Explorer in the left pane, double-click BL_DB_CONNECTION.
- In the dialog box, click Test to verify the connectivity.
|
Verify that product components are operational. | See description column for details. | BMC Atrium Integrator
Run the AtriumCoreMaintenanceTool and use the Health Check page feature to verify that BMC Atrium Integrator is operational.
BMC Atrium CMDB
Run the AtriumCoreMaintenanceTool and use the Health Check page feature to verify that BMC Atrium CMDB is operational. For more information, see "Post-installation Health Check" in the BMC Atrium Core Installation Guide, which is available here.
BMC Server Automation
Using the BMC Server Automation Console, select Configuration > Infrastructure Management. Expand the Application Servers node, and click the name of each Application Server. This displays configuration information about the Application Server. |
Enable debug logs in BMC Atrium Integrator | | If a data exchange runs, but encounters errors transferring some records, you can enable more verbose logging to see the details of which records receive the errors and what data is passed. Data exchange debug logs can grow large quickly, so they should be enabled only during testing. - Access the BMC Remedy AR System by using the following URL in a browser:
http://<midTierServer>:<port>/arsys/forms/<ARserverName> - Log on.
- Click the Atrium Integrator Console link.
- Click Data Exchange Mapping.
- Select the data exchange that is having issues.
- Click Open.
- Go to the Advanced Settings page.
- Select the checkboxes for all debug levels: API calls, SQL Statements, Record Summary, Record Details.
- Set the Max Debug Size to a large value (such as 1048596 bytes) to minimize the number of files generated.
- Generate the logs and search for ERR to find error numbers.
Tips on interpreting Atrium Integrator log entries:
ORA- or SQLSERV - Errors interacting with the BMC Decision Support for Server Automation database
3300 - 3399 - Errors given by BMC Atrium Integrator, such as issues with adapters
8755, 8760 – Errors with BMC Remedy AR System plugins, requires Filter and Plugin logging
90, 91, 92, 93, 94 - Connection or timeout errors to BMC Remedy AR System, which might indicate performance issues
10000 or above – These errors can be caused by BMC Remedy AR System workflow. Search API/SQL, Filter, and Plugin logs to find more detail about the transaction that leads to the error.
<unable to connect to db vendor> - Verify the vendor database connection and parameters
<column does not exist> - Verify that the database views exist in the inventory database.
For help interpreting the logs and using BMC Atrium Integrator diagnostics, see BMC Atrium Integrator logging and debugging in the BMC Atrium Core documentation.
|
Enable debug logs in BMC Remedy AR System. | | If appropriate, enable Filter/API/SQL/Plugin logs in BMC Remedy AR System to investigate specific errors.
To enable BMC Remedy AR System Filter, API, SQL, and Plug-In logs: - Access BMC Remedy AR System by using the following URL in a browser:
http://<midTierServer>:<port>/arsys/forms/<ARserverName> - Log on.
- Click the AR System Administration Console link.
- Navigate in the tree: System > General > Server Information.
- Select the Log Files page.
- Select the checkboxes for API, SQL, Filter, and Plug-In. Verify each writes to a file, and note the file name and location. Select the option for Plug-In Log, and set Log Level to All. Set Maximum Log-File Size to 0 (zero) for unlimited.
- Click Apply to enable the logs. The changes happen immediately.
Generate the logs and examine the contents. |
Collect standard diagnostics. | | You can use the AtriumCoreMaintenanceTool to collect environment, version, configuration, and log files into a zip file for investigation. To do this, launch the tool and click Zip All Logs. This collects the logs and configuration for BMC Atrium Integrator, BMC Atrium CMDB, and BMC Remedy AR System.
For more details, see "How to prepare log files for BMC Customer Support" in the BMC Atrium Core Installation Guide, which is available here. |