With the updated Enterprise Manager, you can perform all the database-administration activities as well as monitor and administer the different targets and applications in the corporate ecosystem.
This will afford you a higher level of flexibility and functionality to centrally manage all the applications on a Web-based Grid Control Console over the Internet or an intranet. Using the Software Development Kit from Oracle, you can also add new targets in your environment as you expand the infrastructure. For more details on setting up and monitoring the grid environment, see Chapter 18, "Leveraging Grid Technology Features.
Let us review the preinstallation requirements for Oracle Enterprise Manager for use with an Oracle database. We will discuss the requirements for the basic components of a small as well as a large environment. The management repository needs 1GB of hard disk and MB of memory for small environments with fewer than 25 managed targets. For a large organization with around targets, the recommended memory is 2GB and 24—48GB of hard disk space depending on your installation and database requirements.
The management service needs a minimum of MB for a Windows installation and around 1. The management agent needs a minimum of MB of initial disk space for Solaris MB for Windows to do all logging and tracing activities, and around 25MB of operating memory per database or application server.
You will need proportionately higher numbers for the service and agent for larger installations. Regardless of whether you choose to create a new database or use an existing database for the repository, the intended repository database must have fine-grained access control turned on with satisfactory software, patch, and tuning requirements met as per the installation guide.
During the database installation process, you will install the OEM 10g database control. The database control has the necessary tools to help you manage the database. This password is needed for the initial login to OEM. This will help you to control access for every DBA working on the system in various roles and responsibilities. There are several methods to configure OEM database control for a database. You can configure your database to be managed by OEM during the database-installation process from the Select Database Management Option screen.
For the database control configuration from a command line, use emca as explained in this section. When executed, the script will present a series of questions with regard to the host name, instance name, and so on, as given in Listing 3. Your screen may vary depending on the operating system being used. For Oracle Real Application Clusters discussed later in this chapter , create the instances first and then configure the database control for each instance in the cluster using EMCA.
The input file for our installation example will be as follows:. When you do your OEM installation, you may see slightly different screens depending on your operating system. The dotted lines denote the execution of various scripts in the process. If you are not sure of the various command options for emctl, type emctl at the command line and Oracle will provide all available options for the command.
Listing 3. After you enter the user name and password, the Web interface will change into the instance summary display, which provides guidance through the rest of the instance administration tasks. The new look and feel of OEM provides a feature-rich display that allows a DBA to drill down to detailed reports on any metric.
You can use the emctl command to start, stop, or check the status of an agent. For Windows-based systems, the agent is listed under Services likely found in Control Panel. When you find the appropriate service, you can start or stop it using the Services control panel. Metrics are units of measurement to assess the health of your system with predefined thresholds for each unit. Oracle has thresholds for most of the metrics. When a metric reaches a threshold, an alert is generated. The alert also indicates that a particular condition has been encountered—for example, a threshold has been reached or an alert has been cleared.
The vast majority of the OEM metric-based alerts are polled by the management agent at intervals. Refer to Figure 3. An online help feature is available in OEM to give you a description of each metric.
Alerts are displayed on the Database Home page under the Alerts section. Nondatabase alerts are displayed under Related Alerts. Figure 3. Oracle has provided a set of predefined metrics, some with predefined thresholds. When your database needs metrics outside these predefined values, you have to set thresholds to different values.
The Manage Metrics page, shown in Figure 3. Review these thresholds and identify the values that need editing. Using the Edit Thresholds link see Figure 3.
In the Response Actions field, you can add the name of a script or operating-system command to be executed when a threshold is crossed and an alert is issued. Click OK and save the changes made to the thresholds from this screen. Set event to level 8 your Oracle Database 10g database session. Oracle Enterprise Manager is a graphical tool supplied with Oracle Database that lets you perform database administration tasks easily. Search, create, edit, and delete XMLType tables and views.
The configuration file can be modified at runtime. Simply updating the configuration file creates a new version of this repository resource.
At the start of each session, the current version of the configuration file is bound to that session. The session uses this configuration-file version for its duration, unless you make an explicit call to refresh the session to the latest version. Its structure is described in the following sections. Its structure is as follows:. It contains any parameters that you may want to add. This includes Web application-specific parameters, such as icon name, display name for the application, and a list of servlets.
It is used to configure servlets, including Java servlets. It exposes the following functions:. You have modified the configuration and now want the session to pick up the latest version of the configuration information. It has been a long running session, the configuration has been modified by a concurrent session, and you want the current session to pick up the latest version of the configuration information.
This example updates parameters ftp-port and http-port in the configuration file. If the appropriate xsi:schemaLocation or xsi:noNamespaceSchemaLocation attribute is found, the specified schema location URL is used to lookup the registered schema. If the appropriate xsi: attribute is not found, the XML document is considered to be non-schema-based.
If the appropriate xsi: attribute is not specified in the XML document, the default schema location mappings will be used. Simply updating the configuration file, causes a new version of the file to be generated.
At the start of each session, the current version of the configuration is bound to that session. The session will use this configuration for its life, unless you make an explicit call to refresh to the latest configuration.
It includes Web application specific parameters, for example, icon name, display name for the application, list of servlets in Oracle XML DB, and so on. It exposes the following functions:. If you have a few parameters to update in the configuration file, then you can use the following:. If you have many parameters to update, then the preceding example may prove too cumbersome. You have modified the configuration and now want the session to pick up the latest version of the configuration information.
It has been a long running session, the configuration has been modified by a concurrent session, and you want the current session to pick up the latest version of the configuration information. Note: If the Listener is running on a non-standard port for example, not , then in order for the protocols to register with the correct listener the init.
0コメント