Teradata数据库NCR UNIX MP-RAS系统消息指南（V2R6.0）

Teradata

4星 · 超过85%的资源需积分: 3 182 浏览量更新于2024-07-31 收藏 4.01MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源推荐

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

033-10100 Series SYS Messages

Messages2 – 2

033-10100 Series SYS Messages

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

gram that logged the event.

Generated By: PDE kernel service calls.

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-10102-00 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 pro-

gram that logged the event.

Generated By: PDE kernel service calls.

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-10103-00 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 pro-

gram that logged the event.

Generated By: PDE kernel service calls.

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-10104-00 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 pro-

gram that logged the event.

Generated By: PDE kernel service calls.

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-10105-00 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 pro-

gram that logged the event.

Generated By: PDE kernel service calls.

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-10106-00 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 pro-

gram that logged the event.

Generated By: PDE kernel service calls.

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-10107-00 Invalid address for argument 7.

Explanation: The kernel could not access data

pointed to by seventh argument to a PDE system ser-

vice 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 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-10108-00 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 pro-

gram that logged the event.

Generated By: PDE kernel service calls.

For Whom: System Support Representative.

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

033-10100 Series SYS Messages

Messages 2 – 3

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-10109-00 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 pro-

gram that logged the event.

Generated By: PDE kernel service calls.

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-10111-00 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 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.

033-10112-00 System is not ready to issue a PDE

service call.

Explanation: A program attempted to use a PDE sys-

tem service during start-up before the necessary initial-

ization 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 Representa-

tive.

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 neces-

sary to do that.

Remedy: Wait until PDE initialization is complete,

then rerun the program that reported the error.

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

033-10114-00 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 causes an automatic DBS restart.

Remedy: Contact the Global Support Center.

033-10115-00 Invalid process class while using

PDE services

Explanation: A program attempted to use a PDE sys-

tem service without entering schdb class.

Generated By: PDE system services.

For Whom: Operator or System Support Representa-

tive.

Notes: The associated stack trace will help the Global

Support Center determine the service in question, if it is

necessary to do that.

Remedy: Contact the Global Support Center.

033-10189-00 Scheduler DEBUG

INFORMATION. %s id :%d ag:%d nnn:%d

nsets:%d free:%d tset:0x%x tset.ag:%d

tset.npps:%d mmm:%d dbproc:0x%x

tset.pg:%d

Explanation: An error occurred in scheduler data

structures. This has been corrected! This probably indi-

cates a PDE error.

Generated By: PDE Scheduler.

For Whom: System Support Representative.

Remedy: Contact the Global Support Center.

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

033-10100 Series SYS Messages

Messages2 – 4

033-10194-00 System name limit reached.

Explanation: This event is used when the vprunique-

name value got wrap-around. The vpruniquename is

used for allocating unique sysname and monitor. Vpru-

niquename is an integer field that gets reset after tpare-

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

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

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

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.

剩余883页未读，继续阅读

vissalan

粉丝: 0
资源: 14

Teradata数据库NCR UNIX MP-RAS系统消息指南（V2R6.0）

Teradata RDBMS Messages

Teradata Vantage - Database Messages.pdf

teradata sql returns

Teradata的SQL用法特点

Teradata数据库的主要组件

TERADATA的数据请求工具有哪些

teradata和oracle区别

teradata fs-ldm

teradata教程pdf

teradata核心技术是什么？

jdk1.8 连接teradata

Teradata中SUBSTR用法

teradata 查看表是否死锁

teradata group_concat

teradata 有PK嘛

teradata fs

Python 连接teradata

jdk1.8 连接teradata代码

hadoop teradata

teradata sql assistant使用

最新资源