ADSM-L

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

2010-04-08 10:28:29
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 16:29:58 +0200
Richard,

I had a look with lsof but I did not find any related files there which
could be locked.

I found out that kuddb2 was not running, because the start of that
process wanted to write in /opt/tivoli/tsm/db2/imta/logs and tmp
directories. I modified them to 777 and then kuddb2 was started with no
errors.

But then again this did not resolve me being able to do a database
backup. Do have any ideas left?

Also:

[tsminst1@tsm62 ~]$ set | grep DSMI
DSMI_CONFIG=/home/tsminst1/tsminst1/tsmdbmgr.opt
DSMI_DIR=/opt/tivoli/tsm/client/api/bin64
DSMI_LOG=/home/tsminst1/tsminst1
_=DSMI_LOG
[tsminst1@tsm62 ~]$ cat $DSMI_CONFIG
SERVERNAME TSMDBMGR_TSMINST1
[tsminst1@tsm62 ~]$ ll $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 ~]$ ll $DSMI_LOG
total 24
drwxrwxr-x 4 tsminst1 tsm 4096 Apr  3 16:32 NODE0000
-rw-r--r-- 1 tsminst1 tsm   29 Apr  3 16:39 tsmdbmgr.opt
-rw------- 1 tsminst1 tsm  151 Apr  3 20:42 TSM.PWD

The other Richard.

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

Richard -

You had posted the contents of your diag log and said that you can't see
the reason, with no reference to anything you had pursued in the
diagnostic messages.  When posting, it will help everyone help you if
you cite what you have already pursued so that people's time is not
wasted.

Pursuit of Sqlerrmc codes is outlined in the TSM 6.1 Technical Guide
redbook and the TSM 6.1 Problem Determination Guide and the Messages
manual, including:

Some common TSM reason codes are:
106     The specified file is being used by another process. You tried
to read from or write to a file that is currently being used by another
process.

and:

106 - Ensure that the DB2 Instance DSMI_DIR environment variable is
pointing to the location of the Tivoli Storage Manger API executables
and the dsm.sys configuration file. If the DSMI_DIR setting is wrong,
correct it for the DB2 instance, and then restart the DB2 instance.

The lsof command may allow you to narrow down contention, if that't the
issue, with /proc/locks possibly helping.

    Richard Sims

On Apr 8, 2010, at 2:55 AM, Richard van Denzel wrote:

> I know, but to what file is access denied? I've looked at all the
files
> which seems to be candidate for this and they all seemed fine.
> I've also compared it to an TSM 6.2 running on AIX and I did not find
> any differences.
> 
> Richard.
> 
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
Of
> Richard Sims
> Sent: woensdag 7 april 2010 16:21
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] SV: Failed to backup DB on Linux TSM 6.2
> 
> On Apr 7, 2010, at 10:10 AM, Richard van Denzel wrote:
> 
>> TSM RC=0x0000006A=106 -- see TSM API Reference for meaning.
> 
> Access Denied error.