Database Reference
In-Depth Information
•
Display software and firmware versions
•
Display disks, disk groups, and other storage details
•
Clean up patches that have been applied
•
Activate cores when additional Oracle licenses are purchased
•
Diagnostics
•
Run a complete check of the system
•
Locate a disk drive and light up its LED indicator to signal which specific disk drive needs
to be replaced
•
Run disk diagnostics
•
Run an ODAchk health check
•
Collect and package diagnostic information
•
Virtualization
•
Create or clone an ODA virtual machine
•
Configure resources on an ODA virtual machine
•
Start and stop ODA_Base (the database partition on a virtualized ODA) or another ODA
virtual machine
•
Display the information for ODA VM templates
•
Deploy/import an Oracle VM template
•
Create CPU pools for ODA virtual machines
•
Display all of the details for one or all of virtual machines on an ODA
•
Apply IPs to an ODA virtual machine
•
Open a VM console to manage an ODA VM
Oracle also provides additional ODA diagnostic utilities as part of the ODA software product set. The main utility
is ODAchk (MOS 1485630.1). This is an ODA-specific version of RACcheck. Oracle recommends that you deploy the
latest version of ODAchk, so you have to check the MOS note as new versions are released following changes to the
RACcheck and Exadata Exachk tools.
ODAs ship with the standard
top
,
vmstat
, and
sar
server resource monitoring utilities. ODAs also ship with the
detailed server resource collection utility OSWatcher (MOS 301137.1 and 461053.1). Two additional standard RAC
utilities common to self-install platforms are also included with the ODA RAC software:
•
Cluster Health Monitor (MOS 736752.1 and 1328466.1)—Granular resource monitoring
•
Trace file analyzer utility (MOS 1513912.1) —Real-time event capture
ODAs ship with a set of database templates designed for performance and consolidating DBs on ODAs. The
Database templates sizing is documented in the Getting Started Guide. The templates range in size from very small,
small, medium, large, extra-large, and extra-extra large. Besides configuring memory, redo log sizes, and the starting
DB size, the templates determine the number of databases that can be deployed on an ODA.
