5 Replies Latest reply on Apr 6, 2012 3:56 AM by Pierre_Michael DESHAYES

    upgrade our Control-M version to 7. ASAP

      Hi Team,

      Hope you guys doing good.

      We are planning to upgrade our Control-M version to 7. ASAP.( current version -6.3 )

      So in order to upgrade Control-M, Here I would like to test/know some points before.

      I would like to take advantage of thisto  install/test the latest release of Control M (release 7) on the development server, , and create a project plan for the implementation. This will accomplish a few things, first it will verify all the procedures and changes needed to successfully upgrade to the new release, second this will give me more exposure/experience with UNIX to help build your technical knowledge and finally it help me establish partnerships with the Oracle DBA’s which is key for future activities.

      after product download from where i can start..the first step..

      Just FYI-- on the machine where i want to insttal this new version..there is already insttaled control-m version 6.3 using oracle database.. and i dont want to remove that one. want to test new one simoultenously..

      Please help..

        • 1. upgrade our Control-M version to 7. ASAP

          There's a program within BMC called the Amigo program.  If you call support and ask for an Amigo for your upgrade, they will set you up with a person who can help you plan your upgrade path. I think it sounds like you should do this as your first step.

          • 2. upgrade our Control-M version to 7. ASAP

            Thanks laurie,


            I know this Amigo program..


            But I've to do it by own on my Test server and test few jobs on this new version.


            So that we can easily finalize whether we go on new version or not.



            • 3. upgrade our Control-M version to 7. ASAP
              Robert Stinnett

              My advice:


              1)  Setup a virtual machine - or ask your VM guys for one.  Don't try to install 7.0 on top of 6.3. 


              2) Install the software ( you can put all the components on that one VM ) and then use it as your sandbox.


              3) Export data (you can do this with the system up) from 6.3 and go through the conversion process and use that as "test" data in the 7.0 environment.  You can even do subsets of data if you have a particularly big environment.


              4)  Based on your comfort level there then begin your upgrade plans.



              I can't stress the fact enough to always have a sandbox.  Development should be for development -- not for trying to test out new versions of the software on :-)



              • 4. upgrade our Control-M version to 7. ASAP

                Before starting EM-7 installation, I had run check_req.sh but I'm getting below error.


                Under dir

                drwxr-xr-x 2 372 328 15 Feb 7 2011 pre_req
                -rwxrwxrwx 1 opergpc staff 48146 Apr 5 04:23 pre_req.tar.Z


                # cd pre_req
                # ls -lrt
                total 251
                -r--r--r-- 1 372 328 44 Oct 2 2007 os_pre_sybase.txt
                -r-xr-xr-x 1 372 328 219 Nov 7 2007 kernelCheck10
                -r--r--r-- 1 372 328 1522 Oct 20 2009 os_pre_ctm.txt
                -rwxr-xr-x 1 372 328 780 Nov 26 2009 awk_test.sh
                -r--r--r-- 1 372 328 14054 Dec 9 2009 check_req_oracle_db.sql
                -r-xr-xr-x 1 372 328 77 May 12 2010 run_limit.sh
                -r-xr-xr-x 1 372 328 341 May 26 2010 get_prctl_result.sh
                -r--r--r-- 1 372 328 4320 May 26 2010 os_pre_postgresql.txt
                -r-xr-xr-x 1 372 328 11485 Jun 20 2010 patch_check.sh
                -r--r--r-- 1 372 328 1920 Jan 3 2011 os_supported.txt
                -rwxr-xr-x 1 372 328 80105 Jan 25 2011 check_req.sh
                -rw-r--r-- 1 372 328 3126 Feb 3 2011 os_pre_em.txt
                -r--r--r-- 1 372 328 129 Feb 7 2011 LAST_CONTENT.TXT




                After test result as below..

                Take into account - "ulimit" limitations where checked for user 372

                Operating System prerequisite check was not successful !!!


                The operating system prerequisites check detected that patches, packages,
                or kernel parameters may be incomplete (see list below).
                Ask your system administrator to verify that all kernel parameters are defined
                as required, and that required patches and packages have either been installed
                or have been replaced by a superseding one.
                You are recommended to rerun the prerequisites check after making any changes
                to the system.

                Patches check results :

                Following OS_patches have to be installed:

                119963-18 - Shared library patch for C++

                OS updates check results :

                Passed Ok.

                OS subversion check results :

                Passed Ok.

                Check was performed on [sun1039]: Solaris 2.10 64 bit computer.
                Control-M product components version 7.0.00 with Oracle cannot be installed
                due to missing prerequisites.
                Please contact your system administrator with the messages above.


                # ./run_limit.sh

                # ./awk_test.sh
                flag set to 1

                N;U:2;SuSE 10 Update level 2


                # ./patch_check.sh
                patch/package/Update level((or subversion) [] or a supersedes patch/package/Update level(or subversion) was not found in your system.
                # patch_check.sh
                patch_check.sh: not found




                • 5. upgrade our Control-M version to 7. ASAP
                  Pierre_Michael DESHAYES

                  You have to install a patch on your Solaris 10 system, patch 119963 to be precise. Ask your system administrator to perform this action.


                  If you want to check which version you have, you can issue the following command:


                  $ showrev -p | grep 119963


                  The other messages can be ignored.