Siebel Installation Guide for UNIX > Uninstalling Siebel CRM > Uninstalling Siebel CRM Server Modules >

Rolling Back the Siebel CRM Server Modules


Use the following procedure to roll back the current release of the Siebel Enterprise Server software (Siebel CRM modules, such as Siebel Server or Siebel Gateway) on a single computer or operating system instance and revert to the previously installed software version. You can do this only when you have installed the current release as a migration installation for an existing installation of a prior release of Siebel CRM.

NOTE:  To be able to roll back the current release and revert to a previous version, you must have retained the backup directory to which the previous installation was moved during the migration installation. During that installation, if the original Siebel Enterprise Server installation directory was named ses, for example, then it was renamed from ses to ses_pre17.0.

NOTE:  This topic describes only rolling back a migration installation of Siebel CRM 17.0, not rolling back an installation of Siebel CRM 18.12 Update. If you installed Siebel CRM 18.12 Update on top of an installation of Siebel CRM 17.x, then you can uninstall Siebel CRM 18.12 Update. For more information, see Installing and Uninstalling Siebel CRM 18.12 Update.

This topic is part of Uninstalling Siebel CRM Server Modules.

To roll back the Siebel CRM server modules

  1. Review all of the information in About Uninstalling Siebel CRM, particularly the requirements and limitations.
  2. Verify that the renamed original installation directory, such as ses_pre17.0, exists.
  3. Stop all the running processes of application containers, which were installed and started during migration installation. You can do so by following the method described for Microsoft Windows or UNIX operating systems.

    For more information, see Stopping and Starting the Siebel Application Container.

  4. Stop the Siebel services for the Siebel CRM 17.0 installation.
  5. You must use the correct rollback uninstallation method for your situation, as follows. For more information, see Requirements for Uninstalling Siebel CRM.
    • If you had originally installed Siebel CRM 8.1.1 (using the InstallShield installer) and are now rolling back to Siebel CRM 8.1.1 through Siebel CRM 8.1.1.7, then use the Oracle Universal Installer uninstallation option to uninstall Siebel CRM 17.0. Follow the procedure described in Uninstalling the Siebel CRM Server Modules, but do not remove configuration data. After performing this task, go to Step 12. (Step 7 through Step 9 do not apply in this case.)
    • If you are rolling back to another prior release of Siebel CRM, then use the manual steps that follow. Go to the next step. (Step 7 through Step 9 apply in this case only.)
  6. Delete the Siebel Gateway Name Server service using one of the following commands:
    • Windows. SIEBEL_ROOT\gtwysrvr\bin\siebctl.exe -S gtwyns -d
    • UNIX. SIEBEL_ROOT/gtwysrvr/bin/siebctl -S gtwyns -d
  7. Delete the directory representing the current installation of Siebel Enterprise Server for the current release. For example, if the directory name is ses, then delete this directory.
  8. Rename the backup directory representing the previously installed software to use the original installation directory name for Siebel Enterprise Server. Rename the original (renamed) directory, such as ses_pre17.0, to ses (depending on your original installation directory name).
  9. If you rolled back to Siebel CRM 16.x, Siebel CRM 15.x, Siebel CRM 8.1.1.8 or later, or Siebel CRM 8.2.2.x, then verify the version number by using the opatch command, as described in Verifying Installation for Siebel CRM.
  10. Open the file SIEBEL_ROOT/gtwysrvr/bin/gateway.cfg in any text editor and make a note of the port number mentioned in the value for the GatewayConnect parameter. You will replace the GATEWAYPORT string in the command mentioned in Step 11 with this port number.
  11. Create the Siebel Gateway Name Server service using one of the following commands:
    • Windows. SIEBEL_ROOT\gtwysrvr\BIN\siebctl.exe -h SIEBEL_ROOT/gtwysrvr -S gtwyns -a -g "/f SIEBEL_ROOT\gtwysrvr\ADMIN\siebns.dat /t GATEWAYPORT /c SIEBEL_ROOT\gtwysrvr\bin\gateway.cfg" -q
    • UNIX. SIEBEL_ROOT/gtwysrvr/bin/siebctl -r SIEBEL_ROOT/gtwysrvr -S gtwyns -a -g "/f SIEBEL_ROOT/gtwysrvr/sys/siebns.dat /t GATEWAYPORT /c SIEBEL_ROOT/gtwysrvr/bin/gateway.cfg" -q
  12. Restart the Siebel services.
  13. Run the Siebel Configuration Wizards, as necessary, to perform any required configuration tasks.

    NOTE:  You must use the Configuration Wizards for the version of the software that you rolled back to. Additional requirements apply to the post-rollback environment

  14. If Oracle Configuration Manager was not configured before you performed a migration installation of Siebel Enterprise Server, then, after a rollback to the original installation, you must configure this instance of Oracle Configuration Manager manually in order for it to function properly.
Related Topics

Installing Siebel CRM Server Modules

Verifying Installation for Siebel CRM

About Uninstalling Siebel CRM

Process of Removing Configuration Data

Siebel Installation Guide for UNIX Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.