Inspecting Stored Procedures - Teradata Database

Teradata Database Node Software Migration Guide

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

If any of the original Stored Procedures were compiled using the NOSPL option, the Source Program Language (SPL) text was not stored with the Stored Procedure. In such cases, the Stored Procedure cannot be recompiled and you must rewrite the Stored Procedure. We recommend not using the NOSPL option for this reason.

If stored procedures exist on the system, the automatic recompile process generates several output log files for inspection.

  1. In /var/opt/teradata/PUTTools/script_name_td_release , inspect each of the following output log files, and take the identified corrective action(s), if necessary.
    Recompile Output File Purpose Corrective Action
    spnorecomp.txt Lists all the stored procedures that failed to recompile for any reason. Review the spconvlog.out file to identify the cause of failure.
    spconvlog.out Lists the specific cause of error for each stored procedure.
    1. Correct any errors in the SPL that may be preventing the recompile.
    2. Manually recompile the stored procedure.
    sp_nospllist.txt Lists all the stored procedures that could not recompile because no SPL was stored with the procedure. Re-create the stored procedure and store the SPL text with the stored procedure.