Creating the Parameter File for the MaxDB Adapter Program


If you want to use another provider’s backup tool with a Backint for Oracle interface for a MaxDB database system, you first have to configure the connection between the MaxDB and the Backint for Oracle program (Configuring the Backint for Oracle Connection). Creating the parameter file for the MaxDB adapter program is one of the required steps for this configuration.

In the parameter file you determine where the adapter program generates the required temporary files, and where the interface program Backint for Oracle is located.

You enter the name of this parameter file in the configuration file of the Backint for MaxDB (keyword PARAMETERFILE) when you configure Backint for MaxDB.


On every line in the parameter file you specify a parameter of the MaxDB adapter program. When you do this, at the beginning of each line you have to specify the keyword for the parameter and then the relevant value(s). Lines that do not begin with keywords are ignored by the system.


<key_string> <value_string>


Keyword for a parameter; can consist of one or more words


Value(s) of the parameter

You can define the following parameters for the MaxDB adapter program:




Absolute path and size of a temporary file

STAGING AREA: <absolute_path>/<file_name> <size> [KB|MB|GB]

You can define up to 256 temporary files.
If you do not specify a unit for the size, the size is configured in bytes.
The program uses precisely one temporary file for each pipe.

Maximum number of temporary files that are to be processed by Backint for Oracle concurrently.


Default value: 1
The program can save temporary files and generate other temporary files at the same time, provided that the
<number> value specified here is smaller than the number of the backup/recovery pipes used.

Absolute path and name of the Backint for Oracle program

BACKINT: <absolute_path>/<file_name>

Absolute path and name of the configuration file for the Backint for Oracle program

PARAMETERFILE OF BACKINT: <absolute_path>/<file_name>h>

Define this parameter only if you have to create a configuration file for the backup tool. Otherwise, do not use this keyword.

Absolute path and name of the backup history

HISTORY FILE: <absolute_path>/<file_name>

The backup history contains the information that is required for the restore function.

Absolute path and name of the standard input file

INPUTFILE FOR BACKINT: <absolute_path>/<file_name>

These files must differ from the files that are configured for the Backint for MaxDB connection (see INPUT, OUTPUT, ERROROUTPUT in Creating the Configuration File for Backint for MaxDB).

Absolute path and name of the standard output file

OUTPUTFILE FOR BACKINT: <absolute_path>/<file_name>

Absolute path and name of the standard error output file

ERRORFILE FOR BACKINT: <absolute_path>/<file_name>

Maximum waiting time in seconds between creating a temporary file and starting to save it by using Backint for Oracle


Default value: 10
This value is specified to prevent deadlocks in exceptional situations during a parallel backup or a restore.

If the temporary files are created at different speeds and one temporary file is already complete, the adapter program waits a maximum of the time specified here for another temporary file to be completely created. If no other file is created within the specified time, the existing temporary file is saved.

Specify a large time period so that the configured number of temporary files (FILES PER BACKINT CALL:) can be saved at the same time.

Specifies whether or not the adapter program should ignore the closing slash (/ or \) of an absolute directory name for Backint for Oracle.


<option> ::= YES | NO

NO: Default value
The slash is not ignored.
YES: The slash is ignored.
Use this option to avoid problems with Backint for Oracle implementations that do not expect a closing slash (/ or \) at the end of a directory name.
This parameter is supported for the following MaxDB versions as of the specified build numbers:
7.4.03 from build 000, 7.4.02 from build 002, 7.3.00 from build 021, 7.2.05 from build 016

Value of the environment variable BI_CALLER

BI_CALLER VALUE: <value>: <value>

Set this parameter only if the backup tool requires you to set this parameter. In accordance with the system default, the variable BI_CALLER is removed from the environment before Backint for Oracle is called. For most Backint for Oracle implementations you do not need to set this value since these implementations allow the environment variables BI_CALLER to be missing. This parameter is supported for the following MaxDB versions as of the specified build numbers:
All versions from 7.4.04 build 000, 7.4.03 from build 006, 7.4.02 from build 016, 7.3.0 from build 029, 7.2.05 from build 025.

See also:

Example of a Parameter File for the MaxDB Adapter Program