Purpose
Scans Teradata systems managed by Unity for new table objects and for changes in table objects that apply to the Data Dictionary you specify.
Syntax
DICTIONARY SCAN {ALL [tdpid1,tdpid2,..,tdpidN]} {[IN db1,db2.. ,dbN] | OBJECT objectname} ;Parameters
- tdpid1, tdpid2, tdpidN
- Unique identifier (TDPID) of a Teradata Database system.
- IN db1,db2,dbN
- Use to specify the Teradata Databases to scan within the Teradata systems managed by Unity. Running DICTIONARY SCAN without a database list scans all Teradata Databases that exist in the specified Data Dictionary (dictionaryname). If you are scanning a new Data Dictionary and exclude this parameter, Unity scans all Teradata Databases that it manages.
- object
- Name of a specific database object in the Teradata managed systems to scan.
Usage Considerations
If any Teradata system or Teradata Database you specify for scanning is inaccessible, the DICTIONARY SCAN operation fails and Unity raises an alert.
This command creates a scan log on the Unity server in /var/opt/teradata/unity/logs managed by the Active Sequencer. The file name is scanner.log. This log includes a full list of table objects added to the managed Unity Data Dictionary and also table objects rejected due to failure to comply with one or more object-matching criteria. For each rejected table object, the log lists and describes the mismatched elements within the object.