6 Configuring Server Pools and Oracle Enterprise Manager Database Control

6.1.1 Oracle RAC One Node and Server Pools

Note the following about Oracle RAC One Node and server pools:

• Oracle RAC One Node runs only in one server pool. This server pool is treated the same as any other server pool.

• Online relocation of an Oracle RAC One Node database instances permits planned migrations of an Oracle RAC One Node database from one node to another node. Relocations must always be within a server pool.

• An Oracle RAC One Node database can be a Data Guard physical standby.

6.1.2 Policy-Based Cluster and Capacity Management

Using policy-based server pool management, database administrators define resource requirements for the workload, including the following:

• Defining the number of servers or instances preferred for the application. Oracle Clusterware automatically allocates resources up to the number specified as long as they are physically available, and relocates a resource to another node as necessary.

• Defining the number of instances required to support the application.

Resources are no longer defined as belonging to a specific instance or node. Instead, the priority of resource requirements is defined.

6.6.1 Using EMCA in Interactive Mode

To use EMCA to configure your database for management using Database Control:

1. Set the default Oracle home to the location of the home directory for the database you are modifying. See Section 7.3, "Working with Multiple Oracle Home Directories on Windows" for details.

2. Change the directory to %ORACLE_HOME%\bin.

3. Start EMCA by entering the following command with any of the optional command-line parameters shown in Table G-1, "EMCA Optional Command-Line Parameters":

   %ORACLE_HOME%\bin> emca.bat
   

   Depending upon the parameters you include on the EMCA command line, you might be prompted for additional information required to configure Database Control.

   Note:

   To configure Database Control for a single-instance database using Oracle Automatic Storage Management (Oracle ASM), you do not have to include extra parameters in the EMCA command. Run the following command to configure Database Control for a new installation. EMCA automatically detects the Oracle ASM instance:

   emca -config dbcontrol db -repos create
   

   Example 6-1 Configuring Database Control and Daily Database Backups using EMCA

   Enter the following commands to configure Database Control for your Oracle RAC database and also to enable automatic daily backups of your database:

   X:\> cd %ORACLE_HOME%\bin
   
   X:\..\bin> emca.bat -config dbcontrol db -backup
   

6.6.2 Using EMCA in Silent Mode With an Input File

Instead of answering a series of prompts when you run EMCA, you can use the -respFile parameter to specify an input file. The input file you create must be in a format similar to the following example:

PORT=1521
SID=DB
DBSNMP_PWD=xpE234D
SYSMAN_PWD=KDOdk432

After you create an EMCA input file, you can use it on the command line as follows, where input_file_path is the full path name of the input file:

emca -config dbcontrol db -respFile input_file_path

PORT=1521
SID=DB
DBSNMP_PWD=dow3l224
SYSMAN_PWD=squN3243
HOST_USER=johnson
HOST_USER_PWD=diTf32of
SYS_PWD=qlKj4352
BACKUP_SCHEDULE=06:30

X:\..\bin> emca -config dbcontrol db -repos create -backup -respFile
input_file_path

6.7.1 Changing the Database Control Implementation for Your Oracle RAC Database

By default, when you configure Database Control for an Oracle RAC 11g database, the Database Control console starts only on the local node. If you upgrade an existing Oracle RAC database configured with Database Control to the current release, then the existing Database Control configuration is retained. For example, if you have an Oracle RAC 10g release 1 (10.1) database, then the existing Database Control configuration has a Database Control console running on each cluster node. If you upgrade this database to Oracle Database 11g release 2, then the Database Control console is still started on each individual node.

You can modify the number of Database Control consoles started for your Oracle RAC database. If you have one Database Control console running in the cluster, or more than one, you can still monitor and manage every node in the cluster from a single Database Control console.

To modify the implementation of Database Control for your database, use the following command, where nodename is the public name of the node, and node_list is a comma-deliminated list of node names:

emca -reconfig dbcontrol –cluster –EM_NODE nodename -EM_NODE_LIST node_list

You can use the emca -reconfig dbcontrol command to start a Database Control console on multiple nodes. This command performs the following actions in sequence:

1. Starts a Database Control console on the node specified by nodename, if there a Database Control console is not started.

2. Redirects the Management Agents monitoring the database instances in node_list so that they upload their data to the Database Control console running on nodename. Also, Management Agents monitoring the Oracle Database instances on nodename upload their data to the local console. Note that if you do not enter the command options -EM_NODE or -EM_NODE_LIST at the command line, you will be prompted for them.

   Note:

   -EM_NODE defaults to the local node if not specified when prompted. If not specified, -EM_NODE_LIST defaults to all nodes where the database is configured.

For information about the current cluster configuration, you can run the following command:

emca -displayConfig dbcontrol –cluster

This command prompts for the database unique name for the cluster database. It prints the current configuration to the screen, indicating the nodes that have Database Control consoles running on them and the Database Control consoles to which each Management Agent is uploading its data.

emca -reconfig dbcontrol –cluster –EM_NODE node1 -EM_NODE_LIST node2,node3,node4
emca -reconfig dbcontrol –cluster –EM_NODE node5 -EM_NODE_LIST node6,node7,node8

6.7.2 Updating Database Control Configuration When Adding and Removing Nodes

For an administrator-managed database, a common operation is the addition and deletion of cluster nodes.

emca -addNode db

Node name: node6
Database Unique Name: myNewDB

emca -deleteNode db

6.7.3 Changing the Ports Used by Database Control

When you initially install Oracle RAC 11g release 2 (11.2) or configure Database Control with EMCA, Database Control uses a set of default system ports. For example, by default, you access Database Control in Oracle Database 11g release 2 (11.2) using a web address that consists of the local host name (host.domain) and port 1158:

https://host.domain:1158/em

Port 1158 is the default port assigned to Database Control by the Internet Assigned Numbers Authority (IANA). Similarly, the default Management Agent port, as assigned by the IANA, is 3938.

To use ports other than the default ports, use EMCA command-line arguments when configuring Database Control using EMCA. Table 6-1 summarizes the EMCA command-line parameters that control the standard Database Control port assignments.

http://host.domain:5570/em

Alternatively, you can explicitly assign ports after configuring Database Control using the following command, where parameters refers to the command-line parameters listed in Table 6-1:

emca -reconfig ports [-cluster] [parameters]

6.8.1 Updating Database Control After Changing the Database Listener Port

If you change the listener port of the database after you have configured Database Control, then the database status appears as down in the Database Control console. To reconfigure Database Control to use the new listener port, run EMCA using the following command:

emca.bat -config dbcontrol db [-cluster]

6.8.2 Upgrading Grid Control Agents for Oracle Database 11g Release 2

When upgrading an Oracle Database 10g release 1 database instance that was configured for Oracle Enterprise Manager (either Database Control or a Grid Control Management Agent) to an Oracle Database 11g release 2 (11.2) database, all resources monitored by Oracle Enterprise Manager targets associated with the upgraded instances are updated automatically. This is because the upgrade involves altering the Oracle home for the instance, the port numbers, or other instance- and node-associated properties.

If an upgraded instance is managed by a Grid Control Agent, then the associated resource information in Grid Control might not be updated successfully during the upgrade. To update the Grid Control target information, perform the following steps:

1. Use Grid Control to access the home page of the upgraded instance.

2. On the home page for the upgraded instance, select Monitoring Configuration.

3. On the Monitoring Configuration page, update the properties to the correct values as needed, for example, Oracle home, listener port, and so on.

6.8.3 Updating Database Control After Changing the Host Name or IP Address

After changing the host name (including the domain name) or the IP address for a node, you must deconfigure Database Control on that node and then reconfigure it using EMCA with the -repos flag, as shown in the following examples:

Reconfigure Enterprise Manager, deleting the repository when removing the configuration

emca -deconfig dbcontrol db -repos drop
emca -config dbcontrol db -repos create

Reconfigure Enterprise Manager, re-creating the repository during reconfiguration

emca -deconfig dbcontrol db
emca -config dbcontrol db -repos recreate

6.8.4 Using EMCA After Changing the TNS_ADMIN Configuration

After you change the TNS_ADMIN environment variable to specify a new configuration, you must update Database Control. Set the TNS_ADMIN environment variable to the new value, then run the following command:

emca -config dbcontrol db