kksfbc Clear parse

如果在udump/bdump目录下trace中找到

 

kksfbc : Clear parse Err=44201 xsc=1105fddf0 chd=0 clk=0 400020 40000000 20a2000

kksfbc : Clear parse Err=44201 xsc=1113ad1f8 chd=0 clk=0 400020 40000000 20a2000

的相关信息，一般是可以忽略的。

 

kksfbc是解析parse 过程中的重要函数，其作用在于find bound cursor、并返回一个合适的子游标， 而相关的内核函数kkspfx则用于pin cursor以便执行。

 

kksfbc – Find Bound Cursor – creation of a new child cursor

 

Oracle 中硬解析(Hard Parse)构造子游标 build child cursor的典型stack call:

opitca()<-kksFullTypeCheck()<-rpiswu2()<-kksLoadChild()<-kkslod()<-kglobld()<-kglobpn()<-kglpim()<-kglpin()<-kxsRuntimeLock()<-kksfbc()<-kkspsc0()<-kksParseCursor()<-opiosq0()<-kpooprx()<kpoal8()<-opiodr()<-ttcpip()<-opitsk()<-opiino()<-opiodr()<-opidrv()<-sou2o()<-opimai_real()<-main()

 

软解析找寻一个合适子游标的典型stack call:

kksSearchChildList ()<-kksfbc()<-kkspsc0()<-kksParseCursor()<-opiosq0()<-kpooprx()<kpoal8()<-opiodr()<-ttcpip()<-opitsk()<-opiino()<-opiodr()<-opidrv()<-sou2o()<-opimai_real()<-main()

 

执行时找到一个合适子游标的典型stack call:

kksSearchChildList()<-kksfbc()<-opiexe ()<-kpoal8 ()<-opiodr ()<-ttcpip ()<-opitsk ()<-opiino ()<-opiodr ()<-opidrv ()<-sou2o ()<-opimai_real main ()

 

 

 

 

	
Continously Receiving "Kksfbc : Clear Parse Err=44201" In Bdump Tracefiles (Doc ID 748940.1)
Modified01-MAR-2013TypePROBLEMStatusMODERATED(EXTERNAL)Priority3To Bottom
In this Document
  Symptoms
  Cause
  Solution
  References

Platforms: 1-914CU;

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.3 and later   [Release: 10.2 and later ]
Information in this document applies to any platform.
Symptoms

-- Problem Statement:
On 10.2.0.3 in Production:
we are getting many trace files generated in bdump with the following message :

ERROR
kksfbc : Clear parse Err=44201 xsc=800003ffbfc3d678 chd=0000000000000000 clk=0000000000000000
400020 0 22080

Cause

This issue due to Bug 5397402 "KKSFBC : CLEAR PARSE ERR=44201 XSC=0XB5F48550 CHD=(NIL) CLK=(NIL)

Diagnostic output may be written to the session's trace file under some conditions. The extraneous
trace looks like this:

kksfbc : Clear parse Err=44201 xsc=800003ffbfc3d678 chd=0000000000000000 clk=0000000000000000 400020 0 22080

Solution

-- To implement the solution, please execute the following steps::

1) Apply Patch 5397402 

Or

2) Apply the 10.2.0.5 patchset.

Also you can safely ignore the generated trace files.
References

BUG:5397402 - KKSFBC : CLEAR PARSE ERR=44201 XSC=0XB5F48550 CHD=(NIL) CLK=(NIL) IN TRACES