RENAME PROCEDURE Usage Notes - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
ft:locale
en-US
ft:lastEdition
2024-12-11
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905

Locks and Concurrency

When an SQL procedure, is renamed, an EXCLUSIVE lock is placed on the procedure being renamed.

Qualifying an Object from Another Database

To rename an SQL procedure that is not contained in the same database or user as your current default database setting, you must qualify both the old and new names with the name of the containing database or user for the object.

You cannot change the immediate owner of the renamed object using this statement.

Character Set Issues for Renaming Procedures

If the UDF library for your database contains any objects with multibyte characters in their name, you cannot use a single-byte session character set to create a new UDF, method, or Java external procedure object even if the new object name contains only single-byte characters. Otherwise, the system returns an error to the requestor. Instead, use a multibyte session character set.