On the job overview page, monitor the status of data profiling tasks and retry profiling for tasks that complete with errors.
After you run a job that includes data profiling, you can monitor the status of the data profiling task and view the results on the job overview page. The results include statistics such as the number of discovered objects, profiled objects, skipped objects, and failed objects.
Data profiling tasks create the following subtasks:
•Bulk ingestion
•Task progress tracker
•Batch profiling
If a subtask completes with errors, retry profiling for the data profiling task. To retry profiling, hover the mouse over the data profiling parent task and click the Retry Task icon. When you retry, the job creates a new data profiling task that includes all failed objects from the batch profiling subtasks and runs the profile again with new batch profiling subtasks.
The number of batch profiling subtasks depends on the number of objects that need to be profiled and the maximum number of objects allowed in a batch profiling subtask. The maximum number of objects in a batch profiling subtask depends on the mps_maxDeploymentBatchSize property of the Metadata Platform Service configured for a Secure Agent.
You can view logs for the profiled objects, tasks, and subtasks on the Logs tab. After the data profiling task completes, you can view the results on the Results tab.
You can download logs to track failed profiling tasks. Click Failed Session Logs to download the logs. The ZIP file name represents the catalog source job ID. The catalog source job ID helps you identify the failed profiling task. You can also find the catalog source job ID from the URL of the Monitor tab as shown in the following image:
Extract the ZIP file. The extracted ZIP file contains multiple ZIP files based on the number of failed batch profiling tasks. Each ZIP file includes profiling session log files.
The following image shows the job Overview page for a data profiling task:
