Skip Headers

Oracle® Enterprise Manager Grid Control Installation and Basic Configuration
10g Release 1 (10.1)
Part No. B12012-03
  Go To Table Of Contents
Contents
Go To Index
Index

Previous Next  

3 Post-Installation Configuration Tasks

This chapter identifies post-installation configuration tasks you must complete after installation. The following topics are covered in this chapter:

Running root.sh to Complete the Post-Installation

If you have performed and completed a silent installation on Solaris, you must run the root.sh script as root to complete the post-installation. (This step is not required for Windows.) The root.sh script finishes the post-installation steps for the Oracle Management Agent, Management Service, and Management Repository database. If you used interactive mode to install Enterprise Manager, you were prompted to run root.sh before completing your installation.

On the Management Service machine, run the root.sh script as root from the $ORACLE_HOME directory.


Note:

For a cluster installation, you must run the root.sh script on each host of the cluster on which you installed a Management Agent.

Checking Database Settings

After the Management Repository has been created you may need to set certain database parameters or settings after installation. Refer to Appendix B for initialization parameters and additional database settings.

Accessing the OracleMetaLink Web Site

To search OracleMetaLink and download Oracle software patches and patchsets using Enterprise Manager, refer to the following sections.

Specifying OracleMetaLink Credentials

Enterprise Manager uses OracleMetaLink credentials to search for and download OracleMetaLink patches. If you did not specify your OracleMetaLink credentials during installation, you can do the following:

  1. On the Enterprise Manager Grid Control Home page, click Setup.

  2. On the Setup page, click Patching Setup.

  3. Specify your OracleMetaLink user name and password in the fields provided.

The URL to access the OracleMetaLink Web site is displayed in the Patch Search URL field on this page:

Access OracleMetaLink directly by going to the following Web site:

http://metalink.oracle.com

From this page, Oracle licensees can register for an account or log in with an existing account. Once logged in, you can search for and download patches.

Setting Up the Proxy Configuration for the Management Service

If your firewall prevents you from accessing Web sites without the use of an HTTP proxy, then you must set the proxy settings for Enterprise Manager to access OracleMetaLink.


See Also:

For information about configuring Enterprise Manager components, such as Management Agents and Beacons, for use in a firewall environment, refer to Oracle Enterprise Manager Advanced Configuration.

If Enterprise Manager is using a proxy server for external access, the following properties must be properly set in the sysman/config/emoms.properties file (with backslashes for Windows):

proxyHost=www-fooproxy.here.com
proxyPort=80
dontProxyFor=.here.com

See Also:

For information about configuring the Management Service properties file, refer to Oracle Enterprise Manager Advanced Configuration.

You can also specify domain names that will cover all hosts with those domain. For example:

dontProxyFor=.us.mycompany.com, .uk.mycompany.com

If the proxy properties are set incorrectly or not set at all, and you try to search for a patch, you will receive an error message indicating that Enterprise Manager cannot access the OracleMetaLink Web site.

Setting Up the Proxy Configuration for the Management Agent

There are two ways to specify proxy information for a Management Agent:

  • Specify values for s_proxyHost and s_proxyPort using a response file when performing a silent installation using Oracle Universal Installer.

  • Specify values directly through the command line option when invoking Oracle Universal Installer. For example:

    <runInstaller or setup.exe> oracle.sysman.top.agent:s_proxyHost="<value>" oracle.sysman.top.agent:s_proxyPort="<value>"
    

Setting Credentials for the Job System (Windows Only)

Windows systems (NT 4.0, 2000, XP, 2003) require that you set the correct credentials for the Jobs system to work properly in Enterprise Manager. By default, the Management Agent service is installed as a LocalSystem user. When submitting jobs, the user submitting the job must have the "Log on as a batch job" privilege enabled.

Perform the following steps to establish that privilege for any user who needs to submit an Enteprise Manager job. This is also required to enable the Preferred Credentials feature.

On Windows 2000, XP, and 2003 systems:

  1. Start the Local Security Policy tool located by clicking Settings, then Control Panel, then Administrative Tools in the Start menu.

  2. Under Local Policies/User Rights Assignment, add the user to the Log on as a batch job privilege.

  3. Windows 2000 may require a restart for the policy change to take effect. Restart as necessary.

On Windows NT 4.0 systems:

  1. Start the User Manager tool by selecting Programs, then Administrative Tools, then User Manager on the Start menu.

  2. Select User Rights from the Policies menu.

  3. Select the Show Advanced User Rights check box.

  4. Select Log on as a batch job from the Right drop-down menu.

  5. Click Add to add the Windows user who is submitting an Enterprise Manager job.

If a user exist both locally and at the domain level, Windows gives the local user precedence. To use the domain user, qualify the user name with the domain name. For example, to use the user joe in the ACCOUNTS domain, specify the username as ACCOUNTS\joe.


Note:

If the Management Agent NT service is installed as any other user (that is, not LocalSystem), then, in addition to granting the "Log on as a batch job" privilege, the user must be granted the following three privileges:
  • Act as part of the operating system.

  • Adjust memory quotas for a process. (This is named "Increase memory quotas" on Windows 2000 and NT 4.0.)

  • Replace a process level token.

In this case, the above three privileges must be granted to the "NT service" user, not the "job" user.


Configuring Database and ASM Targets for Monitoring

When you first display the Database Home page for an Oracle Database 10g target, the Database Home page may display no monitoring data and the status of the database may indicate that there is a metric collection error. This is because you need to supply the DBSNMP password to use to monitor the database. The database may also be listed as being down because the DBSNMP user account has been locked due to unsuccessful login attempts.

Similarly, the first time you display the home page for an Automatic Storage Management (ASM) target, the status of the ASM instance may be unknown or unavailable, and the home page may indicate that the Management Agent is down. Again, this is because you need to supply the ASM SYS password.


Note:

You may first need to unlock the DBSNMP user account before setting the monitoring credentials. If the account is not locked, skip "Unlocking the DBSNMP User Account" and proceed to "Setting Monitoring Credentials" for instructions.

To fix this problem for an Oracle Database 10g target, do the following from the Grid Control Console:

  1. Unlock the DBSNMP account (if necessary).

  2. Update the DBSNMP account password.

These steps are described in detail in the following sections:

Unlocking the DBSNMP User Account

To unlock the DBSNMP user account:

  1. From the Grid Control Console, navigate to the Database Home page and click Administration to display the list of administration functions.

  2. Under Security, click Users to display the list of all user accounts. If you are prompted to log in to the database, make sure to use a database user account with DBA privileges such as SYSTEM.

  3. Find and select the DBSNMP user account, select Unlock User from the Actions menu, and click Go and confirm your choice.

  4. Set the DBSNMP password as described in the "Setting Monitoring Credentials" section. Once the password is set, monitoring can begin.

Setting Monitoring Credentials

You must reset the monitoring credentials for database and ASM targets if the passwords you specified during installation were different from the defaults that Enterprise Manager expects. If you change a password at any time, make sure to update all components using that password as well.

This section contains the following subsections:

Setting Monitoring Credentials for Database Targets

To set the monitoring credentials for a single-instance or cluster Oracle Database 10g target:

  1. From the Grid Control Console, navigate to the Configure Database: Properties page:

    1. On the Targets tab, click Databases to display the list of database targets.

    2. Find and select the database target and click Configure.

    Enterprise Manager displays the Configure Database: Properties page.

  2. Enter the correct password for the DBSNMP user in the Monitor Password field and click Test Connection to verify the monitoring credentials.

  3. If the connection is successful, click Next, then click Submit.

You should now be able to view the complete Database Home page for the Oracle Database 10g target. For more information, see "Specifying New Target Monitoring Credentials," in Oracle Enterprise Manager Advanced Configuration.


Note:

If you change the DBSNMP password at a later date, you must update the password for Grid Control and Database Control and may need to unlock the account.

If you are using Database Control, update the DBSNMP password by doing the following:

  1. Click Monitoring Configuration under Related Links on the Database Control Home page. Enterprise Manager displays the Configure Database: Properties page.

  2. Enter the correct password in the Monitor Password field and click Test Connection. If the connection is successful, click Next, then Submit.


Setting Monitoring Credentials for ASM Targets

To set the monitoring credentials for an ASM target:

  1. From the Grid Control Console, click All Targets on the Targets tab to display a list of all managed targets.

  2. Find and select the ASM target that you want to modify.

  3. Click Configure to display the ASM Monitoring Configuration page.

  4. Enter the ASM SYS password in the Password field and click OK.

You should now be able to view the complete home page for the ASM target with no Management Agent or collection errors. For more information, see "Specifying New Target Monitoring Credentials," in Oracle Enterprise Manager Advanced Configuration.