[go: up one dir, main page]
Scribd
Upload
1K views2 pages

Production Support Issues

Common ETL production support issues include failed file transfers, incorrect source data formats, database deadlocks or servers going down, mapping parameter and variable errors when moving environments, mapping invalidation when moving test to production, and dependency errors between simultaneously running jobs. Providing daily production support, documentation, and status reports are also part of the role.

Uploaded by

Kalyan Chakravrthy
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
1K views2 pages

Production Support Issues

Common ETL production support issues include failed file transfers, incorrect source data formats, database deadlocks or servers going down, mapping parameter and variable errors when moving environments, mapping invalidation when moving test to production, and dependency errors between simultaneously running jobs. Providing daily production support, documentation, and status reports are also part of the role.

Uploaded by

Kalyan Chakravrthy
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Production Support Issues - Informatica

Posted by minnu at 4:50 AM

what are the ETL production support issues that one comes
across on a day to day basis.

• If you have a flat file as a source and it is ftped from other


systems.. at the time of ftp if it got failed then your jobs also fail.
• If source data is not correct means not in correct format.
• Database deadlock (One or more process accessing data at the
same time)
• Database server down
• Taking care of the Mapping parameter and mapping variable file
name
• While importing the Test Environment into Production some of
the Reusable
maps gets invalidate.
• Most issues come back to quality of
the design, quality of the code and complexity of the solution.
How
good were your test cases? Did you do peer code reviews? How
many
disparate systems are you pulling from? etc.
• Error due to dependency of jobs runnning simultaneously.
• Develop new or maintain existing Informatica mappings and
workflows based on specifications.
• Familiarity with administrative tasks within Informatica platform
such as stopping/starting Informatica Repository and Server
processes, performing code migration, backup and restore of
Informatica Repository, and security administration.
• Participate in cross-functional efforts to support other teams **
such as ETL and database tuning to support Business Objects
reporting performance.
• Sharing knowledge by effectively documenting work.
• Session Recovery Procedures.
• Ability to take ownership of projects and critical issues and to
drive those to successful resolution
• Provide daily production support of batches and system processes.
• Produce weekly status report and participate in team meetings
and conference calls with other region.
•

You might also like