XMLW_31026Fatal error opening file <file name> for XML output.
Cause:The XML Writer failed to open the file. Some reasons could be that the file did not have write permissions. The path to the file is incorrect.
Action:Check file write permissions, directory path, disk space, and that the file exists.XMLW_31027Fatal error closing XML output file <file name>. System error message is <message>.
Cause:The XML Writer could not close the XML output file. Some reasons could be that the file did not have write permissions. The path to the file is incorrect.
Action:Check the operating system message for more information.XMLW_31029Cannot locate XML init/deinit functions in the DLL <.dll file name>.
Cause:The XML .dll file does not contain the initialization and deinitialization functions.
Action:Verify that the .dll file is the correct file shipped with the product. If it is incorrect, contact Informatica Technical Support.

XMLW_31030FK field <field name> for group <group name> has to be projected, i.e. there has to be an input field for it.
Cause:The foreign key must be connected in the mapping.
Action:Check that the mapping and that the foreign key are connected. Contact Informatica Technical Support.
or
Cause:The target is not defined as a flat file or XML target. It is an undefined object.
Action:Contact Informatica Technical Support.XMLW_31040Field <field name> of the *ROOT* XML group <group name> is projected while the PK field is not.
Cause:Internal error. If the Primary Key is not connected, none of the fields must be connected. If the Primary Key is connected, other fields may be connected.
Action:Validate the mapping and run the session again. Or contact Informatica Technical Support.

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.

With codeplex shutting down, we have moved SQL Nexus to github with a new release (6.0). Now both Pssdiag/SQLDiag manager and SQL Nexus are on github. Where to get it As you navigate to SQL Nexus, you can download code and released binary files. If you choose to download binary files, you can go to...

SQL Server : large RAM and DB Checkpointing Hi everyone, This post’s purpose is to establish a summary of the specific behaviors with relation to DB Checkpoint that may happen within SQL Server when running with a large quantity of allocated memory and when applicable, how to best address them. SQL Server 2016 improves...

Recently we got an inquiry from a customer who received the following message in errorlog and wanted to know why. [INFO] HkDatabaseTryAcquireUserMemory(): Database ID: [7]. Out of user memory quota: requested = 131200; available = 74641; quota = 34359738368; operation = 1. This is my first time to see this error. As usual, I relied...

Recently I assisted on a customer issue where customer wasn’t able to alter a memory optimized table with the following error Msg 41317, Level 16, State 3, Procedure ddl, Line 4 [Batch Start Line 35]A user transaction that accesses memory optimized tables or natively compiled modules cannot access more than one user database or databases...

In a previous blog, I talked about memory optimized table consumes memory until end of the batch. In this blog, I want to make you aware of cardinality estimate of memory optimized table as we have had customers who called in for clarifications. By default memory optimized table variable behaves the same way as...

I worked on an interesting issue today where a user couldn’t restore a backup. Here is what this customer did: backed up a database from an on-premises server (2008 R2) copied the file to an Azure VM tried to restore the backup on the Azure VM (2008 R2 with exact same build#) But he got...

Recently, I looked an In-Memory OLTP issue with Principal Software Engineer Bob Dorr who is still my office neighbor. After restoring a database that had just one memory optimized table, we dropped the table. Even without any memory optimized tables,number of checkpoint files keep going up every time we issue a checkpoint. For a while,...

In this blog Added per-operator level performance stats for Query Processing, Senior PM in QP talks about extending operator level performance stats. They include stats related to reads, CPU and elapse time. These are very helpful to track down query performance issues. We worked on recent case where we put ActualElapsedms in a good...

In blog “Importance of choosing correct bucket count of hash indexes on a memory optimized table”, I talked about encountering performance issues with incorrect sized bucket count. I was actually investigating an out of memory issues with the following error. Msg 701, Level 17, State 103, Line 11There is insufficient system memory in resource pool...

I was working with a customer to troubleshoot memory optimized table issues. In this scenario, our customer uses a memory optimized table variable. He put 1 million rows of data into the table variable and then process it. Based on what he said, I tried to come up with a repro to see if...