Impact of Mongo Db 3.4 version End of Life on BMC Remedy Digital Workplace and Remedy with Smart IT.

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:

    Remedy with Smart IT


    COMPONENT:

    Remedy with Smart IT


    APPLIES TO:

    Smart IT 1.5, Smart IT 1.6, Smart IT 2.0, DWP 3.3.02, DWP 3.4, DWP 3.5, DWP 18.02



    QUESTION:

    Problem Summary # Impact of Mongo Db 3.4 version End of Life on BMC Remedy Digital Workplace and Remedy with Smart IT. Is BMC Supporting Mongo 3.6 with DWP and Smart IT versions?

    Mongo Db 3.4 version support ends on Jan 2020.

    MongoDB Server                                                                                                                                                                                      
    ReleaseRelease DateEnd of Life Date
    MongoDB 3.0March 2015February 2018
    MongoDB 3.2December 2015September 2018
    MongoDB 3.4November 2016January 2020
    MongoDB 3.6November 2017TBD
    MongoDB 4.0June 2018TBD


    ANSWER:

    What has Changed in Mongo 3.6

    Mongo 3.6 compatibility 
    states that array indexing has been changed to nested, and once upgraded to 3.6, array type indexes need to be rebuilt. If the indexes are not rebuilt, new records will not be inserted.
     
    Additionally, there are changes in sort behavior and the find method.
     
    Ref:
    https://docs.mongodb.com/manual/release-notes/3.6-compatibility/
    If upgrading from a MongoDB 3.4.x deployment that has partial indexes whose partialFilterExpressionincludes a $type : "array" or $type : 4 expression, you must rebuild these indexes after upgrading to avoid conflicting $type : 'array' semantics.
    For more information on the $type: "array" expression, see Querying by Array Type.
    +
    Array Sort Behavior
    Starting in 3.6, when sorting a field containing an array, MongoDB orders the field with the lowest-valued element of the array first for ascending sorts and the highest-valued element of the array first for descending sorts. A sort no longer takes the query predicate into account when choosing the array element which will act as the sort key. This behavior change applies to both the find command and the aggregation pipeline.
    IMPORTANT
    As a result of changes to sorting behavior on array fields in MongoDB 3.6, when sorting on an array indexed with a multikey index the query plan includes a blocking SORT stage. The new sorting behavior may negatively impact performance.
    In a blocking SORT, all input must be consumed by the sort step before it can produce output. In a non-blocking, or indexed sort, the sort step scans the index to produce results in the requested order.
     
    +
     
    find Method Sorting
    A sort key is the array element MongoDB uses during the sorting process to compare and ultimately order documents containing an array. In an ascending sort, documents containing arrays with the lowest-valued sort keys are ordered first. Likewise, in a descending sort, documents containing arrays with the highest-valued sort keys are ordered first.
    In MongoDB 3.4 and earlier, a sort by an array field took into account the query predicate when determining the sort key.

    Solution # 
    BMC Digital Workplace -
    Customer using older version of MyIT/DWP 3.3, 3.3.02, 3.4, 3.5 and 18.02
    Action # Please upgrade to latest version of Digital Workplace ( DWP 19.02 or at a minimum DWP 18.05 ), If you are currently on ITSM 9.1 Stack, you do not need to upgrade ITSM version for the Digital Workplace 19.02 Upgrade. With DWP 18.05 and later versions, You no longer needed a Mongo Db. Please refer documentation - https://docs.bmc.com/docs/display/dwpadvcurr/Upgrading+BMC+Digital+Workplace

    BMC Remedy with Smart IT - Customer using older version of Smart IT 1.5, Smart IT 1.5.01, Smart IT 1.6 and Smart IT 2.0
    Action # Please upgrade to latest version of Smart IT  ( Smart IT 19.02 or at a minimum Smart IT 18.05 ). If you are on ITSM 9.1 stack, you will also need to upgrade the ITSM version to 19.02. With Smart IT18.05 and later versions, You no longer needed a Mongo Db.
                 
    Note:  Short term solution is customers can stay on Mongo 3.4 at their own risk until they upgrade to later version of DWP and Smart IT.


    Article Number:

    000167104


    Article Type:

    FAQ/Procedural



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