Teradata SQL Error and Failure Codes from Error 13838 to 13849

SQLServerF1

13838 Error in startup file: %s File: %s line %d Line: %s
Explanation: The specified error was detected processing one of the PDE startup specification files. The file name and
line number where the error occurred are shown, along with the text of the line, up to the point just before the error wasdetected; the word in error is typically the one following the text shown.
The error is typically a generic synatx error, which probably indicates a misspelled keyword, unexpected punctation, a
number where a word was expected or vice versa, or some other unexpected constuct in the file.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: If the error occurred in the site’s own startup specification file in the PDE Configuration directory, correct theerror and restart PDE. If the error is in the startup file for one of the Teradata components, contact the Global Support Center for assistance in correcting the problem.

13839 Error in startup file: Identifier already defined File: %s line %d Line: %s
Explanation: An error was detected processing one of the PDE startup specification files. The file name and line number
where the error occurred are shown, along with the text of the line.
The specified vproc type or GDO number has already been defined, possibly in another startup file that was processed previously.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: If the error occurred in the site’s own startup specification file in the PDE Configuration directory, correct the error and restart PDE. If the error is in the startup file for one of the Teradata components, contact the Global Support Center for assistance in correcting the problem.

13840 Error in startup file: Invalid identifier File: %s line %d Line: %s
Explanation: An error was detected processing one of the PDE startup specification files. The file name and line number
where the error occurred are shown, along with the text of the line.
The specified vproc type, GDO, partiton or state number is not within the range of values allowed. Vproc types range from 0 to 15. GDO numbers range from 1 to 44. Partition numbers range from 0 to 47. State and substate numbers range from 0 to 255.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: If the error occurred in the site’s own startup specification file in the PDE Configuration directory, correct the error and restart PDE. If the error is in the startup file for one of the Teradata components, contact the Global Support Center for assistance in correcting the problem.

13841 Error in startup file: Invalid GDO size File: %s line %d Line: %s
Explanation: An error was detected processing one of the PDE startup specification files. The file name and line number
where the error occurred are shown, along with the text of the line.
The maximum size specified for a GDO is too large. No GDO can exceed 4 MB in size.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Site-specific startup files should not define these constructs, so this error should not occur in the field. If it does, contact the Global Support Center for assistance.

13842 Error in startup file: Missing or invalid GDO name File: %s line %d Line: %s
Explanation: An error was detected processing one of the PDE startup specification files. The file name and line number
where the error occurred are shown, along with the text of the line.
The name for a GDO is either missing for a GDO that requires one, or, if the name is specified, it is too long. A name is required for all GDOs except for ones marked as resident and non-permanent.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Site-specific startup files should not define these constructs, so this error should not occur in the field. If it does, contact the Global Support Center for assistance.

13843 Error in startup file: Unknown variable name File: %s line %d Line: %s
Explanation: An error was detected processing one of the PDE startup specification files. The file name and line number
where the error occurred are shown, along with the text of the line.
The variable name specified in a SET specification is not one of the variables that can be set. Legal SET variables include: tpareconciletimeout Seconds to wait for reconcile process to finish tpacnstimeout Seconds to wait for console daemon to start tpacrashcleartimeout Minutes before before clearing global crash count tpaminsynctimeout Minimum sync point timeout in seconds tpanetdelay Maxumum netconfig phase delay in seconds tpavprcrashlimit Per-vproc crash count limit
tpasyscrashlimit Systemwide crash count limit
tpastoptimeout Seconds to wait for tasks to stop for debugging or a dump tpakilltimeout Seconds to wait for tasks to die before forcibly killing them msgconsbox Message consumer mailbox number msgconsprt Message consumer partition
msgconsvprtype Message consumer vproc type
msgprodprt Message producer partition
msgprodvprtype Message producer vproc type
segfilesize Number of 256MB chunks of segment space
fsgminampslots Min 128KB FSG slots per AMP
fsgmaxampslots Max 128KB FSG slots per AMP
fsgpagespervproc Pages per vproc that FSG will not use
tpamaxnets Number of networks tested for a split net
tpadumpwait Set nonzero to enable waiting for dumps to complete tpanetwait Max secs for all nodes to appear on net
tpabootwait Additional sec for boot startups
tpaselwait Max secs to a select coordinator
pdeassert Set nonzero to debug assert conditions
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: If the name of a SET variable is misspelled, correct the spelling and restart PDE. If the cause of the problem is unclear, contact the Global Support Center for assistance.

13844 Error in startup file: State or substate already defined.

File: %s line %d Line: %s
Explanation: The specified application state or substate has already been defined by a preceding line in a setup file.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

13847 Error in startup file: Unknown system family name File: %s line %d Line: %s
Explanation: An error was detected processing one of the PDE startup specification files. The file name and line number
where the error occurred are shown, along with the text of the line.
The variable name specified in a MIPSFACTOR specification is not a supported system family name.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: If the name of a MIPSFACTOR family name is misspelled, correct the spelling and restart PDE. If the cause of
the problem is unclear, contact the Global Support Center for assistance.

13848 Error in startup file: Cannot set ENV variable: %$OsError File: %s line %d Line: %s
Explanation: An error was detected processing one of the PDE startup specification files. The file name and line number
where the error occurred are shown, along with the text of the line.
The operating system reported an error when trying to set an environment variable for an ENV specification.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

13849 Unable to write clean shutdown status into Teradata Virtual Storage map file %s for vproc
%d due to a file %s error (errno %d).
Explanation: PDE was unable to write a clean shutdown status into the Teradata Virtual Storage map file for the specified vproc during a tpareset. This means that the Teradata Virtual Storage allocator will rebuild this file when the system comes back up from the reset.
Generated By: PDE Initialization.
For Whom: System Support Representative.
Notes: The tpareset continues as normal, though the Teradata Virtual Storage allocator will have to rebuild the Teradata Virtual Storage map file for this vproc when the system comes back up from the reset. This Teradata Virtual Storage map file rebuild is the same behavior that occurs when the system recovers from a node panic or catastrophic node power/hardware failure.
Remedy: Contact the Global Support Center.

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