If database extent files are deleted or not backed up the database cannot be restarted because of missing files. The only way to really fix the problem is to
- Restore from the latest backup
- Roll forward AI files that are created after the latest backup.
If the
Control Area .db file is missing, refer to Article:
How to recover a missing .db file on a multi-volume database If
After-Image .a file(s) are missing, refer to Article
How to recover from lost AI files ? If Before-Image .b files are missing, refer to Article Before Image (.bi) file is missing, corrupt, or lost and the database fails to start If
Data or Index extents .d are missing, refer to Articles
Recovering missing index storage area extents using UNLOCK EXTENTS How to recover from a missing extent using dummy extents? How to recover some data from a database with missing data extents and no backup?If Schema Area .d1 is missing, restoring to backup is the only real solution. It is unlikely that the schema layout of an object, (object number, object type, object block dbkey, index root etc) is the same when replacing the missing .d1 with a backup copy or reconstructed copy. If there is a mismatch in this information between the .d1 file and the actual data file, you won’t be able to find the data.
Note: No feature built-in into OpenEdge would show which OS user deleted the database files.
This type of information would have to be captured from a previously configured OS auditing tool.
