The handling and installation of an Exadata Database Machine rack require caution and adherence to

recommended guidelines:

Shipping Brackets: Shipping brackets are specifically designed for transportation purposes and should

not be reused for permanent installation. Permanent floor mounting should use approved rack-

mounting equipment to ensure stability and safety .

Steering and Pushing the Rack: Exadata racks should be steered from the rear due to fixed front

casters. It is critical to avoid pushing the rack from the side panels, which could cause it to tip over,

presenting a serious safety risk. This careful movement ensures safe positioning and prevents

damage to the equipment during installation.

According to Oracle’s documentation1, the client network on Exadata X9M-2 Database Server is used

for client access to the database servers using Single Client Access Name (SCAN) and Oracle RAC

Virtual IP (VIP) addresses. To verify that the client network is available via both client switches, you

can use the command:

cat /proc/net/bonding/bondeth0

This command displays information about the bondeth0 interface, which is used for the client

network on Exadata X9M-2 Database Server2. You can check if both interfaces (eth0 and eth1) are

active and connected to different switches3.

According to Oracle.com documents or resources, the three options that are available for database

consolidation on Exadata are:

A . Multiple pluggable databases in one or more container databases on a Virtual Machine or Bare

Metal cluster123.

C . A single database with one or more schema per application12.

E . Multiple Databases on a cluster12.

https://blogs.oracle.com/exadata/post/database-consolidation-why-and-how

The minimum Exadata System Software version required to support Oracle Exadata X9M is

21.2.0.0.0. This version introduced various enhancements and capabilities tailored for the X9M

series, including optimizations for the RoCE network fabric and support for new hardware

components .

Option C shows the number of read hits from PMEM cache on storage servers which indicates how

much data was served from PMEM instead of flash or disk1.

Option E shows detailed information about PMEM cache such as size, utilization, hit ratio, read

latency and write latency2.