If you want to use an external backup tool with a Backint for Oracle interface for a MaxDB database system, you first have to configure the connection between MaxDB and Backint for Oracle (see 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>
<key_string> |
Keyword for a parameter; can consist of one or more words |
<value_string> |
Value(s) of the parameter |
You can define the following parameters for the MaxDB adapter program:
Parameter |
Syntax |
Description |
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. |
Maximum number of temporary files that are to be processed by Backint for Oracle concurrently. |
FILES PER BACKINT CALL: <number> |
Default
value: 1 |
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 external 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 |
OUTPUT FILE 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 |
MAXIMAL DELAY OF BACKINT CALL: <number> |
Default
value: 10 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 enough time to save the configured number of temporary files (FILES PER BACKINT CALL:). However, you must also make sure that the end of the backup process is not delayed for too long. |
Specifies whether or not the adapter program should ignore the closing slash (/ or \) of an absolute directory name for Backint for Oracle. |
OMIT LAST DIRECTORY DELIMITER ON RESTORE: <option> <option> ::= YES | NO |
NO: Default
value |
Value of the environment variable BI_CALLER |
BI_CALLER_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: |
See also:
Example of a Parameter File for the MaxDB Adapter Program