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

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

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

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

7. 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.

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

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

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

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

---

🗃️ Database System & Component Overview

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

13. 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

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

15. 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

 

How to assign ILOM IP to the new Solaris server + Solaris 11

How to Assign ILOM IP to a New Solaris Server (Solaris 11)

Setting up a new Solaris server involves several steps, and one of the most critical is configuring the Integrated Lights Out Manager (ILOM) IP address. This allows administrators to manage the server remotely, even when the operating system is not running. In this blog, I’ll walk you through the process of assigning an ILOM IP to a newly racked Solaris 11 server.

---

🧰 Prerequisites

Before you begin, ensure the following:

• The server is rack-mounted and connected to power and network.
• You have the server make and model noted down.
• A console cable is available to connect your laptop to the server.
• You’ve received the ILOM IP address, gateway, and netmask from your network team.

---

🖥️ Step-by-Step Guide

1. Connect to ILOM via Serial Console

• Use a console cable to connect your laptop to the server’s NET MGMT port.
• On your laptop, open Computer Management:
  • Navigate to: Computer Management > Device Manager > Ports (COM & LPT)
  • Note the COM port number assigned to the console cable.

2. Launch Serial Session Using PuTTY

• Open PuTTY and select the Serial connection type.
• Enter the COM port noted earlier.
• Set the baud rate (typically 9600, but may vary based on server model).
• Click Open to initiate the session.

📌 Tip: Baud rate may differ depending on hardware. Refer to the server documentation or search based on the make and model.

3. Log in to ILOM

• Press Enter in the PuTTY window to bring up the ILOM login prompt.
• Log in using the default or configured credentials.

---

🌐 4. Configure ILOM Network Settings

Once logged in, follow these commands to assign a static IP:

cd /SP/network 

set pendingipdiscovery=static 

set pendingipaddress=(IP address)

set pendingipnetmask=(Netmask)

set pendingipgateway=(Gateway)

set commitpending=true 

set state=enable

✅ Verify Configuration

Run the following to confirm the IP settings:

#show /SP/network

You should now see the assigned IP address and other network details.

---

🌍 5. Access ILOM via Web Interface

With the IP configured, you can now access the server’s ILOM interface through a browser:

https://<ILOM_IP>

Log in and begin managing the server remotely.

---

📝 Conclusion

Assigning an ILOM IP is a foundational step in setting up a new Solaris server. It ensures that you have out-of-band management access, which is crucial for troubleshooting and maintenance. By following the steps above, you can quickly and securely configure ILOM and begin your server setup with confidence.

---

Author:
Kiran Jadhav
Principal Consultant | Solaris Admin
Mumbai, Maharashtra

How to run sundiag on multiple cell nodes - exadata or SSC

 How to run sundiag on multiple cell nodes - exadata or SSC:

What is sundiag:

sundiag is Oracle Exadata Database Machine - Diagnostics Collection Tool which collects diagnostics information which help the support analyst in diagnosing problem such as failed hardware like a failed disk, etc.

In Exadata box or solaris supercluster (SSC) we may have multiple storage cell nodes attached. 

If we have 10-12 storage cells nodes then instead of login to each and every cells and collecting sundiag will be a time consuming task. By below one command we can run sundiag on multiple servers (passwordless ssh should be there from the compute node to the cell nodes).

1. on Solaris super cluster:

#dcli -g /opt/oracle.supercluster/bin/cell_group -l root /opt/oracle.SupportTools/sundiag.sh

where # cat /opt/oracle.supercluster/bin/cell_group  --> will list number of cell nodes attached to the SSC machine

2. on Exadata servers:

#dcli -g /opt/oracle.SupportTools/onecommand/cell_group -l root /opt/oracle.SupportTools/sundiag.sh

where # cat /opt/oracle.SupportTools/onecommand/cell_group  --> will list number of cell nodes attached to the Exadata machine

Thank U

- Kiiran B Jaadhav

How to split big files in Unix

 How to split big files in solaris:

Sometime the log files is too large to send backend team for further analysis, in that case we break the files into multiple pieces using split command.

Whenever we split a large file with split command then split output file’s default size is 1000 lines and its default prefix would be ‘x’.

Suppose we want to send crash dump (vdump) file which is 2GB of size. We will break that file into 4 pieces of size 500MB.

In that case:

#split -b 500M vdump.24 = This will break vdump.24 file into 4 pieces of name Xa , Xb, Xc, Xd

If we feel aa ab are little bit confusing file names then better to give specific name at the time of spliting the file itself.

#split -b 500M vdump.24 vdump_11May2021_X = It will create new files of name vdump_11May2021_Xa ,  vdump_11May2021_Xb

If we want to split file into GB then we may use command something like:

#split -b 1G vdump.24 vdump_11May2021_1

or

#split -b 1024M vdump.24 vdump_11May2021_1

Regards,

Kiren Jadhav

How to run explorer on Solaris 11

How to run explorer on Solaris 11 : 

Why we run explorer: To collect the hardware issues and OS related issues. It contains output of files like dmesg, system files, hardware errors etc...

How to run:  Just run explorer command, the command will run from /usr/sbin/explorer

# explorer

If you are running it for the first time:

# explorer -g

The output will get stored at /var/explorer/output

To check the explorer version:

# explorer -v

 

Regards,

Kirraan Jadhav

scriptlet failed, exit status 127 + RPM error

RPM error "scriptlet failed, exit status 127"

Sometime while patching the server, we may get message to delete some patches which create conflict.

And while deleting those conflicting rpms we get error something like this:

E

[root@cloud home]# rpm -e --nodeps ILMT-TAD4D-agent.i386-cs-cam.noarch

/var/tmp/rpm-tmp.XIuSM4[137]: /var/itlm/utilities/cit/wcitinst: not found [No such file or directory]

error: %preun(ILMT-TAD4D-agent-7.5-1.i386) scriptlet failed, exit status 127

We are erasing the rpms using -e option and not removing the rpm dependency   (Reason : The dependencies could be part of other rpms and by removing it we may encounter problem for other rpms). 
--nodeps Do not verify dependencies

  

 Solution:

 Delete the rpm using --noscripts option. The --noscripts option tells the rpm command not to run any uninstallation scripts

--noscripts  = Do not execute verification script

[root@cloud home]# rpm -e --nodeps  --noscripts ILMT-TAD4D-agent.i386

Regards,

Kalyanjit

How To get ZFS storage serial number + ZFS

How To get ZFS storage serial number, model number and OS details: 

Login to ZFS

zfsc1:> configuration version show

or 

zfsc1:> maintenance hardware show

Regards,

Kiran Jaddhav

How to generate (ak) Support bundles on ZFS storage

How to generate (ak) Support bundles on ZFS storage:

Step 1 : Login to ZFS

 zfsc1:> maintenance system bundle

bundle   bundles

zfsc1:> maintenance system bundle    ---> Main command

The support data you requested is being built in 3 files. Use 'send <srn>' with each bundle to associate the bundle with a Service Request Number and send it to

Oracle Support. Alternatively, you may download the bundles via the appliance BUI.

    ak.938k008c-9e13-4593-9305-b54d87659710.tar.gz

    ak.3b22kdbf-c95i-4b6a-be85-d89f58b18b97.tar.gz

    ak.eee2580k-bfi8-6442-defe-e9faccd32fb7.tar.gz

then 

zfsc1:> confirm shell              ----- We will get shell prompt

step 2 : Go to location where bundles get stored

# cd /var/ak/bundles           -- bundles will be stored here with the current date

step 3: We can check the same in ps command as well.

#ps -ef |grep -i bund = to check support bundle process are running or not

Example:

zfsc1# ps -ef |grep -i bund

    root 16467   389   0 13:03:19 ?           0:10 /usr/bin/bash -p /usr/bin/akbundle -b 938k008c-9e13-4593-9305-b54d87659710 -c C

    root  2251 16467   0 13:13:19 ?           0:05 /usr/bin/bash -p /usr/bin/akbundle -b 938k008c-9e13-4593-9305-b54d87659710 -c C

Regards,

Kiren Jadhav