Consultor Eletrônico

AI Header smashed (3644), how to fix

DRAFT COPY - Currently under review and edit.

INTRODUCTION:
=============
AI header smashed (3644) has been described in K-base 15112, this
K-base explains how to fix the problem.


WHY YOU NEED TO KNOW THIS:
===========================
To have the Databaseserver up and running these steps must be followed
Remember as always on a chrashed database to have a system backup.


PROCEDURAL APPROACH:
====================
Since the After image file has been corrupted it has to be removed
but this is not done by a simple DEL *.AI since that will give error
"Cannot find or open file *.ai, errno = 2 (43)"
When starting the server.
FOR SINGLE VOLUME DATABASE;

First disable after image;
rfutil databasename -C aimage end -a aimagefile
Delete the aimagefile
Backup the database using probkup;
probkup databasename devicename
rfutil databasename -C aimage begin -a aimagefile
and start the database
FOR MULTIVOLUME DATABASE;

disable after image ;
rfutil databasename -C aimage end
delete the aimagefiles (this to overcome corruption in the files)
Now comes the tricky part, a .st file must be created that places the
same number of aimage files that was deleted in the correct directory
example:
a C:\WORK\LINDA.A1 f 1024
a C:\WORK\LINDA.A2 f 1024
a C:\WOROKLINDA.A3
d C:\TEMP\LINDA.D1
b C:\TEMP\LINDA.B1
run the following command to create the aimage files + dummy db that
can be deleted afterwards
PROSTRCT CREATE TEST TEST.ST
Then the database must be marked as backed up done by using the
PROBKUP DATABASENAME DEVICENAME
start the after image again
RFUTIL DATABASENAME -C aimage begin

and finally start the server!

You can with caution use the PROSTRCT LIST command to create a .ST
from the database the problem with this is that you might delete the
Database when using the file, so be very carefull when using this tool
to recreate the afterimage extents.
KDA 19/3-1998
CFE 19/3-1998
Updated (13-04-1998 CFE)

Progress Software Technical Support Note # 17784