We have a big problem of repository being corrupted whenever we export a new version of an Universe. The various problems that we are facing are :
1- Documents are disapearing from the repository 2- List Of Values (LOV) are disapearing from the repository 3- Scripts are disapearing from the repository 4- Some objects do not have the good LOV associated after an import of
the universe and the LOV (the data are wrong and if you edit the LOV the wrong objects are present
5- Some LOV cannot be edited or displayed after an import of the
universe and the LOV (no error message)
6- Some LOV cannot be edited or displayed after an import of the
universe and the LOV: “Some Obsolete objects have been removed from the query”
7- Some LOV could appear in task list the DAS instead of a document.
Has any of you faced this problem ? If yes how did you overcome it ?
We reported this to BO support and received a Customer Service Patch named “CSP21”. In the document that we received along with the patch it was mentioned that this problem is being caused by a bug in the Designer module and the patch would fix the same.
But Alas !!! we found that the patch only makes the problem much more graver. YES !!! it has corrupted our repository completely. Luckily we had a backup with which we restored the repository.
Has any of you used this patch ? Did you face similar problems ? Any help / advice / pointers in this regard is greatly appreciated. We are in touch with BO also for the same problem and will post the reply that we receive.
We have a big problem of repository being corrupted whenever we export a new version of an Universe.
Hi there,
Now that you mention it, we have experienced a few occurences of wierd problems of this sort.
Some documents have occasionally disappeared from the repository (when noone has access to them except myself) although as far as I remember no scripts or LOV files have gone missing. I have definitely experienced problems with LOVs after import/new repository install where a list either cannot be accessed or shows data from a completely different object from a different universe (wrong object is present in the data provider for the list and has to be corrected manually).
Does this mean that our repository might be corrupted? If this service pack does not help, what else are BO Support offering to solve the problems?
Thanks for your warning about using service pack CSP21. It does not sound like it solves the problems at all.
We were having the same problems that you are describing a couple of weeks ago. First, we have done a scan and repair on the repository, and then I installed the CSP20 patch. I still had to replace the already damaged LOVs, but I have not experience any further problems.
Make sure that you import the universe before making any changes to the universe or the lov’s. If this doesn’t work, you might have to delete universe from the repository before you export the new version.
Kurt Kerchner
Southwestern Bell
(314)340-9853
<Has any of you used this patch ? Did you face similar problems ?
Any help / advice / pointers in this regard is greatly appreciated. We are in touch with BO also for the same problem and will post the reply that we receive.
First, we have done a scan and repair on the repository, and then I installed the CSP20 patch.
What is this CSP20 patch ? I mean what does this do ? Does it repair the corrupted repository ?
Make sure that you import the universe before making any changes to the universe or the lov’s.
I guess you are talking about the “Development machine” from where we do all the Universe changes and export it. In that case I am sorry. This will only worsen the situation since the LOVs on “Development machine” will get corrupted if I import the Universe.
If this doesn’t work, you might have to delete universe from the repository before you export the new version.
YES !!! This is what we did before exporting the Universes after applying the patch. But it does not help !!!
I hope somebody from BO is hearing to all these frantic calls.
What is this CSP20 patch ? I mean what does this do ? >Does it repair the corrupted repository ?
I first thought this CSP would fix our LOV problems(the same ones you have mentioned), but it is actually supposed to correct “Unique Constraint” errors on the database when users export documents simultaneously.
I must admit that I had BOb version 4.1.2, and I had to install 4.1.3 before using the patch. We have also done a Scan and Repair of the repository on a weekly basis. So far, we have had no further LOV problems. It’s too bad this solution doesn’t work for everyone.