Teradata SQL Error and Failure Codes from Error 13853 to 13865

SQLServerF1

13853 Removing existing vproc %d.
Explanation: This event is logged when PDE initialization removes a virtual processor that is no longer defined in the
system configuration.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: This message is only written to the log file and DBS event log. It does not appear on the console.
Remedy: None needed. This is for information only.

13857 Application not started because the system-wide crash count has reached its limit.
Explanation: The system crash count is increment by PDE when a user/vproc level error logevent occurred. Once this
count reached the predefined limit, PDE will try to come up without starting the database.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Look for preceding error events in the error log file to determine the actual cause of the problem. Correct the
problem indicated and retry starting PDE.

13858 Application not started because the Minimum Node Action or the Clique Failure option in the Control GDO is set to DBS Shutdown.
Explanation: PDE will not start DBS if the Minimum Node Action or the Clique Failure option is set to DBS Shutdown
in the Control GDO and any Clique is down.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: The Minimum Node Action or the Clique Failure option is normally set by the operator with ctl. If it was set
intentionally then this is normal; no action is needed.

13859 Application not started because the Minimum Node Action in the Control GDO is set to Clique-Down or DBS-Down.
Explanation: PDE will not start DBS if the Cliquedown flag is set in the Control GDO and any Clique is down.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: The Single Node Clique option is normally set by the operator with ctl. If it was set intentionally then this is normal; no action is needed.

13860 Default %s GDO created.
Explanation: A GDO that was missing or corrupted has been recreated with all default values by PDE start-up.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: When PDE is first inatalled, or if the GDO was intentionally deleted, then this is normal; no action is needed.

13862 Vproc type %d definition is changed.
Explanation: The site-specific starup file has overridden the definition of one of the standard vproc types. Vproc type
specifications are not normally changed, but it is possible to do so in case special circumstances dictate the need for an override. Since this is an unusual condition, it it logged to alert site support personnel of the anomoly.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: If the vproc type definition has been purposefully overridden, no action is needed. Otherwise, remove the
offending line from the startup file in the PDE configuration directory.

13863 PDE stopped by reconcile.
Explanation: Recond detected condition during the software reconciliation phase of PDE startup which requires PDE to
be stopped. This happens most commonly on software version switch, when reconcile needs to stop the running version of
PDE so that it can install and start a new one. It can also occur in other circumstances when the reconcile program decides PDE should not run on the node. There should be a previous message logged by reconcile giving the reason that it is stopping PDE.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: If this occurs on a software version switch, no action is needed. This is an expected message in that case.
Otherwise, look for a preceding log message from the recond program to determine the actual cause of the shutdown. If it is not apparent how to resolve the problem, contact the Global Support Center.

13864 Minimum clique size set to %d nodes in the Control GDO.
Explanation: The Control GDO contains a field that specifies the minimum number of nodes that must be up in a clique.
This field is automatically set to the number of nodes that must be up to run all of the vprocs that a node might be required to run, taking into account vproc migration when one or more nodes are down. PDE will not start if there are fewer nodes in a clique than this value. A site can modify this field to specify a higher number, but if it is set lower than the minimum threshold, it will be set back to that value on the next startup cycle.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: None needed. This message normally appears when PDE first comes up after Teradata is installed on a system,
or after the Control GDO has been deleted. If someone tries to set the minimum clique size to less than what is needed to support all of the vprocs in any clique, this message appears again on the next PDE startup cycle.

13865 The system configuration requires all nodes in the clique to be up.
Explanation: Systems are normally configured in cliques such that database can run when one or more nodes are down
by migrating vprocs to the remaining nodes in the clique. The current system configuration requires all nodes in this cliqueto be present in order to have enough memory to bring up all of the vprocs assigned to the clique. Therefore, loss of any node will prevent the database from starting.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: The system will run correctly if all nodes in the clique are up, so no immediate action is required. However, inorder to allow the database to run when a node is down, the system must be reconfigured to reduce the number of vprocsor the amount of memory needed per AMP, or to change the hardware configuration to allow more vprocs per node. See the description of event number 11085 for more information about the variables that go into the system size calculation.

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