dbTalk Databases Forums  

Illegal record type during rollforward

comp.databases.ingres comp.databases.ingres


Discuss Illegal record type during rollforward in the comp.databases.ingres forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Roy Hann
 
Posts: n/a

Default Illegal record type during rollforward - 05-06-2009 , 12:33 PM






I have just been shown a log of a rollforward on a 2.6 system that had
just been patched. The log showed 8 warnings about "Illegal Record Type
159".

What might that be?

Personally I always assume a patch invalidates existing journals and
checkpoints but this group is more bold than I am.

In fairness, the log also claims the rollforward completed successfully.
--
Roy

UK Ingres User Association Conference 2009 will be on Tuesday June 9, 2009
Go to http://www.iua.org.uk/join to get on the mailing list.



Reply With Quote
  #2  
Old   
Karl & Betty Schendel
 
Posts: n/a

Default Re: [Info-Ingres] Illegal record type during rollforward - 05-06-2009 , 12:46 PM







On May 6, 2009, at 1:33 PM, Roy Hann wrote:

Quote:
I have just been shown a log of a rollforward on a 2.6 system that had
just been patched. The log showed 8 warnings about "Illegal Record
Type
159".

What might that be?
According to the current dm0l.h, it's "BTPUTOLD" and commented
to be "INVALID due to b109936".

Comment history says "child on DMPP_INDEX may be > 512, so it must be
logged separately in DM0L_BTPUT, DM0L_BTDEL records". The change
is old enough to plausibly be part of a 2.6 patch.

ie new jnl record types were created to correct a deficiency
in the structure.

BTPUT is put into a btree index.

Karl



Reply With Quote
  #3  
Old   
Roy Hann
 
Posts: n/a

Default Re: [Info-Ingres] Illegal record type during rollforward - 05-06-2009 , 01:30 PM



Karl & Betty Schendel wrote:

Quote:
On May 6, 2009, at 1:33 PM, Roy Hann wrote:

I have just been shown a log of a rollforward on a 2.6 system that had
just been patched. The log showed 8 warnings about "Illegal Record
Type
159".

What might that be?

According to the current dm0l.h, it's "BTPUTOLD" and commented
to be "INVALID due to b109936".

Comment history says "child on DMPP_INDEX may be > 512, so it must be
logged separately in DM0L_BTPUT, DM0L_BTDEL records". The change
is old enough to plausibly be part of a 2.6 patch.

ie new jnl record types were created to correct a deficiency
in the structure.

BTPUT is put into a btree index.
Obliged. As ever.

--
Roy

UK Ingres User Association Conference 2009 will be on Tuesday June 9, 2009
Go to http://www.iua.org.uk/join to get on the mailing list.




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.