Kbase P22032: bfcr error (73) with procopied database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
27/03/2003 |
|
Status: Unverified
FACT(s) (Environment):
Windows NT 4.0
FACT(s) (Environment):
Progress 9.0B
SYMPTOM(s):
bfcr error (73) with procopied database:
SYSTEM ERROR: bfcr called with no template. (73)
procopy failed with 8898 error:
SYSTEM ERROR: Attempted to exceed 2GB limit with file <pname>. (8898)
CAUSE:
procopy was being used to create a test database from production database. Extents were added to production database, but the st file for the test database wasn't updated. For example, suppose the test.st has a variable .d1, but a .d2 is added to the production database (thus fixing the .d1 size for that database). Suppose also that the amount of data in .d1 and .d2 is over 2GB, then the procopy using the test.st will try to expand .d1 beyond 2GB and will crash.
In some earlier v9 it seems it was sometimes still possible to start the target database, even though it was an incomplete procopy of the source.
This behaviour does not occur with at least v9.1D.
FIX:
Ensure that you use a valid st file.