Force logging primary key, and complete column dat
The poster asked whether IDS can be forced to log the primary key and full column values in the logical log, since an update (HUPDAT) only records the changed bytes, unlike Oracle's supplemental logging. Art Kagel answered flatly "No", while Madison Pruet said "sorta": full row logging (giving before/after images, seen as HUPBEF/HUPAFT in 11.x) can be enabled, but only as a side effect of using the CDC API, and at the cost of much more log volume. A follow-up asking for a non-CDC command to enable full row logging (and about behaviour in 9.40/10.0) went unanswered, so no further resolution is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
I wonder that does IDS has some kinds of setting, which would force it logging the primary key and making column data completely. I mean, Now, in logical log, the HUPDAT operation, would just record the updated bytes, with no primary key, and even the column data is not complete. Which I think the IDS logical log only record the necessary bytes.an I just want to know that if IDS has some kind of setting, for example, like Oracle, to force logical log records the primary key and the complete column data. BlackThought --f46d0407166358737004b24d3b30
Reply to myself, found in IDS 11.5 It seems in 11.5, logical log has "HUPBEF" and "HUPAFT", which is update before image and update after. But how about IDS 9.40 and 10.0? which is "HUPDAT" instread ? On Tue, Nov 22, 2011 at 2:51 PM, Wang Shiyi <osdbms@gmail.com> wrote: > I wonder that does IDS has some kinds of setting, which would force it > logging the primary key and making column data completely. > > I mean, Now, in logical log, the HUPDAT operation, would just record the > updated bytes, with no primary key, and even the column data is not > complete. > Which I think the IDS logical log only record the necessary bytes.an > > I just want to know that if IDS has some kind of setting, for example, like > Oracle, to force logical log records the primary key and the complete > column data. > > BlackThought > > --f46d0407166358737004b24d3b30 > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --f46d04071663b1a13f04b24f5f97
No. Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Tue, Nov 22, 2011 at 1:51 AM, Wang Shiyi <osdbms@gmail.com> wrote: > I wonder that does IDS has some kinds of setting, which would force it > logging the primary key and making column data completely. > > I mean, Now, in logical log, the HUPDAT operation, would just record the > updated bytes, with no primary key, and even the column data is not > complete. > Which I think the IDS logical log only record the necessary bytes.an > > I just want to know that if IDS has some kind of setting, for example, like > Oracle, to force logical log records the primary key and the complete > column data. > > BlackThought > > --f46d0407166358737004b24d3b30 > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --e89a8f3ba4d3769aa304b250a9d0
Sorta. You can force a before/after image if you turn on full row logging. This can be done by taking advantage of CDC calls. However if you do this you must be prepared for a significant increase in the amount of logging that is done. From: "Wang Shiyi" <osdbms@gmail.com> To: ids@iiug.org Date: 11/22/2011 12:52 AM Subject: Force logging primary key, and complete column.... [25449] Sent by: ids-bounces@iiug.org I wonder that does IDS has some kinds of setting, which would force it logging the primary key and making column data completely. I mean, Now, in logical log, the HUPDAT operation, would just record the updated bytes, with no primary key, and even the column data is not complete. Which I think the IDS logical log only record the necessary bytes.an I just want to know that if IDS has some kind of setting, for example, like Oracle, to force logical log records the primary key and the complete column data. BlackThought --f46d0407166358737004b24d3b30 ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.
For some operations, it must do a full row logging, like, Insert or Delete.
Otherwise, how can it redo Insert /undo Delete in a transaction?
But, can we use onlog tool to see the full row image?
Thanks,
Frank
On Tue, Nov 22, 2011 at 10:02 AM, Madison Pruet <mpruet@us.ibm.com> wrote:
> Sorta.
>
> You can force a before/after image if you turn on full row logging. This
> can be done by taking advantage of CDC calls. However if you do this you
> must be prepared for a significant increase in the amount of logging that
> is done.
>
> From: "Wang Shiyi" <osdbms@gmail.com>
>
> To: ids@iiug.org
>
> Date: 11/22/2011 12:52 AM
>
> Subject: Force logging primary key, and complete column.... [25449]
>
> Sent by: ids-bounces@iiug.org
>
> I wonder that does IDS has some kinds of setting, which would force it
> logging the primary key and making column data completely.
>
> I mean, Now, in logical log, the HUPDAT operation, would just record the
> updated bytes, with no primary key, and even the column data is not
> complete.
> Which I think the IDS logical log only record the necessary bytes.an
>
> I just want to know that if IDS has some kind of setting, for example, like
>
> Oracle, to force logical log records the primary key and the complete
> column data.
>
> BlackThought
>
> --f46d0407166358737004b24d3b30
>
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--000e0cd3ea08d72ed904b259956d
I think full row logging is used for UPDATE operation. if NOT enabled, CDC
wouldn't work.
On Wed, Nov 23, 2011 at 5:35 AM, FRANK <yunyaoqu@gmail.com> wrote:
> For some operations, it must do a full row logging, like, Insert or Delete.
> Otherwise, how can it redo Insert /undo Delete in a transaction?
> But, can we use onlog tool to see the full row image?
>
> Thanks,
> Frank
>
> On Tue, Nov 22, 2011 at 10:02 AM, Madison Pruet <mpruet@us.ibm.com> wrote:
>
> > Sorta.
> >
> > You can force a before/after image if you turn on full row logging. This
> > can be done by taking advantage of CDC calls. However if you do this you
> > must be prepared for a significant increase in the amount of logging that
> > is done.
> >
> > From: "Wang Shiyi" <osdbms@gmail.com>
> >
> > To: ids@iiug.org
> >
> > Date: 11/22/2011 12:52 AM
> >
> > Subject: Force logging primary key, and complete column.... [25449]
> >
> > Sent by: ids-bounces@iiug.org
> >
> > I wonder that does IDS has some kinds of setting, which would force it
> > logging the primary key and making column data completely.
> >
> > I mean, Now, in logical log, the HUPDAT operation, would just record the
> > updated bytes, with no primary key, and even the column data is not
> > complete.
> > Which I think the IDS logical log only record the necessary bytes.an
> >
> > I just want to know that if IDS has some kind of setting, for example,
> like
> >
> > Oracle, to force logical log records the primary key and the complete
> > column data.
> >
> > BlackThought
> >
> > --f46d0407166358737004b24d3b30
> >
> >
> >
> >
>
>
*******************************************************************************
> >
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
> >
> >
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --000e0cd3ea08d72ed904b259956d
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--f46d04339ee861ca5904b25c9f14
One of the functions/features of CDC is to turn on full row logging..
From: "Wang Shiyi" <osdbms@gmail.com>
To: ids@iiug.org
Date: 11/22/2011 07:13 PM
Subject: Re: Force logging primary key, and complete co.... [25456]
Sent by: ids-bounces@iiug.org
I think full row logging is used for UPDATE operation. if NOT enabled, CDC
wouldn't work.
On Wed, Nov 23, 2011 at 5:35 AM, FRANK <yunyaoqu@gmail.com> wrote:
> For some operations, it must do a full row logging, like, Insert or
Delete.
> Otherwise, how can it redo Insert /undo Delete in a transaction?
> But, can we use onlog tool to see the full row image?
>
> Thanks,
> Frank
>
> On Tue, Nov 22, 2011 at 10:02 AM, Madison Pruet <mpruet@us.ibm.com>
wrote:
>
> > Sorta.
> >
> > You can force a before/after image if you turn on full row logging.
This
> > can be done by taking advantage of CDC calls. However if you do this
you
> > must be prepared for a significant increase in the amount of logging
that
> > is done.
> >
> > From: "Wang Shiyi" <osdbms@gmail.com>
> >
> > To: ids@iiug.org
> >
> > Date: 11/22/2011 12:52 AM
> >
> > Subject: Force logging primary key, and complete column.... [25449]
> >
> > Sent by: ids-bounces@iiug.org
> >
> > I wonder that does IDS has some kinds of setting, which would force it
> > logging the primary key and making column data completely.
> >
> > I mean, Now, in logical log, the HUPDAT operation, would just record
the
> > updated bytes, with no primary key, and even the column data is not
> > complete.
> > Which I think the IDS logical log only record the necessary bytes.an
> >
> > I just want to know that if IDS has some kind of setting, for example,
> like
> >
> > Oracle, to force logical log records the primary key and the complete
> > column data.
> >
> > BlackThought
> >
> > --f46d0407166358737004b24d3b30
> >
> >
> >
> >
>
>
*******************************************************************************
> >
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
> >
> >
>
>
*******************************************************************************
> > Forum Note: Use "Reply" to post a response in the discussion forum.
> >
> >
>
> --000e0cd3ea08d72ed904b259956d
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--f46d04339ee861ca5904b25c9f14
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
I wonder if there is a IDS command to open "full row logging" instead of CDC command? On Tue, Nov 22, 2011 at 11:02 PM, Madison Pruet <mpruet@us.ibm.com> wrote: > Sorta. > > You can force a before/after image if you turn on full row logging. This > can be done by taking advantage of CDC calls. However if you do this you > must be prepared for a significant increase in the amount of logging that > is done. > > From: "Wang Shiyi" <osdbms@gmail.com> > > To: ids@iiug.org > > Date: 11/22/2011 12:52 AM > > Subject: Force logging primary key, and complete column.... [25449] > > Sent by: ids-bounces@iiug.org > > I wonder that does IDS has some kinds of setting, which would force it > logging the primary key and making column data completely. > > I mean, Now, in logical log, the HUPDAT operation, would just record the > updated bytes, with no primary key, and even the column data is not > complete. > Which I think the IDS logical log only record the necessary bytes.an > > I just want to know that if IDS has some kind of setting, for example, like > > Oracle, to force logical log records the primary key and the complete > column data. > > BlackThought > > --f46d0407166358737004b24d3b30 > > > > ******************************************************************************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --f46d040713d1fa269a04b4451a91
Do you know that in IDS 11+, UPDATE operation goes to "HUPBEF" and "HUPAFT" records, which is before/after image of the row, but in IDS 9.40 and 10.00, the Update statement in logical log is a "HUPDAT" record, which doesn't has enough information I heard there is a "full row logging" setting, do you know about it? On Tue, Nov 22, 2011 at 6:57 PM, Art Kagel <art.kagel@gmail.com> wrote: > No. > > Art > > Art S. Kagel > Advanced DataTools (www.advancedatatools.com) > Blog: http://informix-myview.blogspot.com/ > > Disclaimer: Please keep in mind that my own opinions are my own opinions > and do not reflect on my employer, Advanced DataTools, the IIUG, nor any > other organization with which I am associated either explicitly, > implicitly, or by inference. Neither do those opinions reflect those of > other individuals affiliated with any entity with which I am affiliated nor > those of the entities themselves. > > On Tue, Nov 22, 2011 at 1:51 AM, Wang Shiyi <osdbms@gmail.com> wrote: > > > I wonder that does IDS has some kinds of setting, which would force it > > logging the primary key and making column data completely. > > > > I mean, Now, in logical log, the HUPDAT operation, would just record the > > updated bytes, with no primary key, and even the column data is not > > complete. > > Which I think the IDS logical log only record the necessary bytes.an > > > > I just want to know that if IDS has some kind of setting, for example, > like > > Oracle, to force logical log records the primary key and the complete > > column data. > > > > BlackThought > > > > --f46d0407166358737004b24d3b30 > > > > > > > > > > ******************************************************************************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > > --e89a8f3ba4d3769aa304b250a9d0 > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --f46d04088e85a50c9704b4456869