Cluster Server 8.0 Application Note: Dynamic Reconfiguration for Oracle Servers - Solaris
- Dynamic reconfiguration of Oracle servers
- Overview: Dynamic reconfiguration in a VCS environment
- Supported software and hardware
- Preparing to perform dynamic reconfiguration
- Scenarios requiring a VCS shutdown
- Stopping and starting VCS
- Performing dynamic reconfiguration on Oracle SunFire (s6800; e12K/15K/ e25K)
- Replacing an online Host Bus Adapter (HBA) on an M5000 server
CPU/Memory boards with permanent memory
If the CPU/memory board to be removed contains permanent memory, the operating system's function must be suspended to permit dynamic reconfiguration to occur. In such a case, VCS must be stopped.
However, you do not need to stop VCS when you are performing dynamic reconfiguration on a board that does not contain permanent memory. Typically, in a domain with multiple CPU/memory boards, one board has permanent memory, while the others do not. When you are performing dynamic reconfiguration to add a new board to the domain, the existing functions in the domain are not affected by the dynamic addition of a new CPU/memory board.
Note:
If you must reconfigure multiple boards and a board with permanent memory is among them, reconfigure the board with permanent memory last. This sequence ensures minimum VCS downtime.
To determine if the CPU/memory board has permanent memory
- Log in to the domain as domain administrator.
- List the boards with permanent memory in the domain by entering the following command:
# cfgadm -av | grep permanent
SB2::memory connected configured ok base address 0x1e000000000,
16777216 KBytes total, 2001200 KBytes permanent
The output in the example shows SB2 to contain permanent memory. Before this board can be dynamically reconfigured, VCS must be stopped.
See Stopping and starting VCS.
Other CPU/memory boards in the domain do not contain permanent memory and may be dynamically reconfigured without stopping VCS.