BMC Analytics - Known & Corrected Issues List

Version 1
    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 Analytics for BSM


    COMPONENT:

    BMC Analytics for BSM


    APPLIES TO:

    BMC Analytics for BSM 8.1\ 8.1.00.001



    QUESTION:

    Where to find BMC Analytics - Known & Corrected Issues List?


    ANSWER:

     

    Installation and upgrade issues

      

    Known and corrected issues related to installation or upgrade
    Click any column heading to sort this table or change sort direction.

                                                                                                                                                                                                                          

    Defect ID

    Category

    Description

    Affected versions

    Corrected in

    SW00448821Uninstalling

    When you uninstall BMC Atrium Single Sign-On, BMC Analytics for BSM does not clean the installation directory.

    Workaround: Manually delete the folders in the installation directory.

      
    SW00449398Application list

    When you click the Analytics link from BMC Remedy AR System, the application list that is displayed through the fly-out mode does not close after selection.

     8.1.00

    SW00451852

    Importing

    The BMC Analytics for BSM installer does not import some workflows.

     8.1.00
    SW00460736Upgrading

    When you perform the upgrade procedure, some old deprecated database objects still remain in the system instead of getting deleted by the installer.

     8.1.00
    SW00463149Installing

    The Installation Type Selection screen of the BMC Analytics for BSM installer displays the following product options for selection:

          
           
    • BMC ProactiveNet Performance Management
    •      
    • BMC Performance Manager Portal (enabled for continuous data export)
    •      
    • BMC Event and Impact Management
    •     

    Note: BMC Analytics for BSM does not provide the universe, reports, or objects for these products through the installer.

     8.1.00
      

    Other issues

      

    Known and corrected issues for areas other than installation and upgrade
    Click any column heading to sort this table or change sort direction.

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    Defect ID

    Category

    Description

    Affected versions

    Corrected in

    SW00351663Reporting

    The I10 Percentage of Incidents Reopened Incident Management report displays an error in the graph when the reopened_date value is NULL.

     8.1.00
    SW00363923Work Order objectsIf you use the BMC Analytics for BSM product with a BMC Remedy AR System server that uses a Microsoft SQL Server database, the value ALL is not included for the BMC Service Request Management Work Order objects. 

    Workaround: Manually select all the values in the list from within the report.
     8.1.00
    SW00371829Universe

    Importing a linked universe into the Designer tool takes up to 20 minutes, depending on the number of objects in your universe.

    This performance has been improved in SAP BusinessObjects BI 4.0 Service Pack 7 Patch 6.

     8.1.00
    SW00409810Reporting

    When you run any report from BMC Incident Management, the report stops responding without retrieving any data.

     8.1.00
    SW00424204Reporting

    You cannot create a report for the Master Contract in InfoView or BI Launchpad, because the Contract Type List does not have an option of Master Contract.

     8.1.00
    SW00426242Objects

    The description of the Assignee and Assigned Group objects is incorrect. It is the same for the Assignment detail (Service Desk > Incident Management > Incident) and Assignee (Service Desk > Incident Management > Incident > Assignment detail) classes.

    8.0.00
    8.1.00 

    8.1.00.01
    SW00435013Reporting

    When you create a BMC Asset Management report with the CI Name object and the associated manager, each CI name is displayed twice: once with the manager name and once with a duplicate "Unknown" line.

     8.1.00
    SW00443790Processes

    When you create an ad hoc report from the BMC Remedy ITSM universe using the Date Incurred object, a nonnumeric character (ORA-01858) is displayed instead of a date in the form of a numeric character.

     8.1.00
    SW0044536Processes

    When you create ad hoc reports, because of the incorrect definitions of the Work Order Submit Date and the Work Order Completed Date Dimension objects, incorrect results are displayed in the reports.

     8.1.00
    SW00447722Reporting

    Due to the incorrect definition of the Percentage of Resolve SLA and Percentage of Response SLA objects in the universe, the generated reports display incorrect results.

     8.1.00
    SW00449312Reporting

    There are some performance issues when you refresh the BMC Analytics for BSM custom reports using the BMC Remedy ITSM universe.

     8.1.00
    SW00449408Active link URL

    The Active Link URL is not displayed on the BMC Remedy ITSM home page to launch BMC Analytics for BSM even though the Active Link guide is displayed in BMC Remedy AR System.

    Workaround:

          
           
    1. Log in to the BMC Remedy Developer Studio and connect to the BMC Remedy AR System server.
    2.      
    3. Download the Analytics.zip file. Click the link to download the attachment. 
    4.      
    5. Extract the contents of the Analytics.zip file in the directory where you have installed BMC Remedy Developer Studio.
    6.      
    7. Import the Analytics.def file to BMC Remedy Developer Studio.
      Note: Select the Replace Objects on the Destination Server option and clear the other option while importing.
    8.      
    9. After the import procedure is successfully completed, open the ANA:Analytics:OpenURLGuide active link guide.
    10.      
    11. In the Entry Point section, change the Start Active Link from ANA:Analytics:Message to ANA:Analytics:OpenURL.
    12.      
    13. Change the active link guide permissions from Public Hidden to Public Visible and save the active link guide.
    14.      
    15. Open the ANA:Analytics:OpenURL active link.
    16.      
    17. In the if actions Run Process action, enter the correct BO InfoView or BI Launchpad URLs.
      For example:
       http://<hostName>:<port>/BOE/BI
      (If you use BMC Atrium Single Sign-On) Enter: http:// <fullyQualifiedBusinessObjectsServerName>:<port>/BI
      where the <hostName> is the host where SAP BusinessObjects is installed and <port> is the port number used by SAP BusinessObjects.
    18.      
    19. In the if actions Run Process action, change Execution Options from Disabled to Enable.
    20.      
    21. Save the active link.
    22.      
    23. Restart BMC Remedy Mid Tier and flush the mid tier cache and browser cache.
    24.      
    25. Log in to BMC Remedy Mid Tier and click the BMC Analytics for BSM link from the application list.
    26.     
      
    SW00449410Database

    When you access a Change Type object from the Change Management module within the universe and try to view the list of values or use this object in the report to view the data, the Change Request Type field does not display any values.

     8.1.00
    SW00451802Reporting

    When you open and refresh the out-of-the-box Change Management C10 - Forward Schedule of Tasks report, the report incorrectly displays the data, because it pulls the objects from the CIs Related To Tasks class and incorrectly pulls the CI ID from the CIs Related To Change Requests class instead of the CIs Related To Tasks class.

    7.6.06
    8.0.00
    8.1.00 
    8.1.00.01
    SW00451803UniverseWhen you import a BMC Remedy ITSM 7.6.06 universe, the Age of Incidents (minutes) variable calculates and displays results in months instead of minutes. 8.1.00
    SW00455438Universe

    Due to Daylight Saving Time, all the date objects for BMC Incident Management, BMC Change Management, and BMC Release Management in the BMC Remedy ITSM universe display an incorrect date.

     8.1.00
    SW00455799Reporting

    The value of the last row of the Summary tab in the P05 - Percentage of Problems for which Root Cause Analysis was Undertaken out-of-the-box report is displayed as ERROR#.

     8.1.00
    SW00455800Time zone

    (Russian time zone) When you log in to the InfoView or BI Launchpad and run any report using the Date object, the date and time parameters that are received from the BMC Remedy AR System database differ by one hour from the ones that are displayed on the user interface of the application.

     8.1.00
    SW00456201Universe

    When you open the BMC Remedy ITSM universe, under Change Management or Change Lifecycle Dates, the Target Date object and the related trend-based Dimension objects are missing.

     8.1.00
    SW00457390Universe

    The status of the Open Requests condition in the BMC Service Request Management section of the BMC Remedy ITSM universe is spelled incorrectly.

     8.1.00
    SW00457652Reporting

    Some of the BMC Atrium CMDB reports display the results of the Days Since Last Scan object as "Unknown" instead of the number of days.

     8.1.00
    SW00458374Reporting

    The Date objects (for example, Today, Yesterday, Tomorrow, and so on) under Reporting Objects returns incorrect data for the Oracle database when the database server time is set to GMT.

     8.1.00
    SW00458740Reporting

    When you use the Remaining life of VM in days object in any report, the date values are displayed as negative values instead of positive values.

     8.1.00
    SW00458824Reporting

    Under the following conditions, a custom report displays Configuration Item (CI) names multiple times instead of only once:

          
           
    • Create a custom report using objects the following objects:        
               
      • Incident ID (Service Desk > Incident Management > Incident)
      •        
      • CI NameCI ID, and so on (Service Desk > Incident Management > Incident > Incident Management Relationships > CI Items Related to Incidents)
      •       
    •      
    • Verify the results with front-end values
    •      
    • A CI name is associated with two or more dataset IDs that use the same CI name.
    •     

    Workaround:

    For BMC Remedy AR System version 7.6.04 SPx:

    Use the following procedure to add a new DATASETID object into report:

          
           
    1. Log onto the SAP BusinessObjects BI Lauchpad application and open the existing report in Modify mode.
    2.      
    3. Navigate to BMC Analytics for BSM > Service Desk > Incident Management > Incident > Incident Management Relationships > CI Items Related To Incidents.
    4.      
    5. Double-click the Dataset ID object, drag it into the Query Filters section, and set it to BMC.ASSET or required Dataset ID.
    6.      
    7. Click Run Query and validate the results.
    8.     

    For BMC Remedy AR System version 8.0 and later

    Use the following procedure to create a new DATASETID object from the AST_CI_UNAVAILABILITY_CI_JOIN view:

          
           
    1. Log on to the Universe Designer tool and import the BSM ITSM universe.
    2.      
    3. Navigate to BMC Analytics for BSM > Service Desk > Incident Management > Incident > Incident Management Relationships > CI Unavailability Related To Incident Requests.
    4.      
    5. Create a new Dataset ID object with the data type as character and the definition as IM_REL_CI_UNAVAILABLITY.Data_Set_ID.
    6.      
    7. Save and export the BMC ITSM universe.
    8.      
    9. Log onto the SAP BusinessObjects BI Lauchpad application and open the existing report in Modify mode.
    10.      
    11. Navigate to BMC Analytics for BSM > Service Desk > Incident Management > Incident > Incident Management Relationships > CI Items Related To Incidents.
    12.      
    13. Double-click the Dataset ID object, drag it into the Query Filters section, and set it to BMC.ASSET or required Dataset ID.
    14.      
    15. Click Run Query and validate the results. 
    16.     
      
    SW00459184Reporting

    In the I18 - Top Requestor Sites out-of-the-box report, "Incidents" is spelled incorrectly as "Incidence".

     8.1.00
    SW00460465Reporting

    The Cost object under BMC Analytics > Asset Management > Asset Information > Asset Financials > Asset Costs in the universe returns an incorrect value in the reports.

     8.1.00
    SW00460681ReportingWhen you create a report with the CI Name object, the report displays the CI names even though they have been removed from the BMC Remedy Mid Tier. 8.1.00
    SW00462609Reporting

    When you create any report related to BMC Incident Management, because the Relationship Type object refers to an incorrect field, incorrect data is displayed in the report.

     8.1.00
    SW00462867Reporting

    The Company Filter object in the C19 - Trend in Number of Change Requests out-of-the-box report incorrectly fetches data from the back-end table.

     8.1.00
    SW00462906Universe

    In the BMC Remedy ITSM universe, under Asset Management > Asset Information > Asset Relationships > Assets Related To Assets, the Relationship Name object displays values in all languages instead of just the selected language.

     8.1.00
    SW00463815Reporting

    The Problem Closed On Date object displays incorrect results when used in reports.

     8.1.00
    SW00464151ReportingThe I25 - Percentage of Incidents Resolved Within Stated Timeframe (SLA) out-of-the-box report displays incorrect data when the SLA resolution is met, that is, when the percentage count goes beyond 100%. 8.1.00
    SW00464236Work Order objects

    The Request Assignee and Request Manager objects that refer to the Work Order do not get parsed in the BMC Remedy AR System database, and error messages are displayed.

     8.1.00

    SW00464271

    SW00464361

     

    When the BMC Analytics for BSM 8.1.00 out-of-the-box universe points to the BMC Remedy AR System 8.1 database, because the BMC_CORE_BMC_COMPUTERSYSTEM view does not contain the DIMENSION column, the universe-derived BMC_CORE_BMC_VIRTUAL_SYSTEMS table that refers to this column displays the following error message:

    Exception: DBD, ORA-00904 “BMC_CORE_BMC_COMPUTERSYSTEM".
    "DIMENSIONS": invalid identifier.

    Additionally, some out-of-the-box BMC Atrium CMDB reports are also affected and display errors when you try to refresh them.

    Workaround: Manually delete the DIMENSION object from the BMC Analytics for BSM universe and report, because in BMC Atrium CMDB version 8.0 or later, the DIMENSION column has been removed from the BMC_CORE_BMC_COMPUTERSYSTEM view and form.

      
    SW00464725Reporting objects

    When you use the Current Month object from the Reporting Objects class along with the Lifecycle Date objects and use 'Incident Reported Date - Month of Year' as a query filter in the report, the report displays the data for the previous year and the current year instead of only the current year.

    Workaround: Use the 'Incident Reported Date - Month of Year = Current Month' AND 'Incident Reported Date - Year = Current Year' query.

      
    SW00465170Overlays

    The following process results in an incorrect display of records in a report:

          
           
    1. Create a view overlay on the HPD_HELP_DESK form, go to the field properties section of the Reported_Source field, change the alias value from BMC Impact Manager Event to Monitor, and then save the changes and the form.
    2.      
    3. Log in to the ITSM database and execute the ANA_POPULATE_ENUMS procedure using the following command:
      BEGIN PKG_ANA_POPULATE_ENUMS.ANA_POPULATE_ENUMS(); END;
    4.      
    5. Create an ad hoc report with Incident ID and Reported Source as source objects.
    6.     

    The report incorrectly displays two records for the same incident ID: one for the BMC Impact Manager Event value and the other for the Monitor value, instead of displaying only one record for the Monitor value only.

     8.1.00.01
    SW00465510Universe

    (For Oracle database only) When you use the Enter/Select Change Timing filter (under Change Classification subclass) in any report or try to parse this filter in the universe, an invalid prompt definition error is displayed when you run any report that uses that filter.

     8.1.00
    SW00467913Reporting

    (For Oracle and Microsoft SQL databases) The reports display incorrect data because the Problem Completed Date object in the universe fetches the date on which the workaround was entered instead of the date on which the problem was completed.

    7.6.06
    8.0.00
    8.1.00 
    8.1.00.01
    SW00467979Denormalization procedures

    (For Oracle and Microsoft SQL databases) When you create Business Service models with Business Services at the leaf node, execute the denormalization procedures, and then run the BMC Atrium CMDB C02 - Business Services Supported by a CI and the C03 - Business Service Profile reports, no data is displayed in these reports, because the denormalization procedures do not record the parent relationship.

     8.1.00.01
    SW00467986Reporting

    (For Microsoft SQL database only) The C03 - Business Service Profile report runs for a particular business service and does not return any data.

     8.1.00.01
    SW00468912Reporting

    When you create an ad hoc report with objects for the BMC Incident Management module and a filter with the Company option, the list of companies takes a long time to display.

    7.6.06
    8.1.00 
    8.1.00.01
    SW00469435Views

    The Year column of the ANA_FISCAL_CALENDAR view populates the data for the current fiscal year instead of the calendar year.

    For example, if the calendar is loaded for one year from April 1, 2014 to March 31, 2015, the view incorrectly loads the calendar and updates the year to 2014 and the quarter as 2014 Q1 instead of updating the year to 2015 and the quarter to 2015 Q1.

    7.6.06
    8.1.00 
    8.1.00.01
    SW00469649Denormalization procedures

    When you execute the denormalization procedure, the procedure takes a long time to complete and sometimes stops responding.

    7.6.06
    8.1.00
    8.1.00.01
    SW00470660Reporting

    (For Oracle and Microsoft SQL databases) When you insert the Number of Incidents Resolved at First Time object from the Service Desk, KPI Measures, or the BMC Incident Management metrics class into a report, the incidents that are marked as Resolved, Cancelled, or Closed are not reopened, because they are not recorded in the report.

    7.6.06
    8.0.00
    8.1.00 
    8.1.00.01
    SW00470942Error message

    When you log in to the BI Launchpad with a user who does not exist in SAP BusinessObjects, the following error message with a spelling mistake is displayed:

    Unable to login to SAP BusinessObjects BI Platform. Check if the user exists in SAP BusinessObjects BI Platform server or If your SAP BusinessObjects  Server license is valid and not expired. Refer to excpetion below for more details.
    Exception: Enterprise authentication could not log you on. Please make sure your logon information is correct. (FWB 00008)
    7.6.06
    8.1.00 
    8.1.00.01
    SW00471784Reporting

    (For Oracle and Microsoft SQL databases) When you create a report with BMC Incident Management objects and related BMC Incident Management, BMC Problem Management, and BMC Change Management objects with enum fields (used for more than one module), the data is not displayed.

    8.1.00 8.1.00.01
    SW00475070Reporting

    (For Oracle and Microsoft SQL databases) When you select the All option instead of selecting all the objects individually while filtering a query in the report, no data is displayed in the report.

    7.6.06
    8.0.00
    8.1.00 
    8.1.00.01
    SW00484442Reporting

    When you run the I27 - SLA Performance Summary by Group report, SLA Met Percentage is displayed as more than 100%, because the report incorrectly calculates No. of Incidents with Attached SLAs as greater than Total Incidents.

    7.6.06

    8.1.00 

    8.1.00.01
    SW00486177Reporting

    When you create a report with the customer satisfaction survey objects (Survey IDSurvey Status, and so on) together with the BMC Incident Management objects (for example, Incident ID) from the BMC ITSM out-of-the-box Universe, no data is displayed.

    7.6.06
    8.1.00 
    8.1.00.01
    SW00487542Objects

    The following objects from BMC Atrium CMDB and BMC Asset Management classes under Operating System display numbers instead of character values:

          
           
    • License Type
    •     
          
           
    • Product Type
    •     
          
           
    • OS Product Suite
    •     
          
           
    • OS Type
    •     
          
           
    • PAE Enabled
    •     
    7.6.06
    8.1.00 
    8.1.00.01
      
      

    Known and corrected issues for BMC Analytics for BSM version 8.1.00 RoD 2014.01 release only

                                                                                                                                                                                                                                                                                                  

    Defect ID

    Category

    Description

    Affected versions

    Corrected in

    Defect ID

    Category

    Description

    Affected versions

    Corrected in

    SW00436334 

    When you log in as a BMC Analytics for BSM user and allow either the SSO Max Session or the SSO Max IDLE timeout to expire, and then click any link, you do not have to provide the authentication details again.

    Workaround: Manually log off from the InfoView or BI Launchpad.

      
    SW00448752 

    While adding a tenant, if you do not have the BMC Remedy AR System schema for a particular module or product, the following exception occurs in the SAP BusinessObjects multitenancy log file:

    Error occurred while updating  webi document <ReportName>, detailed error message is  Database error: [Microsoft OLE DB Provider  for SQL Server] :  Invalid object name  '<DatabaseTableName/ColumnName> '.. (IES 10901)]}
     8.1.00
    SW00449449 

    When you upgrade from any older BMC Analytics for BSM version to version 7.6.06, the VIP and Case Sensitivity objects are incorrectly displayed in the universe. Because of this, when you create any report that uses these objects, the values for these fields are blank.

     8.1.00
    SW00452199 

    While refreshing reports in the InfoView or BI Launchpad, the following error message is displayed:

    An internal error occured  while calling  'processDPCommandsEx' API. (Error:ERR_WIS_30270)
     8.1.00
    SW00458167 

    When you deploy the Apache Tomcat server on the first instance of BMC Analytics for BSM in a clustered environment and integrate BMC Analytics for BSM with BMC Atrium SSO, the procedure is successful. However, when you deploy the Tomcat server on a second instance of BMC Analytics for BSM and integrate with BMC Atrium Single Sign-On, this integration fails and BMC Atrium Single Sign-On does not send session notifications to the Tomcat server.

      
    SW00465420 

    When you install BMC Analytics for BSM 8.1.00 in a multitenant environment, add a tenant, run the installer again, and select BMC Atrium Single Sign-On authentication, the installation fails with the following error:

    SSO for selected tenant is already configured.
      
      
      

     


    Article Number:

    000131303


    Article Type:

    FAQ/Procedural



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