loadpkg Stored Procedure - Advanced SQL Engine - Teradata Database

Purpose

Use the loadpkg stored procedure to retrieve scripts that you can use to restore a specific version of a package.

To generate the scripts, loadpkg uses the information that was stored in the demddl and dempart system tables by a previous call to savepkg.

Definition

REPLACE PROCEDURE loadpkg
   (IN  U_Name     VARCHAR(30),
    IN  U_Version  VARCHAR(30),
    IN  U_Database VARCHAR(30),
    IN  U_Machine  VARCHAR(30),
    IN  U_InfoType VARCHAR(30),
    OUT script     CLOB
   )

where:

U_Name

Name of the package.

The package name that you specify here must be the same as a package name that you passed in a previous call to savepkg.

U_Version

the version of the package.

The version that you specify here must be the same as a version that you passed in a previous call to savepkg.

U_Database

the name of the database in which the package is installed.

The database name that you specify here must be the same as a database name that you passed in a previous call to savepkg.

U_Machine

the identifier associated with the Teradata server.

The U_Machine identifier is the same identifier you use to log on to the Teradata server.

U_InfoType

the type of contents that loadpkg returns in the script OUT argument. The valid values are:

• 'DDL', which specifies to return the DDL statements required to load the package into the database.
• 'PART', which specifies to return the lobteq commands to retrieve all of the files associated with the package from the SYSLIB tables.

script

DDL statements or lobteq commands, where the contents depend on the value of the U_InfoType IN argument.