Troubleshoot a Full System Restore | Teradata DSA - 17.00 - 17.05 - Troubleshooting a Full System Restore - Advanced SQL Engine - Teradata Database

Teradata Vantageā„¢ - Advanced SQL Engine Node Software Migration Guide

Product
Advanced SQL Engine
Teradata Database
Release Number
17.00
17.05
Release Date
June 2020
Content Type
Administration
Configuration
Installation
Publication ID
B035-5942-170K
Language
English (United States)

If you have problems with a full system restore, try the following.

Verify the Media Server IP Addresses

  1. Ping the IP address from the media server to the database.
  2. Ping the IP address from the database to the media server.
  3. Trim any invalid or unused IP addresses.

post_dbc_restore Script Fails to Launch

If the restore works, but fails to launch the post_dbc_restore script, you receive a message similar to the following:
1079 Post dbc restore script not started. Please run the post_dbc_restore script manually with the following command: /opt/teradata/PUTTools/td17.xx.xx.xx/IUMB_scripts/post_dbc_restore -s -N -j 3 TDT5WSDB/'dbc',<dbc_password>.
In addition, the table SYSBAR.DSAConnectionsTbl is not repopulated and you receive a message similar to this:
1001   SQL Exception 3807 3807: DBCSQL Exception: Object 'SYSBAR.DSAConnectionsTbl' does not exist.  DSAConnectionsTbl INSERT failed.  All DSCs should activate system <system_name>

Follow these steps:

  1. Manually launch the post_dbc_restore script:

    /opt/teradata/PUTTools/td17.xx.xx.xx/IUMB_scripts/post_dbc_restore -s -N -j 3 TDT5WSDB/'dbc',<dbc_password>

  2. Repopulate the DSAConnectionsTbl:
    Interface Steps
    BAR Setup portlet Check the activation status of the destination system in the BAR Setup portlet and do one of the following:
    • If the destination system is configured and enabled, click Update for Selector: Update system selector for JMS messages
    • If the destination system is not configured, add the system and click Apply.
    Command line Check the activation status of the system:

    dsc list_components -t system and do one of the following:

    • If the destination system is configured and enabled, run this command:

      dsc config_systems -f configsystem.xml -s selector

    • If the destination system is not configured, add the system:

      dsc config_systems -f configsystem.xml where configsystem.xml is similar to the example shown in Full System Restore Using the Command Line.

  3. On the destination system, start DSMain from the Database Window (DBW) console supervisor screen by entering:

    start bardsmain -d DSCName , where DSCName is the unique name of your DSC server

Compile Errors Reported During a Restore

When restored by DSA, certain Teradata-provided stored procedures fail to recompile in the post_data_restore scripts. These procedures have dependencies that are not met until after DIPALL is run at the conclusion of the migration. You can can manually recompile them using ALTER statements after DIPALL completes.

These errors are detected by the DSC when it runs the post_data_restore scripts and it concludes with a Warning job status rather than Complete. Check the log file noted in the error message provided by the DSC. The errors flagged by the DSC for these issues will not interfere with the rest of the restore.

This example output file shows queries that failed in post_data_restore scripts but succeed after DIPALL.
 BTEQ -- Enter your SQL request or BTEQ command:
ALTER PROCEDURE "SYSLIB"."JSON_SHRED_BATCH_U" COMPILE;

ALTER PROCEDURE "SYSLIB"."JSON_SHRED_BATCH_U" COMPILE;

 *** Procedure has been altered.
 *** Total elapsed time was 1 second.


 BTEQ -- Enter your SQL request or BTEQ command:
ALTER PROCEDURE "SYSLIB"."JSON_SHRED_BATCH" COMPILE;

ALTER PROCEDURE "SYSLIB"."JSON_SHRED_BATCH" COMPILE;

 *** Procedure has been altered.
 *** Total elapsed time was 1 second.


 BTEQ -- Enter your SQL request or BTEQ command:
ALTER PROCEDURE "TD_SYSXML"."XSLT_SHRED_BATCH" COMPILE;

ALTER PROCEDURE "TD_SYSXML"."XSLT_SHRED_BATCH" COMPILE;

 *** Procedure has been altered.
 *** Total elapsed time was 1 second.


 BTEQ -- Enter your SQL request or BTEQ command:
ALTER PROCEDURE "TD_SYSXML"."AS_SHRED_BATCH" COMPILE;

ALTER PROCEDURE "TD_SYSXML"."AS_SHRED_BATCH" COMPILE;

 *** Procedure has been altered.
 *** Total elapsed time was 1 second.


 BTEQ -- Enter your SQL request or BTEQ command:
ALTER PROCEDURE "TD_SYSXML"."XSLT_SHRED" COMPILE;

ALTER PROCEDURE "TD_SYSXML"."XSLT_SHRED" COMPILE;

 *** Procedure has been altered.
 *** Total elapsed time was 1 second.


 BTEQ -- Enter your SQL request or BTEQ command:
ALTER PROCEDURE "TD_SYSXML"."XMLPUBLISH" COMPILE;

ALTER PROCEDURE "TD_SYSXML"."XMLPUBLISH" COMPILE;

 *** Procedure has been altered.
 *** Total elapsed time was 1 second.


 BTEQ -- Enter your SQL request or BTEQ command:
ALTER PROCEDURE "TD_SYSXML"."XMLPUBLISH_STREAM" COMPILE;

ALTER PROCEDURE "TD_SYSXML"."XMLPUBLISH_STREAM" COMPILE;

 *** Procedure has been altered.
 *** Total elapsed time was 1 second.


 BTEQ -- Enter your SQL request or BTEQ command:
ALTER PROCEDURE "LOCKLOGSHREDDER"."SP_LockLog_Shredder" COMPILE;

ALTER PROCEDURE "LOCKLOGSHREDDER"."SP_LockLog_Shredder" COMPILE;

 *** Procedure has been altered.
 *** Total elapsed time was 1 second.