This can happen when PowerExchange Client for PowerCenter plug-ins are installed but cannot be loaded for various reasons like incorrect releases of PowerExchange installed or PATH problems. For more information, see Informatica Knowledge Base Article # 15346.

Use the DSPRDBDIRE command to see a list of databases on the i5/OS machine.

You can receive this error on UNIX when there is no PWX_HOME environment variable set to the PowerExchange installation directory. Set the PWX_HOME environment variable to the PowerExchange installation directory.

This can occur if EOF=Y is specified in the PowerExchange configuration file (dbmover.cfg) CAPI_CONNECTION statement. When you set EOF=Y, PowerExchange returns an EOF (which stops the session) when it reaches the end of the change stream as determined at the time the session starts reading from it. As a result, the PowerCenter session completes instead of continuing to run.

This message can also occur if the connection with PowerExchange is stopped through the PowerExchange STOPTASK command.

You can configure the PowerCenter Integration Service to process master and detail pipelines sequentially. As a result, it reads data from each source in change and real-time modes sequentially.

Clear the PMServer 6.X Joiner Source Order Compatibility option on the Compatibility and Database tab in the Informatica Server Setup. When you rerun the session, the PowerCenter Integration Service will process pipelines concurrently.

This is a generic message indicating the PWXPC encountered an error. Review the session log for other messages indicating what the problem is. If there are no other error messages in the session log, check the PowerExchange logs on both the PowerCenter Integration Service platform and the Listener platform.

When you use PowerExchange ODBC to read captured changes, INSERT is the default operation. If you want to apply the changes to the target by using the same operation as done on the source (INSERT, UPDATE, or DELETE), you need to explicitly include an Update Strategy transformation in the mapping to make this happen by testing the DTL__CAPXACTION field. In the Update Strategy Expression field, you would code:

When you use PWXPC, the DTL__CAPXACTION field is automatically acted upon when processing change data. If you want to have all changes processed as INSERTs regardless of the DTL__CAPXACTION field, you must code an update strategy specifying DD_INSERT in the Update Strategy Expression field.