Oracle Enterprise Manager Readme Release 9.2 Production -----------------------------------------------------------------------Table of Contents 1. General 1.1 Introduction 1.

2 Language Support 1.3 Installation 1.4 Miscellaneous 2. Event and Job Systems 3. Enhanced Notifications 4. Reporting 5. Oracle Management Server / Repository 6. Browser-based Enterprise Manager 7. Database Management 8. LogMiner Viewer 9. Data Guard Manager 10. Policy Manager 11. HTTP Server Management 12. Forms Server Manager 13. Oracle Wor flow Manager 14. Oracle Diagnostics Pac 14.1 Performance Manager 14.2 Capacity Planner 14.3 Oracle Advanced Events 14.4 Web Server Monitoring 15. Oracle Tuning Pac 15.1 Graphical Explain Plan and Outline Editor 15.2 SQL Analyze 15.3 Oracle Expert 15.4 Tablespace Map and Reorg Wizard 16. Oracle Change Management Pac 16.1 General 16.2 Script Generation and Execution 16.3 Command Line Interface 16.4 Currently Unsupported Database Features and Attributes 17. Oracle Management Pac for Oracle Applications 17.1 Performance Manager 17.2 Events and Jobs 17.3 Concurrent Processing Tuning Assistant 17.4 Console 17.5 Capacity Planner 18. Oracle Standard Management Pac 18.1 New Features in This Oracle Standard Management Pac Release 19. Oracle Enterprise User Security Management 19.1 Command Line Interface 20. Oracle Directory Manager 20.1 Administering Versions of OID with oidadmin version 9.2.0.1.0 20.2 Administering Third-Party Directories Using oidadmin 20.3 Oracle Directory Manager Limitations -----------------------------------------------------------------------1. General 1.1 Introduction

This Readme identifies differences between the delivered Oracle Enterprise Manager Release 9.2 product and its documented functionality. Additional information may also be included in the Release Notes located in the /relnotes/ directory at the root of the CD-ROM. Be sure to review those Release Notes - as well as this Readme- before using the product as it may contain late-brea ing information concerning Enterprise Manager. In addition, before using any of the integrated applications (i.e. Oracle Directory Manager, etc.), you should review the corresponding applications' Readmes; if installed, they can be found in the $ORACLE_HOME/relnotes/em/?directory>. For information on changes in Oracle Intelligent Agent Release 9.2, refer to its Readme file located under its $ORACLE_HOME/networ /doc/ directory. For information on system and hardware requirements specific to Enterprise Manager, refer to the Oracle Enterprise Manager Configuration Guide. 1.2 Language Support 1.2.1 In multi-byte implementations of Enterprise Manager (such as Asian language translations), launching certain pac applications (Performance Manager, Capacity Planner and Change Manager) from the Enterprise Manager Console can result in corrupt text appearing in other applications subsequently launched from that same running console. The applications subsequently launched from the console that are effected by this include: TopSessions, SQLAnalyze, Index Tuning Wizard, Oracle Trace Manager, Oracle Trace Data Viewer and Oracle Expert. In order to avoid this problem, it is recommended that Performance Manager, Capacity Planning and Change Manager be launched from the Windows Start Menu rather than from the Console in multi-byte environments. Should this problem occur, it can be corrected by re-starting the Console and logging into the applications using the Windows Start Menu. (Bug 1344568) 1.2.2 Because NLS environment parameters are not being passed to the C++ applications correctly, Oracle Expert and SQL Analyze must be launched from the Enterprise Manager Console, NOT from the Windows Start menu. (Bugs 1333427, 1338106, 1344568, 1714960, 1793680) 1.2.3 For non-English versions of Enterprise Manager, certain inconsistencies may appear in the non-English versions of the online help. 1.2.4 In an non-English environment, the user needs to set the NLS_DATE_FORMAT appropriately (dd-mm-yyyy) for specifying where clause in Table Data Editor. You must first shutdown the OMS and Console and then set the variables for the changes to ta e effect. 1.2.5 In order to use SQL*Plus Wor sheet in a language other than English, you must first modify the dbappscfg.properties file located in the $ORACLE_HOME/sysman/config/ directory. Modify this file by adding a value for SQLPLUS_NLS_LANG; the value should be the same as the default NLS_LANG parameter. In Solaris or UNIX environment, please also uncomment the lines for SQLPLUS_LD_LIBRARY_PATH and SQLPLUS_ORACLE_HOME in addition to defining the NLS_LANG parameter. (Bug 2181549)

# Parameters for Solaris only # SQLPLUS_LD_LIBRARY_PATH=/private1/oracle/product/ora920/lib SQLPLUS_ORACLE_HOME=/private1/oracle/product/ora9201 1.2.6 On a Japanese operating system only: When you insert data into or select from NCHAR/NVARCHAR2 column using "Graphical Select mode" against 8.1.7 database or earlier, you will get an error. You must use FREE SQL mode with 'N' eyword to insert into or select from NCHAR columns. Example 1: INSERT INTO nchar_tab(ncol1, ncol2)values (N'XXX', N'YYY') Example 2: SELECT ncol2 from nchar_tab where ncol1 = N'XXX' 1.2.7 In any non-English deployments of Enterprise Manager, launching Netscape browser to show HTML files from an Enterprise Manager application installed on Solaris and possibly other UNIX based platforms may not wor . For instance, if from the Console you go to the Help main menu -> Latest Product Information, nothing will appear. (Bugs 2188802 and 2191034) To wor around this problem, you must perform the following steps. Note: In this wor around, we assume you are creating /usr/local/bin/altbrowser. We also assume your default Netscape browser is launched by /usr/local/bin/netscape. You must specify forward slashs (/) and bac slashs (\) as they are in the wor around. Also there should be no spaces between slashes. 1. Create a shell script executable file in any location. % cat << \EOF > /usr/local/bin/altbrowser #!/bin/sh ns=/usr/local/bin/netscape # ---> ns is the absolute path of the actual browser. unset XFILESEARCHPATH # this is the wor around. $ns "$@" # "$@" should be used instead of $* # to allow white spaces as the argument 2. Change the file permission to be able to execute. % chmod 755 /usr/local/bin/altbrowser 3. In the ClientConfig.properties file located in the $ORACLE_HOME/sysman/config/ directory, add the following line to the end of the file: user.browser=/usr/local/bin/altbrowser 1.3 Installation 1.3.1 The JRE is installed by various Oracle products. However, there is only one shared JRE per system. Hence, if after installing Enterprise Manager Release 9.0 you install a previous release of Enterprise Manager (i.e. Release 2.2), the JRE (Java Runtime Environment) installed as part of Release 9.0 will be downgraded automatically; no error messages will appear. This downgrade from JRE Release 1.1.8.10 to 1.1.7.30 will cause

problems for Enterprise Manager Release 9.0. Consequently, do no install Enterprise Manager Release 2.2 after installing Enterprise Manager Release 9.0. Installing a pre-9.0 Oracle database will also cause the same problem of downgrading the JRE. If you run into this situation, you can wor around the problem by re- installing JRE 1.1.8.10 from the CD-ROM you installed Enterprise Manager Release 9.0 (most li ely from a Release 9.0 CD-ROM). Re-install the JRE by re-installing Oracle Universal Installer; as the Installer has a dependency on the JRE. 1.4 Miscellaneous 1.4.1 If you select a different window after launching the Console, the login dialog will not display in the foreground. You may need to minimize any active windows or use ALT -> tab and select the Console application to bring the login dialog to the foreground. (Bug 806713) 1.4.2 When you open a modal dialog box in an Oracle Enterprise Manager application (a modal dialog box is one that requires user action before being able to return to the application) and request context-sensitive help on that dialog box, the help is displayed in a modal help topic window. Before you can return to the modal dialog box, you must close the help topic window that is displaying the help topic for the modal dialog box. 1.4.3 During discovery of remote nodes and their targets, if the node is available and reachable via the networ , but the Intelligent Agent on that node is down, the discovery wizard will give the error "VNI-4044 : Cannot contact agent. Node may be down, or the networ may be down or slow." Instead of the expected error "VNI-4009 : Cannot contact agent on the node. Agent may be down or networ communication to the node has failed." If this occurs, log on to the remote node and chec the status of the Intelligent Agent via the agentctl utility: agenctl status agent If the Agent is not up, start the Agent via: agenctl start agent then perform Discovery again. (Bug 1874173) 1.4.4 The Enterprise Manager Configuration Guide chapter 2 Standalone, section "Standalone Repository", incorrectly states that Index Tuning Wizard requires a standalone repository. Index Tuning Wizard does not require a standalone repository. 1.4.5 The Enterprise Manager Configuration Guide chapter 3 Configuring and Controlling the Management Server, section "Configuring a Local Management Server to Use a New Release 9i Repository", incorrectly states that you should not change the password for SYS during database creation via Database Configuration Assistant as Enterprise Manager Configuration Assistant assumes that the password is "change_on_install". This is no longer a restriction. 1.4.6 To use Enterprise Manager functionality other than SQL*Plus Wor sheet as a non-DBA user, you must have the appropriate privilege. A DBA user will already have the appropriate privileges to manage the database.

* For 8.x databases: You must have been granted the SELECT_CATALOG_ROLE. As the System Administrator or Super Administrator to grant you this role. To create, edit, or drop objects outside of your schema, you must have been granted the DBA role or the appropriate privileges for the object. Note: The SELECT_CATALOG_ROLE is only available for Oracle8.x databases. * For 9.x databases: You must be granted the Select Any Dictionary privilege. As the System Administrator or Super Administrator to grant you this role. 1.4.7 If you select to show an HTML-formatted file (Explain Plan report, Latest Product Information from the Help main menu, etc.), from an installed Enterprise Manager Console and the HTML-formatted file does not appear then in the ClientConfig.properties file located in the $ORACLE_HOME/sysman/config/ directory, add the following line to the end of the file: (Bug 1961020) user.browser=<full_path_to_browser> 2. Event and Job Systems 2.1 If your User-Defined event has failed with an error: "User Defined Event" failed: No result returned in output: then this means the tagged output specific to user-defined events could not be found in standard output. This may mean your script failed to execute for a variety of reasons. Some things to loo into: a) chec that the path to the monitoring script you specified is correct b) chec the execute permissions on the monitoring script c) in the script text, chec that the path to the interpreter specified is correct. As an additional chec , log on to the monitored node using the Node credentials used for the event, then ma e sure the monitoring script runs correctly. 2.2 Associating fixit jobs with unsolicited events is only supported by 9.x Intelligent Agents. 2.3 If the OS character set when the Intelligent Agent is started up and the database character set which the Agent is managing are different, the "Alert" event returns corrupted characters. This happens if alert.ora file has non-US7ASCII characters. (Bug 1689939) Please set the default OS character set by defining the OS locale and define the NLS_LANG parameter properly before the Intelligent Agent gets started. 2.4 Event Handler 2.4.1 If the command to be executed by the Command Executor doesn't seem to be invo ed as expected, ma e sure all to ens in the command are enclosed in double-quotes ("). (Bug 1894728) For example: /com/oracle/sysman/em/commandexecutor/templates/allEvents2/command="C: /myApp/myProg"

"arg1=%node%" "arg2=%targetname%" "-d" "arg3=Event:%eventname% Severity:%severity% Result:%output%" 2.4.2 Event Logger on Windows platforms The default event handler configuration will log event information to the file %ORACLE_HOME%/sysman/log/eventhandler.log. For example, if the ORACLE_HOME is c:\orant, then the logfile specification will loo li e this: /com/oracle/sysman/em/eventlogger/templates/allevents/logfile =c:\orant/sysman/log/eventhandler.log However, directory names that use the bac lash (\) delimiter will not wor for configuration information -- these directory delimiters must be specified as forward-slashes (/). To wor around the problem, change the filename specification to use all forward slashes (/), e.g. /com/oracle/sysman/em/eventlogger/templates/allevents/logfile =c:/orant/sysman/log/eventhandler.log Refer to the Event Handler chapter in the Enterprise Manager Administrator's Guide for details on changing event handler configuration. (Bug 1902918) 2.5 When a job is created by a user, there is an option to override preferred credentials by specifying new credentials to be used for the job. If new credentials are specified, and if other users are then given access to this job (via View, Modify, or Full permissions on the job) then these users can potentially re-use the credentials in other jobs via copy or create li e operations on the original job. If this is a concern, do not override preferred credentials for jobs or use caution when providing other users access to jobs that have overridden credentials. (Bug 2243334) 2.6 When creating a database job which requires a database role be provided as part of the database credentials, use the Run DBA Script job tas and not the Run SQL*Plus Script job tas The Run DBA Script tas uses the Username, Password and Role as specified in the preferred credentials for the target. It also allows the user to override these credentials, including the role. The 'Run SQL*Plus Script' tas does not use the role specified in preferred credentials. 2.7 Broadcasting does not support multibyte characters in both UNIX and NT environment. This is due to the restriction of these platforms. (Bugs 2165255, 2213911) 2.8 In NT OS command does not wor properly with none English command arguments. This is also the restriction of the platform. (Bug 1892345) 2.9 System Interrupts event on IBM AIX On IBM AIX, the System Interrupts (#/s) event test returns the Number of Context Switches per second instead of the number of

system interrupts per second. 3. Enhanced Notifications 3.1 If you configure a paging carrier with invalid entries and then test that paging carrier, it ta es five minutes before a message appears indicating that it failed to send the test page. (Bug 1757910) 4. Reporting 4.1 If after installing the Oracle HTTP Server you manually edit the ServerName property in its httpd.conf file and then access the Enterprise Manager Reporting Web Site, you may encounter the following error: "The management server <hostname> is using a different webserver ?hostname> for Enterprise Manager reporting services. This webserver <hostname> will be deconfigured and will no longer support Enterprise Manager reporting. To access Enterprise Manager Reports in the future, please use the webserver <hostname>." To fix this problem, edit the httpd.conf file located in the $ORACLE_HOME/Apache/Apache/ directory by setting the ServerName property to the hostname of the machine running the Oracle HTTP Server for the Enterprise Manager Reporting Web Site. (Bug 1696527) 4.2 In order to configure the Enterprise Manager Reporting Website, you must run the 'oemctl configure rws' command at the command line on the machine which runs the reporting webserver, and supply the appropriate information as prompted. Note: The Management Server must be installed on the same machine as the reporting webserver. (Bug 1709809) 4.3 If you view Enterprise Manager reports in a non-English environment from Microsoft Internet Explorer release 5.0, you may see garbled, non-legible text in the reports. To wor around this problem, either view the reports from Microsoft Internet Explorer release 5.5 or from Netscape Navigator release 4.7. (Bug 1773959) 4.4 When accessing Enterprise Manager reports from a Web browser (from a Unix-based web server), you may see a blan page or the following error: "Internal Server Error: The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, you@your.address and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log." Review the Oracle HTTP Server error_log file located in the $ORACLE_HOME/Apache/Apache/logs/ directory for the following exception: "Xlib: Client is not authorized to connect to Server java.lang.NoClassDefFoundError: sun/awt/motif/MTool i t" If this exception occurred, perform the following steps to fix the problem:

1) Execute the xhost +<host> command on the X Window machine where you are accessing reports from a web browser. For example, if your reporting web server is running on host servlet1 and the X Window is running on host xserv1, then execute the following command on xserv1: xhost +servlet1 If your UNIX machine does not meet the hardware requirements for running an X server, then read section 4.5 of this readme. 2) Specify the DISPLAY environment variable with the X Window machine name on the host where the reporting web server is running. For example, if your reporting web server is running on host servlet1 and the X Window is running on host xserv1, then execute the following command on servlet1: * If you are using the C Shell: setenv DISPLAY xserv1:0.0 * If you are using the B or K Shell: DISPLAY=xwerv1:0.0; export DISPLAY 3) Verify that the X Window environment has been configured properly. For example, execute the xcloc command. If you see the xcloc window on your X Server (i.e. reporting web server), your X Window environment has been configured properly. 4) Restart the Oracle HTTP Server via the command apachectl restart. 4.5 An alternative to the remote X server solution (should your machine not meet the hardware requirements for running an X server) is to run a pseudo-X server such as the X Virtual Frame Buffer, or XVFB. The main difference between XVFB and the standard X server software is that XVFB uses an in-memory virtual frame buffer instead of a hardware frame buffer. As such, XVFB can be run on almost any Unix machine, including "headless" middle-tier machines which lac a hardware frame buffer and eyboard. If your UNIX vendor does not provide XVFB binary, then you must build the XVFB binary from the X.Org source code. Building XVFB Building an XVFB binary is not especially difficult. The following steps describe how to build XVFB on Solaris 8. 1.Download the X Window System source code Source code for XVFB is available from the X.Org's ftp server. The X Window System source code is distributed in a number of tar files. Only the first tar file is needed to build XVFB. The necessary tar file for version X11R6.5.1 is available at: ftp://ftp.x.org/pub/R6.5.1/tars/xorg-1.tar.gz Download and unzip/untar this tar file on the machine where XVFB is

being built. This should create a top-level directory named xc (which stands for X Consortium, the former name of X.org). 2.Update site.def Configuration information for the build is specified in the site.def file, located in the xc/config/cf/ directory. This file needs to be modified to indicate that XVFB should be built. Also, since it is not necessary to build all of the X Window System, a number of items in the site.def file can be commented out to speed up the build. Finally, for Solaris, the ProjectRoot should be changed to /usr/openwin, which is the normal location for X-related files on Solaris. Or, simply copy this preconfigured site.def file to xc/config/cf. 3.Ma e World

/usr/platform/SUNW,Ultra-1/lib/libc_psr.so.1

The final step is to build the XVFB binary. The following software is required: Ma e: /usr/ccs/bin/ma e should be used C Compiler: Sun Wor Shop 6 is recommended, although gcc can be used. Once you are ready to build XVFB, go to the xc directory and run the following command: ma e World After the build completes (about an hour), the Xvfb executable should be created in xc/programs/Xserver/Xvfb. For a sanity chec on the XVFB executable, run ldd Xvfb to ma e sure that the lin succeeded. You should see something along the lines of: libsoc et.so.1 => /usr/lib/libsoc et.so.1 libnsl.so.1 => /usr/lib/libnsl.so.1 libc.so.1 => /usr/lib/libc.so.1 libdl.so.1 => /usr/lib/libdl.so.1 libmp.so.2 => /usr/lib/libmp.so.2

Running XVFB The following command line can be used to launch XVFB: Xvfb :1 -screen 0 1x1x24 The XVFB binary must be run as root or must have the suid bit set. The :1 argument indicates that the XVFB binary runs as server number 1 (the standard X server typically runs as server number 0). The -screen argument indicates that a single screen of size 1x1 with 24-bit pixel depth should be used. Note, since all images are generated off screen, the 1x1 screen size is sufficient for image generation purposes. Since XVFB must remain running for the lifetime of the application, perhaps the best approach is to automatically launch XVFB during the machine's boot process. XVFB can then remain running as a bac ground process until the machine is shut down. Once the XVFB executable is running, client applications can connect to XVFB by setting the DISPLAY environment variable to :1. The :1 setting indicates that server number 1 (the XVFB server) on the local machine should be used for all X graphics operations. When running in Jserv, the DISPLAY environment variable should be set in jserv.properties, for example: wrapper.env=DISPLAY=:1 4.6 Netscape may not display non-English titles/lin s correctly. If this happens, please set the character set appropriate to your language and select the option "Use my default-fonts, overriding document-specified fonts" in your browser. (Bug 1777348) 4.7 In non English UNIX environment, ma e sure to follow the additional steps below to ma e the Enterprise Manager Reporting Website wor with non English characters. (Bugs 1709744,1786100) The following example assumes the Japanese Solaris environment. 1) $ORACLE_HOME/Apache/Jserv/etc/jserv.properties configuration (1.1) If you want to define the environment variables in the jserv.properties file independently of the runtime environment, uncomment the wrapper.env=LANG= line and set the appropriate OS locale value. (line 87) # Uncomment to set Java default locale based on the LANG environment # variable. #wrapper.env.copy=LANG # Alternatively, a specific value can be set as follows: wrapper.env=LANG=ja wrapper.env.copy=ORACLE_HOME wrapper.env=NLS_LANG=JAPANESE_JAPAN.UTF8

1.2) If you want to dynamically change the environment variables before the Apache server gets restarted, uncomment the wrapper.env.copy=LANG line, comment out wrapper.env=NLS_LANG= line, and add the wrapper.env.copy=NLS_LANG line. (line 87) # Uncomment to set Java default locale based on the LANG environment # variable. wrapper.env.copy=LANG # Alternatively, a specific value can be set as follows: # wrapper.env=LANG=C wrapper.env.copy=ORACLE_HOME #wrapper.env=NLS_LANG=JAPANESE_JAPAN.UTF8 wrapper.env.copy=NLS_LANG If you have chosen this option, ma e sure to define the LANG and NLS_LANG environment variables with the appropriate value before the Apache server gets restarted. (2) X Window server configuration Because the Enterprise Manager Reporting Website uses the X Window system running on the Apache server node, you must start the X Server in the console. This is done by logging into the machine from the machine console and starting the Common Des top Environment (CDE). Even you don't use the console, you have to leave the CDE as it is. Please do not log out in the console. You may also need to execute the following command so that the Enterprise Manager Reporting Website can ma e use of the X Server. % xhost + Ma e sure the DISPLAY environment variable is set properly before the Apache server gets started. If the X Window server is not properly configured, the report may display square boxes. 4.8 For non English environments, some charts may display some of the translated messages as square boxes or question mar s. (Bugs 2274548, 2199733) 4.9 When accessing Enterprise Manager reports from a Web browser (from a Unix-based web server), you may see a blan page or the following error: "Internal Server Error: The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, you@your.address and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log." Review the Oracle HTTP Server error_log file located in the $ORACLE_HOME/Apache/Apache/logs/ directory for the following exception: "[error] OPM: EW: Fails to ping process with pid:11301. Probably the process is hanging and can not response. In most cases, the JVM is either heavily loaded or doing GC. Please increase the jvm timeout value or decrease the

jvm heap size to reduce the time of doing GC. The process is about to be restarted." If this exception occurred, perform the following steps to fix the problem (Bug 2260896): 1) Increase the default time out value by updating the ApJServVMTimeout directive in the jserv.conf located in the $ORACLE_HOME/Apache/Jserv/etc/ directory. Try setting the value to around 30 or 35. 2) Edit the java heap size by adding/updating the following lines in the jserv.properties file located in the $ORACLE_HOME/Apache/Jserv/etc/ directory. The following values should be ideal: wrapper.bin.parameters=-Xms64m wrapper.bin.parameters=-Xmx128m 3) Restart the Oracle HTTP Server. 4.10 If all the gifs in a published report are missing when accessing the central reporting web site (URL http://ServerName.domainName:portNumber) from outside the firewall (Bugs 2246104 and 2242123), do the following: 1) Open $OH/oem_webstage/oem.conf 2) Modify the ServerName directive so that it has the domain name included. For example: "ServerName hostname.us.oracle.com" rather than just "ServerName hostname". 3) Restart Apache 4.11 If a scheduled report job completed successfully and you see the error when trying to view a report from browser: "The requested report is defined to be generated when triggered by a job. However, no job has yet triggered generation of this report. Chec to see if a job has been scheduled for this report.", edit the report from Console and re-schedule the report job. (Bug 2300451) 4.12 If you specify in Capacity Planner to have data collected for Concurrent Managers, Cluster Database Instances, Microsoft SQL Servers, or HTTP Servers you will not be able to view their analyses' reports from the central Reporting Web Site. When trying to access the Reporting Web Site's Trending tab for any of these target types, you will encounter the error "The repository does not contain any historical data. In order to access these reports please initiate historical data collection from the Capacity Planner tool." To wor around this problem, view the analyses for these target types from Capacity Planner. (Bug 2226807) 4.13 Service Level Reporting 4.13.1 In the Downtime Details report, when a service starts the reporting period in an unavailable state, the start of downtime is shown as the date of the start of the reporting period. This may be confusing since a user may now that the service has been down for some time prior to the reporting period start. The

start of downtime is shown as such since the Downtime Details report will only report downtime within the specified reporting period. (Bug 1727432) 4.13.2 The "Availability by Service" report always defaults its reporting period to the current month. A wor around is to clic the Elements tab when creating the report. Then select the top Element, named Overall Availability. Clic the Parameters tab and modify the reporting period. The reporting period chosen for the first Element in the Elements list will dictate the reporting period used for all Elements. (Bug 1715613) 4.13.3 When your display is set to "True Colors" the graph images may appear without color (blac ? white). Reduce your screen color depth to 256 and the images will regain their color. (Bug 1851944) 5. Oracle Management Server / Repository 5.1 It is recommended that you use a fully qualified node name (eg. foo.us.oracle.com) when setting up the name of the Management Server for connecting from the Console. Failing to do so may prevent launching of some of the Management Pac tools from within the Console, when the Console is running on a machine that is not in the same DNS Domain as the Management Server. If you continue to have difficulty launching some tools from the Console you should add an entry to the local 'hosts' file for the IP Address of the host where the Management Server is running. 5.2 Connections from Solaris to HP or Siemens SNI If your Management Server is running on a Solaris node and the Enterprise Manager repository database is running on either an HP 10.20 node or a Siemens SNI node, then you need to set the following SQLNET.ORA parameter on the Management Server node: DISABLE_OOB=ON The SQLNET.ORA file is located in the $ORACLE_HOME/networ /admin/ directory, where $ORACLE_HOME is the directory where the Management Server is installed. This parameter will prevent sqlnet connection hangs that are caused by differences in the way Sun's and HP's/Siemen's TCP layers handle simultaneous urgent messages on the same soc et. After you set this parameter, you need to stop and re-start the Management Server. 5.3 If your repository is in database release 8.1.7.0 or 8.1.7.1, be aware that database base bug 1393049, which causes some SQL queries to return incorrect results, may affect Enterprise Manager in a variety of ways. For example, the aforementioned database bug may manifest itself through Enterprise Manager via incorrect lists of events or jobs in history; incorrect list of event alerts; incorrect list of active jobs, invalid notifications being sent, etc. To fix the problem, refer to the table below: If Repository Resides in Database Release...

Then Fix the Problem by...

8.1.7.0 for all operating systems 8.1.7.1 for all operating systems

Upgrading your database to release 8.1.7.2 Upgrading your database to release 8.1.7.2 or Apply one-off patch for bug 1765292

To avoid these nown database problems entirely, Oracle recommends that you create your repository in a release 9.0.1, 8.1.7.2, or 8.1.7.1 (Sun SPARC Solaris only) database. (Database Base Bug 1393049) 5.4 If your repository is in database release 8.1.7.x for any operating system, Oracle recommends that you apply the patch for bug 1733170. Failure to apply this patch may result in intermittent Management Server faults due to segmentation violations. (Database Base Bug 1733170) 5.5 Please define the OS locale and the NLS_LANG parameter properly before the Management Server gets started. (Bug 2173930) 5.6 If you clic Help in Enterprise Manager Configuration Assistant and access the help topic of Configure a Local Management Server, the incorrect tablepsace name is specified: 'Optionally, creates a local database instance into which the repository will be placed and a recovery catalog in the RCVCAT tablespace. The recovery catalog user and password is RMAN/RMAN.' The correct tablespace should be TOOLS instead of RCVCAT tablespace. (Bug 2279812) 5.7 When configuring a Management Server, you should not include a period (i.e. the character ".") in the repository owner's user name. A repository user name containing a period is not supported. If the repository user name contains a period, the Management Server will successfully start but various Enterprise Manager Console operations will fail or hang. In such scenarios, the oms.log file located in the ORACLE_HOME/sysman/log/ directory will contain ORA-00972 or ORA-04043 errors. (Bugs 2274911, 2293145) 5.8 Before you upgrade Enterprise Manager to release 9.2, you should apply the following patch depending on the version of the Enterprise Manager repository. If you do not apply the appropriate patch prior to upgrading, you will experience an inability to edit registered events or to receive email and page notifications. (Bug 2199718) If Repository Resides in Database Release... 9.0.1.2.x for any operating system 8.1.7.x for any operating system

5.9 Before you upgrade Enterprise Manager to release 9.2, you should apply the following patch depending on the version of the Enterprise Manager repository. If you do not apply the appropriate patch prior to upgrading, events and jobs may remain

Then Fix the Problem by... Applying patch for bug 2199718 Applying patch for bug 2199718

in a scheduled or submitted state. (Bug 2238569) If Repository Resides in Database Release... 9.0.1.2.x for any operating system Then Fix the Problem by... Applying patch for bug 2238569

5.10 When configuring the Management Server via Enterprise Manager Configuration Assistant, you should configure the repository connection service in the JDBC connect string format of host:port:SID (e.g. dlsun1234.oracle.com:1521:orcl) rather than an Oracle Net service name. 6. Browser-based Enterprise Manager 6.1 If you have only installed the Oracle Enterprise Manager Web Site component from a Custom installation session, the Enterprise Manager Reporting website, a website from which you can navigate through all published Enterprise Manager reports, will not be able to run from either the emwebsite.html index page of browser-based Console or from its own reporting "index" page. To wor around this problem, install the Oracle Management Server along with the Oracle Enterprise Manager Web Site to have access to this functionality. 6.2 If you are running browser-based Enterprise Manager from a Netscape browser, do not specify *.?domain> in the manual proxy configuration. For example, do not specify *.us.oracle.com. Instead, you should specify .?domain>. For example, "us.oracle.com. (Bug 1936133) 6.3 The Enterprise Manager Configuration Guide incorrectly states the webservers that browser-based Enterprise Manager 9.2 has been certified against. The correct certifications include: * Oracle HTTP Server 1.3.22 for Windows NT, Windows 2000, Windows XP, Solaris (bundled with Enterprise Manager by default, available out-of-the-box) * Microsoft Internet Information Server 5.0 for Windows 2000 * Microsoft Internet Information Server 4.0 for Windows NT * Apache 1.3.22 for Windows NT, Windows 2000, Solaris * Oracle iAS release 1.0 for Windows NT, Windows 2000, Solaris Note: The only webserver that the central reporting website has been certified against is the Oracle HTTP Server 1.3.22 for Windows NT, Windows 2000, Windows XP, Solaris that is bundled with Enterprise Manager by default and available out-of-the-box. 7. Database Management 7.1 For pre-9i managed databases, to use the Summary Advisor wizard, you need to have an external procedure agent setup in the listener.ora and tnsnames.ora files. Refer to the Networ ing Administrator's Guide for more information. 7.2 The Storage management File IO Topology mapping option is only available for EMC Symetrix systems. The appropriate EMC software must be already installed.

7.3 Oracle 9.2 has dropped support for the CORBA framewor and the J2EE containers, Enterprise Java Beans (EJB) container, the embedded CORBA framewor and other related services, therefore Enterprise Manager no longer supports namespaces and browsing of CORBA and EJB components published in the namespaces. 7.4 Oracle Streams: To have multiple capture processes running concurrently the logmnr_max_persistent_sessions initialization parameter need to be set properly. (The default value is 1, which disallows multi capture running at the same time) 7.5 Existing 9.0.1 Bac up jobs, saved in the Enterprise Manager library, cannot be re-submitted after an upgrade to EM 9.2. The wor around is to do a "Create Li e" on any of those jobs, navigate to the "Parameters" tab, clic the "Generate/View Script through Wizard...", launch the Bac up Wizard without changing the default selections, clic "Finish" and resubmit and/or save the jobs. 7.6 Solaris 8 only - the Bac up Wizard will stop responding when editing a the channel limits from Bac up Wizard-->Bac up Configuration --> Channels --> Channel limits. (bug 2265981). The wor around is to edit the channel limits directly in a bac up configuration: right mouse clic the target database --> "Bac up Management" -> "Bac up Configuration Library"--> Highlight the configuration you want to edit--> Edit--> "Channel" page, clic the "Channel Limits" and edit the "Channel Limits" --> OK 7.10 OLAP Management 7.10.1 Cubes may become obsolete if the underlying tables are deleted or the users that own the metadata are removed. Although an obsolete cube is still visible from the OLAP catalog, it is mar ed as invalid and cannot be used. The cube can be safely deleted from Enterprise Manager or by running the OLAP catalog cleanup as follows: begin cwm_utility.collect_garbage; commit; end; Note: If you do not periodically cleanup obsolete OLAP metadata, your tablespace may fill up and you may not have enough space to create new OLAP metadata.. (Bug 1771957) 7.10.2 The Cube Viewer requires the schema name, cube name, and measure names to be ASCII strings. The Cube Viewer does not startup if the OLAP Services Environment is not started up. Action: You can verify that the OLAP Services Environment is up by launching the OLAP Services Instance Manager by right clic ing on the OLAP Node. Ma e sure that the SessionIIOPService and SessionIIOPContext are correct. 7.10.3 Cube Viewer displays a CUBEVIEWERAPP-10209:

Cube Viewer was unable to authenticate against the OLAP Service." 7.10.4 Action: Ma e sure that the OLAP Service is running and that it is able to register with Oracle JVM. You can verify this by expanding the JVM node in the Enterprise Manager Console for the database specified in the SessionIIOPService parameter in the OLAP Services configuration. You can view the SessionIIOPService parameter by launching the OLAP Services Instance Manager from the OLAP node in the Enterpise Manager Console. 7.10.5 When the Cube Viewer is launched, it sometimes appears behind the Enterprise Manager window. Action: Reduce the size of the EM Window and switch and clic on the Cube Viewer window. 7.10.6 You cannot launch Cube Viewer while logged in as the sys userid or any userid that requires logging in as the SYSDBA or SYSOPER role. You need to login as a userid that has the proxy connection granted to it or you will get an Authentication failure. 7.10.7 When you update the SessionIIOPService or SessionIIOPContext parameters for an OLAP Service you need to restart the OLAP Services Agent to get Cube Viewer to connect properly 7.10.8 In order to use the Summary Advisor directly from the Cube Wizard you require a patch that will be released at later time. The wor around is to use the Summary Advisor from the navigator tree instead of the Cube Wizard after creating a cube. (bug 1785136) 7.10.9 If you are unable to launch OLAP Services Instance Manager from the HTML lin on the OLAP Management logo page, right-clic the OLAP node for the database and then choose OLAP Services Instance Manager. After you launch Instance Manager once by right-clic ing the OLAP node, you can then launch Instance Manager from the logo page. 8. LogMiner Viewer 8.1 If you are connected to LogMiner Viewer in standalone mode, you will need a standalone repository if you want to save 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 "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 easiest way to create this account is to select an existing Oracle Management Server repository account and create the standalone repository account from that using the Create Li e option. This automatically adds the privileges, roles, and quotas needed. If you create the standalone repository database account without copying an existing account, note that 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. 9. Data Guard Manager 9.1 In order to use all of the features of Data Guard Manager, the Intelligent Agent must be running on all primary and standby hosts. In addition, it is recommended that the primary and all standby databases are discovered. 9.2 Data Guard bro er does not manage the local archive destinations for any of the databases in a configuration. However, when a physical or logical standby database is created with Data Guard Manager, the log_archive_dest_1 parameter for the standby database is setup as a local destination with a default directory for locally generated archived logs. For a physical standby, the local destination directory is set to same value that was specified for the standby_archive_dest parameter in the Create Configuration wizard. For a logical standby, the local destination directory is set to the value of standby_archive_dest with a 'dgarc' subdirectory appended. For example, if the standby_archive_dest value is /private/arch, then the log_archive_dest_1 value for a logical standby will be set to 'LOCATION=/private/arch/dgarc'. When adding an existing standby database, Data Guard Manager does not change the value of the log_archive_dest_1 parameter. 9.3 Several features of Data Guard Manager wor differently when the primary and/or standby databases are on Microsoft Windows NT or Windows 2000 systems: 1. The concurrent copy and data compression features of the

Create Configuration wizard are not available. 2. The chec of available dis space on the standby system -normally done for UNIX-based databases -- is not done during the Create Configuration wizard. 3. The archived log destination space chec is not available in the configuration Performance page. 4. During most operations where a progress dialog is shown, Data Guard configuration log and database alert log output -- normally shown for UNIX-based databases -- is not shown in progress dialog 9.4 From Enterpise Manager applications, users cannot connect to logical standby databases as "NORMAL" due to a limitation with logical standby databases. To wor around this problem, you must set the 'O7_DICTIONARY_ACCESSIBILITY' initialization parameter to TRUE, then stop and restart the logical standby database. Also, each user must have the 'SELECT ANY TABLE' privilege. 9.5 When creating a new standby database, it is recommended that the primary SYSDBA password be used as the default password. If the SYSDBA password on the standby is not the same as the primary, then preferred credentials must be set on all databases in order to perform switchover and restart operations from Data Guard Manager. 9.6 Open Sessions Dialog and CJQ processes: CJQ (job_queue_processes) will show up in the Open Sessions Dialog as user sessions during switchover and when moving a standby database out of the read-only state. These processes will not impede the progress of either of these operations and can be ignored. Note that once a physical standby is in read-only state, any other user sessions must be shutdown before the state can be changed. 9.7 If you are running the Data Guard Manager Test Application on a primary database, it must be closed before initiating a switchover to a logical standby database. 9.8 If the DbFileNameConvert property of a standby database resource shows an ORA-16792 (inconsistent property) error immediately after instantiating the standby with Data Guard Manager, this may be due to the property value being longer than 512 characters. Since the DbFileNameConvert property is not actually used until a new datafile is added to the primary, you can clear the error by setting the value to an empty string. However, if you later plan to add a new datafile to the primary, you should set DbFileNameConvert on the standby to the proper value to ensure that the new datafile propagates to the standby. The LogFileNameConvert property has a similar 512 character limitation. Since this property is not used at all for standby databases instantiated by Data Guard Manager, an ORA-16792 error with this property can be cleared in the same manner explained above for DbFileNameConvert. 10. Policy Manager 10.1 When Oracle Policy Manager is connected to the Oracle Management Server, the database names are sorted incorrectly. The wor around is to use all capital or small letters when creating database instances. For example, ALPHA and BETA, or alpha and beta, but NOT alpha and BETA (or ALPHA and beta). You can also

use Oracle Policy Manager to connect directly to the individual database instances without using the Oracle Management Server to circumvent this problem. 11. HTTP Server Management 11.1 If Apache or iAS is configured to listen at a port number below 1024, the user must have root privileges in order to start the Oracle HTTP Listener. In order for administrators to start and shut down the web server using the EM Console, they need to set the Preferred Credentials for the web server node for "root" privilege if the server is listening at a port number below 1024. Otherwise, configure the standalone server to listen at a port number higher than 1024. 11.2 EM parses the HTTP Listener configuration file, httpd(s).conf, linearly. Because of this, directives such as 'Listen', 'IfDefine', 'VirtualHost', 'ResourceConfig', and 'Directory' are not supported (any values specified here will either be ignored or read as variables and will cause the discovery script to fail). To configure Apache and iAS for discovery by the EM Agent, use the following directives: 'Port' -- used to set the port number of the web server target 'Location' -- used to set the server status URL 11.3 Include files are ignored by the EM web server discovery script. The discovery script doesn't interpret any files in the HTTP Listener configuration file, httpd(s).conf, that contain the 'include' verb. 11.4 During the discovery process the Intelligent Agent parses the HTTP Listener configuration file, [httpd(s).conf] linearly. The last port # configured in the file (either through a port or listen directive) is the one discovered by the Agent. This port # will be used for HTTP Server or Apache up/down event. 12. Forms Server Manager 12.1 Installation and Configuration See section 13 of the Oracle Forms Developer Release 6i Online Manuals document for detailed instructions to install Forms support in the OMS Repository and configure the Intelligent Agents to be managed. 12.1.1 The Forms Server Manager component of an OMS installation includes SQL scripts which must be run against the OMS Repository before Forms can be managed through the EM Java Console. Bug 2290630 trac s the fact that these scripts are installed into a different directory than is documented in the Forms Online Manuals. Documented Directory $ORACLE_HOME/sysman/admin/createOEMFormsUser.sql $ORACLE_HOME/sysman/admin/createOEMFormsTables.sql $ORACLE_HOME/sysman/admin/dropOEMFormsUser.sql Actual Directory $ORACLE_HOME/sysman/admin/createOEMFormsUser.sql/createOEMFormsUser.sq

l $ORACLE_HOME/sysman/admin/createOEMFormsTables.sql/createOEMFormsTable s.sql/createOEMFormsTables.sql $ORACLE_HOME/sysman/admin/dropOEMFormsUser.sql/dropOEMFormsUser.sql 12.1.2 Section 13.5.2 of the Forms Online Manuals, referring to the Intelligent Agent node to be managed through EM, notes that "On Windows NT, the user needs to be granted the 'Log on as a service' user right in the User Manager". The same privilege must be granted on Windows 2000 Agents or else any jobs submitted will fail with a VNI-2015 error. 12.2 Restrictions 1. The Database name of the OMS Repository must exist in the tnsnames.ora file on the machine where you intend to run the Enterprise Manager console. 2. If there's more than one OMS Repository in the Database, and they're both managing the same node, Forms-specific changes made in one OMS will appear in another, because only one "OEM-Forms" user can be created per Database. 12.3 Known Issues 1. If a Forms listener startup job is created without attached environment variables which include the correct ORACLE_HOME, the listener will start up but EM will report the error "java.lang.exception: output from job lost" and you will not be able to manage this Listener Process from EM. If you experience this problem, stop the Forms Listener from the operating system and then add the appropriate ORACLE_HOME to the forms startup process before restarting. This issue is trac ed by bug 2091710. 2. When a new listener instance is created and started from the EM console, a "Listener successfully started" message is displayed but the status in the job history is "Failed" due to "Output to job xxx lost." This particular failure message can be ignored and the listener instance can be managed from EM. When attempting to manage an EM 2.2 Agent using the EM 9.2 Console and OMS, Forms target types will not show up in the Job and Event creation screens. To wor around this issue, edit the nmiforms.tcl file (found in the $ORACLE_HOME\networ \agent\config directory). In that file, calls to the methods "set Parameters" and "set ServiceType" require their parameters to be lower case: Original Parameters ORACLE_FORMS_LISTENER ORACLE_METRICS_SERVER ORACLE_METRICS_CLIENT Corrected Parameters oracle_forms_listener oracle_metrics_server oracle_metrics_client 12.4 Bugs Fixed in 9.2

* 1833908 NAMES INCORRECT FOR FORMS_LISTENER, METRICS_CLIENT, METRICS_SERVER * 1934577 "VNI-4030: INVALID TASK: NULL: NULL" WHEN STARTING FORMS LISTENER * 1943818 INTELLIGENT AGENT SCRIPT NMIFORMS.TCL CANNOT FIND ORACLE HOME INFO * 2019562 FORMS UP/DOWN EVENT FAILS WITH VNI-4002 UNKNOWN GATEWAY EXCEPTION * 2033891 NMIFORMS.TCL LOOKS FOR TOO MANY ORACLE HOMES * 2112086 INTELLIGENT AGENT SCRIPT NMIFORMS.TCL FAILS TO DISCOVER FORMS 4.5 13. Oracle Wor flow Manager 13.1 Before you can access Oracle Wor flow Manager through the Oracle Enterprise Manager Console, you must update the Wor flow Manager entry in the OEMClient.properties file with the port number on which your web listener accepts requests. This file is located in the $ORACLE_HOME/sysman/config subdirectory on your server. Open the OEMClient.properties file in a text editor and edit the following entry: /com/oracle/sysman/em/system/applications/oracle_apps_wfm/entrypoint= http://APACHE_HOST%:APACHE_PORT%/servlets/em/oam/wfm/wfmLogin The APACHE_HOST value is automatically set to the host name during the installation process. You must manually replace APACHE_PORT with the actual port number for your web listener.

14.1 Performance Manager 14.1.1 In order to collect dis statistics for a Windows NT host, you may need to enable dis statistics collection on Windows NT before using Performance Manager or Capacity Planner. This is done by typing the following command on the host to be monitored: DISKPERF -Y . Dis statistics will then be enabled the next time the system is restarted. 14.1.2 Due to a nown bug in JDK versions prior to 1.2.2, there is a memory lea when opening and closing each performance chart (Bug 682636). To reduce the impact of the memory consumption there are two things that can be done:

14.1.3 Using Performance Manager to monitor a standby database requires either the use of direct connect mode or the Oracle Agent version 9.2 or higher. 14.1.4 In order to enable or disable SQL tracing for a database session from the Top Sessions chart for an Oracle9i database, the database user used for monitoring must have been previously granted execute privilege on SYS.DBMS_SYSTEM (Bug 1746687). To do

* *

avoid constantly reopening and closing performance charts prior to closing a chart, clic on its title

14. Oracle Diagnostics Pac

this either: * login as SYS and grant "execute on SYS.DBMS_SYSTEM" to the user that will be running the charts * grant the user that will be running the charts the OEM_MONITOR role 14.1.5 When installing a 9i Agent on a machine running a pre-9i database, you must re-run a version specific copy of catsnmp.sql which is located in the ORACLE_HOME/sysman/admin/ directory of the 9i Enterprise Manager Client install. For example, if you are running Oracle Server release 8.1.7 on a machine and then install a 9i Agent, you must re-run the catsnmp_8i.sql script after installing the new Agent. This operation must be performed for each pre-9i database serviced by this Agent. Do not run the 9i version of the catsnmp.sql script against pre-9i databases. Failure to run the version-specific copy of catsnmp.sql would result in the error "DBA-01259: one of the views create by catsnmp.sql is missing from the target database. DBA-1260: Some clasess (sic) and charts will not wor due to previous error." when using Performance Manager or Capacity Planner. 14.1.6 In none English environment, in order to create the user defined chart, the user needs to connect to the database service through the Intelligent Agent. With the direct connection mode, which is the default of the Performance Manager, SQL commands that contain none English characters may cause ORA-933 "SQL command not properly ended" (Bug 2254612). To choose the connection through Intelligent Agent, clic [Connection Details] button in the Database Logon dialog, and clic [Connect through Intelligent Agent] button in the Connection Details dialog. 14.2 Capacity Planner 14.2.1 Due to a nown bug in JDK versions prior to 1.2.2, there is a memory lea when opening and closing each analysis chart (Bug 682636). To reduce the impact of the memory consumption there are two things that can be done:

14.2.2 There is no automatic refresh of analysis data during load passes: Once attached to a Capacity Planner data repository, there is no automatic refresh of the data available in the navigator once loads have occurred. It is necessary to disconnect and reconnect to the Capacity Planner data repository to refresh this view. 14.2.3 Services added at runtime are not saved. Any service added to the navigator at runtime is only visible in the navigator during that session. To ma e the service available for future sessions, it must be added to the Oracle Enterprise Manager discovery cache through the console. 14.2.4 The removal of lines or exclusion of points from a Capacity Planner Analysis is not saved as part of that analysis. 14.2.5 For a pre-defined analysis, the default date selection

* *

avoid constantly reopening and closing analysis charts prior to closing a chart, clic on its title

of one month of hourly data can not be changed. 14.2.6 If a chart contains multiple data sources and you remove a line for one of the data sources, the line for that data item is removed from all other data sources included in the chart. 14.2.7 There are two modes in Capacity Planner: Collection mode and Analysis mode. When creating or viewing charts in Capacity Planner Analysis mode, descriptions of the chart items are not available. This is because the descriptions are obtained from the Agent and there is no connection to the Agent when in Analysis mode. 14.2.8 The Performance Data Report capability has been removed from this release. To delete space consumed by previously running Performance Data Report collections, after connecting to the historical repository execute $ORACLE_HOME /sysman/admin/perfrptdrp.sql. 14.2.9 When installing a 9i Agent on a machine running a pre-9i database, you must re-run a version specific copy of catsnmp.sql which is located in the ORACLE_HOME/sysman/admin/ directory of the 9i Enterprise Manager Client install. For example, if you are running Oracle Server release 8.1.7 on a machine and then install a 9i Agent, you must re-run the catsnmp_8i.sql script after installing the new Agent. This operation must be performed for each pre-9i database serviced by this Agent. Do not run the 9i version of the catsnmp.sql script against pre-9i databases. Failure to run the version-specific copy of catsnmp.sql would result in the error "DBA-01259: one of the views create by catsnmp.sql is missing from the target database. DBA-1260: Some clasess (sic) and charts will not wor due to previous error." when using Performance Manager or Capacity Planner. 14.3 Oracle Advanced Events 14.3.1 There are certain advanced events that do not automatically clear: Database Alert, Data Bloc Corruption, Session Terminated, Archiver Hung, Data Gatherer Alert If any of these events trigger, and these conditions are manually resolved, the event does not automatically clear because there is no way to automatically detect the condition has been resolved. Hence, after resolving the problem for which the event fired, you need to manually clear the event as follows: - In the Events Alerts tab in the EM console, move the triggered event to the History tab. - In the History tab, delete this particular event occurrence. - These steps should clear the event, and also reset (i.e. change to green) any red flags in the group pane that may have been set in alarm due to the event. 14.3.2 Some advanced events are affected by the number of segments, datafiles, tablespaces, and extents in your database. These events include: Chun Small, Fast Segment Growth, Maximum Extents, Multiple Extents, Tablespace Full, Continued Row, Index rebuild. For these events, it is recommended that you reduce the number of objects referenced in the event you are registering.

So, in the example of the Maximum Extents event, rather than using the default of '*' or all segments, you could limit the event to cover the most important segments you need to monitor. 14.3.3 To monitor dis statistics on NT (e.g. the event tests under the Physical Dis folder), you may need to run "DISKPERF -Y" and restart the machine. 14.3.4 Contrary to what is stated in the help for the Database Alert event, this event test CAN be used with 9i Agents. 14.4 Web Server Monitoring 14.4.1 In Windows NT, the Total Servers metric that is displayed in the Server Utilization Chart may appear as a constant value. This will interfere with an event that is registered to trigger if the Total Servers metric exceeds a designated level since NT sees this value as always having been exceeded. (Bug 1307809) 14.4.2 PERL version 5 or higher is required in order to use the reporting features of the e-Business Management Tools. The user should ensure that PERL is included in the UNIX path. For configuration information, see the Installation Guide for Oracle Enterprise Manager with Change Management, Diagnostics and Tuning Pac s

15.1 Graphical Explain Plan and Outline Editor 15.1.1 If you select to show an Explain Plan report from an installed Enterprise Manager Console on a Windows NT Terminal Server or Windows 2000 Terminal Server machine, the HTML-based report may not be displayed (Bug 1961020) due to a generic web browser problem or may be displayed but with missing data (Bug 2261609). While there is currently no wor around for the latter issue, the former issue can be addressed by adding user.browser=<full_path_to_browser> to the ClientConfig.properties file located in the $ORACLE_HOME\sysman\config\ directory. 15.2 SQL Analyze 15.2.1 SQL Analyze uses a data repository that is shared with other Oracle Tuning Pac applications and multiple users can read the repository from multiple Tuning Pac applications. The last user who saves to the repository will override previous data. Because of this, you must be careful about performing repository operations from concurrently open Tuning Pac applications. A nown problem related to this (Bug 778225) involves the following series of steps: you open a SQL Analyze repository that contains a database service with SQL nodes. Before expanding the list of SQL nodes, you delete the same database service from the Oracle Expert navigator. If you then try to expand the SQL node list for the database service in SQL Analyze, an application error will occur.

15. Oracle Tuning Pac

15.2.2 The data results set retrieved by queries run from SQL Analyze can be viewed by using the Execution Results tool bar button. In order to provide fast access to this data, the results sets are cached in local memory by SQL Analyze. The number of rows cached can be controlled by the user through the SQL Analyze - View menu - Preferences - Execution Results setting. You should chec this setting to ensure that you have limited the number of rows to be displayed. Be aware that a high number of cached rows may cause the program to run out of memory. 15.2.3 SQL Analyze - File Menu "Open SQL" restrictions: SQL statements contained in SQL files opened with the "Open SQL" function can be imported into SQL Analyze only if each statement begins on a new line and is terminated with a semicolon. SQL files can not contain SQL comments beginning with REM. 15.2.4 If you load SQL statements from a file and there is an error in parsing one of the SQL statements, SQL Analyze will only show the statements that were successfully parsed prior to the error. It will not show any statements that followed the incorrect SQL statement. 15.2.5 In TopSQL, you have the option to filter-out recursive SQL statements. However, if you login as user SYS, TopSQL will filter-out your non-recursive SQL statements too. So if you login as SYS, do not select the option to filter-out recursive SQL statements. 15.2.6 SQL Analyze allows users to create an explain plan for a SQL statement run by any user. It does this by validating a schema name with an object name. If an object belongs to multiple schemas, it interacts with the user to resolve the schema name. However, public synonyms cannot be qualified. So if you are trying to get an explain plan containing a public synonym and you also have a table, view or a private synonym in your schema, the explain plan you get may not be the same as the one seen by other user. 15.2.7 The SQL Tuning Wizard "Rule of Thumb" tuning for queries containing MINUS and UNION does not support statements containing * in the column list. The wor around is to list the column names in the query. 15.2.8 SQL statements passed from the Diagnostics Pac to SQL Analyze (by using the Tune SQL menu item in a performance chart) may have the end portion of the statement truncated. If this occurs, drill down to full sql text chart from the originating performance chart and copy-paste the full SQL into the SQL Analyze window. 15.2.9 When launching either SQLAnalyze or Expert in standalone mode (without OMS), if you receive an error indicating that the registry variable USERNAME was not found in any of the property files, chec to ensure that the USERNAME Windows System variable is defined in your environment and should represent the authenticated Window user. (Bug 1531646) 15.2.10 When launching SQL Analyze or Oracle Expert from the Start Menu or command line in an NLS environment, if you encounter an ORA-01041 error, the wor around is to start the

application from the Enterprise Manager console (Bug 1714960). 15.3 Oracle Expert 15.3.1 It is currently possible to run more than one Oracle Expert session against the same repository. Oracle Expert does not have integral support for avoiding data conflicts between sessions. Do not run more than one session against the repository at any one time. However, if this is required, each PC session should access a different tuning session. 15.3.2 In order to use the Oracle Expert "Autotune" feature, you must first select a database from the Oracle Expert Navigator window. Once started, Autotune will continue to run until theAutotune menu - Stop function is invo ed for the selected database or the system is rebooted. Note that in order to use the Autotune feature, Oracle Expert must be started connected to the Oracle Management Server (Bug 1359935). 15.3.3 Do not attempt to use Oracle Expert to tune the SYS or System schema. 15.3.4 A schema collection will halt before completion if a table and cluster in the same schema have the same name (Bug #604088). 15.3.5 If a SQL statement is greater than 8K bytes, an error occurs when attempting to edit the Request that contains the statement. The error reads "Error while attempting to load attribute for display". The Request property sheet is still displayed, but the SQL text is not visible. 15.3.6 Oracle Expert does not currently support tuning of tables that use the Oracle8 partitioning feature. Partitioned tables will be ignored during data collection. 15.3.7 Oracle Expert does not support collection/tuning of Materialized Views. 15.3.8 Any wor load request containing SQL that utilizes a dblin to attach to a database is not validated against the database referenced by the dblin . 15.3.9 Importing an Oracle Expert tuning session (.xdl file) that contains extremely large (pages long) SQL statements can cause Oracle Expert to appear to hang and subsequently accessing these SQL statements from the view/edit window may not be possible (Bug 651722). 15.3.10 Source lines greater than 1024 bytes in import files may cause a syntax error. 15.3.11 When launching either SQLAnalyze or Expert in standalone mode (without OMS), if you receive an error indicating that the registry variable USERNAME was not found in any of the property files, chec to ensure that the USERNAME Windows System variable is defined in your environment and should represent the authenticated Window user. (Bug 1531646) 15.3.12 When launching SQL Analyze or Oracle Expert from the

Start Menu or command line in an NLS environment, if you encounter an ORA-01041 error, the wor around is to start the application from the Enterprise Manager console (Bug 1714960). 15.4 Tablespace Map and Reorg Wizard 15.4.1 The Reorg Wizard provides the option of choosing between an online or offline reorganization for certain types of objects. The following database privileges are required by the preferred credentials user in perform an online reorg of Oracle 9i tables: SELECT ANY TABLE, ALTER ANY TABLE, LOCK ANY TABLE, DROP ANY TABLE, CREATE ANY TABLE, and execute privileges on the dbms_redefinition pac age (either granted explicitly or granted through execute_catalog_role). 15.4.2 The Reorg Wizard does not currently support reorganization for the following objects: Hash partitions, List partitions, Somposite partitions, Subpartitions, Tables that contain columns of user-defined types, Indexes on columns of user-defined types, Function-based indexes, Domain indexes, XML object types, Dimensions, Streams and Tables that implement Advanced Queues. Partitioned tables that contain a LOB column can be reorganized on a per-partition basis, but operations that require reorganization of the entire partitioned object (such as the reorganization of a complete tablespace) can not be performed if the partitioned object contains a LOB column. Note that if you perform a reorganization that includes an object from this unsupported list, a diagnostics message will be displayed in the Impact Report alerting you of the unsupported object. 15.4.3 Using the Reorg Wizard to reorganize database objects containing long or long raw datatypes that exceed 32KB requires using the Oracle Agent version 8.1.7 or higher on the server where the object resides. 15.4.4 Note that if a reorg job fails while in process, the reorg operation can be recovered. In this case, there are two ways of dealing with the failure: * Correct the error at the destination database (for example, by increasing the size of a tablespace) and proceed with the reorganization. From the Enterprise Manager Console create a new job. To do this, right-clic on the failed job and select the Create Li e menu item. Then from the Create Job dialog clic Submit. The job will be resubmitted and will continue executing. * Undo the changes from the reorganization job. From the Enterprise Manager Console create a new job. To do this, right-clic on the failed job and select the Create Li e menu item. From the Create Job dialog select the Parameters tab. Change the parameters from 'agent false proceed_and_cleanup' to 'agent false revert' and submit the modified job. 15.4.5 If using a scratch tablespace to hold the temporary objects used in the reorganization, the scratch tablespace and production tablespace should be of the same management type; both should be either dictionary-managed or locally-managed. If they are not of the same type a diagnostics message will be displayed in Impact Report.

16.1 General 16.1.1 When you propagate a tablespace to a different database, Change Manager does not verify the existence of the directory specified for the tablespace's datafile(s), nor does it chec if any datafile in the tablespace is already in use by another tablespace. If the directory does not exist, the script will fail. Currently the impact report does not provide a warning in this case. The wor around is to ma e sure that the directory exists on the destination and to re-run the script. (Bug 643516) 16.1.2 If the target database of the change plan is prior to 9i and the database character set of the source and the target databases are multibyte character set (for example JA16SJIS) and UTF8 respectively, possible data truncation error of ORA-1401 "inserted value too large for column" during character data copy may not be detected properly. Wor around is to expand the size of the destination table column by 50%. (Bugs 1549576, 1623683) 16.1.3 For this release, multibyte user names are not supported as the preferred database connection credential. Please use user names which have only ASCII characters. (Bug 1314390) 16.1.4 You cannot launch the Clone Table and Data or the Compare DB Objects wizards in the context of the search results when the search is performed using the Find DB Objects tool from the console. These operations can be performed from several other contexts. (Bug 2250121) 16.2 Script Generation and Execution 16.2.1 If you generate a script, then change a script option (such as mapping or temporary tablespace), then execute the script, the application does not prompt you to regenerate the script. This means you could run the script without realizing the script option changes you requested were not in effect. Be sure to regenerate the script after changing script options. (Bug 685123) 16.2.2 During script execution, if the destination database crashes or the user interrupts execution in some situations, Change Manager may lose trac of the last step completed. If this occurs, an attempt to Undo the execution will not start with the last completed step. Should this occur, the following procedure will correct the problem: o Obtain the script ID from the script by editing the script and copying the long number in the line "set SCRIPTID nnnnnnnn". o At the destination database, in the schema of the user executing the script (that is, the user in the destination's preferred credentials), find the table VBZ$CHECKPOINT_SID_9I and examine the row whose script_id equals the script ID obtained above. o If the problem occurred while executing in the forward direction, decrement the value of last_step by 1. If the problem occurred while executing in the reverse direction (Undo) then increment last_step by 1. Commit the change. It should now be possible to continue with script execution or Undo. (Bug 782142) 16.2.3 For LOB columns stored in a dictionary-managed tablespace that are rebuilt using the ALTER statements, if the scratch tablespace is locally managed, then the LOB column's extent-related parameters are

16. Oracle Change Management Pac

16.2.4 When propagating a user and a number of objects owned by the user to a destination database that does not contain that user, the owned objects may be created in the wrong order. For example: o Pac age bodies and other source objects may be created before tables to which they refer, and will therefore be invalid when created. (However, they will be compiled automatically at their first use.) o Objects such as views that use a private database lin that is also propagated may be created before the database lin , resulting in possible failure of the script to execute. If this occurs, try creating the user object first in a separate change plan. (Bugs 2192617, 2192635) 16.2.5 If you rename a constraint and also change certain attributes of the constraint (such as RELY or No Validate), the resulting script will change the constraint name but will not modify the attributes. To wor around this problem, change the attributes in a separate change plan, if possible. (Bug 2185541) 16.2.6 Propagating a table with its data from a 9i instance to an 8i instance may fail if the table contains NCHAR or NVARCHAR2 columns and the character sets at the instances are mismatched. (Bug 2077303) 16.2.7 When cloning a table and its contents from the Clone Table and Data option of the Change Management popup menu in the OEM console, data will not get copied if the user goes through the Custom Propagate option without ma ing any changes to the Copy Data Data options (step 5 of the wizard) or the Copy Table Data options (step 6 of the wizard). For example, in step 5 the user can simply unchec and rechec the Copy Table Data chec box to ensure that data gets copied. (Bug 2305272) 16.3 Command Line Interface (CLI) 16.3.1 Currently you cannot use change plan names that have a $ in them, if you would li e to execute the script using the command line interface on solaris. The change plan name created by the quic propagate option always includes a $, so you will not be able to execute it using the command line interface. Be sure to use the custom propagate option instead of the quic propagate option so that you can specify the name of the change plan without the '$' symbol in it. (Bug 1715746) 16.3.2 When using the Change Manger command line interface (either ocm or oemapp ocmcli) on Win '98, parameters that are strings with embedded spaces must be enclosed by '\"' (bac slash double-quote) and not just '"' (double-quote) so that they are recognized properly as a single parameter. For example: ocm capture \"baseline name with spaces in it\" (bug 1865274) 16.4 Currently Unsupported Database Features and Attributes Note: The "Objects Supported by Oracle Change Management Pac Applications" section of the Getting Started with the Oracle Change Management Pac manual lists the database objects supported in this release of the Oracle Change Management Pac . All features for the listed database object types are supported except as described in this

not preserved when the column is moved bac tablespace. (Bug 1094357)

to the original

section. This section describes: o Unsupported database features o Partially supported database attributes o Unsupported database attributes Future releases will provide support for these Oracle features and attributes. 16.4.1 Unsupported Database Features The database features that are currently not supported are listed below. o Unsupported object-oriented features: object tables nested tables object views o Snapshots that are not read-only o Consumer groups (belonging to users and to roles) o Proxy users o Hash partitions, list partitions, composite partitions, and subpartitions o Undo tablespaces o Java classes, sources, and resources o XML features + XML Type tables + XML Type views + XML Type functions + Indexes on XML Type tables + XML Type columns o Dimensions o Streams If you create a change plan that references an object with unsupported features, a diagnostic message will be displayed when you generate a script to alert you to the unsupported feature. An object with unsupported features can become part of a plan when you: o create an exemplar for an object with any of the unsupported features o request an operation that forces the dropping and/or creation of such an object (for example, you as to rename a schema that contains an object table) o create a directive for an object with any of the unsupported features or that attempts to modify the object to have any of the unsupported features Create Baseline and Compare Database Objects applications will capture objects and compare them, but some attributes of the unsupported features, such as nested tables, are ignored. 16.4.2 Partially Supported Database Features Some attributes are supported except that you cannot compose a directive that refers to these attributes. Thus, you can use Create Baseline and Compare Database objects applications to capture and compare these attributes and you can use exemplars to reproduce these attributes elsewhere. However, you cannot modify these attributes using a directive. o Partially supported database attributes: + for a table constraint: [NOT] DEFERRABLE EXCEPTIONS INTO ?table> + bitmapped join indexes and function-based indexes are not directly supported (that is, you cannot create a change request for one of these objects). They also are not supported for operations that drop and re-create them.

However, if one of these indexes is stored in a tablespace that is being dropped and re-created (e.g., renamed or modified), the script will properly move the index out of the tablespace before the operation, and bac into it afterwards. 16.4.3 Unsupported Database Attributes Some database attributes are unsupported in this release of Oracle Change Management Pac , which means: o These attributes are not captured by Create Baseline application o Compare Database Objects application does not detect differences between objects that include these attributes o When reproducing an object that includes these attributes, the new object will not include these attributes o When dropping and recreating an object that includes these attributes, (for example, to eliminate a table column) the object will not be properly recreated The unsupported database attributes are: o for a database lin : SHARED AUTHENTICATED BY o CREATE SNAPSHOT statement CLUSTER clause table partitioning information o CREATE SNAPSHOT LOG statement table partitioning information

17.1 Performance Manager 17.1.1 Version 9i of Performance Manager has a new capability called the "Direct Connection mode" for connecting to remote targets that do not have an Intelligent Agent installed. Unfortunately, the Direct Connection mode of operation is not supported for the Concurrent Manager target. If you try to access a Concurrent Manager target and you get an error, change the connection mode from "Direct Connection" to "Agent Connection." This can be done either through the "Connection Details" button on the logon screen, or by right-mouse clic ing on the target that appears in the navigator tree. Trying to use the Direct Connection mode of operation will result in an error message, and may even cause Performance Manager to hang. (Bugs 1697293 ? 1775279) 17.1.2 The "New Chart" button (oval button with arrow found in upper right-hand corner of a chart) has many problems when used in Oracle Applications charts. It is recommended that you drill down to related charts by directly highlighting a record and invo ing the right-mouse menu. (Bug 1711914 ? 1845027) 17.1.3 Context sensitive online help is not available in Oracle Applications charts. For a description of a chart, go to the Help menu, select "Search Help" and type in the name of the chart. (Bug 1845053) 17.1.4. Information in bubble help for Applications resources is not available. When the mouse hovers over a resource, the following message appears, 'No tooltip available. Select item and view help via

17. Oracle Management Pac

for Oracle Applications

Selected Item from Help menu.' This is not supported for Applications resources. (Bug 1630422) 17.1.5 This release of the product has several limitations against Oracle Applications instances running on Real Applications Clusters (Oracle Parallel Server). For instance, all charts relating to the form sessions and database sessions will only display sessions connected to the OPS instance on the node which the Intelligent Agent is connected to. The same is true for the "Kill Session" command. (Bugs 1180573 1180563). 17.1.6 When you ill a database session from the "Session Details" chart, it ta es some time before the session actually gets terminated. This gives the impression that you can ill the same session multiple times. This is the way the database behaves and is not a bug. (Bug 1179061) 17.1.7 Some drilldown charts may show fewer records than their source charts indicate. If you notice such discrepancy, clic on the Set Options button on the tool bar and go to the Options tab to see if the data source limit is set to a low value. Increase the data source limit and clic on the Show Chart button to see the new results. (Bug 1154985) 17.1.8 Some of the change options in Performance Manager do not wor . Currently the cartridge ignores changes in these options once the collection is started and the chart is being displayed, thus the user will continue to see the chart with the options as set at the start of the collection. The following change options will not wor in PM: - The max # of rows displayed - The "view by" or "sort by" option (where available) In order to change these options, close the chart, change the options, and then relaunch the chart. (Bugs 1729868 and 1691508) 17.1.9 When you drill down to the SQL statement of a running request or an active form session, the SQL lines may come up in reverse order. This can be corrected by clic ing on the column header and reversing the sort order. (Bug 1844998) 17.2 Jobs and Events 17.2.1 The "Load Data into Concurrent Processing Tuning Assistant Repository" job doesn't complete when submitted to an Oracle Applications instance using tnsnames. You may receive these error messages: o smamp-8031 Connecting to the application schema APPS/?pwd>@JIGNAZI-SUN-AP505DBS o smamp-8008 failed to connect to database using APPS/?pwd>@JIGNAZI-SUN-AP505DBS To avoid these errors and for the job to wor , there needs to be a tnsnames.ora entry on the agent node AND the CPTA repository node into which the data will be copied. This is because a dblin will be created between the CPTA repository and the Applications database. (Bug 1687471) 17.2.2 The "Load Data into Concurrent Processing Tuning Assistant Repository" job can only be run against a 9.0.1 agent. If you try to register it against an earlier agent, registration will fail, although you will not receive a descriptive error telling you why.(Bug 1675918)

17.2.3 You can only register the Unresponsive Manager event against a 9.0.1 or later version of the Intelligent Agent. If you try to register this event against an earlier version of the Agent, the registration will fail without an error message. (Bug 1734313) 17.2.4 You will not be able to register Concurrent Manager events against a group target. You can only register them against individual Concurrent Manager targets. (Bug 1756802) 17.2.5 The Kill Session fixit job for v8.1.7 and earlier agents will trigger under both alert AND warning conditions. If this is not the desired behavior, you can register two separate events, one with the threshold set at the "warning" level and another with the threshold set at the "alert" level. You would then associate the Kill Session fixit job with the second event. Note the two events must have different names and parameter values. When using the Intelligent Agent 9.0, the job will only execute at the alert threshold. (Bug 1093188) 17.2.6 In 8i, if the Concurrent Manager goes down because of database problems, a "Startup Concurrent Manager" fixit job will fail to complete because the Concurrent Manager cannot operate without a fully functioning database available. In this case you would register a fixit job against the database up/down event and use an OS script to start up the Concurrent Manager after the database has been successfully restarted. With 9i, the Startup Concurrent Manager job will sleep for awhile and try again if it cannot connect to the database. After the database fixit job has brought the DB bac up, the next attempt to start the concurrent manager should succeed. (Bug 1328567) 17.2.7 The Intelligent Agent must be able to read the Applications environment variables in order for the dis -free event to wor . Two things must be present for this to wor . First, the OS user the Intelligent Agent executes as must have the Oracle Home of the Intelligent Agent defined in its environment. Secondly, the oapps.ora file must have an entry for an Oracle Applications environment file (e.g. appsora.env) that sets the values of the following Applications environment variables: APPLCSF, APPLLOG, and APPLOUT. (Bugs 1698906 ? 1764266) 17.2.8 Event filtering in the Applications Pac has a different model than event filtering for the database. You cannot use "=", "LIKE", or "IN" operators in any of the Concurrent Manager events. You can only enter valid Oracle Applications names and Concurrent Program names WITHOUT any operators. Also, you do not need to use any quotes around the values. (Bug 1353553) 17.3 Concurrent Processing Tuning Assistant 17.3.1 The slide bar at the bottom of the Concurrent Manager Utilization report is for the utilization value. Even if you change the data displayed through the drop down list, the coloring will be based on the utilization value. This is by design. The same is true for the Waiting Requests by Hour report. (Bug 1018227) 17.3.2 After launching the Concurrent Processing Tuning Assistant (CPTA) from command line or start menu and clic ing the help button on the login screen, the online help describes connecting to an Applications instance directly, but doesn't address using the OMS. Using the OMS requires the same credentials as console: administrator,

password, and management server. By using OMS, all discovered concurrent managers are populated on the CPTA navigator tree. If no concurrent manager is discovered, an alert will remind users to add one to the CPTA navigator tree manually. Additionally, users can connect to a repository li e a real Applications instance. (Bug 1628575) 17.3.3 The Concurrent Manager Utilization values can be slightly off if you have frequently repeating requests that reuse request IDs. This should be very rare. (Bug 1328428) 17.3.4 If you get a SQL Exception error when displaying any of the reports, that means the necessary Applications patch has not been applied to the Applications database. Please ma e sure you have Applications patch #1302931 applied before running any of the tools from the Management Pac for Oracle Applications. (Bug 1352872) 17.3.5 When printing, some labels may overlap (Bug 925479) 17.3.6 To use Coucurrent Tuning Processing Assistance in NLS environment, please set the same LANG parameter between OMS environment and Client environment. (Bug 1766497) 17.3.7 If you get an error message when trying to save a report to dis , chec to see if you have write privleges to the destination directory. This may not be obvious because the product only provides a generic error message (Bug 1788539) 17.3.8 The ability to store concurrent processing historical data in a separate database is not currently supported for 11i or 11.5.x versions of Oracle Applications. While the "Load Data into Concurrent Processing Tuning Assistant Repository" job will succeed, and the CPTA client tool can wor against this database, the data will not be accurate. This will be addressed in a future patch. For the time being, customers who are running Oracle Applications version 11.5.x must use CPTA in a direct connect mode. (Bug 2221774, 2221789, 2221818) 17.4 Console 17.4.1 There's a typo in oapps.ora. The sample apps environment file entry in oapps.ora is incorrect. The example should read $APPL_TOP/APPSORA.env. (Bug 1609995) 17.4.2 The Intelligent Agent prior to version 8.1.6 was unable to discover databases installed as part of the Oracle Applications Rapid Install. The wor around is to find the listener.ora file used by the Applications database, note the location of the "ifile=" entries, and replace those entries with the contents of those files. Bring down and restart the Intelligent Agent. You should now be able to discover the Oracle Applications databases. (Bug 931511) 17.5 Capactiy Planner 17.5.1 Even after turning off all collections on a Concurrent Manager target, you may still see a green dot on the Completed Requests by Status chart. This is a display bug that will disappear if you exit Capacity Planner and reconnect. (Bug 1063000)

17.5.2 result switch invo e

Trying to get online help for items in the navigator tree may in a null pointer exception. If you encounter this problem, to the Collection Tab at the bottom of the navigator tree and online help for the same item. (Bug 1692695)

17.5.3 When a Database instance and a Concurrent Manager instance have the same name, the metric collections for these targets may appear under the same container class. If you cannot find any Concurrent Manager collections, try loo ing under the Database instance in the navigator with the same name (Bug 1857992)

18.1 New Features in This Oracle Standard Management Pac Release The Getting Started with the Oracle Standard Management Pac manual was not updated for this release. This section describes the new features for the change management applications (Create Baseline, Compare Database Objects, and Change Manager) in this release. 18.1.1 Less powerful privileges and roles are needed to create a baseline or comparison in an Oracle 9.x database: In previous releases users needed the SELECT ANY TABLE database privilege to create a baseline or comparison. With this release, to create a baseline or comparison in an Oracle 9.x database, you must have the SELECT ANY DICTIONARY privilege. Or, you must have the SELECT ANY TABLE privilege for a database with database parameter 07_DICTIONARY_ACCESSIBILITY=true. See Oracle9i Database Administrator's Guide for the implications of setting the 07_DICTIONARY_ACCESSIBILITY parameter. Due to these ramifications, Oracle recommends that you use SELECT ANY DICTIONARY, instead. 18.1.2 Less powerful privileges and roles are needed to create a baseline or comparison in an Oracle 8.x database: In previous releases users needed the SELECT ANY TABLE database privilege to create a baseline or comparison. With this release, to create a baseline or comparison in an Oracle 8.x database, you must have either the SELECT ANY TABLE privilege or the less powerful CM_SELECT_ROLE role, which is explained in the next note. 18.1.3 Defining and granting the CM_SELECT_ROLE role in Oracle 8.x databases: To create the CM_SELECT_ROLE in an Oracle 8.x database, log in as SYS and execute the ocmselectrole.sql script at the database. The ocmselectrole.sql script is located in the $ORACLE_HOME/sysman/admin directory where Oracle Enterprise Manager is installed. After the CM_SELECT_ROLE is created in a

18. Oracle Standard Management Pac

17.5.4 The Enterprise Manager reporting framewor is not capable of showing historical trending reports for concurrent managers. To wor around this problem, you can create a database or host analysis in Capacity Planner, save it, overlay the concurrent manager collection of your choice, then remove the original database or host from the analysis and save it bac to the repository. Although this analysis will appear under the database or host target you originally created the analysis for, you will see the concurrent manager collection that you specified. (Bug 2247629)

database, it can be granted to users that need to create baselines or comparisons that access objects in that database. Note that if while performing change management operations you receive error messages about objects that do not exist, these messages may mean that you lac the appropriate privileges to access those objects. 18.1.4 Index-organized tables are fully supported. In previous releases, the change management applications did not provide full support for index-organized tables. In this release, the change management applications provide full support for index-organized tables. 19. Enterprise User Security Management 19.1 Command Line Interface The Enterprise Manager Configuration Guide chapter 9 describes a Command Line Tool feature for Oracle Enterprise User Security Management. This feature is not available with Oracle 9.2 and will be made available in future releases. 20. Oracle Directory Manager The Oracle Directory Manager (ODM) provides an easy to use graphical user interface for administering data and policies in Oracle Internet Directory. It can be launched through command-line invocation (oidadmin) 20.1 Administering Older Versions of OID with oidadmin Version 9.2.0.1.0 The version of ODM shipped with the 9.2.0.1.0 release will only wor with the following versions of the Oracle Internet Directory Server: 2.0.4.x, 2.0.5.x, 2.0.6.x, 2.1.1.x, and 3.0.1. 20.2 Administering Third-Party Directories Using oidadmin Administering LDAP directories other than Oracle Internet Directory with 'oidadmin' is not supported. 20.3 Oracle Directory Manager Limitations 20.3.1 ODM CANNOT BE USED TO ADD OBJECT CLASSES TO EXISTING ENTRIES OID allows existing entries to be extended (i.e., support additional attributes) by adding object classes to their objectClass attribute. This form of schema extension can not be done using ODM, only via command line tools, and must never create schema inconsistencies (e.g., where an attribute does not contain a value where one is required). Typically, so as to avoid such inconsistencies, auxiliary object classes with only optional attributes are used exclusively for extending existing entries in this way. 20.3.2 MOVING SCROLLBAR ON THE HELP WINDOW SOMETIMES CRASHES ODM

(bug 2162732) ODM online help scrolling can cause the crash of the jvm in Simplified Chinese environment. This problem is seen only on some machines. If you hit this problem, only wor around is to replace the contents of the chinese help to english in the jar file. The steps need to be followed to achieve this are: cd /tmp jar xf $ORACLE_HOME/ldap/oidadmin/osdadminhelp.jar mv -f oracle/ldap/admin/help/ldap/* oracle/ldap/admin/help/ldap_zh_CN/ mv -f $ORACLE_HOME/ldap/oidadmin/osdadminhelp.jar $ORACLE_HOME/ldap/oidadmin/osdadminhelp.jar.ba jar cf $ORACLE_HOME/ldap/oidadmin/osdadminhelp.jar oracle jar tf $ORACLE_HOME/ldap/oidadmin/osdadminhelp.jar