7
Installation and Configuration Highlights for Oracle Enterprise Manager in Real Application Clusters

Oracle Enterprise Manager supports the administration of cluster databases with Server Management (SRVM). SRVM was previously known as Oracle Parallel Server Management (OPSM). SRVM enables the clustered components of Oracle Enterprise Manager. A performance monitoring tool called Oracle Performance Manager further enhances SRVM. It enables you to monitor cluster database performance using the global V$ view tables. This chapter describes how to install and configure SRVM. The topics in this chapter include:

• Server Management Architecture

• SRVM Requirements

• Understanding the Oracle Enterprise Manager Setup

• Installing and Configuring Oracle Enterprise Manager in Real Application Clusters

• Configuring Oracle Performance Manager

• Additional Notes for Running the Console in Stand-Alone Mode

Server Management Architecture

You can use Server Management (SRVM) to control the activity of Real Application Clusters and their instances. SRVM is a comprehensive, integrated system management solution for Real Application Clusters. SRVM enables you to manage cluster databases through an open client-server architecture.

Oracle Enterprise Manager provides tools to manage, monitor, and administer even the most complex network of databases from a single workstation known as the Enterprise Manager Console. You can use Oracle Enterprise Manager with single instance databases as well as with Real Application Clusters databases.

See Also: Oracle9i Real Application Clusters Administration for further information about using views not available with Oracle Enterprise Manager, and for more detail on monitoring and tuning Real Application Clusters databases

Within the context of Oracle Enterprise Manager, SRVM contains the instance management utilities shown in Table 7-1:

Table 7-1 SRVM Instance Management Utilities

Component	Description
Server Control (SRVCTL)	The SRVCTL Utility serves as a single point of control between the Oracle Intelligent Agent and each node. SRVCTL uses RMI to communicate with the Global Services Daemon on other nodes. SRVCTL is installed on the nodes.
Global Services Daemon (GSD)	Global Services Daemon (GSD) receives requests from SRVCTL to execute administrative job tasks, such as startup or shutdown. The command is executed locally on each node, and the results are sent back to SRVCTL. GSD is installed on the nodes. GSD is implemented on Windows NT, Windows 2000, and UNIX operating systems.

The Global Services Daemon (GSD) background process allows you to use Oracle Enterprise Manager or the SRVCTL utility to perform system management tasks. It is important that you do not kill this process.

The Oracle Intelligent Agent invokes SRVCTL to execute jobs. The GSD then receives requests from SRVCTL, as shown in Figure 7-1:

Figure 7-1 SRVCTL Architecture for UNIX and Windows NT and Windows 2000

Text description of the illustration pss81008.gif

See Also: Oracle9i Real Application Clusters Administration for information on using SRVCTL

SRVM Requirements

You must meet the requirements for each node to use SRVM from the Console as shown in Table 7-2. These requirements should be satisfied if you followed the database creation procedures described in Part One of this book, "Installing Oracle9i Real Application Clusters".

Node Requirements	References
Ensure Oracle9i Enterprise Edition, Real Application Clusters Option, and Oracle Intelligent Agent are installed on each node in the cluster.	Part One of this book, "Installing Oracle9i Real Application Clusters".
Each instance's Oracle System Identifiers (sid) in the cluster database must be unique.	Part One of this book, "Installing Oracle9i Real Application Clusters".
Each node must have a tnsnames.ora file configured with a net service name entry for: The database Each instance	Part Three of this book, "Oracle Enterprise Manager Installation Highlights".
The listener.ora file must define a listener for each node with: A TCP/IP address for the listener An entry for the sid of the node's instances in the sid_LIST_listener_name section.	Part Three of this book, "Oracle Enterprise Manager Installation Highlights".
The oratab file must be configured on UNIX for the agent to discover the database.	Part One of this book, "Installing Oracle9i Real Application Clusters".
For UNIX, Windows NT, and Windows 2000, ensure GSD has been started on each managed node by the oracle account at system startup. GSD resides in $ORACLE_HOME/bin on UNIX and in %ORACLE_HOME%\bin on Windows NT and Windows 2000.	Part One of this book, "Installing Oracle9i Real Application Clusters". This part describes how to run the command gsd in the ORACLE_HOME/bin directory.
The srvcfg cluster configuration file must have entries for the cluster database and instances.	Part One of this book, "Installing Oracle9i Real Application Clusters".

Understanding the Oracle Enterprise Manager Setup

You can run the individual Oracle Enterprise Manager components on separate machines or combine components on separate machines to collaboratively manage the complete Oracle environment. Two environments are described under the following headings:

• Console, Management Server, and Repository on Same Machine

• Console, Management Server, and Repository on Separate Machines.

Console, Management Server, and Repository on Same Machine

The Console, with the aid of the Management Server, remotely manages the databases for both nodes as shown in Figure 7-2. The Console and the Management Server are running on a Solaris, Windows NT, or Windows 2000 machine with an Oracle database installed that is only used as a repository. The Oracle Intelligent Agent does not need to be running.

The nodes share an Oracle database. The repository is not created in this database, and Oracle Intelligent Agent runs on both nodes.

Figure 7-2 Console, Management Server, and Repository on the Same Machine

Text description of the illustration pss81011.gif

Console, Management Server, and Repository on Separate Machines

The Repository is on a separate Solaris, Windows NT, or Windows 2000 machine with an Oracle database installed that is used solely as a repository as shown in Figure 7-3. The Oracle Intelligent Agent does not need to be running.

The Management Server remotely manages the databases for the Console on a Windows machine. The Console is running on a Windows NT, Windows 95, Windows 98, or Windows 2000 machine.

The nodes run an Oracle database. The repository is not created in this database, and the Oracle Intelligent Agent runs on both nodes.

Figure 7-3 Console, Management Server, and Repository on Separate Machines

Text description of the illustration pss81010.gif

Installing and Configuring Oracle Enterprise Manager in Real Application Clusters

This section describes the installation and configuration process for Oracle Enterprise Manager in Real Application Clusters.

Task 1: Oracle Enterprise Manager Installation

1. Install Oracle Enterprise Manager. Note that you can either install a complete Oracle9i database or Oracle9i Management and Integration. (Oracle Enterprise Manager is included in both software packages.)

2. Use the Enterprise Manager Configuration Assistant (EMCA) to create and load your version 2 repository. The repository is a set of tables in an Oracle database that stores data required by Oracle Enterprise Manager.

3. Start the Oracle Intelligent Agent on each of the nodes.

4. Start the Management Server.

5. Start the Enterprise Manager Console.

   See Also: Oracle Enterprise Manager Configuration Guide for complete Oracle Enterprise Manager configuration instructions. Oracle9i Installation Guide for Compaq Tru64, Hewlett-Packard HPUX, IBM AIX, Linux, and Sun Solaris-based systems, and Oracle9i Database installation guide for Windows to install Oracle Enterprise Manager without Oracle Diagnostics Pack Oracle Diagnostics Pack Installation to install Oracle Enterprise Manager and Oracle Diagnostics Pack

Task 2: Specify Preferred Credentials for Nodes and Database

You must configure the Oracle Enterprise Manager with preferred user credentials to perform certain functions. Oracle Enterprise Manager uses these credentials when establishing connections to Real Application Clusters, such as when the database is expanded in the Console's navigator. Startup and shutdown operations also use the credentials.

The credentials you configure must identify a valid DBA user with SYSDBA or SYSOPER privileges for the database on the target node. This enables you to expand the Database folder in the Navigator window and to perform connection and job execution operations. If you do not identify a valid database user, Oracle Enterprise Manager prompts you for this information each time you attempt to connect to the database.

You must also identify an operating system user to run jobs on particular nodes, such as starting or stopping an instance. Although you submit a job from the Console, the job scripts themselves reside on the Oracle Intelligent Agent on the nodes. For this reason, you must configure a user that has operating system access to the node.

To complete the installation process, you must complete the following tasks related to creating accounts, granting privileges, and setting credentials.

Task 3: Create an Operating System Account

On UNIX, this user can be the oracle account set up during the installation process.

On Windows NT or Windows 2000, create a Windows user account. You must be a member of the "Administrators" group and you must also select the Logon on as a batch job User Right policy.

See Also: Microsoft Corporation documentation at http://www.microsoft.com/ for details on setting up User Accounts, Group Membership, and User Right Policy information.

Task 4: Grant SYSDBA or SYSOPER Privileges to a Database User

Identify a current user, such as SYSTEM, or create a new user that will connect, start, and stop the database.

Once you identify a user, ensure it has SYSDBA or SYSOPER privileges. SYSDBA and SYSOPER privileges contain all the system privileges you need to manage the database.

To grant SYSDBA or SYSOPER privileges to a user, use the GRANT command:

GRANT sysdba to username;
GRANT sysoper to username; 

Task 5: Set User Credentials in the Console

You must set user credentials for the database and each node.

To set credentials:

1. Choose System > Preferences.

   The Edit User Preferences dialog box appears.

2. Click the Preferred Credentials tab to enter credentials for various service types:

3. Click on a node (identified by the Node service type) and enter the operating system user name and password.

4. Perform Step 3 for each node in your cluster.

5. Click on the Real Application Clusters database (identified by the service type)

   Enter a DBA user name and password that has SYSDBA or SYSOPER privileges for the target database, such as SYSTEM/password, and select SYSDBA or SYSOPER from the Role list.

   Important: The SYSDBA or SYSOPER privilege is required for the Real Application Clusters database and for instance startup and shutdown.

6. To use the Oracle Performance Manager application, click on an instance (identified by the Instance service type), enter a user name and password that can connect to the instance, select NORMAL role from the drop-down menu.

7. Click OK.

   See Also: Oracle Enterprise Manager Administrator's Guide for general Console administration information Oracle Enterprise Manager Configuration Guide for optional Console configuration

Configuring Oracle Performance Manager

Note: Oracle Enterprise Manager is not required by the Oracle Performance Manager because its functions are performed using a database connection to the cluster database. Oracle Performance Manager can be run with or without running Oracle Enterprise Manager. If you run this product as a stand-alone product, then you do not have to configure Oracle Enterprise Manager.

To configure Oracle Performance Manager, perform the following tasks:

Task 1: Start Oracle Performance Manager

Start Oracle Performance Manager in Standalone mode or from the Console.

See Also: Oracle Enterprise Manager Administrator's Guide for general Console administration information Oracle Enterprise Manager Configuration Guide for optional Console configuration

Task 2: Accessing Statistical Charts

You can access statistical charts from the Cluster Databases folder or from the Databases folder.

Instances Folder

If the login occurred from the Console or if you selected the Login to the Oracle Management Server option in the Performance Manager Login dialog box, then you can expand the Instances folder to display the instances from which the list of available charts can be obtained.

Note: When you are accessing a cluster database of version 8.1.7 and earlier, you will see charts referred to with Oracle Parallel Server names. When accessing a cluster database of version 9.0.1 and later, you will see charts referred to with Real Application Clusters names.

Once you expand the Instances folder, expand Real Application Clusters.

If you did not specify credentials for the instances, as described in "Task 2: Specify Preferred Credentials for Nodes and Database", then the Instances Logon dialog appears when you attempt to expand an instance.

See Also: Oracle9i Real Application Clusters Deployment and Performance for detailed information on the Performance Manager charts

Enter a database user and password.

Databases Folder

If the login occurred in standalone mode or if you selected the Standalone, no repository connection option in the Performance Manager Login dialog box, then you can access the Real Application Clusters charts from the Databases folder:

1. Click the Databases folder.

2. Choose File > Add New Service.

   The Database Logon dialog prompts you for the required Oracle database credential.

3. Enter the required information, including a database user name and password, and a net service name in the Service field.

4. Expand Databases > Cluster Databases (or Parallel Servers, depending on the software version you are running).

   See Also: Oracle9i Real Application Clusters Deployment and Performance for more information about viewing Real Application Clusters performance statistics Getting Started with the Oracle Standard Management Pack for general information about the Oracle Performance Manager application

Additional Notes for Running the Console in Stand-Alone Mode

To run the Oracle Enterprise Manager console in stand-alone mode without a connection to the Management Server, a tnsnames.ora file must be created. It must contain entries for the database and each instance.

When running the DBA Studio application in stand-alone mode, the Startup and Shutdown menu items start and stop an individual instance, not the Real Application Clusters database.