MDS Error Messages
The following table lists MDS error messages.
Message |
Code |
Probable Cause |
META_SUCCESS |
0x80000000 |
API Successful: The API completed successfully. |
META_FAILURE |
0x80007000 |
General API Error: General API error. See the MDS error log for more details. |
META_E_INVALID_PARAMETER |
0x80007001
|
Invalid Parameter: One of the parameters passed in the API is invalid or a required parameter is not set. |
WriteObject: Requires the attributes which uniquely identify the object be set (the ObjectID or the ObjectGUID) or to write a new object the ClassID or ClassGUID must be set in the object. |
||
ReadObject: If the ObjectID or the ObjectGUID is not set, then the ClassID or ClassGUID AND the ObjectName must be set. |
||
GetClassObjects, GetClassObjectKeys: the ClassID or ClassGUID: Must be set. |
||
GetPropertyValue: The Variant pointer passed in is NULL |
||
GetOrig/DestCollection, GetOrig/DestCollectionKeys, AddToOrig/DestCollection, AddManyToOrig/DestCollection, RemoveFromOrig/DestCollection - Internal Object ID: must be set. |
||
META_E_CLASS_NAME_ ALREADY_EXISTS_IN_AIM |
||
|
0x80007002 |
Name of Class Already Exists: Call to CMetaAIM::CreateClassDesc to create a class with the name of a class which already exists in the model. The names of classes within a model must be unique. |
META_E_OBJECT_NOT_FOUND |
0x80007003 |
Object Not Found: The object identified by Object ID, Object GUID or ClassID/Name was not found in the repository. |
META_E_INSUFFICIENT_ MEMORY |
0x80007004 |
Cannot Allocate Enough Memory: MDS could not allocate enough memory to perform the action. On Linux, the data space available to the program can be increased by the ulimit command. |
META_E_SERVER_NOT_ AVAILABLE |
0x80007005 |
This status is obsolete. |
META_E_NO_ACCESS_RIGHTS
|
0x80007006
|
No Access Permissions: The logged in user does not have permissions to access the object as requested. |
For example: ReadObject: Does not have read permissions to perform a ReadObject. |
||
WriteObject: Does not have write permissions to perform a WriteObject. |
||
AddToDestCollection/RemoveFromDestCollection: Does not have collection permissions to perform a AddToDestCollection/RemoveFromDestCollection. |
||
META_E_PROPERTY_NOT_ FOUND |
0x80007008 |
Invalid Relative Property ID: The Relative Property ID passed in is invalid or a ReadObject was not performed before the call to GetPropertyValue |
META_E_FATAL_ERROR |
0x8000700A |
Internal MDS processing has failed due to an unexpected error. |
META_E_REPOSITORY_NOT_ INITIALIZED |
0x8000700B |
Call Made to APIs before Initializing: A call was made to any MDS API before calling CMetaRepository::Initialize. |
META_E_AIM_NAME_ ALREADY_EXISTS |
0x8000700C |
Model Name Already Exists: The call to CMetaAIM::CreateModel to create a model was made with the name of a model which already exists in the MDS repository. Names of metamodels in the MDS repository must be unique. |
META_E_MULTIPLE_OBJECTS_ FOUND |
0x8000700D |
Corrupt MDS Table: Multiple rows with the same MDS Internal ID were found in a repository table or an object with a specific name exists twice in a repository table. This indicates a corrupt MDS Repository table. |
META_E_MISSING_REQUIRED_ PARAMETER |
0x8000700E |
Attribute Not Set: One of the attributes which is required to perform the requested API is not set. |
META_E_DATATYPE_MISMATCH |
0x80007011 |
Invalid Variant Type: The VariantType defined for a CMetaPropertyDesc is not a valid VariantType for the PropertyType defined for the CMetaPropertyDesc. |
META_E_OBJ_NOT_IN_ CORRECT_RELATION_CLASS |
||
|
0x80007012
|
GetDestCollection, AddToDestCollection, AddManyToDestCollection: the object ID of the calling object is not in the origin class of the specified relationship. |
GetOrigCollection AddToOrigCollection, AddManyToOrigCollection: the object ID of the calling object is not in the destination class of the specified relationship. |
||
AddToDestCollection, AddManyToDestCollection: the object IDs to add to the collection are not in the destination class of the relationship. |
||
AddToOrigCollection, AddManyToOrigCollection: the object IDs to add to the collection are not in the origin class of the relationship. |
||
META_E_EXCEPTION |
0x80007013 |
MDS Exception: An operating system call made by MDS has caused an exception. |
META_E_CLASS_NOT_FOUND |
0x80007014 |
Invalid MDS ClassID: The ClassID or ClassGUID set in the object or API parameter is not a valid MDS Class ID. |
META_E_RELATIONSHIP_ NOT_FOUND |
0x80007015 |
Invalid CMetaRelationshipDesc: The RelID or RelGUID specified for the relationship was not found to be a valid CMetaRelationshipDesc defined in the MDS repository. |
META_E_PROP_NAME_ ALREADY_EXISTS_IN_CLASS |
||
|
0x80007016 |
Property Already Exists: The call to CMetaClassDesc::CreatePropertyDesc to create a property was made with the name of a property which already exists in the class. Names of properties within a class must be unique. |
META_E_CLASS_OBJ_MISMATCH
|
0x80007017
|
Object Contains Undefined Property: WriteObject was requested on an object which contains a property which is not defined for the class. |
Example: The application performed a SetPropertyValue(99, PropObj) and then a WriteObject(). |
||
If the class of the object being written does not have a property (CMetaPropertyDesc) with a Relative Property ID of 99, this error will occur. |
||
META_E_NO_UNUSED_LOIDS |
0x80007018 |
Out of Object IDs: MDS has run out of new objects IDs to assign to new objects. |
META_E_UNSUPPORTED_ VARIANT_TYPE |
0x80007019 |
WriteObject: WriteObject was requested on an object which has a property set with a Variant type that is not supported by MDS. If the CMetaProperty functions are used to set properties this will not occur. MDS also provides a SetPropertyValue API in which the Variant record can be passed in. The Variant record must be set to the Variant Type defined for the property in the CMetaPropertyDesc object. |
META_E_UNSUPPORTED_ SQL_TYPE |
0x8000701A |
Invalid Database Column Type: The database column type of a MDS repository table is not a type supported by MDS. This could only happen if the column type was altered outside of MDS through a database utility such as BTEQ. |
META_E_DBACCESS_ERROR |
0x8000701B |
SQL Request Failed: The SQL request to the MDS repository database which MDS issued to perform the API or utility failed. Look in the MDS Error Log for the explanation of the cause of the error. |
META_E_OBJNAME_ INCORRECTLEN |
0x8000701C |
Object Name Too Long: The ObjectName was set to a name which is greater than 255 characters. Object Names are limited to 255 characters in length. |
META_E_REGISTRY_LOOKUP_ FAILED |
0x8000701D |
Lookup Failed: Lookup of one of the MDS Windows Registry entries failed. MDS stores in the registry the Database ODBC DataSourceName, Logon Name and Password. These entries are defined and saved in the MDS setup and using the MDS metaconfig.exe program. |
META_E_DATABASE_CONNECT_FAILED |
0x8000701E |
MDS Engine Could Not Connect to the Database: The MDS engine could not connect to the database. One probable cause is the MDS database configuration is incorrect (Invalid DSN, User name or password). The MDS Error log will contain detail which describes the actual cause of the error. |
META_E_NO_TERADATA_TYPE |
0x8000701F |
SQL Type is Not Supported: In the CMetaClassDesc::CreatePropertyDesc() function, the SQL Type specified for the PropType parameter is not a type supported by MDS. |
META_E_INVALID_DATATYPE_ MODIFIER
|
0x80007021
|
Invalid Property Length/Total Digits In the CMetaClassDesc::CreatePropertyDesc() function, the Property Length or Total Digits specified is invalid. |
For Property Types in which the length must be defined (SQL_CHAR, SQL_VARCHAR, SQL_VARBINARY, and so on), the length must be greater than 0 (zero). |
||
For types which use the Total Digits (SQL_NUMERIC, SQL_DOUBLE, and so on), Total Digits must be 0 (zero) or greater. |
||
META_E_MODEL_NOT_CREATED |
0x80007022 |
ObjectID of Existing Model: When the functions in the CMetaAIM API class (except the CreateModel API) are called, the CMetaAIM object must contain the ObjectID of an existing model in the repository. |
META_E_CLASS_NOT_CREATED |
0x80007023 |
ObjectID of Existing Class Description: When the functions in the CMetaClassDesc API class (except the CreatePropertyDesc API) are called, the CMetaClassDesc object must contain the ObjectID of an existing class description in the repository. |
META_E_REL_NAME_ALREADY_EXISTS_IN_AIM |
||
|
0x80007024 |
Relationship Name Already Exits: A call to CMetaAIM::CreateRelationshipDesc was made with the name of a relationship which already exists in the model. Names of relationships within a model must be unique. |
META_E_COLUMN_MISSING |
0x80007025 |
Class Description contains more properties than corresponding MDS database table: An object read from the repository was missing an expected (common or unique) property (that is, the data retrieved does not have all the properties that the object's class definition in the repository says it should) or the result of a non-object table read did not contain an expected column. |
META_E_INVALID_VARIANT_ TYPE |
0x80007026 |
Invalid Variant Type: In the CMetaClassDesc::CreatePropertyDesc() function, the Variant Type specified is invalid. |
META_E_PROPERTY_TEMPLATE_MISSING |
0x80007027 |
Corresponding MDS database table contains more properties than defined for the Class Description: An object read from the repository contained a unique property that was not expected. That unique property is not part of the object's class definition in the repository. |
META_E_COLNAME_EXCEEDS_ THIRTY_CHAR |
||
|
0x80007028
|
Column Names Limited to 30 Characters: CMetaPropertyDesc names are used as the name of a Teradata Database column and therefore must follow the guidelines for Teradata column names. |
Teradata column names are limited to 30 characters. Provide a shorter name to the CMetaClassDesc::CreatePropertyDesc call. |
||
META_E_NULL_OBJECT_ID |
0x80007029 |
ObjectID of Zero: The list of object ids to passed to AddManyToDestCollection, AddManyToOrigCollection, RemoveManyFromDestCollection or RemoveManyFromOrigCollection contains an object ID of 0 (zero). |
META_E_VARIANT_ T_EXCEPTION |
0x8000702B |
MDS is Unable to Access the SafeArray in the VARIANT Structure: MDS uses the SafeArray field of the VARIANT structure to pass BINARY data. If MDS is unable to access the SafeArray in the VARIANT structure, this error is set. |
META_E_LOAD_IN_PROGRESS |
0x8000702C |
Concurrent Loads of the Same System Not Permitted: MDS is currently loading the database schema information for the specified system. Concurrent loads of the same system are not permitted. |
META_E_LOAD_INVALID_ PARMNUM |
0x8000702D |
Number of Parameters Incorrect: The number of parameters specified when running the command line tools (metaload.exe, metaaim.exe or metacreate.exe) is not correct. |
META_E_OPENFILE_ERRROR |
0x8000702E |
metacreate.dat File Missing: Returned by metacreate.exe if the metacreate.dat file is missing. |
META_E_NO_AIM_UPDATES |
0x8000702F |
Update of AIM Objects: A call has been made to add a property to the PropertyDescClass class. |
META_E_REPOSITORY_ ALREADY_INITIALIZED |
||
|
0x80007030
|
Multiple Initialize Calls: Call to CMetaRepository::Initialize for the second time in the process. |
Recommended Action: To Initialize with a different user, call CMetaRepository::Deinitialize before calling CMetaRepository::Initialize |
||
META_E_INVOKE_FAILED
|
0x80007031
|
Invoke Fails: In the CMetaCOM ReadObject, WriteObject and WriteObjects functions, MDS performs
an hr = pIMetaPersist->QueryInterface(IID_IDispatch, |
Using the Dispatch pointer returned from QueryInterface, MDS calls the Invoke function to get or set the properties in the COM object. This error is returned if the Invoke fails. The result code returned by Invoke is logged in the MDS error log. |
||
See COM Documentation for a description of the errors returned by Invoke. Make sure the Dispatch ID matches the Relative Property ID in the CMetaPropertyDesc and that the Variant Type matches the VariantType in the CMetaPropertyDesc. |
||
META_E_QUERY_INTERFACE_ FAILED
|
0x80007032
|
Query Interface Fails: In the CMetaCOM ReadObject, WriteObject and WriteObjects functions, MDS performs an hr = pIMetaPersist->QueryInterface (IID_IDispatch, (void**)&pDispatch); using the IMetaPersist pointer passed into the function. |
This error is returned if the QueryInterface fails. The result code returned by QueryInterface is logged in the MDS error log. See COM Documentation for a description of the errors returned by QueryInterface. |
||
META_E_COCREATEINSTANCE_ FAILED
|
0x80007033
|
CoCreateInstance Call Fails: The CMetaCOM GetDestCollection GetOrigCollection, GetDestCollectionKeys, GetOrigCollectionKeys, GetClassObjects, and GetClassObjectKeys functions perform a call to CoCreateInstance to create the vector in which to return the objects. |
This error is returned if CoCreateInstance fails. The result code returned by CoCreateInstance is logged in the MDS error log. |
||
See COM Documentation for a description of the errors returned by CoCreateInstance. |
||
META_E_VARIANTTYPE_ MISMATCH
|
0x80007034
|
Current Variant Type of The Property Does Not Match the Type Requested: A call to a GetXXX function in the CMetaProperty API class returns this error when the current variant type of the property does not match the type requested. |
Example: GetString(): will return this error if the property variant type is an Integer. |
||
GetInt(): will return the error is the variant type is a float. |
||
META_E_REQUIRES_ UNIQUE_NAMES
|
0x80007035
|
Multiple Objects with the Same Name: This error is returned from WriteObject() if the object being written has the same name as an object which already exists in the class and the class has the unique naming flag on. This error is also returned from WriteObject() if the call is an update of an existing object that changes the object's name and the new name conflicts with that of another object in a uniquely named collection both objects are members of. The object will not be written. |
AddToDest(Orig)Collection(): The error is returned from AddToDest(Orig)Collection() when the object being added to the collection has the same name as an object which already exists in the collection and the relationship description defining the collection has the unique naming flag on. The add to collection operation will not be performed. |
||
META_E_UNIQUE_NAMES_ ARE_VIOLATED
|
0x80007036
|
Duplicate Names Found: This error code indicates a data inconsistency in the repository. A class or collection, though marked as uniquely named, contains objects with duplicate names. |
Multiple Objects with the Same Name: This error is returned from WriteObject() if it detects that a unique naming constraint is already violated in the repository before writing the object. This can be either a class violation (the object's class has the unique naming flag on, and there already exist multiple objects of that class that have the same name as each other) or a collection violation (an existing object's name is being updated, and multiple objects in a uniquely named collection it is a member of already have the same name as each other). The object will not be written |
||
AddToDest(Orig)Collection(): The error is returned from AddToDest(Orig)Collection() if it detects that the collection the object is being added to already violates a collection unique naming constraint. That is, the collection contains multiple objects with the same name as each other and the relationship description defining the collection has the unique naming flag on. The add to collection operation will not be performed. |
||
META_E_REMOVE_FROM_ COLLECTION_FAILED |
||
|
0x80007037 |
Objects Not in Correct Class: One or more of the objects were not in the correct class or were not in the collection calling object not in appropriate (origin or destination) class object to remove not in appropriate (origin or destination) class object to remove not in collection |
META_E_REQUIRES_UNIQUE_ PROPERTY_IDS |
||
|
0x80007038 |
Existing Relative Property ID: The call to CMetaClassDesc::CreatePropertyDesc specifies the same Relative Property as an existing property in the class. Relative Property IDs must be unique for all properties of a class. |
META_E_UNIQUE_PROPERTY_ IDS_ARE_VIOLATED |
||
|
0x80007039 |
Relative Property ID: MDS has detected that two properties of a class have the same Relative Property ID. |
META_E_BUFFER_TOO_SMALL |
0x8000703A |
Buffer Not Large Enough: The buffer passed to CMetaProperty::GetBinary() is not large enough to return the binary field. |
META_E_UNKNOWN_USER |
0x8000703B |
Name is Not User Defined: The name passed to CMetaRepository::Intialize() is not User defined in MDS. |
META_E_INVALID_PASSWORD |
0x8000703C |
Password Incorrect: The password passed to CMetaRepository::Intialize() does not match the current password for the specified user. |
META_E_INVALID_ACCESS_ RIGHTS |
0x8000703D |
Access Permissions Value Invalid: The value specified for access permissions on an object is not a valid value. |
It is recommended that you use the predefined constants (meta.h). The constants are defined as hex values. In the example, 666 decimal translates to 0x29A hex, which is not valid. |
||
You want to pass 0x666 or META_OWNER_ READWRITE|META_APPGRP_READWRITE| META_ ALL_READWRITE |
||
META_E_INVALID_FOREIGN_ KEY_VALUE |
0x8000703E |
Objectid Is Not In The Specified Classid: The ObjectID is not in the specified ClassID or is not a valid object identifier at all |
META_E_APPLICATION_ GROUP_NOT_CREATED |
||
|
0x8000703F |
Application Group is Not Valid: The Application Group ID set in an object is not a valid Application Group. |
META_E_OWNER_INVALID |
0x80007040 |
OwnerID is Not a Valid User: The Owner ID set in an object is not a valid User. |
META_E_OBJECT_IN_USE |
0x80007041 |
Cannot Delete User Object: Cannot delete a User object which is the owner of objects. Cannot Delete Application Group Object: Cannot delete an Application Group object if this is the Application Group of any object. |
META_E_OBJECT_ALREADY_ EXISTS |
0x80007042 |
User or Application Group Already Exists: Attempt to create a User or an Application Group which already exists. Names of Users and Application Groups must be unique. |
META_E_CREATEPROPERTY_ NOT_ALLOWED |
||
|
0x80007043 |
CMetaClassDesc::CreatePropertyDesc: MDS could not create a column with the information defined for the property in CMetaClassDesc::CreatePropertyDesc. This could be caused by using a Teradata keyword for the property name.
|
META_E_DATABASE_ TABLES_NOT_INITIALIZED |
||
|
0x80007044 |
Repository Not Created: The MDS database repository has not been created. |
META_E_PASSWORD_TOO_ SHORT_OR_TOO_LONG |
||
|
0x80007045 |
Password Incorrect: The password is less than 5 characters or greater than 14 characters. |
META_E_MUST_BE_METASU_USER |
0x80007046 |
This status has been superseded by META_E_MUST_BE_A_SUPERUSER |
META_E_DATABASE_TABLES_ ALREADY_INITIALIZED |
||
|
0x80007047 |
Existing MDS Tables: metacreate.exe is being run to create and load the initial MDS database tables and there is already an existing set of MDS tables. |
META_E_NO_CHANGES_TO_ MDSMETAMODEL_OBJECTS_ ALLOWED |
||
|
0x80007049 |
Object ID Less than 10,000: Modification or delete of MDS internal objects (objects with ids < 10,000) is not permitted |
META_E_UNIQUENESS_ VIOLATION_OR_OBJECT_ NOT_FOUND |
||
|
0x8000704A |
Failed Uniqueness Check: A WriteObject failed because one of the properties violated a uniqueness check. |
META_E_INVALID_DATABASE_ USER_NAME |
0x8000704B |
User Name Invalid: Teradata user name is not valid. |
META_E_INVALID_DATABASE_ PASSWORD |
0x8000704C |
Password Invalid: Teradata password is not valid. |
META_E_INVALID_DATA_ SOURCE_NAME |
0x8000704D |
DSN Invalid: ODBC data source name (DSN) is missing, invalid, or too long. |
META_E_DUPLICATE_ OBJECT_GUID |
0x8000704E |
GUID Not Unique: The application attempted to write an object whose GUID is the same as that of another object. Can occur when inserting a new object or when updating an existing object. |
META_E_INSUFFICIENT_ DATABASE_ACCESS_ PERMISSIONS |
||
|
0x8000704F |
Insufficient Access Permissions: The Teradata user MDS is logged in as does not have sufficient access permissions to perform the operation that was attempted. |
In general the MDS Teradata user needs at least SELECT, INSERT, UPDATE, DELETE, CREATE TABLE, and DROP TABLE access to its database, which are granted to the MDS Teradata user with the SQL “GRANT” statement by a user who is sufficiently privileged. |
||
META_E_INVALID_DATABASE_ SIZE |
0x80007050 |
This status is obsolete. |
META_E_DATABASE_OR_USER_ ALREADY_EXISTS |
||
|
0x80007051 |
This status is obsolete. |
META_E_CLASS_OR_ RELATIONSHIP_NOT_FOUND |
||
|
0x80007052 |
Table Not Found: The table for the specified class or relationship description was not found in the MDS repository database. |
META_E_TRANSACTION_ ABORTED_DUE_TO_DEADLOCK |
||
|
0x80007053 |
Deadlock Detected: A deadlock detected by the Teradata Database caused the transaction to be aborted. |
META_E_LOCK_HINT_CONFLICT |
0x80007054 |
Internal Database Locking: An internal database locking hint indicated that additional MDS internal server APIs were expected to be called within the previous transaction. This should never occur. If it does, it means MDS internal locking hints are out of synchrony with MDS internal server APIs. This is not under the user’s control. |
META_E_LOCK_HINT_ WRONG_API_SEQUENCE |
||
|
0x80007055 |
Internal Database Locking: An internal database locking hint indicated that a different MDS internal server API was called than was expected as the next call within the current transaction. This should never occur. If it does, it means MDS internal locking hints are out of synchrony with MDS internal server APIs. This is not under the user’s control. |
META_E_NO_DELETE_ PROPAGATION_TO_AIM_ COMPONENTS |
||
|
0x80007056 |
Attempt to create a relationship description with delete propagation turned on whose destination class was one of the following AIM component classes defined in the header file metaglobals.h: Deletion is not allowed to propagate to these classes.
|
META_E_OBJECT_ALREADY_ IN_COLLECTION |
||
|
0x80007057 |
Attempt to add an object to a collection of which the object was already a member. An object cannot be a member of the same collection multiple times. |
META_E_DUPLICATE_UNIQUE_ PRIMARY_KEY |
||
|
0x80007058 |
Internal error code indicating a database error occurred due to an attempt to insert a row: Internal error code indicating a database error occurred due to an attempt to insert a row whose primary key matched that of an existing row in the table. This code will normally be converted to the more specific META_E_OBJECT_ALREADY_IN_COLLECTION error code before being returned to the user. |
META_E_CONNECTION_NOT_ OPEN |
0x80007059 |
MDS server attempted to close a connection that was not currently open: Internal code indicating that during cleanup of ODBC connections, the MDS server attempted to close a connection that was not currently open. This is normally not an error and this code will not normally be returned to the user. |
META_E_TOOL_TERMINATED_ ABNORMALLY |
||
|
0x8000705A |
Command line was aborted or terminated before completion: The command line program (metacreate, metadelete, metaaim or metaload) called by MetaConfigurator was aborted or terminated before completion. |
META_E_TOO_MANY_DIGITS_ AFTER_DECIMAL_POINT |
||
|
0x8000705B |
More than 15 digits to the right of the decimal point: Attempt to create a fixed-point property description that specified more than 15 digits to the right of the decimal point (CMetaClassDesc::CreatePropertyDesc argument sPropType == SQL_DECIMAL or SQL_NUMERIC and sTotalDigits > 15). |
META_E_MIGRATION_REQUIRED |
0x8000705C |
The MDS Repository is a previous version. Run the metamigrate utility to upgrade the MDS repository to the current version before completing this operation.
|
META_E_LOAD_VIEWCOL_ DATATYPE_FAILED |
||
|
0x8000705D |
Teradata User does not have permissions: The MDS metaload utility uses the Teradata "HELP Column" command to get information on View Columns from Teradata. This error indicates that either: Look in the MDS Error log for the explanation of the actual cause of the error. |
META_E_DATABASE_FULL |
0x8000705E |
No more perm space in Teradata: Indicates there is no more perm space in the MDS Teradata Database. Use a Teradata utility such as BTEQ or WINDDI to increase the perm space for the MDS database. |
META_E_NAME_NOT_FOUND |
0x8000705F |
Database name not found: Database name given to metaload to load was not found in the Teradata Database System |
META_E_INVALID_OR_ MISSING_DB_TAG |
0x80007060 |
Database name incorrect: The file containing database names given to metaload contains an invalid tag or is missing a closing tag. |
META_E_DSN_DOES_NOT_ MATCH_CONFIGURED_DSN |
||
|
0x80007061 |
DSN does not match: The DSN specified as a parameter to metacreate to use to create a new Teradata User does not match the DSN in the MDS configuration for the MDS repository database. The DSNs must match to ensure that the MDS repository is created in the correct Teradata Database Systems. |
META_E_WARNING_ONLY_ BASE_TABLES_DROPPED |
||
|
0x80007062 |
MDS Repository partially corrupted: metadelete detected that the MDS repository was partially corrupted and could only drop the base MDS database tables. |
META_E_REPOSITORY_ CORRUPTED_NO_TABLES_ DROPPED |
||
|
0x80007063 |
MDS Repository corrupted: metadelete detected that the MDS repository was corrupted and was unable to drop any of the MDS database tables.
|
META_E_SECONDARY_INDEX_ UNIQUENESS_VIOLATION |
||
|
0x80007064 |
Internal error used by MDS: It is mapped to other MDS error codes before returning the API call. An error was detected by the MDS engine in checking for unique names or GUIDs. The engine returns the error as META_E_OBJECT_ALREADY_IN_COLLECTION or META_E_DUPLICATE_OBJECT_GUID. |
META_E_QUEUE_NOT_ATTACHED |
0x800070A0 |
Failure to access message queue: A read or write to the MDS message queue occurred when the queue is not currently attached to the process. At startup there is an attempt to detect orphaned queues by a failed attach/detach. This is not under the user's control. |
META_E_QUEUE_ALREADY_ATTACHED |
0x800070A1 |
Failure to access MDS queue: An attempt to attach the MDS queue to the process was made and it is already attached. This is not under user control. |
META_E_QUEUE_DOES_NOT_EXIST |
0x800070A2 |
Failure to access MDS queue: An attempt to attach to the MDS queue was made and it does not exist. Not necessarily an error. At startup there is an attempt to detect orphaned queues by a failed attach. This is not under user control. |
META_E_QUEUE_ALREADY_EXIST |
0x800070A3 |
MDS queue already exists: Attempt to create the MDS queue and it already exists. This is not under user control. |
META_E_QUEUE_NO_MSG |
0x800070A4 |
No messages in queue: A read of the message queue was made with the option to not wait for a message set to true and there are no messages. Not necessarily an error. This is not under user control. |
META_E_MDS_RESERVED_CLASS |
0x80007100 |
Invalid Class: An attempt was made to create an object of the MetaObjectClass class type (ClassID= 107). This is an internal MDS class and can not be used to create user objects. |
META_E_UNKNOWN_ COMPARISON_OPERATOR |
||
|
0x80007101 |
Invalid operator: An invalid comparison operator has been specified in a CMetaFilterInfo object. |
META_E_UNKNOWN_LOGICAL_OPERATOR |
0x80007102 |
Invalid operator: An invalid logical operator has been specified in a CMetaFilterInfo object. |
META_E_UNDERSPECIFIED_ PROPERTY |
0x80007103 |
Unidentified property: The CMetaFilterInfo object contains a value which has neither the PID nor the name of the property set to identify the property.
|
META_E_REGEX_COMPARISON_OPERATOR_REQUIRES_STRING_OPERAND |
||
|
0x80007104 |
Invalid search operator: The REGEX comparison operator can only be used to search properties with a character type. |
META_E_CREATE_GUID_FAILED |
0x80007105 |
Network failure: The system call to create a GUID to uniquely identify a new object failed. This can be caused by the absence of a network card or a bad network card. |
META_E_UNSUPPORTED_TERADATA_RELEASE |
||
|
0x80007107 |
Incompatible database version: Indicates that the repository is on a system with an unsupported release of Teradata. See the Teradata Meta Data Services Administrator Guide (B035‑3118) for a list of supported releases. For the MetaLoad utility, can indicate that the system being loaded has a version of Teradata lower than V2R4.0. |
META_E_ANOTHER_ACTION_ PROCESSOR_IS_RUNNING |
||
|
0x80007108 |
Duplicate Action Processor running: Attempt to run another Action Processor while one was running. Only one AP may run against a given repository |
META_E_OBJECT_LOCKED_ AND_NOWAIT_SPECIFIED |
||
|
0x80007109 |
Table locked: A select statement was returned because the table to read was locked and no wait time was specified. This code is used internally by MDS. |
META_E_XML_ERROR |
0x8000710A |
XML error: A general XML script error occurred. Normally an XML Scripting Error Codes will be returned. |
META_E_SYSTEM_NAME_NOT_ FOUND |
0x8000710B |
Invalid system name: The metaload utility, while running with the option to resync previously loaded databases, detected that the system name specified does not exist. |
META_E_NO_DATABASES_ LOADED |
0x8000710C |
No databases loaded: The metaload utility, while running with the option to resync previously loaded databases, detected that the no databases have been loaded.
|
META_E_PROPAGATION_DELETE_LIMIT_REACHED |
||
|
0x8000710D |
Too many objects deleted: System resources limit the number of objects that can be deleted in one delete object transaction. The object being deleted has relationships with Propagate Delete set to true. The number of objects to delete through propagate deletion when deleting this object exceeds the system limit. Delete the collection objects for this object before the object can be deleted. |
Note: The call to ODBC to rollback this transaction will likely timeout and log a SQL_TIMEOUT error in the MDS error log. This is because the ODBC function uses the CONNECT timeout value which defaults to 20 seconds and this may not be sufficient time for Teradata to roll back the transaction. The transaction, however, will be rolled back. |
||
META_E_NAME_EXCEEDS_ THIRTY_CHAR |
0x8000710E |
Invalid system name: Teradata System Names are limited to 30 bytes. |
META_E_RELPROPID_MUST_BE_GREATER_THAN_ZERO |
||
|
0x8000710F |
Invalid Property ID: The Relative Property ID when creating a CMetaProperty object must be greater than 0. |
META_E_USER_NOT_SIGNED_ON |
0x80007110 |
User not logged on: MDS User is not logged on to MDS. |
META_E_TABLE_ALREADY_EXISTS |
0x80007111 |
Duplicate repository table: The MDS repository table already exists. Used internally by the metamigrate program. |
META_E_TIMEOUT_EXPIRED |
0x80007112 |
Time out for SQL command: The maximum time set for a SQL command expired and the command was aborted. |
META_E_METALOAD_SYSTEM_LOGIN_NOT_SET |
||
|
0x80007113 |
Repository not in sync with database: If the DIM Update Gateway detects that the MDS repository has become out of sync with a Teradata Database, during its recovery schedule, it calls the metaload utility to resync the database. The metaload utility uses the database connection in the System object to connect to the Teradata Database Systems. The database connection must have been set in the System object (using the MetaManager). |
META_E_NO_DELETE_DIM_UPDATEABLE_SYSTEM |
||
|
0x80007114 |
System cannot be deleted: Cannot delete a System which has DIM Updates Enabled. |
META_E_INVALID_SCRIPT_TYPE |
0x80007115 |
Invalid script type: metaclient was unable to determine what type of Client Load script is being processed. metaclient supports Fastload, Multiload and TPump scripts. |
META_E_BAD_ATTRIBUTE_INFO |
0x80007116 |
Invalid attribute: metaclient has determined that the attribute information associated with a Field or Column definition is invalid. |
META_E_NO_DATA_SOURCE |
0x80007117 |
Missing data source: metaclient has determined that no data source has been specified in the Client Load script being processed |
META_E_BAD_DEFINE_STMT |
0x80007118 |
Invalid script: metaclient has determined that the Define statement in a Fastload script contains invalid information. |
META_E_BAD_INSERT_STMT |
0x80007119 |
Invalid script: metaclient has determined that the Insert statement in a Fastload or Multiload script contains invalid information. |
META_E_BAD_OUTPUT_FILE_DATA |
0x8000711A |
Invalid script: metaclient has determined that the Output file associated with the Client Load script being processed contains invalid information. |
META_E_NULL_THIS_PTR |
0x8000711B |
Invalid pointer: The object pointer from which the function was invoked is a NULL pointer.
|
META_E_REPOSITORY_IS_CURRENT_RELEASE |
||
|
0x8000711C |
Migration not needed: metamigrate was run to migrate an MDS repository that is already at the current release level. |
META_E_DATABASE_DOES_NOT_EXIST |
0x8000711D |
Invalid database: The default database in the MDS database connection DSN is not a valid Teradata Database. Used internally by MDS. |
META_E_METALOAD_CHILD_PROCESS_DIED |
||
|
0x8000711E |
Database load failed: When metaload runs to initially load databases in a system, the utility runs as two processes. This error indicates that the child process died. Look in the MDS error log for reasons for the termination. Rerun metaload to recover.
|
META_E_METALOAD_PARENT_PROCESS_DIED |
||
|
0x8000711FL |
Database load failed: When metaload runs to initially load databases in a system, the utility runs as two processes. This error indicates that the parent process died. Look in the MDS error log for reasons for the termination. Rerun metaload to recover. |
META_E_SECURITY_PROFILE_IN VALID |
0x80007140 |
The ID specified for the Security Profile ID is not the ID of an existing Security Profile. |
META_E_INTERNAL_ERROR |
0x80007141 |
An MDS internal error occurred. Send the error log to global support. |
META_E_OBSOLETE_PROPERTY |
0x80007142 |
The ID of the ApplicationGroupID or the AccessRights is specified in the list to sort or search by. These properties have been eliminated. |
Obsolete code - no longer used |
0x80007143 |
|
META_E_DDL_PARSING_FAILED |
0x80007144 |
The DDL Processor could not process a DDL for metaload because the MDS parser could not parse the statement. |
META_E_UNKNOWN_DATABASE S_FOR_DDL |
0x80007145 |
The DDL Processor could not process a DDL for metaload because not all of the referenced databases were defined in the DIM. This status is no longer used. |
META_E_DERIVED_CLASS_CON FLICT |
0x80007146 |
Attempt to create a non-derived property in a derived class. Derived properties can only be created in derived classes. |
META_E_DERIVED_PROPERTY_ CONFLICT |
0x80007147 |
Attempting to create a derived property in a nonderived class. Derived properties can only be created in derived classes.
|
META_E_DERIVED_CLASS_WRIT ES_NOT_ALLOWED |
||
|
0x80007148 |
Attempt to specify a derived class id when creating a new object. Objects can only be created for non-derived classes. |
META_E_DERIVED_PROPERTY_ RELATIONSHIP_ERROR |
||
|
0x80007149 |
The RelationshipsToProperty specified for this derived property conflicts with a derived property which already exists for this derived class. All derived properties in a class must be in the same relationship hierarchy.
|
META_E_BASE_PROPERTY_NA ME_NOT_FOUND |
||
|
0x8000714A |
The BasePropertyName specified for this derived property is not the name of a property in the origin class of the relationship as specified by the RelationshipsToProperty parameter. |
META_E_MAX_SECPROFILE_PE RMISSIONS_EXCEEDED |
||
|
0x8000714B |
Attempt to add more than 100 permission entries to a security profile. |
META_E_INVALID_PROPERTYDE SC_PTR |
0x8000714C |
An invalid CMetaPropertyDesc pointer was passed into the CMetaClassDesc:: CreateMDSPropertyDesc, CreateMDSDerivedProperty, CreatePropertyDesc or GetPropertyDesc function. Make sure the variable was initialized to NULL on the stack. |
META_E_INVALID_CLASSDESC_ PTR |
0x8000714D |
An invalid CMetaClassDesc was passed into the CMetaAIM:: CreateMDSClassDesc, CreateMDSDerivedClass, CreateClassDesc or GetClassDesc function. Make sure the variable was initialized to NULL on the stack. |
META_E_INVALID_RELATIONSHI PDESC_PTR |
0x8000714E |
An invalid CMetaRelationshipDesc was passed into the CMetaAIM::CreateMDSRelationshipDesc, CreateRelationshipDesc, or GetRelationshipDesc function. Make sure the variable was initialized to NULL on the stack. |
META_E_DATABASE_NOT_LOAD ED |
0x8000714F |
This is an internal status originally introduced to relay error information from the DDL Processor to metaload. The status is no longer used. |
META_E_COLUMN_DOES_NOT_ EXIST |
0x80007150 |
This is an internal status originally introduced to relay error information from the DDL Processor to metaload. The status ices a column that is not defined in the DIM. |
META_E_CANNOT_ALTER_COLU MN |
0x8000715 |
MDS issued a SQL statement to alter a table column and Teradata indicated that the change is not permitted.
|
META_E_DEST_CANNOT_BE_A_ DERIVED_CLASS |
||
|
0x80007152 |
When creating a Relationship Description, the Destination Class cannot be the class ID of a derived class. |
META_E_ORIG_CANNOT_BE_A_ DERIVED_CLASS |
||
|
0x80007153 |
When creating a Relationship Description, the Origin Class cannot be the class ID of a derived class. |
META_E_UNBALANCED_PARENT HESES |
0x80007154 |
The sum of the Open Parentheses counts set in each CMetaFilterInfo object in the MetaFilterInfoVector parameter must match the sum of the Close Parentheses counts set. |
MET A_E_ALREADY_MIGRATED |
0x80007155 |
The current repository has already completed the migration process. |
META_E_NO_SPL_TEXT |
0x80007156 |
Metaload has determined that a Stored Procedure does not have any text associated with it in Teradata. |
META_E_BASECLASSID_IS_NOT_A_VALID_CLASS |
||
|
0x80007157 |
The class ID specified for the base class of a Derived Class is not the ID of an existing class. |
META_E_BASECLASS_CANNOT_ BE_A_DERIVEDCLASS |
||
|
0x80007158 |
The class ID specified for the base class of a Derived Class cannot the ID of a Derived Class. |
META_E_INVALID_SP_VERSION |
0x80007159 |
Metaload attempted to load a stored procedure that has a version that is not compatible with the current Teradata Database Systems server release. (See Teradata Error Code –5559) |
META_E_FETCH_NEXT_ROW_END_OF_RESULTS |
||
|
0x80007180 |
Used internally by MDS. Indicates that there are no more rows to be retrieved in the buffer |
META_E_MAX_PROPERTIES_PER_CLASS_EXCEEDED |
||
|
0x80007181 |
The maximum number of properties than can be defined for a class has been exceeded. The limitation is determined by the "properties" field of the metaclassdesc table in the MDS repository. The column is 32000 bytes. This is enough space to allow for 696 properties or 307 derived properties. |
META_E_TERADATA_MAX_STRING_SIZE_EXCEEDED |
||
|
0x80007182 |
The value of a string size has been set too large. The Teradata limit is 31000 bytes. |
META_E_SECURITY_PROFILE_LIMIT_EXCEEDED |
||
|
0x80007183 |
The MetaSurf business search will fail if more than 512 security profiles are defined on objects in the business search tables. You must run the search as the meta super user (metasu) or reduce the number of security profiles.
|
META_E_A_ABSTRACT_CLASS_HAS_NO_OBJECTS |
||
|
0x80007184 |
You cannot create an object in a class that has been defined as an abstract class. Abstract classes do not have objects. |
META_E_CANNOT_DELETE_A_SUPERCLASS |
||
|
0x80007185 |
A superclass cannot be deleted if there are existing subclasses inheriting from this superclass. You must delete all the subclasses before a superclass can be deleted |
META_E_MACRO_DOES_NOT_EXIST |
0x80007186 |
A macro used by MDS does not exist in the MDS repository. Used internally by MDS |
META_E_SUPERCLASS_CANNOT_BE_A_DERIVEDCLASS |
||
|
0x80007187 |
The class ID specified for a superclass class when creating a class is the ID of a derived class. A derived class cannot be a superclass |
META_E_SUPERCLASS_IS_NOT_A_VALID_CLASS |
||
|
0x80007188 |
The class ID specified for a superclass class when creating a class is not the ID of a valid class |
META_E_MAX_ALLOWED_SUPERCLASSES_EXCEEDED |
||
|
0x80007189 |
This error means that the superClasses list passed by the application when creating a class has more than one entry. |
META_E_CANNOT_DELETE_INHERITED_PROPERTY |
||
|
0x8000718A |
An attempt is being made to delete a property description in a class that is a property of one of the class's superclasses. The property can only be deleted from the superclass |
META_E_CANNOT_ADD_SUPERCLASS_WITH_PROPERTIES |
||
|
0x8000718B |
When modifying the superclass list of a class description, only a class with no properties can be added to the superclass list. |
META_E_CANNOT_REMOVE_SUPERCLASS_WITH_PROPERTIES |
||
|
0x8000718C |
When modifying the superclass list of a class description, only a class with no properties can be removed to the superclass list.
|
META_E_UPGRADE_MDS_SOFTWARE |
0X80007194 |
The version of the MDS repository is greater than the current version of the MDS software. This means you are using the wrong repository for the current MDS software version. Either run MetaManager to point to a different repository or install the version of MDS software that matches the repository version. |
META_E_UPGRADE_ODBC_DRIVER |
0X80007195 |
MDS cannot use the current ODBC driver because the version is incompatible with the repository. For MDS 13.0 and later, the minimum acceptable ODBC driver version is 12.00.00.00 and later. |
META_E_RELPROPID_MUST_BE_GREATER_THAN_500 |
||
|
0X80007196 |
The RelativePropID for a new class property must be greater than 500. Property IDs from 1 to 500 are reserved for internal MDS use. This error is returned by CMetaClassDesc::CreateMDSPropertyDesc. |
META_E_UNKNOWN_KANJI_TRANSLATE_FUNCTION |
||
|
0X80007194 |
This message occurs only with a Teradata Database that has DBC information indicating that Kanji data may be used and metaload determines that system being loaded has a Kanji database but the Teradata Database does not support all of the Kanji translation functions it needs. Metaload will not terminate if one of the tables is not loaded. However, if none of the tables are loaded, metaload will terminate. The Kanji translations required by MDS are: |
META_E_MUST_BE_A_SUPERUSER |
0x800071A0 |
Some changes to the MDS repository are restricted to MDS users with super user privileges. Examples are creating a super user, dropping a user, or executing metacreate, metamigrate, or metadelete |
META_E_OBJECT_FROZEN |
0x800071A1 |
The application is attempting to update an inactive version of an object or an object that is protected by MDS. Only the highest numbered version of an object may be modified. |
META_E_NO_MORE_VERSIONS |
0x800071A2 |
The application is attempting to update an object by using WriteObject() and a new version of the object must be created. The maximum number of versions (2,147,483,647) for the object has been reached and a new version can not be created. To resolve this situation, delete the object and recreate the object and setup all of the collections to which it belongs. |
META_E_NOT_CURRENT_VERSION |
0x800071A3 |
The application has called an API that requires the local object ID, also known as the loid, to specify the latest version of an object. If you are adding a loid to a collection, that is, AddToDestCollection, AddToOrigCollection, and so on, the origin loid must be for the latest version of an object. |
META_E_LABEL_NOT_DEFINED |
0x800071A4 |
The application has specified a label parameter that is not currently defined in the Repository. |
META_E_REPOSITORY_VERSIONING_NOT_ENABLED |
||
|
0x800071A5 |
The application is trying to enable data versioning for a model, but the Repository does not allow data versioning. Data versioning can be enabled with the -v on parameter to metacreate or metamigrate. |
META_E_METAMODEL_VERSIONING_NOT_ENABLED |
||
|
0x800071A6 |
The application is trying to enable data versioning for a class, but a metamodel containing the class does not allow data versioning. An entry in the MDS log should identify the metamodel preventing the change. |
META_E_LABEL_NOT_USED |
0x800071A7 |
CMetaObject::FindLabel could not find a version of the object that used the specified label. |
META_E_UNIQUE_DEST_VERSIONS_VIOLATED |
||
|
0x800071A8 |
When adding entries to a collection (for example, AddToDestCollection or ReplaceDestCollection), MDS has determined that the application is trying to have the origin object point to two versions of the same destination object. |
META_E_NO_VIRTUAL_CIRCUITS |
0x800071A9 |
The application is doing a CMetaRepository::Initialize or CMetaRepository::SignOn and Teradata has refused a connection request because it has no more virtual circuits |
META_E_LABEL_IN_USE |
0x800071AA |
The –L parameter to metaload specifies a label that has already been used to label objects in the repository. |
META_E_ROW_TOO_LONG |
0x800071B0 |
The read of an object has failed because the SQL generated by MDS requires a result set that exceeds the maximum allowed by Teradata. This error is mainly expected with the read of a derived object. |
META_E_DB_OUT_OF_SPOOL_SPACE |
0x800071B1 |
The API call has failed because there is insufficient spool space in the repository database to return the results of a query. |
META_E_DORMANT_OBJECT |
0x800071B2 |
The read or update of an object failed because the object is currently dormant. Dormant objects may only be accessed by MDS Administrator users and only through special APIs. |
META_E_DORMANT_OBJECTS_NOT_SUPPORTED |
||
|
0x800071B3 |
The API requested information on dormant objects, but the Repository does not support dormant objects or the class does not support dormant objects. Dormant objects are limited to tables and views. |
META_E_SYSTEMNAME_EXCEEDS_256_CHARS |
||
|
0x800071C0 |
A WriteObject has failed because the name of a DIM System object is limited to 256 characters. |
META_E_METALOAD_ABORT_REQUESTED |
||
|
0x800071C1 |
The user has requested the abort of a metaload started by the MetaManager utility |
META_E_MDS_VIEWS_NOT_INSTALLED |
||
|
0x800071C2 |
When the metaload utility is loading the data dictionary from a Teradata 12.0 or later system, the MDS views must be present in the system’s DBC database. Use the metaviews utility to load the required views. |
META_E_MUST_BE_UNIX_ROOT_USER |
0x800071C3 |
The user trying to execute an MDS utility on a Linux system does not have root access. |
META_E_METALOAD_BUFFER_OVERFLOW |
0x800071C4 |
Internal metaload status – should never be seen by an application other than metaload |
META_E_METALOAD_RESYNC_NEEDS_UTF16 |
||
|
0x800071C5 |
A metaload resync has been requested and metaload needs to be able to use UTF-16 as the session character set with the system being loaded. The UTF-16 session character set should be installed on the system being loaded and on the system containing the MDS repository.
|
META_E_MISSING_REQUIRED_DESCRIPTION |
||
|
0x800071D0 |
WriteObject: the Description property for the object must be non-null CMetaClassDesc::ChangeDescriptionRequired: DescriptionRequired property for the class cannot be set to true because one or more existing objects in the class do not have descriptions. |
META_E_REQUIRED_PROPERY_NOT_ALLOWED_IN_MODEL |
||
|
0x800071D1 |
The DescriptionRequired property for a class cannot be set to true when the class is in one of the protected metamodels (DIM, MDSbase, CLM and CWM) |
META_E_MISSING_REQUIRED_PROPERTY |
0x800071D2 |
A WriteObject has failed because a required property does not contain a value. |
META_E_PROPERTY_RENAME_NOT_ALLOWED |
||
|
0x800071D3 |
A WriteObject of a CMetaPropertyDesc object has failed because a rename of the object was requested. Properties cannot be renamed after they have been created. |
META_E_UPGRADE_MDS_VIEWS |
0x800071D5 |
Metaload cannot load the system's data because the MDS views installed in the system's DBC database are not for the current version of MDS. Run metaviews for the system and then resubmit your metaload request. |
META_E_WRONG_VERSION_FOR_MIGRATION |
||
|
0x800071D6 |
Metamigrate cannot migrate a repository that is for a version of MDS greater than the current MDS version. |
META_E_MAY_NOT_UNLOAD_SYSUDTLIB |
0x800071DA |
Metaload will not unload the database SYSUDTLIB when the load of UDTs or UDFs are enabled. |
META_E_UDT_DOES_NOT_EXIST |
0x800071DB |
Metaload or DIM Update could not resolve the relationships for an object because it references an unknown UDT. This means the database SYSUDTLIB has not been loaded or it has not been resync’d recently. |
META_E_UDF_DOES_NOT_EXIST |
0x800071DC |
Metaload or DIM Update could not resolve the relationships for an object because it references an unknown function. This could mean that the database containing the function is not loaded or that the database has not been resync’d recently. |
META_E_AMP_DOWN |
0x800071DD |
The system containing the repository database has a down AMP which prevents MDS from writing to a repository table. |
META_E_TERADATA_SQL_ERROR |
0x800071E0 |
An SQL statement issued by an MDS component was rejected by Teradata because of a syntax error. |
META_E_BEST_FIT_UDF_ERROR |
0X800071E1 |
A metaload or DIM update could not resolve a function used in a view, macro, stored procedure, or UDF definition to match one of the known function definitions because its parameters do not appear to fit any of the known function definitions. |
META_E_SEC_CONSTRAINT_DOES_NOT_EXIST |
||
|
0x800071EA |
A table column is defined as being a security constraint, but the security constraint is not loaded into the repository. |
META_E_INVALID_CHARACTER_FOUND |
0x800071EB |
MDS could not write to the repository because a character string contains a character that Teradata does not consider to be valid. |
META_E_DEFAULT_VALUE_EXCEEDS_PROPERTY_LENGTH |
||
|
0x800071EC |
The definition of a property has failed because the specified default value is longer than the property's defined length; e.g. specifying a default of 'Unknown' for a property defined with a length of 6. |
META_E_NAME_EXCEEDS_MAX_TERADATA_LENGTH |
||
|
0x800071ED |
An object's name exceeds 128 characters in length. |
META_E_LIMITED_SUPPORT_FOR_TABLE_FUNCTIONS |
||
|
0x800071EE |
MDS does not retain information about the columns returned by a table function. |
META_E_BLANK_NAME_NOT_ALLOWED |
0x800071EF |
A WriteObject has failed because the object has a blank name. |
META_E_CANNOT_QUICKLOAD_DATABASE |
0x800071F0 |
Metaload cannot QuickLoad a database that is currently loaded into the repository without the QuickLoad option. |
META_E_UNTRANSLATABLE_STRING |
0x800071F1 |
MDS received, from Teradata or an application, a character string that could not be translated to Unicode format. |