7
Configuration Highlights for Enterprise Manager in Real Application Clusters Environments

This chapter describes the highlights of installing and configuring Oracle Enterprise Manager for use in Real Application Clusters environments. The topics in this chapter include:

• Server Management Architecture for Enterprise Manager in Real Application Clusters
• Server Management Requirements for Enterprise Manager in Real Application Clusters
• Understanding the Enterprise Manager Setup in Real Application Clusters
• Configuring Enterprise Manager for Real Application Clusters Management
• Using Oracle Performance Manager for Real Application Clusters Management

Server Management Architecture for Enterprise Manager in Real Application Clusters

Oracle Enterprise Manager (EM) supports the administration of cluster databases by using Server Management (SRVM) to perform Real Application Clusters-specific tasks. SRVM includes all the components of EM, such as the Intelligent Agent Control Utility, the Server Control Utility (SRVCTL), and the Global Services Daemon.

EM provides tools to manage, monitor, and administer even the most complex network of databases from a single point known as the Enterprise Manager Console. You can use EM with single-instance Oracle databases as well as with Real Application Clusters databases. Within the context of EM, SRVM includes 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 Remote Method Invocation (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 a SRVCTL command to execute administrative tasks, such as startup or shutdown. You execute a SRVCTL command on any node and the results are returned to you. The GSD is installed on the nodes and is implemented on UNIX, Windows NT, and Windows 2000 operating systems.

The Global Services Daemon (GSD) enables EM 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 multiple GSDs then receive a request from an SRVCTL command, and the results are returned to SRVCTL, then to the Agent, and then to the console 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

Server Management Requirements for Enterprise Manager in Real Application Clusters

Each node must meet the requirements as shown in Table 7-2 to perform Real Application Clusters-specific tasks by way of SRVM from the Console. You met these requirements if you followed the database creation procedures described in Part I of this book, "Setup and Configuration of Oracle9i Real Application Clusters".

Table 7-2  Server Management Node Requirements

Node Requirements	References
Ensure Oracle9i Enterprise Edition, with Real Application Clusters, and the Oracle Intelligent Agent are installed on each node in the cluster.	Part I of this book, "Setup and Configuration of Oracle9i Real Application Clusters".
Each instance's Oracle System Identifiers (sid) in the cluster database must be unique.	Part I of this book, "Setup and Configuration of 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 III of this book, "Oracle Enterprise Manager Installation Highlights for Real Application Clusters".
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 III of this book, "Oracle Enterprise Manager Installation Highlights for Real Application Clusters".
The oratab file must be configured on UNIX for the agent to discover the database.	Part I of this book, "Setup and Configuration of Oracle9i Real Application Clusters".
Make sure that the Global Services Daemon is running on each managed node using the gsdctl stat command by executing it from the $ORACLE_HOME/bin directory. On Windows NT and Windows 2000 platforms, this daemon is called OracleGSDService and you should run the gsdctl stat command from the %ORACLE_HOME%\bin directory.	Part I of this book, "Setup and Configuration of Oracle9i Real Application Clusters".
The srvcfg cluster configuration file must have entries for the cluster database and instances.	Part I of this book, "Setup and Configuration of Oracle9i Real Application Clusters".

Understanding the Enterprise Manager Setup in Real Application Clusters

You can run the individual EM components on separate machines or combine the components on separate machines to collaboratively manage the complete Oracle environment. You can also run the console in standalone mode as described under the following headings:

• Using the Console, Management Server, and Repository on the Same Machine
• Using the Console, Management Server, and Repository on Separate Machines

Using the Console, Management Server, and Repository on the 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 using an Oracle database as a repository. Although the nodes share an Oracle database, the repository is not created in the shared database. In addition, the 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

Using the 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 that is used solely as a repository as shown in Figure 7-3. The Oracle Intelligent Agent does not need to be running on the machine that only hosts the repository.

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

Notes for Running the Console in Standalone Mode

To run the EM console in standalone mode without a connection to the Management Server, manually enter the connection details for the cluster database instances that you want to manage. If you have a tnsnames.ora file, then you can use the cluster databases listed in it as targets.

If you have entered the connection details for the cluster database, the database is displayed as a single instance database target. In this case, the startup and shutdown menu items would only start and stop the instance to which the connection has been established.

Configuring Enterprise Manager for Real Application Clusters Management

This section describes the installation and configuration process for EM in Real Application Clusters.

Task 1: Oracle Enterprise Manager Installation

1. Install EM. Note that you can either install a complete Oracle9i database or Oracle9i Management and Integration. (EM 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 EM. If you install an Oracle9i Management and Integration, then EMCA runs automatically.

3. Start the Oracle Intelligent Agent on each of the nodes using the Intelligent Agent Control Utility
4. Start the Management Server with the Management Server control utility.
5. Start the Enterprise Manager Console.

   See Also: Oracle Enterprise Manager Configuration Guide for complete EM configuration instructions. Oracle9i Installation Guide Release 2 (9.2.0.1) for UNIX Systems: AIX-Based Systems, Compaq Tru64, HP 9000 Series HP-UX, Linux Intel, and Sun Solaris, and Oracle9i Database Installation Guide for Windows to install EM without Oracle Diagnostics Pack Oracle Enterprise Manager Installation to install EM and the Oracle Diagnostics Pack

Task 2: Specify Preferred Credentials for Nodes and Database

You must configure the EM with two types of credentials:

• Cluster Database credentials
• Node credentials

EM uses cluster database credentials when establishing connections to Real Application Clusters, such as when the cluster or database instance is expanded in the Console's navigator. Startup and shutdown operations use the node credentials in addition to the cluster database credentials.

The cluster database 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, EM 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 reside on the node where the Oracle Intelligent Agent runs. 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.

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:

SQL>GRANT sysdba to username;
SQL>GRANT sysoper to username; 

Task 5: Set Preferred Credentials in the Console

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

To set credentials:

1. Choose Configuration > Preferences.

   The Edit Administrator Preferences dialog box appears.

2. Click the Preferred Credentials tab to enter credentials for various target types.
3. Click a node (identified by the Node target type) and enter the operating system user name and password.
4. Perform Step 3 for each node in your cluster.
5. Click the cluster database identified by the target 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 cluster database, instance startup and shutdown, initialization parameter management, and resource plan management.

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

Using Oracle Performance Manager for Real Application Clusters Management

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.

Task 2: Accessing Statistical Charts

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

Cluster Database 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 Cluster Database Instances folder to display the instances from which the list of available charts can be obtained.

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.

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