Materialized View Created Between Different Characterset Database Using Substr Function May Have Incorrect Character Column Length
Last updated on SEPTEMBER 04, 2016
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11 [Release 12.1]
Information in this document applies to any platform.
Creating materialized view using substr function and between different multibyte characterset database, created materialized view can have smaller column length for character(CHAR,VARCHAR2) datatype than expected.
For example, consider db1 is JA16SJIS, db2 is AL32UTF8 characterset case, we will see following result
Due to this problem, create materialized view can fail with ORA-1406 because materialized view column length is short to put fetched data, and ORA-1723: zero-length columns are not allowed might be returned
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms