Start EM stack in the order:
1. The listener for the repository database
2. The repository database
3. Start the OMS and the Web Tier
Note: The "emctl start oms" command will start both the OMS and the Web Tier including WebLogic Admin server and the Node Manager.
4. Start the agent
Stop the stack in the reverse order, but use command "emctl stop oms -all" to stop the OMS and the Web Tier
The stop/start procedure is applicable whether the OMS and repository are on the same or separate machine.
For documentation, see chapter 24 of the Oracle Enterprise Manager Cloud Control Administrator's Guide.
Thank you for that. Here is another question.
The repository is on a seperate server thus shutdown/startup there is not an issue unless there is something I must do with the Webtier and OMS when restarting the repository. Is there or are those independant processes.
On the OMS server one of the processes I see is the rotatelog process. Will that be started as part of the web tier startup or must I start it independantly. I have seen examples showing the command -
Is it necessary to do that or will that shutdown/startup as part of the webtier/OMS shutdown/startup?
If you are bringing down the repository DB or performing any maintenance activity on it, you should ideally shutdown the OMS (including the webtier). Before starting the OMS, always verify that the Repository DB and its listener are up and running.
The rotatelog process is automatically started/stopped by the OHS and is responsible for regular rotation of the OHS logs.
Thank you. That means, if I am understanding corectly all I must do are start/stop the OMS and start/stop the agent in the proper order and all components will be properly stopped/started. Is that correct?
The OMS needs to connect to the repository database to function, so make sure the listener and the repository database are up before starting the OMS.
When to start the agent is not that critical. If the OMS is down when it is started, it will try to connect to the OMS later.
Thank you. One (hopefully) last question. From what you are saying it follows that if I shut down the repository for patching I should shut down the OMS during that period of time. Is that correct? What are the ramifications of leaving the OMS up if the repository is down? Will it cause problems or just numerous errors being logged?
If the Repository is down, the OMS will eventually crash and stop trying to reconnect. It requires the Repository to function.
Thank you all.
If the OEM repository is down OMS will try to reconnect when It's up again. At least that functionality work in the latest versions of EM12c.
It's worth looking at the startup script for 12c Cloud Control is : /etc/init.d/gcstartup
For more information kindly refer to the document : http://docs.oracle.com/cd/E24628_01/install.121/e24089/getstrtd_things_to_know.htm#EMADV12174
-- Kirill Loifman, dadbm.com
This is a part of my old script to do the same manually:
echo -n $"Starting $prog: "
su - $ORA_OWNER -c "$ORA_HOME/bin/lsnrctl start"
su - $ORA_OWNER -c "$ORA_HOME/bin/dbstart"
su - $ORA_OWNER -c "$AGENT_HOME/bin/emctl start agent"
su - $ORA_OWNER -c "$OMS_HOME/bin/emctl start oms"
echo -n $"Stopping $prog: "
su - $ORA_OWNER -c "$OMS_HOME/bin/emctl stop oms -all"
su - $ORA_OWNER -c "$AGENT_HOME/bin/emctl stop agent"
su - $ORA_OWNER -c "$ORA_HOME/bin/dbshut"
su - $ORA_OWNER -c "$ORA_HOME/bin/lsnrctl stop listener_ohegc"
-- Kirill Loifman
Please note, that additional component installs (BI Publisher, JVMD, etc) may have additional startup/shutdown pieces and should proceed the OMS shutdown, and follow OMS startup.
shutdown BI publisher
shutdown repository (if needed)
The agent generally doesn't have to be shutdown during OMS maintenance (except if instructed during EM upgrades), however if you enable out of band notifications or such, you may want to start a blackout on the agent if you're shutting down for a planned maintenance activity.