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

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 create bootable USB in solaris

How to Create a Bootable USB (Pen Drive) in Solaris

Creating a bootable USB in Solaris is a crucial task for system administrators, especially when dealing with server recovery, new installations, or maintenance scenarios. Whether you're recovering a root password or booting a server from ISO media, having a bootable USB ready can save valuable time.

---

Why Is It Required?

There are several scenarios where booting from a USB ISO image becomes necessary:

• Root password recovery
• Fresh OS installation
• Server in maintenance mode
• Booting from ISO for troubleshooting

---

Step-by-Step Guide

Step 1: Download the Solaris ISO

Search on Google:
Solaris 11.4 ISO download

Choose the correct ISO based on your server architecture:

• SPARC → Download SPARC USB Text Installer
• X86 → Download X86 USB Text Installer

For SPARC hardware, download:

SPARC Text Installer ISO

---

Step 2: Transfer ISO to a Test Solaris Server

Once downloaded, copy the ISO to a working Solaris server.

root@cdom3:~# ls -lrth
-rw-r--r--   1 root     root        1.1G Jul 18 13:09 sol-11_4-text-sparc.usb
root@cdom3:~#

Step 3: Write ISO to USB Drive

Insert the USB drive into the test server and run:

root@cdom3:~# usbcopy sol-11_4-text-sparc.usb

You’ll see output like:

image type: dd-able Sparc
Found the following USB devices:
0:      /dev/rdsk/c9t0d0s2      14.7 GB SanDisk  Cruzer Blade     1.00
Enter the number of your choice: 0
WARNING: All data on your USB storage will be lost.
Are you sure you want to install to
SanDisk Cruzer Blade 1.00, 14700 MB at /dev/rdsk/c9t0d0s2 ?  (y/n) y
Copying and verifying image to USB device
Finished 1160 MB in 234 seconds (4.9MB/s)
Successfully completed copy to USB

---

Step 4: Remove USB and Insert into Target Server

Once the image is successfully copied, remove the USB from the test server and insert it into the target server (in maintenance mode).

---

Step 5: Boot Server from USB

At the OK prompt, scan for connected devices

{0} ok probe-scsi-all       
Target 9
  Unit 0   Disk   HITACHI  H109030SESUN300G A606    585937500 Blocks, 300 GB
  SASDeviceName 5000cca043487328  SASAddress 5000cca043487329  PhyNum 0
Target a
  Unit 0   Disk   HITACHI  H109030SESUN300G A606    585937500 Blocks, 300 GB
  SASDeviceName 5000cca043487400  SASAddress 5000cca043487401  PhyNum 1
/pci@340/pci@1/pci@0/pci@3/usb@0/hub@8/storage@1
  Unit 0   Removable Disk     SanDiskCruzer Blade1.00

Identify the USB device:

{0} ok devalias

Select the USB disk (e.g., option h) and create a device alias:

{0} ok show-disks
a) /reboot-memory@0
b) /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0,1/fp@0,0/disk
c) /pci@380/pci@1/pci@0/pci@7/SUNW,qlc@0/fp@0,0/disk
d) /pci@380/pci@1/pci@0/pci@6/SUNW,qlc@0,1/fp@0,0/disk
e) /pci@380/pci@1/pci@0/pci@6/SUNW,qlc@0/fp@0,0/disk
f) /pci@3c0/pci@1/pci@0/pci@2/scsi@0/disk
g) /pci@300/pci@1/pci@0/pci@2/scsi@0/disk
h) /pci@340/pci@1/pci@0/pci@3/usb@0/hub@8/storage@1/disk
i) /iscsi-hba/disk
q) NO SELECTION
Enter Selection, q to quit: h
/pci@340/pci@1/pci@0/pci@3/usb@0/hub@8/storage@1/disk has been selected.
Type ^Y ( Control-Y ) to insert it in the command line.
e.g. ok nvalias mydev ^Y
         for creating devalias mydev for /pci@340/pci@1/pci@0/pci@3/usb@0/hub@8/storage@1/disk

Boot from the USB:

{0} ok boot mydev
Boot device: /pci@300/pci@1/pci@0/pci@2/scsi@0/disk@p0  File and args: mydev
/

If that fails, boot directly using the full device path:

{0} ok boot /pci@340/pci@1/pci@0/pci@3/usb@0/hub@8/storage@1/disk

Conclusion

Creating a bootable USB in Solaris is straightforward but powerful. It enables administrators to recover, reinstall, or troubleshoot servers efficiently. Always ensure you select the correct ISO and verify the USB copy process before proceeding.

Regards,

Kiren Jadhav

How to mirror root disks in Solaris 11

 How to mirror root disks in Solaris 11

Mirroring root disks is used for redundancy purpose i.e. incase of failure of 1 disk the data will be accessible from other disks. If we want to mirror the root disk in rpool then we need to follow below process.

In this example we are mirroring root disk which are locally present on server. We can mirror the disks which are coming from external storage. 

1.       To know the disks attached to the server.

#echo |format

1.       Check rpool status. Here it is showing only 1 disk is present in rpool.

#zpool status rpool

1.       Attach one more disk of same size to rpool.

#zpool attach -f rpool <disk1> <New disk_disk2>

1.       Resilvering will start on new disk and till that time you will see the particular pool in Degraded state.

 

What is resilvering: Resilvering operation is moving data from the good copies to the new device.

1.       Once resilvering done the pool will have status ONLINE and you will be see 2 disks in mirrored.

Thanks,

Kiren Jadhav