Wednesday 9 March 2011

Solution to Common issues with controlM server.

In this post I have tried to provide a solution to common issues faced by system administrators with contolM server.I will try to give a basic solution for the problems generally faced not each and every one and are in particular reference to system admins only.

Q1. How to upgrade ControlM Server and ControlM EM server?
Ans.It's not an easy task to upgrade controlm and EM server.First we need to take a dump of the database to have all the previous information then we need to stop the server then database then upgrade it obviously jobs needs to be on hold for that but its a very heavy exercise and should be avoided by you until you are experienced with it.

Q2. How to install and upgrade ControlM Agent?
Ans. Installing controlm agent is simple and menu driven just download the set up and install it.Now a days with new version of 6.4 agent gets installed automatically when server gets installed,however in previous versions you needed to install it seprately.
Upgrading a controlM agent is a simple task.You just need to download the updates from the net and then install them on the agent from the installation directory folder under controlm agent folder.The installation is simply menu driven simple next next types.

Q3. How to restart ControlM agent?
Ans.Go to the home directory of your controlm user,then go to ctm directory and in that go to scripts directory so if your control agent user is ctmu then go to /home/ctmu/ctm/scripts
there you will find two scripts start-ag for starting the agent and stop-ag for stopping the agent.So to restart or stopping the agent just issue start-ag or stop-ag in scripts folder if your environment variable are not set.
Log files for above would be formed in /home/ctmu/proclog.

Q4. How to enter the controlM server database?
Ans.Since controlM is not such a big application that we need separate database team to look after it generally admins only look after it.I am gonna describe about postgre database here only.So to enter database on controlm server just enter sql its a shortcut to enter database.Else issue command
psql -u username -p passowrd.

Q5.How to check connectivity between server and client.
Ans.To know the status of any agent from server we will issue   ctm_diag_comm <name of agent machine>
From Agent to server connectivity we issue.    ag-diag-comm no control me server name needed because one agent gets connected to one server only whose name we define at the time of installation.
These commands do two level of pinging one unix level ping and one controlm server level swing which take ports into account as well.So if your agent becomes unavailable then first check with unix level ping which is normal ping if that comes as fine then check for the agent to server port and server to agent port.So above commands can be used to look for connectivity or agent becoming unavailable issues.Also check if naming services are on.

Q6.How to stop and start the database?
Ans.Look for the proper script in script folder like check_all to display overall health
start-all and stop-all to start and stop server plus database while start-server and stop-server for stoping and starting server only not database.

Q7.How to configure database and check mirroring of database.
Ans.check_mirror is the command to check if mirroring is abled or disabled.However to set the mirroring use ctm_menu.To check the configuration file in case of postgre database go to /home/controlmuser/pgsql/data and edit postgresql.conf.To check database log go to pmg-log directory.

Other useful commands are:
ctmrpln-->run from controlm user used in case of mismatching of scheduling between EM server and controlM server.
ctmpsm-->Listing jobs and menu for all kind of work that can be done from EM server.Used in case of outage on EM server and from mainframes to handle jobs.

So these are some of the common questions and useful commands that come in handy while handling controlM server.

No comments:

Post a Comment