DbgtfRecWriteFailure: Max Write Recursion Depth, 10, Reached

(Doc ID 2207020.1)

Last updated on DECEMBER 16, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
Information in this document applies to any platform.

Symptoms

1. The following message is reported in the alert.log file of 12.1.0.2 database:
  

dbgtfRecWriteFailure: max write recursion depth, 10, reached

  

Check trace directory for a simple trace file created, which could show a failing function stack that contains dbgtfRecWriteFailure

dbgtfRecWriteFailur call kgdsdst()
000000000 ?
 000000000 ?

e()+3338
000000000 ?
 000000000 ?

 

3. Trace file also shows:

Error ORA-48127 signaled at ksedsts()+244<-ksf_short_stack()+85<-kge_snap_callstack()+72<-kge_sigtrace_dump()+69<-kgepop()+734<-kgesev()+424<-kgecxd()+160<-slgei()+24<-kgecss()+98<-dbgrfof_open_file()+561<-dbgrfosf_open_stream_file()+371<-dbgtfmGetSegMetaHeader()+174<-dbgtfdCheckTraceFileNameClash()+153<-dbgtfdFileWrite()+2726<-dbgtfdFileAccessCbk()+357<-dbgtfPutStr()+592<-dbktPri()+149<-ksdwri()+567<-kge_sigtrace_dump()+94<-kgepop()+734<-kgesev()+424<-kgecxd()+160<-slgei()+24<-kgecss()+98<-dbgrfof_open_file()+561<-dbgrfosf_open_stream_file()+371<-dbgtfmGetSegMetaHeader()+174<-dbgtfdCheckTraceFileNameClash()+153<-dbgtfdFileWrite()+2726<-dbgtfdFileAccessCbk()+357<-dbgtfPutStr()+592<-dbktPri()+149<-ksdwri()+567<-kge_sigtrace_dump()+94<-kgepop()+734<-kgesev()+424<-kgecxd()+160<-slgei()+24<-kgecss()+98<-dbgrfof_open_file()+561<-dbgrfosf_open_stream_file()+371<-dbgtfmGetSegMetaHeader()+174<-dbgtfdCheckTraceFileNameClash()+153<-dbgtfdFileWrite()+2726<-dbgtfdFileAccessCbk()+357<-dbgtfPutStr()+592<-dbktPri()+149<-ksdwri()+567<-kge_sigtrace_du

 

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