I've come across an unusual occurrence where history records appear not to have been captured when they should have been. We are using DOORS 9.5.
We have an attribute where users enter comments, and the History capture option is turned on for the attribute. Standard users do not have the permissions to modify the attribute properties, so are not able to turn off History capture. Database Managers do have the ability to turn off the History capture, but they have not done so. If an attribute is modified, you get a History record indicating that a modification has been done. In this instance, there is no history record of any attribute property changes. No module baselines were done.
It appears that on a single day, a user made comments against multiple objects. History records were recorded for 44 of 46 commented objects. For 2 objects, comments have been recorded, yet no history records exist for those comments.
Has anyone come across a similar occurrence? jsarkic - Mon May 05 11:18:48 EDT 2014 |
Re: Missing History Records? How are you viewing the history records - via the DOORS standard functionality (object properties)? Are you sure there was no baseline taken between the changes to 2 the objects which appear to have missing history and the changes to the other 44 objects?
|
Re: Missing History Records? This has been happenning for a customer for at least 5-6 years, tends to be most common in shareable edit when a lot of users are editing a module at the same time. We get less occurrences in DOORS 9.3 than in DOORS 8.2, but it occassionally happens. We had IBM in to solve thies problem many years ago and we installed debug versions of DOORS 8.2 on a number of machines, but the break conditions apparrently never occurred and it happens much less in 9.3 than in 8.2 so we just live with it. Bizzarrely we sometimes got the opposite as well i.e. history changes wthout actual changes as well as actual changes but no history ;-) Weird I know, but we cannot reproduce it on demand for IBM so we were/ are a bit snookered! |
Re: Missing History Records? Richard_Good - Tue May 06 13:03:17 EDT 2014 This has been happenning for a customer for at least 5-6 years, tends to be most common in shareable edit when a lot of users are editing a module at the same time. We get less occurrences in DOORS 9.3 than in DOORS 8.2, but it occassionally happens. We had IBM in to solve thies problem many years ago and we installed debug versions of DOORS 8.2 on a number of machines, but the break conditions apparrently never occurred and it happens much less in 9.3 than in 8.2 so we just live with it. Bizzarrely we sometimes got the opposite as well i.e. history changes wthout actual changes as well as actual changes but no history ;-) Weird I know, but we cannot reproduce it on demand for IBM so we were/ are a bit snookered! We have also observed this same issue (on multiple occasions) of missing history records (using 9.3.0.6) also occurring on modules configured for shareable edit, with multiple, concurrent editors. Is there an IBM problem report that documents this problem that you know of? If there isn't, I had planned on submitting one. |
Re: Missing History Records? Robert_Stoick - Wed Jul 02 21:49:05 EDT 2014 We have also observed this same issue (on multiple occasions) of missing history records (using 9.3.0.6) also occurring on modules configured for shareable edit, with multiple, concurrent editors. Is there an IBM problem report that documents this problem that you know of? If there isn't, I had planned on submitting one. Had one open for 6 months/ a year, but we could not repeat the problem on demand so IBM closed the problem down - no idea what the number is - issue raised more than two years ago. The debug build of DOORS.exe they sent me - which was supposed to pump out error logs when history record issue symptoms occurred never pumped out an error report even though we experienced the issue several times with it installed. It remains a mystery. If you can find some way to reliably repeat the problem you stand a chance. Due to the nature of my client we cannot send the modules/ server files to IBM, if you can do this you also stand a greater chance of them solving the issue, so if you can send them the back end data they will probably request - then I suggest you do raise an error report. |