Oracle Application Management Pack for Oracle E-Business Suite User's Guide

Skip Headers

Contents

Known Product Limitations

Use of the native Oracle Enterprise Manager (EM) patch mechanism to apply core technology patches (Developer Forms, Application Server, Database or other standalone technologies) against Oracle E-Business Suite managed targets should NOT be done under any circumstances.

While EM can be used to apply such patches to standalone installations of Developer Forms, Application Server and the RDBMS products, when these components are part of an Oracle E-Business Suite environment (installed at the same time via the Rapid Install Wizard), they must not be patched via Oracle Enterprise Manager.

Failure to acknowledge this caveat could result in unrecoverable system status.
Start and Stop features present in some of the Enterprise Manager UI pages should NOT be used against individual Oracle E-Business Suite sub-targets. One example is starting and stopping the Oracle E-Business Suite database. While Oracle Enterprise Manager has no problems starting and stopping individual standalone product services, doing the same with Oracle E-Business Suite components will produce unexpected and inconsistent results.

The Oracle E-Business Suite start and stop scripts are documented in the Oracle E-Business Suite System Administrator's Guide Documentation Set and only those scripts as provided within the Oracle E-Business Suite environment should be used. There are certain services that may be controlled from within the Oracle Application Manager UI (which is tightly bundled with the Oracle E-Business Suite).
At this time, Shared Agent Configurations are limited to Discovery and Monitoring of Oracle E-Business Suite systems. Cloning using the Oracle Application Management Pack for Oracle E-Business Suite in a Shared Agent environment is currently not certified. Shared Agent configurations are currently not supported with the Applications Management Pack on Windows platforms.
The only mechanisms for cloning an Oracle E-Business Suite system from within the Oracle Enterprise Manager UI are the following: the provided cloning flows as discussed within the cloning chapters of this guide (both basic cloning and Smart Clone, Chapters 6 and 7), or alternatively as described in the following Oracle E-Business Suite documents on My Oracle Support: Knowledge Document 230672.1, "Cloning Oracle Applications Release 11i with Rapid Clone", and Knowledge Document 406982.1, "Cloning Oracle Applications Release 12 with Rapid Clone".
Cloning of Oracle E-Business Suite systems which use a shared APPL_TOP is certified with the Smart Clone deployment procedures only.
Customizations of the seeded cloning procedures are not supported. However, existing cloning procedures may be copied and those copies then edited.
In cloning, data files without the ".dbf" extension are currently not supported. Ensure that the data files on the source system database have the ".dbf" extension.
For hot mode cloning, the option to select only dbtechstack files has been disabled and is not supported.
Cloning a source system with multiple applications nodes that share the file system is not supported in the basic cloning procedures described in Chapter 6.
For basic cloning procedures: Rapid Clone does not support cloning with symbolic links. Therefore, on the HP-PA platform with an Oracle E-Business Suite instance on any database: For a Source-to-Image or a Source-to-Target clone procedure, remove the symbolic link present inside the database ORACLE_HOME on HP-PA:
```
<DB_OH>/jdk/jre/lib/PA_RISC/hotspot
```
and replace it with absolute files.

Note: The above step is not necessary for Smart Clone procedures.
Recording and playback for Oracle Forms-based beacon tests is not certified with Oracle E-Business Suite (Releases 11i and 12).
In discovery and monitoring, Oracle Application Management Pack for Oracle E-Business Suite does not support multiple Oracle E-Business Suite instances with the same name across different hosts on a given Oracle Management Server; that is, instances are differentiated only by the Oracle System Identifier (SID) and not the CONTEXT_NAME values.
In the Configured Components page, the Oracle Workflow Background Engine's status, if shown, will show as Up if the background engine's status is Pending or Up.