Question & Answer
Question
Why do I get the error "Can't open data file for read/write" when I try to archive a module?
Cause
A possible cause is if the module's index file is missing on the DOORS database server machine as a result of a DOORS client losing connection to the DOORS database server during some operation. To figure out if the module's index file is missing follow these steps:
- Get the unique ID of the module. To do this run the following DXL code while highlighting the problem module
print uniqueID getSelectedItem ""
This will give a unique ID for the module. (say 00000002). Make a note of it. - On the DOORS database server machine, in your DOORS data do a search for the module from the unique number (say m00000002.mod from the unique ID found in the first step).
- Check the folder of the resulting mXXXXXXX.mod file to see if there is a module.dtc file or not
Answer
If it is determined that the index file for the module is missing, the issue can be resolved by:
- Log into DOORS as the 'Administrator' user and right click the project the module is a child of and select "Check Integrity..."
- Run through the integrity check wizard and the problem module will be identified and you will be able to select which project the module should belong to.
- After the wizard is complete the module's index file will have been re-created and the issue will be resolved.
If the issue is still not resolved or there are other complications, please contact IBM Rational DOORS Support for help.
[{"Product":{"code":"SSKR2T","label":"IBM Engineering Requirements Management DOORS"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"General Information","Platform":[{"code":"PF033","label":"Windows"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"9.2;9.3;9.3.0.1;9.3.0.2;9.3.0.3;9.2.0.4;9.2.0.5;9.2.0.3;9.2.0.2;9.2.0.1;9.0;9.1;9.1.0.2","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
Modified date:
01 May 2020
UID
swg21499094