Simple Trick to View .bin log files in INFA

Success and Failures of an Informatica map are part of a developers life and Session log files save a hell lot of time in finding the issues.

However many a times we do not get .log files; rather we get .bin files from QA team which do not open in a text editor. In such cases we usually try connecting to QA's INFA environment to see the log from INFA monitor or ask QA to provide it in .txt format. All these could take time and delay the bug fix.

W can read these .bin files itself easily. There are two options available -

Use this command after copying the .bin file to you local INFA environment --
'infacmd ConvertLogFile -in -lo'. This batch files is present in Informatica\PowerCenter8.6.1\CMD_Utilities\PC\server\bin

However there is a much better and an easier way to read those files -
Copy the .bin files to a folder.
Go to your local Informatica Monitor. Go to Tools --> Import log --> Browse for the .bin file

The log file opens like any other session log on the monitor. Find the issue and fix it. If required, save the log as .txt for future usage.

Why do we prefer Inner Join then Outer Join between the RPD LTS tables

Except for the requirements on the join condition between the tables in the LTS we may choose outer join, but default join condition between two tables in the LTS are joined as INNER JOIN, and we prefer Inner Join.

You can think of the tables in a logical dimension table source as being like a database view. When it formulates physical SQL, Oracle BI Server will leave out the tables in this “view” that are not needed to satisfy the logical query (join elimination), but only if the join type is Inner. When the join type is Outer, however, Oracle BI Server will always include the tables.

So for the better performance we always use INNER JOIN.

Btw dont believe on my words... Just my analysis...

(Reference: Oracle BI Suite EE 10g R3 - Activity Guide)