Explanation: | Internal error. The PowerCenter repository contains inconsistencies. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Subject attribute in the application connection for TIBCO sources and targets is invalid. |
User Response: | Enter a valid subject name for the Subject attribute in the application connection for the TIBCO source or target. |
Explanation: | The ReplySubject value in the session properties is invalid. |
User Response: | Enter a valid reply subject name for the ReplySubject property in the session properties. |
Explanation: | A TIBCO target message contains an invalid subject. |
User Response: | Verify that the value for the subject for TIBCO target messages is valid. For more information about subject names, see the TIBCO documentation. |
Explanation: | Internal error. The PowerCenter repository contains inconsistencies. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. The PowerCenter repository contains inconsistencies. |
User Response: | Contact Informatica Global Customer Support. Enter a value for the Message Count session condition of at least -1. |
Explanation: | Internal error. The PowerCenter repository contains inconsistencies. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The CM name in the application connection for the TIBCO source or target is invalid. |
User Response: | Enter a valid CM name. |
Explanation: | Internal error. The PowerCenter repository contains inconsistencies. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Integration Service could not confirm the specified certified message. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | Some connected ports in the mapping have datatypes that are not compatible with the message data fields. |
User Response: | Modify the mapping to include datatypes that are compatible. |
Explanation: | The Integration Service could not pass all the data from one column to another. The specified value is too large for the column with the specified datatype. |
User Response: | Modify the datatype for the column in the mapping. |
Explanation: | The date value for the column is invalid. |
User Response: | Check the data. Make sure the data contains valid values for the date. |
Explanation: | The Integration Service could not pass all the data from one column to another. The Integration Service rejects the row if the precision of the output port is less than the precision of the input port. |
User Response: | Modify the mapping by changing the precision or datatypes of the ports so that the precision of the output port is greater than or equal to the precision of the input port. |
Explanation: | The data contained an invalid value for a column. |
User Response: | Check the data. Verify that the data contains values for the column, which are valid. |
Explanation: | The Integration Service could not pass all the data from one column to another. The data contains inconsistencies. The row was rejected. |
User Response: | Modify the mapping to include datatypes that are compatible. |
Explanation: | Some connected ports in the mapping have different datatypes. The input port has a larger datatype than the output port. As a result, the Integration Service could not pass all the data. |
User Response: | Modify the mapping so that the connected columns contain datatypes of a similar range. |
Explanation: | The Integration Service could not pass all the data from one column to another. The specified value is too large for the column with the specified datatype. |
User Response: | Modify the datatype for the column in the mapping. |
Explanation: | You passed invalid data to a column with the datatype msg. The Integration Service rejected the row. |
User Response: | Check the data. The TIBCO data should be of the datatype msg. |
Explanation: | The Integration Service could not read data from the specified field. |
User Response: | See the TIBCO documentation for information about fixing the error. |
Explanation: | The Integration Service could not convert the data for the specified field from one datatype to another. |
User Response: | See the TIBCO documentation for information about fixing the error. |
Explanation: | The Integration Service encountered an error while adding a message field to the TIBCO target definition. |
User Response: | See the TIBCO documentation for information about fixing the error. |
Explanation: | The Integration Service could not pre-register the specified subscriber. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | The Integration Service could not set the specified subject name for the current message. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | The Integration Service could not send the specified message. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | The Integration Service failed to initialize the session. The proper TIB/Rendezvous libraries are not installed. |
User Response: | Check the PowerExchange for TIBCO installation. Verify that TIB/Rendezvous is properly installed. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Integration Service cannot initialize a connection for the specified Source Qualifier transformation. The connection attributes may be invalid. |
User Response: | Verify the connection attributes for the Source Qualifier transformation in the Connection Object Definition dialog box. |
Explanation: | The Integration Service cannot initialize the session. Session properties for the source qualifier instance might be invalid. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service cannot initialize the session. Session properties for the source qualifier instance might be invalid. |
User Response: | Check the additional error message for more information. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The recovery cache folder in the session properties is invalid. |
User Response: | In the session properties, specify a recovery cache folder. |
Explanation: | The Integration Service could not configure recovery for the session. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service failed to cache the TIBCO message. The Integration Service might have written only part of the message to the recovery cache before the session failed. |
User Response: | Check the additional error message for more information. |
Explanation: | This is an informational message. The Integration Service truncated the last message in the cache. |
User Response: | None. |
Explanation: | The Integration Service could not truncate the last message in the cache. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service could not flush the cache. |
User Response: | Check the additional error message for more information. |
Explanation: | A column contains an incompatible datatype. |
User Response: | Check the additional error message for more information. |
Explanation: | The number of row errors exceeded the threshold in the Stop on Errors property in the session properties. |
User Response: | Fix the invalid message data. Increase the threshold in the session properties by specifying a higher number for Stop on Errors in the session properties. |
Explanation: | The Integration Service encountered an error connecting to TIBCO. The application connection attributes for the TIBCO source might be invalid. |
User Response: | Verify the application connection attributes for the TIBCO source. |
Explanation: | The network may be down. |
User Response: | Verify the network connection. |
Explanation: | The Integration Service could not commit messages to the target when it reached the session condition(s) you specified in the session properties. The session failed. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service encountered an error getting reading from TIBCO. There is a TIB/Rendezvous error. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service could not commit messages to the target at the end of the Real-time Flush Latency interval. The session failed. |
User Response: | Check the additional error message for more information. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | This is an informational message. You did not configure the session to run in real time. |
User Response: | If you want to run the session in real time, you must configure the session properties for real-time data extraction. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Integration Service could not read the cached message. The cache might contain inconsistencies. |
User Response: | Check the additional error message for more information. |
Explanation: | A field in the source definition contains the datatype msg. This datatype is incompatible with the TIB/Adapter SDK application connection. As a result, the session failed. |
User Response: | Remove any fields in the source definition with the datatype msg. To include the message metadata in this field, add the metadata as separate columns in the source definition. |
Explanation: | You attempted to run a session with a TIB/Adapter SDK application connection for the specified Source Qualifier transformation. However, the TIBCO source definition associated with the Source Qualifier contains the field Time Limit. As a result, the session failed. |
User Response: | Remove the Time Limit field from the source definition. |
Explanation: | The Integration Service cannot connect to TIB/Rendezvous. The application connection attributes for the TIBCO source or target may be invalid. |
User Response: | Verify the application connection attributes for the TIBCO source or target. |
Explanation: | The network may be down. |
User Response: | Check the network connection. |
Explanation: | TIB/Rendezvous might not be properly installed. |
User Response: | Verify the TIB/Rendezvous software installation. |
Explanation: | The Integration Service cannot set a default time limit for sending certified messages. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Integration Service could not create a message queue. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | The Integration Service could not create a listener to read messages. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | The Integration Service failed to set the specified reply subject name for the current message. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | The Integration Service could not set a time limit for the current message. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | The Integration Service could not open TIB/Rendezvous. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | The Integration Service could not create the TIB/Rendezvous transport. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | The Integration Service could not create an event queue, listener, or dispatch thread for advisory messages. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | The Integration Service could not set a limit policy for the event queue. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | The Integration Service could not create a message queue for message events. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | The Integration Service could not create a listener for advisory messages. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | The Integration Service could not create a dispatch thread for advisory messages. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | Fatal error. The system is out of memory. |
User Response: | Increase the system memory. Change the queue limit policy in the session properties. |
Explanation: | The TIB/Rendezvous license expires soon or expired on the specified date. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | The Integration Service did not receive confirmation for the specified message. If the time limit expired, the message may have been deleted. PowerCenter may not know if the message reached the subscriber. |
User Response: | Change the time limit policy in the session properties. Verify that the subscriber is running. |
Explanation: | Two subscribers or publishers on the same network have the same CmName. Each application must use a unique CmName. |
User Response: | Verify that each application on the network uses a unique CmName. See the TIBCO documentation for instructions to correct the error. |
Explanation: | TIB/Rendezvous cannot get the message sequence number. |
User Response: | See the TIBCO documentation for instructions to correct the error. |
Explanation: | The Integration Service could not write the message to the recovery cache. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service could not read the message from the recovery cache. |
User Response: | Check the additional error message for more information. |
Explanation: | The recovery cache contains inconsistencies. The session failed. |
User Response: | Manually delete the corrupted cache. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | You passed invalid data to a column with the datatype msg. The Integration Service rejected the row. |
User Response: | See the TIBCO documentation for information about fixing the error. |
Explanation: | The Integration Service encountered an error while trying to determine the number of fields in the TIB/Rendezvous message. |
User Response: | See the TIBCO documentation for information about fixing the error. |
Explanation: | The Integration Service could not start the session. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service could not initialize the session. |
User Response: | See the TIBCO documentation for information on fixing the error. |
Explanation: | The Integration Service could not initialize the session. |
User Response: | See the TIBCO documentation for information on fixing the error. |
Explanation: | The Integration Service could not initialize the session. |
User Response: | See the TIBCO documentation for information on fixing the error. |
Explanation: | The Integration Service could not read a TIBCO message in AE wire format. The session failed. |
User Response: | See the TIBCO documentation for information on fixing the error. |
Explanation: | The Integration Service could not start the specified adapter instance. As a result, the Integration Service could not initialize the session. |
User Response: | See the TIBCO documentation for information on fixing the error. |
Explanation: | The Integration Service could not initialize the session. |
User Response: | See the TIBCO documentation for information on fixing the error. |
Explanation: | The Integration Service could not process advisory messages. |
User Response: | See the TIBCO documentation for information on fixing the error. |
Explanation: | The Integration Service could not find the specified session in TIB/Repository. You may have entered an invalid session name in the TIB/Adapter SDK connection properties. |
User Response: | Verify the session name in the TIB/Adapter SDK connection properties. |
Explanation: | The Integration Service could not initialize the session. |
User Response: | See the TIBCO documentation for information on fixing the error. |
Explanation: | The Integration Service could not cache a message. |
User Response: | Check the additional error message for more information. |
Explanation: | The Integration Service could not a read a cached message during a recovery session. |
User Response: | Check the additional error message for more information. |
Explanation: | The session protocol for the TIB/Repository session you specified is invalid. The protocol must be RV or RVCM. |
User Response: | Set RV or RVCM as the session protocol in TIB/Adapter Administrator. For more information, see the TIBCO documentation. |
Explanation: | You selected Not Null for the specified field in the target properties. |
User Response: | From the Columns tab of the Edit Table properties for the target definition, clear the Not Null option for the field. |
Explanation: | The Integration Service could not initialize the writer properties for the specified target. The session failed. |
User Response: | Check the additional error message for more information. |
Explanation: | An attribute in the application connection for the TIBCO target is invalid. The session failed. |
User Response: | Check the additional error message for more information. |
Explanation: | Internal error. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Integration Service could not initialize the target. The session failed. |
User Response: | Check the additional error message for more information. |
Explanation: | Row error. Data overflow occurred in the specified field. |
User Response: | Use a larger datatype for the output field. For example, use int64 instead of int32. |
Explanation: | This is a warning message. The data for a string field was truncated. |
User Response: | Increase the precision of the output field. |
Explanation: | Internal error. The repository may contain inconsistencies. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The session properties contain pre-registered listeners for a TIBCO target. Also, the mapping contains a link to the SendSubject port in the target definition. This is not allowed. |
User Response: | Remove the link to the SendSubject port in the target definition to use the default subject. Remove the pre-registered listeners you specified in the session properties. |
Explanation: | A field in the target definition contains the datatype msg. This datatype is incompatible with the TIB/Adapter SDK application connection. As a result, the session failed. |
User Response: | Remove any fields in the source definition with the datatype msg. To include the message metadata in this field, add the metadata as separate columns in the target definition. |
Explanation: | You attempted to run a session with a TIB/Adapter SDK application connection for a TIBCO target. However, the TIBCO target definition contains the port Time Limit, which is linked with the Time Limit port in another transformation. As a result, the session failed. |
User Response: | Remove the link to the Time Limit port in the target definition. |
Explanation: | You selected a TIB/Adapter SDK application connection for a TIBCO target. However, the TIBCO target definition contains fields with the datatypes ipaddr32 and/or ipport16. This is not allowed. |
User Response: | Use the datatype string for fields with ipaddr32 or ipport16 datatypes. |