Fixing Stored Procedures - Teradata Database

Teradata Database Node Software Migration Guide

Product
Teradata Database
Release Number
15.10
Published
November 2017
Language
English (United States)
Last Update
2018-04-25
dita:mapPath
heq1467819788761.ditamap
dita:ditavalPath
5942_Migrating_1510.ditaval.ditaval
dita:id
B035-5942
lifecycle
previous
Product Category
Software

The migration process automatically recompiles stored procedures if the corresponding source code exists. Running the pre_upgrade_prep.pl generates the sp_nospllist.txt report, which lists stored procedures that were not saved with their source code and must, therefore, be recreated.

The SPL option to CREATE/ALTER PROCEDURE causes the procedure source text (SQL and procedural code) to be stored in the database. Stored procedures can be created without SPL for several reasons, but in general this is done to prevent unauthorized modifications, replication,, or distribution of the source code. Teradata stored procedures created without SPL can usually be recreated by executing an appropriate DIP script. Stored procedures without SPL provided by third party vendors may require re-installing a software package, and possibly assistance from the vendor.

Stored procedures need to be recompiled only for major upgrades.

  1. View the sp_nospllist.txt report.
    The report provides stored procedure names in ASCII text and in hexint forms.

  2. Recreate each listed stored procedure.