This is not a dxl question but you guys seem to know almost everything about DOORS so I will ask it here. I am trying to do a regular DOORS baseline from the menu, not dxl, of a module. After a while I get the following error message and the baseline does not complete.
I am one of the system administrators (maintain users, archive modules, etc., but not restart/update the server) and I have no idea what to do so that the module can be baselined. Our IT person (restart/update server) may know what to do but he is out for a week. He also may not know what to do. Any suggestions either for me or what I can tell him when he returns?
Thanks, anotherDaniel - Wed Mar 28 17:36:54 EDT 2018 |
Re: Error while baselining Hi Daniel I believe pic### files are DOORS pictures - not OLEs - "DOORS picture objects" - DOORS can't find the picture file so the baseline is failing - I would go to the module folder in question on the server from the path above and if you have other pic## files there or in other modules copy and rename them to pic1000004.dtc- (may need dtb file too??) that should at least allow you to baseline. You still will need to find the bogus copy and restore the figure - I would suggest as an OLE. It is not clear however if you have a systemic issue where you have lost all of your picture files - that was an issue quite a few years ago. Best of Luck Sara |
Re: Error while baselining smarti.sj - Thu Mar 29 07:56:29 EDT 2018 Hi Daniel I believe pic### files are DOORS pictures - not OLEs - "DOORS picture objects" - DOORS can't find the picture file so the baseline is failing - I would go to the module folder in question on the server from the path above and if you have other pic## files there or in other modules copy and rename them to pic1000004.dtc- (may need dtb file too??) that should at least allow you to baseline. You still will need to find the bogus copy and restore the figure - I would suggest as an OLE. It is not clear however if you have a systemic issue where you have lost all of your picture files - that was an issue quite a few years ago. Best of Luck Sara Moderators: I don't know if netiquette dictates that I should do something to "fix" this cross post (e.g., somehow re-create this thread in the DOORS Admin forum and post a link to that thread here?). Daniel, I'm pretty sure Sara is right about pic### files being non-OLE DOORS pictures. What I am certain of is that a .dtb file is a backup of the .dtc file that has the same name on the left-hand-side of the dot. When you do an archive, there is an option to "Include DOORS back up system files..." Checking that box means that .dtb's are included. Before I continue, I must warn you that tinkering with the DOORS database (DB) file structure always carries some risk. You should have a genuine backup of the entire DB data directory to reduce your risk of data loss. Not just .dpa, .dma and .dua archives, because they don't include how permissions are applied throughout the DB and there are a variety of other settings (e.g., page setups, color/font schemes, user options), that you would regret having to reconstruct if something were to go very wrong (power outage, slip of your mouse-hand, etc.). NOTE:if you are manipulating individual files, the DOORS DB server should be stopped/offline. You will need to be granted the ability to do that or collaborate with the guy who is out and can stop & start the DB. Each manipulation you make should be done with the DB server stopped, but then you'll immediately want to get back into the client to see if the fix worked, which requires the DB server to be re-started and operational. Also, just to be crystal clear [past experience with co-workers who didn't recognize as "obvious" the same things that I did requires me to say this], if you're working with archive files as I describe below, you should not be working directly with your golden, master backup file, always a copy. If your DOORS Software Subscription & Support is current, truly, the safest course would be to open a service request with IBM tech support. All that being said, the simplest thing you could try, if you see that pic1000004.dtc really is missing from the current.ver folder, would be to make a copy of pic1000004.dtb, and rename it pic1000004.dtc. Then restart the server and try again to baseline. If the .dtb file is missing too, you could look in archives of the module for the .dtc (preferable) or the .dtb, and try dropping a renamed-if-necessary .dtc file in the current.ver directory. If you have a .dma of that module, you could either restore it in another location in the DB and look for the file in that "new" module's data directory, or you could access the archive contents directly. In case you are not aware, the "Archive" function in DOORS, for both modules and projects, is an adapted form of .zip archiving. You can simply replace the .dma extension with .zip and open the file to see the contents. Inside a single module archive, you will see a 1.dac file. Pull the 1.dac file out of the archive and now replace the .dac extension with .zip. Again, you can open that to see the contents, which should look like the contents of your problem module, minus backup files if that opition during archive was not ticked. Pull the file you want out of the archive, rename if necessary, drop it where it needs to go, restart DB server, etc... Project archives are only slightly different, with each module represented by a ##.dac file. I believe the ## assigned follows the order that each module was archived during the archiving of the project, but you'd be pretty much guessing. Better to restore the project, find and pluck the file you need from the restored module's current.ver folder, and continue as described above.
Please let me know if this is useful.
Bill Adelman All constructive criticism is welcome! |
Re: Error while baselining DOORSguy - Fri Mar 30 10:35:50 EDT 2018 Moderators: I don't know if netiquette dictates that I should do something to "fix" this cross post (e.g., somehow re-create this thread in the DOORS Admin forum and post a link to that thread here?). Daniel, I'm pretty sure Sara is right about pic### files being non-OLE DOORS pictures. What I am certain of is that a .dtb file is a backup of the .dtc file that has the same name on the left-hand-side of the dot. When you do an archive, there is an option to "Include DOORS back up system files..." Checking that box means that .dtb's are included. Before I continue, I must warn you that tinkering with the DOORS database (DB) file structure always carries some risk. You should have a genuine backup of the entire DB data directory to reduce your risk of data loss. Not just .dpa, .dma and .dua archives, because they don't include how permissions are applied throughout the DB and there are a variety of other settings (e.g., page setups, color/font schemes, user options), that you would regret having to reconstruct if something were to go very wrong (power outage, slip of your mouse-hand, etc.). NOTE:if you are manipulating individual files, the DOORS DB server should be stopped/offline. You will need to be granted the ability to do that or collaborate with the guy who is out and can stop & start the DB. Each manipulation you make should be done with the DB server stopped, but then you'll immediately want to get back into the client to see if the fix worked, which requires the DB server to be re-started and operational. Also, just to be crystal clear [past experience with co-workers who didn't recognize as "obvious" the same things that I did requires me to say this], if you're working with archive files as I describe below, you should not be working directly with your golden, master backup file, always a copy. If your DOORS Software Subscription & Support is current, truly, the safest course would be to open a service request with IBM tech support. All that being said, the simplest thing you could try, if you see that pic1000004.dtc really is missing from the current.ver folder, would be to make a copy of pic1000004.dtb, and rename it pic1000004.dtc. Then restart the server and try again to baseline. If the .dtb file is missing too, you could look in archives of the module for the .dtc (preferable) or the .dtb, and try dropping a renamed-if-necessary .dtc file in the current.ver directory. If you have a .dma of that module, you could either restore it in another location in the DB and look for the file in that "new" module's data directory, or you could access the archive contents directly. In case you are not aware, the "Archive" function in DOORS, for both modules and projects, is an adapted form of .zip archiving. You can simply replace the .dma extension with .zip and open the file to see the contents. Inside a single module archive, you will see a 1.dac file. Pull the 1.dac file out of the archive and now replace the .dac extension with .zip. Again, you can open that to see the contents, which should look like the contents of your problem module, minus backup files if that opition during archive was not ticked. Pull the file you want out of the archive, rename if necessary, drop it where it needs to go, restart DB server, etc... Project archives are only slightly different, with each module represented by a ##.dac file. I believe the ## assigned follows the order that each module was archived during the archiving of the project, but you'd be pretty much guessing. Better to restore the project, find and pluck the file you need from the restored module's current.ver folder, and continue as described above.
Please let me know if this is useful.
Bill Adelman All constructive criticism is welcome! Thank you both for these answers. Our IT person was willing to look at the backups to see if the file exists. We couldn't find it, although our backups don't go back very far. Our IT person was totally unwilling to do any of this or provide the files to me so I could try it, so we are living with the gap.
Daniel |