Oracle Parallel Server Getting Started Release 8.0.4 for Windows NT A55925-01 |
|
This chapter describes how to install and set up Oracle Parallel Server Manager (OPSM).
Specific topics discussed are:
You can control the activity of parallel servers and parallel server instances using the OPSM.
OPSM is a comprehensive and integrated system management solution for the Oracle Parallel Server. OPSM allows you to manage multi-instance databases running in heterogeneous environments through an open client-server architecture.
In addition to managing parallel databases, OPSM 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.
This console requires the following components:
OPSM uses the OPSCTL utility (installed on each node) to manage instances. This utility is run directly from the command line on a node, or called by the Oracle Enterprise Manager Console. OPSCTL gathers information about all the instances in a cluster from the TNSNAMES.ORA files. When OPSCTL is called by the Oracle Enterprise Manager Console, only one node's Intelligent Agent is used to communicate to OPSCTL. OPSCTL on that node then communicates to the other nodes through Net8.
Figure 6-1 shows how OPSCTL operates between the agent and the nodes:
The following requirements must be met in order to use OPSM from the Oracle Enterprise Manager Console:
The requirements for each node are:
Node Requirements | For additional information, see: |
---|---|
Ensure Oracle8 Enterprise Edition, Oracle Parallel Server Option, Oracle Parallel Server Manager Server, and Oracle Intelligent Agent are installed on each node in the cluster. |
"Step 1: Install Oracle8 Enterprise Edition and Oracle Parallel Server on Nodes" in Chapter 4, "Installing Oracle Parallel Server" |
The INIT_COM.ORA and INITSID.ORA initialization files must located in ORACLE_HOME\DATABASE. |
"Step 1: Copy Initialization Files" in Chapter 5, "Configuring Oracle Parallel Server" |
Use OPSCONF or Oracle Net8 Easy Config to create a TNSNAMES.ORA file for each node. Each instance must have a service name defined for it, which is used in defining the database links for the instances. Also, edit the LISTENER.ORA file accordingly if you use the Net8 Easy Config. |
"Step 6: Configure the Network" in Chapter 5, "Configuring Oracle Parallel Server" |
The SIDs of the instances in the parallel server must be different. |
|
In order to use the optional Oracle Performance Manager component: |
|
"Using OPSCONF" in Chapter 5, "Configuring Oracle Parallel Server", and "Step 3: Configure Oracle Performance Manager" in this chapter |
|
"Step 3: Configure Oracle Performance Manager" in this chapter |
The requirements for the Oracle Enterprise Manager Console are:
Oracle Enterprise Manager Console Requirements | For additional information, see: |
---|---|
Install your Enterprise Manager 1.5 software (with or without Oracle Enterprise Manager Performance Pack 1.5 option) on a Windows NT or Windows 95 computer. The Enterprise Manager Console is part of this installation. Oracle Enterprise Manager Performance Pack, which contains the Oracle Performance Manager application, is sold separately. |
"Step 1: Install Oracle Enterprise Manager" in this chapter. |
If the Oracle Enterprise Manager Console is on separate machine than the repository database, ensure that the Net8 Client is installed and properly configured on the Console. |
"Step 1: Install Oracle Enterprise Manager" in this chapter. and "Step 2d: Create Configuration Files" in this chapter |
Configure and connect to the repository database, including performing auto-discovery of your nodes. |
"Step 2: Configure Oracle Enterprise Manager" in this chapter. |
To use the optional Oracle Performance Manager component, specify the user preferences for your Oracle Parallel Server nodes and your Oracle Parallel Server databases. |
Chapter 2, "Oracle Parallel Server Management Operations," of the Oracle Parallel Server Management User's Guide. |
Set up your Oracle Enterprise Manager Console environment in either of two ways. Both environments are illustrated below:
You can install Oracle Enterprise Manager on a Windows NT or Windows 95 machine.
Installing Oracle Enterprise Manager includes:
The repository database is an Oracle8 Enterprise Edition database installed on the console if it is a Windows NT machine, or on another Windows NT machine where the Windows 95 or Windows NT console can connect.
To install the repository database:
Install Oracle8 Enterprise Edition on a Windows NT Server by following the instructions in Oracle8 Enterprise Edition Installation for Windows NT CD-ROM insert.
Oracle Enterprise Manager version 1.5 is installed on a console workstation, a Windows NT or Windows 95 client which connects to the Oracle8 repository database.
To install the Oracle Enterprise Manager:
Additional Information:
See the Oracle8 Enterprise Edition Installation for Windows NT CD-ROM insert for complete installation instructions. |
This table describes the tasks that must be performed to configure the two Oracle Enterprise Manager Console environments illustrated above. Each task is then described fully below.
Note: These instructions assume Oracle Enterprise Manager is already installed on a Windows NT or Windows 95 console workstation. See the Oracle8 Enterprise Edition Installation for Windows NT CD-ROM insert to install Oracle Enterprise Manager. |
Start OracleServiceSID, OracleHOME_NAMETNSListener80, OracleAgent and OraclePGMSService services are running on each node:
To start the Oracle services:
If all the services are already running, close the window and go to "Step 2b: Create a Repository User Account". If a service is not running, to Step 3 in this procedure.
Note: Prior to starting a OracleServiceSID service, the OraclePGMSService service must be running. If you used the CRTSRV script in "Step 4: Create Services" in Chapter 6, "Installing and Configuring Oracle Parallel Server Manager", OraclePGMSService automatically starts when the OracleServiceSID service is started. If you chose to create your services with another method, you can still have OraclePGMSService start up automatically with a OracleServiceSID service by entering the following at the command for each node:
|
C:\> NET START SERVICE
The SNMP_RW.ORA and SNMP_RO.ORA files are automatically generated when the Intelligent Agent is started. These files contains the listening address of the agent, the names of Net8 listener and Oracle database services it knows about, plus tracing parameters.
You need to have a user account with DBA (database administrator) privileges set up on the Oracle8 repository database. Oracle Enterprise Manager places its repository in the default tablespace of the user account to which you are connected when creating the repository. Because of this, Oracle Corporation recommends that you create a new user account so that the repository can be created in its own tablespace. It is also recommended that you create a new tablespace and the newly-created user be customized to use this tablespace as its default tablespace.
To create a repository user account on the Oracle8 repository database:
C:\> SVRMGR30 SVRMGR> CONNECT SYSTEM/MANAGER
SVRMGR> CREATE TABLESPACE REPOSIT_TABLESPACE DATAFILE 'path\DATAFILE' SIZE XM;
where X is the tablespace size in megabytes; 20 MB is a good starting place.
SVRMGR> CREATE USER USERNAME IDENTIFIED BY PASSWORD 2> DEFAULT TABLESPACE REPOSIT_TABLESPACE;
SVRMGR> GRANT DBA TO USERNAME IDENTIFIED BY PASSWORD;
SVRMGR> EXIT
Exiting Server Manager closes the database connection.
After a repository user account is created, an NT user account with the same user name as the repository user account must be created on the Oracle8 Enterprise Edition server.
To create a user account on each node of the cluster:
The User Manager window appears:
The New User dialog box appears:
The Group Memberships dialog box appears:
Administrators is added to the Member of list box.
The user is added and the User Manager window re-appears.
The User Rights Policy dialog box appears:
If Users does not exist, create it:
The Add Users and Groups dialog box appears:
Users appears in the Grant To list box.
The User Manager window re-appears.
If Oracle Enterprise Manager is installed on a Windows 95 or Windows NT client console separate from the machine on which the repository database is installed, you must configure the client machine so it can connect to the Oracle8 repository database. Use the Net8 Assistant to configure your network.
Before you can use Oracle Enterprise Manager Console, you need a repository on the console workstation where Oracle Enterprise Manager Console will run. The repository is a set of base tables in a database that contains status and environment information for your managed databases. A separate repository must be created for each user wanting to use Oracle Enterprise Manager Console.
The Oracle Enterprise Manager Console machine must also discover network services, such as databases, listeners, and nodes, to populate the Navigator tree. In addition to discovery, the Oracle Enterprise Manager Console must also be able to manage these services for the Job Scheduling and Event Management systems. This can be achieved with the Discovery Wizard.
When the agent starts up and is explicitly requested by the Oracle Enterprise Manager Console with the Navigator Discovery feature, the agent passes information from the Oracle Enterprise Manager Console to populate the Navigator tree.
To create a repository on the Oracle Enterprise Manager Console machine:
The Oracle Repository Manager window appears, prompting you to build the repository:
The repository is built. A dialog box asking if you want a quick tour of Oracle Enterprise Manger appears.
The Discover New Services Wizard appears:
Services are discovered when you see the dialog box below with a status of Discovered:
The Oracle Enterprise Manager Console appears with access to the Oracle Parallel Servers in the Navigator tree:
Additional Information:
See the Oracle Parallel Server Management User's Guide for further information about managing Oracle Parallel Servers and parallel server instances from Oracle Enterprise Manager Console. |
The Oracle Enterprise Manager's Oracle Performance Manager allows you to choose from a variety of tabular and graphic performance statistics for parallel servers. The statistics represent the aggregate performance for all instances running on a parallel server. The statistics are displayed in individual charts and include information on data block pings, lock activity, file I/O, and session and user information.
Note: The Enterprise Manager Intelligent Agent is not required by the Oracle Performance Manager, as its functions are performed using a database connection to the parallel server. |
Configuring the Oracle Performance Manager involves running the OPS_MON.SQL script located in ORACLE_HOME\OPS to run the following SQL scripts:
Script | Description |
---|---|
OPS_PACK.SQL |
Contains a set of PL/SQL procedures that are executed by Oracle Performance Manager to aggregate results from all instances of the parallel server. |
OPS_CTAB.SQL |
Contains a set of tables used to store the aggregated results. |
OPS_DBL.SQL1 |
Contains database links for each instance of the parallel server. |
1
OPS_DBL.SQL is not generated until the OPSCONF utility is run. |
To configure Oracle Performance Manager:
If it does not exist, go to Step 2. If it does exist, go to Step 3.
The format of ORACLE_HOME\OPS\OPS_DBL.SQL script file is as follows for each instance's entry:
DB_NAME |
database name from V$DATABASE |
NODE_NAME |
host name of the node on which the instance runs |
SID |
instance name |
SERVICE_NAME |
Net8 service name for the instance |
Below is an example OPS_DBL.SQL script for a database named "OPS" with four instances:
drop public database link ops@opshost13_ops1 / create public database link ops@opshost13_ops1 using 'ops1' / drop public database link ops@opshost14_ops2 / create public database link ops@opshost14_ops2 using 'ops2' / drop public database link ops@opshost15_ops3 / create public database link ops@opshost15_ops3 using 'ops3' / drop public database link ops@opshost16_ops4 / create public database link ops@opshost16_ops4 using 'ops4' /
C:\> CD ORACLE_HOME\OPS C:\ORACLE_HOME\OPS> SVRMGR30 SVRMGR> @OPS_MON.SQL
OPS_MON.SQL executes the following scripts:
SELECT NAME FROM V$DATABASE;
If you configured the Oracle Parallel Server with the default scripts, OPS
(the default name of the database) is returned to the screen.
Note: By default these parameters are not stored in the INIT_COM.ORA file. To increase the value of these parameters, you must add them to the INIT_COM.ORA file. |
Once the scripts have been executed, Oracle Enterprise Manager Oracle Performance Manager can be invoked against any instance of the parallel server. Oracle Performance Manager will execute a PL/SQL procedure on this instance to query for performance data from all instances of the parallel server via database links, aggregating the results into a set of database tables, which are then displayed in graphical form by Oracle Performance Manager.
To start Oracle Performance Manager:
The Login Information dialog box appears:
The Oracle Performance Manager window appears: