At 08:58 PM 25/07/2006, you wrote:

> > I've looked around and the only mention of this I could find was in
> > 2003... looked to be a problem in 1.5RC3 - is it still an issue?
> > Have also done a backup & restore but the problem still occurs. The
> > only other thing I thought to check was the DB page size but they're
> > all the same.
> >
> >
> > Does anyone have any ideas?
>
>Hi, has nobody come across this before?
>
>It is really important that we have an answer to this; some time soon
>we will have to automatically alter some columns in customer databases
>(changing charset/collation) and since we have 100's of databases, we
>cannot have this error occuring.
>
>For the case above, I've scripted some SQL to drop the column and add
>a new one with the correct charset/collation at creation time. This
>all works. However this is not really a nice solution when we need to
>start updating multiple columns (which all have data)....

Umm, I thought about answering your original posting yesterday and
deferred, hoping someone else would...

You get an internal software consistency check when you've done
something to stuff up your database internally. Sometimes (as in
your case) you get some help to point to where you might start looking.

Sigh. You tried to rectify your design oversights by updating the
system tables. So now you have data stored that is inconsistent with
the metadata.

Now do you believe there's no quickfix for changing the character set
of your data?

>Any ideas how to avoid this gds error?

Yup. Don't meddle with the system tables.

./heLen

>Thanks
>Phil
>
>
>
>
>
>
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>Visit http://www.firebirdsql.org and click the Resources item
>on the main (top) menu. Try Knowledgebase and FAQ links !
>
>Also search the knowledgebases at http://www.ibphoenix.com
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>Yahoo! Groups Links
>
>
>
>