Starting and Stopping RSG - Teradata Meta Data Services

Teradata Meta Data Services
Product
Teradata Meta Data Services
Release Number
15.00
Published
February 2015
Language
English (United States)
Last Update
2018-09-27
dita:mapPath
B035-3045-114K/MDS_Installation_1500.ditamap
dita:ditavalPath
ft:empty
Product Category
Teradata Tools and Utilities
  1. Run the dbscontrol utility to verify that the MDS is Enabled flag is set.

    When the MDS is Enabled flag is set in dbscontrol, the RSG starts automatically with the Teradata Database.

  2. Display the MDS is Enabled flag:

    display general

    On Linux, view the /var/log/messages file to see if RSG started.

    On Windows, an entry that indicates RSG started is made in the Event Viewer log.

    If DEBUGTRACE is set to ON, full RSG logging takes place.

    If DEBUGTRACE is set to OFF, minimal logging occurs.

    The REPLACE option indicates that the old RSG log file will be removed and a new log file created at the next TPA reset.

    The files are located in the following directory:
    • tdconfig_directory\RSG (Windows)
    • tdconfig_directory/RSG (Linux)

    One set of files exists on each node.

  3. If the tdinfo utility indicates that the RSG vproc is not online, run the vprocmanager utility to set it online:
    • set xxxx online

    where xxxx is the ID of the RSG vproc on one TPA node.

    The id of the RSG vproc on the RSG master node should be as follows:
    RSG Version id on the Master Node
    13.10 or earlier 9215
    14.0 or later 26623
    The id of the RSG vproc on secondary RSG nodes should be as follows:
    RSG Version id on the Secondary Node
    13.10 or earlier 9214 or a lesser number (9213, 9212, and so on)
    14.0 or later 26622 or a lesser number (26621, 26620, and so on)

    Repeat these steps for the other TPA nodes.

    The RSG stops when the Teradata Database stops.