Teradata SQL Error and Failure Codes from Error 11449 to 11455

SQLServerF1

11449 Internal error in TOS services.
Explanation: This event is reserved for use in situations that should be logically impossible are detected by the TOS
compatibility kernel services. This indicates an internal PDE error.
Generated By: TOS compatibility PDE services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11450 Create/Open of GDO mapfile failed: %$OsError.
Explanation: An error occurred attempting create the memory map file for Globally Distributed Objects.
Generated By: TOS compatibility PDE services.
For Whom: System Support Representative.
Notes: This error forces the node to reboot.
Remedy: Contact the Global Support Center.

11451 Invalid GDO initialization arguments.
Explanation: One of the arguments passed to a PDE Globally Distributed Object initialization service is incorrect. This
indicates a bug in a PDE kernel driver.
Generated By: TOS compatibility PDE services.
For Whom: System Support Representative.
Notes: This error forces the node to reboot.
Remedy: Contact the Global Support Center.

11452 Mapping resident Gdo failed: %$OsError
Explanation: TBD
Generated By: TOS compatibility PDE services.
For Whom: System Support Representative.
Notes: This error forces the node to reboot.
Remedy: Contact the Global Support Center.

11453 Cannot load a GDO.
Explanation: TBD
Generated By: TOS compatibility PDE services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11454 Cannot synchronize GDOs.
Explanation: TBD
Generated By: TOS compatibility PDE services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11455 Cannot read a GDO.
Explanation: TBD
Generated By: TOS compatibility PDE services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 11449 to 11455 received while performing certain operation against Teradata Database or related products.

What are Teradata Database Errors?

In general, each Teradata error message contains the following information:
• The message number.
• The message text. This text is usually returned with the message number. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.
• Generated-by text that indicates the software module which initiated the message. This field serves a diagnostic purpose for support and development personnel.
• A remedy which suggests how to resolve the condition.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *