Troubleshooting Informatica Error Messages and Resolution – Part 21

The Designer cannot import the selected objects.
Cause:A transfer structure that is not an InfoSource was selected in the Import SAP BW Metadata dialog box. Only InfoSources can be imported.
Action:Select InfoSources only and then click Add to Import List.

Hostname <hostname> unknown.
Cause:The SAP BW Service cannot connect to the host specified in the saprfc.ini file (as the GWHOST entry) and cannot connect to the BW system. This error originates in Common Program Interface-Communications (TCP/IP) on the local host.
Action:Change the GWHOST entry in the saprfc.ini file to point to the host on which the BW system is running.The SAP BW system does not contain any activated InfoSources.
Cause:The SAP BW system does not contain any activated InfoSources. InfoSources must be activated before they can be imported into PowerCenter.
Action:In the SAP BW system, create and activate the InfoSources you want to import into PowerCenter.

The Designer cannot import all of the selected items. <Number of items> items were selected. However, only <number of items> items were added to the import list.
Cause:InfoSources that are not correctly created and activated in the SAP BW system were selected in the Import SAP BW Metadata dialog box.
Action:In the SAP BW system, verify that the InfoSources you want to import into PowerCenter are properly created and activated.The Designer is not connected to the SAP BW server.
Cause:In the Import SAP BW Metadata dialog box, Add to Import List was clicked before a connection was made to the SAP BW system.
Action:Connect to the SAP BW system by entering the appropriate Connect to SAP values and clicking Connect. Select the InfoSources you want to import and click Add to Import List.Open saprfc.ini failed: No such file or directory.
Cause:The Designer, Integration Service, or SAP BW Service could not locate the saprfc.ini file. Either the file does not exist or the RFC_INI environment variable is not set correctly.
Action:Verify that the saprfc.ini file exists. Also verify that the RFC_INI environment variable is equal to the full path of the saprfc.ini file. You must stop and restart the Service Manager for the environment variables to take effect.Partner not reached (host <host name>, service <service number>).
Cause:The SAP BW Service is unable to connect to the BW system specified as GWSERV in the saprfc.ini file. This error originates in Common Program Interface-Communications (TCP/IP) on the local host.
Action:Change the GWSERV entry in the saprfc.ini file to point to the server on which the BW system is running.

Above are list of Informatica Error Messages or Warnings received while performing certain operation against Informatica related products.

What are Informatica Error Messages?

Informatica error codes are a set of error codes for use by all Informatica products. Every Informatica error message returned by Informatica, is self explanatory and contains the object name in cases where required.

When it comes to troubleshooting, the more you know the better troubleshooter you are (in my option). Sometimes knowing more actually gets in the way. We repeatedly get calls where customers couldn’t connect to AlwaysOn Listener on Azure because of the misconfiguration of the subnet mask for the listener IP. They receive this error “A...

We just released SQL Nexus 5.5.0.1 on codeplex. In addition to numerous ‘rules’ that catch issues that can potentially impact your SQL Server performance, we added quite a few reports. Some of the reports are displayed below. The following three were born out of troubleshooting experience. “Top 20 Active CPU Intensive Queries”: When troubleshooting CPU...

A user called in for help because he wasn’t able to drop a user from a database. The error message is below Msg 15136, Level 16, State 1, Line 2The database principal is set as the execution context of one or more procedures, functions, or event notifications and cannot be dropped. From the error, the...

There are multiple levels of throttling with Azure. You can get throttled at disk level, storage account level or VM/host level. These types of throttling can manifest into something that may not be that obvious. Recently we received a call from customer who was backing up databases from Azure VM to Azure blob storage. The...

Lately, we had a customer who contacted us for a performance issue where their server performed much worse in SQL Server 2016 following upgrade. To show us as an example, he even captured a video. In the video, he showed that the session that was compiling the query had multiple threads waiting on LATCH_EX of...

With so many users new to Azure, Sometimes an issue appears more complex than it really is. If you back up your databases to Azure blob storage but your company uses proxy servers for internet access, you will need to configure backuptoURL.exe.config per SQL Server Backup to URL Best Practices and Troubleshooting. We...

If you created an SQL Server VM via azure portal, there will be a section called “SQL Server Configuration” which was introduced via blog “Introducing a simplified configuration experience for SQL Server in Azure Virtual Machines”. Here is a screenshot of that setting. It allows you to configure various things like auto backup, patching or...

If you need to open up your SQL Server on an Azure VM to public internet access, you need to look no further than this document Connect to a SQL Server Virtual Machine on Azure (Resource Manager). It has very detailed step-by-step instructions. On a very high level, here are steps In your VM, create...

Recently we got a customer who called in and wanted to know why he received NULL for query_plan when querying sys.dm_exec_query_plan. This customer referenced a blog from https://dzone.com/articles/dmexecqueryplan-returning-null. In that scenario, you will get NULL for query_plan if there are any statements involving temp tables that have not been executed for the first time. For...