# Striim 3.10.2 documentation

#### File lineage in Oracle

See Console commands for instructions on using SHOW LINEAGE. The file lineage report is also available in the Flow Designer and via the getOracleFLM endpoint in the Striim application management REST API (see Using the Striim Application Management REST API).

By default, this feature is disabled. See Enabling file lineage.

For OracleReader, the file lineage data includes:

 File Name the archive log file name, for example, /oracle_archivelogs/1_4009_890952357.dbf (the NAME value taken from V$ARCHIVED_LOG based on log sequence number and thread number) or ONLINE REDO when OracleReader is reading from redo logs Status PROCESSING when OracleReader is reading the file, COMPLETED when it has finished Directory Name the directory in which the file is located File Creation Time the time Striim created the file lineage entry for the file Number Of Events the number of events OracleReader has read from the file; if the application has been restarted, OracleReader may not start reading from the first event, so the number will be less than the total number of events in the file First Event Timestamp FIRST_TIME value taken from V$ARCHIVED_LOG based on log sequence number and thread number Last Event Timestamp NEXT_TIME for the file taken from V$ARCHIVED_LOG based on log sequence number and thread number Wrap Number the number of times OracleReader resumed reading the file after the application was restarted SequenceNumber the unique sequence number from the file name, for example, for /oracle_archivelogs/1_4009_890952357.dbf it would be 4009 ThreadID the thread number associated with the log sequence number and file name FirstChangeNumber FIRST_CHANGE# for the file taken from V$ARCHIVED_LOG based on log sequence number and thread number LastChangeNumber NEXT_CHANGE# for the file taken from V\$ARCHIVED_LOG based on log sequence number and thread number

When OracleReader is reading from redo logs, file-related values are NOT APPLICABLE or N/A.