ORA-01450: Maximum Key Length (6398) Exceeded Error When Catbundle.Sql Is Run

(Doc ID 1325010.1)

Last updated on MAY 27, 2011

Applies to:

Oracle Server - Enterprise Edition - Version: 11.2.0.2 to 11.2.0.2 - Release: 11.2 to 11.2
Oracle Exadata Hardware - Version: 11.2.0.2 to 11.2.0.2   [Release: 11.2 to 11.2]
Information in this document applies to any platform.

Symptoms

- When applying an Exadata DBM Bundle patch on a system where Data Vault is installed the catbundle script may fail.

- Check the contents of the following log file :

$ORACLE_HOME/cfgtoollogs/catbundle/catbundle_EXA_<DB
NAME>_APPLY_<DATE>.log


Check if it  contains an error like this in the 'Processing Data Vault' section :

SQL> PROMPT Processing Oracle Database Vault...
...
SQL> BEGIN
2 EXECUTE IMMEDIATE 'ALTER TABLE DVSYS."IDENTITY_MAP$"
3 ADD CONSTRAINT "IDENTITY_MAP_UK1" UNIQUE
4 (
5 IDENTITY_ID#
6 ,FACTOR_LINK_ID#
7 ,OPERATION_CODE_ID#
8 ,OPERAND1
9 ,OPERAND2
10 )
11 ENABLE'
12 ;
13 EXCEPTION
14 WHEN OTHERS THEN
15 IF SQLCODE IN ( -02260, -02261, -02275) THEN NULL;
16 --ignore primary key errors and referential constraint error
17 ELSE RAISE;
18 END IF;
19 END;
20 /
BEGIN
*
ERROR at line 1:
ORA-01450: maximum key length (6398) exceeded
ORA-06512: at line 17




Changes

Applying an Exadata Bundle Patch to a system with Data Vault installed.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms