Re: XBSA Error (BSAInit): An unspecified XBSA error has occured: 96

Posted in 2005

Martin Fuerderer — Fri, 29 Jul 2005 11:38:44 +0200 — source: Usenet: comp.databases.informix

Hi, you may have to update the file "sm_versions" in your $INFORMIXDIR/etc directory to reflect that now you are using TSM. Other than that check whether there is a log file from the TSM software that gives more detail about the problem. Also, I think it is not sufficient to install the TSM's XBSA library (aka "Data Protector") only. For ON-Bar to be able to work with TSM, there is some TSM API software (more shared libraries) necessary. The XBSA itself doesn't connect to the storage manager server (remote TSM). Only these additional libraries can do that and therefore are needed, in fact acting as a client. Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Information Management owner-informix-list@iiug.org wrote on 28.07.2005 16:51:57: > Hi, > I am trying to move from ISM to TSM and I have the following error: > - XBSA Error (BSAInit): An unspecified XBSA error has occured: 96 - > > Althrough I spent a lot of time on Internet and some news groups, I didn't > see anything interessting... > > bar_act.log: > ------------------------------------------------- > 2005-07-28 15:40:03 108878 167326 /opt/informix/9.4/bin/onbar_d -b > 2005-07-28 15:40:03 108878 167326 BAR_XFER_BUF_SIZE exceeded maximum > allowed limit. Changing buffer size to 61440. > 2005-07-28 15:40:07 108878 167326 Begin level 0 backup rootdbs. > 2005-07-28 15:40:07 108878 167326 XBSA Error (BSAInit): An unspecified > XBSA error has occured: 96 > 2005-07-28 15:40:19 108878 167326 /opt/informix/9.4/bin/onbar_d > complete, returning 96 (0x60) > ------------------------------------------------- > > Extract of the bar_dbug.log: > ------------------------------------------------- > 2005-07-28 15:40:07 108878 167326 barBsaInit: envtab[0] > ISM_SERVER=p02101lint0 > 1 > 2005-07-28 15:40:07 108878 167326 barBsaInit: envtab[1] > ISM_DATA_VOLUME_POOL=I > SMData > 2005-07-28 15:40:07 108878 167326 barBsaInit: envtab[2] > ISM_LOG_VOLUME_POOL=IS > MLogs > 2005-07-28 15:40:07 108878 167326 barBsaInit: envtab[3] > ISM_SAVESET_NAME=:/STE > LINK_UAT/rootdbs/0 > 2005-07-28 15:40:07 108878 167326 bar_alarm: enter > 2005-07-28 15:40:07 108878 167326 bar_alarm: input 0 seconds > 2005-07-28 15:40:07 108878 167326 bar_alarm: return 600 (0x258) > 2005-07-28 15:40:07 108878 167326 BSAInit: enter > 2005-07-28 15:40:07 108878 167326 BSAInit: input tokenPtr owner > 2005-07-28 15:40:07 108878 167326 BSAInit: return 96 (0x60) > 2005-07-28 15:40:07 108878 167326 do_xbsa_error: enter > 2005-07-28 15:40:07 108878 167326 do_xbsa_error: input the_error 96 > function B > SAInit > 2005-07-28 15:40:07 108878 167326 do_xbsa_error: return 138 (0x8a) > 2005-07-28 15:40:07 108878 167326 barBsaInit: return 96 (0x60) > 2005-07-28 15:40:08 108878 167326 barBeginTxn: return 96 (0x60) > 2005-07-28 15:40:08 108878 167326 barEndTxn: enter > 2005-07-28 15:40:08 108878 167326 barEndTxn: return 0 (0x00) > 2005-07-28 15:40:08 108878 167326 barTerminate: enter > 2005-07-28 15:40:08 108878 167326 barTerminate: return 0 (0x00) > ------------------------------------------------- > > I don't know why I have still some reference to ISM variables since I have > removed all. > > Thanks for any help > Regards > ptitchuisse > > sending to informix-list