CATALOG provides direct tape positioning for restore and copy operations when a table or a database is archived with the CATALOG runtime parameter enabled.
where:
Syntax Element |
Definition |
CATALOG or CTLG |
Enables CATALOG at the table level for ARCHIVE, RESTORE/COPY and/or ANALYZE statements |
CATALOGALLTABLES or CTLGALL |
Synonyms for CATALOG |
CATALOGOBJONLY or CTLGOBJ |
Enables CATALOG at the object level for ARCHIVE, RESTORE/COPY and/or ANALYZE statements |
CATALOGFILE or CTLGFILE |
Enables CATALOG to write all catalog information to a file on the client machine The default file name for the catalog is 'CATALOG' on mainframe systems, and 'CATALOG_<uen>.CTG' on other systems, where <uen> is the Utility Event Number for the archive job. |
OLDCATALOG or OLDCTLG |
When specified, along with CATALOG, enables use of the multi-table implementation of CATALOG, instead of the single-table method which does not create a new table for each ARCHIVE |
NOCATALOG or NOCTLG |
Disables CATALOG for ARCHIVE, RESTORE/COPY and/or ANALYZE statements |
CATALOGFILENAME or CTLGFILE |
Enables changing the file name for the catalog |
NOCATALOGFILE or NOCTLGFILE |
Disables CATALOGFILE so that catalog information is not created during ARCHIVE, and not used during RESTORE or COPY |
The following syntax is not supported:
CATALOG has two levels of granularity: OBJECT and ALL tables. If CATALOG is specified at the object level, the repositioning information is inserted into the CATALOG table for the database header record only.
Change the database in which the CATALOG table is created by adding this runtime parameter:
CATALOGDB=dbname
If CATALOGDB is not specified, Teradata ARC uses $ARC as the default CATALOG database.
Catalog information is saved in the database, therefore CATALOG enabled has a slight impact on performance. However, it is recommended that when archiving a database that contains many small or empty tables, disable CATALOG or, alternately, enable CATALOG at the object level.
Teradata ARC automatically excludes an active CATALOG database from its object list to avoid HUT lock conflicts. To archive, restore, or copy a CATALOG database, use NOCATALOG.