CL 5.7 and 6.0

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf CL 5.7 and 6.0

  • Creator
    Topic
  • #53750
    Mike Campbell
    Participant

      Here is a fun one for all.

      Current production is 5.7 patch 2 on AIX.

      Working at converting to 6.0 on AIX, on the same box.  

      The initial threads to convert are the ‘batch’ ones, that process a single file.

      The shell scripts issue a stop and start on the threads needed.

      The problem is the HCIROOT.  

      Is there any way to change from the 5.7 to 6.0 and then back again to avoid affecting the existing 5.7 threads?

      I can manually copy the /etc/environment file for 6.0 or 5.7, but you have to be ‘root’ to do that.  

      Any ideas?

      Thanks.

      Mike C.

    Viewing 1 reply thread
    • Author
      Replies
      • #78827
        Russ Ross
        Participant

          We use AIX LPARS too and rather than figure out a problem that does not need to even exist I will share how we have upgraded from Cloverleaf 5.6 to 6.0.

          Using P7 LPARs is nice becuase upgrading in place is not necessary for us to deal with such greif anymore.

          I hope I never go back to upgrading in place on the same box and encourage you to consider doing the same.

          We are on AIX too and create a fresh LPAR from scratch and then do NFS read only mount of older cloverleaf filesystem to new cloverleaf LPAR.

          This way neither environment can harm the other.

          I bridge the gap from Cloverleaf 5.6 to Cloverleaf 6.0 with a symbolic link something like this so hcirootcopy will work:

          In my /cloverleaf directory the scrtach install creates a 6.0 directory then in the /cloverleaf directory I manually created this symbolic link

          qdx5.6 -> /nfs/mdahub8sna/upgrade/cloverleaf/qdx5.6

          This way I can run my cloverleaf 5.6 stuff on my cloverleaf 5.6 LPAR during transitional upgrading of my numerous sites until completely moved over to cloverleaf 6.0.

          This solves all the stress and headaches that comes with upgrading in place.

          Different OS, security patches, JAVA, HA, SNA, HCIROOT, whatever no problem.

          It is so easy for things to go wrong when upgrading in place and not even know it sometimes and all the versions of this conflicting with that are an unecessary pain that can be completely avoided with this approach.

          Russ Ross
          RussRoss318@gmail.com

        • #78828
          John Mercogliano
          Participant

            Hi Mike,

            John Mercogliano
            Sentara Healthcare
            Hampton Roads, VA

        Viewing 1 reply thread
        • The forum ‘Cloverleaf’ is closed to new topics and replies.