Uninstall OpenText Dimensions CM

Introduction

The Dimensions CM installer creates uninstaller files in the directory _uninst_maintlocated one level up from the Dimensions CM root directory. A record of the installed products is also created in the directory /var/opt/serena/inventory. To uninstall Dimensions CM components, you must use these uninstaller files.

Note: It is good administrative practice to regularly back up the files in /var/opt/serena/inventory.

During uninstallation, Java executable files are installed that enable you to run the uninstaller in either GUI mode or "dumb-terminal/VT100" mode. GUI mode is the default, VT100 mode is invoked by specifying "uninstaller.bin -console".

Before initiating the procedures, ensure that you are not running any Dimensions or RDBMS applications.

Stop Tomcat

If you are uninstalling a Dimensions CM server first shut down Tomcat:

  1. Log in as the Dimensions system administrator (the user who owns the Dimensions CM files). Default: dmsys

    Caution: Do not stop Tomcat as user root. It must be stopped by the DSA to shut down correctly.

  2. Stop the Common Tomcat:

    $ cd $installdir/../common/tomcat/<tomcat-version>/bin
    $ ./shutdown.sh
  3. To verify that Tomcat is not running check the process list for the tomcat process.

Shut down Dimensions CM

If you are uninstalling a Dimensions CM server or agent, first shut down Dimensions CM:

  1. Log in as user root.

  2. Give yourself the Dimensions CM environment variable values by running the appropriate Dimensions CM login script, for example:

    • Bourne Shell

      $ cd /opt/opentext/dimensions/<version>/cm
      $ . ./dmprofile
    • C Shell

      $ cd /opt/opentext/dimensions/<version>/cm
      $ source ./dmlogin
  3. Shut down Dimensions CM:

    1. Go to the Dimensions CM prog directory, for example:

      # cd /opt/opentext/dimensions/<version>/cm/prog
    2. Run this command:

      # dm_control cm_stop
  4. Check that the Dimensions CM processes have shut down:

    # ps -eaf | grep dm[pal]

    Services such as dmappsrv.x and dmpool.x should not be listed.

Uninstall components‌

To uninstall Dimensions CM components:

  1. Log in as user root.

  2. Navigate to the _uninstall director located one level up from the Dimensions CM root directory, for example:

    opt/opentext/dimensions/<version>/_uninst_maint
  3. Invoke the uninstaller:

    • For GUI mode:
      # ./uninstaller.bin
    • For CUI mode:

      # ./uninstaller.bin -console

Error messages when uninstalling UNIX clients‌

If you uninstall the UNIX client from a directory beneath the root directory of the Dimensions CM installation you may receive spurious messages. Uninstallation completes successfully, and you can ignore these messages.

These messages include:

  • <tomcat-install-dir>/conf/server.xml exists on this system and it has been modified since installation. Do you want to remove this file?
  • rm: cannot determine if this is an ancestor of the current working directory /tmp/istemp495138092221 bash- 2.05# id uid=0(root) gid=1(other)7
  • cat: cannot open /tmp/istemp4482139051720/chunk2 , / tmp/istemp4482139051720/chunk1: No such file or directory , /tmp/istemp4482139051720/chunk2: No such file or directory# rm -r $installdir

Manually clean up‌

If you are not going to re-install Dimensions CM, do the following:

  1. Delete these files:

    •  /etc/tnsnames.ora
    • /etc/sqlnet.ora
  2. Remove pcms_sdp from this file: /etc/services