Monday, October 1, 2012

PC86 - Purge older versions of objects in a versioned PowerCenter Repository


pmrep connect -r Repo_Name -d Domain_Name -n Administrator -x Pwd> test.out


pmrep purgeversion -n -f > test1.out

last_n_versions_to_keep --- Number of latest checked-in object versions to keep for an active object in the folder specified (note: -f is an optional feature).

The value must be an integer greater than 0.

For example, enter 5 to purge all versions except the last five checked-in versions.

PC86 - Informatica Services Not able to Start



Informatica Repository and Integration Services will be Not able to Start and you can view below error codes in admin console and server logs

ERROR CODES: [CNX_53021 ],[DOM_10022], [LGS_10048],[DOM_10055],[SPC_10050],[SPC_10013],[SPC_10008] and  [InfPrivilegeSynchronizationEngine]

Logs:

Admin Console:

ERROR Mon Sep 24 00:00:33 2012 1833290048 CNX_53021 Received an invalid request.

Service Manager ERROR Mon Sep 24 04:07:21 2012 Thread 2 of 6 in DomainServiceThreadPool DOM_10055 Unable to start service process [INFA8_DEV_REPO] on node [n1_ServerName].


Service Manager ERROR Mon Sep 24 04:07:21 2012 Thread 2 of 6 in DomainServiceThreadPool SPC_10050 The domain failed to restart the service [INFA8_DEV_REPO] after trying for the maximum [3] restart attempts.

Service Manager ERROR Mon Sep 24 04:07:21 2012 Thread 2 of 6 in DomainServiceThreadPool SPC_10013 Process for service INFA8_DEV_REPO failed to start.

Service Manager WARNING Mon Sep 24 04:07:21 2012 Domain Monitor SPC_10012 Process for service [INFA8_DEV_REPO] terminated unexpectedly.

Service Manager ERROR Mon Sep 24 04:07:21 2012 Domain Monitor SPC_10008 Service Process [INFA8_DEV_REPO] output error [/infa/informatica/pc86/server/bin/pmrepagent: error while loading shared libraries: libpmrcore.so: cannot open shared object file: No such file or directory

Service Manager ERROR Mon Sep 24 04:07:17 2012 Thread 2 of 6 in DomainServiceThreadPool DOM_10055 Unable to start service process [INFA1_DEV_REPO] on node [n1_ServerName].

Service Manager ERROR Mon Sep 24 04:07:17 2012 Thread 2 of 6 in DomainServiceThreadPool SPC_10050 The domain failed to restart the service [INFA1_DEV_REPO] after trying for the maximum [3] restart attempts.

Service Manager ERROR Mon Sep 24 04:07:17 2012 Thread 2 of 6 in DomainServiceThreadPool SPC_10013 Process for service INFA1_DEV_REPO failed to start.

Service Manager WARNING Mon Sep 24 04:07:16 2012 Domain Monitor SPC_10012 Process for service [INFA1_DEV_REPO] terminated unexpectedly.

Service Manager ERROR Mon Sep 24 04:07:16 2012 Domain Monitor SPC_10008 Service Process [INFA1_DEV_REPO] output error [/infa/informatica/pc86/server/bin/pmrepagent: error while loading shared libraries: libpmrcore.so: cannot open shared object file: No such file or directory

Service Manager ERROR Mon Sep 24 04:07:06 2012 Thread 3 of 6 in DomainServiceThreadPool SPC_10013 Process for service INFA8_DEV_REPO failed to start.

Service Manager WARNING Mon Sep 24 04:07:06 2012 Domain Monitor SPC_10012 Process for service [INFA8_DEV_REPO] terminated unexpectedly.

Service Manager ERROR Mon Sep 24 04:07:06 2012 Domain Monitor SPC_10008 Service Process [INFA8_DEV_REPO] output error [/infa/informatica/pc86/server/bin/pmrepagent: error while loading shared libraries: libpmrcore.so: cannot open shared object file: No such file or directory

Service Manager ERROR Mon Sep 24 04:07:06 2012 Thread 3 of 6 in DomainServiceThreadPool DOM_10055 Unable to start service process [INFA8_DEV_REPO] on node [n1_ServerName].

Service Manager ERROR Mon Sep 24 04:07:02 2012 Thread 3 of 6 in DomainServiceThreadPool DOM_10055 Unable to start service process [INFA1_DEV_REPO] on node [n1_ServerName].

Service Manager ERROR Mon Sep 24 04:07:02 2012 Thread 3 of 6 in DomainServiceThreadPool SPC_10013 Process for service INFA1_DEV_REPO failed to start.

Service Manager WARNING Mon Sep 24 04:07:01 2012 Domain Monitor SPC_10012 Process for service [INFA1_DEV_REPO] terminated unexpectedly.

Service Manager ERROR Mon Sep 24 04:07:01 2012 Domain Monitor SPC_10008 Service Process [INFA1_DEV_REPO] output error [/infa/informatica/pc86/server/bin/pmrepagent: error while loading shared libraries: libpmrcore.so: cannot open shared object file: No such file or directory

Catalina Log :

2012-09-24 02:47:06,619 INFO [InfPrivilegeSynchronizationEngine] Returning 55 supported privileges.
2012-09-24 02:47:16,919 ERROR [ConfigFacadeImpl] PCSF Error in listAvailableNamespaces.
com.informatica.pcsf.common.exception.PCSFTimeoutException: [DOM_10022] Election is in progress, cannot complete request.

Node Log:

2012-09-24 02:47:25,398 ERROR [Monitor Guaranteed Message File Thread] [LGS_10048] The following error occurred while logging to Log Service: [[DOM_10022] Election is in progress, cannot complete request.].\n
com.informatica.pcsf.common.exception.PCSFTimeoutException: [DOM_10022] Election is in progress, cannot complete request.

exceptions.log

2012-09-24 02:47:25,397 ERROR [Monitor Guaranteed Message File Thread] [LGS_10048] The following error occurred while logging to Log Service: [[DOM_10022] Election is in progress, cannot complete request.].\n
com.informatica.pcsf.common.exception.PCSFTimeoutException: [DOM_10022] Election is in progress, cannot complete request.

ISSUE Services will be not be starting due to missing of  libpmrcore.so file

SOLUTION:
  • Copy libpmrcore.so file from other server to current server path, installation path (/server/bin/)
  • Start infaservices from tombin path
  • Verify Repository and integration Services



Part 4.5 Physical Data Modeling


Physical Database Design

Physical database design is the process of developing a set of required data structures on a selected database. It involves the following tasks:
  • Converting entities into tables
  • Converting relationships into foreign keys
  • Converting attributes into columns
  • Defining constraints
 The purpose of physical design is to optimize performance as closely as possible.







 Along with the logical data model, the database designer requires the following to make sound design decisions:

  • The Process Model, detailing input processes (creation and updating of rows in tables) and output requirements (retrieval of data from the database)
  • The mapping that shows the processes that access each entity class and how (create, update, retrieve)
  • Nonstructural data requirements
  • Performance requirements
  • The target DBMS
  • Disk space requirement
  • Availability of skilled programming resources








 

Part 4.4 Logical Data Modeling



Introduction to Logical Model

Logical Data Model refers to the actual implementation of a conceptual module in a database. It represents normalized design of common data model which is required to support the design of an information system.
The very core of the logical data model is the definition of the three types of data objects which the building blocks of the data model and these data objects are the entities, attributes, and relationships. Entities refer to persons, places, events or things which are of particular interest to the company.

Some examples of entities are Employees, States, Orders, and Time Sheets. Attributes refer to the properties of the entities. Examples of attributes for the Employee entity are first name, birthday, gender, address, age and many others. Lastly, relationships refer to the way where in the entities relate to each other.  An example relationship would be "customers purchase products" or "students enroll in classes". 

If the database is ported to another DBMS supporting a similar structure, the logical data model can still be used as a baseline for the new physical data model.


Characteristics of a Logical Model

  • Logical model works in an iterative manner.
  • Its design is independent of database.
  • It includes all entities and relationships among them.
  • All attributes for each entity are specified.
  • The primary key for each entity is specified.
  • Foreign keys (keys identifying the relationship between different entities) are specified.










Part 4.3 Dimensional Data Model



4.3 Dimensional Data Modeling


4.3.1      Steps in Dimensional Modeling
4.3.2      Star Schema & Snowflake Schema
4.3.3      The Implementation Approach (Bill & Ralph)
4.3.4      Dimensional Modeling Fundamentals
4.3.4.1   Dimensional Modeling Overview
4.3.4.2   Dimensional Modeling Steps
4.3.5     Confirmed Dimensions
4.3.6     Slowly Changing Dimension
4.3.7     Additivity of Measures
4.3.8     Dimensional Modeling framework


4.3.1 Steps in Dimensional Modeling





4.3.2 Star Schema & Snowflake Schema






4.3.3 The Implementation Approach (Bill & Ralph)


  4.3.4 Dimensional Modeling Fundamentals


4.3.4.1 Dimensional Modeling Overview


Dimensional Modeling


  • A logical design technique that seeks to present the data in a standard framework that is intuitive and allows for high performance access
  • It is inherently dimensional and adheres to a discipline that uses relational model with some important restrictions
  • The fundamental idea of dimensional modeling is that nearly every type of business data can be represented as a kind of cube of data, where the cells of the cube contain measured values and the edges of the cube define the natural dimensions of the data
  • Every dimensional model is composed of one table with multipart key, called the fact table, and a set of smaller tables called dimension tables
  • Each dimension table has a single part primary key that corresponds exactly to one of the components of the multipart key in the fact table
  • This characteristic star-like structure is often called a star join
  • The fact table contains facts or measurements of the business
  • The dimension tables contain textual attributes that describe the facts
  • The attributes in the dimension tables are used for constraining & grouping data within data warehouse queries

Dimension Tables


  • Dimension Tables are the entry points into the data warehouse
  • Dimension tables are designed especially for selection and grouping under a common head
  • Determine contextual background for facts
  • Parameters for OLAP
  • Common Dimensions are D
          Date
         
Product
         
Location/Region
         
Customers
 Fact Table


The fact table is where the numerical measurements (measure)of the business are stored

Facts

  • The detail information in a Fact tables,For Examples: Sales Quantity, Unit Sales Price, Sales Amount etc.
  • Key performance indicators of the business
  • Numeric in Nature
  • Analyzed across the dimensions

4.3.4.2 Dimensional Modeling Steps


Dimensional Modeling Steps


  1. To build a dimensional database Choose the business processes that you want to use to analyze the subject area to be modeled.
  2. Determine the Granularity of the fact tables.
  3. Identify Dimensions and Hierarchies for each fact table.
  4. Identify Measures for the fact tables.
  5. Determine the Attributes for each dimension table.
  6. Get users to verify the data model.

4.3.5 Confirmed Dimensions








4.3.6 Slowly Changing Dimension








4.3.7 Additivity of Measures



Additivity is the ability of measures to be added across all dimensions of the fact table. Measures could be fully additive, semi additive or non additive


Fully Additive - Perfectly additive across all dimensions - No issues.

Semi Additive - Not additive across one or more dimensions (usually across time). Need to query using single unit of non-additive dimension.

Non-Additive - Non-additive. Store individual components and calculate ratio of sums vs. sum of ratio’s.



4.3.8 Dimensional Modeling framework