Before You Begin

For open databases, there are three GUIDs that must be changed: the node, database, and manager. These GUIDs are maintained outside of the PostgreSQL datastore, which makes the updating easier than for a proprietary database that must be removed before you can update it.

Steps

  1. Stop the TeamQuest Manager service using the following command:

    manager/bin/tqmgr -shutdown

  2. Remove the TeamQuest PostgreSQL database using the following command:

    manager/bin/tqdbu -r -d databasename

    This does not remove the PostgreSQL datastore; it removes the connection information and associated GUIDs.

  3. Recreate the TeamQuest link to the PostgreSQL datastore by providing connection information to the PostgreSQL database using the same account as you used in Step 2 using the following command:

    manager/bin/tqdbu -i -t pdb -d databasename

  4. Change the TeamQuest Manager GUID using the following command:

    manager/bin/tqmgr -init reset_guid

  5. Re-register with the database with TeamQuest Administration Console using the following command:

  manager/bin/tqsync

  1. Reapply the policies you had in the old database.
  2. Delete the old database from TeamQuest Administration Console.

You now have two databases with the same name in TeamQuest Administration Console. However, one has new GUIDs and you must apply policies from the old database. These policies are active in the new database; however, they are not displayed in TeamQuest Administration Console yet. 

Note: If a new virtual machine becomes available, you must perform the above steps to make cloned systems available in TeamQuest Administration Console.


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: November 13, 2019