15.11 - config_systems - Data Stream Architecture

Teradata Data Stream Architecture (DSA) User Guide

prodname
Data Stream Architecture
vrm_release
15.11
created_date
December 2016
category
User Guide
featnum
B035-3150-026K

Purpose

The config_systems command configures the DSC settings for the Teradata system and nodes used for backup and restore jobs. It also sets the selector in the targeted system for ActiveMQ.

Syntax

config_systems -f|-file File -s|skip_system_config SkipSystemConfiguration

Example

dsc config_systems -f configSystem.xml -s system

Parameters

f|file filename
The full path and name of the file containing the necessary configuration parameters.
configSystem.xml
s|skip_system_config SkipSystemConfiguration
[Optional] Flag indicating whether the systems and node configuration or selector setting is skipped when you run the command. If this option is not specified, then both parts of the configuration (system and selector) are run. Enter one of the following:
  • system to avoid configuring Teradata systems and nodes
  • selector to avoid setting the selector in the targeted system for ActiveMQ
If you choose the selector option with this parameter, restart Teradata Database using a DSMain restart.
u|user_authentication User
Required when security management is enabled. Supplies the command with the Viewpoint user, and triggers a password prompt for authentication.

Usage Notes

Item Description
Component names

The component name can only use the following characters: 'A-Z', 'a-z', '0-9' and '_'.

The first character of the component name cannot be '_'.
Hot Standby Nodes Hot standby nodes should be included when configuring a system.
IP Addresses
IP addresses can be changed whether or not nodes are in use. If IP addresses are not entered and IP addresses for the node exist in the repository, there will be no change and nothing will be deleted. IP addresses need to be unique. There are two validations:
  • IP addresses in pass-in nodes need to be unique.
  • If the IP address has been used by a different node in the repository, is in the list of pass-in nodes, and has a new IP address, it is valid. If the node is not in the list of pass-in nodes and the request comes from a portlet, it is rejected as the same IP address cannot be used for multiple nodes. If the request comes from the command line, it is valid, as the node in the repository is deleted.
Allowing Incremental Jobs Based on Full or Cumulative Backup Jobs Completed with Errors
By setting the skipForceFull option in the XML file, you can run an incremental backup job that is based on a prior full or cumulative backup job that completed with errors.
  • If you set skipForceFull to false and the full or cumulative backup job fails, aborts, or completes with errors, the next time the job is run, the job is forced to be a full backup.
  • If you set skipForceFull to true and the full or cumulative backup job fails or aborts, the next time the job is run, the job is forced to be a full backup. Jobs that complete with errors are handled the same as jobs that complete successfully or with a warning.
By default, the skipForceFull option is false.
The skipForceFull option is set system-wide. You cannot use this option on a single-job basis.
System Configuration Attributes The following XML file example shows some system configuration attributes. System configuration is subject to the following restrictions and requirements.
Setting reset_node_limit to true overwrites node limits with the system's hard and soft limits.
Soft and hard limits for insertion of new nodes:
  • If node limits are specified, they are used.
  • If node limits are not specified, the system limits are used.
  • The soft limits cannot be greater than the hard limits.
Soft and hard limits when updating existing nodes:
  • If the node limit is specified, the node limit is used.
  • If a node limit is not specified and the system limit = system limit in database, the node limit is used.
  • If a node limit is not specified and system limit is not the same as system limit in database, system limit is used.

XML File Example

A representative XML file containing system configuration information is shown below.

<?xml version="1.0" encoding="UTF-8" standalone="true"?>

-<dscConfigSystems xsi:schemaLocation="DSC.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.teradata.com/v2012/DSC"> -<system> 
<!-- 'system_name' - Required, max 32 characters -->
 <system_name>system7</system_name> 
<!-- 'tdpid' - Required (unless skipped by option)-->
 <tdpid>system7</tdpid> 
<!-- 'database_query_method' - Required, accepted values: BASE_VIEW/EXTENDED_VIEW required -->
 <database_query_method>BASE_VIEW</database_query_method> 
<!-- 'streams_softlimit' - Required, number of streams per node per job -->
 <streams_softlimit>20</streams_softlimit> 
<!-- 'streams_hardlimit' - Required, max number of streams per node-->
 <streams_hardlimit>20</streams_hardlimit> 
<!-- 'reset_node_limit' - Optional, accepted values: true/false -->
 <reset_node_limit>false</reset_node_limit> 
<!-- 'node', Required (at least one) -->
 -<node> 
<!-- 'node_name', Required -->
 <node_name>system7Node1</node_name> 
<!-- 'ip_address' - Required (at least one)-->
 <ip_address>229.0.0.1</ip_address> <ip_address>99.23.106.11</ip_address> 
<!-- 'streams_softlimit' - Optional, number of streams per node for each job -->
 <streams_softlimit>20</streams_softlimit> 
<!-- 'streams_hardlimit' - Optional, max number of streams per node -->
 <streams_hardlimit>20</streams_hardlimit> </node> -<node> <node_name>system7Node2</node_name> <ip_address>99.23.110.12</ip_address> <ip_address>229.0.0.2</ip_address> <streams_softlimit>20</streams_softlimit> <streams_hardlimit>20</streams_hardlimit> </node> 
<!-- 'skip_force_full' - Optional, accepted values: true/false -->
 <skip_force_full>false</skip_force_full> </system> </dscConfigSystems>