ADSM-L

Re: [ADSM-L] SV: Failed to backup DB on Linux TSM 6.2

2010-04-08 05:53:52
Subject: Re: [ADSM-L] SV: Failed to backup DB on Linux TSM 6.2
From: Richard van Denzel <RDenzel AT SLTN DOT NL>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 8 Apr 2010 11:55:20 +0200
Hi Stephan,

I've already tried that one for Linux (the Windows tools do not apply).

Richard.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Stephan Boldt
Sent: donderdag 8 april 2010 10:41
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] SV: Failed to backup DB on Linux TSM 6.2

Hi Richard,

I had a similar problem (except that the OS was Windows) and the following
article helped me solving the issue:

http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/topic/com.ibm.itsm.srv.install.doc/t_srv_prep_dbmgr.html

kind regards,
Stephan


2010/4/8 Richard van Denzel <RDenzel AT sltn DOT nl>

> I already found this document and had a look at my machine, but everything
> seems ok.
>
> Richard.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Rejean Larivee/Quebec/IBM
> Sent: woensdag 7 april 2010 17:08
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] SV: Failed to backup DB on Linux TSM 6.2
>
> Hello,
> your db2diag.log shows a return code of 106.
> This is a permission denied which may have to do
> with the error log file permissions.
> See this solution here for details on this :
> http://www-1.ibm.com/support/docview.wss?uid=swg21385178
>
>
>  Rejean Larivee                                     NEW IBM Tivoli Storage
> Manager Wiki Home NEW
>  IBM Tivoli Storage Manager support                 IBM Tivoli Storage
> Manager Support Home
>                                                    -How to gather documents
> for IBM TSM support
>                                                    -Instruction Manuals
>                                                    -Recommended fixes for
> IBM TSM products
>
>
>
>
>
> "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 04/07/2010
> 11:10:33 AM:
>
> > [image removed]
> >
> > Re: SV: Failed to backup DB on Linux TSM 6.2
> >
> > Richard van Denzel
> >
> > to:
> >
> > ADSM-L
> >
> > 04/07/2010 11:12 AM
> >
> > Sent by:
> >
> > "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
> >
> > Please respond to "ADSM: Dist Stor Manager".
> >
> > 2010-04-07-16.00.16.788881+120 E405247E455         LEVEL: Info
> > PID     : 6282                 TID  : 47891674556736PROC : db2sysc 0
> > INSTANCE: tsminst1             NODE : 000          DB   : TSMDB1
> > APPHDL  : 0-347                APPID: *LOCAL.tsminst1.100407140403
> > AUTHID  : TSMINST1
> > EDUID   : 39                   EDUNAME: db2agent (TSMDB1) 0
> > FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:1508
> > MESSAGE : Starting an online db backup.
> >
> > 2010-04-07-16.00.29.467092+120 E405703E361         LEVEL: Error
> > PID     : 6558                 TID  : 46920181258944PROC : db2vend
> > (db2med - 50 (TSMDB1))
> > INSTANCE: tsminst1             NODE : 000
> > FUNCTION: DB2 UDB, database utilities, sqluvint, probe:374
> > DATA #1 : TSM RC, PD_DB2_TYPE_TSM_RC, 4 bytes
> > TSM RC=0x0000006A=106 -- see TSM API Reference for meaning.
> >
> > 2010-04-07-16.00.29.503949+120 I406065E749         LEVEL: Error
> > PID     : 6282                 TID  : 47891628419392PROC : db2sysc 0
> > INSTANCE: tsminst1             NODE : 000
> > EDUID   : 50                   EDUNAME: db2med.39.0 (TSMDB1) 0
> > FUNCTION: DB2 UDB, database utilities, sqluMapVend2MediaRCWithLog,
> probe:646
> > DATA #1 : String, 135 bytes
> > Vendor error: rc = 11 returned from function sqluvint.
> > Return_code structure from vendor
> library /home/tsminst1/sqllib/adsm/libtsm.a:
> >
> > DATA #2 : Hexdump, 48 bytes
> > 0x00002B8EC5F95370 : 6A00 0000 3337 3420 3130 3600 0000 0000    j...
> > 374 106.....
> > 0x00002B8EC5F95380 : 0000 0000 0000 0000 0000 0000 0000 0000
> > ................
> > 0x00002B8EC5F95390 : 0000 0000 0000 0000 0000 0000 0000 0000
> > ................
> >
> > 2010-04-07-16.00.29.515091+120 I406815E375         LEVEL: Error
> > PID     : 6282                 TID  : 47891628419392PROC : db2sysc 0
> > INSTANCE: tsminst1             NODE : 000
> > EDUID   : 50                   EDUNAME: db2med.39.0 (TSMDB1) 0
> > FUNCTION: DB2 UDB, database utilities, sqluMapVend2MediaRCWithLog,
> probe:686
> > MESSAGE : Error in vendor support code at line: 374 rc: 106
> >
> > 2010-04-07-16.00.29.515261+120 E407191E351         LEVEL: Error
> > PID     : 6282                 TID  : 47891628419392PROC : db2sysc 0
> > INSTANCE: tsminst1             NODE : 000
> > EDUID   : 50                   EDUNAME: db2med.39.0 (TSMDB1) 0
> > FUNCTION: DB2 UDB, database utilities, sqluMCInitBackupMC, probe:677
> > MESSAGE : Media controller -- Generic error
> >
> > 2010-04-07-16.00.29.515349+120 E407543E443         LEVEL: Error
> > PID     : 6282                 TID  : 47891628419392PROC : db2sysc 0
> > INSTANCE: tsminst1             NODE : 000
> > EDUID   : 50                   EDUNAME: db2med.39.0 (TSMDB1) 0
> > FUNCTION: DB2 UDB, database utilities, sqluMCInitBackupMC, probe:677
> > MESSAGE : SQL2033N  An error occurred while accessing TSM during
> theprocessing
> >           of a database utility.  TSM reason code: "".
> >
> > 2010-04-07-16.00.29.517426+120 E407987E337         LEVEL: Error
> > PID     : 6282                 TID  : 47891628419392PROC : db2sysc 0
> > INSTANCE: tsminst1             NODE : 000
> > EDUID   : 50                   EDUNAME: db2med.39.0 (TSMDB1) 0
> > FUNCTION: DB2 UDB, database utilities, sqluMCInitBackupMC, probe:677
> > DATA #1 : String, 3 bytes
> > 106
> >
> > 2010-04-07-16.00.29.517744+120 E408325E566         LEVEL: Severe
> > PID     : 6282                 TID  : 47891674556736PROC : db2sysc 0
> > INSTANCE: tsminst1             NODE : 000          DB   : TSMDB1
> > APPHDL  : 0-347                APPID: *LOCAL.tsminst1.100407140403
> > AUTHID  : TSMINST1
> > EDUID   : 39                   EDUNAME: db2agent (TSMDB1) 0
> > FUNCTION: DB2 UDB, database utilities, sqlubHandleTSMError, probe:1144
> > DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
> > -2033
> > DATA #2 : Hexdump, 8 bytes
> > 0x00002B8EC61063F8 : 0FF8 FFFF 3130 3600                        ....106.
> >
> > 2010-04-07-16.00.29.517885+120 E408892E974         LEVEL: Severe
> > PID     : 6282                 TID  : 47891674556736PROC : db2sysc 0
> > INSTANCE: tsminst1             NODE : 000          DB   : TSMDB1
> > APPHDL  : 0-347                APPID: *LOCAL.tsminst1.100407140403
> > AUTHID  : TSMINST1
> > EDUID   : 39                   EDUNAME: db2agent (TSMDB1) 0
> > FUNCTION: DB2 UDB, database utilities, sqlubHandleTSMError, probe:1144
> > MESSAGE : SQL2033N  An error occurred while accessing TSM during
> theprocessing
> >           of a database utility.  TSM reason code: "".
> > DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
> >  sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -2033   sqlerrml: 3
> >  sqlerrmc: 106
> >  sqlerrp : sqlubHan
> >  sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 0x00000000
> >            (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
> >  sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
> >            (7)      (8)      (9)      (10)        (11)
> >  sqlstate:
> >
> > 2010-04-07-16.00.29.966759+120 E409867E364         LEVEL: Error
> > PID     : 6578                 TID  : 47538148035264PROC : db2vend
> > (DB2 Backup Agent - 39 (
> > INSTANCE: tsminst1             NODE : 000
> > FUNCTION: DB2 UDB, database utilities, sqluvdel, probe:1742
> > DATA #1 : TSM RC, PD_DB2_TYPE_TSM_RC, 4 bytes
> > TSM RC=0x0000006A=106 -- see TSM API Reference for meaning.
> >
> > 2010-04-07-16.00.29.967360+120 I410232E946         LEVEL: Error
> > PID     : 6282                 TID  : 47891674556736PROC : db2sysc 0
> > INSTANCE: tsminst1             NODE : 000          DB   : TSMDB1
> > APPHDL  : 0-347                APPID: *LOCAL.tsminst1.100407140403
> > AUTHID  : TSMINST1
> > EDUID   : 39                   EDUNAME: db2agent (TSMDB1) 0
> > FUNCTION: DB2 UDB, database utilities, sqlubDeleteVendorImage, probe:558
> > MESSAGE : SQL2062N  An error occurred while accessing media "".  Reason
> code:
> >           "".
> > DATA #1 : String, 27 bytes
> > Error returned by sqluvdel.
> > DATA #2 : Vendor RC, PD_DB2_TYPE_VENDOR_RC, 4 bytes
> > Vendor RC=0x0000001A=26 -- see DB2 API Guide for meaning.
> > DATA #3 : Hexdump, 48 bytes
> > 0x00002B8EC5F96050 : 6A00 0000 3137 3432 2031 3036 0000 0000    j...
> > 1742 106....
> > 0x00002B8EC5F96060 : 0000 0000 0000 0000 0000 0000 0000 0000
> > ................
> > 0x00002B8EC5F96070 : 0000 0000 0000 0000 0000 0000 0000 0000
> > ................
> >
> > 2010-04-07-16.00.29.978235+120 E411179E604         LEVEL: Error
> > PID     : 6282                 TID  : 47891674556736PROC : db2sysc 0
> > INSTANCE: tsminst1             NODE : 000          DB   : TSMDB1
> > APPHDL  : 0-347                APPID: *LOCAL.tsminst1.100407140403
> > AUTHID  : TSMINST1
> > EDUID   : 39                   EDUNAME: db2agent (TSMDB1) 0
> > FUNCTION: DB2 UDB, database utilities, sqlubCleanupPartialBackup,
> probe:708
> > MESSAGE : SQL2062N  An error occurred while accessing media "".  Reason
> code:
> >           "".
> > DATA #1 : String, 63 bytes
> > Could not delete partial backup image created on vendor device.
> >
> > 2010-04-07-16.00.30.083011+120 E411784E433         LEVEL: Severe
> > PID     : 6282                 TID  : 47891674556736PROC : db2sysc 0
> > INSTANCE: tsminst1             NODE : 000          DB   : TSMDB1
> > APPHDL  : 0-347                APPID: *LOCAL.tsminst1.100407140403
> > AUTHID  : TSMINST1
> > EDUID   : 39                   EDUNAME: db2agent (TSMDB1) 0
> > FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:848
> > MESSAGE : Backup terminated.
> >
> > I can't see the reason, can you?
> >
> > Richard.
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> > Behalf Of Christian Svensson
> > Sent: dinsdag 6 april 2010 21:21
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: [ADSM-L] SV: Failed to backup DB on Linux TSM 6.2
> >
> > What does DB2Diag.log tell you?
> >
> > Best Regards
> > Christian Svensson
> >
> > Cell: +46-70-325 1577
> > E-mail: Christian.Svensson AT cristie DOT se
> > Skype: cristie.christian.svensson
> > Supported Platform for CPU2TSM:: http://www.cristie.se/cpu2tsm-
> > supported-platforms
> >
> > ________________________________________
> > Från: Richard van Denzel [RDenzel AT SLTN DOT NL]
> > Skickat: den 6 april 2010 21:19
> > Till: ADSM-L AT VM.MARIST DOT EDU
> > Ämne: Failed to backup DB on Linux TSM 6.2
> >
> > Hi All,
> >
> >
> >
> > For some reason I'm unable to backup my TSM DB on Linux (TSM Server
> > 6.2.0.0, TSM Client 6.2.0.0). I get the infamous message:
> >
> >
> >
> > ANR2968E Database backup terminated. DB2 sqlcode: -2033. DB2 sqlerrmc:
> > 106.
> >
> > ANR0985I Process 1 for DATABASE BACKUP running in the BACKGROUND
> > completed with completion state FAILURE at 09:07:52 PM.
> >
> >
> >
> > I've done everything I could find on the net to resolve the problem but
> > no luck!.
> >
> >
> >
> > [tsminst1@tsm62 ~]$ env | grep DSMI
> >
> > DSMI_DIR=/opt/tivoli/tsm/client/api/bin64
> >
> > DSMI_LOG=/home/tsminst1/tsminst1
> >
> > DSMI_CONFIG=/home/tsminst1/tsminst1/tsmdbmgr.opt
> >
> > [tsminst1@tsm62 ~]$ ls -l $DSMI_DIR
> >
> > total 5856
> >
> > -rw-r--r-- 1 root     root      17 Apr  6 20:30 dsm.opt
> >
> > -r--r--r-- 1 root     bin      782 Mar  9 12:28 dsm.opt.smp
> >
> > -rwxrwxr-x 1 tsminst1 tsm      292 Apr  3 20:49 dsm.sys
> >
> > -r--r--r-- 1 root     bin      971 Mar  9 12:28 dsm.sys.smp
> >
> > -rwsr-xr-x 1 root     bin  2670186 Mar  2 09:58 dsmtca
> >
> > lrwxrwxrwx 1 root     root      16 Apr  3 20:40 en_US ->
> > ../../lang/EN_US
> >
> > lrwxrwxrwx 1 root     root      16 Apr  3 20:40 EN_US ->
> > ../../lang/EN_US
> >
> > -r-xr-xr-x 1 root     bin  3259048 Mar  2 09:58 libApiTSM64.so
> >
> > drwxr-xr-x 2 root     bin     4096 Apr  3 17:36 sample
> >
> > [tsminst1@tsm62 ~]$ ls -l $DSMI_LOG
> >
> > total 28
> >
> > drwxrwxr-x 4 tsminst1 tsm 4096 Apr  3 16:32 NODE0000
> >
> > -rw-r--r-- 1 tsminst1 tsm    0 Apr  6 20:25 tsmdbmgr.log
> >
> > -rw-r--r-- 1 tsminst1 tsm   29 Apr  3 16:39 tsmdbmgr.opt
> >
> > -rw------- 1 tsminst1 tsm  151 Apr  3 20:42 TSM.PWD
> >
> > [tsminst1@tsm62 ~]$ cat $DSMI_CONFIG
> >
> > SERVERNAME TSMDBMGR_TSMINST1
> >
> > [tsminst1@tsm62 ~]$ cat $DSMI_DIR/dsm.sys
> >
> > Servername TSM62
> >
> > COMMMethod TCPip
> >
> > TCPPort 1500
> >
> > TCPServeraddress localhost
> >
> >
> >
> > servername TSMDBMGR_TSMINST1
> >
> > commmethod tcpip
> >
> > tcpserveraddr localhost
> >
> > tcpport 1500
> >
> > passwordaccess generate
> >
> > passworddir /home/tsminst1/tsminst1
> >
> > errorlogname /home/tsminst1/tsminst1/tsmdbmgr.log
> >
> > nodename $$_TSMDBMGR_$$
> >
> > [tsminst1@tsm62 ~]$
> >
> >
> >
> > Anyone got a clue to where I probably missed the obvious?
> >
> >
> >
> > Richard.
>

<Prev in Thread] Current Thread [Next in Thread>