16.10 - Setting Redrive Protection for Users, Accounts, and Profiles - Teradata Database

Teradata Database Administration

Product
Teradata Database
Release Number
16.10
Release Date
April 2018
Content Type
Administration
Publication ID
B035-1093-161K
Language
English (United States)

You can enable or disable Redrive protection for individual users, accounts, and profiles using the TDWM.Redrive table:

  1. Ensure that TASM is running.
  2. Insert, modify, or delete rows in TDWM.Redrive to specify whether particular users, accounts, or profiles will participate in Redrive.
  3. From the Teradata Viewpoint Workload Designer portlet, issue the TDWM Activate command after changing the TDWM.Redrive table in order for the new changes to take effect.

The table definition for TDWM.Redrive is:

CREATE SET TABLE TDWM.Redrive ,FALLBACK ,
     NO BEFORE JOURNAL,
     NO AFTER JOURNAL,
     CHECKSUM = DEFAULT,
     DEFAULT MERGEBLOCKRATIO
     (
      ObjectType VARCHAR(10) CHARACTER SET UNICODE
                 NOT CASESPECIFIC NOT NULL,
      ObjectName VARCHAR(128) CHARACTER SET UNICODE
                 NOT CASESPECIFIC NOT NULL,
      RedriveMethod INTEGER NOT NULL)
UNIQUE PRIMARY INDEX ( ObjectType ,ObjectName );

Insert a row into the table or modify an existing row in the table to specify whether Redrive protection is enabled for a particular user, account, or profile:

Column Name Valid Values Description
ObjectType In order of precedence, where USER is most specific and PROFIL is least specific:
  • USER
  • ACCT (account)
  • ACCTSTR (account string)
  • PROFIL (profile)
Specifies whether you are setting Redrive protection for a user, an account, or a profile.
ObjectName The name of the object The name of the user (or application), account, or profile for which you are setting Redrive protection.

For example, if ObjectType is USER, then ObjectName is the user name.

RedriveMethod
  • 1 (Disable Redrive)
  • 2 (Enable Redrive)
Determines whether Redrive is enabled or disabled for the user, account, or profile specified by ObjectName.

When there is a conflict, the most specific ObjectType is used. For example, suppose these rows are in TDWM.Redrive:

ObjectType ObjectName RedriveMethod
USER Mark 1
PROFIL Manager 2

If a session logs on as USER Mark and PROFIL Manager, since both rows in the table qualify, the most specific ObjectType is chosen. USER is more specific than PROFIL; therefore, RedriveMethod 1 (Do not use Redrive) is chosen and the session will not participate in Redrive.

If there is no row in TDWM.Redrive for the session, the RedriveDefaultParticipation DBS Control field determines whether the session participates in Redrive.

Redrive attributes are assigned to users, accounts, and profiles at logon time, and these attributes remain for the entire session. The attributes are not changed for that session even if new entries are made to TDWM.Redrive that would apply to the session. However, once Redrive is enabled, you can use the Redrive query band to turn Redrive off and on during the life of the session.