Teradata SQL Error and Failure Codes from Error 13810 to 13826

SQLServerF1

13810 Vconfig GDO is missing or corrupt.
Explanation: The VConfig GDO was missing or empty when PDE initialization was attempted.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: This error aborts PDE initialization; the VConfig GDO is required in order to bring up PDE.
Remedy: If this is a new system that has not been configured for Teradata, doing that will correct the problem. If vconfig.
gdo is lost on a node of an existing system, copy it from another node, or recreate it from the vconfig.txt file by running
the vconfig utility. GDOs can also be recovered from backup copied in the Backup directory.

13811 Vproc %d cannot be removed.
Explanation: A virtual processor has been removed from the VConfig GDO, but the vproc cannot be removed from the
system because it is not in NewProc state.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: Initialization continues, but the vproc in question is retained in the VprocConfig GDO, which may lead to unexpected
behavior.
Remedy: To remove the vproc, change its state to NewProc using vprocmanager and force a TPA restart. If the vproc
should not be removed, use configuration utility to put it back into the configuration.

13815 Application not started because all AMPs are in NewProc or Fatal state.
Explanation: Any vproc whose state is NewProc or Fatal cannot be started. Currently, all AMPs are in one or the other of
those states. Without AMPs, the database cannot be accessed, so TPA initialization is aborted. PDE is up, but the DBS is not
running.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: If the system is newly installed, or the database is being recreated from scratch, this is normal. Continue with
system initialization by running sysinit, config (if needed), and reconfig. as described in the Field Support Guide.
If this happens because all vprocs have gone into Fatal state, examine the error log files to see why the vprocs failed. Correct
the problem, set the vprocs to Online state with vprocmanager, and force a TPA restart.

13816 Application not started because the Start DBS flag is off in the Control GDO.
Explanation: The Start DBS flag is off in the Control GDO. Since the purpose of this flag is to allow PDE to come up
without starting the database, that is what happened.
The Start DBS flag is normally set by the operator with ctl. However, certain errors during PDE initialization implicitly set
this flag to off, as noted in the message text for those events.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: If the Start DBS flag is off intentionally, this is normal, no action is needed.
If the Start DBS flag was off due to some other error, correct that problem, reset the flag, and force a TPA restart.
If it is not known why the flag is off, try setting the flag and forcing a TPA restart. If it had been off due to an error which
has not since been fixed, the same error will occur again.

13821 Crash loop detected during TPA initialization.
Explanation: In order to prevent PDE initialization from looping forever when an error prevents it from completing, it is
only automatically restarted three times. After three unsuccessful initialization attempts, this message is issued and restart
attempts are discontinued, leaving PDE down.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Examine the error log to determine the reason for the initialization failures. Correct the problem as described
under the message for the event causing the failure, then restart PDE initialization.

13823 Cannot access node list from reconcile: %$OsError
Explanation: The file which communicates the node list determined by software version reconciliation process back to
PDE Initialization could not be accessed. This typically indicates a failure during the reconciliation process. A previous
event reported by the reconcile program may give additional information.
PDE initialization proceeds using the local copy of the VConfig GDO to provide a list of all TPA nodes that are configured
in the system.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Look for a preceding error message from the reconciliation program to determine the actual cause of the problem.
If the TPA comes up correctly despite this error, this message can be ignored.

13824 TPA reset occurred during PDE initialization (PDE event code 033-%d-00).
Explanation: PDE initialization was aborted because one of the programs started during the initialization process
aborted, causing a TPA restart. The event code shown in the message identifies the event that was reported to the initialization
task; this may help identify what state the task was in when it was informed of the reset.
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: Examine the error log file, find the message issued by the task that caused the restart, and proceed accordingly.
Once the problem is resolved, restart PDE.

13825 The VConfig GDO is obsolete.
Explanation: The version field in the VConfig GDO indicates that it was not created by the current vconfig utility. Either
the GDO was created by an obsolete version of vconfig and not converted, or the contents of the GDO have been destroyed.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: This event aborts PDE initialization.
Remedy: Rerun vconfig to create a good vconfig GDO, then restart PDE.

13826 StartDebug flag set in Control GDO. Application will not run until the system debugger is attached.
Explanation: The StartDebug flag in the Control GDO can be used to debug problems early in DBS initialization. When
this flag is set, the DBS start-up programs are put into execution, but not allowed to run until the system debugger is
attached. The programs can then be continued under control of the debugger to catch the problem.
This message is issued when PDE initialization reaches the point that the debugger can be attached when the StartDebug
flag is set.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Attach the system debugger, do whatever preparation is needed for debugging, and continue system execution.
If on-line debugging is not desired, attach the system debugger and immediately detach it to allow the system to come
up normally. If the StartDebug flag had not been intentionally set, turn it off with ctl.

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