GOLD Image Creation IN OEM

 

🛠️ GOLD Image Creation 

Creating a standardized GOLD image for Oracle Grid Infrastructure and Database binaries is essential for maintaining consistency, simplifying patching, and ensuring compliance across production environments. This guide walks you through the process of setting up and generating a GOLD image using Oracle Enterprise Manager (OEM) on the GCP production server (OEM Server).

✅ Prerequisites

🖥️ Environment Setup

  • Login Server: OEM Server

  • Source Database Server: Test DB Server

  • Oracle Version: 19.22

  • Target Requirement: Database must be patched with version 19.22 before proceeding.

🔐 Credential Creation

In the OEM Console, create the following credentials:

  1. Normal Credential

    • Name: V2V_ORACLE_VM_LOGIN

    • User: oracle

  2. Privilege Credential

    • Name: GLOBAL_SUDO_TO_ROOT_VIA_ORACLE

    • User: oracle with sudo privileges to root

📸 Screenshot Placeholder:
🖼️ OEM Console → Setup → Security → Named Credentials
👉 Show creation screen of both credentials

📁 Step 1: Prepare Directories on Source DB Server

On the source server geetldbpl01, execute:

bash
CopyEdit
mkdir -p /ora01/app/dispatch
mkdir -p /ora01/app/stage

📸 Screenshot Placeholder:
🖼️ Terminal session showing directory creation

🧾 Step 2: Create Parameter and Input Files

Login to the GCO prod server (OEM Server) as oracle user.

🔧 Create a Working Directory

bash
CopyEdit
mkdir FPP
cd FPP

✍️ Create Parameter Files

bash
CopyEdit
vi grid1922_image.txt
vi DB1922_image.txt
chmod 755 *.txt

📸 Screenshot Placeholder:
🖼️ Terminal window showing ls -lrt of FPP directory after file creation

✍️ Create Input Deployment Files

bash
CopyEdit
vi input_deploy_grid1922.txt
vi input_deploy_db1922.txt
chmod 755 *.txt

📸 Screenshot Placeholder:
🖼️ Final file listing with permissions shown via ls -lrt

📄 Step 3: Parameter File Contents

grid1922_image.txt

ini
CopyEdit
IMAGE_NAME=GRID922
IMAGE_DESCRIPTION=GRID PSU
REF_TARGET_NAME=OraHome1_4_Test DB Server_8731
IMAGE_SWLIB_LOC=FPPGIMAGE/GRID_1922
STORAGE_TYPE_FOR_SWLIB=OmsShared
STORAGE_NAME_FOR_SWLIB=default_loc
REF_GI_CREDENTIALS=V2V_ORACLE_VM_LOGIN:SYSMAN
REF_HOST_ROOT_CREDENTIALS=GLOBAL_SUDO_TO_ROOT_VIA_ORACLE:SYSMAN
WORKING_DIRECTORY=/ora01/app/stage
VERSION_NAME=19.22

DB1922_image.txt

ini
CopyEdit
IMAGE_NAME=DB1922
IMAGE_DESCRIPTION=DB PSU
REF_TARGET_NAME=OraHome2_5_Test DB Server_6713
IMAGE_SWLIB_LOC=FPPGIMAGE/DB_922
STORAGE_TYPE_FOR_SWLIB=OmsShared
STORAGE_NAME_FOR_SWLIB=default_loc
REF_HOST_CREDENTIALS=V2V_ORACLE_VM_LOGIN:SYSMAN
REF_HOST_ROOT_CREDENTIALS=GLOBAL_SUDO_TO_ROOT_VIA_ORACLE:SYSMAN
WORKING_DIRECTORY=/ora01/app/stage
VERSION_NAME=19.22

📸 Screenshot Placeholder:
🖼️ Terminal output showing contents using cat grid1922_image.txt and cat DB1922_image.txt

🖥️ Step 4: OEM Console – Create FPP Image Directory

  1. Login to OEM Console.

  2. Navigate to Enterprise → Provisioning and Patching → Software Library.

  3. Create a new directory:

    • Path: FPPGIMAGE

    • Structure: Subdirectories for GRID_1922 and DB_922

📸 Screenshot Placeholder:
🖼️ OEM Console view showing creation of directories in Software Library

🚀 Step 5: Initiate GOLD Image Creation

  • Use the OEM’s image creation workflow.

  • Select the parameter files grid1922_image.txt and DB1922_image.txt.

  • Choose the respective credentials.

  • Confirm all validations and begin the creation process.

📸 Screenshot Placeholder:
🖼️ OEM screen during image creation wizard showing parameter file inputs

🧩 Summary Checklist

Task

Description

Status

Patch source DB to 19.22

Ensure DB is updated

✅

Create required directories

On source server

✅

Create credentials in OEM

V2V_ORACLE_VM_LOGIN, GLOBAL_SUDO_TO_ROOT_VIA_ORACLE

✅

Build parameter/input files

Use provided formats

✅

Setup Software Library

Create FPPGIMAGE in OEM

✅

Launch Image Creation

From OEM Console

✅



Comments

Post a Comment

Dear User,

Thank you very much for your kind response

Popular posts from this blog

Agent Installation on Windows Server. SQL Server (Failover Cluster) target addition in OEM 12c

Image
Agent Installation on Windows Server. SQL Server (Failover Cluster) target addition in OEM 12c This document is prepared for monitoring windows server where sql server installed.Mostly used OEM for monitoring databases. In this document we will cover agent installation with target addition into OEM 12c. We will also cover prerequisite like enabling port for communication from agent to oms server Agent Installation on windows server  As a part of installation, we require to fulfil prerequisite like connectivity between OEM server and Window server. For Port opening and communication between two servers Ports required to open : 4903 , 7799 , 3872 Following steps require doing for manually installation of Agent in Windows server. Verifying if the agent exists on OMS. To begin, open your Cloud Control and go to "Setup -> Extensibility -> Self Update". Open the "Agent Software" folder and check if the Agent Software of Windows x64 is with statu...
Read more

Oracle 11g: Install Instant Client 11.2.0.3.0 on Linux x86_64 Server.

Oracle 11g: Install Instant Client 11.2.0.3.0 on Linux x86_64 Server. ***What is Instant Client &benefits? As per Oracle docs, Oracle Database Instant Client Instant Client allows you to run your applications without installing the standard Oracle client or having an ORACLE_HOME. OCI, OCCI, Pro*C, ODBC, and JDBC applications work without modification, while using significantly less disk space than before. Even SQL*Plus can be used with Instant Client. No recompile, no hassle. ISVs and Partners   benefit greatly from packaging Instant Client along with their applications, saving customers the extra step of installing and configuring an Oracle client. Free. The same fully-featured, high-performance applications that Oracle ISVs and partners have always delivered will continue to work, untouched. Customers can try new packaged applications and Oracle client features quickly without worrying about other installations. Larger enterprises ca...
Read more

Oracle 12c : How To Purge The UNIFIED AUDIT TRAIL

Image
Oracle 12c : How To Purge The UNIFIED AUDIT TRAIL  APPLIES TO: Oracle Database - Enterprise Edition - Version 12.1.0.1 and later Information in this document applies to any platform. GOAL  How to purge the  UNIFIED_AUDIT_TRAIL table ? SOLUTION The unified audit trail can be purged using the DBMS_AUDIT_MGMT package:  qlplus / as sysdba SQL>  select  count(*) from unified_audit_trail;   COUNT(*) ----------       2619 SQL>  BEGIN DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL( audit_trail_type         =>  DBMS_AUDIT_MGMT.AUDIT_TRAIL_UNIFIED, use_last_arch_timestamp  =>  FALSE); END; / PL/SQL procedure successfully completed. SQL>  select  count(*) from unified_audit_trail;   COUNT(*) ----------          1 You can also use the last_arch_timestamp, if you don't want to purge all ...
Read more