RE: ORA-01450: maximum key length (3215) exceeded -- Can't create index online with an nvarchar2 column

How did you conclude that the length of the C1 column in the iot was in 
characters and not in bytes?
If the nls_length_semantics is set to byte and no CHAR keyword was used when 
defining the column, then it should be defined in bytes.

Unless the nls_length_semantics is altered in the session itself, but this 
should show in the sql trace.


Kind regards,

Freek D'Hooge
Uptime
Oracle Database Administrator
email: freek.dhooge@xxxxxxxxx
tel +32(0)3 451 23 82
http://www.uptime.be
disclaimer: www.uptime.be/disclaimer
----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On 
Behalf Of Kudryk, Mark
Sent: maandag 29 augustus 2011 22:38
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: ORA-01450: maximum key length (3215) exceeded -- Can't create 
index online with an nvarchar2 column

select *
from nls_database_parameters
where parameter IN ('NLS_LENGTH_SEMANTICS','NLS_NCHAR_CHARACTERSET')

PARAMETER
VALUE
NLS_NCHAR_CHARACTERSET
UTF8
NLS_LENGTH_SEMANTICS
BYTE


From: David Fitzjarrell [mailto:oratune@xxxxxxxxx] 
Sent: Monday, August 29, 2011 2:31 PM
To: Kudryk, Mark (ES); oracle-l@xxxxxxxxxxxxx
Subject: Re: ORA-01450: maximum key length (3215) exceeded -- Can't create 
index online with an nvarchar2 column

Before you do check how NLS_LENGTH_SEMANTICS is set; it may be set for CHAR 
rather than BYTE.  If it's set correctly (BYTE) and this still occurs submit an 
SR.
 
David Fitzjarrell
--
http://www.freelists.org/webpage/oracle-l

Other related posts: