Kbase P35580: Errors 6081 and 6091 when restoring version 8 database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/6/2003 |
|
Status: Unverified
SYMPTOM(s):
Errors 6081 and 6091 when restoring version 8 database
bkioWrite: lseek error <error number> on file <file> at <address>, file <file-name>. (6081)
<function>:Insufficient disk space during <system call>, fd <file descriptor>, len <bytes>, offset <bytes>, file <file-name>. (6091)
Errors 6081 and 6091 refer to .db file
Errors 6081 and 6091 indicate 2GB filesize limit reached
CAUSE:
When a v8 probkup is restored with prorest, the database created will by default be a single-volume database.
In order for the restored database to be multi-volume, a void multi-volume structure must be created before the restore is done.
Even if the original source database was multi-volume, prorest will try to create a single-volume database. If the source database was over 2GB in size, this means that prorest will reach the 2GB filesize limit on the .db file and will error out with the 6081 and 6091. The errors will refer to addresses around the -214783648 value.
FIX:
Create a void multi-volume database structure and prorest into that structure.
FIX:
An example using 8.3E on Windows 2000:
1. prodb sports sports
This creates a single-volume database in your working directory, comprised of - sports.bi, sports.db, sports.lg
2. mkdir prorest
3. probkup sports prorest\sportsbak
4. cd prorest
5. In the prorest directory create a sports.st file:
d C:\PRGSWRK\83EWRK\prorest\sports.d1 f 1024
d C:\PRGSWRK\83EWRK\prorest\sports.d2
b C:\PRGSWRK\83EWRK\prorest\sports.b1 f 1024
b C:\PRGSWRK\83EWRK\prorest\sports.b2
6. prostrct create sports
This creates a void multi-volume structure.
7. prorest sports sports sportsbak
The database is restored into the multi-volume structure.
Compare the sizes of the .db files from the target and the source databases. In the single-volume database the .db is the file that contains the data, whereas the .d files contain the data in the multi-volume database. Thus the .db file in the multi-volume target database will be smaller than the .db from the single-volume source.