Kbase P48996: Known danger to run automatically "prostrct repair <dbname>"?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
GOAL:
Is there any danger to run "prostrct repair <dbname>" each time prior to starting the database?
GOAL:
Known danger to run automatically "prostrct repair <dbname>"?
FIX:
There is no known danger to always run the two following commands prior to starting a database server or prior to connecting in single user mode to that database
prostrct list <dbname>
prostrct repair <dbname>
However, we cannot guarantee that a corrupted control area for the database (<dbname>.db file) might generate a wrong <dbname>.st file and therefore not allow you anymore to repair the control area with the command
prostrct builddb <dbname>
The command "prostrct list" will update the file "<dbname>.st" with the information from <dbname>.db. The command "prostrct repair" will clean the shared memory segment identifier in the database master block, to resolve for example
** SYSTEM ERROR: Unspecified shared memory error errno=43 (1180)
as well as updating the control area (<dbname>.db) with the information read within <dbname>.st
Should you have no more control area for your database, then the existing <dbname>.st file will not be modified.
ADVISE: Make always a copy of <dbname>.st, within a file of different name, after any structure change of your database.