Attempted to archive a large DOORS 7.1 project with the goal of restoring it into DOORS 9.3. After about an hour, and the progress bar is almost at 100%, an error appears "Input file read failure". No archive file is created.
This situation occurs only when saving all baselines. This does not happen when choosing NOT to save baselines. In this case a file is saved.
I must have the baseline information as well as the data in DOORS 9.3.
Worked fine for smaller projects. I'm attmpting to save the archive on my local drive which has 141GB of free space.
PJMinWa - Tue Apr 03 13:30:11 EDT 2012 |
|
Re: Archive Error "Input file read failure" llandale - Tue Apr 03 17:07:48 EDT 2012
Seems to me I had this error once, and it turned out to be a corrupted database file whose name was illegal as far as Windows was conserned; containing some illegal characters.
I narrowed down the problem by taking the project's 1st order folders, converting each to a project and trying to archive it; turning it back to a folder afterwards. Ended up finding the offending module, tracked down its location in the database, then looked at all the files until I found one that clearly didn't look right.
It seems to me that I just deleted that file after confirming that its real counterpart was still valid.
-Louie
|
|
Re: Archive Error "Input file read failure" PJMinWa - Tue Apr 03 17:44:28 EDT 2012 llandale - Tue Apr 03 17:07:48 EDT 2012
Seems to me I had this error once, and it turned out to be a corrupted database file whose name was illegal as far as Windows was conserned; containing some illegal characters.
I narrowed down the problem by taking the project's 1st order folders, converting each to a project and trying to archive it; turning it back to a folder afterwards. Ended up finding the offending module, tracked down its location in the database, then looked at all the files until I found one that clearly didn't look right.
It seems to me that I just deleted that file after confirming that its real counterpart was still valid.
-Louie
I'll look into checking the database integrity. But seems like if it was a corrupt file/module name then I shouldn't have been able to archive without baselines.
Given a successful archive without baselines is about 800K, what would be an estimated archive file size for a project with 25 baselines, consisting of 11 folders and a total of 47 modules?
|
|
Re: Archive Error "Input file read failure" llandale - Wed Apr 04 11:07:01 EDT 2012 PJMinWa - Tue Apr 03 17:44:28 EDT 2012
I'll look into checking the database integrity. But seems like if it was a corrupt file/module name then I shouldn't have been able to archive without baselines.
Given a successful archive without baselines is about 800K, what would be an estimated archive file size for a project with 25 baselines, consisting of 11 folders and a total of 47 modules?
I'm not saying your problem is the same as mine.
It turns out the file was recovered by the database and there was no DOORS 'corruption' nor nothing for the integrity checker to fix. I don't recall the exact name, but for example if these exist:
then also this file existed:
If that file is on one of the "baseline" sub-folders, then DOORS wouldn't look and you would not get the error. Since the corresponding file indeed existed, I just deleted the one with the Windows offensive name.
I think the storage for each baseline is on the same order as the storage needed for the current version.
-Louie
|
|
Re: Archive Error "Input file read failure" SudarshanRao - Fri Apr 06 03:56:35 EDT 2012 PJMinWa - Tue Apr 03 17:44:28 EDT 2012
I'll look into checking the database integrity. But seems like if it was a corrupt file/module name then I shouldn't have been able to archive without baselines.
Given a successful archive without baselines is about 800K, what would be an estimated archive file size for a project with 25 baselines, consisting of 11 folders and a total of 47 modules?
I think the problem here is with the limitation that DOORS 7.1 had on archive -
a. The size should not be more than ~2GB
b. The number of files to be included should not exceed 64k files.
There's no work-around for this. But these limitations are lifted in DOORS 8.x onwards. So, the best option for you is to take a copy of your DOORS 7.x db, upgrade to DOORS 8x, and then archive.
Hope that helps.
|
|
Re: Archive Error "Input file read failure" SudarshanRao - Fri Apr 06 04:02:08 EDT 2012 SudarshanRao - Fri Apr 06 03:56:35 EDT 2012
I think the problem here is with the limitation that DOORS 7.1 had on archive -
a. The size should not be more than ~2GB
b. The number of files to be included should not exceed 64k files.
There's no work-around for this. But these limitations are lifted in DOORS 8.x onwards. So, the best option for you is to take a copy of your DOORS 7.x db, upgrade to DOORS 8x, and then archive.
Hope that helps.
Minor addition to my previous note -
While archiving, if you have chosen "Include backup files" option, then you can probably try removing that. That will possibly reduce the number of files to be included significantly. So, if you're hitting on the number of files limit, you may as well be able to get below that.
|
|
Re: Archive Error "Input file read failure" PJMinWa - Fri Apr 06 12:01:45 EDT 2012
Thanks SudarshanRao. The archive size is probably the issue. (I've always had the backup files option deselected so that isn't the problem.)
We do have DOORS 8.x with a couple of databases active. Is there an easy way to move a DOOR 7.1 db to DOORS 8.x without affecting the other existing DOORS 8.x databases?
|
|
Re: Archive Error "Input file read failure" SudarshanRao - Mon Apr 09 08:59:17 EDT 2012 PJMinWa - Fri Apr 06 12:01:45 EDT 2012
Thanks SudarshanRao. The archive size is probably the issue. (I've always had the backup files option deselected so that isn't the problem.)
We do have DOORS 8.x with a couple of databases active. Is there an easy way to move a DOOR 7.1 db to DOORS 8.x without affecting the other existing DOORS 8.x databases?
Yes, you can create an additional instance of database server in 8.x (refer to Help manual under "Managing Database Server" section).
You'd basically need to take a copy of the 7.1 data folder (this will mean that 7.1 database server will have to be stopped), create a new 8.x instance, point that instance to the copy of 7.x data folder.
|
|