Labels

hpunix (63) marathi kavita (52) linux (21) solaris11 (11) AWS (5) numerology (5)
Showing posts with label BM. Show all posts
Showing posts with label BM. Show all posts

Wednesday, July 9, 2025

Basic important ODA (Oracle Database Appliance) commands:

Mastering Oracle Database Appliance (ODA): 15 Essential Commands Every Admin Should Know

As working ODA admin, one of the key responsibilities is ensuring the smooth operation of Oracle Database Appliances (ODA). Whether you're managing a Bare Metal (BM) or Virtualized ODA environment, having a solid grasp of the most frequently used commands can significantly enhance your efficiency and troubleshooting capabilities.

In this blog, I’ll walk you through 15 essential ODA commands that every administrator should keep in their toolkit.


🔍 System & Disk Insights

  1. odaadmcli show disk
    Displays the current status of all disks in the system.
    Useful for checking disk health and identifying potential issues.

  2. odaadmcli show server
    Provides server details including serial number and hardware specifications.
    Handy for inventory and support cases.

  3. odaadmcli show env_hw
    Reveals the ODA model and whether it's configured as Bare Metal or Virtualized.
    Crucial for understanding the deployment architecture.


🖥️ Virtual Machine (VM) Management

  1. odacli list-vms
    Lists all running VMs and their associated nodes.
    Helps track VM distribution across nodes.

  2. odacli stop-vm -n <VM_Name>
    Stops the specified VM gracefully.
    Ideal for maintenance or resource reallocation.

  3. odacli start-vm -n <VM_Name>
    Starts the specified VM.
    Quick recovery or scheduled startup.

  4. odacli start-vm -n odavm -nn node0
    Starts the VM odavm on a specific node (e.g., node0).
    Useful for node-specific operations or testing.

  5. virsh list or virsh list --all
    Lists all VMs, including inactive ones.
    A broader view of VM inventory.

  6. virsh domblklist <VM_Name>
    Displays all disk details attached to a VM.
    Essential for snapshot planning and storage audits.

  7. odacli describe-vm -n <VM_Name>
    Provides detailed information about a specific VM.
    Includes configuration, resource allocation, and status.

  8. virsh console <VM_ID>
    Accesses the console of a specific VM.
    Direct interaction for troubleshooting or configuration.


🗃️ Database System & Component Overview

  1. odacli list-dbsystems
    Lists all DB systems configured on the ODA.
    Helps monitor database deployments and usage.

  2. odacli describe-component
    Displays installed and available versions of components like DCS Controller, OS, ILOM, BIOS, etc.
    Vital for patching and version control.


📋 Job Monitoring & Troubleshooting

  1. odacli list-jobs
    Lists all jobs initiated via odacli commands.
    Tracks task execution and history.

  2. odacli describe-job -i <Job_ID>
    Provides detailed status (success/failure) of a specific job.
    Crucial for debugging and audit trails.


✅ Final Thoughts

These commands form the backbone of ODA administration. Whether you're provisioning VMs, monitoring disk health, or managing patch levels, having these commands at your fingertips can streamline operations and reduce downtime.

If you're new to ODA or looking to refine your command-line skills, start by practicing these commands in a test environment. Over time, they’ll become second nature and empower you to manage your Oracle infrastructure with confidence.


Author:
Kiran Jadhav
Mumbai, Maharashtra



 


Friday, November 22, 2024

ODA Patching from version 19.21 to 19.23

 ODA Patching from version 19.21 to 19.23


This document will help you in ODA patching to upgrade from version 19.21 to version 19.23

If we have ODA box with version 19.17 then we cannot directly patch it to 19.23 version. We must patch the ODA box to version to 19.21 and then we can go on patch 19.23.

To perform ODA patching VM snapshots and RMAN backup is most important; if anything fails then we can restore VMs from the snapshot.

1.       Download 19.23 patches from Oracle site:

https://docs.oracle.com/en/engineered-systems/oracle-database-appliance/19.23/cmtrn/oda-patches.html#GUID-ACB179CD-5901-405C-B732-AD6923D78339

 

                     Patch list:

                 Oracle Database Appliance Server Patch for the ODACLI/DCS stack (patch 36524605),

                 Oracle Grid Infrastructure clone files (patch 30403673),

                 Oracle Database clone files (patch 30403662)

2.       Login to the Oda bare metal (BM) servers and note down the VMs and DB system details.

#virsh list    >>> This command shows VM names and we will be taking VM snapshots for the same before starting patching

 

#odacli list-vms  >>> This command list VMs information like VM names, they are active on which node,current state, target state etc…

 

3.       Identify the vdisk assosiated with the respective VM

#virsh domblklist <VM Name>

 

4.       Here we are taking snapshot of vda and vdb disk so note down the size of the vdisk and here we will ignore hda as it is iso

Note: Bring down respective VM before taking snapshot.


5.       Create VM snapshot for the both the vdisks

6.       Save the VM snapshot to some NFS location

 

Actual Patching process:

Before starting the patching process make sure DB and DB system and crs cluster service should be running.

 

Run below commands from BM server

1.       Update repository with server patch

#unzip p35938481_1923000_Linux-x86-64.zip             >>> The zip file will contain oda-sm-19.23.0.0.0-date-server.zip and readme.html file

 

2.       Update the repository with the server software file

# odacli update-repository -f /tmp/oda-sm-19.23.0.0.0-date-server.zip

 

3.       Confirm that the repository update is successful

                              # odacli describe-job -i <job_ID>           >>> every odacli commands generate some                                         job id

4.       Update DCS admin/Components/Agents

4.1   Update DCS admin

                              # odacli update-dcsadmin -v 19.23.0.0.0

4.2   Update the DCS components

# odacli update-dcscomponents -v 19.23.0.0.0 

4.3   Update the DCS agent

#odacli update-dcsagent -v 19.23.0.0.0

 

5.       Unzip below patches:

Oracle Grid Infrastructure clone files (patch 30403673),
Oracle Database clone files (patch 30403662)

 

6.       Update the repository with the Oracle Grid Infrastructure clone file and the Oracle Database clone file:

# odacli update-repository -f /tmp/odacli-dcs-19.23.0.0.0-date-GI-19.23.0.0.zip

# odacli update-repository -f /tmp/odacli-dcs-19.23.0.0.0-date-DB-19.23.0.0.zip

 

7.       Create prepatch report for server

# odacli create-prepatchreport -s -v 19.23.0.0.0

 

8.       Verify that the patching pre-checks ran successfully

# odacli describe-prepatchreport -i <job ID>        

Note: Fix the warnings and errors mentioned in the report and proceed with the server patching.

 

9.       Apply the server update. 

                              # /opt/oracle/dcs/bin/odacli update-server -v 19.23.0.0.0

 

10.   Confirm that the server update is successful

        # /opt/oracle/dcs/bin/odacli describe-job -i <job_ID>

 

Run below commands from DB server

11.   Update DCS admin/Components/Agents

11.1           Update DCS admin

                              # odacli update-dcsadmin -v 19.23.0.0.0

11.2           Update the DCS components

# odacli update-dcscomponents -v 19.23.0.0.0

11.3           Update the DCS agent

#odacli update-dcsagent -v 19.23.0.0.0

 

12.   Update the repository with the Oracle Grid Infrastructure clone file and the Oracle Database clone file:

# odacli update-repository -f /tmp/odacli-dcs-19.23.0.0.0-date-GI-19.23.0.0.zip

# odacli update-repository -f /tmp/odacli-dcs-19.23.0.0.0-date-DB-19.23.0.0.zip

 

13.   Apply the server update. 

                              # /opt/oracle/dcs/bin/odacli update-server -v 19.23.0.0.0               >>> verify it by                                               using command “#odacli describe-component”

14.   Create prepatch report for DB home

# odacli create-prepatchreport --dbhome --dbhomeid d8307f2e-c126-41da-ab6a-1a7f23c5c074 -v 19.23.0.0.0


We can get dbhome id by using command “#odacli list-databases”

 

15.   Verify the pre-patch report; it should be successful.

Note down the job id and run below command to verify

#odacli describe-jobs -I <job-id>

 

16.   Update db_home

# odacli update-dbhome --id d8307f2e-c126-41da-ab6a-1a7f23c5c074 -v 19.23.0.0.0 -f 

 

17.   Note down the job id and observe the status; it should be successful.


18.   Verify patching by using command:

# odacli describe-component        >>> we can see here version 19.23



Regards,

Kiren Jadhav