Skip to Content
avatar image
Former Member

Multiple nodes in 4.2 Upgrade

Hi,

We have a 2 node cluster in business objects, both nodes are on seperate servers. These point to the same database and use the same sid.

We are on 4.1 sp3.

Is it possible to patch node 1 to 4.2 and let users continue on node 2. Once node 1 is tested and signed off then patch node 2?

From the documentation I get the impression this is possible but wanted to check if anyone as done it.

Thanks in advance

Jim

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    avatar image
    Former Member
    Oct 21, 2016 at 02:01 PM

    Thanks Denis, that ans my question. Much appreciated.

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 20, 2016 at 04:25 PM

    Jim. Dont try to attempt that. If you are going for an upgrade always restrict users to access any of the clusters in the system.

    In order to upgrade the system you need to stop the all the services (Except CMS, IFRS & OFRS) in all your clusters. This is to avoid any discrepancy in between your CMS and your File store servers.

    Thanks

    Mani

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 20, 2016 at 06:57 PM

    you cannot upgrade just one node in a cluster and still use other node at previous patch level.
    You need to test upgrade on a test system first, then upgrade your prod cluster.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 21, 2016 at 11:02 AM

    Folks,

    Thanks for replying. No intention of running this in production without trying it in DEV environment first. Currently I have two CMS's and the only things shared are the FRS and database.

    I was under the impression you could do a rolling upgrade to minimize downtime.

    Thanks

    Jim

    Add comment
    10|10000 characters needed characters exceeded

    • One of the things that came up in the BI Platform Influence Council meeting this past week at the ASUG BI+A conference was that there are issues if you try to upgrade multiple CMS servers in a cluster at the same time. In talking with folks from product management (Maheshwar and others), they recommend that you upgrade one CMS first so that the database gets any needed updates from a single source. So, with two servers, you would have to upgrade them consecutively. You can upgrade multiple application servers at the same time, but you still need to upgrade one CMS server first and then you can upgrade any others in Parallel.

      -Dell