The Basic Repair Wizard lets you perform an unattended full repair, local database repair, or single object repair. You can also check external references and delete unknown leaf objects.
An unattended full repair checks for and repairs most critical eDirectory errors in the eDirectory database files of a given server. It performs eight primary operations each time it is run, none of which require any intervention by the administrator. During some of these operations, the local database is locked. An unattended full repair builds a temporary set of local database files and runs the repair operation against those files. That way, if a serious problem develops, the original files are still intact.
This is the suggested means of repair if you are not familiar with the interactive options of the Local Database Repair. Running the Unattended Full Repair might require twice the amount of disk space currently used by the database files. See Performing a Local Database Repair for more information.
Rebuilding the operational indexes used by eDirectory is possible only when the local database is locked.
The following table lists the operations performed during an unattended full repair:
To perform an unattended full repair:
In Novell iManager, click the Roles and Tasks button .
Click eDirectory Maintenance Utilities > Basic Repair.
Specify the server that will perform the operation, then click Next.
Specify a user name, password, and context for the server where you will perform the operation, then click Next.
Click Unattended Full Repair, then click Start.
Follow the online instructions to complete the operation.
Use this repair operation to resolve inconsistencies in the local database so that it can be opened and accessed by eDirectory.
A local database repair can be performed on a temporary set of files if you specifically request it. Otherwise, the repair operation will take place on the live database.
Performing the repair operation on a temporary set of database files requires closing the database during this part of the operation. If you choose to work on a temporary set of files, you will be prompted to commit the repair modifications before they are made permanent. Otherwise, changes take place immediately.
Following a repair operation, you can view a log of the repair operations to determine if further operations are required to complete the repair. For more information, see Viewing and Configuring the Repair Log File.
In Novell iManager, click the Roles and Tasks button .
Click eDirectory Maintenance Utilities > Basic Repair.
Specify the server that will perform the operation, then click Next.
Specify a user name, password, and context for the server where you will perform the operation, then click Next.
Click Local Database Repair, then click Next.
Specify the options you want for running the local repair, then click Start.
Follow the online instructions to complete the operation.
This repair operation checks each external reference object to determine if a replica containing the object can be located. If all the servers containing a replica of the partition that the object is in are inaccessible, the object will not be found. If the object cannot be found, a warning is posted.
This operation also provides obituary information.
In Novell iManager, click the Roles and Tasks button .
Click eDirectory Maintenance Utilities > Basic Repair.
Specify the server that will perform the operation, then click Next.
Specify a user name, password, and context for the server where you will perform the operation, then click Next.
Click Check External References, then click Start.
Follow the online instructions to complete the operation.
This repair operation will try to resolve any inconsistencies in an eDirectory object which might be preventing eDirectory from accessing such data. This operation works only on user-created partitions and on the external reference partition.
This operation is performed on the live database files. If the corruption is at the physical level, you might need to perform a Physical and Structure check before the Single Object Repair is run.
Make sure you always have a current backup copy of the eDirectory database.
In Novell iManager, click the Roles and Tasks button .
Click eDirectory Maintenance Utilities > Basic Repair.
Specify the server that will perform the operation, then click Next.
Specify a user name, password, and context for the server where you will perform the operation, then click Next.
Click Single Object Repair, then click Start.
Specify the object you want to repair, then click Next.
Follow the online instructions to complete the operation.
Repair changes inconsistent objects to Unknown objects when they do not have mandatory properties or are invalid in other respects (their properties don't meet minimum requirements for an object type). Unknown objects are real objects and eDirectory knows about them. They are unknown because their object class cannot be fully validated. Unknown objects, represented by question mark icons, can be deleted but cannot easily be changed back to their original object type.
This repair operation deletes all objects in the local eDirectory database that have the Unknown object class and maintain no subordinate objects. The deletion is later synchronized to other replicas in the eDirectory tree.
IMPORTANT: This operation should not be run unless you understand the consequences or have been advised by Novell Support to run it.
In Novell iManager, click the Roles and Tasks button .
Click eDirectory Maintenance Utilities > Basic Repair.
Specify the server that will perform the operation, then click Next.
Specify a user name, password, and context for the server where you will perform the operation, then click Next.
Click Delete Unknown Leaf Objects, then click Start.
Follow the online instructions to complete the operation.