Kbase P17160: Cannot resync BCV due to IO inconsistencies between disk arrays caused by proquiet not suppressing w
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
21/09/2010 |
|
Status: Verified
SYMPTOM(s):
Cannot resync BCV (Business Continuity Volumes) due to IO inconsistencies between disk arrays
Write activity is being allowed to the log file
Users can login into the database with a quiet point enabled
Disabled user logins on OS level but users still connecting to the database.
FACT(s) (Environment):
Command being issued: proquiet dbname -C enable
All Supported Operating Systems
Progress/OpenEdge Product Family
CAUSE:
Bug# OE00086208
CAUSE:
Proquiet command does not disable logging to dbname.lg. The Proquiet command quiets all write, update, and delete activity against a database, but does not prohibit writes to the .lg file.
FIX:
An enhancement request has been created requesting that the proquiet command be reviewed to determine: 1) If it could be modified to suppress users from logging into the database or 2) If a startup option could be used to relocate the .lg file to a different location than where the .db currently resides.