Thursday, 21 April 2016

DBA_DIRECTORIES

DBA_DIRECTORIES describes all directory objects in the database. Its columns are the same as those in "ALL_DIRECTORIES".

This  view will be helpful to locate the dump files which are created through the DBA option in Oracle SQL Developer. 

Tuesday, 5 April 2016

Truncating Logs with the pmrep TruncateLog Command


Truncating Logs with the pmrep TruncateLog Command 

You can use the pmrep TruncateLog command to truncate workflow and session logs in the PowerCenter repository. 

The command returns "truncatelog completed successfully" or returns "Failed to execute truncatelog." 

The truncate operation might fail for the following reasons: • The folder name is not valid. •
 
The workflow does not exist in the given folder. • You specified a workflow, but no folder name.

 The TruncateLog command uses the following syntax: truncatelog -t [-f ] [-w ]

Step 1 : 
 pmrep connect -r ******** -d ******* -n ********* -x ***********

Step2 :  pmrep truncatelog -t 200

Truncatelog command purges the log information in below listed tables 

OPB_DTL_SWIDG_LOG
OPB_PERF_COUNT
OPB_SESS_TASK_LOG
OPB_SWIDGINST_LOG
OPB_TASK_INST_BRK
OPB_TASK_INST_RUN
OPB_WFLOW_CACHE
OPB_WFLOW_DEP_RUN
OPB_WFLOW_RUN

Monday, 4 April 2016

Precision Property in Informatica Session.. avoid data loss!!

Found something interesting last week @ work. This was a failure we had due to data overflow. We were trying to load data from source of higher precision into the target of same data type but with lesser precision. We had a source column of Decimal(17,3). Before we proceed, we must all be aware that 17 here refers to the precision length (i.e. 14 digits before decimal + 3 digits after decimal). And the target was set of a size or precision Numeric(15,5) means 10 digits before and 5 digits after decimal.

This was all working good until all our source data was within the precision of (15,5), and finally when the size outlined this there came a data overflow error while running the Informatica session. so all we had to do was change the precision at the data base level as from Numeric(15,5) to Numeric(17,3). Then again the session failed, and it was right as we are yet to change the same in the Informatica Target transformation.

Now a change done on Target in informatica to match with the table in SQL Server (in our case the target table here). On running the session it all succeeded. But there is something we have to wonder on!! "The precision were not changed in all other transformation in the mapping!! still the session made it through with no truncate on the source data value."

Well this was possible with one property set on your session level, enable high precision on the properties tab of the session. In case of Decimal values the Integration services handles the values in a different way as is explained in the
Informatica help:

"To ensure precision of up to 28 digits, use the Decimal datatype and enable high precision in the session properties. When you run a session with high precision, the Integration Service processes decimal values as Decimal. Precision loss does not occur in a calculation unless the result produces a value with precision greater than 28 digits. In this case, the Integration Service stores the result as a double."

For example, you have a mapping with Decimal (17,3) that passes the number 400120303049 and we have to convert from here to Numeric(15,5). If the session does not run with high precision, the Integration Service converts the decimal value to Numeric and passes 4001203030 to the next transformation.

To sum up here, the integration services allows the precision of the maximum allowed (say for decimal as 28) to pass through without any truncate on the result one and only if the high precision property is set on the session Property.