On a Linux system also check this symlink and create if it's not there (this
fixed the issue on a 6.2.3.0 linux server after upgrading the TSM client to
the lastest level (that broke my db backup, TSM support was quick and gave
me this fix)


*ln -s /opt/tivoli/tsm/client/lang/EN_US/ /opt/tivoli/tsm/client/api/bin64*

Regards,
  Stefan


On Sat, Sep 24, 2011 at 8:35 AM, Erwann SIMON <erwann.simon AT free DOT fr> 
wrote:

> Hi,
>
> I generaly check with the db2adutl tool.
>
> Login with the instance user id :
> # su - <instance_id>
>
> Run the db2adutl tool with the query parameter as instance user :
> $ /opt/tivoli/tsm/db2/adsm/db2adutl query
>
> (It should also be in the path for the instance user id).
>
> If it fails, look in the DB2 documentation for the sqlcode and the sqlrrmc
> :
> $ db2 ? sql<sqlcode number>
>
>
> --
> Best regards / Cordialement / مع تحياتي
> Erwann SIMON
>
> -----Original Message-----
> From: Steven Harris <steve AT STEVENHARRIS DOT INFO>
> Sender: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> Date:         Sat, 24 Sep 2011 13:52:17
> To: <ADSM-L AT VM.MARIST DOT EDU>
> Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> Subject: Re: [ADSM-L] DB error in TSM6.2.3
>
> Hi Tandon
>
> I ran into something similar this week in a Solaris install.  Check the
> DSM* environment variables.  If you change them you will need to restart
> your TSM Server and DB instance to pick up the changes.
>
> Regards
>
> Steve
>
> Steven Harris
> TSM Admin
> Canberra Australia
>
> On 24/09/2011 2:52 AM, Tandon K wrote:
> > Dear ,
> >
> > when i am firing db i got error  can help me
> >
> > 09/23/2011 22:15:11      ANR2017I Administrator TSMADMIN issued command:
> BACKUP DB
> >                            dev=dlfclass t=f vol=DQ1093L5  (SESSION: 1)
> > 09/23/2011 22:15:11      ANR4559I Backup DB is in progress. (SESSION: 1)
> > 09/23/2011 22:15:11      ANR0984I Process 2 for Database Backup started
> in the
> >                            BACKGROUND at 10:15:11 PM. (SESSION: 1,
> PROCESS: 2)
> > 09/23/2011 22:15:11      ANR2280I Full database backup started as process
> 2.
> >                            (SESSION: 1, PROCESS: 2)
> > 09/23/2011 22:15:13      ANR0406I Session 2 started for node
> $$_TSMDBMGR_$$
> >                            (DB2/LINUXX8664) (Tcp/Ip 127.0.0.1(41087)).
> (SESSION: 2)
> > 09/23/2011 22:15:13      ANR0403I Session 2 ended for node $$_TSMDBMGR_$$
> >                            (DB2/LINUXX8664). (SESSION: 2)
> > 09/23/2011 22:15:13      ANR0406I Session 3 started for node
> $$_TSMDBMGR_$$
> >                            (DB2/LINUXX8664) (Tcp/Ip 127.0.0.1(41088)).
> (SESSION: 3)
> > 09/23/2011 22:15:13      ANR0403I Session 3 ended for node $$_TSMDBMGR_$$
> >                            (DB2/LINUXX8664). (SESSION: 3)
> > 09/23/2011 22:15:13      ANR4588E A database backup configuration might
> be
> >                            incorrect.(SESSION: 1, PROCESS: 2)
> > 09/23/2011 22:15:13      ANR0985I Process 2 for Database Backup running
> in the
> >                            BACKGROUND completed with completion state
> FAILURE at
> >                            10:15:13 PM. (SESSION: 1, PROCESS: 2)
> > 09/23/2011 22:15:13      ANR1893E Process 2 for Database Backup
>  completed with a
> >                            completion state of FAILURE. (SESSION: 1,
> PROCESS: 2)
> >                            ACTLOG  (SESSION: 1)
> >
>