Table of Contents

 1.  General
        1.1  Introduction
        1.2  Installation and Configuration
2.   Monitoring
3.   Job Systems
4.   Blackouts
5.   Database Management
6.   Configuration Management Pack
7.   Online Help
8.   Enterprise Manager 10g Java Console 

1. General

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

1.2  Installation and Configuration
1.2.1  Running Database Control 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.1.1  Changing the Oracle Management Service  IP Address After Initial Installation
Changing the Oracle Management Service IP address after initial installation is not currently supported.  To change the Oracle Management Service IP address after installation you must first deinstall and then reinstall the Management Service.

1.2.1.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 by editing the EMD_URL, emd. emdWalletSrcUrl and REPOSITORY_URL property in

$ORACLE_HOME/<host_sid>/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.

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.2  Handling short and fully qualified hostnames on RAC
DB Control Configuration currently makes a "best-effort" attempt to determine the fully-qualified hostnames (FQHN) of all RAC nodes.  It employs a variety of    mechanisms in doing so; however, none of the mechanisms are guaranteed to return the FQHN.  Fortunately, EMCP does not require FQHN's to work correctly – if "short" hostnames are used consistently in all operations, Enterprise Manager configuration will proceed correctly.  In fact, short and long hostnames can be used together. Take for instance,  the following two-node RAC cluster.
 <o:p></o:p>

It is possible to use “nodeA” as the hostname for node A, and “nodeB.us.oracle.com” as the hostname for node B.  This combination of short and long hostnames is permissible as long as these names are used consistently.  Specifically, this means that “nodeA” (and not “nodeA.us.oracle.com”) must always be used to identify node A, and “nodeB.us.oracle.com” (and not “nodeB”) must always be used to identify node B.

Problems arise when the short and long hostnames are both used to identify a single node.  For instance, node A may use the short name “nodeB” to identify node B, while node B uses its long name “nodeB.us.oracle.com” to identify itself.  In this case, Enterprise Manager will not function properly, as the location of Enterprise Manager configuration, log, and data files are all hostname-dependent.

Whether a machine uses the short or long name to identify itself and other nodes in the cluster depends on the machine configuration.  To avoid the problem discussed above, make sure each machine in the cluster is configured correctly.  For any given node X in the cluster, every node (including node X) should use the same hostname (whether long or short) to identify node X.

1.2.3  Discovering ASM Instance in a RAC Environment
If the ASM instance is added in an existing RAC environment, it is not discovered automatically by the Database Control. One needs to do the following to discover the ASM target:

a. Manually create an XML file of the following format:

<Target TYPE="osm_instance" name="%ASM_TARGET_NAME%20%" DISPLAY_name="%ASM_TARGET_DISPLAY_NAME%20%"><o:p></o:p>
                 <Property name="SID" VALUE="%ASM_SID%"/><o:p></o:p>
                <Property name="MachineName" VALUE="%HOSTNAME %"/><o:p></o:p>
                 <Property name="OracleHome" VALUE="%ASM_OH %"/><o:p></o:p>
                 <Property name="UserName" VALUE="%ASM_USER_NAME%"/><o:p></o:p>
                 <Property name="password" VALUE="%ASM_USER_PWD%" ENCRYPTED="FALSE "/><o:p></o:p>
                 <Property name="Role" VALUE="%ASM_USER_ROLE%"/><o:p></o:p>
                 <Property name="Port" VALUE="%ASM_PORT%"/><o:p></o:p>
</Target><o:p></o:p>

Parameter	Explanation
%ASM_TARGET_NAME %	ASM target name. Usually “hostname_ASMSid”
%ASM_TARGET_DISPLAY_NAME%	ASM target display name. Usually “ASMSid”
%ASM_USER_NAME%	Username (default is SYS) of the ASM instance
%ASM_USER_PWD%	ASM user's password
%ASM_USER_ROLE%	ASM user's role (default is SYSDBA)
%ASM_PORT%	ASM port
%ASM_SID%	ASM SID
%ASM_OH%	ASM Oracle Home
%HOSTNAME%	Hostname. In RAC environment, use may VIP

b. Run "emctl config agent addtarget <filename>". This will append the above target to the list of targets in targets.xml.
c. Restart the agent.

<o:p></o:p>

1.2.4 Changing the Oracle Management Service Port
If a user wants to change the OMS port, they'll have to modify three files, and then restart DB Control in order to force these changes to take effect.

a) Edit $ORACLE_HOME/<host>_<sid>/sysman/config/emoms.properties and modify the following parameters:

oracle.sysman.emSDK.svlt.ConsoleServerPort
oracle.sysman.emSDK.svlt.ConsoleServerHTTPSPort

b) Edit $ORACLE_HOME/<host>_<sid>/sysman/config/emd.properties and modify the following parameters:

REPOSITORY_URL
emdWalletSrcUrl

c) Edit $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_<host>_<sid>/config/http-web-site.xml and modify the following parameter:

web-site port

Please back up the existing files before making changes.

1.2.5 Discovering Database Listener Targets Running From a Different ORACLE_HOME
If you want to discover a database listener target that is running out of a different ORACLE_HOME, you have to set TNS_ADMIN variable to point to the listener configuration directory before running emca for configuring database control.

1.2.6  Verify NLS Settings Are Configured Properly
If you launch emctl in a non English environment, make sure the OS default locale setting is configured properly. To check the current setting  for LC_ALL or LANG, issue this command:  % locale.  To verify the specific value for your Operating System, please refer to platform specific documentation.

1.2.7 Page Cannot Be Displayed
User may occasionally encounter "The page cannot be displayed" error in Database control secure mode using Internet Explorer.  This happens when browser is configured to use proxy server. One workaround is to avoid using proxy server if possible.  Another workaround is to use Netscape. When this problem occurs, user can click the refresh button of the browser to redo the previous operation.

1.2.8 Database Control Does Not Start Properly after Editing http-web-site.xml
In the http-web-site.xml file (located in $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_$HOST_$SID/config/ ), if you comment out the last occurrence of port = or secure = , the Database Control product will not start properly. If you want to make a new entry for Port or Security, make sure it is the last entry in the file. (Bug 3365751)

1.2.9 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.10  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.  Monitoring System
2.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)

2.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.  For errors related to database User-Defined Metrics, users should click on the Metric Collection Errors link under the Related Links section of the database home page.  For errors related to host User-Defined Metrics,  users should check the Alerts section of the host home page (Bug 3301699)

2.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)

2.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)

2.5.0  Response Actions Will Not Work for Server-Generated Alerts (Bug 3129353)

2.6.0 Securing Multiple Database Controls in a RAC Environment Should Not Be Done Simultaneously
The first time you secure any RAC Database Control, you should not attempt to secure more than one at a time.  After one RAC Database Control has been successfully secured, you can secure multiple RAC Database Controls at one time. (Bug 3335221)

2.7.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.

2.8.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.2.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)

3.3.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)

3.4.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)

3.5.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.

3.6.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)

3.7.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 using the 'Jobs' link under the Related Links section of any database page: Home page,  Performance, Administration, Maintenance.   Also, the Job Activity section in the database home page refers to Enterprise Manager job activity  (Bug 3312974)

3.8.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)

3.9.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)

4. Blackouts
4.1.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.2.0  OMS and Repository Targets Not Supported
When selecting targets for blackouts,  users will see a target type called "OMS and Repository".  This target type does not apply to blackouts created in the Database Control and should be ignored  (Bug 3241207)

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  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.5.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.  Database Management
5.1.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 or OidCA. If ldap.ora file location is not OH\network\admin or OH\ldap\admin, then you must define TNS_ADMIN / LDAP_ADMIN environment variable to that location before starting DBControl.

5.2.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)

5.3.0 Reorganize Objects

5.3.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.

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

5.3.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.

5.3.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)

5.3.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.

5.3.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.

5.4.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)

5.5.0 Editing Multiple 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.

5.6.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)

5.7.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)

5.8.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--
 

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.

5.9.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)

5.10.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)

6.  Configuration Management Pack
6.1.0 Oracle Targets Missing from Deployments Summary Rollup Tables
If Oracle software was not installed using the Oracle Universal Installer or 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.

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

6.3.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)

6.4.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)

6.5.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)

6.6.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)

6.7.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 sub component of another Oracle product. (Bug 3336562)

6.8.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.

6.9.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.

6.10.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)

6.11.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)

6.12.0 Database Control Agent Patching Not Possible Using Database Control
You can't use Database Control to patch the Database Control Agent as this requires a job to be run which will stop the agent (thus stopping itself, which will terminate the job). Given this catch 22 situation, you should not attempt to apply the patch, but limit the job to staging the patch (which requires de-selecting the "Run Script to Apply Patch" check box in the fourth step of the patching wizard), and then manually run opatch from the command line. (Bug 3356582)

6.13.0 Database Control Proxy Settings For Patching
In order for the Critical Patch Functionality to download the alerts from MetaLink, as well as the patching functionality to query MetaLink for relevant patches, Database Control needs to be able to access the Oracle MetaLink web site. If your Database Control instance requires a proxy to access the Internet, you must configure it to use that proxy. As described in the documentation, this is achieved by editing $ORACLE_HOME/<hostname>_$ORACLE_SID/sysman/config/emoms.properties from the root of the
Database Control home directory.

6.14.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)

6.15.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)

6.16.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. Online Help
7.1.0 References to "Oracle Agent"
Any references to "Oracle Agent" in the Enterprise Manager online help refer to the Oracle Management Agent. These help topics will be updated to use the term "Oracle Management Agent" in a future release.

7.2.0 References to "Enterprise Manager repository"
Any references to Enterprise Manager repository in the online help actually refer to the Management Repository. These help topics will be updated to use the term  "Management Repository" in a future release.

7.3.0 Context Sensitive Help Doesn't Work in 1 to N Comparison
The context sensitive help for comparing one host to many hosts does not work in this release of Enterprise Manager.  Help for this functionality can be found using the Search mechanism from the Help link. (Bug 3058387)

8.  Enterprise Manager 10g Java Console
8.1.0  Quick Tours not Available
Quick Tours are no longer supported in Enterprise Manager 10g. Potentially remaining links to "Quick Tours" are not working.

8.2.0  LogMiner Viewer
You will need a standalone repository if you want to save LogMiner Viewer queries. LogMiner Viewer will prompt you for a standalone repository when needed.  Once a standalone repository is created using LogMiner Viewer (or any other Enterprise Manager application that supports a standalone repository), LogMiner Viewer will use that standalone repository during any standalone mode sessions.

For information about creating a standalone repository, see the online help for LogMiner Viewer. Select the section "Getting Started", subsection "Connecting to or Creating a Standalone Repository". Additional information can be found in the online help for Enterprise Manager Console.  Select the section "Console Administration", subsection "Requirements Before Creating a Standalone Repository".  The following is supplemental information to that documentation.  The Standalone Repository informational message dialog, Repository Login dialog, and Creating Standalone Repository dialog box each have a help button. The online help for those dialogs is not available.

The standalone repository owner is a database account that must be created before you create a standalone repository. Create this account with the Enterprise Manager Console. The account must have the following roles:

* CONNECT
* SELECT_CATALOG_ROLE

Also, it must have the following privileges:
             * CREATE PROCEDURE
             * CREATE TRIGGER
             * CREATE TYPE
             * EXECUTE ANY PROCEDURE
             * EXECUTE ANY TYPE
             * SELECT ANY DICTIONARY
             * SELECT ANY TABLE

In addition, the account must have unlimited quota for its default tablespace and its temporary tablespace.
If you encounter an ORA-03113 error executing a LogMiner Viewer query against the online redo log files, it generally means the redo log files are empty.  Exit LogMiner Viewer, switch each log file by executing the 'alter system switch logfile' SQL*Plus command for each redo log file, restart LogMiner Viewer and execute your query.

---

Copyright © 2004, Oracle. All rights reserved.