DB2 Backup fails with libdb2hook message (80134)

Title: DB2 Backup fails with libdb2hook message
Date: 13/12/2006
NV Version: 7.1.3
OS Version: windows 2000, windows 2003
Application version:DB2 8.1
Plugin version: 1.7



Description:
DB2 plugin fails with :
An error occurred while accessing media "libdb2hook.dll". Reason code: "11".

Database fails to backup.




Symptoms:

Binary log shows:
An error occurred while accessing media "libdb2hook.dll". Reason code: "11"

DB2 plugin trace shows:
0 DB2AGENT:4020 754 0 115050 Set Hook Lib string to libdb2hook.dll
0 DB2AGENT:4020 755 0 115050 Write Master PID and Option 'YOUR-12TNJPQ8R2-440-YOUR-12TNJPQ8R2-7=DB2=' to temp file C:/Program Files/BakBone Software/NetVault/tmp/nvdb2Tmp
0 DB2AGENT:4020 756 0 115050 DB2 Agent Call sqlubkp API to backup TEST
0 DB2AGENT:4020 758 0 115051 DB2 Agent call sqlubkp API completed with failure: SQL2062N An error occurred while accessing media "libdb2hook.dll". Reason code: "11".
0 DB2AGENT:4020 702 0 115051 Agent Backup Database with Failure: SQL2062N An error occurred while accessing media "libdb2hook.dll". Reason code: "11".
0 MSGWAIT :4020 16 0 115051 Message 'MSG_CHANNEL_DOWN_MSG' not handled a depth 0

IBM's information re SQL error states:

SQL2062N An error occurred while accessing
media “ ”. Reason code:
“ ”
Explanation: An unexpected error occurred while accessing a device, file, TSM or the vendor shared library during the processing of a database utility. The following is a list of reason
codes:
1 An attempt to initialize a device, file, TSM or the vendor shared library failed.
2 An attempt to terminate a device, file, TSM or the vendor shared library failed.
other If you are using TSM, this is an error code returned by TSM. The utility stops processing. User Response: Ensure the device, file, TSM or vendor shared library used by the utility is available and re

The error reported is misleading, in our case this was caused by an illegal charater in the Netvault Machine name - in this case a "-". Reinstalling Netvault with a machine name without the "-" sign.

This problem is fixed in later versions of the APM.