Set the Workstation or Server Configuration Parameters
After the appropriate software is installed on your workstation or server, set the MDS configuration parameters for each workstation or server.
Linux Workstations or Servers
On Linux workstations the local configuration parameters are set using the mdsconfig program. You must be logged on as root to run mdsconfig.
The DSN name specified with mdsconfig for the location of the MDS repository should have been added to the odbc.ini file on the Linux workstation or server.
Command-line Syntax
The parameters for the mdsconfig program are:
mdsconfig -h <metahome> -o <DSNname> -u <dbuser> -p <dbpasswd> -l <loglevel> -t <tracelevel> -s <numISvr>
Use mdsconfig –H to get help for the mdsconfig program.
Parameter |
Description |
-h <metahome> |
The MDS Installation folder. It is highly recommended that the default location of /opt/teradata/mds not be changed. |
-o <DSN name> |
Default ODBC Data Source Name (DSN) that MDS uses to connect to the Teradata Database System containing the MDS repository. |
-u <dbuser> |
Database User Name that MDS uses to log on to the Teradata Database System to access the MDS repository. |
-p <dbpasswd> |
Database User Password that MDS uses to log on to the Teradata Database System to access the MDS repository. |
-l <loglevel> |
Error Log level (0-5). Where 0 is the least amount of logging and 5 is the greatest amount. |
-t <tracelevel> |
Trace level (0-5) to be used for Application debugging. Where 0 is the least amount of tracing and 5 is the greatest amount of tracing. |
-s <numIntSvr> |
Number of Integrity Servers for the MDS Data Definition Language (DDL) Gateway to start. Defaults to 5. |
-H |
Displays option list. |
If you will be installing and using the Automatic DIM Update, refer to Chapter 7: “Automatic DIM Updates,” for additional installation and configuration tasks.
Windows Workstations or Servers
On Windows, the local MDS configuration parameters are stored in the Windows Registry. To change the settings, you must be logged onto the Windows system as a user who has permission to update the Windows Registry.
Note: On 64-bit Windows platforms you need to make sure that the MDS Configuration is “Run as administrator” for the changes to take place.
1 Locate the program icon for MetaManager, or MDS Configuration in the Control Panel.
2 Right-click the program icon or shortcut, and then click Run as administrator.
3 If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
Note: On Windows, users who are only members of the Guests group will not be able to change the settings.
To display the MDS Configuration tab of the Teradata Meta Data Services Configuration dialog box:
1 Click MDS Configuration from the Windows Control Panel.
2 Click Star > All Programs > Teradata Meta Data Services > MetaManager to display The Teradata Meta Data Services MetaManager Logon dialog box, then click Configure.
Note: If you did not accept the default name as your choice during installation, you must find your specified name for the MDS program group to launch MetaManager.
Set the Database Connection Information
During installation, the MDS Database connection information is specified. This information resides in the local client system registry files, not in the repository. The MDS engine uses this information to connect to the MDS repository.
The settings can be changed before making the connection, using the Teradata Meta Data Services Configuration dialog box.
1 In the Data Source Name box enter the ODBC system Data Source Name (DSN) to use to connect to the Teradata Database System containing the MDS repository.
2 In the Database User Name box enter the user name that MDS will use to log onto the Teradata Database System.
The user must have permissions to access the MDS database tables.
If the MDS users on the local system are browsing the MDS repository, the user needs SELECT privileges to the database containing the MDS repository.
If any user loads or updates the MDS repository, INSERT, UPDATE and DELETE privileges are also required.
To create an Application Information Metamodel, CREATE TABLE privileges are needed.
If this user will be creating the MDS repository, GRANT ALL PRIVILEGES to the user on the database.
3 In the Database User Password box enter the password that MDS will use to log onto the Teradata Database System.
4 In the Database Name box enter the name of the Teradata Database within the Teradata Database System where the MDS repository is stored.
This can be the same as the Database User Name.
If omitted, the Database Name will default to the default Database Name in the ODBC DSN for that Teradata Database System where the database is housed.
Note: If the DSN does not have a default Database Name, the connection will be made to the default database of the Database User.
5 To save changes to these settings in the registry, click Apply or OK.
Note: If you are connected to MetaManager when you make changes to these settings, they will not take effect until the next time you run MetaManager.
Setting Logging and Trace Levels
From the Teradata Meta Data Services Configuration dialog box, choose the Logging tab to see the log options.
The logging and tracing levels only apply to the local system, where an MDS application is running. They can be changed at any time and changes are written to the local system’s registry immediately.
MDS applications read the log level settings at 30 second intervals and will immediately use the settings. MDS applications only read the trace level settings on start up, therefore restart the application for new trace level settings to take effect.
Logging Level
This choice controls the amount of log messages written to the MDS log file. The default is Warning.
Level |
Description |
Critical |
Logs Critical messages |
Error |
Logs Error and Critical messages |
Warning |
Logs Warning, Error and Critical messages. Warning is the default logging level |
Information |
Logs Information, Warning, Error and Critical messages |
All |
Logs Debug, Information, Warning, Error and Critical messages |
Tracing Level
This choice controls the type of messages traced and written to the standard error output. The Tracing Level and error output are used primarily when writing an application using the MDS APIs. The default is Disable.
Level |
Description |
Disable |
No messages are traced |
Critical |
Traces Critical messages |
Error |
Traces Error and Critical messages |
Warning |
Traces Warning, Error and Critical messages |
Information |
Traces Information, Warning, Error and Critical messages |
All |
Traces Debug, Information, Warning, Error and Critical messages |
Log Filename
The Log filename is read-only. The filename is meta_yyyymmdd.txt (where yyyy = year, mm = month, dd = day). The date contained in the log filename indicates the date the log entries were written.
MDS creates a new log file each day. The log does not wrap. Old log files should be deleted by the MDS Administrator.
Log Files Manager
To see previously generated log files (their names, and file sizes in bytes), click Log Files Manager.
View or delete the logs in this window.