The CATALOG Table
The default CATALOG database is $ARC (or $NETVAULT_CATALOG when using NetVault). It must be created and appropriate access privileges must be granted before the first use of the CATALOG runtime parameter.
Catalog information for all archive jobs is kept in the one CATALOG table. To continue using the previous multi-table implementation of CATALOG, specify the OLDCATALOG parameter in addition to the CATALOG parameter. Using old catalog tables during RESTORE or COPY is valid, even if OLDCATALOG is not specified. ARCMAIN searches for a table with the old naming style, and uses it if one exists.
Example
For UEN 1234, the following table is automatically created at the beginning of an archive operation:
$ARC.CATALOG_1234
If an error occurs when creating the CATALOG table, Teradata ARC terminates with a fatal error. Correct the error and resubmit the archive job.
During an archive operation, a CATALOG table row is inserted at the following instances:
The CATALOG tables can be used for detailed archive history in conjunction with the database DBC.RCEvent table. For information on the database DBC.RCEvent table, see the Data Dictionary.
Changing the Primary Index in the CATALOG Table
In previous versions of Teradata ARC, CATALOG tables were created with inefficient primary indexes that sometimes caused rows to be skewed on a limited number of AMPS. To correct this, follow these steps to change the primary index of an existing catalog table.
Note: If a new catalog table is created by Teradata ARC, these steps are not necessary.
CREATE TABLE CATALOGNEW AS CATALOG WITH NO DATA;
ALTER TABLE CATALOGNEW
MODIFY PRIMARY INDEX(EVENTNUM, DATABASENAME, TABLENAME);
INSERT INTO CATALOGNEW SELECT * FROM CATALOG;
DROP TABLE CATALOG;
RENAME TABLE CATALOGNEW AS CATALOG;