Create Materialized View May Fail with ORA-972 if PK Constraint Name Contains Multibyte Character
Last updated on MAY 24, 2017
Applies to:Oracle Database - Standard Edition - Version 18.104.22.168 and later
Information in this document applies to any platform.
Create materialized view with primary key sometimes fails with ORA-972 when master table primary key constraint name includes multibyte character.
Even this problem happen, retry sometimes finishes successfully.
In above example, JA16SJIS characterset is used, and 130,98 represents to_multibyte('C').
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