5
Installing and Configuring Oracle Parallel Server Management

Oracle Enterpise Manager supports administration of Oracle Parallel Server databases with Oracle Parallel Server Management. Oracle Parallel Server Management enables certain parallel components of Oracle Enterprise Manager. A performance monitoring tool called Oracle Performance Manager further enhances Oracle Parallel Server Management, allowing end users to monitor the global V$ view tables for performance.

This chapter describes how to install and configure Oracle Parallel Server Management.

Specific topics discussed are:

• Oracle Parallel Server Management Architecture

• Oracle Parallel Server Requirements

• Understanding Oracle Enterprise Manager Setup

• Installing Oracle Enterprise Manager

• Configuring Oracle Enterprise Manager

• Installing Oracle Performance Manager

• Configuring Oracle Performance Manager

Oracle Parallel Server Management Architecture

You can control the activity of Oracle Parallel Servers and their instances using Oracle Parallel Server Management. Oracle Parallel Server Management is a comprehensive and integrated system management solution for the Oracle Parallel Server. Oracle Parallel Server Management allows you to manage multi-instance databases running in heterogeneous environments through an open client-server architecture.

In addition to managing parallel databases, Oracle Parallel Server Management allows you to schedule jobs, perform event management, monitor performance, and obtain statistics to tune parallel databases.

Oracle Enterprise Manager provides database administrators (DBAs) with a powerful set of tools to manage, monitor, and administer even the most complex network of databases from a single workstation, called the Enterprise Manager Console.

Oracle Parallel Server Management within the Oracle Enterprise Manager context, is comprised of the following components:

Component	Description
Console	The Console is a graphical user interface that provides menus, toolbars, and launch palettes to allow access to Oracle tools. The Console is run from a client machine or a browser. The Console is comprised of four windows: Navigator window -- Contains an object browser which provides an organized, consistent and hierarchical view of the database objects in the network. Group window -- Provides a customized, graphical representation of key objects, created by the administrator. Event Management window -- Allows the administrator to remotely monitor for critical database and system events. Job window -- Provides the administrator with the ability to automate repetitive activities.
Management Server	The Management Server performs functions requested by the Console. Each Management Server manages exactly one domain. The domain is the logical grouping of machines for administrative purposes. The Management Server processes all system management tasks and administers the distribution of these tasks to the Oracle Intelligent Agents on the managed nodes.
Repository Database	All administrators in a domain share a repository, a set of database tables. The repository contains the accounts of every administrator in the domain. The Management Server uses the repository to store all system data, application data, and the state of managed nodes throughout the environment. The repository can be shared by multiple administrators. The repository must be on a separate machine from the nodes.
Oracle Intelligent Agents	Manages and completes tasks requested from the Console. Once installed, the Oracle Intelligent Agent: Listens for and responds to job requests initiated by the Console. Schedules job requests. Requests can include detecting and correcting abnormal conditions, performing standard database administration procedures, and monitoring events. The Oracle Intelligent Agent is installed on the nodes.
(Optional) Oracle Performance Manager	The Oracle Performance Manager allows you to choose from a variety of tabular and graphic performance statistics for Oracle Parallel Servers. The statistics represent the aggregate performance for all instances running on an Oracle Parallel Server. The statistics are displayed in individual charts and include information about data block pings, lock activity, file I/O, and session and user information.
(Optional) Oracle Data Gatherer	Gathers performance statistics for the Oracle Performance Manager. The Oracle Data Gatherer must be installed on a node somewhere on the network.

Oracle Parallel Server Management uses the following utilities to manage instances:

Component	Description
OPSCTL	Serves as a single point of control between the Oracle Intelligent Agent and the nodes. Only one node's Oracle Intelligent Agent is used to communicate to OPSCTL. OPSCTL on that node then communicates to the other nodes through Net8. OPSCTL is installed on the nodes.
OPS Communication Daemon (OPSD)	Receives requests from OPSCTL 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 OPSCTL. OPSD is installed on the nodes. OPSD is only implemented on UNIX platforms.

On UNIX, the Oracle Intelligent Agent invokes OPSCTL to executes jobs. OPSD then receives requests from OPSCTL, as shown in Figure 5-1:

Figure 5-1 OPSCTL Architecture for UNIX

On Windows NT, the Oracle Intelligent Agent invokes OPSCTL to executes jobs. OPSCTL then sends requests to Oracle Server Manager. Oracle Server Manager uses information from configured TNSNAMES.ORA files on the nodes to connect to a listener, which sends the OPSCTL requested action to the instance. Therefore, it is essential to have the TNSNAMES.ORA file configured on all nodes in cluster.

Figure 5-2 shows how OPSCTL operates between the agent and the nodes on Windows NT:

Figure 5-2 OPSCTL Architecture for Windows NT

Oracle Parallel Server Requirements

The following requirements must be met in order to use OPSM from the Console:

The requirements for each node are:

Node Requirements	For additional information, see:
Ensure Oracle8i Enterprise Edition, Oracle Parallel Server Option, and Oracle Intelligent Agent are installed on each node in the cluster.	Chapter 3, "Installation"
Each node must have a TNSNAMES.ORA configured. Create a TNSNAMES.ORA file so that each instance has a unique net service name. The net service names should contain the same service name but the instance names should be unique. The LISTENER.ORA file must be configured with information about the database on each node.	"Configuring Net8 for Nodes"
Each instance's Oracle System Identifiers (SIDs) in the Oracle Parallel Server must be unique.	"Unique Identification of Instances"

Understanding Oracle Enterprise Manager Setup

You can run the individual Oracle Enterprise Manager components on separate machines or combine different components on separate machines to collaboratively manage the complete Oracle environment. Two environments are shown below:

Environment 1: Console, Management Server and Repository on same machine

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

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

Figure 5-3 Console, Management Server and Repository on the Same Machine

Environment 2: Console, Management Server and repository on separate machines

The Repository is on a separate Windows NT or Solaris machine with an Oracle8i database installed that is only being used as a repository. The Oracle Intelligent Agent does not need to be running.

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

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

Figure 5-4 Console, Management Server and Repository on the Separate Machines

Installing Oracle Enterprise Manager

To install Oracle Enterprise Manager:

1. Install the repository database on a machine other than one of the Oracle Parallel Server nodes by following the instructions in:
   • Windows NT Server by following the instructions in Oracle8i Enterprise Edition Installation for Windows NT

   • Solaris 2.6 or Solaris 2.5.1 by following the instructions in Oracle8i Installation Guide for Sun Solaris

2. Install Oracle Enterprise Manager.

   You can install the Management Server and the Console on the machine where the repository database resides or individual machines. See Oracle Enterprise Manager Installation for complete installation instructions. Oracle Enterprise Manager is a separate CD from the Oracle8i Enterprise Edition CD.

Configuring Oracle Enterprise Manager

To configure Oracle Enterprise Manager, perform these tasks:

• Step 1: Configure Net8

• Step 2: Configure OPSCTL for UNIX Platforms

• Step 3: Configure Repository

• Step 4: Start Oracle Enterprise Manager Components

• Step 5: Discover Nodes

• Step 6: Specify Preferred Credentials for Nodes and Oracle Parallel Server Database

Step 1: Configure Net8

In order for Oracle Parallel Server nodes to be discovered by Oracle Enterprise Manager, a TNSNAMES.ORA file that contains net service name for each instance in the cluster must exist in the $ORACLE_HOME/network/admin on UNIX platforms or ORACLE_HOME\network\admin on Windows NT. To create this file, follow the procedures in:

"Creating Entries in TNSNAMES.ORA for Each Instance"

"Creating An Entry in the TNSNAMES.ORA File for the Database and Enabling Client Load Balancing"

The Console requires domain-qualified net service names. Therefore, ensure all the net service names are domain qualified.

A sample TNSNAMES.ORA file is shown below:

op1.us.oracle.com = 
  (description = 
   (address = 
       (protocol = tcp) 
       (host = opshp1) 
       (port = 1521))
   (connect_data = 
       (service_name = op.us.oracle.com)
       (instance_name = op1))
op2.us.oracle.com  = 
  (description = 
    (address = 
       (protocol = tcp) 
       (host = opshp2) 
       (port = 1521))
    (connect_data = 
       (service_name = op.us.oracle.com)
       (instance_name = op2))

Step 2: Configure OPSCTL for UNIX Platforms

OPSCTL requires additional configuration if Oracle Parallel Server is installed on UNIX:

1. Create an oratab entry for the name of the Oracle Parallel Server The syntax for this entry is:

   db_name: oracle_home:N
   
   

   where db_name is the database name given to your Oracle Parallel Server database. oratab should be in /etc/oratab or /var/opt/oracle/oratab depending on the platform.

2. You must manually create an DB_NAME.CONF file on each node in $ORACLE_HOME/ops. Do this for the first node and then FTP this file to all nodes in the cluster.

   The OPSCTL utility requires the existence of this file to run properly, even if this file is empty. Depending on your platform, you may need to set the node_list parameter. For example,

   node_list = "1,3-7"
   
   

   Other optional parameters may be set, as described in "Creating the DB_NAME.CONF File".

3. Ensure that OPSD has been started on each managed node by the oracle account at system startup. OPSD resides in $ORACLE_HOME/bin.

Step 3: Configure Repository

Use the Configuration Assistant to create and load your version 2 repository. The repository is a set of tables in an Oracle database which stores data required by the Oracle Enterprise Manager. See the Oracle Enterprise Manager Configuration Guide for complete configuration instructions.

Step 4: Start Oracle Enterprise Manager Components

To use the Console, start the following components:

• Oracle Intelligent Agent

• Management Server

• Console

Oracle Intelligent Agent

Start the Oracle Intelligent Agent on each of the nodes.

At an operating system prompt, enter the command:

lsnrctl dbsnmp_start

On Windows NT, you can also use the Control Panel:

1. Double-click the Services icon in the Control Panel window.

2. Select the OracleHOME_NAMEAgent service.

3. Click Start to start the service.

   Note: Additional Oracle Intelligent Agent configuration is required if the ORACLE_HOME is shared, as described in "Oracle Intelligent Agent Configuration".

Management Server

Note: Your Management Server service is started automatically during repository creation if you had launched the Configuration Assistant from the Oracle Enterprise Manager installation.

To start the Management Server, at an operating system prompt, enter:

oemctrl start oms
     


         

The command string is case-sensitive and must be entered with lowercase characters.

To start the Management Server in the background on Solaris, enter:

% oemctrl start oms&

On Windows NT, you can also use the Control Panel:

1. Double-click the Services icon in the Control Panel window.

2. Select the OracleHOME_NAMEManagementServer service.

3. Click Start to start the service.

The Management Server looks for the OMSCONFIG.PROPERTIES file in the $ORACLE_HOME/sysman/config directory on UNIX and ORACLE_HOME\sysman\config directory on Windows platforms. It contains the connect information required by the Management Server to start up.

Note: You should always use the Oracle Enterprise Manager Configuration Assistant to create a repository or to change the repository's connect information. The information is encrypted in the OMSCONFIG.PROPERTIES file. For detailed information editing this file, see the Oracle Enterprise Manager Configuration Guide.

Console

The Console gives you a central point of control for the Oracle environment through an intuitive graphical user interface (GUI) that provides powerful and robust system management.

To start the Enterprise Manager Console:

1. At an operating system prompt, enter:

   oemapp console
       
   
            

   The command string is case-sensitive and must be entered with lowercase characters.

   On Windows NT, you can also choose Start > Programs > Oracle - HOME_NAME > Oracle Enterprise Management > Oracle Enterprise Manager Console.

2. If you are logging in to the Console for the first time, after the first login dialog appears, type in the default credentials for the super administrator account:

   Administrator = sysman

   Password = oem_temp

   
   
3. Select a Management Server which is configured with the repository you want to access from the Management Server drop-down list.

   If the name of the Management Server you want to use does not appear, follow the instructions below:

   1. Click the Management Servers button. The Management Servers dialog appears.

   2. Click the Add button. The Add Management Server dialog appears.

   3. Type in the name of the Management Server and click OK.

   4. Select the Management Server from the pull-down list.

4. A Security Warning dialog appears where you can change your password. The new password you enter will be the password you use to log in to the Console for subsequent logins.

   
   

   Note: Passwords must have no more than 8 characters.

   The Console appears:

   
   

   The first time you start the Console, you must login as the super administrator. After other administrator accounts have been created using the super administrator account, you can login as an administrator.

Step 5: Discover Nodes

After the Console has been started, the Console machine must also discover network services, such as databases, listeners, and nodes, to populate the Navigator tree.

To discover services:

1. Choose Discover Node from the Navigator menu.

   The Discover Nodes dialog appears:

   
   

   Note: Prior to discovering Oracle Parallel Server nodes, a single-instance must be discovered first. If Databases folder does not exist in the Navigator window, enter the host name of single-instance database. After the single-instance database is discovered, perform discovery of the nodes. If the repository database is located on the machine with the Console and the Oracle Intelligent Agent is installed and running, the repository database will be discovered automatically.

2. Enter the host names of Oracle Parallel Server nodes.

   Successful discovery results in the following:

   
   

   Ignore the VD-4520 errors for the second and subsequent nodes. The Console considers it an error when a database target is discovered on multiple nodes, but the Oracle Parallel Server discovery reports that the Oracle Parallel Server database exists on each of the nodes. Simply click OK:

   
   

   An unsuccessful discovery is usually the result of the Oracle Intelligent Agent not being started on the node. For further information about the discovery process and handling errors, see "Handling Auto-Discovery Failures".

3. Click Close to acknowledge the status dialog.

   Once a node is identified, Oracle Enterprise Manager automatically discovers (locates) all the databases and other services running on the managed nodes. When a node is discovered, the services located are:

   • the database it supports

   • its instance

   • listener

   When an Oracle Parallel Server instance is discovered, a new folder named Parallel Server Instances is created for the node it belongs to.

   By expanding and contracting the folders in the Navigator window, you can see the object discovered.

   Below is an example of an Oracle Parallel Server database named OP with instance OP1 on host opshp1 and OP2 on opshp2:

   
   

Step 6: Specify Preferred Credentials for Nodes and Oracle Parallel Server Database

Oracle Enterprise Manager must be configured with preferred user credentials in order to perform certain functions. These credentials are used when establishing connections to the Oracle Parallel Server, such as when the Oracle Parallel Server is expanded in the Console's navigator. The startup and shutdown operations also use the credentials.

A valid DBA user with SYSDBA or SYSOPER privileges must be identified for the Oracle Parallel Server database in order to expand the Oracle Parallel Server database in the Navigator window or to perform connection and job execution operations. If a valid database user is not identified, you will be prompted each time you try to connect to the database.

Likewise, an operating system user must be identified 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 have configure a user that has operating system access to the node. You should enter node credentials for each node that was discovered.

This section covers the following topics:

• Create an Operating System Account

• Grant SYSDBA or SYSOPER Privileges to a User

• Set User Credentials in the Console

Create an Operating System Account

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

On Windows NT, you will need to create a NT user account in the following fashion. To create a user account on each node of the cluster:

1. Choose Start > Programs > Administrative Tools (Common) > User Manager:

   The User Manager window appears:

   
   
2. Choose New User from the User menu.

   The New User dialog box appears:

   
   
3. Enter the appropriate information in the dialog box:
   1. Enter a user name and password.

   2. Make sure the User Must Change Password at Next Logon check box is not checked and Password Never Expires check box is checked.

   3. Make the user a member of the Administrator's group by clicking Groups.

      The Group Memberships dialog box appears:

      
      
   4. Select Administrators from the Not member of list box, then click <- Add.

      Administrators is added to the Member of list box.

   5. Click OK to close the Group Memberships dialog box and return to the New User dialog box.

4. Click OK in the New User dialog box.

   The user is added and the User Manager window re-appears.

5. Select the newly-created user, then choose User Rights from the Policies menu.

   The User Rights Policy dialog box appears:

   
   
6. Click the Show Advanced User Rights check box, then select Log on as a batch job from the Right drop-down list box.

7. Select the newly created from the Grant To list box.

   If user does not exist, create it:

   1. Click Add.

      The Add Users and Groups dialog box appears:

      
      
   2. Select the name of the local host machine from the List Names From drop-down list box.

   3. Click the Show Users button.

   4. Select the user from the Names list box, then click Add:

      
      

      The user displays in the Add Names list box.

   5. Click OK.

      The user appears in the Grant To list box in the User Rights Policy dialog box.

8. Click OK in the User Rights Policy dialog box in the User

   The User Manager window re-appears.

9. Choose Exit from the User menu.

Grant SYSDBA or SYSOPER Privileges to a User

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

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

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

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

Set User Credentials in the Console

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

To set credentials:

1. Choose Preferences from the System menu.

   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.

5. Click on the Oracle Parallel Server database (identified by the Parallel Server service type).

6. Enter a DBA user name and password that has SYSDBA or SYSOPER privileges for the database, such as SYSTEM/MANAGER, and select SYSDBA or SYSOPER from the Role drop-down menu.

   Important: The SYSDBA or SYSOPER privilege is required for Oracle Parallel Server database and instance startup and shutdown.

7. If you plan to use the Oracle Performance Manager application, click on an instance (identify by the Parallel Server Instance service type), enter a user name and password that can connect to instance, select NORMAL role from the drop-down menu.

8. Click OK.

See also:

• "Managing Instances Using Oracle Parallel Server Management" for more information about using the Console for Oracle Parallel Server

• Oracle Enterprise Manager Administrator's Guide for general Console administration information

• Oracle Enterprise Manager Configuration Guide for optional Console configuration

Installing Oracle Performance Manager

To install Oracle Performance Manager:

1. Install the Oracle Diagnostics Pack. See Oracle Diagnostics Installation for complete installation instructions. Oracle Diagnostics Pack is on another CD from Oracle Enterprise Manager, requiring a separate license.

2. If you do not plan on using the Oracle Data Gatherer on one of the nodes, install the Oracle Intelligent Agent somewhere on the network. The Oracle Data Gatherer, which is required for Oracle Performance Manager, is automatically installed with the Oracle Intelligent Agent. The Oracle Intelligent Agent may be selected when the Custom install type is chosen in the Oracle8i Enterprise Edition CD-ROM. See the following for further information:
   • Oracle8i Installation Guide for Sun Solaris, HP 9000 or AIX-based systems

   • Oracle8i Enterprise Edition Installation for Windows NT

     Note: The Oracle Performance Manager can be run in addition to or without the Oracle Enterprise Manager. If you choose to run this product stand-alone, Oracle Enterprise Manager does not have to be configured.

Configuring Oracle Performance Manager

Note: Oracle Enterprise Manager and the Oracle Intelligent Agent are not required by the Oracle Performance Manager, as its functions are performed using a database connection to the Oracle Parallel Server.

To configure Oracle Performance Manager, perform these tasks:

• Step 1: Configure Net8

• Step 2: Start Oracle Performance Manager Components

Step 1: Configure Net8

When Oracle Performance Manager gathers statistics for an Oracle Parallel Server database, it performs a Net8 connection. The machine where Oracle Data Gatherer runs must have a TNSNAMES.ORA file configured with net service names.

A net service name must be created for each Oracle Parallel Server instance. To create this file, follow the procedures in "Creating Entries in TNSNAMES.ORA for Each Instance".

Step 2: Start Oracle Performance Manager Components

To use the Oracle Performance Manager, start the following components:

• Oracle Data Gatherer

• Oracle Performance Manager

Oracle Data Gatherer

Start the Oracle Data Gatherer on at least one of the Oracle Parallel Server nodes.

At an operating system prompt, enter:

vppcntl -start

On Windows NT, you can also use the Control Panel:

1. Double-click the Services icon in the Control Panel window.

2. Select the OracleHOME_NAMEDataGatherer service.

3. Click Start to start the service.

Oracle Performance Manager

1. Start Oracle Performance Manager in one of two ways:
   • Standalone

     At an operating system prompt, enter:

     vtm
     
     

     On Windows NT, you can also choose Start > Programs > Oracle - HOME_NAME > Oracle Diagnostics Pack > Performance Manager.

     The Performance Manager Login dialog box appears:

     
     

     Select whether to log on to the Management Server or in standalone fashion. If Login to Oracle Management Server is chosen, additionally enter the Oracle Enterprise Manager administrator user name, password and location of the Management Server.

   • Started from Console

     Choose Oracle Performance Manager in the Diagnostics Pack toolbar or from the Tools menu choose Diagnostics Pack, and click Oracle Performance Manager.

     When Oracle Performance Manager is started from the Console, the Oracle Enterprise Manager repository log on credentials are automatically passed to Oracle Performance Manager, thereby providing you with access to all repository-based information. Also, if a service is selected in the Console Navigator window when Oracle Performance Manager is started, Oracle Performance Manager connects to the database.

   The first time you log on to Oracle Performance Manager with the Login to Oracle Management Server option, the Oracle Enterprise Manager Repository Manager window appears, prompting you to build Oracle Performance Manager components in the repository database.

   
   
2. Click OK to build the Oracle Performance Manager component.

   The Oracle Performance Manager starts:

   
   

Step 3: Accessing Oracle Parallel Server Charts

Oracle Parallel Server charts may be accessed from the Parallel Server Instance folder or the Databases folder.

Parallel Server Instances Folder

If the log in occurred from the Console or the Login to the Oracle Management Server option was selected in the Performance Manager Login dialog box, the Parallel Server Instances folder can be expanded to display the instances, from which the list of available charts may be obtained:

Once the Parallel Server Instances folder is expanded, select User Defined Charts, then select Parallel Server.

If the credentials for the instances was not performed, as described in "Step 6: Specify Preferred Credentials for Nodes and Oracle Parallel Server Database", the following error appears when you try to expand an instance:

Click Continue to acknowledge the message. The Parallel Server Instance Logon prompts you for the required instance credentials:

Supply the required information, including a database user and password and location of the Oracle Data Gatherer. The Oracle Data Gatherer should be installed and running on some machine in the network. The instance can now be expanded.

See Chapter 7, "Monitoring Performance with Oracle Parallel Server Management Charts" for more information about viewing Oracle Parallel Server reports and the Oracle Enterprise Manager Performance Monitoring and Planning Guide for more general information about the Oracle Performance Manager application.

Databases Folder

If the log in occurred in standalone mode or the Standalone, no repository connection option was selected in the Performance Manager Login dialog box, you can access the Oracle Parallel Server charts from the Databases folder:

1. Click the Databases folder.

2. Choose Add New Service from the File menu.

   The Database dialog prompts you for the required Oracle database credentials:

   
   
3. Supply the required information, including a database user and password, net service name in Service field, and location of the Oracle Data Gatherer. The Oracle Data Gatherer should be installed and running on some machine in the network.

4. Expand the Databases folder, select User Defined Charts, then select Parallel Server.

   
   

See Chapter 7, "Monitoring Performance with Oracle Parallel Server Management Charts" for more information about viewing Oracle Parallel Server reports and the Oracle Enterprise Manager Performance Monitoring and Planning Guide for more general information about the Oracle Performance Manager application.

---