DPB Parameters
Go Up to Connecting to Databases
The table below groups the DPB parameters by purpose.
User validation parameters | |
User name |
|
Password |
|
Encrypted password |
|
Database system encryption password |
|
System database administrator’s user name |
|
Authorization key for a software license |
|
Database encryption key |
|
Environmental control | |
Number of cache buffers |
|
|
|
Force writes to the database to be done asynchronously or synchronously. |
|
Instructs server to include validation checks during a database restore. |
|
Specify whether or not to reserve a small amount of space on each database page for holding backup versions of records when modifications are made. |
|
Specifies whether or not the database should be marked as damaged. |
|
Performs consistency checking of internal structures. |
|
Specifies database space preallocation. |
|
Use this parameter to request database preallocate information that is stored on the database header. |
|
This directive initiates an online dump. |
|
This parameter indicates that the current online dump files should be deleted and a full database dump executed (optional). |
|
Specifies the name of an online dump file, up to 255 characters. |
|
This parameter specifies the number of pages for the online dump file (optional). |
|
This indicates the backup database to archive. The equivalent command line is: gbak-archive_database. |
|
This parameter specifies the backup journals to archive. The equivalent command line is: gbak-archive_journals. |
|
This indicates the database to recover from archive. The equivalent command line is: gbak-archive_recover. |
|
This deletes all files in |
|
Configures the maximum number of database dumps allowed in the archive. The equivalent command line is: gfix-archive_dumps<n>. |
|
Recovers from archive until provided timestamp value. This is also known as Point-in-time-recovery. This is an optional argument. Full recovery will happen if this value is not provided. |
|
Shadow control | |
Activates the database shadow, an optional, duplicate, in-sync copy of the database. |
|
Deletes the database shadow. |
|
Replay logging system control | |
Activates a replay logging system to keep track of all database calls. |
|
Deactivates the replay logging system. |
|
Character set and message file specification | |
Language-specific message file. |
|
Character set to be used. |
|
The following table lists DPB parameters in alphabetical order. For each parameter, it lists its purpose, the length, in bytes, of any values passed with the parameter, and the value to pass.
Parameter | Purpose | Length | Value |
---|---|---|---|
|
Directive to activate the database shadow, which is an optional, duplicate, in-sync copy of the database. |
1 (Ignored) |
0 (Ignored) |
|
Backup database to archive. The equivalent command line is: gbak -archive_database |
1 |
1 |
|
Backup journals to archive. The equivalent command line is: gbak -archive_journals |
1 |
1 |
|
Configures the maximum number of database dumps allowed in the archive. The equivalent command-line is: gfix -archive_dumps <n> |
Number of bytes occupied by integer Value (1, 2 or 4) |
Number of database dump files allowed in the archive directory. 0 indicates no limit. |
|
Recovers database from archive. The equivalent command line is: gbak -archive_recover String specifying the name of an archived database dump file from the recovery folder, up to 255 characters. |
Number of bytes in string |
Archive database dump filename |
|
Deletes all files in gfix -archive_sweep <n>. |
Number of bytes occupied by integer Value (1, 2 or 4) |
Delete journal archives less than this Archive Sequence integer number |
|
Number signifying whether or not the database should be marked as damaged. 1 = mark as damaged 0 = do not mark as damaged |
1 |
0 or 1 |
|
Scope of |
1 |
0 or 1 |
|
Directive to delete a database shadow that is no longer needed. |
1 (Ignored) |
0 (Ignored) |
|
String encryption key, up to 255 characters |
Number of bytes in string |
String containing key |
|
Specifies whether database writes 0 = asynchronous; 1 = synchronous |
1 |
0 or 1 |
|
Instructs server to include validation checks during a database restore. |
||
|
String specifying the character set to be utilized |
Number of bytes |
String containing character set name |
|
String specifying a language-specific message file |
Number of bytes |
String containing message file name |
|
String authorization key for a software license |
Number of bytes |
String containing key |
|
Specifies whether or not a small amount of space on each database page is reserved for holding backup versions of records when modifications are made; keeps backup versions on the same page as the primary record to optimize update activity. 0 (default) = reserve space 1= do not reserve space |
1 |
0 or 1 |
|
Creates database with specified major ODS version as the target version. |
2-bytes Short integer |
Value denoting the major ODS version number of the target database |
|
Number of database cache buffers to allocate for use with the database; default=2,048. |
Number of bytes in the length indicator (1,2, or 4) |
Number of buffers to allocate |
|
Directive to initiate an online dump. |
1 |
0 or 1 |
|
Indicates the current online dump files should be deleted and a full database dump executed (optional). |
1 |
0 or 1 |
|
String specifying the name of an online dump file, up to 255 characters. |
Number of bytes in string |
Dump file name string |
isc_dpb_old_file_size |
Number of pages for online dump file (optional) |
Number of bytes for length indicator (1, 2, or 4) |
Number of pages for dump length |
|
String password, up to 255 characters. |
Number of bytes |
String containing password |
|
String encrypted password, up to 255 characters. |
Number of bytes |
String containing password |
|
Specifies database preallocation. It is only recognized and processed by isc_create_database(). isc_attach_database() silently ignores isc_dpb_preallocate. Use the isc_info_db_preallocate database info parameter to request database preallocate information stored on the database header page. |
4 |
|
|
Recovers from archive until provided timestamp value. This is also known as Point-in-time-recovery. This is an optional argument. Full recovery will happen if this value is not provided. Accepted Timestamp string format detailed in Formatting Dates for Input. For example: "2006-08-21 18:08:15" |
Number of bytes in string |
String indicating Timestamp, format |
|
Number indicating the SQL dialect used by the client; used by the gfix utility to set the dialect in the database header page. Dialect 3 gives access to features introduced in InterBase XE. |
1 |
1 - V5.x & V6 compatible 2 - diagnostic 3 - V6 only |
|
Number indicating the SQL dialect used by the client. Dialect 3 gives access to features introduced in InterBase XE. |
1 |
1 - V5.x & V6 compatible 2 - diagnostic 3 - V6 only |
|
String login role name. |
Number of bytes in string |
String |
|
Database system encryption password (SEP), up to 255 characters. |
Number of bytes in string |
String containing SEP |
|
String system DBA name, up to 255 characters. |
Number of bytes |
String containing SYSDBA name |
|
String user name, up to 255 characters. |
Number of bytes |
String containing user name |
Some parameters, such as isc_dpb_delete_shadow
, are directives that do not require additional parameters. Even so, you must still provide length and value bytes for these parameters. Set length to 1 and value to 0. InterBase ignores these parameter values, but they are required to maintain the format of the DPB.
With the InterBase service API, actions isc_action_svc_backup (isc_action_svc_restore) take new parameters, isc_spb_bkp_preallocate (isc_spb_res_preallocate), respectively. Both parameters take a 4-byte argument to specify the database preallocation in units of database pages. The service parameters have the same numeric value, but two symbolic constants are provided for source code clarity to show the proper intent.