ADSM-L

Re: FW: Informix and ADSM problems.

1997-12-18 03:23:23
Subject: Re: FW: Informix and ADSM problems.
From: Keith Downer <Keithdo AT EI.CSS.MOT DOT COM>
Date: Thu, 18 Dec 1997 08:23:23 -0000
> ----------
> From:         Gardar Georg Nielsen[SMTP:goggi AT RSP DOT IS]
> Sent:         16 December 1997 14:27
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: FW: Informix and ADSM problems.
>
> >
> > > 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 for these responses Gardar,

> Answer 1.
>
> This is from the
> http://www.storage.ibm.com/software/adsm/pubsv3/aix/server/html/admmsg
> /a45emc26.htm:
>
> ANS0282E Password file is not available.
> Explanation: The file containing the stored password for the specified
> server-name is unavailable.
> System Action: ADSM ends.
> User Response: The root user must set and store a new password.
>
> Have you generated the the password file by running a dsmc command
> f.ex.
> dsmc query host
>
The password has been generated and stored.  My first example above
using 'onbar -l' shows it must be working because the logs are backed up
successfully.  The second example with the failure shows part of the
backup succeeding (the rootdbs) but the backup of the logical logs
failing.  It's like ADSM knows the password in the first part but
'forgets' it in the second.  The two examples were also run within
minutes of one another.  I'll keep plugging away in this area but if
anyone has any more ideas I'd be pleased to hear them.

> Answer 2.
>
> This is from the
> http://ppdbooks.pok.ibm.com:80/cgi-bin/bookmgr/bookmgr.cmd/BOOKS/EZ319
> 901/CO
>
> The ON-Bar utility references the ADSM client code version according
> to
> the first, second and last fields of the IBM fix level output, shown
> with
> the lslpp -h command.  Therefore you are supposed to put 2.1.7 into
> bar_version.
> If informix is already running it is not going to read the sm_version
> file
> then you have to use dbaccess to insert into the bar_version table
> with
>   insert into bar_version values ('1','2.1.7','adsm','2')
>
This works for version 2.1.0.6 of the client but IBM have renamed the
AIX 4.1 version of the client 2.1.10.7 (at least in the version I pulled
off the ADSM website last week).  When I enter the information as you
have shown above I get the version mismatch errors.  I wasn't too
concerned about using this version of the client but I was wondering
whether IBM have checked that onbar still runs with ADSM after this
change.

> Best,
> Gardar Nielsen,
> goggi AT rsp DOT is
>
<Prev in Thread] Current Thread [Next in Thread>