Teradata SQL Error and Failure Codes from Error 10303to 10307

SQLServerF1

10303 Invalid segment: Illegal address for a segment.
Explanation: The address passed to a segment service is not within the range of addresses used by the segment subsystem,
or it is not an address in a segment that is accessed by the program. This usually indicates an error in the logic of the
program logging the event.
Generated By: PDE segment subsystem.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10304 Lock conflict: Deadlock with self.
Explanation: The lock requested for a segment conflicts with the lock already obtained for the same segment. This is
typically caused by an error in the logic of the program logging the event.
Generated By: PDE segment subsystem.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10305 Access argument is incorrect.
Explanation: The value of the access argument passed to a segment system service is out of range. This indicates a coding
error in the program that logs the event.
Generated By: PDE segment subsystem.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10306 Length argument is incorrect.
Explanation: The value of the access argument passed to a segment system service is less than one or greater than 4 MB.
This indicates an error in the program that logs the event.
Generated By: PDE segment subsystem.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10307 Lock argument is incorrect.
Explanation: The value of the lock argument passed to a segment system service is out of range. This indicates a coding
error in the program that logs the event.
Generated By: PDE segment subsystem.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 10303to 10307 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.

 

Teradata SQL Error and Failure Codes from Error 10204to 10302

SQLServerF1

10204 Process is not in the yield state.
Explanation: The monresume() service was passed a task identifier for a task that has not yielded a monitor. This is usually
caused by an error in the logic of the program logging the event.
Generated By: PDE monitor services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10205 Monitor is in use by another task
Explanation: The monenter() service was passesd a monitor identifier for a monitor that is already owned by an another
task. This is not an error,this is logged when a task which does not want to wait for a monitor could not get the monitor
immediately
Generated By: PDE monitor services.
For Whom: System Support Representative.
Remedy: No action is needed.

10300 Address is in use.
Explanation: The new location passed to the segrelocate() service is already in use. This is usually caused by an error in
the logic of the program logging the event.
Generated By: PDE segment subsystem.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10301 Invalid segment identifier.
Explanation: The segment identifier passed to a segment system service is not assigned to any segment. This is usually
caused by an error in the logic of the program logging the event.
Generated By: PDE segment subsystem.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10302 Invalid pointer: No segment at this address.
Explanation: The address passed to a segment service is does not point to a segment that is accessed by the program, or
the segment passed to segchange() is a shared segment, or the address passed to segaccessloc() or seggetloc() or the new
location passed to segrelocate () is not aligned on a segment boundary. This usually indicates an error in the logic of the program
logging the event.
Generated By: PDE segment subsystem.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 10204to 10302 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.

 

Teradata SQL Error and Failure Codes from Error 10198to 10202

SQLServerF1

10198 Force a TPA restart. Restart reason is: %s
Explanation: This event is logged when the TPA is intentionally restarted, either by the operator or some DBS utility,
such as reconfig.
Generated By: PDE restart.
For Whom: Operator.
Remedy: None. This message is for information only.

10199 Assertion failed.
Explanation: This event code is reserved for internal use. It is generated by debugging code for diagnosing unexpected
internal states. This code is omitted in software released to the field.
Generated By: PDE kernel drivers.
For Whom: System Support Representative.
Notes: This error forces the node to reboot.
Remedy: Contact the Global Support Center

10200 Monitor ID is not assigned.
Explanation: A monitor service was passed a monitor identifier that is not allocated. This could be due to passing a bad
monitor id argument, or the monitor could have been deallocated by another task.
Generated By: PDE monitor services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10201 Process is not in the monitor.
Explanation: A monleave(), mondetach(), or monyield() service was passed a monitor identifier for a monitor that is not
owned by the task. This is usually caused by an error in the logic of the program logging the event.
Generated By: PDE monitor services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10202 Process is already in the monitor.
Explanation: The monenter() service was passed a monitor identifier for a monitor that is already owned by the task.
This is usually caused by an error in the logic of the program logging the event.
Generated By: PDE monitor services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 10198to 10202 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.

 

Teradata SQL Error and Failure Codes from Error 10183to 10197

SQLServerF1

10193 Premature return from system call.
Explanation: A task was interrupted while it was sleeping in a system call. This can happen for a variety of reasons,
such as the task being stopped by a debugger.
When a service call returns this event code, the program should normally reissue the call, since nothing is really wrong, but
the call was not completed. For many PDE system calls, the call is automatically reissued, but in some cases the call returns
this error to the caller.
Programs issuing calls that can receive this event code should test for it and proceed accordingly (normally, by reissuing
the call after taking appropriate corrective action), so if this event is logged, it probably indicates a bug in the program that
logged it.
Generated By: PDE scheduler class.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: This event should never be logged. If it is, contact the Global Support Center.

10194 System name limit reached.
Explanation: This event is used when the vpruniquename value got wrap-around. The vpruniquename is used for allocating
unique sysname and monitor. Vpruniquename is an integer field that gets reset after tpareset. Experiement shows
that it probably takes 7 years to use all possible values before wrap-around. Thus this is a very unlikely condition.
Generated By: PDE system services.
For Whom: Operator.
Notes: This will cause the system to reset. As a result, vpruniquename associates with each vproc will get reset back to 0.
Remedy: None. This message is for information only.

10195 Premature return from system call.
Explanation: A task was interrupted while it was sleeping in a system call. This can happen for a variety of reasons, such
as the task being stopped by a debugger.
When a service call returns this event code, the program should normally reissue the call, since nothing is really wrong, but
the call was not completed. For many PDE system calls, the call is automatically reissued, but in some cases the call returns
this error to the caller.
Programs issuing calls that can receive this event code should test for it and proceed accordingly (normally, by reissuing the
call after taking appropriate corrective action), so if this event is logged, it probably indicates a bug in the program that
logged it.
Generated By: PDE scheduler class.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: This event should never be logged. If it is, contact the Global Support Center.

10196 Force a TPA restart with a dump. Restart reason is: %s
Explanation: This event is logged when the TPA is intentionally restarted and a dump is requested. This is normally
done by the operator with a restart command in the DBW supervisor window.
Generated By: PDE restart.
For Whom: Operator.
Remedy: None. This message is for information only.

10197 Force a TPA dump followed by panic dump. Restart reason is: %s
Explanation: This event is logged when the TPA is intentionally resetted and both TPA and panic dump are requested.
This is normally done by the operator with a tpareset -p command.
Generated By: PDE restart.
For Whom: Operator.
Remedy: None. This message is for information only.

Above are list of Teradata Errors or Failure Codes from Error 10193 to 10197 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.

 

Teradata SQL Error and Failure Codes from Error 10187to 10192

SQLServerF1

10187 Force a TPA shutdown by DApowerfail script. Restart reason is: %s
Explanation: This event is logged when the TPA is intentionally shutdown, by the DApowerfail script.
Generated By: DApowerfail Script.
For Whom: Operator.
Remedy: None. This message is for information only.

10188 Priority Scheduler was unable to allocate %u bytes for stats.
Explanation: Priority Scheduler was unable to allocate memory for PG/PPID or CPU stats. Priority Scheduler behavior
is not compromised, but will not be able to collect stats for the schstat tool.
Generated By: PDE system services.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

10189 %s
Explanation: A backtrace is being generated because of the reason specified.
Generated By: PDE system services.
For Whom: PDE developers.
Remedy: For information only, no response is needed.

10190 A call to a sysukevent function has passed in an illegal token.
Explanation: This error is returned if the token passed to a sysukevent function does not identify a valid event. This may
occur because the caller has the incorrect token value, or because the event that it identifies has been freed.
Generated By: PDE sysukevent services
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
Remedy: Contact the Global Support Center.

10191 A call to a SYSLOCK function has passed in an illegal token.
Explanation: This error is returned if the token passed to a syslock function does not identify a valid lock. This may
occur because the caller has the incorrect token value, or because the lock that it identifies has been freed.
Generated By: PDE syslock services
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
Remedy: Contact the Global Support Center.

10192 ERRSYSRESET: Operation aborted because of reset.
Explanation: A task was killed while it was sleeping in a system call due to a TPA reset.
Generated By: PDE scheduler class.
For Whom: System Support Representative.
Notes: This message should not appear in the error log. Its event code is used within the kernel to control reset-time processing,but the task should exit without actually logging the event.The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: This event should never be logged. If it is, report the problem to the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 10187 to 10192 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.

 

Teradata SQL Error and Failure Codes from Error 10182to 10186

SQLServerF1

10182 Teradata restart with dump forced due to a fault in the exception handler for program %s
Explanation: The event is logged when a TPA is automatically restarted because of a fault in the exception handler. The
crash dump should provide more information about the original exception and the subsequent fault in the program mentioned.
Generated By: PDE restart.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

10183 TPA restart force due to %s unexpectedly exiting
Explanation: The event is logged when a critical DBS process is unexpectedly exiting
Generated By: TPA restart
For Whom: Operator.
Remedy: Contact the Global Support Center.

10184 Force a TPA shutdown. Shutdown reason is: %s
Explanation: The event is logged when a TPA is intentionally shutdown.
Generated By: PDE shutdown.
For Whom: Operator.
Remedy: None. This message is for information only.

10185 Priority boosting error detected.
Explanation: An error was detected in the priority boosting logic.
Generated By: PDE scheduler class.
For Whom: PDE developers.
Notes: This event normally causes an automatic DBS restart.
Remedy: For information only, no response is needed.

10186 Unable to obtain Statistics Priority Scheduler (SPS) information.
Explanation: This error indicates a failure to obtain valid SPS information. This can happen for various reasons and does
not represent an error.
Generated By: PDE Scheduler
For Whom: System Support Representative.
Remedy: None. This event should never be logged.

Above are list of Teradata Errors or Failure Codes from Error 10182 to 10186 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.

 

Teradata SQL Error and Failure Codes from Error 10117 to 10181

SQLServerF1

10117 PDE device driver call failed: %$OsError.
Explanation: The call to the PDE device driver failed with the error code shown. This typically indicates an internal PDE
error concerning the service call in question.
Generated By: PDE system services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
Remedy: Contact the Global Support Center.

10118 Syszone RCB elements have exhausted.
Explanation: This is issued after the syszone allocator returns NULL due to non-availability of further elements in the
pool.
Generated By: PDE restart.
For Whom: Operator.
Remedy: Contact the Global Support Center

10119 The Operating System I/O Request Packet elements have exhausted.
Explanation: This event is issued when the operating system call, IoBuildAsynchronousFsdRequest, returns NULL due
to non-availability of IRP elements in the Kernel Pool
Generated By: PDE restart.
For Whom: Operator.
Remedy: Contact the Global Support Center

10180 sysqevent Queue has no tasks to process .
Explanation: This error is returned if the token passed to a sysqevent function sees no tasks in the queue to process, usually
returned by wake function.
Generated By: PDE sysqevent services
For Whom: System Support Representative.
Remedy: nothing.

10181 Desired Priority Scheduler configuration is invalid
Explanation: The desired settings would result in an invalid configuration. The existing Priority Scheduler settings
remain intact.
Generated By: PDE Scheduler
For Whom: System Support Representative.
Remedy: Contact the Global Support Center

Above are list of Teradata Errors or Failure Codes from Error 10117 to 10181 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.

 

Teradata SQL Error and Failure Codes from Error 10112 to 10116

SQLServerF1

10112 System is not ready to issue a PDE service call.
Explanation: A program attempted to use a PDE system service during start-up before the necessary initialization to
perform the service was complete. This typically occurs when the operator tries to run a utility program too soon after a
node is booted, or after a DBS restart.
Generated By: PDE system services.
For Whom: Operator or System Support Representative.
Notes: The necessary state and substate is determined based on the service call attempted. Some programs can run successfully
during PDE initialization and others cannot, depending on which system services they use.
The associated stack trace will help the Global Support Center determine the service in question, if it is necessary to do that.
Remedy: Wait until PDE initialization is complete, then rerun the program that reported the error.

10113 A syszone resource could not be acquired.
Explanation: A task was killed while it was sleeping in a syszone allocation call. This can happen when the TPA is
restarted because the system is hung due to exhaustion of some syszone resource.
Generated By: PDE system services.
For Whom: System Support Representative.
Notes: The associated stack trace will help the Global Support Center determine the exact reason for the error.
Remedy: Although this event is expected in cases of syszone exhaustion, the reason that the system ran out of resources
needs to be investigated. That is typically due to a resource leakage in the DBS.

10114 Could not start %s PDE system daemon.
Explanation: The indicated system daemon could not be started.
Generated By: PDE system services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
Remedy: Contact the Global Support Center.

10115 A call to a sysqevent function has passed in an illegal qevent token.
Explanation: This error is returned if the token passed to a sysqevent function does not identify a valid event. This may
occur because the caller has the incorrect token value, or because the event that it identifies has been freed.
Generated By: PDE sysqevent services
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
Remedy: Contact the Global Support Center.

10116 A call to sleep has resulted in a TIMEOUT wakeup.
Explanation: A task was sleeping, and a timeout (requested on the call to sleep) has triggered.
Generated By: PDE syssleep.
For Whom: The code that asked for the sleep has to check for this value.
Remedy: None. This is for information only.

Above are list of Teradata Errors or Failure Codes from Error 10112 to 10116 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.

 

Teradata SQL Error and Failure Codes from Error 10106 to 10111

SQLServerF1

10106 Invalid address for argument 6.
Explanation: The kernel could not access data pointed to by sixth argument to a PDE system service call. This typically
indicates a coding error in the program that logged the event.
Generated By: PDE kernel service calls.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10107 Invalid address for argument 7.
Explanation: The kernel could not access data pointed to by seventh argument to a PDE system service call. This typically
indicates a coding error in the program that logged the event.
Generated By: PDE kernel service calls.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10108 Invalid address for argument 8.
Explanation: The kernel could not access data pointed to by eighth argument to a PDE system service call. This typically
indicates a coding error in the program that logged the event.
Generated By: PDE kernel service calls.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10109 Invalid address for argument 9.
Explanation: The kernel could not access data pointed to by ninth argument to a PDE system service call. This typically
indicates a coding error in the program that logged the event.
Generated By: PDE kernel service calls.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10111 Resource limit is exceeded.
Explanation: This event code is reserved for future use.
Generated By: PDE system services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: This event should never be logged. If it is, report the problem the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 10106 to 10111 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.

 

Teradata SQL Error and Failure Codes from Error 10101 to 10105

SQLServerF1

10101 Invalid address for argument 1.
Explanation: The kernel could not access data pointed to by first argument to a PDE system service call. This typically
indicates a coding error in the program that logged the event.
Generated By: PDE kernel service calls.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10102 Invalid address for argument 2.
Explanation: The kernel could not access data pointed to by second argument to a PDE system service call. This typically
indicates a coding error in the program that logged the event.
Generated By: PDE kernel service calls.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10103 Invalid address for argument 3.
Explanation: The kernel could not access data pointed to by third argument to a PDE system service call. This typically
indicates a coding error in the program that logged the event.
Generated By: PDE kernel service calls.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10104 Invalid address for argument 4.
Explanation: The kernel could not access data pointed to by fourth argument to a PDE system service call. This typically
indicates a coding error in the program that logged the event.
Generated By: PDE kernel service calls.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

10105 Invalid address for argument 5.
Explanation: The kernel could not access data pointed to by fifth argument to a PDE system service call. This typically
indicates a coding error in the program that logged the event.
Generated By: PDE kernel service calls.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 10101 to 10105 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.

 
1 48 49 50