Troubleshoot a Full System Restore | Teradata DSA - Troubleshooting a Full System Restore - BAR - Data Stream Architecture

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

1079 Post dbc restore script not started. Please run the post_dbc_restore script manually with the following command:
/opt/teradata/PUTTools/td17<version>/IUMB_scripts/post_dbc_restore -s -N -j 3 TDT5WSDB/'dbc',<dbc_password>.

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<version>/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

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.

The following commands will recompile the stored procedures after DIPALL has been run.

• ALTER PROCEDURE "SYSLIB"."JSON_SHRED_BATCH_U" COMPILE;
• ALTER PROCEDURE "SYSLIB"."JSON_SHRED_BATCH" COMPILE;
• ALTER PROCEDURE "TD_SYSXML"."AS_SHRED_BATCH" COMPILE;
• ALTER PROCEDURE "TD_SYSXML"."XSLT_SHRED" COMPILE;
• ALTER PROCEDURE "TD_SYSXML"."XSLT_SHRED_BATCH" COMPILE;
• ALTER PROCEDURE "TD_SYSXML"."XMLPUBLISH" COMPILE;
• ALTER PROCEDURE "TD_SYSXML"."XMLPUBLISH_STREAM" COMPILE;
• ALTER PROCEDURE "LOCKLOGSHREDDER"."SP_LockLog_Shredder" COMPILE;

Warning When the Database Exceeds Logical Space Limit

When the database exceeds its logical space limit while doing a restore operation, warning messages may appear. You can ignore the messages as the restore does not fail. However, when the restore is complete, you must modify the perm space to add objects to the database or to add new rows to the tables.

The warning message looks like this:

Warning code   Warning message
-------------------------------------------------------------------------------
1196           Database <database_name> has exceeded it's logical space limit.