SEO

I am having fun trying to get onbar to work on IDS 9.40 running on
Linux.

Whenever I run onbar -b -L I get shmdt: errno = 22, and the
bar_act.log indicates that onbar has completed with code 156. Where
can I find what these error codes mean?

As to the shmdt error I have observed that there is a segment of
shared memory owned by Informix which does not get removed when I stop
the engine. It has a status of dest.

There do seem to be rather a large number of segments (>20) for such
a small system.

I would include the ONCONFIG file but there is no link between the
Linux server and the network.

regards

Malcolm

Error 22 means "out of resources", usually a kernel tuning issue.

"malcolm" <malcolm.weallans@btopenworld.com> wrote in message
news:3efc1745.0404290751.220b0316@posting.google.c om...
> I am having fun trying to get onbar to work on IDS 9.40 running on
> Linux.
>
> Whenever I run onbar -b -L I get shmdt: errno = 22, and the
> bar_act.log indicates that onbar has completed with code 156. Where
> can I find what these error codes mean?
>
> As to the shmdt error I have observed that there is a segment of
> shared memory owned by Informix which does not get removed when I stop
> the engine. It has a status of dest.
>
> There do seem to be rather a large number of segments (>20) for such
> a small system.
>
> I would include the ONCONFIG file but there is no link between the
> Linux server and the network.
>
> regards
>
> Malcolm

"malcolm" <malcolm.weallans@btopenworld.com> wrote in message
news:3efc1745.0404290751.220b0316@posting.google.c om...
> I am having fun trying to get onbar to work on IDS 9.40 running on
> Linux.
>
> Whenever I run onbar -b -L I get shmdt: errno = 22, and the
> bar_act.log indicates that onbar has completed with code 156. Where
> can I find what these error codes mean?
>

Have a look at the Backup and restore guide, chapter 11.
Oh, bugger.
Code 155 and 157 are listed..... gues which one ain't?

Malc_p

I've had the same problem on Solaris 9 with IDS 9.40.
The solution was to tune kernel parameters (/etc/system on Solaris, I don't
know about Linux).
Precisely it's this parameter: shmsys:shminfo_shmmax.
The machine on which IDS RUNS has 8 GB of RAM but the default value for
shmsys:shminfo_shmmax was set to 268435456 (256 MB), according to
ids_machine_notes.txt. I've set it to 1073741824 (1 GB) and error never
occured again.

"malcolm" <malcolm.weallans@btopenworld.com> wrote in message
news:3efc1745.0404290751.220b0316@posting.google.c om...
> I am having fun trying to get onbar to work on IDS 9.40 running on
> Linux.
>
> Whenever I run onbar -b -L I get shmdt: errno = 22, and the
> bar_act.log indicates that onbar has completed with code 156. Where
> can I find what these error codes mean?
>
> As to the shmdt error I have observed that there is a segment of
> shared memory owned by Informix which does not get removed when I stop
> the engine. It has a status of dest.
>
> There do seem to be rather a large number of segments (>20) for such
> a small system.
>
> I would include the ONCONFIG file but there is no link between the
> Linux server and the network.
>
> regards
>
> Malcolm

Thanks all for the help so far. This is the news.

The problem with onbar seems to have been fixed. It turned out to be
that I had TAPEDEV set to /dev/null in the onconfig file. That has
got me very confused as I am not using ontape so why does onbar look
at the TAPEDEV. (I guess some developer somewhere has a good reason
for that - but it doesn't make life any easier).

I am now getting lots of the shmdt: errno 22 messages, so it looks
like that could be a separate problem.

As to the completion codes - I still can't find out what 156 means.
As my alter ego Malc_p pointed out the manual lists 155 and 157 but
not 156. And how are we supposed to find this in the manual. I
looked in the index for error codes, and even completion codes. In
onbar they are RETURN codes - I guess I should have known that as the
error message does say RETURNING but I searched the document for
returning and that didn't find anything. I even looked in the section
marked "Troubleshooting" but that doesn't include analysing the log.

regards

Malcolm

"Malc" <malc_p@btinternet.com> wrote in message news:<c6rlt8$pbq$1@sparta.btinternet.com>...
> "malcolm" <malcolm.weallans@btopenworld.com> wrote in message
> news:3efc1745.0404290751.220b0316@posting.google.c om...
> > I am having fun trying to get onbar to work on IDS 9.40 running on
> > Linux.
> >
> > Whenever I run onbar -b -L I get shmdt: errno = 22, and the
> > bar_act.log indicates that onbar has completed with code 156. Where
> > can I find what these error codes mean?
> >
>
> Have a look at the Backup and restore guide, chapter 11.
> Oh, bugger.
> Code 155 and 157 are listed..... gues which one ain't?
>
> Malc_p

> The problem with onbar seems to have been fixed. It turned out to be
> that I had TAPEDEV set to /dev/null in the onconfig file. That has
> got me very confused as I am not using ontape so why does onbar look
> at the TAPEDEV. (I guess some developer somewhere has a good reason
> for that - but it doesn't make life any easier).

Well, if that is the behaviour, I'd contact your support provider and
look to get a bug logged.

The "Backup and Restore Guide" states (page 4-4 in my copy) TAPEDEV
Specifies the tape device where storage spaces are backed up. ON-Bar
does not use the TAPEDEV parameter.

So the behaviour you describe is either a docs bug or a product bug.

However if you had LTAPEDEV set to /dev/null thats a different
problem.

Despite the fact onbar will ignore the value, of LTAPEDEV, if it is
set to /dev/null the engine will already have marked the logs as
backed up. The engine will have read LTAPEDEV and seen it is s
"special device". So when onbar tries to backup the logs it says ..
these have already been backed up. Hence the Warning on page 4-10 of
my manual.


malcolm.weallans@btopenworld.com (malcolm) wrote in message news:<3efc1745.0404300155.4d91049d@posting.google. com>...
> Thanks all for the help so far. This is the news.
>
> The problem with onbar seems to have been fixed. It turned out to be
> that I had TAPEDEV set to /dev/null in the onconfig file. That has
> got me very confused as I am not using ontape so why does onbar look
> at the TAPEDEV. (I guess some developer somewhere has a good reason
> for that - but it doesn't make life any easier).
>
> I am now getting lots of the shmdt: errno 22 messages, so it looks
> like that could be a separate problem.
>
> As to the completion codes - I still can't find out what 156 means.
> As my alter ego Malc_p pointed out the manual lists 155 and 157 but
> not 156. And how are we supposed to find this in the manual. I
> looked in the index for error codes, and even completion codes. In
> onbar they are RETURN codes - I guess I should have known that as the
> error message does say RETURNING but I searched the document for
> returning and that didn't find anything. I even looked in the section
> marked "Troubleshooting" but that doesn't include analysing the log.
>
> regards
>
> Malcolm
>
> "Malc" <malc_p@btinternet.com> wrote in message news:<c6rlt8$pbq$1@sparta.btinternet.com>...
> > "malcolm" <malcolm.weallans@btopenworld.com> wrote in message
> > news:3efc1745.0404290751.220b0316@posting.google.c om...
> > > I am having fun trying to get onbar to work on IDS 9.40 running on
> > > Linux.
> > >
> > > Whenever I run onbar -b -L I get shmdt: errno = 22, and the
> > > bar_act.log indicates that onbar has completed with code 156. Where
> > > can I find what these error codes mean?
> > >
> >
> > Have a look at the Backup and restore guide, chapter 11.
> > Oh, bugger.
> > Code 155 and 157 are listed..... gues which one ain't?
> >
> > Malc_p