How to Reinitialize an Existing Change Manager Database Setup

Follow this procedure if you want to reinitialize the Change Manager database setup you created when you first installed Change Manager 1.0.1 server software.

Though the graphical installation program and command-line installation program perform the same tasks, they might appear somewhat differently on the screen.

1. Become superuser.

2. Set up the Change Manager 1.0.1 server software in one of the following ways:

   • Set up the Change Manager software by using the GUI.

     # /opt/SUNWsymon/sbin/es-guisetup -p ichange

   • Set up the Change Manager software by using the command line.

     # /opt/SUNWsymon/sbin/es-setup -p ichange

   The Sun Management Center components are stopped.

   Configure the add-on products only.

   The wizard checks for an existing Change Manager database setup and finds one.

   • Go to Step 3 if the database is valid.

   • Go to Step 4 if the database is invalid.

3. Specify whether to use or discard the Change Manager database that was found.

   • If you want to use the database, then you are done with the Change Manager setup.

     Go to Step 9 to restart the Sun Management Center agent and server components.

   • If you do not want to use the database, then the database is reinitialized and the data is discarded.

     Go to Step 5 to specify the location of the Change Manager repository.

4. Determine what to do if an invalid database was found.

   • Try restoring the database from a backup, then rerun the check starting with Step 2.

   • If you do not want to use the database, then discard the data from the repository and reinitialize the database.

     If you choose to reinitialize the database, be sure to make a copy of the repository before it is discarded.

5. Specify the directory in which to create the Change Manager repository.

   By default, the directory is /var/opt/ichange.

   The repository must be a local disk slice, which should be allocated several gigabytes of disk space. To determine the amount of space you need, estimate the number and size of the Solaris Flash archives, Solaris boot image (about 200 Mbytes each in size), manifests, and other data you plan to store in the repository.

   If /var/opt/ichange does not have sufficient disk space, then specify another directory that does.

6. Specify the password that was used to generate the security keys when you set up the Sun Management Center server.

   Change Manager must use the same security keys as those used by the Sun Management Center server. To do this, you must specify the same password that you supplied when you set up the Sun Management Center server software. By using the same password, identical security keys are generated.

   These security keys are used to configure the agent on the managed host after initial installation or update operations have been performed.

   The Change Manager database environment is set up.

7. Specify the directory in which to create the Change Manager database.

   By default, the directory is /var/opt/ichange.

   If the /var/opt/ichange directory does not have at least 0.5 Gbytes of available disk space, specify another directory that does.

   The Change Manager database setup is performed.

8. Specify whether to restart the Sun Management Center Web Console server.

   If you are setting up Change Manager for the first time, then you must restart the Sun Management Center Web Console server. If you do not restart it, you cannot access the Change Manager web application.

   The only time it is safe to restart the web console server is when no other users are using the web console. If you decide to wait to restart the web console server, you must restart it manually by running the /usr/sadm/bin/smcwebserver restart command.

   If you decide to restart the web console server now, it is restarted.

9. Start the Sun Management Center agent and server components.

   Starting the agent and server components takes a while.