Troubleshooting - Miscellaneous - Teradata Meta Data Services

Problem

Possible Fix

Multiple entries in the MDS error log appear that say something like this: “Could not match column 'xxxx’ in list of column entries.”

Cause: MDS tries loading all table meta data first and then Views to make sure all base table information is already loaded and available in the repository to meet dependencies. But this does not guarantee that MDS will be able to resolve all viewcolumn to column mappings because a view may in turn reference another view. As a result MDS makes multiple passes to parse and load view information. So the first pass may generate the warning but on a subsequent pass it will find the base table information and nothing is logged in the error file.

These entries are warnings and usually not errors. To determine whether the View/Macro/Stored Procedure is missing information and an error truly exists:

Read the “SynchronizationLevel” property for the View/Macro/Stored Procedure. When the SynchronizationLevel property has a value = 0 then it means that MDS was not able to resolve all of the references in the item.

The following error message is found in the MDS error log after running metacreate to create the MDS repository:

05/03/00 17:26:52|PID-280|THREAD-220|2|CDBAccess::DBODBCError: ODBC error (connection, statement, return code, native error code) (14357064, 14358104, -1, -3807) S0002 [Teradata][Teradata Database System] Table/view/trigger 'metalatesttx' does not exist.

05/03/00 17:26:52|PID-280|THREAD-220|2|CDBAccess::DBRunSql: ODBC SQLExecDirect error. Failed SQL=SHOW TABLE metalatesttx;

Ignore these error messages. MDS logs all SQL statements that return an error. The metacreate utility performs a “SHOW TABLE metalatesttx;” to see if a MDS repository already exists. If the table does not exist, metacreate proceeds to create the repository tables.

Non ASCII characters in the Error Log can appear differently depending on the program you use to view the log.

For example, the following entry viewed with Notepad on Windows looks like:

05/11/00 15:23:05|PID-149|5|TXP::dump_new_msg : <|| gwsDDL: Node=BRONCOS1, Sid=[0 8665], Tid=16380 [7 54646], CREATE USER “FäshiönStær” FROM "DBC" AS PERMANENT = 3000000 ,SPOOL = 80000000 ,DEFAULT DATABASE = “FäshiönStær” ,NO FALLBACK,NO BEFORE JOURNAL,NO AFTER JOURNAL; [len=160]

The same entry, viewed with VI on Linux looks like:

05/11/00 15:23:05|PID-149|5|TXP::dump_new_msg : <|| gwsDDL: Node=BRONCOS1, Sid=[0 8665], Tid=16380 [7 54646], CREATE USER “F\344shi\366nSt\346r” FROM "DBC" AS PERMANENT = 3000000 ,SPOOL = 80000000 ,DEFAULT DATABASE = “F\344shi\366nSt\346r” ,NO FALLBACK,NO BEFORE JOURNAL,NO AFTER JOURNAL; [len=160]

An AMP containing the MDS repository is down. A message similar to the following will be found in the MDS error log:

CDBAccess::DBODBCERROR: ODBC error (connection, statement, return code, native error code) (15078056, 15079088, -1, -2642) S1000 [Teradata] [Teradata Database System] AMP Down: the request against nonfallback metarelation_204 cannot be done.

The MDS repository will be unavailable until the AMP is restored. To save processing cycles, stop the MDS DDL Gateway and Action Processor processes until the AMP is restored.

When attempting to load database information through MetaManager or directly through Metaload, the following is generated:

6701 An unknown character string translation was requested.

For Kanji-based systems, the necessary translation tables must be installed. For detailed installation information, see the Teradata Metadata Services Installation Guide (B035-3045).