DB2 Z/OS Damaged Table Sends error SQL1224N to Siebel and It Loops

(Doc ID 2116583.1)

Last updated on SEPTEMBER 22, 2017

Applies to:

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


Whenever there are tables or indexes corruption, Siebel task immediately loops . It occurs in any functionality.

 DB2 z/os sends errors SQL01224N and SQL30081 to Siebel , it occurs also with the standard srf and Siebel does not send a friendly message, but loops.

The issue can be reproduced at will with the following steps:

1. Cause a damage to a table. In this test the table damaged was S_CONTACT. The utility DSN1COPY can be used to cause the data set damage

2. Log in Siebel Fins Obj mgr

3. Siebel loops .


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