Showing posts with label odacli. Show all posts

Friday, July 18, 2025

How to Add Disks in an Oracle Database Appliance (ODA) Single Node BM

How to Add Disks in an Oracle Database

Appliance (ODA) Single Node BM

When managing an Oracle Database Appliance (ODA), ensuring sufficient disk space in the DATA and RECO diskgroups is crucial for optimal performance and storage management. If you find yourself running low on space and need to add new physical NVMe disks, follow these step-by-step instructions to expand your storage on a single-node Bare Metal ODA.

Prerequisites

Ensure you have 4 new NVMe disks ready for installation.
Confirm the ODA is a single-node Bare Metal system.
Have administrative access to run odaadmcli commands.

Step-by-Step Guide

1. Check Current Diskgroup Usage

Before adding new disks, assess the current size of the DATA and RECO diskgroups:

# odaadmcli show diskgroup

This command displays the current allocation and usage of the diskgroups.

2. Review Existing Disk Status

Identify the existing disk IDs and their status:

# odaadmcli show disk

Note down disk IDs like pd_00, pd_01, etc., for reference.

3. Insert New Physical Disks

Insert the new NVMe disks one at a time into available slots (e.g., slots 4 to 7). If a disk is not automatically powered on or visible, manually power it on:

# odaadmcli power disk on pd_04
# odaadmcli power disk on pd_05
# odaadmcli power disk on pd_06
# odaadmcli power disk on pd_07

Replace pd_04 to pd_07 with the actual disk IDs if they differ.

4. Expand Storage

Once all disks are inserted and powered on, expand the storage to include the new disks:

# odaadmcli expand storage -ndisk 4

This command adds the 4 new disks to the ODA storage pool.

5. Verify Disk Addition

Recheck the disk status to confirm the new disks are recognized:

# odaadmcli show disk

You should now see the newly added disks listed.

6. Confirm Diskgroup Expansion

Finally, verify that the DATA and RECO diskgroups have increased in size:

# odaadmcli show diskgroup

This confirms successful expansion of your storage.

Conclusion

Adding disks to an Oracle Database Appliance is a straightforward process when done methodically. Regular monitoring and timely expansion of storage ensure your database environment remains robust and efficient.

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

odaadmcli show disk
Displays the current status of all disks in the system.
Useful for checking disk health and identifying potential issues.
odaadmcli show server
Provides server details including serial number and hardware specifications.
Handy for inventory and support cases.
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

odacli list-vms
Lists all running VMs and their associated nodes.
Helps track VM distribution across nodes.
odacli stop-vm -n <VM_Name>
Stops the specified VM gracefully.
Ideal for maintenance or resource reallocation.
odacli start-vm -n <VM_Name>
Starts the specified VM.
Quick recovery or scheduled startup.
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.
virsh list or virsh list --all
Lists all VMs, including inactive ones.
A broader view of VM inventory.
virsh domblklist <VM_Name>
Displays all disk details attached to a VM.
Essential for snapshot planning and storage audits.
odacli describe-vm -n <VM_Name>
Provides detailed information about a specific VM.
Includes configuration, resource allocation, and status.
virsh console <VM_ID>
Accesses the console of a specific VM.
Direct interaction for troubleshooting or configuration.

🗃️ Database System & Component Overview

odacli list-dbsystems
Lists all DB systems configured on the ODA.
Helps monitor database deployments and usage.
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

odacli list-jobs
Lists all jobs initiated via odacli commands.
Tracks task execution and history.
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

Kiran Jadhav

Labels

Friday, July 18, 2025