Problem
The dbmcli command, that should start the backup, hangs and does not return to a command prompt. It also does not start the backint program so NetBackup is unaware of any backup requests. A similar problem may occur during the restore from the command line.
Backup and restore operations via the Database Manager (DBM) GUI are successful and appear unaffected by upgrading to MAXDB 7.6.
Error Message
The dbmcli command hangs using the SAP MAXDB 7.5 syntax.
dbmcli on MAXDB>backup_start BACKData DATA
When interrupted, [ctrl-c], dbmcli displays one of these two sets of messages before exiting.
ERR
-24988,ERR_SQL: SQL error
-903,Host file I/O error
3,Data backup failed
Servertask Info: because Error in backup task occured
Job 1 (Backup / Restore Medium Task) [executing] WaitingT105 Result=3700
Error in backup task occured, Error code 3700 "hostfile_error"
Backupmedium #1 (<path_to_medium>) Could not open stream
Backup error occured, Error code 3700 "hostfile_error"
or
ERR
-24988,ERR_SQL: SQL error
-903,Host file I/O error
3,Data backup failed
1,Backupmedium #1 (<path_to_medium>) Wrong file type
6,Backup error occured, Error code 3700 "hostfile_error"
17,Servertask Info: because Error in backup task occurred
10,Job 1 (Backup / Restore Medium Task) [executing] WaitingT193 Result=3700
6,Error in backup task occured, Error code 3700 "hostfile_error"
Cause
Prior to MaxDB 7.6, the medium_put syntax for a backup was
dbmcli> medium_put <medium_name> <medium_path> PIPE <backup_type>
Example:
dbmcli> medium_put BACKData \\.\PIPE\medium1 PIPE DATA
Prior to MaxDB 7.6, the restore syntax was
dbmcli> recover_start <medium_name> <backup_type> ExternalBackupId <backup_id>
Both syntax have changed in MaxDB 7.6 and above.
Solution
Beginning with MaxDB 7.6, SAP has modified the syntax for both backup and restore. Any scripts used to start dbmcli to interface with backint will need to be updated, unless backup and restore operations will be initiated from the SAP DBM GUI (which automatically uses the correct syntax).
For backup, the new position dependent parameter 'tool_type' is required.
dbmcli> medium_put <medium_name> <medium_path> <type> <backup_type> <size> <block_size> <overwrite> <autoloader> <os_command> <tool_type>
Example, using the default values for size, block_size, overwrite, autoloader, and os_command:
dbmcli> medium_put BACKData /tmp/medium1 PIPE DATA 0 8 NO NO backup_replace BACK
For restore, the dbmcli command has changed from recover_start to backup_restore.
dbmcli> backup_restore <medium_name> <backup_type> EBID <db_name> <backup_id> <medium_path>
dbmcli> backup_restore ”BACKData” DATA EBID ”DEMODB VXP11326896506 /tmp/medium1”
Please review the SAP MAXDB document for additional command syntax details;
https://maxdb.sap.com/doc/7_7/45/1125da4d9e7307e10000000a1553f7/content.htm
Veritas is currently reviewing MAXDB 7.7 to see if any additional changes are needed to allow successful backup and restore.
Applies To
Windows Server 2008 R2 x64
Solaris 10
NetBackup 7.0.1 but could affect any version
SAP: ECC6.0
MaxDB: 7.7.06.010
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.