IDS Forum

RE: TSM XBSA Error 96

Posted By: Roger Kee
Date: Friday, 2 June 2006, at 5:58 p.m.

In Response To: RE: TSM XBSA Error 96 (Thirugnanam, Kannan)

Kannan,

Sorry for the confusion. I don't support the TSM product line, so I wo=
uld
suggest you
contact Tivoli support for assistance with your TSM issue. However, I=
did
look up the
error code for you and it can be found using the 2nd link below. The f=
irst
link is to the online
TSM documentation page. Based on what I have seen in previous IDS/TSM
PMRs,
the values you listed for IDLETIMEOUT and COMMTIMEOUT seem low, so it c=
ould
be that TSM thinks there is a communications failure due to the low val=
ues
(which may
have worked fine in the past, but currently do not due to some change).=

"I think the IDLETIMEOUT was 60 and COMMTIMEOUT was 15. "

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=3D=
/com.ibm.itsmm.doc/9090u/ANS1017E.htm

ANS1017E
Session rejected: TCP/IP connection failure
Explanation:
An attempt to connect to the server using TCP/IP communications failed=
.
This error can occur if the LAN connection went down or if your system=

administrator canceled a backup operation.

System Action:
Session rejected. Processing stopped.

User Response:
Retry the operation, or wait until the server comes back up and retry =
the
operation. If the problem continues, see your system administrator for=

further help.

Thank you,

Roger

=

"Thirugnanam...." =

<Kannan.Thirugnan =

am@JTax.com> =
To

Sent by: ids@iiug.org =

ids-bounces@iiug. =
cc

org =

Subj=
ect

RE: TSM XBSA Error 96 [6870] =

06/02/2006 05:23 =

PM =

=

=

Please respond to =

ids@iiug.org =

=

=

Thanks, Roger.

The dsierror.log contains the below messages
06/02/06 12:30:22 sessRecvVerb: Error -50 from call to 'readRtn'.
06/02/06 12:30:22 ANS4993E TDPI SOL7 64bit ANS1017 ANS1017E (RC-50)
Session rejected: TCP/IP connection failure

06/02/06 13:23:30 sessRecvVerb: Error -50 from call to 'readRtn'.
06/02/06 13:23:30 ANS4993E TDPI SOL7 64bit ANS1017 ANS1017E (RC-50)
Session rejected: TCP/IP connection failure

Can you infer the above messages. The tsmlic.log had a license violatio=
n
message a few days back but there aren't any new messages.

Thank you,
Kannan Thirugnanam

-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Roger Kee
Sent: Friday, June 02, 2006 5:08 PM
To: ids@iiug.org
Subject: Re: TSM XBSA Error 96 [6868]

Kannan,

Some additional information.

ON-Bar might report an unspecified XBSA error 96. This indicates
that a TSM error occurred that could not be explained with the
currently defined XBSA return codes. The explanation for the error
will be in the dsierror.log file, which is specified by the DSMI_LOG
environment variable.

If there are any license violations, these will be documented in the
tsmlic.log file.

For other TSM API return codes, see Tivoli Storage Manager Using
the Application Program Interface.

The setting for COMMTIMEOUT can be changed from the TSM
management console at runtime, or in the dsmserv.opt file on the server=
=3D

...

Also, I substituted the word "client" for "storage agent" in the previo=
=3D

us
email.

Thank you,

Roger

=3D

Roger =3D

Kee/Tampa/IBM@IBM =3D

US =3D
To

Sent by: ids@iiug.org =3D

ids-bounces@iiug. =3D
cc

org =3D

Subj=3D
ect

Re: TSM XBSA Error 96 [6867] =3D

06/02/2006 04:49 =3D

PM =3D

=3D

=3D

Please respond to =3D

ids@iiug.org =3D

=3D

=3D

Kannan,

You should look at your Tivoli log files for clues to the source of the=
=3D

=3D3D

problem. You should check with
your Tivoli rep and see what you have set for the following parameters.=
=3D

=3D3D

You may need to check the
settings for both the sever and client side.

1. IDLETIMEOUT in the server option file (dsm.sys)
2. COMMTIMEOUT in dsmsta.opt

Thank you,

Roger

=3D3D

"Thirugnanam...." =3D3D

<Kannan.Thirugnan =3D3D

am@JTax.com> =3D3D
To

Sent by: ids@iiug.org =3D3D

ids-bounces@iiug. =3D3D
cc

org =3D3D

Subj=3D3D
ect

TSM XBSA Error 96 [6864] =3D3D

06/02/2006 04:19 =3D3D

PM =3D3D

=3D3D

=3D3D

Please respond to =3D3D

ids@iiug.org =3D3D

=3D3D

=3D3D

Hi Guys,

We are moving from Veritas NetBackup SM to Tivoli SM. The Informix
version is 9.40FC1 and TSM client version is 5.2.1, in our test server.=
=3D

=3D3D

The instance was running fine and we removed Netbackup client and
installed TSM. We were able to back up the instance using TSM
successfully.

While restoring, it doesn't restore root DBSpace but it starts restorin=
=3D

=3D3D
g
the other spaces successfully. Without the root DBSpace, the instance i=
=3D

=3D3D
s
cooked. The last time (the one below), we had to stop the restore
before it finished. We are getting error 96, which seems to be a
generalized XBSA error.

I couldn't find any resolution to this error in the TSM and Onbar
manuals or through the internet. If you have experience in fixing
issues with Informix-TSM combination and would like to share it, I will=
=3D

=3D3D

deeply appreciate the help.

The backup message in the bar_act.log
***********************************************************************=
=3D

=3D3D
*
********************************
2006-06-02 12:57:56 4999 4997 /opt/informix/bin/onbar_d -b -L 0 -w
2006-06-02 12:58:03 4999 4997 Begin level 0 backup rootdbs.
2006-06-02 12:58:03 4999 4997 Successfully connected to Storage
Manager.
2006-06-02 12:58:06 4999 4997 Completed level 0 backup rootdbs
(Storage Manager copy ID: 0 3096).
2006-06-02 12:58:06 4999 4997 Begin level 0 backup phyldbs.
2006-06-02 12:58:06 4999 4997 Completed level 0 backup phyldbs
(Storage Manager copy ID: 0 3097).
2006-06-02 12:58:06 4999 4997 Begin level 0 backup llogdbs.
2006-06-02 12:58:06 4999 4997 Completed level 0 backup llogdbs
(Storage Manager copy ID: 0 3098).
2006-06-02 12:58:06 4999 4997 Begin level 0 backup dbs1.
2006-06-02 12:58:47 4999 4997 Completed level 0 backup dbs1 (Storage
Manager copy ID: 0 3099).
2006-06-02 12:58:47 4999 4997 Begin level 0 backup dbs2.
2006-06-02 13:01:24 4999 4997 Completed level 0 backup dbs2 (Storage
Manager copy ID: 0 3100).
2006-06-02 13:01:24 4999 4997 Begin level 0 backup dbs3.
2006-06-02 13:01:27 4999 4997 Completed level 0 backup dbs3 (Storage
Manager copy ID: 0 3101).
2006-06-02 13:01:27 4999 4997 Begin backup logical log 12559.
2006-06-02 13:01:27 4999 4997 Successfully connected to Storage
Manager.
2006-06-02 13:01:27 4999 4997 Completed backup logical log 12559
(Storage Manager copy ID: 0 3102).
2006-06-02 13:01:28 5020 5018 /opt/informix/bin/onbar_d -b -l
2006-06-02 13:01:30 4999 4997 /opt/informix/bin/onbar_d complete,
returning 0 (0x00)
2006-06-02 13:01:31 5020 5018 /opt/informix/bin/onbar_d complete,
returning 0 (0x00)
***********************************************************************=
=3D

=3D3D
*
********************************

The restore message in the bar_act.log
***********************************************************************=
=3D

=3D3D
*
********************************
2006-06-02 13:21:40 5063 5061 /opt/informix/bin/onbar_d -r -w
2006-06-02 13:21:46 5063 5061 Successfully connected to Storage
Manager.
2006-06-02 13:21:46 5063 5061 Begin salvage for log 12560.
2006-06-02 13:21:47 5063 5061 Completed salvage of logical log 12560.
2006-06-02 13:22:09 5063 5061 Successfully connected to Storage
Manager.
2006-06-02 13:22:09 5063 5061 Begin cold level 0 restore rootdbs
(Storage Manager copy ID: 0 3096).
2006-06-02 13:23:30 5063 5061 XBSA Error (BSAGetData): An unspecified
XBSA error has occured: 96
2006-06-02 13:23:31 5063 5061 Skipped backup/restore of space
'rootdbs'.
2006-06-02 13:23:31 5063 5061 Begin cold level 0 restore llogdbs
(Storage Manager copy ID: 0 3098).
2006-06-02 13:23:32 5063 5061 Completed cold level 0 restore llogdbs.
2006-06-02 13:23:33 5063 5061 Begin cold level 0 restore phyldbs
(Storage Manager copy ID: 0 3097).
2006-06-02 13:23:33 5063 5061 Completed cold level 0 restore phyldbs.
2006-06-02 13:23:34 5063 5061 Begin cold level 0 restore dbs1 (Storage
Manager copy ID: 0 3099).
2006-06-02 13:51:14 5063 5061 Completed cold level 0 restore dbs1.
2006-06-02 13:51:15 5063 5061 Begin cold level 0 restore dbs2 (Storage
Manager copy ID: 0 3100).
2006-06-02 14:07:56 5063 5061 Process 5063 received signal 15. Process
will exit after cleanup.
2006-06-02 14:07:57 5063 5061 Skipped backup/restore of space 'dbs2'.
2006-06-02 14:10:29 5063 5061 Due to the previous error, logical
restore will not be attempted.
2006-06-02 14:10:29 5063 5061 /opt/informix/bin/onbar_d complete,
returning 141 (0x8d)
***********************************************************************=
=3D

=3D3D
*
********************************

The messages in the bar_debug.log

***********************************************************************=
=3D

=3D3D
*
********************************
2006-06-02 13:22:09 5063 5061 bar_phys_write_restore: input buf
0x021a8540 bufnbytes 63488
2006-06-02 13:23:30 5063 5061 bar_phys_write_restore: output buf
0x6f615400 events 0 errtxt
2006-06-02 13:23:30 5063 5061 bar_phys_write_restore: return 0 (0x00)
2006-06-02 13:23:30 5063 5061 barGetData: enter
2006-06-02 13:23:30 5063 5061 BSAGetData: enter
2006-06-02 13:23:30 5063 5061 BSAGetData: input 1
2006-06-02 13:23:30 5063 5061 BSAGetData: input: bufferLen =3D3D3D 6348=
8,=3D

numBytes =3D3D3D 0
2006-06-02 13:23:30 5063 5061 BSAGetData: output: bufferLen =3D3D3D 634=
88=3D

,
numBytes =3D3D3D 0
2006-06-02 13:23:30 5063 5061 BSAGetData: return 96 (0x60)
2006-06-02 13:23:30 5063 5061 do_xbsa_error: enter
2006-06-02 13:23:30 5063 5061 do_xbsa_error: input the_error 96
function BSAGetData
2006-06-02 13:23:31 5063 5061 do_xbsa_error: return 138 (0x8a)
2006-06-02 13:23:31 5063 5061 barGetData: output last_lap
2006-06-02 13:23:31 5063 5061 barGetData: return 96 (0x60)
2006-06-02 13:23:31 5063 5061 do_phys_restore: Got 0:31 pages for
rootdbs
2006-06-02 13:23:31 5063 5061 barEndTxn: enter

***********************************************************************=
=3D

=3D3D
*
********************************

Thank you,
Kannan Thirugnanam

The information in this electronic mail message is Jackson Hewitt
Confidential and may be legally privileged. It is intended solely for
the addressee's. Access to this Internet electronic mail message by
anyone else is unauthorized. If you are not the intended recipient, any=
=3D

=3D3D

disclosure, copying, distribution or any action taken or omitted to be
taken in reliance on it is prohibited and may be unlawful.

***** Jackson Hewitt Email Disclaimer *****

The sender believes that this E-mail and any attachments were free of a=
=3D

=3D3D
ny
virus, worm,
Trojan horse, and/or malicious code when sent. This message and its
attachments could
have been infected during transmission. By reading the message and open=
=3D

=3D3D
ing
any
attachments, the recipient accepts full responsibility for taking
protective
and remedial
action about viruses and other defects. The sender's business entity is=
=3D

=3D3D
not

liable for any
loss or damage arising in any way from this message or its attachments.=
=3D

=3D3D

Privileged/Confidential Information may be contained in this message. I=
=3D

=3D3D
f
you
are not the
addressee indicated in this message (or responsible for delivery of the=
=3D

=3D3D

message to such
person), you may not copy or deliver this message to anyone. In such ca=
=3D

=3D3D
se,
you
should
destroy this message and kindly notify the sender by reply email.

***********************************************************************=
=3D

=3D3D
********

Forum Note: Use "Reply" to post a response in the discussion forum.

=3D3D

***********************************************************************=
=3D

********

Forum Note: Use "Reply" to post a response in the discussion forum.

=3D

***********************************************************************=
*
*******
Forum Note: Use "Reply" to post a response in the discussion forum.

***** Jackson Hewitt Email Disclaimer *****

The sender believes that this E-mail and any attachments were free of a=
ny
virus, worm,
Trojan horse, and/or malicious code when sent. This message and its
attachments could
have been infected during transmission. By reading the message and open=
ing
any
attachments, the recipient accepts full responsibility for taking
protective
and remedial
action about viruses and other defects. The sender's business entity is=
not

liable for any
loss or damage arising in any way from this message or its attachments.=

Privileged/Confidential Information may be contained in this message. I=
f
you
are not the
addressee indicated in this message (or responsible for delivery of the=

message to such
person), you may not copy or deliver this message to anyone. In such ca=
se,
you
should
destroy this message and kindly notify the sender by reply email.

***********************************************************************=
********

Forum Note: Use "Reply" to post a response in the discussion forum.

=

Messages In This Thread

• TSM XBSA Error 96
  Thirugnanam, Kannan -- Friday, 2 June 2006, at 4:18 p.m.
  • Re: TSM XBSA Error 96
    Darren_Jacobs@carmax.com -- Friday, 2 June 2006, at 4:28 p.m.
    • RE: TSM XBSA Error 96
      Thirugnanam, Kannan -- Friday, 2 June 2006, at 4:33 p.m.
      • RE: TSM XBSA Error 96
        Thirugnanam, Kannan -- Friday, 2 June 2006, at 5:08 p.m.
  • Re: TSM XBSA Error 96
    Roger Kee -- Friday, 2 June 2006, at 4:49 p.m.
    • Re: TSM XBSA Error 96
      Roger Kee -- Friday, 2 June 2006, at 5:07 p.m.
      • RE: TSM XBSA Error 96
        Thirugnanam, Kannan -- Friday, 2 June 2006, at 5:23 p.m.
        • RE: TSM XBSA Error 96
          Roger Kee -- Friday, 2 June 2006, at 5:58 p.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.