Uninstall enterprise manager

Use the install -e command to uninstall the Enterprise Controller software components from your system. When complete, the install script indicates that the Ops Center Enterprise Controller has been uninstalled. Click Next. The Enter Server Credential pane is displayed. Enter the access credentials using the following fields: SSH Username — Enter either the root user, or the name of the non-root administrative user to use for ssh access.

The Summary pane is displayed. Click Close to close the Unmanage and Delete Assets wizard. Unconfiguring and Uninstalling a Proxy Controller Unconfiguring and uninstalling a Proxy Controller breaks its connection with the Enterprise Controller and removes the Proxy Controller software. Note: The co-located Proxy Controller that is installed with the Enterprise Controller cannot be uninstalled without uninstalling the Enterprise Controller.

Unconfiguring an Enterprise Controller Unconfiguring an Enterprise Controller removes user, authentication, and configuration data and unregisters the Enterprise Controller from Oracle. Click Unconfigure in the Actions pane. A confirmation page is displayed.

Click Unconfigure. The Enterprise Controller is unconfigured. Restore file system configuration. Remove users. Uninstall application packages. Run preremove tasks.

Uninstall Expect. Uninstall IPMI tool. Destroy database. For information on the support for -action drop and -action dropall, see Table The -action drop command drops all the schemas and provides a confirmation message.

If the action was unsuccessful, then it lists all the entities that could not be cleaned or dropped. For example, X schema is not cleaned, synonyms are not cleaned, tablespaces are not cleaned. In this case, rerun the command. If you do not have RepManager, or if you want to manually clean up the leftover entities, then see My Oracle Support note Do not use the one in database home because it cannot remove the Enterprise Manager schema completely.

Manually delete the data files mgmt. The process cannot access the file because it is being used by another process. Deinstall the components in the order described in this procedure. Otherwise, the installation wizard displays an error. You can invoke the installer even from the directory where you downloaded the software. When you run runInstaller -help , you will see the option -nowarningonremovefiles listed.

This option is currently not supported and has no effect even if you use it. If you are deinstalling the entire Enterprise Manager system with or without the Management Repository , then deinstall all the plug-in homes, including the OMS and Management Agent plug-in homes. On the Inventory screen, select the sbin home, and click Remove.

Manually download and install JDK 1. If you already have this supported version, then you can reuse it. Once the Management Repository is deinstalled from the database, you can reuse the empty database for any other purpose.

Only the Enterprise Manager schema is removed from the database, but the physical files or the software binaries of the database software will continue to remain on the host.

The steps outlined in this section do not deinstall, remove, or roll back any of the patches applied on the database. You must manually remove its contents. You must deinstall the Management Agent as described in Chapter 24 , and manually remove the contents of the shared location configured for Oracle BI Publisher. Copy the deinstallation script from the Oracle home of the OMS host to a temporary or stage location.