Kbase 19582: Prostrct unlock fails to work properly in 9.0B
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  3/9/2000 |
|
Prostrct unlock does not work properly in Progress 9.0B.
If the bi file is lost or removed while a transaction is active, prostrct create will fail to create a proper file.
The error that follows is..
$ prostrct unlock sports
Database sports is not properly closed, command ignored. (6754)
Failure of the unlock then prevents force-in of the db..
$ proutil sports -C truncate bi -F
PROGRESS Version 9.0B as of Sat May 8 06:28:21 EDT 1999
The -F option has been specified to proutil. (6260)
Forcing into the database skips database recovery. (6261)
This leaves the database in an unknown state, considered damaged. (6262)
Are you sure you want to skip crash recovery? (6263)
y
File /users/ts/plamothe/fidelity9/sports.db is on a remote system (2226)
Database integrity CANNOT be guaranteed for this session. (2227)
** Cannot find or open file /users/ts/plamothe/fidelity9/sports.b1, errno = 2. (43)
Subsequent attempts with -F to dbrpr or buildbd also fail..
$ proutil sports -F -C dbrpr
PROGRESS Version 9.0B as of Sat May 8 06:28:21 EDT 1999
Invalid file size for Extent ./sports.b1 of Area Primary Recovery Area
Unable to open ./sports.b1, errno 2
$
The problem is that the database is not opened for prostrct unlock if the database is not closed properly.
The code has been modified for 9.1A so that the problem will not occur
there.
EXPECTED BEHAVIOR:
The prostrct unlock is in the example below of Progress 8.3B
$ prostrct unlock sports
WARNING: Database is damaged, missing extent file
/users/ts/plamothe/fidelity9/sports.b2. (1990)
** Cannot find or open file /users/ts/plamothe/fidelity9/sports.b2, errno =
0. (43)
** Creating missing BI extent /users/ts/plamothe/fidelity9/sports.b2. (1992)
1 inconsistency fixed