Readme
Readme
Readme
Download the appropriate file for the client operating system. For example, if O
racle Exadata Deployment Assistant configuration tool is to be run on a Microsof
t Windows client, then download the Microsoft Windows file. The operating system
of the client does not have to match the operating system of the engineered sys
tem.
See Also
Oracle Exadata Database Machine Owner's Guide for additional information about O
racle Exadata Deployment Assistant
1.1 Changes in This Release
The following changes are included in this release of Oracle Exadata Deployment
Assistant:
1.1.1 Changes in December 2014 Release
o
Added support for Oracle Database 12c Release 1 (12.1.0.2) DBBP3, and ma
ndatory Oracle Java Virtual Machine (OJVM) patch set update 19282028.
o
Added support for Oracle Database 11g Release 2 (11.2.0.4) BP14, and man
datory OJVM patch set update 19282021, and JDBC patch 19852360.
1.1.2 Changes in November 2014 Release
o
Added support for Oracle Database 12c Release 1 (12.1.0.2) DBBP2, and ma
ndatory Oracle Java Virtual Machine (OJVM) patch set update 19282028 (for both D
BBP1 and DBBP2).
o
Added support for Oracle Database 12c Release 1 (12.1.0.1) mandatory OJV
M patch set update 19282024, and Java Database Connectivity (JDBC) patch 1985235
7 (for PSU5).
o
Added support for Oracle Database 11g Release 2 (11.2.0.4) mandatory OJV
M patch set update 19282021, and JDBC patch 19852360 (for both BP13 and BP12).
o
Added support for Oracle Database 11g Release 2 (11.2.0.3) mandatory OJV
M patch set update 19282015, and JDBC patch 19852361 (for BP25).
o
Added support for identification and configuration of additional spine s
witches during initial data configuration.
o
Updated the initial Oracle Exadata Deployment Assistant configuration sc
reen to have options for Oracle Exadata Database Machine, Oracle Zero Data Loss
Recovery Appliance, and Oracle SuperCluster.
1.1.3 Changes in October 2014 Release
o
Added support for Oracle Database 12c Release 1 (12.1.0.2) DBBP1.
o
Added support for Oracle Database 12c Release 1 (12.1.0.1) PSU5.
n
Added support for Oracle Database 11g Release 2 (11.2.0.4) Patch Set 3 B
P12.
o
Added support for Oracle Database 11g Release 2 (11.2.0.3) Patch Set 2 B
P25.
o
Reduced setup time for the Cell Alerting configuration step.
o
Updated the bash rpm on Linux database and storage servers to counter th
e bash shell vulnerability CVE-2014-6217 and CVE-2014-7169.
o
Support for Zero Data Loss Recovery Appliance
1.1.4 Changes in September 2014 Release
o
Added support for Oracle Database 11g Release 2 (11.2.0.4) Patch Set 3 B
P11.
n
Added a timestamp to the Installation Template report.
o
Updated the checkip.sh script so that it no longer displays incorrect er
rors for Oracle Exadata Storage Expansion Rack.
o
Updated Oracle Exadata Deployment Assistant deployment tool so that NTP
services (ntpd) are restarted before the Install Cluster Software step.
1.1.5 Changes in August 2014 Release
o
Added support for Oracle Database 11g Release 2 (11.2.0.4) Patch Set 3 B
P10.
o
Implemented a set of questions in Oracle Exadata Deployment Assistant to
clarify the proposed installation.
o
Enabled appliance.mode attribute for disk groups in Oracle Database rele
ases 11.2.0.4 and 12.1.0.2 deployments.
o
Enhanced Oracle Exadata Deployment Assistant validation check to disable
active-active bonding on Oracle Exadata Database Machine X4-2 Solaris X64 deplo
yments.
o
Corrected the reported Oracle ASM disk group size in the installation te
mplate for eighth rack deployments.
o
Corrected the number of InfiniBand adapters created in Oracle SuperClust
er Zones deployment.
o
Implemented a full set of new database DBCA templates for Oracle SuperCl
uster deployments.
o
Corrected intermittent delay at the end of the Initialize Cluster step.
n
Fixed issues with the Apply Security Fixes step.
1.1.6 Changes in July 2014 Release
o
o
o
o
o
Oracle
Oracle
Oracle
Oracle
-
Section
(12.1.0.2)"
o
Section
(12.1.0.1)"
o
Section
(11.2.0.4)"
o
Section
(11.2.0.3)"
linuxamd64_12102_database_1of2.zip
linuxamd64_12102_database_2of2.zip
-
Patch Number
20026159
19774304
19404326
ml
o
The patch for the relevant PSU being deployed. The following are the GIP
SUs and patch numbers for release 12.1.0.1:
GIPSU
5
4
3
2
1
Patch Number
19392372
18705901
18139660
17735306
17272829
Patch Number
19893788
19713190
19542004
19353130
19023390
18840215
18632316
18530329
18371656
18179615
18006587
17904156
17838803
17628025
The patch for the relevant bundle patch being deployed. The following ar
Patch Number
19500593
18835772
18342655
17747147
17395890
16869210
16784993
16627873
16474946
16233552
16039087
15835102
14786157
14662263
14474780
14352236
14229857
14103267
13992240
13870089
13734832
13667791
13556853
Note
Oracle patch 20116094 is needed when using release 11.2.0.3 Bundle Patch 25 on O
racle SuperCluster Solaris SPARC.
Oracle patch 16057129 is needed when using release 11.2.0.3 Bundle Patch 21. In
addition, the patch zip file must be renamed to following, depending on the oper
ating system:
o
o
o
On Microsoft Windows:
config.cmd
When using Oracle Exadata Deployment Assistant from a database server on Oracle
Exadata Database Machine, log in as the root user, and copy the configuration fi
les created by Oracle Exadata Deployment Assistant to a directory in the /u01 di
rectory, such as the /u01/oeda directory.
When using Oracle Exadata Deployment Assistant remotely, run the assistant from
the directory that has the install.sh file.
The following steps are performed by the assistant:
1. Validate Configuration File
2. Setup Required Files
3. Create Users
4. Setup Cell Connectivity
5. Verify Infiniband
6. Calibrate Cells
7. Create Cell Disks
8. Create Grid Disks
9. Configure Cell Alerting
10. Install Cluster Software
11. Initialize Cluster Software
12. Install Database Software
13. Relink Database with RDS
14. Create ASM Diskgroups
15. Create Databases
16. Apply Security Fixes
17. Setup ASR Alerting
18. Create Installation Summary
19. Resecure Machine
Note
The number of steps and step numbers may be different, depending on the features
selected for configuration.
Oracle Exadata Deployment Assistant uses the configuration files located in the
./config/ directory. These files cannot be changed or edited.
Log files are generated when using the deployment tool. The log files are locate
d in the ./log/ directory. If there is an error when using Oracle Exadata Deploy
ment Assistant, then open a service request, and include the diagnostics file. T
he diagnostics file is created in the ./WorkDir/ directory, and is a compressed
zip file that contains information relevant to the error.
3.1 Oracle Exadata Deployment Assistant Commands
The install.sh script is used to run Oracle Exadata Deployment Assistant. The sc
ript is run by the root user.
The following arguments are available with the script:
-l
List all the steps that exist
-cf
The config file name (use full path)
-s <step num> Run a particular step
-r <num-num> Run the steps one after the other as long as no errors are encoun
tered
-u <num-num> <step num> Undo a range of steps or a particular step
-h
Usage
The following examples show how to use the install.sh script:
o
To undo a step:
# ./install.sh -cf ../exadatarack1.xml -u 3
The steps Validate the configuration files and Apply security fixes cannot be un
done.
o