MaxDB backup through Backint on Oracle for TSM

Question

Hello Gurus:
We are using TSM backint interface for Oracle database. We are in the process of implementing SCM. We would like to schedule MaxDB backup through backint interface for Oracle.
I checked some forums and configured but backint is not recognizing MaxDB parameter file. Please see below parameter file and error logs.
*BSI File:*
BACKINT D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
INPUT D:\sapdb\data\wrk\backint\sapdb.in
OUTPUT D:\sapdb\data\wrk\backint\sapdb.out
ERROROUTPUT D:\sapdb\data\wrk\backint\sapdb.err
PARAMETERFILE D:\sapdb\data\wrk\LCD\maxdb_config.par
ORIGINAL_RUNDIRECTORY L:\sapdb\LCD\sapdata
*Parameter File - MaxDB_config*
STAGING AREA:     D:\TEMP\STAGE1 1024000 KB
FILES PER BACKINT CALL:     2
BACKINT:     D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
PARAMETERFILE OF BACKINT:     D:\oracle\SCD\102\database\initSCD.utl
HISTORY FILE:     D:\sapdb\data\wrk\BackintHistory
INPUTFILE OF BACKINT:     D:\sapdb\data\wrk\backint\backint.in
OUTPUTFILE OF BACKINT:     D:\sapdb\data\wrk\backint\backint.out
ERRORFILE OF BACKINT:     D:\sapdb\data\wrk\backint\backint.err
MAXIMAL DELAY OF BACKINT CALL:     30
Error Logs:
2010-03-30 17:38:35
Using environment variable 'TEMP' with value 'C:\Windows\TEMP' as directory for temporary files and pipes.
Using connection to Backint for MaxDB Interface.
2010-03-30 17:38:35
Checking existence and configuration of Backint for MaxDB.
    Using environment variable 'BSI_ENV' with value 'D:\sapdb\data\wrk\LCD\bsi.env' as path of the configuration file of Backint for MaxDB.
    Reading the Backint for MaxDB configuration file 'D:\sapdb\data\wrk\LCD\bsi.env'.
        Found keyword 'BACKINT' with value 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe'.
        Found keyword 'INPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.in'.
        Found keyword 'OUTPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.out'.
        Found keyword 'ERROROUTPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.err'.
        Found keyword 'PARAMETERFILE' with value 'D:\sapdb\data\wrk\LCD\maxdb_config.par'.
        Found keyword 'ORIGINAL_RUNDIRECTORY' with value 'L:\sapdb\LCD\sapdata'.
    Finished reading of the Backint for MaxDB configuration file.
    Using 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe' as Backint for MaxDB program.
    Using 'D:\sapdb\data\wrk\backint\sapdb.in' as input file for Backint for MaxDB.
    Using 'D:\sapdb\data\wrk\backint\sapdb.out' as output file for Backint for MaxDB.
    Using 'D:\sapdb\data\wrk\backint\sapdb.err' as error output file for Backint for MaxDB.
    Using 'D:\sapdb\data\wrk\LCD\maxdb_config.par' as parameter file for Backint for MaxDB.
    Using '300' seconds as timeout for Backint for MaxDB in the case of success.
    Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
    Using 'L:\sapdb\LCD\sapdata\dbm.knl' as backup history of a database to migrate.
    Using 'L:\sapdb\LCD\sapdata\dbm.ebf' as external backup history of a database to migrate.
    Checking availability of backups using backint's inquire function.
Check passed successful.
2010-03-30 17:38:35
Checking medium.
Check passed successfully.
2010-03-30 17:38:35
Preparing backup.
    Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
    Setting environment variable 'BI_REQUEST' to value 'NEW'.
    Setting environment variable 'BI_BACKUP' to value 'FULL'.
    Constructed Backint for MaxDB call 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe -u LCD -f backup -t file -p D:\sapdb\data\wrk\LCD\maxdb_config.par -i D:\sapdb\data\wrk\backint\sapdb.in -c'.
    Created temporary file 'D:\sapdb\data\wrk\backint\sapdb.out' as output for Backint for MaxDB.
    Created temporary file 'D:\sapdb\data\wrk\backint\sapdb.err' as error output for Backint for MaxDB.
    Writing '
.\pipe\BACKscd #PIPE' to the input file.
Prepare passed successfully.
2010-03-30 17:38:35
Starting database action for the backup.
    Requesting 'SAVE DATA QUICK TO '
.\pipe\BACKscd' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'Back123'' from db-kernel.
The database is working on the request.
2010-03-30 17:38:35
Waiting until database has prepared the backup.
    Asking for state of database.
    2010-03-30 17:38:35 Database is still preparing the backup.
    Waiting 1 second ... Done.
    Asking for state of database.
    2010-03-30 17:38:36 Database has finished preparation of the backup.
The database has prepared the backup successfully.
2010-03-30 17:38:36
Starting Backint for MaxDB.
    Starting Backint for MaxDB process 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe -u LCD -f backup -t file -p D:\sapdb\data\wrk\LCD\maxdb_config.par -i D:\sapdb\data\wrk\backint\sapdb.in -c >>D:\sapdb\data\wrk\backint\sapdb.out 2>>D:\sapdb\data\wrk\backint\sapdb.err'.
    Process was started successfully.
Backint for MaxDB has been started successfully.
2010-03-30 17:38:36
Waiting for end of the backup operation.
    2010-03-30 17:38:36 The backup tool process has finished work with return code 2.
    2010-03-30 17:38:36 The backup tool is not running.
    2010-03-30 17:38:36 The database is working on the request.
    2010-03-30 17:38:36 The database is working on the request.
    2010-03-30 17:38:41 The database is working on the request.
    2010-03-30 17:38:51 The database is working on the request.
    2010-03-30 17:39:06 The database is working on the request.
    2010-03-30 17:39:26 The database is working on the request.
    2010-03-30 17:39:37 Canceling Utility-task after a timeout of 60 seconds elapsed ... OK.
    2010-03-30 17:39:38 The database has finished work on the request.
    Receiving a reply from the database kernel.
    Got the following reply from db-kernel:
        SQL-Code              :-903
The backup operation has ended.
2010-03-30 17:39:38
Filling reply buffer.
    Have encountered error -24920:
        The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
    Constructed the following reply:
        ERR
        -24920,ERR_BACKUPOP: backup operation was unsuccessful
        The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
Reply buffer filled.
2010-03-30 17:39:38
Cleaning up.
    Copying output of Backint for MaxDB to this file.
    **-- Begin of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)--**
                                 **Data Protection for SAP(R)**
                     **Interface between BRTools and Tivoli Storage Manager***
                     **- Version 6, Release 1, Modification 0.0  for Win x64 -**
                           **Build: 358  compiled on Nov  4 2008**
                **(c) Copyright IBM Corporation, 1996, 2008, All Rights Reserved.**
        **BKI8310E: The keyword MAXIMAL is not allowed.**
        **BKI1001E: syntax error in file 'D:\sapdb\data\wrk\LCD\maxdb_config.par'. Exiting program.**
        **BKI0020I: End of program at: 03/30/10 17:38:36 .**
        **BKI0021I: Elapsed time: 00 sec .**
        **BKI0024I: Return code is: 2.**       
End of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)----
    Removed Backint for MaxDB's temporary output file 'D:\sapdb\data\wrk\backint\sapdb.out'.
    Copying error output of Backint for MaxDB to this file.
Begin of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
End of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
    Removed Backint for MaxDB's temporary error output file 'D:\sapdb\data\wrk\backint\sapdb.err'.
    Removed the Backint for MaxDB input file 'D:\sapdb\data\wrk\backint\sapdb.in'.
Have finished clean up successfully.
Any help will be appreciated.
Thanks,
Miral.

Answer 1

> We are using TSM backint interface for Oracle database. We are in the process of implementing SCM. We would like to schedule MaxDB backup through backint interface for Oracle.
> *BSI File:*
>
> BACKINT D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
> *Parameter File - MaxDB_config*
> STAGING AREA:     D:\TEMP\STAGE1 1024000 KB
> FILES PER BACKINT CALL:     2
> BACKINT:     D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
>
>     Using 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe' as Backint for MaxDB program.
> 2010-03-30 17:39:38
> Cleaning up.
>     Copying output of Backint for MaxDB to this file.
>                                  **Data Protection for SAP(R)**
>                      **Interface between BRTools and Tivoli Storage Manager***
>                      **- Version 6, Release 1, Modification 0.0  for Win x64 -**
>         **BKI8310E: The keyword MAXIMAL is not allowed.**
>         **BKI1001E: syntax error in file 'D:\sapdb\data\wrk\LCD\maxdb_config.par'. Exiting program.**
>         **BKI0020I: End of program at: 03/30/10 17:38:36 .**
>         **BKI0021I: Elapsed time: 00 sec .**
>         **BKI0024I: Return code is: 2.**       
>
>     -
End of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)----
>     Removed Backint for MaxDB's temporary output file 'D:\sapdb\data\wrk\backint\sapdb.out'.
>     Copying error output of Backint for MaxDB to this file.
>     -
Begin of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
@Markus: thanks for the hint with the quote-formatting option!
Concerning the issue:
Sorry, but you misunderstood the way how the general BACKINT for Oracle interface is used with MaxDB.
See, MaxDB comes with a own BACKINT executable.
This is a enhanced BACKINT tools that allows pipes as data input channels - which is not supported by the Backint for Oracle.
The MaxDB Backint serves as a adapter program between the MaxDB Kernel and the backint for Oracle program.
So instead of
BACKINT:     D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
you should point it to the MaxDB provided adapater program.
I propose to revisit the documentation on that topic [Connecting to a Backint for Oracle Interface |http://maxdb.sap.com/doc/7_7/45/746a5712e14022e10000000a1553f6/content.htm].
best regards,
Lars