2x 25Gb ports on eth1 and eth2 using SFP28 transceivers and OM4 fiber cable for backup network, and 2x 25Gb ports on eth5 and eth6 using SFP28 transceivers and OM4 fiber cable for client network

2x 25Gb ports on eth1 and eth2 using SFP28 transceivers and OM4 fibre cable for client network, and 2x 10Gb ports on eth9 and eth10 using RJ45 cat6 cable for backup network

2x 10Gb ports on eth1 and eth2 using FU45 cat6 cable for client network, and 2x 25Gb ports on eth11 and eth12 using SFP28 transceivers and OM4 fiber cable for backup network

2x 25Gb ports on eth1 and eth2 using SFP28 transceivers and OM4 fiber cable for backup network, and 2x 10Gb ports on eth3 and eth4 using RJ45 cat6 cable for client network

ASR Manager must be installed and configured on a dedicated server external to the Database Machine.

Configuring ASR is mandatory for all Database Machine assets.

ASR Manager must be installed and configured on one of the database servers.

ASR can upload configuration metadata to support problem resolution.

ASR Manager opens a service request (SR) automatically after sensors detect hardware faults.

# lvextend -L +20G —verbose /dev/mapper/VGExaDb-LVDbOral

# xfs_growfs /uOl +20G

# resize2fs +20G /dev/VGExaDb/LVDbOral

# lvextend -L +20G —verbose /dev/VGExaDb/LVDbOral

Persistent Memory Commit Accelerator tracks changes to Persistent Memory Data Accelerator to ensure duplicate blocks are not written to Flash.

Persistent Memory Commit Accelerator helps to further reduce redo log write latency by using Persistent Memory and Remote Direct Memory Access (RDMA).

Persistent Memory Commit Accelerator copies redo log data from disk for faster redo apply on Data Guard Standby Databases.

Persistent Memory Commit Accelerator contains logging information from all tiers of the software stack for rapid triage and diagnostics.

Persistent Memory Commit Accelerator reduces redo log write latency by using Persistent Memory and RDMA before flushing to Flash then disk.

A splitter cable can be used to provide power to all PDU cables.

The power cables from the servers to the PDUs can be rearranged inside the rack following OECA guidance to utilize a single PDU power cable.

The installation cannot proceed until two power feeds are available per PDU.

The installation can go ahead, no change is required.

2, 3, 4, 8, and 10 run on the database servers; 1, 5, 6, 7and 9 run on the Exadata storage servers.

1, 2, 3, 4, 9 and 10 run on the database servers; 5, 6, 7, 8, 9, and 10 run on the Exadata storage servers.

1, 2, 3, 4, 5, 8, 9 and 10 run on the database servers; 5, 6,7, 9 and 10 run on the Exadata storage servers.

3, 4, 8, and 10 run on the database servers; 1, 2, 5, 6, 7 and 9 run on the Exadata storage servers.

1, 2, 3, 4, 8 and 9 run on the database servers; 5, 6, 7, 9 and 10 run on the Exadata storage servers.

It can execute commands on multiple storage servers in parallel.

It has command-line history.

It requires root privileges to create CELLDISKS and GRIDDISKS.

It can be executed on storage servers.

It can be executed using the DCLI utility.

Placing the backup network on dedicated switches installed in the top of the rack (ToR) has the benefits of isolating the backup network from other workloads and providing a greater level of control.

Even if the backup was limited to writing to four tape drives, eight channels could be specified to expedite the restore process.

The internal Recovery Appliance backup and restore processing is optimized when the RMAN FILESPERSET parameter is set to 1 for the level 1 incremental backup set.

When off-site long-term backup retention is needed, use Oracle Database Backup Cloud Service as a low-cost, offsite scalable storage for a disaster recovery solution.