> Hi,
>
> I'm running ADSM V3 server with a V2 client on AIX 4.1.5 and
> attempting
> to backup Informix 7.23 database using onbar but running into a
> problem.
> I can successfully backup the logical logs using onbar -l.  The onbar
> message file /tmp/bar_act.log contains the following:-
>
> 1997-12-15 12:20:22 22170  18064 Begin backup logical log 62756.
> 1997-12-15 12:20:22 22170  18064 Successfully connected to Storage
> Manager.
> 1997-12-15 12:20:23 22170  18064 Completed backup logical log 6
>
> However, if I try to backup an individual dbspace using, for example,
> 'onbar -b -L 0 rootdbs' I get the following:-
>
>  1997-12-15 12:25:04 22192  18064 onbar -b -L 0 rootdbs
>  1997-12-15 12:25:04 22192  18064 Begin level 0 backup rootdbs.
>  1997-12-15 12:25:05 22192  18064 Successfully connected to Storage
> Manager.
>  1997-12-15 12:27:58 22192  18064 Completed level 0 backup rootdbs.
>  1997-12-15 12:28:03 22192  18064 Begin backup logical log 62757.
>  1997-12-15 12:28:03 22192  18064 An unspecified XBSA error has
> occurred: 96
>  1997-12-15 12:28:08 22192  18064 SQL   -25580  System error occurred
> in
> network function.
>  1997-12-15 12:28:08 22192  18064 bar_sighdlr: Received signal 11.
> Process 22192 exiting...
>
> Notice that the backup of the rootdbs appears to be successful but the
> backup of the logical log fails.  I get a similar error when I try to
> restore.
>
> The readme for the API tells me to look in the dsierror.log which
> contains:-
>
> 10/12/97   16:37:47  ANS0282E (RC168)  Password file is not available.
> 10/12/97   16:43:54  ANS0282E (RC168)  Password file is not available.
> 10/12/97   16:45:58  ANS0282E (RC168)  Password file is not available.
> 15/12/97   12:28:03  ANS0282E (RC168)  Password file is not available.
>
> Which password file?  We are set up to generate the password file and
> the encrypted version has been made readable by everyone just in case
> that was the issue.
>
> My local IBM support have suggested that in a similar situation,
> setting
> 'compressalways yes' in dsm.opt on the client would fix it but it
> appears to have made no difference.
>
> I also had this issue on the ADSM V2 server.
>
> The version of the client is 2.1.0.6.  I've tried using the latest
> client 2.1.0.7 but IBM have changed the numbering system so that it
> appears as 2.1.10.7 and I cannot get this to be recognised in the
> Informix sm_versions file.
>
> Has anyone seen this?  I'd be interested to hear from anyone who has
> set
> up ADSM/Informix and what issues they had also which versions of
> clients/server, etc they are using.
>
> Thanks,
>
> Keith
>