Purpose
Scans Teradata systems managed by Business Continuity Manager 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 database system.
- IN db1,db2,dbN
- Use to specify the databases to scan within the Teradata systems managed by Business Continuity Manager. Running DICTIONARY SCAN without a database list scans all databases that exist in the specified Data Dictionary (dictionaryname). If you are scanning a new Data Dictionary and exclude this parameter, Business Continuity Manager scans all 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 database you specify for scanning is inaccessible, the DICTIONARY SCAN operation fails and Business Continuity Manager raises an alert.
This command creates a scan log on the Business Continuity Manager server in /var/opt/teradata/bcm/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 Business Continuity Manager 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.