The script tests for several types of issues that can adversely prevent or halt the migration. The script outputs results for each type of check to the standard output. As the script runs, results for each of the individual checks are preceded by an output line such as **** Checking for Reserved Words ….
The script saves the results of each type of check to a separate output file in the directory where the script is located. Inspect these files and resolve any reported problems before continuing.
There are checks for each of the following types of items:
|Item Type||What the Script Checks||What You Must Do|
|Reserved Words||Use of any reserved words in the user-defined tables and stored procedures.||Remove reserved words from tables and procedures. For more information, see Working With Reserved Words.|
|DBQL Data||Non-empty tables are reported because DBQL tables are not archived/restored.||Copy DBQL table data to a user table, if you want to migrate the DBQL data to the destination system. For more information, see Saving DBQL Log Data.|
|Stored Procedures with No Source Code||Stored procedures without source code cannot be recompiled on the destination system.||Rewrite SQL procedures to include the WITH SPL option in order to store the source code in the database. For more information, see Fixing SQL Stored Procedures.|
|DBC Startup String||
Checks for a startup string assigned to user DBC. A startup string may prevent logons after the version switch to a new release.
|Set StartupString to NULL for user DBC before the migration or upgrade.|
|Identity Columns With Permanent Journal Data||Checks for the existence of an Identity Column Table that uses a permanent journal.||Move the permanent journal data to a non-identity column table before the migration or upgrade.|
|Triggers on TDWM.RULEBYPASS||Checks for triggers on the TDWM.RULEBYPASS table.||Remove any triggers on the TDWM.RULEBYPASS table before the migration or upgrade.|
|Orphaned Access Rights||Checks for orphaned rows in DBC.AccessRights.||Open an incident for Teradata Support and attach the orphaned rows report file.|
|DBC Statistics||Checks for statistics collection on DBC tables. Statistics collection must be re-enabled after the migration or upgrade.||The pre-migration script creates a dbcstats.rpt file that contains the COLLECT STATISTICS ON DBC.table_name found on the source system. These statements should be manually executed on the target system after migration to reinstate the statistics collection that occurred on the source system.|
|Storage Profiled||Checks whether the storage has been profiled.
The system storage must be profiled in order to use ONE_DIMENSIONAL data migration mediated by Teradata Virtual Storage.
|Prior to migration or upgrade, either profile the system storage or use the ctl utility to set the TVS migration type to TERADATA_TRADITIONAL.|
|Secure Zones||Checks for the use of secure zones on the source system.||See Secure Zone documentation in Teradata Vantage™ NewSQL Engine Security Administration, B035-1100.|
|PPI tables using hashbuckets function to define partition ranges.||Checks for PPI tables.||This is not supported as part of the migration. You must partition the tables differently prior to the migration.|
|Geospatial types||Checks for old geospatial type definitions which are not compatible with the latest geospatial types provided by Teradata.||In order to use the latest geospatial types and functionality provided by Teradata Vantage, you muse drop these old geospatial types.|
|HUT locks||Checks for any HUT locks that have not been released.||You must release the HUT lock manually.|
|Cnsrun||This check is used to detect whether there is something wrong with the way the system is configured that will cause problems with the migration.||You should examine the /etc/hosts file and resolve the inconsistencies.|
A summary section at the end of the report indicates whether the system is ready to proceed with the migration or upgrade.