<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-9109385660486825237</atom:id><lastBuildDate>Mon, 20 Apr 2026 22:09:47 +0000</lastBuildDate><category>Informatica</category><category>Scripting</category><category>Administration</category><category>Automation</category><category>pmrep</category><category>Job Scheduling</category><category>webservice</category><category>Data_Integration_Hub</category><category>Informatica Sequence</category><category>Informatica_10</category><category>Repository</category><category>SAP</category><category>aggregation</category><category>email</category><title>Jeff&#39;s Cluttered Mind</title><description>Ramblings on Informatica PowerCenter and SQL</description><link>http://jeffkinzer.blogspot.com/</link><managingEditor>noreply@blogger.com (J. Kinzer)</managingEditor><generator>Blogger</generator><openSearch:totalResults>25</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-4950279489333641581</guid><pubDate>Thu, 27 Apr 2017 16:41:00 +0000</pubDate><atom:updated>2017-04-27T11:57:17.834-05:00</atom:updated><title>Informatica Truncate Target Table</title><atom:summary type="text">In the Target Table session properties there is an option to Truncate existing data before loading.  It is important to realize Informatica does not always use the TRUNCATE function to clear the table, sometimes a DELETE statement is issued, this decision is made at runtime depending on different factors, noted in the table below.




&amp;nbsp;
Depending on your needs, TRUNCATE may be what you want </atom:summary><link>http://jeffkinzer.blogspot.com/2017/04/informatica-truncate-target-table.html</link><author>noreply@blogger.com (J. Kinzer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEil_Br1394NapHH1_plHAi7NYIPWspg0bEee3o7hyprnQzKA_UgN20PPGgEJEMqOHfP4wBYPzPrt-I32HhOXngJx9wuZl0AFfqM_V-XUdESbz1DNxWex6kdAArGBzM_Dsw1N1GajO1ZDKk/s72-c/Truncate.png" height="72" width="72"/><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-7071346070857908732</guid><pubDate>Sun, 16 Oct 2016 02:28:00 +0000</pubDate><atom:updated>2016-11-21T19:34:08.780-06:00</atom:updated><title>Web Service Consumer for JDE BSSV Customer Manager - processCustomer</title><atom:summary type="text">Calling JDE Business Services (BSSV), aka Web Services, can be tricky and there is little information on Oracle&#39;s or Informatica&#39;s website showing how. In fact, importing the JDE CustomerManager.wsdl into an Informatica web service consumer creates a large confusing, near impossible to understand transformation.  Here&#39;s a high level overview to create a usable JDE 9.0 Customer Manager BSSV, be </atom:summary><link>http://jeffkinzer.blogspot.com/2016/10/web-service-consumer-for-jde-bssv.html</link><author>noreply@blogger.com (J. Kinzer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhrfvCmBVA4sOamGIWcFLmZq-Y70Swc9hHQfQxwYi8ncfX594gx625pyhKH8cGOAQ1cngUj7u_n5s-4hLiiVU7C8UFtuQnszWv_C06rF_UksWRyXc42lsInt571Nux9OsvnbkHiEb3-QDE/s72-c/BSSV+1.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-8762904786115058794</guid><pubDate>Tue, 11 Oct 2016 14:44:00 +0000</pubDate><atom:updated>2016-11-21T19:34:55.444-06:00</atom:updated><title>Scheduled Workflow Fails But Completes when Ran Manually</title><atom:summary type="text">Here&#39;s a solution to an obscure issue. A workflow/session completes successfully when ran manually but gives error LM_44127 Failed to prepare the task when ran from the scheduler.

If you are using Versioning, ALL objects must be checked in.  Use the option Versioning &gt; Find Checkouts to see any checked out objects.  Check in all objects.

Also, IMPORTANT, if using shortcuts for sources, targets </atom:summary><link>http://jeffkinzer.blogspot.com/2016/10/scheduled-workflow-fails-but-completes.html</link><author>noreply@blogger.com (J. Kinzer)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-1051419301038419737</guid><pubDate>Wed, 24 Aug 2016 02:46:00 +0000</pubDate><atom:updated>2016-11-21T19:35:13.696-06:00</atom:updated><title>Data Integration Hub Errors</title><atom:summary type="text">This page will be a running list of tips and workarounds for Data Integration Hub 10.



Error: unable to create all staging tables for topic
This error can occur if you have a reserved word as a column name.





Session must be established for &#39;end&#39;
This error can occur if the Web Service Hub (WSH) is down.  Log into the Informatica Console (not DIH console), check all the services. Restart any</atom:summary><link>http://jeffkinzer.blogspot.com/2016/08/data-integration-hub-errors.html</link><author>noreply@blogger.com (J. Kinzer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhQOoHp3UoXDix9Y-QC24fwb5Z4ImKVFqDBNHeqDg4Pp8vVC8vU-YuGYiuv2XM7ukoiPVvC_3fc7KBTMOKbzIksCY61PdMD9NLt2mZyY14ZL8oJswH2U_xR-VZ6eJna-jeH7LuwvQcbhXc/s72-c/UnableToCreateAllStagingTables.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-2814742879932981985</guid><pubDate>Sun, 21 Aug 2016 01:10:00 +0000</pubDate><atom:updated>2016-11-21T19:35:31.635-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Data_Integration_Hub</category><category domain="http://www.blogger.com/atom/ns#">Informatica_10</category><title>Data Integraton Hub DX_ETL DateTime Precision Issue</title><atom:summary type="text">This issue was found in Informatica Data Integration Hub 10 on Windows Server 2012 using SQL Server 2012 as the Repository. 
The PowerCenter Workflow DX_ETL can abort in mapping m_SET_CURRENT_CUTOFF giving the errors:

Timestamp parameters with a scale, must have a scale less than ten and a precision equal to 20 plus the scale. You specified a precision of 999 and scale of 9.

Fractional second </atom:summary><link>http://jeffkinzer.blogspot.com/2016/08/data-integraton-hub-dxetl-datetime.html</link><author>noreply@blogger.com (J. Kinzer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjx_m7UeHfls1zLwneNbbi3mtGvEtHs4hWJe9c-9coPqaaa0xQE5B9sKPDbCHXqQElsjUiEfha5ydkFBFWTMoJzZ46uGvjo_8AdQJ-BvCB3qcTn1w9XyAHeBQ4LXxOeQeJYOWDo-U7dfFc/s72-c/ODBC+DNS.png" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-6282986279359524613</guid><pubDate>Fri, 27 May 2016 16:09:00 +0000</pubDate><atom:updated>2016-11-21T19:35:55.612-06:00</atom:updated><title>Formatting Telephone Numbers</title><atom:summary type="text">I created this simple PowerCenter mapplet to format phone numbers. Informatica Developer (IDQ) may have a different or easier way to do it but I wanted something I could use in PowerCenter without the hassle of maintaining a separate object in IDQ and having to import it into PowerCenter.   You can alter the mapplet to format other data like postal codes, SSNs, etc.

Download the mapplet and give</atom:summary><link>http://jeffkinzer.blogspot.com/2016/05/formatting-telephone-numbers.html</link><author>noreply@blogger.com (J. Kinzer)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-7334582872499865636</guid><pubDate>Sun, 18 Jan 2015 16:37:00 +0000</pubDate><atom:updated>2017-01-07T07:30:00.296-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">SAP</category><title>Limit Extracts from SAP Tables Using Mapping Parametes</title><atom:summary type="text">When extracting large tables from SAP, you can limit the
amount of data selected by using Informatica parameters.&amp;nbsp; Here are two examples.


Use a parameter to limit the extract to retrieve only a specified set of data. Your target uses a truncate and load scenario.
Use parameters as in the example above but also use a persistent cache lookup on the target table. Append new rows to the
table.</atom:summary><link>http://jeffkinzer.blogspot.com/2015/01/limit-extracts-from-sap-tables-using.html</link><author>noreply@blogger.com (J. Kinzer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjiXsO51MvUX1HiMUjGhYMc6I8LbkRV4gLHVqFkNHcbsboFjE_s4OtT2eSPlo9Gt7fdEipXqZLN8TZ5VSyCCXwF9Pj6XcgOhww4_Ox4urtJtgUmY-3uTpQ8l1YHlzKHF25a-_k3BfgG14c/s72-c/ABAP+Program+Flow.jpg" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-7936794643719948025</guid><pubDate>Sun, 18 Jan 2015 16:19:00 +0000</pubDate><atom:updated>2016-11-21T19:37:55.083-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Administration</category><category domain="http://www.blogger.com/atom/ns#">Informatica</category><category domain="http://www.blogger.com/atom/ns#">webservice</category><title>Diary of an Informatica 9.6.1 HF1 Install</title><atom:summary type="text">Here are some notes on an Informatica PowerCenter 9.6.1 64 bit server install.&amp;nbsp; This also includes the setup of the Informatica Cloud Secure Agent (64)

Most of the install went smooth.&amp;nbsp; However I want to list some of the problems I encountered.


Something unique about this install is the PowerCenter server name was in this format: SERVERT.corpt.tginternaltest.dev.&amp;nbsp; There was </atom:summary><link>http://jeffkinzer.blogspot.com/2015/01/diary-of-informatica-916-hf1-install.html</link><author>noreply@blogger.com (J. Kinzer)</author><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-6254710880374994513</guid><pubDate>Thu, 21 Jun 2012 01:00:00 +0000</pubDate><atom:updated>2016-11-21T19:40:29.339-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Automation</category><category domain="http://www.blogger.com/atom/ns#">Informatica</category><category domain="http://www.blogger.com/atom/ns#">Scripting</category><title>VBScript to Convert Excel to CSV</title><atom:summary type="text">Using Excel files as the source for Informatica mappings can be more trouble than it&#39;s worth. You have to setup a connection and name a range in the Excel document which can be difficult to maintain.   I much prefer to read text or CSV files, they&#39;re simpler to work with and less error prone.  I created a VB script for the purpose of converting Excel to CSV.


You can use the script to convert an</atom:summary><link>http://jeffkinzer.blogspot.com/2012/06/vbscript-to-convert-excel-to-csv.html</link><author>noreply@blogger.com (J. Kinzer)</author><thr:total>26</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-3809897928750434284</guid><pubDate>Tue, 22 May 2012 01:32:00 +0000</pubDate><atom:updated>2016-11-21T19:40:55.855-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Administration</category><category domain="http://www.blogger.com/atom/ns#">Repository</category><title>Querying the Repository</title><atom:summary type="text">Here are some SQL scripts you can use to query the repository.  Most of these I got from an Informatica employee, others I put together. Use them as a base to create your own queries or reports.  
One word of caution, use a profile with READ ONLY permission to access the repository and NEVER update the repository using SQL unless advised to do so by Informatica support.

The scripts use MS SQL </atom:summary><link>http://jeffkinzer.blogspot.com/2012/05/querying-repository.html</link><author>noreply@blogger.com (J. Kinzer)</author><thr:total>5</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-1056425670733713492</guid><pubDate>Sun, 29 Jan 2012 20:40:00 +0000</pubDate><atom:updated>2016-11-21T19:41:49.016-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Automation</category><category domain="http://www.blogger.com/atom/ns#">Informatica</category><category domain="http://www.blogger.com/atom/ns#">Scripting</category><title>Using pmrep to import an Informatica folder</title><atom:summary type="text">Here’s the companion script for the “Using pmrep to export an Informatica folder” article.  Use this script to import objects into PowerCenter.

One use for scripting an import would be to schedule it during off hours, for example moving development code to production during off hours.  You may also need to export some objects, then do a &quot;mass change&quot; or Find/Replace on the XML file, then export </atom:summary><link>http://jeffkinzer.blogspot.com/2012/01/using-pmrep-to-import-informatica.html</link><author>noreply@blogger.com (J. Kinzer)</author><thr:total>13</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-6849729220941651152</guid><pubDate>Thu, 01 Dec 2011 02:07:00 +0000</pubDate><atom:updated>2016-11-21T19:42:12.724-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Informatica</category><title>Managing Connections using Parameter Files</title><atom:summary type="text">Try this tip for managing PowerCenter connections.
Parametrize connections and use one parameter file to define them. Use the one parameter file in all your workflows.  This will bring consistency to development and make it easy when connection changes are required.


Parameter files are also useful for defining “logic” related parameters or variables but define those in a separate parameter file</atom:summary><link>http://jeffkinzer.blogspot.com/2011/11/managing-connections-using-parameter.html</link><author>noreply@blogger.com (J. Kinzer)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-6411891912198215001</guid><pubDate>Sat, 09 Jul 2011 20:24:00 +0000</pubDate><atom:updated>2016-11-21T19:43:27.659-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Scripting</category><title>VBScript to Combine Multiple XLS Files into a Single File</title><atom:summary type="text">Here&#39;s a companion tip to the &quot;VBScript to convert CSV to XLS&quot; post.

This script will combine two Excels files into one workbook. The files will be treated as separate worksheets inside the workbook.  The worksheet names will be the same as the file names. 

You may find this useful when an Inforamtica process outputs multiple flat files and you have converted them into native Excel format but </atom:summary><link>http://jeffkinzer.blogspot.com/2011/07/vbscript-to-combine-multiple-xls-files.html</link><author>noreply@blogger.com (J. Kinzer)</author><thr:total>7</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-2761922934609104325</guid><pubDate>Fri, 15 Apr 2011 02:21:00 +0000</pubDate><atom:updated>2016-11-21T19:44:51.275-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Informatica</category><title>The Transaction Control</title><atom:summary type="text">Here is a sample mapping to illustrate how the Transaction Control transformation can dynamically create multiple flat file outputs, each with a unique name and data set.

The mapping reads a source table whose key is “Group Id”, and outputs a separate target file for each Group Id data set.  The file names are also generated dynamically based on the Group Id.

There are two “secrets” to the </atom:summary><link>http://jeffkinzer.blogspot.com/2011/04/the-transaction-control.html</link><author>noreply@blogger.com (J. Kinzer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhzNaTJs8oUopCAJFjHSH53TPVD0loZVeRAIJhtv6RRrhw_X9Fpe4X3jXysJHuVlOEptHr91UtgXkaePSlLmJYe3Tl-7zz7gti25aOlhKa5uFDONWuRcfov3mpC5U_7tKX0kSuZuelzFdc/s72-c/FileName_icon.jpg" height="72" width="72"/><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-985535688972906250</guid><pubDate>Sat, 12 Feb 2011 15:58:00 +0000</pubDate><atom:updated>2016-11-21T19:45:37.490-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">aggregation</category><category domain="http://www.blogger.com/atom/ns#">email</category><category domain="http://www.blogger.com/atom/ns#">Informatica</category><category domain="http://www.blogger.com/atom/ns#">webservice</category><title>Using a  web service to send e-mail</title><atom:summary type="text">Informatica allows options for sending email at the session level (on Session Success or Failure) but there is not a standard way to send email from the mapping.   By using a web service (written in a third party language such as .Net or Java) to send email, you can generate email from a mapping based on conditional logic and include relevant &quot;pipeline&quot; data in the email body.  An additional </atom:summary><link>http://jeffkinzer.blogspot.com/2011/02/using-web-service-to-send-e-mail.html</link><author>noreply@blogger.com (J. Kinzer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj810XTzoKRWr5arJXtcdJS20NCh0mx_FzOcGEDEgbiSq1BA78tLlG1UJ-Tt5qr0bPKkMqJf-zLtdzvvvAmM985sD9x0hB8DZIQZnx6T8E_d6RAgPZ4VA231AGeTeyC3kDgSnEmnSMZyuA/s72-c/email_example.jpg" height="72" width="72"/><thr:total>5</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-3269663330284893052</guid><pubDate>Tue, 11 Jan 2011 03:20:00 +0000</pubDate><atom:updated>2016-11-21T19:46:52.583-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Administration</category><category domain="http://www.blogger.com/atom/ns#">Automation</category><category domain="http://www.blogger.com/atom/ns#">Job Scheduling</category><category domain="http://www.blogger.com/atom/ns#">pmrep</category><title>Unschedule Workflow Script</title><atom:summary type="text">Here is a technique that can be used to unschedule workflows automatically or conditionally.  This process uses the pmrep command to unschedule any workflows specified in a CSV file.

I have a copy of this workflow scheduled on our development server using the scheduling option &quot;Run on Integration Service initialization&quot;.  I do this because any restart of the Informatica service will “re-schedule</atom:summary><link>http://jeffkinzer.blogspot.com/2011/01/unschedule-workflow-script.html</link><author>noreply@blogger.com (J. Kinzer)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-6997879923682956998</guid><pubDate>Mon, 01 Nov 2010 17:00:00 +0000</pubDate><atom:updated>2016-11-21T19:47:20.554-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Informatica</category><title>Session Failure emails</title><atom:summary type="text">Here is a reusable email task you can use for the “On Failure E-Mail” property for any Informatica session. If the session fails an email is sent to an address you specify. The content of the email is generic but you get all relative information about the session’s failure, plus the session log as an email attachment.

Download the task and import it into a PowerCenter folder. Next set the “On </atom:summary><link>http://jeffkinzer.blogspot.com/2010/11/session-failure-emails.html</link><author>noreply@blogger.com (J. Kinzer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhuJmZJUZ9KTUn2V1jeMuHlDSvP5Mt73BBmxV7Y6WkyOd48RVT8a9wxbGrvgDUQOCuFF5nEBs42TPX_CnboIT4JgCvOk6-zpJbc4jzH30YZ4XZn012abL3dFJ7Z8AonkUAbyd2AVvOTmKk/s72-c/eamil_session_failure.jpg" height="72" width="72"/><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-2053931278182096123</guid><pubDate>Mon, 04 Oct 2010 10:49:00 +0000</pubDate><atom:updated>2016-11-21T19:47:49.194-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Administration</category><category domain="http://www.blogger.com/atom/ns#">Automation</category><category domain="http://www.blogger.com/atom/ns#">pmrep</category><category domain="http://www.blogger.com/atom/ns#">Scripting</category><title>Assign Object Permissions - pmrep AssignPermission</title><atom:summary type="text">Note: This tip is part of a series on administration scripts.

These scripts automate the process to grant permissions to PowerCenter Folders, Connections and Query objects.  In my company’s PowerCenter development environment, we allow each developer to access all folders and connection objects.  Our security structure is designed so all developers are in a security group, these scripts grant </atom:summary><link>http://jeffkinzer.blogspot.com/2010/10/assign-object-permissions-pmrep.html</link><author>noreply@blogger.com (J. Kinzer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjV7KFP989nu_YaWdQqYJlRX0-atMrqoxWHmusX1wW6Ei0fc6lr2GvDFW0-cOBBnommmHb_C9840URMi-hzqlLqXkeZy8rpdlYgtd6NyNe0vzUXpGQzRkw1C7D7tt83QFAgouqW8g4LftI/s72-c/connection_permission.jpg" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-7635242766256853082</guid><pubDate>Sat, 04 Sep 2010 12:58:00 +0000</pubDate><atom:updated>2016-11-21T19:48:15.318-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Informatica Sequence</category><title>Sequence Number Generation</title><atom:summary type="text">The Sequence Generator transformation is great sometimes but I cannot find a way to reset the generated sequence based on external conditions. For example, when a value in the current row is different from the value in a previous row, I would like to reset the Sequence number.

Using some information I found on Informatica’s Knowledge base, I created a reusable Expression that will increment or </atom:summary><link>http://jeffkinzer.blogspot.com/2010/09/sequence-number-generation.html</link><author>noreply@blogger.com (J. Kinzer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjKwu4pAFaYMaOEYlKRlUaquHyoN_E9GQyXIPTgQcSDHt8uTB5AK7XWMUSp5a5tPOo5eBfMZVJEBcIdVX3664pGWOWSpGB4TFFpCH9ozxtPQEbtP6wrYNN1Wu9BWkqzZIndipPnKWGm9kQ/s72-c/exp_Sort_Seq.jpg" height="72" width="72"/><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-1613172955590488157</guid><pubDate>Sun, 01 Aug 2010 12:00:00 +0000</pubDate><atom:updated>2016-11-21T19:48:32.484-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Administration</category><category domain="http://www.blogger.com/atom/ns#">Automation</category><category domain="http://www.blogger.com/atom/ns#">Informatica</category><title>A Script For Informatica Repository Backups</title><atom:summary type="text">Summary:&amp;nbsp;&amp;nbsp;&amp;nbsp;This tip will show you how to augment the&amp;nbsp;pmrep command&#39;s&amp;nbsp;backup function with environment variables to dynamically create the backup file names.&amp;nbsp; I&#39;ve included a visual basic script that can be used to delete old backup files from any folder. &amp;nbsp;The result is a script you can schedule on your Windows server for unattended repository backups.
An example</atom:summary><link>http://jeffkinzer.blogspot.com/2010/05/using-script-to-automating-informatica.html</link><author>noreply@blogger.com (J. Kinzer)</author><thr:total>5</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-5135046659276687187</guid><pubDate>Fri, 11 Jun 2010 00:48:00 +0000</pubDate><atom:updated>2016-11-21T19:48:51.067-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Informatica</category><category domain="http://www.blogger.com/atom/ns#">pmrep</category><category domain="http://www.blogger.com/atom/ns#">Scripting</category><title>Using pmrep to export an Informatica folder</title><atom:summary type="text">Sometimes you need to export the contents of a PowerCenter folder for offline storage. This post will show you how to quickly export a PowerCenter folder&#39;s contents using the pmrep command&#39;s ObjectExport function.

The nice thing about this tip is I give you a script (download here) that will export a folder&#39;s contents as individual XML files and export one XML file containing all the folder&#39;s </atom:summary><link>http://jeffkinzer.blogspot.com/2010/06/using-pmrep-to-export-informatica.html</link><author>noreply@blogger.com (J. Kinzer)</author><thr:total>41</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-4002839591290229605</guid><pubDate>Thu, 03 Jun 2010 00:24:00 +0000</pubDate><atom:updated>2022-10-07T08:34:15.179-05:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Informatica</category><category domain="http://www.blogger.com/atom/ns#">pmrep</category><category domain="http://www.blogger.com/atom/ns#">Scripting</category><title>VBScript to convert CSV to XLS</title><atom:summary type="text">Informatica can easily output target data in comma separated value format (CSV) but sometimes you require output formatted in native Excel. &amp;nbsp;Here&#39;s a reusable Visual Basic Script that will convert a CSV file into a nicely formatted native Excel file. 

The script can be ran individually or as this tip will demonstrate,  can be evoked from a PowerCenter Session&#39;s &quot;Post-Session Success Command</atom:summary><link>http://jeffkinzer.blogspot.com/2010/06/vbscript-to-convert-csv-to-xlsx.html</link><author>noreply@blogger.com (J. Kinzer)</author><thr:total>30</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-6622942318291562154</guid><pubDate>Mon, 10 May 2010 23:09:00 +0000</pubDate><atom:updated>2016-11-21T19:54:29.747-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Informatica</category><title>PowerCenter Dependences Report</title><atom:summary type="text">The &quot;Dependences&quot; report in PowerCenter is great for showing where objects (especially sources and targets) are used.  Recently however, one of my team members almost deleted a  Flat File source definition because it showed NO dependencies.  After double checking they found where the Flat File object was used as a lookup!!

Has anyone else had issues with the &quot;Dependences&quot; report not showing all </atom:summary><link>http://jeffkinzer.blogspot.com/2010/05/powercenter-dependences-report.html</link><author>noreply@blogger.com (J. Kinzer)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-1980636503170288159</guid><pubDate>Thu, 06 May 2010 01:39:00 +0000</pubDate><atom:updated>2016-11-21T19:52:47.766-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Informatica</category><category domain="http://www.blogger.com/atom/ns#">Scripting</category><title>Using Informatica Environment Variables</title><atom:summary type="text">If you frequently use scripts to run PowerCenter commands pmrep and pmcmd, make sure you are using server environment variables for repetitive command parameters.

Benefits of using environment variables:
Eliminate the need to change scripts when migrating from test to production.
Reduce need to change scripts when upgrading to new version of PowerCenter.
Better security: user id and passwords </atom:summary><link>http://jeffkinzer.blogspot.com/2010/05/using-informatica-server-environment.html</link><author>noreply@blogger.com (J. Kinzer)</author><thr:total>18</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-9109385660486825237.post-1033489753561448488</guid><pubDate>Fri, 30 Apr 2010 16:56:00 +0000</pubDate><atom:updated>2016-11-21T19:52:24.988-06:00</atom:updated><category domain="http://www.blogger.com/atom/ns#">Informatica</category><category domain="http://www.blogger.com/atom/ns#">Job Scheduling</category><title>Running an Informatica workflow hourly, but only between specific hours of the day</title><atom:summary type="text">If you need a workflow to run every day, but only during working hours, for example you need a workflow to only run if the time is between. 8:00 a.m. to 6:00 p.m., try this technique.

Use&amp;nbsp;a Decision task to compare a workflow&#39;s start time to a range of hours/minutes you specify.

The general idea is, using a Decision task you compare the workflow start time with a predetermined time, then </atom:summary><link>http://jeffkinzer.blogspot.com/2010/04/running-informatica-workflow-hourly-but.html</link><author>noreply@blogger.com (J. Kinzer)</author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi1nKlSLyIa_s-7isP9j1JylUrySi4W-RCvL6SSsSRCDi6Ux4UQ9WdJdh8CZ-Klw1InJhXEwblvS5J6unMqWQuPk7qEmjc7Pi8PemAqiXTj_BDqcVR67cOuQOWJcKu9QVIyFdYlnAASjzc/s72-c/wfexample_time.jpg" height="72" width="72"/><thr:total>5</thr:total></item></channel></rss>