Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: ora-1450 even though max key length is well below the max
Anurag Varma wrote:
> Chuck wrote:
>> Gints Plivna wrote: >>>> Single byte character set on both databases - WE8ISO8859P1 >>> Yea but you said that error message gave you 3118. But looking at your >>> table definition -length of both varcahr2 columns together (2000 + >>> 2000) is more than 3118. >>> So at least the error message is completely justifiable. >>> >>> Gints Plivna >>> http://www.gplivna.eu/ >>> >> You can't determine key length by adding the max defined size of the >> columns. To determine key length you must query >> max(length(col1)+length(col2)...) + number of columns. >> >> See metalink note # 136158.1.
At carumba.
Does anyone around here read? I'll say it one last time... this works in a 9205 instance with the exact same DDL. If as you say it's based on the max defined width of the varchars how does this work on 9205?
desc mytable
Name Null? Type ----------------------------- -------- -------------------- LOGDATE NOT NULL DATE URI VARCHAR2(2000) REFERRER VARCHAR2(2000) PAGEVIEWS NUMBER(38)
CREATE UNIQUE INDEX MYINDEX_U1 ON MYTABLE
(LOGDATE, URI, REFERRER)
COMPRESS 2;
Index created.
Received on Thu Jun 22 2006 - 10:39:50 CDT