CUST_ADDR AND KDD_CASE_CUST_ADDR TABLE COLUMN DIFFERENCE (Doc ID 2792279.1)

Last updated on JULY 21, 2021

Applies to:

Symptoms

There is a table column length issue in CUST_ADDR and kdd_case_cust_addr.
Columns of Cust address has length defined as below
ADDR_STRT_LINE1_TX VARCHAR2(255 CHAR)
ADDR_STRT_LINE2_TX VARCHAR2(255 CHAR)
ADDR_STRT_LINE3_TX VARCHAR2(255 CHAR)
ADDR_STRT_LINE4_TX VARCHAR2(255 CHAR)
ADDR_STRT_LINE5_TX VARCHAR2(255 CHAR)
ADDR_STRT_LINE6_TX VARCHAR2(255 CHAR)

In 804 version, KDD_CASE_CUST_ADDR has below length for address fields:

ADDR_STRT_LINE1_TX VARCHAR2(60 CHAR)
ADDR_STRT_LINE2_TX VARCHAR2(60 CHAR)
ADDR_STRT_LINE3_TX VARCHAR2(60 CHAR)
ADDR_STRT_LINE4_TX VARCHAR2(60 CHAR)
ADDR_STRT_LINE5_TX VARCHAR2(60 CHAR)
ADDR_STRT_LINE6_TX VARCHAR2(60 CHAR)

Due to this difference once system is trying to promote alerts in cases we are getting length error, please let us know why there is a difference in structure logically both tables should be identical.

Below error we are getting in kdd_logs_msgs table.

21-AUG-19 Error occured in stage - 1340 - ErrorCode - ORA-12899: value too large for column "OFSAAFCCM"."KDD_CASE_CUST_ADDRS"."ADDR_STRT_LINE1_TX" (actual: 84, maximum: 60) PROMOTE TO CASE
21-AUG-19 Error occured in stage - 1340 - ErrorCode - ORA-12899: value too large for column "OFSAAFCCM"."KDD_CASE_CUST_ADDRS"."ADDR_STRT_LINE1_TX" (actual: 77, maximum: 60) PROMOTE TO CASE
21-AUG-19 Error occured in stage - 1340 - ErrorCode - ORA-12899: value too large for column "OFSAAFCCM"."KDD_CASE_CUST_ADDRS"."ADDR_STRT_LINE1_TX" (actual: 73, maximum: 60) PROMOTE TO CASE

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.