Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Bolo.
Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Ingestion and Replication
  • All Products

Table of Contents

Search

  1. Introducing Mass Ingestion
  2. Getting Started with Mass Ingestion
  3. Connectors and Connections
  4. Mass Ingestion Applications
  5. Mass Ingestion Databases
  6. Mass Ingestion Files
  7. Mass Ingestion Streaming
  8. Monitoring Mass Ingestion Jobs
  9. Asset Management
  10. Troubleshooting

Mass Ingestion

Mass Ingestion

Back Next

File ingestion job details

File ingestion
 job details

The job results for each
file ingestion
 task instance display the status of the job, and success and error statistics.
To view detailed information about a
file ingestion
 task, click the task name on the
My Jobs
 page in
Mass Ingestion
 or on the
All Jobs
 tab of the
Mass Ingestion
 page in both the
Monitor
 and
Operational Insights
 services.
You can download the job. The following image shows the details of a
file ingestion
 job:
Job details of file ingestion jobs

Job Properties

The job properties for the
file ingestion
 task instance display general properties about the instance.
The following table describes the job properties:
Property
Description
Task Name
The name of the associated ingestion task. You can click the task-name link to view or edit task details in Mass Ingestion.
Task Type
Task type. In this case,
file ingestion
 task.
Started By
Name of the user or schedule that started the job.
Start Time
Date and time when the job was started.
End Time
Date and time when the job completed or stopped.
Duration
The amount of time the job ran before it completed or was stopped.

Results

The job results for the
file ingestion
 task instance display the status of the job and error statistics.
The job results include the following properties:
Property
Description
State
Job status. A job can have one of the following statuses:
  • Running
    . The job is still running.
  • Success
    . The job completed successfully.
  • Failed
    . The job did not complete because it encountered errors
  • Aborted
    . The job was aborted.
Session Log
Allows you to download the session log file. By default, Informatica Intelligent Cloud Services stores session logs for 10 runs before it overwrites the logs with the latest runs. If you need the session logs for earlier runs, take a backup of the directory that holds the session log files.
Session log files are written to the following directory:
<Secure Agent installation directory>/apps/Data_Integration_Server/logs
Success Files
Number of files that are successfully transferred, downloaded, and uploaded to the target.
Error Files
Number of files that were not transferred to the target.
Duplicate Files
Number of files that were identified as duplicates.
Error Message
Error message, if any, that is associated with the job.

File Events

This section shows the total number of files that the
file ingestion
 task has transferred with information about each file.
The File Events section is updated each time the
file ingestion
 task transfers a file, and the state of the file updates throughout the file transfer process. You can track the progress of a file transfer based on the state of the file.
The File Events section displays the following properties for each file:
Property
Description
Name
The name of the file.
File size
The size of the file in bytes.
Status
The status of the file transfer. A file can have one of the following status:
  • Success
    . The file transfer completed successfully.
  • Failed
    . The file transfer did not complete because it encountered errors.
  • Processing
    . The file transfer is still running.
  • Duplicate
    . The task previously transferred a file with the same name, directory location, and size.
  • Interrupted
    . The file transfer is interrupted because of network issues or changed server credentials during the file transfer. Run the
    file ingestion
     job to resume the transfer of the interrupted files. This status is applicable when the
    file ingestion
     task transfers file from the advanced FTP, advanced SFTP, or advanced FTPS sources.
  • In Doubt
    . The previous task instance encountered errors while transferring the file. Applicable for tasks where the source is configured to skip duplicate files.
  • Quarantined
    . The task marks any infected file it detects from a source as quarantined.
You can monitor the Status property to track the progress of the file transfer of each file.
Transfer Type
The type of file transfer. A file can have one of the following transfer types:
  • <source_name>
    Download. The file is downloaded from source.
    <source_name>
     is the name of the source.
  • <target_name>
    Upload. The file is uploaded to the target.
    <target_name>
     is the name of the target.
  • Copy from Source. The
    file ingestion
     task is performing file processing actions.
  • Copy to Target. The file is transferred from a local directory to a local directory.
Start time
Date and time when the file transfer started.
Duration
The length of time to transfer the file, in milliseconds.
Remarks
Applies to file events in Failed status. The message includes the reason for failure of the event based on the file transfer type.
0 COMMENTS
We’d like to hear from you!