dbamboot
Synopsis
dbamboot
-P profile_name
[-a max_indexed_attributes]
[-c cache_size]
[-o real_object_block_size] |
-V
Purpose
Initializes the DirX Directory database described by the database profile. (See the dbamconfig command for details how to create a database profile.)
Options
-P profile_name
-
The profile name of the DirX Directory database to be initialized. The maximum size of a profile name is 32 characters.
-a max_indexed_attributes
-
The maximum number of attribute types for which indexes can be created when post-indexing is performed on the database. The minimum is 2, the maximum is 800, and the default is 20.
-c cache_size
-
The size of the database cache in megabytes (MB). The default is 512 MB.
-o real_object_block_size
-
The size of the REAL block type (the device stores real object blocks). Specify one of the following values:
-
0—1KB REAL block size (default)
-
1—4KB REAL block size
-
2—16KB REAL block size
-
3—64KB REAL block size
-
-V
-
Displays the DirX Directory product version, in the format:
product_version build_id date time
For example:
DirX Directory V9.0 9.4.428 2023:03:23 20:10 64-Bit
Description
The dbamboot command initializes the DirX Directory database(s) associated with (a) profile(s).
Before you can use dbamboot, you must:
-
Provide disk space for the database(s).
-
Create the profile(s) with dbamconfig
Use the -a option to specify how many attribute types may be indexed. If the size of the attribute value index (AVIDX) blocks configured by dbamconfig is not big enough to save all possible indexes, dbamboot reduces the specified number of indexed attribute types and displays a message (see also Example 3 below).
Use the -o option to control the size of a REAL block type. A block of type REAL is used to store a directory object; it contains the RDN of the object and all attributes assigned to the object. If the size of a REAL object block is not sufficient to store all of the directory object information, an extension block of type GENERAL is linked to the REAL block. Because the extension block is located in a different block of the device, accessing all of the object’s data is slower. Thus, you should select the size of the REAL blocks according to the size of the object data (if an extension block is typically necessary to store the object’s information, choose a larger block type).
After the database has been successfully initialized dbamboot displays information about database limitations, for example the maximum number of entries that can be saved, or the maximum number of attribute type indexes that can be created.
Examples
-
The following sample command initializes a DirX Directory database with the profile
Profile. The maximum number of indexes is 16. The block size of one REAL block is 4KB.dbamboot -PProfile -a16 -o1
-
The following sample command initializes a DirX Directory database with the profile
Profile1. The maximum number of indexes is 50.dbamboot –PProfile1 –a50
The sample output is as follows:
DB successfully initialized DB-limits: 10237286 objects 50 indexed attribute type(s) Calculated DB parameters: Internal AVIDX cluster size: 128 MB Internal AVIDX clusters: 204 -
The following sample command initializes a DirX Directory database with the profile
Profile2. The maximum number of indexes is 100.dbamboot indicates insufficient device space for the planned number of attribute type indexes. It reduces the number to a maximum value of 62 that can be saved to the AVIDX blocks created by the previous dbamconfig command for profile Profile2.
dbamboot –PProfile2 –a100
The sample output is as follows:
DB successfully initialized DB-limits: 10237286 objects 62 indexed attribute type(s) Calculated DB parameters: Internal AVIDX cluster size: 128 MB Internal AVIDX clusters: 248 NOTICE: restricted number of indexed attribute types due to an insufficient attribute index device size