Kbase P28140: Error: Multiple version recs for repo rec site
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/27/2003 |
|
Status: Unverified
FACT(s) (Environment):
RoundTable 9.1x
SYMPTOM(s):
RoundTable. Multiple version recs for repo rec site
Repository Check Report:
Error: Multiple version recs for repo rec site: 0 addr: 7690 blk: 1
version pmod: 090dlc-adm2 type: PCODE obj: caller.cld ver: 010000
version pmod: t_db-icfdump type: PCODE obj: tbs_rf028.ado ver: 010008
Error: Multiple version recs for repo rec site: 0 addr: 7691 blk: 1
version pmod: 090dlc-adm2 type: PCODE obj: caller.i ver: 010000
version pmod: t_db-icfdump type: PCODE obj: tbs_rf030.ado ver: 010008
Error: Multiple version recs for repo rec site: 0 addr: 7693 blk: 1
version pmod: 090dlc-adm2 type: PCODE obj: callprop.i ver: 010000
version pmod: t_db-icfdump type: PCODE obj: tbs_rf034.ado ver: 010008
Error: Multiple version recs for repo rec site: 0 addr: 7698 blk: 1
version pmod: 090dlc-adm2 type: PCODE obj: calltables.i ver: 010000
version pmod: t_db-icfdump type: PCODE obj: tbs_rf042.ado ver: 010008
CHANGE:
Does an consistency check with roundtable but gets an error message about record verisons not compatible ?
CAUSE:
RELEASE NOTE:
For some Roundtable repositories that have been upgraded from 1.1A of Dynamics, there may be some issues with "rtb_ver record not on file" errors being displayed during partner site load of a Dynamics 2.0A upgrade or as part of an import from an upgraded 2.0ASP1 workspace into a 1.1A workspace that is to be upgraded.
Although the errors indicate a corruption of the RTB repository, the errors are not know at this time to cause any show stopping problems with the functionality of the RTB environment or the Dynamics framework.
To determine of the Roundtable repository is corrupted with the above errors, run a Repository Check Report fro the Reports menu off the Roundtable Table top. If there are repository problems, they will typically show as errors with multiple object versions pointing to the same repository address in the Roundtable repository.
All of the objects that have shown to have errors of this kind belong to Dynamics specific product modules and not to customers' own product modules.
FIX:
There are a couple of ways to fix errors for these issues.
1. The cleanest solution is to create a new Roundtable Dynamics 2.0A-based repository environment from the latest full Roundtable partner deployment package. This then has to be updated with the application objects from the old repository (after this has been updated to Dynamics 2.0ASP1) - so that it is only objects from the non-Dynamics products and product modules that are imported from the old repository to the new repository.
From the old Roundtable repository a workspace and subsequent
deployment containing only the customer specific objects (in own products and product modules) can be created from the customer development workspace and loaded into the new Roundtable repository.
Although this involves some extra effort in rebuilding the workspaces in the new repository, it avoids having to manually delete and update objects in the RTB repository.
This is the recommended solution.
2. This solution involves manual changes to the contents of the RTB repository. A full backup of the RTB database must be made before this is attempted.
Fixing the corrupt repository these issues requires manual deletion and editing of data in the Roundtable repository. As it is necessary to know which objects need to be fixed, it is not possible to create a simple fix program to resolve all of the problems in one go.
For each of the situations where multiple objects are pointing to the same repository address, one of them has to be deleted from the repository. From the testing that has been done on this, it is the second object of the pairs of objects listed in the Repository Check Report, that should be deleted.
The code to delete the object is :
FIND FIRST rtb_ver WHERE
rtb_ver.object = "<name of object to delete>" AND
rtb_ver.obj-type = "PCODE":U AND
rtb_ver.version = <version of object to delete>
EXCLUSIVE-LOCK NO-ERROR.
IF AVAILABLE rtb_ver THEN DO:
DELETE rtb_ver.
END.
Once this has been done, Rebuild the Names table from Roundtable and re-load the latest Partnership Deployment package. This should reload the deleted object versions.
Run a new Repository Check Report to ensure that the repository is no longer corrupt.