EMCA Troubleshooting Tips

The following sections describe troubleshooting tips to consider when using EMCA to configure Database Control.

Using EMCA After Changing the Database Listener Port
Upgrading 11g Release 2 Grid Control Agents
Using EMCA When the Database Host Name or IP Address Changes
Using EMCA When the TNS Configuration Is Changed
Using EMCA for Desktop Class Installations
Handling EMCA Error Messages

Using EMCA After Changing the Database Listener Port

If you change the listener port of the database after you have configured Database Control, the database status will appear as down. To reconfigure Database Control so it uses the new listener port, run the EMCA command using the -config dbcontrol db [-cluster] command-line arguments.

Upgrading 11g Release 2 Grid Control Agents

When upgrading an Oracle Database 11g Release 2 database or an Oracle ASM instance that was configured for Oracle Enterprise Manager (either Database Control or a Grid Control central agent) to an Oracle Database 11g Release 2 (11.2) database, all Enterprise Manager targets on the relevant hosts referring to the upgraded instances are updated automatically. This occurs because the upgrade involves altering the instance Oracle home, port, or other target-associated properties. However, some of these targets on the hosts are not updated successfully during the upgrade if they are managed by an Oracle Database 11g Release 2 (11.2) Grid Control Agent.

To update these targets, in the Home page for the upgraded database (or Oracle ASM) target, click Monitoring Configuration. On the Monitoring Configuration page, you can update properties such as Oracle home, listener port, and so on to the correct values.

Using EMCA When the Database Host Name or IP Address Changes

When the database host name (including the domain name) or the IP address changes, deconfigure and then reconfigure Database Control with the -repos recreate flag for the emca command. For example, to re-create Database Control with a new host name, complete the following steps:

Set ORACLE_HOSTNAME=old_hostname in the environment.
De-configure the old dbconsole by running the following command:

For a single-instance database:
```
$ $ORACLE_HOME/bin/emca -deconfig dbcontrol db
```
For Oracle RAC:
```
$ $ORACLE_HOME/bin/emca -deconfig dbcontrol db -cluster
```
Un-set ORACLE_HOSTNAME in the environment.

Configure a new dbconsole by running one of the following commands:

For a single-instance database, enter:

$ $ORACLE_HOME/bin/emca -config dbcontrol db -repos recreate

For Oracle RAC, enter:

$ $ORACLE_HOME/bin/emca -config dbcontrol db -repos recreate -cluster

Using EMCA When the TNS Configuration Is Changed

When the TNS configuration is changed, set the environment variable, then run the following command:

$ emca -config dbcontrol db

Using EMCA for Desktop Class Installations

For Desktop class installation where hostname is localhost, set ORACLE_HOSTNAME=localhost in the environment before you perform any EMCA or emctl operations.

Handling EMCA Error Messages

The following are some EMCA error messages and instructions for handling them.

Failed To Allocate Port(s) In the Specified Range(s)

Check the following:

Free the ports if they are in use or use EMCA to provide free ports in command line options.
Open up the required ports in the firewall and re-run the emca -config dbcontrol db [-cluster] command by specifying free ports in the command line.
Check the /etc/hosts file. It should contain an entry for the physical host. Enter the following command to determine the physical host name:

$ CMD>hostname

Set the environment variable:

$ set ORACLE_HOSTNAME=output of above command

Try to run the following command:

$ $ORACLE_HOME/bin/emca -config dbcontrol db

By completing these steps you are fixing the environment variable and then running the –config dbcontrol db command again to re-attempt to allocate the ports.

Listener Is Not Up or Database Service Is Not Registered With It

Check the following:

If the listener is not up on the specified port, then start it and rerun the EMCA script.
Check whether the database service is registered with the listener. If not, then register it and rerun the EMCA script.
If the listener is configured with a different host name than the physical host name, configure Database Control as follows:

$ set ORACLE_HOSTNAME=listener host

$ $ORACLE_HOME/bin/emca -config dbcontrol db

If the listener port changes, then reconfigure Database Control by providing the new listener port:

$ $ORACLE_HOME/bin/emca -config dbcontrol db