Kbase P123871: Cannot disable replication if database is shutdown, AI extents are all LOCKED, and busy extent is fu
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/4/2009 |
|
Status: Verified
SYMPTOM(s):
Cannot disable replication if database is shutdown, AI extents are all LOCKED, and busy extent is full
Can't switch to after-image extent <extent> it is full. (3775)
Database Server shutting down as a result of after-image extent switch failure.
Backup after-image extent and mark it as empty. (3774)
FACT(s) (Environment):
proutil <dbname> -C disablesitereplication source
OpenEdge Replication 10.1B 32-bit
OpenEdge Replication 10.1B 64-bit
CAUSE:
Bug# OE00149697
FIX:
Upgrade to 10.1B02 or later
Workarounds:
1. Backup the database using probkup with the -norecover option and then restore the database into a new structure.
probkup <dbname> <dbname.bkup> -norecover
2. Add additional AI areas:
Adding AI areas will only work if the BUSY area is physically the last AI area, so that any newly added EMPTY areas would follow.
(There is a known issue with prostrct reorder ai, whereby the reorder fails when these conditions are not met. See solution P123872)
3. Restore the source database from a previous backup and roll-forward AI files, delete recovery files, then re-enable after imaging and replication.
4. Force entry into the database and dump/load the data. Not recommended because the force option can cause corruption.