After uninstalling version 1.5.x and installing a fresh 6.0, the repository is not compatible. How can the long term repository be reconfigured to the 6.0 installation?
A good scenario would be an ACTIVE/PASSIVE Cluster environment. Nodes may failover so the initial installation on the original node is no longer ACTIVE. Therefore the INSTANCE_KEY column from QUEST_INSTANCE_DIM is still pointing to the original node referencing the old version.
On the repository database, open query analyzer to connect to the repository and issue the following sql:
select * from QUEST_INSTANCE_DIM;
(this will retrieve the INSTANCE_KEYs)
1) Make note of the INSTANCE_KEY for the row that matches the HOST and INSTANCE_NAME in question where the SC_VERSION is 1.5.x. This is the old (original) instance key.
2) Make note of the INSTANCE_KEY for the row that matches the HOST and INSTANCE_NAME in question where the SC_VERSION is 6.0.x. This is the new instance key.
update QUEST_INSTANCE_DIM set HOST = '<HOSTNAME>_TEMP' where INSTANCE_KEY = 'new key'
update QUEST_INSTANCE_DIM set HOST = '<HOSTNAME>' where INSTANCE_KEY = 'old key'
commit
select * from QUEST_INSTANCE_DIM order by INSTANCE_KEY
The first update statement above will rename the HOSTNAME to HOSTNAME_TEMP for the new instance key. This will effectively delink this instance key from this instance in the repository.
The second update statement above will relink the old (original) instance key to this instance in the repository.
For further assistance, please contact Quest Support.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center