If you can't find the product or version you're looking for, visit support.ataccama.com/downloads

Scanner Output File Structure

Each scan generates a set of files that can be found in a so-called debug archive. These files include metadata information about the scan as well as log outputs. As such, they can help you troubleshoot if you encounter issues when running the scanner.

Understanding the debug archive directory structure

A debug archive contains the following:

File Description

File	Description
`exec_ folder`	Main folder with a unique name. The root folder of the whole execution.
`exec_ folder/job folder`	Each defined configuration is mapped into a job. Each job has a local subfolder containing intermediate files (as local file database for intermediate computations). This is where SQLite database files are located as well: `<jobName>.db` - Contains pre-export enriched lineage data. `internal.db` - Iinternal job database. `data_catalog.db` - Data catalog items identified during scanning.
`exec_ folder/assets.csv, flows.csv, connections.csv, transformations.csv, export.json`	Exported lineage files in Ataccama Lineage format as described in Ataccama Lineage Format.
`exec_ folder/exec_*.zip`	Zipped lineage files.
`exec_ folder/job_context.log`	Log file of the whole scanning run. If issues occur during scanning, refer to this file for detailed logs that provide insights into the scanning processes, configurations, and potential errors.
`definition.json`	JSON definition used to execute this scan.
`console-err.log`	Internal use.
`command.txt`	Internal use.
`console-out.log`	Internal use.
`logs`	Folder containing additional log files.

exec_ folder

Main folder with a unique name. The root folder of the whole execution.

exec_ folder/job folder

Each defined configuration is mapped into a job. Each job has a local subfolder containing intermediate files (as local file database for intermediate computations).

This is where SQLite database files are located as well:

<jobName>.db - Contains pre-export enriched lineage data.
internal.db - Iinternal job database.
data_catalog.db - Data catalog items identified during scanning.

exec_ folder/assets.csv, flows.csv, connections.csv, transformations.csv, export.json

Exported lineage files in Ataccama Lineage format as described in Ataccama Lineage Format.

exec_ folder/exec_*.zip

Zipped lineage files.

exec_ folder/job_context.log

Log file of the whole scanning run.

If issues occur during scanning, refer to this file for detailed logs that provide insights into the scanning processes, configurations, and potential errors.

definition.json

JSON definition used to execute this scan.

console-err.log

Internal use.

command.txt

Internal use.

console-out.log

Internal use.

logs

Folder containing additional log files.

Was this page useful?