Quickly increasing trace files containing "FND_TRACE.START_TRACE", Causing Ora-48913
(Doc ID 1281069.1)
Last updated on FEBRUARY 02, 2022
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Goal
Many trace files are being generated by the database consuming large amount of space with contents similar to below, Is this normal?
PARSING IN CURSOR #2 len=33 dep=0 uid=44 oct=47 lid=44 tim=9902643598558 hv=1991901736 ad='52f5c57b0' sqlid='4g2612tvbn0j8'
begin FND_TRACE.START_TRACE; end;
END OF STMT
EXEC #2:c=0,e=15351,p=0,cr=0,cu=0,mis=0,r=1,dep=0,og=1,plh=0,tim=9902643598558
WAIT #2: nam='SQL*Net message to client' ela= 3 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=10140307045556
WAIT #2: nam='SQL*Net message from client' ela= 145 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=10140307045748
CLOSE #2:c=0,e=0,dep=0,type=1,tim=9902643598558
begin FND_TRACE.START_TRACE; end;
END OF STMT
EXEC #2:c=0,e=15351,p=0,cr=0,cu=0,mis=0,r=1,dep=0,og=1,plh=0,tim=9902643598558
WAIT #2: nam='SQL*Net message to client' ela= 3 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=10140307045556
WAIT #2: nam='SQL*Net message from client' ela= 145 driver id=1952673792 #bytes=1 p3=0 obj#=-1 tim=10140307045748
CLOSE #2:c=0,e=0,dep=0,type=1,tim=9902643598558
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |