Upgrep Fails With Error Value "Type Of Contact Empty0000000002. " Is Too Long

(Doc ID 2121357.1)

Last updated on JULY 12, 2017

Applies to:

Siebel CRM - Version 8.1.1.11 [IP2013] and later
Information in this document applies to any platform.

Symptoms

Following error message was observed during upgrep on non unicode db2 of solaris

DBCLog DBCLogError 1 0000000256d96e00:0 SQL Warning, SQL State 22001, -433, [IBM][CLI Driver][DB2/SUN64] SQL0433N Value "Type Of Contact Empty0000000002. " is too long. SQLSTATE=22001


Steps to reproduce:
--------------------
1. Installed 8.1.1.11 patch on top of existing 8.1.1.8 environment
2. Backed up Db and did pre-requisite step for running IRM
3. When running upgrep got an error in step upg_data_afterseed.sql after the seed import

Changes

 

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