2 Replies Latest reply on Jul 31, 2020 10:14 PM by Bentze Perlmutter

    Steps from CTM for OS server reboot

      Share This:

      Hi,

       

      We have a Control-M prod setup with EM and Server on the same OS host (Linux). But, the oracle DB is on a different host.

       

      The Linux server which hosts our CTM application is scheduled for a reboot in the near future. I would like to understand the steps that have to be performed from Control-M to ensure a smooth shut down and resumption of services post reboot.

       

      Thanks in advance.

        • 1. Re: Steps from CTM for OS server reboot
          Markus Isert

          Moin,

           

          first we activate a "Workload Policies Definitions" that no Job is starting and running jobs can end.

          "Workload Policies Definitions" is set with:

          Filter:

          Job Name/Mem Name -> *

          Running Jobs: 0 <on Each> All Days,All Hours

           

          When no Jobs are running:

          on Console:

          1) ctm_menu -> Activation Menu -> STOP ALL

          2) root_menu -> Activation Menu -> STOP ALL

           

          Now all Server and EM components are stopped, and you are able to update your server and restart.

           

          Maybe your Server is set to start automaticly EM and CTM Server, you have to deactivate the "Workload Policies Definitions" and the sheduling will continued to run.

          Otherwise you have to start EM and Server with console first.

           

          Greetz

          Markus

          • 2. Re: Steps from CTM for OS server reboot
            Bentze Perlmutter

            Hi Varun,

             

            To stop/start Control-M via CLI, so you can use it in a script, the commands are:

             

            1. Stop Control-M/EM #run this as EM User

            em ctl -mcs -C Config_Agent -all -cmd shutdown # this stops Control-M/EM on all hosts where it runs, for example, HA Primary and Secondary and on Workload Archiving host too (but you need to stop PGSQL on Workload Archiving host, if that's the DB used for WA: arc DBUStop -FORCE N)

             

            2. Stop Control-M/Server (Secondary) #run this as CTM/Server User

            shut_ca

             

            3. Stop Control-M/Server (Primary) #run this as CTM/Server User

            shut_ca; shut_ctm

             

            4. Start Control-M/Server (Primary) #run this as CTM/Server User

            start_ctm; start_ca

             

            5. Start Control-M/Server (Secondary) #run this as CTM/Server User

            start_ca

             

            6. Start Control-M/EM (Primary) #run this as EM User

            start_config_agent

             

            7. Start Control-M/EM (Secondary) #run this as EM User

            start_config_agent

             

            8. If you have Workload Archiving you first start PGSQL DB (if it uses PGSQL) and then the Config Agent: #run this as EM User

            arc DBUStart

            start_config_agent

             

            9. Start Control-M/Agent, run this as root (if agent runs as root) or as agent-user (if agent runs as non-root):

            "<home of ctm/server>/ctm_agent/ctm/scripts/start-ag -u <ctm server user> -p ALL

             

            NOTE1: you can setup auto-stop/start for all Control-M components using Linux rc.d and/or systemd facilities.

            The documentation has the high-level commands but you would need to write the scripts: Control-M 9.0.19.200 Control-M Documentation - Control-M - BMC Documentation

             

            NOTE2: In case the Oracle host is being rebooted too, you need to ensure that:

            - Oracle is shutdown after Control-M applications are stopped

            - Oracle is started before Control-M applications are started

             

            Regards,

            Bentze