OEM 13c - Managing agent with Gold Image using command Line

This blogpost will list down steps to manage and create an gold image with OEM 13(available in previous version of OEM versions as well). 


Step1: Login to OEM emcli and perform the sync with repository

emcli login -username=<oem username>

emcli sync


Step2: Next step is to create the gold image and a image version. Before this we have to prepare an agent which needed to be used as a gold copy and rest all agents will use same version of plugins. We assume with in this blog source agent is already prepared.

emcli create_gold_agent_image -image_name="<image name>" -version_name="<version name>" -source_agent="<source agent with port"> -gold_image_description="<Description>"


Step3: Once gold images and it's version is created and we decided to use it. The version needs to be marked as current and then only we can use it for agent upgrades.

emcli promote_gold_agent_image -version_name=<version name> -maturity=Current


Step4: Next step is to subscribe the agent which needs to be managed through this gold image and upgrade similar to it's source agent.

emcli subscribe_agents -image_name="<Image Name>" -agents="agent1,agent2,..."


Step5: Once agent is subscribed it's now ready to be upgrade using following verb

emcli update_agents -version_name="<version name>" -agents="agent1,agent2,..." -stage_location="<staging location>

Make sure you don't use /tmp as staging location as this file size can be big and if /tmp for the machine is filled, it can cause outage on your server.


This concludes the steps to create an gold image and updates the agents to it. There are some important commands to list down various properties:

emcli list_gold_agent_images (List gold image)

emcli list_gold_agent_imageversions -image_name=<image name> (List of gold image versions)

emcli list_gold_image_subscribed_agent -image_name=<image name>

emcli get_updatable_agents -version_name="<version name>"

emcli get_not_updatable_agents -version_name="<version name>"

emcli list_agents_on_gold_image -version="<version name>"


Comments

Post a Comment

Popular posts from this blog

How to Solve - "WAIT FOR EMON PROCESS NTFNS"

Event Monitor Process in short called as EMON is generally used by oracle to send notification. Often applications uses Database Change Notification process also called as DBCN to be aware of changes in the database, based on these notifications they take further actions. Often clients subscribe to the database and notifications are send as callback to them. In some cases you will notice database sessions are showing wait event "WAIT FOR EMON PROCESS NTFNS" and it can even make your database un-responsive. One observation can be these processes are taking more CPU (may not in be in all cases). As stated EMON process deals with database notification and it's spawn and gets down itself and Administrators have no control on theses processes. Anyone can go through oracle documents to read more EMON functioning process.  EMON uses oracle advanced queues and database queue notifications into them and EMON process these notifications to clients based on their subscriptions. In s
Read more

Query Regression - "OR" Transformation Oracle 19c

Recently while upgrading Oracle Database from version 12.1 to 19.10 found there were couple of queries which was running slow post upgrade. Usually these type of behavior is seen while upgrading to newer version and oracle provide various ways to fix them. The difference between good and bad plan was an introduction of  "MERGE JOIN CARTESIAN" (aka MJC) and that's in where regressed query in 19c taking most of the time. MJC sometimes works for queries but in this case it was clearly not helping.  We had following options here:     1. Copy the profile from 12c to 19c database and it worked, but the problem was not just to specific query but with many similar query. This means profile option is not very attractive in this case.     2. We also tried running query with OFE 12.1 to use the same optimizer features as previous version and query behaves well. Though this option can't be placed as we need to use 19c OFE and can be placed only for testing purpose.           alte
Read more

ORA - 12537: TNS: connection closed

Often when active clone to be done to create a new environment, we land up into couple of issues. I will discuss about one issues during this process. Action : Create a new database on different machine from a source. Error : ORA - 12537: TNS: connection closed In order to duplicate the environment was using below rman log /tmp/duplicate.log connect target sys/<password>@<source tns alias> connect auxiliary sys/<password>@<target tns alias> run{ allocate channel ch1 device type disk; allocate channel ch2 device type disk; allocate channel ch3 device type disk; allocate channel ch4 device type disk; allocate auxiliary channel ax1 device type disk; allocate auxiliary channel ax2 device type disk; allocate auxiliary channel ax3 device type disk; allocate auxiliary channel ax4 device type disk; DUPLICATE TARGET DATABASE TO <TARGET_DBNAME> FROM ACTIVE DATABASE NOFILENAMECHECK; } While making connection to Auxiliary database received mentioned error ORA - 12537:
Read more