4.1 Procedure 25 DIU Upgrade Server B

Note:

Ensure that the Legacy Upgrade before DIU is accepted, otherwise it might cause an error while initiating background upgrade in DIU.

Table 4-1 Procedure 25 DIU Upgrade Server B

S.No Steps This procedure performs Dual Image Upgrade on the server.Check off (✔️) each step as it is completed. Boxes have been provided for this purpose beside each step number.If this procedure fails, contact My Oracle Support and ask for ASSISTANCE.Estimated time: 80 mins Note: Make sure to follow DIU Upgrade Steps before starting this procedure

1

MPS B: Login prompt is displayed. 

<hostname> console login:

Note: Press enter if no login prompt is displayed.

2

MPS B: Log in as “root” user. 

[hostname] consolelogin: root 
password:	password

3

MPS B: Copy DIU ISO

Perform the procedure in Procedure A.1 or copy LSMS APPB DIU ISO to /var/TKLC/upgrade directory.

Make sure that only the DIU ISO and patch is present in the directory.

4

Create a terminal window log in MPS B.

If not already connected, connect to the E5-APP-B card via the serial port.

For connecting the E5-APP-B B card, disconnect the console cable from the serial port on the E5-APP-B A card’s adapter. The cable should be disconnected at the point where it connects to the serial port labeled ‘S1’ on the E5-APP-B A card’s adapter and use it for serial access. Cable part numbers - 830-1220-xx

5

MPS B: Stop Node and Move all custom files and run pre upgrade script

Note: NTP must be configured before starting DIU.

Note: All custom files, scripts, folders need to be migrated to remote server before the DIU process is started. These need to be restored back to their place after the DIU process is completed. 

<hostname> console login: 
root password:
# su – lsmsmgr

Main Menu with Maintenance selected for node management.


Maintenance Menu with Stop Node selected.


Stop Node dialog asking for confirmation of a possible service interruption.


Message confirming that node shutdown completed successfully.

Exit the lsmsmgr menu.

Run the following command and verify the HA state 

# hastatus

Verify that the hastatus of server is ‘UNINITIALIZED "INHIBITED"’

Before running below script, make sure to grep and kill ‘osisk6|opesk6|npacagent’ process if running

# ps -ef | egrep 'osisk6|opesk6|npacagent' | grep -v grep
# kill –9 <PID>

Note: Bring DIU_script.sh from Oracle Software Delivery Cloud (OSDC) and place it in /usr/TKLC/lsms/tools/ directory. Use DIU_script.sh to cleanup the extra files and make extra space for DIU.

Change permission and group of the script:

[root@MPS-B tools]# chmod 777 DIU_script.sh 
[root@MPS-B tools]# chown root:root DIU_script.sh

Note: Before running the pre-upgrade script, ensure the mount point `/var/TKLC/lsms/free` is not in active use. Specifically, verify that no interactive shells (e.g., `bash`) or other processes have their current working directory set to `/var/TKLC/lsms/free` (or any subdirectory), as this will cause the unmount step to fail with “target is busy.”

Run the pre-upgrade script.


Terminal output from the pre-upgrade script showing storage and RAID preparation.

Run vgs to make sure Free space is more than 50G
[root@Steak-B ~]# vgs
  VG     #PV #LV #SN Attr   VSize    VFree  
  vgroot   1  12   0 wz--n- <442.41g <53.33g

6

MPS B: Start platcfg utility.

 
$ su – platcfg

7

MPS B: Navigate to the Upgrade menu.

**NOTE**: Make sure to select Dual Image

Upgrade only.

The platcfg Main Menu appears.

  1. On the Main Menu, select Maintenance and press [ENTER].
    Main Menu with Maintenance selected for Dual Image Upgrade.

  2. Select the Dual Image Upgrade menu and press [ENTER].
    Maintenance Menu with Dual Image Upgrade selected.

8.

MPS B: Validate ISO file.

Validate ISO file using Procedure A.2.

9.

MPS B: Select Early Upgrade Checks

Select the “Early Upgrade Checks” menu to verify that the system is ready for upgrade.


Dual Image Upgrade Menu with Early Upgrade Checks selected.

Note: Please note that the previous upgrade should be accepted before proceeding for DIU upgrade. If the previous upgrade is not accepted, then early upgrade checks will fail with the error that previous upgrade is not yet accepted.

If the Early Upgrade Checks fail due to the NTP related alarms, then ignore the NTP alarms using the following commands:

  • Exit the platcfg menu.

  • Change to root user using the “su –" command.

  • vim /usr/TKLC/plat/etc/upgrade/upgrade.conf

  • Edit the following line to include the NTP related alarms.

    • EARLY_CHECK_ALARM_WHITELIST=TKSPLATMI2

    • Add the following alarm code to ignore Storage Capacity Problem:

      TKSPLATMA5

    • Add the following line for the RAID related alarms:

    • EARLY_CHECK_ALARM_WHITELIST=TKSPLATMA2

For example:

To allowlist the NTP alarm, “tpdNTPDaemonNotSynchronizedWarning”, which has the alarm code TKLCPLATMI10, the above-mentioned line should be edited as EARLY_CHECK_ALARM_WHITELIST=TKSPLATMI2,TKSPLATMI10

Note: There should not be any space between two alarms i.e. between TKSPLATMI2 and TKSPLATMI10.

If the Early Upgrade Checks fail due to “Server Default Route Network Error”, then this alarm shall be allowlisted in upgrade.conf file. To allowlist the alarm which has the alarm code TKSPLATMA14, the above-mentioned line should be edited as:

EARLY_CHECK_ALARM_WHITELIST=TKSPLATMA2,TKSPLATMI2,TKSPLATMA5,TKSPL ATMI10, TKSPLATMA14,TKSPLATMA28,TKSPLATMI39

Note: Please note that TKSPLATMA5, TKSPLATMA2, TKSPLATMI2 should always be whitelisted.

10

MPS B: Navigate to the Initiate Upgrade menu

Select the Initiate Background Upgrade menu and press [ENTER].


Dual Image Upgrade Menu with Initiate Background Upgrade selected.

11

MPS B: Select the Upgrade Media.

The screen displays a message that it is searching for upgrade media. When the upgrade media is found, an Upgrade Media selection menu appears similar as shown in the example below.

Select the desired upgrade media and press [ENTER].


Choose Upgrade Media Menu with the LSMS DIU ISO selected.

In case there is a failure in the upgrade process, then run the following command to verify whether the raid is synced or not:

  • lsblk Key Points:

  • Under a healthy, in-sync RAID, both member partitions will show the same md device.

  • If the RAID is not in sync or missing a member, only one partition will show the md device.

Example of lsblk output when raid is in sync,


Terminal screenshot showing the example lsblk output when RAID is in sync.

Please note that in the above raid in sync snapshot of lsblk, sdb is for USB as it shows 28.9G while sda and sdc are for HDD which is 447.1G. Hence whenever you run lsblk command, always take a note of which drive is showing USB and which drives are showing HDD.

Raid not in sync example snapshot:


lsblk output showing the example when RAID is not in sync.

Please note that in the above raid in sync snapshot of lsblk, sda is for USB as it shows 28.9G while sdb and sdc are for HDD which is 447.1G. Hence whenever you run lsblk command, always take a note of which drive is showing USB and which drives are showing HDD. Here we are saying raid is not in sync because only sdb is showing md1 device but sdc is not showing any md device.

If the raid is not in sync, then run the following command:

mdadm --add /dev/md1 /dev/sdX

where sdX can be any of sda, sdb, or sdc according to LV configurations.

sdX will never be the USB partition. This can be verified using lsblk command. In the above example, sdb and sdc are for hard disk and sda is for USB, here sdc is not in sync as it is not showing the proper md device md1. Hence, the command for syncing the above raid not in sync scenario will be like given below.

mdadm --add /dev/md1 /dev/sdc

The following command can be used to check the status of the sync after running the above command.

[root@MPS-B upgrade]# cat /proc/mdstat 
Personalities : [raid1]
md1 : active raid1 sdb[3] sdc2[2] 468091904 blocks super 1.2 [2/1] [U_]
[===>.................] recovery = 19.1% (89824128/468091904)
finish=81.5min speed=77331K/sec
bitmap: 4/4 pages [16KB], 65536KB chunk 
unused devices: <none>

Wait till the time recovery is not completed 100%.

12

MPS B: Upgrade proceeds.

Apply Upgrade.

Many informational messages appear on the terminal screen as the upgrade proceeds.

After the background upgrade is done, the system will return to this screen.


Choose Upgrade Media Menu with the LSMS DIU ISO selected.

After this, select [EXIT] and press [ENTER].

From the Dual image Upgrade Menu, select [EXIT] and press [ENTER}.


Dual Image Upgrade Menu with Exit selected.

Exit platcfg meny and verify the status using below command, It should show “Ready to Apply upgrade”

/var/TKLC/backout/diUpgrade –status
[root@Arica-b tmp]# /var/TKLC/backout/diUpgrade --status 
State: Ready to Apply Upgrade

Status Messages:

  • Performing early checks

  • Downloading upgrade data

  • Verifying image

  • Performing image pre-install

  • Configuring images

  • Identifying resources

  • Reserving image storage

  • Installing image

  • Verifying configuration sanity

  • Performing image post-install

  • Image install complete

From the platcfg menu -> select maintenance menu, select Dual Image Upgrade and then Press Enter.


Maintenance Menu with Dual Image Upgrade selected before applying the upgrade.

From the Dual Image Upgrade Menu, select Apply Upgrade and press [ENTER].


Dual Image Upgrade Menu with Apply Upgrade selected.

Select YES and press ENTER.


Confirmation dialog asking whether to apply the upgrade.

When the upgrade process is complete, the server reboots.

13

MPS B: Upgrade completed.

After the final reboot, the screen displays the login prompt as displayed in the example below.


Terminal output showing upgrade application progress and successful completion.

Make sure to verify that the state is transitioned from “Applying upgrade” to “Upgrade Applied” and we get Completed Result: SUCCESS using below command.

/var/TKLC/backout/diUpgrade --status

14

MPS B: log in as “root” user. 

[hostname] consolelogin: root 
password:	password

15

MPS B: Check the Upgrade log.

Examine the upgrade logs in the directory /var/TKLC/log/upgrade and verify that no errors and warnings were reported.

$ grep –i error /var/TKLC/log/upgrade/upgrade.log
$ grep -i warning /var/TKLC/log/upgrade/upgrade.log

16

MPS B: Check that the upgrade completed

successfully.

Run the command from the root user:

[root@Floater04 ~]$ /var/TKLC/backout/diUpgrade --status

17

MPS B: Check that the upgrade completed

successfully.

Verify that the following output is displayed. If it is not, contact My Oracle Support following the instructions on the front page or the instructions on the Appendix E.


diUpgrade status output showing the Upgrade Applied state.

19

MPS B: Reboot after installation

Reboot the system after the “Apply Complete Process” to finally finish the installation.

$ reboot

20

MPS B: Install Complete.

The installation procedure is complete. If there are any issues in the upgrade, check Procedure A.48 Dual Image Upgrade Known Issues Fix.

21

Note down the timestamp in log.

Run the following command:

$ date

22

Start Node the server to make it Standby

 
$ startNode

The command will take time depending on the DB size.

$ hastatus
STANDBY