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:ads...@vm.marist.edu] On Behalf Of
> Richard Sims
> Sent: woensdag 7 april 2010 16:21
> To: ADSM-L@VM.MARIST.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.
