Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 12 Oct 2010 @ 15:15:52 GMT


     
  <Prev Next>   <<First <Prev Next> Last>>  


Subj:   Re: Can post_data_restore script be run at a table or database level
 
From:   Clark, Dave

Mark-

Here is an article that addresses your question. Let me know if you have further questions or comments.

-dave.clark


-----------------------------------------------------------

Short Description: Is it necessary to run post_data_restore after a cross-release restore of user tables?

Question:

The customer is using ARC to migrate user tables from one release to another. Following the restore operation, ARC issues the warning:

*** Warning ARC1257:A cross-release data restore requires that a Teradata SQL conversion script be run. The following steps must be performed:

1) Log in as user DBC, and execute the following SQL statement:

          CREATE MACRO DBC.DIPMarkNS60 AS (;);

2) Execute one of the following conversion scripts: post_data_restore.

The script post_data_restore requires that logon be disabled and the system quiesced. Is it necessary to run the script?

Note that the execution time can be prolonged if the site has an extensive number of UDTs/UDFs/XSPs/UDMs and/or JAVA objects but the worst case scenario has never been seen to exceed an hour.

This script performs a number of functions:

updates fields within the DBC tables to accurately reflect information regarding UDF/UDT/UDM s and Triggers sets up SYSLIB and generates system UDFs and XSP (dipdem) generates system User Defined Types (dipudt) generates Jar objects for Java External Objects (dipsqlj) re- makes the UDF library links (udfalter.pl) revalidates Partitioned Primary Indexes (ppireval.pl) recompiles all stored procedures (sp_mig.pl) redistributes JAR objects (jxspconv) It does not convert any data tables.

The script should be run following the migration of tables or objects. If a site is performing incremental migration, it is possible to defer the execution and only run it once as long as there is not an extended period between data migration. It should be run prior to handing the system over to production.



     
  <Prev Next>   <<First <Prev Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023