Engineered Systems – Blog DBA Dutra

How to use Data Preserving Reprovisioning on ODA

André Luiz Dutra Ontalba — Fri, 13 Jan 2023 23:43:25 +0000

Introduction

Data Preserving Reprovisioning enables reprovisioning of an already deployed Oracle Database Appliance system without modifying the storage and and the databases on the appliance. The advantage of this method over the regular upgrade process is that it has a much shorter upgrade path. This is achieved by saving the information of the source system, capturing them as server data archive files.

Advantages of using Data Preserving Reprovisioning for upgrade are as follows:

The upgrade utility runs prechecks on the system, such as detection of databases that are inactive and provides a warning before you upgrade the appliance. You can proactively address these failures beforehand and not encounter issues at the time of reprovisioning of the appliance.
During the first step of detaching the node, information about the system is collected and preserved, including information about the VLAN, CPU, and Oracle AFD settings. These settings are migrated after the reimage and the third step in this process reprovisions these settings.
The deployment is initially at Oracle Database Appliance release 12.1.2.12, 12.2.1.4, or 18.x, but after the reprovisioning process, the software is upgraded to Oracle Database Appliance release 19.15 and the deployment automatically starts using new features wherever applicable. For example, the database software is installed on Oracle ACFS-based storage.
You can upgrade your appliance directly to the latest Oracle Database Appliance release without upgrading to intermediate releases.

Limits

Data Preserving Reprovisioning (DPR) is limited to old versions: 12.1.2.12, 12.2.1.4, 18.3, 18.5, 18.7, and 18.8.

How does it work?

Reimaging normally implies wiping out the data disks before, but this is not mandatory. You can keep your databases on disk, extract the metadata of your ODA setup, reimage your appliance and then remap the databases to your fresh install.

Environment

I have an X7 and the first thing I did is a reimaging to 18.8. X7 came along 19c, but also supports 18.8.

On this 18.8 environment, I deployed 2 DB homes, 18.8 and 12.2. I created 2 databases on it.

odacli describe-component
System Version
---------------
18.8.0.0.0

Component                                Installed Version    Available Version
---------------------------------------- -------------------- --------------------
OAK                                       18.8.0.0.0            up-to-date
DB {
[ OraDB18000_home1 ]                      18.8.0.0.191015       up-to-date
[ OraDB12204_home1 ]                      12.2.1.4.191015       up-to-date
}
DCSAGENT                                  18.8.0.0.0            up-to-date
ILOM                                      5.0.2.24.r141466      4.0.4.38.a.r132148
BIOS                                      52050300              52020500
OS                                        6.10                  up-to-date
FIRMWARECONTROLLER                        VDV1RL04              vdv1rl02
FIRMWAREDISK                              1132                  1102

odacli list-databases

ID                                       DB Name    DB Type  DB Version           CDB        Class    Shape    Storage    Status        DbHomeID
---------------------------------------- ---------- -------- -------------------- ---------- -------- -------- ---------- ------------ ----------------------------------------
7c724f57-a495-4db9-a88a-48323f3632c6     DUTS18c   Si       18.8.0.0.191015      false      Oltp     Odb4     ASM       Configured   3eac70f5-6510-4c7c-bf5b-ed938dc60aa1
7041785be-d58e-44c6-b51d-d2729a99b8e8    DUTS12c   Si       12.2.1.4.191015      false      Oltp     Odb4     ASM       Configured   8dbba7de-4348-4c61-a171-f7413d30bc14

Detach the node

First step is to detach your configuration. You will need this additional tool from MOS:

Patch 33594115: DATA PRESERVING REPROVISIONING: UPLOAD ODA UPGRADE UTILITY ZIP TO ARU

Unzip the files and run the precheck:

cd /transfer/oracle
unzip p33594115_1915000_Linux-x86-64.zip

unzip -d /opt/oracle odaupgradeutil_220530.zip

cd /opt/oracle/odaupgradeutil/

./odaupgradeutil run-prechecks

Initializing...
########################## ODAUPGRADEUTIL - INIT - BEGIN ##########################
Please check /opt/oracle/oak/restore/log/odaupgradeutil_init_12-01-2023_10:06:55.log for details.
Get System Version...BEGIN
System Version is: 18.8.0.0.0
Get System Version...DONE
Get Hardware Info...BEGIN
Hardware Model: X7-2, Hardware Platform: M
Get Hardware Info...DONE
Get Grid home...BEGIN
Grid Home is: /u01/app/18.0.0.0/grid
Get Grid home...DONE
Get system configuration details...BEGIN
Grid user is: grid
Oracle user is: oracle
Get system configuration details...DONE
########################## ODAUPGRADEUTIL - INIT - END ##########################
*********
IMPORTANT
*********
odaupgradeutil will bring down the databases and grid services on the system.
The files that belong to the databases, which are stored on ASM or ACFS,
are left intact on the storage. The databases will be started up back after
re-imaging the ODA system using 'odacli restore-node' commands.
As a good precautionary measure, please backup all the databases on the
system before you start this process. Do not store the backup on this ODA
machine since the local file system will be wiped out as part of the re-image.
*********
IMPORTANT
*********
########################## ODAUPGRADEUTIL - PRECHECKS - BEGIN ##########################
Please check /opt/oracle/oak/restore/log/odaupgradeutil_prechecks_12-01-2023_10:07:15.log for details.
System version precheck...BEGIN
System version precheck...PASSED
System config precheck...BEGIN
System config precheck...PASSED
Required Files precheck...BEGIN
Required Files precheck...PASSED
Need to discover DB homes
Get Database homes...BEGIN
Get Database homes...SUCCESS
Disk space precheck...BEGIN
Get Quorum Disks...BEGIN
Get Quorum Disks...SUCCESS
Disk space precheck...PASSED
DCS Agent status precheck...BEGIN
DCS Agent status precheck...PASSED
OAK precheck...BEGIN
OAK precheck...PASSED
ASM precheck...BEGIN
ASM precheck...PASSED
Database precheck...BEGIN
Get databases...BEGIN
  Database Name: DUTS18c
  Oracle Home: /u01/app/oracle/product/18.0/dbhome_1
  Database Name: DUTS12c
  Oracle Home: /u01/app/oracle/product/12.2/dbhome_1
Get databases...SUCCESS
Database precheck...PASSED
Audit Files precheck...BEGIN
Audit Files precheck...WARNING
Custom RPMs precheck...BEGIN
Custom RPMs precheck...PASSED
########################## ODAUPGRADEUTIL - PRECHECKS - END ##########################
Use 'odaupgradeutil describe-precheck-report [-j]' to view the precheck report.

Once precheck is OK, you can detach:

./odaupgradeutil detach-node
*********
IMPORTANT
*********
odaupgradeutil will bring down the databases and grid services on the system.
The files that belong to the databases, which are stored on ASM or ACFS,
are left intact on the storage. The databases will be started up back after
re-imaging the ODA system using 'odacli restore-node' commands.
As a good precautionary measure, please backup all the databases on the
system before you start this process. Do not store the backup on this ODA
machine since the local file system will be wiped out as part of the re-image.
*********
IMPORTANT
*********
Do you want to continue? [y/n]: y
########################## ODAUPGRADEUTIL - SAVECONF - BEGIN ##########################
Please check /opt/oracle/oak/restore/log/odaupgradeutil_saveconf_12-01-2023_10:1:47.log for details.
Backup files to /opt/oracle/oak/restore/bkp...BEGIN
Backup files to /opt/oracle/oak/restore/bkp...SUCCESS
Get provision instance...BEGIN
Get provision instance...SUCCESS
Get network configuration...BEGIN
Get network configuration...SUCCESS
Get databases...BEGIN
  Database Name: DUTS18c
  Oracle Home: /u01/app/oracle/product/18.0/dbhome_1
  Database Name: DUTS12c
  Oracle Home: /u01/app/oracle/product/12.2/dbhome_1
Get databases...SUCCESS
Get Database homes...BEGIN
  Checking Unified Auditing for dbhome '/u01/app/oracle/product/18.0/dbhome_1'
  Unified Auditing is set to TRUE
  Checking Unified Auditing for dbhome '/u01/app/oracle/product/12.2/dbhome_1'
  Unified Auditing is set to TRUE
Get Database homes...SUCCESS
Get Database storages...BEGIN
  Database Name: DUTS18c
    DATA destination: +DATA
    RECO destination: +RECO
    REDO destination: +RECO
    Flash Cache destination:
  Database Name: DUTS12c
    DATA destination: +DATA
    RECO destination: +RECO
    REDO destination: +RECO
    Flash Cache destination:
Get Database storages...SUCCESS
Get Volumes...BEGIN
Get Volumes...SUCCESS
Get Filesystems...BEGIN
Get Filesystems...SUCCESS
Get Quorum Disks...BEGIN
Get Quorum Disks...SUCCESS
SAVECONF: SUCCESS
########################## ODAUPGRADEUTIL - SAVECONF - END ##########################
########################## ODAUPGRADEUTIL - DETACHNODE - BEGIN ##########################
Please check /opt/oracle/oak/restore/log/odaupgradeutil_detachnode_12-01-2023_10:15:01.log for details.
Deconfigure databases...BEGIN
  Database Name: DUTS18c
  Local Instance: DUTS18c
  Local Instance Status: RUNNING
  Stopping database 'DUTS18c'...
  Removing database 'DUTS18c' from CRS...
  Database Name: DUTS12c
  Local Instance: DUTS12c
  Local Instance Status: RUNNING
  Stopping database 'DUTS12c'...
  Removing database 'DUTS12c' from CRS...
Deconfigure databases...SUCCESS
Get DB backup metadata...BEGIN
No backupconfigs found
No backupreports found
Quorum Disks were found
  Quorum disk '/dev/SSD_QRMDSK_p1' is 1024 MB in size, no resizing needed
  Quorum disk '/dev/SSD_QRMDSK_p2' is 1024 MB in size, no resizing needed
Deconfigure Grid Infrastructure...BEGIN
Deconfigure Grid Infrastructure...SUCCESS
Backup quorum disks...
  Backing up quorum disk '/dev/SSD_QRMDSK_p1'
  Backing up quorum disk '/dev/SSD_QRMDSK_p2'
Create serverarchives...BEGIN
  Serverarchive '/opt/oracle/oak/restore/out/serverarchive-oda-x7.zip' created
  Size = 365741 bytes
  SHA256 checksum = c01b39c7a35ccc3b081a3e83d2c71fa9a767ebfeb45c69f08e17dfe3ef375a7b
Create serverarchives...DONE
DETACHNODE: SUCCESS
[CRITICAL] Server data archive file(s) generated at /opt/oracle/oak/restore/out . Please ensure the file(s) are copied outside the ODA system and preserved.
########################## ODAUPGRADEUTIL - DETACHNODE - END ##########################

Backup was generated successfully. Let’s move it to an area outside of ODA.

ls -lrt /opt/oracle/oak/restore/out/
total 368
-rw------- 1 root root     65 Jan 12 10:21 serverarchive-oda-x7.zip.sha256
-rw-r--r-- 1 root root 365741 Jan 12 10:21 serverarchive-oda-x7.zip

cp /opt/oracle/oak/restore/out/serverarchive* /transfer/oda-bkp-dpr

Reimage the node

Reimaging is very easy, first you need to connect the 19.15 ISO from the ILOM console, then choose CDROM for next boot, then do a power cycle. You will need to do that on each node for an HA ODA.

Reimaging takes about 60 minutes to complete.

Once done, your ODA is no more reachable on the network because no network configuration exists on your system.

Configure firstnet

After reimaging is finished, you can connect through ILOM console with root/welcome1.

First step after a normal reimaging is the configure firstnet.

[root@cko1 ~]# /opt/oracle/dcs/bin/odacli configure-firstnet
Select the Interface to configure the network on (bond0 bond1) [bond0]:
Configure DHCP on bond0 (yes/no) [no]:
INFO: You have chosen Static configuration
Use VLAN on bond0 (yes/no) [no]:yes
Configure VLAN on bond0, input VLAN ID [2 - 4094] 1099
INFO: using network interface bond0.1099
Enter the IP address to configure : 200.201.65.100
Enter the Netmask address to configure : 255.255.255.0
Enter the Gateway address to configure[200.201.65.1] :
INFO: Restarting the network
Shutting down interface bond0:  [  OK  ]
Shutting down interface bond1:  [  OK  ]
Shutting down interface ib0:  [  OK  ]
Shutting down interface ib1:  [  OK  ]
Shutting down interface ibbond0:  [  OK  ]
Shutting down loopback interface:  [  OK  ]
Bringing up loopback interface:  [  OK  ]
Bringing up interface bond0:  [  OK  ]
Bringing up interface bond1:  [  OK  ]
Bringing up interface ibbond0:  Determining if ip address 192.168.16.24 is already in use for device ibbond0...
[  OK  ]
Bringing up interface bond0.1099:  Determining if ip address 200.201.65.100 is already in use for device bond0.1099...
[  OK  ]
INFO: Restarting the DCS agent
initdcsagent stop/waiting
initdcsagent start/running, process 23750
[root@cko1 ~]#

Reprovision the appliance

Put back the backup files and register them in the ODA repository, unzip and register the GI clone 19.15, and do a restore node with the -g (grid) option:

odacli update-repository -f /transfer/oda-bkp-dpr/serverarchive-oda-x7.zip

cd /transfer/oracle

unzip p30403673_1915000_Linux-x86-64.zip

odacli update-repository -f /transfer/oracle/odacli-dcs-19.15.0.0.0-220425-GI-19.15.0.0.zip

odacli list-jobs

ID Description Created Status

—————————————- ————————————————————————— ———————————– ———-

b66269aa-e007-4304-8074-7ba7e9c8c5c2 Repository Update Jan 12, 2023 1:00:43 PM UTC Success

f07961fa-4192-489b-9a55-53165a012376 Repository Update Jan 12, 2023 1:10:43 PM UTC Success

odacli restore-node -g

Enter new system password:

Retype new system password:

Enter an initial password for Web Console account (oda-admin):

Retype the password for Web Console account (oda-admin):

User ‘oda-admin’ created successfully…

{

“jobId” : “cdfd2e72-777b-4ccb-a670-17b88c7cc102”,

“status” : “Created”,

“message” : “The system will reboot, if required, to enable the licensed number of CPU cores”,

“reports” : [ ],

“createTimestamp” : “Jan 12, 2023 1:14:19 PM UTC”,

“resourceList” : [ ],

“description” : “Restore node service – GI”,

“updatedTime” : “July 12, 2023 1:14:19 PM UTC”

}

odacli describe-job -i cdfd2e72-777b-4ccb-a670-17b88c7cc102

Job details

—————————————————————-

ID: cdfd2e72-777b-4ccb-a670-17b88c7cc102

Description: Restore node service – GI

Status: Success

Created: Jan 12, 2023 1:14:19 PM CST

Message: The system will reboot, if required, to enable the licensed number of CPU cores

Task Name Start Time End Time Status

—————————————- ———————————– ———————————– ———-

Restore node service creation Jan 12, 2023 1:14:28 PM CST Jan 12, 2023 1:38:26 PM CST Success

Setting up Network Jan 12, 2023 1:14:29 PM CST Jan 12, 2023 1:14:29 PM CST Success

Setting up Vlan Jan 12, 2023 1:14:48 PM CST Jan 12, 2023 1:14:48 PM CST Success

Setting up Network Jan 12, 2023 1:15:08 PM CST Jan 12, 2023 1:15:08 PM CST Success

network update Jan 12, 2023 1:15:32 PM CST Jan 12, 2023 1:15:51 PM CST Success

updating network Jan 12, 2023 1:15:32 PM CST Jan 12, 2023 1:15:51 PM CST Success

Setting up Network Jan 12, 2023 1:15:32 PM CST Jan 12, 2023 1:15:32 PM CST Success

OS usergroup ‘asmdba’creation Jan 12, 2023 1:15:52 PM CST Jan 12, 2023 1:15:52 PM CST Success

OS usergroup ‘asmoper’creation Jan 12, 2023 1:15:52 PM CST Jan 12, 2023 1:15:52 PM CST Success

OS usergroup ‘asmadmin’creation Jan 12, 2023 1:15:52 PM CST Jan 12, 2023 1:15:52 PM CST Success

OS usergroup ‘dba’creation Jan 12, 2023 1:15:52 PM CST Jan 12, 2023 1:15:52 PM CST Success

OS usergroup ‘dbaoper’creation Jan 12, 2023 1:15:52 PM CST Jan 12, 2023 1:15:52 PM CST Success

OS usergroup ‘oinstall’creation Jan 12, 2023 1:15:52 PM CST Jan 12, 2023 1:15:52 PM CST Success

OS user ‘grid’creation Jan 12, 2023 1:15:52 PM CST Jan 12, 2023 1:15:52 PM CST Success

OS user ‘oracle’creation Jan 12, 2023 1:15:52 PM CST Jan 12, 2023 1:15:52 PM CST Success

Default backup policy creation Jan 12, 2023 1:15:52 PM CST Jan 12, 2023 1:15:52 PM CST Success

Backup config metadata persist Jan 12, 2023 1:15:52 PM CST Jan 12, 2023 1:15:52 PM CST Success

Grant permission to RHP files Jan 12, 2023 1:15:52 PM CST Jan 12, 2023 1:15:52 PM CST Success

Add SYSNAME in Env Jan 12, 2023 1:15:52 PM CST Jan 12, 2023 1:15:52 PM CST Success

Install oracle-ahf Jan 12, 2023 1:15:52 PM CST Jan 12, 2023 1:16:53 PM CST Success

Stop DCS Admin Jan 12, 2023 1:16:55 PM CST Jan 12, 2023 1:16:55 PM CST Success

Generate mTLS certificates Jan 12, 2023 1:16:55 PM CST Jan 12, 2023 1:16:56 PM CST Success

Exporting Public Keys Jan 12, 2023 1:16:56 PM CST Jan 12, 2023 1:16:58 PM CST Success

Creating Trust Store Jan 12, 2023 1:16:58 PM CST Jan 12, 2023 1:16:59 PM CST Success

Update config files Jan 12, 2023 1:16:59 PM CST Jan 12, 2023 1:17:00 PM CST Success

Restart DCS Admin Jan 12, 2023 1:17:00 PM CST Jan 12, 2023 1:17:20 PM CST Success

Unzipping storage configuration files Jan 12, 2023 1:17:20 PM CST Jan 12, 2023 1:17:20 PM CST Success

Reloading multipath devices Jan 12, 2023 1:17:20 PM CST Jan 12, 2023 1:17:20 PM CST Success

restart oakd Jan 12, 2023 1:17:20 PM CST Jan 12, 2023 1:17:31 PM CST Success

Reloading multipath devices Jan 12, 2023 1:18:32 PM CST Jan 12, 2023 1:18:32 PM CST Success

restart oakd Jan 12, 2023 1:18:32 PM CST Jan 12, 2023 1:18:42 PM CST Success

Restore Quorum Disks Jan 12, 2023 1:18:42 PM CST Jan 12, 2023 1:18:43 PM CST Success

Creating GI home directories Jan 12, 2023 1:18:43 PM CST Jan 12, 2023 1:18:43 PM CST Success

Extract GI clone Jan 12, 2023 1:18:43 PM CST Jan 12, 2023 1:20:15 PM CST Success

Creating wallet for Root User Jan 12, 2023 1:20:15 PM CST Jan 12, 2023 1:20:20 PM CST Success

Creating wallet for ASM Client Jan 12, 2023 1:20:20 PM CST Jan 12, 2023 1:20:23 PM CST Success

Grid stack creation Jan 12, 2023 1:20:24 PM CST Jan 12, 2023 1:31:53 PM CST Success

GI Restore with RHP Jan 12, 2023 1:20:24 PM CST Jan 12, 2023 1:28:32 PM CST Success

Updating GIHome version Jan 12, 2023 1:28:33 PM CST Jan 12, 2023 1:28:36 PM CST Success

Post cluster OAKD configuration Jan 12, 2023 1:31:53 PM CST Jan 12, 2023 1:34:16 PM CST Success

Mounting disk group DATA Jan 12, 2023 1:34:16 PM CST Jan 12, 2023 1:34:17 PM CST Success

Mounting disk group RECO Jan 12, 2023 1:34:25 PM CST Jan 12, 2023 1:34:33 PM CST Success

Setting ACL for disk groups Jan 12, 2023 1:34:40 PM CST Jan 12, 2023 1:34:44 PM CST Success

Configure export clones resource Jan 12, 2023 1:35:40 PM CST Jan 12, 2023 1:35:41 PM CST Success

Adding Volume COMMONSTORE to Clusterware Jan 12, 2023 1:35:43 PM CST Jan 12, 2023 1:35:47 PM CST Success

Adding Volume DATTSTNOC12 to Clusterware Jan 12, 2023 1:35:47 PM CST Jan 12, 2023 1:35:50 PM CST Success

Adding Volume DATTSTNOC18 to Clusterware Jan 12, 2023 1:35:50 PM CST Jan 12, 2023 1:35:54 PM CST Success

Adding Volume RDOTSTNOC12 to Clusterware Jan 12, 2023 1:35:54 PM CST Jan 12, 2023 1:35:57 PM CST Success

Adding Volume RDOTSTNOC18 to Clusterware Jan 12, 2023 1:35:57 PM CST Jan 12, 2023 1:36:01 PM CST Success

Adding Volume RECO to Clusterware Jan 12, 2023 1:36:01 PM CST Jan 12, 2023 1:36:04 PM CST Success

Enabling Volume(s) Jan 12, 2023 1:36:04 PM CST Jan 12, 2023 1:37:16 PM CST Success

Provisioning service creation Jan 12, 2023 1:38:25 PM CST Jan 12, 2023 1:38:25 PM CST Success

persist new agent state entry Jan 12, 2023 1:38:25 PM CST Jan 12, 2023 1:38:25 PM CST Success

persist new agent state entry Jan 12, 2023 1:38:25 PM CST Jan 12, 2023 1:38:25 PM CST Success Restart Zookeeper and DCS Agent Jan 12, 2023 1:38:25 PM CST Jan 12, 2023 1:38:26 PM CST Success

Reprovision the DB homes and remap the databases

Required clone files can be found in a list:

cat /opt/oracle/oak/restore/metadata/dbVersions.list
# List of all db versions found, to be used for downloading required clones before DB restore
18.8.0.0.191015
12.2.0.4.191015

Add the DB clones to the repository:

odacli update-repository -f /transfer/oracle/odacli-dcs-18.8.0.0.0-191226-DB-12.2.0.4.zip

odacli update-repository -f /transfer/oracle/odacli-dcs-18.8.0.0.0-191226-DB-18.0.0.0.zip

Now it’s possible to remap the database to the DB homes with the restore-node -d (database):

odacli restore-node -d

odacli describe-job -i 18d1e5f8-7c31-4ce7-8241-f7b2ed5673cd

Job details
----------------------------------------------------------------
                     ID:  18d1e5f8-7c31-4ce7-8241-f7b2ed5673cd
            Description:  Restore node service - Database
                 Status:  Success
                Created:  Jan 12, 2023 4:36:29 PM CST
                Message:

Task Name                                Start Time                          End Time                            Status
---------------------------------------- ----------------------------------- ----------------------------------- ----------
Setting up ssh equivalance               Jan 12, 2023 4:36:49 PM CST       Jan 12, 2023 4:36:49 PM CST       Success
DB home creation: OraDB18000_home1       Jan 12, 2023 4:36:50 PM CST       Jan 12, 2023 4:39:31 PM CST       Success
Validating dbHome available space        Jan 12, 2023 4:36:50 PM CST       Jan 12, 2023 4:36:50 PM CST       Success
Creating DbHome Directory                Jan 12, 2023 4:36:50 PM CST       Jan 12, 2023 4:36:50 PM CST       Success
Create required directories              Jan 12, 2023 4:36:50 PM CST       Jan 12, 2023 4:36:50 PM CST       Success
Extract DB clone                         Jan 12, 2023 4:36:50 PM CST       Jan 12, 2023 4:38:15 PM CST       Success
ProvDbHome by using RHP                  Jan 12, 2023 4:38:15 PM CST       Jan 12, 2023 4:39:12 PM CST       Success
Enable DB options                        Jan 12, 2023 4:39:13 PM CST       Jan 12, 2023 4:39:29 PM CST       Success
Creating wallet for DB Client            Jan 12, 2023 4:39:31 PM CST       Jan 12, 2023 4:39:31 PM CST       Success
DB home creation: OraDB12204_home1       Jan 12, 2023 4:39:31 PM CST       Jan 12, 2023 4:42:47 PM CST       Success
Validating dbHome available space        Jan 12, 2023 4:39:31 PM CST       Jan 12, 2023 4:39:31 PM CST       Success
Creating DbHome Directory                Jan 12, 2023 4:39:31 PM CST       Jan 12, 2023 4:39:31 PM CST       Success
Create required directories              Jan 12, 2023 4:39:31 PM CST       Jan 12, 2023 4:39:31 PM CST       Success
Extract DB clone                         Jan 12, 2023 4:39:31 PM CST       Jan 12, 2023 4:41:02 PM CST       Success
ProvDbHome by using RHP                  Jan 12, 2023 4:41:02 PM CST       Jan 12, 2023 4:42:30 PM CST       Success
Enable DB options                        Jan 12, 2023 4:42:30 PM CST       Jan 12, 2023 4:42:40 PM CST       Success
Creating wallet for DB Client            Jan 12, 2023 4:42:46 PM CST       Jan 12, 2023 4:42:47 PM CST       Success
Persist database storage locations       Jan 12, 2023 4:42:47 PM CST       Jan 12, 2023 4:42:47 PM CST       Success
  Save metadata for DUTS18c              Jan 12, 2023 4:42:47 PM CST       Jan 12, 2023 
4:42:47 PM CST       Success
  Save metadata for DUTS12c              Jan 12, 2023 4:42:47 PM CST       Jan 12, 2023 4:42:47 PM CST       Success
Persist database storages                Jan 12, 2023 4:42:47 PM CST       Jan 12, 2023 4:42:47 PM CST       Success
  Save metadata for DUTS18c              Jan 12, 2023 4:42:47 PM CST       Jan 12, 2023 4:42:47 PM CST       Success
  Save metadata for DUTS12c              Jan 12, 2023 4:42:47 PM CST       Jan 12, 2023 4:42:47 PM CST       Success 
Restore database: DUTS18c                Jan 12, 2023 4:42:47 PM CST       Jan 12, 2023 4:44:11 PM CST       Success
  Adding database DUTS18c to GI          Jan 12, 2023 4:42:47 PM CST       Jan 12, 2023 4:42:49 PM CST       Success
  Adding database instance(s) to GI      Jan 12, 2023 4:42:49 PM CST       Jan 12, 2023 4:42:49 PM CST       Success
  Modifying SPFILE for database          Jan 12, 2023 4:42:49 PM CST       Jan 12, 2023 4:43:33 PM CST       Success
  Restore password file for database     Jan 12, 2023 4:43:33 PM CST       Jan 12, 2023 4:43:34 PM CST       Success
  Start instance(s) for database         Jan 12, 2023 4:43:34 PM CST       Jan 12, 2023 4:43:52 PM CST       Success
  Persist metadata for database          Jan 12, 2023 4:43:52 PM CST       Jan 12, 2023 4:43:52 PM CST       Success
  Clear all listeners from Database      Jan 12, 2023 4:43:52 PM CST       Jan 12, 2023 4:43:53 PM CST       Success
  Run SqlPatch                           Jan 12, 2023 4:43:56 PM CST       Jan 12, 2023 4:44:11 PM CST       Success
Restore database: DUTS12c                 Jan 12, 2023 4:44:11 PM CST       Jan 12, 2023 4:46:05 PM CST       Success
  Adding database DUTS12c to GI           Jan 12, 2023 4:44:11 PM CST       Jan 12, 2023 4:44:13 PM CST       Success
  Adding database instance(s) to GI      Jan 12, 2023 4:44:13 PM CST       Jan 12, 2023 4:44:13 PM CST       Success
  Modifying SPFILE for database          Jan 12, 2023 4:44:13 PM CST       Jan 12, 2023 4:45:05 PM CST       Success
  Restore password file for database     Jan 12, 2023 4:45:05 PM CST       Jan 12, 2023 4:45:05 PM CST       Success
  Start instance(s) for database         Jan 12, 2023 4:45:05 PM CST       Jan 12, 2023 4:45:28 PM CST       Success
  Persist metadata for database          Jan 12, 2023 4:45:28 PM CST       Jan 12, 2023 4:45:28 PM CST       Success
  Clear all listeners from Database      Jan 12, 2023 4:45:28 PM CST       Jan 12, 2023 4:45:29 PM CST       Success
  Run SqlPatch                           Jan 12, 2023 4:45:32 PM CST       Jan 12, 2023 4:46:05 PM CST       Success
Restore Object Stores                    Jan 12, 2023 4:47:38 PM CST       Jan 12, 2023 4:47:38 PM CST       Success
Remount NFS backups                      Jan 12, 2023 4:47:38 PM CST       Jan 12, 2023 4:47:38 PM CST       Success
Restore BackupConfigs                    Jan 12, 2023 4:47:38 PM CST       Jan 12, 2023 4:47:38 PM CST       Success
Reattach backupconfigs to DBs            Jan 12, 2023 4:47:38 PM CST       Jan 12, 2023 4:47:39 PM CST       Success
Restore backup reports                   Jan 12, 2023 4:47:39 PM CST       Jan 12, 2023 4:47:39 PM CST       Success

Everything looks OK.

Let’s check databases and pmon process:

odacli list-databases

ID                                       DB Name    DB Type  DB Version           CDB        Class    Shape    Storage    Status        DbHomeID
---------------------------------------- ---------- -------- -------------------- ---------- -------- -------- ---------- ------------ ----------------------------------------
886021e5-9bbf-4a14-9b50-398ddd00bfd0     DUTS18c   SI       18.8.0.0.191015      false      OLTP     odb4     ASM       CONFIGURED   3512b78c-a1c9-42dd-a9b7-ff13d5a587fe
d791001f-b812-49fd-94f5-b11c5f580a30     DUTS12c   SI       12.2.1.4.191015      false      OLTP     odb4     ASM       CONFIGURED   3b10a8ce-bdb4-4d4c-2053-9dac8dff7e61


ps -ef | grep pmon | grep -v grep
oracle     447     1  0 16:45 ?        00:00:00 ora_pmon_DUTS18c
grid      2986     1  0 14:30 ?        00:00:00 asm_pmon_+ASM1
oracle   19304     1  0 16:46 ?        00:00:00 ora_pmon_DUTS12c

Hope this helps you!!!

Disclaimer: “The postings on this site are my own and don’t necessarily represent may actual employer positions, strategies or opinions. The information here was edited to be useful for general purpose, specific data and identifications was removed to allow reach generic audience and to be useful

How to ODA update to 19.17

André Luiz Dutra Ontalba — Fri, 13 Jan 2023 00:06:24 +0000

Today, I’m bringing you an article with the steps to update the ODA version to 19.17.

What’s new?

As usual, this version brings the latest PSUs to database and grid homes with their bug fixes. It also brings the latest 21.8 databases.

The only new features the release note are:

Error correlation in the Browser User Interface (BUI), making a kcross-check between odacli errors and log files from the various components. As you may know, odacli is just an interface on top of classic OS and Oracle tools, and it’s sometimes tough to find the log which refer to the error.

Database patching can now be done at the database level, and not only at the DB home level, with oracle update-database.

Enhanced patching when using Data Guard to limit downtime.

Which ODA is compatible with this 19.17?

The new ODAs X9-2S/L/HA and for sure X8, X7 and X6 series. X5-2HA is still on the compatibility list, so you can keep this old appliance up-to-date.

Is this patch a cumulative one?

This 19.17 can be applied on top of 19.13 or later. I just applied this new patch on an X9 running on 19.13.

Download the patch and clone files

Download the patch and the corresponding clones to be able to apply the complete patch.

You don’t need the ISO file for patching, but I would recommend downloading it (patch 30403643).

Be sure to choose the very latest 19.17 when downloading the clones.

Prepare the patching

Before running prepatch, please check these prerequisites:

filesystems have 20% available free space .
additional rpms manually installed should be removed
revert profile scripts to default’s one (for grid and oracle users)
make sure you planned a downtime, 5 hours being the bare minimum for patching and troubleshooting.
You should use odabr to make snapshots of the important filesystems prior patching.

Version precheck

Start to check current version on all components:

odacli describe-component | grep -v ^$

System Version
---------------
19.13.0.0.0
System node NPMe
---------------
cko-oda1
Local System Version
---------------
19.13.0.0.0
Component                                Installed Version    Available Version
---------------------------------------- -------------------- --------------------
OAK                                       19.13.0.0.0           up-to-date
GI                                        19.13.0.0.211019      up-to-date
DB {
[ OraDB19000_home2,OraDB19000_home3 ]     19.13.0.0.211019      up-to-date
}
DCSCONTROLLER                             19.13.0.0.0           up-to-date
DCSCLI                                    19.13.0.0.0           up-to-date
DCSAGENT                                  19.13.0.0.0           up-to-date
DCSADMIN                                  19.13.0.0.0           up-to-date
OS                                        7.9                   up-to-date
ILOM                                      5.0.2.24.r141466      up-to-date
BIOS                                      41100500              up-to-date
SHARED CONTROLLER FIRMWARE                QDV1RF32              up-to-date
LOCAL DISK FIRMWARE                       0121                  up-to-date
SHARED DISK FIRMWARE                      0121                  up-to-date
HMP                                       2.4.8.0.600           up-to-date

Once the patch will be registered in the ODA repository, the “Available Version” column will be updated with versions provided within the patch.

Prepararing the patch and updating the DCS tools

Copy the patch files on your ODA in a temp directory. Then unzip the files:

cd /transfer/oracle
unzip -o p30403662_1917000_Linux-x86-64.zip  
unzip -o p30403673_1917000_Linux-x86-64.zip  
unzip -o p34753059_1917000_Linux-x86-64.zip

Update the repository

odacli update-repository -f /transfer/oracle/oda-sm-19.17.0.0.0-221126.1-server.zip
odacli describe-job -i "dbacdj43-505f-4f08-acf2-11d78b66945b"

Job details
----------------------------------------------------------------
                     ID:  dbacdj43-505f-4f08-acf2-11d78b66945b
            Description:  Repository Update
                 Status:  Success
                Created:  January 2, 2023 9:55:39 PM CST
                Message:  /transfer/oracle/oda-sm-19.17.0.0.0-221126.1-server.zip

Task NPMe                                Start Time                          End Time                            Status
---------------------------------------- ----------------------------------- ----------------------------------- ----------
Unzip bundle                             Janurary 2, 2023 9:55:40 PM CST     January 2, 2023 9:56:09 PM CST     Success

odacli describe-component | grep -v ^$ 
System Version
---------------
19.13.0.0.0
System node NPMe
---------------
cko-oda1
Local System Version
---------------
19.13.0.0.0
Component                                Installed Version    Available Version
---------------------------------------- -------------------- --------------------
OAK                                       19.13.0.0.0           19.17.0.0.0
GI                                        19.13.0.0.211019      19.17.0.0.221018
DB {
[ OraDB19000_home2,OraDB19000_home3 ]     19.13.0.0.211019      19.17.0.0.221018
}
DCSCONTROLLER                             19.13.0.0.0           19.17.0.0.0
DCSCLI                                    19.13.0.0.0           19.17.0.0.0
DCSAGENT                                  19.13.0.0.0           19.17.0.0.0
DCSADMIN                                  19.13.0.0.0           19.17.0.0.0
OS                                        7.9                   up-to-date
ILOM                                      5.0.2.24.r141466      5.1.0.23.r146986
BIOS                                      41100500              41120100
SHARED CONTROLLER FIRMWARE                QDV1RF32              QDV1RF35
LOCAL DISK FIRMWARE                       0121                  not-available
SHARED DISK FIRMWARE                      0121                  not-available
HMP                                       2.4.8.0.600           2.4.8.9.603






odacli update-repository -f /transfer/oracle/odacli-dcs-19.17.0.0.0-221029-GI-19.17.0.0.zip

odacli describe-job -i " e07fb8f3-e937-44b9-8934-7c1343b1b3ef"

Job details
----------------------------------------------------------------
                     ID:  e07fb8f3-e937-44b9-8934-7c1343b1b3ef
            Description:  Repository Update
                 Status:  Success
                Created:  January 2, 2023 9:56:40 PM CST
                Message:  /transfer/oracle/odacli-dcs-19.17.0.0.0-221029-GI-19.17.0.0.zip

Task NPMe                                Start Time                          End Time                            Status
---------------------------------------- ----------------------------------- ----------------------------------- ----------
Unzip bundle                             January 2, 2023 09:57:45 PM CST    January 2, 2023 09:58:21 PM CST    Success

Update the DCS admin

odacli update-dcsadmin -v 19.17.0.0.0
odacli describe-job -i "1b7ddd74-7580-4480-8584-251932476f35"

Job details
----------------------------------------------------------------
                     ID:  1b7ddd74-7580-4480-8584-251932476f35
            Description:  DcsAdmin patching
                 Status:  Success
                Created:  January 2, 2023 9:59:42 PM CST
                Message:

Task NPMe                                Start Time                          End Time                            Status
---------------------------------------- ----------------------------------- ----------------------------------- ----------
Patch location validation                January 2, 2023 9:59:42 PM CST     January 2, 2023 10:00:42 PM CST     Success
dcs-admin upgrade                        January 2, 2023 9:59:42 PM CST     January 2, 2023 10:00:49 PM CST     Success

Update the DCS components

The command below may take some time as specified in the documentation. So be patient and wait.

This command upgrades Zookeeper, installs MySQL, migrates metadata from Derby to MySQL, and upgrades other DCS components such as the DCS Agent, DCS CLI, and DCS Controller on the Oracle Database Appliance.

odacli update-dcscomponents -v 19.17.0.0.0
This job is interactive
{
  "jobId" : "c3ed2959-82b4-45a4-b7d4-813da9b3aa1a",
  "status" : "Success",
  "message" : "Update-dcscomponents is successful on all the node(s):DCS-Agent shutdown is successful. MySQL upgrade is successful. Metadata migration is done before. Metadata schema update is done. dcsagent RPM upgrade is successful.  dcscli RPM upgrade is successful.  dcscontroller RPM upgrade is successful.  Successfully ran setupAgentAuth.sh zookeeper RPM upgrade is successful.  ",
  "reports" : null,
  "createTimestPMp" : "January 02, 2023 10:03:37 PM CST",
  "description" : "Update-dcscomponents job completed and is not part of Agent job list",
  "updatedTime" : "January 02, 2023 10:05:16 PM CST"
}

Update the DCS Agent

odacli update-dcsagent -v 19.17.0.0.0 odacli describe-job -i “71637667-3dea-4ac4-a2dd-5d9e7726874a” Job details —————————————————————- ID: 71637667-3dea-4ac4-a2dd-5d9e7726874a Description: DcsAgent patching Status: Success Created: January 2, 2023 10:06:21 PM CST Message: Task NPMe Start Time End Time Status —————————————- ———————————– ———————————– ———- Stop DCS Admin January 2, 2023 10:06:22 PM CST January 2, 2023 10:06:22 PM CST Success Generate mTLS certificates January 2, 2023 10:06:22 PM CST January 2, 2023 10:06:23 PM CST Success Exporting Public Keys January 2, 2023 10:06:23 PM CST January 2, 2023 10:06:24 PM CST Success Creating Trust Store January 2, 2023 10:06:24 PM CST January 2, 2023 10:06:26 PM CST Success Update config files January 2, 2023 10:06:26 PM CST January 2, 2023 10:06:26 PM CST Success Restart DCS Admin January 2, 2023 10:06:26 PM CST January 2, 2023 10:06:46 PM CST Success Dcs-agent upgrade to version 19.17.0.0.0 January 2, 2023 10:06:46 PM CST January 2, 2023 10:07:58 PM CST Success Update System version January 2, 2023 10:07:58 PM CST January 2, 2023 10:07:58 PM CST Success

Prepatching report

Before updating the server, we run pre-checks

odacli create-prepatchreport -s -v 19.17.0.0.0
odacli describe-prepatchreport -i a3569c92-beef-46a6-b36d-d7d8c7fb6066


Patch pre-check report
------------------------------------------------------------------------
                 Job ID:  a3569c92-beef-46a6-b36d-d7d8c7fb6066
            Description:  Patch pre-checks for [OS, ILOM, GI, ORACHKSERVER, SERVER]
                 Status:  SUCCESS
                Created:  January 2, 2023 10:23:01 PM CST
                 Result:  All pre-checks succeeded

Node NPMe
---------------
cko-oda1

Pre-Check                      Status   Comments
------------------------------ -------- --------------------------------------
__OS__
Validate supported versions     Success   Validated minimum supported versions.
Validate patching tag           Success   Validated patching tag: 19.17.0.0.0.
Is patch location available     Success   Patch location is available.
Verify OS patch                 Success   Verified OS patch
Validate command execution      Success   Validated command execution

__ILOM__
Validate ILOM server reachable  Success   Successfully connected with ILOM
                                          server using public IP and USB
                                          interconnect
Validate supported versions     Success   Validated minimum supported versions.
Validate patching tag           Success   Validated patching tag: 19.17.0.0.0.
Is patch location available     Success   Patch location is available.
Checking Ilom patch Version     Success   Successfully verified the versions
Patch location validation       Success   Successfully validated location
Validate command execution      Success   Validated command execution

__GI__
Validate GI metadata            Success   Successfully validated GI metadata
Validate supported GI versions  Success   Validated minimum supported versions.
 
Validate available space        Success   Validated free space under /u01
Is clusterware running          Success   Clusterware is running
Validate patching tag           Success   Validated patching tag: 19.17.0.0.0.
Is system provisioned           Success   Verified system is provisioned
Validate ASM in online          Success   ASM is online
Validate kernel log level       Success   Successfully validated the OS log
                                          level
Validate minimum agent version  Success   GI patching enabled in current
                                          DCSAGENT version
Validate Central Inventory      Success   oraInventory validation passed
Validate patching locks         Success   Validated patching locks
Validate clones location exist  Success   Validated clones location
Validate DB start dependencies  Success   DBs START dependency check passed
Validate DB stop dependencies   Success   DBs STOP dependency check passed
Validate space for clones       Success   Clones volume is already created
volume
Evaluate GI patching            Success   Successfully validated GI patching
Validate command execution      Success   Validated command execution

__ORACHK__
Running orachk                  Success   Successfully ran Orachk
Validate command execution      Success   Validated command execution

__SERVER__
Validate local patching         Success   Successfully validated server local
                                          patching
Validate command execution      Success   Validated command execution

Everything is OK to start patching.

Apply the Server update

Let’s start the update-server:

odacli update-server -v 19.17.0.0.0
odacli describe-job -i "59bbb6d2-bf6e-451a-8a4e-1de86c490d26"

Job details
----------------------------------------------------------------
                     ID:  59bbb6d2-bf6e-451a-8a4e-1de86c490d26
            Description:  Server Patching
                 Status:  Success
                Created:  January 2, 2023 10:35:33 PM CST
                Message:  Successfully patched GI with RHP

Task NPMe                                Start Time                          End Time                            Status
---------------------------------------- ----------------------------------- ----------------------------------- ----------
Validating GI user metadata              January 2, 2023 10:35:46 PM CST    January 2, 2023 10:35:46 PM CST    Success
Validate ILOM server reachable           January 2, 2023 10:35:46 PM CST    January 2, 2023 10:35:46 PM CST    Success
Validate DCS Admin mTLS setup            January 2, 2023 10:35:46 PM CST    January 2, 2023 10:35:46 PM CST    Success
Configure export clones resource         January 2, 2023 10:35:47 PM CST    January 2, 2023 10:35:48 PM CST    Success
Creating repositories using yum          January 2, 2023 10:35:48 PM CST    January 2, 2023 10:35:52 PM CST    Success
Updating YumPluginVersionLock rpm        January 2, 2023 10:35:52 PM CST    January 2, 2023 10:35:52 PM CST    Success
Applying OS Patches                      January 2, 2023 10:35:52 PM CST    January 2, 2023 10:46:25 PM CST    Success
Creating repositories using yum          January 2, 2023 10:46:26 PM CST    January 2, 2023 10:46:26 PM CST    Success
Applying HMP Patches                     January 2, 2023 10:46:26 PM CST    January 2, 2023 10:46:46 PM CST    Success
Patch location validation                January 2, 2023 10:46:46 PM CST    January 2, 2023 10:46:46 PM CST    Success
Oda-hw-mgmt upgrade                      January 2, 2023 10:46:47 PM CST    January 2, 2023 10:47:21 PM CST    Success
OSS Patching                             January 2, 2023 10:47:21 PM CST    January 2, 2023 10:47:21 PM CST    Success
Applying Firmware Disk Patches           January 2, 2023 10:47:21 PM CST    January 2, 2023 10:47:23 PM CST    Success
Applying Firmware Controller Patches     January 2, 2023 10:47:24 PM CST    January 2, 2023 10:48:12 PM CST    Success
Checking Ilom patch Version              January 2, 2023 10:48:12 PM CST    January 2, 2023 10:48:13 PM CST    Success
Patch location validation                January 2, 2023 10:48:13 PM CST    January 2, 2023 10:48:13 PM CST    Success
Save password in Wallet                  January 2, 2023 10:48:13 PM CST    January 2, 2023 10:48:13 PM CST    Success
Disabling IPMI v2                        January 2, 2023 10:48:13 PM CST    January 2, 2023 10:48:14 PM CST    Success
Apply Ilom patch                         January 2, 2023 10:48:14 PM CST    January 2, 2023 10:57:11 PM CST    Success
Copying Flash Bios to Temp location      January 2, 2023 10:57:11 PM CST    January 2, 2023 10:57:11 PM CST    Success
Starting the clusterware                 January 2, 2023 10:57:11 PM CST    January 2, 2023 10:58:54 PM CST    Success
Registering image                        January 2, 2023 10:58:54 PM CST    January 2, 2023 10:58:54 PM CST    Success
Registering working copy                 January 2, 2023 10:58:54 PM CST    January 2, 2023 10:58:54 PM CST    Success
Registering image                        January 2, 2023 10:58:54 PM CST    January 2, 2023 10:58:54 PM CST    Success
Creating GI home directories             January 2, 2023 10:58:54 PM CST    January 2, 2023 10:58:54 PM CST    Success
Extract GI clone                         January 2, 2023 10:58:54 PM CST    January 2, 2023 10:58:55 PM CST    Success
Provisioning Software Only GI with RHP   January 2, 2023 10:58:55 PM CST    January 2, 2023 10:58:55 PM CST    Success
Patch GI with RHP                        January 2, 2023 10:58:55 PM CST    January 2, 2023 11:05:10 PM CST    Success
Updating GIHome version                  January 2, 2023 11:05:10 PM CST    January 2, 2023 11:05:14 PM CST    Success
Validate GI availability                 January 2, 2023 11:05:52 PM CST    January 2, 2023 11:05:52 PM CST    Success
Patch KVM CRS type                       January 2, 2023 11:05:52 PM CST    January 2, 2023 11:05:52 PM CST    Success
Patch VM vDisks CRS dependencies         January 2, 2023 11:05:52 PM CST    January 2, 2023 11:05:52 PM CST    Success
Patch DB System domain config            January 2, 2023 11:05:53 PM CST    January 2, 2023 11:05:53 PM CST    Success
Update System version                    January 2, 2023 11:05:53 PM CST    January 2, 2023 11:05:53 PM CST    Success
Cleanup JRE Home                         January 2, 2023 11:05:53 PM CST    January 2, 2023 11:05:53 PM CST    Success
Add SYSNPME in Env                       January 2, 2023 11:05:53 PM CST    January 2, 2023 11:05:53 PM CST    Success
Starting the clusterware                 January 2, 2023 11:05:53 PM CST    January 2, 2023 11:05:53 PM CST    Success
Setting ACL for disk groups              January 2, 2023 11:05:53 PM CST    January 2, 2023 11:05:57 PM CST    Success
Enable LKCE                              January 2, 2023 11:07:50 PM CST    January 2, 2023 11:10:37 PM CST    Success
Update previous workarounds              January 2, 2023 11:10:37 PM CST    January 2, 2023 11:10:37 PM CST    Success
Generating and saving BOM                January 2, 2023 11:10:37 PM CST    January 2, 2023 11:12:32 PM CST    Success
PreRebootNode Actions                    January 2, 2023 11:12:32 PM CST    January 2, 2023 11:13:19 PM CST    Success
Reboot Ilom                              January 2, 2023 11:13:19 PM CST    January 2, 2023 11:13:19 PM CST    Success

The server reboots 5 minutes after the patch ends. On this X9-2M server patching lasted 40 minutes.

Update the existing dbhomes

Time for patching the DB homes depends on the number of DB homes and number of databases.

odacli list-dbhomes
ID                                       NPMe                 DB Version                               Home Location                                 Status
---------------------------------------- -------------------- ---------------------------------------- --------------------------------------------- ----------
7c724f57-a495-4db9-a88a-48323f3632c6     OraDB19000_home2     19.13.0.0.211019                         /u01/app/oracle/product/19.0.0.0/dbhome_2 CONFIGURED
7041785be-d58e-44c6-b51d-d2729a99b8e8     OraDB19000_home3     19.13.0.0.211019                         /u01/app/oracle/product/19.0.0.0/dbhome_3 CONFIGURED

unzip -o p30403662_1917000_Linux-x86-64.zip
odacli update-repository -f /transfer/oracle/odacli-dcs-19.17.0.0.0-221029-DB-19.17.0.0.zip
odacli describe-job -i "ff6d6ad4-de02-432b-b62e-5986146a8eee"

Job details
----------------------------------------------------------------
                     ID:  ff6d6ad4-de02-432b-b62e-5986146a8eee
            Description:  Repository Update
                 Status:  Success
                Created:  January 2, 2023 11:50:02 PM CST
                Message:  /transfer/oracle/odacli-dcs-19.17.0.0.0-221029-DB-19.17.0.0.zip

Task NPMe                                Start Time                          End Time                            Status
---------------------------------------- ----------------------------------- ----------------------------------- ----------
Unzip bundle                             January 2, 2023 11:50:02 PM CST    January 2, 2023 11:50:38 PM CST    Success



odacli update-dbhome -i 7c724f57-a495-4db9-a88a-48323f3632c6 -v 19.17.0.0.0 -f
odacli describe-job -i "cf0d4064-1eb2-4b9a-8653-41fe1f06f98"

Job details
----------------------------------------------------------------
                     ID:  cf0d4064-1eb2-4b9a-8653-41fe1f06f98
            Description:  DB Home Patching: Home Id is 7c724f57-a495-4db9-a88a-48323f3632c6 
                Status:  Success
                Created: January 3, 2023 12:11:31 AM CST
                Message:

Task NPMe                                Start Time                          End Time                            Status
---------------------------------------- ----------------------------------- ----------------------------------- ----------
Creating wallet for DB Client            January 3, 2023 12:12:18 AM CST    January 3, 2023 12:12:18 AM CST    Success
Patch databases by RHP                   January 3, 2023 12:12:18 AM CST    January 3, 2023 12:18:34 AM CST    Success
Updating database metadata               January 3, 2023 12:18:34 AM CST    January 3, 2023 12:18:34 AM CST    Success
Set log_archive_dest for Database        January 3, 2023 12:18:34 AM CST    January 3, 2023 12:18:37 AM CST    Success
Patch databases by RHP                   January 3, 2023 12:18:37 AM CST    January 3, 2023 12:20:09 AM CST    Success
Updating database metadata               January 3, 2023 12:20:09 AM CST    January 3, 2023 12:20:09 AM CST    Success
Set log_archive_dest for Database        January 3, 2023 12:20:09 AM CST    January 3, 2023 12:20:13 AM CST    Success
Patch databases by RHP                   January 3, 2023 12:20:13 AM CST    January 3, 2023 12:25:58 AM CST    Success
Updating database metadata               January 3, 2023 12:25:58 AM CST    January 3, 2023 12:25:58 AM CST    Success
Set log_archive_dest for Database        January 3, 2023 12:25:58 AM CST    January 3, 2023 12:26:00 AM CST    Success
Update System version                    January 3, 2023 12:26:00 AM CST    January 3, 2023 12:26:00 AM CST    Success
Generating and saving BOM                January 3, 2023 12:26:00 AM CST    January 3, 2023 12:28:03 AM CST    Success
TDE parPMeter update                     January 3, 2023 12:28:39 AM CST    January 3, 2023 12:28:39 AM CST    Success

It’s the exact same procedure for the second DB home.

Final checks

Let’s get the final versions:

odacli describe-component | grep -v ^$
System Version
---------------
19.17.0.0.0
System node NPMe
---------------
cko-oda1
Local System Version
---------------
19.17.0.0.0
Component                                Installed Version    Available Version
---------------------------------------- -------------------- --------------------
OAK
                                          19.17.0.0.0           up-to-date
GI
                                          19.17.0.0.221018      up-to-date
DB {
[ OraDB19000_home2,OraDB19000_home3 ]}    19.17.0.0.221018      up-to-date

DCSCONTROLLER
                                          19.17.0.0.0           up-to-date
 
DCSCLI
                                          19.17.0.0.0           up-to-date
DCSAGENT
                                          19.17.0.0.0           up-to-date
DCSADMIN
                                          19.17.0.0.0           up-to-date
OS
                                          7.9                   up-to-date
ILOM
                                          5.1.0.23.r146986      up-to-date
BIOS
                                          41120100              up-to-date
LOCAL CONTROLLER FIRMWARE {
[c6]
                                          80000690              up-to-date
[c7]
                                          214.2.271.9           up-to-date
}
SHARED CONTROLLER FIRMWARE
                                          QDV1RF35              up-to-date
LOCAL DISK FIRMWARE
                                          N2010121              up-to-date
SHARED DISK FIRMWARE
                                          N2010121              up-to-date
HMP
                                          2.4.8.9.603           up-to-date

Hope this helps you!!!

ODA Upgrade 19.x to 19.10

André Luiz Dutra Ontalba — Fri, 09 Jul 2021 09:03:02 +0000

Hoje estou trazendo um artigo com as etapas para atualizar a versão ODA para 19.10.

Antes de começar, devemos verificar a release mínima para que possamos realizar o upgrade com sucesso.

https://docs.oracle.com/en/engineered-systems/oracle-database-appliance/19.10/cmtrn/oda-patches.html#GUID-220DA05B-0F52-4EDA-84C9-BFD15F43802D

Antes de iniciar os patches, certifique-se de ter espaço suficiente nos sistemas de arquivos /, / u01 e / opt.

1. Backup snapshot from ODA

root@oda-duts-01 / # /opt/odabr/odabr backup -snap -osize 35 -rsize 20 -usize 60

INFO: 2021-07-01 10:58:35: Please check the logfile '/opt/odabr/out/log/odabr_53053.log' for more details

│▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│

 odabr - ODA node Backup Restore - Version: 2.0.1-58

 Copyright Oracle, Inc. 2013, 2020

 --------------------------------------------------------

 Author: Ruggero Citton 

 RAC Pack, Cloud Innovation and Solution Engineering Team

│▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│

INFO: 2021-07-01 10:58:35: Checking superuser

INFO: 2021-07-01 10:58:35: Checking Bare Metal

INFO: 2021-07-01 10:58:35: Removing existing LVM snapshots

WARNING: 2021-07-01 10:58:36: LVM snapshot for 'opt' does not exist

WARNING: 2021-07-01 10:58:36: LVM snapshot for 'u01' does not exist

WARNING: 2021-07-01 10:58:36: LVM snapshot for 'root' does not exist

INFO: 2021-07-01 10:58:36: Checking LVM size

INFO: 2021-07-01 10:58:36: Boot device backup

INFO: 2021-07-01 10:58:36: Getting EFI device

INFO: 2021-07-01 10:58:36: ...step1 - unmounting EFI

INFO: 2021-07-01 10:58:36: ...step2 - making efi device backup

SUCCESS: 2021-07-01 10:58:40: ...EFI device backup saved as '/opt/odabr/out/hbi/efi.img'

INFO: 2021-07-01 10:58:40: ...step3 - checking EFI device backup

INFO: 2021-07-01 10:58:40: Getting boot device

INFO: 2021-07-01 10:58:40: ...step1 - making boot device backup using tar

SUCCESS: 2021-07-01 10:58:45: ...boot content saved as '/opt/odabr/out/hbi/boot.tar.gz'

INFO: 2021-07-01 10:58:45: ...step2 - unmounting boot

INFO: 2021-07-01 10:58:45: ...step3 - making boot device backup using dd

SUCCESS: 2021-07-01 10:58:50: ...boot device backup saved as '/opt/odabr/out/hbi/boot.img'

INFO: 2021-07-01 10:58:50: ...step4 - mounting boot

INFO: 2021-07-01 10:58:50: ...step5 - mounting EFI

INFO: 2021-07-01 10:58:50: ...step6 - checking boot device backup

INFO: 2021-07-01 10:58:51: OCR backup

INFO: 2021-07-01 10:58:53: ...ocr backup saved as '/opt/odabr/out/hbi/ocrbackup_53053.bck'

INFO: 2021-07-01 10:58:53: Making LVM snapshot backup

SUCCESS: 2021-07-01 10:58:53: ...snapshot backup for 'opt' created successfully

SUCCESS: 2021-07-01 10:58:55: ...snapshot backup for 'u01' created successfully

SUCCESS: 2021-07-01 10:58:55: ...snapshot backup for 'root' created successfully

SUCCESS: 2021-07-01 10:58:55: LVM snapshots backup done successfully

root@oda-duts-01 / # /opt/odabr/odabr infosnap

│▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│

 odabr - ODA node Backup Restore - Version: 2.0.1-58

 Copyright Oracle, Inc. 2013, 2020

 --------------------------------------------------------

 Author: Ruggero Citton 

 RAC Pack, Cloud Innovation and Solution Engineering Team

│▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│

LVM snap name         Status                COW Size              Data%

-------------         ----------            ----------            ------

root_snap             active                20.00 GiB             0.01%

opt_snap              active                35.00 GiB             0.01%

u01_snap              active                60.00 GiB             0.01%

2. Unzip and update the repository

Para o patch do servidor, você precisará dos seguintes patchs (para download em support.oracle.com)

-p32351355_1910000_Linux-x86-64_1of2.zip
-p32351355_1910000_Linux-x86-64_2of2.zip

As etapas são as seguintes. Todas as ações podem ser encontradas na documentação

2.1 Unpack the two files and then copy them to the oda-duts-01

root@oda-duts-01 /backups # cd patches/

root@oda-duts-01 /backups/patches # ll

total 23037662

-rw-r--r-- 1 root root  3035715218 May 25 10:07 p23494997_1910000_Linux-x86-64.zip

-rw-r--r-- 1 root root 11467982793 May 25 11:18 p32351355_1910000_Linux-x86-64_1of2.zip

-rw-r--r-- 1 root root  9086867187 May 25 09:53 p32351355_1910000_Linux-x86-64_2of2.zip

root@oda-duts-01 /backups/patches # unzip p32351355_1910000_Linux-x86-64_1of2.zip

Archive:  p32351355_1910000_Linux-x86-64_1of2.zip

 extracting: oda-sm-19.10.0.0.0-210222.4-server1of2.zip

  inflating: README.txt

root@oda-duts-01 /backups/patches # unzip p32351355_1910000_Linux-x86-64_2of2.zip

Archive:  p32351355_1910000_Linux-x86-64_2of2.zip

 extracting: oda-sm-19.10.0.0.0-210222.4-server2of2.zip

root@oda-duts-01 /backups/patches # ll

total 43110758

-rw-r--r-- 1 root root 11467982139 Mar 20 22:40 oda-sm-19.10.0.0.0-210222.4-server1of2.zip

-rw-r--r-- 1 root root  9086866837 Mar 20 23:02 oda-sm-19.10.0.0.0-210222.4-server2of2.zip

-rw-r--r-- 1 root root  3035715218 May 25 10:07 p23494997_1910000_Linux-x86-64.zip

-rw-r--r-- 1 root root 11467982793 May 25 11:18 p32351355_1910000_Linux-x86-64_1of2.zip

-rw-r--r-- 1 root root  9086867187 May 25 09:53 p32351355_1910000_Linux-x86-64_2of2.zip

-rwxr-xr-x 1 root root         191 Feb 24 02:17 README.txt

You have new mail in /var/spool/mail/root

root@oda-duts-01 /backups/patches # ll -ltr

total 43110758

-rwxr-xr-x 1 root root         191 Feb 24 02:17 README.txt

-rw-r--r-- 1 root root 11467982139 Mar 20 22:40 oda-sm-19.10.0.0.0-210222.4-server1of2.zip

-rw-r--r-- 1 root root  9086866837 Mar 20 23:02 oda-sm-19.10.0.0.0-210222.4-server2of2.zip

-rw-r--r-- 1 root root  9086867187 May 25 09:53 p32351355_1910000_Linux-x86-64_2of2.zip

-rw-r--r-- 1 root root  3035715218 May 25 10:07 p23494997_1910000_Linux-x86-64.zip

-rw-r--r-- 1 root root 11467982793 May 25 11:18 p32351355_1910000_Linux-x86-64_1of2.zip

You have new mail in /var/spool/mail/root

2.2 Update the repository with the 2 files

root@oda-duts-01 /backups/patches # /opt/oracle/dcs/bin/odacli update-repository -f /backups/patches/oda-sm-19.10.0.0.0-210222.4-server1of2.zip

{

  "jobId" : "ff6d6ad4-de02-432b-b62e-5986146a8eee",

  "status" : "Created",

  "message" : "/backups/patches/oda-sm-19.10.0.0.0-210222.4-server1of2.zip",

  "reports" : [ ],

  "createTimestamp" : "Jul 01, 2021 11:55:02 AM CEST",

  "resourceList" : [ ],

  "description" : "Repository Update",

  "updatedTime" : "Jul 01, 2021 11:55:02 AM CEST"

}

root@oda-duts-01 /backups/patches # odacli describe-job -i ff6d6ad4-de02-432b-b62e-5986146a8eee

Job details

----------------------------------------------------------------

                     ID:  ff6d6ad4-de02-432b-b62e-5986146a8eee

            Description:  Repository Update

                 Status:  Running

                Created:  Jul 01, 2021 11:55:02 AM CEST

                Message:  /backups/patches/oda-sm-19.10.0.0.0-210222.4-server1of2.zip

Task Name                                Start Time                          End Time                            Status

---------------------------------------- ----------------------------------- ----------------------------------- ----------

Job details

----------------------------------------------------------------

                     ID:  ff6d6ad4-de02-432b-b62e-5986146a8eee

            Description:  Repository Update

                 Status:  Success

                Created:  Jul 01, 2021 11:55:02 AM CEST

                Message:  /backups/patches/oda-sm-19.10.0.0.0-210222.4-server1of2.zip

Task Name                                Start Time                          End Time                            Status

---------------------------------------- ----------------------------------- ----------------------------------- ----------

root@oda-duts-01 /backups/patches #

root@oda-duts-01 /backups/patches # /opt/oracle/dcs/bin/odacli update-repository -f /backups/patches/oda-sm-19.10.0.0.0-210222.4-server2of2.zip

{

  "jobId" : "e07fb8f3-e937-44b9-8934-7c1343b1b3ef",

  "status" : "Created",

  "message" : "/backups/patches/oda-sm-19.10.0.0.0-210222.4-server2of2.zip",

  "reports" : [ ],

  "createTimestamp" : "Jul 01, 2021 11:59:48 AM CEST",

  "resourceList" : [ ],

  "description" : "Repository Update",

  "updatedTime" : "Jul 01, 2021 11:59:48 AM CEST"

}

root@oda-duts-01 /backups/patches # odacli describe-job -i e07fb8f3-e937-44b9-8934-7c1343b1b3ef

Job details

----------------------------------------------------------------

                     ID:  e07fb8f3-e937-44b9-8934-7c1343b1b3ef

            Description:  Repository Update

                 Status:  Running

                Created:  Jul 01, 2021 11:59:48 AM CEST

                Message:  /backups/patches/oda-sm-19.10.0.0.0-210222.4-server2of2.zip

Task Name                                Start Time                          End Time                            Status

---------------------------------------- ----------------------------------- ----------------------------------- ----------

root@oda-duts-01 /backups/patches # odacli describe-job -i e07fb8f3-e937-44b9-8934-7c1343b1b3ef

Job details

----------------------------------------------------------------

                     ID:  e07fb8f3-e937-44b9-8934-7c1343b1b3ef

            Description:  Repository Update

                 Status:  Success

                Created:  Jul 01, 2021 11:59:48 AM CEST

                Message:  /backups/patches/oda-sm-19.10.0.0.0-210222.4-server2of2.zip

Task Name                                Start Time                          End Time                            Status

---------------------------------------- ----------------------------------- ----------------------------------- ----------

Após a atualização do repositório, você pode remover os dois arquivos para economizar espaço.

3. Update the DCS admin

root@oda-duts-01 /backups/patches # /opt/oracle/dcs/bin/odacli update-dcsadmin -v 19.10.0.0.0

{

  "jobId" : "03c4fb7f-5de6-425b-bb63-0663180ae488",

  "status" : "Created",

  "message" : null,

  "reports" : [ ],

  "createTimestamp" : "Jul 01, 2021 12:04:50 PM CEST",

  "resourceList" : [ ],

  "description" : "DcsAdmin patching",

  "updatedTime" : "Jul 01, 2021 12:04:50 PM CEST"

}

root@oda-duts-01 /backups/patches # odacli describe-job -i 03c4fb7f-5de6-425b-bb63-0663180ae488




Job details

----------------------------------------------------------------

                     ID:  03c4fb7f-5de6-425b-bb63-0663180ae488

            Description:  DcsAdmin patching

                 Status:  Success

                Created:  Jul 01, 2021 12:04:50 PM CEST

                Message:




Task Name                                Start Time                          End Time                            Status

---------------------------------------- ----------------------------------- ----------------------------------- ----------

Patch location validation                Jul 01, 2021 12:04:51 PM CEST       Jul 01, 2021 12:04:51 PM CEST       Success

dcsadmin upgrade                         Jul 01, 2021 12:04:51 PM CEST       Jul 01, 2021 12:04:52 PM CEST       Success

Update System version                    Jul 01, 2021 12:04:57 PM CEST       Jul 01, 2021 12:04:57 PM CEST       Success

4. Update the DCS components

root@oda-duts-01 /backups/patches # /opt/oracle/dcs/bin/odacli update-dcscomponents -v 19.10.0.0.0

{

  "jobId" : "672e3572-db10-48ea-b737-ae075793c3bb",

  "status" : "Success",

  "message" : "Update-dcscomponents is successful on all the node(s):DCS-Agent shutdown is successful. MySQL upgrade is successful. Timezone is set successfully. Metadata migration is successful. Agent rpm upgrade is successful. DCS-CLI rpm upgrade is successful. DCS-C",

  "reports" : null,

  "createTimestamp" : "Jul 01, 2021 12:07:17 PM CEST",

  "description" : "Update-dcscomponents job completed and is not part of Agent job list",

  "updatedTime" : "Jul 01, 2021 12:09:59 PM CEST"

}

root@oda-duts-01 /backups/patches #

O comando abaixo pode levar algum tempo, conforme especificado na documentação. Portanto, seja paciente e aguarde.

Este comando atualiza o Zookeeper, instala o MySQL, migra metadados do Derby para o MySQL e atualiza outros componentes DCS, como o DCS Agent, DCS CLI e DCS Controller no Oracle Database Appliance.

root@oda-duts-01 /backups/patches # /opt/oracle/dcs/bin/odacli update-dcsagent -v 19.10.0.0.0

{

  "jobId" : "71637667-3dea-4ac4-a2dd-5d9e7726874a",

  "status" : "Created",

  "message": "Dcs agent will be restarted after the update. Please wait for 2-3 mins before executing the other commands",

  "reports" : [ ],

  "createTimestamp" : "Jul 01, 2021 12:12:01 PM CEST",

  "resourceList" : [ ],

  "description" : "DcsAgent patching",

  "updatedTime" : "Jul 01, 2021 12:12:01 PM CEST"

}

root@oda-duts-01 /backups/patches # odacli describe-job -i "71637667-3dea-4ac4-a2dd-5d9e7726874a"

root@oda-duts-01 /backups/patches # odacli describe-job -i "71637667-3dea-4ac4-a2dd-5d9e7726874a"

Job details

----------------------------------------------------------------

                     ID:  71637667-3dea-4ac4-a2dd-5d9e7726874a

            Description:  DcsAgent patching

                 Status:  Running

                Created:  Jul 01, 2021 12:12:01 PM CEST

                Message:

Task Name                                Start Time                          End Time                            Status

---------------------------------------- ----------------------------------- ----------------------------------- ----------

dcs-agent upgrade  to version 19.10.0.0.0 Jul 01, 2021 12:12:01 PM CEST       Jul 01, 2021 12:12:01 PM CEST       Running

root@oda-duts-01 /backups/patches # odacli describe-job -i "71637667-3dea-4ac4-a2dd-5d9e7726874a"

Job details

----------------------------------------------------------------

                     ID:  71637667-3dea-4ac4-a2dd-5d9e7726874a

            Description:  DcsAgent patching

                 Status:  Success

                Created:  Jul 01, 2021 12:12:01 PM CEST

                Message:

Task Name                                Start Time                          End Time                            Status

---------------------------------------- ----------------------------------- ----------------------------------- ----------

dcs-agent upgrade  to version 19.10.0.0.0 Jul 01, 2021 12:12:01 PM CEST       Jul 01, 2021 12:13:36 PM CEST       Success

Update System version                    Jul 01, 2021 12:13:36 PM CEST       Jul 01, 2021 12:13:36 PM CEST       Success

6. Create a precheck report

Antes de atualizar o servidor, executamos as pré-verificações

root@oda-duts-01 /backups/patches # /opt/oracle/dcs/bin/odacli create-prepatchreport -s -v 19.10.0.0.0

Job details

----------------------------------------------------------------

                     ID:  a3569c92-beef-46a6-b36d-d7d8c7fb6066

            Description:  Patch pre-checks for [OS, ILOM, GI, ORACHKSERVER]

                 Status:  Created

                Created:  Jul 01, 2021 12:15:39 PM CEST

                Message:  Use 'odacli describe-prepatchreport -i a3569c92-beef-46a6-b36d-d7d8c7fb6066' to check details of results

Task Name                                Start Time                          End Time                            Status

---------------------------------------- ----------------------------------- ----------------------------------- ----------

root@oda-duts-01 /backups/patches # odacli describe-prepatchreport -i 9d93bb8b-9ede-4deb-9f2d-7c16a2d5abfa

Patch pre-check report

------------------------------------------------------------------------

                 Job ID:  9d93bb8b-9ede-4deb-9f2d-7c16a2d5abfa

            Description:  Patch pre-checks for [OS, ILOM, GI, ORACHKSERVER]

                 Status:  FAILED

                Created:  Jul 01, 2021 1:11:54 PM CEST

                 Result:  One or more pre-checks failed for [ORACHK]

Node Name

---------------

oda-duts-01

Pre-Check                      Status   Comments

------------------------------ -------- --------------------------------------

__OS__

Validate supported versions     Success   Validated minimum supported versions.

Validate patching tag           Success   Validated patching tag: 19.10.0.0.0.

Is patch location available     Success   Patch location is available.

Verify OS patch                 Success   Verified OS patch

Validate command execution      Success   Validated command execution

__ILOM__

Validate supported versions     Success   Validated minimum supported versions.

Validate patching tag           Success   Validated patching tag: 19.10.0.0.0.

Is patch location available     Success   Patch location is available.

Checking Ilom patch Version     Success   Successfully verified the versions

Patch location validation       Success   Successfully validated location

Validate command execution      Success   Validated command execution

__GI__

Validate supported GI versions  Success   Validated minimum supported versions.

Validate available space        Success   Validated free space under /u01

Is clusterware running          Success   Clusterware is running

Validate patching tag           Success   Validated patching tag: 19.10.0.0.0.

Is system provisioned           Success   Verified system is provisioned

Validate ASM in online          Success   ASM is online

Validate minimum agent version  Success   GI patching enabled in current

                                          DCSAGENT version

Validate GI patch metadata      Success   Validated patching tag: 19.10.0.0.0.

Is patch location available     Success   Patch location is available.

Patch location validation       Success   Successfully validated location

Patch verification              Success   Patches 32218454 not applied on GI

                                          home /u01/app/19.0.0.0/grid on node

                                          oda-duts-01

Validate Opatch update          Success   Successfully updated the opatch in

                                          GiHome /u01/app/19.0.0.0/grid on node

                                          oda-duts-01

Patch conflict check            Success   No patch conflicts found on GiHome

                                          /u01/app/19.0.0.0/grid on node

                                          oda-duts-01

Validate command execution      Success   Validated command execution

__ORACHK__

Running orachk                  Failed    Orachk validation failed: .

Validate command execution      Success   Validated command execution

Verify the vm.min_free_kbytes   Failed    AHF-4819: The vm.min_free_kbytes

configuration                             configuration is not set as

                                          recommended

Software home                   Failed    Software home check failed

Nos resultado, podemos ver que existem um erro no oracheck. Com base no seguinte documento:

https://docs.oracle.com/en/engineered-systems/oracle-database-appliance/19.10/cmtrn/issues-with-oda-odacli.html#GUID-F2B10F21-3D1E-4328-8E9B-D75AD38D26A1

O Oracle informou que podemos ignorar os erros e, em seguida, continuar atualizando o servidor.

7. Apply the server update

Como ignoramos o erro, usamos a flag sko para o patch.

root@oda-duts-01 /backups/patches # /opt/oracle/dcs/bin/odacli update-server -v 19.10.0.0.0 -sko

{

  "jobId" : "59bbb6d2-bf6e-451a-8a4e-1de86c490d26",

  "status" : "Created",

  "message" : "Success of server update will trigger reboot of the node after 4-5 minutes. Please wait until the node reboots.",

  "reports" : [ ],

  "createTimestamp" : "Jul 01, 2021 20:23:54 PM CEST",

  "resourceList" : [ ],

  "description" : "Server Patching",

  "updatedTime" : "Jul 01, 2021 20:23:54 PM CEST"

}




root@oda-duts-01 ~ # odacli describe-job -i "59bbb6d2-bf6e-451a-8a4e-1de86c490d26"




Job details

----------------------------------------------------------------

                     ID:  59bbb6d2-bf6e-451a-8a4e-1de86c490d26

            Description:  Server Patching

                 Status:  Success

                Created:  Jul 01, 2021 8:24:34 PM CEST

                Message:




Task Name                                Start Time                          End Time                            Status

---------------------------------------- ----------------------------------- ----------------------------------- ----------

Patch location validation                Jul 01, 2021 8:24:41 PM CEST        Jul 01, 2021 8:24:41 PM CEST        Success

dcs-controller upgrade                   Jul 01, 2021 8:24:42 PM CEST        Jul 01, 2021 8:24:42 PM CEST        Success

Creating repositories using yum          Jul 01, 2021 8:24:43 PM CEST        Jul 01, 2021 8:24:46 PM CEST        Success

Updating YumPluginVersionLock rpm        Jul 01, 2021 8:24:46 PM CEST        Jul 01, 2021 8:24:46 PM CEST        Success

Applying OS Patches                      Jul 01, 2021 8:24:46 PM CEST        Jul 01, 2021 8:24:47 PM CEST        Success

Creating repositories using yum          Jul 01, 2021 8:24:47 PM CEST        Jul 01, 2021 8:24:47 PM CEST        Success

Applying HMP Patches                     Jul 01, 2021 8:24:47 PM CEST        Jul 01, 2021 8:24:48 PM CEST        Success

Client root Set up                       Jul 01, 2021 8:24:48 PM CEST        Jul 01, 2021 8:24:48 PM CEST        Success

Client grid Set up                       Jul 01, 2021 8:24:48 PM CEST        Jul 01, 2021 8:24:48 PM CEST        Success

Patch location validation                Jul 01, 2021 8:24:48 PM CEST        Jul 01, 2021 8:24:48 PM CEST        Success

oda-hw-mgmt upgrade                      Jul 01, 2021 8:24:49 PM CEST        Jul 01, 2021 8:24:49 PM CEST        Success

OSS Patching                             Jul 01, 2021 8:24:50 PM CEST        Jul 01, 2021 8:24:50 PM CEST        Success

Applying Firmware Disk Patches           Jul 01, 2021 8:24:50 PM CEST        Jul 01, 2021 8:24:53 PM CEST        Success

Applying Firmware Controller Patches     Jul 01, 2021 8:24:53 PM CEST        Jul 01, 2021 8:24:55 PM CEST        Success

Checking Ilom patch Version              Jul 01, 2021 8:24:55 PM CEST        Jul 01, 2021 8:24:55 PM CEST        Success

Patch location validation                Jul 01, 2021 8:24:55 PM CEST        Jul 01, 2021 8:24:56 PM CEST        Success

Save password in Wallet                  Jul 01, 2021 8:24:56 PM CEST        Jul 01, 2021 8:24:56 PM CEST        Success

Apply Ilom patch                         Jul 01, 2021 8:24:56 PM CEST        Jul 01, 2021 8:24:56 PM CEST        Success

Copying Flash Bios to Temp location      Jul 01, 2021 8:24:56 PM CEST        Jul 01, 2021 8:24:56 PM CEST        Success

Starting the clusterware                 Jul 01, 2021 8:24:59 PM CEST        Jul 01, 2021 8:24:59 PM CEST        Success

clusterware patch verification           Jul 01, 2021 8:24:59 PM CEST        Jul 01, 2021 8:25:01 PM CEST        Success

Patch location validation                Jul 01, 2021 8:25:01 PM CEST        Jul 01, 2021 8:25:01 PM CEST        Success

Opatch update                            Jul 01, 2021 8:26:32 PM CEST        Jul 01, 2021 8:26:36 PM CEST        Success

Patch conflict check                     Jul 01, 2021 8:26:36 PM CEST        Jul 01, 2021 8:27:29 PM CEST        Success

clusterware upgrade                      Jul 01, 2021 8:27:34 PM CEST        Jul 01, 2021 9:04:18 PM CEST        Success

Updating GiHome version                  Jul 01, 2021 9:04:18 PM CEST        Jul 01, 2021 9:04:21 PM CEST        Success

Starting the clusterware                 Jul 01, 2021 9:05:25 PM CEST        Jul 01, 2021 9:05:25 PM CEST        Success

remove network public interface          Jul 01, 2021 9:05:25 PM CEST        Jul 01, 2021 9:05:28 PM CEST        Success

create bridge network                    Jul 01, 2021 9:05:28 PM CEST        Jul 01, 2021 9:05:33 PM CEST        Success

modify network public interface          Jul 01, 2021 9:05:33 PM CEST        Jul 01, 2021 9:05:34 PM CEST        Success

Update System version                    Jul 01, 2021 9:05:35 PM CEST        Jul 01, 2021 9:05:35 PM CEST        Success

Cleanup JRE Home                         Jul 01, 2021 9:05:35 PM CEST        Jul 01, 2021 9:05:35 PM CEST        Success

Add SYSNAME in Env                       Jul 01, 2021 9:05:35 PM CEST        Jul 01, 2021 9:05:35 PM CEST        Success

Setting ACL for disk groups              Jul 01, 2021 9:05:35 PM CEST        Jul 01, 2021 9:05:38 PM CEST        Success

preRebootNode Actions                    Jul 01, 2021 9:05:44 PM CEST        Jul 01, 2021 9:06:30 PM CEST        Success

Reboot Ilom                              Jul 01, 2021 9:06:30 PM CEST        Jul 01, 2021 9:06:30 PM CEST        Success

Podemos confirmar a atualização executando o seguinte comando

root@oda-duts-01 ~ # odacli describe-component

System Version

---------------

19.10.0.0.0




System node Name

---------------

oda-duts-01




Local System Version

---------------

19.10.0.0.0




Component                                Installed Version    Available Version

---------------------------------------- -------------------- --------------------

OAK                                       19.10.0.0.0           up-to-date




GI                                        19.10.0.0.210119      up-to-date




DB                                        11.2.0.4.200414       11.2.0.4.210119




DCSAGENT                                  19.10.0.0.0           up-to-date




OS                                        7.9                   up-to-date




ILOM                                      5.0.1.21.a.r138015    up-to-date




BIOS                                      41080800              up-to-date




FIRMWARECONTROLLER                        QDV1RF30              up-to-date




FIRMWAREDISK                              0121                  up-to-date




HMP                                       2.4.7.0.1             up-to-date

8. Update the existing dbhomes

root@oda-duts-01 ~ # odacli list-dbhomes




ID                                       Name                 DB Version                               Home Location                                 Status

---------------------------------------- -------------------- ---------------------------------------- --------------------------------------------- ----------

7c724f57-a495-4db9-a88a-48323f3632c6     OraDB11204_home1     11.2.0.4.200414                          /u01/app/oracle/product/11.2.0.4/dbhome_1     CONFIGURED







root@oda-duts-01 ~ # odacli create-prepatchreport --dbhome --dbhomeid 7c724f57-a495-4db9-a88a-48323f3632c6 -v 19.10.0.0.0







root@oda-duts-01 ~ # odacli update-dbhome --dbhomeid 7c724f57-a495-4db9-a88a-48323f3632c6 -v 19.10.0.0.0 -sko

{

  "jobId" : "cf0d4064-1eb2-4b9a-8653-41fe1f06f98a",

  "status" : "Created",

  "message" : null,

  "reports" : [ ],

  "createTimestamp" : "Jul 01, 2021 21:26:05 PM CEST",

  "resourceList" : [ ],

  "description" : "DB Home Patching: Home Id is 7c724f57-a495-4db9-a88a-48323f3632c6",

  "updatedTime" : "Jul 01, 2021 21:26:05 PM CEST"

}

root@oda-duts-01 ~ #

root@oda-duts-01 ~ #




root@oda-duts-01 ~ # odacli describe-job -i "cf0d4064-1eb2-4b9a-8653-41fe1f06f98a"




Job details

----------------------------------------------------------------

                     ID:  cf0d4064-1eb2-4b9a-8653-41fe1f06f98a

            Description:  DB Home Patching: Home Id is 7c724f57-a495-4db9-a88a-48323f3632c6

                 Status:  Success

                Created:  Jul 01, 2021 9:26:05 PM CEST

                Message:  Success




Task Name                                Start Time                          End Time                            Status

---------------------------------------- ----------------------------------- ----------------------------------- ----------

clusterware patch verification           Jul 01, 2021 9:26:19 PM CEST        Jul 01, 2021 9:26:21 PM CEST        Success

Patch conflict check                     Jul 01, 2021 9:26:21 PM CEST        Jul 01, 2021 9:26:21 PM CEST        Success

Patch location validation                Jul 01, 2021 9:26:21 PM CEST        Jul 01, 2021 9:26:21 PM CEST        Success

Opatch update                            Jul 01, 2021 9:27:13 PM CEST        Jul 01, 2021 9:27:17 PM CEST        Success

Patch conflict check                     Jul 01, 2021 9:27:17 PM CEST        Jul 01, 2021 9:27:30 PM CEST        Success

Creating wallet for DB Client            Jul 01, 2021 9:27:58 PM CEST        Jul 01, 2021 9:28:03 PM CEST        Success

db upgrade                               Jul 01, 2021 9:28:03 PM CEST        Jul 01, 2021 9:30:06 PM CEST        Success

SqlPatch upgrade                         Jul 01, 2021 9:30:06 PM CEST        Jul 01, 2021 9:30:07 PM CEST        Success

SqlPatch upgrade                         Jul 01, 2021 9:30:07 PM CEST        Jul 01, 2021 9:30:08 PM CEST        Success

SqlPatch upgrade                         Jul 01, 2021 9:30:08 PM CEST        Jul 01, 2021 9:30:09 PM CEST        Success

SqlPatch upgrade                         Jul 01, 2021 9:30:09 PM CEST        Jul 01, 2021 9:30:10 PM CEST        Success

SqlPatch upgrade                         Jul 01, 2021 9:30:10 PM CEST        Jul 01, 2021 9:30:11 PM CEST        Success

SqlPatch upgrade                         Jul 01, 2021 9:30:11 PM CEST        Jul 01, 2021 9:30:12 PM CEST        Success

SqlPatch upgrade                         Jul 01, 2021 9:30:12 PM CEST        Jul 01, 2021 9:30:13 PM CEST        Success

SqlPatch upgrade                         Jul 01, 2021 9:30:13 PM CEST        Jul 01, 2021 9:30:14 PM CEST        Success

SqlPatch upgrade                         Jul 01, 2021 9:30:14 PM CEST        Jul 01, 2021 9:30:15 PM CEST        Success

SqlPatch upgrade                         Jul 01, 2021 9:30:15 PM CEST        Jul 01, 2021 9:30:16 PM CEST        Success

SqlPatch upgrade                         Jul 01, 2021 9:30:17 PM CEST        Jul 01, 2021 9:30:18 PM CEST        Success

SqlPatch upgrade                         Jul 01, 2021 9:30:18 PM CEST        Jul 01, 2021 9:30:19 PM CEST        Success

Update System version                    Jul 01, 2021 9:30:19 PM CEST        Jul 01, 2021 9:30:19 PM CEST        Success

updating the Database version            Jul 01, 2021 9:30:21 PM CEST        Jul 01, 2021 9:30:22 PM CEST        Success

updating the Database version            Jul 01, 2021 9:30:22 PM CEST        Jul 01, 2021 9:30:24 PM CEST        Success

updating the Database version            Jul 01, 2021 9:30:24 PM CEST        Jul 01, 2021 9:30:26 PM CEST        Success

updating the Database version            Jul 01, 2021 9:30:26 PM CEST        Jul 01, 2021 9:30:28 PM CEST        Success

updating the Database version            Jul 01, 2021 9:30:28 PM CEST        Jul 01, 2021 9:30:30 PM CEST        Success

updating the Database version            Jul 01, 2021 9:30:30 PM CEST        Jul 01, 2021 9:30:32 PM CEST        Success

updating the Database version            Jul 01, 2021 9:30:32 PM CEST        Jul 01, 2021 9:30:34 PM CEST        Success

updating the Database version            Jul 01, 2021 9:30:34 PM CEST        Jul 01, 2021 9:30:36 PM CEST        Success

updating the Database version            Jul 01, 2021 9:30:36 PM CEST        Jul 01, 2021 9:30:38 PM CEST        Success

updating the Database version            Jul 01, 2021 9:30:38 PM CEST        Jul 01, 2021 9:30:40 PM CEST        Success

updating the Database version            Jul 01, 2021 9:30:40 PM CEST        Jul 01, 2021 9:30:41 PM CEST        Success

updating the Database version            Jul 01, 2021 9:30:41 PM CEST        Jul 01, 2021 9:30:43 PM CEST        Success




You have new mail in /var/spool/mail/root

Agora que o patch foi bem-sucedido, podemos excluir o snapshot do oda.

root@oda-duts-01 ~ # /opt/odabr/odabr delsnap

INFO: 2021-07-01 21:33:02: Please check the logfile '/opt/odabr/out/log/odabr_48818.log' for more details




INFO: 2021-07-01 21:33:02: Removing LVM snapshots

INFO: 2021-07-01 21:33:02: ...removing LVM snapshot for 'opt'

SUCCESS: 2021-07-01 21:33:03: ...snapshot for 'opt' removed successfully

INFO: 2021-07-01 21:33:03: ...removing LVM snapshot for 'u01'

SUCCESS: 2021-07-01 21:33:03: ...snapshot for 'u01' removed successfully

INFO: 2021-07-01 21:33:03: ...removing LVM snapshot for 'root'

SUCCESS: 2021-07-01 21:33:03: ...snapshot for 'root' removed successfully

SUCCESS: 2021-07-01 21:33:03: Remove LVM snapshots done successfully

root@oda-duts-01 ~ #

9. Update the repository com o RDBMS clone 19.10

A última etapa é atualizar o repositório com o clone RDBMS 19.10. Para isso, baixe o patch p23494997_1910000_Linux-x86-64.zip. E então descompacte o arquivo e execute o comando:

root@oda-duts-01 /backups/patches # odacli update-repository -f /backups/patches/odacli-dcs-19.10.0.0.0-210115-DB-11.2.0.4.zip

{

  "jobId" : "9e5124ef-670a-41a5-9135-4f1688cad2b7",

  "status" : "Created",

  "message" : "/backups/patches/odacli-dcs-19.10.0.0.0-210115-DB-11.2.0.4.zip",

  "reports" : [ ],

  "createTimestamp" : "Jul 01, 2021 21:38:53 PM CEST",

  "resourceList" : [ ],

  "description" : "Repository Update",

  "updatedTime" : "Jul 01, 2021 21:38:53 PM CEST"

}

root@oda-duts-01 /backups/patches # odacli describe-job -i "9e5124ef-670a-41a5-9135-4f1688cad2b7"




Job details

----------------------------------------------------------------

                     ID:  9e5124ef-670a-41a5-9135-4f1688cad2b7

            Description:  Repository Update

                 Status:  Running

                Created:  Jul 01, 2021 9:38:53 PM CEST

                Message:  /backups/patches/odacli-dcs-19.10.0.0.0-210115-DB-11.2.0.4.zip




Task Name                                Start Time                          End Time                            Status

---------------------------------------- ----------------------------------- ----------------------------------- ----------

Unzip bundle                             Jul 01, 2021 9:38:53 PM CEST        Jul 01, 2021 9:38:53 PM CEST        Running




root@oda-duts-01 /backups/patches # odacli describe-job -i "9e5124ef-670a-41a5-9135-4f1688cad2b7"




Job details

----------------------------------------------------------------

                     ID:  9e5124ef-670a-41a5-9135-4f1688cad2b7

            Description:  Repository Update

                 Status:  Success

                Created:  Jul 01, 2021 9:38:53 PM CEST

                Message:  /backups/patches/odacli-dcs-19.10.0.0.0-210115-DB-11.2.0.4.zip




Task Name                                Start Time                          End Time                            Status

---------------------------------------- ----------------------------------- ----------------------------------- ----------

Unzip bundle                             Jul 01, 2021 9:38:53 PM CEST        Jul 01, 2021 9:39:36 PM CEST        Success

Espero que isso ajude você!!!

Fique ligado, acompanhando no twitter @aontalba e no Linkedin

Falha no opatch com o Error: ‘Archive Action: Source file “$ ORACLE_HOME / .patch_storage / …” does not exist.’

André Luiz Dutra Ontalba — Tue, 15 Sep 2020 11:03:15 +0000

Outro artigo rápido sobre um problema que tive ontem durante um patch de atualização no ODA. Encontrei um erro durante a aplicação do patch no binário do Oracle.

[Sep 14, 2020 2:40:58 PM] [INFO] add CopyAction for olsrelod.sql
[Sep 14, 2020 2:40:58 PM] [INFO] OPatchSessionHelper::sortOnOverlay() Given list - 25897615 25034396 26477255 20370037 21688501 18430870 27435440 24425998
[Sep 14, 2020 2:40:58 PM] [INFO] size of PatchObject list: 8
[Sep 14, 2020 2:40:59 PM] [INFO] Patch 24425998:
Achive Action: Directory "/u01/app/oracle/product/12.1.0.2/dbhome_3/.patch_storage/24425998_Sep_28_2016_12_31_24" does not exists or is not readable.
'oracle.rdbms, 12.1.0.2.0': Cannot update file '/u01/app/oracle/product/12.1.0.2/dbhome_3/lib/libserver12.a' with '/ksfd.o'
[Sep 14, 2020 2:40:59 PM] [INFO] Prerequisite check "CheckRollbackable" on auto-rollback patches failed.
The details are:
Patch 24425998:
Achive Action: Directory "/u01/app/oracle/product/12.1.0.2/dbhome_3/.patch_storage/24425998_Sep_28_2016_12_31_24" does not exists or is not readable.
'oracle.rdbms, 12.1.0.2.0': Cannot update file '/u01/app/oracle/product/12.1.0.2/dbhome_3/lib/libserver12.a' with '/ksfd.o'
[Sep 14, 2020 2:40:59 PM] [SEVERE] OUI-67073:UtilSession failed: Prerequisite check "CheckRollbackable" on auto-rollback patches failed.
[Sep 14, 2020 2:40:59 PM] [INFO] --------------------------------------------------------------------------------
[Sep 14, 2020 2:40:59 PM] [INFO] The following warnings have occurred during OPatch execution:
[Sep 14, 2020 2:40:59 PM] [INFO] 1) OUI-67303:
Patches [ 25897615 25034396 26477255 20370037 21688501 18430870 27435440 24425998 ] will be rolled back.
[Sep 14, 2020 2:40:59 PM] [INFO] 2) OUI-67303:
Patches [ 25897615 25034396 26477255 20370037 21688501 18430870 27435440 24425998 ] will be rolled back.
[Sep 14, 2020 2:40:59 PM] [INFO] --------------------------------------------------------------------------------
[Sep 14, 2020 2:40:59 PM] [INFO] Finishing UtilSession at Mon Sep 14 14:40:59 CEST 2020
[Sep 14, 2020 2:40:59 PM] [INFO] Log file location: /u01/app/oracle/product/12.1.0.2/dbhome_3/cfgtoollogs/opatchauto/core/opatch/opatch2020-09-14_14-39-20PM_1.log

De acordo com o documento: opatch fails with Error: ‘Archive Action: Source file “$ ORACLE_HOME / .patch_storage / …” does not exist.’ or ‘Achive Action: Directory “$ ORACLE_HOME / .patch_storage / …” does not exist or is not readable’. (Doc ID 1244414.1)

O razão do problema é :

Files needed to rollback existing subset patch (es) are missing from $ORACLE_HOME/.patch_storage.

BACKGROUND

When an Oracle software patch is installed, the first step is to place an unmodified copy of each affected $ORACLE_HOME file into a directory under the “$ORACLE_HOME/.patch_storage”. These file copies will be used if the software patch is ever manually, or automatically rolled back.

Bem depois de ver esse erro, fui verificar e ter a certeza de que nada havia sido removido antes do patch.

As únicas soluções suportadas são:

1. The missing directories and files can be restored from a backup of the ORACLE_HOME.

2. If no backups exist then re-install the $ORACLE_HOME.

3. Clone from another ORACLE_HOME of a like installation.

No meu caso, sempre tenho o backup dos seguintes diretórios $ ORACLE_HOME/inventory/oneoffs e $ORACLE_HOME/.patch_storage.

Eu encontrei a pasta do patch /.patch_storage/24425998_Sep_28_2016_12_31_24 que era necessário para realizar o rollback e depois disso o patch foi aplicado com sucesso.

2020-09-15 07:47:04 Patch 29972716 is successfully already applied on the Home: /u01/app/oracle/product/12.1.0.2/db_home3
2020-09-15 07:47:04 SUCCESS: Successfully applied the patch on the Home : /u01/app/oracle/product/12.1.0.2/db_home4, /u01/app/oracle/product/12.1.0.2/db_home1, /u01/app/oracle/product/12.1.0.2/db_home3.

Espero que isso ajude vocês!!!

Fique ligado, acompanhando no twitter @aontalba e no Linkedin

rootupgrade.sh Fails with CRS-1136: Rejecting the rolling upgrade mode change because the cluster is being patched

André Luiz Dutra Ontalba — Fri, 04 Sep 2020 09:28:51 +0000

Ontem, durante uma atualização de um ODA, encontrei um erro durante o processo de atualização do cluster, onde este erro foi apresentado.


.
2020/03/03 14:34:00 CLSRSC-595: Executing upgrade step 8 of 19: 'PreUpgrade'.
2020/03/03 14:34:04 CLSRSC-468: Setting Oracle Clusterware and ASM to rolling migration mode
2020/03/03 14:34:32 CLSRSC-482: Running command: '/u01/app/12.1.0.2/grid/bin/crsctl start rollingupgrade 18.0.0.0.0'
CRS-1136: Rejecting the rolling upgrade mode change because the cluster is being patched.
CRS-4000: Command Start failed, or completed with errors.
2020/03/03 14:34:32 CLSRSC-511: failed to set Oracle Clusterware and ASM to rolling migration mode
Died at /u01/app/18.0.0.0/grid/crs/install/oraasm.pm line 1455.

Bem, seguindo a nota da Oracle rootupgrade.sh Fails with CRS-1136: Rejecting the rolling upgrade mode change because the cluster is being patched (Doc ID 2494827.1) .

Encontrei a solução para o problema seguindo as etapas abaixo.

Execute os comandos abaixo para identificar as versões de crs, releasepatch e softwarepatch para ver se existe alguma diferença

bash-4.3# crsctl query crs activeversion -f
Oracle Clusterware active version on the cluster is [12.1.0.2.0]. The cluster upgrade state is [ROLLING PATCH]. The cluster active patch level is [2660242823].
bash-4.3#

bash-4.3# crsctl query crs releasepatch
Oracle Clusterware release patch level is [1953265745] and the complete list of patches [23600818 26839277 27001739 27105253 27128906 27144050 27335416 ] have been applied on the local node.
bash-4.3#

bash-4.3# crsctl query crs softwarepatch
Oracle Clusterware patch level on node odatest1 is [1953265745]

Podemos ver que o crs tem uma versão diferente do releasepatch e do softwarepatch.

Muito bem, resolveremos o problema com os seguintes passos:

1 – Execute stop rollingpatch como usuário root, que atualizará o OCR com os valores corretos

/bin/crsctl stop rollingpatch

root@odatest1:~# /u01/app/12.1.0.2/grid/bin/crsctl stop rollingpatch
CRS-1161: The cluster was successfully patched to patch level [1953265745].
root@odatest1:~#

2 – Verifique os níveis do software/release patch e tente rodar novamente o rootupgrade.sh.

bash-4.3# crsctl query crs activeversion -f
Oracle Clusterware active version on the cluster is [12.1.0.2.0]. The cluster upgrade state is [ROLLING PATCH]. The cluster active patch level is [1953265745].
bash-4.3#

bash-4.3# crsctl query crs releasepatch
Oracle Clusterware release patch level is [1953265745] and the complete list of patches [23600818 26839277 27001739 27105253 27128906 27144050 27335416 ] have been applied on the local node.
bash-4.3#

bash-4.3# crsctl query crs softwarepatch
Oracle Clusterware patch level on node odatest1 is [1953265745]

root@odatest1:~# /u01/app/18.0.0.0/grid/rootupgrade.sh

.
.
2020/03/03 15:34:00 CLSRSC-595: Executing upgrade step 8 of 19: 'PreUpgrade'.
2020/03/03 15:34:04 CLSRSC-468: Setting Oracle Clusterware and ASM to rolling migration mode
2020/03/03 15:34:32 CLSRSC-482: Running command: '/u01/app/12.1.0.2/grid/bin/crsctl start rollingupgrade 18.0.0.0.0'
CRS-1131: The cluster was successfully set to rolling upgrade mode.
2020/03/03 15:35:10 CLSRSC-482: Running command: '/u01/app/18.0.0.0/grid/bin/asmca -silent -upgradeNodeASM -nonRolling false -oldCRSHome /u01/app/12.1.0.2/grid -oldCRSVersion 12.1.0.2.0 -firstNode true -startRolling false '

ASM configuration upgraded in local node successfully.

2020/03/03 15:34:20 CLSRSC-469: Successfully set Oracle Clusterware and ASM to rolling migration mode

.
.

2020/03/03 15:54:00 CLSRSC-595: Executing upgrade step 8 of 19: 'UpgradeNode'.

2020/03/03 15:54:04 CLSRSC-474: Initiating upgrade of resource types

2020/03/03 15:56:20 CLSRSC-475: Upgrade of resource types successfully initiated.

2020/03/03 15:56:44 CLSRSC-595: Executing upgrade step 19 of 19: 'PostUpgrade'.

2020/03/03 15:57:05 CLSRSC-325: Configure Oracle Grid Infrastructure for a Cluster ... succeeded

Espero que isso ajude você!!!

Fique ligado, acompanhando no twitter @aontalba e no Linkedin

COMO REMOVER HAIP NO ODA 18.8.0.0.0

André Luiz Dutra Ontalba — Fri, 17 Jul 2020 08:06:45 +0000

Eu precisava remover o HAIP do ODA após migrar para a versão 18.8.0.0.0 e decidi preparar este procedimento.

Esse plano de ação deve exigir apenas uma reinicialização do clusterware versus correção, o que pode resultar em duas ou três reinicializações do clusterware.

Vamos ao procedimento.

1. Backup gpnp profile

[grid@testoda1 peer]$ cd /u01/app/18.0.0.0/grid/gpnp/'hostname'/profiles/peer
[grid@testoda1 peer]$ cp -p profile.xml profile.xml.bkp
[grid@testoda2 peer]$ /u01/app/18.0.0.0/grid/gpnp/'hostname'/profiles/peer
[grid@testoda2 peer]$ cp -p profile.xml profile.xml.bkp

2. Obtenha as interfaces cluster_interconnect (apenas no node 1)

[grid@testoda1 ~]$ /u01/app/18.0.0.0/grid/bin/oifcfg getif

btbond1 10.32.16.0 global public
p1p1 192.168.16.0 global cluster_interconnect,asm
p1p2 192.168.17.0 global cluster_interconnect,asm

Observe: que os nomes de interface privada podem ser diferentes, dependendo do modelo e / ou versão do ODA que foi usada para implantar a máquina etc.

No restante desta nota, estamos usando p1p1 / p1p2 como exemplo nas etapas abaixo.

3. Faça backup de arquivos ifcfg- existentes

[root@testoda1 ~]# cd /etc/sysconfig/network-scripts
[root@testoda1 network-scripts]# cp ifcfg-p1p1 backupifcfgFiles/ifcfg-p1p1.bak
[root@testoda1 network-scripts]# cp ifcfg-p1p2 backupifcfgFiles/ifcfg-p1p2.bak
[root@testoda2 ~]# cd /etc/sysconfig/network-scripts
[root@testoda2 network-scripts]# cp ifcfg-p1p1 backupifcfgFiles/ifcfg-p1p1.bak
[root@testoda2 network-scripts]# cp ifcfg-p1p2 backupifcfgFiles/ifcfg-p1p2.bak

4. Crie ifcfg-icbond0 e modifique os arquivos ifcfg-

[root@testoda1 network-scripts]# vi /etc/sysconfig/network-scripts/ifcfg-icbond0

# This file is automatically created by the ODA software.

DEVICE=icbond0
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
TYPE=BOND
IPV6INIT=no
NM_CONTROLLED=no
PEERDNS=no
MTU=9000
BONDING_OPTS="mode=active-backup miimon=100 primary=p1p1"
IPADDR=192.168.16.24
NETMASK=255.255.255.0

[root@testoda1 network-scripts]# vi /etc/sysconfig/network-scripts/ifcfg-p1p1

# This file is automatically created by the ODA software.

DEVICE=p1p1
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=no
USERCTL=no

# disable generic and large receive offloads on all interfaces,
# to prevent known problems, specifically in bridge configurations.

ETHTOOL_OFFLOAD_OPTS="lro off gro off"
IPV6INIT=no
PEERDNS=no
BOOTPROTO=none
MASTER=icbond0
SLAVE=yes
MTU=9000

[root@testoda1 network-scripts]# vi /etc/sysconfig/network-scripts/ifcfg-p1p2

/etc/sysconfig/network-scripts/ifcfg-p1p2

# This file is automatically created by the ODA software.

DEVICE=p1p2
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=no
USERCTL=no

# disable generic and large receive offloads on all interfaces,
# to prevent known problems, specifically in bridge configurations.

ETHTOOL_OFFLOAD_OPTS="lro off gro off"
IPV6INIT=no
PEERDNS=no
BOOTPROTO=none
MASTER=icbond0
SLAVE=yes
MTU=9000

[root@testoda2 network-scripts]# vi /etc/sysconfig/network-scripts/ifcfg-icbond0

# This file is automatically created by the ODA software.

DEVICE=icbond0
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
TYPE=BOND
IPV6INIT=no
NM_CONTROLLED=no
PEERDNS=no
MTU=9000
BONDING_OPTS="mode=active-backup miimon=100 primary=p1p1"
IPADDR=192.168.16.25
NETMASK=255.255.255.0

[root@testoda2 network-scripts]# vi /etc/sysconfig/network-scripts/ifcfg-p1p1

# This file is automatically created by the ODA software.

DEVICE=p1p1
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=no
USERCTL=no

# disable generic and large receive offloads on all interfaces,
# to prevent known problems, specifically in bridge configurations.

ETHTOOL_OFFLOAD_OPTS="lro off gro off"
IPV6INIT=no
PEERDNS=no
BOOTPROTO=none
MASTER=icbond0
SLAVE=yes
MTU=9000

[root@testoda2 network-scripts]# vi /etc/sysconfig/network-scripts/ifcfg-p1p2

# This file is automatically created by the ODA software.

DEVICE=p1p2
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=no
USERCTL=no

# disable generic and large receive offloads on all interfaces,
# to prevent known problems, specifically in bridge configurations.

ETHTOOL_OFFLOAD_OPTS="lro off gro off"
IPV6INIT=no
PEERDNS=no
BOOTPROTO=none
MASTER=icbond0
SLAVE=yes
MTU=9000

5. Criando / substituindo init.ora-s para instâncias APX

[grid@testoda1]$ echo "+APX1.cluster_interconnects='192.168.16.24'" > $ORACLE_HOME/dbs/init+APX1.ora

[grid@testoda2]$ echo "+APX2.cluster_interconnects='192.168.16.25'" > $ORACLE_HOME/dbs/init+APX2.ora

6. Pare o Clusterware no node 2

[root@testoda2 ~]# /u01/app/18.0.0.0/grid/bin/crsctl stop crs -f

7. Defina a nova interface cluster_interconnect ligada e remova as interfaces p1p1 / p1p2 da configuração (apenas no node 1)

[grid@testoda1 ~]$ oifcfg setif -global icbond0/192.168.16.0:cluster_interconnect,asm

[grid@testoda1 ~]$ oifcfg getif

btbond1 10.209.244.0 global public
p1p1 192.168.16.0 global cluster_interconnect,asm
p1p2 192.168.17.0 global cluster_interconnect,asm
icbond0 192.168.16.0 global cluster_interconnect,asm

[grid@testoda1 ~]$ oifcfg delif -global p1p1/192.168.16.0

[grid@testoda1 ~]$ oifcfg delif -global p1p2/192.168.17.0

[grid@testoda1 ~]$ oifcfg getif

btbond1 10.209.244.0 global public
icbond0 192.168.16.0 global cluster_interconnect,asm

8. Remova a dependência do HAIP no ora.asm

[root@testoda1 ~]# /u01/app/18.0.0.0/grid/bin/crsctl modify res ora.cluster_interconnect.haip -attr ENABLED=0 -init

[root@testoda2 ~]# /u01/app/18.0.0.0/grid/bin/crsctl modify res ora.cluster_interconnect.haip -attr ENABLED=0 -init

[root@testoda1 ~]# /u01/app/18.0.0.0/grid/bin/crsctl modify res ora.asm -attr "START_DEPENDENCIES='hard(ora.cssd,ora.ctssd) pullup(ora.cssd,ora.ctssd) weak(ora.drivers.acfs)', STOP_DEPENDENCIES='hard(intermediate:ora.cssd)'" -init

[root@testoda2 ~]# /u01/app/18.0.0.0/grid/bin/crsctl modify res ora.asm -attr "START_DEPENDENCIES='hard(ora.cssd,ora.ctssd) pullup(ora.cssd,ora.ctssd) weak(ora.drivers.acfs)', STOP_DEPENDENCIES='hard(intermediate:ora.cssd)'" -init

9. Removendo o recurso ora.cluster_interconnect.haip

[root@testoda1 ~]# /u01/app/18.0.0.0/grid/bin/crsctl delete resource ora.cluster_interconnect.haip -init –f

[root@testoda2 ~]# /u01/app/18.0.0.0/grid/bin/crsctl delete resource ora.cluster_interconnect.haip -init –f

10. Pare o Clusterware no node1

[root@testoda1 ~]# /u01/app/18.0.0.0/grid/bin/crsctl stop crs -f

11. Reinicie a rede

[root@testoda1 network-scripts]# service network restart

[root@testoda1 network-scripts]# ifconfig -a

[root@testoda1 network-scripts]# cat /proc/net/bondinf/icbond0

[root@testoda2 network-scripts]# service network restart

[root@testoda2 network-scripts]# ifconfig -a

[root@testoda2 network-scripts]# cat /proc/net/bondinf/icbond0

12. Reinicie o Clusterware

[root@testoda1 ~]# /u01/app/18.0.0.0/grid/bin/crsctl start crs

[root@testoda2 ~]# /u01/app/18.0.0.0/grid/bin/crsctl start crs

13. Reinicie o dcs-agent para redescobrir as interfaces automaticamente

[grid@testoda1 ~]# /opt/oracle/dcs/bin/restartagent.sh

[grid@testoda2 ~]# /opt/oracle/dcs/bin/restartagent.sh

14. Verificando o serviço de cluster após remover o serviço

[root@testoda1 ~]#

[root@testoda1 ~]# /u01/app/18.0.0.0/grid/bin/crsctl check cluster -all
**************************************************************
testoda1:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************
testoda2:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************

Espero ter ajudado com este procedimento

Disclaimer: “The postings on this site are my own and don’t necessarily represent may actual employer positions, strategies or opinions. The information here was edited to be useful for general purpose, specific data and identifications was removed to allow reach generic audience and to be useful.”

Como atualizar o ODA Patch: 18.8.0.0 para ambientes virtualizados (OVM)

André Luiz Dutra Ontalba — Sun, 07 Jun 2020 14:21:39 +0000

Introdução

O objetivo deste documento é descrever passo a passo como atualizar ODA com a configuração de ambiente virtualizado.

Pré-requisitos

Para este Upgrade do ODA você deve está no mínimo na versão 18.3

Oracle Database Appliance Documentation (Check the last version of the patch)

Iniciando o Upgrade

1 – Backup do ODA_BASE (ambos Nodes): Pode levar até 2h00 horas.

No DOM0:

Com o user root:

Node 1:

oakcli stop oda_base
mkdir -p /backup/odax58duts1/odax58duts1_date +"%Y%m%d"
nohup tar -cvzf oakDom1.odax58duts1_dom0.tar.gz /OVS/Repositories/odabaseRepo/VirtualMachines/oakDom1 &

Após completar o backup:

oakcli start oda_base

Node 2:

oakcli stop oda_base
mkdir -p /backup/odax58duts2/odax58duts2_date +"%Y%m%d"
nohup tar -cvzf oakDom1.odax58duts2_dom0.tar.gz /OVS/Repositories/odabaseRepo/VirtualMachines/oakDom1 &

Após completar o backup:

oakcli start oda_base

2 – Baixe patch em um diretório compartilhado ou diretório separado em ambos os servidores ODA:

Com o user: root

mkdir -p /backup/patchODA2020

Baixe todos os arquivos necessários para este diretório:

/backup/patchODA2020

Há 2 arquivos .zip para ser feito download (30518438):

p30518438_188000_Linux-x86-64_1of2.zip
p30518438_188000_Linux-x86-64_2of2.zip

Nota: Devemos garantir uma quantidade mínima de espaço livre (20GB) na ODA BASE, sistemas de arquivos: “/ ” e “/u01”

– Purge logs antigo do ODA, com usuário root:

oakcli manage cleanrepo --ver 18.3.0.0.0
oakcli manage cleanrepo --ver 18.6.0.0.0
/usr/local/bin/purgeODALog -orcl 20 -tfa 10 -osw 10 -oak 10

– Limpe os patches antigos do GRID_HOME, “/u01“:

su -grid
. oraenv
+ASM1 or +ASM2
cd $ORACLE_HOME/OPatch
./opatch util cleanup

– Limpe os patches antigos do ORACLE_HOME, “/u01“:

su - oracle
. oraenv 
cd $ORACLE_HOME/OPatch
./opatch util cleanup

Nota:
– Deve ser realizado a limpeza em todas as versões ORACLE_HOME existentes no servidor.
– Veja o “/home/oracle”, “/home/grid” e “/tmp” para realizar alguma limpeza e liberar algum espaço no sistema de arquivos “/”.

3 – Unpack do patch baixado em ambos os nós ODA:

Node 1:

cd /backup/patchODA2020
 
[root@odax58duts1 patchODA2020]# oakcli unpack -package p30518438_188000_Linux-x86-64_1of2.zip
[root@odax58duts1 patchODA2020]# oakcli unpack -package p30518438_188000_Linux-x86-64_2of2.zip

Node 2:

cd /backup/patchODA2020
 
[root@odax58duts2 patchODA2020]# oakcli unpack -package p30518438_188000_Linux-x86-64_1of2.zip
[root@odax58duts2 patchODA2020]# oakcli unpack -package p30518438_188000_Linux-x86-64_2of2.zip

4 – Verificar e validar componentes ODA para atualização (S.O):

export EXTRA_OS_RPMS_LOC=/backup/patchODA2020
oakcli validate -c ospatch -ver 18.8.0.0.0

e.g: Com erros e conflitos

Inicio do OUTPUT:

NODE 1:

[root@odax58duts1 patchODA2020]# oakcli validate -c ospatch -ver 18.8.0.0.0
INFO: Validating the OS patch for the version 18.8.0.0.0
 
INFO: 2020-06-06 14:06:16: Performing a dry run for OS patching
ERROR: 2020-06-06 14:06:31: Unable to run the command : /usr/bin/yum --exclude=kmod-mpt2sas,ibutils-libs,dapl,libcxgb3,libipathverbs,libmthca,libnes,ofed-docs update --disablerepo=* --enablerepo=ODA_REPOS_LOC -y
ERROR: 2020-06-06 14:06:31: Loaded plugins: rhnplugin, ulninfo, versionlock
This system is not registered with ULN.
You can use uln_register to register.
ULN support will be disabled.
Repository ol6_latest is listed more than once in the configuration
Repository ol6_addons is listed more than once in the configuration
Repository ol6_UEK_latest is listed more than once in the configuration
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package cpupowerutils.x86_64 0:1.3-2.el6 will be updated
---> Package cpupowerutils.x86_64 0:1.3-2.0.1.el6 will be an update
---> Package cups-libs.x86_64 1:1.4.2-79.el6 will be updated
---> Package cups-libs.x86_64 1:1.4.2-81.el6_10 will be an update
---> Package dbus.x86_64 1:1.2.24-9.0.1.el6 will be updated
---> Package dbus.x86_64 1:1.2.24-11.0.1.el6_10 will be an update
---> Package dbus-libs.x86_64 1:1.2.24-9.0.1.el6 will be updated
---> Package dbus-libs.x86_64 1:1.2.24-11.0.1.el6_10 will be an update
---> Package dracut.noarch 0:004-411.0.3.el6 will be updated
---> Package dracut.noarch 0:004-411.0.4.el6 will be an update
---> Package dracut-kernel.noarch 0:004-411.0.3.el6 will be updated
---> Package dracut-kernel.noarch 0:004-411.0.4.el6 will be an update
---> Package glibc.x86_64 0:2.12-1.212.0.2.el6 will be updated
---> Package glibc.x86_64 0:2.12-1.212.0.3.el6_10.3 will be an update
---> Package glibc-common.x86_64 0:2.12-1.212.0.2.el6 will be updated
---> Package glibc-common.x86_64 0:2.12-1.212.0.3.el6_10.3 will be an update
---> Package glibc-devel.i686 0:2.12-1.212.0.2.el6 will be updated
---> Package glibc-devel.x86_64 0:2.12-1.212.0.2.el6 will be updated
---> Package glibc-devel.i686 0:2.12-1.212.0.3.el6_10.3 will be an update
---> Package glibc-devel.x86_64 0:2.12-1.212.0.3.el6_10.3 will be an update
---> Package glibc-headers.x86_64 0:2.12-1.212.0.2.el6 will be updated
---> Package glibc-headers.x86_64 0:2.12-1.212.0.3.el6_10.3 will be an update
---> Package initscripts.x86_64 0:9.03.61-1.0.3.el6 will be updated
---> Package initscripts.x86_64 0:9.03.61-1.0.6.el6 will be an update
---> Package kernel-headers.x86_64 0:2.6.32-754.11.1.el6 will be updated
---> Package kernel-headers.x86_64 0:2.6.32-754.18.2.el6 will be an update
---> Package kernel-uek.x86_64 0:4.1.12-124.33.4.el6uek will be installed
---> Package kernel-uek-firmware.noarch 0:4.1.12-124.33.4.el6uek will be installed
---> Package kexec-tools.x86_64 0:2.0.7-1.0.27.el6 will be updated
---> Package kexec-tools.x86_64 0:2.0.7-1.0.28.el6 will be an update
---> Package ksplice.x86_64 0:1.0.38-1.el6 will be updated
---> Package ksplice.x86_64 0:1.0.43-1.el6 will be an update
---> Package ksplice-core0.x86_64 0:1.0.38-1.el6 will be updated
---> Package ksplice-core0.x86_64 0:1.0.43-1.el6 will be an update
---> Package ksplice-offline.x86_64 0:1.0.38-1.el6 will be updated
---> Package ksplice-offline.x86_64 0:1.0.43-1.el6 will be an update
---> Package ksplice-tools.x86_64 0:1.0.38-1.el6 will be updated
---> Package ksplice-tools.x86_64 0:1.0.43-1.el6 will be an update
---> Package libgudev1.x86_64 0:147-2.73.0.1.el6_8.2 will be updated
---> Package libgudev1.x86_64 0:147-2.73.0.2.el6_8.2 will be an update
---> Package libudev.x86_64 0:147-2.73.0.1.el6_8.2 will be updated
---> Package libudev.x86_64 0:147-2.73.0.2.el6_8.2 will be an update
---> Package mailx.x86_64 0:12.4-8.el6_6 will be updated
---> Package mailx.x86_64 0:12.4-10.el6_10 will be an update
---> Package openssl.x86_64 0:1.0.1e-57.0.6.el6 will be updated
---> Package openssl.x86_64 0:1.0.1e-58.0.1.el6_10 will be an update
---> Package oracle-ofed-release.x86_64 0:1.0.0-50.el6 will be updated
---> Package oracle-ofed-release.x86_64 0:1.0.0-51.el6 will be an update
---> Package perf.x86_64 0:2.6.32-754.11.1.el6 will be updated
---> Package perf.x86_64 0:2.6.32-754.18.2.el6 will be an update
---> Package python.x86_64 0:2.6.6-66.0.1.el6_8 will be updated
---> Package python.x86_64 0:2.6.6-68.0.1.el6_10 will be an update
---> Package python-libs.x86_64 0:2.6.6-66.0.1.el6_8 will be updated
---> Package python-libs.x86_64 0:2.6.6-68.0.1.el6_10 will be an update
---> Package rdma.noarch 2:3.10-3.0.40.el6 will be updated
---> Package rdma.noarch 2:3.10-3.0.41.el6 will be an update
---> Package samba.x86_64 0:3.6.23-51.0.1.el6 will be updated
---> Package samba.x86_64 0:3.6.23-52.0.1.el6_10 will be an update
---> Package samba-client.x86_64 0:3.6.23-51.0.1.el6 will be updated
---> Package samba-client.x86_64 0:3.6.23-52.0.1.el6_10 will be an update
---> Package samba-common.x86_64 0:3.6.23-51.0.1.el6 will be updated
---> Package samba-common.x86_64 0:3.6.23-52.0.1.el6_10 will be an update
---> Package samba-winbind.x86_64 0:3.6.23-51.0.1.el6 will be updated
---> Package samba-winbind.x86_64 0:3.6.23-52.0.1.el6_10 will be an update
---> Package samba-winbind-clients.x86_64 0:3.6.23-51.0.1.el6 will be updated
---> Package samba-winbind-clients.x86_64 0:3.6.23-52.0.1.el6_10 will be an update
---> Package sudo.x86_64 0:1.8.6p3-29.el6_9 will be updated
---> Package sudo.x86_64 0:1.8.6p3-29.0.1.el6_10.2 will be an update
---> Package tzdata.noarch 0:2019a-1.el6 will be updated
---> Package tzdata.noarch 0:2019c-1.el6 will be an update
---> Package tzdata-java.noarch 0:2018e-3.el6 will be updated
---> Package tzdata-java.noarch 0:2019c-1.el6 will be an update
---> Package udev.x86_64 0:147-2.73.0.1.el6_8.2 will be updated
---> Package udev.x86_64 0:147-2.73.0.2.el6_8.2 will be an update
---> Package vim-common.x86_64 2:7.4.629-5.el6_8.1 will be updated
---> Package vim-common.x86_64 2:7.4.629-5.el6_10.2 will be an update
---> Package vim-enhanced.x86_64 2:7.4.629-5.el6_8.1 will be updated
---> Package vim-enhanced.x86_64 2:7.4.629-5.el6_10.2 will be an update
---> Package vim-minimal.x86_64 2:7.4.629-5.el6_8.1 will be updated
---> Package vim-minimal.x86_64 2:7.4.629-5.el6_10.2 will be an update
---> Package xorg-x11-server-Xorg.x86_64 0:1.17.4-17.0.1.el6 will be updated
---> Package xorg-x11-server-Xorg.x86_64 0:1.17.4-17.0.2.el6 will be an update
---> Package xorg-x11-server-common.x86_64 0:1.17.4-17.0.1.el6 will be updated
---> Package xorg-x11-server-common.x86_64 0:1.17.4-17.0.2.el6 will be an update
--> Finished Dependency Resolution
 
Dependencies Resolved
 
================================================================================
 Package                 Arch    Version                   Repository      Size
================================================================================
Installing:
 kernel-uek              x86_64  4.1.12-124.33.4.el6uek    ODA_REPOS_LOC   42 M
 kernel-uek-firmware     noarch  4.1.12-124.33.4.el6uek    ODA_REPOS_LOC  2.6 M
Updating:
 cpupowerutils           x86_64  1.3-2.0.1.el6             ODA_REPOS_LOC   77 k
 cups-libs               x86_64  1:1.4.2-81.el6_10         ODA_REPOS_LOC  322 k
 dbus                    x86_64  1:1.2.24-11.0.1.el6_10    ODA_REPOS_LOC  211 k
 dbus-libs               x86_64  1:1.2.24-11.0.1.el6_10    ODA_REPOS_LOC  127 k
 dracut                  noarch  004-411.0.4.el6           ODA_REPOS_LOC  129 k
 dracut-kernel           noarch  004-411.0.4.el6           ODA_REPOS_LOC   29 k
 glibc                   x86_64  2.12-1.212.0.3.el6_10.3   ODA_REPOS_LOC  3.8 M
 glibc-common            x86_64  2.12-1.212.0.3.el6_10.3   ODA_REPOS_LOC   14 M
 glibc-devel             i686    2.12-1.212.0.3.el6_10.3   ODA_REPOS_LOC  992 k
 glibc-devel             x86_64  2.12-1.212.0.3.el6_10.3   ODA_REPOS_LOC  991 k
 glibc-headers           x86_64  2.12-1.212.0.3.el6_10.3   ODA_REPOS_LOC  620 k
 initscripts             x86_64  9.03.61-1.0.6.el6         ODA_REPOS_LOC  952 k
 kernel-headers          x86_64  2.6.32-754.18.2.el6       ODA_REPOS_LOC  4.6 M
 kexec-tools             x86_64  2.0.7-1.0.28.el6          ODA_REPOS_LOC  339 k
 ksplice                 x86_64  1.0.43-1.el6              ODA_REPOS_LOC  9.1 k
 ksplice-core0           x86_64  1.0.43-1.el6              ODA_REPOS_LOC  271 k
 ksplice-offline         x86_64  1.0.43-1.el6              ODA_REPOS_LOC  7.9 k
 ksplice-tools           x86_64  1.0.43-1.el6              ODA_REPOS_LOC   92 k
 libgudev1               x86_64  147-2.73.0.2.el6_8.2      ODA_REPOS_LOC   65 k
 libudev                 x86_64  147-2.73.0.2.el6_8.2      ODA_REPOS_LOC   78 k
 mailx                   x86_64  12.4-10.el6_10            ODA_REPOS_LOC  235 k
 openssl                 x86_64  1.0.1e-58.0.1.el6_10      ODA_REPOS_LOC  1.5 M
 oracle-ofed-release     x86_64  1.0.0-51.el6              ODA_REPOS_LOC   16 k
 perf                    x86_64  2.6.32-754.18.2.el6       ODA_REPOS_LOC  4.8 M
 python                  x86_64  2.6.6-68.0.1.el6_10       ODA_REPOS_LOC   76 k
 python-libs             x86_64  2.6.6-68.0.1.el6_10       ODA_REPOS_LOC  5.3 M
 rdma                    noarch  2:3.10-3.0.41.el6         ODA_REPOS_LOC   76 k
 samba                   x86_64  3.6.23-52.0.1.el6_10      ODA_REPOS_LOC  5.1 M
 samba-client            x86_64  3.6.23-52.0.1.el6_10      ODA_REPOS_LOC   11 M
 samba-common            x86_64  3.6.23-52.0.1.el6_10      ODA_REPOS_LOC   10 M
 samba-winbind           x86_64  3.6.23-52.0.1.el6_10      ODA_REPOS_LOC  2.2 M
 samba-winbind-clients   x86_64  3.6.23-52.0.1.el6_10      ODA_REPOS_LOC  2.0 M
 sudo                    x86_64  1.8.6p3-29.0.1.el6_10.2   ODA_REPOS_LOC  712 k
 tzdata                  noarch  2019c-1.el6               ODA_REPOS_LOC  507 k
 tzdata-java             noarch  2019c-1.el6               ODA_REPOS_LOC  188 k
 udev                    x86_64  147-2.73.0.2.el6_8.2      ODA_REPOS_LOC  360 k
 vim-common              x86_64  2:7.4.629-5.el6_10.2      ODA_REPOS_LOC  6.7 M
 vim-enhanced            x86_64  2:7.4.629-5.el6_10.2      ODA_REPOS_LOC  1.0 M
 vim-minimal             x86_64  2:7.4.629-5.el6_10.2      ODA_REPOS_LOC  421 k
 xorg-x11-server-Xorg    x86_64  1.17.4-17.0.2.el6         ODA_REPOS_LOC  1.4 M
 xorg-x11-server-common  x86_64  1.17.4-17.0.2.el6         ODA_REPOS_LOC   51 k
 
Transaction Summary
================================================================================
Install       2 Package(s)
Upgrade      41 Package(s)
 
Total download size: 126 M
Downloading Packages:
--------------------------------------------------------------------------------
Total                                           190 MB/s | 126 MB     00:00
Running rpm_check_debug
Running Transaction Test
 
 
Transaction Check Error:
  file /usr/bin/ldd from install of glibc-common-2.12-1.212.0.3.el6_10.3.x86_64 conflicts with file from package glibc-common-2.12-1.212.0.3.el6_10.3.i686
  file /usr/lib/locale/locale-archive.tmpl from install of glibc-common-2.12-1.212.0.3.el6_10.3.x86_64 conflicts with file from package glibc-common-2.12-1.212.0.3.el6_10.3.i686
 
Error Summary
-------------
 
WARNING: 2020-06-06 14:06:31: OS Upgrade is not successful. Need to resolve conflicts
INFO: 2020-06-06 14:06:31: Copy the required RPMs to a location and set EXTRA_OS_RPMS_LOC to that location

Aqui precisamos resolver o problema de dependência, neste caso vamos remover o pacote

[root@odax58duts1 patchODA2020]# rpm -e glibc-common-2.12-1.212.0.3.el6_10.3.i686 --nodeps
You have new mail in /var/spool/mail/root
[root@odax58duts1 patchODA2020]# oakcli validate -c ospatch -ver 18.8.0.0.0
INFO: Validating the OS patch for the version 18.8.0.0.0
 
INFO: 2020-06-06 14:09:51: Performing a dry run for OS patching
INFO: 2020-06-06 14:10:09: No conflict detected during the OS update, dry run check.

NODE 2:

[root@odax58duts2 patchODA2020]# oakcli validate -c ospatch -ver 18.8.0.0.0
INFO: Validating the OS patch for the version 18.8.0.0.0
 
INFO: 2020-06-06 14:15:59: Performing a dry run for OS patching
ERROR: 2020-06-06 14:16:18: Unable to run the command : /usr/bin/yum --exclude=kmod-mpt2sas,ibutils-libs,dapl,libcxgb3,libipathverbs,libmthca,libnes,ofed-docs update --disablerepo=* --enablerepo=ODA_REPOS_LOC -y
ERROR: 2020-06-06 14:16:18: Loaded plugins: rhnplugin, ulninfo, versionlock
This system is not registered with ULN.
You can use uln_register to register.
ULN support will be disabled.
Repository ol6_latest is listed more than once in the configuration
Repository ol6_addons is listed more than once in the configuration
Repository ol6_UEK_latest is listed more than once in the configuration
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package cpupowerutils.x86_64 0:1.3-2.el6 will be updated
---> Package cpupowerutils.x86_64 0:1.3-2.0.1.el6 will be an update
---> Package cups-libs.x86_64 1:1.4.2-79.el6 will be updated
---> Package cups-libs.x86_64 1:1.4.2-81.el6_10 will be an update
---> Package dbus.x86_64 1:1.2.24-9.0.1.el6 will be updated
---> Package dbus.x86_64 1:1.2.24-11.0.1.el6_10 will be an update
---> Package dbus-libs.x86_64 1:1.2.24-9.0.1.el6 will be updated
---> Package dbus-libs.x86_64 1:1.2.24-11.0.1.el6_10 will be an update
---> Package dracut.noarch 0:004-411.0.3.el6 will be updated
---> Package dracut.noarch 0:004-411.0.4.el6 will be an update
---> Package dracut-kernel.noarch 0:004-411.0.3.el6 will be updated
---> Package dracut-kernel.noarch 0:004-411.0.4.el6 will be an update
---> Package glibc.x86_64 0:2.12-1.212.0.2.el6 will be updated
---> Package glibc.x86_64 0:2.12-1.212.0.3.el6_10.3 will be an update
---> Package glibc-devel.i686 0:2.12-1.212.0.2.el6 will be updated
---> Package glibc-devel.x86_64 0:2.12-1.212.0.2.el6 will be updated
---> Package glibc-devel.i686 0:2.12-1.212.0.3.el6_10.3 will be an update
---> Package glibc-devel.x86_64 0:2.12-1.212.0.3.el6_10.3 will be an update
---> Package glibc-headers.x86_64 0:2.12-1.212.0.2.el6 will be updated
---> Package glibc-headers.x86_64 0:2.12-1.212.0.3.el6_10.3 will be an update
---> Package initscripts.x86_64 0:9.03.61-1.0.3.el6 will be updated
---> Package initscripts.x86_64 0:9.03.61-1.0.6.el6 will be an update
---> Package kernel-headers.x86_64 0:2.6.32-754.11.1.el6 will be updated
---> Package kernel-headers.x86_64 0:2.6.32-754.18.2.el6 will be an update
---> Package kernel-uek.x86_64 0:4.1.12-124.33.4.el6uek will be installed
---> Package kernel-uek-firmware.noarch 0:4.1.12-124.33.4.el6uek will be installed
---> Package kexec-tools.x86_64 0:2.0.7-1.0.27.el6 will be updated
---> Package kexec-tools.x86_64 0:2.0.7-1.0.28.el6 will be an update
---> Package ksplice.x86_64 0:1.0.38-1.el6 will be updated
---> Package ksplice.x86_64 0:1.0.43-1.el6 will be an update
---> Package ksplice-core0.x86_64 0:1.0.38-1.el6 will be updated
---> Package ksplice-core0.x86_64 0:1.0.43-1.el6 will be an update
---> Package ksplice-offline.x86_64 0:1.0.38-1.el6 will be updated
---> Package ksplice-offline.x86_64 0:1.0.43-1.el6 will be an update
---> Package ksplice-tools.x86_64 0:1.0.38-1.el6 will be updated
---> Package ksplice-tools.x86_64 0:1.0.43-1.el6 will be an update
---> Package libgudev1.x86_64 0:147-2.73.0.1.el6_8.2 will be updated
---> Package libgudev1.x86_64 0:147-2.73.0.2.el6_8.2 will be an update
---> Package libudev.x86_64 0:147-2.73.0.1.el6_8.2 will be updated
---> Package libudev.x86_64 0:147-2.73.0.2.el6_8.2 will be an update
---> Package mailx.x86_64 0:12.4-8.el6_6 will be updated
---> Package mailx.x86_64 0:12.4-10.el6_10 will be an update
---> Package openssl.x86_64 0:1.0.1e-57.0.6.el6 will be updated
---> Package openssl.x86_64 0:1.0.1e-58.0.1.el6_10 will be an update
---> Package oracle-ofed-release.x86_64 0:1.0.0-50.el6 will be updated
---> Package oracle-ofed-release.x86_64 0:1.0.0-51.el6 will be an update
---> Package perf.x86_64 0:2.6.32-754.11.1.el6 will be updated
---> Package perf.x86_64 0:2.6.32-754.18.2.el6 will be an update
---> Package python.x86_64 0:2.6.6-66.0.1.el6_8 will be updated
---> Package python.x86_64 0:2.6.6-68.0.1.el6_10 will be an update
---> Package python-libs.x86_64 0:2.6.6-66.0.1.el6_8 will be updated
---> Package python-libs.x86_64 0:2.6.6-68.0.1.el6_10 will be an update
---> Package rdma.noarch 2:3.10-3.0.40.el6 will be updated
---> Package rdma.noarch 2:3.10-3.0.41.el6 will be an update
---> Package samba.x86_64 0:3.6.23-51.0.1.el6 will be updated
---> Package samba.x86_64 0:3.6.23-52.0.1.el6_10 will be an update
---> Package samba-client.x86_64 0:3.6.23-51.0.1.el6 will be updated
---> Package samba-client.x86_64 0:3.6.23-52.0.1.el6_10 will be an update
---> Package samba-common.x86_64 0:3.6.23-51.0.1.el6 will be updated
---> Package samba-common.x86_64 0:3.6.23-52.0.1.el6_10 will be an update
---> Package samba-winbind.x86_64 0:3.6.23-51.0.1.el6 will be updated
---> Package samba-winbind.x86_64 0:3.6.23-52.0.1.el6_10 will be an update
---> Package samba-winbind-clients.x86_64 0:3.6.23-51.0.1.el6 will be updated
---> Package samba-winbind-clients.x86_64 0:3.6.23-52.0.1.el6_10 will be an update
---> Package sudo.x86_64 0:1.8.6p3-29.el6_9 will be updated
---> Package sudo.x86_64 0:1.8.6p3-29.0.1.el6_10.2 will be an update
---> Package tzdata.noarch 0:2019a-1.el6 will be updated
---> Package tzdata.noarch 0:2019c-1.el6 will be an update
---> Package tzdata-java.noarch 0:2018e-3.el6 will be updated
---> Package tzdata-java.noarch 0:2019c-1.el6 will be an update
---> Package udev.x86_64 0:147-2.73.0.1.el6_8.2 will be updated
---> Package udev.x86_64 0:147-2.73.0.2.el6_8.2 will be an update
---> Package vim-common.x86_64 2:7.4.629-5.el6_8.1 will be updated
---> Package vim-common.x86_64 2:7.4.629-5.el6_10.2 will be an update
---> Package vim-enhanced.x86_64 2:7.4.629-5.el6_8.1 will be updated
---> Package vim-enhanced.x86_64 2:7.4.629-5.el6_10.2 will be an update
---> Package vim-minimal.x86_64 2:7.4.629-5.el6_8.1 will be updated
---> Package vim-minimal.x86_64 2:7.4.629-5.el6_10.2 will be an update
---> Package xorg-x11-server-Xorg.x86_64 0:1.17.4-17.0.1.el6 will be updated
---> Package xorg-x11-server-Xorg.x86_64 0:1.17.4-17.0.2.el6 will be an update
---> Package xorg-x11-server-common.x86_64 0:1.17.4-17.0.1.el6 will be updated
---> Package xorg-x11-server-common.x86_64 0:1.17.4-17.0.2.el6 will be an update
--> Finished Dependency Resolution
 
Dependencies Resolved
 
================================================================================
 Package                 Arch    Version                   Repository      Size
================================================================================
Installing:
 kernel-uek              x86_64  4.1.12-124.33.4.el6uek    ODA_REPOS_LOC   42 M
 kernel-uek-firmware     noarch  4.1.12-124.33.4.el6uek    ODA_REPOS_LOC  2.6 M
Updating:
 cpupowerutils           x86_64  1.3-2.0.1.el6             ODA_REPOS_LOC   77 k
 cups-libs               x86_64  1:1.4.2-81.el6_10         ODA_REPOS_LOC  322 k
 dbus                    x86_64  1:1.2.24-11.0.1.el6_10    ODA_REPOS_LOC  211 k
 dbus-libs               x86_64  1:1.2.24-11.0.1.el6_10    ODA_REPOS_LOC  127 k
 dracut                  noarch  004-411.0.4.el6           ODA_REPOS_LOC  129 k
 dracut-kernel           noarch  004-411.0.4.el6           ODA_REPOS_LOC   29 k
 glibc                   x86_64  2.12-1.212.0.3.el6_10.3   ODA_REPOS_LOC  3.8 M
 glibc-devel             i686    2.12-1.212.0.3.el6_10.3   ODA_REPOS_LOC  992 k
 glibc-devel             x86_64  2.12-1.212.0.3.el6_10.3   ODA_REPOS_LOC  991 k
 glibc-headers           x86_64  2.12-1.212.0.3.el6_10.3   ODA_REPOS_LOC  620 k
 initscripts             x86_64  9.03.61-1.0.6.el6         ODA_REPOS_LOC  952 k
 kernel-headers          x86_64  2.6.32-754.18.2.el6       ODA_REPOS_LOC  4.6 M
 kexec-tools             x86_64  2.0.7-1.0.28.el6          ODA_REPOS_LOC  339 k
 ksplice                 x86_64  1.0.43-1.el6              ODA_REPOS_LOC  9.1 k
 ksplice-core0           x86_64  1.0.43-1.el6              ODA_REPOS_LOC  271 k
 ksplice-offline         x86_64  1.0.43-1.el6              ODA_REPOS_LOC  7.9 k
 ksplice-tools           x86_64  1.0.43-1.el6              ODA_REPOS_LOC   92 k
 libgudev1               x86_64  147-2.73.0.2.el6_8.2      ODA_REPOS_LOC   65 k
 libudev                 x86_64  147-2.73.0.2.el6_8.2      ODA_REPOS_LOC   78 k
 mailx                   x86_64  12.4-10.el6_10            ODA_REPOS_LOC  235 k
 openssl                 x86_64  1.0.1e-58.0.1.el6_10      ODA_REPOS_LOC  1.5 M
 oracle-ofed-release     x86_64  1.0.0-51.el6              ODA_REPOS_LOC   16 k
 perf                    x86_64  2.6.32-754.18.2.el6       ODA_REPOS_LOC  4.8 M
 python                  x86_64  2.6.6-68.0.1.el6_10       ODA_REPOS_LOC   76 k
 python-libs             x86_64  2.6.6-68.0.1.el6_10       ODA_REPOS_LOC  5.3 M
 rdma                    noarch  2:3.10-3.0.41.el6         ODA_REPOS_LOC   76 k
 samba                   x86_64  3.6.23-52.0.1.el6_10      ODA_REPOS_LOC  5.1 M
 samba-client            x86_64  3.6.23-52.0.1.el6_10      ODA_REPOS_LOC   11 M
 samba-common            x86_64  3.6.23-52.0.1.el6_10      ODA_REPOS_LOC   10 M
 samba-winbind           x86_64  3.6.23-52.0.1.el6_10      ODA_REPOS_LOC  2.2 M
 samba-winbind-clients   x86_64  3.6.23-52.0.1.el6_10      ODA_REPOS_LOC  2.0 M
 sudo                    x86_64  1.8.6p3-29.0.1.el6_10.2   ODA_REPOS_LOC  712 k
 tzdata                  noarch  2019c-1.el6               ODA_REPOS_LOC  507 k
 tzdata-java             noarch  2019c-1.el6               ODA_REPOS_LOC  188 k
 udev                    x86_64  147-2.73.0.2.el6_8.2      ODA_REPOS_LOC  360 k
 vim-common              x86_64  2:7.4.629-5.el6_10.2      ODA_REPOS_LOC  6.7 M
 vim-enhanced            x86_64  2:7.4.629-5.el6_10.2      ODA_REPOS_LOC  1.0 M
 vim-minimal             x86_64  2:7.4.629-5.el6_10.2      ODA_REPOS_LOC  421 k
 xorg-x11-server-Xorg    x86_64  1.17.4-17.0.2.el6         ODA_REPOS_LOC  1.4 M
 xorg-x11-server-common  x86_64  1.17.4-17.0.2.el6         ODA_REPOS_LOC   51 k
 
Transaction Summary
================================================================================
Install       2 Package(s)
Upgrade      40 Package(s)
 
Total download size: 112 M
Downloading Packages:
--------------------------------------------------------------------------------
Total                                           187 MB/s | 112 MB     00:00
Running rpm_check_debug
ERROR with rpm_check_debug vs depsolve:
glibc = 2.12-1.212.0.1.el6 is needed by (installed) nscd-2.12-1.212.0.1.el6.x86_64
** Found 11 pre-existing rpmdb problem(s), 'yum check' output follows:
glibc-2.12-1.212.0.2.el6.x86_64 has missing requires of glibc-common = ('0', '2.12', '1.212.0.2.el6')
glibc-2.12-1.212.0.3.el6_10.3.i686 is a duplicate with glibc-2.12-1.212.0.2.el6.x86_64
libgcc-4.4.7-23.0.1.el6.x86_64 is a duplicate with libgcc-4.4.7-18.el6.i686
nscd-2.12-1.212.0.1.el6.x86_64 has missing requires of glibc = ('0', '2.12', '1.212.0.1.el6')
oak-18.7.0.0.0_LINUX.X64_190915-1.x86_64 has missing requires of libnfsodm18.so()(64bit)
oak-18.7.0.0.0_LINUX.X64_190915-1.x86_64 has missing requires of perl(GridDefParams)
oak-18.7.0.0.0_LINUX.X64_190915-1.x86_64 has missing requires of perl(oakosdiskinfo)
oak-18.7.0.0.0_LINUX.X64_190915-1.x86_64 has missing requires of perl(oaksharedstorageinfo)
oak-18.7.0.0.0_LINUX.X64_190915-1.x86_64 has missing requires of perl(oakstoragetopology)
oak-18.7.0.0.0_LINUX.X64_190915-1.x86_64 has missing requires of perl(ol5_to_ol6_upgrade)
oak-18.7.0.0.0_LINUX.X64_190915-1.x86_64 has missing requires of perl(s_GridSteps)
Your transaction was saved, rerun it with:
 yum load-transaction /tmp/yum_save_tx-2020-06-06-14-16PkHNuJ.yumtx
WARNING: 2020-06-06 14:16:18: OS Upgrade is not successful. Need to resolve conflicts
INFO: 2020-06-06 14:16:18: Copy the required RPMs to a location and set EXTRA_OS_RPMS_LOC to that location

Aqui precisamos resolver o problema de dependência, neste caso vamos remover o pacote

[root@odax58duts2 patchODA2020]# rpm -e nscd-2.12-1.212.0.1.el6 --nodeps
 
 
[root@odax58duts2 patchODA2020]# oakcli validate -c ospatch -ver 18.8.0.0.0
INFO: Validating the OS patch for the version 18.8.0.0.0
 
INFO: 2020-06-06 14:16:38: Performing a dry run for OS patching
INFO: 2020-06-06 14:16:55: No conflict detected during the OS update, dry run check.

Agora temos o ambiente validado para atualização do sistema operacional.

5 – Verifique quais componentes serão necessário para atualizar:

oakcli update -patch 18.8.0.0.0 --verify
e.g:
[root@odax58duts1 patchODA2020]#   oakcli update -patch 18.8.0.0.0 --verify
INFO: 2020-06-06 14:27:34: Reading the metadata file now...
                Component Name            Installed Version         Proposed Patch Version
                ---------------           ------------------        -----------------
                Controller_INT            11.05.03.00               Up-to-date
                Controller_EXT            11.05.03.00               Up-to-date
                Expander                  001E                      Up-to-date
                SSD_SHARED                944A                      Up-to-date
                HDD_LOCAL                 A7E0                      Up-to-date
                HDD_SHARED                A7E0                      Up-to-date
                ILOM                      4.0.4.40 r130079          5.0.0.20 r133445
                BIOS                      25080100                  Up-to-date
                IPMI                      1.8.15.0                  Up-to-date
                HMP                       2.4.5.0.1                 Up-to-date
                OAK                       18.7.0.0.0                18.8.0.0.0
                OL                        6.10                      Up-to-date
                OVM                       3.4.4                     Up-to-date
                GI_HOME                   18.7.0.0.190716           18.8.0.0.191015
                DB_HOME {
                [ OraDb12102_home1 ]      12.1.0.2.190716           12.1.0.2.191015
                [ OraDb11204_home1 ]      11.2.0.4.190716           11.2.0.4.191015
                [ OraDB18Home1 ]          18.7.1.0.191015           18.8.0.0.191015
                [ OraDb11203_home2 ]      11.2.0.3.15               No-update
                             }
 
 
[root@odax58duts2 patchODA2020]#   oakcli update -patch 18.8.0.0.0 --verify
INFO: 2020-06-06 14:27:39: Reading the metadata file now...
                Component Name            Installed Version         Proposed Patch Version
                ---------------           ------------------        -----------------
                Controller_INT            11.05.03.00               Up-to-date
                Controller_EXT            11.05.03.00               Up-to-date
                Expander                  001E                      Up-to-date
                SSD_SHARED                944A                      Up-to-date
                HDD_LOCAL                 A7E0                      Up-to-date
                HDD_SHARED                A7E0                      Up-to-date
                ILOM                      4.0.4.40 r130079          5.0.0.20 r133445
                BIOS                      25080100                  Up-to-date
                IPMI                      1.8.15.0                  Up-to-date
                HMP                       2.4.5.0.1                 Up-to-date
                OAK                       18.7.0.0.0                18.8.0.0.0
                OL                        6.10                      Up-to-date
                OVM                       3.4.4                     Up-to-date
                GI_HOME                   18.7.0.0.190716           18.8.0.0.191015
                DB_HOME {
                [ OraDb12102_home1 ]      12.1.0.2.190716           12.1.0.2.191015
                [ OraDb11204_home1 ]      11.2.0.4.190716           11.2.0.4.191015
                [ OraDB18Home1 ]          18.7.1.0.191015           18.8.0.0.191015
                [ OraDb11203_home2 ]      11.2.0.3.15               No-update

Nota:

– Pare todos os bancos de dados e recursos de clusterware antes de atualizar o ILOM em ambos os servidores

6 – Update ILOM

Prefiro primeiro atualizar o ILOM caso haja um problema durante o patch, para que eu possa acessar o ambiente via ILOM.

Se você quiser atualizar o ILOM com o patch, pode ser sua escolha também.

Nota: Upgrade ILOM: Ambos os nós do ILOM, mas não ao mesmo tempo.

Baixe o ILOM Patch separadamente: Sun Server X5-8 (ILOM 5.0.0.20 133445)

File Name: p30802633_300_Generic.zip

O firmware está dentro deste arquivo .zip no seguinte caminho:

C:\Users\andre.ontalba\Downloads\p30802633_300_Generic\Oracle_Server_X5-8-3.0.0.91223-FIRMWARE_PACK\Firmware\service-processor\ILOM-5_0_0_20_r133445-Oracle_Server_X5-4_X5-8.pkg

Você deve copiar este arquivo para o seguinte diretório abaixo no servidor para um servidor, para ser usado no Upgrade. No meu caso dutsLinux1.

/patch/ILOM

Este arquivo deve ser propriedade de “oracle” usuário e grupo “oinstall”

Conecte-se à máquina de gateway:dutsLinux1

ssh xxxx@dutsLinux1

Conecte-se ao primeiro ILOM a partir da máquina gateway

ssh root@odax58duts1-ilom
Enter remote user password: **********

Confira a versão atual:

e.g:

Digite

  -> version
SP firmware 4.0.4.40
SP firmware build number: 130079
SP firmware date: Thu May 07 09:54:31 CST 2019
SP filesystem version: 0.2.10

Pare a DOM0 e ODA_BASE: (Conectado na ILOM):

stop /SYS

Verifique o status:

show /SYS

e.g: Seção “Properties –> power_state = Off”

Properties:
      type = Host System
      ipmi_name = /SYS
      product_name = SUN SERVER X5-8
      product_part_number = XXXXXXXXXXXXXXX
      product_serial_number = XXXXXXXXXXXXXXX
      product_manufacturer = Oracle Corporation
      fault_state = OK
      clear_fault_action = (none)
      power_state = Off

Carregar nova imagem do ILOM:

load -source scp://xxxx@dutsLinux1/ILOM/ ILOM-5_0_0_20_r133445-Oracle_Server_X5-4_X5-8.pkg

e.g:
load -source scp://root@dutsLinux1/ILOM/ ILOM-5_0_0_20_r133445-Oracle_Server_X5-4_X5-8.pkg
Enter remote user password: **********
 
NOTE: An upgrade takes several minutes to complete. ILOM
      will enter a special mode to load new firmware. No
      other tasks can be performed in ILOM until the
      firmware upgrade is complete and ILOM is reset.
 
    You can choose to postpone the server BIOS upgrade until the
    next server poweroff. If you do not do that, you should
    perform a clean shutdown of the server before continuing.
 
Are you sure you want to load the specified file (y/n)? y
Preserve existing SP configuration (y/n)? y
Preserve existing BIOS configuration (y/n)? y
Delay BIOS upgrade until next server poweroff or reset (y/n)? n
...

Após a reinicialização automática realizada no ILOM, você pode validar o novo firmware e a versão BIOS:

version
Hostname: odax58duts1-ilom
 
-> version
SP firmware 5.0.0.20
SP firmware build number: 133445
SP firmware date: Thr Feb 06 09:54:31 CST 2020
SP filesystem version: 0.2.10

show /SYS/MB/BIOS

Targets:
  Properties:
      type = BIOS
      ipmi_name = MB/BIOS
      fru_name = SYSTEM BIOS
      fru_manufacturer = AMERICAN MEGATRENDS
      fru_version = 25080100
      fru_part_number = APTIO

Inicie a DOM0 e o ODA_BASE depois do upgrade ILOM:

start /SYS
exit

Nota: Repita este procedimento no segundo nó

7 – Atualize servidores ODA

Nota: Execute somente a partir do primeiro servidor e certifique-se de que é o nó mestre: oakcli show ismaster ⇒ “OAKD is in Master Mode”

oakcli update -patch 18.8.0.0.0 –server

e.g:
 
[root@odax58duts2 patchODA2020]# oakcli update -patch 18.8.0.0.0 –server

Este procedimento pode levar entre 2 a 3 horas para ser executado em ambos os nós.

INFO: DB, ASM, Clusterware may be stopped during the patch if required
INFO: Both Nodes may get rebooted automatically during the patch if required
Do you want to continue: [Y/N]?: y
INFO: User has confirmed for the reboot
INFO: Patch bundle must be unpacked on the second Node also before applying the patch
Did you unpack the patch bundle on the second Node? : [Y/N]? : y
INFO: All the VMs except the ODABASE will be shutdown forcefully if needed
Do you want to continue : [Y/N]? : y

Para poder monitorar a aplicação do patch podemos ver os logs nos diretórios abaixo

Log file directory node 1: /opt/oracle/oak/log/odax58duts1/patch/18.8.0.0.0/

Log file directory node 2: /opt/oracle/oak/log/odax58duts2/patch/18.8.0.0.0/

Vamos verificar como está a atualização do servidor

Node 1

[root@odax58duts1 patchODA2020]# oakcli show version -detail
INFO: 2020-06-06 17:17:34: Reading the metadata file now...
                Component Name            Installed Version         Proposed Patch Version
                ---------------           ------------------        -----------------
                Controller_INT            11.05.03.00               Up-to-date
                Controller_EXT            11.05.03.00               Up-to-date
                Expander                  001E                      Up-to-date
                SSD_SHARED                944A                      Up-to-date
                HDD_LOCAL                 A7E0                      Up-to-date
                HDD_SHARED                A7E0                      Up-to-date
                ILOM                      5.0.0.20 r133445          Up-to-date
                BIOS                      25080100                  Up-to-date
                IPMI                      1.8.15.0                  Up-to-date
                HMP                       2.4.5.0.1                 Up-to-date
                OAK                       18.8.0.0.0                Up-to-date
                OL                        6.10                      Up-to-date
                OVM                       3.4.4                     Up-to-date
                GI_HOME                   18.8.0.0.191015           Up-to-date
                DB_HOME {
                [ OraDb12102_home1 ]      12.1.0.2.190716           12.1.0.2.191015
                [ OraDb11204_home1 ]      11.2.0.4.190716           11.2.0.4.191015
                [ OraDB18Home1 ]          18.7.1.0.191015           18.8.0.0.191015
                [ OraDb11203_home2 ]      11.2.0.3.15               No-update

Node 2

[root@odax58duts2 patchODA2020]#   oakcli show version -detail
INFO: 2020-06-06 17:18:39: Reading the metadata file now...
                Component Name            Installed Version         Proposed Patch Version
                ---------------           ------------------        -----------------
                Controller_INT            11.05.03.00               Up-to-date
                Controller_EXT            11.05.03.00               Up-to-date
                Expander                  001E                      Up-to-date
                SSD_SHARED                944A                      Up-to-date
                HDD_LOCAL                 A7E0                      Up-to-date
                HDD_SHARED                A7E0                      Up-to-date
                ILOM                      5.0.0.20 r133445          Up-to-date
                BIOS                      25080100                  Up-to-date
                IPMI                      1.8.15.0                  Up-to-date
                HMP                       2.4.5.0.1                 Up-to-date
                OAK                       18.8.0.0.0                Up-to-date
                OL                        6.10                      Up-to-date
                OVM                       3.4.4                     Up-to-date
                GI_HOME                   18.8.0.0.191015           Up-to-date
                DB_HOME {
                [ OraDb12102_home1 ]      12.1.0.2.190716           12.1.0.2.191015
                [ OraDb11204_home1 ]      11.2.0.4.190716           11.2.0.4.191015
                [ OraDB18Home1 ]          18.7.1.0.191015           18.8.0.0.191015
                [ OraDb11203_home2 ]      11.2.0.3.15               No-update

8 – ODA Patch: Binários de banco de dados

Agora é hora de aplicar patch nos Binários de Banco de Dados Oracle (11.2.0.4,12.1,12.2,18.).

Obtenha a lista de banco de dados e o Oracle Home antes do patch:

oakcli show databases

O primeiro passo é parar o TFA (Ambos os nós com user root)

tfactl stop

Para aplicar o patch nos Binários Oracle: (Execute somente do primeiro nó)

oakcli update -patch 18.8.0.0.0 --database
 
[root@odax58duts1 18.8.0.0.0]# oakcli update -patch 18.8.0.0.0 --database
INFO: Running pre-install scripts
INFO: Running  prepatching on node 0
INFO: Running  prepatching on node 1
INFO: Completed pre-install scripts
...
...
INFO: 2020-06-06 18:51:24: ------------------Patching DB-------------------------
INFO: 2020-06-06 18:51:24: Getting all the possible Database Homes for patching
...
INFO: 2020-06-06 18:52:03: Patching 11.2.0.4 Database Homes on the Node odax58duts1
 
Found the following 11.2.0.4 homes possible for patching:
 
HOME_NAME                      HOME_LOCATION
---------                      -------------
OraDb11204_home1               /u01/app/oracle/product/11.2.0.4/dbhome_1
 
[Please note that few of the above Database Homes may be already up-to-date. They will be automatically ignored]
 
Would you like to patch all the above homes: Y | N ? : Y
INFO: 2020-06-06 18:52:15: Updating OPATCH
Verifying Opatch version for home:.
Expecting version:<11.2.0.3.22>
Opatch version on node  is <11.2.0.3.22>
Opatch version on node  is <11.2.0.3.22>
INFO: 2020-06-06 18:53:41: Performing the conflict checks...
SUCCESS: 2020-06-06 18:53:53: Conflict checks passed for all the Homes
INFO: 2020-06-06 18:53:53: Checking if the patch is already applied on any of the Homes
INFO: 2020-06-06 18:53:58: Home is not Up-to-date
SUCCESS: 2020-06-06 18:53:59: Successfully stopped the Database consoles
SUCCESS: 2020-06-06 18:54:06: Successfully stopped the EM agents
INFO: 2020-06-06 18:54:11: Applying the patch on oracle home : /u01/app/oracle/product/11.2.0.4/dbhome_1 ...
SUCCESS: 2020-06-06 18:56:20: Successfully applied the patch on the Home : /u01/app/oracle/product/11.2.0.4/dbhome_1
SUCCESS: 2020-06-06 18:56:20: Successfully started the Database consoles
SUCCESS: 2020-06-06 18:56:20: Successfully started the EM Agents
INFO: 2020-06-06 18:56:23: Patching 11.2.0.4 Database Homes on the Node odax58duts2
...
INFO: 2020-06-06 19:00:02: Patching 12.1.0.2 Database Homes on the Node odax58duts1
 
 
Found the following 12.1.0.2 homes possible for patching:
 
HOME_NAME                      HOME_LOCATION
---------                      -------------
OraDb12102_home1               /u01/app/oracle/product/12.1.0.2/dbhome_1
 
[Please note that few of the above Database Homes may be already up-to-date. They will be automatically ignored]
 
Would you like to patch all the above homes: Y | N ? : Y
INFO: 2020-06-06 19:06:38: Updating OPATCH
Verifying Opatch version for home:.
Expecting version:<12.2.0.1.18>
Opatch version on node  is <12.2.0.1.18>
Opatch version on node  is <12.2.0.1.18>
INFO: 2020-06-06 19:07:37: Rolling back patches on 12.1.0.2.x home if required...
INFO: 2020-06-06 19:07:43: Checking if any patches need to be rolled back on 
INFO: 2020-06-06 19:11:35: Performing the conflict checks...
SUCCESS: 2020-06-06 19:11:59: Conflict checks passed for all the Homes
INFO: 2020-06-06 19:11:59: Checking if the patch is already applied on any of the Homes
INFO: 2020-06-06 19:12:11: Home is not Up-to-date
SUCCESS: 2020-06-06 19:12:13: Successfully stopped the Database consoles
SUCCESS: 2020-06-06 19:12:19: Successfully stopped the EM agents
INFO: 2020-06-06 19:12:25: Applying patch on /u01/app/oracle/product/12.1.0.2/dbhome_1 Homes
INFO: 2020-06-06 19:12:25: It may take upto 15 mins. Please wait...
SUCCESS: 2020-06-06 19:17:19: Successfully applied the patch on the Home : /u01/app/oracle/product/12.1.0.2/dbhome_1
SUCCESS: 2020-06-06 19:17:19: Successfully started the Database consoles
SUCCESS: 2020-06-06 19:17:19: Successfully started the EM Agents
INFO: 2020-06-06 19:17:23: Patching 12.1.0.2 Database Homes on the Node odax58duts2
...
INFO: 2020-06-06 19:27:08: Patching 18.0.0.0 Database Homes on the Node odax58duts1
 
Found the following 18.0.0.0 homes possible for patching:
 
HOME_NAME                      HOME_LOCATION
---------                      -------------
OraDB18Home1                   /u01/app/oracle/product/18.0.0.0
 
[Please note that few of the above Database Homes may be already up-to-date. They will be automatically ignored]
 
Would you like to patch all the above homes: Y | N ? : Y
INFO: 2020-06-06 19:27:15: Updating OPATCH
Verifying Opatch version for home:.
Expecting version:<12.2.0.1.18>
Opatch version on node  is <12.2.0.1.18>
Opatch version on node  is <12.2.0.1.18>
INFO: 2020-06-06 19:27:26: Rolling back patches on 18.x home if required...
INFO: 2020-06-06 19:27:33: Checking if any patches need to be rolled back on 
INFO: 2020-06-06 19:28:57: Performing the conflict checks...
SUCCESS: 2020-06-06 19:29:57: Conflict checks passed for all the Homes
INFO: 2020-06-06 19:29:57: Checking if the patch is already applied on any of the Homes
INFO: 2020-06-06 19:30:36: Home is not Up-to-date
SUCCESS: 2020-06-06 19:30:38: Successfully stopped the Database consoles
SUCCESS: 2020-06-06 19:30:44: Successfully stopped the EM agents
INFO: 2020-06-06 19:30:49: Applying patch on /u01/app/oracle/product/18.0.0.0 Homes
INFO: 2020-06-06 19:30:49: It may take up to 15 mins. Please wait...
SUCCESS: 2020-06-06 19:40:34: Successfully applied the patch on the Home : /u01/app/oracle/product/18.0.0.0
SUCCESS: 2020-06-06 19:40:34: Successfully started the Database consoles
SUCCESS: 2020-06-06 19:40:34: Successfully started the EM Agents
INFO: 2020-06-06 19:40:37: Patching 18.0.0.0 Database Homes on the Node odax58duts2
 
INFO: DB patching summary on node: odax58duts1
SUCCESS: 2020-06-06 19:52:28:  Successfully applied the patch on the Home /u01/app/oracle/product/11.2.0.4/dbhome_1
SUCCESS: 2020-06-06 19:52:28:  Successfully applied the patch on the Home /u01/app/oracle/product/12.1.0.2/dbhome_1
SUCCESS: 2020-06-06 19:52:28:  Successfully applied the patch on the Home /u01/app/oracle/product/18.0.0.0
 
INFO: DB patching summary on node: odax58duts2
SUCCESS: 2020-06-06 19:52:28:  Successfully applied the patch on the Home /u01/app/oracle/product/11.2.0.4/dbhome_1
SUCCESS: 2020-06-06 19:52:28:  Successfully applied the patch on the Home /u01/app/oracle/product/12.1.0.2/dbhome_1
SUCCESS: 2020-06-06 19:52:28:  Successfully applied the patch on the Home /u01/app/oracle/product/18.0.0.0
 
INFO: Executing /tmp/pending_actions on both nodes
You have new mail in /var/spool/mail/root
 
[root@odax58duts1 18.8.0.0.0]#

Vamos verificar como está a atualização do banco de dados

Node 1

[root@odax58duts1 patchODA2020]# oakcli show version -detail
INFO: 2020-06-06 19:55:34: Reading the metadata file now...
                Component Name            Installed Version         Proposed Patch Version
                ---------------           ------------------        -----------------
                Controller_INT            11.05.03.00               Up-to-date
                Controller_EXT            11.05.03.00               Up-to-date
                Expander                  001E                      Up-to-date
                SSD_SHARED                944A                      Up-to-date
                HDD_LOCAL                 A7E0                      Up-to-date
                HDD_SHARED                A7E0                      Up-to-date
                ILOM                      5.0.0.20 r133445          Up-to-date
                BIOS                      25080100                  Up-to-date
                IPMI                      1.8.15.0                  Up-to-date
                HMP                       2.4.5.0.1                 Up-to-date
                OAK                       18.8.0.0.0                Up-to-date
                OL                        6.10                      Up-to-date
                OVM                       3.4.4                     Up-to-date
                GI_HOME                   18.8.0.0.191015           Up-to-date
                DB_HOME {
                [ OraDb12102_home1 ]      12.1.0.2.191015           Up-to-date
                [ OraDb11204_home1 ]      11.2.0.4.191015           Up-to-date
                [ OraDB18Home1 ]          18.8.0.0.191015           Up-to-date
                [ OraDb11203_home2 ]      11.2.0.3.15               No-update
                             }

Node 2

[root@odax58duts2 patchODA2020]#   oakcli show version -detail
INFO: 2020-06-06 19:56:39: Reading the metadata file now...
                Component Name            Installed Version         Proposed Patch Version
                ---------------           ------------------        -----------------
                Controller_INT            11.05.03.00               Up-to-date
                Controller_EXT            11.05.03.00               Up-to-date
                Expander                  001E                      Up-to-date
                SSD_SHARED                944A                      Up-to-date
                HDD_LOCAL                 A7E0                      Up-to-date
                HDD_SHARED                A7E0                      Up-to-date
                ILOM                      5.0.0.20 r133445          Up-to-date
                BIOS                      25080100                  Up-to-date
                IPMI                      1.8.15.0                  Up-to-date
                HMP                       2.4.5.0.1                 Up-to-date
                OAK                       18.8.0.0.0                Up-to-date
                OL                        6.10                      Up-to-date
                OVM                       3.4.4                     Up-to-date
                GI_HOME                   18.8.0.0.191015           Up-to-date
                DB_HOME {
                [ OraDb12102_home1 ]      12.1.0.2.191015           Up-to-date
                [ OraDb11204_home1 ]      11.2.0.4.191015           Up-to-date
                [ OraDB18Home1 ]          18.8.0.0.191015           Up-to-date
                [ OraDb11203_home2 ]      11.2.0.3.15               No-update

9- Aplicar DATAPATCH/CATBUNDLE em bancos de dados 11.2 / 12.1 / 12.2 e 18.8

export NLS_LANG=AMERICAN_AMERICA.AL32UTF8
$ORACLE_HOME/OPatch/datapatch -verbose

Nota: É necessário configurar o NLS_LANG para “AMERICAN_AMERICA. VARIÁVEL AL32UTF8” para evitar um BUG durante o DATAPATCH no Banco de Dados Oracle 12.1

Documentos de referência:

Oracle Database Appliance – 18.2, 12.X, and 2.X Supported ODA Versions & Known Issues (Doc ID 888888.1)

https://docs.oracle.com/en/engineered-systems/oracle-database-appliance/18.8/cmtxn/patching-oda.html#GUID-49F5F510-3A38-4E6A-B915-FCBCD36CDDDB

Espero ter ajudado com este procedimento de atualização da ODA

Disclaimer: “The postings on this site are my own and don’t necessarily represent may actual employer positions, strategies or opinions. The information here was edited to be useful for general purpose, specific data and identifications was removed to allow reach generic audience and to be useful.”

Evolução dos sistemas X6 – Exadata

André Luiz Dutra Ontalba — Wed, 08 Jun 2016 19:37:57 +0000

Do que se trata o artigo:

Neste artigo sera apresentado as principais mudanças no X6 – System

Em que situação o tema é útil:

Para entendimento da evolução do equipamento X6.

Fala galera !!

Achei interessante compartilhar algumas melhorias no Exadata System na sua versão 6.

Servidores agora são baseados no mais novo processador Intel Broadwell

Processadores Xeon de 22 Cores para Computer Nodes – até 25% mais rápido

Processadores Xeon de 10 Cores para Storage Nodes – até 25% mais rápido

Mais avançados Flash Cards (Novas placas NVMe) –até 2X mais rápido.

Servidores para Banco de Dados

2 sockets = 44 cores, até 768GB DRAM DDR4 ou 8 sockets = 144 cores, até 6TB DRAM.

Rede ultra-rápida unificada

Conexão InfiniBand interna de 40 Gb
Conexão data center de 1 Gb ou 10 Gb Ethernet

Servidores de storage inteligente e escalável

Storage -Extreme Flash = 25.6TB NVMeFlash
Storage -High Capacity = 12.8TB NVMeFlash + 96 TB SAS drives
2 socket servers = 20cores por servidor.

X6-2 Extreme Flash (EF) Storage Server

All Flash –Storage Inteligente, Escalável, Disponibilidade Alta, conectado via InfiniBand.

8x placas PCIe Flash de 3.2TB.

Capacidade incrementada para 25.6TB, dobrando a última geração de PCIe Flash

X6-2 High Capacity (HC) Storage Server

Storage Inteligente, Emcamadas, Escalável, Disponibilida de Alta, conectado via InfiniBand.

12x discos High Capacity de 8TB –1.3PB por full rack

4x Placas PCIe Flash de 3.2TB PCIe por servidor de armazenamento.

Smart Flash Cache – Software inteligente que gerencia os dados quentes.

Melhorias no Softwares do Sistema (Exadata)

Smart Analytics

Levar a query para o storage, e não o storage para a query

Paralelismo e descarregamento automático das queries em todos os servidores de armazenamento

Até 100x – Ganho analítico

Smart OLTP

Protocolo InfiniBand de alta velocidade e baixa latência para OLTP

Transações ultra rápidas utilizando o smart flash logging

Alta disponibilidade em memória espelhando entre os nodes.

Smart Fusion Block Transfer –Elimina escrita de logs quando move-se de um storage para outro.

Smart Storage

Hybrid Columnar Compression minimiza o uso de espaço em até 10x

Flash cache inteligente entrega a capacidade de discos com velocidade do flash

Smart Consolidation

Mensagens críticas do DB sempre tem preferência na fila de I/O

Priorização de I/O conforme regras de negócio

Até 4X mais DB no mesmo hardware

Criação automática de VLAN

Exadata 12.1.2.3.0 Software Enhancements

Ganho no desempenho da aplicação de patches e atualizações

Utilitário para gerenciamento dos discos de Quorum

Suporte a VLAN (tanto baremetal quanto OVM)

Aumento do número máximo de processos de DB

Verificação do tamanho dos discos do ASM quando diminuindo o mesmo.

Conclusões

Bem acho que esse resumo traz grandes oportunidades de aprofundar mais e mais no mundo de system machines da Orace.

Espero ter ajudado.

Até a próxima!

André Luiz Dutra Ontalba

Instalação Oracle Database Appliance – ODA – Parte 2

André Luiz Dutra Ontalba — Mon, 27 Jul 2015 18:50:49 +0000

Do que se trata o artigo:

Neste artigo sera apresentado o Oracle Database Appliance.

Em que situação o tema é útil:

Para entendimento do equipamento Oracle Database Appliance.

Bem vamos iniciar o deploy do Oracle Database Appliance, para tanto precisamos antes fazer a checagem de alguns itens importantes.

Primeiramente devemos ter instalado e checado todo o hardware para iniciar a instalação.

O Oracle Appliance Manager instala o software de banco de dados nos discos espelhados que são internos ao Oracle Database Appliance. Durante a configuração inicial, a Oracle Appliance Manager oferece três opções de implantação.

Enterprise Edition: Oracle Database 11g Release 2 Enterprise Edition (sem failover automático), com as seguintes características:Single-instância Oracle Database Enterprise Edition

Instalado em um ou ambos os servidores

Oracle Real Application Clusters (Oracle RAC) um nó: Oracle RAC One Node 11g Release 2, com as seguintes características:

Oracle RAC One Node

Oracle RAC instalado em ambos os servidores
Failover automatizado
Requer licença Enterprise Edition
Requer licença de Oracle RAC One Node em cada servidor (exceção: você pode designar um servidor como um servidor de backup, e você pode usar o servidor sem licença, de acordo com a regra de 10 dias)

Oracle RAC: Oracle Real Application Clusters 11g Release 2, com as seguintes características:

Oracle RAC
Oracle RAC instalado em ambos os servidores
Requer licença Enterprise Edition Oracle RAC em cada servidor (não elegível para a regra de 10 dias).

O software do Oracle Database Appliance inclui modelos pré-configurados que são otimizados para diferentes classes de bases de dados.

Cada classe de banco de dados tem diferentes perfis de carga de trabalho e requisitos de desempenho. Os modelos de incorporar as melhores práticas da Oracle.

Os modelos para Oracle Database Appliance X3-2 e o Oracle Database Appliance são ligeiramente diferentes. Use a lista que é apropriado para seu hardware.

Para o Oracle Appliance Gerente X3-2, escolha um dos seguintes modelos:

Very Small: SGA 4096 MB, PGA 2048 MB, 200 processes, 16 MB log buffer, 1 GB online redo log file

Small: SGA 8192 MB, PGA 4096 MB, 400 processes, 16 MB log buffer, 1 GB redo log file

Medium: SGA 16384 MB, PGA 8192 MB, 800 processes, 32 MB log buffer, 2 GB redo log file

Large: SGA 24576 MB, PGA 12288 MB, 1200 processes, 64 MB log buffer, 4 GB redo log file

Extra Large: SGA 49152 MB, PGA 24576 MB, 2400 processes, 64 MB log buffer, 4 GB redo log file

Extra Extra Large: SGA 65536 MB, PGA 32768 MB, 3200 processes, 64 MB log buffer, 4 GB redo log file

Para o Oracle Appliance Manager, escolher um dos seguintes modelos:

Very Small: SGA 4096 MB, PGA 2048 MB, 200 processes, 16 MB log buffer, 1 GB online redo log file

Small: SGA 8192 MB, PGA 4096 MB, 400 processes, 16 MB log buffer, 1 GB redo log file

Medium: SGA 16384 MB, PGA 8192 MB, 800 processes, 32 MB log buffer, 2 GB redo log file

Large: SGA 24576 MB, PGA 12288 MB, 1200 processes, 64 MB log buffer, 4 GB redo log file

Extra Large: SGA 49152 MB, PGA 24576 MB, 2400 processes, 64 MB log buffer, 4 GB redo log file

Nota:

A Oracle recomenda enfaticamente que você use esses modelos, porque implementam as melhores práticas e são configurados especificamente para o Oracle Database Appliance.
Você pode usar o Gerenciador de Appliance da Oracle ou Database Configuration Assistant (DBCA) para criar bancos de dados Oracle Database Appliance. Os modelos estão disponíveis em ambos os utilitários.

Antes de configurar os nomes e endereços de seu DNS, certifique-se de que todos os nomes de rede em conformidade com o padrão RFC 952, que permite caracteres alfanuméricos e hífens (“-“), mas não permite sublinhados(“_”).
Análise Tabela abaixo para garantir que sua s reservas de administrador de rede, pelo menos, o número mínimo de endereços IP necessários para o seu banco de dados Oracle

Confirme com o seu administrador de rede que os endereços que você configurou para o Oracle Database Appliance atendem a esses três critérios:

1. Eles são endereços IP estáticos
Eles estão na mesma sub-rede que todos os outros endereços IP, IP virtual (VIP) endereços (usado para Real Application Clusters comunicação) e endereços SCAN.

Eles incluem o seguinte:

Um endereço IP público para cada nó, com as seguintes características:

Configurado no DNS antes da instalação para cada nó, e resolvido para esse nó antes da instalação.

Um endereço de VIP em cada nó, com as seguintes características:

Configurado no DNS antes da instalação para cada nó, mas não atualmente em uso

Verifica Oracle Database Appliance, com as seguintes características:

Configurado no DNS antes da instalação para que os dois endereços IP são associados com o nome fornecido como o SCAN, e ambos os endereços são retornados em ordem aleatória pelo DNS para o solicitante
Configurado no DNS antes da instalação para resolver a endereços que não estão atualmente em uso
Use um nome que não começar com um numeral

Usando o Oracle Appliance Manager Configurator

A Oracle Appliance Gerente Configurator é uma ferramenta baseada em Java que você pode usar para introduzir o seu plano de implantação e validar suas configurações de rede antes da implantação real.

No final de uma sessão configurador, você pode salvar seu plano de implantação em um arquivo de configuração. Quando você estiver pronto para implantar, copie este arquivo de configuração para Oracle Database Appliance, onde o Oracle Appliance Gerente Configurator irá usá-lo para implantar o seu plano.

Você também pode imprimir o conteúdo do arquivo e usar a impressão como uma lista de verificação para configurar a configuração de rede externa.

Antes de salvar o seu arquivo de configuração, você pode testar suas configurações de rede, mas apenas se estiver conectado a mesma rede que você vai usar para Oracle Database Appliance.

Confirmando os seus endereços de DNS não é necessário durante a execução do configurador em um cliente, mas é fortemente recomendado quando você é capaz de testar o seu arquivo de configuração.

Para executar o configurador:

Download do Oracle Appliance Gerente Configurator que corresponde à sua versão do Oracle Database Appliance. Todas as versões do Configurator estão disponíveis no Appliance página Visão Geral do Oracle Database no seguinte URL:

http://www.oracle.com/technetwork/server-storage/engineered-systems/database-appliance/index.html

Inicie o Configurador usando o config.bat comando em um cliente Windows ou o comando ./config.sh em um cliente Linux. O Appliance página Bem-vindo Gerente da Oracle aparece.

Clique em NEXT

3. Em a Select Configuration Type, selecione as opções para o tipo de configuração, tipo de ambiente e hardware. Você também pode localizar e carregar um arquivo de configuração existente com a opção de navegação.

Configuração típica é a opção recomendada, a menos que você estará usando Oracle Database Appliance para bancos de dados e aplicativos SAP, nesse caso, escolha a aplicação SAP. Escolha a opção Custom para configurar interfaces de rede adicionais ou alternativos ou para substituir os valores padrão para uma ou mais das seguintes opções:

Bloco de banco de dados de tamanho, língua, território, a localização do arquivo de backup, ou o nível de redundância de disco para os dados e RECO diskgroups.

Você pode executar o Configurador usando a opção Custom para ver os valores padrão para a versão do Oracle Database Appliance, antes de escolher a opção típica ou personalizada.
Se você estiver instalando o Oracle Database Appliance plataforma virtualizada, em seguida, selecione plataforma virtualizada, ou deixe o valor padrão, Bare Metal, como a opção de ambiente.

Se você estiver instalando o Oracle Database Appliance X3-2, em seguida, selecione a APD-X3-2, ou deixe o valor padrão, a APD V1, como a opção de hardware.
A opção Procurar não é útil durante a execução inicial, porque você ainda não tiver criado os arquivos de configuração para carregar.
Neste exemplo, típica, plataforma virtualizada, e APD-X3-2 são as opções selecionadas.

Clique em NEXT.

Em página Informações do sistema, forneça o nome do sistema, e selecione o valor correto a partir das listas para a sua região e fuso horário.

No campo de Database Deployment, selecione o tipo de implantação de banco de dados que você deseja:

Oracle Database Enterprise Edition (sem Oracle RAC)
Oracle RAC One
Oracle RAC

No campo Nova senha de root e Nova Senha Root (confirmar), digite uma nova senha para o usuário root. Esta senha é criptografada no arquivo de configuração e será de-codificado e usado para redefinir a senha durante a implantação.

Clique em NEXT

Em a página de Informação de Rede, fornecer o nome de domínio, endereços de servidor DNS público e endereços VIP para seus dois nós, o nome SCAN e endereços, e máscara de rede e endereços de gateway. Por exemplo:

Como você inserir dados nesta tela, alguns campos vão pré-preencher com os valores derivados de entradas anteriores. Por exemplo, se o endereço que você fornecer para o nó 0 endereço IP público é 192.0.2.18, então os endereços de nó são atribuídos da seguinte forma:

Node 0 endereço IP público: 192.0.2.18.
Node um endereço IP público: 192.0.2.19.
Node 0 IP (VIP) endereço virtual: 192.0.2.20.
Node 1 IP (VIP) endereço virtual: 192.0.2.21.
SCAN ADDRESS (dois endereços resolvendo o nome VIP SCAN): 192.0.2.22, 192.0.2.23.

Clique em NEXT.

Na página de informações de banco de dados, forneça o nome de seu banco de dados e selecione o modelo de configuração de banco de dados e linguagem de banco de dados.

Clique NEXT.

Na página Validação de Rede, você pode validar as configurações de rede e salvar a saída de validação em um arquivo, ou você pode ignorar a etapa de validação, selecionando a caixa de seleção Ignorar validações rede, como mostrado no exemplo a seguir:

A Oracle recomenda que você valide sua rede antes de implantar a sua configuração. Porém, se você estiver executando o Oracle Appliance Manager Configurator em Oracle Database Appliance, ou em servidor ligado à sub-rede configurada para o seu aparelho, a validação irá falhar.

Nesse caso, marque a caixa de seleção Rede validações, em seguida, clique em Avançar para prosseguir para a próxima página. Se você executar a validação, em seguida, analisar os resultados. Depois de rever o resultados, se você estiver pronto para continuar, clique em Avançar.

Se a validação falhar, em seguida, salvar a saída de validação para rever esses resultados com o seu administrador de rede.

Para salvar as informações de configuração que você digitou e corrigir os endereços de rede mais tarde, selecione Skip Network Validations e clique em Avançar para continuar para a próxima página.

Na página Resumo, revise as opções de configuração que você selecionou. Clique em Salvar para salvar o arquivo de configuração, ou clique em Voltar para modificar as seleções.

Se você estiver executando o Configurator em um Oracle Database Appliance e ter concluído os passos preliminares para configurar a sua rede inicial e instalar o pacote End-User ou ODA_BASE, então você pode clicar em Instalar para implantar a configuração que você acabou de criar.

Conclusões

Bem está é uma das formas de instalar o Oracle Database Appliance, nos próximos artigos apresentaremos outras formas de se instalar o ODA.

Espero ter ajudado.

Até a próxima!

André – BLOG DBA DUTRA

Instalação Oracle Database Appliance – ODA – Parte 1

André Luiz Dutra Ontalba — Wed, 03 Jun 2015 16:42:06 +0000

Neste artigo sera apresentado o Oracle Database Appliance.

Em que situação o tema é útil:

Para entendimento do equipamento Oracle Database Appliance e sua implementação

Oracle Database Appliance é um pacote completo de hardware e software, junta armazenamento e hardware de rede combinada com a rede, cluster, e software de banco de dados, com, se desejado, o Oracle VM no Oracle Database Appliance plataforma virtualizada. Oracle suporta integralmente todos os componentes de hardware e software. O hardware e software são projetados em conjunto para ser simples de configurar e manter e, para ser pré-configurado para cargas de trabalho de banco de dados específicos. Oracle Database Appliance foi projetado para minimizar o custo, tempo e risco na implantação e manutenção de banco de dados. Oracle Database Appliance plataforma virtualizada proporciona flexibilidade adicional, isolando seu software Oracle de domínios de máquinas virtuais que você pode implantar máquinas virtuais sempre que necessário.

Vamos agora conhecer um pouco deste hardware.

Frente do Painel do Oracle Database Appliance X3-2, são 2 equipamentos X3-2 para criação do ambiente de Alta disponibilidade.

ID	Descrição
1	LED – SP (Server Process)
2	Power Button
3	LED – Power/OK

ID	LABEL	ETHERNET	BOND	Descrição
1	NET MGT	–	–	Conexão Oracle ILOM
2	100 – 10GbE(NET0,NET1, NET2, NET3)	Eth2, Eth3, Eth4 Eth5	Bond0, Bond1	Eth2 e eth3 são configurados como bond0. Eth4 e Eth5 são configurados como bond1. Essas portas de rede externa proporcionar o acesso de usuários e conexões para outras funções personalizadas, tais como rede geral, backups externos e recuperação de desastres.
3	USB e Video			Fornecer conexões para um teclado e um mouse (portas USB) e um monitor de vídeo (porta VGA). Nota: este é suportado no Nó 0 apenas.
4				Fonte de alimentação
5	1:Pcle3 (NET0, NET1)	Eth0, Eth1	Icbond0	Cluster interconnects.

ID	Descrição
1	LED Locator
2	LED SP (Service Processor) OK
3	LED de Informação para remoção de nodes
4	LED Service Required (Para alerta de Falhas).
5	LED Power / OK
6	LED Temperatura do Hardware
7	LED Temperatura dos dispositivos (HDD, FAN e Processador)
8	Botão Power
9	Drive Map
10	Etiqueta RFID e Serial number e tag do serviço.

ID	LABEL	ETHERNET	BOND	Descrição
1				Fonte de alimentação
2	PCIe1	Eth7,6,5,4 (da esquerda para direita)	Bond1, Bond2	Eth4 e Eth5 são configurados como bond1. Eth6 e Eth7 são configurados como bond2. Essas portas de rede externa proporcionar o acesso de usuários e conexões para outras funções personalizadas, tais como rede geral, backups externos e recuperação de desastres.
3	PCIe0	Eth8, Eth9	xbond0	2 portas 10GbE
4	SER MGT			Conector Serial Oracle ILOM e System Console
5	Net0, Net1	Eth2, Eth3	bond0	Dois conectores de 1 GbE. Se você configurar uma rede de 1 GbE, em seguida, conectar essas portas para a rede pública.
6	NET MGT			Ethernet Connector ILOM
7	USB e Video			Fornecer conexões para um teclado e um mouse (portas USB) e um monitor de vídeo (porta VGA). Nota: este é suportado no Nó 0 apenas.
8				Node 0
9				Node 1

Conclusões

Bem demos uma breve descrição e demonstração do equipamento, no próximo artigo iremos realizar o DEPLOY assim como explicar o que precisa para realizar toda a instalação do equipamento.

Até a próxima!

André