Presentation Server returns error BCO_PRV_ERR012 [DatamartServiceRestWS] Failed to query datamart 2151

Version 5
    Share This:

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


    PRODUCT:

    TrueSight Capacity Optimization


    COMPONENT:

    Capacity Optimization


    APPLIES TO:

    TSCO 10.7, 11.0



    PROBLEM:

    Truesight capacity optimization Presentation Server returns error BCO_PRV_ERR012 [DatamartServiceRestWS] Failed to query datamart 2151 [03/04/2017 10:06:40]. Manual rebuild of datamart eliminates the error. No errors found in previous days materialization task. Yet, "physical name" views are not available even with query via TOAD.

    12
    3

    Below is an example of a similar issue with the Sentry Netapp views in TSCO:

    User-added image
    It is showing the datamart is trying to access an orphaned datamart (1830 SEN_NETAPP_SYSTEM). The log shows the orphaned datamarts when it tries to materialize:: 
     

    2019-02-26 00:11:01,919 INFO [[4] chainPos-3]- Clearing orphan database objects...  2019-02-26 00:11:03,144 INFO [[4] chainPos-3]- Dropping orphan VIEW ER_V_1837_3  2019-02-26 00:11:03,466 INFO [[4] chainPos-3]- Dropping orphan VIEW ER_V_1837_2  2019-02-26 00:11:03,487 INFO [[4] chainPos-3]- Dropping orphan VIEW ER_V_1837_1  2019-02-26 00:11:03,504 INFO [[4] chainPos-3]- Dropping orphan VIEW ER_V_1836_3  2019-02-26 00:11:03,524 INFO [[4] chainPos-3]- Dropping orphan VIEW ER_V_1836_2  2019-02-26 00:11:03,540 INFO [[4] chainPos-3]- Dropping orphan VIEW ER_V_1836_1  2019-02-26 00:11:03,559 INFO [[4] chainPos-3]- Dropping orphan VIEW ER_V_1835_3  2019-02-26 00:11:03,575 INFO [[4] chainPos-3]- Dropping orphan VIEW ER_V_1835_2  2019-02-26 00:11:03,590 INFO [[4] chainPos-3]- Dropping orphan VIEW ER_V_1835_1  2019-02-26 00:11:03,604 INFO [[4] chainPos-3]- Dropping orphan VIEW ER_V_1831_3  2019-02-26 00:11:03,620 INFO [[4] chainPos-3]- Dropping orphan VIEW ER_V_1831_2  2019-02-26 00:11:03,636 INFO [[4] chainPos-3]- Dropping orphan VIEW ER_V_1831_1  2019-02-26 00:11:03,649 INFO [[4] chainPos-3]- Dropping orphan VIEW ER_V_1830_3  2019-02-26 00:11:03,668 INFO [[4] chainPos-3]- Dropping orphan VIEW ER_V_1830_2  2019-02-26 00:11:03,687 INFO [[4] chainPos-3]- Dropping orphan VIEW ER_V_1830_1  2019-02-26 00:11:03,706 INFO [[4] chainPos-3]- 15 orphan objects dropped from database 
      
    This means we need to correct the views that are being orphaned that are needed by the views. To do this we are going to fix the physname of the orphaned view with the following sql:  

       
      update er_def set physname='ER_V_1830_${POSTFIX}' where erid=1830;   
    update er_def set physname='ER_V_1831_${POSTFIX}' where erid=1831;   
    update er_def set physname='ER_V_1835_${POSTFIX}' where erid=1835;   
    update er_def set physname='ER_V_1836_${POSTFIX}' where erid=1836;   
    update er_def set physname='ER_V_1837_${POSTFIX}' where erid=1837;   
     
    commit;  
      
    Another option is to install the latest NetApp-Capacity-Views-for-TrueSight-CO from Sentry. It needs to be version NetApp Capacity Views - Code Level 132 or higher for the fix. 

     


    CAUSE:

    when the SQLview was created the view was using name as mixed case,hence it labelled the view as orphaned and DB space manager task clears the orphan views from TSCO.


    SOLUTION:

    Solution:

    Workaround:
    Run below Query to fix the mixed case PHYSNAME column updation

    begin
    UPDATE ER_DEF
    SET PHYSNAME = UPPER(PHYSNAME)
    WHERE ERID IN (2244, 2230, 2264, 2234, 2263, 2229);
    commit;
    end;

    Defect#QM002305827-custom datamart view is deleted by database manager task

    Defect created to fix the mixed case PHYSNAME column updation problem, as well as update the v_orphan view to also to case in-sensitive  check for views to be labeled as orphan.

    This fix will be added in next CHF of 10.7

     


    Article Number:

    000137582


    Article Type:

    Solutions to a Product Problem



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