kksfbc child completion

Database Hung With "kksfbc child completion" and "Cursor: Pin X" Waits (Doc ID 430555.1)

 

 

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.3 - Release: 10.2 to 10.2
Information in this document applies to any platform.

Symptoms

Database hung along with high CPU utilization with "kksfbc child completion"  and "cursor:pin X' waits in Top 5 Events.  Also system state dump gets generated automatically

 

Cause:

Execution of DDL against a partitioned object which has a object-based column (CLOB in this particular case) could result in sessions blocking on the 'cursor: pin X' and 'kksfbc child completion' wait events.

This is due to Bug 5500044 (Bug 5217203 is closed as duplicate)

Bug 5217203 - SYSTEM STATES DUMPED TO TRACE FILE MESSAGES IN ALERT.LOG

Bug 5500044 - ORA-44203 ON TABLE_X_X CHILD FROM CONCURRENT LOB APPEND AND DROP PARTITION


To be seeing this problem under 10.2 then you are likely to need to see the following:

1) DDL on a partitioned table
2)Sessions block on 'cursor: pin X' and 'kksfbc child completion'
3)The 'cursor: pin X' is waiting on a pseudo cursor (a cursor with a name that starts with "table_")
4)The partitioned table has an object column (LOB, CLOB etc)

 

SOLUTION:

 

Please download and apply patch 5500044 for your platform.This bug has been fixed in 10.2.0.4 and 11g. In case the patch is not available for your platform, then raise a service request with Oracle support for requesting the same

Also workaround for this bug is to avoid executing DDL on partitioned tables with object column when there are other sessions that may be concurrently executing DML against the partitioned table.