Oracle Exadata Deployment Assistant has two main phases:
In phase 1, the customer provides naming, DNS, NTP, and networking details. This
information is collected using the Oracle Exadata Deployment Assistant user interface.
A configuration file is generated.
In phase 2, the configuration file is pushed to the database node, and the validation
and installation is completed.
Accessibility Note: If you are using Oracle Exadata Deployment Assistant with
assistive technology (for accessibility) on Windows, you need to enable Java Access
Bridge.
3.1.1 Considerations when Using Oracle Exadata Deployment
Assistant
Review this information when using Oracle Exadata Deployment Assistant (OEDA).
Note the following when using Oracle Exadata Deployment Assistant:
•
Oracle Exadata Rack ships with the Oracle Linux operating system installed on the
database servers, with the Oracle Linux as the default.
•
The rack name is used to generate host names for network interfaces for all
systems. For example, a value of
dm01
results in database server host names of
dm01db01
,
dm01db02
,
dm01db03
, and so on, and Exadata Storage Server host names
of
dm01cel01
,
dm01cel02
,
dm01cel03
, and so on.
In a multi-rack configuration, each Oracle Exadata Rack name should be a unique
name that identifies the machine. Oracle recommends using
dm01
for the first
Oracle Exadata Rack,
dm02
for the second,
dm03
for the third, and so on. Up to
eighteen Oracle Exadata Racks can be cabled together without additional Sun
Datacenter InfiniBand Switch 36 switches.
•
The backup method information is used to size the Oracle Automatic Storage
Management (Oracle ASM) disk groups created during installation. The amount of
usable disk space varies depending on the backup method. The backup methods
are as follows:
–
Backups internal to Oracle Exadata Rack mean database backups are created
only on disk in the Fast Recovery Area (FRA). In addition to the database
backups, there are other objects such as Archived Redo Logs and Flashback
Log Files stored in the FRA. The division of disk space between the DATA
disk group and the RECO disk group (the FRA) is 40% and 60%, respectively.
–
Backups external to Oracle Exadata Rack mean database backups are
created on disk or tape media that is external to currently deployed Oracle
Exadata Database Machine, and not on existing Exadata Storage Servers. If
you are performing backups to disk storage external to Oracle Exadata
Database Machine, such as to additional dedicated Exadata Storage Servers,
an NFS server, virtual tape library or tape library, then do not reserve
additional space in the RECO disk group when using Oracle Exadata
Deployment Assistant.
When choosing this option, the FRA internal to Oracle Exadata Rack contains
objects such as archived redo log files and flashback log files. The division of
disk space between the DATA disk group and the RECO disk group (the FRA)
is 80% and 20%, respectively.
Chapter 3
Overview of Oracle Exadata Deployment Assistant
3-2
