IDS Forum

RE: TSM XBSA Error 96

Posted By: Thirugnanam, Kannan
Date: Friday, 2 June 2006, at 5:08 p.m.

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

Thanks Darren and Roger for the replies.

The bar parameters in the onconfig are
BAR_BSALIB_PATH=/opt/tivoli/tsm/client/informix/bin64/libTDPinf.so
BAR_ACT_LOG /opt/informix/bar_act.log
BAR_DEBUG_LOG /opt/informix/bar_dbg.log
BAR_MAX_BACKUP 0
BAR_RETRY 1
BAR_NB_XPORT_COUNT 10
BAR_XFER_BUF_SIZE 31
RESTARTABLE_RESTORE off
BAR_PROGRESS_FREQ 0
BAR_DEBUG 7

The BSALIB file seems to be for 32 bit. There is one more file
libTDPinf64.so. Is this the file we should be using for 64 bit IDS.

/opt/tivoli/tsm/client/informix/bin64/libTDPinf64.so
/opt/tivoli/tsm/client/informix/bin64/libTDPinf.so

I think the IDLETIMEOUT was 60 and COMMTIMEOUT was 15.

The permissions and mode to all the DBSPaces are correct. The only
difference I find is that the DBSpace link is pointing to another link
which points to a raw device. When I had set up servers a few months
back, we could only have 1 level in the link chain. Since the instance
was up and running, I don't see the DBSpaces to be an issue.

Thank you,
Kannan Thirugnanam

-----Original Message-----
From: Darren_Jacobs@carmax.com [mailto:Darren_Jacobs@carmax.com]
Sent: Friday, June 02, 2006 4:45 PM
To: Thirugnanam, Kannan
Subject: RE: TSM XBSA Error 96 [6866]

We are using the same version of TSM. Below are my onconfig settings,
may
not have anything to do with your issue, but if I recall I saw something
similiar when trying to do the backups but not a restore. Have you
doubled
checked the perms on the rootdbs and ensured they are 660?

onconfig settings:

BAR_ACT_LOG /usr/informix/logs/bar_act_1st.log
BAR_MAX_BACKUP 0
BAR_RETRY 1
BAR_NB_XPORT_COUNT 10
BAR_XFER_BUF_SIZE 31
BAR_DEBUG_LOG /usr/informix/logs/bar_dbug.log # ON-Bar Debug Log - not
in
/tmp please
BAR_PROGRESS_FREQ 0
BAR_BSALIB_PATH /opt/tivoli/tsm/client/informix/bin64/libTDPinf64.sl #
full
pathname of storage manager

"Thirugnanam...."

<Kannan.Thirugnan

am@JTax.com>
To

Sent by: ids@iiug.org

ids-bounces@iiug.
cc

org

Subject

RE: TSM XBSA Error 96 [6866]

06/02/2006 04:33

PM

Please respond to

ids@iiug.org

Thank you, Darren for the reply.

The ixbar.1 (servernum=1) contains the Storage ID #, one for each
DBSpace. While restoring, Onbar requests the correct Storage ID#.

I had set BAR_DEBUG (to) 7 and that's how I was able to get XBSA detail.
It is a BIG file so I have pasted only the portion where it failed.

Thank you,
Kannan Thirugnanam

-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Darren_Jaco....
Sent: Friday, June 02, 2006 4:28 PM
To: ids@iiug.org
Subject: Re: TSM XBSA Error 96 [6865]

What does your ixbar.<servernum> look like? Does it contain the backup
id
of the rootdbs space?

It looks like you are performing whole system backups. What are your BAR

settings in your onconfig? Do you have BAR_DEBUG set? If not, set it to
5, run it again and take a look in the debug log.

"Thirugnanam...."

<Kannan.Thirugnan

am@JTax.com> To

Sent by: ids@iiug.org

ids-bounces@iiug. cc

org

Subject

TSM XBSA Error 96 [6864]

06/02/2006 04:19

PM

Please respond to

ids@iiug.org

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.
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 restoring

the other spaces successfully. Without the root DBSpace, the instance is

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
deeply appreciate the help.

The backup message in the bar_act.log
************************************************************************

********************************
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)
************************************************************************

********************************

The restore message in the bar_act.log
************************************************************************

********************************
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)
************************************************************************

********************************

The messages in the bar_debug.log

************************************************************************

********************************
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 = 63488,
numBytes = 0
2006-06-02 13:23:30 5063 5061 BSAGetData: output: bufferLen = 63488,
numBytes = 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

************************************************************************

********************************

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
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
any
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
opening
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. If

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
case,
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.

************************************************************************
*******
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
any
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
opening
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. If
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
case,
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.

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

The sender believes that this E-mail and any attachments were free of any 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 opening 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. If 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 case, you should
destroy this message and kindly notify the sender by reply email.

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.