DBA Data[Home] [Help] [Dependency Information]

TABLE: APPLSYS.FND_TRACE_LOG

Object Details
Object Name: FND_TRACE_LOG
Object Type: TABLE
Owner: APPLSYS
FND Design Data: TableFND.FND_TRACE_LOG
Subobject Name:
Status: VALID


FND_TRACE_LOG is populated by FND_CTL if the LOG_MODE is set. This is normally used for testing of Cost-Based-Optimization. This table can be purged from time-to-time. This should not be used for user_tracing.
.
By using the profile option "Initialization SQL Statement - Custom" and the package FND_CTL , the behavior of the optimizer and statistics can be controlled at the user/responsibility/application level . If LOG_MODE is set to "on" , FND_TRACE_LOG will be populated. Normally, this should be used during the testing phase only. In a production environment it should not be used and the LOG_MODE of FND_CTL should not be set.
.


Storage Details
Tablespace: TablespaceAPPS_TS_ARCHIVE
PCT Free: 10
PCT Used:
Columns
Name Datatype Length Mandatory Comments
USERNAME VARCHAR2 (30)
Application username
TIMESTAMP DATE

Timestamp of when user logged on
OUTPUT_CONC_REQUEST_ID NUMBER (15)
Concurrent request ID
OLTP_OPT_MODE VARCHAR2 (10)
OLTP optimizer mode
CONC_OPT_MODE VARCHAR2 (10)
Concurrent optmizer mode
CONC_PROGRAM_NAME VARCHAR2 (30)
Concurrent program name
USER_CONC_PROGRAM_NAME VARCHAR2 (240)
User concurrent program name
RESP_NAME VARCHAR2 (100)
Responsibility name
APPLICATION_SHORT_NAME VARCHAR2 (50)
Application short name
Query Text

Cut, paste (and edit) the following text to query this object:


SELECT USERNAME
,      TIMESTAMP
,      OUTPUT_CONC_REQUEST_ID
,      OLTP_OPT_MODE
,      CONC_OPT_MODE
,      CONC_PROGRAM_NAME
,      USER_CONC_PROGRAM_NAME
,      RESP_NAME
,      APPLICATION_SHORT_NAME
FROM APPLSYS.FND_TRACE_LOG;

Dependencies

[top of page]

APPLSYS.FND_TRACE_LOG does not reference any database object

APPLSYS.FND_TRACE_LOG is referenced by following:

SchemaAPPLSYS
ViewFND_TRACE_LOG#