Error BACKINT for Oracle Connection

[andreas_herzog]

hi @ maxdb gurus...

i have a problem backing up my maxdb 7.6.0.033 (serving for a mysap.erp2005 on aix 5.3) using the backint mechanism.

-> backup media created: two pipes and one parallel medium containing these pipes

-> bsi.env has been created

-> backint4sapdb.sar contains

4 staging areas each with 4096 MB

files per backint call 2

-> maxdb is about 57 gb perm. data area (and 6 gb temp.)

i use the backup wizard (dbmgui) to invoke a complete data backup which starts (pipes are created in the file system) and runs until approx. 4 gb...then the backup terminates with error "-24920 backup operation was unsuccesful. The database request failed with error -8020"

what might be the problem? are the staging areas too small? is says that when using only one stage area it must hold the complete database...can i then conclude that 4 staging areas must hold the database as well - meaning they must be around 15 gb each?

GreetZ, AH

[andreas_herzog]

see post....

[andreas_herzog]

so...it's solved! everything was fine incl. the environments etc. what was wrong was the user rights for selected files which should have been set by the tsm troops..but were not ;-(

-> have a look under /syslog/dsierror.log which hints to a problem accessing /usr/lpp/adsmcust/TSM.PWD

-> i changed that to 666 (was 600 before) and bingo!

GreetZ, AH

[Former Member]

Hello Andreas,

I remember such an issue from some time ago, which was solved with increasing the staging area size. Can you try this with larger staging areas, so that they hold the db, and update us with the result?

Thanks,

Ashwath

[andreas_herzog]

hi, thx for the answer.

do i get this correct: <b>the stage area must hold the complete database meaning i need (another) 70 gigs af disk space?</b> well....if this would be the solution i'd rather switch the database system which would be a shame...maxdb is kind of neat ggg

-> i don't have that much disk space...

any other solution?

GreetZ, AH

[Former Member]

Andreas,

I believe the other message said that the sum of the staging areas should be as large as the instance, not separately.

Can you copy the dbm.ebp file from the MAXDB rundirectory here? If you are an SAP customer, please create a CSS ticket about this.

Thanks,

Ashwath

[andreas_herzog]

yup...but that also means that the sum of the staging areas need as much space as the database ie. around 70 gigs netto! the staging files will be filled and thus grow until the defined size, meaning that the file system(s) need to be big enough!

everything works fine until the stage files are filled (up to the defined size) and then stops...when i change the sizes of the staging areas i can reproduce the error!

i compared the tsm implementation of that system with another system (live cache...kind of small regarding db size...) and found nothing serious...

-> dbm.ebp (AIX 5.3, MaxDB 7.6.0.033, ERP2005, TSM 5.3.3.0)

2006-11-09 13:56:50
Using environment variable 'TEMP' with value '' as directory for temporary files and pipes.
Using environment variable 'TMP' with value '' as directory for temporary files and pipes.
Using connection to Backint for MaxDB Interface.

2006-11-09 13:56:50
Checking existence and configuration of Backint for MaxDB.
    Using configuration variable 'BSI_ENV' = '/sapdb/data/wrk/TDV/bsi.env' as path of the configuration file of Backint for MaxDB.
    Setting environment variable 'BSI_ENV' for the path of the configuration file of Backint for MaxDB from '/sapdba/data/wrk/TDV/bsi.env' to configuration value '/sapdb/data/wrk/TDV/bsi.env'.
    Reading the Backint for MaxDB configuration file '/sapdb/data/wrk/TDV/bsi.env'.
        The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            ########################################################
        The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
        The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
        The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            ########################################################
        Found keyword 'BACKINT' with value '/sapdb/TDV/db/bin/backint'.
        The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            #
        Found keyword 'INPUT' with value '/sapdb/TDV/backup/backint4sapdb.in'.
        Found keyword 'OUTPUT' with value '/sapdb/TDV/backup/backint4sapdb.out'.
        Found keyword 'ERROROUTPUT' with value '/sapdb/TDV/backup/backint4sapdb.err'.
        The following line of the Backint for MaxDB configuration file does not start with a proper keyword and is ignored:
            #
        Found keyword 'PARAMETERFILE' with value '/sapdb/data/wrk/TDV/backint4sapdb.par'.
        Found keyword 'TIMEOUT_SUCCESS' with value '6000'.
        Found keyword 'TIMEOUT_FAILURE' with value '300'.
    Finished reading of the Backint for MaxDB configuration file.

    Using '/sapdb/TDV/db/bin/backint' as Backint for MaxDB program.
    Using '/sapdb/TDV/backup/backint4sapdb.in' as input file for Backint for MaxDB.
    Using '/sapdb/TDV/backup/backint4sapdb.out' as output file for Backint for MaxDB.
    Using '/sapdb/TDV/backup/backint4sapdb.err' as error output file for Backint for MaxDB.
    Using '/sapdb/data/wrk/TDV/backint4sapdb.par' as parameter file for Backint for MaxDB.
    Using '6000' 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 '/sapdb/data/wrk/TDV/dbm.knl' as backup history of a database to migrate.
    Using '/sapdb/data/wrk/TDV/dbm.ebf' as external backup history of a database to migrate.
    Checking availability of backups using backint's inquire function.
Check passed successful.

2006-11-09 13:56:50
Checking medium.
Check passed successfully.

2006-11-09 13:56:50
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 '/sapdb/TDV/db/bin/backint -u TDV -f backup -t file -p /sapdb/data/wrk/TDV/backint4sapdb.par -i /sapdb/TDV/backup/backint4sapdb.in -c'.
    Created temporary file '/sapdb/TDV/backup/backint4sapdb.out' as output for Backint for MaxDB.
    Created temporary file '/sapdb/TDV/backup/backint4sapdb.err' as error output for Backint for MaxDB.
    Writing '/sapdb/TDV/backup/back-tdv-data-m10.pipe #PIPE' to the input file.
    Writing '/sapdb/TDV/backup/back-tdv-data-m11.pipe #PIPE' to the input file.
Prepare passed successfully.

2006-11-09 13:56:51
Creating pipes for data transfer.
    Creating pipe '/sapdb/TDV/backup/back-tdv-data-m10.pipe' ... Done.
    Creating pipe '/sapdb/TDV/backup/back-tdv-data-m11.pipe' ... Done.
All data transfer pipes have been created.

2006-11-09 13:56:51
Starting database action for the backup.
    Requesting 'SAVE DATA QUICK TO '/sapdb/TDV/backup/back-tdv-data-m10.pipe' PIPE,'/sapdb/TDV/backup/back-tdv-data-m11.pipe' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BACK-TDV-DATA-G1'' from db-kernel.
The database is working on the request.

2006-11-09 13:56:51
Waiting until database has prepared the backup.
    Asking for state of database.
    2006-11-09 13:56:51 Database is still preparing the backup.
    Waiting 1 second ... Done.
    Asking for state of database.
    2006-11-09 13:56:52 Database is still preparing the backup.
    Waiting 2 seconds ... Done.
    Asking for state of database.
    2006-11-09 13:56:54 Database is still preparing the backup.
    Waiting 3 seconds ... Done.
    Asking for state of database.
    2006-11-09 13:56:57 Database is still preparing the backup.
    Waiting 4 seconds ... Done.
    Asking for state of database.
    2006-11-09 13:57:01 Database is still preparing the backup.
    Waiting 5 seconds ... Done.
    Asking for state of database.
    2006-11-09 13:57:06 Database has finished preparation of the backup.
The database has prepared the backup successfully.

2006-11-09 13:57:06
Starting Backint for MaxDB.
    Starting Backint for MaxDB process '/sapdb/TDV/db/bin/backint -u TDV -f backup -t file -p /sapdb/data/wrk/TDV/backint4sapdb.par -i /sapdb/TDV/backup/backint4sapdb.in -c >>/sapdb/TDV/backup/backint4sapdb.out 2>>/sapdb/TDV/backup/backint4sapdb.err'.
    Process was started successfully.
Backint for MaxDB has been started successfully.

2006-11-09 13:57:06
Waiting for end of the backup operation.
    2006-11-09 13:57:06 The backup tool is running.
    2006-11-09 13:57:06 The database is working on the request.

    2006-11-09 13:57:11 The backup tool is running.
    2006-11-09 13:57:11 The database is working on the request.

    2006-11-09 13:57:21 The backup tool is running.
    2006-11-09 13:57:21 The database is working on the request.

    2006-11-09 13:57:36 The backup tool is running.
    2006-11-09 13:57:36 The database is working on the request.

    2006-11-09 13:57:56 The backup tool is running.
    2006-11-09 13:57:56 The database is working on the request.

    2006-11-09 13:58:21 The backup tool is running.
    2006-11-09 13:58:21 The database is working on the request.

    2006-11-09 13:58:51 The backup tool is running.
    2006-11-09 13:58:51 The database is working on the request.

    2006-11-09 13:59:21 The database has finished work on the request.
    Receiving a reply from the database kernel.
    Got the following reply from db-kernel:
        SQL-Code              :-8020
        Date                  :20061109
        Time                  :00135703
        Database              :TDV
        Server                :r4335
        KernelVersion         :Kernel    7.6.00   Build 033-123-130-873
        PagesTransfered       :377688
        PagesLeft             :6903331
        MediaName             :BACK-TDV-DATA-G1
        Location              :/sapdb/TDV/backup/back-tdv-data-m10.pipe
        Errortext             :end of file
        Label                 :DAT_000000017
        IsConsistent          :true
        FirstLogPageNo        :247812
        DBStamp1Date          :20061109
        DBStamp1Time          :00135651
        BDPageCount           :7280971
        DevicesUsed           :2
        DatabaseID            :r4335:TDV_20061109_135703
        Max Used Data Page    :0
        Converter Page Count  :5201

    2006-11-09 13:59:21 The backup tool is running.

    2006-11-09 13:59:22 The backup tool process has finished work with return code 2.
    2006-11-09 13:59:22 The backup tool is not running.
The backup operation has ended.

2006-11-09 13:59:22
Filling reply buffer.
    Have encountered error -24920:
        The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.

    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 failed with error -8020.
Reply buffer filled.

2006-11-09 13:59:22
Cleaning up.
    Removing data transfer pipes.
        Removing data transfer pipe /sapdb/TDV/backup/back-tdv-data-m11.pipe ... Done.
        Removing data transfer pipe /sapdb/TDV/backup/back-tdv-data-m10.pipe ... Done.
    Removed data transfer pipes successfully.

    Copying output of Backint for MaxDB to this file.
    ---------- Begin of output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.out)----------
        Reading parameter file /sapdb/data/wrk/TDV/backint4sapdb.par.
        Using staging area /sapdb/TDV/backup/stage1 with a size of 1585446912 bytes.
        Using staging area /sapdb/TDV/backup/stage2 with a size of 1585446912 bytes.
        Using 1 file per Backint for Oracle call.
        Using /sapdb/TDV/dbs/backint as Backint for Oracle.
        Using /sapdb/TDV/dbs/initTDV.utl as parameterfile of Backint for Oracle.
        Using /sapdb/data/wrk/TDV/backint4oracle.his as history file.
        Using /sapdb/TDV/backup/backint4oracle.in as input of Backint for Oracle.
        Using /sapdb/TDV/backup/backint4oracle.out as output of Backint for Oracle.
        Using /sapdb/TDV/backup/backint4oracle.err as error output of Backint for Oracle.
        Using a maximal delay for a Backint for Oracle call of 60 seconds.
        
        Reading input file /sapdb/TDV/backup/backint4sapdb.in.
        Backing up pipe /sapdb/TDV/backup/back-tdv-data-m10.pipe.
        Backing up pipe /sapdb/TDV/backup/back-tdv-data-m11.pipe.
        Found 2 entries in the input file.
        
        Starting the backup.
        Starting pipe2file program(s).
        
        Waiting for creation of temporary files.
        1 temporary file is available for backup.
        Calling Backint for Oracle at 2006-11-09 13:59:20.
        Calling '/sapdb/TDV/dbs/backint -u TDV -f backup -t file -p /sapdb/TDV/dbs/initTDV.utl -i /sapdb/TDV/backup/backint4oracle.in -c' .
        Backint for Oracle ended at 2006-11-09 13:59:20 with return code 2.
        Backint for Oracle output: 
        Backint for Oracle output:                          Data Protection for mySAP(R)
        Backint for Oracle output: 
        Backint for Oracle output:              Interface between BR*Tools and Tivoli Storage Manager
        Backint for Oracle output:              - Version 5, Release 3, Modification 2.0  for AIX LF 64-bit -
        Backint for Oracle output:                    Build: 275  compiled on Nov 20 2005
        Backint for Oracle output:         (c) Copyright IBM Corporation, 1996, 2005, All Rights Reserved.
        Backint for Oracle output: 
        Backint for Oracle output: BKI2027I: Using TSM-API version 5.3.3.0 (compiled with 5.3.0.0).
        Backint for Oracle output: BKI2000I: Successfully connected to ProLE on port tdpr3ora64.
        Backint for Oracle output: BKI0005I: Start of program at: Thu Nov  9 13:59:20 MEZ 2006 .
        Backint for Oracle output: BKI5014E: Tivoli Storage Manager Error:
        Backint for Oracle output: ANS1035S (RC406)  Options file '*' could not be found.
        Backint for Oracle output: 
        Backint for Oracle output: BKI0020I: End of program at: Thu Nov  9 13:59:20 MEZ 2006 .
        Backint for Oracle output: BKI0021I: Elapsed time: 00 sec .
        Backint for Oracle output: BKI0024I: Return code is: 2.
        Backint for Oracle output: 
        Backint for Oracle error output: 
        
        Finished the backup unsuccessfully.
        
        #ERROR /sapdb/TDV/backup/back-tdv-data-m10.pipe
        #ERROR /sapdb/TDV/backup/back-tdv-data-m11.pipe
        
    ---------- End of output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.out)----------
    Removed Backint for MaxDB's temporary output file '/sapdb/TDV/backup/backint4sapdb.out'.
    Copying error output of Backint for MaxDB to this file.
    ---------- Begin of error output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.err)----------
        Backint for Oracle was unsuccessful.
        
    ---------- End of error output of Backint for MaxDB (/sapdb/TDV/backup/backint4sapdb.err)----------
    Removed Backint for MaxDB's temporary error output file '/sapdb/TDV/backup/backint4sapdb.err'.
    Removed the Backint for MaxDB input file '/sapdb/TDV/backup/backint4sapdb.in'.
Have finished clean up successfully.

i invoke the backup through dbmgui, not dbmcli!

any clues? thx in advance!

GreetZ, AH