Kbase P13542: Database crashed, after imaging running during crash
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/29/2005 |
|
Status: Unverified
FACT(s) (Environment):
Progress 8.3X
SYMPTOM(s):
Database crashed
Using variable ai files
After imaging active when database crashed
Unable to re-start database in multi-user mode
** The file <name> is not the correct after-image file. (829)
Rfutil extent list displays A2 extent busy; all other Ai extents were empty
Unable to disable ai
CHANGE:
Bi file reached 2 GB limit, brought down database
CAUSE:
The database master block considers ai active, in the process of rolling over to next ai extent. Therefore, the database cannot start in multi-user mode as after imaging is active.
FIX:
Go to backup and use ai files to bring database to current state