My Oracle Support Banner

Siebel Merge or Delta Merge Fails With "Unable to connect to the database" And "ORA-24345: A Truncation or null fetch error occurred" In The MERGE Log (Doc ID 1073581.1)

Last updated on SEPTEMBER 14, 2020

Applies to:

Siebel CRM - Version 8.1.1 [21112] and later
Information in this document applies to any platform.
***Checked for Currency 10-SEP-2020***

Symptoms

Siebel merge or delta merge fails with:

!!ERROR::SBL-DEV-62158: MergeType. Type - Type - exiting with error Error retrieving next record from the database.(SBL-DBC-00104)--
ORA-24345: A Truncation or null fetch error occurred

Siebel Tools Pop-up error is displayed: "Unable to connect to the database".

The error affects Siebel upgrades or IRM processes executed on Oracle RDBMS 11.2.0.1 platforms specifically. Or if you are running a Siebel upgrade or IRM process pointing to a higher Oracle RDBMS version but using the _add_col_optim_enabled hidden parameter TRUE setting.

 

Changes

With Oracle RDBMS 11.2, the default value for the _add_col_optim_enabled hidden parameter is TRUE. This affects ALTER TABLE commands that add a column with a default value specified. When the ALTER TABLE .. ADD .. DEFAULT commands are executed as part of the Siebel upgrade database schema process (upgrep) and the RDBMS hidden parameter is enabled (TRUE) we will execute SQL to set the new column to the default value via an UPDATE command.

The following RDBMS article describes in detail the impact of the _add_col_optim_enabled hidden RDBMS parameter: (Doc 1492674.1)

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


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