Drop Processes and Java External Procedures - Analytics Database - Teradata Vantage

SQL Data Definition Language Detailed Topics

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
2023-07-11
dita:mapPath
vuk1628111288877.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1184
lifecycle
latest
Product Category
Teradata Vantage™

After a DROP USER request has been processed successfully, and before returning its status to the client application, the UDF symbol cache must be spoiled. This is done as part of the dictionary cache spoiling process. Because you must successfully submit a DELETE USER request before you can submit the DROP USER request, these actions will have already occurred. See DELETE USER.

In conjunction with the DROP USER operation, the following actions are taken on the appropriate dictionary tables:

  1. The system checks DBC.Jar_Jar_Usage to determine if any JARs in the user to be deleted are in the SQL-Java path of another JAR.

    If so, the request aborts and the system returns an error to the requestor.

  2. Delete all rows in DBC.Jar_Jar_Usage where the value for the JarDatabaseId column matches the ID of the user to be deleted.
  3. Delete all rows in DBC.Routine_Jar_Usage where the value for the DatabaseId column matches the ID of the user to be deleted.
  4. Delete all rows in DBC.Jars where the value for the DatabaseId matches the ID of the user to be deleted.