DB2 backup fails with SQL2079N return code 30

DB2 backup fails with SQL2079N return code 30

2005-07-19-15.34.41.479674+480 I5379133C371 LEVEL: Error
PID : 430324 TID : 1 PROC : db2med.184372.0 0
INSTANCE: db2inst NODE : 000
FUNCTION: DB2 UDB, database utilities, sqluvintCall, probe:10
MESSAGE : Signal encountered in sqluvint
DATA #1 : Hexdump, 4 bytes
0x2FF20D70 : 800F 00AF ....

2005-07-19-15.34.41.480174+480 I5379505C630 LEVEL: Error
PID : 430324 TID : 1 PROC : db2med.184372.0 0
INSTANCE: db2inst NODE : 000
FUNCTION: DB2 UDB, database utilities, sqluMapVend2MediaRCWithLog, probe:0
DATA #1 : String, 108 bytes
Vendor error: rc = 30 returned from function sqluvint.
Return_code structure from vendor library libtsm.a:

DATA #2 : Hexdump, 40 bytes
0x2FF20DE8 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF20DF8 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF20E08 : 0000 0000 0000 0000 ........

2005-07-19-15.34.41.480361+480 I5380136C311 LEVEL: Error
PID : 430324 TID : 1 PROC : db2med.184372.0 0
INSTANCE: db2inst NODE : 000
FUNCTION: DB2 UDB, database utilities, sqluMapVend2MediaRCWithLog, probe:0
MESSAGE : Error in vendor support code at line: 0 rc: 0

2005-07-19-15.34.41.480520+480 I5380448C345 LEVEL: Warning
PID : 430324 TID : 1 PROC : db2med.184372.0 0
INSTANCE: db2inst NODE : 000
FUNCTION: DB2 UDB, database utilities, sqluMCInitBackupMC, probe:85
MESSAGE : Media controller -- vendor device initialization error (zrc =
0x0000001e)

2005-07-19-15.34.41.480733+480 I5380794C595 LEVEL: Severe
PID : 184372 TID : 1 PROC : db2agent (FDBK51) 0
INSTANCE: db2inst NODE : 000 DB : FDBK51
APPHDL : 0-27 APPID: *LOCAL.db2inst.050719073441
FUNCTION: DB2 UDB, database utilities, sqlubMWResponse, probe:5
MESSAGE : DiagData
DATA #1 : Hexdump, 42 bytes
0x40A1D148 : FFFF F7E1 2F68 6F6D 652F 6462 3269 6E73 ..../home/db2ins
0x40A1D158 : 742F 7371 6C6C 6962 2F61 6473 6D2F 6C69 t/sqllib/adsm/li
0x40A1D168 : 6274 736D 2E61 FF33 3000 btsm.a.30.

2005-07-19-15.34.41.481086+480 I5381390C443 LEVEL: Severe
PID : 184372 TID : 1 PROC : db2agent (FDBK51) 0
INSTANCE: db2inst NODE : 000 DB : FDBK51
APPHDL : 0-27 APPID: *LOCAL.db2inst.050719073441
FUNCTION: DB2 UDB, database utilities, sqlubMWResponse, probe:10
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0x2FF0F250 : FFFF F7E1 ....

2005-07-19-15.34.41.498895+480 I5381834C461 LEVEL: Error
PID : 184372 TID : 1 PROC : db2agent (FDBK51) 0
INSTANCE: db2inst NODE : 000 DB : FDBK51
APPHDL : 0-27 APPID: *LOCAL.db2inst.050719073441
FUNCTION: DB2 UDB, database utilities, sqluvdelCall, probe:50
MESSAGE : Signal encountered in sqluvdel
DATA #1 : Hexdump, 4 bytes
0x2FF0A9F0 : 800F 00AF ....

2005-07-19-15.34.41.499145+480 I5382296C453 LEVEL: Severe
PID : 184372 TID : 1 PROC : db2agent (FDBK51) 0
INSTANCE: db2inst NODE : 000 DB : FDBK51
APPHDL : 0-27 APPID: *LOCAL.db2inst.050719073441
FUNCTION: DB2 UDB, database utilities, sqluCleanupPartialBackup, probe:669
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0x2FF0AA74 : 0000 001E ....

2005-07-19-15.34.41.499349+480 I5382750C607 LEVEL: Warning
PID : 184372 TID : 1 PROC : db2agent (FDBK51) 0
INSTANCE: db2inst NODE : 000 DB : FDBK51
APPHDL : 0-27 APPID: *LOCAL.db2inst.050719073441
FUNCTION: DB2 UDB, database utilities, sqluCleanupPartialBackup, probe:670
MESSAGE : Vendor RC:
DATA #1 : Hexdump, 40 bytes
0x2FF0AB10 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF0AB20 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x2FF0AB30 : 0000 0000 0000 0000 ........

2005-07-19-15.34.41.507222+480 I5383358C359 LEVEL: Severe
PID : 184372 TID : 1 PROC : db2agent (FDBK51) 0
INSTANCE: db2inst NODE : 000 DB : FDBK51
APPHDL : 0-27 APPID: *LOCAL.db2inst.050719073441
FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:140
MESSAGE : Backup Terminated.

出現原因：
Tivoli client 版本存在漏洞

解決辦法：
備份的客戶端需要更新版本
DB2 backup fails with SQL2079N return code 30
Technote (FAQ)

Problem
DB2 backup using TSM API or db2adutl query fail with the following errors:

Segmentation fault(coredump)
SQL2079N An error was reported by the shared library "/home/inst1/sqllib/adsm/libtsm.a". Return code: "30".

Cause
This error can indicate a crash occurred in the TSM API. If the command is not run in the foreground, the 'Segmentation fault(coredump)' message may not be seen.

Solution
In this case, the "Return Code: 30" is coming from DB2 and indicates a fatal error.
Check the DB2 trap files in db2dump directory for a stack traceback of the crash. If the failing function (on top of the stack) shows an offset in library libApiDS.a, libApiDS64.a, or libApiTSM64.a then it is crashing inside the TSM API. The TSM API fileset should be upgraded to the latest levels to ensure all crash fixes are in place. This type of crash is usually seen on machines running HACMP due to TSM APARs like IC35331, IC37526, and IC41286.

DB2 trap file example (/home/inst1/sqllib/db2dump/t17576.000):

DB2 (inst1.000) : db2ipccm (0x1) 2004-08-01-16.20.34.950096
signal #11 encountered, stack traceback follows:
IAR: D0354C94 MSR: 0000D032 LR: FFFFFFFF
CTR: FFFFFFFF XER: FFFFFFFF FPSCR: 00000000
CR: 2A2D4222
GPR[00]: FFFFFFFF GPR[01]: 2FF1EE48 GPR[02]: FFFFFFFF
.....
FPR[28]: 0000000000000000 FPR[29]: 0000000000000000
FPR[30]: 0000000000000000 FPR[31]: 0000000000000000
0xD3DEE9AC strcpy + 0x8C
( = offset 0x108AC in library libApiDS.a )
0xD3DEB430 psGetClusterName + 0x12C
( = offset 0x16E2B in library libApiDS.a )
.....



Product Alias/Synonym
TSM

-------------------------------

SQL2079N共享庫 "" 報告了錯誤。返回碼：""。

解釋:

在資料庫實用程式處理期間，供應商共享庫報告了錯誤。顯示的返回碼響應
有效的供應商API 返回碼之一。實用程式停止處理。

可能的 API 返回碼是：

30 供應商產品內遇到嚴重錯誤。

其它 供應商產品返回特定嚴重錯誤。

使用者響應:

確保提供的共享庫是有效的。嘗試根據供應商 API 返回碼和相應的db2diag
條目做必要的更正操作並重新提交實用程式命令。

From the above info, your problem might related to the storage used for your backup operation. There won't be any problem if your backup to the local disk. Pls check the storage problem. Thanks!

[@more@]