Teradata SQL Error and Failure Codes from Error 13486 to 08005

SQLServerF1

13486 Channel device went ONLINE to OFFLINE CUA = %X in slot %d
Explanation: An ONLINE channel device reported transitioning to offline by the channel adapter.
Generated By: PDE channel interface driver.
For Whom: System Support Representative.
Remedy: This event is normal and expected if the LPAR or mainframe owning the device is going down for an IPL. If the
event was unexpected, contact the Global Support Center as there may be a problem with the channel path. Otherwise
ignore this message.

13487 Host Channel Driver: line[%d] of %s Could not obtain %d byte free list element.
Explanation: Parse GDO failure – internal free list exhausted.
Generated By: PDE channel interface driver.
For Whom: System Support Representative.
Remedy: This error prevents the Teradata Channel Protocol process from initializing. The channel interface will not go
active on the node where this message was issued. Contact the Global Support Center.

13488 Host Channel Driver: line[%d] of %s Could not allocate %d count NP context blocks.
Explanation: Start NP failure – internal context space exhausted.
Generated By: PDE channel interface driver.
For Whom: System Support Representative.
Remedy: This error prevents the Teradata Channel Protocol process from fully initializing. The channel interface will go active in a degraded mode on the node where this message was issued. Contact the Global Support Center.

13489 Host Channel Driver: line[%d] of %s EnableMasterNP() returned error: %d.
Explanation: Internal service call failed.
Generated By: PDE channel interface driver.
For Whom: System Support Representative.
Remedy: This error prevents the Teradata Channel Protocol process from fully initializing. The channel interface will go active in a degraded mode on the node where this message was issued. Contact the Global Support Center.

13490 Host Channel Driver: NP migrated from node [%d] to node %d.
Explanation: Informational only: an ECS hosted NP has migrated from a own to an up node.
Generated By: PDE channel interface driver.
For Whom: System Support Representative.
Remedy: Informational only. One or more ECS hosted channel connections are now being managed from a node other
than the preferred node recorded in vconfig. Connection will revert to the preferred node when that node rejoins the configuration.

13491 Host Channel Driver: line[%d] of %s PDE service call returned %d error.
Explanation: Initialization failure – PDE service call error.
Generated By: PDE channel interface driver.
For Whom: System Support Representative.
Remedy: This error prevents the Teradata Channel Protocol process from initializing. The channel interface will not go
active on the node where this message was issued. Contact the Global Support Center.

08000 A fatal unexpected error was returned by PDE: %s
Explanation: An error was returned by PDE.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

08001 Starting Gateway
Explanation: The Gateway successfully started.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

08002 A fatal programming fault detected: %s
Explanation: The gateway software detected an progamming error.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

08003 Invalid message type received.
Explanation: The gateway software received a message whose type was in error.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

08004 Message size invalid.
Explanation: The gateway software received a message whose size was in error.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

08005 Message Class is invalid.
Explanation: The gateway software received a message whose class was in error.
Generated By: Gateway
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 13486 to 08005 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 *