Reconciliation Engine crashes after Atrium CMDB 9.1.04/18.05 Upgrade with ORA-00932: inconsistent datatypes: expected - got CLOB

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC Atrium CMDB Suite


    COMPONENT:

    BMC Atrium Core


    APPLIES TO:

    Atrium CMDB 9.1.04/18.05



    PROBLEM:

    After upgrading to CMDB 9.1.04 or 18.05, while running recon & armonitor logs we see

    arrecond.log
    <ERROR > <TID: 139778114111232> /* Fri Feb 02 2018 12:12:49.3881 */ Exception in changeState (ARERR[552] The SQL database operation failed.
    <ERROR > <TID: 139778114111232> /* Fri Feb 02 2018 12:12:49.3881 */ ORA-00932: inconsistent datatypes: expected - got CLOB
    <ERROR > <TID: 139778114111232> /* Fri Feb 02 2018 12:12:49.3881 */ )
    <INFO > <TID: 140219167295296> /* Fri Feb 02 2018 12:12:49.4290 */ 9.1.04: 9.1.04
    <INFO > <TID: 140219167295296> /* Fri Feb 02 2018 12:12:49.4291 */ 9.1.04: 9.1.04
    <INFO > <TID: 140219167295296> /* Fri Feb 02 2018 12:12:49.4291 */ Reconciliation Engine: Reconciliation Engine 9.1 Service Pack 04

    armonitor.log
    <MNTR> <TNAME: Thread-13 > <INFO > <ProcessMonitor > < ProcessMonitor.java:602 > /* Fri Feb 02 18 12:18:51.0559 */ Attempting to start Process [ BMC:ReconcilationEngine ], attempt [ 424 ].
    <MNTR> <TNAME: Thread-13 > <INFO > <ProcessMonitor > < ProcessMonitor.java:170 > /* Fri Feb 02 18 12:18:51.0559 */ ProcessMonitor starting process [ BMC:ReconcilationEngine ].
     


    CAUSE:

    Defect with Field z_tmp_JobRunInstanceId size set to 0


    SOLUTION:

    This has been identified as a defect SW00542359 which will be resolved in a future release. The procedure (workaround) below will resolve the issue

    1. Open the AR developer studio in Base Development mode (Do not use Best Practice mode here)
    2. Open the CMDB:JobRunInfo form and look for the z_tmp_JobRunInstanceId
    3. Change its input length to 38 under properties--> Database
    4. Save the changes

    This should be enough to resolve this problem for next RE Jobs. 


     


    Article Number:

    000148831


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles