cancel
Showing results for 
Search instead for 
Did you mean: 

Backup error occured, Error code 3700 "hostfile_error"

Former Member
0 Kudos

HI,

We are trying to MaxDB database backup to tape and getting below error.

===================================================================================================

ERR

-24988,ERR_SQL: SQL error

-104,DBM command impossible at this time

3,Data backup failed

Servertask Info: because Error in backup task occured

Job 1 (Backup / Restore Medium Task) [executing] WaitingT204 Result=3700

Error in backup task occured, Error code 3700 "hostfile_error"

Backupmedium #1 (
.\pipe\backup) I/O Error

Backup error occured, Error code 3700 "hostfile_error"

===================================================================================================

I went through the previous threads regarding the same error but couldn't find a solution.

System Info is Win 2008, MaxDB version 7.7.07.14.

Here is the complete log, please suggest what can be done.

===================================================================================================

      • DBA Action starts:

Timestamp: 20110831100408 Function: sda Object: DATA

2011-08-31 10:04:08

Using environment variable 'TEMP' with value 'C:\Windows\TEMP' as directory for temporary files and pipes.

Using connection to Backint for MaxDB Interface.

2011-08-31 10:04:09

Checking existence and configuration of Backint for MaxDB.

Using environment variable 'BSI_ENV' with value 'G:\sapdb\data\wrk\MXP\bsi.env' as path of the configuration file of Backint

Reading the Backint for MaxDB configuration file 'G:\sapdb\data\wrk\MXP\bsi.env'.

Found keyword 'BACKINT' with value 'D:\sapdb\MXP\db\bin\backint.exe'.

Found keyword 'INPUT' with value 'G:\sapdb\data\wrk\backint\sapdb.in'.

Found keyword 'OUTPUT' with value 'G:\sapdb\data\wrk\backint\sapdb.out'.

Found keyword 'ERROROUTPUT' with value 'G:\sapdb\data\wrk\backint\sapdb.err'.

Found keyword 'PARAMETERFILE' with value 'G:\sapdb\data\wrk\MXP\maxdb_config.par'.

Found keyword 'ORIGINAL_RUNDIRECTORY' with value 'G:\sapdb\MXP\sapdata'.

Finished reading of the Backint for MaxDB configuration file.

Using 'D:\sapdb\MXP\db\bin\backint.exe' as Backint for MaxDB program.

Using 'G:\sapdb\data\wrk\backint\sapdb.in' as input file for Backint for MaxDB.

Using 'G:\sapdb\data\wrk\backint\sapdb.out' as output file for Backint for MaxDB.

Using 'G:\sapdb\data\wrk\backint\sapdb.err' as error output file for Backint for MaxDB.

Using 'G:\sapdb\data\wrk\MXP\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 'G:\sapdb\MXP\sapdata\dbm.knl' as backup history of a database to migrate.

Using 'G:\sapdb\MXP\sapdata\dbm.ebf' as external backup history of a database to migrate.

Checking availability of backups using backint's inquire function.

Check passed successful.

2011-08-31 10:04:09

Checking medium.

Check passed successfully.

2011-08-31 10:04:09

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:\sapdb\MXP\db\bin\backint.exe -u MXP -f backup -t file -p G:\sapdb\data\wrk\MXP\maxdb_

Created temporary file 'G:\sapdb\data\wrk\backint\sapdb.out' as output for Backint for MaxDB.

Created temporary file 'G:\sapdb\data\wrk\backint\sapdb.err' as error output for Backint for MaxDB.

Writing '
.\pipe\backup #PIPE' to the input file.

Prepare passed successfully.

2011-08-31 10:04:09

Starting database action for

the backup.

Requesting 'SAVE DATA QUICK TO '
.\pipe\backup' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BackupMXP'' from db-kernel.

The database is working on the request.

2011-08-31 10:04:09

Waiting until database has prepared the backup.

Asking for state of database.

2011-08-31 10:04:09 Database is still preparing the backup.

Waiting 1 second ...

Done.

Asking for state of database.

2011-08-31 10:04:10 Database has finished preparation of the backup.

The database has prepared the backup successfully.

2011-08-31 10:04:10

Starting Backint for MaxDB.

Starting Backint for MaxDB process 'D:\sapdb\MXP\db\bin\backint.exe -u MXP -f backup -t file -p G:\sapdb\data\wrk\MXP\maxdb_

Process was started successfully.

Backint for MaxDB has been started successfully.

2011-08-31 10:04:10

Waiting for end of the backup operation.

2011-08-31 10:04:10 The backup tool is running.

2011-08-31 10:04:10 The database is working on the request.

2011-08-31 10:04:15 The backup tool is running.

2011-08-31 10:04:15 The database is working on the request.

2011-08-31 10:04:25 The backup tool is running.

2011-08-31 10:04:25 The database is working on the request.

2011-08-31 10:04:40 The backup tool is running.

2011-08-31 10:04:40 The database is working on the request.

2011-08-31 10:05:00 The backup tool is running.

2011-08-31 10:05:00 The database is working on the request.

2011-08-31 10:05:13 The backup tool process has finished work with return code 2.

2011-08-31 10:05:13 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.

2011-08-31 10:05:13

Filling reply buffer.

Have encountered error -24920:

The backup tool failed with 2 as sum of exit codes. The database request failed 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 failed with error -903.

Reply buffer filled.

2011-08-31 10:05:13

Cleaning up.

Copying output of Backint for MaxDB to this file.

-


Begin of output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.out)----


Reading parameter file G:\sapdb\data\wrk\MXP\maxdb_config.par.

Using staging area D:\TEMP\STAGE1 with a size of 1048576000 bytes.

Using staging area D:\TEMP\STAGE2 with a size of 1048576000 bytes.

Using 2 file per Backint for Oracle call.

Using C:\Program Files\Tivoli\TSM\tdp_r3\ora64\backint.exe as Backint for Oracle.

Using G:\sapdb\data\wrk\MXP\initMXP.utl as parameterfile of Backint for Oracle.

Using G:\sapdb\data\wrk\MXP\BackintHistory.txt as history file.

Using G:\sapdb\data\wrk\backint\backint1.in as input of Backint for Oracle.

Using G:\sapdb\data\wrk\backint\backint1.out as output of Backint for Oracle.

Using G:\sapdb\data\wrk\backint\backint1.err as error output of Backint for Oracle.

Using a maximal delay for a Backint for Oracle call of 3600 seconds.

Reading input file G:\sapdb\data\wrk\backint\sapdb.in.

Backing up pipe
.\pipe\backup.

Found 1 entry 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 2011-08-31 10:05:12.

Calling 'C:\Program Files\Tivoli\TSM\tdp_r3\ora64\backint.exe -u MXP -f backup -t file -p G:\sapdb\data\wrk\MXP\initMXP.

Backint for Oracle ended at 2011-08-31 10:05:13 with return code 2.

Backint for Oracle output:

Backint for Oracle output: Data Protection for SAP(R)

Backint for Oracle output:

Backint for Oracle output: Interface between BR*Tools and Tivoli Storage Manager

Backint for Oracle output: - Version 6, Release 1, Modification 0.0 for Win x64 -

Backint for Oracle output: Build: 358 compiled on Nov 4 2008

Backint for Oracle output: (c) Copyright IBM Corporation, 1996, 2008, All Rights Reserved.

Backint for Oracle output:

Backint for Oracle output: BKI2027I: Using TSM-API version 6.2.3.1 (compiled with 5.3.2.0).

Backint for Oracle output: BKI2000I: Successfully connected to ProLE on port tdpr3ora64.

Backint for Oracle output: BKI0005I: Start of program at: 08/31/11 10:05:12 .

Backint for Oracle output: BKI1216E: There are no backup management classes available.

Backint for Oracle output: BKI1215I: Average transmission rate was 0.000 GB/h (0.000 MB/sec).

Backint for Oracle output: BKI1227I: Average compression factor was 1.000.

Backint for Oracle output: BKI0020I: End of program at: 08/31/11 10:05:13 .

Backint for Oracle output: BKI0021I: Elapsed time: 01 sec .

Backint for Oracle output: BKI0024I: Return code is: 2.

Backint for Oracle output:

Backint for Oracle error output:

Finished the backup unsuccessfully.

#ERROR
.\pipe\backup

-


End of output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.out)----


Removed Backint for MaxDB's temporary output file 'G:\sapdb\data\wrk\backint\sapdb.out'.

Copying error output of Backint for MaxDB to this file.

-


Begin of error output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.err)----


Backint for Oracle was unsuccessful.

-


End of error output of Backint for MaxDB (G:\sapdb\data\wrk\backint\sapdb.err)----


Removed Backint for MaxDB's temporary error output file 'G:\sapdb\data\wrk\backint\sapdb.err'.

Removed the Backint for MaxDB input file 'G:\sapdb\data\wrk\backint\sapdb.in'.

Have finished clean up successfully.

      • SAVE/RESTORE request:

SAVE DATA CANCEL

      • SAVE/RESTORE request accepted:

OK

      • SAVE/RESTORE result:

ERR

-24988,ERR_SQL: SQL error

-104,DBM command impossible at this time

3,Data backup failed

Servertask Info: because Error in backup task occured

Job 1 (Backup / Restore Medium Task) [executing] WaitingT204 Result=3700

Error in backup task occured, Error code 3700 "hostfile_error"

Backupmedium #1 (
.\pipe\backup) I/O Error

Backup error occured, Error code 3700 "hostfile_error"

      • DBA Action ends:

Timestamp: 20110831100513 State: Failure

===================================================================================================

Accepted Solutions (0)

Answers (1)

Answers (1)

markus_doehr2
Active Contributor
0 Kudos

> -104,DBM command impossible at this time

> 3,Data backup failed

> Servertask Info: because Error in backup task occured

> Job 1 (Backup / Restore Medium Task) [executing] WaitingT204 Result=3700

> Error in backup task occured, Error code 3700 "hostfile_error"

> Backupmedium #1 (
.\pipe\backup) I/O Error

> Backup error occured, Error code 3700 "hostfile_error"

Please check KnlMsg for possible errors (use protconv to convert the XML).

Markus

Former Member
0 Kudos

Hi Markus,

Thanks for quick response. I did checked KNLMSG file and it has XML file kind of information where as dbm.prt has some information and here it is

=================================================================================================

2011-08-31 10:18:30 0x00009ecc INF 1 DBMSrvCo A DBM Server client connection was established at 2011-08-31 10:18:29 (client process has process ID 24352 on computer 10.1.47.21).

2011-08-31 10:18:30 0x00009ecc INF 283 DBMSrv Command 'auto_extend show' is being executed.

2011-08-31 10:18:30 0x00009ecc INF 419 DBMSrv Command 'auto_extend' has ended with return code 0.

2011-08-31 10:18:30 0x00009ecc INF 283 DBMSrv Command 'auto_update_statistics show' is being executed.

2011-08-31 10:18:31 0x00009ecc INF 419 DBMSrv Command 'auto_update_statistics' has ended with return code 0.

2011-08-31 10:18:41 0x00009ecc INF 283 DBMSrv Command 'backup_save "Backup" DATA RECOVERY' is being executed.

2011-08-31 10:18:42 0x00009ecc INF 1 DBMKnl Sending an administrative statement to the database

0x00009ecc INF 8 DBMKnl Statement: SAVE DATA QUICK TO '
.\pipe\backup' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'Backup'

2011-08-31 10:19:47 0x00009ecc ERR 3 DBMKnl Received the result of an administrative statement from the database

0x00009ecc ERR 9 DBMKnl Statement: SAVE DATA QUICK TO '
.\pipe\backup' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'Backup'

0x00009ecc ERR 10 DBMKnl Returncode: -903

0x00009ecc ERR 5 DBMKnl Errortext: Host file I/O error

2011-08-31 10:19:47 0x00009ecc ERR -24580 DBMSrv ERR_COMMAND_FAILED: Command 'backup_save' has ended and failed with return code -24920.

0x00009ecc ERR -24920 DBMSrv ERR_BACKUPOP: backup operation was unsuccessful

0x00009ecc ERR -24778 DBMSrv The backup tool failed with 2 as sum of exit codes. The database request failed with error -903.

2011-08-31 10:19:53 0x00009ecc INF 2 DBMSrvCo A DBM Server client connection was released (client process has process ID 24352 on computer 10.1.47.21).

2011-08-31 10:19:53 0x00009ecc INF 1 DBMKnl Sending an administrative statement to the database

0x00009ecc INF 8 DBMKnl Statement: SAVE DATA CANCEL

2011-08-31 10:19:53 0x00009ecc ERR 3 DBMKnl Received the result of an administrative statement from the database

0x00009ecc ERR 9 DBMKnl Statement: SAVE DATA CANCEL

0x00009ecc ERR 10 DBMKnl Returncode: -104

0x00009ecc ERR 5 DBMKnl Errortext: DBM command impossible at this time

markus_doehr2
Active Contributor
0 Kudos

> Thanks for quick response. I did checked KNLMSG file and it has XML file kind of information where as dbm.prt has some information and here it is

Yes, the KnlMsg is an XML formatted file of the database kernel, this file contains usually more information about the error. To read it you can execute "protconv" in the directory or use DBStudio or DBMGUI.

dbm.prt has just the same information as you already posted.

Markus