Actually, the onbar debug file doesn't track the shared (XBSA) library
stuff much.  I think it would be preferable to turn on TSM tracing in the
client's dsm.opt file with the following stanzas. The tracing wraps so the
XBSA library which causes the
session to bomb would very likely be caught since this activity will be
what terminates the session. The stuff is also difficult to read and you
would do well to bring Tivoli support and Informix support into the problem
to interpret the trace.
Since your version of Tivoli doesn't come with an XBSA library, you must
have gotten it elsewhere. Check the sm_versions file; if you are using the
Informix supplied shared library (ISM) it should be in the bar_versions
table of the sysutils database as well as the sm_versions file. I don't
know where you are keeping the library files but they should also be linked
into /usr/lib.

dsm.opt trace stuff:

TRACEMAX 10000
TRACEFILE  /tmp/filename  (((make sure permissions are set to allow writing
to this file- your filename may differ)))
TRACEFLAG  service -policy

George Lesho
System/Storage Admin
AFC Enterprises



                    "Sarver,
                    Theresa (Osky        To:     [EMAIL PROTECTED]
                    UNIX                 cc:     (bcc: George Lesho/Partners/AFC)
                    Administrator)       Subject:     Re: Informix API 3.7.1
                    "
                    <tsarver@CLOWV
                    ALVE.COM>
                    Sent by:
                    "ADSM: Dist
                    Stor Manager"
                    <[EMAIL PROTECTED]
                    IST.EDU>


                    03/12/02 07:53
                    AM
                    Please respond
                    to "ADSM: Dist
                    Stor Manager"






Hi Doug;

I don't know what TSM error 168 is...however, I have had the "XBSA Error
(BSAInit): An unspecified XBSA error has occurred: 96" before.  In my case
there was a problem with the sm_versions table.  Anyway, here's a URL that
might help you with the onbar-XBSA errors:

http://www.geocities.com/maury.geo/onbar.html

Also, you may want to turn on bar_debug (in your onconfig file) until this
problem is resolved, as that is what actually helped me resolve my XBSA
problems last time.

Thanks;
Theresa
-----Original Message-----
From: Doug McLauchlan [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 11, 2002 9:28 PM
To: [EMAIL PROTECTED]
Subject: Informix API 3.7.1


   Hi all *SM's, I need some help please. We are running TSM Server 4.2.1.6
with TSM Client 4.2.1.0 and API 3.7.1.0 on aix 4.3.3.0. We have
successfully
been backup up the Informix Database (Informix Dynamic Server Version
7.30.UC7) until last Sunday when I received the message
10-03-2002 16:12:41  ANR0424W Session 3130 for node WW-DATAW-MONTHLY (AIX)

                      refused - invalid password submitted.

this backup is a monthly Level 0 backup of the database and is a separate
node on the machine (I run 2 nodes on the same machine, 1 for monthly & 1
for daily), On Monday night the Level 1 backup failed with this message
from
the bar.act.log
2002-03-11 18:37:26 255704  225818 /informix/bin/onbar_d -b -L 1 -f
/tmp/dwd485p.dbslist.250184.out
 2002-03-11 18:38:04 255704  225818 Begin level 1 backup rootdbs.
 2002-03-11 18:38:07 255704  225818 XBSA Error (BSAInit): Attempt to
authorize root failed.
 2002-03-11 18:38:10 255704  225818 Begin level 1 backup rootdbs.
 2002-03-11 18:38:11 255704  225818 XBSA Error (BSAInit): Attempt to
authorize root failed.
 2002-03-11 18:38:14 255704  225818 Begin level 1 backup rootdbs.
 2002-03-11 18:38:15 255704  225818 XBSA Error (BSAInit): Attempt to
authorize root failed.
and in the dsm error log I had the following messages
11-03-2002 18:38:07 sessOpen: Error 137 from signon authentication.
11-03-2002 18:38:11 sessOpen: Error 137 from signon authentication.
11-03-2002 18:38:15 sessOpen: Error 137 from signon authentication.

I have reset the password on both nodes and now I receive the following
errors
 2002-03-12 15:55:27 275680  259688 /informix/bin/onbar_d -b -L0 rootdbs
 2002-03-12 15:55:29 275680  259688 Begin level 0 backup rootdbs.
 2002-03-12 15:55:30 275680  259688 XBSA Error (BSAInit): An unspecified
XBSA error has occurred: 96
 2002-03-12 15:55:35 275680  259688 Begin backup logical log 1432.
 2002-03-12 15:55:35 275680  259688 XBSA Error (BSAInit): An unspecified
XBSA error has occurred: 96
 2002-03-12 15:55:40 275680  259688 Begin backup logical log 1432.
 2002-03-12 15:55:41 275680  259688 XBSA Error (BSAInit): An unspecified
XBSA error has occurred: 96
 2002-03-12 15:55:46 275680  259688 Begin backup logical log 1432.
 2002-03-12 15:55:46 275680  259688 XBSA Error (BSAInit): An unspecified
XBSA error has occurred: 96

12-03-2002 15:55:30 sessOpen: Error 168 from signon authentication.
12-03-2002 15:55:35 sessOpen: Error 168 from signon authentication.
12-03-2002 15:55:41 sessOpen: Error 168 from signon authentication.
12-03-2002 15:55:46 sessOpen: Error 168 from signon authentication.


What does a Error 168 mean, and where do I go to find those error's, and
also does any know why my backups are failing.

Thanks   Doug McLauchlan
DISCLAIMER: "The information in this email and in any attachments is
confidential and intended solely for the attention and use of the
addressee(s). If this email is not intended for you, you must not use,
read,
distribute or copy it. If you have received this email by mistake please
call the sender immediately on 64-9-2620772 and erase the email and any
attachments, and any copies of the same. Internet communications are not
secure and therefore Woolworths (NZ) Ltd does not accept legal
responsibility for the contents of this message. Any views or opinions
expressed are solely those of the author and do not necessarily represent
those of Woolworths (NZ) Ltd unless specifically stated."

Reply via email to