JAR_JAR_USAGE View - Teradata Vantage

Teradata® VantageCloud Lake

Deployment

VantageCloud

Edition

Lake

Product

Teradata Vantage

Published

January 2023

Language

English (United States)

Last Update

2024-04-03

dita:mapPath

phg1621910019905.ditamap

dita:ditavalPath

pny1626732985837.ditaval

dita:id

phg1621910019905

The JAR_JAR_USAGE view identifies each JAR owned by a given user or database on which other JARs defined on the system are dependent.

View Column Name	Description	Data Type	Format
DatabaseId	The identifier of the database or user in which the JAR identified by JarName is defined.	BYTE(4) NOT NULL	X(8)
JarName	The name designator for a JAR that depends on code from another JAR.	VARCHAR(128) UNICODE UPPERCASE NOT CASESPECIFIC NOT NULL	X(128)
PathJarName	The name designator for a JAR, which is in the SQL-Java path of the JAR identified by JarName. The SQL-Java path is the search path defined for a specific JAR. With a SQL-Java path defined, a method defined in a specific JAR (JAR A) may invoke a method which is defined in another JAR (JAR B), if JAR B (and all its classes) is contained in the SQL-Java path of JAR A. A SQL-Java path for a JAR can only be created, altered, or dropped using a call to SQLJ.Alter_Java_Path.	VARCHAR(128) UNICODE UPPERCASE NOT CASESPECIFIC NOT NULL	X(128)

The corresponding system tables for SQLJ.JAR_JAR_USAGE are: