Troubleshooting Informatica Error Messages and Resolution – Part 12

Connections from a MQ source cannot be modified.
Cause:You tried to modify the connections from the MQSeries source to the MQ Source Qualifier.
Action:None. You cannot modify the connections from the MQSeries source to the MQ Source Qualifier.

VSAM, XML, MQ sources connect to exactly one source qualifier transformation.
Cause:You tried to connect an MQSeries, VSAM, or XML source definition to more than one Source Qualifier or Normalizer transformation. This action is not allowed.
Action:Do not connect an MQSeries, VSAM, or XML source definition to more than one Source Qualifier or Normalizer transformation.
Unable to delete links from an MQ source to an MQ Source Qualifier transformation.
Cause:You tried to delete the link between the MQSeries source definition and the MQ Source Qualifier.
Action:None. You cannot delete links between the MQSeries source definition and the MQ Source Qualifier.

Unable to delete links from an MQ Source Qualifier transformation to an associated source qualifier transformation.
Cause:You tried to delete the link between MQ Source Qualifier and the associated source qualifier.
Action:To delete the link, remove the association between the MQ Source Qualifier and the associated source qualifier in the Edit Transformation dialog box of the MQ Source Qualifier.
Cannot link to MsgId port.
Cause:You tried to link a non-MsgId port to a MsgId port.
Action:None. You cannot link a non-MsgId port to a MsgId port.

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.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Informatica Error Code Messages or Warning Messages on Windows and Linux Operating Systems.

 

SQL Server Errors or Failures from Error: 22511 to Error: 22530

SQLServerF1

 

Error: 22511, Severity: 16, The merge completed successfully.
Error: 22512, Severity: 16, Cannot use partition groups with unfiltered publications. Set “use_partition_groups” to “false” using sp_changemergepublication.
Error: 22513, Severity: 16, Cannot use partition groups because the join filter between the following articles contains one or more functions: “%s” and “%s”.
Error: 22514, Severity: 16, Cannot use partition groups because one or more filters reference the following view, which contains functions: “%s”.

Error: 22515, Severity: 16, The publication cannot use precomputed partitions because there is at least one circular reference in the join filters specified for the articles in the publication. To use precomputed partitions, ensure that no circular join filter relationships exist.
Error: 22516, Severity: 16, The publication “%s” was defined as having dynamic filters, but it does not contain any dynamic filters.
Error: 22517, Severity: 16, The publication was defined as having no dynamic filters, but contains one or more dynamic filters.

Error: 22518, Severity: 16, Cannot use column of type image, ntext, xml, CLR type, varchar(max), nvarchar(max), or varbinary(max) in a subset or join filter for article: ‘%s’.
Error: 22519, Severity: 16, Cannot add a logical record relationship between tables “%s” and “%s” because a text, image, ntext, xml, varchar(max), nvarchar(max), or varbinary(max) column was referenced in the join clause.
Error: 22520, Severity: 10, A filtering type changed for the article. Any pending or future changes made in this article by a Subscriber in a given partition will no longer be propagated to Subscribers in other partitions. Check the documentation for details.
Error: 22521, Severity: 10, Unable to synchronize the row because the row was updated by a different process outside of replication.
Error: 22522, Severity: 16, Article ‘%s’ cannot be published because it is published in another merge publication. An article that has a value of 3 for the @partition_options parameter of sp_addmergearticle (nonoverlapping partitions with a single subscription per partition) cannot
Error: 22523, Severity: 16, An article cannot use @partition_options 2 or 3 (nonoverlapping partitions) and be a part of a logical record relationship at the same time. Check article “%s”.
Error: 22524, Severity: 16, Article ‘%s’ is published in another merge publication, with a different value specified for the @partition_options parameter of sp_addmergearticle. The specified value must be the same in all merge publications. Either specify the same value as the exist
Error: 22525, Severity: 16, The publication “%s” cannot allow multiple subscriptions per partition if it contains articles using @partition_options = 3.
Error: 22526, Severity: 16, An invalid value was specified for %s. Valid values are 0 (none), 1 (enforced partitions), 2 (nonoverlapping partitions with multiple subscriptions per partition), and 3 (nonoverlapping partitions with single subscription per partition).
Error: 22527, Severity: 16, Invalid value specified for %s. Valid values are ‘day’, ‘days’, ‘dd’, ‘year’, ‘years’, ‘yy’, ‘yyyy’, ‘month’, ‘months’, ‘mm’, ‘week’, ‘weeks’, ‘wk’, ‘hour’, ‘hours’, ‘hh’, ‘minute’, ‘minutes’, ‘mi’.
Error: 22528, Severity: 16, Cannot use a retention period unit other than “days” for publication “%s” because the compatibility level of the publication is lower than 90. Use sp_changemergepublication to set publication_compatibility_level to 90RTM.
Error: 22529, Severity: 16, Cannot change the retention period unit for publication “%s” because the compatibility level of the publication is lower than 90. Use sp_changemergepublication to set publication_compatibility_level to 90RTM.
Error: 22530, Severity: 16, Cannot update any column in article “%s” that is used in a logical record relationship clause.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures from Error: 7664 to Error: 7685

SQLServerF1

 

Error: 7664, Severity: 16, Full-text change tracking must be started on table or indexed view ‘%.*ls’ before the changes can be flushed.
Error: 7665, Severity: 16, Full Crawl must be executed on table or indexed view ‘%.*ls’. Columns affecting the index have been added or dropped since the last index full population.
Error: 7666, Severity: 16, User does not have permission to perform this action.
Error: 7668, Severity: 16, Cannot drop full-text catalog ‘%ls’ because it contains a full-text index.
Error: 7669, Severity: 10, Warning: Full-text index for table or indexed view ‘%.*ls’ cannot be populated because the database is in single-user access mode. Change tracking is stopped for this table or indexed view.

Error: 7670, Severity: 16, Column ‘%.*ls’ cannot be used for full-text search because it is not a character-based, XML, image or varbinary(max) type column.
Error: 7671, Severity: 16, Column ‘%.*ls’ cannot be used as full-text type column for image column. It must be a character-based column with a size less or equal than %d characters.
Error: 7672, Severity: 16, A full-text index cannot be created on the table or indexed view because duplicate column ‘%.*ls’ is specified.
Error: 7673, Severity: 10, Warning: Full-text change tracking is currently disabled for table or indexed view ‘%.*ls’.
Error: 7674, Severity: 10, Warning: The fulltext catalog ‘%.*ls’ is being dropped and is currently set as default.
Error: 7676, Severity: 10, Warning: Full-text auto propagation is on. Stop crawl request is ignored.

Error: 7677, Severity: 16, Column “%.*ls” is not full-text indexed.
Error: 7678, Severity: 16, The following string is not defined as a language alias in syslanguages: %.*ls.
Error: 7679, Severity: 16, Full-text index language of column “%.*ls” is not a language supported by full-text search.
Error: 7680, Severity: 16, Default full-text index language is not a language supported by full-text search.
Error: 7681, Severity: 10, Warning: Directory ‘%ls’ does not have a valid full-text catalog. Full-text catalog header file or attach state file either is missing or corrupted. The full-text catalog cannot be attached.
Error: 7682, Severity: 10, The component ‘%ls’ reported error while indexing. Component path ‘%ls’.
Error: 7683, Severity: 16, Errors were encountered during full-text index population for table or indexed view ‘%ls’, database ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’). Please see full-text crawl logs for details.
Error: 7684, Severity: 10, Error ‘%ls’ occurred during full-text index population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’), full-text key value ‘%ls’. Failed to index the row.
Error: 7685, Severity: 10, Error ‘%ls’ occurred during full-text index population for table or indexed view ‘%ls’ (table or indexed view ID ‘%d’, database ID ‘%d’), full-text key value ‘%ls’. Attempt will be made to reindex it.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures from Error: 6816 to Error: 6839

SQLServerF1

 

Error: 6816, Severity: 16, In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, and NMTOKENS attributes cannot be generated as CDATA, XML, or XMLTEXT in ‘%.*ls’.
Error: 6817, Severity: 16, FOR XML EXPLICIT cannot combine multiple occurrences of ELEMENT, XML, XMLTEXT, and CDATA in column name ‘%.*ls’.
Error: 6819, Severity: 16, The FOR XML clause is not allowed in a %ls statement.
Error: 6820, Severity: 16, FOR XML EXPLICIT requires column %d to be named ‘%ls’ instead of ‘%.*ls’.
Error: 6821, Severity: 16, GROUP BY and aggregate functions are currently not supported with FOR XML AUTO.
Error: 6824, Severity: 16, In the FOR XML EXPLICIT clause, mode ‘%.*ls’ in a column name is invalid.

Error: 6825, Severity: 16, ELEMENTS option is only allowed in RAW, AUTO, and PATH modes of FOR XML.
Error: 6826, Severity: 16, Every IDREFS or NMTOKENS column in a FOR XML EXPLICIT query must appear in a separate SELECT clause, and the instances must be ordered directly after the element to which they belong.
Error: 6827, Severity: 16, FOR XML EXPLICIT queries allow only one XMLTEXT column per tag. Column ‘%.*ls’ declares another XMLTEXT column that is not permitted.
Error: 6828, Severity: 16, XMLTEXT column ‘%.*ls’ must be of a string data type or of type XML.
Error: 6829, Severity: 16, FOR XML EXPLICIT and RAW modes currently do not support addressing binary data as URLs in column ‘%.*ls’. Remove the column, or use the BINARY BASE64 mode, or create the URL directly using the ‘dbobject/TABLE[@PK1=”V1″]/@COLUMN’ syntax.

Error: 6830, Severity: 16, FOR XML AUTO could not find the table owning the following column ‘%.*ls’ to create a URL address for it. Remove the column, or use the BINARY BASE64 mode, or create the URL directly using the ‘dbobject/TABLE[@PK1=”V1″]/@COLUMN’ syntax.
Error: 6831, Severity: 16, FOR XML AUTO requires primary keys to create references for ‘%.*ls’. Select primary keys, or use BINARY BASE64 to obtain binary data in encoded form if no primary keys exist.
Error: 6832, Severity: 16, FOR XML AUTO cannot generate a URL address for binary data if a primary key is also binary.
Error: 6833, Severity: 16, Parent tag ID %d is not among the open tags. FOR XML EXPLICIT requires parent tags to be opened first. Check the ordering of the result set.
Error: 6834, Severity: 16, XMLTEXT field ‘%.*ls’ contains an invalid XML document. Check the root tag and its attributes.
Error: 6835, Severity: 16, FOR XML EXPLICIT field ‘%.*ls’ can specify the directive HIDE only once.
Error: 6836, Severity: 16, FOR XML EXPLICIT requires attribute-centric IDREFS or NMTOKENS field ‘%.*ls’ to precede element-centric IDREFS/NMTOKEN fields.
Error: 6838, Severity: 16, Attribute-centric IDREFS or NMTOKENS field not supported on tags having element-centric field ‘%.*ls’ of type TEXT/NTEXT or IMAGE. Either specify ELEMENT on IDREFS/NMTOKENS field or remove the ELEMENT directive.
Error: 6839, Severity: 16, FOR XML EXPLICIT does not support XMLTEXT field on tag ‘%.*ls’ that has IDREFS or NMTOKENS fields.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

SQL Server Errors or Failures from Error: 5310 to Error: 5331

SQLServerF1

 

Error: 5310, Severity: 16, Aggregates are not allowed in the VALUES list of an INSERT statement.
Error: 5311, Severity: 16, Invalid quote character ‘%lc’. A remote server or user command used an invalid quote character.
Error: 5312, Severity: 16, The input to the function ‘ntile’ cannot be bound.
Error: 5313, Severity: 16, Synonym ‘%.*ls’ refers to an invalid object.
Error: 5315, Severity: 16, The target of a MERGE statement cannot be a remote table, a remote view, or a view over remote tables.
Error: 5316, Severity: 16, The target ‘%.*ls’ of the MERGE statement has an INSTEAD OF trigger on some, but not all, of the actions specified in the MERGE statement. In a MERGE statement, if any action has an enabled INSTEAD OF trigger on the target, then all actions must have enab

Error: 5317, Severity: 16, The target of a MERGE statement cannot be a partitioned view.
Error: 5318, Severity: 16, In a MERGE statement, the source and target cannot have the same name or alias. Use different aliases for the source and target to ensure that they have unique names in the MERGE statement.
Error: 5319, Severity: 16, Aggregates are not allowed in a WHEN clause of a MERGE statement.
Error: 5321, Severity: 16, The ‘%ls’ function is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
Error: 5322, Severity: 16, An aggregate function is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
Error: 5323, Severity: 15, Subqueries are not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.

Error: 5324, Severity: 15, In a MERGE statement, a ‘%S_MSG’ clause with a search condition cannot appear after a ‘%S_MSG’ clause with no search condition.
Error: 5325, Severity: 15, The order of the data in the data file does not conform to the ORDER hint specified for the BULK rowset ‘%.*ls’. The order of the data must match the order specified in the ORDER hint for a BULK rowset. Update the ORDER hint to reflect the order in which
Error: 5326, Severity: 15, The data in the data file does not conform to the UNIQUE hint specified for the BULK rowset ‘%.*ls’. The data in the data file must be unique if the UNIQUE hint is specified for a BULK rowset. Remove the UNIQUE hint, or update the input data file to ensur
Error: 5327, Severity: 15, The column ‘%.*ls’ does not have a valid data type for the ORDER hint specified for data source ‘%.*ls’. The text, ntext, image, xml, varchar(max), nvarchar(max) and varbinary(max) data types cannot be used in the ORDER hint for a BULK rowset or CLR TVF.
Error: 5328, Severity: 15, Cannot insert explicit value for the identity column ‘%.*ls’ in the target table ‘%.*ls’ of the INSERT statement when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
Error: 5329, Severity: 15, Windowed functions are not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
Error: 5330, Severity: 16, Full-text predicates cannot appear in the OUTPUT clause.
Error: 5331, Severity: 16, Full-text predicates cannot appear in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.