Oracle Enterprise Manager Configuration Guide
Release 9.0.1

Part Number A88769-01
Go To Documentation Library
Library
Go To Product List
Product
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

3
Configuring and Controlling the Management Server

If you have chosen to deploy the entire Enterprise Manager framework (for example, Console, Management Server, and Intelligent Agents), you will need to perform additional configuration tasks on the middle tier Management Server machine(s). On such a machine(s), you will need to use the Enterprise Manager Configuration Assistant to configure the Management Server.

This chapter will describe the following:

Starting the Enterprise Manager Configuration Assistant

The Enterprise Manager Configuration Assistant will launch automatically during the post install configuration phase when the Management Server is being installed and if you are performing one of the following installation scenarios:

The Enterprise Manager Configuration Assistant will not launch automatically during any other installations; you must manually launch the Enterprise Manager Configuration Assistant when installation completes.


Note:

A database (a supported version for a 9i Management Server repository) must be installed and running anywhere on the network before you can create the Oracle Enterprise Manager repository schema.

Choose a database that also meets the following criteria:

  • the database is always available.

  • the database will not be shut down by other administrators.

 

To start the Enterprise Manager Configuration Assistant, perform the following steps:

You must have write access to the omsconfig.properties file in the $ORACLE_HOME\sysman\config directory to run the emca command.

Configuring a Local Management Server To Use a New Release 9i Repository

Whenever you start the Enterprise Manager Configuration Assistant to create a new 9i repository (whether during a post install configuration or by launching the assistant manually), it will perform the following tasks for you:

Welcome

When you start the Configuration Assistant by launching it manually, the Welcome page appears.

A checkbox "Show this page next time" is available to you so that you can specify not to show this page again once you are familiar with the Configuration Assistant. By default, the checkbox is selected. If you deselect the checkbox, the Configuration Assistant starts on the Configuration Operation page next time.

Figure 3-1 Welcome


Text description of rep0.gif follows.
Text description of the illustration rep0.gif

Configuration Operation

After pressing the Next button on the Welcome page, the "Configuration Operation" page appears.

Figure 3-2 Configuration Operation


Text description of rep1.gif follows.
Text description of the illustration rep1.gif

If you want to configure the Management Server by creating a repository or editing an existing repository configuration, select "Configure local Management Server" from the list of repository operations and press Next.

If no previous configuration exists, the Configure Oracle Management Server page appears.

If a configuration already exists, a dialog appears asking you if you want to edit this configuration or create a new configuration.

Figure 3-3 Edit or Create Dialog


Text description of editorcr.gif follows.
Text description of the illustration editorcr.gif

Press the Edit or Create button.

If you press the Edit button, the Edit Configuration Parameters page appears. For more information on editing the configuration, skip to Edit Configuration Parameters on page 3-28.

If you press the Create button, the Configure Oracle Management Server page appears.

Configure Oracle Management Server

The Management Server on this host requires a repository to hold information about the servers and targets that you will be managing.

Figure 3-4 Configure Management Server


Text description of cfgoms.gif follows.
Text description of the illustration cfgoms.gif

If you are a new Oracle Enterprise Manager user or if you want to configure the first Management Server in your environment and create a new Release 9i repository, you will use the "Create a new repository" choice. It will create and load your Release 9i repository and set up the configuration parameters for a local Management Server.

Create New Repository Options

The Enterprise Manager Configuration Assistant can automate the creation of a new repository or you can specify the details of creating a new repository.


Note:

This page will only appear if the Configuration Assistant is run from an Oracle Home that contains a 9i database server installation. 


Figure 3-5 Create New Repository Options


Text description of repoptio.gif follows.
Text description of the illustration repoptio.gif

Typical

The actions may include all or some of the ones detailed below.

If you choose Typical, there are no additional steps to perform, and the next page will be the Create Repository Summary page with special entries.

Figure 3-6 Create Repository Summary for Typical Repository Option


Text description of sumtypic.gif follows.
Text description of the illustration sumtypic.gif


Note:

Record the password for the repository user for future reference. This is the only time the password will appear, and you will need it to perform such tasks as dropping or upgrading the repository. For information on changing the password for the repository user at a later date, refer to "Changing the Repository User Password" on page F-23


Click Finish to initiate repository creation or click Back to return to previous pages to make modifications.

When you click the Finish button, the Enterprise Manager Configuration Assistant launches the Database Configuration Assistant to create the database instance.


Note:

It may not be obvious that the Database Configuration Assistant is being run since there is no Database Configuration Assistant identification on the progress dialog. 


When the Database Configuration Assistant allows you to change the passwords for the database on its last dialog, take the default passwords instead of changing them.


Note:

Do not change the password for SYS. The Enterprise Manager Configuration Assistant assumes that the password is "change_on_install", and if you change this password now, when the Enterprise Manager attempts to login using those credentials, it will fail. You can change the password as soon as the Enterprise Manager Configuration Assistant has completed its operations, because it no longer needs the SYS credentials. 


Once the instance has been created and the Database Configuration Assistant exits, the Enterprise Manager Configuration Assistant tries to connect to the database using the SYS credentials. Once the connection has been made, the Enterprise Manager Configuration Assistant then creates the repository user and populates the repository schema.


Custom

If you choose Custom, the assistant will allow you to select from the following actions later depending on the choices you make.

If you choose Custom, the Select Database Location page appears.

Select Database Location

You may place your Enterprise Manager repository in a new local database or in another existing database somewhere on your network. The database must be a version which supports a 9i Management Server repository.


Note:

This page will only appear if the Configuration Assistant is run from an Oracle Home that contains a 9i database server installation. 


Figure 3-7 Select Database Location


Text description of dblocati.gif follows.
Text description of the illustration dblocati.gif

If you select "In a new local database instance," without pressing the Change Database SID button, the Repository Login Information page appears. Skip to Repository Login Information on page 3-16 for details.

If you select "In a new local database instance" and press the Change Database SID button, the Change Database SID dialog appears. Skip to Change Database SID on page 3-13 for details.

If you select "In another existing database," the Select Database for Repository page appears. Skip to Select Database for Repository on page 3-15 for details.

Change Database SID

You can change the Oracle System Identifier (SID) that identifies the local database instance where your Enterprise Manager repository will be created.

Figure 3-8 Change Database SID


Text description of changesi.gif follows.
Text description of the illustration changesi.gif

Oracle recommends that you choose a database SID that will not be managed using this Enterprise Manager repository.

Press OK to dismiss the dialog after changing the database name or SID. Then press the Next button on the Select Database Location page to proceed to the Repository Login Information page. Skip to Repository Login Information on page 3-16 for details.

Select Database for Repository

Log in to the database where you want to create the repository.

Figure 3-9 Select Database for Repository


Text description of dbrep.gif follows.
Text description of the illustration dbrep.gif

User name and Password: You must connect to the database as a user with DBA privileges. The Enterprise Manager Configuration Assistant asks for a DBA account in case a new user needs to be created in the database to contain the repository and to allow the Configuration Assistant to make queries about the database/repository.

This is an individual database user account, not an Oracle Enterprise Manager administrator account.

For example, system/manager.

Service: The service may be specified using the form:

<host>:<port>:<sid> 

where

host is the machine name where the database is located

port is the database listener port address, usually 1521 or 1526

SID is the database system identifier

An example:

my_em_machine:1521:em90

which connects to the em90 database using port 1521 on the my_em_machine machine.


Note:

Specifying the service as <host>:<port>:<sid> is the recommended method, but you may also use Oracle Net names if your Oracle Net client is properly configured. 


Press Next to continue.

Repository Login Information

An Enterprise Manager repository is owned by a database user. During repository creation, a database user (repository schema user) who owns the repository will be created by the Enterprise Manager Configuration Assistant with the username and password you enter on this page.

Figure 3-10 Repository Login Information


Text description of rep3.gif follows.
Text description of the illustration rep3.gif

User name: By default, the Enterprise Manager Configuration Assistant uses OEM_<TCP/IP hostname of machine>_<SID> as the repository's user name that will be used to create a database user that will own the repository.

The repository's user name must be unique across the network. If you choose another name, you must ensure that it is unique.

The Intelligent Agent identifies each Management Server by its repository name. If two repositories existed with the same name in different databases, the Intelligent Agent would have difficulty contacting the Management Server.

Password: Enter the password for that user.

Confirm: Verify the password by typing it again.

You can choose whether to save the user name and encrypted password in the omsconfig.properties file, which is read by the Management Server on startup. If these repository credentials are stored in the file, the Management Server uses them to login to the repository. The password is stored in encrypted format.

On Windows NT and Windows 2000, if they are not saved, you can enter them in the Control Panel's Startup Parameters field when you start the Management Server. If you do not enter the repository credentials in the Startup Parameters field, you will be prompted for them in a dialog.

On UNIX, if they are not saved, the Management Server will prompt you for a user name and password before it starts up.

If you do not want to store the user name and encrypted password in the omsconfig.properties file, check the "Do not save username and password" checkbox. The option of not storing your repository credentials is referred to as the secure Management Server mode.

The repository account information will be used to perform the maintenance operations in the repository schema like create, upgrade, or drop.

The roles and privileges required by the repository schema user which are automatically created by the Configuration Assistant are listed below:

To avoid potential security issues and unnecessary access to objects outside of Oracle Enterprise Manager, do not grant more privileges to your repository schema user than is absolutely necessary.

Select Repository User Tablespaces

The Select Repository User Tablespaces page does not appear:


Note:

Do not install the Oracle Enterprise Manager repository into the SYSTEM (especially the SYSTEM tablespace of your production database), ROLLBACK, or TEMPORARY tablespaces.

The tablespace parameter settings used for the SYSTEM tablespace are not appropriate for Oracle Enterprise Manager use. You should only use the SYSTEM tablespace for "system" entities. Tools, users, and management products such as Oracle Enterprise Manager should be placed in other tablespaces.

ROLLBACK tablespaces are used for creating rollback segments. Rollback segments are used by Oracle user processes to store rollback information.

TEMPORARY tablespaces, which are assigned as TEMPORARY tablespaces for users, are used by Oracle user processes as a "scratch pad." Both of these tablespaces fluctuate in tablespace usage when the database is up and running. The TEMPORARY tablespace can be used as the user's temporary tablespace.

The Configuration Assistant does not allow you to use the SYSTEM tablespace either as a temporary tablespace or as a default tablespace. 


When you launch the Configuration Assistant manually, if the OEM_REPOSITORY tablespace already exists and you have entered the name of a different repository user than the one managing the repository in the "Repository Login Information" page, an error message appears, saying, "Do you wish to change it to manage the repository owned by user '<user>' on service '<service>'?" If you click the "Yes" or the "No" button, the following page appears.

Figure 3-11 Select Repository User Tablespaces if OEM_REPOSITORY Exists


Text description of rep4.gif follows.
Text description of the illustration rep4.gif

Select the default and temporary tablespaces for the Enterprise Manager repository to use.

If the OEM_REPOSITORY tablespace does not exist, the following page appears:

Figure 3-12 Select Repository User Tablespaces if OEM_REPOSITORY Does Not Exist


Text description of oemrep.gif follows.
Text description of the illustration oemrep.gif

Default Tablespace:

Temporary Tablespace

Select a temporary tablespace from the pull-down list.

Click Next to continue.

If the Enterprise Manager Configuration Assistant detects that the default tablespace for the repository contains the required amount of free space, the "Create Repository Summary" page appears. Otherwise, errors will appear.

Create Repository Summary

If you have chosen to specify the details of creating a new repository in the "Create New Repository Options" page, the "Create Repository Summary" page provides a summary of all the information supplied.

The following page appears at the end of the "Custom" sequence.

Figure 3-13 Create Repository Summary


Text description of rep5.gif follows.
Text description of the illustration rep5.gif

Click Finish to initiate repository creation or click Back to return to previous pages to make modifications.

When you click the Finish button, the Configuration Assistant Progress window appears, showing the processing performed and the processing steps that comprise the operation being performed.

Configuration Assistant Progress Window

If you want to view detailed information about what is happening during the processing, including any errors that might occur, click the "Show Details" button to expand the dialog to show a text area. You can hide the detailed information by clicking the "Hide Details" button.

Figure 3-14 Configuration Assistant Progress


Text description of rep6.gif follows.
Text description of the illustration rep6.gif

The Cancel button changes to a Close button when processing is completed, whether it is successful or not.

When all of the steps have been completed without error, the "Processing completed." message appears.

You can cancel the requested operation before it completes by clicking the Cancel button.


Note:

If you cancel the repository creation while it is in progress, the state of the repository is in doubt. In these circumstances, you should drop the repository using the Enterprise Manager Configuration Assistant. 


You must click the Close button to exit the Configuration Assistant.

If the repository creation fails, drop the repository, turn on tracing for the Management Server by adding the appropriate tracing properties to the omsconfig.properties file, and perform the repository creation procedure again. For information on Management Server tracing and logging, refer to Appendix B, "Activating Logging and Tracing".

For information on dropping the repository, refer to Dropping an Existing Repository on page 3-38.

Configuring a Local Management Server To Use An Existing Repository

In an environment with multiple Oracle Management Servers, a set of Management Servers can share the same repository. There may be only one Management Server running per node.

Select the "Configure local Management Server" selection if you want to perform the following tasks:

As the number of nodes and managed services in your network increases or if the current Management Server is overloaded, you can add more Oracle Management Servers to the middle tier to share and balance the workload.

Multiple Oracle Management Servers provide fault tolerance for each other. If an Oracle Management Server fails, the other Management Servers continue to operate. The clients that registered with the failed Management Server can immediately log in again, registering with any of the other Management Servers using or sharing the same repository, and work continues with the remaining available Oracle Management Servers. Any clients that had been configured to register with a different Oracle Management Server than the one that failed are unaffected.

If the available Management Servers are CPU-bound (the CPU usage is exhausted), adding additional Management Servers is an alterative to increasing the capacity of the nodes that run the Management Servers.


Note:

All Management Servers connecting to the same repository must reside in the same DNS Domain.  


If you want to run an Oracle Management Server on a specific machine, you must first install the Oracle Management Server software on that machine.

Refer to the installation guide provided with the database release for detailed instructions.

When you add a new management server, you must run the Enterprise Manager Configuration Assistant to update the configuration for that node.

The Configuration Assistant can only set or change configuration parameters (omsconfig.properties file) for the machine on which it is running. It does not have the ability to change another machine's configuration parameters; you must go to each of the other Management Servers using (sharing) the repository and run the Configuration Assistant to change each machine's configuration parameters.

You must set up or change the repository connect information (user name, password, service) to point to the correct repository. It is important that all the Management Server machines that are using (sharing) the same repository have consistent configuration parameters.


Note:

If you change the password for the database user account which owns the repository, you must also change the corresponding Management Server configuration parameter for every Management Server that uses the repository; otherwise, the next Management Server start will fail. 


For information about starting the Enterprise Manager Configuration Assistant, refer to "Starting the Enterprise Manager Configuration Assistant" on page 3-2.

Configuration Operation

Select "Configure local Management Server" from the list of configuration operations in the Configuration Operation page and press Next to Continue.

For details about the Configuration Operation page, see Configuration Operation on page 3-6.

Configure Management Server

On the Configure Management Server page, choose "Use an existing repository" to configure a second or subsequent Management Server to share an existing repository with other Management Servers, and press Next to Continue.

If a configuration already exists, a dialog appears asking you if you want to edit this configuration or create a new configuration. See Figure 3-3, "Edit or Create Dialog". Clicking the Edit button takes you to the Edit Configuration Parameters page directly.

Edit Configuration Parameters

On the Edit Configuration Parameters page, direct the local Management Server to use an existing repository by entering the username, password, and service for an existing repository.
User Name

Enter the user name of the existing repository which you wish this machine's Management Server to use or enter the repository's user name to change the Management Server configuration to use another repository. The user name is a database username, not an Oracle Enterprise Manager administrator name.

Password

Enter the password for the above user name or enter the repository user's password to change the password that the Management Server uses to log into the repository when it starts. The information will be used on the next Management Server start up.

If you change the password, you must also change the Confirm field so that it matches the password you changed.

Service

Enter the service/database where the repository resides to change the Management Server to use a repository in another database.

This information will be used when this machine's Management Server next starts up. If any of the information is invalid, then the Management Server will not start successfully.

Do not save username and password

You can choose whether to save the user name and encrypted password in the omsconfig.properties file, which is read by the Management Server on startup. If the user name and encrypted password are stored in the file, the Management Server uses them to login to the repository.

On Windows NT, if they are not saved, you can enter them in the Control Panel's Startup Parameters field when you start the Management Server. If you do not enter the repository credentials in the Startup Parameters field, you will be prompted for them in a dialog.

On UNIX, if they are not saved, the Management Server will prompt you for a user name and password before it starts up.

If you do not want to save the user name and password, check the "Do not save username and password" checkbox. The option of not storing your repository credentials is referred to as the secure Management Server mode.

Press the Next button to proceed from the Edit Configuration Parameters page.

If the username and password are not stored in the configuration file, you are prompted with a Login dialog for the credentials to log into the repository. The Configuration Assistant connects to the specified repository and validates the specified repository and displays any errors it encounters. If the validation was successful, the Select Management Region page appears.

Select Management Region

If you have a large, global deployment of Enterprise Manager or have Enterprise Manager deployed across a mixture of LANs and WANs, then you should consider using the new 9i feature Management Regions. In both situations, Management Regions can improve performance over slow networks by allowing you to assign a subset of Management Servers and a subset of discovered nodes to a Management Region to prevent cross-regional or cross-network communication. Additionally, Management Regions are useful for mapping discovered nodes within firewall boundaries.

For example: Company XYZ has a Management Server running in England and monitored targets in England. It also has a Management Server running at its headquarters in California and monitored targets in California.

With previous releases of Enterprise Manager, the Management Server in England could actually monitor the targets in California. You could not "bind" a Management Server to the targets. Additionally, if there is a firewall between the Management Server in England and the monitored node in California, the Management Server and the nodes would not interact with each other. Management Regions functionality in release 9i prevents this cross regional communication and allows users to specify that the Management Server in England should only monitor targets in England (within a firewall). It should not monitor the targets in California.

The Enterprise Manager Configuration Assistant by default creates the initial, default Management Region called DEFAULT. By default, all Management Servers that use the existing repository and all discovered nodes within the repository will be placed within this DEFAULT Management Region. If your enterprise does not see a need to use Management Region functionality (i.e. you do not have a large, global enterprise or a deployment that spans several LANs and WANs) then using this DEFAULT Management Region would be sufficient. However, if you want to take complete advantage of the Management Region functionality, then you should create additional Management Regions and specify a subset of discovered nodes and a subset of Management Servers within each Management Region.

When a Management Server is not already assigned to a Management Region, the Enterprise Manager Configuration Assistant will prompt you to assign it to one, or to create an entirely new Management Region to which the local Management Server will be assigned. Under most circumstances, the Select Management Region page will appear with the options disabled because the Management Server will have already been assigned to a Management Region. In this case, an explanatory message will appear in red within the page.

In situations where the local Management Server is not already assigned to a Management Region, you will see the following page in Enterprise Manager Configuration Assistant:

Figure 3-15 Assign Management Region


Text description of mg_regio.gif follows.
Text description of the illustration mg_regio.gif


Note:

Creating new Management Regions and assigning Management Servers to Management Regions is also accessible from the Enterprise Manager Console. From the Console, only Super Administrators have access to this functionality. 


Select one of the listed options or enter a name for a new management region.


An existing region

Select Region: Select the region from the pull-down list.

By default, all nodes and Management Servers are in the same management region, called DEFAULT. You can reassign a node/Management Server from one management region to another if you are logged into the Console as a super administrator.


A new region you create

Region Name: Type in the name of the region.


Note:

In order to progress to the next page, you must change at least one of the parameters in the Edit Configuration Parameters page or the Select Management Regions page. If the Next button is pressed without changing anything, an error message appears: "There were no changes to the configuration parameters. Make changes or cancel." In this case, the Enterprise Manager Configuration Assistant does not allow navigation to the next page. 


Configuration Parameters Summary

The "Configuration Parameters Summary" page provides a summary of all the information supplied during the modify configuration parameters operation. Click Finish to initiate the change or click Back to return to previous pages to change your information.


Note:

When you use the Edit Configuration Parameters to change parameters, the Configuration Assistant changes the Management Server configuration parameters, which are stored in the configuration file: ORACLE_HOME\sysman\config\omsconfig.properties. These parameters provide the necessary input to the Management Server, so that it may connect to the repository user within the proper database. The Configuration Assistant does not change the repository username or password in the repository itself once the repository has been created. The Configuration Assistant only manipulates the repository user's password at repository creation time when it creates the repository user. 


Upgrading a Release 2.x Repository to a Release 9i Repository

Existing pre-9i repositories are not upgraded automatically during installation. To upgrade, you must run the Oracle Enterprise Manager Configuration Assistant manually after the installation. Prior to upgrading, you need to create a new 9i repository.

The Oracle Enterprise Manager Configuration Assistant takes an existing Release 2.x repository and upgrades it directly to a Release 9i. After the upgrade, the repository is at the newer version.

Direct migration of Release 1.x repositories to a single Release 9i repository is not supported with the Enterprise Manager Configuration Assistant. This migration is a two step process. First you must run the Enterprise Manager Migration Assistant to migrate Version 1 to Version 2 and then run the Enterprise Manager Configuration Assistant Release 9i to upgrade Version 2 to Version 9. Refer to the Oracle Enterprise Manager Configuration Guide Release 2.2 for instructions on migrating Version 1 repositories to a single Version 2 repository.

Stopping Management Servers and Enterprise Manager Applications

Before you attempt to perform an upgrade, you must first stop all Management Servers and Oracle Enterprise Manager applications that are using this repository. If any Management Server is currently using this repository, upgrading the repository causes a server error.

Backing Up the Repository

Before you attempt to upgrade the repository, you must first back up the database or repository schema using the standard export mechanism.


Note:

A repository created under the SYS user cannot be exported.  


The EXPORT utility is a base utility shipped with the Oracle database server. For detailed information about the Export utility, refer to Oracle9i Utilities.

If there is a failure during a repository upgrade, the repository will no longer be usable. The failed repository would no longer appear in the list of available repositories that could be upgraded.

Coordinating the Upgrade of Oracle Enterprise Manager Products

If you are using a Release 2.x repository and want to upgrade your repository to Release 9i, do not perform any repository upgrades until all Oracle Enterprise Manager components have been upgraded to Release 9i.

Because an Enterprise Manager repository is shared, it is important to coordinate your repository upgrade with the installation of the new Oracle Enterprise Manager software on all the machines that share the repository. If you do not upgrade your repository, the new version of the software will not operate with that repository.

However, if you do upgrade your repository, the older version of the software will not operate with that repository. Remember that both the base Oracle Enterprise Manager system, which includes the Management Server, and the Oracle Enterprise Manager packs share a repository, so if you want all your users to continue to perform their work, you must ensure that the repository upgrade is coordinated with the software upgrades on all relevant machines.

The Enterprise Manager Console, separately licensable Packs, Management Server and repository must all be of the same release. For example, you cannot use a Release 2.2 Management Server and repository with a Release 9i Console nor can you use a Release 9i Management Server and repository with a Release 2.2 Pack.

If the existing Management Server and repository are of a previous version, then you can upgrade them to the most recent version. In the case of upgrading a Management Server and repository to Release 9i, ensure that all Enterprise Manager products you intend to use with the repository are of Release 9i. For instance, do not upgrade the Management Server and repository to Release 9i if you are still using Diagnostics Pack Release 2.2 or Change Management Pack Release 2.2.


Note:

Reports scheduled and generated with the Enterprise Manager Reporting Wizard Release 2.2 cannot be upgraded to Release 9.0.x. 


Configuration Assistant Steps to Upgrading the Repository

To upgrade the repository, follow the steps outlined in the following sections.


Note:

All job and event details in the repository are stored in binary fields to keep the information secure. The data itself is also encrypted using the schema owner name. Therefore, an Enterprise Manager repository can be moved to another database, but the owner of the repository must have the same schema name. You cannot change the schema name of a repository. If you export/import the repository from one user to another, the decryption key will not match and your jobs and events will no longer be usable. 


For information about starting the Enterprise Manager Configuration Assistant, refer to "Starting the Enterprise Manager Configuration Assistant" on page 3-2.

Configuration Operation

When you press the Next button on the Welcome page, the "Configuration Operation" page appears.

Select "Upgrade an existing repository" from the list of configuration operations and press Next to continue. The "Select Database for Repository" page appears.

Select Database for Repository

Log in to the database which contains the repository you want to upgrade.

In order to upgrade a repository, you must connect to the database as a user with DBA privileges. The repository schema user created by the Enterprise Manager Configuration Assistant will not have the necessary DBA privileges for this step. To avoid potential security issues, do not grant more privileges to your repository schema user than is necessary. Connect to the database as a different user with DBA privileges instead. For example, system/manager.

For information about logging in to the database which contains the repository, refer to Select Database for Repository on page 3-15.

If you log in successfully, the "Select Repository" page appears.

Select Repository for Upgrade

If you are selecting a repository to upgrade, the Select Repository page shows only Release 2.0, 2.1, and 2.2 repositories. The Enterprise Manager Configuration Assistant does not display Release 9.0.1 repositories in this situation, because they do not need to be upgraded; they are already at the most up-to-date version.

Select the appropriate repository and press the Next button to continue.

If the specified database does not contain any Release 2.x repositories, the list of repositories is empty and grayed out, and a note stating that "No repositories were found in the database" appears. You may click the Cancel button to exit the Enterprise Manager Configuration Assistant or click the Back button to return to previous pages to connect to a different database.

Repository Login Information

In the "Repository Login Information" page, you must supply the repository user password.

During repository creation, a database user (repository schema user) who owns the repository was created by the Enterprise Manager Configuration Assistant with the username and password you have supplied.

In order to perform a repository upgrade, it is necessary to logon to the repository database as this user.

The repository user name has been entered into the username field as a result of your choice in the previous page. However, you will need to enter the password.

Press Next to continue. The "Upgrade Repository Summary" page appears.

Upgrade Repository Summary

The "Upgrade Repository Summary" page provides a summary of all the information supplied during the upgrade repository session. Click Finish to initiate the repository upgrade or click Back to return to previous pages to change the information.

Upgrade Repository Configuration Assistant Progress

When you click the Finish button, the Configuration Assistant Progress window appears, showing the processing performed and the processing steps that comprise the operation being performed. Each processing step is shown by a line of text.

If you want to view detailed information, click the "Show Details" button to expand the dialog to show a text area. You can hide the text area by pressing the "Hide Details" button.

The Cancel button changes to a Close button when processing is completed whether it is successful or not.

When all of the steps have been completed without error, the "Processing completed." message appears.

You can cancel the requested operation before it completes by clicking the Cancel button. However, if you cancel the operation, the repository will become unusable.

Click the Close button when you are finished.

During the Configuration Assistant upgrade operation, the Oracle Management Service will be created, if it does not already exist and only if the repository being upgraded is the one actually being used by the local Management Server.

Dropping an Existing Repository

In order to drop a repository, you must connect to the database as a user with DBA privileges.

To drop the repository and deconfigure the local Management Server if it uses that repository, follow the steps outlined in the following sections.

Stop the Management Servers and Enterprise Manager Applications

Before you attempt to drop the repository, you must first stop all Management Servers and Oracle Enterprise Manager applications that are using this repository.

If any Management Server is currently using this repository, deleting the repository causes a server error.

Start the Configuration Assistant

For information about starting the Enterprise Manager Configuration Assistant, refer to "Starting the Enterprise Manager Configuration Assistant" on page 3-2.

Drop Repository Configuration Operation

After pressing the Next button on the Welcome page, the "Configuration Operation" page appears.

Select "Drop an existing repository" from the list of configuration operations and press Next to continue. The "Select Database for Repository" page appears.

Select the Database of the Repository You Want to Drop

Log in to the database which contains the repository you want to drop. You must connect to the database as a user with DBA privileges.

The repository schema user created by the Enterprise Manager Configuration Assistant will not have the necessary DBA privileges for this step. To avoid potential security issues, do not grant more privileges to your repository schema user than is necessary. Connect to the database as a different user with DBA privileges instead. For example, system/manager.

For information about logging in to the database which contains the repository, refer to Select Database for Repository on page 3-15. If you log in successfully, the "Select Repository" page appears.

Select Repository to Drop

If you are selecting a repository to drop, the Select Repository page shows all releases of repositories, beginning with 2.0.

Choose the appropriate repository and press the Next button to continue.

If the specified database does not contain any Release 2.x or 9i repositories, the list of repositories is empty and grayed out, and a note stating that "No repositories were found in the database" appears. You may click the Cancel button to exit the Enterprise Manager Configuration Assistant or click the Back button to return to previous pages to change the information.

Select Drop Repository Options

From the "Select Drop Repository Options" page, you can choose to drop the repository user and all its schema objects or merely the repository objects.

If you choose to drop only the repository, you must supply the repository user's password so that the Enterprise Manager Configuration Assistant can connect to the repository in order to invoke the Oracle Enterprise Manager SQL drop scripts. Only repository objects are dropped. Other schema objects in the repository remain.

If you choose to drop the repository user and all its schema objects, a password is not required. Make sure that you do not have other objects of value in that schema before proceeding with this step. Valuable data may be lost if you do not ensure this.

If a repository is selected that is not at the current/latest version, the only valid choice is to drop the repository user because the drop scripts can only handle the latest/current version.

If the Configuration Assistant detects that a managed repository is specified in the omsconfig.properties file, and you are not dropping that repository, the Configuration Assistant will not change the Management Server configuration.

If you are dropping the managed repository, the Configuration Assistant will clear the Management Server configuration.

Press Next to continue. The "Drop Repository Summary" page appears.

Drop Repository Summary

The "Drop Repository Summary" page provides a summary of all the information supplied during the drop repository operation.

Click Finish to initiate repository removal or click Back to return to previous pages to change the information.

Drop Repository Configuration Assistant Progress

When you click the Finish button, the Configuration Assistant Progress window appears, showing the processing performed and the processing steps that comprise the operation being performed. Each processing step is shown by a line of text.

If you want to view detailed information, click the "Show Details" button to expand the dialog to show a text area. You can hide the text area by pressing the "Hide Details" button.

The Cancel button changes to a Close button when processing is completed whether it is successful or not.

When all of the steps have been completed without error, the "Processing completed." message appears.

You can cancel the requested operation before it completes by clicking the Cancel button.

Click the Close button when you are finished.

Controlling the Management Server After Configuration

Once configured, the Management Server provides distributed control between clients and managed nodes. A central engine for notification, it processes all system management tasks and administers the distribution of these tasks across the enterprise.

Specific topics discussed in this section are listed below:

Starting a Local Management Server

The repository database used with the Management Server must be started and open and the database listener must be started before starting the Management Server.

Starting a Local Management Server On Windows

To start the Management Server on Windows, follow the instructions below.

  1. From the Start menu->Settings->Control Panel, double-click the Services icon.

  2. If you have chosen not to store your repository credentials during repository creation (referred to as the secure Management Server mode), you can enter the repository's user name that was used to create the database user and the password for that user in the Control Panel's Startup Parameters field when you start the Management Server. The Startup Parameters field is under the list of services. The database user and password must be in the format of <username>/<password>.

    If you supply invalid or incomplete repository credentials in the Control Panel's Startup Parameters field, the Management Server will not start, and an error message will appear.

    If you are in secure mode and do not enter the repository credentials in the Startup Parameters field, you will be prompted for them later in a dialog.

    For information on troubleshooting the Management Server if it does not start, refer to "Management Server Does Not Start" on page F-16.

  3. Select the Oracle<Oracle_Home_Name>ManagementServer service.

  4. Click the Startup push-button to access the Service Startup dialog box.


Note:

Step 4 only needs to be performed once, not every time you start up the service. 


    1. In the Startup Type section, specify how the Management Server service is started up by choosing Automatic or Manual. Manual allows the Management Server to be started by a user. Automatic allows the Management Server to start automatically whenever the user starts the system. Disabled does not allow the Management Server to start at all. By default, the Configuration Assistant sets the service to Manual.

    2. In the Log On As section, check for the following settings:

      • Ensure that the System Account option, which is the supported way to run the Management Server, is selected. The Management Server will not run if you use a local account.

      • Ensure that the "Allow Service to Interact with Desktop" box is selected; otherwise, the Management Server will not run.

  1. Click the Start push-button to start the Management Server.


Note:

Your Management Server service is started automatically and set to Manual on Windows during repository creation if you had launched the Enterprise Manager Configuration Assistant from an installation session and if you had chosen to save your repository credentials.

If you have chosen not to save your repository credentials, you can enter them in the Control Panel's Startup Parameters field when you start the Management Server. If you do not enter the repository credentials in the Startup Parameters field, you will be prompted for them in a dialog. 


Starting a Local Management Server On UNIX

To start the Management Server on UNIX, at the command line, enter

% oemctl start oms

When you are prompted, enter the repository's user name that was used to create the database user and the password for that user if you have chosen not to save your repository credentials during repository configuration. For a complete definition of a repository owner, refer to "Repository Login Information" on page 3-16.


Note:

If the ORACLE_HOME environment variable is not set to the Oracle home in which the Management Server is running, the Management Server will not start correctly because it will try to find its class files in the default Oracle home instead of the correct Oracle home. For information on setting the Oracle environment, refer to "Management Server May Not Run Correctly from a Non-Default Oracle Home" on page F-15


Checking the Status of the Management Server

To quickly check whether a local or remote Management Server is up or down on Windows or UNIX, at the operating system prompt, enter:

% oemctl ping oms

To check the status of the Management Server on Windows or UNIX, at the operating system prompt, enter:

% oemctl status oms

You will be prompted to enter the username and password of an Oracle Enterprise super administrator. You will also need to provide the hostname for the machine running the Management Server if you are checking the status of a remote Management Server. For example, znripley-pc.ovenbird.com.

The information that oemctl status oms returns include the following:

An example of the output is shown below:

OEMCTL for Windows NT: Version 9.0.0.0.0
Copyright (c) 1998, 2001 Oracle Corporation.  All rights reserved.

The Oracle Management Server on host [znripley-pc.ovenbird.com] is functioning 
pr
operly.

  The server has been up for 0 00:00:25.953

  Target database session count: 0 (session sharing is off)
  Operations queued for processing: 1
  Number of OMS systems in domain: 1 (znripley-pc.ovenbird.com)
  Number of administrators logged in: 0
  Repository session pool depth: 15
  Repository session count: 8 in-use and 1 available, pool efficiency: 18%

Stopping a Local Management Server

To stop a local Management Server, perform the following steps:


On Windows:
  1. From the Start menu->Settings->Control Panel, double-click the Services icon.

  2. Select the Oracle<Oracle_Home_Name>ManagementServer service.

  3. Click the Stop push-button to stop the Management Server.

You will be prompted to enter the username and password of an Oracle Enterprise super administrator.


On UNIX:

At the command line, enter

% oemctl stop oms

You will be prompted to enter the username and password of an Oracle Enterprise super administrator.


Go to previous page Go to next page
Oracle
Copyright © 2001 Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Library
Go To Product List
Product
Go To Table Of Contents
Contents
Go To Index
Index