!!!HELP -6022 FFFFE87A ERR RFL TRANS GAP

[Павел aka GOLD]

После crash не откывается база. eDir 8.7.3.7. NW 5.1. Реплика раздела есть, но так как я не могу удалить ничего с упавшего сервера (с закрытой базой ничег оне выходит), то и не могу залить на него эту реплику. Все плохо...

[Павел aka GOLD]

-6022 FFFFE87A ERR RFL TRANS GAP

Source: eDirectory

Explanation: The database has detected that transactions are missing from the roll-forward log (RFL).

Possible Cause: This error is reported during recovery (after a server crash) or during a database restore operation if one or more RFL files have been damaged, resulting in a gap in the transactions recorded in the log.


Action: Run DSREPAIR.

[Павел aka GOLD]

SYS:\_NETWARE\NDS.RFL\xxxxxxx.LOG - Roll Forward Logs


To protect against loss of data from a catastrophic failure such as a server crash, eDirectory incorporates a Roll Forward log to track all changes made to the eDirectory database. The Roll Forward log naming convention starts at 00000001.LOG and, as needed, increments to FFFFFFFF.LOG. If necessary, eDirectory can recommit lost data to the database by examining the xxxxxxx.LOG files when the server is restarted.



As records are modified in the eDirectory database, but before those records are committed to the disk, a copy of the changes is entered into the Roll Forward log file. These entries are completed transactions that had not been written to disk. Upon server failure, the records committed to the disk may be lost, but the changes will be maintained in the Roll Forward Log. This process is handled by the check point thread on the server and this file should decrease in time as transactions are written to disk.



The Roll Forward logs are typically stored in the SYS:\_NETWARE\NDS.RFL directory. With eDirectory 8.7 it should be possible to store this file in a different location. To ensure database integrity, it could be recommended to place the Roll Forward logs on a disk other than the one holding the eDirectory database. This will be accomplished by using the backup and restore utility. It is possible to delete this file but it is NOT recommended. There is the possibility of corrupting the DS database.


Видимо именно с этим файлом неприятность.......