Oracle Enterprise Manager 10g
Grid Control Release 10.1.0.2
Readme
Last updated: January 28, 2004


Table of Contents

 1.   General
        1.1  Introduction
        1.2  Installation and Configuration
2.    Oracle Management Service/Repository/Management Agent
3.    Monitoring System
4.    Blackouts
5.    Jobs
6.   Database Management
        6.1 Data Guard
        6.2 Reorganize Objects
7.    Configuration Management Pack
8.    Application Server Management
9.    Application Performance Management
10.  Oracle Collaboration Suite
11.  EM2Go
12.  Enterprise Manager 9i to 10.1 Migration

1.  General

1.1  Introduction
This Readme identifies differences between the delivered Oracle Enterprise Manager 10g Grid Control Release 10.1.0.2. product and its documented functionality. 

1.2  Installation
1.2.1 Resuming Agent Installations After  Failure
While performing "Complete Enterprise Manager with a Database", "Complete Enterprise Manager in an Existing Database" or "Additional Management Service" install, if the agent install fails, you can resume the Management Agent install after exiting Oracle Universal Installer by performing the following steps :

        a)  Set the environment variable EM_REPOS_PWD to the value of sysman schema password entered in the OMS install, using "setenv" for C-Shell and export for Korn shell .
        b)  If the install performed was "Complete Enterprise Manager  with a Database" or "Complete Enterprise Manager in an Existing Database", set the environment variable EM_REPOS_DBSYSPWD to the value of sys schema password
        c)  Execute the installer using the following command:

                runInstaller -responseFile <oms_home>/agent/agent.rsp

Alternately, you can run the installer in GUI (interactive) mode and invoke the "Additional Management Agent" installation for the agent home. The agent home  is typically created at the same level as the Enterprise Manager home. However, it may be nested within the Enterprise Manager home in cases where the parent directory of the Enterprise Manager home cannot be written onto.

1.2.2  Installation of the OMS and Agent on machines with multiple network interfaces and/or virtual hosts
Machines with multiple network interfaces or virtual hosts bound to single or multiple network adapters are accessible by more than one IP address. The Enterprise Manager installation for both the Management Service and the Management Agent will always select the primary machine alias.

            1.2.2.1  Changing Management Service IP Address
Changing Management Service IP address after initial installation is not currently supported without deinstalling and reinstalling the Management Service.

1.2.2.2 Changing the Management Agent IP address after initial installation
If the existing host name remains unchanged but resolves to a new IP address, then no changes are required.

If the Agent host is assigned a new machine name (a new primary alias that resolves to the current IP address, or a new IP address), then the following steps will rename the Agent on the managed node.

a) Create a backup of the existing targets.xml
b) Edit the existing targets.xml, replacing the old host name with the new host name
c) Alter the Management Agent configuration file:

Edit the EMD_URL property in
$ORACLE_HOME/sysman/config/emd.properties to reflect the new host name.

d) Shut down and restart the Management Agent
e) Verify that the new host name appears in the Enterprise Manager console along with its associated targets.

 

Note: the targets associated with the old host name will continue to be displayed in the Enterprise Manager console. If the historical data are not required, it is recommended that the targets associated with the old host name be removed using the Enterprise Manager console UI.

1.2.3  Retrying Secure Agent action
During the configuration portion of the agent install, the Secure Agent action may fail if the OMS is down or busy processing other requests.

This operation can be retried multiple times from the installer by retrying the "Secure Agent action"  until the agent is secured successfully.  Another alternative is to complete the installation with this failure and use:

emctl secure agent <reg password>

at the command line to secure the agent.

1.2.4 Securing OMS via EMCTL Changes Upload Port
When using non-default ports, the command

emctl secure oms

does not retain the console upload ports specified at install time.  The ports are always defaulted to 4889 (unsecure) and 4888 (secure).

To workaround this problem, set:

EM_UPLOAD_PORT to oracle.sysman.emSDK.svlt.ConsoleServerPort in $ORACLE_HOME/sysman/config/emoms.properties.

EM_UPLOAD_HTTPS_PORT in $ORACLE_HOME/sysman/config/emoms.properties should be set to the port number being used for secure upload.

After setting these variables, rerun emctl secure oms.

 (Bug 3346036)

1.2.5 De-installation
If  you de-install the Enterprise manager 10g ORACLE_HOME using Oracle universal installer (OUI), it de-registers the ORACLE_HOME  from the central inventory and the oratab file. It may, however, leave some files within the ORACLE_HOME. If the ORACLE_HOME has been successfully removed (it can be verified from OUI by clicking on 'Installed products' button) one can manually delete the files using the appropriate command on the Operating System.

 The proper sequence of de-installation is:
        a) Shutdown the repository database (if it is a part of the de-installation)
        b) Shutdown the database listener
        c) Shutdown Apache using "opmnctl stopall"
        d) Shutdown Application Server Console using "emctl stop em"
        e) Shutdown agent in the chained agent home using "emctl stop agent".
        f) Run the Oracle Universal Installer and select the ORACLE_HOME to de-install. It would then be removed from the Central Inventory.
        g) Remove stray files from the ORACLE_HOME by appropriate operating system command. .

1.2.6 Problems With Agent Shutdown Operation on NT 4.0

If you are running the agent on a Windows NT 4.0 host, you may find that the agent does not shutdown or recover gracefully from a timeout. This may lead to an inconsistency between the status reported by ‘emctl’ and the status reported by Windows service control manager. To workaround this issue the following internal command “emctl istop agent” can be issued to shutdown the agent. You may then bring up the agent using your Windows service control manager (Bug 3320183)

1.2.7 Verify NLS settings are configured properly
If you launch opmnctl or emctl in non English environment, make sure the OS default locale and the NLS_LANG settings are configured properly. (Bug 3128644)

1.2.7.1 OS default locale

a) Make sure LC_ALL or LANG environment variables are set with the appropriate value. To check the current setting, issue locale command:
        % locale
    for the specific value in each OS, refer to the platform specific documents.

 

1.2.7.2 NLS_LANG setting

    a) Make sure NLS_LANG environment variable is set with the appropriate and compatible value with the OS default locale setting. For the specific value for the language, refer to the Globalization Support Guide of the Oracle product you are using.

    b) Check if the NLS_LANG setting exists in $ORACLE_HOME/opmn/conf/opmn.xml. If      $ORACLE_HOME/opmn/conf/opmn.xml exists, make sure the NLS_LANG setting in opmn.xml file is identical to the NLS_LANG environment variable. For example,

<environment>
<variable id="NLS_LANG" value="JAPANESE_JAPAN.JA16SJIS"/>
</environment>

 

1.2.8 National Language Support: Performance Analysis Findings Return As Garbled Text
If the NLS settings of the Enterprise Manager repository database are different from the NLS settings of a managed database target, the Performance Analysis findings may return as garbled text, e.g. question marks. The workaround is to click on the finding text, which will display the finding in the language of the database target (Bug 3351589)

 

1.2.9  Changing the agent port for a secured agent
You can change the listen port of an agent by editing the EMD_URL property in the $OH/sysman/config/emd.properties file. If you do this for an agent that has already been secured, you will need to resecure the agent (via emctl secure agent). If you do not resecure the agent, agent uploads to the OMS will fail - data will back up at the agent, and the OMS will not be able to contact the agent to retrieve real time metric values (Bug 2814831)

 

1.2.10 Changing the agent port for an agent monitoring cluster targets
One can change the listen port of an agent by editing the EMD_URL property in the $OH/sysman/config/emd.properties file. If you do this for an agent that monitors cluster targets, the cluster targets will remain in "Agent Unreachable"  state even when the agent is UP. (bug 3376838)
 

1.2.11 OMS Fails to Secure

If all registration passwords are removed, the OMS will not secure any new agents.  You will get the following error:

 

The OMS is not set up for Enterprise Manager Security.

 

To workaround this issue, login to Enterprise Manager as a Super Administrator and add a new registration password from the Setup -> Registration Passwords page.  Once this is finished, resecure the agent using the emctl secure agent command. (Bug 3356147)

 

1.2.12 Use of a RAC database as 10g Grid Repository
The database provided in the installation of the 10g Grid Management Server is a single instance 9.0.1.5 database. In order to have a real application cluster instance, the installation of the 10g Grid Management Server must be that of Management Server using an existing database.

In the course of the installation, the installer will request a SID to be specified. Chose one instance of the Oracle RAC and specify its SID. When prompted for the location of the 10g Grid management tablespaces, insure that the location is one mutually accessible by all members of the RAC.

Upon completion of the installation, edit the $ORACLE_HOME/sysman/config/emoms.properties file. Alter the property of the name oracle.sysman.eml.mntr.emdRepConnectDescriptor to represent the SERVICE name of the RAC vs the SID that will be found there.

Restart the OMS.

Subsequent additions of other OMS' that wish to use the RAC database should perform the installation choice of an 'Additional 10g Grid Management Server'. When prompted for the connection information, they too should specify the SID of one of the database instances comprising the RAC. After the installation has completed, the emoms.properties file in that newly added 10g Grid Management Server's home should be altered in the same manner as in the initial installation. (Bug 3259014)

 

1.2.13 Oracle Universal Installer Does Not Start Up on Windows 2000

Oracle Universal Installer may not start up properly (appear and then disappear) on Windows 2000 with Service pack 4. This is
due to an underlying JRE bug. You need to run 'install\win32\setup.exe -J-Dsun.java2d.noddraw=true' to workaround the issue.

 

1.2.14 Email Address Undefined When Editing Administrators

If you create an administrator, and specify an email address for the administrator, the email address will not show up when you edit that administrator. You must re-enter the email address every time you edit the adminstrator account. (Bug 3378174)

 

1.2.15 Set session_cached_cursors to Reduce SQL Statement Parsing

The database parameter session_cached_cursors can be set to 200 to reduce the amount of sql statement parsing done by the database for sql executed by the Oracle Management Server.  Setting this parameter will reduce cpu usage on the database server.  The amount of cpu reduction is dependant on the size and activities done with the site.  The parameter is especially important it the job system is used heavily.  (Bug 3385784)

2.  Oracle Management Service / Repository / Oracle Management Agent
2.1.0 Securing Multiple Oracle Management Services Should Not Be Done Simultaneously
The first time you secure any Oracle Management Service, you should not attempt to secure more than one Oracle Management Service at a time.  After one Oracle Management Service has been successfully secured, you can secure multiple Oracle Management Services at one time. (Bug 3335221)

2.2.0 Troubleshooting Agent Upload Problems
If data from the agent is not arriving at the OMS/console, the agent trace file might provide a hint about the problem.

In the Agent's oracle home directory,  look for the sysman/log/emagent.trc file.  In this file, look for messages with the string "ERROR upload:" in them.   There is one specific case which points to an OMS that is overloaded and is taking longer time than expected to load the files. The entries in the trace file should look like this:

 

2003-10-31 15:48:45 Thread-1499 ERROR upload: FxferSend: HTTP Error=-2 reading request response from:

http://ap401ses.us.oracle.com:4889/em/upload/

2003-10-31 15:48:45 Thread-1499 ERROR upload: Failed to upload file A0000002.xml , ret = -2

 

If this happens, you may be able to improve the situation somewhat by increasing the timeout of the Apache server in the OMS home.

 

In the oracle home of the OMS, edit the $OH/Apache/Apache/conf/httpd.conf file and change the Timeout setting from

     Timeout   300

           to

     Timeout  600

 

Then stop and restart the OMS in order for the new settings to take effect.   This will allow the system to take more time before dropping the agent connection (and causing it to retry again)

 

2.3.0 Queries to Some Views May Hang

Queries to the following views may hang due to RDBMS bug 3243901.

mgmt$metric_details
mgmt$metric_daily
mgmt$metric_hourly
em$rt_loopback_details_1day
em$rt_metrics_details_1day
em$rt_metrics_details_7day
em$rt_metrics_details_31day
em$rt_loopback_details_7day
em$rt_loopback_details_31day

The shadow process corresponding to this database session will consume a lot of memory and CPU. The fix to this problem is to kill that database session and recompile these views. Alternatively use a 9204 database for your management repository.

 

2.4.0 Out of Memory Errors Under Heavy Load

Under heavy load, especially when connecting to multiple target databases, the Oracle Management Service may encounter out-of-memory errors and restart. When an Oracle Management Service restarts, there is no loss of state in the repository, but users logged in to that Management Service will be asked to login again. If the restarts are frequent, do the following for each installed Management Service:

 

a)  Stop the oms;

 $ORACLE_HOME/opmn/bin/opmnctl stopall
 

(Note: it is important to use opmnctl stopall here rather than the usual "emctl stop oms" since we need to
completely stop the associated Application Server instance as well)

b)  Edit $ORACLE_HOME/opmn/conf/opmn.xml
Search for the OC4J_EM section, which is a line that looks like this:

<process-type id="OC4J_EM" module-id="OC4J">

Edit the "java-options" data tag under this process type. Before edit, this line should look similar to this:

<data id="java-options" value="-server
-Djava.security.policy=/private/smptest/oms_rel9/j2ee/OC4J_EM/config/java2.policy
-Djava.awt.headless=true -Xmx512M -XX:MaxPermSize=64m
-DORACLE_HOME=/private/smptest/oms_rel9 "/>


Change the -Xmx option from 512M to 1024M, and the -XX:MaxPermSize option from 64M to 256M. Also add the
-Xnoclassgc option.

 

After edits, the line should look like this:

<data id="java-options" value="-server
-Djava.security.policy=/private/smptest/oms_rel9/j2ee/OC4J_EM/config/java2.policy
-Djava.awt.headless=true -Xmx1024M -XX:MaxPermSize=256M -Xnoclassgc
-DORACLE_HOME=/private/smptest/oms_rel9 "/>

c) Restart the Oracle Management Service using emctl start oms. (Bug 3272105)

 

2.5.0 Oracle Management Service Deadlocks

During intense OMS activity, two or more threads in the OMS may deadlock. As a result, the Oracle Management Service interface pages may become unresponsive, or the OMS may not upload data from agents. This is a Oracle jdbc issue, and a patch for this is forthcoming.  Please check MetaLink for patch availability. (Bug 3347676)

 

2.6.0 Security Considerations When Adding Granting "Manage Group" Privileges
As an Enterprise Manager super administrator, use caution when assigning group privileges to other Enterprise Manager administrators. For example, if you grant a user "Full" privileges for a particular group, note that the user who created the group could add additional targets to the group and indirectly give other users full privileges to these targets. In other words, any users that have full privileges on the group will also have full privileges on targets added to the group by the group creator.
 

In general, Enterprise Manager super administrators should make sure that no users have higher privileges on a group than the user or users who manage the group. (Bug 3217302)

 

2.7.0 Java Exception When Logging Into Enterprise Manager

You may see the following Java Error when logging into Enterprise Manager:

 

 java.sql.SQLException: ORA-00020: maximum number of processes (300)exceeded

 

If this happens, you will need to stop and restart your Oracle Management Service (Bug 3401100)

 

2.8.0 Installing Management Agents on Clusters

If you are installing Oracle Management Agents on a cluster with vendor clusterware that does not have Oracle 10g CRS installed, cluster databases can not be discovered by the agent install or via EM Console Add target interface.The workaround is to change the targets.xml on *all* the cluster hosts as follows.

Assuming that the host name is myhost.mydomain.com, the targets.xml should be edited as below. Note that the change below involves adding a new entry for cluster target and updating the host target to register cluster membership. The cluster target name must be the same on all hosts.

       <Target TYPE="cluster" NAME="your_cluster_name" />
        <Target TYPE="host" NAME="myhost.mydomain.com">
                <CompositeMembership>
                        <MemberOf TYPE="cluster"
NAME="your_cluster_name"
ASSOCIATION="cluster_member"/>
                </CompositeMembership>
        </Target>

Shutdown and restart the agent before proceeding to exercising the Add Target interface via EM console to discover the cluster database target. You can delete improperly discovered targets from EM Console if needed.
 

3.  Monitoring System
3.1.0  User-Defined Metrics
If the name specified for the database User Defined Metric is more than 30 characters, the metric will not be evaluated properly.  Please ensure that the metric name is at most 30 characters (Bug 3301697)

3.2.0  Metric Errors for User-Defined Metrics
If the evaluation of a user-defined metric results in an error, then there will be no return value associated with the metric in the User-Defined Metrics page.   The user should go to the Errors subtab of the Alerts tab to get information about the metric error (Bug 3301699)

3.3.0  Alert remains for deleted User-Defined Metrics
If a user deletes a User-Defined Metric that is still in warning or critical alert, then the alert will remain.   Make sure the User-Defined Metric is in 'clear' state before deleting it (Bug 3301704)

3.4.0  Agent Unreachable in the Availability page
If a target is currently in the 'Agent Unreachable' state, then in the Availability page for that target,  this 'Agent Unreachable' state is shown in 'white' (i.e. no color) in the bar graph that represents the target’s availability over time.   Typically, the Agent Unreachable state is reached if there are network problems between the Oracle Management Service and the Agent that is monitoring the target,  making the true target status unavailable for display in the console.  Once the target is out of Agent Unreachable state,  then the 'Agent Unreachable' period will be replaced in the bar graph with the appropriate status of the target (up, down, etc) (Bug 3152217)

3.5.0  Response Actions
    3.5.1  Response Actions will not work for server-generated alerts.   (Bug 3129353)
    3.5.2  Response Actions for metrics can only be specified by Enterprise Manager users with superuser privileges

3.6.0 Issues with host metrics on NT 4.0

If you are running the agent on a Windows NT 4.0 host with more than 2 GB of RAM, you may find that certain host metrics related to host memory are inaccurate. (Bug 3294952)

 

3.7.0 Missing Help for Metric Details

In some cases when you are displaying a metric on the Metric Detail Page and you click Help, the help system displays the Table of Contents for the help system, not the appropriate help topic for the metric. In this situation, the workaround is to choose one of the Real Time options in the View Data field on the Metric Detail page, then click the Help link again. Then the help system will display the appropriate metric help topic. (Bug 3341196)

 

3.8.0  Host Metrics on Solaris 9

On Solaris 9, the Host target has been enhanced by the addition of a new metric - Aggregate resource usage statistics, gathered by User and by Project. These metrics are collected by using the "CIM Object Manager" on the Solaris 9 host. In order to get this information, the CIM Object Manager needs to be supplied with Username and Password of a user on that host so that authentication can successfully happen. These values can be provided by following the Monitoring Configuration link from the Host homepage for this target. (Bug 3330619)

The following are examples of Errors/Messages seen when the credentials have not been provided:

2004-01-01 19:09:53 Thread-1690 ERROR fetchlets.wbem: Server reported error.
2004-01-01 19:09:53 Thread-1690 ERROR fetchlets.wbem: Server reported error.
2004-01-01 19:09:53 Thread-1690 ERROR engine: [host,dlsun454.us.oracle.com,ProjectResourceUsage] : meegd_GetMetricData failed : Server reported error.
2004-01-01 19:10:53 Thread-1714 ERROR fetchlets.wbem: No username specified for WBEM fetchlet.
2004-01-01 19:10:53 Thread-1714 ERROR engine:  [host,dlsun454.us.oracle.com,UserResourceUsage] : nmeegd_GetMetricData failed : No username specified for WBEM fetchlet.

 

3.9.0 Userblock Server-Generated Alert Has No Associated Data
Though the alerts are properly delivered for this type of server-generated alert, the metric details show no corresponding data trend (Bug 3054330)

 

3.10.0  Failure to Render Pages that Contain Real-time Metric Value

You may see errors such as: "An internal error has occurred" or "Error getting data for target {target-name}. Exception: null" when EM is trying to display a page that is showing real-time metrics for a target that was deleted and recreated. This may occur if you discover a target such as an application server, then remove it and rediscover it. If you see these errors, stop and restart the agent that is monitoring the target:

{agent-home}/bin/emctl stop agent
{agent-home}/bin/emctl start agent

(Bug 3381701)
 

4. Blackouts
4.1.0  Users Must Have Operator Privileges To Blackout Group
If a user creates a group and would later like to blackout the group, he should ask an Enterprise Manager superuser to grant him 'Operator' privileges on the group.  Operator privileges are required to blackout a group and by default, 'Operator' privileges for a group are not automatically granted to the creator of a group.

4.2.0 Blackouts With Immediate Start Times May Be Delayed
The start of an immediate, one-time blackout or the first occurrence of recurring blackout with an immediate start time may be postponed by up to 2 minutes.  The goal is to use the target's time as the blackout start time, and the target's time, in turn,  is determined based on its monitoring Agent's last heartbeat time to the Oracle Management Service (OMS).  The additional 2 minutes is added by the OMS to the Agent's heartbeat time in order to accommodate any network delays in receiving such heartbeat information.   This time is then used as the blackout start time.  This calculation was specifically designed to ensure the proper handling of potential metric severities pending from the Agent.  Since blackouts suspend monitoring,  severities that have a timestamp before the official blackout start time will be kept; otherwise, they will be discarded (Bug 3299198)

4.3.0 Agent Unreachable or Status Pending State
After a blackout on a target ends, Enterprise Manager re-evaluates the target status.  During this brief evaluation period, users may see the target in either 'Agent Unreachable' state (for host targets) or 'Status Pending' state (for non-host targets).    These states are temporary and will be resolved once the true status of the target is determined  (Bug 3317976)

4.4.0 Operator Privileges Required to Blackout a Target
An Enterprise Manager administrator needs at least Operator privileges on a target in order to blackout the target.   The Create Blackout UI will only display targets for which the current Enterprise Manager administrator has at least Operator privileges.  When creating a blackout, if no targets are available for selection, this means the administrator does not have Operator privileges on any target.  To resolve this, he should ask an Enterprise Manager super administrator (i.e. administrator with superuser privileges) to grant him Operator privileges on the targets that he wants to blackout.

4.5.0  Reason Field Required When Creating Blackout
When creating a blackout, a 'reason' for a blackout is a required field.  Only Enterprise Manager administrators with superuser privileges (aka super administrators) can create a 'reason' during blackout creation.   When creating a blackout, if the appropriate value for 'reason' is not available for selection, ask your Enterprise Manager super administrator to create the reason by creating a 'dummy' blackout that has the appropriate reason in it.   The dummy blackout can be, for example, a future blackout for any target.  As soon as the dummy blackout is created,  the reason has also been created.  At that point, he should STOP and DELETE the dummy blackout.   Make sure the dummy blackout DOES NOT ACTUALLY START and is DELETED because a blackout will stop monitoring the targets under blackout and will appear in that target's availability records.   (ER 3145500)

4.6.0 Daylight Savings Time Not Supported
Daylight savings time is not supported for blackouts.   Users need to manually adjust a blackout's schedule, as needed, to accommodate schedule changes due to daylight savings time.

4.7.0 Availability History
When a blackout is submitted and the Oracle Management Service is down for the entire duration of the blackout, and no severities come in for a target during the blackout window, the blackout window will be compressed to a one-second window in the availability history. Note that this does not cause any unnecessary notifications to be sent, since it only happens when no severities are generated for the target during the blackout. (Bug 3317965)

5. Jobs
5.1.0  Deleting job runs
If a user attempts to delete a job run wherein at least one execution in the job run is still active  (i.e. Scheduled, Running, or in Suspended status), then he may see this error message: “ The specified job, job run or execution is still active. It must finish running, or be stopped before it can be deleted. Filter on status 'Active' to see active executions.”.   'Active' refers to a combination of the following status values:  Scheduled, Running, or Suspended.   However,  ‘Active’ is not available as one of the search filter for the Status search field.  Hence to see all active job executions, you can perform separate searches on jobs where the Status is Scheduled, Running, or Suspended (Bug 3256113)

5.2.0  Host Command Against Groups
If a user submits a Host Command job against a Group of different target types, then the Host Command job will automatically run against the Host targets in the group.   In order to run the Host command against targets of a different type (e.g. databases), the user can choose those targets directly, or in the case of database targets,  choose a Database Group containing those databases (Bug 3241432)

5.3.0 RefreshFromMetalink Jobs
When querying jobs, if a user chooses the job type 'RefreshFromMetalink', then, for convenience,  Enterprise Manager automatically assumes the value of the Target Type filter is 'System' (regardless of what the user has selected for 'TargetType').    The RefreshFromMetalink jobs always have 'System' as their associated target type, and thus will only be found if the Target Type is set to 'System' (Bug 3230111)

5.4.0  CloneHome and Patch Jobs Are Not Supported In The Library
In the Job Library page, the 'CloneHome' and  'Patch' jobs are listed as job types for which library jobs can be created.  However, these job types cannot be saved to the library,  they can only be created and submitted as active jobs (Bug 3281143)

5.5.0  Credentials for Host Command Jobs Against Database Targets
A user's preferred credentials for a database target consist of  normal database credentials, privileged database credentials, and host credentials.  When creating a Host Command job against a database target,  the Create Job UI allows the user to select 'Normal' or 'Privileged'  preferred credentials.   Either option will result in using the same host credentials  -- these are the single host credentials that are part of the database target credentials (Bug3290724)

5.6.0  Single group target in Host Command/SQL Script jobs
When creating a Host Command or SQL Script job, if any type of group is selected as a target for the job, then no other targets can be added to the job.

5.7.0  Immediate, Repeating Jobs
When specifying the schedule for a job, if 'Immediately' is selected for the Start time, then any other repeat option specified will be ignored.  Hence, the job will become an immediate, one-time job.    If the user wants to create a job that runs immediately and also repeats at regular intervals,  then he should choose the 'Later' Start option, and specify a time a few minutes after the current time.  These additional minutes are required to accommodate the time needed to process and submit the job from the Oracle Management Service to the agents (Bug 3262332)

5.8.0  Editing Finished Jobs
When attempting to edit a job, a user might see this error message:  "No scheduled executions - this job cannot be modified".   This means that based on the job's schedule, Enterprise Manager has determined that there are no future job executions scheduled for this job.  Hence editing the parameters of the job does not make sense and thus will be prevented.  However, the access page of the job can always be modified by the job owner, even after the job finishes, in order to share job output with others.

5.9.0  Searching For Jobs Against Groups
If the user uses the 'Target Type' filter to search for jobs against groups, make sure the Target Type filter is set to one of the following:  'All Groups', 'Database Group', 'Group' or 'Host Group'.   Setting the filter to 'All Targets' will not work in this case because 'All Targets'  refers to individual non-group targets (Bug 3282349)

5.10.0  Skipped Executions
For recurring jobs, a future execution of a job is only scheduled when the current execution is completed. There may be cases wherein some job executions are skipped.  The most common causes are:
    a) the currently running execution is taking longer than expected, and continues to run during the time the next execution(s) is supposed to run    

     b) the current execution has been suspended by the user, and continues to be suspended during the time the next execution(s) is supposed to run

    c) the current execution has been suspended by the system (due to the agent becoming unreachable or the target of the job being under blackout), and continues to be suspended during the time the next execution(s) is supposed to run

When the current execution finally completes, the next job execution is scheduled.  The next scheduled execution is always a date in the future, hence any executions that were supposed to run in the past but were skipped will never be run.    The Enterprise Manager console will NOT display these skipped executions.  If some job executions seem to be missing from the jobs table in the console,  these are most likely due to the cases enumerated above.  (ER 3330400)

5.11.0  Unified Scheduler Jobs vs Enterprise Manager Jobs
Users have access to 2 types of job systems:  Unified Scheduler jobs and Enterprise Manager jobs.  The former are jobs that run inside the database; the latter are jobs that run outside the database using the Oracle Management Agent.   You can access the Unified Scheduler jobs using the 'Jobs' link under the Scheduler section in the database Administration page.    You can access the Enterprise Manager jobs from the Jobs primary tab in the console, or by using the 'Jobs' link under the Related Links section of any database page: Home page,  Performance, Administration, Maintenance.   Also, the Job Activity section in any target home page refers to Enterprise Manager job activity  (Bug 3312974)

5.12.0  Daylight Savings Time Not Supported
Daylight savings time is not supported for jobs.  Users need to manually adjust a job's schedule, as needed, to accommodate schedule changes due to daylight savings time. (Bug 3328590)

5.13.0 Preferred Credentials on Cluster Targets
Because of this bug, overridden preferred credentials do not work correctly with cluster targets for OSCommand and SQLScript jobs. If preferred credentials are set for the cluster, they will be used instead of the overridden credentials. The only workaround is to clear the preferred credentials for the cluster target when submitting jobs with overridden credentials. (Bug 3339631)

5.14.0 Secure Agents
We strongly recommend that all Grid Control agents be secured on install. Leaving unsecured agents in a deployment can cause problems especially if you run clone jobs across agents, and only one of the two agents is secured. . In such a scenario, the clone will always fail

 

6.  Database Management

6.1.0 Data Guard

6.1.1 Creating a Recovery Catalog for a Physical Standby Database
Backing up a physical standby database requires a recovery catalog. However, attempting to create a recovery catalog for a physical standby database will result in the following error: RMAN-08040: full resync skipped, controlfile is not current or backup.  The workaround is to switch over to the standby database, configure the recovery catalog, and then switch back. (Bug 3298797)

6.1.2 Metric Collection Errors in Standby Databases
After switching a primary database to a standby database you may notice a few metric collection errors for the new standby database. These errors can be ignored. The workaround to clear the metric collection errors is to briefly open the database in read-only mode. (Bug 3312518)

6.1.3 Data Guard: Upgrading Protection Mode Causes Exception With a RAC Database
When upgrading the protection mode in a Data Guard configuration that has a RAC database, connecting to the RAC database at the end of a successful protection mode upgrade may throw an exception. The workaround is to log out of the database and log back in again from Enterprise Manager. (Bug 3345796)

6.1.4 Logical Standby Database Unable to Obtain Log Containing Dictionary from RAC Primary System
After creation of a logical standby system from a RAC primary database, the standby may occasionally be unable to obtain the log files from the primary RAC system. ORA-27063 alerts may be encountered. Use the following
workaround:

a)  Locate the particular log file from the primary alert log file that has the FAL archival problem.

b) Determine the thread number and sequence number of this log file.

c) Locate the local archived copy of this log on the primary archived directory (It can be your recovery area or your log_archive_dest_1 area).

d) Copy the file to the logical standby and use the ALTER DATABASE REGISTER LOGFILE command to register the log file to the logical standby.

 If your logical apply engine is already started, it should find the file soon and be able to continue to start the apply. If not, then start the apply using ALTER DATABASE START LOGICAL STANDBY APPLY command (Bug 3347273)

6.1.5 Using Primary Database as Recovery Area for Locally-Archived Logs
If your primary database is using a recovery area for locally-archived logs, ensure that the log_archive_dest_10 parameter is set to the following prior to creating a physical or logical standby database:

log_archive_dest_10='location=use_db_recovery_file_dest','valid_for=(ONLINE_LOGFILE, ALL_ROLES)'

If this parameter is not set on a primary database that uses a recovery area prior to switching over to a logical standby
database, online logfile archival will fail with an ORA-16104 after the database is activated as a logical standby. If you neglect to set this parameter prior to switchover and see this problem, it can be fixed by setting the above parameter on the logical standby database. (Bug 3349731)

6.1.6 ORA-16627 After Upgrading Data Guard Broker to Max Protection
Upgrading to Max Protection from the default Arch mode without standby redo logs may result in an ORA-16627 error. This is due to a temporary gap in the log stream. The workaround is to retry the operation.

6.1.7  Data Guard Pages Remember First Browser Locale
The Data Guard pages always display in the language that corresponds to the preferred locale of the browser that was used to view the pages the first time. In subsequent visits to the Data Guard pages the browser locale is ignored. The workaround to unset this preference is to bounce the Oracle Management Service and visit the Data Guard pages with the appropriate browser locale setting. (Bug 3342523)

6.1.8 Creating A Standby Database For A Cluster Database (RAC) Primary Database
When creating standby databases for cluster database (RAC) primary databases in Enterprise Manager you must follow all the configuration steps described in Section 2.2 ("Setting Up the Broker Configuration Files") of the Data Guard Broker book in the Oracle Database 10g documentation.

6.1.9 Physical Apply Service Unexpectedly Offline (ORA-16766)

The Data Guard broker RSM0 background process will crash if the DB_DOMAIN initialization parameter is not set. When this occurs, the following error will occur while using the Data Guard GUI or CLI:

 

ORA-16766: Physical apply service unexpectedly offline

 

Workaround: Set the DB_DOMAIN initialization parameter to the null value.

 

For example:

 

SQL> ALTER SYSTEM SET DB_DOMAIN='' SCOPE=SPFILE;

 

This will require the database to be restarted. If DB_DOMAIN is not set on the primary database, set the parameter value on the primary as well, but the restart may be deferred until a role change operation. After doing so, re-enable the database using either the Data Guard CLI or GUI.

 

For example:

 

DGMGRL> ENABLE DATABASE <db_unique_name>;

Enabled.

 

Note: If you are using the Data Guard GUI, click the Reset button on the database General properties page to re-enable the database.

 

If you set the DB_DOMAIN initialization parameter to a non-null value, you must remove the database and add it back into the configuration.

 

For example:

 

DGMGRL> REMOVE DATABASE <db_unique_name>

Removed database "<db_unique_name>" from the configuration.

 

DGMGRL> ADD DATABASE '<db_unique_name>' AS CONNECT IDENTIFIER IS '<connect_identifier>' MAINTAINED AS PHYSICAL;

 

Database "<db_unique_name>" added.

 

Note: If you are using the Data Guard GUI, the Add Standby Database wizard can be used to add the database back into the configuration. (Bug 3389628) 

6.2 Reorganize Objects

6.2.1 The database can be adversely affected if metadata changes occur between the time the reorganization script is generated and the time it is executed.

6.2.2 The database can be adversely affected if an offline reorganization is attempted while DDL is in progress against the tables being reorganized.       

6.2.3 Before using the Reorganize Objects wizard or the Make Tablespace Locally Managed wizard Oracle recommends that you ensure you have a very recent backup of your database.   

6.2.4 For 10g database targets only, attempting to do an online reorganization of  the outer join table of a bitmap join index will fail. Use the offline method for reorganizing such a table or reorganizing a tablespace containing such a table (Bug 3330361)   

6.2.5 For 10g database targets only, attempting to do an online reorganization of a tablespace that contains an index-organized table overflow segment partition will fail when the "tablespace rename" option is used for the Scratch Tablespace.  Use the offline method for reorganizing such a tablespace, or specify a scratch tablespace instead of using the tablespace rename option (Bug 3334289)

6.2.6 Error in Impact Report
When reorganizing a tablespace in a 10G database, you may encounter the following error message in the Impact Report:

This tablespace contains recycle-bin segments from tables that have been dropped. It cannot be reorganized. Use the PURGE TABLESPACE command to remove the recycle-bin segments from the tablespace and re-try the reorganization.

The PURGE TABLESPACE command only removes recycle-bin segments belonging to the currently connected user. Therefore, it may not remove all the recycle-bin segments in the tablespace. You can determine which users have recycle-bin segments in a target tablespace using the following query:

SELECT DISTINCT owner FROM dba_recyclebin WHERE ts_name = 'TARGET_TS';

You can then use the following command to purge the segments for each of the users:

PURGE TABLESPACE target_ts USER scott;

An alternative is to use the following command:

PURGE DBA_RECYCLEBIN;

This can be used only if you have SYSDBA system privilege. It removes all objects from the recycle bin, regardless of user.

6.3.0 Net Services Administration
For 'Directory Naming' feature to work, a valid ldap.ora file must exist in the 'Configuration File Location' selected by the user in the 'Net Services Administration' page. The ldap.ora file should be created using NetCA.

6.4.0 Shutting Down the Database
Shutting down a database in normal mode does not work in Enterprise Manager. However, a database can be shut down in transactional, immediate and abort modes with Enterprise Manager. Use SQL*Plus to shut down a database in normal mode. (Bug 3239095)

6.5.0 Running SQL Access Advisor With Materialized View Recommendation May Cause Library Cache Deadlock
A deadlock on the library cache may happen when a select statement is evaluated for rewrite at the same time as a create materialized view statement requests exclusive locks on its base tables. This could happen when a SQL Access Advisor is running to generate materialized view recommendations while another user issues a select statement at the same time that references the same base tables.  The workaround is to stop the SQL Access Advisor job and the deadlock will be released. (RDBMS bug 3230878, 2018081, 2124800)

6.6.0 Default Database Credentials May Not Be Used for Cluster Databases
Default database credentials will not be picked up for cluster databases unless at least one cluster database was already discovered at the time when the default credentials were set. The workaround for this problem is to delete and reset the default database credentials. (Bug 3312344)

6.7.0 Launch iSQL*Plus Requires Configuration
For Grid Control, the iSQL*Plus server is not shipped with the OMS (Oracle Management Services). Therefore iSQL*Plus needs to be manually configured to point to any running Oracle Database 10g iSQL *Plus server. All the target databases discovered in this Grid Control application will then use this iSQL*Plus server for their queries.

To configure iSQL*Plus, two entries in the $ORACLE_HOME/sysman/config/emoms.properties file on the OMS (Oracle Management Server) machine needs to be populated by replacing the following placeholders: replace %ISQLPLUS_PROTOCOL%, %ISQLPLUS_HOST% and %ISQLPLUS_PORT% with the protocol, the host and the port of the iSQL*Plus server you want to use.

For example:
    oracle.sysman.db.isqlplusUrl=http://rooster.au.oracle.com:8888/isqlplus/dynamic
    oracle.sysman.db.isqlplusWebDBAUrl=http://rooster.au.oracle.com:8888/isqlplus/dba/dynamic

For RAC applications, the emoms.properties file for all nodes of the cluster must also have these two entries configured. After configuring the entries, the OMS needs to be restarted to pick up the change.

6.8.0 10g RAC Database Recovery in Archivelog Mode
When a 10g cluster database is in archivelog mode, in order to perform a restore and recovery of the entire database, the user should only leave one RAC instance up and shut down all other RAC instances. Affected areas include whole database complete/point-in-time/flashback recovery (Bug 3334212)

6.9.0  Editing Objects
Enterprise Manager only supports having one browser window open for editing an object. For example, Enterprise Manager only supports editing one tablespace at a time.  Note, if a window is read only, you may have multiple browser windows open.

6.10.0 Target Names For Oracle Suggested Backup Strategy
When Oracle's Suggested Backup Strategy is to be used for offline backups, the target name should be less than 52 characters in length (Bug 3347338)

6.11.0 NullPointerException When Drilling on Top Object
If you see a NullPointerException when drilling down on an object under the Top Objects tab, and the URL ends in %20PARTITIon, try removing %20PARTITION from the URL, and the link should work (Bug 3350008)

6.12.0 Recovery Area Free Space Metric Graph is Inverted
The alert for the recovery area free space metric fires under the correct conditions (when free space is low), but clicking on the chart
of data associated with this alert displays space used, not space free. The correct value for free space at any point in time is 100%
minus the displayed value. (Bug 3375524)

 

6.13.0 Cluster Database Agent in Unknown or Unreachable State After Enabling Security

If you enabled security for a cluster database agent during the installation of the agent, or later via the emctl command, the following problems may occur: the agent remains in an unknown or unreachable state, and the cluster target availability does not get updated beyond that point.  (Bug 3370009)

 

The following workaround may be used to resolve the problems.

a)  Start SQL*Plus and log in as SYSMAN.
b)  Copy and paste the PL/SQL block below into the SQL*Plus window.

-- Script to fix corrupted agent state after an agent is secured--

set serveroutput on size 100000 FORMAT WRAPPED
DECLARE
   l_agent_url  VARCHAR2(256);  
BEGIN

   FOR clust_rec IN (SELECT target_guid, emd_url
                       FROM mgmt_targets
                      WHERE target_type = 'cluster'
                        AND emd_url NOT IN
                        (SELECT emd_url FROM mgmt_targets
                          WHERE target_type = 'oracle_emd') )
   LOOP

     l_agent_url := replace(clust_rec.emd_url, 'http:', 'https:');

     INSERT INTO mgmt_change_agent_url
       VALUES(clust_rec.emd_url, l_agent_url);

     UPDATE mgmt_targets
        SET emd_url = l_agent_url
      WHERE target_guid = clust_rec.target_guid;

     DELETE FROM mgmt_change_agent_url;
     COMMIT;

     dbms_output.put_line('Agent state corrected. ');
     dbms_output.put_line('Please restart the agent on ' || clust_rec.emd_url);

   END LOOP;

EXCEPTION
  WHEN OTHERS THEN
     dbms_output.put_line('Did not find any agents in corrupted state');
END;
/

 

c) Restart the agent by running "emctl stop agent" and "emctl start agent" commands.

 

6.14.0 Viewing of SQL Execution Plan in Korean

There is a known bug where viewing an execution plan of a Period SQL causes an internal server error.  This is a bug that is unique to Korean and does not reproduce in Japanese or Chinese.  The only workaround currently available is to run the product in a non-Korean language when you need to view this page. (Bug 3380531)

 

6.15.0  Garbled Characters Shown in "PGA Memory Usage Details" Page
The "PGA Memory Usage Details" page under Administration -> Instance:Memory Parameters -> PGA will show garbled characters when the product is run in a multi-byte (Asian) language environment.  The only workaround currently available is to run the product in a single-byte Western European language when you need to view this page. (Bug 3272773)

7.  Configuration Management Pack
7.1.0 Oracle Targets Missing From Deployments Summary Rollup Tables
 If Oracle software was not installed using the Oracle Universal Installer or was not cloned using Enterprise Manager, the software will not show up in Deployments Summary rollup tables. This is due to the fact that data is collected from the Oracle Universal Installer inventory. Software not installed via Oracle Universal Installer will not have an entry in the inventory, and as a result cannot be displayed in rollup tables.

7.2.0 Cloning Support For Legacy Deployments Not Available At Release Time For All Platforms
 Cloning for legacy software deployments on certain platforms may not be immediately available at the time of
release. The Cloning wizard will detect this and point you to the appropriate web site to go check for the availability of an update.

7.3.0 Agent Patching On RAC Is Not Supported
Patching of the Enterprise Manager Agent in a RAC setup is not currently supported, use the command line utilities instead.

7.4.0 Patch Number Inconsistencies
On the Patch: Select Patch page, you can specify a MetaLink patch number to locate a patch published at the
OracleMetaLink web site. For some interim patches, a second patch number is used that is unique to the platform. In such cases, this number will appear in the readme as the interim patch number, e.g.: "Interim Patch:3243133 Base Bug:3239222". This is the number that is returned as part of enterprise configuration searches and is the number that will appear on the Oracle Home page. (Bug 3320868)

7.5.0 Cloning Of Oracle Home Fails If A 9.2 Agent Is Running
If a 9.2 Enterprise Manager Agent is running on a host, cloning operations will fail. You must stop the Enterprise
Manager 9.2 Agent before performing any clone operation for it to succeed. (Bug 3164441)

7.6.0 Oracle Home Link In Critical Patch Advisory Page Is Broken If The Name Contains An Underscore
 The Critical Patch Advisory page entitled: "Policy Rule: Critical Patch Advisories for Oracle Homes" will have
broken Oracle Home links in it's table, for any Oracle Homes that contain underscores ("_") in their name (Bug
3324506)

7.7.0 MetaLink Password Change May Have Delayed Propagation
 Password changes performed on the MetaLink site may have a slight propagation delay that affects Enterprise
Manager. If you get MetaLink credential errors in Enterprise Manager shortly after having changed your password on MetaLink, simply wait a while and retry later (Bugs 3319786, 3265575)

7.8.0 Deployments Summary Table Shows Database Targets That Aren't Directly Visible In The "Oracle Home" Page
 The Deployments Summary table shows all database targets, whether they are standalone or part of another Oracle product, but if you drill down on a database target that is part of another Oracle product, and from there drill down into the "Oracle Home" page, you won't see the database component as part of that home, as it's in fact a subcomponent of another Oracle product. (Bug 3336562)

7.9.0 Database Patches Prior To 9.2.0.5 And 10g May Have Bugs Fixed Inconsistencies
 Database patches prior to versions 9.2.0.5 and 10g may have inconsistencies with regards to the bugs fixed list, both within the readme and the metadata written by the patch itself.. Enterprise Manager uses the information written by the patch.

7.10.0 Patch Version Information Not Available In Enterprise Manager
 Enterprise Manager does not currently have patch version information in it's repository. Oracle may re-release a
patch without updating the identification number used by Enterprise Manager, and thus it will not be possible to
discern the old from the new.

 7.11.0 Critical Patch Advisory Message Incorrectly Uses Term Patchset Instead of Version
 When listing all possible patches that can be used to address a Critical Patch Advisory, Enterprise Manager sometimes lists a patch and the version number to which the patch applies, for instance Alert 46 can be fixed with an interim patch for 9201 or an interim patch for 9202. In some cases, the phrase “(Requires patchset x.y.z.a)” is included to make clear which version of the patch is being referred to. This may lead to confusion when the patch is for the initial release of the product, e.g. you may see “Requires patchset 9.2.0.1”. In such cases, there is no patchset – it simply refers to the patch for version 9.2.0.1. (Bug 3347848)

7.12.0 Availability of Critical Patch Advisories
 At the time of this release, Critical Patch Advisories are being provided for the Oracle database server (versions 9.2 and higher) and for iAS (versions 9.0.4 and higher). Advisories for other products may be added at any time. The following Operating System platforms are currently supported:

AIX5L Based Systems (64-bit)
HP Tru64 UNIX
HP-UX Itaninum -- HP-UX PA-RISC (64-bit)
IBM zSeries Based Linux
Linux Itaninum
Linux x86
Microsoft Windows (32-bit)
Microsoft Windows (64-bit)
Solaris Operating System (SPARC 32-bit)
Solaris Operating System (SPARC 64-bit) . (Visible as 32 bit as the Critical Patch Advisory does not currently does not distinguish between 32 bit and 64 bit Oracle Homes)
Solaris Operating System (x86)

(Bug 3368719)

7.13.0 Non-Oracle Database 10g Home Clonerstage Availability
 For Oracle Database homes prior to 10g, as well as Oracle Application Server homes 9.0.4, Enterprise Manager requires a clonerstage to perform home cloning operations, as this functionality wasn't present in the Oracle Universal Installer for products shipped prior to Oracle Database 10g. Only a limited amount of clonerstages are shipped with the product, and thus when you attempt to clone a home for which a clonerstage isn't currently available within your Oracle Management Service, you'll be presented with a page telling you so and pointing you to the appropriate location to download that clonerstage.

7.14.0 Home Cloning for Homes Requiring Clonerstages Absolute Path Issues When using Multiple Oracle Management Services
 If you have multiple Oracle Management Services within your Grid Control setup and you attempt to perform a home cloning operation on a legacy home that requires a clonerstage, the path to that clonerstage is an absolute one, and thus if the job runs on a different Oracle Management Service than the one that submitted the job and if the path on both Oracle Management Services is different, the job will fail. To avoid this problem, either use consistent paths on your multiple Oracle Management Services or as an alternative for non-Windows platforms, simply create appropriate symbolic links so that all path combinations are valid on all Oracle Management Services. (Bug 3349916)

7.15.0 Installing Home In Pre-Existing Path Prevents Later Home Cloning
 If you install Oracle Database 10g in a path that already exists, a clone home operation on that home at a later time will fail. To avoid this, simply ensure that the path you're installing in (ORACLE_HOME) doesn't already exist, letting the installer take care of creating it for you. If you do install into a pre-existing directory, you may see a later error from the home cloning wizard, that mentions the install.platform file could not be read.  To work around this problem, copy the install.platform file from the central OUI inventory directory into the home you are attempting to clone.(Bug 3235500)

7.16.0 Cloning Job File Transfer May Fail Without Appropriately Returning An Error
In certain cases (for instance lack of disk space), a cloning job's file transfer step may fail without returning an appropriate error indicating the fact. The job should eventually fail when the subsequent steps attempt to access the files that weren't successfully transferred, but the error message returned may not clearly indicate the true cause of the failure. (Bug 3313196)

 

7.17.0 Job Failure when Cloning Homes

The CloneHome job may fail during the updateBuiltInClonable step. If this happens, stop and restart the agent on the node you are cloning.  (Bug 3400612)

 

7.18.0 Content of Search Results Saved To Local .csv File Are Unreadable

The list of Oracle Products Installed in Oracle Homes can be stored to a local .csv file.  This feature can be found under Deployment-> Search -> "Oracle Products Installed in Oracle Homes"-> "Save to File".  The content of this file is stored using the UTF-8 character set, which may not be recognized by some desktop applications.  If you find garbled characters in this file, try opening it with an application that can handle the UTF-8 character set, such as most web browsers. (Bug 3184524)

 

7.19.0 Files to Exclude When Cloning an Oracle Home

If you clone an Oracle Database 10g home, you should exclude some additional files from being copied to the new home.  To do this, add the following to the home cloning wizard's "Files to Exclude" list:
, listener.ora, tnsnames.ora, sqlnet.ora

If these files have already been copied during home cloning, delete them from the new home before running the DB Clone utility. (Bug 3394291)

 

8.  Application Server Management 
8.1.0  Using Application Server Control to Administer the Management Service's Application Server
If you plan to use Oracle Enterprise Manager 10g Application Server Control bundled with the Application Server 10g instance that the Management Service relies upon, then refer to the Oracle Application Server 10g Release Notes for differences between the delivered Application Server Control Release 9.0.4.0.0 product and its documented functionality.  The Application Server Release Notes are located on the Oracle Technology Network (OTN) at http://otn.oracle.com/docs/products/ias/content.hmtl.  Refer to the section labeled "Oracle Enterprise Manager".

8.2.0  Disabling Application Server Components
After disabling an application server component from Application Server Control, you will still continue to see that disabled component from Grid Control. Grid Control will display the component's last known state, eg. Up or Down. To remove the disabled component from Grid Control, go to the All Targets subtab, select the component, and click the Remove button. Note:  when you remove this component, all historical data for the component will also be deleted and will not be available if you subsequently enable the component.

8.3.0  Charts Not Displaying Data for Past 24 Hours
Charts displaying data for the past 24 hours from the Grid Control user interface, will not display data for the full 24 hour time period if the Management Agent is in a different timezone from the Management Repository.  (Bug 3243165)

8.4.0  Agents monitoring an Oracle Application Server Instance
 Agents monitoring Oracle Application Servers may experience memory growth based on the usage patterns of the monitored Oracle Application Server targets. Specifically, we have seen a significant impact due to applications using JDBC and caching connections and statements.

The growth in the agent virtual memory is bounded by the size of the JVM within the agent. By default this is set to 64M. Based on the behavior of the monitored applications, the number of these within a monitored Oracle Application Server, and the number of Oracle Application Servers, it is possible that this limit will be reached.

When this happens, several of the Oracle Application Server metrics may start failing with java.lang.OutOfMemoryError errors.  If this happens, the limit on the size of the JVM can be increased by adding a -Xmx option to the agentJavaDefines property in the $AGENT_ORACLE_HOME/sysman/config/emd.properties file.

Originally, 
agentJavaDefines=-Doracle.dms.refresh.wait.time=1000 -DUrlTiming.UseJSSE=true
 

To set the JVM size to 128M:

agentJavaDefines=-Doracle.dms.refresh.wait.time=1000 -DUrlTiming.UseJSSE=true -Xmx128M
 

8.5.0  Incorrect Value For Forms Targets
 When viewing a Forms target's metrics from the All Metrics Page, the value for Total Memory will be displayed as zero or a very small number.  This value is incorrect.  The correct value can be viewed on the User Sessions tab of the Forms homepage in the Application Server Control. (Bug 3334946)

8.6.0 Errors During Discovering or Deleting an Application Server Target
If any errors occur while discovering or deleting an application server target, you will likely need to perform the following manual clean up steps:

a) Delete the file centralagents.lst from the Application Server home. This file is located in <AppServerHome>/sysman/emd.

b)  Delete any remaining targets from Grid Control. To do this, go to the appropriate Host homepage in Grid Control. Select the targets that need to be deleted and click Remove.

(Bugs 3343940, 3294659, 3279776)

8.7.0 Discovering Application Server 10g v9.0.4 Instances
If you encounter errors when discovering Application Server 10g v9.0.4 instances, you likely need to apply a patch to each application server home. Check metalink for patch availability. (Bugs 3343940, 3294659, 3356160)

8.8.0 Creating OC4J's in a 9.0.2/9.0.3 Application Server Instance
When you create a new OC4J in an Application Server instance, that new OC4J will not automatically be displayed in Grid Control. For Grid Control to recognize this new OC4J, you need to delete the Application Server target in Grid Control and re-discover it. Note that when you delete the Application Server target, all historical data for the Application Server and all of the targets that it contains will also be deleted and will not be available once you rediscover the Application Server.  (bugs 3256873, 3351200)

8.9.0  Deleting OC4J's in an Application Server Instance
When you delete an OC4J from an Application Server instance, that OC4J will still be displayed in Grid  Control. You must also delete the specific OC4J from Grid Control. (Bugs 3355848)

8.10.0 Discovering Standalone Webcache Installations
The Enterprise Manager Central Agent does not discover standalone Webcache installations.  In order to configure the central agent to monitor these instances, you must perform the following steps in the Central Agent home:

a) setenv OH ${PWD}   (in Central Agent home root directory)

b) Based on OS type, set the PERL5LIB environment variable accordingly

(Line wraps added for readability):

 

Solaris:

  setenv PERL5LIB

$OH/perl/lib/5.6.1/sun4-solaris:$OH/perl/lib/5.6.1:$OH/perl/lib/5.6.1/File:

$OH/perl/lib/site_perl/5.6.1/sun4-solaris:$OH/perl/lib/site_perl/5.6.1:$OH/perl/lib/site_perl:

$OH/perl/lib/5.6.1/sun4-solaris/auto/POSIX:$OH/sysman/admin/scripts:$OH/bin 

            HP-UX:

  setenv PERL5LIB

$OH/perl/lib/5.6.1/PA-RISC2.0:$OH/perl/lib/5.6.1:$OH/perl/lib/site_perl/5.6.1/PA-RISC2.0: 

$OH/perl/lib/site_perl/5.6.1:$OH/perl/lib/site_perl:$OH/perl/lib/5.6.1/PA-RISC2.0/auto/POSIX:

   $OH/sysman/admin/scripts:$OH/bin

Linux:

  setenv PERL5LIB

$OH/perl/lib/5.6.1/i686-linux:$OH/perl/lib/5.6.1:$OH/perl/lib/site_perl/5.6.1/i686-linux: 

$OH/perl/lib/site_perl/5.6.1:$OH/perl/lib/site_perl:$OH/perl/lib/5.6.1/i686-linux/auto/POSIX:

   $OH/sysman/admin/scripts:$OH/bin

OSF-1:

  setenv PERL5LIB

$OH/perl/lib/5.6.1/alpha-dec_osf:$OH/perl/lib/5.6.1:$OH/perl/lib/site_perl/5.6.1/alpha-dec_osf:

$OH/perl/lib/site_perl/5.6.1:$OH/perl/lib/site_perl:$OH/sysman/admin/scripts:$OH/bin

 
AIX:

  setenv PERL5LIB

$OH/perl/lib/aix:$OH/perl/lib/5.6.1:$OH/perl/lib/site_perl/5.6.1/aix: 

$OH/perl/lib/site_perl/5.6.1:$OH/perl/lib/site_perl:$OH/sysman/admin/scripts:$OH/bin

 

c) Run these two commands; this will gather information about standalone

Webcache installs and add them to the central agent's list of managed targets: 

$OH/perl/bin/perl $OH/sysman/admin/discover/oracle_webcache.pl $OH

`hostname`  > ./target.outwebcache

$OH/bin/emctl config agent addtarget ./target.outwebcache
 

d) reload the agent:  ./emctl reload

8.11.0 Metric Collection Error in Workflow Response Metric
The collection of Workflow's Response metric will result in a metric collection error of  "ORA-01017: invalid username/password; logon denied (DBD ERROR: OCISessionBegin)".  In order to use Workflow's Response metric, you will need to download and install a patch for this issue.  In the meantime, you can remove the Workflow target and still see its status by viewing the status of the database target in which Workflow is installed. (Bug 3382082)

8.12.0 Incorrect Metric Values for Reports Targets
The Trace File and Roll Up metrics that are available on the All Metrics page for a Reports target have incorrect
values and should be ignored as the metrics were pertinent for only pre-9.0.4 Reports targets. Bugs 3334355 and 3355631)

8.13.0 Start Time Label
The "Since (Start Time)" column of the Server Information metric that is available on the All Metrics page for a Reports target should be labeled "Start Time (ms since epoch)", which is consistent with all other target types. (Bug 3334182)

9.  Application Performance Management

9.1.0 Reflecting Server Downtime in Response Time Charts
Currently there is no way to reflect server downtime in a response time chart. Because of this behavior, the response time chart will never show you any down time. You should not rely on this chart to find out down times. (Bug 2053646)

9.2.0 Transaction Response Time Chart Updates
When Web Cache is allowed to cache images, the Transaction Response Time chart will only update intermittently (Bug 2460691) Web Cache must be configured to disallow image caching for Enterprise Manager. The following rule must be applied to Web Cache:
---------------------------
This rule must be global, and must supersede (be above / have a smaller number than) the png rule (i.e. : "\.(bmp|png)$" ).
URL Expression: \/em\/dynamicImage\/emSDK\/chart\/EmChartBean
Method: GET, GET with query string, POST
POST Body Expression: .*
Don't Cache
---------------------------
If in doubt on where to put this rule, make this the lowest number global rule.

9.3.0 Serving Frames Based Web Applications
End-User Monitoring should be disabled for frame page URIs (i.e. pages that are members of a frameset) in both of the following cases. (Bug 2413777)

9.3.1 The frameset page itself (i.e. the page containing the <FRAMESET> tag) is served by a different web server, whether or not the frameset page is enabled for end user Monitoring.  If End-User Monitoring is not disabled in this case, users of the monitored web application will see a Javascript security exception.
 

9.3.2 The frameset contains frame pages which are not all enabled for end-user monitoring; for example, if some frame pages are served from a different web server.  If End-User Monitoring is not disabled in this case, end-user timing data for the frameset page will be inaccurate.

End-User Monitoring can be disabled or enabled for specific URIs in Oracle Web Cache version 9.0.4 and later by using the End-User Performance Monitoring section of the Web Cache Manager.
 

9.4.0 Use of Pop up Pages When Recording Transactions
The Enterprise Manager Application Performance Monitoring tool set does not support pop-up pages when recording a transaction. Any activity in pop-up pages is not  recorded.

9.5.0 Portal Error
When using Portal, if the Portal application accesses a separate Web Application that is being monitored with APM End-User Monitoring tools, you will see an error when the Portal application tries to access the monitored application (Bug 2528239)

9.6.0 Support for Session Based Parameters
The Enterprise Manager APM recorder does not support URLs with session-based parameters. (Bug 2682893)

9.7.0 Internet Access and Recorder Installation
When installing the recorder in the client machine (i.e. downloading it for the first time), the browser checks that all required Microsoft libraries are already installed. Any missing libraries are downloaded directly from Microsoft. The client machine must have access to the internet when installing the recorder.

9.8.0 Disable Pop-Up Blocking Utilities
The Enterprise Manager Application Performance Monitoring downloads a recording control to the local computer. Utilities that block pop-up windows may disable the control and prevent transaction recording and playback to function properly.

9.9.0 Configuring End-User Performance Monitoring for a Web Application
The following steps are necessary to enable End-User Performance Monitoring for a Web Application.

1) Create a Web Application target and add as components any Web Caches that host that web application. [The "Enterprise Manager Website" Web Application target is already created for you as part of the installation process].

2) Enable Chronos instrumentation on every Web Cache that hosts a monitored Web Application. Using the Web Cache administrative interface:

a) Set access logging format to WCLF
b) Enable End-User Monitoring for each site and for the entire cache.

3) In order to see End-User Performance data appear on the console sooner, reduce the minimum-hits filter to 1:

Execute the following SQL on the Enterprise Manager repository:
update mgmt_parameters set parameter_value = 1 where parameter_name = 'mgmt_rt_min_hits';

After end-user data is collected and a reasonable amount of traffic has been generated, this value can be set back to its default (10).
 

9.10.0 Web Cache Target Names Should Not Contain "/"
The name of a Web Cache target that is enabled for End-User Performance Monitoring should not contain a slash ('/'). A metric collection error of the form:
"Fatal error: Fatal Error in Stage PROCESSCOMMANDLINEINPUT: Error: Failed To Open Output Lock File...." will be seen if there is a slash in the Web Cache target name.

9.11.0 Configuration of Web Cache Site Name and/or Alias
For all sites enabled for End-User Monitoring, ensure that all possible hostnames (and possibly the associated port numbers) used to access the site (e.g. example.com, www.example.com, www (for internal access)) are specified either in the Host Name and Port specification of the site, or as one of the Aliases of the site. If the site is accessed using a hostname/port that is specified as described, such accesses will not be instrumented for End-User Monitoring.

9.12.0 End-User Performance Monitoring Requires Website Logging to Default Access Log File
End-User Response Time monitoring will only function for websites that are configured to log data into the default access log file. A default access log file is configured in the Site-Specific Access Log Configuration section of the Web Cache Manager. This also implies that in order to maintain URL namespace separation between websites, only one website per Web Cache should be configured for End-User Performance monitoring. (Bug 3257131)

9.13.0 Treatment of Web Caches and OC4Js That Are Members of an Oracle Application Server Target
If an Oracle Application Server target is added as a component of a Web Application, all subcomponents of the Application Server (including all the OC4J's and Web Caches) are automatically included in the 'Components' page of the Web Application. However:

1) All the Application Server's OC4Js will NOT automatically appear in the 'Configure Web Application OC4Js' page unless the specific OC4Js are explicitly added to the Web Application.

2) The Middle Tier Performance data for a Web Application will display data from all OC4Js (from the same Application Server) that have been configured for ANY Web Application target.

3) The Web Caches will NOT automatically appear in the 'Configure Web Application Web Caches' page unless the specific Web Caches are explicitly added to the Web Application.

4) Web Caches need to be explicitly added to the Web Application and specifically configured in order to view End-User Response Time data on the Page Performance Page.(Bug 3336996)

9.14.0 Inconsistent Time Zone Used for Web Application Page Performance Data
The End-User Response Time and Middle Tier Performance data uses the time zones of the Web Cache and OC4J target respectively, and not the Web Application's time zone. As a result, the End-User Response Time and Middle Tier Performance data may not be processed and displayed using a consistent time zone. (Bug 3323378)

9.15.0 Error Occurs When A Large Number of Components Are Added to a Web Application
If there are approximately over 30 components added to a Web Application target, this will result in an Internal Error on the 'Components' page. (Bug 3298071)

9.16.0 Transactions Do Not Play at the Same Frequency As Expected
As the Enterprise Manager agent tries to bucket collections with the same frequency, it is possible that a particularly slow or timed out transaction may cause other transaction collections to suffer. (Bug 3183810)

9.17.0 Missing Schema and Connection String
Middle Tier Performance data may be missing the schema and connection string from certain connection trees. (Bug 2837122)

9.18.0 Agent Privileges Must Be Assigned in Order to Create / Modify Transactions for Beacon
If a user is to be allowed to modify a Web Application by adding/removing beacons or modifying its transactions, then this user must be granted at least the 'View' privilege on all beacons and agents whose beacons are used in the Web Application. The workaround is to create a role that has 'View' privilege on all beacons and agents whose beacons are used in the Web Application, and then assign this role to all administrators for this Web Application. (Bugs 3346241, 3347678)


9.19.0 Error on JDBC Time for Processing Time Breakdown
Clicking on the JDBC Time on the Processing Time Breakdown section of the URL Performance in OC4J page may result in a 500 Internal Server Error. This problem may occur if a URL exists for which the number of processing components exceeds the maxRows limit (see oracle.sysman.emSDK.eml.maxRows in emoms.properties). In this situation it is possible that a connection component could be loaded and then because the limit is reached, no SQL children will be loaded for the connection. The workaround for this is to increase the maxRows limit and restart the OMS. Note that this workaround will cause additional rows to be loaded in any place within Enterprise Manager to honor this limit (the number of target rows Enterprise Manager loads) and as more rows are loaded, additional memory is consumed by the OMS. (Bug 3323075)

9.20.0  Playback and Playback with Trace
In browsers running in French locale, playback and playback with trace will not work.  The workaround is to set the browser to run in the English locale to use these features (Bug 3383621).
 

10.  Oracle Collaboration Suite
10.1.0 Autodiscovery of Oracle Collaboration Suite Targets
No autodiscovery is available for Grid Control monitoring of Oracle Collaboration Suite targets. In order to use Grid Control with Oracle Collaboration  Suite, you must perform some manual configuration steps.

Consult the Oracle Enterprise Manager documentation at http://otn.oracle.com for information about how to configure Grid Control for Oracle Collaboration Suite.

10.2.0 Wireless Not Supported in this Release
In this release of Enterprise Manager 10g the Wireless component of Collaboration Suite is not supported.

10.3.0 Owner of Management Agent on Calendar Hosts
When installing the Oracle Management Agent on a host that is running Calendar, you must install the agent as the same OS user as the user who installed Calendar. If the users are different the agent will be unable to monitor Calendar. (Bug 3146883)

11.  EM2Go
11.1.0 Supported Hosts
EM2Go supports administration of Host & Database targets, and monitoring of all other targets.

11.2.0  Using EM2Go in a Firewall Environment
If you are using EM2Go in a firewall environment, refer to "Configuring Enterprise Manager for Firewalls" in Oracle Enterprise Manager Advanced Configuration for information about accessing Oracle Enterprise Manager 10g Grid Control through a firewall.

11.3.0 TopSQL Functionality Does Not Work
With this release of Enterprise Manager Grid Control, TopSQL functionality does not work in EM2Go.

12. Enterprise Manager 9i to 10.1 Migration
12.1.0  Migration and Running the 10.1 OMS in Secure Mode
If the Enterprise Manager 10g OMS is running in secure mode the newly installed 10.1 agents will need to be set to run in secure mode as well.  In order to do this please refer to the Enterprise Manager Advanced Configuration Guide for instructions on securing 10.1 management agents.  Once the agents have been secured by the OMS, check to make sure that the targets have been successfully uploaded to the OMS.

12.2.0  Deploying the 10.1 Agent in a High Availability (HA) architecture
If you have installed the Enterprise Manager 10g in a HA configuration, you will need to make you point the agentInstallJob.tcl parameters at one of the 10.1 OMS and not at the router URL.  The migration script cannot obtain the agent download files it needs to create the 10.1 agent using this type of architecture.