Explanation: | The Integration Service failed to create the partition driver for the Java transformation class. This error can occur due to inconsistent byte code in the repository. |
User Response: | Use the Designer to recompile the byte code for the Java transformation, and run the session again. |
Explanation: | The repository stores the code for the Java transformation in metadata extensions for the Java transformation. The Integration Service could not find the metadata extensions that correspond to the code for the Java transformation in the repository. This error can occur due to inconsistent metadata in the repository. |
User Response: | Use the Designer to save the Java transformation to the repository, and run the session again. Otherwise, contact Informatica Global Customer Support. |
Explanation: | The Integration Service could not retrieve the metadata for the input and output ports in the Java transformation from the repository. This error can occur due to inconsistent metadata in the repository. |
User Response: | Use the Designer to save the Java transformation to the repository, and run the session again. Otherwise, you need to re-create the repository. |
Explanation: | The Integration Service could not retrieve the metadata for the Java transformation because the column name is not valid. |
User Response: | None. |
Explanation: | The Java transformation contains more than one input group or output group. |
User Response: | Edit the Java transformation in the Designer and remove the extra group or groups. |
Explanation: | You used the setOutRowType API to set the output row type for the Java transformation. However, the specified row type is not valid. Valid row types are INSERT, DELETE, and UPDATE. |
User Response: | Change the row type for the setOutRowType API to a valid type. |
Explanation: | The Integration Service failed to create the partition driver for the Java transformation class. This error can occur due to inconsistent byte code in the repository. |
User Response: | Use the Designer to recompile the byte code for the Java transformation, and run the session again. |
Explanation: | Because the Integration Service could not retrieve the transformation name from the repository, the Integration Service failed to create the class loader for a Java transformation. |
User Response: | None. |
Explanation: | You used the failSession method to throw a fatal error in the Java transformation. |
User Response: | None. |
Explanation: | You used the logError method to write an error message to the session log for a Java transformation. |
User Response: | None. |
Explanation: | In a Java transformation, you passed a parameter with a value of NULL to an API method. However, parameters for APIs in a Java transformation cannot be NULL. |
User Response: | Modify the code for the Java transformation to pass a non-NULL parameter to the API method. |
Explanation: | The code in a Java transformation threw an error. This message occurs when the code throws an SDKException. |
User Response: | None. |
Explanation: | You used the specified API method in an active Java transformation. However, the transformation property was not selected. You must select the transformation property to use the API method in an active Java transformation. |
User Response: | Use the API method after you select the appropriate transformation property. |
Explanation: | You used the API method in a passive Java transformation, However, you cannot use the specified API method in a passive transformation. |
User Response: | To use the API method, create an active Java transformation. |
Explanation: | An unexpected error occurred at run time when the Java transformation tried to initialize the Java transformation input and output variables to the default values that you specified for the input and output ports for the Java transformation. |
User Response: | None. This error is an unexpected error that occurs at run time. If you specify an incorrect default value for any transformation field, that error is caught during validation of the mapping or the transformation. |
Explanation: | In the Java code for the transformation, the call to defineJExpression failed. |
User Response: | In the Designer, verify that the expression is valid and run the session again. |
Explanation: | You used a row type that is not valid in a Java expression. Valid row types are INSERT, DELETE, and UPDATE. |
User Response: | Use a valid row type. |
Explanation: | In a Java transformation, you used an expression that returned a NULL value. You cannot return NULL values from a Java expression. |
User Response: | Modify the expression in the Designer so it returns a non-NULL value. |
Explanation: | You passed a datatype that is not valid to an API method in a Java expression. |
User Response: | Modify the call to the API method to pass a valid datatype, or use the correct API method. |
Explanation: | The Java expression returned a datatype that is not valid. Valid datatypes are Integer, Double, String, and Byte[]. |
User Response: | Modify the Java expression to return a valid datatype. |
Explanation: | The Integration Service failed to fetch the session object from the repository. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | In a Java transformation, you passed a datatype that is not valid to an expression. The argument for the expression is a different type than the one you passed to the expression. |
User Response: | Pass the correct datatype to the expression. |
Explanation: | You passed a NULL value for the String parameter of a Java expression API method. The String parameter cannot take a NULL value. |
User Response: | Modify the call the Java expression API method to pass a non-NULL value to the String parameter. |
Explanation: | In a Java transformation, you did not pass the required number of parameters to an expression. |
User Response: | Edit the Java code for the transformation and pass the correct number of parameters to the expression. |
Explanation: | In an expression in a Java transformation, you passed more parameters than the expression requires. The Integration Service ignored the extra parameters. |
User Response: | None. If you do not want the Integration Service to ignore the extra parameters, redefine the Java expression. |
Explanation: | In a Java expression API method, you passed a NULL value to a parameter. You cannot pass NULL values for Java expression API method parameters. |
User Response: | Pass a non-NULL value to the parameter in the Java expression API method. |
Explanation: | The Integration Service could not load the Java transformation class or an inner class in a Java transformation. This error can occur if the repository contains inconsistent data for the byte code or the repository does not contain the updated byte code for the transformation. |
User Response: | Correct the error indicated in the error text in the message and run the session again. You might need to recompile the Java code for the transformation in the Designer. |
Explanation: | The initialization of a JExpression object failed. |
User Response: | Verify that the defined expression is valid and run the session again. |
Explanation: | The precision of the data assigned to a binary or string output port in a Java transformation is greater than the configured precision for the port. As a result, the Java transformation truncated the data for the port. This warning can occur for data assigned to an output port. |
User Response: | Make sure the precision of the port is equal to or greater than the precision of the data assigned to the port. |
Explanation: | The Designer or Integration Service encountered an internal error when retrieving the metadata extensions for the Java transformation. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Designer or Integration Service encountered an internal error when retrieving the Java code snippets for the transformation from the repository. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Designer or Integration Service encountered an internal error when retrieving the byte code for the transformation from the repository. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Designer or Integration Service encountered an internal error when retrieving the CRC value for the transformation from the repository. The Designer or Integration Service compares the current CRC value for the byte code to the CRC value stored in the repository to verify the byte code for the transformation. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The byte code for the transformation is not in the repository. |
User Response: | Compile the Java code for the transformation, and validate the transformation or mapping. |
Explanation: | The CRC value for the byte code retrieved from the repository does not match the CRC value stored in the repository. As a result, the transformation is not valid. |
User Response: | Compile the Java code for the transformation, and validate the transformation or mapping. |
Explanation: | The Java Runtime Environment cannot retrieve the object class for the class name in the byte code. This error can occur when the pmjtx.jar file in the server/bin/javalib directory contains inconsistent data. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Java Runtime Environment cannot find the Java method in the byte code for the transformation. This error can occur when the pmjtx.jar file in the server/bin/javalib directory contains inconsistent data. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Java Runtime Environment could not create an object for a Java transformation class. This error can occur when there is not enough memory available to the JRE when it runs the byte code for a Java transformation. |
User Response: | Make sure there is enough memory available and run the session again. |
Explanation: | The Java Runtime Environment could not create a global reference to a Java transformation class. This error can occur when there is not enough memory available to the JRE when it runs the byte code for a Java transformation. |
User Response: | Make sure there is enough memory available and run the session again. |
Explanation: | A Java expression created with the advanced interface uses the getLong API to get the result of an expression that does not return a Date or Time value. You can only use getLong to get the result of an expression with a Date or Time return value. |
User Response: | Use the getInt or getDouble API with the expression. |
Explanation: | The datatype of the argument passed to a Java expression is invalid. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Designer or Integration Service could not retrieve the value of the classpath for the Java transformation from the repository. This error can occur due to inconsistent data in the repository. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | The Designer or Integration Service could not retrieve the value of the precision mode for the Java transformation from the repository. This error can occur due to inconsistent data in the repository. |
User Response: | Contact Informatica Global Customer Support. |