IRM fails with error "CREATE INDEX failed because the following SET options have incorrect settings: 'CONCAT_NULL_YIELDS_NULL, ANSI_WARNINGS'" (Doc ID 1619780.1)

Last updated on JULY 20, 2016

Applies to:

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

Symptoms

Environment
===========
8.1.1.11 SIA [23030]

Description
==========

During the upgrade to V8.1.1.11, you are encountering errors with UpgPhys process.

Errors
==========


reate nonclustered index S_CONTACT_F6_C1_X on S_CONTACT
("OWNER_PER_ID", "X_LAST_NAME_CI", "X_FST_NAME_CI", "PRIV_FLG")
on 'default'

2013-11-08 15:54:30 [Microsoft][SQL Server Native Client 10.0][SQL Server]CREATE INDEX failed because the following SET options have incorrect settings: 'CONCAT_NULL_YIELDS_NULL, ANSI_WARNINGS'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations.
2013-11-08 15:54:30
2013-11-08 15:54:30 37000: [Microsoft][SQL Server Native Client 10.0][SQL Server]CREATE INDEX failed because the following SET options have incorrect settings: 'CONCAT_NULL_YIELDS_NULL, ANSI_WARNINGS'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations.
2013-11-08 15:54:30 Dropping index with the same column signature and retrying...
2013-11-08 15:54:30 create nonclustered index S_CONTACT_F6_C1_X on S_CONTACT
2013-11-08 15:54:30 ("OWNER_PER_ID", "X_LAST_NAME_CI", "X_FST_NAME_CI", "PRIV_FLG")
2013-11-08 15:54:30 on 'default'
2013-11-08 15:54:30
2013-11-08 15:54:30 ;
2013-11-08 15:54:30 writeExecDDL error (pOperCallback UTLDbDdlOperIndCreate).
2013-11-08 15:54:30 Error in MainFunction (UTLDbDdlDbMerge).
2013-11-08 15:54:30 Error in Main function...
2013-11-08 15:54:30 (logapi.cpp (184) err=1 sys=0) SBL-GEN-00001: (logapi.cpp: 184) error code = 1, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null), msg4 = (null)

Impact
=====

Dev upgrade is halted.

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