JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Geographic Edition Installation Guide     Oracle Solaris Cluster 3.3 3/13
search filter icon
search icon

Document Information

Preface

1.  Planning the Geographic Edition Installation

2.  Installing Geographic Edition Software

Installation Overview

Installing Geographic Edition Software

How to Install Geographic Edition Software

Installing Patches

How to Prepare the Cluster for Patch Installation

How to Install Patches

3.  Enabling and Configuring the Geographic Edition Software

4.  Upgrading the Geographic Edition Software

5.  Uninstalling Geographic Edition 3.3 1/13 Software

Index

Installation Overview

You can install Geographic Edition software on a running cluster without disruption. Because the Geographic Edition software installation process does not require you to restart Oracle Solaris Cluster software, the cluster remains in production with services running.

The installer program offers two interactive installation modes, graphical user interface (GUI) and text-based interface. The graphical mode provides a wizard that guides you, step by step, through the tasks that you need to perform to install the Geographic Edition components. The text-based mode provides the same functions that the GUI provides. However, this mode prompts you for responses on a line-by-line basis, rather than by means of a wizard.


Note - Ensure that you have installed all the required patches for your cluster configuration on each node of every cluster before you start installing the software. See Patches and Required Firmware Levels in Oracle Solaris Cluster 3.3 3/13 Release Notes for the location of patches and installation instructions.


You must install Geographic Edition software in the global zone for all nodes of a cluster in a partnership, whether it is a global cluster or a zone cluster. This is true even if the Geographic Edition software will not be configured or started in the global zone. For zone clusters, the Geographic Edition software is propagated to the zone-cluster nodes by default. If a zone cluster uses sparse-root zones, each node of that zone cluster must run the same supported version of Geographic Edition software as the global zone. This limitation does not apply to a zone cluster that uses whole-root zones.