Oracle enterprise manager config files

This example of listener. To start this listener on UNIX, enter the command:. If you are using the default listener name, you do not need to specify the name when starting the listening process. The default listener name is "listener. This snmp. These files are created automatically by the Intelligent Agent. Do not update this read-only file. It contains the following parameters:.

You can modify this read-write file, but this should be done carefully. Agents, versions 7. The port address is automatically set. The following parameters are not automatically generated, but may be added to the file:. The services. This file contains a list of the services, such as Oracle databases and listeners, on the node where the agent resides.

This file is retrieved from the agent by Oracle Enterprise Manager through the Navigator Discovery menu options. Note: Do not manually edit the services. The agent rewrites the file on startup. These parameters are also used in the snmp. Note: If. The name of the services that the agent is monitoring. Each database and each SNMP-manageable service must be listed. For a database, the service name is the name of the database as it appears in the tnsnames.

The unique index number of the service that the agent is monitoring. Table A-6 lists the agent installation logs and their locations. Table A-7 lists all the other installation logs that are created during an agent installation using the Add Host wizard.

Table A-8 lists the installation logs that are created when a Management Agent is installed manually, that is, in silent mode. Table A-9 lists the log files that need to be scrutinised for a failure of Gold Image creation process.

On the Agent Gold Images page click on Show all activities link to see all the jobs. Click on the job name to see the job result and the output logs. Table A lists the log files that need to be scrutinised for Agent update failure. Table A lists the installation logs that you can view when adding an OMS fails:.

Previous Next JavaScript must be enabled to correctly display this content. Initialization Logs Table A-2 lists the ini tialization logs of the remote host and their locations. Application Prerequisite Logs Table A-3 lists the a pplication prerequisite logs and their locations. System Prerequisite Logs Table A-5 lists the system prerequisite logs and their locations. Agent Installation Logs Table A-6 lists the agent installation logs and their locations. Other Add Host Logs Table A-7 lists all the other installation logs that are created during an agent installation using the Add Host wizard.

Manual Management Agent Installation Logs Table A-8 lists the installation logs that are created when a Management Agent is installed manually, that is, in silent mode. Output logs for the agent gold image job run. Agent deploy logs. All log files. Install a new or Upgrade Enterprise Manager system. Add an additional Management Service. Install Oracle Management Agent. New Agent Installation. Agent Cloning. Shared Agent Installation.

Fresh and Cloned Agent install logs. Shared Agent installation logs. Agent Configuration logs. Information about the directories that are specific to the Oracle Application Server installation can be found in the Oracle Application Server documentation. For example, the location of the most of the Oracle Application Server configuration and log files are described in the Oracle Application Server documentation. In addition to the Management Service home directory, the installation procedure installs the Oracle Management Agent that is used to gather management data and perform administration tasks for the targets on the Management Service host.

By default, if the Oracle Universal Installer or the account used to run the Universal Installer has the proper privileges to write to the install directories, the Management Agent is installed in a separate Oracle home directory at the same level as the Oracle Application Server home directory. However, if the Oracle Universal Installer does not have the necessary privileges, the Management Agent is installed in a subdirectory of the Oracle Application Server home directory.

Figure shows some of the important directories you should be familiar with in a typical Grid Control Console installation. You can use this information as you begin to maintain, troubleshoot, and configure the Oracle Management Service installation.

Table describes in more detail the Management Service directories shown in Figure Use the emctl command in this directory to start and stop the Application Server Control Console.

The sysman directory in the Oracle Application Server Home contains the system management files associated with this Oracle Application Server Release 2 9. This directory contains the files associated with the OC4J instances running in this instance of Oracle Application Server.

This local instance of the Management Agent gathers management information about the targets on the Management Service host. You can then manage those targets, such as the host itself, from the Grid Control Console.

The Management Agent is also available as its own install type. This enables you to install the Management Agent on the hosts throughout your enterprise. The Management Agent can then gather management data about the targets on each host so those targets can be managed from the Grid Control Console. When you select the Additional Management Agent installation type, you install only the files required to run the Management Agent.

Specifically, the Management Agent files are installed into the same directory structure shown in the agent directory when you install the Oracle Management Service Figure The agent directory contains all the files required to configure and run the Oracle Management Agent on this host. This directory serves as the Oracle Home for the Management Agent. If you install only the Management Agent on a managed host, only the files in this directory are installed.

You use the emctl command in this directory to start and stop the Oracle Management Agent on this host. This directory contains the files used by the Management Agent to define target types such as databases, hosts, and so on , to run configuration scripts, and other administrative tasks.

This directory contains the configuration files for the Management Agent. For example, this is where Enterprise Manager stores the emd. The emd. For real application clusters, this directory contains all configuration, log files, and system files. As a result, the Oracle Application Server installation procedure installs a set of Enterprise Manager directories and files into each Oracle Application Server home directory.

Database Control provides the tools you need to manage your Oracle Database 10g immediately after you install the database. As a result, the Oracle Database 10g installation procedure installs a set of Enterprise Manager directories and files into each Oracle Database 10g home directory. The Management Agent and Management Service support files are installed in two locations in an Oracle Database 10g installation:. Files that are common and shared among all instances of the database are stored in the following directory of the Oracle Database 10g home:.

Files that are unique to each instance of the database are stored in following directory of the Oracle Database 10g home:. Both paths refer to the same concept — the Enterprise Manager directory for the specific database instance. In cluster databases, nodename refers to the public name of the node, as specified during Cluster Ready Services CRS configuration for cluster environments.

For example, if the database host name is mgmt1. Figure summarizes the location of the important Enterprise Manager directories in a typical Oracle Database 10g home directory.

When you install Grid Control, Oracle Application Server, or Oracle Database 10g, the resulting directory structure can often include multiple subdirectories with the same name.

In addition, you can have a bin directory within the Management Service Oracle home. Use the emctl command in this directory to control the Management Service. To quickly identify the Oracle home that is controlled by the files in a particular bin directory, use the following command:.

This command displays the path to the current Oracle home that will be affected by commands executed by this instance of the emctl command. The following sections describe how Oracle Enterprise Manager 10 g Database Control is configured during the Oracle Database 10g installation. These sections also describe how you can configure Database Control after the installation:. Figure shows the Management Options page, which allows you to select your database management options while installing Oracle Database 10g.

To select Grid Control Console as your management option, the Oracle Management Service must be installed on a network host. In addition, the Oracle Management Agent must be installed on the host where you are installing the database. Otherwise, the Grid Control Console option is unavailable and you must instead choose to manage your database with Database Control.

For most of the Oracle Database 10g installation types, you must choose either Database Control or Grid Control as your management option when you create a database during the installation.

However, if you create a database using one of the following methods, you can choose not to configure Database Control:. Choosing the Advanced database configuration option during an Enterprise or Standard Edition installation. You can use DBCA to create a new database or to reconfigure an existing database. Log into the database host as a member of the administrative group that is authorized to install Oracle software and create and run the database.

Advance to the Management Options page Figure and select the following options:. For more information about Enterprise Manager notifications and daily backups, click Help on the Management Options page. This directory is named using the following format and contains Database Control configuration and state files specific to the database you just configured:. Set the following environment variables to identify the Oracle home and the system identifier SID for the database you want to manage:.

Start EMCA by entering the following command with any of the optional command-line arguments shown in Table :. For example, enter the following command to configure Database Control so it will perform automatic daily backups of your database:.

Table describes the valid execution operations and modes, and lists the optional parameters in brackets. Table discusses the flags and their behavior, while Table defines the optional parameters in detail. Multiple parameters can be used in combination at the command line. The options described in Table , Table , and Table , and the valid parameters you may include are listed.

Configures Database Control for a database. Options include creating or recreating Database Control repository, configuring automatic backups, and performing these operations on a cluster database. Options include performing this operation on a cluster environment.

This operation will configure the database so that it can be centrally managed by the Oracle Enterprise Manager 10g Grid Control Console. To use this option, you must have previously installed the Oracle Management Service component of Enterprise Manager on a network host.

In addition, the Oracle Management Agent must be installed on the host where you are running the database. Configures both Database Control and central agent management for a database. The possible configuration options are similar to those described above. Deconfigures Database Control for a database. Options include dropping the Database Control repository and performing these operations on a cluster database.

For example, you might use this command to remove the Database Control configuration from a database you are planning to delete. In such a scenario, remove the Database Control configuration before physically deleting the database. This operation does not remove the actual database or its data files.