Running Teradata ARC in a Multiple Hash Map (MAPS) Environment - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-01
dita:mapPath
utr1488824663491.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

When running Teradata ARC in a MAPS-enabled system (TD 16.10 or higher), Teradata ARC can only archive/restore objects contained in the Contiguous Hashmap (All-AMPs Contiguous MAP).

During archive, if Teradata ARC attempts to archive an object that is not in the ALL AMP Contiguous Map, the DBS will return a 9028 error which causes Teradata ARC to abort the archive job.
*** Failure 9028:Legacy BAR job does not support sparse maps or contiguous maps that are not on all amps
Before the archive job can be successfully rerun, the object(s) getting the 9028 error must be removed from the archive job. For database-level archive jobs, the object(s) can be removed from the archive operation by using the Exclude Tables clause in the Archive statement:
archive data tables (DB1) (exclude tables (t1)), release lock, file=archive;

If a database contains more than one object which does not belong to the All AMP Contiguous map, each object must be excluded before the database can be successfulyl archived.

To find all of the objects that do not belong to the All AMP Contiguous map, use the following SQL query:

select  d1.DatabaseName, 
        t1.TvmName (NAMED TableName)
from    dbc.BAR_Databases2V d1, dbc.BAR_Tables2V t1,
        dbc.BAR_MapsV m1, dbc.BAR_MapsV m2
where   ((d1.DatabaseId = t1.DatabaseId) and (m1.MapNo = t1.MapNo) and
         (m2.MapNo = 1 and (m1.ContiguousStartAmp <> m2.ContiguousStartAmp or 
          m1.NumberOfAmps <> m2.NumberOfAmps)))
order by 1,2;
If using BTEQ to execute the above query, enter .sidetitles on prior to the query to generate an output in a more readable format.

During restore or copy, only objects archived from the ALL AMP Contiguous Map can be restored or copied. When restored/copied, these objects will be placed in the DBS according to the ALL AMP Contiguous Map since there is no option to request a different Map.

When doing a Database-level restore/copy, if the target database contains any objects that do not belong to the All AMP Contiguous map, and you don't want the map definition to change, add an Exclude Tables clause to the restore/copy statement for those objects.

restore data tables (DB1) (exclude tables (t1)), release lock, file=archive;

The Exclude Tables clause is used to tell the DBS not to change the specified objects in the target database prior to starting the restore/copy operation. To find all of the objects in the target database that do not belong to the All AMP Contiguous map, use the SQL query shown above.