Message Reference > E Message Codes > EXP Messages
  

EXP Messages

EXP_19007 Date function error.

Explanation:
An invalid argument was entered in a date function.
User Response:
Check the function syntax and enter a valid argument.

EXP_19108 The Integration Service failed to parse the date format <date format string>.

Explanation:
An invalid date format was entered in a date function.
User Response:
Check the function syntax and enter a valid date format string.

EXP_19138 The Integration Service failed to parse the date format <unit portion of date format>.

Explanation:
A date format was entered in a date function. Part of the date format string is invalid.
User Response:
Check the function syntax and enter a valid date format string.

EXP_19145 Invalid date value string: <date format string>.

Explanation:
The string argument provided to the TO_DATE function is invalid.
User Response:
Check the function syntax and enter a valid string argument.

EXP_19160 Failed to find version API <function name> in module <module name>.

Explanation:
The custom function developer did not implement the INFA_EXPR_GetPluginVersion function.
User Response:
The custom function developer needs to implement the function in the implementation file.

EXP_19161 Version API <function name> in module <module name> failed.

Explanation:
The custom function developer configured INFA_EXPR_GetPluginVersion to return INFA_FAILURE.
User Response:
The custom function developer needs to configure the function to return INFA_SUCCESS.
Explanation:
The custom function developer did not configure the plug-in version to be compatible with the Custom Function API version. The Custom Function API version includes major release number, minor release number, and patch number, such as 8.0.0.
User Response:
The custom function developer needs to configure the plug-in version in INFA_EXPR_GetPluginVersion to be compatible with the Custom Function API version.

EXP_19162 Module <module name> interface version <version number> is incompatible with framework version <version number>.

Explanation:
The custom function developer did not configure the plug-in version to be compatible with the Custom Function API version. The Custom Function API version includes major release number, minor release number, and patch number, such as 8.0.0.
User Response:
The custom function developer needs to configure the plug-in version in INFA_EXPR_GetPluginVersion to be compatible with the Custom Function API version.

EXP_19163 Failed to find module API <function name> in module <module name>.

Explanation:
The custom function developer did not implement the INFA_EXPR_ModuleGetUserInterface function.
User Response:
The custom function developer needs to implement the function in the implementation file.

EXP_19164 Module API <function name> in module <module name> failed.

Explanation:
The custom function developer configured the INFA_EXPR_GetPluginVersion function to return INFA_FAILURE.
User Response:
The custom function developer needs to configure the function to return INFA_SUCCESS.

EXP_19165 Module init for <function name> failed: <error message>.

Explanation:
The custom function developer configure module_init to return INFA_FAILURE.
User Response:
The custom function developer needs to configure the function to return INFA_SUCCESS.
Explanation:
The function failed for the reason specified in the additional error message.
User Response:
The custom function developer may need to correct the function syntax.

EXP_19166 Failed to find validation API <function name> in module <module name>.

Explanation:
The custom function developer did not implement INFA_EXPR_ValidateGetUserInterface.
User Response:
The custom function developer needs to implement the function in the implementation file.

EXP_19167 Failed to find function API <function name> in module <module name>.

Explanation:
The custom function developer did not implement INFA_EXPR_FunctionGetUserInterface.
User Response:
The custom function developer needs to implement the function in the implementation file.

EXP_19168 Failed to find function instance API <function name> in module <module name>.

Explanation:
The custom function developer did not implement INFA_EXPR_FunctionInstanceGetUserInterface.
User Response:
The custom function developer needs to implement the function in the implementation file.

EXP_19169 Module deinit for <function name> failed: <error message>.

Explanation:
The custom function developer configured module_deinit to return INFA_FAILURE.
User Response:
The custom function developer needs to configure the function to return INFA_SUCCESS.
Explanation:
The function failed for the reason specified in the additional error message.
User Response:
The custom function developer may need to correct the function syntax.

EXP_19170 Failed to get validation interface for <function name>.

Explanation:
The custom function developer configured INFA_EXPR_ValidateGetUserInterface to return INFA_FAILURE.
User Response:
The custom function developer needs to configure the function to return INFA_SUCCESS.

EXP_19171 Failed to get function interface for <function name>.

Explanation:
The custom function developer configured INFA_EXPR_FunctionGetUserInterface to return INFA_FAILURE.
User Response:
The custom function developer needs to configure the function to return INFA_SUCCESS.

EXP_19172 Failed to get function instance interface for <function name>.

Explanation:
The custom function developer configured INFA_EXPR_FunctionInstanceGetUserInterface to return INFA_FAILURE.
User Response:
The custom function developer needs to configure the function to return INFA_SUCCESS.

EXP_19173 Failed to initialize function for <function name>: <error message>.

Explanation:
The custom function developer configured function_init to return INFA_FAILURE.
User Response:
The custom function developer needs to configure the function to return INFA_SUCCESS.
Explanation:
The function failed for the reason specified in the additional error message.
User Response:
The custom function developer may need to correct the function syntax.

EXP_19174 Failed to deinitialize function for <function name>: <error message>.

Explanation:
The custom function developer configured function_deinit to return INFA_FAILURE.
User Response:
The custom function developer needs to configure the function to return INFA_SUCCESS.
Explanation:
The function failed for the reason specified in the additional error message.
User Response:
The custom function developer may need to correct the function syntax.

EXP_19175 Function validation for <function name> failed: <error message>.

Explanation:
The custom function developer configured the validation API to return INFA_FAILURE.
User Response:
The custom function developer needs to configure the function to return INFA_SUCCESS.
Explanation:
The custom function developer specified an invalid return datatype for the custom function.
User Response:
The custom function developer needs to specify a valid return datatype for the custom function.

EXP_19176 Failed to get process row API for <function name>.

Explanation:
The custom function developer did not set a pointer to processRow in INFA_EXPR_FunctionInstanceGetUserInterface.
User Response:
The custom function developer needs to set a pointer to processRow in INFA_EXPR_FunctionInstanceGetUserInterface.
Explanation:
The custom function developer did not implement processRow.
User Response:
The custom function developer needs to implement the function in the implementation file.

EXP_19177 Failed to initialize function instance for <function name>: <error message>.

Explanation:
The custom function developer configured fnInstance_init to return INFA_FAILURE.
User Response:
The custom function developer needs to configure the function to return INFA_SUCCESS.
Explanation:
The function failed for the reason specified in the additional error message.
User Response:
The custom function developer may need to correct the function syntax.

EXP_19178 Failed to deinitialize function instance for <function name>: <error message>.

Explanation:
The custom function developer configured fnInstance_deinit to return INFA_FAILURE.
User Response:
The custom function developer needs to configure the function to return INFA_SUCCESS.
Explanation:
The function failed for the reason specified in the additional error message.
User Response:
The custom function developer may need to correct the function syntax.

EXP_19179 Invalid datatype specified for return value.

Explanation:
The custom function developer specified an invalid return datatype for the custom function.
User Response:
The custom function developer needs to specify a valid return datatype for the custom function.

EXP_19180 Process row failed for function <function name>: <error message>.

Explanation:
The custom function developer configured processRow to return INFA_FAILURE.
User Response:
The custom function developer needs to configure the function to return INFA_SUCCESS.
Explanation:
The function failed for the reason specified in the additional error message.
User Response:
The custom function developer may need to correct the function syntax.

EXP_19181 Failed to get validation functions for <function name>.

Explanation:
The custom function developer did not implement one ore more of the following functions: validateFunction, getFunctionDescription, getFunctionPrototype, and DestroyString.
User Response:
The custom function developer needs to verify that these functions are implemented.

EXP_19182 User-defined function <user-defined function> has a cyclic dependency. Call stack is <call stack>.

Explanation:
The specified user-defined function contains a reference to itself in the expression syntax. Or, it contains another user-defined function which refers to it.
User Response:
Modify the user-defined function so that it does not refer to itself or to another user-defined function that refers to the user-defined function specified in the error message.

EXP_19183 User-defined function <user-defined function> uses an aggregator function.

Explanation:
The specified user-defined function contains an aggregator function in the syntax. This is not allowed.
User Response:
Remove the aggregator function from the function syntax.

EXP_19185 Compilation for the user-defined function <user-defined function> failed.

Explanation:
The Integration Service could not validate the user-defined function.
User Response:
Edit the user-defined function and make sure the function syntax is valid.
Check the additional error message for more information.

EXP_19186 <<Expression Fatal Error: user-defined function>> <token>: <error message>. <sub-expression>.

Explanation:
The Integration Service encountered an error while evaluating the expression in the user-defined function. For example, the Integration Service is calling a stored procedure but cannot access the database.
User Response:
See the additional error message for more information.

EXP_19187 <<Expression Error: user-defined function>> <token>: <error message>. <sub-expression>.

Explanation:
The Integration Service truncated an operand value because the precision is too low. The error message may provide more information about this error.
User Response:
Increase the precision.
Explanation:
Data overflow occurred for an integer value.
User Response:
Check the data values for the overflow. The error message may provide more information about this error.

EXP_19188 <<Expression Warning: user-defined function>> <token>: <error message>. <sub-expression>.

Explanation:
The Integration Service encountered an error converting between a COM and Informatica datatype. Either the external procedure attempted an invalid conversion, or a data overflow occurred.
User Response:
Check the session log for messages related to data overflow or invalid datatype conversions. If data overflowed, change the external procedure or mapping to accommodate the data. Otherwise, make sure the external procedure uses valid datatype conversions.

EXP_19189 Error in fetching metadata for the user-defined function <user-defined function>.

Explanation:
The Integration Service or PowerCenter Client cannot fetch metadata for the specified user-defined function.
User Response:
Close the repository connection and reconnect. Run the session again.
Verify that you are not trying to use a user-defined function that does not exist.

EXP_19190 Error: Argument mismatch for user-defined function <user-defined function>

Explanation:
The number of arguments in the user-defined function does not match the number of required arguments. The user-defined function may contain too many or too few arguments.
User Response:
Edit the user-defined function syntax to include the correct number of arguments.

EXP_19191 Argument name for expression must start with an x or an X.

Explanation:
The argument for the expression in not named correctly. The name of an argument for a Java expression must start with an x or X.
User Response:
Rename the argument.

EXP_19192 Argument number is too large.

Explanation:
The number in the argument name is too large. The number is larger than can be stored by an integer value.
User Response:
Reduce the number of arguments for the expression.

EXP_19193 Cannot get argument index from argument name.

Explanation:
You created a argument name or names for an expression, but did not correctly name the argument. Argument names for expressions must start with an x or X, followed by an integer (index) starting from 1. All arguments for an expression must be indexed in sequential order, such as x1, x2, x3.
User Response:
Rename the argument.

EXP_19194 Argument index <index number> exceeds the expected number of arguments, <number>, in the expression.

Explanation:
The expression contains an argument having an index greater then the expected number of arguments for the expression. For example, you created an expression that takes two arguments, but used an argument name x3 inside the expression. Instead, the expression should use x1 and x2.
User Response:
Use the correct number of arguments for the expression when you invoke the expression.

EXP_19195 Error: A non-callable user-defined function <user-defined function> is being called directly in the expression.

Explanation:
An expression contains a non-callable user-defined function. You may have manually entered the user-defined function in the expression syntax. Or, the expression contains a user-defined function which you modified to be non-callable.
User Response:
Edit the user-defined function to be callable. Or, remove the user-defined function from the expression.

EXP_19197 Error: The Designer cannot find function <function name>. The function name may be incorrect.

Explanation:
An expression contains a function that has an incorrect function name.
User Response:
Ensure that the function name is correct.

EXP_20010 Integration Service failed to parse the date format <date format>. Expected format is seconds and above.

Explanation:
An invalid date format was entered in the SYSTIMESTAMP function.
User Response:
Check the function syntax and enter a valid date format.

EXP_20011 Date function error. Expected format is seconds and above.

Explanation:
A variable port supplied an invalid date format to the SYSTIMESTAMP function.
User Response:
Check the variable port and make sure it supplies a valid date format.