Siebel Upgrade From Version 15.5 To 23.* And Later Fails With Error, "ORA-01450: Maximum Key Length (6398) Exceeded"
(Doc ID 2942227.1)
Last updated on MAY 09, 2023
Applies to:
Siebel CRM - Version 15.5 [IP2015] and laterInformation in this document applies to any platform.
Symptoms
When running Siebel upgrade from version 15.5 to version 23.1 an index cannot be created and in "ddlctl_indx1.log" file the following error occurs:
ERROR
-----------------------
create unique index CX_CAMPAIGN_U1 on CX_CAMPAIGN
("PAR_ROW_ID", "TYPE", "NAME", "CONFLICT_ID")
tablespace SIEBEL_INDX_TBLSPACE_16K
DBCLog DBCLogError 1 0000000264234058:0 2023-03-28 21:55:51 [Oracle][ODBC][Ora]ORA-01450: maximum key length (6398) exceeded
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 S1000: [Oracle][ODBC][Ora]ORA-01450: maximum key length (6398) exceeded
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 Dropping index with the same column signature and retrying...
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 create unique index CX_CAMPAIGN_U1 on CX_CAMPAIGN
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 ("PAR_ROW_ID", "TYPE", "NAME", "CONFLICT_ID")
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 tablespace SIEBEL_INDX_TBLSPACE_16K
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 ;
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 writeExecDDL error (pOperCallback UTLDbDdlOperIndCreate).
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 Error in MainFunction (UTLDbDdlDbMerge).
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 Error in Main function...
GenericLog GenericError 1 0000000264234058:0 2023-03-28 21:55:52 (logapi.cpp (184) err=1 sys=2) : (logapi.cpp: 184) error code = 1, system error = 2, msg1 = (null), msg2 = (null), msg3 = (null), msg4 = (null)
-----------------------
create unique index CX_CAMPAIGN_U1 on CX_CAMPAIGN
("PAR_ROW_ID", "TYPE", "NAME", "CONFLICT_ID")
tablespace SIEBEL_INDX_TBLSPACE_16K
DBCLog DBCLogError 1 0000000264234058:0 2023-03-28 21:55:51 [Oracle][ODBC][Ora]ORA-01450: maximum key length (6398) exceeded
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 S1000: [Oracle][ODBC][Ora]ORA-01450: maximum key length (6398) exceeded
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 Dropping index with the same column signature and retrying...
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 create unique index CX_CAMPAIGN_U1 on CX_CAMPAIGN
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 ("PAR_ROW_ID", "TYPE", "NAME", "CONFLICT_ID")
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 tablespace SIEBEL_INDX_TBLSPACE_16K
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 ;
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 writeExecDDL error (pOperCallback UTLDbDdlOperIndCreate).
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 Error in MainFunction (UTLDbDdlDbMerge).
SQLDBUtilityLog SQLDBUtilityLog 3 0000000264234058:0 2023-03-28 21:55:51 Error in Main function...
GenericLog GenericError 1 0000000264234058:0 2023-03-28 21:55:52 (logapi.cpp (184) err=1 sys=2) : (logapi.cpp: 184) error code = 1, system error = 2, msg1 = (null), msg2 = (null), msg3 = (null), msg4 = (null)
The issue can be reproduced as follows:
- In Siebel version 15.5 keep default values for tablespace index.
- Start to perform Siebel upgrade to version 23.1.
- Check if during upgrade process "unique index" can be created.
Before to start Siebel upgrade database tablespace limit was not adjusted.
Changes
Siebel environment was upgraded from version 15.5 to version 23.1.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |