Subject | 2.0 to 2.1 |
---|---|
Author | Mentek |
Post date | 2011-05-16T07:06:24Z |
Hi to all
I've upgraded a 2.0 database to 2.1 and encounter a problem of
transliterating.
In release notes i've found this:
Fixing the metadata
To fix the metadata, you need to know in what character set the objects were
created. The upgrade script will work correctly only if all your metadata
was created using the same character set.
[1] isql /path/to/your/database.fdb
[2] SQL> input
'$fbroot$/misc/upgrade/metatdata/metadata_charset_create.sql';
[3] SQL> select * from rdb$fix_metadata('WIN1252'); -- replace WIN1252 by
your charset
[4] SQL> commit;
- Where can i find the character set with which 2.0 database was created
- and what to do if all metadata wasn't created in same character set ??
Any help will be appreciated
Bogdan
I've upgraded a 2.0 database to 2.1 and encounter a problem of
transliterating.
In release notes i've found this:
Fixing the metadata
To fix the metadata, you need to know in what character set the objects were
created. The upgrade script will work correctly only if all your metadata
was created using the same character set.
[1] isql /path/to/your/database.fdb
[2] SQL> input
'$fbroot$/misc/upgrade/metatdata/metadata_charset_create.sql';
[3] SQL> select * from rdb$fix_metadata('WIN1252'); -- replace WIN1252 by
your charset
[4] SQL> commit;
- Where can i find the character set with which 2.0 database was created
- and what to do if all metadata wasn't created in same character set ??
Any help will be appreciated
Bogdan