OSF DCE Problem Determination Guide

Error Messages and Status Codes

0x1260a89f GDS_S_BAD_SOUNDEX

Severity: Warning Component: gds / GDS_S_GENERAL

Text: Active soundex algorithm: %s, Data are generated with soundex algorithm: %s.\n

Explanation: The Directory Service Agent (DSA) uses a soundex algorithm, that was not

used to generate the data.

Action: Go ofﬂine and run gdschdb to regenerate the phonetical representations of the

data.

0x1260aa9a GDS_S_BADSRT_ENTRY

Severity: Fatal Component: gds / GDS_S_GENERAL

Text: The Structure Rule Table contains an incorrectly formatted entry: %s.\n

Explanation: The speciﬁed Structure Rule Table entry is formatted incorrectly.

Action: This problem may occur due to a change to the schema object by an application

program, that did not use the schema administration of GDS. The error is fatal for

gdsgendb but not for gdsdsa, which continues with the unchanged schema. No action

required. The problem may also occur, when a corrupted database is restored. In this case

it is fatal for the gdsdsa. A consistent database has to be restored in this case.

0x1260a3f2 GDS_S_CACHE_BUFSZ_ERR

Severity: Fatal Component: gds / GDS_S_GENERAL

Text: IPC-communication buffer too small

Explanation: The program was not able to write a message into an IPC- communication

buffer. Normally, messages are fragmented if the message size exceeds the size of a

communication buffer. But sometimes this fragmentation is done on a logical level and

not on a byte level. Thus, this error occurs always, if the size of a logical unit exeeds the

communication buffer size.

Action: The size of the IPC-communication buffer must be increased by means of the -l

conﬁguration parameter (see IPC con- ﬁguration ﬁle).

0x1260a3eb GDS_S_CACHE_DESCR_SZ_ERR

Severity: Fatal Component: gds / GDS_S_GENERAL

Text: Wrong size of description ﬁle (size = %d, should be %d)

Explanation: The program has detected a wrong size of the description ﬁle. This could

indicate a data inconsistency

Action: To determine the reason report the problem to the responsible software engineer.

In the case of a data inconsistency, restore the database to regain a consistent state.

0x1260a3ec GDS_S_CACHE_HASH_SZ_ERR

Severity: Fatal Component: gds / GDS_S_GENERAL

124330 Tandem Computers Incorporated 2−275