Dropped, Renamed, or Replaced Objects - Analytics Database - Teradata Vantage

SQL Data Manipulation Language

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2024-04-05
dita:mapPath
pon1628111750298.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
esx1472246586715
lifecycle
latest
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.