Dropped, Renamed, or Replaced Objects - Teradata Database - Teradata Vantage NewSQL Engine

SQL Data Manipulation Language

Product
Teradata Database
Teradata Vantage NewSQL Engine
Release Number
16.20
Published
March 2019
Language
English (United States)
Last Update
2019-05-03
dita:mapPath
fbo1512081269404.ditamap
dita:ditavalPath
TD_DBS_16_20_Update1.ditaval
dita:id
B035-1146
lifecycle
previous
Product Category
Teradata Vantage™

Consider the scenario when a procedure references another procedure that has been dropped or renamed.

If the called procedure X references another procedure Y, and Y is later dropped, renamed, or replaced before executing X, the following occurs:

Session Mode Condition Generated when X Submits an Internal CALL to Execute Y
ANSI Error
Teradata Failure

If Y is replaced, then its execution generates an error in ANSI session mode or a failure in Teradata session mode if the specified arguments are not compatible with the changed definition of Y.

The following cases cause an error or failure:
  • The number of call arguments is not equal to the number of parameters in the changed definition of Y.
  • The data type of the call arguments is incompatible with the changed parameters of Y.

These conditions also apply to the attributes of any referenced database objects.