Issue 1: BMC Asset Management - Sandbox recon jobs keep failing due to in correct configuration. Issue 2: BMC.ASSET records with 0 reconciliation id Issue 3: BMC Asset Management - Sandbox recon jobs keep failing due to multiple trigger within a few milliseconds in 23.3.Patch 3 after reconciliation is a separate pod <ERROR > <TID: 140001309133624> /* Thu Oct 31 2024 10:52:32.4459 */ Error encountered:: Issue 4: BMC Asset Management - Sandbox reconciliation job experiences a delay of 4 to 5 minutes at the beginning of each run. API/SQL/Filter logs show the job trigger is done as per CI creation, and a record is pushed to the Application Pending form. > /* Tue Jul 08 2025 11:18:14.4290 */ Application-Command Reconciliation Trigger-Job -o "BMC Asset Management - SandBox" The Application Pending form has huge records
|
Issu 1 and Solution 1 Follow the below steps in case recon jobs run slow 1) Change log level from Debug to Error for Reconciliation logs
Issue 2 and Solution 2 BMC.ASSET records with 0 reconciliation id These records have to be cleaned up Some of the sample queries that can be used for Business Service CI class where reconciliation id is 0. These may vary on different environment. The table name has to be picked from the specific environments. T918 (BMC.CORE:BMC_BusinessService join form) Select * from T805 where C400079600 ='BMC_BUSINESSSERVICE' AND C400127400 = 'BMC.ASSET' AND C400129200 = '0' BMC.CORE:BMC_BusinessService
Sandbox job gets triggered when a CI is modified via the integrations or via Asset management console When the same job is triggered frequently (within milliseconds), symptoms like incorrect job status and timings are reported.
Issue 4 and Solution 4 Check the records in Application Pending form if records are huge delete them select count (*) from T41 where C501 like '%Trigger-Job%'; Once records are reduced below 100 the sandbox job will start working fine and trigger will be there every 1 or 2 minutes
|