We are seeing the list of values being corrupted here. It's almost as
if it's pointing at the wrong data. We did a scan and repair of the
document domain, but still have the problem. Has anybody seen a
problem with a list of values being corrupted or pointed to the wrong
data within the universe?
Jodie
BusinessObjects V 4.x prior to 4.1.4 (or 4.1.3 with various CSP) contain
known bugs with LOV. We have personally had our repository corrupted beyond
repair. We were seeing LOV point to different universes, custom LOV
disappear, etc. This caused all sorts of problems including users queries
no longer executing and @prompts no longer working.
Scan, repair & compact did not fix the problem. What we did is to bypass
BusinessObjects “import” function. We cleaned up all our universes’ LOV and
saved a copy of the universe & its related LOV folder on a server. Now,
whenever we modify a universe, we take the copy off the server instead of
importing it from the repository.
The cleanup involved ensuring that the LOV name was OK by clicking on the
default button. Then, the LOV was recreated (ensuring the right object or
objects were in the LOV) and LOV were set to export with universe. Finally,
each LOV was run. All universes were then exported to a newly created
repository. This process took several days which meant several days down
time for our users.
It would be of benefit to you to get onto v 4.1.4 a.s.a.p. 4.1.4 is
supposed to have solved this problem with corrupt LOV & it has been good to
us so far. Good luck.
I’ve had this file corrupted and what I did was delete the LOVs from the C:
drive and from the supervisor module. I then renamed the lov file in the
designer module and never select export to universe.
Now when the user logs in their lov files will be recreated. This has
always fixed mine.
We are seeing the list of values being corrupted here. It's almost
as
if it’s pointing at the wrong data. We did a scan and repair of the
document domain, but still have the problem. Has anybody seen a
problem with a list of values being corrupted or pointed to the wrong
data within the universe?
There are patches to address this but I don’t remember which service pack
has these in it. I believe it was 4.1.4 so I would try to see if the most
current version would address this issue. (I believe that service pack 5 -
4.1.5 - is due to be released very soon so it may be worth your while to
wait another week or so and try it).