Teradata RDBMS 错误代码查询指南

需积分: 50 39 浏览量更新于2024-07-31 收藏 4.71MB PDF 举报

"Teradata RDBMS Messages - V2R5.0 & Teradata Tools and Utilities 07.00.00 B035-1096-122A - December 2002" Teradata RDBMS Messages 是一个关于Teradata数据库管理系统错误代码的参考指南，用于帮助用户查询和理解遇到的错误信息。这个资源包含了版本V2R5.0以及Teradata Tools and Utilities 07.00.00的相关消息信息。文档的版本B035-1096-122A发布于2002年12月，由NCR Corporation出版，这是一家在数据库管理系统领域有着丰富经验的公司。 Teradata RDBMS（关系数据库管理系统）是一种高性能、大规模并行处理的数据仓库系统，广泛应用于企业级数据分析。它能够处理海量数据，并且具有高度可扩展性和高可用性。当在使用Teradata时遇到问题，如查询失败或系统异常，这个文档可以作为排查问题的重要工具。用户可以通过错误代码快速定位问题，找到相应的解决策略。文档中可能包括了各种错误代码、其含义、可能的原因以及推荐的解决方案。例如，可能有连接问题、查询语法错误、资源争用问题、权限问题或者系统配置错误等常见问题的描述。每个错误代码都对应详细的解释，有助于数据库管理员和开发人员迅速识别和修复问题。此外，文档中还提到了其他公司的商标，如IBM的CICS、DB2、DFSMS，Digital Equipment Corporation的VAX和VMS，以及Microsoft的Windows和SQL Server等，这些商标表示Teradata系统与其他知名IT产品有接口或兼容性，表明Teradata在多厂商环境中的兼容性和互操作性。通过这个资源，IT专业人员可以更好地管理和维护Teradata环境，确保数据库系统的稳定运行。对于那些处理复杂数据操作和需要解决数据库故障的人来说，这是一个必不可少的参考资料。

Chapter 2: PDE Messages (NCR UNIX MP-RAS)

033-10100 Series SYS Messages

Teradata RDBMS Messages2 – 4

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.

033-10195-00 Force a vproc restart with a

dump. Restart reason is: %s

Explanation: This event is logged when a virtual pro-

cessor 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.

Notes: Single virtual processor recovery is not sup-

ported in this release. Attempting to restart a single

vproc will force a restart of the entire TPA.

Remedy: None. This message is for information only.

033-10196-00 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.

033-10197-00 Force a vproc restart. Restart

reason is: %s

Explanation: This event is logged when a virtual pro-

cessor is intentionally restarted, either by the operator

or some DBS utility program.

Generated By: PDE restart.

For Whom: Operator.

Notes: Single virtual processor recovery is not sup-

ported in this release. Attempting to restart a single

vproc will force a restart of the entire TPA.

Remedy: None. This message is for information only.

033-10198-00 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.

033-10199-00 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 soft-

ware 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.

Chapter 2: PDE Messages (NCR UNIX MP-RAS)

033-10200 Series MON Messages

Teradata RDBMS Messages 2 – 5

033-10200 Series MON Messages

033-10200-00 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 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.

033-10201-00 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 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.

033-10202-00 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 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.

033-10204-00 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 pro-

gram logging the event.

Generated By: PDE monitor services.

For Whom: System Support Representative.

Notes: This event 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.

Chapter 2: PDE Messages (NCR UNIX MP-RAS)

033-10300 Series SEG Messages

Teradata RDBMS Messages2 – 6

033-10300 Series SEG Messages

033-10300-00 Address is in use.

Explanation: The new location passed to the segrelo-

cate() 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 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.

033-10301-00 Invalid segment identifier.

Explanation: The segment identifier passed to a seg-

ment system service is not assigned to any segment.

This is usually caused by an error in the logic of the pro-

gram logging the event.

Generated By: PDE segment subsystem.

For Whom: System Support Representative.

Notes: This event 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.

033-10302-00 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 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.

033-10303-00 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 seg-

ment 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 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.

033-10304-00 Lock conflict: Deadlock with

self.

Explanation: The lock requested for a segment con-

flicts with the lock already obtained for the same seg-

ment. 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 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.

033-10305-00 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 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.

033-10306-00 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 pro-

gram that logs the event.

Generated By: PDE segment subsystem.

For Whom: System Support Representative.

Notes: This event 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.

Chapter 2: PDE Messages (NCR UNIX MP-RAS)

033-10300 Series SEG Messages

Teradata RDBMS Messages 2 – 7

033-10307-00 Lock argument is incorrect.

Explanation: The value of the lock argument passed

to a segment system service is out of range. This indi-

cates a coding error in the program that logs the event.

Generated By: PDE segment subsystem.

For Whom: System Support Representative.

Notes: This event 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.

033-10308-00 Cannot discard an accessed

segment.

Explanation: An attempt was made to discard a

shared segment that is currently being accessed by

other tasks.

Generated By: PDE segment subsystem.

For Whom: System Support Representative.

Notes: This event 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.

033-10309-00 No virtual memory for segment.

Explanation: A segment could not be created because

the virtual address space of the task is full.

Generated By: PDE segment subsystem.

For Whom: System Support Representative.

Notes: This event 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.

033-10310-00 ERRSEGRELOCATED:

Segment is relocated.

Explanation: This event is returned by the seg-

change() service when a segment is moved to a different

virtual address so that it could be increased in size. The

calling program should test for this result and react

appropriately, not enter the event in the log.

Generated By: PDE segment subsystem.

For Whom: System Support Representative.

Notes: The associated stack trace will help the Global

Support Center determine the exact cause of the failure.

Remedy: This event should not appear in the log file.

If it does, contact the Global Support Center.

033-10311-00 No swap space for segment.

Explanation: The system was not able to reserve anon

space to back up a new segment in swap space because

all available space has already been reserved. This prob-

ably means that some program (not necessarily the one

reporting the problem) is not releasing segments when

it should, or that the PDE segment subsystem is failing

to properly account for freed segments.

Generated By: PDE segment subsystem.

For Whom: System Support Representative.

Notes: This event causes an automatic DBS restart.

The associated stack trace will help the Global Support

Center determine the exact cause of the failure.

Remedy: Verify that sufficient swap space is allocated

on the system. If more space is needed, allocate one or

more additional swap partitions, or increase the size of

existing ones on secondary system disks.

Otherwise, if the automatic DBS restart does not clear

up the problem, a UNIX shutdown and reboot should

do so. However, this is possibly caused by a bug in DBS

or PDE software, which should be reported to the Glo-

bal Support Center.

033-10312-00 Cannot allocate SDB structure

for segment.

Explanation: A segment could not be created because

no SDB kernel structure could be allocated for it. This

indicates PDE kernel memory saturation, either because

kernel blocks are being lost, or too many system

resources have been allocated.

Generated By: PDE segment subsystem.

For Whom: System Support Representative.

Notes: This event causes an automatic DBS restart.

The associated stack trace will help the Global Support

Center determine the exact cause of the failure.

Remedy: If the automatic DBS restart does not clear

up the problem, a UNIX shutdown and reboot should

do so. However, this is possibly caused by a bug in DBS

or PDE software, which should be reported to the Glo-

bal Support Center.

033-10313-00 RCB contains an invalid

segment size.

Explanation: This event is logged when an invalid

segment size is passed to the PDE segment subsystem

from the PDE message subsystem. This indicates a PDE

kernel driver problem.

Generated By: PDE segment subsystem.

Chapter 2: PDE Messages (NCR UNIX MP-RAS)

033-10400 Series TSK Messages

Teradata RDBMS Messages2 – 8

For Whom:

System Support Representative.

Notes: This event 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.

033-10314-00 Unable to map seg into user

space.

Explanation: This event is logged when an error is

returned from as_map while trying to map a PDE seg-

ment into the address space of a process. This indicates

a PDE kernel driver problem.

Generated By: PDE segment subsystem.

For Whom: System Support Representative.

Notes: This event 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.

033-10399-00 Unrecoverable error in segment

system.

Explanation: This event is logged for various condi-

tions that should be logically impossible that are

detected by the PDE segment management subsystem.

This indicates a PDE kernel driver problem.

Generated By: PDE segment subsystem.

For Whom: System Support Representative.

Notes: This error forces the node to reboot.

Remedy: Contact the Global Support Center.

033-10400 Series TSK Messages

033-10400-00 Program does not exist.

Explanation: The tskget() service was passed the

name of a program that cannot be found in any of the

default directories for PDE executable files.

Generated By: PDE task management services.

For Whom: System Support Representative.

Notes: This event causes an automatic DBS restart.

The associated stack trace will help the Global Support

Center determine the exact cause of the failure.

Remedy: This may be caused to an error in the

pkgadd the installed that TDBMS or TGTW package. If

the pkgadd failed due to insufficient disk space or for

some other reason, correct the problem, reinstall the

package, and restart the DBS.

If the cause of the problem is unclear, contact the Global

Support Center.

033-10402-00 Process ID is not valid.

Explanation: A PDE task management service has

been given a process identifier for a task that does not

exist, or is not a member of the database scheduling

class (SCHDB). This is usually caused by an error in the

logic of the program logging the event.

Generated By: PDE task management services.

For Whom: System Support Representative.

Notes: This event 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.

033-10404-00 Critical region nesting limit

exceeded.

Explanation: A task is trying entering a critical region

too many times, or leaving a critical region more times

than it has entered one. This is usually caused by an

error in the logic of the program logging the event.

Generated By: PDE task management services.

For Whom: System Support Representative.

Notes: This event 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.

剩余815页未读，继续阅读

ruby512

粉丝: 4
资源: 6

Teradata RDBMS 错误代码查询指南

Teradata SQL Reference Fundamentals

Teradata RDBMS Database Design

Teradata RDBMS SQL

数据仓库专用引擎-Teradata RDBMS.DOC

python-tdadapter:一个Python扩展库，允许通过CLIv2连接到Teradata RDBMS

Teradata Messages (English)

Teradata Vantage - Database Messages.pdf

TeraData

teradata

Teradata-SQL.rar_teradata_teradata sql

最新资源