This section describes the Oracle9i release 2 (9.2) new features as they pertain to the setup and configuration of Oracle Real Application Clusters. The topic in this section is:
- Oracle9i Release 2 New Features for Real Application Clusters Setup and Configuration
See Also:
- Platform-specific documentation for information about installing Oracle Real Application Clusters Guard I (except for Windows NT and Windows 2000 where Real Application Clusters Guard I installation information is in the Real Application Clusters Guard I document on the Fail Safe/Real Application Clusters Guard software CD-ROM)
- Real Application Clusters Guard II installation documentation on the Real Application Clusters Guard II software CD for information about installing Real Application Clusters Guard II
|
Oracle9i Release 2 New Features for Real Application Clusters Setup and Configuration
- New Tablespace Requirements
- This release requires two additional tablespaces: the XDB and the ODM tablespaces to accommodate the Oracle XML DB and the Oracle Data Mining features respectively.
- Oracle Universal Installer Enhancements
- The Installer propagates its inventory to the remote cluster nodes if you are not using a cluster file system. Therefore, you can perform deinstalls and patch installs from any node in you cluster database.
- Diagnostic and error messages are cluster-aware.
- Registry operations in the Installer are clusterized for Windows NT and Windows 2000 platforms.
- The order and composition of some Installer screens have changed and a Summary page displays the names of the nodes on which installation operations are performed.
- On a machine on which you are installing Oracle for the first time, the Installer prompts you to run the root script for the creation of the
instLoc file on all the cluster nodes.
- On UNIX platforms, the Installer displays a message prompting you to run the
root.sh script on the selected cluster nodes.
- Database Configuration Assistant Enhancements
- On platforms that support them, you can use cluster file system files to store datafiles for your cluster database.
- You can specify the raw devices for datafiles in a text file and provide it as input to the Database Configuration Assistant (DBCA). You can also place the SRVM Configuration Repository on a cluster file system.
- You can customize redo thread assignments to redo log groups. For example, you can customize the default redo log group-to-instance thread assignment using the DBCA Storage page.
- The DBCA displays an Instance Management summary page that shows the attributes of the instance you are adding or deleting.
- You can add multiple instances on a cluster node.
- When an operation fails, the DBCA reverses partially completed operations to restore your system to its previous state.
- Whether you use the DBCA in interactive or non-interactive mode, the DBCA displays a password management page and requires that you change the default passwords for the user accounts SYS and SYSTEM.
- Server Management Architecture Enhancements
- You can use one
gsdctl command syntax on all platforms to install, start, stop, and check the status of the GSD.
- Database Upgrade Assistant Enhancements
- The Database Migration Assistant has been renamed the Database Upgrade Assistant (DBUA). In addition, the DBUA is fully functional to upgrade your pre-release 2 (9.2) Oracle cluster database to Oracle9i Real Application Clusters release 2 (9.2).
- Dynamic Support for the Remote Listener Parameter
- You can use the
ALTER SYSTEM SET SQL statement to dynamically update the REMOTE_LISTENER initialization parameter. The DBCA also dynamically updates these parameters when you add or delete instances from your cluster database. When Oracle updates these parameters, the PMON process registers the new information with the listener.
- Parameter Changes for Manual Database Creation
- If you create a Real Application Clusters database manually, then you must set the value of the
ORACLE_SID environment variable to a unique value for all instances of a Real Application Clusters database.
- If you create a Real Application Clusters database manually, then you must set the value of the
INSTANCE_NUMBER initialization parameter to a unique integer for each instance. Oracle Corporation recommends that you set INSTANCE_NUMBER to the same value as the redo THREAD number for the instance.
