| Skip Navigation Links | |
| Exit Print View | |
|
Oracle SuperCluster M6-32 Owner's Guide: Administration |
Understanding SuperCluster Software
Identify the Version of SuperCluster Software
Controlling SuperCluster M6-32
Powering Off SuperCluster M6-32 Gracefully
Shut Down the Oracle Solaris Cluster
Shut Down the Enterprise Controller (Ops Center)
Shut Down the OS on the Compute Servers
Shut Down the ZFS Storage Appliance
Power Off the Switches and Racks
Power Off SuperCluster M6-32 in an Emergency
Monitoring SuperCluster M6-32 (OCM)
Monitoring the System With ASR
Configure ASR on the Compute Servers (Oracle ILOM)
Configure SNMP Trap Destinations for Storage Servers
Configure ASR on the ZFS Storage Appliance
Configuring ASR on the Compute Servers (Oracle Solaris 11)
Enable the HTTP Receiver on the ASR Manager
Enable HTTPS on ASR Manager (Optional)
Register Compute Servers With Oracle Solaris 11 or Database Domains to ASR Manager
Approve and Verify ASR Asset Activation
Change ssctuner Properties and Disable Features
Configuring CPU and Memory Resources (osc-setcoremem)
Minimum and Maximum Resources (Dedicated Domains)
Supported Domain Configurations
Plan CPU and Memory Allocations
Display the Current Domain Configuration (osc-setcoremem)
Display the Current Domain Configuration (ldm)
Change CPU/Memory Allocations (Socket Granularity)
Change CPU/Memory Allocations (Core Granularity)
Access osc-setcoremem Log Files
Revert to a Previous CPU/Memory Configuration
Remove a CPU/Memory Configuration
Obtaining the EM Exadata Plug-in
Known Issues With the EM Exadata Plug-in
Configuring the Exalogic Software
Prepare to Configure the Exalogic Software
Enable Domain-Level Enhancements
Enable Cluster-Level Session Replication Enhancements
Configuring Grid Link Data Source for Dept1_Cluster1
Runtime Connection Load Balancing
Secure Communication With Oracle Wallet
Create a Grid Link Data Source on Dept1_Cluster1
Configuring SDP-Enabled JDBC Drivers for Dept1_Cluster1
Configure the Database to Support IB
Create an SDP Listener on the IB Network
Administering Oracle Solaris 11 Boot Environments
Advantages to Maintaining Multiple Boot Environments
Mount to a Different Build Environment
Reboot to the Original Boot Environment
Create a Snapshot of a Boot Environment
Remove Unwanted Boot Environments
Monitor Write-through Caching Mode
Perform this procedure for each storage server before you power them off. For more information on this task, refer to the Exadata documentation at:
http://wd0338.oracle.com/archive/cd_ns/E13877_01/doc/doc.112/e13874/maintenance.htm#CEGBHCJG
CellCLI> LIST GRIDDISK ATTRIBUTES name WHERE asmdeactivationoutcome != 'Yes'
If any grid disks are returned, then it is not safe to take the storage server offline, because proper Oracle ASM disk group redundancy will not be maintained. Taking a storage server offline when one or more grid disks are in this state causes Oracle ASM to dismount the affected disk group, which causes the databases to shut down abruptly.
CellCLI> ALTER GRIDDISK ALL INACTIVE
This command completes after all disks are inactive and offline.
CellCLI> LIST GRIDDISK WHERE STATUS != 'inactive'
If all grid disks are inactive, then you can shut down a storage server without affecting database availability.
|