Kbase 16774: Force Access -F Parameter in Version 8.2 and Later
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
09/05/2003 |
|
Solution ID: 16774
GOAL:
Changes in the use of the -F parameter to force access to a database.
FACT(s) (Environment):
Progress 8.2x
FACT(s) (Environment):
Progress 8.3x
FACT(s) (Environment):
Progress 9.x
SYMPTOM(s):
** The FORCE option was given, database recovery will be skipped. (33)
** Your database was damaged. Dump its data and reload it. (37)
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)
CAUSE:
In Versions prior to 8.2, the -F parameter was used in the following three scenarios:
- To force access to a damaged database in order to recover as much data as possible (for example, pro demo -F, PROSERVE demo -F).
Forced access to a database causes Progress to skip crash recovery and basically clear the before-image (BI) file.
This leaves the database in an unknown state because the data in the BI file is lost.
- To access shared memory information with PROMON without locking any data structures (for example, PROMON demo -F).
- To invoke an emergency shutdown of a database when normal shutdown might may be taking too long or appears hung (for example, PROSHUT demo -F).
The second two scenarios have no adverse affects on the database. The first scenario, however, has very serious consequences. For this reason, the use of the -F parameter for forcing access to a database is restricted in Progress Versions 8.2 and later.
FIX:
In Version 8.2 and later, forced access to the database is allowed only from the PROUTIL utility in conjunction with either:
- The TRUNCATE BI qualifier.
- The DBRPR qualifier.
TRUNCATE BI (for example, proutil demo -C truncate bi -F):
When this is done, the following messages and prompt is displayed:
The -F option has been specified to proutil. (6260)
Forcing into the database skips database recovery. (6261)
This leaves the database in unknown state, considered damaged. (6262)
Are you sure you want to skip crash recovery? (6263)
If you enter "y" for "yes", the force access occurs and the following messages are displayed and written to the log file:
** The FORCE option was given, database recovery will be skipped.
** Your database was damaged. Dump its data and reload it. (37)
For DBRPR (for example, proutil demo -F -C dbrpr >outputfile):
This accomplishes the same end as the truncate BI qualifier and allows direct access to the dbrpr menu utilities.
This qualifier does not display the above listed messages until the next time you start a process or server against this database. Even though these messages are not listed immediately at the time the -F is given, they are still directly applicable to the state of the database and appropriate action should be taken.