RE: onconfig file
I have seen this stated here, and have some others say they cannot change
this. I have not had problems just changing LTAPEDEV with vi, then running
ontape. It appears to read onconfig and pick up the new value. (It may be
the side of bed you got out of).
MW
> -----Original Message-----
> From: owner-informix-list@iiug.org
> [mailto:owner-informix-list@iiug.org]On Behalf Of David Williams
> Sent: Wednesday, 11 June 2003 7:10 a.m.
> To: informix-list@iiug.org
> Subject: Re: onconfig file
>
> [cut]
>
> Once transaction logging to a device (LTAPEDEV set to /dev/null) you
> cannot re-
> enable it without onmonitor. It sets a shared memory flag
> which says "keep
> logical logs
> for ontape to be able to collect and write to tape".
> Otherwise they get
> discarded.
>
> THIS IS WHY IT IS NEEDED.
>
> Also when creating a chunk it gives better error messages
> than onspaces.
> i.e.
> Whether the chunk has the wrong owner/wrong group/wrong
> permissions/does not exist. onspaces just gives a generic
> message like
> 'cannot access
> chunk'.
>
> [cut]
>
"Murray Wood" <murray@quanta.co.nz> wrote in message
news:bc5mp2$sam$1@terabinaries.xmission.com...
>
> I have seen this stated here, and have some others say they cannot change
> this. I have not had problems just changing LTAPEDEV with vi, then
running
> ontape. It appears to read onconfig and pick up the new value. (It may
be
> the side of bed you got out of).
>
That is except when the engine has to start saving them rather then just
marking them as
already backed up in which case ontape will not back them up!
ontape reads LTAPEDEV and I assume is restarted after a change.
The engine reads LTAPEDEV to see if it is /dev/null or not to set this
flag.
The engine is NOT restarted!!
> MW
>
> > -----Original Message-----
> > From: owner-informix-list@iiug.org
> > [mailto:owner-informix-list@iiug.org]On Behalf Of David Williams
> > Sent: Wednesday, 11 June 2003 7:10 a.m.
> > To: informix-list@iiug.org
> > Subject: Re: onconfig file
> >
> > [cut]
> >
> > Once transaction logging to a device (LTAPEDEV set to /dev/null) you
> > cannot re-
> > enable it without onmonitor. It sets a shared memory flag
> > which says "keep
> > logical logs
> > for ontape to be able to collect and write to tape".
> > Otherwise they get
> > discarded.
> >
> > THIS IS WHY IT IS NEEDED.
> >
> > Also when creating a chunk it gives better error messages
> > than onspaces.
> > i.e.
> > Whether the chunk has the wrong owner/wrong group/wrong
> > permissions/does not exist. onspaces just gives a generic
> > message like
> > 'cannot access
> > chunk'.
> >
> > [cut]
> >
>