Teradata SQL Error and Failure Codes from Error 13770 to 13809

SQLServerF1

13770 Unable to start Teradata Virtual Storage vproc(s).
Explanation: During the Teradata Virtual Storage startup phase of PDE intitialization, PDE waits for Teradata Virtual
Storage nitialization to complete. If Teradata Virtual Storage initiallization times out or fails, this message is displayed and
a tpareset occurs.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: This event aborts PDE startup, causing an automatic retry. After three failures, PDE stops retrying and remains
down.
Specific problems related to Teradata Virtual Storage startup are described by previous log entries and the Teradata Virtual
Storage allocator and agent trace log files.
Remedy: This indicates a Teradata Virtual Storage startup problem on this or some other node. Check their logs and
Teradata Virtual Storage trace log files to find the real error and respond accordingly.

13800 Too many memory allocations during TPA initialization.
Explanation: PDE initialization keeps track of the memory it allocates so the memory can be release if initialization fails.
It uses a fixed sized table to do this, with what should be more than enough entries, so if this error occurs, it indicates a bug
in PDE initialization logic.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: This event aborts PDE startup, causing an automatic retry. After three failures, PDE stops retrying and remains
down.
Remedy: An operating system shutdown and reboot may clear up the problem. However, this is probably caused by a
bug in PDE startup logic, which should be reported to the Global Support Center.

13802 Attempt to start %s in vproc %d failed with error code %d.
Explanation: The indicated program could not be started for the reason given. If the program is marked as required in
the startup file that defines it, a TPA restart is initiated. Otherwise, startup continues without the program running.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

13804 Unknown OneNodeAction in Control GDO. Defaulting to commit immediately to disk.
Explanation: The One Node Action flag specified in the Control GDO is not one of the expected values. Since this field is
normally only ever set by programs which validate the field contents before saving it, this may indicate that the Control
GDO has been corrupted.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: PDE initialization continues, with the default One Node Action set to commit immediately to disk, which ensures
database integrity. However, if this was caused by a corruption of the Control GDO, other unpredictable errors may occur.
Remedy: Check the Control GDO setting using ctl. If all other fields appear to be intact, change the One Node Action to
the desired setting. If other fields appear to be corrupted, use the default command to restore all fields to normal values,
then redo any site-specific changes to default settings. Or, remove the control.gdo in the Teradata configuration directory
and reboot the operating system to generate a default Control GDO from scratch.

13805 Required node not available for vproc %d.
Explanation: The VConfig GDO specifies that the virtual processor run on a particular node, and that node is not currently
running.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: The specified vproc is not started, but PDE initialization otherwise continues normally. However, the lack of this
vproc may lead to other problems during DBS startup.
Remedy: When the required node for a vproc is back up, force a TPA restart to get the vproc running again. Verify that
the vproc actually requires a specific node; if not, use vconfig utility to alter the vproc definition to make it movable.
This could also be due to corruption of the VConfig or VprocConfig GDO. Run vconfig -x and vprocgdo to display these
GDOs. If they are not correct, rerun vconfig and force a TPA restart.

13806 No more nodes are available for vproc %d assignment.
Explanation: The TPA startup logic could not find a node where the specified virtual processor could be started. This
probably indicates corruption of the VConfig or VprocConfig GDO.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: This could also be due to corruption of the VConfig or VprocConfig GDO. Run vconfig -x and vprocgdo to display
these GDOs. If they are not correct, rerun vconfig and force a TPA restart.

13807 The operating system error %d returned attempting to locate /dev/cid. PDE will run with no console.
Explanation: The /dev/cid device must be defined in order for the DBS console daemons which communicate with the
DBW database console window to be started. That device does not exist.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: PDE initialization continues without starting the console daemon. The database will come up but DBW cannot be
used.
Remedy: If the system was not intentionally set up to run with no console, define the console devices and force a TPA
restart. Console devices are normally created by the pkgadd for PDE. The safest way to create them if they are missing is to
redo the pkgadd and reboot the operating system.

13809 Console timeout.
Explanation: PDE initialization normally waits for the DBS console daemon to start before going on to start any program
which might try to communicate with DBW. It timed out waiting for this to happen, which probably means that the
console daemon aborted almost immediately after being started.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: PDE initialization continues without waiting for the console to start. The database will come up but DBW probably
cannot be used.
Remedy: Check the console and/or error log for a previous message from the cnscim program that indicates the reason
for the error. If there is such a message, take appropriate action to correct the problem and force a TPA restart. Otherwise,
an operating system shutdown and reboot may clear up the problem.

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