| Subject | RE: [firebird-support] Not your typical 'gds software consistency check (284)' |
|---|---|
| Author | Bob Murdoch |
| Post date | 2009-05-12T13:10:26Z |
Dmitry,
-----Original Message-----
Sibiryakov
As for the "fix metadata character set" - this database has never had
any operation performed with a specific character set, so that thought
has never occurred to me. Even then, how is it that the procedure
worked for a week after the 1.5 -> 2.1 conversion without issue?
I did run the rdb$fix_metadata procedure but with updates commented
out. There were quite a number of returned rows from this procedure.
Does that mean that each of these represents a ticking time bomb?
I did not try the 2.1.3 snapshot for two reasons - I cannot find it,
and this is a production database of 50GB so it is not a simple matter
of moving it for testing.
Bob M..
-----Original Message-----
> From: firebird-support@yahoogroups.com[mailto:firebird-support@yahoogroups.com] On Behalf Of Dimitry
Sibiryakov
> Sent: Monday, May 11, 2009 4:58 PMThank you for the response.
> To: firebird-support@yahoogroups.com
>
> Did you pass through "fix metadata character set" procedure as
> described in installation manual?
> Did you try 2.1.3 snapshot?
As for the "fix metadata character set" - this database has never had
any operation performed with a specific character set, so that thought
has never occurred to me. Even then, how is it that the procedure
worked for a week after the 1.5 -> 2.1 conversion without issue?
I did run the rdb$fix_metadata procedure but with updates commented
out. There were quite a number of returned rows from this procedure.
Does that mean that each of these represents a ticking time bomb?
I did not try the 2.1.3 snapshot for two reasons - I cannot find it,
and this is a production database of 50GB so it is not a simple matter
of moving it for testing.
Bob M..