Hello all,
we are trying to backup our MaxDB using the backint interface. Unfortunately, the backup process fails with the error messages shown in the appended KNLDIAG log and EXTERNAL BACKUP log
KNLDIAG
0:32:53 31276 11560 COMMUNIC Releasing T132
2008-07-31 20:32:53 31276 12827 COMMUNIC wait for connection T132
2008-07-31 20:32:54 31258 11561 COMMUNIC Connecting T125 local 3626
2008-07-31 20:32:54 31276 12929 TASKING Task T125 started
2008-07-31 20:32:54 31276 11007 COMMUNIC wait for connection T125
2008-07-31 20:32:54 31276 11561 COMMUNIC Connected T125 local 3626
2008-07-31 20:32:54 31276 11560 COMMUNIC Releasing T125
2008-07-31 20:32:54 31276 12827 COMMUNIC wait for connection T125
2008-07-31 20:32:55 3634 ERR 11000 devio write error (fd = 54): Broken pipe
2008-07-31 20:32:55 31272 11000 vasynclo '/tmp/backintdb-pipe' devno 34 T72
2008-07-31 20:32:55 31259 12822 TASKING Thread 3634 joining
2008-07-31 20:32:55 3634 11566 stop DEVi stopped
2008-07-31 20:32:55 31272 52024 SAVE 63992 pages -> "/tmp/backintdb-pipe"
2008-07-31 20:32:55 31276 52012 SAVE new tape required 4300
2008-07-31 20:32:55 31276 1 Backup Backupmedium #1 (/tmp/backintdb-pipe) end of file
2008-07-31 20:32:55 31276 6 KernelCo + Backup error occured, Errorcode 4300 "new_hostfile_required"
2008-07-31 20:32:56 31276 12929 TASKING Task T142 started
2008-07-31 20:32:56 31258 11561 COMMUNIC Connecting T142 local 3626
2008-07-31 20:32:56 31276 11007 COMMUNIC wait for connection T142
2008-07-31 20:32:56 31276 11561 COMMUNIC Connected T142 local 3626
2008-07-31 20:32:56 31276 11560 COMMUNIC Releasing T142
2008-07-31 20:32:56 31276 12827 COMMUNIC wait for connection T142
2008-07-31 20:36:23 31276 11000 vasynclo '/sapdata/SOM/DISKD0001' devno 17 T143
2008-07-31 20:36:23 31259 12822 TASKING Thread 3629 joining
EXTERNAL BACKUP
2008-07-31 20:32:36
Setting environment variable 'TEMP' for the directory for temporary files and pipes to default ''.
Setting environment variable 'TMP' for the directory for temporary files and pipes to default ''.
Using connection to Backint for MaxDB Interface.
2008-07-31 20:32:36
Checking existence and configuration of Backint for MaxDB.
Reading the Backint for MaxDB configuration file '/sapdb/data/wrk/SOM/bsi.env'.
Found keyword 'BACKINT' with value '/sapdb/SOM/db/bin/backint'.
Found keyword 'INPUT' with value '/tmp/tsm-logs/som-backint4maxdb.in'.
Found keyword 'OUTPUT' with value '/tmp/tsm-logs/som-backint4maxdb.out'.
Found keyword 'ERROROUTPUT' with value '/tmp/tsm-logs/som-backint4maxdb.err'.
Found keyword 'PARAMETERFILE' with value '/sapdb/SOM/db/bin/backintmaxdbconfig.par'.
Found keyword 'TIMEOUT_SUCCESS' with value '600'.
Found keyword 'TIMEOUT_FAILURE' with value '300'.
Found keyword 'ORIGINAL_RUNDIRECTORY' with value '/sapdb/data/wrk/SOM'.
Finished reading of the Backint for MaxDB configuration file.
Using '/sapdb/SOM/db/bin/backint' as Backint for MaxDB program.
Using '/tmp/tsm-logs/som-backint4maxdb.in' as input file for Backint for MaxDB.
Using '/tmp/tsm-logs/som-backint4maxdb.out' as output file for Backint for MaxDB.
Using '/tmp/tsm-logs/som-backint4maxdb.err' as error output file for Backint for MaxDB.
Using '/sapdb/SOM/db/bin/backintmaxdbconfig.par' as parameter file for Backint for MaxDB.
Using '600' 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/SOM/dbm.knl' as backup history of a database to migrate.
Using '/sapdb/data/wrk/SOM/dbm.ebf' as external backup history of a database to migrate.
Checking availability of backups using backint's inquire function.
Check passed successful.
2008-07-31 20:32:36
Checking medium.
Check passed successfully.
2008-07-31 20:32:36
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/SOM/db/bin/backint -u SOM -f backup -t file -p /sapdb/SOM/db/bin/backintmaxdbconfig.par -i /tmp/tsm-logs/som-backint4maxdb.in -c'.
Created temporary file '/tmp/tsm-logs/som-backint4maxdb.out' as output for Backint for MaxDB.
Created temporary file '/tmp/tsm-logs/som-backint4maxdb.err' as error output for Backint for MaxDB.
Writing '/tmp/backintdb-pipe #PIPE' to the input file.
Prepare passed successfully.
2008-07-31 20:32:36
Creating pipes for data transfer.
Creating pipe '/tmp/backintdb-pipe' ... Done.
All data transfer pipes have been created.
2008-07-31 20:32:36
Starting database action for the backup.
Requesting 'SAVE DATA QUICK TO '/tmp/backintdb-pipe' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'backindb'' from db-kernel.
The database is working on the request.
2008-07-31 20:32:36
Waiting until database has prepared the backup.
Asking for state of database.
2008-07-31 20:32:36 Database is still preparing the backup.
Waiting 1 second ... Done.
Asking for state of database.
2008-07-31 20:32:37 Database is still preparing the backup.
Waiting 2 seconds ... Done.
Asking for state of database.
2008-07-31 20:32:39 Database is still preparing the backup.
Waiting 3 seconds ... Done.
Asking for state of database.
2008-07-31 20:32:42 Database is still preparing the backup.
Waiting 4 seconds ... Done.
Asking for state of database.
2008-07-31 20:32:46 Database is still preparing the backup.
Waiting 5 seconds ... Done.
Asking for state of database.
2008-07-31 20:32:51 Database has finished preparation of the backup.
The database has prepared the backup successfully.
2008-07-31 20:32:51
Starting Backint for MaxDB.
Starting Backint for MaxDB process '/sapdb/SOM/db/bin/backint -u SOM -f backup -t file -p /sapdb/SOM/db/bin/backintmaxdbconfig.par -i /tmp/tsm-logs/som-backint4maxdb.in -c >>/tmp/tsm-logs/som-backint4maxdb.out 2>>/tmp/tsm-logs/som-backint4maxdb.err'.
Process was started successfully.
Backint for MaxDB has been started successfully.
2008-07-31 20:32:51
Waiting for end of the backup operation.
2008-07-31 20:32:51 The backup tool is running.
2008-07-31 20:32:51 The database is working on the request.
2008-07-31 20:32:56 The backup tool process has finished work with return code 2.
2008-07-31 20:32:56 The backup tool is not running.
2008-07-31 20:32:56 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 :20080731
Time :00203248
Database :SOM
Server :bssomp02
KernelVersion :Kernel 7.6.00 Build 035-123-139-084
PagesTransfered :64000
PagesLeft :4907326
MediaName :backindb
Location :/tmp/backintdb-pipe
Errortext :end of file
Label :DAT_000000055
IsConsistent :true
FirstLogPageNo :3321207
DBStamp1Date :20080731
DBStamp1Time :00203244
BDPageCount :4971302
DevicesUsed :1
DatabaseID :bssomp02:SOM_20070910_162640
Max Used Data Page
Converter Page Count :2676
The backup operation has ended.
2008-07-31 20:32:56
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.
It seem to me that it is a MUST to use the Tivoli Data Protection for the MaxDB. Is anybody out there to tell me if this is right? Or ist it possible to directly transfer backup data from MaxDB to Tivoli Storage Manager (TSM) via a pipe?
Thanks and kind regards
Anette Feierabend
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.