Sun Management Center Change Manager 1.0.1 Administration Guide

- Previous: Sun Management Center Agent Cannot Communicate With the Change Manager Server After Installing a Managed Host
- Next: Information About Managed Hosts and Host Groups Created by Change Manager Remains in the Topology Database Even After Change Manager Software Is Uninstalled

## Stale Custom JumpStart Data Not Removed When Change Manager 1.0 Server Software Is Uninstalled

Description:

  If you upgrade your Change Manager 1.0 server to run Sun Management Center 3.5 server software and you do not preserve the data, then only the Change Manager 1.0 server software is uninstalled. None of the Change Manager data (the custom JumpStart data and the Change Manager repository) is removed from the Change Manager server.

Cause:

  This situation occurs when Change Manager 1.0 server software is uninstalled in one of the following two ways:

  - Using the `es-guiinst` command or the `es-inst` command to upgrade from Sun Management Center 3.0 to Sun Management Center 3.5

  - Using the `es-uninst` command to uninstall Sun Management Center 3.0 server software

Solution:

  Manually clean up entries in the `/etc/dfs/dfstab` file and in the `/etc/bootparams` file. Then, delete the Change Manager 1.0 repository. The directory that holds the Change Manager repository is specified by the value of the `cmdataroot` property in the `/var/opt/SUNWsymon/cfg/ichange.cfg` file.

- Previous: Sun Management Center Agent Cannot Communicate With the Change Manager Server After Installing a Managed Host
- Next: Information About Managed Hosts and Host Groups Created by Change Manager Remains in the Topology Database Even After Change Manager Software Is Uninstalled

- © 2010, Oracle Corporation and/or its affiliates