The external procedure is to be recompiled.
Teradata Database recompiles the procedure and generates a new library for it.
For Java external procedures, the JAR file referenced in the EXTERNAL NAME clause is redistributed to all affected nodes on the system. This is useful for the case of a missing JAR file on a given node.
- Teradata Database recompiles the procedure but does not generate a new library.
- You cannot specify this for Java external procedures. Teradata Database does not distribute a new dynamic linked library to database nodes.
- When you load an external procedure onto another platform of a different type, the system marks it as not valid, and it must be recompiled. If there are many external procedures in one database, it saves time to specify the ONLY option for all recompilations to avoid having to generate and distribute a new library, until the last one is compiled in that database leaving off the ONLY option.
Example: Recompiling an External Procedure
This example recompiles the C-language external procedure named my_xsp.
ALTER PROCEDURE my_xsp LANGUAGE C COMPILE;