Requirements for Uninstalling Siebel CRM

This topic is part of About Uninstalling Siebel CRM.

Uninstallation of Siebel CRM software is subject to various requirements. The following requirements apply to uninstalling Siebel CRM software:

Use documented methods. To successfully uninstall, you must use the supported methods documented in this chapter and observe all of the requirements and limitations that apply for uninstalling each module. Review this entire chapter before you uninstall any software.
Before a full uninstallation, you must remove configuration data. For Siebel CRM server modules, including Siebel Server, Siebel Gateway, Siebel Application Interface, or other modules that were previously configured using Siebel Management Console, you must perform tasks to remove the configuration data before you uninstall the Siebel software. For detailed information, see Process of Removing Configuration Data.
You must have the required access. When you uninstall an instance of a Siebel CRM server module, you must either be the same user or be a user in the same group as the user who performed the installation. This requirement applies to both full uninstallation and restoring a prior installation.
Clustered nodes present special requirements. Clustered nodes present special requirements that might change part of the installation and uninstallation process from what is described in this guide. Siebel Gateway clustering includes such requirements, as noted in Changing the Primary Nodes for a Siebel Gateway Cluster.
Do not delete installation directories until you have performed a full uninstallation. Do not delete the installation directories for any Siebel CRM module until after you have performed a full uninstallation of the module. After a full uninstallation has completed successfully, you might have to restart your computer. Afterwards, you can safely delete the remaining directories. (Do not delete any installation directories after you perform an uninstallation as part of restoring a prior installation.)
Siebel CRM modules must use the same version after restoring an installation of a prior version. If you restore a previously installed version of Siebel Enterprise Server and SWSE, then you must also perform a similar process for all of the other Siebel CRM modules sharing the same Siebel Enterprise and Siebel database. After restoring the prior installation, see the documentation that applies to your currently installed Siebel CRM software version for information about this version.
To restore a prior release, you must have retained the previous installation. If you installed the current release as a migration installation from Siebel CRM 16.x or earlier, then the existing installation directory was renamed. You must retain this installation directory in order to be able to restore the version that it represents. For information about restoring or rolling back to earlier releases, see the applicable Siebel Installation Guide for your operating system for the release you are restoring.
After restoring a prior release, you must restore the Siebel Repository. New functionality and bug fixes might no longer be available after restoring a prior release. After you restore a prior release, you must remove any configuration changes and restore the Siebel Repository and the Siebel Repository file (SRF), where applicable, to the state when you first installed the current release. (SRF files are applicable only to releases prior to Siebel CRM 17.0.)
Note: After you installed the current release as a migration installation, you would have used the Incremental Repository Merge feature to update the Siebel Repository and to make other Siebel database changes. For more information about Incremental Repository Merge, see Siebel Database Upgrade Guide.
After restoring a prior release, you must re-enable the applicable services. After you restore a prior release, the Siebel Server service and the Siebel Gateway Name Server service are disabled and must be re-enabled.
After restoring a prior release, refer to earlier versions of the documentation. After you restore a prior release, you must refer to the documentation that applies to the Siebel CRM version that you restore. You can find the Siebel Installation Guide for your operating system for prior releases on the Siebel Bookshelf for each release.
After restoring a prior release, verify the software version. After restoring a prior release, verify the version number of the installed software that you restored. See the documentation that applies to your new effective version. See also Verifying Installation for Siebel CRM and related topics.
After restoring a prior release, you must restore previous required versions of third-party software. After restoring a version prior to Siebel CRM 17.0, you must restore installed third-party (or non-Siebel Oracle) software to applicable prior versions supported for the version of Siebel CRM that you are restoring, where necessary. For supported versions of third-party software, see the Certifications tab on My Oracle Support.
After restoring a prior release, you must reconfigure SWSE. After restoring a version prior to Siebel CRM 17.0, you must reconfigure the SWSE. For more information, see Additional Tasks for Migration Installations and About Configuring Siebel CRM.
After restoring a prior release, configure Oracle Configuration Manager (if necessary). If Oracle Configuration Manager was not configured before you performed a migration installation of Siebel Enterprise Server, then, after restoring the original installation, you must configure this instance of Oracle Configuration Manager manually in order for it to function properly.

The following recommendations apply to performing a full uninstallation:

Uninstall Database Configuration Utilities only after backing up files. Before you uninstall an instance of Siebel Enterprise Server that includes the Database Configuration Utilities and Siebel Server, it is strongly recommended that you back up relevant files, such as summary.html and summary.txt in the SIEBEL_ROOT\dbsrvr directory and the files in the SIEBEL_ROOT\siebsrvr\log directory.
Uninstall Database Configuration Utilities only after removing configuration data. Before you uninstall the Database Configuration Utilities and the Siebel Server it is installed with, it is strongly recommended that you first remove the Siebel Enterprise configuration or remove both the Enterprise and the Siebel Gateway.
Uninstall Oracle Database SE2 before you perform a full uninstallation for Siebel Web Client. If Oracle Database SE2 was installed for use with Siebel Web Client, and you plan to uninstall Siebel Web Client, then it is recommended that you first uninstall Oracle Database SE2. For more information, see Uninstalling Oracle Database XE.

Related Books

Siebel Database Upgrade Guide

Related Topics

Related Books