Configuration File (Adapter Program) 

To be able to use the backup tool Backint for Oracle, you must, as a step of the Configuration of the Backint for Oracle Connection, create a configuration file for the Backint for SAP DB adapter program. This configuration file tells the adapter program, among other things, where it should create the necessary temporary files and where it can find the interface program Backint for Oracle. The name of this configuration file must be stored in the configuration file for the Backint for SAP DB connection (Parameter PARAMETERFILE <value>).

Procedure

You can define a parameter in the format <key_string> <value_string> in each line of the configuration file.

If you want to avoid a certain parameter being set by the configuration file, you must completely remove the corresponding line with the format <key_string> <value_string> from the configuration file.

You can use the following keywords to define parameters:

Keyword(s)

Value(s)

STAGING AREA:

Absolute path and size of a temporary file
STAGING AREA: <absolute_path> <size> [KB|MB|GB]
If you do not specify a size unit, the size is configured in bytes.
Up to 256 temporary files of this type can be defined. Exactly one temporary file is used for each pipe used.

FILES PER BACKINT CALL:

Maximum number of temporary files that are to be processed by Backint for Oracle concurrently.
In this way, temporary files can be created at the same time as other temporary files are backed up.

BACKINT:

Absolute name of the interface program Backint for Oracle

PARAMETERFILE OF BACKINT:

Absolute name of a parameter file for the interface program Backint for Oracle
The line
PARAMETERFILE OF BACKINT: <value_string> should not appear in the configuration file, if no parameter file is required for Backint for Oracle.
The name of the parameter file is transferred to Backint for Oracle as a parameter. It is therefore possible to configure the Backint for Oracle program in accordance with the specifications in this parameter file.
The description of a parameter file of this type is provided by the backup tool vendor.

HISTORY FILE:

Absolute name of the history file
The adapter program stores the information required for restores in the history file.
If more than one SAP DB version is backed up on one server, a different history file must be used for each database system. If the history file is damaged, this file must be restored manually with the help of the Backint for Oracle program. You should ensure that you are familiar with Backint for Oracle and handling of your backup tool in case this is necessary.

INPUTFILE FOR BACKINT:
OUTPUT FILE FOR BACKINT
ERRORFILE FOR BACKINT:

Specifies which files are used for standard input, standard output and error output for the Backint for Oracle processes to be started
These files must be different from the files configured for the Backint for SAP DB connections (see INPUT, OUTPUT, ERROROUTPUT in
Configuration File (Backint for SAP DB))

MAXIMAL DELAY OF BACKINT CALL:

Maximum time in seconds that Backint for Oracle should wait after the creation of a temporary file through a call of Backint for Oracle, until the complete number of temporary files has been created, as specified in the line FILES PER BACKINT CALL: <value_string>.
This specification helps to avoid deadlocks that can occur in exceptional situations. The length of time must be large enough so that during normal backup operation, the configured number of temporary files can be saved at the same time using Backint for Oracle. On the other hand, the time must not be too large, so that the end of the backup is not extended too far due to unfavorable configurations.

OMIT LAST DIRECTORY DELIMITER ON RESTORE:

Specifies whether or not the adapter program should ignore the closing slash (/ or \) of an absolute directory name for Backint for Oracle.
NO (Default): 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 specification is supported as of the following SAP DB versions: 7.2.05.016, 7.3.00.021, 7.4.02.002, 7.4.03.000

See also:

Example configuration file