Friday, 2 November 2012

TYPES OF METADATA THAT IS STORED IN INFORMAITCA


Following are the types of metadata that is stored in the Informatica repository
  • Database connections
  • Global objects
  • Mappings
  • Mapplets
  • Multidimensional metadata
  • Reusable transformations
  • Sessions and batches
  • Short cuts
  • Source definitions
  • Target definitions
  • Transformations

Difference between OLTP and DWH


OLTP system is basically application orientation (eg, purchase order it is functionality of an application) Where as in DWH concern is subject orient (subject in the sense customer, product, item, time)

OLTP

  • Application Oriented
  • Used to run business
  • Detailed data
  • Current up to date
  • Isolated Data
  • Repetitive access
  • Clerical User
  • Performance Sensitive
  • Few Records accessed at a time (tens)
  • Read/Update Access
  • No data redundancy
  • Database Size 100MB-100 GB

DWH

  • Subject Oriented
  • Used to analyze business
  • Summarized and refined
  • Snapshot data
  • Integrated Data
  • Ad-hoc access
  • Knowledge User
  • Performance relaxed
  • Large volumes accessed at a time (millions)
  • Mostly Read (Batch Update)
  • Redundancy present

Fatal Error in Informatica


A Fatal error occurs when the Informatica Server cannot access the source, target, or repository. This can include loss of connection or target database errors, such as lack of database space to load data. If the session uses a Normalizer or Sequence Generator transformation, the Informatica Server cannot update the sequence values in the repository, and a fatal error occurs.

Causes for Informatica Session Failure


Reader errors
Errors encountered by the Informatica Server while reading the source database or source files. Reader threshold errors can include alignment errors while running a session in Unicode mode.

Writer errors
Errors encountered by the Informatica Server while writing to the target database or target files. Writer threshold errors can include key constraint violations, loading nulls into a not null field, and database trigger responses.

Transformation errors
Errors encountered by the Informatica Server while transforming data. Transformation threshold errors can include conversion errors, and any condition set up as an ERROR, such as null input.

Objects Created in Informatica Designer


Use the Designer to create and edit the following repository objects:

Source definitions
Detailed descriptions of database objects (tables, views, and synonyms), flat files, XML files, or COBOL files that provide source data. For example, a source definition might be the complete structure of the EMPLOYEES table, including the table name, column names and datatypes, and any constraints applied to these columns, such as NOT NULL or PRIMARY KEY. Use the Source Analyzer tool to import and create source definitions.

Target definitions
Detailed descriptions for database objects, flat files, or XML files to receive transformed data. During a session, the Integration Service writes the transformed data to targets. Use the Target Designer tool to import or create target definitions.

Transformations
A transformation generates, modifies, or passes data through ports that you connect in a mapping or mapplet. When you build a mapping or mapplet, you add transformations and configure them to handle data according to your business purpose.

Reusable transformations
You can design a transformation that you can reuse in multiple mappings or mapplets within a folder, a repository, or a repository domain. Rather than recreate the same transformation each time, you can make the transformation reusable and add instances of the transformation to individual mappings or mapplets. Use the Transformation Developer tool to create reusable transformations.

Mappings
A mapping specifies how to move and transform data from sources to targets. Mappings include source and target definitions and transformations. Transformations describe how the Integration Service Understanding Metadata 3
transforms data. Mappings can also include shortcuts, reusable transformations, and mapplets. Use the Mapping Designer tool to create mappings.

Mapplets
You can design a mapplet to contain sets of transformation logic to be reused in multiple mappings within a folder, a repository, or a repository domain. Rather than recreate the same set of transformations each time, you can create a mapplet containing the transformations and then add instances of the mapplet to individual mappings. Use the Mapplet Designer tool to create mapplets.

User-defined functions
You can create user-defined functions using the PowerCenter transformation language. Create user-defined functions to reuse expression logic and build complex expressions. Userdefined functions are available to other users in a repository.

Multi-dimensional metadata
Multi-dimensional metadata refers to the logical organization of data used for analysis in OLAP applications. Dimensions and cubes are most often used by end users of OLAP applications. Use the Target Designer tool to create dimensions and cubes.

You can also create shortcuts to metadata in shared folders. Use shortcuts to repository objects in shared folders. You can create local shortcuts to shared folders within the same repository and global shortcuts to shared folders in the global repository of the repository domain. Use the Designer to create shortcuts.