"TopologyObjectNotFoundException" in log (4328255)

We exported our Registry variables from one FMS and imported into another.
We now see these TopologyObjectNotFoundExceptions in the Foglight Management Server (FMS) logs.

How can we identify which Registry variables are causing this problem and correct the issue?

2009-12-08 18:14:05.314 VERBOSE [http-0.0.0.0-5155-74] com.quest.nitro.service.sl.impl.registry.RegistryVariableBean - Registry value bond to topology object d7cc5e5e-a8f8-4d24-8c0b-02ff47fcbe06 is invalid: com.quest.nitro.service.topology.TopologyObjectNotFoundException: Topology Object Not Found: d7cc5e5e-a8f8-4d24-8c0b-02ff47fcbe06
2009-12-08 18:14:05.315 VERBOSE [http-0.0.0.0-5155-74] com.quest.nitro.service.sl.impl.registry.RegistryVariableBean - Registry value bond to topology object 06ae9d86-27fb-49c1-9b2f-0c000a5062c7 is invalid: com.quest.nitro.service.topology.TopologyObjectNotFoundException: Topology Object Not Found: 06ae9d86-27fb-49c1-9b2f-0c000a5062c7
2009-12-08 18:14:05.316 VERBOSE [http-0.0.0.0-5155-74] com.quest.nitro.service.sl.impl.registry.RegistryVariableBean - Registry value bond to topology object 85ba53a4-03d4-45b6-87cc-4beb16359c60 is invalid: com.quest.nitro.service.topology.TopologyObjectNotFoundException: Topology Object Not Found: 85ba53a4-03d4-45b6-87cc-4beb16359c60

The Registry variables were scoped to particular clients which do not report to the FMS where the Registry variables were imported.

1) Create a FMS support bundle.

2) Extract the Diagnostic Snapshot file from the compressed Support Bundle.

3) Using a text editor, search the DiagnosticSnapshot file for your offending object IDs from the FMS log.
ie. d7cc5e5e-a8f8-4d24-8c0b-02ff47fcbe06
Registry value bond to topology objectd7cc5e5e-a8f8-4d24-8c0b-02ff47fcbe06is invalid:

In this example the search found:
Registry variable:OraDBAFatalwith values for {TopologyObject,85ba53a4-03d4-45b6-87cc-4beb16359c60,06ae9d86-27fb-49c1-9b2f-0c000a5062c7,d7cc5e5e-a8f8-4d24-8c0b-02ff47fcbe06,fe45497d-c888-4ef1-871c-f0a253ffa90e,}

4) Edit the Registry Variable in Administration | Rules & Notifications | Manage Registry Variables.
This example OraDBAFatal was edited by placing the cursor in the GLOBAL Default box at the end of the current entry, pressing the space bar, then backspace. Select Save. This effectively overwrites the current entry which removes the references to the non-existent Topology Object IDs.

5) Repeat for any other found Registry variables.

If there are a lot variables which needs to set again, use the script below:

1) Go to "Administration | Tooling | Script Console"

2) Open the Script Editor and enter the following script:

regSvc = server["RegistryService"];
all_vars = regSvc.getAllRegistryVariables() ;
for (regVariable in all_vars) {
regSvc.saveRegistryVariable(regVariable);
}

3) Click on "Run"

If you only want to affect one variable at a time, and are locked out of the management pages, use the following script in the script editor; (edit the first line)

variableName="Full_Variable_Name";
regSvc = server["RegistryService"];
all_vars = regSvc.getAllRegistryVariables() ;
for (regVariable in all_vars) {
if (regVariable.getName() == variableName){
regSvc.saveRegistryVariable(regVariable);
return "success\n";
}
}