The SQLJ system database contains 3 views defined by the ANSI SQL:2011 standard as well as five external procedures for handling JAR files. SQLJ, which is created by a DIP script, should be treated as if it were an extension to the system dictionary beneath the DBC database. You should never insert anything into, or delete anything from, the SQLJ database.
The DIP script that creates SQLJ and its components follows the pattern set by the Data Dictionary initialization process, which includes revoking all privileges that could result in modification of the views and external procedures contained within SQLJ.
The SQLJ database requires sufficient space for all of its required components, and its initial space allocation is determined based on that necessity.
The following 3 views are system-defined for reporting information about JAR files.
|SQLJ.Jar_Jar_Usage||Identifies each JAR owned by a given user or database on which other JARs defined on the system are dependent.|
|SQLJ.Jars||Identifies the installed JARs on the system that can be accessed by the current user or database.|
|SQLJ.Routine_Jar_Usage||Identifies the JARs owned by a given user or database on which external Java routines defined on the system are dependent.|
See Teradata Vantage™ - Data Dictionary, B035-1092 and Teradata Vantage™ - SQL External Routine Programming, B035-1147 for details about the definitions and usage of these views.
The following five external procedures are system-defined for maintaining JAR files. You must have the EXECUTE privilege on any of the procedures to be able to execute it.
|SQLJ.Alter_Java_Path||Changes the search path for Java classes across installed JAR files.|
|SQLJ.Install_Jar||Registers a JAR file and its classes with the database.
You must have either the CREATE EXTERNAL PROCEDURE or the CREATE FUNCTION privilege to be able to install JAR files.
|SQLJ.Replace_Jar||Replaces an installed JAR file.
You must have either the DROP PROCEDURE or the DROP FUNCTION privilege to be able to replace JAR files.
|SQLJ.Remove_Jar||Removes a JAR file and its classes from the database.
You must have either the DROP PROCEDURE or the DROP FUNCTION privilege to be able to remove JAR files.
|SQLJ.Redistribute_Jar||Redistributes an installed JAR file to all nodes on the system.
You must have either the DROP PROCEDURE or the DROP FUNCTION privilege on the current database to be able to redistribute JAR files.
See Teradata Vantage™ - SQL External Routine Programming, B035-1147 for details on the signatures and usage of these external procedures.