🚀 go-pugleaf

It seems in this case:
while the fix is the same backup/restore
the problem is not the same.

I have been investigating and have found that
what Jeff and Bill are talking about is the
FORMATID value in the RDB$RELATIONS table.

None of these values in any of our systems is over 50.
Also no "Too many versions" exception message was generated.

All that happenned is that the MetaData was not actually created.
after a CREATE TABLE/CREATE PROCEDURE statement.

This happened in half of our systems at around the same time.

I am still very perplexed.

Regards,

Robert.


"Jeff Overcash (TeamB)" <jeffovercash@mindspring.com> wrote in message
news:41733CBC.70EC7E84@mindspring.com...
>
>
> Robert Gilland wrote:
> >
> > Let me clarify:
> >
> > How does this mean that all metadata updates fail, once a particular
> > Metadata has exceeded its limit.
> >
>
> You will get an error message of too many versions.
>
> -- 
> Jeff Overcash (TeamB)
>       (Please do not email me directly unless  asked. Thank You)
> A human being should be able to change a diaper, plan an invasion, butcher
> a hog, conn a ship, design a building, write a sonnet, balance accounts,
build
> a wall, set a bone, comfort the dying, take orders, give orders,
cooperate, act
> alone, solve equations, analyze a new problem, pitch manure, program a
computer,
> cook a tasty meal, fight efficiently, die gallantly.  Specialization is
for
> insects.   (RAH)