Home > Articles > Certification > Other IT

  • Print
  • + Share This
This chapter is from the book

NDS 8 and eDirectory DIB

Versions of NDS prior to NDS 8 use a database engine called Recman, which, as the name suggests, is a record-based database management engine. NDS 8 and eDirectory uses a database engine called FLAIM, which stands for Flexible and Adaptable Information Manager. It is a database engine that is optimized for search and retrieval for a large number of small interrelated objects. (Novell's GroupWise email system also uses the FLAIM engine for its database.)

What Is FLAIM?

The initial idea for what later became FLAIM came from the genealogy world. Genealogical databases can be huge. When you consider that there are now more than 6 billion people on the planet, and a genealogical database stores information about the ancestors of these people, the sheer size of the data store and the complex relationships between arbitrarily structured data items challenges conventional database techniques. FLAIM was designed to handle databases of this scale and to have the very desirable attribute of handling information whose interrelationships (and hence the database schema) may not be known in advance of adding data to the database.

WordPerfect Corporation acquired the initial idea for FLAIM and developed it for use in the WordPerfect product. Over time, the database came to be known as FLAIM. With Novell's merger with WordPerfect in 1994, FLAIM became the property of Novell. At that time, NDS was just being introduced to the world and already had its own database. However, a few years later, when looking to make the next generation of NDS more scalable and more efficient, Novell investigated several databases as potential candidates but then realized that a high- performance, expandable, and quick database had already been developed in-house. To make a long story short, Novell eventually investigated FLAIM and decided to use it for NDS 8. The FLAIM development team joined the NDS development team, and the result was a much more robust directory.

As an impressive demonstration of the increased capabilities of eDirectory due to FLAIM, Novell has publicly showcased, several times since 2000, eDirectory running on a single server with 1.5 billion objects in the database!

A FLAIM database file is divided into logical files called containers. A FLAIM database can have multiple containers, including custom containers. Each FLAIM database must have at least a Default Data, a Local Dictionary, and a Tracker container. Data in one container can reference data in another container, by using the data record number (DRN) of the data being referenced. Table 3.1 lists the containers used in DS 8 and eDirectory databases.

FLAIM Container Descriptions

FLAIM Container


Default Data

Actual data records (entries, values, schema definitions, and so on)

Local Dictionary

Container and field definitions


A tracker for record changes


Partition records


Attribute syntax information


Stream records


The change cache for system-created Partition 0 (System)


The change cache for system-created Partition 1 (Schema)


The change cache for system-created Partition 2 (External Reference)


The change cache for system-created Partition 3 (Bindery)


The change cache for user-created Partition 4; this is the first user-created partition, and other containers will be created for each new partition


The Member container


The Private Key container


The Public Key container


The Reference container


The Equivalent to Me container


The NLS:Common_Certificate container


The NLS:List_Of_Handles container


The NDSPKI:Key_File container


The NLS:Cert_Peak_Used_Pool

These logical files may be stored in one or more physical files. eDirectory's implementation is that each physical file can grow to 2GB in size for NDS 8/eDirectory 8.5 and to 4GB in size for eDirectory 8.6 and higher; then the content is "spilled" over to another file. Therefore, depending on the size of your DS database, you will at least have a file called NDS.01, and when it reaches the maximum allowed size, an NDS.02 file is created, and when that file reaches the maximum allowed size, an NDS.03 file is created, and so on.


The FLAIM database can be compressed to remove blank or deleted records. Therefore, one of the options in DSRepair for DS 8 and eDirectory is to reclaim unused space. In Figure 3.6 later in this section, you can see the option about halfway down the list.

The following is a list of files employed by eDirectory 8.5 and higher:

  • NDS.xx—These are the main eDirectory database files, where xx is 01, 02, and so on. These files contain several types of records (such as partition and schema records) and also any eDirectory attribute indexes (such as CN and Surname, which can be used to speed up DS and Lightweight Directory Access Protocol queries) defined on the server.

  • NDS.RFL\xxxxxxxx.LOG—These are the RFL files, where xxxxxxxx ranges from 00000001 to FFFFFFFF. In order to protect against loss of data from a catastrophic failure such as a server crash, eDirectory uses an RFL to track all changes made to the database. Hence, if necessary, eDirectory can recommit lost data to the database by examining the xxxxxxxx.LOG files when the server is restarted.

  • As records are modified in the eDirectory database, but before they are committed to the disk, a copy of the changes is stored in the RFL 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 are maintained in the RFL file. This process is handled by the checkpoint thread on the server, and the size of the RFL file should decrease in time as transactions are written to disk.


    The RFLs are typically stored in the NDS.RFL directory under the main DIB folder (for example, for NetWare, it is SYS:_NETWARE\NDS.RFL). With eDirectory 8.7 and higher, you can store this file in a different location. To ensure database integrity, it is recommended that you do place the RFLs on a disk other than the one that holds the eDirectory database. You accomplish this by using the eDirectory Backup eMTool utility. It is possible to delete this directory, but it is not recommended because it involves the possibility of corrupting the eDirectory database.

  • NDS.DB—This is the roll-back log file. Because changes to the eDirectory database can include operations that require many data packets' worth of information to be sent to the server, eDirectory commits each packet to the database as it is being received—even though the entire transaction may not yet be complete. To safeguard against communication failure, eDirectory writes these transactions to a roll-back log. If an incomplete operation is encountered, eDirectory can use the roll-back log to undo incomplete transactions. (This is why TTS is not required for eDirectory to function.)

  • NDS.LCK—This is the NDS lock file. During database maintenance, sometimes the eDirectory database needs to be closed or locked for modifications. The NDS.LCK file is used to designate this locked condition. For eDirectory 8.5 and higher, this file shows as a 0 byte file. When the database is locked, attributes are changed on this file to signify that condition, and the file still shows as a 0 byte file. The timestamp of the file is updated whenever the database is locked or unlocked.

  • _NDSDB.INI—This is the database cache configuration file. When an eDirectory tuning parameter, such as the hard limit of the database cache size, is statically assigned, the setting is stored in the _NDSDB.INI file.

  • NOTE

    See Chapter 16, "Tuning eDirectory," for information about eDirectory tuning.

  • *.FRS—These are the temporary FLAIM record set files used by FLAIM.

  • NDT.DB—This is a DSRepair temporary database file for NDS.DB.

  • NDT.xx—These are DSRepair temporary database files for NDS.xx.

  • NDT.RFL\xxxxxxxx.LOG—These are DSRepair temporary database files, where xxxxxxxx ranges from 00000001 to FFFFFFFF.

When you're running DSRepair to repair the local database, one option (see Figure 3.6) is to use a temporary DS database during the repair. This allows the repair operation to be done on a copy of the database (using the NDT.* files) and not the live database.

Figure 3.6Figure 3.6 Select Use Temporary NDS Database During Repair? if you do not want to work on a live database.

Table 3.2 gives the names of the database files used by the various versions of NDS/eDirectory and summarizes their purposes. It also shows the location of each of these files.

Summary of DS File Functions

NDS 6 and Prior

NDS 7 (Recman)

NDS 8 and Above (FLAIM)

Located in SYS:_NETWARE

Located in SYS:_NETWARE

Located in SYS:_NETWARE on NetWare servers, [drive:]\Novell\NDS\ DIBFiles on Windows, and /var/nds/dib on Unix servers

ENTRY.NDS— Object information

0.DSD—Entry information

NDS.01—Entry, attribute, schema, and partition information; rolls over to NDS.02 and so on when file size reaches 2GB or 4GB

VALUE.NDS— Attribute information

1.DSD— Attribute information


BLOCK.NDS— Attribute (more than 16 bytes) overflow

2.DSD Attribute overflow


PARTITO.NDS— Partition information

3.DSD— Partition information



0.DSB—[Lookup table of names of .DSD files (only 28 bytes in size!)


Stream files (*.000)—Login scripts and so on

Stream files (*.000)—Login scripts and so on

Stream files (0-9, A-F.NDS)—Login scripts, and so on (for example, 1.NDS, 4F.NDS)



NDS.DB—Control file containing rollback information for aborted transactions



NDS.RFL\*.LOG—RFL file to reapply transactions that have been completed but not written to disk



_NDSDB.INI—File that keeps cache information



NDS.LCK—File that prevents access to database when open

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020