Re: Change charset of database

From: Norman Dunbar <Norman.Dunbar_at_lfs.co.uk>
Date: Mon, 10 Jun 2002 10:09:07 +0100
Message-ID: <E2F6A70FE45242488C865C3BC1245DA702365644@lnewton.leeds.lfs.co.uk>

Morning Howard,

I only put 'bytes' to make sure that there was no mis-understanding in thinking that 2000 bytes was 2000 charcters in UTF8 (or not UTF8) charsets. But, you are correct (as ever).

As for whether it is a bug or not, Oracle seem to think so. See bug 1400539 as this is exactly what we are hitting on UTF8 server and non UTF8 client setups. We are hitting ORA-01461 and ORA-01026 errors.

Regards,
Norman.

Norman Dunbar
Database/Unix administrator
Lynx Financial Systems Ltd.
mailto:Norman.Dunbar_at_LFS.co.uk

Tel: 0113 289 6265
Fax: 0113 289 3146
URL: http://www.Lynx-FS.com


-------------------------------------

-----Original Message-----
From: Howard J. Rogers [mailto:dba_at_hjrdba.com] Posted At: Sunday, June 09, 2002 10:19 PM Posted To: server
Conversation: Change charset of database Subject: Re: Change charset of database

Well, Oracle has always used byte semantics, not character ones. Create table blah (col1 char(5)) means that column 1 will be 5 bytes long -and has
always meant that so far as I'm aware.

In 9i, you get the chance to specify "...col1 char(5) byte" or "...col1 char(5) char", so now it's explicit, though byte is still the default. So I
would have thought that the first 'bug' you report isn't a bug at all.

Regards
HJR Received on Mon Jun 10 2002 - 04:09:07 CDT