Kbase P154904: Errors 3773, 5350 and 3774 trying to start a database with ai archiver enabled
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/5/2010 |
|
Status: Verified
SYMPTOM(s):
Errors 3773, 5350 and 3774 trying to start a database
Can't switch to after-image extent it is full. (3773)
Database Server shutting down as a result of after-image extent switch failure. (5350)
Backup after-image extent and mark it as empty. (3774)
Found errors 12288, 3775 an 3776 after error 13198 in the database log file prior to database shutdown
The after-image management daemon cannot find a destination in its current list with enough space to continue archiving extents. (13198)
There are no available EMPTY AI extents. Database activity is stalled until an AI extent becomes available. (12288)
Can't switch to after-image extent it is full. (3775)
Backup ai extent and mark it as empty. (3776)
Error 13216 trying to mark ai as empty
After-image extents cannot be emptied using aimage empty when a database is enabled for after-image Management. (13216)
FACT(s) (Environment):
Database is ai archiver enabled
All Supported Operating Systems
Progress/OpenEdge Product Family
CAUSE:
After-image management daemon could not find any space in its current list of destinations to continue the archival process due to lack of space. Since database was shutdown after that during physical redo it found that there was no empty ai availables to switch.
FIX:
Follow the steps below:
1. disable the ai archiver
$ rfutil dbname -C aiarchiver disable
2. rfutil dbname -C aimage list >> ailist.out
3. OS copy the FULL extents noted from the output in STEP 2 above
4. mark the FULL extents as EMPTY
$ rfutil dbname -C aimage empty
5. Re-enable ai archiving
$ rfutil dbname -C mark backedup
$ rfutil dbname -C aiarchiver enable
6. Restart the database with the appropriate ai archiver database startup parameters: -aiarcdir -aiarcinterval -aistall -aibufs.