Inspecting Pre-Processing Preparation Script Output - 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
The results of the pre-processing script are stored in the script output file. You must resolve any reported problems before continuing.

Each of the pre-processing checks performed by the script outputs results in the file named on the command line. For easy identification, results for each of the individual checks are preceded by an output line such as **** Checking for Reserved Words …

There are pre-processing checks for each of the following:

Script Check Description
Reserved Words Use of any reserved words in the user-defined tables and stored procedures.
DBQL Data Non-empty tables are reported because DBQL tables are not archived/restored.
Stored Procedures with No Source Code Stored procedures without source code cannot be recompiled on the destination system.
DBC Startup String

Check for a startup string assigned to user DBC.

Solution: Set StartupString to NULL for user DBC before the migration or upgrade because it may prevent logons after the version switch to the new release.

Identity Columns With Permanent Journal Data Check for the existence of an Identity Column Table that uses a permanent journal.

Solution: The permanent journal data must be moved to a non-identity column table before the migration or upgrade.

Triggers on TDWM.RULEBYPASS Check for triggers on the TDWM.RULEBYPASS table.

Solution: Any triggers on the TDWM.RULEBYPASS table MUST be removed before a migration or upgrade can be performed.

Orphaned Access Rights Check for orphaned accessrights rows in DBC.AccessRights.

Solution: Open an incident and assign it to the TGSC DBS Support group and attach the orphaned rows report file.

Statistics Access Rights Check for objects that need STATISTICS accessrights granted.

Solution: Execute the created script, grantstatsrights.bteq, before the migration or upgrade. If the grant rights script is run, it restores all of the default access rights associated with the QSTATS database. If custom access rights are required for this system, apply them manually.

When running the script, use the UTF8 character set, otherwise, error 3704 may occur. To run the script, logon and enter:

.SET SESSION CHARSET 'UTF8'
.RUN FILE=grantstatsrights.bteq
DBC Statistics Check for statistics on DBC tables which must be re-enabled after the migration or upgrade.

Solution: Execute the script, dbcstats.rpt, after the migration or upgrade to re-enable statistics collections on the DBC tables.

Storage Profiled Check if the storage has been profiled.

Solution: The migration type is set to ONE_DIMENSIONAL but storage has not been profiled. The storage must be profiled or the migration type must be set to TERADATA_TRADITIONAL prior to the migration or upgrade.

Geospatial Check for the external UDT (pre-13.0) version of Geospatial, the existence of which prevents installation of the Teradata-supplied (13.0) implementation of Geospatial as part of the upgrade due to related problems.

Solution: If you want to use the Teradata implementation of Geospatial, first uninstall the pre-13.0 version, in which case the Teradata supplied implementation of Geospatial installs as part of the migration or upgrade.

A summary section at the end of the report indicates whether the system is ready to proceed with the migration or upgrade based on the problems that are identified.

You can ignore any In-Doubt Transaction messages at this time. These transactions are part of the Replication operation and do not need to be corrected as part of the pre-processing script process. In-Doubt Transaction problems are corrected at another step in the process.