Managing Oracle OEM Gold Images for Agent Standardization

 Oracle Enterprise Manager (OEM) provides the Gold Image feature to simplify large-scale agent management and standardization. Using Gold Images, administrators can maintain a consistent agent configuration, plugin set, and patch level across multiple servers.

This feature is available in OEM 13c and was also present in earlier OEM releases with similar functionality.

In this article, we will walk through the process of creating, managing, and deploying a Gold Agent Image using emcli.

Why Use Gold Images?

Gold Images help standardize OEM agents across environments by allowing administrators to:

  • Maintain consistent plugin versions
  • Simplify agent patching and upgrades
  • Reduce manual configuration drift
  • Automate large-scale agent deployments
  • Ensure uniform monitoring behavior

Instead of patching every agent individually, administrators can prepare one reference agent and use it as the baseline for all other agents.

Step 1: Login to EMCLI and Synchronize

Before performing any Gold Image operations, log in to emcli and synchronize it with the OEM repository.

emcli login -username=<oem username>

emcli sync

The sync operation ensures that the local EMCLI metadata is updated with the OEM repository.

Step 2: Create the Gold Agent Image

The next step is to create the Gold Image along with its image version.

Before doing this, prepare a reference agent that will act as the source or master copy. This source agent should already contain the required plugins, patches, and configurations that you want all target agents to inherit.

Once the source agent is ready, execute the following command:

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

Example:

emcli create_gold_agent_image \
-image_name="Linux_Agent_Gold_Image" \
-version_name="v1" \
-source_agent="host01.example.com:3872" \
-gold_image_description="Baseline OEM agent image for Linux servers"

Step 3: Promote the Gold Image Version

After creating the image version, it must be promoted to Current status before it can be used for agent upgrades.

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

Example:

emcli promote_gold_agent_image \
-version_name=v1 \
-maturity=Current

Only Gold Image versions marked as Current are eligible for deployment and upgrades.

Step 4: Subscribe Agents to the Gold Image

Once the image is ready, subscribe the target agents that should be managed using this Gold Image.

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

Example:

emcli subscribe_agents \
-image_name="Linux_Agent_Gold_Image" \
-agents="server01:3872,server02:3872"

After subscription, these agents become associated with the Gold Image lifecycle.

Step 5: Upgrade Agents Using the Gold Image

Now the subscribed agents can be upgraded using the Gold Image version.

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

Example:

emcli update_agents \
-version_name="v1" \
-agents="server01:3872,server02:3872" \
-stage_location="/u01/oem_stage"

Important Recommendation

Avoid using /tmp as the staging location.

Gold Image files can become quite large, and filling up /tmp may lead to unexpected server issues or outages. Always use a filesystem with sufficient free space.

Useful EMCLI Commands for Gold Image Management

Below are some additional commands that are helpful while managing Gold Images.

List Available Gold Images

emcli list_gold_agent_images

List Gold Image Versions

emcli list_gold_agent_imageversions \
-image_name=<image name>

List Agents Subscribed to a Gold Image

emcli list_gold_image_subscribed_agent \
-image_name=<image name>

List Agents Eligible for Upgrade

emcli get_updatable_agents \
-version_name="<version name>"

List Agents That Cannot Be Upgraded

emcli get_not_updatable_agents \
-version_name="<version name>"

List Agents Running on a Specific Gold Image Version

emcli list_agents_on_gold_image \
-version="<version name>"

Final Thoughts

Gold Images in Oracle OEM provide an efficient and scalable way to standardize agent deployments across enterprise environments.

By maintaining a well-prepared source agent and managing upgrades centrally through Gold Images, administrators can significantly reduce operational overhead and improve consistency across monitored systems.

For larger environments managing hundreds of OEM agents, this approach becomes especially valuable for lifecycle management, compliance, and automation.

Comments

Post a Comment

Popular posts from this blog

Upgrading to Oracle 23ai: A Step-by-Step Guide to Oracle's Next-Gen Database

Oracle has raised the bar once again with the release of Oracle Database 23ai , a forward-looking evolution of its flagship database platform. Formerly referred to as Oracle 23c, the "ai" suffix underscores Oracle's pivot toward AI-integrated capabilities —bringing new levels of automation, data management, and performance enhancements. In this blog, I’ll walk you through what’s new in Oracle 23ai and how to safely upgrade your existing Oracle database to this powerful new version. What is Oracle 23ai? Oracle 23ai is the long-term support (LTS) release in Oracle’s database lineup. It introduces groundbreaking features designed for developers, data scientists, and DBAs. Key highlights include: AI Vector Search and Embedding Support : Designed for AI/ML and LLM apps. JSON Relational Duality Views : Bridge relational and document models seamlessly. SQL Domains and Property Graphs Enhancements Automatic Index Optimization Improved In-Memory Features and M...
Read more

Initial Load - Instantiation - Oracle Golden Gate using Datapump

Full database export using expdp Enable Minimal Supplemental Logging in Oracle on source alter database add supplemental log data ; Enable Supplemental Logging at Table Level on source GGSCI> dblogin userid xxxxx password xxxxxx GGSCI> add trandata <schema>.<tablename> Add Extract, Add Exttrail, Add Pump, Add Rmttrail on source Start Extract, Start Pump on source Create a database directory: SQLPLUS> create directory dumpdir as '<some directory>' ; Get the current SCN on the source database:  SQLPLUS> select current_scn from v$database ;  28318029 Run the Data Pump Export using the flashback SCN you obtained in the previous step. The following example shows running the expdp utility at a Degree Of Parallelism (DOP) of 4. If you have sufficient system resources (CPU, memory and IO) then running at a higher DOP will decrease the amount of time it takes to take the export (up to 4x for a DOP of 4). Note that expdp uses Oracle Database parallel execut...
Read more

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