--- In firebird-support@yahoogroups.com, Adriano dos Santos
Fernandes <adrianosf@...> wrote:

>
> skoczian escreveu:
> >> Please do a ldd fbserver (for Super) or libfbembed (for

Classic)

> > to see
> >> dependencies.
> >>
> > sib@Elend ~ $ ldd /usr/bin/fbserver
> > linux-gate.so.1 => (0xffffe000)
> > libdl.so.2 => /lib/libdl.so.2 (0xb7f77000)
> > libncurses.so.5 => /lib/libncurses.so.5 (0xb7f33000)
> > libicuuc.so.38 => /usr/lib/libicuuc.so.38 (0xb7e13000)
> > libicudata.so.38 => /usr/lib/libicudata.so.38

(0xb733c000)

> > libicui18n.so.38 => /usr/lib/libicui18n.so.38

(0xb71e0000)

> > libstdc++.so.6
> > => /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libstdc++.so.6

(0xb70f6000)

> > libm.so.6 => /lib/libm.so.6 (0xb70d0000)
> > libgcc_s.so.1
> > => /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgcc_s.so.1

(0xb70c4000)

> > libpthread.so.0 => /lib/libpthread.so.0 (0xb70ad000)
> > libc.so.6 => /lib/libc.so.6 (0xb6f7d000)
> > /lib/ld-linux.so.2 (0xb7f93000)
> >
> >
> > Does this help?
> >
> Yes. We link with ICU 3.0, but they use 3.8. This creates

incompatible

> databases (due to different keys in indexes).
>
> Have you created this database on this server? Could you create a

new

> one and see if it works?
>

I'm not absolutely sure, but I think I created the database from
metadata extracted from another database under Windows. Very
probably before updating from Firebird 2.1 to 2.1.1, possibly even
before the upgrade to 2.1. So - not really on this server.

With a newly created database the collate clause was accepted.

> Also please see result of this command on both databases:
> select rdb$specific_attributes from rdb$collations where
> rdb$collation_name = 'UNICODE';
>

Sorry, forgot to do it before doing a backup and restore of the
problematic database. In the new database I get:

SQL> select rdb$specific_attributes from rdb$collations where
rdb$collation_name = 'UNICODE';

RDB$SPECIFIC_ATTRIBUTES
=======================
0:3
==============================================================================
RDB$SPECIFIC_ATTRIBUTES:
COLL-VERSION=49.192.5.5
==============================================================================

> If it works in the new database, you'll need to backup and restore

the

> problematic one.
>

Done and helped. This is a very small experimental database, so
backup and restore was a matter of minutes.

I suppose I should have done the backup before updating the server,
and a restore afterwards, right? Did so with my production
databases - but they use ISO8859_1 anyway.

Found a problem with ISQL and UTF8, but will post that separately.

Many thanks for your help!
Herta