Digital PDFs

AA-PCAXA-TE

June 1990

561 pages

Original

18MB

Document:	ULTRIX/SQL Error Message Dictionary
Order Number:	AA-PCAXA-TE
Revision:	000
Pages:	561
Original Filename:

OCR Text

ULTRIX

ULTRIX/SQL Error Message Dictionary

Order Number: AA-PCAXA-TE
June 1990

Software Version:

ULTRIXlSQL Version 1.0

Operating System and Version:

ULTRIX Version 4.0 or higher

This manual contains supplementary information for ULTRIX/SQL error messages.
ULTRIX/SQL Version 1.0 is based on Release 6.2 of INGRES.

digital equipment corporation
maynard, massachusetts

Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in
subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause of DFARS 252.227-7013.

The information in this document is subject to change without notice and should not be construed as a commitment
by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may
appear in this document.
The software described in this document is furnished under a license and may be used or copied only in accordance
with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital or its
affiliated companies.

The following are trademarks of Digital Equipment Corporation:

mamaama
CDA
DDIF
DDIS
DEC
DECnet
DEC station

DECUS
DECwindows
DTIF
MASSBUS
MicroVAX
Q-bus
ULTRIX
ULTRIX Mail Connection

ULTRIX Worksystem Software
VAX
VAXstation
VMS
VMS/ULTRIX Connection
VT
XUI

UNIX is a registered trademark of AT&T in the USA and other countries.
Network File System and NFS are trademarks of Sun Microsystems, Inc.
INGRES is a trademark of Ingres Corporation.

(

Contents

Preface
Purpose of this Document
Intended Audience
Associated Documents
References to Products

Introduction

1.1

What Is an Error Message? ... .... .... ........................ ................................................ ............

1-1

1.1.1 The Error Code......................................................................................................
1.1.2 Error Message Text"..............................................................................................

1-1
1-1

1.2 Viewing an Error Message.............................................. ..................................................

1-2

1.3 Programming Error-Handling in Embedded Applications .............................................

1-2

AD Class Messages

AF Class Messages

CD Class Messages

CL Class Messages

CO Class Messages

DC Class Messages

DE Class Messages

9 OM Class Messages
10 OU Class Messages
11

EO Class Messages

12 E1 Class Messages
13 E6 Class Messages
14 EO' Class Messages
15 FR Class Messages
16 FT Class Messages
17 FV Class Messages
18 GC Class Messages
19 IC Class Messages
20 LC Class Messages
21

La Class Messages

22 MF Class Messages
23 MO Class Messages
24 OP Class Messages
25 PS Class Messages

Contents

26 QE Class Messages
27 QG Class Messages
28 QR Class Messages
29 QS Class Messages
30 RO Class Messages
31

RQ Class Messages

32 SC Class Messages
33 TO Class Messages
34 TP Class Messages
35 UO Class Messages
36 UF Class Messages
37 UG Class Messages
38 UI Class Messages
39 UL Class Messages
40 US Class Messages
41

XF Class Messages

Contents

(

Preface

Purpose of this Document
The ULTRIX/SQL Error Message Dictionary lists all the ULTRIX/SQL messages
with their codes. Explanations are provided for many of the error messages. This
manual serves as a reference for finding out information about messages that result
from using the ULTRIX/SQL relational database software.

Intended Audience
The ULTRIX/SQL Error Message Dictionary is intended for all users of the
ULTRIX/SQL software. Programmers and database administrators will find it most
useful.

Associated Documents
The following associated manuals are included in your ULTRIX/SQL base system
documentation set:
ULTRIX/SQL Database Administrator's Guide
ULTRIX/SQL NET User's Guide
ULTRIX/SQL Operations Guide
ULTRIX/SQL Reference Manual
ULTRIX/SQL Release Notes

References to Products
The ULTRIX/SQL documentation to which this manual belongs often refers to
products by their abbreviated names:
ULTRIX/SQL refers to ULTRIX/SQL database software and to its
implementation of the SQL language.

Preface

vii

Introduction

This manual lists the error messages for ULTRIX/SQL. An error message is a
message that the ULTRIX/SQL software displays for interactive users or returns to
an application when an error occurs. The manual also includes warning and status
messages.

1.1 The Parts of an Error Message
An error message consists of an error code and accompanying descriptive text. In
addition, error messages that come from the server have a date and time stamp.

1.1.1

The Error Code
An error code always has at least two parts, and often three. The parts are separated
by underscores lJ For example:
E- US138D- 5005

The first part is common to all error codes. It consists of the letter E, W, or S (E for
Error, W for Warning, and S for Status).
The second part consists of a one- or two-letter facility code, followed by a
hexadecimal number. This element is unique for each error code. The facility code
indicates the origin of the error. The hexadecimal number represents a value that is
returned to an application for use in error handling.
The error code's third part, if present, is either a decimal number or a series of letters
which, in abbreviated form, indicate the error. If the third element is a decimal
number, that number is equivalent in value to the hexadecimal number in the second
element.

1.1.2

Error Message Text
The error message text is a one-line or several-line summary of the error and is often
followed by an explanation. The error message text appears immediately after its
error code entry.
In this document, parameters (for example, % lcand %2c) serve as placeholders for
numbers and object names that ULTRIX/SQL provides when it returns an error. For
example, the message text for error E_US157C_5500, as given in this document,
says:
MODIFY:

table %Oc does not exist.

When this message is returned by ULTRIX/SQL, the parameter %Oc is replaced with
the name of the table that the user tried to access.

The parameters indicate the kind of object that will replace them:

1.1.3

•

The letter c indicates a character data type object.

•

The letter d indicates a numeric data type object.

Error Message Explanations
In addition to the error message code and error message text, this document provides
explanations for many of the messages. These explanations have up to four sections:
•

Parameters: a description of the parameters used in the error message

•

Explanation: an expanded description of the error message

•

System Status: the state of the system after the error occurs

•

Recommendations: suggestions for solutions to the error condition

Some recommendations instruct you to submit a Software Performance Report
(SPR). Note that SPRs are answered in accordance with software warranties and the
terms and conditions of your Software Product Service (SPS) contract with Digital
Equipment Corporation.

1.2 Viewing an Error Message
There are several ways to view error messages, depending on how you are interacting
with ULTRIX/SQL.
If you are working in one of the forms-based user interfaces, such as isql or accessdb,
error messages appear on a single line across the bottom of your screen. The error
message text appears first, followed by the error code. If the text extends beyond a
single line, ULTRIX/SQL prompts you to press the specified key to see the
remainder of the message and the error code. To clear an error message from the
screen, press RETURN.
If you are not working in a forms-based user interface, but are working interactively,
ULTRIX/SQL displays the error code first, followed by the message text.
Error messages are not displayed automatically in embedded SQL applications.
Application developers must provide program code for such display. (See Section
1.3 for more information.)

1.3 Error-Handling in Embedded Sal Applications
Embedded SQL programs always return error message numbers and message text to
the application. However, the description is not complete.
To use, display, or print this information, programmers must provide an errorhandling mechanism. Embedded SQL provides the following statements that you can
use to write error-handlers:
•

inquire_sql

•

whenever

The "ULTRIX/SQL Reference Guide to Embedded SQL" contains information on
providing error-handling in embedded SQL applications, as well as descriptions of
each of these statements.

1-2 Introduction

AD Class Messages

E - ADOOOO- OK
ADF successful return status.
E- ADOOOI - EX - IGN - CONT
Expected internal error code ... No message needed. An ADF math exception has occurred
with the math exception option set to ignore.
CHAR
E - ADOIOI - EMBEDDED-TRUNC
Truncation has ocurred while converting a string type data base value into a string type
embedded value.
E - ADOI02- NULL IN TEXT
Warning: Null character(s) converted to blank(s) in text string.
E - ADOl15 - EX- WRN- CONT
Expected internal error code ... No message needed. An ADF math exception has occurred
with the math exception option set to warn.
E - ADOl16EX
UNKNOWN
Expected internal error code ... No message needed. The current exception is not one that
ADF recognizes.
E- AD0120- INTDIV- WARN

E - AD0121 - INTOVF- WARN

E - AD0122- FLTDIV- WARN

E - AD0123- FLTOVF- WARN

E - AD0124- FLTUND- WARN
AD Class Messages

2-1

E - AD0125- MNYDIV- WARN
E AD0126 DECDIV WARN

E - AD0127- DECOVF- WARN

E AD0500 ABS DATE IN AG

E - ADOFFF- NOT- IMPLEMENTED- YET
ADF function has not been implemented yet.
E - ADIOOIBAD
DATE
ADF date format, %Od, is invalid.
E - ADI002 - BAD - MONY - SIGN
ADF money sign, %Oc, is invalid.
E - ADI003 - BAD - MONY- LORT
ADF money sign position designater, %Od, is invalid.
E - ADI004- BAD - MONY- PREC
ADF money precision specification, %Od, is invalid.
BAD
E - ADI005-DECIMAL
Bad decimal character specification, '%Ox'.
E - ADI006- BAD - OUTARG - VAL
Bad output argument specification (Le. one of your OUTARG members is bogus).
E_ADI007_BAD _QLANG
Unknown query language ... query language ID = %Od.
E - ADI008- BAD- MATHEX - OPT
Unknown math exception option, %Od.
E - ADI009BAD
-SRVCB
ADF Server control block passed into adg_initO is invalid.
E - ADIOOABAD
NULLSTR
The 'NULLstring' passed into adg_initO is invalid.

2-2

AD Class Messages

E - ADlOOBBAD
-MAXSTRING
The max size ULTRIX/SQL string given to ADF at session init time (%Od) is invalid. It
must be between = 1 and ~
E - ADlOlO- BAD - EMBEDDED- TYPE
ADF routine was passed an invalid embedded type id.
E - ADlOll - BAD - EMBEDDED - LEN
ADF routine found DB_EMBEDDED_DATA with an invalid length.
TO
E - ADlOl2- NULL-NONNULL
An attempt to place a null value in a non-null able datatype.
E - ADlOl3 - EMBEDDED - NUMOVF
Numeric overflow while converting a data base value into an embedded value.
FOR
DT
E - ADlOl4- BAD- VALUEExpected internal error code ... No message needed. Invalid data for datatype found while
doing value checking.
BAD
E - ADlOl5-RANGE
Illegal pattern match specified. One of the following:
An opening' [' without a closing'] ,
Vice-versa
Range ending with '-]'
Range of the form '[x-y]' where char 'y' comes before 'x'.
E - ADlOl6- PMCHARS IN RANGE
Illegal pattern match specified: You cannot have pattern match characters included in a '[
]' range.
E - ADlOl7- ESC - AT- ENDSTR
Illegal pattern match specified: ESCAPE character at end of string.
E _ ADlOl8 _BAD _ESC _SEQ
Illegal pattern match specified: Illegal ESCAPE sequence. The ESCAPE char must be
followed by one of:
'\%' (percent)
'_' (underscore)
, [' (left square bracket)
']' (right square bracket)
another ESCAPE char.

AD Class Messages

2-3

E - ADI020- BAD - ERROR- LOOKUP
ADF was unable to lookup error code: %Ox
E - ADI021 - BAD- ERROR- PARAMS
adu_errorO was called with a bad argument list.
E - ADI022- BAD - USER - LOOKUP
ADF was unable to lookup the USER error code, %Od
E- ADI02S- BAD- ERROR- NUM
adu_errorO was called with an unknown error code, %Ox
E - ADI030- F - COpy- STR- TOOSHORT
The floating point number being copied will not fit in the field specified. Either give a
longer field, or use a different setting of the -f flag on the command line.
E - ADI040- CV- DVBUF - TOOSHORT
ADF routine, adc_tolocalO, was passed a data value buffer that was too small to do the
conversion from the network standard form.
E - ADI041 - CV- NETBUF- TOOSHORT
ADF routine, adc_tonetO, was passed a buffer that was too small to do the conversion to
the network standard form.
E - ADI0S0- NULL - HISTOGRAM
Expected internal error code ... No message needed. Attempt to create a histogram
element for a NULL value.
E - ADl120 - INTDIV - ERROR

E - ADl121 - INTOVF- ERROR
E - ADl122- FLTDIV- ERROR
E - ADl123 - FLTOVF- ERROR

E - ADl124- FLTUND - ERROR

E - ADl12S - MNYDIV- ERROR

2-4

AD Class Messages

E - ADl126- DECDIV - ERROR

E - ADl127 - DECOVF- ERROR

E - AD2001BAD
OPNAME
ADF routine was given an unknown operater.
E - AD2002BAD
-OPID
ADF routine was passed an invalid operater id.
BAD
E - AD2003-DTNAME
ADF routine was passed an unknown datatype name.
E - AD2004BAD
-DTID
ADF routine was passed an invalid datatype id.
BAD
E - AD2005-DTLEN
ADF routine found DB_DATA_ VALUE with an invalid length.
E - AD2006BAD
-DTUSRLEN
ADF routine encountered user-declared datatype length to be wrong.
E - AD2007- DT IS FIXLEN
Datatype is fixed length, yet a length specification was given.
E - AD2008- DT IS VARLEN
Datatype is variable length, but no length specification was given.
E - AD2009 - NOCOERCION
No coercion is available for datatypes given.
E - AD200A - NOCOPYCOERCION
No copy-coercion is available for datatypes given.
E - AD200BBAD
PREC
Invalid precision specified for DECIMAL value ... 1 <= precision <= 31.
E - AD200CBAD
-SCALE
Invalid scale specified for DECIMAL value ... 0 <= scale <= precision.
E - AD200D - BAD - BASE - DTID
Illegal or unknown base datatype ID.

AD Class Messages

2-5

E - AD2010BAD
-FIID
ADF found a bad function instance id.
LENSPEC
E- AD2020BAD
ADF does not recognize the length specification code %Od.
E - AD2021 - BAD - DT- FOR- PRINT
Illegal datatype for the PRINT style lenspecs.
E - AD2022- UNKNOWN - LEN
Expected internal error code ... No message needed. The length of the result can not be
determined because one (or more) of the input lengths that are required to determine the
result length is ADE_LEN_UNKNOWN.
E_AD2030_LIKE_ONLY_FOR_SQL
The LIKE/NOTLIKE operators are only valid in SQL.
E - AD2040- INCONSISTENT- TPL - CNT
The number of T/P/L's for base datatype ID '%Od' listed in the datatypes table differs
from the number generated by that datatype's routine.
E - AD2041 - TPL - ARRAYTOO
-SMALL
The T/pjL array passed in was not big enough to hold the number ofT/P/L's that needed
to be generated.
E - AD2042- MEMALLOC - FAIL
The memory allocation routine supplied by GCA failed with a status of %Ox.
E - AD2043- ATOMIC - TPL
The T/pjL triad being decomposed is already an 'ATOMIC' element. No further
decomposition is possible.
E - AD20S0- NO- COMVEC - FUNC
Missing function pointer in the datatypes table for function '%OcO', datatype ID '%ld'.
E - AD3001 - DTS - NOT - SAME
Some ADF function was given two datatypes that were expected to be the same but were
not. The most likely routines would be adc_keybldO, adc_compareO, adc_minmaxdvO, or
the ADE_KEYBLD CX instruction.
E - AD3002BAD
-KEYOP
KEYBLD (either the adc_keybldO routine or the ADE_KEYBLD instruction) was passed
an unknown key operator.

2-6

AD Class Messages

E - AD3003- DLS - NOT - SAME
KEYBLD (either the adc_keybldO routine or the ADE_KEYBLD instruction) was passed
low and high data values with inconsistent data lengths.
E - AD3004- ILLEGAL- CONVERSION
E _ AD300S _BAD _EQ_DTID

E _ AD3006_BAD _EQ_DTLEN

E - AD3007- BADDS
-DTID
E - AD3008- BADDS
-DTLEN
E - AD3009- BADHP
-DTID
E - AD3010- BADHP
-DTLEN
Illegal data length for a hash-prep value.
E - AD3011 - BAD- HG- DTID
Illegal datatype for a histogram element.
E - AD3012- BAD - HG - DTLEN
Illegal data length for a histogram element.
E- AD4001 - FIID IS AG
Trying to use an aggregate function instance as a non-aggregate.
E - AD4002- FIID- IS - NOT- AG
Trying to use a non-aggregate function instance as an aggregate.
E_AD4003_AG_WORKSPACE_TOO_SHORT
Aggregate needs more work space ... ADF_AG_STRUCT.adf_agwork.db_length needs to
be >= ADI_FI_DESC.adi_agwsdv_len.
E - AD4004- BAD - AG- DTID
Illegal datatype for result of an aggregate.
E - AD400S- NEG- AG - COUNT
A negative number of values have been aggregated!? How can this be?
AD Class Messages

2-7

E - ADSOOI - BAD- STRING - TYPE
Datatype is not a string datatype.
E - ADS002- BAD - NUMBER - TYPE
Datatype is not a numeric datatype.
BAD
CVTONUM
E - ADS003-

E - ADS004- OVER- MAXTUP
Length of a data value exceeds maximum tuple length.
E - ADSOOS- BAD DI FILENAME
E - ADS020- BADCH - MNY
E - ADS021 - MNY- SIGN
E - ADS022- DECPT - MNY
E - ADS031 - MAXMNY - OVFL
E - ADS032- MINMNY - OVFL
E ADSOSO DATEADD

E - ADSOSIDATESUB
E - ADSOS2- DATEVALID
E - ADSOS3- DATEYEAR
E - ADSOS4- DATEMONTH

2-8

AD Class Messages

E - ADSOS5 - DATEDAY

E - ADSOS6- DATETIME

E - ADSOS8- DATEBADCHAR

E - ADSOS9- DATEAMPM

E - ADSOSA- DATEYROVFLO

E - ADSOSB - DATEYR

E - ADSOSC - DOWINVALID

E - ADSOSD - DATEABS

E - ADSOSE- NOABSDATES

E - ADSOSF - DATEINTERVAL

E - ADS060- DATEFMT

E - ADS061 - DGMTON
-INTERVAL
The date_gmt function only works on absolute dates.
BAD
SEG
E - ADSSOOUnknown ex segment.
E - ADSSOI - BAD- SEG - FOR- ICODE
The instruction being compiled cannot be placed in the requested ex segment.
NUM
E - ADSS02- WRONG-OPRS
Wrong number of operands for a function instance.
It is possible that there have been changes to ADF's function instance table, that make

some views, integrities, or permits no longer valid.
AD Class Messages

2-9

E - AD5503- BAD - DTID- FOR- FIID
Datatype of operand (input or output) for a function instance is not correct. It is possible
that there has been a change to the datatypes accepted or returned for this function
instance in ADF's function instance table, thus making a view, integrity, or permit no
longer valid.
E - AD5504- BAD- RESULT- LEN
Length of result data for a function instance is not correct.
It is possible that there has been a change to the len spec for this function instance in

ADF's function instance table, thus making a view, integrity, or permit no longer valid.
E - AD5505 - UNALIGNED
Expected internal error code ... No message needed. ADE has detected an attempt to
compile an unaligned piece of data.
NO
SPACE
E - AD5506Expected internal error code ... No message needed. The ex is out of space; caller must
make it bigger.
E - AD5507 - BAD - DTID- FOR - KEYBLD
The output operand's length for the ADE_KEYBLD instruction must be 'int'.
E - AD5508- BAD - DTLENFOR
-KEYBLD
The output operand's length for the ADE_KEYBLD instruction must be 2.
E - AD5509 - BAD - RANGEKEY - FLAG
Range-key flag supplied when compiling the ex special instruction, ADE_KEYBLD, is
not recognized by the ade_instr_genO routine.
E- AD550A - RANGE- FAILURE
Expected internal error code ... No message needed. The ADE_KEYBLD instruction has
detected a RANGE-FAILURE; that is, when it was compiled it was told to accept only
RANGE-type keys, and the key found is not, or it was told to accept only
non-RANGE-type keys, and the key found was.
E - AD550B - TOO - FEW- BASES
The ex header states that there should be more base addresses that the caller has supplied.
E - AD550C - COMP - NOT IN PROG
ULTRIX/SQL is attempting to compile an instruction or constant into a ex without first
calling ade_bgn_compO to initialize the ex.
E - AD550D - WRONG CX
-VERSION
This version of ADF cannot execute the supplied ex due to a version mis-match.

2-10

AD Class Messages

E - ADSSOE- TOO - MANY- VLTS
The maximum number of VLTs (Variable Length Temporaries) has been exceeded. This
query cannot be executed.
E _ ADSSOF _BAD _CX _REQ UEST
Unknown request code detected by ade_cxinfoO routine: %Od.
E - ADSSIO- BAD- DTID- FOR- ESCAPE
The output operand's length for the ADE_ESC_CHAR instruction must be 'char'.
E - ADSSll - BAD- DTLENFOR
-ESCAPE
The output operand's length for the ADE_ESC_ CHAR instruction must be 1.
E - AD6000- BAD - MATH- ARG
E - AD6001BAD
-MATHOPT
Unknown math exception option found in ADF's session control block.
E - AD8999- FUNC - NOT - IMPLEMENTED
The function '%OcO' is not currently implemented.
E- AD9999 - INTERNAL- ERROR
An ADF internal coding error has been detected.

AD Class Messages

2-11

AF Class Messages

E- AF5000- VALUE- TRUNCATED
The return value has been truncated.

E - AF6001 - WRONG - NUMBER
The wrong number of parameters was passed to an AFE routine.

E - AF6002- INVALID - TYPE
An invalid type was passed to an AFE routine.

E - AF6004NOT
-LONGTEXT
The type passed to an AFE routine is not a longtext.

E- AF6005- SMALL- BUFFER
The buffer in the DB_DATA_ VALUE passed to AFE is too small.

E - AF6006- OPTYPE- MISMATCH
No function exists with this operator and the given operand datatypes.

E - AF6007 - INCOMPATABLE - OPID
The operator ids passed to AFE are incompatible.

E - AF6008- AMBIGUOUS - OPID
The operator ids passed to AFE are ambiguous.

E- AF6009BAD
MECOPY
An error occurred in MEcopy within an AFE routine.

E - AF600A- NAME- TOO- LONG
The name passed to AFE is too long.

E- AF600BBAD
LENGTH
The length passed to AFE is illegal.

E - AF600C - NOT- TEXT- TYPE
The type passed to AFE is not of type text.
AF Class Messages

3-1

E - AF600DBAD
-ASCII
AFE found a bad ascii character in a text constant.

E - AF600E- NO - DBDV- ROOM
There is not enough room allocated in the DB_DATA_VALUE.

E - AF600F- NO- CLOSE- PAREN
A close paren was not found in a type declaration.

E- AF6010- XTRACH
-PAREN
Extra characters were found following a close paren.

E - AF6011 - XTRACH
-NUM
Extra characters were found following a type length.

E - AF6012- BAD - TRAIL - CH
Illegal trailing characters were found at the end of a type name.

E - AF6013BAD
-NUMBER
A bad number was returned by afe_donum.

E - AF6014- BAD - ERROR- PARAMS
The wrong number of arguments was passed to afe_error.

E - AF6015- CANT- CONVERT- NUMERIC
Couldn't covert internal value to a numeric when making a constant.

E - AF6016- BUFFERTOO
-SMALL
The supplied buffer to afe_wconst is too small for the constant being built.

E - AF6017- CANT- FIND - COERCE
The type supplied to afe_ wconst does not have a coercion to int, float or char.

E - AF6018- ZERO IN TEXT
The character value supplied to afe_ wconst has a NULL byte in it.

E - AF6019BAD
-OPCOUNT
The wrong number of operands for the given function was passed to AFE.

E - AF601A - NOT - AGG - FUNC
The function name passed to AFE exists, but it is not an aggregate function.

E - AF601B - MORE- AGG - NEED
The number of eligible aggregates (%Od) for the type (%2d) exceeds the number
anticipated (%ld) by the caller of afe_agnames.

3-2

AF Class Messages

E - AF601C - BAD- AGG - INIT
afe_numaggs got error %Od when initializing its tables.

E AF601D NO LEN CHAR
afe_dtrimlen couldn't find a length function for type %Od.

E- AF601E- NOT- VCHR- TYPE
The type passed to AFE is not of type varchar.

AF Class Messages

3-3

CD Class Messages

E _ CDOOOl_Incorrect_language _sp
Incorrect language specification, using default
Explanation:

The user specified the DDL/DML language incorrectly.

System Status:

The default language for the installation is used.

Recommendation:

Check the language specifications and rerun if necessary.

E_ CD0002_Not_ Ingres
This DBMS does not have the capability to run copydb.
You must be running against an ULTRIX/SQL dbms to use these products.

CD Class Messages

4-1

CL Class Messages

E- CL0301 - CK- BAD- PARAM
Bad parameter passed to a CK routine
CK
SPAWN
E - CL0302Could not spawn a subprocess to perfrom backup
CK
BACKUP
E - CL0303Unexpected backup error received from operating system
E - CL0304CK
-CMKRNL
Could not enter change mode to kernel to perform backup
E - CL0305CK
-NOTFOUND
Checkpoint object could not be found.
E- CL0306CK
BADDELETE
Error deleting file or directory
E - CL0307CK
-BADPATH
The path specified was in error.
E - CL0308CK
-END FILE
End of file
E - CL0309CK
-BADLIST
Error listing objects in a directory
E - CL030ACK
-FILENOTFOUND
The file specified could not be found
E - CL030BCK
-DIRNOTFOUND
The directory pointed to path could not be found
CK
E - CL030C-BADDIR
Error verifying directory
CL Class Messages

5-1

E - CL030DCK
-EXISTS
The object specified already exists
CV
SYNTAX
E - CLOSOI Bad syntax in ascii form of number
CV
E - CLOS02-UNDERFLOW
Number underflow in the conversion
E - CLOS03CV
-OVERFLOW
Number overflow in the conversion
CV
E - CLOS04-TRUNCATE
Output too wide for space passed in
E CL0601 DI BADPARAM
Bad parameter(s) passed to routine
E CL0602 DI BADFILE
Illegal file control block pointer
E CL0603 DI END FILE
End of file
E CL0604 DI BAD OPEN
Error trying to open file
E CL060S DI BADCLOSE
Error trying to close file
E CL0606 DI BADWRITE
Error writing page to disk
E CL0607 DI BADREAD
Error reading page from disk
E CL0608 DI BADEXTEND
Error allocating disk space
E CL0609 DI BADDIR
Error verifying directory
E CL060A DI BADINFO
Error seeking to page in file

5-2

CL Class Messages

E CL060B DI BADSENSE
Error reading file attributes

E CL060C DI BADCREATE
Error creating file or directory

E CL060D DI BADDELETE
Error deleting file or directory

E CL060E DI BADRNAME
Error renaming file

E - CL060F DI EXCEED- LIMIT
File resource quota exceeded

E CL0610 DI DIRNOTFOUND
The directory pointed to path could not be found

E CL0611 DI FILENOTFOUND
The file specified could not be found

E CL0612 DI EXISTS
The object specified already exists

E CL0613 DI BADLIST
Error listing objects in a directory

E - CL0701DSN
RECUR
Recursive call atempted

E - CL0702DSN
-LANG
Unsupported language specifier

E - CL0703DSN
-ALIGN
Illegal alignment constraint

E - CL0704DSN
-VIS
Illegal visibility level

E - CL070SDSN
UNKNOWN
Unknown operation requested

E- CL0801DY
-NOSTAB
No symbol table generated

CL Class Messages

5-3

E - CL0802DY
-NOEXE
No executable built
DY
E - CL0803-NOMEM
Error allocating memory to load image
E - CL0804DY
-NOREAD
Error reading in image
DY
E - CL0805-NOFILE
Error locating image file
E - CL0901 - ER- NO- FILE
The file $II_SYSTEM/sql/files/errlog.log could not be opened
E - CL0902- ER- NOT- FOUND
No text found for message identifier
ER
E - CL0903-BADPARAM
Bad parameter
E - CL0904ER
-BAD READ
Error reading the ULTRIX/SQL message file.
ER
E - CL0905-TOOSMALL
Buffer smaller then size of the message name
E - CL0906ER
TRUNCATED
Message text truncated because buffer was too small
E - CL0907ER
-BAD OPEN
Can't open/create receive channel for error logger
E - CL0908ER
-BADRECEIVE
Error receiving error logger message
E CL0909 ER BAD SEND

Error sending message to error logger
ER
E - CL0910-UNIXERROR
% IcO failed with ULTRIX error %Od (%2c)
Parameters:

o ermo
1
2

5-4

CL Class Messages

library or system call name, e.g. "open", "read"
sys_errlist[ erma]

E - CL0911- ER - INTERR- TESTMSG
Internal compatibility routine failed, parameter was "%Oc".
E CLOAOI EXEXIT

Exiting program
E - CLOA17- EXBADRETURN
Invalid return from a signal. Valid returns are EXDECLARE, EXRESIGNAL, and
EXCONTINUE
E CLOAFF EXDECLARE

Unwind to declaring frame
E - CLOEOI - IN- BACKEND- NAME
INingres: Unable to start ULTRIX/SQL -- unable to find name for backend
E - CLOE02 IN INTR - NAME
INingres: Unable to start ULTRIX/SQL -- unable to find name for interrupt process
E - CLOE03 IN NO- DB - NAME
INingres: no database name specified
E CLOE04 IN RD UNDEF

INread: receive pipe was not defined INingres did not complete normally
E - CLOEOS - IN- RD - SYSERR
INread: unable to get complete PIPEBLK -- system error during read
E - CLOE06 IN RD - INTR
INread: read call was interrupted
E - CLOE07- IN- RD- PIPE- GONE
INread: read pipe is no longer accessible
E - CLOE08- IN- RD- NOTWHOLE
INread: system read function did not write an entire pipe block
E - CLOE09 - IN- RD - CTLC
INread: got control-C
E - CLOEOA IN WR- UNDEF
INwrite: send pipe was not defined INingres did not complete normally
E - CLOEOB IN WR- SYSERR
INwrite: unable to send complete PIPEBLK -- system error during write

CL Class Messages

5-5

E CLOEOC IN WR INTR

INwrite: write call was interrupted
E CLOEOD IN WR PIPE GONE

INwrite: write pipe is no longer accessible
E- CLOEOE- IN- WR- NOTWHOLE

INwrite: system write function did not write an entire pipe block
E- CLOEOF IN WR- CTLC

INwrite: got control-C
E- CLOEIO- IN- NO- BACKEND

INintrpt: there is no ULTRIX/SQL backend process to interrupt
E CLOEll IN INACTIVE

INtimeout: timeout period exceeded
E- CLOFOILG
CANTINIT
-

Error trying to initialize log file
E- CLOF02LG
-CANTO PEN

Error trying to open log file
E- CLOF03LG
-CANTCLOSE

Error trying to close log file
E CLOF04 LG BADPARAM

Bad input parameter passed to LG routine
E CLOFOS LG READERROR

Error reading from log file
E CLOF06 LG BADHEADER

Log file has bad header context
E CLOF07 LG INITHEADER

Error trying to initialize log file header context
E CLOF08 LG ENDOFFILE

Log logical end of file has been reached
E- CLOF09LG
-OFFLINE

Logging system not running

5-6

CL Class Messages

E - CLOFOALG
-BADFORMAT
Log file record has a bad format
E - CLOFOBLG
-NOTLOADED
Logging system device has not been loaded
LG
E - CLOFOC-UNEXPECTED
Logger received unexpected error from operating system
E_CLOFOD_LG_CHK_SUM_ERROR
Bad checksum for log page
E - CLOF30- LG- NO - MASTER
Could not initialize the logging system for this process because the RCP process is not
running. This indicates that either the RCP abnormally exited, or that the server has
attempted to connect to the logging system before the RCP was brought up.
Shutdown all processes associated with this installation, and bring up the installation from
scratch using the supported startup tools, documented in Installation and Operations guide.
Parameters:

None.

Explanation:

Each installation contains a single process designated to be the
"master" of the logging and locking operations of that
installation.

The process named "dmfrcp" is the usual master process. If this process exits abnormally
without running certain cleanup routines it may be possible for other processes to connect
to the data structures left about in shared memory, and get into a state where they wait
forever from a response from tne non-existent "master" process.
A check for the existence of the "master" is performed whenever a process connects to the
logging system. If the "master" process does not exist then this error is returned.
This error indicates that the dmfrcp process has exited abnormally (causes include "kill
-9" and system coding errors). A server cannot be allowed to start up when this condition
exists, so this error is returned.
System Status:

The process being started up (the dmfacp or dbms server) fails to
come up, printing error messages to the error log (errlog.log),
and possibly, in the case of the dmfacp, to the II_ACP.LOG file.

Recommendation:

1. Check to see if a "dmfrcp" process is running in your
installation. If one exists, this error may have been caused by a
race condition between starting your process and starting the
"dmfrcp" process. Try starting your server once more.
2. IF 1 is not true THEN:
All the following should only be done by a System Administrator.
a. Shutdown entire installation using "rcpconfig" with the
"imm_shutdown" option.

CL Class Messages

5-7

b. If any other processes remain active in your installation
following this shutdown, then shutdown these processes
manually with the appropriate operating system command.
c. Restart the installation from scratch using the appropriate
startup command documented in your Installation and
Operations guide.
E _ CLOF31_ LG_CANT_OPEN
Could not initialize the logging system for this process because the database recovery log
file (%Oc) could not be opened. We attempted to open the file with the a flag mask of
(% lc). Check the ownership and permisions on the ULTRIX/SQL log file.
Parameters:

%0 The name of the recovery log file which the system
attempted to open. % I The ULTRIX flag mask passed to the
openO system call.

Explanation:

All transaction recovery information is written to a single log
file. The file is expected to be found in a file named:
$II_LOG_FILE/ingres/log/ingres_log. For some reason the
system's attempt to open this file has failed.

System Status:

The process being started up halts with a fatal error.

Recommendation:

1. Check the file permisions on the ULTRIX/SQL recovery log
file.
This file is located in $II_LOG_FILE/ingres/log/ingres_log,
where $II_LOG_FILE is the value of II_LOG_FILE printed
when the "ingprenv" command is issued.
This file should be owned by the same user who owns the rest of
the ULTRIX/SQL installation (ie. usually "ingres"). The path to
the file should be accessible by the "ingres" user. The file must
be readable and writeable by the "ingres" user.
Make sure that the environment variable II_LOG_FILE is not set
in your local shell environment.
2. Check permisions on executables being run. All executables
which must access the recovery log file must have the "setuid"
bit on and be owned by the "ingres" user. These executables
include: dmfacp, dmfrcp, dmfjsp, iidbms, csinstall, and others.

LK
BUSY
E - CLIOOIResource is busy
E _ CLI002 _LK_TIMEOUT
Lock timed out
LK
E - CLI003-BADPARAM
Bad parameter(s) passed to routine

5-8

CL Class Messages

E - CLI004LK
-DEADLOCK
Deadlock detected

E - CLI005LK
NOLOCKS
Out of lock resources

E- CLI006LK
-UNEXPECTED
Lock manager internal error

E - CLI007 - LK- NEW - LOCK
New lock was obtained

E - CLI020- LK- BUSY- ALTER
LKalter call failed because lkd-lkd_llb_inuse was set to %Od.

E - CLI021 - LK- LLB - ALLOC - FAILED
LKalter's call to allocate %Od locks lists ran out of memory

E - CLI022- LK- LOCK- ALLOC - FAILED
LKalter's call to allocate %Od locks ran out of memory

E - CLI023- LK- LKH - ALLOC - FAILED
LKalter's call to allocate %Od hash buckets for the lock hash table ran out of memory

E - CLI024- LK- RSH - ALLOC - FAILED
LKalter's call to allocate %Od hash buckets for the lock hash table ran out of memory

E - CLI025 - LK- NOINTERRUPT- ALTER
LKalter's call to change the interrupt status failed due to a bad paramter; the lock id =
%Od; the number of locks in the system = %d.

E - CLI026- LK- NOINTERRUPT - ALTER
LKalter's call to change the interrupt status failed due to a bad paramter; input lock id
instance = %Od; the system lock type = % Id; the system id instance = %2d.

E_CLI027_LK_BAD_ALTER_REQUEST
LKalter recieved request to alter parameter %Od, which is not a supported LKalter
parameter.

E - CLI028- LK- CANCEL- BADPARAM
LKcancelO failed due to a lock id bad paramter; the input lock id = %Od; the number of
locks in the system = %d.

E - CLI029 - LK- CANCEL- BADPARAM
LKcancelO failed due to a lock id bad paramter; input lock id instance = %Od; the system
lock type = % Id; the system id instance = %2d.
CL Class Messages

5-9

E - CLI02A- LK- CREATE- BADPARAM
LKcreate_listO failed due to a lock id bad paramter; the input related lock id = %Od; the
number of locks in the system = %d.
E CLI02B LK CREATE BADPARAM

LKcreate_listO failed due to a lock id bad paramter; input related lock id instance = %Od;
the system related lock type = % Id; the system related id instance = %2d.
E - CLI02C - LK- CREATE- BADPARAM
LKcreate_listO failed due to a NULL lock list pointer.
E _ CLI02D _ LK_EXPAND _LIST _FAILED
LK failed while trying to allocate more objects of type %Od, The reason for failure was
that the locking and logging shared memory pool was exhausted. % Id lock lists and %2d
locks have already been allocated
E - CLI02E- LK - EXPANDLIST
-FAILED
LK failed while trying to allocate more locks. There are %Od locks, allocated at system
startup time, of which % Id are used. The request was made with either (LLB_RECOVER
I LLB_MASTER) status.
E - CLI02F- LK- EXPANDLIST
-FAILED
LK failed while trying to allocate more locks. There are %Od locks, allocated at system
startup time, of which % 1d are used. %2d locks have been reserved for use by the
recovery system.
E - CLI030- LK- EXPANDLIST
FAILED
LK failed while trying to allocate more locks lock lists. There are %Od locks lists,
allocated at system startup time, of which % Id are used.
E_CLI031_LK_BAD_UNIQUE_ID
LK failed while allocating a lock list, due to a bad unique identifier passed in by the
caller. The unique id's value is %Od, and the lk_uhigh part of this structure is %ld
E_CLI032_LK_DUPLICATE_LOCK_ID
LK failed while allocating a lock list, due to a bad unique identifier passed in by the
caller. The unique id's value is %Od, and the lk_uhigh part of this structure is % Id
E - CLI033 - LK- EVENTBAD
-PARAM
LKeventO failed due to a lock id bad paramter; the input related lock id = %Od; the
number of locks in the system = % Id.
E - CLI034- LK- EVENTBAD
PARAM
LKeventO failed due to a lock id bad paramter; input lock id instance = %Od; the system
related lock type = % Id; the system related id instance = %2d.

5-10

CL Class Messages

E - CLI035 - LK- EVENTBAD
-PARAM
LKeventO failed due to a bad paramter. The lock identified was already waiting for an
event; status of the lock is %Od, and flag is % Id.
E CLI036 LK RELEASE BAD PARAM

LKreleaseO failed due to a lock list id bad paramter; the input lock list id = %Od; the
number of lock lists in the system = % I d.
E - CLI037- LK- RELEASEBAD
-PARAM
LKreleaseO failed due to a lock id bad paramter; input lock id instance = %Od; the system
lock type = % Id; the system id instance = %2d.
E CLI038 LK RELEASE BAD PARAM

LKeventO failed due to a lock id bad paramter; the input related lock id = %Od; the
number of locks in the system = % Id.
E - CLI039- LK- RELEASEBAD
PARAM
LKreleaseO failed due to a lock id bad paramter; input lock id instance = %Od; the system
lock type = % Id; the system id instance = %2d.
E - CLI03A- LK- RELEASEBAD
-PARAM
LKreleaseO failed due to a bad paramter, neither lock_key nor lockid were set.
E CLI03B LK RELEASE BAD PARAM
-

LKreleaseO failed due to a bad paramter, either the system could not find the lock
(lkb = %Od) or the lock found had an incorrect attribute (lkb_attribute = % Ix).
BAD
E - CLI03C - LK- RELEASE-PARAM
LKreleaseO failed due to a bad paramter, no lock_key was specified for a partial release.
E _ CLI03D _LK_REQUEST _BAD _ PARAM
LKrequestO failed due to a lock list id bad parameter, or a bad mode (lock mode = %2d);
the input lock list id = %Od; the number of locks in the system = % Id.
E _ CLI03E _LK _REQUEST _BAD _ PARAM
LKrequestO failed due to a lock list id bad parameter; input lock list id instance = %Od;
the system lock type = % Id; the system lock list id instance = %2d.
E_CLI03F_LK_REQUEST_BAD _PARAM
LKrequestO failed due to a bad parameter, no lockid was specified for a convert.
E _ CLI040_LK_REQUEST_BAD _ PARAM
LKrequestO failed due to a lock list id bad parameter; the input lock list id = %Od; the
number of lock lists in the system = % Id.

CL Class Messages

5-11

E_CLI041_LK_REQUEST_BAD_PARAM
LKrequestO failed due to a lock id bad parameter; input lock id instance = %Od; the
system lock type = % ld; the system id instance = %2d.
E_CLI042_LK_REQUEST_BAD_PARAM
LKrequestO failed due to no lock key being passed in.
E - CLI043- LK- SHOW- BAD - PARAM
LKshowO failed to show LK_S_ORPHANED'd locks. Size requested is %Od, size of a
LK_ID is % 1d, and lock_key is %2x.
E - CLI044- LK- SHOW- BAD - PARAM
LKshowO failed to show LK_S_RESOURCE. Count requested is %Od.
E - CLI045- LK- SHOW- BAD - PARAM
LKshowO failed to show LK_S_LOCKS. Count requested is %Od.
E - CLI046- LK- SHOW- BAD - PARAM
LKshowO failed to show LK_S_OWNER. Bad lockid pointer (%Ox) or bad lock_key
(%lx).
E - CLI047 - LK- SHOW- BAD - PARAM
LKshowO failed due to an unrecognized show flag (%Od).
E - CLIIOI - LO- ADD - BAD- SYN
LOaddpath: Bad syntax in arguments to LOaddpath -- tail shouldn't begin at root
E - CLII02- LO- FR- BAD - SYN
LOfroms: String argument to LOfroms has bad syntax
E - CLII03- LO- NO- SUCH
No such location exists
E - CLII04- LO- NO- PERM
You do not have permission to access the location with this call
E - CLII05- LO - NO - SPACE
Not enough space on file system
E - CLII06- LO - NOT - FILE
Location argument was not a FILENAME
E - CLII07- LO- NULL- ARG
Illegal null pointer was passed to location routine

5-12

CL Class Messages

E - CLII08- LO - CANT- TELL
Undetermined error in LO routines

E - CLII09- LONOSAVE
LOreset called without matching call to LOsave

E- CLIIOA- LO- TOO- LONG
LOgtLocation obtained overflowed buffer

E - CL1201ME
-GOOD
ME routine: The Status returned was good

E - CL1202- ME - BD - CHAIN
MEdump: correct parameter value must be one of ME_D_ALLOC, ME_D_FREE,
ME_D_BOTH

E - CL1203- ME - BD- CMP
MEcmp: number of bytes to compare must be 0

E- CL1204- ME - BD - COpy
MEcopy: number of bytes to copy must be 0

E - CL120S - ME - BD - FILL
MEfill: number of bytes to fill must be 0

E - CL1206- ME - BD - TAG
MEt[alloc, free]: tags must be 0

E - CL1207 - ME - ERR - PROGRAMMER
MEfree: There is something wrong with the way this routine was programmed.Sorry

E - CL1208- ME - FREE- FIRST
ME[t]free: can't free a block before any blocks have been allocated

E- CL1209ME
-GONE
ME[t]alloc: system can't allocate any more memory for this process

E- CL120A- ME - NO - ALLOC
ME[t]alloc: request to allocate a block with zero (or less) bytes was ignored

E - CL120B - ME- NO - FREE
MEfree: can't find a block with this address in the free list

E - CL120C - ME- NO- TFREE
MEtfree: process hasn't allocated any memory with this tag

CL Class Messages

5-13

E- CL120D- ME-00-PTR
ME[t]alloc: passed a null pointer

E - CL120E - ME 00 CMP
MEcmp: passed a null pointer

E- CL120F- ME-00-COpy
MEcopy: passed a null pointer

E- CL1210- ME 00 DUMP
MEdump: passed a null pointer

E- CL1211 - ME 00 FILL
MEfill: passed a null pointer

E- CL1212- ME 00 FREE
MEfree: passed a null pointer

E - CL1213 - ME - TR - FREE
MEfree: the memory has been corrupted

E - CL1214- ME - TR- SIZE
MEsize: the memory has been corrupted

E- CL1215 - ME - TR - TFREE
MEtfree: the memory has been corrupted

E- CL1216- ME - OUTOF
-RANGE
ME routine: address is out of process's data space, referencing will cause bus error

E- CL1217 - ME - BF- OUT
MEneed: 'buf' doesn't have 'nbytes' left to allocate

E- CL1218- ME - BF- ALIGN
MEinitbuf: 'buf' not aligned

E - CL1219 - ME - BF- FALIGN
MEfbuf: 'buf' not aligned

E- CL121A- ME - BF- PARAM
MEfbuf: 'bytes' argument must come from call to MEfbufO

E- CL1301MH
-BADARG
Bad argument

5-14

CL Class Messages

E - CL1302MH
PRECISION
Lost precision during calculation

E - CL1303MH
-INTERNERR
Internal error

E CL1304 MH MATHERR
-Math error
E CL1401 NM PWDOPN
-NMpathIng: Unable to open passwd file
E - CL1402NM
-PWDFMT
NMpathlng: Bad passwd file format

E - CL1403NM
INGUSR
NMpathIng: There is no ULTRIX/SQL user in the passwd file

E- CL1404NM
-INGPTH
NM[sg]tIngAt: No path returned for ULTRIX/SQL user

E - CL1405NM
-STOPN
NM[sg]tIngAt: Unable to open symbol table

E- CL1406NM
-STPLC
NMstIngAt: Unable to position to record in symbol table

E - CL1407NM
STREP
NMstIngAt: Unable to replace record in symbol table

E - CL1408NM
-STAPP
NMstIngAt: Unable to append symbol to symbol table

E - CL1409NM
LOC
NM_loc: first argument must be 'f' or 't'

E - CL140A- NM- BAD - PWD
NMpathlng: Bad home directory for ULTRIX/SQL superuser

E- CL1601- PC- CM- CALL
PCcmdline: arguments incorrect

E- CL1602- PC- CM- EXEC
PCcmdline: cannot execute command specified, bad magic number

CL Class Messages

5-15

E - CL1603- PC - CM- MEM
PCcmdline: system temporarily out of core or process requires too many segmentation
registers
E - CL1604- PC - CM- OWNER
PCcmdline: must be owner or super-user to execute this command
E - CL160S- PC - CM- PATH
PCcmdline: part of specified path didn't exist
E - CL1606- PC - CM- PERM
PCcmdline: didn't have permission to execute
E - CL1607 - PC - CM - PROC
PCcmdline: system process table is temporarily full
E - CL1608- PC - CM- REOPEN
PCcmdline: couldn't associate argument [in, out]_name with std[in, out]
E - CL1609 - PC - CM- SUCH
PCcmdline: command doesn't exist
E - CL160A- PC - CM- BAD
PCcmdline: child didn't execute, e.g bad parameters, bad or inacessible date, etc
E- CL160B - PC - CM- TERM
PCcmdline: child we were waiting for returned bad termination status
E - CL160C - PC - END- PIPE
PCendpipe: had trouble closing PIPE argument passed in
E - CL160D- PC - SP- CALL
PC[f][s]spawn: arguments incorrect
E - CL160E - PC - SP- EXEC
PC[f] [s]spawn: cannot execute command specified, bad magic number
E - CL160F- PC - SP- MEM
PC[f][s]spawn: system temporarily out of core or process requires too many segmentation
registers
E - CL1610- PC - SP- OWNER
PC[f][s]spawn: must be owner or super-user to execute this command
E - CL1611 - PC- SP- PATH
PC[f] [s]spawn: part of specified path didn't exist
5-16

CL Class Messages

E- CL1612- PC - SP- PERM
PC[f][s]spawn: didn't have permission to execute
E- CL1613 - PC - SP- PROC
PC[f][s]spawn: system process table is temporarily full
E- CL1614- PC - SP- SUCH
PC[f][s]spawn: command doesn't exist
E- CL1615- PC - SP- CLOSE
PC[f]sspawn: had trouble closing unused sides of pipes
E- CL1616- PC - SP- DUP
PC[f]sspawn: had trouble associating, dupO'ing, the pipes with child's std[in,out]
E- CL1617 - PC - SP- PIPE
PC[f]sspawn: couldn't establish communication pipes
E- CL1618- PC - SP- OPEN
PCfsspawn: had trouble associating child's std[in,out] with passed in FILE pointers
E- CL1619 - PC - SP- REOPEN
PCspawn: couldn't associate argument [in, out]_name with std[in, out]
E- CL161A- PC- RD - CALL
PCread: one of the passed in arguments is NULL
E- CL161B - PC - RD - CLOSE
PCread: stream corrupted, should never happen
E- CL161C - PC - RD - OPEN
PCread: trouble establishing communication pipes
E- CL161D - PC - SD- CALL
PCsend: invalid exception value
E- CL161E- PC - SD - NONE
PCsend: No process corresponding to the pid (process argument) exists
E- CL161F- PC - SD- PERM
PCsend: Can't signal specified process. Effective uid of caller isn't 'root' and doesn't
match real uid of receiving process
E- CL1620- PC - WT - BAD
PCwait: child didn't execute, e.g bad parameters, bad or inacessible date, etc

CL Class Messages

5-17

E - CL1621 - PC - WT- NONE
PCwait: no children of this process are currently alive

E - CL1622- PC - WT- TERM
PCwait: child we were waiting for returned bad tennination status

E - CL1623 - PC - WT- INTR
PCwait: child was interrupted by a signal

E - CL1624- PC - NOT - MBX
PEendpipe: channel not assigned to mailbox

E - CL1625PC
-INTERLOCK
PEendpipe: mailbox locked by another process

E - CL1626PC
-BADCHAN
PEendpipe: not a legal channel number

E - CL1627PC
NOPRIV
PEendpipe: mailbox not assigned or insufficient privilege

E- CL1701 - PE- BAD- PATTERN
Pennission pattern passed to a pennission routine had syntax errors

E - CL1702- PE- NULL - LOCATION
Location passed to a pennission routine was null

E_CL1800_QU
No errors from these routines

E - CL1901 SI BAD- SYNTAX
Slopen: Bad syntax in mode argument to Slopen

E CL1902 SI EMFILE
Can't open another file -- maximum number of files already opened

E - CL1903 SI BAD - MODE
SIfopen: Bad mode paramete

E - CL1904 SI CANT- OPEN
SIfopen: Can't open file

E - CLIBOISR
-BADFILE
Bad sort file identifier

5-18

CL Class Messages

E - CLIB02SR
-END FILE
End of File

E - CLIB03SR
-BADOPEN
Error opening sort file

E- CLIB04SR
-BADCLOSE
Error closing sort file

E - CLIB05SR
-BADWRITE
Error writing to sort file

E CLIB06 SR BADREAD
-Error reading from sort file
E - CLIB07SR
-BADEXTEND
Error allocating space to sort file

E - CLIB08SR
-BADCREATE
Error creating sort file

E - CLIFOI- TM- BAD- MSECS
Number of milliseconds for an alarm was less than zero

E - CLIF02- TM- ZERO- TIME
Zero seconds resulted when rounding milliseconds for an alarm

E - CLIF03TM
-NOTIMEZONE
The environment variable, 11_TIMEZONE, is undefined

E - CLIF04TM
SYNTAX
syntax error in time format

E - CL210t TR
-BADCREATE
Error creating trace output file

E - CL2102TR
-BADOPEN
Error opening trace output file

E- CL2103TR
-ENDINPUT
End of File

E- CL2104TR
-BADPARAM
Bad parameter(s) passed to this routine

CL Class Messages

5-19

E - CL2105TR
-BAD READ
Error reading trace file
E - CL2106TR
-BADWRITE
Error writing trace file
E - CL2201 - UT- CO- FILE
Can't open utcom.def
E- CL2202- UT- CO- IN- NOT
Can't open input file
E- CL2203- UT- CO- LINES
Bad line in utcom.def
E - CL2204- UT- CO- CHARS
Bad line in utcom.def
E - CL2205 - UT - CO- SUF- NOT
Couldn't find suffix
E - CL2206- UT- ED - CALL
UTedit: NULL filename argument
E_CL2207_UTENOEQUAL
No equal sign ('= ') in argument list
E - CL220S- UTENOPERCENT
No percent sign ('% ') in argument list
E - CL2209 - UTENOSPEC
No type specifier in argument list
E - CL220A- UTEBADARG
The argument list has does not have a comma between two arguments or ends too early
E - CL220B - UTENOARG
Given argument not in utexe.def entry for program
E - CL220C - UTEBIGCOM
Command length exceeds utexe's limit
E - CL220D- UTEBADSPEC
Utexe.def has a bad type specifier in one entry for the program

5-20

CL Class Messages

(

E - CL220E - UTENOBIN
No executable found for program

E - CL220F- UTENOPROG
The given program name is not in utexe.def

E- CL2210- UT- PR- CALL
UTprint: NULL filename argument

E - CL2211- UTENoInit
No text

E - CL2212- UTENo WriteFunc
No text

E - CL2213 - UTENoReadFunc
No text

E_ CL2214 _UTENoModuleType
No text

E - CL2215 - UTENOSYM
The actual argument for a \%C parameter was not a valid user command

E - CL2216- UTELATEEXE
A module being run as a procedure had a \%C or \%E actual argument

E - CL2217 - UTEBADTYPE
The type specifier for one argument was not of an expected type

E- CL2218- UT- EXE- DEF
Can't open utexe.def

E CL2300 NT
No errors for these routines
E _ CL2401_JF_BAD _FILE
Bad journal file

E_ CL2402_JF_END _FILE
End of journal file reached

E _ CL2403 _JF _BAD_OPEN
Error trying to open a journal file

CL Class Messages

5-21

E_ CL2404_JF_BAD_CLOSE
Error trying to close a journal file
E _ CL240S _JF _BAD _WRITE
Error trying to write a journal file
E_CL2406_JF_BAD _READ
Error trying to read a journal file
E _ CL2407 _JF _BAD _ALLOC
Error trying to extend a journal file
E_ CL2408_JF_BAD _UPDATE
Error trying to updating the header of a journal file
E_ CL2409 _JF_BAD_CREATE
Error trying to create a journal file
E_ CL240A_JF_BAD _DELETE
Error trying to delete a journal file
CS
E - CL2S00-OK
All is fine.
E - CL2S01 - CS- INVALID - STATE
The Server control block indicates an invalid state.
E - CL2S02- CS - SCB - ALLOC - FAIL
Unable to allocate a session control block.
E_CL2S03_CS_NOT_QUIESCENT
Server has active sessions: Unable to perform shutdown.
E - CL2S04- CS- BAD- PARAMETER
Invalid parameter on CS call.
E - CL2S06- CS - TIMER- ERROR
Unable to queue timer request.
E_CL2S07_CS_RDY_QUE_CORRUPT
The ready queue for the server is in an inconsistent state.
E - CL2S08CS
-INTERRUPTED
The request was interrupted at user request.

5-22

CL Class Messages

E - CL2509CS
-TIMEOUT
The request has returned due to timeout.

E - CL250A- CS - NO- SEMAPHORE
The task requesting a semaphore operation does not own a semaphore.

E - CL250C - CS- INVALID- MODE
The session control block indicates an invalid mode.

E - CL250D- CS- INVALIDRTN
-MODE
The routine called by CS returned an invalid mode.

E - CL250E- CS- SESSION - LIMIT
Too many sessions have been requested.

E_ CL250F_ CS_REQUEST_ABORTED
The request has been aborted.

E_CL2510_CS_QUANTUM_INVALID
The user specified timer quantum is invalid.

E - CL2511 - CS- BAD - CNX- STATUS
Unable to make connection with the working partner.

E - CL2512- CS - BAD- ADMIN - SCB
The admin session has been called with a non-admin scb.

E - CL2513- CS- CORRUPT- ADMIN- SCB
The session control block for the admin SCB has been corrupted.

E - CL2514- CS- ESCAPED - EXCEPTION
An exception has escaped from user session. This session will be terminated.

E - CL2515 - CS - FORCED - EXIT
The server has be forced to exit involuntarily.

E - CL2516- CS- SYSTEM- ERROR
The server has encountered an unexpected system error.

E - CL2517- CS- SMPR- DEADLOCK
A session has requested a semaphore which it already owns.

E - CL2518- CS - NORMAL - SHUTDOWN
The Server has terminated normally.

CL Class Messages

5-23

E - CL2519- CS- INVALID - READY
A session has been RESUMED before it became runnable.

E - CL251A- CS- STACK- DEAL- FAIL

as Error deallocating a STACK region.

E - CL251B - CS- IDLE - RESUME
Attempt to resume the idle job

E - CL251CCS
-TERM W SEM
Session terminated while holding semaphore(s).

E - CL2520CS
AMBIGUIOUS
%Oc ambiguious

E - CL2521 - CS - ARG - UNKNOWN
argument %Oc unknown

E - CL2522- CS - NO - VALUE
value not supplied to %Oc

E _ CL2523 _ CS _TOO_MANY _ OPTIONS
Too many options have been used, please re-issue with fewer options

E - CL2524- CS - NON- NUMERIC - ARG
%Oc requires non numeric arguments

E - CL2525 - CS - NUMERIC - ARG
invalid numeric argument to %Oc

E - CL2526- CS - POSITIVE - VALUE
%Oc value must be greater than zero

E _ CL2527 _ CS _PARSE_ERROR
internal error parseing options

E - CL2528- CS - ARG- USAGE
Option names must begin with a '-'

E - CL25F9- CS - 2STK- OVFL
Stack overflow while correcting previous stack overflow. The server will be terminated.

E - CL25FACS
UNWIND - FAILURE
-

as error while attempting to unwind an exception stack.

5-24

CL Class Messages

E - CL25FB - CS- UNDELIV - AST
VMS was unable to deliver an AST to a thread.

E - CL25FC - CS - CRTCL- RESRC - HELD
Thread encountered a thread fatal error while holding a critical resource.

E- CL25FD- CS- THREADSTK
OVFL
Thread operating for has exhausted stack space (% Id. bytes). The thread will be
terminated. Please consult your ULTRIX/SQL system adminstrator.
NOTE: The stack space can be expanded with the use of the /stack_size qualifer at
iirundbms time.

E - CL25FE- CS - 25FE- RET- FROM- IDLE
The idle thread has erroneously returned. This is server fataL

E- CL25FF- CS- FATAL- ERROR
The server has encountered a FATAL error. The server will be terminated.

E - CL2601 -CI-NOSTR
The authorization string (II_AUTHORIZATION) is not available. Please consult the
ULTRIX/SQL system manager.

E - CL2602-CI-TOOLITTLE
The authorization string (II_AUTHORIZATION) contains too few characters. Please
consult the ULTRIX/SQL system manager.

E CL2603 CI TOO BIG
The authorization string (II_AUTHORIZATION) contains too many characters. Please
consult the ULTRIX/SQL system manager.

E - CL2604-CI-BADCHKSUM
The authorization string (II_AUTHORIZATION) checksums incorrectly. This is probably
a typographical input error. Please consult the ULTRIX/SQL system manager.

E CL2605 CI BADEXPDATE
The authorization string (II_AUTHORIZATION) indicates that your license has expired.
Please consult the ULTRIX/SQL system manager.

E - CL2606-CI-BADSERNUM
The authorization string (II_AUTHORIZATION) does not match the serial number of the
machine on which you are running. Please consult the ULTRIX/SQL system manager.

E- CL2607-CI-BADCPUMODEL
The authorization string (II_AUTHORIZATION) does not match the CPU model of the
machine on which you are running. Please consult the ULTRIX/SQL system manager.

CL Class Messages

5-25

E - CL2608-CI-BADERROR
An unexpected error occurred during authorization string processing. Please consult the
ULTRIX/SQL system manager.
E CL2609 CI BAD KEY
The authorization string (II_AUTHORIZATION) was improperly created for this version
of the software. Please consult the ULTRIX/SQL system manager.
E CL2614 CI BADCAP
The required (DBMS) capability is not provided by the authorization string
(II_AUTHORIZATION). Please consult the ULTRIX/SQL system manager.
E CL2616 CI BADCAP
The required (NET) capability is not provided by the authorization string
(II_AUTHORIZATION). Please consult the ULTRIX/SQL system manager.
E CL2618 CI BADCAP
The required (SQL TM) capability is not provided by the authorization string
(II_AUTHORIZATION). Please consult the ULTRIX/SQL system manager.
E CL262A CI BADCAP

The required (ESQL/ADA) capability is not provided by the authorization string
(II_AUTHORIZATION). Please consult the ULTRIX/SQL system manager.
E CL262C CI BADCAP
The required (ESQL/C) capability is not provided by the authorization string
(II_AUTHORIZATION). Please consult the ULTRIX/SQL system manager.
E CL262E CI BADCAP
The required (ESQL/FORTRAN) capability is not provided by the authorization string
(II_AUTHORIZATION).
Please consult the ULTRIX/SQL system manager.
E CL2633 CI BADCAP
The required (BLOCK/3270 Mode) capability is not provided by the authorization string
(II_AUTHORIZATION). Please consult the ULTRIX/SQL system manager.
E CL2634 CI BADCAP
The required (Distributed DBMS) capability is not provided by the authorization string
(II_AUTHORIZATION). Please consult the ULTRIX/SQL system manager.
E - CL2781 - GC- CONNECT- FAIL
An attempted network connection failed
E - CL2782- GC - DISCONNECT- FAIL
An attempted network disconnect failed
5-26

CL Class Messages

E - CL2783- GC - SEND - FAIL
An attempted network send failed

E - CL2784- GC - RECEIVE - FAIL
An attempted network receive failed

E- CL2785- GC- LISTEN- FAIL
An attempted network listen failed

E - CL2786- GC - PINIT - FAIL
Protocol initialization failed

E - CL2787 - GC - OPEN- FAIL
An attempted network open failed

E- CL2788- GC - NTWK- STATUS
Error status returned by network

E - CLFEOI - BS - SOCK- ERR
Could not create socket - Socket(2) call failed; presumably system error.

E - CLFE02- BS- BIND- ERR
Server could not bind address to socket; check II_DBMS_SERVER_PORT.

E - CLFE03 - BS - LISTEN - ERR
Server listen(2) call failed; presumably system error.

E - CLFE04- BS- ACCEPT - ERR
Server accept(2) call failed; presumably system error.

E - CLFE05 - BS- CONNECT- ERR
Connect failed: NAME server, DBMS server, or COMM server not running or busy. First
retry, and then check servers.

E - CLFE06- BS- WRITE- ERR
Write to peer process failed; it may have exited.

E - CLFE07- BS- READ - ERR
Read from peer process failed; it may have exited.

E - CLFE08- BS- CLOSE - ERR
Error closing connection; presumably system error.

E - CLFE09- BS - REGISTER - ERR
Error registering a process connection: presumably system error.

CL Class Messages

5-27

E_CLFEOA_BS_BADADDR_ERR

5-28

CL Class Messages

CO Class Messages

E- C00005 - FILE- OPEN - ERR
COPY: can't open file '%Oc'.

E- C00006- FILE- CREATE- ERR
COPY: can't create file '%Oc'.

E- C00008- DOMAIN- SIZE
COPY: domain '%Oc', size too small for conversion. There were %lc rows successfully
copied from ' %2c' into '% 3c' .

E- C00009BAD
-INPUT
COPY: bad input string for domain '%Oc'. Input was '%lc'. There were %2c rows
successfully copied from ' % 3c' into ' %4c. '

E- COOOOAEOF
-ERR
COPY: unexpected end of file found while filling domain ' %Oc' for row % I c.

E- COOOOB - LEN- SPEC - ERR
COPY: bad varchar length specifier found while filling domain '%Oc' for row % lc.

E- COOOOF- UNTERMINATED
COPY: an unterminated 'cO' or 'text(O)' field occurred while filling domain '%Oc'.

E- COOOll- WIDTH- EXCEEDED
COPY: The maximum width of the output file cannot exceed 2008 bytes per row.

E- C00014- BLANKED- CHARS
COPY: Warning: %Oc domains had control characters which were converted to blanks.

E- C00015 - TRUNCATED- CHARS
COPY: Warning: %Oc cO or text(O) character domains were truncated.

E - C00018BAD
-FILETYPE
COPY: '%Oc' is an invalid filetype. Filetype must be 'text', 'binary' ,or 'variable'.

CO Class Messages

6-1

E - C00019- NOBINARY
COPY: The filetype must not be 'binary' when any of the columns are 'text(O)'.

E- COOOIA- GENERAL- ERR
COPY: Error encountered while processing row %Oc.

E - COOOIB - INVALID - VALUE
COPY: Invalid character value (numeric value %Od) found while processing row % lc.

E- COOOID- ROWLEN- EXCEEDED
COPY: Computed row length exceeds allowable row length.

E- COOOIE- TYPE- CONVERT
COPY: Column '%Oc', cannot convert type '%lc' to type '%2c'.

E - C00022 - COpy - INIT- ERR
COPY: Internal error initializing COPY.

E- C00023- COpy- INTRNL- ERR
COPY: ULTRIX/SQL internal error processing row %Oc.

E- C00024- FILE- READ - ERR
COPY: Unexpected END OF FILE while processing row %Oc.

E- C00025 - MEM - ALLOC - ERR
COPY: Error allocating memory while processing row %Oc.

E - C00028- WARNINGS
COPY: Warning: Copy completed with %Oc warnings. %1c rows successfully copied.

E - C00029 - COpy- TERMINATED
COPY: Copy terminated abnormally. %Oc rows successfully copied.

E- C0002A- COpy- ABORTED
COPY: Copy has been aborted.

E - C0002B - BADROWS
COPY: %Oc rows could not be processed.

E - C0002C - LOGGED
COPY: %Oc rows were written to the Copy Log File '%lc'.

E- C0002F- LOG- WRITE- ERR
COPY: Error writing to Copy Log File '%Oc' while processing row %lc.

6-2

CO Class Messages

E- C00030- LOG- CLOSE- ERR
COPY: Error closing Copy Log File '%Oc'.

E- C00031 - FILE- CLOSE- ERR
COPY: Error closing Copy File ' %Oc' .

E- C00032BAD
DATA
COPY: Bad data value for column '%Oc' encountered while processing row % lc.
E- C00036- LOG- OPEN- ERR
COPY: Error opening Copy Log File ' %Oc' .

E- C00037 - MEM- INIT- ERR
COPY: Error allocating memory while initializing Copy.

E- C00038- MEM- ERR
COPY: Error allocating memory while processing row %Oc.

E- C00039- TUP- FORMAT- ERR
COPY: Error processing row %Oc. Cannot convert column '%lc' to tuple format.

E- C0003A- ROW- FORMAT- ERR
COPY: Error processing row %Oc. Cannot convert column '%lc' to row format.

E- C0003B- FILE- WRITE - ERR
COPY: Error writing to Copy File while processing row %Oc.

E- C0003C - PROG - READ - ERR
COPY: Error reading row from ULTRIX/SQL Application while processing row %Oc.

E- C0003D- PROG - WRITE- ERR
COPY: Error writing row to ULTRIX/SQL Application while processing row %Oc.

CO Class Messages

6-3

DC Class Messages

E- DCOOOI- OPENDB

Unable to open database '%Oc'.
Explanation:

This error will occur when the database specified as a command
line argument does not exist. There may be other reasons as to
why a connection to the named database cannot be made.

System Status:

Program exits.

Recommendation:

If the named database is known to exist, try connecting to it
using the terminal monitor. This will result in a more explicit
error message.

E- DC0002- NOTABLE

Table '%Oc' does not exist in database '% 1c' .
Explanation:

The table that the user wishes to be described as a data structure
does not exist.

System Status:

Program exits.

Recommendation:

Check the table name used for correctness.

E - DC0003- FILE

Cannot open output file '%Oc'.
Explanation:

This error occurs if the user does not have write permission in
the location specified or has given an directory path that does not
exist.

System Status:

Program exits.

Recommendation:

Check that a file can be opened in the location specified.

E - DC0004- OPNTABLE

An error occurred while trying to open table '%Oc'.
Explanation:

A DBMS error occurred during the opening of the specified table.

System Status:

Program exits.

Recommendation:

Try running the program again. There may be a temporary
condition that is preventing the table from being opened.
DC Class Messages

7-1

E_DCOOOS_SQLTYPE
Internal conversion error with SQL data type %Od, data size % Id.
Explanation:

The internal data type of one or more of the columns in the table
to be described cannot be converted to an SQL datatype. This is
probably caused by an internal error.

System Status:

Program exits.

Recommendation:

Please submit a Software Performance Report (SPR).

E - DC0006- FLAG
Unknown flag '%Oc'.
Explanation:

An unknown flag was used on the command line.

System Status:

Program exits.

Recommendation:

Check validity of command line arguments.

E- DC0007 - MANYARGS
Too many command line arguments.
Explanation:

DCLGEN takes five arguments: language, database, table, file
and structure-name. If more than 5 are given, it is an error.

System Status:

Program exits.

Recommendation:

Check validity of command line arguments.

E- DC0008- BAD NAME
Illegal database/table name '%Oc'.
Explanation:

ULTRIX/SQL database and table names may consist of between
1 and 24 characters. They must start with an alpha character or
an underscore followed by alpha-numeric characters or
underscores. They may contain no special characters.

System Status:

Program will prompt for valid database name.

E - DC0009 - BADLANG
Unknown or unsupported language '%Oc'.
Explanation:

The user has specified a host language that is not supported by
the DCLGEN utility.

System Status:

Program will prompt for valid language name.

Recommendation:

Check spelling of language.

S- DCOOAl - WORK:
Informs user that the program is in progress.
S- DCOOAl- WORK
DCLGEN: Working ...
7-2

DC Class Messages

S DCOOA2 DESC:

Informs user that program is writing out data declaration to file.
S DCOOA2 DESC

DCLGEN: Describing table '%Oc' ...
S DCOOA3 COMMENT:

This text represents a host language comment that is generated into the output file along
with the data structure.
S- DCOOA3- COMMENT

Description of table %Oc from database % lc
S- DCOOA4- USAGE:

S- DCOOAS- ARGS:

These two messages are issued if the user types in the DCLGEN command line with an
incorrect number of arguments.
S- DCOOA4- USAGE

DCLGEN Usage is:
S- DCOOAS- ARGS

dclgen language database table file structure/prefix
S- DCOOA6- ARGLANG:

S- DCOOA7- ARGDB:

S- DCOOA8- ARGTABLE:

S- DCOOA9- ARGFILE:

S- DCOOAA- ARGSTRUCT:

These are used as command line prompts to the user.
S- DCOOA6- ARGLANG

Language
S- DCOOA7- ARGDB

Database
DC Class Messages

7-3

S DCOOA8 ARGTABLE

Table

S- DCOOA9- ARGFILE
File

S- DCOOAA- ARGSTRUCT
Structure

S- DCOOAC - ARGPREFIX
Prefix
S DCOOAB:
This message is printed if the user has interrupted the program.

S- DCOOAB - ABORT
DCLGEN: Aborting ...

7-4 DC Class Messages

DE Class Messages

E- DEOOOI - NoClass
No object type '%Oc' found. No object type '%Oc' found. Valid values are 'a', 'f', 'g', 'j',
'r', or 'q'. This parameter will be skipped.
Explanation:

This occurs if a bad prefix is given on the command line or in
the prompt, and no matching class of frontend objects
corresponds to the prefix.

System Status:

This parameter will be skipped.

Recommendation:

Specify the correct prefix and rerun command.

E - DE0002- NotDBA
Only the DBA may use the -c flag. You are not the DBA for this database, so you cannot
use the -c flag.
Explanation:

The -c flag is used to delete all objects, irrespective of who owns
it. This is only allowed by the DBA.

System Status:

Pro gram stops.

Recommendation:

Use the -u flag to become the DBA, if you have authority.

E _ DE0003 _ BadFlag
Bad flag %Oc specified. The correct syntax is:
deleter [-s] [-uuser] [-c] dbname
{-[rfjagq]objectname}
Explanation:

An illegal flag was specified.

System Status:

Program stops.

Recommendation:

Correct error and retry.

E _ DE0004_ NoOpen
Could not open database. An error occurred in opening the database. Details were in the
previous message.
Explanation:

An error occurred, and was displayed to the user.

System Status:

Program aborts.

Recommendation:

Try again.
DE Class Messages

8-1

E_DE0005_BadType
Bad object type %Oc given. A bad object type prefix was found. Valid prefixes are 'j' 'a'
'f' 'r' 'q' and 'g'. Reenter.
Explanation:

Prefix did not match one of the valid prefixes.

System Status:

Reprompt.

Recommendation:

Reenter correct entry.

E _ DE0006_ TooMany
More than %Od matching objects found. More than %Od matching objects were found
when checking for type % Ic with name of %2c and owner %3c. Any more than %Od will
be left in the database.
Explanation:

Only the first set will be processed.

System Status:

The rest will be left in the database.

Recommendation:

Rerun command to get the rest.

S- DE0007 - Status
Deleting %Oc % Ic with owner %2c from database ...
S- DE0008- NoMatch
No %Ocs matching name %Ic and owner %2c found ...
E - DE0009- GenError
Error occurred in deleting %Oc. An error occurred in deleting %Oc % Ic with owner %2c.
The status code is %3x. A previous message should explain what the problem was.

8-2

Explanation:

An error status was returned from the deleting routines.
Generally this is because of a database error of some sort. Check
the status number if no message was given.

System Status:

Correct action according to status.

Recommendation:

Correct and rerun.

DE Class Messages

OM Class Messages

E - DMOOOO- OK
DMF successful return status.
E - DM0006- BAD- ATTR - FLAGS
Illegal flags for attribute characteristics.
E - DM0007 - BAD - ATTR- NAME
Illegal attribute name.
E - DM0008- BAD- ATTR- PRECISION
Illegal value for attribute precision.
E - DM0009 - BAD- ATTR- SIZE
Illegal size for attribute.
E - DMOOOA- BAD - ATTR- TYPE
Illegal type for attribute.
CB
E - DMOOOB - BAD-LENGTH
Incorrect length for DMF control block.
CB
E - DMOOOC - BAD-TYPE
Incorrect type for DMF control block.
E - DMOOOD- BAD- CHAR- ID
Unknown characteristics identifier.
E - DMOOOE- BAD- CHAR- VALUE
Illegal characteristics value.
E - DMOOOF- BAD- DB - ACCESS - MODE
Unknown database access mode.
DB
E - DMOOIO- BAD-ID
Illegal database identifier.
OM Class Messages

9-1

E - DMOOll- BADDB
-NAME
Illegal database name.
E DMOOIA BAD FLAG

Illegal flag value or combination, in control block.
E - DMOOIBBAD
-INDEX
Corrupt index table found.
E_DMOOIC_BAD_KEY_SEQUENCE
Illegal key sequence to modify.
E - DMOOID- BAD- LOCATION- NAME
Unknown location name.
LIST
E - DMOOIF- LOCATION-ERROR
The new and old location lists specified for the relocate command are incorrect.
E - DM0020- DMU- TOO- MANY
No more than 255 DMU statements can be executed in a transaction.
TOO
E - DM0021 - TABLES-MANY
No more than Ox3fffffff tables can be created in a database.
BAD
PARAMETER
E - DM002ABad parameter to DMF operation.
E - DM002B - BAD- RECORD - ID
Illegal record identifier.
E - DM002C - BAD- SAVEPOINT- NAME
Unknown savepoint name.
E - DM002D- BAD - SERVER- ID
Illegal server identifier.
E - DM002E- BAD - SERVER- NAME
Illegal server name.
E - DM002F- BAD - SESSION- ID
Illegal session identifier.
E - DM0030- BAD- SESSION- NAME
Illegal session name.

9-2

OM Class Messages

E - DM0039 - BAD- TABLE- NAME
Illegal table name.
E - DM003A- BAD - TABLE- OWNER
Illegal table owner.
E - DM003B- BAD - TRAN - ID
Illegal transaction identifier.
E - DM003CBAD
TID
Illegal tuple identifier.
E - DM003E- DB - ACCESS - CONFLICT
Database access conflict.
E - DM003FDB
-OPEN
Database is op n.
E_DM0040_DB_OPEN_QUOTA_EXCEEDED
Open database quota exceeded.
E_DM0041_DB_QUOTA_EXCEEDED
Server database quota exceeded.
E - DM0042- DEADLOCK
Resource deadlock.
E - DM0044- DELETED - TID
Tuple at tid already deleted.
E - DM0045 - DUPLICATE- KEY
Attempt to insert duplicate key.
E - DM0046- DUPLICATE- RECORD
Attempt to insert duplicate record.
E - DM0047 - CHANGED - TUPLE
Attempt to changed a record which has already been changed by the query.
E - DM004A- INTERNAL - ERROR
Internal DMF error detected.
E_DM004B_LOCK_QUOTA_EXCEEDED
Lock quota exceeded.

OM Class Messages

9-3

E- DM004C - LOCK- RESOURCE- BUSY
Lock resource is currently busy.

E - DM004D- LOCK- TIMER- EXPIRED
Lock timer expired before lock granted.

E- DM004F- LOCK- RETRY
Lock is held by a run away server. Recover the transactions on the run away server and
retry.

E - DM0050- TABLENOT
-LOAD ABLE
The table requested cannot be loaded: it is indexed, joumaled, or not empty.

E- DM0053- NONEXISTENT- DB
Nonexistent database.

E - DM0054- NONEXISTENT- TABLE
Nonexistent table.

E- DM0055- NONEXT
No more data satisfies request.

E- DM0056- NOPART
NOPART btree error.

E- DM0057- NOROOM
No space in current page.

E - DM0058- NOTIDP
No tid pointer in index.

E - DM0059 - NOT- ALL- KEYS
Not all keys specified in modify of a index table.

E- DM005A- CANT- MOD- CORE- STRUCT
The structure of the core system catalogs: iirelation, iiattribute, iiindexes, ii_relidx,
iidevices cannot be modified.

E - DM005B - SESSION- OPEN
Session(s) are open.

E_DM005C_SESSION_QUOTA_EXCEEDED
Server quota on sessions exceeded.

E - DM005D - TABLE- ACCESS - CONFLICT
Table access conflict.
9-4

OM Class Messages

E - DM005E- CANT- UPDATE- SYSCAT
User does not have enough privilege to change the core system catalogs:iirelation,
iiattribute, iiindexes, iidevices.

E - DM005F- CANT- INDEX- CORE- SYSCAT
User cannot place an index on the core system catalogs: iirelation, iiattribute, iiindexes,
ii_relidx, iidevices.

E- DM0060- TRAN IN PROGRESS
Transaction in progress.

E - DM0061 - TRAN - NOT IN PROGRESS
Transaction in not in progress.

E_DM0062_TRAN_QUOTA_EXCEEDED
Session transaction quota exceeded.

E - DM0063- TRAN- TABLE- OPEN
Table still open at end of transaction.

E - DM0064- USER - ABORT
User abort forced DMF operation abort.

E - DM0065 - USER - INTR
User interrupt forced DMF operation abort.

E - DM006D- BAD - OPERATION- CODE
Unrecognized DMF operation code.

E - DM006F- SERVER- ACTIVE
Server is active.

E- DM0070- SERVER- STOPPED
Server is stopped.

E - DM0071 - LOCATIONSTOO
-MANY
Number of locations exceeds the maximum allowed for this operation.

E - DM0072NO
LOCATION
Location list must be specified for this operation.

E- DM0073- RECORD - ACCESS - CONFLICT
Attempted to insert or delete or replace record in a table open for read.

E - DM0074NOT
POSITIONED
Attempted to get/replace/delete next record in scan but record is not currently positioned.
OM Class Messages

9-5

E - DM0075- BAD- ATTRIBUTE- ENTRY
Invalid attribute record read while attempting to open a table.
E - DM0076- BAD - INDEX- ENTRY
Invalid index record read while attempting to open a table.
E - DM0077 - BAD - TABLE- CREATE
Could not create table.
E - DM0078- TABLE- EXISTS
Table already exists.
E- DM0079- BAD - OWNER- NAME
Invalid characters in owner name.
E - DM007C - BAD - KEY - DIRECTION
Illegal key direction.
E - DM007D - BTREE- BAD- KEY - LENGTH
Invalid key length for btree table.
E - DM007E- LOCATION- EXISTS
Location already exists.
E - DM007F- ERROR- STARTING- SERVER
Could not start the server due to an internal error.
E - DM0080- BAD - LOCATION - AREA
Location Area specified is not valid.
E - DM0081 - NO - LOGGING - SYSTEM
The Logging System is not active on this node. The server cannot be brought up until the
logging system is started.
E - DM0083 - ERROR- STOPPING- SERVER
Error trying to stop the server.
E - DM0084 - ERROR - ADDING - DB
Error trying to add database to server.
E - DM0085- ERROR- DELETING- DB
Error deleting database from server.
E - DM0086- ERROR- OPENING- DB
Error opening database in server.

9-6

OM Class Messages

E - DM0087- ERROR- CLOSING- DB
Error closing database in server.

E - DM0088- ERROR- ALTERING - SERVER
Error altering server.

E- DM0089- ERROR- SHOWING- SERVER
Error Showing server characteristics.

E - DM008A- ERROR- GETTING- RECORD
Error trying to get a record.

E - DM008B- ERROR- PUTTING - RECORD
Error trying to put a record.

E - DM008C - ERROR- REPLACING - RECORD
Error trying to replace a record.

E - DM008D - ERROR- DELETING- RECORD
Error trying to delete a record.

E - DM008E- ERROR- POSITIONING
Error trying to position a table.

E - DM008F- ERROR- OPENING- TABLE
Error opening a table.

E- DM0090- ERROR- CLOSING- TABLE
Error closing a table.

E- DM0091 - ERROR- MODIFYING - TABLE
Error modifying a table.

E- DM0092- ERROR- INDEXING - TABLE
Error creating an index for a table.

E- DM0093- ERROR- SORTING
Error sorting data.

E- DM0094- ERROR- BEGINNING- TRAN
Error beginning a transaction.

E- DM0095- ERROR- COMMITING - TRAN
Error committing a transaction.

OM Class Messages

9-7

E - DM0096- ERROR- ABORTING - TRAN
Error aborting a transaction.
E - DM0097 - ERROR- SAVEPOINTING
Error creating a savepoint.
E_DM0098_NOJOIN
Did not join two leafs during a BTREE merge.
E- DM009D- BAD - TABLE- DESTROY
Error trying to destroy a table.
E - DM009E- CANT- OPEN- VIEW
It is illegal to try to open a view, base table(s) must be opened.

E - DM009F- ILLEGAL- OPERATION
DMF illegal operation for current state, such as trying to begin a transaction when a
transaction is already in progress.
E - DMOODO- LOCK- MANAGER - ERROR
Error creating a server lock list.
E- DMOODI - BAD - SYSCAT- MOD
Error trying to modify core system catalogs:
iirelation, iiattribute or iiindexes.
E - DMOIOODB
INCONSISTENT
Database is inconsistent.
E_DMOIOl_SET_JOURNAL_ON
Joumaling was turned on for the table created.
E - DMOI02- NONEXISTENT- SP
Error aborting to a nonexistent savepoint.
E - DMOI03- TUPLE- TOO - WIDE
Error trying to create a table with illegal tuple size.
E - DMOI04- ERROR- RELOCATING - TABLE
An error occurred trying to relocate a table.
E - DMOI05 - ERROR - BEGIN- SESSION
An error occurred trying to begin a session.
E - DMOI06- ERROR- ENDING - SESSION
An error occurred trying to end a session.
9-8

OM Class Messages

E - DMOI07- ERROR- ALTERING - SESSION
An error occurred trying to alter session parameters.

E- DMOI08- ERROR- DUMPING- DATA
An error occurred trying to truncate the data of a temporary file.

E - DMOI09 - ERROR- LOADING- DATA
An error occurred while trying to load data into a file.

E - DMOIOA- ERROR- ALTERING- TABLE
An error occurred while alter the characteristics of a table.

E - DMOIOB - ERROR- SHOWING - TABLE
An error occurred while showing information about a table.

E - DMOIOC - TRAN - ABORTED
The transaction has been aborted by the logging system in order to reclaim log space.

E - DMOIOD - ERROR- ALTERING- DB
An error occurred while altering the characteristics of a database.

E- DMOIOF- ISAM- BAD - KEY - LENGTH
Invalid key length for isam table.

E- DMOIIO- COMP- BAD- KEY- LENGTH
Invalid key length for compressed table.

E_DMOlll_MOD_IDX_UNIQUE
It is not allowed to modify a secondary index with non-unique keys to a unique structure.

E_DMOl12_RESOURCE_QUOTA_EXCEED
Error allocating resource, resource limit exceeded.

E - DMOl13DB
-INCOMPATABLE
Database is incompatible with the current version of ULTRIX/SQL.

E - DMOl14- FILE- NOT- FOUND
Specified Table is missing underlying physical file.

E - DMOl15- FCMULTIPLE
Database must be added in SINGLE SERVER mode in order for FAST COMMIT to be
used.

E - DMOl16- FAST- COMMIT
An Error occurred in the DMF Fast Commit procedure - Server can no longer support
Fast Commit protocol.
DM Class Messages

9-9

E - DMOl17- WRITE- BEHIND
An error occurred in a session used for Asynchronous Write Behind. Write Behind session
terminated.
E - DMOl18- CANT- OPEN- GATEWAY
Gateway tables do not have an underlaying data file in ULTRIX/SQL format. DMF cannot
access this gateway table as thought it were a local table.
E - DM0133 - SERVER- CANT- OPEN- DB
Server must be restarted to clear invalid database control block.
E_DMIOOl_JSP_INIT
An error occurred initializing the journal support program. Make sure program is installed
or you are running with proper privilege.
E _ DMI002 _JSP_MISS _ ARGS
Wrong number of arguments given.%! dmfjsp operation [ operation-specific-arguments ]
E_DMI003_JSP_UNRECOGNIZED
Unrecognized command line flag.
E _ DMI004_JSP_BAD_ARGUMENT
Bad argument given.
E_DMI005_JSP_BAD_ARG_COMBO
An inconsistent combination of arguments was given.
E_DMI006_JSP_TAPE_ONE_DB
You can only checkpoint/rollforward one database at a time to/from tape.
E_DMI007_JSP_MEM_ALLOC
Error allocating memory for the journal support program.
E - DMI008- CANT - OPEN - DB
Error occurred trying to open the database.
E_DMI009 _JSP _DBDB_OPEN
Error occurred trying to open IIDBDB database.
E _ DMIOOA _JSP _ OPEN _IIUSER
Error occurred trying to open IIUSER table.
E _ DMIOOB _JSP _NOT_USER
You are not a valid ULTRIX/SQL user.

9-10

DM Class Messages

E_DMIOOC_JSP_NOT_OVERUSER
The user specified with -u flag is not a valid ULTRIX/SQL user.
E _ DMIOOD _JSP _ CLOSE _IIUSER
Error occurred trying to close the IIUSER table.
E_DMIOOE_JSP_NO_SUPERUSER
You do not have superuser privilege.
E _DMIOOF _JSP _ OPEN _IIDB
Error occurred trying to open the IIDATABASE table.
E_DMIOIO_JSP_CLOSE_IIDB
Error occurred trying to close the IIDATABASE table.
E _ DMIOll_JSP _DB _NOTFOUND
The database specified was not found. If no database name was specified, there were no
databases owned by you.
E _DMI013 _JSP _CLOSE _IILOC
Error occurred trying to close the IILOCATION table.
E_DMI014_JSP_DB_NOT_DB_OWNER
You do not own the database specified.
E_DMI016_JSP_MUST_USE_TABLE
Must specify a table using the -t flag when using the -f flag.
E_DMI017 _JSP_II_DATABASE
II_DATABASE must be defined for the ULTRIX/SQL LAR utilities to function.
Parameters:

None.

Explanation:

The ULTRIX/SQL LAR utilities (ckpdb, rollforwarddb and
auditdb) can not function unless II_DATABASE is correctly
defined. In fact all of ULTRIX/SQL is dependent on these values
being properly defined.

System Status:

Processing aborts.

Recommendation:

Consult the ULTRIX/SQL Operations Guide.

E _ DMI018_JSP _II_LOCATION
The ULTRIX/SQL LAR utilities could not open the IILOCATION table in IIDBDB.
Parameters:

None.

Explanation:

The ULTRIX/SQL LAR utilities (ckpdb, rollforwarddb and
auditdb) can not function unless II_LOCATION is available and
consistent.
DM Class Messages

9-11

System Status:

Processing aborts.

Recommendation:

Consult your ULTRIX/SQL system administrator.

E_DMI019 _JSP_NO_ATP _DB
No database name passed to auditdb. Check the command line arguments.

E- DMII00- CPP- BAD - LOCATION
Error checkpoint database, unusable location found.

E- DMIIOI- CPP- WRITE - ERROR
Error writing checkpoint.

E- DMII02CPP
-FAILED
Previous errors caused checkpoint to fail.

E- DMII03- CPP- CONFIG- UPDATE
Error occurred updating configuration file.

E- DMII04- CPP- CKP- ERROR
Error occurred taking checkpoint.

E DMII05 CPP CNF OPEN
Error occurred opening configuration file.

E_DMII06_CPP_JNL_CREATE
Error occurred creating journal file.

E- DMII07- CPP- CATALOG- ERROR
Error occurred updating system catalogs.

E- DMII08- CPP- OPEN- DB
Error occurred trying to open the database.

E- DMII09- CPP- MEM - ALLOC
Checkpoint requesting more memory than available.

E- DMIIOA- CPP- CLOSE- DB
Error occurred closing the database.

E- DMl10BCPP
FAILED
Error occurred checkpointing the database.

E- DMIIOC- CPP- CNF- CLOSE
Error occurred closing the configuration file for the database.

9-12

OM Class Messages

E - DMII0D- CPP- DB - BUSY
Database is currently being used. Database lock conflict.
E_DMII0E_CPP_FAIL_NO_JNL
Error occurred trying to checkpoint the database, the database remains not joumaled.
E - DMII0F- CPP- FAILNO
-CHANGE
Error occurred trying to checkpoint the database, the database journal status remains
unchanged.
E _ DMIII0 _ CPP_DELETE _JNL
Error deleting old journal files.
E - DMllll - CPP- DELETE- CKP
Error deleting old checkpoint files.
E_DMll12_CPP_JNLCKP _NODEL
Error deleting journal or checkpoint files.
E - DMll13CPP
NOARCHIVER
Need to drain journal records from the log and the Archiver Process does not exist. Must
restart the archiver.
E - DMll15 - CPP II CHECKPOINT
ULTRIX/SQL cannot function unless II_CHECKPOINT is properly defined.
Parameters:

None.

Explanation:

The ULTRIX/SQL LAR utilities (ckpdb, rollforwarddb and
auditdb) can not function unless II_CHECKPOINT is correctly
defined. In fact all of ULTRIX/SQL is dependent on these values
being properly defined.

System Status:

Processing aborts.

Recommendation:

Consult the ULTRIX/SQL Operations Guide.

E_DMll16_CPP_II_JOURNAL
ULTRIX/SQL cannot function unless II_JOURNAL is properly defined.
Parameters:

None.

Explanation:

The ULTRIX/SQL LAR utilities (ckpdb, rollforwarddb and
auditdb) can not function unless II_JOURNAL is correctly
defined. In fact all of ULTRIX/SQL is dependent on these values
being properly defined.

System Status:

Processing aborts.

Recommendation:

Consult the ULTRIX/SQL Operations Guide.

OM Class Messages

9-13

E - DMll17- CPP-II-DATABASE
ULTRIX/SQL cannot function unless II_DATABASE is properly defined.
Parameters:

None.

Explanation:

System Status:

Processing aborts.

Recommendation:

Consult the ULTRIX/SQL Operations Guide.

E_ DMll18_ CPP_JNL _ OPEN
Error opening journal file while checkpointing the database.

E_DMll19_CPP_JNL_TRUNCATE
Error truncating journal file while checkpointing the database.

E _ DMl120_ CPP _JNL _CLOSE
Error closing journal file while checkpointing the database.

E- DMl121 - CPP- BEGIN- ERROR
Error starting checkpoint sequence.

E- DMl122- CPP- END - ERROR
Error ending checkpoint sequence.

E_DM1200_ATP_DB_NOT_JNL
This database is not journaled, thus cannot be audited.

E - DM1201 - ATP- WRITING - AUDIT
Error occurred writing audit trail.

E_DM1202_ATP _JNL_OPEN
Error occurred opening a journal file.

E_DM1203_ATP_JNL_READ
Error occurred reading a journal file.

E _ DM1204_ ATP _JNL _ CLOSE
Error occurred closing a journal file.

E - DM1205 - ATP - NO - BT- FOUND
Audit records found for a unknown transaction.

9-14

DM Class Messages

E- DM1206- ATP - TOO- MANY - TX

Too many simultaneous transactions.
E- DM1207- ATP - NON - DB

Nonexistent database.
E- DM1208- ATP- OPEN- DB

Error occurred opening the database.
E- DM1209- ATP- CNF- OPEN

Error occurred opening the configuration file.
E- DM120A- ATP- CNF- CLOSE

Error occurred closing the configuration file.
E- DM120B - ATP- CATALOG - ERROR

Error occurred retrieving catalog information.
E- DM120C - ATP- ADF- ERROR

Unexpected ADF runtime error.
E- DM120DATP
-DESCRIBE

Error occurred retrieving table description.
E- DM120E- ATP- DB - BUSY

Can't audit database at this time. Database is currently being used by an exclusive
(SOLE_SERVER) server.
E- DM120F- ATP- TBL- NOTFOUND

Attempting to audit for a nonexistent table.
E- DM1300- RFP- OPEN- DB

Error occurred opening the database.
E- DM1301 - RFP- ROLL - FORWARD

An error occurred that precludes further processing.
E- DM1302- RFP- CNF- OPEN

Error occurred opening the configuration file.
E- DM1303 - RFP- CNF- CLOSE

Error occurred closing the configuration file.
E- DM1304- RFP- MEM - ALLOC

Error occurred allocating memory.

OM Class Messages

9-15

E _DM1305 _RFP_JNL_ OPEN
Error occurred opening journal file.

E - DM1306- RFP- APPLY - RECORD
Error occurred attempting to apply roll forward record.

E- DM1307 - RESTORE
Error occurred restoring checkpoint.

E - DM1308- RFP- BAD- RECORD
Bad record type found in journal.

E- DM1309- RFP- RFC - DELETE
Error deleting the temporary configuration file aaaaaaaa.rfc during restoration.

E - DM130A- RFP - NO - CNFRFC
Error occurred restoring the checkpoint, no aaaaaaaa.cnf or aaaaaaaa.rfc configuration file
exists for the database.

E- DM130B - RFP- RENAME- CNF
Error occurred renaming the configuration file.

E - DM130C - RFP - DELETE- ALL
Error deleting files from directory before restoring from checkpoint.

E- DM130D- RFP- BAD- RESTORE
Error occurred trying to restore the checkpoint.

E- DM130FRFP
-RESTORED
The checkpoint has been successfully restored.

E - DM1310- RFP- CLOSE- DB
Error occurred trying to close the database.

E - DM1311- RFP - MUST- RESTORE
The database has not been restored, can't rollforward only from journals.

E _DM1312 _RFP _JNL _CREATE
Error creating the new journal file.

E- DM1313- RFP- CKP- HISTORY
Error updating checkpoint history.

E - DM1314- RFP- DRAIN- ERROR
Error occurred while records were being journaled from the logfile.

9-16

OM Class Messages

E - DM1315- RFP- DB- BUSY
Database is currently being used. Database lock conflict.

E - DM1316- RFP- NO- CHECKPOINT
Database has not been checkpointed. Cannot rollforward.

E - DM1317- RFP- CKP- MISSING
One of the Checkpoint files for this database is missing. Cannot rollforward.

E - DM1318- RFP- NO- CKP- FILE
The Checkpoint file % Ic for database %Oc at location:%2c does not exist.

E - DM1319- RFP- NO - BT- FOUND
No begin transaction record found for current journal record.

E - DM1320- RFP- TOO- MANY - TX
Error allocating new transaction queue entry in rollforward.

E - DM1321 - RFP- BEGIN- ERROR
Error starting rollforward sequence.

E - DM1322- RFP- END - ERROR
Error ending rollforward sequence.

E - DM9000- BAD - FILE- ALLOCATE
Disk file allocation error on database:%Oc table: % Ic pathname:%2c filename:%3c

E - DM9001 - BAD- FILE- CLOSE
Disk file close error on database:%Oc table:% Ic pathname:%2c filename:%3c

E - DM9002- BAD - FILE- CREATE
Disk file create error on database:%Oc table: % Ic pathname:%2c filename:%3c

E - DM9003- BAD - FILE- DELETE
Disk file delete error on database:%Oc table:%Ic pathname:%2c filename:%3c

E - DM9004- BAD - FILE- OPEN
Disk file open error on database:%Oc table: % Ic pathname:%2c filename:%3c

E - DM9005- BAD- FILE- READ
Disk file read error on database:%Oc table: % Ic pathname:%2c filename:%3c page:%4d

E- DM9006- BAD- FILE- WRITE
Disk file write error on database:%Oc table: % Ic pathname:%2c filename:%3c page:%4d

OM Class Messages

9-17

E - DM9007 - BAD - FILE- SENSE
Disk file sense error on database:%Oc table:% Ic pathname:%2c filename:%3c
E - DM9008- BAD- FILE- FLUSH
Disk file flush error on database:%Oc table:%Ic pathname:%2c filename:%3c
E - DM9009 - BAD - FILE- RENAME
Disk file rename error on database:%Oc physicallocation:% Ic 0Id:%2c new: %3c
E - DM900A- BAD - LOG- DBADD
Error adding a database to the logging system for the server:%Ox on database: % Ic
owner:%2c physicallocation:%3c.
E - DM900B - BAD - LOG - ALTER
Error altering the characteristics of the logging system, characteristics:%Ox.
E - DM900C - BAD - LOG - BEGIN
Error trying to begin a transaction on the database %Ox.
E - DM900D - BAD - LOG- CLOSE
Error removing the server:%Ox from the logging system.
E - DM900E- BAD - LOG - END
Error trying to end the transaction:%Ox.
E - DM900F- BAD - LOG - EVENT
Error waiting for the logging system event:%Ox.
E _ DM9010_BAD _LOG_FORCE
Error forcing the log page to disk for transaction:%Ox.
E - DM9011 - BAD- LOG - INIT
Error initializing the logging system.
E - DM9012- BAD - LOG - OPEN
Error adding a server to the logging system.
E - DM9013- BAD- LOG - POSITION
Error positioning the log file for transaction:%Ox.
E - DM9014- BAD - LOG - READ
Error reading record from log file for transaction:%Ox.
E - DM9015 - BAD - LOG - WRITE
Error writing record to log file for transaction:%Ox.

9-18

DM Class Messages

E- DM9016- BAD- LOG- REMOVE

Error removing the database:%Ox from the logging system.
E- DM9017 - BAD - LOG- SHOW

Error trying to display the logging system information:%Ox.
E- DM9018- BAD- LOG- ERASE

Error initializing the log file, %Oc.
E- DM9019- BAD - LOCK- ALTER

Error altering the characteristics of the locking system, characteristics:%Ox.
E- DM901A- BAD - LOCK- CREATE

Error creating a lock list.
E- DM901B - BAD - LOCK- RELEASE

Error releasing the lock list:%Ox.
E_DM901C_BAD_LOCK_REQUEST

Error requesting a lock on mode:%Ox for the lock list:%Ix.
E- DM901D- BAD- LOCK- SHOW

Error trying to display the locking system information:%Ox.
E- DM901E- BAD - LOCK - INIT

Error initializing the locking system.
E- DM901F- BAD- TABLE- CREATE

Error creating the table:% Ic in database:%Oc.
E- DM9020- BM- BAD - UNLOCK- PAGE

Error unlocking the page:%Od for table:% Ic in database:%2c for lock list:%3x.
E- DM9021 - BM- BAD - LOCK- PAGE

Error locking the page:%Od for table:% Ic in database:%2c with mode:%3d for lock
list:%4x.
E- DM9022- BM- BAD - PROTOCOL

Buffer manager protocol error in the page:%Od for table:%Ic in database:%2c with
mode:%3d for lock list:%4x.
E- DM9023 - ERROR- OPENING- TABLE

Error opening the table:% lc in database:%Oc.
E- DM9024- ERROR- CLOSING - TABLE

Error closing the table: % Ic in database:%Oc.
DM Class Messages

9-19

E - DM9025 - BAD - TABLE- DESTROY
Error destroying the table:% Ic in database:%Oc.
E - DM9026- REL- UPDATE- ERR
Error updating iirelation system table on database %Oc while executing some other
operation such as modify, index, etc. Check consistency of system catalogs.
E - DM9027- INDEX- UPDATE- ERR
Error updating iiindexes system table on database %Oc while executing some other
operation such as modify, index, etc. Check consistency of system catalogs.
E - DM9028- ATTR - UPDATE - ERR
Error updating iiattribute system table on database %Oc while executing some other
operation such as modify, index, etc. Check consistency of system catalogs.
E - DM9029- UNEXPECTED - FILE
When trying to relocate a table a file was found at the new location %Oc with the same
name % Ic as the file your are relocating. Check the new location directory and delete any
files which should not exist at this location.
E _DM902A _BAD _JNL _ CLOSE
Error closing journal file for database %Oc file sequence % I d.
E_DM902B_BAD_JNL_CREATE
Error creating journal file % I c at location %Oc for sequence %2d.
E _ DM902C _BAD _JNL _ OPEN
Error opening journal file for database %Oc file sequence % I d.
E_DM902D _BAD _JNL_READ
Error reading journal file for database %Oc file sequence % Id block %2d.
E_DM902E_BAD _JNL_ WRITE
Error writing journal file for database % 1c file sequence %Od block %2d.
E_DM902F_BAD _JNL_ UPDATE
Error updating journal file for database %Oc file sequence % Id.
E_DM9030_BAD _JNL_FORMAT
Format error in journal file for database %Oc file sequence % Id block %2d.
E_DM9031_BAD _JNL_LENGTH
Record length error in journal file for database %Oc file sequence % Id block %2d.
E_DM9032_BAD_JNL_DELETE
Error occurred trying to delete a journal file.
9-20

DM Class Messages

E _ DM9033 _BAD _JNL _DIRCREATE
Error occurred trying to create a journal directory.
E_DM9034_BAD_JNL_NOT_FOUND
Error occurred trying to access a journal file.
E - DM9040- BAD- CKP- DIRCREATE
Error occurred trying to create a checkpoint directory.
E - DM9041 - LK - ESCALATE- TABLE
Maximum number of locks for transaction exceeded. Escalating to table level lock on
table %Oc in database % 1c.
E - DM9042- PAGE- DEADLOCK
Deadlock encountered locking page %Od for table % lc in database %2c with mode %3d.
E - DM9043 - LOCK- TIMEOUT
Timeout occurred during lock request on table %Oc in database % Ic with mode %2d.
E - DM9044- ESCALATE- DEADLOCK
Deadlock encountered while escalating to table level locking on table %Oc in database
%Ic with mode %2d.
E - DM9045 - TABLE - DEADLOCK
Deadlock encountered locking table %Oc in database % I c with mode %2d.
E - DM9046- TABLE- NOLOCKS
Lock quota exceeded with lock request on table %Oc in database % 1c.
E- DM9047 - LOCK - RETRY
Lock is held by a run away server. Recover the transactions on the run away server and
retry.
E - DM9048- DEV - UPDATE - ERROR
An error occurred while trying to update the iidevices table.
E - DM9049- UNKNOWN - EXCEPTION
An Unexpected Exception occurred in the DMF Facility, exception number %Od.
E - DM904A- FATAL- EXCEPTION
A Fatal Error has occurred in the DMF Facility.
E - DM904B - BAD - LOCK- EVENT
Error requesting lock event with flag %Od and value % ld for lock list %2x.

OM Class Messages

9-21

E_DM9100_LOAD_TABLE_ERROR
Error occurred while loading a table for a modify, index, or load table operation.
E_DM9101_UPDATE_CATALOGS_ERROR
Error occurred while executing the update system tables phase for a modify or index table
operation.
E - DM9200BM
-BUSY
Error deallocating the buffer manager. Buffer manager is still busy.
E_DM9201_BM_CLOSE_PAGE_ERROR
Error writing pages to disk when close a table.
E_DM9202_BM_BAD _FILE _PAGE_ADDR
Error specifying an invalid page number to access.
E _ DM9203 _ DM2R_ RCB _ ALLOC
Error allocating a ReB.
E_DM9204_BM_FIX_PAGE_ERROR
Error fixing a page.
E_DM9205_BM_INVALIDATE_PAGE_ERR
Error invalidating a page.
E_DM9206_BM_BAD _PAGE
Error specifying a bad page buffer address.
E_DM9207 _BM_INTERNAL_ERROR
Buffer manager internal error.
E_DM9208_BM_UNFIX_PAGE_ERROR
Error unfixing a page.
E_DM9209_BM_NO_CACHE_LOCKS
Out of buffer manager cache locks.
E_DM920A_BM_ESCALATE_LOCK_ERR
Error escalating page level lock to table level lock for a table.
E_DM920B_BM_NO_BUFFERS
Out of buffer manager buffers.
E_DM920C_BM_BAD _FAULT_PAGE
Error faulting a page.

9-22

OM Class Messages

E- DM920D - BM- BAD - GROUP- FAULTPAGE

Error faulting a group of pages.
E- DM920E- BM- FORCE- PAGE- ERROR

Error forcing a page to disk.
E- DM920F- BM- GROUP- FORCEPAGE- ERR

Error forcing a group of pages to disk.
E- DM9210- BM- VALIDATEPAGE
-ERROR

Error validating a page.
E DM9211 DMOL BT

Error logging BEGIN TRANSACTION operation.
E- DM9212- DMOL- ROBT

Error logging begin readonly transaction operation.
E DM9213 DMOL ET

Error logging END TRANSACTION operation.
E DM9214 DMOL BI

Error logging before image.
E- DM9215- DMOL- PUT

Error logging APPEND operation.
E- DM9216- DMOL- DEL

Error logging DELETE operation.
E- DM9217 - DMOL- REP

Error logging REPLACE operation.
E- DM9218- DMOL- SBI

Error logging system catalog before image.
E- DM9219- DMOL- SPUT

Error logging system catalog APPEND operation.
E- DM921A- DMOL- SDEL

Error logging system catalog DELETE operation.
E- DM921B- DMOL- SREP

Error logging system catalog REPLACE operation.

DM Class Messages

9-23

E - DM921C - DMOL- BM
Error logging begin mini transaction operation.
E- DM921D- DMOL- EM
Error logging end mini transaction operation.
E - DM921E- DMOL- BALLOC
Error logging BTREE page allocation operation.
E- DM921F- DMOL- BDEALLOC
Error logging BTREE page deallocation operation.
E- DM9220- DMOL- CALLOC
Error logging common page allocation operation.
E- DM9221 - DMOL- SAVEPOINT
Error logging savepoint declaration.
E- DM9222- DMOL- ABORTSAVE
Error logging abort to savepoint operation.
E - DM9223- DMOL - FRENAME
Error logging file rename operation.
E - DM9224- DMOL- FCREATE
Error logging file create operation.
E - DM9225- DMOL- OPENDB
Error logging database open operation.
E - DM9226 - DMOL - CLOSEDB
Error logging database close operation.
E- DM9227- DMOL- PHASE1
Error logging the begin of the first phase for two phase commit operation.
E - DM9228- DMOL- CONFIG
Error logging the configuration file update operation.
E - DM9229 - DMOL - CREATE
Error logging table CREATE operation.
E - DM922A- DMOL- DESTROY
Error logging table DESTROY operation.

9-24

OM Class Messages

E - DM922B - DMOL- RELOCATE
Error logging table RELOCATE operation.
E- DM922C- DMOL- MODIFY
Error logging table MODIFY operation.
E - DM922D- DMOL- INDEX
Error logging table INDEX operation.
E - DM922E- DMOL- POSITION
Error positioning the log file.
E - DM922F- DMOL- READ
Error reading the log file.
E - DM9230- DMOL - FORCE
Error forcing the log record to disk.
E - DM9231 - DMOL - LOGFORCE
Error forcing the last log page to disk.
E- DM9232- DMOL- ALLOCATE
Error initializing the logging system and allocate the logging context.
E- DM9233 - DMOL - DEALLOCATE
Error terminating the logging system and deallocate the logging context.
E - DM9234- DMOL- BPEXTEND
Error logging BTREE file extend operation.
E - DM9235 - DMOL- BCP
Error logging begin consistency point operation.
E - DM9236- DMOL - SM1 - RENAME
Error logging SYSMOD file rename operation.
E - DM9237- DMOL- SM2- CONFIG
Error logging SYSMOD configuration file update operation.
E - DM9238- LOG- READ- EOF
End of the log file is encountered.
E - DM9239- BM- BAD- PARAMETER
Bad parameters to buffer manager.

DM Class Messages

9-25

E- DM923A- CONFIG - OPEN- ERROR
Error occurred opening configuration file, (aaaaaaaa.cnf).
E - DM923B- CONFIG- CLOSE- ERROR
Error occurred closing the configuration file, (aaaaaaaa.cnf).
E - DM923C - CONFIG - FORMAT- ERROR
Error in configuration file format.
E - DM923D - DMOM- NOMORE
DMF memory exhausted.
E - DM923E- DMOM- SIZE
Size of 0 passed to memory allocator.
E - DM923F- DM2F- OPEN- ERROR
Error occurred opening a file for a table.
E - DM9240- DM2F- CLOSE- ERROR
Error occurred closing a file for a table.
E - DM9241 - DM2F- BAD- LOCATION
Error finding location for table.
E - DM9242- DMIR- EXTEND
Error occurred while extending a heap, isam or hash table.
E - DM9243- DMIR- PUT
Error occurred while putting a record to a heap, isam or hash table.
E - DM9244- DMIR- REPLACE
Error occurred while replacing a record in a heap, isam or hash table.
E - DM9245- DMIS- ALLOCATE
Error occurred allocating disk space for a heap table.
E - DM9246- DMIS - DEALLOCATE
Error occurred de allocating disk space for a temporary table.
E - DM9247 - DMIH - ALLOCATE
Error occurred allocating disk space for a hash table.
E - DM9248- DMIH - SEARCH
Error occurred searching a hash table.

9·26

OM Class Messages

E - DM9249 - DMII- ALLOCATE
Error occurred allocating disk space for a isam table.
E- DM924ADMII
-SEARCH
Error occurred searching a isam table.
E- DM924B- DMlS- BBEGIN
Error occurred beginning to build a heap table.
E - DM924C - DMlS - BEND
Error occurred ending the build of a heap table.
E - DM924D- DMlS - BPUT
Error occurred adding a record to a heap table being built.
E - DM924E- DMIH- BBEGIN
Error occurred beginning to build a hash table.
E - DM924F- DMIH- BEND
Error occurred ending the build of a hash table.
E - DM9250- DMIH - BPUT
Error occurred adding a record to hash table being built.
E - DM9251 - DMII- BADD
Error occurred adding disk space to an isam table during a build.
E - DM9252- DMII- BEND
Error occurred ending the build of a isam table.
E - DM9253- DMII- BOTTOM
Error occurred building the index of an isam table.
E - DM9254- DMIB - EXTEND
Error occurred extending the disk file for a btree table.
E - DM9255 - DMIB - FREEDATA
Error occurred adding a page to the free list.
E- DM9256- DMIB - FINDFREE
Error occurred finding a page on the free list.
E - DM9257 - DMIB - FINDDATA
Error occurred finding disk space for a new record.

OM Class Messages

9-27

E - DM9258- DMIB - MERGE
Error occurred merging the index of a btree table.

E - DM9259 - DMIB - BEND
Error occurred completing the build of a btree table.

E - DM925A- DMIB - BEGIN
Error occurred preparing to build a btree table.

E - DM925B- DMIB - BPUT
Error occurred adding a record to a btree table being built.

E - DM925C - DMIB - BADD
Error occurred adding disk space to a btree table during a build.

E- DM925D - DMIB- BOTTOM
Error occurred adding or updating an index page in a btree during a build.

E - DM925E- DMIB - ALLOCATE
Error occurred allocating disk space for a new record.

E- DM925F- DMIB - GETBYBID
Error occurred accessing a record by it's index address.

E - DM9260- DMIB - DELETE
Error occurred deleting a record.

E - DM9261 - GET
Error occurred getting a record.

E - DM9262- DMIB - PUT
Error occurred adding a record.

E - DM9263 - DMIB - REPLACE
Error occurred replacing a record.

E - DM9264- DMIB - SEARCH
Error occurred searching the btree index.

E - DM9265ADD
DB
Error occurred while trying to add a database.

E - DM9266- UNLOCK- CLOSE- DB
Error occurred unlocking a database during a close.

9-28

OM Class Messages

E - DM9267 - CLOSE- DB
Error occurred closing a database.

E - DM9268- OPEN- DB
Error occurred opening a database.

E- DM9269- LOCK- OPEN- DB
Error occurred locking a database during a open.

E - DM926A- TBL- CACHE- LOCK
Error occurred cache locking a table.

E - DM926B - BUILD- TCB
Error occurred while building a TCB.

E - DM926CTBL
-CLOSE
Error occurred during a close table.

E - DM926DTBL
-LOCK
Error occurred locking a table.

E - DM926E- RECLAIM - TCB
Error occurred while reclaiming unused TCB's.

E - DM926F- TBL- CACHE- CHANGE
Error occurred updating table cache lock.

E - DM9270- RELEASE - TCB
Error occurred releasing a TCB.

E - DM9271 - BUILD - TEMP- TCB
Error occurred building a TCB for a temporary table.

E - DM9272- REL- UPDATE- ERROR
Error occurred updating a system table.

E - DM9273TBL
-UPDATE
Warning due to resource shortages an error occurred updating the tuple count information
for a table.

E - DM9274TBL
VERIFY
Error occurred verifying a cache table.

E - DM9275- DM2R- LOAD
Error adding a record to a sort table.

DM Class Messages

9-29

E - DM9276TBL
-OPEN
Error occurred opening a table.
E - DM9277 - DMOL- LOCATION
Error occurred writing a log record for adding a location.
E - DM9278- DMOL- SETBOF
Error occurred positioning Log File BOP.
E _ DM9279 _ DMOL _JNLEOF
Error occurred updating Log File EOP.
E - DM927A- DMOL- ARCHIVE
Error occurred logging archive operation.
E - DM927B - DMOL- STARTDRAIN
Error occurred starting drain operation.
E - DM927C - DMOL- END DRAIN
Error occurred ending drain operation.
E - DM927D- DMOL- LOAD
Error occurred writing a log record for LOAD TABLE.
E_DM927E_VPDATE_TCB
Error updating TCB tuple and pages counts for system catalog.
DCB
E - DM927F-INVALID
An Error closing the database '%Oc' has made it unavaliable by this server. In order to
access this database, the server should be shut down and a new server started up.
E_DM9280_DMOJ_CLOSE_ERROR
Error occurred closing a journal file.
E _ DM9281_DMOJ _ CREATE_ERROR
Error occurred creating a journal file.
E _ DM9282 _ DMOJ _ OPEN_ERROR
Error occurred opening a journal file.
E_DM9283_DMOJ_READ_ERROR
Error occurred reading a journal file.
E_DM9284_DMOJ_WRITE_ERROR
Error occurred writing a journal file.

9-30

OM Class Messages

E_DM9285_DMOJ_UPDATE_ERROR
Error occurred updating a journal file.
E_DM9286_DMOJ_FORMAT_ERROR
Error occurred in the journal file format.
E_DM9287 _DMOJ_LENGTH_ERROR
Error occurred in the length of a journal record.
E - DM9288- TBL- CTRL- LOCK
Error requesting a table control lock.
E - DM9289 - BM- BAD - MUTEX - PROTOCOL
Page mutex protocol error.
E- DM928A- CONFIG - EXTEND - ERROR
Error occurred extending the configuration file, (aaaaaaaa.cnf).
NOT
E - DM928B - CONFIG-COMPATABLE
Configuration file is not compatible with the current version of ULTRIX/SQL. Config
version = %Od.%ld, ULTRIX/SQL version = %2d.%3d.
E - DM9290- DM2F- DELETE- ERROR
Error occurred while attempting to delete a file.
E - DM9291 - DM2F- FILENOTFOUND
When attempting to open a file, the file did not exist.
E - DM9292- DM2F- DIRNOTFOUND
When attempting to open a file, the directory did not exist.
E - DM9293- DM2F- BADDIR- SPEC
When attempting to open a file, the directory specification was incorrect.
E - DM9294- DM2R- BADLOGICAL
II_SRT_IN_DEV value is invalid for this database.
E- DM9295- DM2U- BADLOGICAL
II_SRT_OUT_DEV value is invalid for this database.
E - DM9300- DMOP- CLOSE- PAGE
Buffer still fixed.
E - DM9301 - DMOP- FORCE- PAGES
Buffer still fixed.

OM Class Messages

9-31

E - DM9302- DMOP- INVALIDATE
Page is fixed or busy.

E- DM9303- DMOP- MUTEX
Inconsistent page and buffer.

E- DM9304- DMOP- UNMUTEX
Inconsistent page and buffer.

E - DM930S- DMOP- TRAN - INVALIDATE
Page is fixed or busy.

E- DM9306- DMOP- UNFIX - PAGE
Bad page address.

E - DM9307- DMOP - WBEHIND - SIGNAL
Error signaling Write Behind Threads to wakeup.

E - DM930A- DMOP- ALLOCATE
Error starting up the Buffer Manager.

E - DM930B- DMOP- DEALLOCATE
Error shutting down the Buffer Manager.

E - DM9310- DM2R- RELEASE - RCB
Not a reb.

E - DM9311- DM2R- DELETE
Not a reb or tcb.

E - DM9312- DM2R- GET
Not a reb.

E- DM9313- DM2R- POSITION
Not a reb or tcb.

E- DM9314- DM2R- PUT
Not a reb or tcb.

E - DM9315 - DM2R - REPLACE
Not a reb or tcb.

E - DM9316- DM2R- UNFIX - PAGES
Error occurred releasing page held in reb during query to system catalog.

9-32

OM Class Messages

E - DM931F- DM2T- RENAME- FILE
Error occurred renaming load file during a LOAD operation.

E - DM9320- DM2T- BUILD- TCB
Not a dcb.

E- DM9321 - DM2T- CLOSE
Not a rcb.

E - DM9322- DM2T- FIND - TCB
Not a dcb.

E - DM9323- DM2T- OPEN
Not a dcb.

E- DM9324- DM2T- DEALLOCATE- TCB
Not a tcb.

E - DM9325 - DM2T- UPDATE- REL
Not a tcb.

E - DM9326- DM2T- VERIFY - TCB
Not a tcb.

E - DM9327 - BAD - DB - OPEN- COUNT
The database open count was greater than zero for the first opener of the database,
therefore the database must be considered inconsistent. This can happen when the log file
was not readable,therefore if any transaction were in progress they could not be backed
out. This database must be rolled forward from a checkpoint or destroyed and recreated.

E - DM9328- DM2T- NOFREE- TCB
Cannot free resources, no TCB's to reclaim.

E_DM9329 _DMOJ_M_ALLOCATE
An allocation error occurred trying to merge the cluster journal files.

E _ DM932A_DMOJ_M _LIST_FILES
An error occurred trying to list the cluster journal files to merge.

E_DM932B_DMOJ_M_NO_FILES
The config file indicates there should be cluster journal files to merge but none were
found.

E _DM932C _DMOJ_M _BAD _NODE_JNL
An invalid node id was found for one of the journal cluster files.

DM Class Messages

9-33

E_DM932D _DMOJ_M_BAD _READ
An error occurred reading one of the cluster journal files.
E_DM932E_DMOJ_M_BAD_RECORD
An illegal records was found when reading one of the cluster journal files.
E - DM932F- DMOL- ALTER
An error occurred trying to log an ALTER log record.
E - DM9330- DM2T- PURGE- TCB
An error occurred while invalidating a TCB.
E - DM9331 - DM2T- TBL- IDX- MISMATCH
Base table missing or indices missing.
E - DM9332 - DM2T - lOX - DOMAIN - ERROR
Index domain out of range of incorrect length and/or type.
E- DM9333- DM2T- EXTRA - lOX
Extra entry found in index table.
E- DM9334- DM2T- MISSING- IDX
Missing index entry in index table.
E- DM9335 - DM2F- END FILE
End of file was reached during a read or write operation.
E - DM9336- DM2F- BUILD - ERROR
Error building a File Control Block.
E - DM9337 - DM2F- CREATE- ERROR
Error creating physical file(s) for database table.
E - DM9338- DM2F- INIT - ERROR
Error initializing newly created physical file(s) for database table.
E - DM9339 - DM2F- ALLOC - ERROR
Error allocating space in physical file(s) for database table.
E - DM933A- DM2F- FORCE - ERROR
Error forcing physical file for database table.
E - DM933B - DM2F- FLUSH- ERROR
Error flushing physical file for database table.

9-34

DM Class Messages

E - DM933C - DM2F- READ- ERROR
Error reading pages for database table.
E - DM933D- DM2F- SENSE- ERROR
Error sensing physical file for database table.
E - DM933E- DM2F- RENAME- ERROR
Error renaming physical file.
E - DM933F- DM2F- WRITE- ERROR
Error writing pages for database table.
E - DM9340- DM2F- RELEASE- ERROR
Error releasing a File Control Block.
E - DM9341 - DMII- FLUSH
Error occurred flushing pages to an isam table during a build.
E - DM9342- DM2U- REORG
Error occurred during MODIFY TO REORGANIZE operation.
E - DM9343 - DMOL - ECP
Error logging end consistency point operation.
E - DM9344- BM- CP- FLUSH- ERROR
Error flushing dirty pages from Buffer Manager during Consistency Point.
E - DM9345 - BM- WBFLUSH - WAIT
Error in Write Behind Thread waiting for WBFLUSH event.
E - DM9346- DIRTY- PAGE- NOT - FIXED
Buffer Manager protocol error: page %Od of table (% Ic, %2c) in database '%3c' is not
fixed for write but is marked as modified - buffer state Ox%4x.
E DM9347 CONFIG FILE PATCHED
-

Config file for data base '%Oc'was marked inconsistent by '%Ic' (time = %2d).
It is now being marked consistent (time = %3d).
E - DM9348- BM- FLUSH- PAGES - ERROR
Error flushing dirty pages from Buffer Manager in Write Behind Thread.
E - DM9349 - DMIH- NOFULL
Error updating primary page of hash chain to indicate that it is not full.
E - DM9350- BTREE- INCONSIST
Inconsistency found in Btree Index
OM Class Messages

9-35

E - DM9351 - BTREEBAD
-TID
Btree Error on table (%Oc, %lc) of database '%2c' : Leaf page references non existent
tuple: Bid (%3d, %4d), Tid (%5d, %6d), Key is '%7c' (%8c).
E _ DM9371_RELEASE _ TCB _ WARNING
Table Control Block could not be released due to inability to flush out modified pages
from cache.
E - DM937ETCB
-BUSY
Table Control Block is unexpectedly busy when attempting to deallocate.
E _ DM9381_DM2R_PUT_ERROR
Error putting a record.
E _ DM9385 _NO _INDEX_TUPLE
Cannot locate secondary index row for base table row at tid %Od.
Parameters:

Tid of base table row being updated

Explanation:

An update was made on a table that has a secondary index. When
the system attempted to update the corresponding secondary
index row, it was unable to find a row describing the updated
tuple of the base table.

System Status:

Update will be rejected and statement aborted.

Recommendation:

Index table may be no good.
Other errors in error log may give indication of reason for failing
to find index row. If system seems to be functioning correctly,
but row cannot be updated, recreating the secondary index may
be necessary.

E _ DM9386_SEC _INDEX_ERROR
Error updating secondary index '%Oc' for change to base table row at tid %ld.
Parameters:

N arne of secondary index - Blank if failed during open of 2nd
index. Tid of base table row being updated

Explanation:

An update was made on a table that has a secondary index. A
failure occurred attempting to update the corresponding
secondary index entry.

System Status:

Update will be rejected and statement aborted.

Recommendation:

Other errors in error log should give indication of reason for
failure. If bringing down server cannot solve problem, recreating
the secondary index may be necessary.

9-36

DM Class Messages

E- DM9387- INDEX - UPDATE- ERROR
Update failed due to inability to update secondary index table.
Parameters:

None.

Explanation:

An update was made on a table that has a secondary index. A
failure occurred attempting to update the corresponding
secondary index entry.

System Status:

Update will be rejected and statement aborted.

Recommendation:

Other errors in error log should give indication of reason for
failure. If bringing down server cannot solve problem, recreating
the secondary index may be necessary.

E - DM9388 - BAD - DATA- LENGTH
Character data value in row has an illegal length descriptor - length is %Od.
Parameters:

%Od

Explanation:

A VARCHAR or TEXT datatype has been encountered that has a
length descriptor that gives an impossible length. This means this
row is probably trashed. This error is probably encountered
while trying to compress or uncompress the tuple -- in these
cases the length value is needed.

- length given in length descriptor.

If the error is returned on an insert, then the bad row will not be
added to the database. If this error is returned on a select, then
the bad row is probably already in the database.
System Status:

Query will be rejected in normal case and the transaction
aborted. These actions can be altered by trace flags desribed
below.

Recommendation:

This error probably indicates a bad row. If this error is returned
on a select, then the table needs to be fixed. Following this error
should be an E_DM938A_BAD_DATA_ROW error that will
give the TID of the bad row.
The user should attempt to select the row by TID to verify that
this row is really unable to be returned from the database. The
table probably needs some type of recovery to fix the bad row.
See the User Action described below on error
E_DM938A_BAD_DATA_ROW.

E - DM9389- BAD- DATA- VALUE
Bad data value encountered in row of database.
Parameters:

None.

Explanation:

A bad data value was encountered in the database that could not
be interpreted by DMF. This error should be followed by an
E_DM938A error which indicates the TID of the bad tuple.

OM Class Messages

9-37

If the error is returned on an insert, then the bad row will not be
added to the database. If this error is returned on a select, then

the bad row is probably already in the database.
System Status:

Query will be rejected and the transaction aborted.

Recommendation:

See error E_DM938A_BAD_DATA_ROW.

E - DM938A- BAD - DATA- ROW
Bad row encountered in database '%Oc', table (%lc, %2c) - TID '%3d'.
Parameters:

%Oc
% 1c
%2c
%3d

Explanation:

A bad row was encountered in the database that could not be
interpreted by DMF.

- databse name
- table name
- table owner
- TID of bad row

If the error is returned on an insert, then the bad row will not be
added to the database. If this error is returned on a select, then

the bad row is probably already in the database.
System Status:

Query will be rejected in normal case and the transaction aborted.
The error recovery actions can be altered by the trace flags below.

Recommendation:

If this error is returned on a SELECT statement then there is

probably a bad row in the database. The user should do a select
by TID of the reported row to make sure that it is really bad. The
table should be recovered -- methods for doing this are described
below.
The supported method of fixing a table like this is to recover it
from the last checkpoint. If this is not practical or possible, the
table can be patched by removing the offending row.
There are two trace flags provided for this -- these are
undocumented trace flags that are not intended to be distributed
for general use! SET TRACE POINT DM801 will cause DMF to
skip bad rows like this when scanning the table. Thus the user
could do set trace point DM801 modify table to
storage_structure which would have the effect of rebuilding the
table without any of the offending rows.
SET TRACE POINT DM802 will cause DMF to return a
garbage row when a bad row is encountered. This allows the user
to do set trace point DM802 delete table where table.tid =
BAD_TID set notrace point DM802 This will delete the
offending row directly.
This is the only operation that should be attempted while having
this trace flag on as it may cause unexpected and upredictable
results if used while SELECTing a bad row.

9-38

DM Class Messages

E - DM938B - INCONSISTENT- ROW
Bad row encountered in database.
Parameters:

None.

Explanation:

A bad row was encountered in the database that could not be
interpreted by DMF.
If the error is returned on an insert, then the bad row will not be
added to the database. If this error is returned on a select, then

the bad row is probably already in the database.
System Status:

Query will be rejected and the transaction aborted.

Recommendation:

See E_DM938A_BAD_DATA_ROW desription.

RCP
E - DM9400-LOGSTAT
Error writing the logging statistics to the output log file.
E - DM9401RCP
-LOGINIT
Error initialize the logging system.
RCP
E - DM9402-BLDHDR
Error reconstructing the state of the log file header.
RCP
GETBLKSIZE
E - DM9403Error determining the block size of the log file.
E - DM9404RCP
-GETLASTBLK
Error locating the last block of the log file.
E- DM9405RCP
-GETCP
Error locating the last consistency point of the log file.
RCP
E- DM9406-GETAP
Error locating the last archiver point of the log file.
E - DM9407RCP
RECOVER
Error recovering transactions from the log file.
E- DM9408RCP
-PO
Error occurred in phase zero of recovering transactions from the log file.
E - DM9409RCP
-PI
Error occurred in phase one of recovering transactions from the log file.
E - DM940ARCP
P2
Error occurred in phase two of recovering transactions from the log file.

OM Class Messages

9-39

E- DM940CRCP
-ABORT
Error aborting a transaction.
E DM940E RCP RCPRECOVER
-Error recovering the transactions for the server.
E DM940F RCP CHKEVENT
-Error waiting for the logging system events.
E- DM9410RCP
-SHUTDOWN
Error shutting down the recovery process.
E- DM9411DMF
INIT
Error initializing the DMF working environment.
E - DM9412DMF
-TERM
Error terminating the DMF working environment.
E - DM9414- RCP- REDO- RECOV
Error in Rep Redo Recovery.
RCP
E - DM9415-GENDB
Error in Rep generating list of Redo Databases during REDO recovery.
RCP
REDOINIT
E- DM9416Error initializing Rep for REDO recovery.
E - DM9417 - RCP- REDO - PROC
Error in Rep processing REDO transactions.
E - DM9418RCP
RDMUINS
Error in Rep adding entry to REDO recovery DMU list.
RCP
E - DM9419-RDDBINS
Error in Rep adding entry to REDO recovery DB list.
RCP
E - DM941A-RBINS
Error in Rep adding entry to REDO recovery BI list.
E DM941B RCP REDOFINALE
-Error in Rep cleaning up after REDO recovery.
RCP
E - DM941C-GENDB
Error in Rep getting list of REDO databases

9-40

OM Class Messages

E - DM941DRCP
-MPO
Error in RCP processing mini phase-O of redo recovery

E - DM941ERCP
-MPI
Error in RCP processing mini phase-l of redo recovery

E DM941F PROC REDO
Error in RCP processing redo recovery
E- DM9500- DMXE- BEGIN
Error occurred beginning a transaction.

E - DM9501 - DMXE- COMMIT
Error occurred committing a transaction.

E- DM9502- DMXE- SAVE
Error occurred attempting to savepoint a transaction.

E - DM9503 - DMXE- ABORT
Error occurred aborting a transaction.

E - DM9504- DMXE- WRITEBT
Error writing delayed Begin Transaction record.

E - DM9600- DMVE- BALLOC
Error recovering BTREE page allocation operation.

E - DM9601 - DMVE- BAD- PARAMETER
Bad parameters to the recovery routine.

E - DM9602- DMVE- BDEALLOC
Error recovering BTREE page deallocation operation.

E - DM9603 - DMVE- BIPAGE
Error performing before image undo operation.

E - DM9604- DMVE- BPEXTEND
Error recovering BTREE file extend operation.

E - DM9605- DMVE- CALLOC
Error recovering common page allocation operation.

E - DM9606- DMVE- CREATE
Error recovering table CREATE operation.

OM Class Messages

9-41

E- DM9607- DMVE- DEL
Error recovering DELETE operation.

E - DM9608- DMVE- DESTROY
Error recovering table DESTROY operation.

E- DM9609 - DMVE- FCREATE
Error recovering file create operation.

E - DM960A- DMVE- FRENAME
Error recovering file rename operation.

E - DM960B - DMVE- INDEX
Error recovering table INDEX operation.

E - DM960C - DMVE- MODIFY
Error recovering table MODIFY operation.

E - DM960D - DMVE- PUT
Error recovering PUT operation.

E - DM960E- DMVE - RELOC
Error recovering table RELOCATE operation.

E- DM960F- DMVE- REP
Error recovering REPLACE operation.

E - DM9610- DMVE- SDEL
Error recovering system catalog DELETE operation.

E - DM9611 - DMVE- SMIRENAME
Error recovering SYSMOD file rename operation.

E - DM9612- DMVE- SM2CONFIG
Error recovering SYSMOD configuration file update operation.

E - DM9613 - DMVE- SPUT
Error recovering system catalo g PUT operation.

E - DM9614 - DMVE- SREP
Error recovering system catalog REPLACE operation.

E - DM9615 - DMVE- LK- FILE- EXTEND
Error extending the file:%Oc in database:% Ic for lock list:%2x while recovering a
transaction.

9-42

OM Class Messages

E - DM9616- DMVE- UNLK- FILE - EXTEND
Error extending the file:%Oc in database: % Ic for lock list:%2x while recovering a
transaction.
E - DM9617 - DMVE- LOCATION
Error recovering database ADD LOCATION operation.
E - DM961B - DMVE- ALTER
Error recovering table ALTER operation.
E - DM961C - DMVE- LOAD
Error recovering LOAD TABLE operation.
E - DM961D- DMVE- BAD- LOADTAB
Error recovering LOAD TABLE operation. Table is unexpected type.
E - DM961E- DMVE- REDEL
Error processing REDO recovery on Delete operation.
E - DM961F- DMVE- REPUT
Error processing REDO recovery on Insert operation.
E - DM9620- DMVE- REREP
Error processing REDO recovery on Replace operation.
E - DM9621 - DMVE- BAD - BEFORE- IMAGE
Error during recovery attempting to apply page Before Image. Logged BI record is not
consistent.
E - DM9700 - SR- OPEN- ERROR
Error occurred opening sort work file.
E - DM9701 - SR- CLOSE- ERROR
Error occurred deleting a sort work file.
E - DM9702- SR- READ - ERROR
Error occurred reading a sort work file.
E - DM9703 - SR- WRITE - ERROR
Error occurred writing a sort work file.
E - DM9704 - SORT- ALLMEM - ERROR
Error occurred allocating memory for a sort.
E - DM9706- SORT- PROTOCOL- ERROR
Sort routine call~d out of phase.
OM Class Messages

9-43

E- DM9707- SORT- BEGIN
Error occurred beginning a sort.

E - DM9708- SORT- END
Error occurred ending a sort.

E - DM9709 - SORT- INPUT
Error occurred switching from write to read phase.

E - DM970A- SORT- GET
Error occurred getting next sorted record.

E- DM970B- SORT- PUT
Error occurred adding a record to be sorted.

E - DM970C - SORT- DOMERGE
Error occurred merging sorted runs.

E - DM970D - SORT- WRITE- RECORD
Error occurred writing a record to the sort work file.

E- DM970E- SORT- READ - RECORD
Error occurred reading a record from the sort work file.

E- DM970F- SORT- OUTPUT- RUN
Error occurred preparing work file for a new run.

E- DM9710- SORT- INPUT - RUN
Error occurred preparing to read a run from the work file.

E - DM9800- ARCH - TERMINATE
Archi ver is Terminating.

E- DM9801 - ARCH - PHASE- ZERO
Error occurred during phase zero of the archiver.

E - DM9802- ARCH - PHASE- ONE
Error occurred during phase one of the archiver.

E - DM9803 - ARCH - PHASE- TWO
Error occurred during phase two of the archiver.

E- DM9804- ARCH - PHASE- THREE
Error occurred during phase three of the archiver.

9-44

OM Class Messages

E - DM9805 - ARCHCP
FORMAT
Archiver read a consistency point log record which had a bad format.
E - DM9806- ARCH - BAD - DBID
Archiver was given a bad LG database id from an LGshow call.
E- DM9807- ARCH - REUSED - DBID
Archiver was given a LG database id from an LGshow call which it had previously
returned.
E - DM9809- ARCH - LOG - SHOW
The Archiver got an error while trying to do an LGshow call.
E - DM980A- ARCH- LOG - READ
The Archiver got an error reading the log file.
E- DM980B- ARCH- LOG - FORCE
The Archiver got an error trying to force the log file.
E- DM980C - ARCH- LOG - EVENT
The Archiver got an error while trying to request a LG event.
E - DM980D- ARCH - LOG - ALTER
The Archiver got an error while trying to execute an LGalter.
E - DM980E- ARCH- LOG - ADD
The Archiver got an error trying to do an LGadd call.
E - DM980F- ARCH- LOG - REMOVE
The Archiver got an error trying to an LGremove call.
E - DM9810- ARCH - LOG- BEGIN
The Archiver got an error trying to do an LGbegin call.
E- DM9811- ARCH- LOG- END
The Archiver got an error trying to do an LGend call.
E - DM9812- ARCH - OPEN- LOG
The Archiver got an error trying to open the log file.
E - DM9813- ARCH - CLOSE- LOG
The Archiver got an error trying to close the logfile.
E - DM9814- ARCH - LOCK - CREATE
The Archiver got an error trying to create a lock list.

OM Class Messages

9-45

E - DM9815- ARCH - SHUTDOWN
The Archiver was told to shutdown.
E - DM9818- ARCH - ADD- DBID
The Archiver received a bad or duplicate database id from LG.
E_DM9819 _ARCH_ADD _JOURNAL
The Archiver got an error constructing the list of databases to be archived.
E_DM981C_ARCH_PURGE_JOURNAL
The Archiver got an error constructing the list of databases to be purged from the archiver.
E - DM981D- ARCH- PURGE- DBID
The Archiver received a bad or duplicate database id from LG.
E - DM981E- ARCH- READ - CP
The Archiver got an error trying to read a consistency point.
CSP
E - DM9900-INITIALIZE
The CSP process couldn't startup due to initialization errors.
E - DM9901 - CSP- ACTION- FAILURE
Unexpected failure processing node action event.
E - DM9902- CSP- CONFIG- ERROR
Unexpected error opening/reading II_CONFIG:CLUSTER.CNF.
E - DM9903 - CSP- CONFIG - FORMAT
Unexpected format for file II_CONFIG:CLUSTER.CNF.
E - DM9904CSP
-DECNET
Error creating DECnet object. Program requires an operational DECnet and SYSNAM
privilege.
E - DM9905- CSP- NOT- NODE
This node is not listed in the configuration file.
E_DM9906_CSP_RCPCONFIG
Error opening/reading RCP configuration file for this node.
E - DM9907- CSP- CREATE- RCP
Error creating process to execute as the RCP.
E_DM9908_CSP_CREATE_ACP
Error creating process to execute as the RCP.

9-46

OM Class Messages

E - DM9909CSP
-TIMER
Error queuing timer request.

E - DM990A- CSP- STALL- CLEAR
Error occurred when attempting to continue stalled lock requests. Wrong driver could be
loaded.

E- DM990B- CSP- DEADLOCK- CLEAR
Error occurred when attempting to continue distributed deadlock searches. Wrong driver
could be loaded.

E - DM990C - CSP- MASTER- LOCK
Unexpected error occurred attempting to request MASTER lock.

E - DM990D- CSP- NO- MSGS
No free messages available.

E - DM990E- CSP- READ - ACTION
Unexpected action associated with message being read.

E - DM990FCSP
-NETSHUT
DECnet is shutting down. The CSP will now shutdown.

E- DM9910CSP
-NETMSG
Unrecognized network message received.

E - DM9911CSP
-CANIO
Expected cancel I/O request found.

E_DM9912_CSP_READ_QUEUE
Error queuing read request.

E - DM9913 - CSP- READ - COMPLETE
Read request completed with unexpected error.

E- DM9914- CSP- WRITE- COMPLETE
Write request completed with unexpected error.

E - DM9915 - CSP- CONNECT- FAIL
Unexpected connect failure.

E - DM9916- CSP- ACCEPT - FAILURE
Unexpected accept failure.

E_DM9917 _CSP _REJECT _FAILURE
Unexpected reject failure.
OM Class Messages

9-47

E - DM9918- CSP- WRITE- ERROR
Unexpected error queuing write request.
E - DM9919- CSP- WRITE- ACTION
Unexpected action associated with message being written.
E - DM991A- CSP- NODE - LOCK
Unexpected error attempting to obtain NODE lock.
CSP
E - DM991B-'FAILOVER
Unexpected error attempting to obtain FAILOVER lock.
E - DM991C - CSP- MASTER- SIX
Unexpected error converting MASTER lock to SIX.
E - DM991D - CSP- NO- NODE- LOCK
Unexpected error attempting to block on node lock for another node.
E- DM991E- CSP- BAD- BROADCAST
Unexpected broadcast attempted.
E - DM991FCSP
-CSID
Unexpected error asking for cluster system node identifier.
CSP
E - DM9920-GETLKI
Unexpected error asking for lock information from VMS.
E - DM9921 - CSP- REFLECT- CONVERT
Unexpected error reflecting convert-convert deadlock.
E - DM9922- CSP- BAD - DEADLOCK
Unexpected status from LKdeadlock call.
E - DM9923- CSP - ACTION- ORDER
Node action was executed out of order.
E- DMFOOO- MUTE X- INIT
Error initializing a mutex.
E - DMFOOI - MUTE X- LOCK
Error locking a mutex.
E - DMF002- MUTEX- FREE
Error releasing a mutex.

9-48

DM Class Messages

E - DMF003 - MUTE X- UNLOCK
Error unlocking a mutex.

E - DMF004- EVENT- DECLARE
Error declaring an event. This is a result of a known bug that occurs when trying to end a
transaction or close a database and no more locks are available. To avoid this problem
until it has been fixed, configure your system with more locks.

E- DMFOOS- EVENT- PREPARE
Error preparing an event. This is a result of a known bug that occurs when trying to end a
transaction or close a database and no more locks are available. To avoid this problem
until it has been fixed, configure your system with more locks.

E - DMF006- EVENT- RELEASE
Error releasing an event.

E- DMF007- WAIT
Error waiting for an event. This is a result of a known bug that occurs when trying to end
a transaction or close a database and no more locks are available. To avoid this problem
until it has been fixed, configure your system with more locks.
E_ DMF008_DMOM_BAD_OBJECT
Memory manager given bad object to deallocate.

E - DMF009- DMOM- FREE- OVERLAP- PREV
Memory manager given object to free that overlaps the previous free object. %! Possible
double deallocation.

E - DMFOOA- DMOM- FREE- OVERLAP- PREV
Memory manager given object to free that overlaps the next free object. %! Possible
double deallocation.

E- DMFOOB - DMOM- PROTECT
Memory manager couldn't change memory protection.

E - DMFOOC - DMOM- FREE- OVERLAP- PREV
Memory manager data structures corrupted.

E - DMFOIO- DMIRNO
-PAGE
Expected page not given.

E- DMFOll- DMIR- BAD- TID
Given tid is not valid.

E - DMF012ADT
-FAIL
Unexpected ADT routine failure.
OM Class Messages

9-49

E - DMF013 - DMIB - CURRENT- INDEX
Current btree index page is inconsistently marked.
E - DMF014 - DMIB - PARENT- INDEX
Parent btree index page is inconsistently marked.
E - DMF015 - EVENT - SET
Unexpected error set event wait reason.
E - DMF016- EVENT - LWAIT
Unexpected error waiting for event.
E - DMF020- DMOP- VALIDATE
Unexpected error getting lock value for cached page.
E - DMF022- DMOP- CACHE IX IS
Unexpected error converting page cached in IX to IS.
E - DMF023- BM- CP- FLUSH- SEVERE
Severe Error flushing pages from Buffer Manager during Consistency Point.
E - DMF024- INCOMPLETE- CP
Fatal Error: All modified pages could not be flushed out of Buffer Manager during
Consistency Point.

9-50

DM Class Messages

DU Class Messages

S- DU0300- PROMPT
Enter Y for yes, N for no.
Parameters:

None.

Explanation:

Requests input from user -- used with runinteractive mode of
VERIFYDB. This prompt message always follows an
informative message indicating the action that VERIFYDB will
take if the user gives permission. It is automatically output by
duve_talk when message_type (duve_mtype) = ASK and mode
(duve_cb-duve_mode) = RUNINTERACTIVE. It is also output
when duve_mtype = INTERACTIVE and mode =
RUNINTERACTIVE. It is never output with any other message
type and mode combinations.

System Status:

Wait until input, loop back to prompt if input not valid

Recommendation:

Enter Y or N and hit carriage retum:Y means yes, do suggested
action.N means no, do not do suggested action.

S- DU0301- DROP- IIRELATION- TUPLE
The recommended action is to drop this tuple from iirelation (which effectively drops
table %Oc (owner % lc) from the database)
Parameters:

%Oc -- name of table (from iirelation.relid)
%lc -- name of table's owner (from iirelation.relowner)

Explanation:

VERIFYDB test #1 found a tuple with an invalid table specifier.
Since the table specifier is used to join iirelation tuples to tuples
in other system catalogs, this tuple is useless. If we know the
correct table id for this table, we should manually replace it in
iirelation. Otherwise, this tuple should be deleted from iirelation.
The recommended corrective action to make the system catalogs
consistent is to drop this table from the database by removing it
from the iirelation catalog. The user will be prompted to give
yes/no permission. If yes is given, VERIFYDB will take
recommended action. If no is given, VERIFY DB will proceed on
to next test.

DU Class Messages

10-1

NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.
System Status:

This is only an informative message, processing continues.
However, this type of message requires input from the user. The
S_DU0300_PROMPT message will be displayed following this
message, and processing will simply wait until some input is
given. If the input is not a valid response, the message will be
repeated until a valid response is given.

Recommendation:

Enter Y(ES) or N(O).

S- DU0302- DROP- TABLE
The recommended action is to drop table %Oc (owner %Ic) from the database.
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- name of table's owner (from iirelation.relowner)

Explanation:

A VERIFY DB test found a condition (which it reported) that
leaves the system catalogs inconsistent. The recommended
corrective action to make the system catalogs consistent is to
drop this table from the database via an SQL drop. The user will
be prompted to give yes/no permission. If yes is given,
VERIFY DB will take recommended action. If no is given,
VERIFY DB will proceed on to next text. (This message is
displayed in conjunction with VERIFY DB test 2a.)
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

S- DU0303- REPLACE- RELWID
The recommended action is correct the value in iirelation of (%Od) with (% Id)
Parameters:

%Od -- table's width from iirelation (ii relation. rei wid) % ld -sum of width of each attribute (from each iiattribute.attfrml)

Explanation:

VERIFY DB test #2b found a mismatch in table width between
iirelation and the sum of each column's width. The user will be
prompted to give yes/no permission. If yes is given, VERIFYDB
will take recommended action. If no is given, VERIFY DB will
proceed on to next text.

10-2

DU Class Messages

NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.
System Status:

Recommendation:

Enter Y(ES) or N(O).

S- DU0304- REPLACE- RELKEYS
The recommended action is to correct the value in iirelation of (%Od) with (% Id)
Parameters:

%Od -- # keys iirelation thinks there are (iirelation.relkeys)
% Id -- count of each key in iiattribute.

Explanation:

VERIFY DB test 3 found a mismatch between the number of
keys that should be in the table's primary key and the number
that are actually in the key. The user will be prompted to give
yes/no permission. If yes is given, VERIFYDB will take
recommended action. If no is given, VERIFYDB will proceed on
to next text.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

S- DU0305- CLEAR- PRTUPS
Recommended action is to clear protection information from iirelation.
Parameters:

None.

Explanation:

VERIFY DB test #8 found that iirelation specified there are
protections on this table, but none are defined in iiprotect. The
user will be prompted to give yes/no permission. If yes is given,
VERIFY DB will take the recommended action. If no is given,
VERIFY DB will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

DU Class Messages

10-3

System Status:

This is only an informative message, so processing continues.
However, this type of message requires input from the user. The
S_DU0300_PROMPT message will be displayed following this
message, and processing will simply wait until some input is
given. If the input is not a valid response, the message will be
repeated until a valid response is given.

Recommendation:

Enter YCES) or NCO).

S- DU0306- CLEAR- INTEGS
Recommended action is to clear integrity information from iirelation.
Parameters:

None.

Explanation:

VERIFY DB test #9 found that iirelation specified there are
integrities on this table, but none are defined in iiintegrity. The
user will be prompted to give yes/no permission. If yes is given,
VERIFY DB will take the recommended action. If no is given,
VERIFY DB will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

This is only an informative message, so processing continues.
However, this type of message requires input from the user. The
S_DU0300_PROMPT message will be displayed following this
message, and processing will simply wait until some input is
given.
If the input is not a valid response, the message will be repeated

until a valid response is given.
Recommendation:

Enter YCES) or NCO).

S- DU0307- CLEAR- CONCUR
Recommended action is to clear this locking specification from iirelation.
Parameters:

None.

Explanation:

VERIFYDB test #10 found that the CONCUR bit was set for a
table that was not a DBMS core system catalog. The user will be
prompted to give yes/no permission. If yes is given, VERIFYDB
will take the recommended action. If no is given, VERIFYDB
will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

10-4

DU Class Messages

given. If the input is not a valid response, the message will be
repeated until a valid response is given.
Recommendation:

Enter Y(ES) or N(O).

S- DU0308SET
-CONCUR
Recommended action is to set this locking specification from iirelation.
Parameters:

None.

Explanation:

VERIFY DB test #11 found that one of the DBMS core system
catalogs did not have the special locking (CONCUR) bit set in
iirelation.relstat. The user will be prompted to give yes/no
permission. If yes is given, VERIFYDB will take the
recommended action. If no is given, VERIFYDB will proceed to
the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

This is only an informative message, so processing continues.
However, this type of message requires input from the user. The
S_DU0300_PROMPT message will be displayed following this
message, and processing will simply wait until some input is
given.
If the input is not a valid response, the message will be repeated

until a valid response is given.
Recommendation:

Enter Y(ES) or N(O).

S- DU0309- MAKE- TABLE
Recommended action is to alter iirelation to indicate that this is a table, not a view
Parameters:

None.

Explanation:

VERIFY DB test #12 found that there was a physical disk file
associated with this view. This often indicates that it's really a
table that has been mismarked as a view. However, it is possible
that this is really a view and some joker has played around with
renaming files or messed up a backup somehow. The user will be
prompted to give yes/no permission. If yes is given, VERIFYDB
will take the recommended action. If no is given, VERIFYDB
will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

DU Class Messages

10-5

given. If the input is not a valid response, the message will be
repeated until a valid response is given.
Recommendation:

Enter Y(ES) or N(O).

S_ DU030A_CLEAR_CATALOG
Recommended action is to alter iirelation to stop indicating that this table is a system
catalog.
Parameters:

None.

Explanation:

VERIFY DB test # 5a found that a table was mismarked as a
system catalog when it did not start with "ii" or when the owner
was not $ingres. The user will be prompted to give yes/no
permission. If yes is given, VERIFYDB will take the
recommended action. If no is given, VERIFYDB will proceed to
the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

S_ DU030B _DROP_VIEW
The recommended action is to drop view %Oc (owner % Ic) from the database.
Parameters:

%Oc - name of view [null terminated string] % 1c - name of
view's owner [null terminated string]

Explanation:

VERIFY DB test #12 found that the specified view was not
defined in iitree. The user will be prompted to give yes/no
permission. If yes is given, VERIFYDB will take the
recommended action. If no is given, VERIFYDB will proceed to
the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

10-6

DU Class Messages

S- DU030C- CLEAR- VBASE
Recommended action is to clear view base specification from iirelation.
Parameters:

None.

Explanation:

VERIFYDB test #15 found that iirelation believed there was a
view based on this table, but none could be found in iidbdepends.
The user will be prompted to give yes/no permission. If yes is
given, VERIFYDB will take the recommended action. If no is
given, VERIFYDB will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

S- DU030DSET
-IDXD
The recommended action is to set a bit in iirelation.relstat for base table %Oc (owner % Ic)
to indicate that the table has a secondary index.
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- name of tables owner (from iirelation.relowner)

Explanation:

The IDXD bit in iirelation.relstat for the base table indicates that
there is a secondary index table for this table. VERIFYDB will
set this bit automatically, unless VERIFYDB is in
RUNINTERACTIVE mode. Then the user will be prompted to
give yes/no permission. If yes is given, VERIFYDB will take the
recommended action. If no is given, VERIFYDB will proceed to
the next test. This is the prompt for VERIFYDB test #17 and #30.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

DU Class Messages

10-7

S- DU030EFIX
-RELIDXCOUNT
The recommended action is to set iirelation.relidxcount to %Od (from % 1d)
Parameters:

%Od -- number of secondary indexes defined in iiindexes.
% ld -- number of secondary indexes iirelation thinks there are
(from iirelation.relidxcount)

Explanation:

VERIFY DB test #18 found a discrepancy between the number of
secondary indexes that iirelation thinks there are and the number
of secondary indexes defined in iiindex.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

VERIFYDB keeps running.

Recommendation:

Enter Y(ES) or N(O).Ie, give yes/no permission to set
iirelation.relidxcount to the number of index tables defined in
iiindex.

S_DU030F_CLEAR_RELIDXCOUNT
The recommended action is to modify iirelation to indicate that there are no secondary
indexes for table %Oc (owner % lc)
Par~meters :

%Oc -- name of table (from iirelation.relid)
% lc -- name of tables owner (from iirelation.relowner)

Explanation:

VERIFYDB test #18 found that iirelation thinks there are
secondary indexes defined on this table and there AREN'T any.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

VERIFY DB keeps running.This is only an informative message,
so processing continues. However, this type of message requires
input from the user. The S_DU0300_PROMPT message will be
displayed following this message, and processing will simply
wait until some input is given. If the input is not a valid
response, the message will be repeated until a valid response is
given.

Recommendation:

Enter Y(ES) or N(O).Give yes/no permission to clear
iirelation.relidxcount and clear IDXD bit from iirelation.relstat.

10-8

DU Class Messages

S- DU0310- CLEAR- OPTSTAT
The recommended action is to modify iirelation to stop indicating that there are optimizer
statistics for this table.
Parameters:

None.

Explanation:

VERIFYDB test # 19 found that iirelation thinks there are
optimizer statistics for this table, but there aren't any. The user
will be prompted to give yes/no permission. If yes is given,
VERIFYDB will take the recommended action. If no is given,
VERIFY DB will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

S_DU0311_RESET_RELLOCOUNT
The recommended action is to modify the number of locations in iirelation from %Od to
%ld.
Parameters:

%Od -- number of locations iirelation thinks there are (from
iirelation.relloccount)
% ld -- number of locations defined in iidevices.

Explanation:

VERIFY DB test #20 found a discrepancy between the number of
locations that iirelation thinks there are and the number of
locations defined in iidevices.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

VERIFYDB keeps running.

Recommendation:

Enter Y(ES) or N(O).

DU Class Messages

10-9

S- DU0312FIX
-RELDFILL
The recommended action is to replace the invalid data fill factor with the default data fill
factor.
Parameters:

None.

Explanation:

The data page fill factor must be specified for all table types. If it
is not, then a default value will be used. This is detected by
VERIFYDB tests 22 through 25. The user will be prompted to
give yes/no permission. If yes is given, VERIFY DB will take the
recommended action. If no is given, VERIFY DB will proceed to
the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

S- DU0313- FIX RELLFILL
The recommended action is to replace the invalid leaf fill factor with the default leaf fill
factor.
Parameters:

None.

Explanation:

The leaf page fill factor must be specified for all table types. If it
is not, then a default value will be used. This is detected by
VERIFY DB test 25, and applies only to btrees. The user will be
prompted to give yes/no permission. If yes is given, VERIFYDB
will take the recommended action. If no is given, VERIFYDB
will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

10-10

DU Class Messages

S- DU0314FIX
-RELIFILL
The recommended action is to replace the invalid index fill factor with the default index
fill factor.
Parameters:

None.

Explanation:

The index page fill factor must be specified for all table types. If
it is not, then a default value will be used. This is detected by
VERIFY DB test 25, and applies only to btrees. The user will be
prompted to give yes/no permission. If yes is given, VERIFYDB
will take the recommended action. If no is given, VERIFYDB
will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

S- DU0315- CREATE- IIRELIDX
The recommended action is to create a tuple in iirel_idx for this table.
Parameters:

None

Explanation:

VERIFY DB test # 26 found a tuple in iirelation that does not
have a corresponding tuple in iirel_idx. The user will be
prompted to give yes/no permission. If yes is given, VERIFYDB
will take the recommended action. If no is given, VERIFYDB
will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

DU Class Messages

10-11

S- DU0316- CLEAR- IIRELIDX
The recommended action is to drop this tuple from system catalog iirel_idx.
Parameters:

None.

Explanation:

VERIFY DB test # 27 found an entry in iirel_idx that does not
have a corresponding entry in iirelation. The user will be
prompted to give yes/no permission. If yes is given, VERIFYDB
will take the recommended action. If no is given, VERIFYDB
will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

S_DU0317_DROP _ATTRIBUTES
The recommended action is to delete tuples with attrelid = %Od, attrelidx = % Id from
iiattributes.
Parameters:

%Oc - attrelid from iiattributes
% 1c - attrelidx from iiattributes

Explanation:

VERIFY DB test #28 found some tuples in iiattributes that have
table id and index table id values that do not match any entries in
iirelation. this means that they are useless, and should be deleted.
The user will be prompted to give yes/no permission. If yes is
given, VERIFYDB will take the recommended action. If no is
given, VERIFYDB will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

This is only an informative message, so processing continues.
However, this type of message requires input from the user. The
S_DU0300_PROMPT message will be displayed following this
message, and processing will simply waJt until some input is
given. If the input is not a valid response, the message will be
repeated until a valid response is given.

Recommendation:

Enter Y(ES) or N(O).

10-12

DU Class Messages

S- DU0318- DROP- INDEX
The recommended action is to delete this tuple (baseid = %Od, indexid = % Id) from
iiindex.
Parameters:

%Od - baseid from iiindex
% 1d - indexid from iiindex

Explanation:

VERIFY DB test #30 found some tuples in iiindex that have table
id and index table id values that do not match any entries in
iirelation. this means that they are useless, and should be deleted.
The user will be prompted to give yes/no permission. If yes is
given, VERIFYDB will take the recommended action. If no is
given, VERIFYDB will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

S- DU0319SET
-INDEX
The recommended action is to modify iirelation to indicate that this is an index table.
Parameters:

None.

Explanation:

VERIFY DB test #31 found that this table is a secondary index
table, but is not marked as such in iirelation. The user will be
prompted to give yes/no permission. If yes is given, VERIFYDB
will take the recommended action. If no is given, VERIFYDB
will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

This is only an informative message, so processing continues.
However, this type of message requires input from the user. The
S_DU0300_PROMPT message will be displayed following this
message, and processing will simply wait until some input is
given.
If the input is not a valid response, the message will be repeated

until a valid response is given.
Recommendation:

Enter Y(ES) or N(O).

DU Class Messages

10-13

S- DU031A- DROP- DEVRELID
The recommended action is to delete tuples with devrelid = %Od, devrelidx = % Id from
iidevices.
Parameters:

%Od - devrelid from iidevices
% Id - devrelidx from iidevices

Explanation:

VERIFYDB test #33 found some tuples in iidevices that have
table id and index table id values that do not match any entries in
iirelation. This means that they are useless, and should be
deleted. The user will be prompted to give yes/no permission. If
yes is given, VERIFYDB will take the recommended action. If
no is given, VERIFYDB will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

S_DU031B_SET_MULTIPLE_LOC
The recommended action is to modify iirelation to indicate that this table has multiple
locations defined.
Parameters:

None.

Explanation:

VERIFYDB test #34 found that iirelation did not have the
MULTIPLE_LOC bit set in relstat, but there are actually
locations defined for this table in iidevices. The user will be
prompted to give yes/no permission. If yes is given, VERIFYDB
will take the recommended action. If no is given, VERIFYDB
will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

10-14

DU Class Messages

S- DU031CDEL
TREE
The recommended action is to delete all tuples with base table id = %Od, index table id =
% Id from iitree.
Parameters:

%Od - base table id associated with tree (from iitree. treetabbase)
% Id - base table index id associated with tree (from
ii tree. treetabidx)

Explanation:

VERIFY DB test #35 found tuples in iitree with invalid table id.
OR
VERIFYDB test #36 found tuples in iitree with an invalid tree
mode.
OR
VERIFY DB test #37 found the tree id was invalid. The user will
be prompted to give yes/no pennission. If yes is given,
VERIFY DB will take the recommended action. If no is given,
VERIFY DB will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).

S- DU031DSET
-VIEW
The recommended action is to set the VIEW bit in iirelation.relstat.
Parameters:

None.

Explanation:

VERIFY DB test #38 found that the VIEW bit should have been
set in iirelation.relstat (for this view) but was not. The user will
be prompted to give yes/no pennission. If yes is given,
VERIFY DB will take the recommended action. If no is given,
VERIFY DB will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

DU Class Messages

10-15

Recommendation:

Enter Y(ES) or N(O).
NOTE: User will usually want to enter yes. The query text for
this view can be retrieved from iiqrytext, and ULTRIX/SQL can
rebuild the view if the query text is rekeyed.

S_ DU031E_SET _PRTUPS
The recommended action is to set the PRTUPS bit in iirelation.relstat.
Parameters:

None.

Explanation:

VERIFY DB test #38 found that the PRTUPS bit should have
been set in iirelation.relstat (for this table) but was not. The user
will be prompted to give yes/no permission. If yes is given,
VERIFY DB will take the recommended action. If no is given,
VERIFYDB will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).
NOTE: User will usually want to enter yes. The query text for
this permit can be retrieved from iiqrytext, and ULTRIX/SQL
can rebuild the permit if the query text is rekeyed.

S- DU031FSET
-INTEGS
The recommended action is to set the INTEGS bit in iirelation.relstat.
Parameters:

None.

Explanation:

VERIFYDB test #38 found that the INTEGS bit should have
been set in iirelation.relstat (for this table) but was not. The user
will be prompted to give yes/no permission. If yes is given,
VERIFY DB will take the recommended action. If no is given,
VERIFYDB will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission. This is only an informative message, so processing
continues. However, this type of message requires input from the
user. The S_DU0300_PROMPT message will be displayed
following this message, and processing will simply wait until
some input is given. If the input is not a valid response, the
message will be repeated until a valid response is given.

10-16

DU Class Messages

Recommendation:

Enter Y(ES) or N(O).
NOTE: User will usually want to enter yes. The query text for
this integrity can be retrieved from iiqrytext, and ULTRIX/SQL
can rebuild the integrity if the query text is rekeyed.

S- DU0320- DROP- FROM- IIINTERGRITY
The recommended action is to drop all tuples from iiintegrity with inttabbase = %Od and
inttabidx = % 1d.
Parameters:

%Od - base table id (from iiintegrity.inttabbase)
% Id - index table id (from iiintegrity.inttabidx)

Explanation:

VERIFY DB test # 40 found that the table that is supposed to
receive this integrity doesn't exist (at least it's not listed in
iirelation.)
OR
VERIFY DB test # 42 found the tree that defines the integrity is
missing from iitree, which means the DBMS cannot enforce the
integrity. The user will be prompted to give yes/no permission. If
yes is given, VERIFY DB will take the recommended action. If
no is given, VERIFYDB will proceed to the next test.
NOTE: this message will also be displayed in REPORT lnode,
but the user will not be given the opportunity to input yes/no
permission. This is only an informative message, so processing
continues. However, this type of message requires input from the
user. The S_DU0300_PROMPT message will be displayed
following this message, and processing will simply wait until
some input is given. If the input is not a valid response, the
message will be repeated until a valid response is given.

Recommendation:

Enter Y(ES) or N(O).

S- DU0321 - DROP- FROM- IIPROTECT
The recommended action is to drop all tuples from iiprotect with protabbase = %Od and
protabidx = % 1d.
Parameters:

%Od - base table id (from iiprotect.protabbase)
% Id - index table id (from iiprotect.protabidx)

Explanation:

VERIFY DB test # 44 found that the table that is supposed to
receive this integrity doesn't exist (at least it's not listed in
iirelation.)
OR
VERIFYDB test # 46 found the tree that defines the permit is
missing from iitree, which means the DBMS cannot enforce the
permit. The user will be prompted to give yes/no permission. If
yes is given, VERIFYDB will take the recommended action. If
no is given, VERIFY DB will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no

DU Class Messages

10-17

permission. This is only an informative message, so processing
continues. However, this type of message requires input from the
user. The S_DU0300_PROMPT message will be displayed
following this message, and processing will simply wait until
some input is given. If the input is not a valid response, the
message will be repeated until a valid response is given.
Recommendation:

Enter Y(ES) or N(O).

S- DU0322- DROP- IIDBDEPENDS- TUPLE
The recommended action is to delete all tuples with inidl = %Od, inid2 = %ld, deidl =
%2d and deid2 = %3d from iidbdepends.
Parameters:

%Od = iidbdepends.inid 1
% Id = iidbdepends.inid2
%2d = iidbdepends.deid 1
%3d = iidbdepends.deid2

Explanation:

VERIFYDB test # 54 found an entry in iidbdepends that
describes a view or table with permit as dependent on another
table. However, the dependent table/view does not exist (or is
not defined in iirelation)
OR
VERIFY DB test # 55 found that the independent table does not
exist, so the dependency described by this entry in iidbdepends is
not valid. The user will be prompted to give yes/no permission.
If yes is given, VERIFYDB will take the recommended action. If
no is given, VERIFY DB will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission. This is only an informative message, so processing
continues. However, this type of message requires input from the
user. The S_DU0300_PROMPT message will be displayed
following this message, and processing will simply wait until
some input is given. If the input is not a valid response, the
message will be repeated until a valid response is given.

Recommendation:

Enter Y(ES) or N(O).

S- DU0323SET
-VBASE
The recommended action is to indicate that a view is defined against this table/view.
Parameters:

None.

Explanation:

VERIFY DB test # 56 found that the independent table does not
indicate that there is a view defined against this table/view. The
recommended solution is to change iirelation.relstat (set
VBASE) for the independent table. The user will be prompted to
give yes/no permission. If yes is given, VERIFY DB will take the
recommended action. If no is given, VERIFYDB will proceed to
the next test.

10-18 DU Class Messages

NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission. This is only an informative message, so processing
continues. However, this type of message requires input from the
user. The S_DU0300_PROMPT message will be displayed
following this message, and processing will simply wait until
some input is given. If the input is not a valid response, the
message will be repeated until a valid response is given.
Recommendation:

Enter Y(ES) or N(O).

S_DU0324_ CREATE_IIXDBDEPENDS
The recommended action is to create a tuple in iixdbdepends for this table.
Parameters:

None

Explanation:

VERIFYDB test # 58 found a tuple in iidbdepends that does not
have a corresponding tuple in iixdbdepends. The user will be
prompted to give yes/no permission. If yes is given, VERIFYDB
will take the recommended action. If no is given, VERIFYDB
will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission. This is only an informative message, so processing
continues. However, this type of message requires input from the
user. The S_DU0300_PROMPT message will be displayed
following this message, and processing will simply wait until
some input is given. If the input is not a valid response, the
message will be repeated until a valid response is given.

Recommendation:

Enter Y(ES) or N(O).

S_ DU0325_REDO _IIXDBDEPENDS
The recommended action is to drop this index table and recreate it.
Parameters:

None

Explanation:

VERIFY DB test # 59 found an entry in iixdbdepends that does
not have a corresponding entry in iidbdepends. The user will be
prompted to give yes/no permission. If yes is given, VERIFYDB
will take the recommended action. If no is given, VERIFYDB
will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission. This is only an informative message, so processing
continues. However, this type of message requires input from the
user. The S_DU0300_PROMPT message will be displayed
following this message, and processing will simply wait until
some input is given. If the input is not a valid response, the
message will be repeated until a valid response is given.

Recommendation:

Enter Y(ES) or N(O).
DU Class Messages

10-19

S_DU0326_DROP _FROM _IISTATISTICS
The recommended action is to drop all tuples from iistatistics with stabbase = %Od and
stabindex = % I d.
Parameters:

%Od - base table id (from iistatistics.stabbase)
% ld - index table id (from iistatistics.stabindex)

Explanation:

VERIFY DB test # 60 found that the table that is supposed to
receive these statistics doesn't exist (at least it's not listed in
iirelation.)
OR
VERIFY DB test #61 found that the column number receiving the
statistics was invalid.ORVERIFYDB test #65 found the statistics
were performed on an index table.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.This is only an informative message, so processing
continues. However, this type of message requires input from the
user. The S_DU0300_PROMPT message will be displayed
following this message, and processing will simply wait until
some input is given. If the input is not a valid response, the
message will be repeated until a valid response is given.

Recommendation:

Enter Y(ES) or N(O).

S- DU0327SET
OPSTAT
The recommended action is to indicate that there are optimizer statistics for this tale/view.
Parameters:

None.

Explanation:

VERIFY DB test # 62 found that the iirelation entry for this table
does not indicate there are optimizer statistics defined for this
table. The recommended solution is to change iirelation.relstat
(set OPSTST). The user will be prompted to give yes/no
permission. If yes is given, VERIFYDB will take the
recommended action. If no is given, VERIFY DB will proceed to
the next test.
NOTE: thhis message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission. This is only an informative message, so processing
continues. However, this type of message requires input from the
user. The S_DU0300_PROMPT message will be displayed
following this message, and processing will simply wait until
some input is given. If the input is not a valid response, the
message will be repeated until a valid response is given.

Recommendation:

10-20

DU Class Messages

Enter Y(ES) or N(O).

S_ DU0328_FIX _SNUMCELLS
The recommended action is to correct snumcells (in iistatistics) from %Od to % Id for
table %2c (owner %3c) attribute# %4d
Parameters:

%Od - current value of snumcells
% 1d - actual count of cells in iihistogram
%2c - name of table statistics are for
%3c - owner of that table
%4d - attribute number that histogram is on.

Explanation:

VERIFY DB test # 64 found a mismatch between iistatistics and
iihistogram in the number of cells in the histogram. If the real
count is zero, then the whole histogram is missing. The user will
be prompted to give yes/no permission. If yes is given,
VERIFY DB will take the recommended action. If no is given,
VERIFYDB will proceed to the next test.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission. This is only an informative message, so processing
continues. However, this type of message requires input from the
user. The S_DU0300_PROMPT message will be displayed
following this message, and processing will simply wait until
some input is given. If the input is not a valid response, the
message will be repeated until a valid response is given.

Recommendation:

Enter Y(ES) or N(O).

S_ DU0329 _DROP _FROM _IIHISTOG RAM
The recommended action is to drop all tuples from iihistogram with htabbase = %Od and
htabindex = %ld for attribute # %2d.
Parameters:

%Od - base table id (from iihistogram.htabbase)
% Id - index table id (from iihistogram.htabindex)
%2d - attribute number (from iihistogram.hatno)

Explanation:

VERIFY DB test # 65 found that the statistics associated with
this histogram doesn't exist
OR
VERIFY DB test #66 found some of the tuples that comprise the
histogram are missing from iihistogram.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission. This is only an informative message, so processing
continues. However, this type of message requires input from the
user. The S_DU0300_PROMPT message will be displayed
following this message, and processing will simply wait until
some input is given. If the input is not a valid response, the
message will be repeated until a valid response is given.

Recommendation:

Enter Y(ES) or N(O).

DU Class Messages

10-21

S_ DU032A_SET_ RELSPEC _TO_HASH
The recommended action is to set the default storage structure for table %Oc to HASH.
Parameters:

%Oc - Name of DBMS system catalog

Explanation:

VERIFY DB test # 4 found a DBMS catalog with an invalid
relspec, and the relspec for that table should be TCB _HASH.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission. This is only an informative message, processing
continues. However, this type of message requires input from the
user. The S_DU0300_PROMPT message will be displayed
following this message, and processing will simply wait until
some input is given. If the input is not a valid response, the
message will be repeated until a valid response is given.Enter
Y(ES) or N(O).

S_DU032B_SET_RELSPEC_TO_BTREE
The recommended action is to set the default storage structure for table %Oc to BTREE.
Parameters:

%Oc - Name of DBMS system catalog

Explanation:

VERIFYDB test # 4 found a DBMS catalog with an invalid
relspec, and the relspec for that table should be TCB_BTREE.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.This is only an informative message, processing
continues. However, this type of message requires input from the
user. The S_DU0300_PROMPT message will be displayed
following this message, and processing will simply wait until
some input is given. If the input is not a valid response, the
message will be repeated until a valid response is given.

Recommendation:

Enter Y(ES) or N(O).

S_ DU032C _EMPTY _IIHISTOGRAM
The recommended action is to empty the iihistogram table by deleting all tuples from it.
Parameters:

None

Explanation:

VERIFYDB found tuples in iihistogram but iistatistics is empty.
The iihistogram tuples are used in conjunction with the
iistatistics tuples, so these tuples are meaningless and should be
dropped.This is only an informative message, processing
continues. However, this type of message requires input from the
user. The S_DU0300_PROMPT message will be displayed
following this message, and processing will simply wait until
some input is given. If the input is not a valid response, the
message will be repeated until a valid response is given.

10-22

DU Class Messages

System Status:

VERIFYDB skips the checks for each tuple in iihistogram, since
the iistatistics cache was not built.

Recommendation:

Enter Y(ES) or N(O).

S- DU032D- DROP- TABLE
The recommended action is to drop table %Oc (owner % Ie) from
database %2c.
Parameters:

%Oc - name of table
% Ie - owner of table
%2c - name of database that table is in.

Explanation:

VERIFY DB 's drop_table action will prompt the user for
permission to drop the table if running in INTERACTIVE mode.
Otherwise it will just go ahead with the drop (after all, that is
what the user told you to do. -- Its nonsense to evoke the feature
in report mode, but if so, VERIFYDB will log that the table
should be dropped and exit without dropping it.

System Status:

VERIFYDB will continue processing.

Recommendation:

If prompted, user must enter Yes/No permission to drop this

table. Otherwise, no action is required.
S- DU032E- DROP- USER
The recommended action is to drop user' %Oc' .
Parameters:

%Oc - name of user

Explanation:

Verifydb will drop the tuple from the iiuser table. This will
effectively drop the user from the installation (and make any DB
objects that user owns orphans. However, the user name has been
corrupted anyhow, so the objects will be orphans anyhow.)

System Status:

VERIFY DB will continue processing.

Recommendation:

If prompted, user must enter Yes/No permission to drop this

table. Otherwise, no action is required. It might be a good idea
for the user to answer NO to all subsequent VERIFY DB
prompts, go in via ACCESSDB and assure that all users are
defined (if not define them), then run VERIFYDB.
S- DU032F- CLEAR- BAD BITS
The recommended action is to remove invalid privileges for user' %Oc'.
Parameters:

%Oc - name of user

Explanation:

iiuser.status is a bitmap of user privileges. Some of the bits set in
the bitmap are invalid. Verifydb wants to zero the invalid bits.

System Status:

VERIFYDB will continue processing.

Recommendation:

If prompted, user must enter Yes/No permission to drop this

table. Otherwise, no action is required.There is a good chance
that the user's permissions may not be rightif there were invalid
DU Class Messages

10-23

bits in the permission bitmap. SYSTEM Administrator should
run ACCESSDB to assure that user has correct permissions.

S- DU0330- DROP- IIDATABASE- TUPLE
The recommended action is to drop the tuple from iidatabase (which effectively removes
the database from the installation.) If you permit this drop, run
finddbs -r to attempt to recover the database.
Parameters:

None.

Explanation:

VERIFYDB test #69 found a tuple with an invalid database
name specifier. The recommended corrective action to make the
database database catalogs consistent is to drop information
about this database from the installation by removing it from the
iidatabase catalog. The user will be prompted to give yes/no
permission. If yes is given, VERIFYDB will take recommended
action. If no is given, VERIFY DB will proceed on to next text.
NOTE: this message will also be displayed in REPORT mode,
but the user will not be given the opportunity to input yes/no
permission.

System Status:

Recommendation:

Enter Y(ES) or N(O).If user enters Y, that user should run
finddbs to attempt to recover the database.

S- DU0331- CREATE- IIEXTEND - ENTRY
The recommended action is to put a tuple in iiextend for database %Oc at location % I c.
Parameters:

%Oc - name of database (from iidatabase.name)
% lc - database default data location (from iidatabase.dbdev)

Explanation:

VERIFYDB test #72 found no iiextend entry for this database.
All databases should have atleast one entry in iiextend for their
default data location. Additionally, databases extended via
accessdb will have an entry for each extended location, but we
cannot test for that here.Verifydb will build a iiextend tuple,
since it has all of the information that it needs.

System Status:

This is only an informative message, processing continues.

Recommendation:

None, unless in RUNINTERACTIVE mode, then must give
Yes/No answer to the VERIFY DB prompt.

10-24

DU Class Messages

S- DU0332- CREATE- DBACCESS - ENTRY
The recommended action is to put a tuple in iidbaccess for dba % I c to access database
%Oc.
Parameters:

%Oc - name of database (from iidatabase.name)
% Ic - name of database's owner (from iidatabase.own)

Explanation:

VERIFY DB test #76 found no iidbaccess entry for the DBA of
this private database. It is possible that this database should
really be marked public and iidatabase.access is corrupted.
However, it is also possible that this database is really a private
DB, and somehow the dba no longer has access to it. This fix
will force the DB to be private, and will give access to the DBA.

System Status:

This is only an informative message, processing continues.

Recommendation:

None, unless in RUNINTERACTIVE mode, then must give
Yes/No answer to the VERIFY DB prompt.

S- DU0333 - MARKDB
-OPERATIVE
The recommended action is to mark the database as operative.
Parameters:

None.

Explanation:

VERIFY DB test #77 found that the DB was not marked
operative, but there was no reason that the db should not be
marked as such. However, VERIFY DB will not take this
corrective action unless it is in RUNINTERACTIVE mode.

System Status:

This is only an informative message, processing continues.

Recommendation:

User must give Yes/No answer to the VERIFYDB prompt.

S- DU0334- UPDATE- IIDBID - IDX
The recommended action is to make an entry in secondary index iidbid_idx with db_id =
%Od and tidp = % Id.
Parameters:

%Od - database id (from iidatabase.db_id)
%ld - tid

Explanation:

VERIFY DB test #82 found that the secondary index tuple for
this database was missing or incorrect.

System Status:

This is only an informative message, processing continues.

Recommendation:

If in RUNINTERACTIVE mode, user must give Yes/No answer

to the VERIFYDB prompt. Otherwise no action is required.

S- DU0335- DROP- IIDBIDIDX
The recommended action is to remove the tuple from secondary index iidbid_idx.
Parameters:

None.

Explanation:

VERIFY DB test #83 found a secondary index tuple with no
corresponding tuple in the base table.

DU Class Messages

10-25

System Status:

This is only an informative message, processing continues.

Recommendation:

If in RUNINTERACTIVE mode, user must give Yes/No answer

to the VERIFYDB prompt. Otherwise no action is required.
S- DU0336- UPDATE- IIDBIDIDX
The recommended action is to upate iidbid_idx.tidp to %Od.
Parameters:

%Od - tid pointer value

Explanation:

VERIFYDB test #84 found a secondary index tuple with with the
wrong tid pointer value. The tid pointer should be updated to the
correct value.

System Status:

This is only an informative message, processing continues.

Recommendation:

None, unless in RUNINTERACTIVE mode, then give Yes/No
permission.

S- DU0337- DROP- DBACCESS
The recommended action is to remove access to private database '%Ic' for user '%Oc'.
Parameters:

%Oc - name of User with access to this db (from
iidbaccess. usmame)
% Ic - name of private database (from iidbaccess.dbname)

Explanation:

VERIFYDB test #85 or #86 found a an invalid entry in
iidbaccess. This entry is being removed from the catalog.

System Status:

This is only an informative message, processing continues.

Recommendation:

None, unless in RUNINTERACTIVE mode, then give Yes/No
permission.

S- DU0338- MARKDB
-PRIVATE
The recommended action is to mark database '%Oc' as a private database.
Parameters:

%Oc - name of private database (from iidbaccess.dbname)

Explanation:

VERIFYDB test 87 found a private database that was marked as
a global database. Verifydb knows it is a private database
because there is a valid entry in table iidbaccess giving the DBA
access to the database.

System Status:

This is only an informative message, processing continues.

Recommendation:

None, unless in RUNINTERACTIVE mode, then give Yes/No
permission.

S- DU0339- DROP- LOCATION
The recommended action is to drop location with area = '%Oc'
from the iilocations catalog.
Parameters:

%Oc -location physical name (from iilocations.area)

Explanation:

VERIFY DB test 88 found an invalid location logical name.

10-26

DU Class Messages

(See description on message S_DUI66B_INVALID_LOCNAME
for a full explanation.)
System Status:

This is only an informative message, processing continues.

Recommendation:

If in RUNINTERACTIVE mode, then give Yes/No permission.

After the corrective action is taken, user should use ACCESSDB
to redefine the location.
NOTE: user must use same logical/physical names that the
location was previously defined at, as the location information is
in the config file. If the user does not know how the location
should be defined, do an ASCII dump on the config file to find
out. The config file resides in the database's default data location
and is file aaaaaaaa.cnf.

S- DU033A- FIX- LOC - STAT
The recommended action is to clear invalid bits in location status.
Parameters:

None.

Explanation:

VERIFYDB test 89 found an invalid bits in location status (used
to define what the location may be used for).

System Status:

This is only an informative message, processing continues.

Recommendation:

If in RUNINTERACTIVE mode, user must answer prompt with

Yes/No. After the corrective action is taken, user should use
ACCESSDB to assure that the location is defined for the correct
uses.

S- DU033B- DROP- IIEXTEND
The recommended action is to drop this tuple from iiextend.
Parameters:

None.

Explanation:

VERIFY DB test 90,91 found an iiextend tuple.

System Status:

This is only an informative message, processing continues.

Recommendation:

If in RUNINTERACTIVE mode, user must answer prompt with

Yes/No. After the corrective action is taken, user should use
ACCESSDB to assure that the database is correctly defined.

S- DU0351 - DROP- IIRELATION- TUPLE
VERIFY DB dropped this tuple from iirelation (which effectively drops table %Oc (owner
% 1c) from the database)
Parameters:

%Oc -- name of table (from iirelation.relid)
% lc -- name of table's owner (from iirelation.relowner)

Explanation:

VERIFY DB test #1 found a tuple with an invalid table
specifier. Since the table specifier is used to join iirelation tuples
to tuples in other system catalogs, this tuple is useless.

DU Class Messages

10-27

System Status:

This is only an informative message, processing continues.

Recommendation:

None.

S- DU0352- DROP- TABLE
table %Oc (owner % Ic) dropped from the database.
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- name of table's owner (from iirelation.relowner)

Explanation:

System Status:

This is only an informative message, processing continues.

Recommendation:

None.

S- DU0353- REPLACE - RELWID
the value in iirelation of (%Od) replaced with (% Id)
Parameters:

%Od -- table's width from iirelation (iirelation.rel wid)
% Id -- sum of width of each attribute (from each
iiattribute.attfrml)

Explanation:

VERIFY DB test #2b found a mismatch in table width between
iirelation and the sum of each column's width.

System Status:

This is only an informative message, processing continues.

Recommendation:

None.

S_ DU0354_ REPLACE _ RELKEYS
value in iirelation of (%Od) replaced with (%Id)
Parameters:

%Od -- # keys iirelation thinks there are (iirelation.relkeys)
% Id -- count of each key in iiattribute.

Explanation:

VERIFYDB test 3 found a mismatch between the number of
keys that should be in the table's primary key and the number
that are actually in the key.

System Status:

This is only an informative message, processing continues.

Recommendation:

None.

S- DU03SS- CLEAR- PRTUPS
protection information cleared from iirelation.
Parameters:

None.

Explanation:

VERIFY DB test #8 found that iirelation specified there are
protections on this table, but none are defined in iiprotect.

10-28

DU Class Messages

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S_DU0356_CLEAR_INTEGS
integrity information cleared from iirelation.
Parameters:

None.

Explanation:

VERIFY DB test #9 found that iirelation specified there are
integrities on this table, but none are defined in iiintegrity.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S_DU0357_CLEAR_CONCUR
CONCUR locking specification cleared from iirelation.
Parameters:

None.

Explanation:

VERIFYDB test #10 found that the CONCUR bit was set for a
table that was not a DBMS core system catalog.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU0358SET
-CONCUR
CONCUR locking specification set in iirelation.
Parameters:

None.

Explanation:

VERIFY DB test #11 found that one of the DBMS core system
catalogs did not have the special locking (CONCUR) bit set in
iirelation.relstat.The user will be prompted to give yes/no
permission.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU0359- MAKE- TABLE
iirelation altered to indicate that this is a table, not a view
Parameters:

None.

Explanation:

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

DU Class Messages

10-29

S_ DU03SA_ CLEAR_CATALOG
iirelation altered to stop indicating that this table is a system catalog.
Parameters:

None.

Explanation:

VERIFYDB test # 5a found that a table was mismarked as a
system catalog when it did not start with "ii" or when the owner
was not $ingres.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU03SB - DROP- VIEW
view %Oc (owner %1c) dropped from the database.
Parameters:

%Oc - name of view [null terminated string]
% lc - name of view's owner [null terminated string]

Explanation:

VERIFY DB test #12 found that the specified view was not
defined in iitree.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU03SC- CLEAR- VBASE
view base specification cleared from iirelation.
Parameters:

None.

Explanation:

VERIFY DB test #15 found that iirelation believed there was a
view based on this table, but none could be found in iidbdepends.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU03SDSET
IDXD
iirelation.relstat INDEXED bit set for base table %Oc (owner % Ic)
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- name of tables owner (from iirelation.relowner)

Explanation:

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

10-30

DU Class Messages

S- DU0360- CLEAR- OPTSTAT
iirelation modified to stop indicating that there are optimizer statistics
for this table.
Parameters:

None.

Explanation:

VERIFYDB test # 19 found that iirelation thinks there are
optimizer statistics for this table, but there aren't any.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU0361 - RESET- RELLOCOUNT
number of locations in iirelation modified from %Od to %Id.
Parameters:

%Od -- number of locations iirelation thinks there are (from
iirelation.relloccount)
% 1d -- number of locations defined in iidevices.

Explanation:

VERIFY DB test #20 found a discrepancy between the number of
locations that iirelation thinks there are and the number of
locations defined in iidevices.

System Status:

VERIFY DB keeps running.

Recommendation:

Nnone.

S- DU0362FIX
-RELDFILL
invalid data fill factor replaced with the default data fill factor.
Parameters:

None.

Explanation:

The data page fill factor must be specified for all table types. If it
is not, then a default value will be used. This is detected by
VERIFYDB tests 22 through 25.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU0363FIX
-RELLFILL
invalid leaf fill factor replaced with the default leaf fill factor.
Parameters:

None.

Explanation:

The leaf page fill factor must be specified for all table types. If it
is not, then a default value will be used. This is detected by
VERIFY DB test 25, and applies only to btrees.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

DU Class Messages

10-31

S- DU0364FIX
-RELIFILL
invalid index fill factor replaced with the default index fill factor.
Parameters:

None.

Explanation:

The index page fill factor must be specified for all table types. If
it is not, then a default value will be used. This is detected by
VERIFY DB test 25, and applies only to btrees.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU0365- CREATE- IIRELIDX
iirel_idx tuple created.
Parameters:

None

Explanation:

VERIFY DB test # 26 found a tuple in iirelation that does not
have a corresponding tuple in iirel_idx.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU0366- CLEAR- IIRELIDX
tuple dropped from system catalog iirel_idx.
Parameters:

None

Explanation:

VERIFY DB test # 27 found an entry in iirel_idx that does not
have a corresponding entry in iirelation.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU0367- DROP- ATTRIBUTES
tuples with attrelid = %Od, attrelidx = % ld deleted from iiattributes.
Parameters:

%Oc - attrelid from iiattributes
% lc - attrelidx from iiattributes

Explanation:

VERIFYDB test #28 found some tuples in iiattributes that have
table id and index table id values that do not match any entries in
iirelation. this means that they are useless, and should be deleted.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU0368- DROP- INDEX
this tuple (with baseid = %Od, indexid = % ld) deleted from iiindex.
Parameters:

10-32

DU Class Messages

%Od - baseid from iiindex
% ld - indexid from iiindex

Explanation:

VERIFY DB test #30 found some tuples in iiindex that have table
id and index table id values that do not match any entries in
iirelation. this means that they are useless, and should be deleted.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU0369SET
-INDEX
iirelation modified to indicate that this is an index table.
Parameters:

None.

Explanation:

VERIFYDB test #31 found that this table is a secondary index
table, but is not marked as such in iirelation.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU036A- DROP- INDEX
tuples with devrelid = %Od, devrelidx = % Id deleted from iidevices.
Parameters:

%Od - devrelid from iidevices
% 1d - devrelidx from iidevices

Explanation:

VERIFY DB test #33 found some tuples in iidevices that have
table id and index table id values that do not match any entries in
iirelation. this means that they are useless, and should be deleted.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU036B - SET- MULTIPLE- LOC
iirelation modified to indicate that this table has multiple locations defined.
Parameters:

None.

Explanation:

VERIFY DB test #34 found that iirelation did not have the
MULTIPLE_LOC bit set in relstat, but there are actually
locations defined for this table in iidevices.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU036CDEL
-TREE
tuples with base table id = %Od, index table id = % 1d deleted from iitree.
Parameters:

%Od - base table id associated with tree (from iitree.treetabbase)
% 1d - base table index id associated with tree (from
ii tree. treetabidx)

Explanation:

VERIFY DB test #35 found tuples in iitree with an invalid tree
mode.

DU Class Messages

10-33

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU036DSET
-VIEW
iirelation.relstat VIEW bit flag set.
Parameters:

None.

Explanation:

VERIFYDB test #38 found that the VIEW bit should have been
set in iirelation.relstat (for this view) but was not.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU036ESET
-PRTUPS
iirelation.relstat PRTUPS bit flag set.
Parameters:

None.

Explanation:

VERIFY DB test #38 found that the PRTUPS bit should have
been set in iirelation.relstat (for this table)'but was not.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU036FSET
-INTEGS
iirelation.relstat INTEGS bit flag set.
Parameters:

None.

Explanation:

VERIFY DB test #38 found that the INTEGS bit should have
been set in iirelation.relstat (for this table) but was not.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S_ DU0370_DROP_FROM _IIINTERGRITY
tuples with inttabbase = %Od and inttabidx = % Id dropped from iiintegrity
Parameters:

%Od - base table id (fromiiintegrity.inttabbase)
% Id - index table id (from iiintegrity.inttabidx)

Explanation:

VERIFYDB test # 40 found that the table that is supposed to
receive this integrity doesn't exist (at least it's not listed in
iirelation.) VERIFYDB test # 42 found the tree that defines the
integrity is missing from iitree, which means the DBMS cannot
enforce the integrity.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

10-34

DU Class Messages

S- DU0371 - DROP- FROM- IIPROTECT
tuples with protabbase = %Od and protabidx = % Id dropped from iiprotect
Parameters:

%Od - base table id (from iiprotect.protabbase)
% Id - index table id (from iiprotect.protabidx)

Explanation:

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU0372- DROP- IIDBDEPENDS - TUPLE
tuples with inidl = %Od, inid2 = %ld, deidl = %2d and deid2 = %3d deleted from
iidbdepends.
Parameters:

%Od = iidbdepends.inid 1
% Id = iidbdepends.inid2
%2d = iidbdepends.deid 1
%3d = iidbdepends.deid2

Explanation:

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU0373SET
-VBASE
iirelation modified to indicate that a view is defined against this table/view.
Parameters:

None.

Explanation:

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

DU Class Messages

10-35

S_DU0374_CREATE_IIXDBDEPENDS
iixdbdepends tuple created.
Parameters:

None

Explanation:

VERIFY DB test # 58 found a tuple in iidbdepends that does not
have a corresponding tuple in iixdbdepends.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S_ DU0375_REDO _IIXDBDEPENDS
iixdbdepends dropped and recreated.
Parameters:

None

Explanation:

VERIFY DB test # 59 found an entry in iixdbdepends that does
not have a corresponding entry in iidbdepends.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S_ DU0376_DROP _FROM _IISTATISTICS
tuples with stabbase = %Od, stabindex = % Id dropped from iistatistics
Parameters:

%Od - base table id (from iistatistics.stabbase)
% Id - index table id (from iistatistics.stabindex)

Explanation:

VERIFYDB test # 60 found that the table that is supposed to
receive these statistics doesn't exist (at least it's not listed in
iirelation.)
OR
VERIFYDB test #63 found that the column number receiving the
statistics was invalid.ORVERIFYDB test #61 found the statistics
were performed on an index table.

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU0377SET
-OPTSTAT
iirelation.relstat modified to indicate that there are optimizer statistics for this table/view.
Parameters:

None.

Explanation:

System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

10-36

DU Class Messages

S- DU0378FIX
-SNUMCELLS
snumcells (in iistatistics) corrected from %Od to % Id for table %2c (owner %3c)
attribute# %4d
Parameters:

%Od - current value of snumcells
% Id - actual count of cells in iihistogram
%2c - name of table statistics are for
%3c - owner of that table
%4d - attribute number that histogram is on.

Explanation:

VERIFY DB test # 64 found a mismatch in the number of tuples
in the histogram for this attribute.

System Status:

This is only an informative message, so processing continues.

Recommendation:

none.

S- DU0379- DROP- FROM- IIHISTOGRAM
tuples with htabbase = %Od, htabindex = % Id dropped from iihistogram for attribute #
%2d.
Parameters:

%Od - base table id (from iihistogram.htabbase)
% Id - index table id (from iihistogram.htabindex)
%2d - attribute number (from iihistogram.hatno)

Explanation:

VERIFY DB test # 65 found that the statistics associated with
this histogram doesn't exist

OR
VERIFYDB test #66 found some of the tuples that comprise the
histogram are missing from iihistogram.
System Status:

This is only an informative message, so processing continues.

Recommendation:

None.

S- DU037 A- SET- RELSPECTO
-HASH
The default storage structure for table %Oc set to HASH.
Parameters:

%Oc - Name of DBMS system catalog

Explanation:

VERIFY DB test # 4 found a DBMS catalog with an invalid
relspec, and the relspec for that table should be TCB _HASH.

System Status:

This is only an informative message,. so processing continues.

Recommendation:

None.

S- DU037B- SET- RELSPECTO
BTREE
The the default storage structure for table %Oc set to BTREE.
Parameters:

%Oc - Name of DBMS system catalog

Explanation:

VERIFY DB test # 4 found a DBMS catalog with an invalid
relspec, and the relspec for that table should be TCB _BTREE.

DU Class Messages

10-37

System Status:

This is only an infonnative message, so processing continues.

Recommendation:

None.

S- DU037C- EMPTY- IIHISTOGRAM
All tuples cleared from iihistogram.
Parameters:

None

Explanation:

VERIFY DB found tuples in iihistogram but iistatistics is empty.
The iihistogram tuples are used in conjunction with the
iistatistics tuples, so these tuples are meaningless and should be
dropped.

System Status:

This is only an infonnative message, so processing continues.

Recommendation:

None.

S- DU037D- DROP- TABLE
Table %Oc (owner %Ic)'n dropped from database %2c.
Parameters:

%Oc - name of table
% Ic - owner of table
%2c - name of database that table is in.

Explanation:

VERIFYDB's drop_table action will prompt the user for
pennission to drop the table if running in INTERACTIVE mode.
Otherwise it will just go ahead with the drop (after all, that is
what the user told you to do. -- Its nonsense to evoke the feature
in report mode, but if so, VERIFYDB will log that the table
should be dropped and exit without dropping it.

System Status:

VERIFYDB will continue processing.

Recommendation:

If prompted, user must enter Yes/No pennission to drop this

table. Otherwise, no action is required.

S- DU037E- DROP- USER
User '%Oc' dropped from installation.
Parameters:

%Oc - name of user

Explanation:

Verifydb deleted the tuple from the iiuser table. This effectively
dropped the user from the installation (and make any DB objects
that user owns orphans. However, the user name has been
corrupted anyhow, so the objects will be orphans anyhow.)

System Status:

VERIFY DB will continue processing.

Recommendation:

If user sees this message, they should use accessdb to add

anyone back who was dropped and should not have been.

10-38

DU Class Messages

S- DU037F- CLEAR- BAD BITS
invalid privileges for user '%Oc' were removed.
Parameters:

%Oc - name of user

Explanation:

iiuser.status is a bitmap of user privileges. Some of the bits set in
the bitmap are invalid. Verifydb zeroed the invalid bits.

System Status:

VERIFYDB will continue processing.

Recommendation:

There is a good chance that the user's permissions may not be
right if there were invalid bits in the permission bitmap.
SYSTEM Administrator should run ACCESSDB to assure that
user has correct permissions.

S- DU0380- DROP- IIDATABASE- TUPLE
The tuple has been dropped from iidatabase (which effectively removeed the database
from the installation.)
Parameters:

None.

Explanation:

VERIFYDB test #69 found a tuple with an invalid database
name specifier. VERIFYDB removed the tuple from the
iidatabase table.

System Status:

This is only an informative message, processing continues.

Recommendation:

the user should run finddbs to attempt to recover the database.

S- DU0381 - CREATE- IIEXTEND - ENTRY
iiextend tuple build with dname = %Oc, lname= % 1c.
Parameters:

%Oc - name of database (from iidatabase.name)
% 1c - default data location (from iidatabase.dbdev)

Explanation:

VERIFY DB test #72 found no iiextend entry for this database.
All databases should have atleast one entry in iiextend for their
default data location. Additionally, databases extended via
accessdb will have an entry for each extended location, but we
cannot test for that here. Verifydb will build a iiextend tuple,
since it has all of the information that it needs.

System Status:

This is only an informative message, processing continues.

Recommendation:

None.

S_DU0382_CREATE_DBACCESS_ENTRY
DBA %Oc now has access to private database % 1c.
Parameters:

%Oc - name of database's owner (from iidatabase.own)
% 1c - name of database (from iidatabase.name)

Explanation:

10-39

DB, and somehow the dba no longer has access to it. Verifydb
has now forced the DB to be private, and has given access to the
DBA.
System Status:

This is only an informative message, processing continues.

Recommendation:

User may wish to use ACCESSDB to give other ULTRIX/SQL
users access to this database.

S- DU0383- MARKDB
-OPERATIVE
The database was marked as operative.
Parameters:

None.

Explanation:

VERIFYDB test #77 found that the DB was not marked
operative, but there was no reason that the db should not be
marked as such. So VERIFYDB marked the database operative.

System Status:

This is only an informative message, processing continues.

Recommendation:

None.

S- DU0384- UPDATE- IIDBID - IDX
secondary index iidbid_idx entry created with db_id = %Od and tidp = %ld.
Parameters:

%Od - database id (from iidatabase.db_id)
%ld - tid

Explanation:

VERIFY DB test #82 found that the secondary index tuple for
this database was missing or incorrect. The fix is to update
iidatabase's secondary index table by placing a valid entry for
this database in it.

System Status:

This is only an informative message, processing continues.

Recommendation:

If in RUNINTERACTIVE mode, user must give Yes/No answer

to the VERIFY DB prompt. Otherwise no action is required.

S- DU0385- DROP- IIDBIDIDX
Tuple dropped from secondary index iidbid_idx.
Parameters:

None.

Explanation:

VERIFY DB test #83 found a secondary index tuple with no
corresponding tuple in the base table.

System Status:

This is only an informative message, processing continues.

Recommendation:

None.

10-40

DU Class Messages

S- DU0386- UPDATE- IIDBIDIDX
iidbid_idx.tidp updated to %Od.
Parameters:

%Od - tid pointer value

Explanation:

VERIFY DB test #84 found a secondary index tuple with with the
wrong tid pointer value. The tid pointer has been updated to the
correct value.

System Status:

This is only an informative message, processing continues.

Recommendation:

None.

S- DU0387- DROP- DBACCESS
Access to private database '%Ic' for user '%Oc' is removed.
Parameters:

%Oc - name of User with access to this db (from
iidbaccess. usmame)
% Ic - name of private database (from iidbaccess.dbname)

Explanation:

VERIFY DB test #85 or #86 found a an invalid entry in
iidbaccess. This entry is being removed from the catalog.

System Status:

This is only an informative message, processing continues.

Recommendation:

None.

S- DU0388- MARKDB
-PRIVATE
Private database' %Oc' now marked as a private database.
Parameters:

%Oc - name of private database (from iidbaccess.dbname)

Explanation:

VERIFY DB test 87 found a private database that was marked as
a global database. Verifydb knows it is a private database
because there is a valid entry in table iidbaccess giving the DBA
access to the database.

System Status:

This is only an informative message, processing continues.

Recommendation:

None.

S- DU0389- DROP- LOCATION
location dropped from the iilocations catalog. Use ACCESSDB to redefine the location
for area = '%Oc'.
Parameters:

%Oc - location physical name (from iilocations.area)

Explanation:

VERIFY DB test 88 found an invalid location logical name.
(See description on message S_DUI66B_INVALID_LOCNAME
for a full explanation.)

System Status:

This is only an informative message, processing continues.

Recommendation:

After the corrective action is taken, user should use ACCESSDB
to redefine the location. NOTE: user must use same
logical/physical names that the location was previously defined
DU Class Messages

10-41

at, as the location information is in the config file. If the user
does not know how the location should be defined, do an ASCII
dump on the config file to find out.
The config file resides in the database's default data location and
is file aaaaaaaa.cnf.

S- DU038A- FIX- LOC - STAT
Invalid bits cleared from location status word.
Parameters:

None.

Explanation:

VERIFYDB test 89 found an invalid bits in location status (used
to define what the location may be used for).

System Status:

This is only an informative message, processing continues.

Recommendation:

After the corrective action is taken, user should use ACCESSDB
to assure that the location is defined for the correct uses.

S- DU038B - DROP- IIEXTEND
The tuple is removed from iiextend.
Parameters:

None.

Explanation:

VERIFY DB test 90,91 found an iiextend tuple.

System Status:

This is only an informative message, processing continues.

Recommendation:

After the corrective action is taken, user should use ACCESSDB
to assure that the database is correctly defined.

S- DU0400- DEL- TEMP - FILE
The recommended action is to delete,temporary file %Oc from location % 1c
Parameters:

%Oc - name of temporary file;
% 1c - location temporary file resides in.

Explanation:

VERIFY DB 's purge operation found a temporary or
non-ULTRIX/SQL file in an ULTRIX/SQL database directory.

System Status:

This is only an informative message, processing continues.
However, this type of message may require input from the user.
The S_DU0300_PROMPT message will be displayed following
this message, and processing will simply wait until some input is
given. If the input is not a valid response, the message will be
repeated until a valid response is given.

Recommendation:

In RUNINTERACTIVE mode, user must answer prompt Y/N. If
user does not wish to delete this file, s/he should move it to some
location other than an ULTRIX/SQL database directory.

10-42

DU Class Messages

S- DU0401 - DROP- EXPIRED - RELATION
The recommended action is to destroy expired table %Oc (owner % Ic).
Parameters:

%Oc - name of expired table
% I c - owner of expired table

Explanation:

VERIFY DB 's purge operation found an expired relation in the
database.

System Status:

Recommendation:

In RUNINTERACTIVE mode, user must answer prompt YIN. If
user does not wish to destroy this table, they should change the
expiration date in iirelation.relsave. If they set it to zero, then the
relation becomes perminate, or cannot expire.

S- DU0410- DEL- TEMP - FILE
Temporary file %Oc deleted from location % 1c.
Parameters:

%Oc - name of temporary file;
% 1c - location temporary file resides in.

Explanation:

VERIFYDB's purge operation found a temporary or
non-ULTRIX/SQL file in an ULTRIX/SQL database directory
and deleted it.

System Status:

This is only an informative message, processing continues.

Recommendation:

none.

S- DU0411 - DROP- EXPIRED - RELATION
Expired table %Oc owner % 1c) is destroyed.
Parameters:

%Oc - name of expired table
% lc - owner of expired table

Explanation:

VERIFY DB 's purge operation found an expired relation in the
database and destroyed it.

System Status:

This is only an informative message, processing continues.

Recommendation:

None.

S- DU04AO- SHOW- MODE
VERIFYDB SELECTED MODE IS %Od
Parameters:

Decimal integer: value corresponding to keyword supplied with
-m flag 1 = RUN, 2 = RUNSILENT, 3 = RUNINTERACTIVE, 4
= REPORT, -1 = INVALID, -2 = NOTSPECIFIED

DU Class Messages

10-43

Explanation:

DEBUG info: shows what mode VERIFYDB was evoked with

System Status:

For development only

Recommendation:

None

S- DU04Al - SHOW- SCOPE
VERIFY DB SELECTED SCOPE IS %Od
Parameters:

Decimal Integer: value corresponding to keyword supplied with
-s flag 1 = SPECIFIED_DB, 2 =DBA, 3 = INSTALLATION,-l
= INVALID, -2 = NOTSPECIFIED

Explanation:

DEBUG info: shows what mode VERIFYDB was evoked with

System Status:

For development only

Recommendation:

None

S- DU04A2- SHOW- SCOPE- NAME
VERIFY DB SPECIFIED DATABASE: %Oc
Parameters:

Null Terminated String containing 1st database name specified
with -sdbname flag.

Explanation:

DEBUG info: Name of user specified database

System Status:

For development only

Recommendation:

None

S- DU04A3- SHOW- OPERATION
VERIFY DB SELECTED OPERATION IS %Od
Parameters:

Decimal Integer: value corresponding to keyword supplied with
-0 flag 1 = DBMS_CATALOGS, 2 = FORCE_CONSISTENT, 3
= PURGE, 4 =TEMP_PURGE, 5 =EXPIRED_PURGE,
6 =TABLE, -1 = INVALID, -2 = NOTSPECIFIED

Explanation:

DEBUG info: shows what operation VERIFYDB was evoked
with

System Status:

For development only

Recommendation:

None

S- DU04A4- SHOW - TABLE- NAME
VERIFY DB SPECIFIED TABLE NAME IS %Oc
Parameters:

Null Terminated Character String - contains name of table
specified with -otable flag.

Explanation:

DEBUG info: shows name of table that table operation is to be
performed on

System Status:

For development only

Recommendation:

None

10-44

DU Class Messages

S- DU04A5- SHOW- USER
VERIFYDB SPECIFIED USER IS %Oc
Parameters:

Null Terminated Character String - contains name of user
specified with -u flag.

Explanation:

DEBUG info: shows name of user that operator specifies if -u
option

System Status:

For development only

Recommendation:

None

S- DU04CO- CKING- CATALOGS
VERIFY DB : beginning check of DBMS catalogs for database %Oc
Parameters:

%Oc - name of database that VERIFYDB is checking.

Explanation:

Purely informative--used with dbms_catalogs VERIFYDB
operation.

System Status:

VERIFY DB keeps processing.

Recommendation:

None

S- DU04Cl- CATALOGS - CHECKED
VERIFY DB : catalog check for database %Oc complete.
Parameters:

%Oc - name of database that VERIFYDB checked.

Explanation:

Purely informative-- used with dbms_catalogs VERIFYDB
operation.

System Status:

VERIFY DB will exit successfully -- its done.

Recommendation:

None.

S_DU04C2_FORCING_CONSISTENT
VERIFYDB: beginning attempt to patch database %Oc consistent
Parameters:

%Oc - name of database that VERIFYDB is forcing consistent.

Explanation:

Purely informative-- used with force_consistent VERIFYDB
operation.

System Status:

VERIFY DB keeps processing.

Recommendation:

None.

S- DU04C3- DATABASE- PATCHED
VERIFY DB : database %Oc patched consistent
Parameters:

%Oc - name of database that VERIFY DB is patched to consistent.

Explanation:

Purely informative-- used with force_consistent VERIFYDB
operation.

DU Class Messages

10-45

System Status:

VERIFY DB will exit successfully -- its done.

Recommendation:

None.

S- DU04C4- DROPPING - TABLE
VERIFY DB : beginning the drop of table %Oc from database % 1c.
Parameters:

%Oc - name of table
% 1c - name of database that table is in.

Explanation:

Purely informative -- used with drop_table VERIFYDB
operation.

System Status:

VERIFYDB is starting to drop the table.

Recommendation:

None.

S- DU04CS- TABLE- DROPPED
VERIFYDB: table %Oc successfully dropped from database % 1c.
Parameters:

%Oc - name of table
% 1c - name of database that table is in.

Explanation:

Purely informative-- used with drop_table VERIFYDB operation.

System Status:

VERIFY DB will exit successfully -- its done.

Recommendation:

None.

S- DU04C6- USER - ABORT
VERIFY DB : executation terminated at user request.
Parameters:

None.

Explanation:

Purely informative-- displayed when user opts NOT to do
VERIFYDB after reading warning message.

System Status:

VERIFY DB will exit without doing anything because user asked
it to.

Recommendation:

None.

S- DU04C7- PURGE- START
VERIFYDB: beginning PURGE of temporary and/or expired tables for database %Oc
Parameters:

%Oc - name of database that VERIFY DB is purging.

Explanation:

Purely informative--used with purge, temp_purge or
expired_purge VERIFYDB operation.

System Status:

VERIFY DB keeps processing.

Recommendation:

None.

10-46

DU Class Messages

S- DU04C8- TEMPPURGE- START
VERIFYDB will remove all temporary tables from database.
Parameters:

None.

Explanation:

Purely informative-- used with purge or temp_purge VERIFYDB
operation. Identifies the type of purge being performed.

System Status:

VERIFY DB keeps processing.

Recommendation:

None.

S- DU04C9- EXPPURGE- START
VERIFY DB will remove all expired relations tables from the database.
Parameters:

None ..

Explanation:

Purely informative-- used with purge or expired_purge
VERIFY DB operation. Identifies the type of purge being
performed.

System Status:

VERIFY DB keeps processing.

Recommendation:

None.

S- DU04CA- PURGE- DONE
VERIFY DB : PURGE of database %Oc is complete.
Parameters:

%Oc - name of database that VERIFY DB is purging.

Explanation:

Purely informative--used with purge, temp_purge or
expired_purge VERIFYDB operation.

System Status:

VERIFY DB keeps processing.

Recommendation:

None.

S- DU04FF- CONTINUE- PROMPT
Do you wish to continue? (Y = yes, N = no)
Parameters:

None.

Explanation:

Requests input from user -- used with runinteractive mode of
VERIFY DB . This prompt message always follows an
informative message indicating the risk of running VERIFYDB's
DBMS_CATALOGS operation in RUNINTERACTIVE mode.

System Status:

Wait until input, loop back to prompt if input not valid

Recommendation:

Enter Y or N and hit carriage retum:Y means yes, do suggested
action.N means no, do not do suggested action.

W - DUIOOO- DB- NOT- FOUND
The database '%Oc' could not be found in the IIDBDB database system catalog.

DU Class Messages

10-47

W - DUIOOI - NO - IIEXTEND - ENTRIES
There were no entries in the IIextend catalog of IIDBDB for this database.
W - DUIOIO- UTIL- ABORT
%Oc of database '% 1c' abnormally terminated.
W - DUIOll - INTERRUPT
Utility interrupt terminated.
W - DUI012- UNKNOWN- EX
Unexpected exception occurred in utility.
DEL
W - DUI020-DIRNOTFOUND
The directory' % 1c' in the path '%Oc' was not found.
DEL
FILENOTFOUND
W - DUI021The file '% 1c' in the path '%Oc' was not found.
W_DUI030_UNKNOWN_CATALOG_SY
The system catalog' %Oc' is unknown to the SYSMOD utility. Please submit a Software
Performance Report (SPR).
W - DUI040- FOUND- EXTDB - FI
Found extended database '%Oc' in the area '% 1c' .
W - DUI041 - NOLOC - FI
'%Oc' has not been defined as a locationname in the IILOCATIONS catalog.
W - DUI042- NO- CNFLOC - FI
The locationname '%Oc' found in the '% 1c' database's configuration file has not been
defined in this installation's IILOCATIONS catalog.
W - DUI043- SAME- DBNAME- FI
Second occurrence of '%Oc' ignored.
W - DUI044- REALDBS - NOT- FOUND - FI
Real databases not in the IIDATABASE catalog:
W - DUI045- DBTUPS - NOT - FOUND- FI
'iidatabase' tuples not corresponding to real databases:
W - DUI046- DUP- DBTUP- FI
The IIDBDB contains more than one entry for the database %Oc.
W - DUI047 - SAMEDB
-FI
Database '%Oc' already located.
10-48

DU Class Messages

W - DUI048- ABORT- FI
Rebuilding of IIDBDB abnormally terminated.

W - DUI062- DBMS60- FAIL
Conversion of the database '%Oc 's' DBMS objects failed.

W - DUI080RUN
-DESTROYDB
Run DESTROYDB to delete the partially created database '%Oc'.

W - DU1520- NO - UCODE50- FILE
The ULTRIX/SQL utility file '%Oc' doesn't exist. This file is needed to create the
ULTRIX/SQL utility table 'iicodemap'. 'iicodemap' is used to map 5.0 user codes to their
corresponding user names. Please consult DUF annotated error messages for suggested
solutions to this problem.

W - DU1521BAD
-UCODE
The user code '%Oc' could not be found in the 'iicodemap' table. This code was
encountered in a 5.0 admin file when trying to rebuild a 5.0 iidatabase tuple for
FINDDBS. Please consult DUF annotated error messages for suggested solutions to this
problem.

W - DU1522NO
-50AREA
The 5.0 area '%Oc' could not be found in the 'iilocations' table. This area was
encountered in a 5.0 admin file when trying to rebuild a 5.0 iidatabase tuple. Please
consult DUF annotated error messages for suggested solutions to this problem.

W - DU1523- BAD - 50ADMIN- READ
Can't read 5.0 admin file '%Oc' for database '%Ic' on '%2c'.

W - DU1524- TOO - MANY - LOCS
The 5.0 area '%Oc' is referenced by two or more locations in the iilocations catalog.
FINDDBS is unable to determine what location this database belongs on. Because of this
no iidatabase tuple can be built for this 5.0 database. Please consult DUF annotated error
messages for suggested solutions to this problem.

S- DU1600- INVALID - RELID
Table %Oc (owner %Ic) has invalid table identifier
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- name of table's owner (from iirelation.relowner)

Explanation:

VERIFY DB test I found entry in iirelation where reltid = O.
Since reltid is used to join the iirelation catalog to other system
catalogs that are required to retrieve any data from the table (like
iiattribute), this tuple is useless.

System Status:

VERIFY DB keeps running

DU Class Messages

10-49

Recommendation:

recommended action can only be performed in interactive mode.
That is to delete this tuple from iirelation. If the user does not opt
to delete this tuple, s/he can manually modify iirelation.reltid to
the correct value (if known)
SEE S_DU030I.

S- DU1601- INVALID - ATTID
Table %Oc (owner % I c) has a mismatch in number of columns. iirelation indicates there
are %2d but iiattribute contains %3d.
Parameters:

%Od -- attribute number (from iiattribute.attno)
% I c -- name of table (from iirelation.relid)
%2c -- tables owner (from iirelation.relowner)

Explanation:

VERIFY DB test 2a found invalid attno in iiattribute

System Status:

VERIFYDB keeps running

Recommendation:

recommended action can only be performed in interactive mode.
That is to delete this table from the database. If the user does not
opt to drop this table, s/he can manually reconstruct the
iiattribute tuples.
SEE S_DU0302.

S- DU1602- DUPLICATE- ATTIDS
Table %Oc (owner %Ic) has too many column # %2d)
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- tables owner (from iirelation.relowner)
%2d -- attribute number (from iiattribute.attno)

Explanation:

VERIFY DB test 2a found more than one tuple with specified
attno

System Status:

VERIFY DB keeps running

Recommendation:

S- DU1603- MISSING - ATTIDS
Attribute # %Od is missing from table %Ic (owner %2c).
Parameters:

%Od -- attribute number (from iiattribute.attno)
% Ic -- name of table (from iirelation.relid)
%2c -- tables owner (from iirelation.relowner)

Explanation:

VERIFYDB test 2a found missing attribute definition for table.

System Status:

VERIFY DB keeps running

10-50

DU Class Messages

Recommendation:

S- DU1604- ATTID - MISMATCH
Mismatch on number of columns in table %Oc (owner %Ic) -- iirelation indicates it has
%2d columns and there are %3d columns defined in iiattributes.
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- tables owner (from iirelation.relowner)
%2d -- #attributes (from iirelation.relatts)
%3d -- largest value of attribute number (from iiattribute.attno)

Explanation:

There is a mismatch between the number of columns that
iirelation indicates the table has and the actual number of
columns defined in iiattributes. This is detected by VERIFYDB
test 2a.

System Status:

VERIFYDB keeps running

Recommendation:

S- DU1605- INCORRECT- RELWID
There is a mismatch between the table width defined in iirelation as %Od and the sum of
each column's width in iiattributes (which is % Id) for table %2c (owner %3c)
Parameters:

%Od -- table's width from iirelation (iirelation.rel wid)
% Id -- sum of width of each attribute (from each
iiattribute.attfrml)
%2c -- name of table (from iirelation.relid)
%3c -- table's owner (from iirelation.relowner)

Explanation:

VERIFY DB test 2b found a mismatch between how large
(#bytes of storage) a tuple in the table is and the actual columns
defined in iiattributes.

System Status:

VERIFY DB keeps running

Recommendation:

recommended action can only be performed in interactive mode.
That is to replace iirelation.relatts with the sum of each attfrml.
If the user does not opt to do so, s/he can manually reconstruct
the iiattribute tuples, or drop the table from the database.
SEE S_DU0303.

DU Class Messages

10-51

S- DU1606- KEYMISMATCH
Mismatch between iirelation and iiattributes concerning # keys in table. iirelation
indicates there are %Od but iiattribute indicates there are %ld for table %2c (owner %3c)
Parameters:

%Od -- # columns iirelation indicates there are (iirelation.relkeys)
% ld -- count of number of keys in iiattributes for this table
(count(iiattributes.attkey == ISKEY)
%2c -- name of table (from iirelation.relid)
%3c -- table's owner (from iirelation.relowner)

Explanation:

VERIFYDB test 3 found a mismatch between the # columns
marked as keys in iiattributes and the # keys that iirelation
indicates there should be.

System Status:

VERIFYDB keeps running

Recommendation:

Replace iirelation.relkeys with the count of keys defined in
iiattribute. If the user is in interactive mode and does not opt for
the recommended action, s/he can manually repair or reconstruct
the iiattribute tuples, or drop the table from the database. Of
course, no correction is made if VERIFYDB is in REPORT
mode.
SEE S_DU0304.

S- DU1607- INVALID - RELSPEC
Table %Oc (owner %Ic) has invalid storage structure specified Run VERIFYDB with
-otable option for this table.
Parameters:

%Oc -- name of table (from iirelation.relid)
% lc -- tables owner (from iirelation.relowner)

Explanation:

VERIFY DB test 4 found invalid relspec in iirelation for this
table.

System Status:

VERIFYDB keeps running.

Recommendation:

Run VERIFYDB's patchlink function on this table or drop this
table from the database.

S_DU1608_MARKED_AS_CATALOG
Table %Oc (owner %lc) incorrectly marked as system catalog.
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- tables owner (from iirelation.relowner)

Explanation:

VERIFY DB test Sa found table marked as system catalog that
does not start with 'ii' or is not owned by $ingres or both.
System Status VERIFYDB keeps running

Recommendation:

in interactive mode can grant yes/no premission to clear bit in
iirelation. else user takes no action. Of course, no correction is
made if VERIFYDB is in REPORT mode.

10-52

DU Class Messages

S_DU1609 _NOT_CATALOG
Table %Oc (owner %Ic) is not a system catalog
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- tables owner (from iirelation.relowner)

Explanation:

VERIFY DB test 5b found a catalog that starts with 'ii' but does
not have iirelation.relstat==CATALOG

System Status:

VERIFY DB keeps running.

Recommendation:

(Some tables beginning with ii are permitted from CONVT060.
The user must decide if this is one. If not, the user may wish to
manually modify iirelation.relstat)

S- DU1610- NO - TABLE- FILE
Warning: Physical File for table %Oc (owner %lc) does not exist.
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- name of tables owner (from iirelation.relowner)

Explanation:

VERIFY DB test #6 found

System Status:

VERIFY DB keeps running as long as it can before it crashes. It
should not crash if the missing file is for a user table, but it will
crash if the missing file is for a core system catalog.

Recommendation:

Try to find a backup tape with the disk file if the table should
have a file (or files if there are multiple locations) associated
with it. If the table is a core catalog and the file cannot be
restored or recreated, the user has just lost all of the data in the
database. If the user cannot recover the disk file for a user table,
then only the user table is lost, not the whole database. If
VERIFY DB is being run in interactive mode, it will prompt for
permission to drop the table from the system catalogs. Such
permission should NOT be granted until the user is sure that he
does not have a backup of the file(s).
SEE S_DU0302.

S_DU1611_NO _PROTECTS
iirelation indicates that there are protections for table %Oc (owner % Ic), but none are
defined.
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- name of tables owner (from iirelation.relowner)

Explanation:

VERIFY DB test #8 found that there were not really protections
defined for this table, but iirelation thought that there were.

System Status:

VERIFYDB keeps running.

Recommendation:

None required unless running in interactive mode. Then enter
yes/no permission for request to clear PRTUPS bit from

DU Class Messages

10-53

iirelation.relstat after being prompted for permission. Of course,
no correction is made if VERIFYDB is in REPORT mode.

S_ DU1612_NO _INTEGS
iirelation indicates that there are integrities for table %Oc (owner % Ic), but none are
defined.
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- name of tables owner (from iirelation.relowner)

Explanation:

VERIFYDB test #9 found that there were not really integrities
defined for this table, but iirelation thought that there were.

System Status:

VERIFYDB keeps running.

Recommendation:

N one required unless running in interactive mode. Then enter
yes/no permission for request to clear INTEGS bit from
iirelation.relstat after being prompted for permission. Of course,
no correction is made if VERIFYDB is in REPORT mode.
SEE S_DU0306.

S_ DU1613_BAD _CONCUR
iirelation specifies special core catalog locking for non core catalog table: Table %Oc
(owner %Ic)
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- name of tables owner (from iirelation.relowner)

Explanation:

VERIFY DB test #10 found that a table that is not a DBMS core
catalog was marked for special core catalog locking that blocks
out no_read_lock users while catalog is being updated.

System Status:

VERIFY DB keeps running.

Recommendation:

None required unless in interactive mode. Then enter yes/no
permission to clear the CONCUR bit from iirelation.relstat -then answer should be yes unless the table is one of (iirelation,
iirel_idx, iiattribute, iiindex, iidevices). If the table is one of
these and VERIFY DB outputs this message, then there is a
serious problem. Of course, no correction is made if VERIFYDB
is in REPORT mode.
SEE DU0307.

S_DU1614_MISSING_CONCUR
iirelation does not specify special core catalog locking for core catalog %Oc
Parameters:

%Oc -- name of table (from iirelation.relid)

Explanation:

VERIFY DB test #11 found that one of the DBMS core catalogs
is not marked for the special locking that keeps no_read_lock
users from accessing the catalog while it is being updated.

10-54

DU Class Messages

System Status:

VERIFYDB keeps running.

Recommendation:

none required unless in interactive mode. Then enter yes/no
permission to set the CONCUR bit from iirelation.relstat -- then
answer should be yes if the table is one of (iirelation, iirel_idx,
iiattribute, iiindex, iidevices). If the table is not one of these and
VERIFYDB outputs this message, then there is a serious
problem. Of course, no correction is made if VERIFYDB is in
REPORT mode.
SEE DU0308.

S DU1615 NOT VIEW

iirelation indicates that %Oc (owner %lc) is a view, but a physical disk file exists for it,
which indicates that it's really a table.
Parameters:

%Oc -- name of view/table (from iirelation.relid)
% lc -- name of tables owner (from iirelation.relowner)

Explanation:

VERIFYDB test #12 found that there is a physical disk file
associated with this view's reltid -- and views never have
physical tables associated with them. Besides, there is NOT an
entry in iitree for this view. Therefore, it is either a table that has
been mismarked as a view, or someone has been playing with
file names and iitree has lost some of its tuples.

System Status:

VERIFY DB keeps running.

Recommendation:

If the user is not running in interactive mode, VERIFYDB

automatically changes iirelation to assume this is a table, not a
view. If VERIFYDB is in RUNINTERACTIVE mode, then the
user must grant yes/no permission to redefine the view to be a
table. Of course, no correction is made if VERIFYDB is in
REPORT mode.
SEE S_DU0309.
S_DU1616_MISSING _VIEW _ DEF

there is no view definition (in iitree) for %Oc (owner % lc)
Parameters:

%Oc -- name of view (from iirelation.relid)
% lc -- name of view's owner (from iirelation.relowner)

Explanation:

VERIFY DB test12 could not find the view definition for this
view.

System Status:

VERIFYDB keeps running.

Recommendation:

If VERIFY DB is not in RUNINTERACTIVE mode, it
automatically drops this view from the system. If it is in

RUNINTERACTIVE, then the user must give yes/no permission
to drop this view from the system. Of course, no correction is
made if VERIFYDB is in REPORT mode.
SEE S_DU030B.

DU Class Messages

10-55

S- DU1617NO
-DBDEPENDS
Missing information in iidbdepends for view %Oc (owner %lc).
Parameters:

%Oc -- name of table (from iirelation.relid)
% lc -- name of tables owner (from iirelation.relowner)

Explanation:

VERIFYDB test #13 found that the view was not shown in
iidbdepends -- therefore the DBMS can't trace the view back to
the table(s) its based on. This means there is no way to verify
that the base table for the view really exists.

System Status:

VERIFY DB keeps running.

Recommendation:

If VERIFY DB is not in RUNINTERACTIVE mode, it

automatically drops the view. Otherwise, the user must give
interactive yes/no permission. Of course, no correction is made if
VERIFY DB is in REPORT mode.

S_DU1618_NO_QUERYTEXT
Warning: there is no entry in iiqrytext to define view %Oc (owner % lc).
Parameters:

%Oc -- name of table (from iirelation.relid)
% lc -- name of tables owner (from iirelation.relowner)

Explanation:

VERIFY DB test #14 found that the query text (which defined
the view) is not in iiqrytext table.

System Status:

VERIFYDB keeps running.

Recommendation:

VERIFY DB only prints a warning message, so there is no user
action required. However, the user may desire to drop this view
and redefine it, so that the query test is defined.

S- DU1619NO
VIEW
iirelation indicates that there is a view defined for table %Oc (owner % lc), but none exists.
Parameters:

%Oc -- name of table (from iirelation.relid)
% lc -- name of tables owner (from iirelation.relowner)

Explanation:

VERIFY DB test #15 found that iirelation believes this is a base
table for a view, but there is no view defined that uses this table
as part (or all) of the view base.

System Status:

VERIFY DB keeps running.

Recommendation:

If VERIFY DB is not in RUNINTERACTIVE mode, it

automatically clears the VBASE bit from iirelation.relstat.
Otherwise it prompts the user for permission to do so. The user
must give yes/no permission -- usually s/he should give yes in
this case. If the user wants to recreate the view, s/he can get the
view definition from iiqrytext. Of course, no correction is made
if VERIFYDB is in REPORT mode.
SEE S_DU030C.

10-56

DU Class Messages

S- DU161A- NO- BASE- FOR- INDEX
The base table for index table %Oc (owner %1c) does not exist.
Parameters:

%Oc -- name of index table (from iirelation.relid)
% lc -- name of tables owner (from iirelation.relowner)

Explanation:

VERIFY DB test #16 found that this index table is useless
because the base table that it describes does not exist.

System Status:

VERIFY DB keeps running.

Recommendation:

VERIFYDB will automatically drop the index table unless in
RUNINTERACTIVE mode, where it will prompt the user for
permission to drop the table. In this case, user must give yes/no
permission. Of course, no correction is made if VERIFYDB is in
REPORT mode.
SEE S_DU0302.

S- DU161BNO
2NDARY
iirelation does not indicate that there is a secondary index table for base table %Oc (owner
%lc). However, index table %2c (owner %3c) exists.
Parameters:

%Oc -- name of table (from iirelation.relid for base table)
% lc -- name of tables owner (from iirelation.relowner for base
table)
%2c -- name of index table (from iirelation.relid for index table)
%3c -- name of index tables owner (from iirelation.relowner)

Explanation:

VERIFY DB test #17 found that the iirelation entry for a base
table did not indicate there is a secondary index table for this
table.

System Status:

VERIFYDB keeps running.

Recommendation:

None unless running in RUNINTERACTIVE mode. Then give
yes/no permission to set IDXD bit in iirelation.relstat for base
table. Of course, no correction is made if VERIFYDB is in
REPORT mode.
SEE S_DU030D.

S_DU161C_WRONG_NUM_INDEXES
iirelation believes there are %Od indexes on table % lc (owner %2c) but %3d are defined.
Parameters:

%Od -- number of index tables iirelation thinks there are (from
iirelation.relidxcount)
% lc -- name of base table (from iirelation.relid)
%2c -- name of tables owner (from iirelation.relowner)
%3d -- actual number of index tables defined in iiindex.

Explanation:

VERIFY DB test #18 found that iirelation thinks there are more
secondary indexes defined for this table than really exist.

System Status:

VERIFY DB keeps running.

DU Class Messages

10-57

Recommendation:

None unless VERIFYDB is in RUNINTERACTIVE mode. Then
give yes/no permission to change value of iirelation.relidxcount.
Of course, no correction is made if VERIFYDB is in REPORT
mode. See S_DU030E.

S_ DU161D_ NO _INDEXS
iirelation believes there are indexes on table %Oc (owner % 1c) but none are defined.
Parameters:

%Oc -- name of table (from iirelation.relid for base table)
% lc -- name of tables owner (from iirelation.relowner for base
table)

Explanation:

VERIFY DB test #18 found that iirelation thinks there are
secondary indexes defined for this table, but none exist.

System Status:

VERIFYDB keeps running.

Recommendation:

None unless VERIFYDB is in RUNINTERACTIVE mode. Then
give yes/no permission to clear iirelation.relidxcount and clear
IDXD bit from iirelation.relstat. Of course, no correction is made
if VERIFY DB is in REPORT mode.
SEE S_DU030F.

NO
S- DU161E-STATISTICS
iirelation believes there are optimizer statistics for table %Oc (owner % Ic) but none are
defined.
Parameters:

%Oc -- name of table (from iirelation.relid for base table)
% Ic -- name of tables owner (from iirelation.relowner for base
table)

Explanation:

VERIFYDB test #19 found that iirelation thinks there are
optimizer statistics defined for this table, but none exist.

System Status:

VERIFY DB keeps running.

Recommendation:

None unless VERIFYDB is in RUNINTERACTIVE mode. Then
give yes/no permission to clear OPTSTAT bit from
iirelation.relstat. Of course, no correction is made if VERIFYDB
is in REPORT mode.
SEE S_DU03IO.

S_ DU161F_ WRONG _ NUM
iirelation believes there are %Od locations for table % Ic (owner %2c) but %3d are defined.
Parameters:

%Od -- number of locations iirelation thinks there are (from
iirelation.relloccount)
% lc -- name of table (from iirelation.relid)
%2c -- name of tables owner (from iirelation.relowner)
%3d -- actual number of locations defined in iidevices.

Explanation:

VERIFYDB test #20 found that iirelation thinks there are more
locations defined for this table than are defined in iidevices.

10-58

DU Class Messages

System Status:

VERIFY DB keeps running.

Recommendation:

None unless VERIFYDB is in RUNINTERACTIVE mode. Then
give yes/no permission to change value of iirelation.relloccount
if there are some locations defined in iidevices. Or, if there are
no locations defined in iidevices then give yes/no permission to
reset the MULTIPLE_LaC bit of iirelation.relstat and to clear
iirelation. relloccount.
NOTE: VERIFYDB will not take corrective action unless it is
running in RUNINTERACTIVE mode and yes permission has
been granted.
SEE S_DU03I1.

S- DU1620- INVALID - LOC
location %Oc for table % Ic (owner %2c) is invalid
Parameters:

%Oc -- name of location (from iirelation.relloc)
% Ic -- name of table (from iirelation.relid)
%2c -- name of tables owner (from iirelation.relowner)

Explanation:

VERIFY DB test #21 found that the default location for this table
is not valid, or one of the extended locations for this table is not
valid.

System Status:

VERIFYDB keeps running.

Recommendation:

VERIFYDB will not permit user any action. However, user will
want to manually fix location to be valid.

S- DU1621- INVALID - FILLFACTOR
Table %Oc (owner %lc) has an invalid data page fill factor of %2d
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- name of tables owner (from iirelation.relowner)
%2d -- fill factor (from iirelation.reldfill)

Explanation:

VERIFYDB test #22, 23, 24 or 25 found an invalid data page fill
factor.

System Status:

VERIFY DB keeps running.

Recommendation:

None unless VERIFYDB in RUNINTERACTIVE mode. Then
give yes/no permission to put default fill factor for this table type
into iirelation.reldfilL Of course, no correction is made if
VERIFYDB is in REPORT mode.
SEE DU03I2

S- DU1622- INVALIDLEAF
FILLFTR
Table %Oc (owner %Ic) has an invalid leaf page fill factor of %2d
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- name of tables owner (from iirelation.relowner)
%2d -- fill factor (from iirelation.rellfill)
DU Class Messages

10-59

Explanation:

VERIFYDB test 25 found an invalid leaf page fill factor.

System Status:

VERIFYDB keeps running.

Recommendation:

None unless VERIFYDB inRUNINTERACTIVE mode. Then
give yes/no permission to put default fill factor for this table type
into iirelation.rellfill. Of course, no correction is made if
VERIFYDB is in REPORT mode.
SEE DU03I3.

S- DU1623- INVALID - INDEX- FILLFTR
Table %Oc (owner %Ic) has an invalid index page fill factor of %2d
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- name of tables owner (from iirelation.relowner)
%2d -- fill factor (from iirelation.relifill)

Explanation:

VERIFY DB test 25 found an invalid index page fill factor.

System Status:

VERIFY DB keeps running.

Recommendation:

None unless VERIFYDB in RUNINTERACTIVE mode. Then
give yes/no permission to put default fill factor for this table type
into iirelation.relifill. Of course, no correction is made if
VERIFY DB is in REPORT mode.
SEE DU03I4.

S- DU1624- MISSING - IIRELIDX
system catalog iirel_idx is missing the entry for table %Oc (owner % Ic)
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- name of tables owner (from iirelation.relowner)

Explanation:

VERIFYDB test #26 found a table definition in iirelation that
does not have a corresponding entry in iirel_idx.

System Status:

VERIFYDB keeps running.

Recommendation:

None is required unless VERIFY DB in RUNINTERACTIVE
mode. Then user must give yes/no permission to create a tuple in
iirel_idx for this table. Of course, no correction is made if
VERIFY DB is in REPORT mode.

S- DU1625- MISSING - IIRELATION
Table %Oc (owner %Ic) is defined in iirel_idx, but is missing from iirelation. This means
that the database does not recognize this table.
Parameters:

%Oc -- name of table (from iirel_idx.relid)
% I c -- name of tables owner (from iirel_idx.relowner)

Explanation:

VERIFYDB test #27 found an entry in the index table for a
nonexistent table -- ie there is no corresponding entry in
iirelation for this table.

System Status:

VERIFY DB keeps running.

10-60

DU Class Messages

Recommendation:

None is required unless VERIFYDB in RUNINTERACTIVE
mode. Then user must give yes/no permission to drop this tuple
from iirel_idx. Of course, no correction is made if VERIFYDB is
in REPORT mode.

S- DU1626- INVALID - ATTRELID
Table id of %Od, Index table id of % Id in iiattribute does not match any table listed in
iirelation.
Parameters:

%Oc - attrelid from iiattributes
% Ic - attrelidx from iiattributes

Explanation:

VERIFYDB test #28 found some tuples in iiattributes that have
table id and index table id values that do not match any entries in
iirelation. this means that they are useless, and should be deleted.

System Status:

VERIFYDB keeps running.

Recommendation:

User must give yes/no permission to drop these tuples from
iiattribute. User may wish to construct an iirelation tuple
manually, rather than to delete these tuples from iiattribute.
NOTE: VERIFYDB will not take any corrective action for this
situation unless mode = RUNINTERACTIVE and "yes"
permission has been granted.
SEE S_DU03I7

S- DU1627- INVALID - ATTFMT
Table %Oc (owner %Ic) has invalid attribute format for column %2d of %3d.
Parameters:

%Oc -- name of table (from iirelation.relid)
% Ic -- name of tables owner (from iirelation.relowner)
%2d -- column number (from iiattribute.attid)
%3d -- numeric value of iiattribute.attfrmt

Explanation:

VERIFY DB test #29 found an invalid attribute format
specification for one of the columns. It must be one of
INTEGER, FLOAT, C, TEXT, DATA, MONEY, CHAR or
VCHAR.

System Status:

VERIFY DB keeps running.

Recommendation:

If VERIFY DB mode = RUNINTERACTIVE, user must give
yes/no permission to drop table from database. If user withholds

permission or in another mode, user may wish to manually
update iiattribute.attfrmt. Valid values are:

DU Class Messages

10-61

INTEGER
FLOAT
C

TEXT
DATE
MONEY
CHAR
OVCHAR

Nullable
-30
-31
-32
-31-3
-5

-20
-21

Not Nullable
30
31
32
37
3
5
2
21

SEE S_DU0302
S- DU1628- INVALID - BASEID
Table id of %Od, Index table id of % Id in iiindex does not match any table listed in
iirelation.
Parameters:

%Oc - baseid from iiindex
% 1c - indexid from iiindex

Explanation:

VERIFY DB test #30 found some tuples in iiindex that have table
id and index table id values that do not match any entries in
iirelation. this means that they are useless, and should be deleted.

System Status:

VERIFYDB keeps running.

Recommendation:

User must give yes/no permission to drop these tuples from
iiindex. User may wish to construct an iirelation tuple manually,
rather than to delete these tuples from iiindex. Of course, no
correction is made if VERIFYDB is in REPORT mode.

S DU1629 IS INDEX
iirelation does not indicate that table %Oc (owner % lc) is a secondary index table.
Parameters:

%Oc -- name of table (from iirelation.relid for base table)
% lc -- name of tables owner (from iirelation.relowner for base
table)

Explanation:

VERIFY DB test #31 found that the iirelation entry did not mark
this as a secondary index table, but it is one.

System Status:

VERIFY DB keeps running.

Recommendation:

None unless running in RUNINTERACTIVE mode. Then give
yes/no permission to set INDEX bit in iirelation.relstat for this
index table.

10-62

DU Class Messages

S- DU162A- INVALID - INDEXKEYS
Secondary index table %Oc (owner % Ic) has invalid key column of %2d
Parameters:

%Oc -- name of table (from iirelation.relid for base table)
% Ic -- name of tables owner (from iirelation.relowner for base
table)
%2d -- invalid idom element in iiindex table (where value is #
columns in base table).

Explanation:

VERIFYDB test #32 found that one of the table columns marked
as a key is invalid, because it's value is larger than the number of
columns in the table.

System Status:

VERIFY DB keeps running.

Recommendation:

None unless running in RUNINTERACTIVE mode. Then give
yes/no permission to drop this index table.
SEE S_DU0302.

S- DU162B- INVALID - DEVRELIDX
Table id of %Od, Index table id of % 1d in iidevices does not match any table listed in
iirelation.
Parameters:

%Oc - devrelid from iidevices
% 1c - devrelidx from iidevices

Explanation:

VERIFYDB test #33 found some tuples in iidevices that have
table id and index table id values that do not match any entries in
iirelation. This means that they are useless, and should be deleted.

System Status:

VERIFY DB keeps running.

Recommendation:

User must give yes/no permission to drop these tuples from
iidevices. User may wish to construct an iirelation tuple
manually, rather than to delete these tuples from iidevices. Of
course, no correction is made if VERIFYDB is in REPORT
mode.
SEE S_DU03IA.

S- DU162C- LOCATIONS - EXIST
Locations have been defined for table %Oc (owner % 1c) but iirelation does not indicate
that they exist.
Parameters:

%Oc -- name of table (from iirelation.relid)
% 1c -- name of table's owner (from iirelation.relowner)

Explanation:

VERIFY DB test 34 found locations for this table defined in
iidevices, but iirelation.relstat.MUTLIPLE_LOC was set to false.

System Status:

VERIFY DB keeps running

Recommendation:

VERIFY DB will automatically set the MULTIPLE_LOC bit in
iirelation's relstat unless VERIFYDB in RUNINTERACTIVE.

DU Class Messages

10-63

Then user must grant yes/no permission. Of course, no
correction is made if VERIFYDB is in REPORT mode.
SEE S_DU03lB.
S_DU162D_UNKNOWN_TREEMODE
iitree table id= %Od, index id= % ld for table/view %2c (owner %3c) has unknown tree
modes of %4d. Valid values are: view=17, protection=19, integrity=20, register link =
101, create link = 100
Parameters:

%Od - base table id associated with tree (from iitree.treetabbase)
%ld - base table index id associated with tree (from
ii tree. treetabidx)
%2c - name of table/view (from iirelation.relid)
%3c - owner of table/view (from iirelation.relowner)
%4d - mode value (from iitree.treemode)

Explanation:

VERIFY DB test #36 found an entry in iitree that has a mode
unknown to the DBMS. Of course, it is possible that new tree
entries will be created in later versions of the database (greater
than 1.0) and an older version of VERIFYDB is being run.
Therefore, the correction of deleting these tuples from the tree
will only be performed in interactive mode.

System Status:

VERIFY DB keeps running.

Recommendation:

Give yes/no permission to delete these tuples from iitree. Of
course, no correction is made if VERIFYDB is in REPORT
mode.
SEE S_DU03lC.

S- DU162E- INVALID - TREEID
iitree table id= %Od, index id= % ld for %2c (owner %3c) has invalid treeid. Tree cannot
be referenced by other system catalog tables.
Parameters:

%Od - base table id associated with tree (from iitree.treetabbase)
% ld - base table index id associated with tree (from
ii tree. treetabidx)
%2c - name of table/view (from iirelation.relid)
%3c - owner of table/view (from iirelation.relowner)

Explanation:

VERIFY DB test #37 found a tree id that is invalid. Since treeid
is how other system catalogs reference this tree, this tree cannot
be used by the DBMS.

System Status:

VERIFY DB keeps running.

Recommendation:

If user knows the correct tree id value, s/he can replace in it the
effected iitree tuples. In such a case, s/he should give no
permission to delete the tuples (RUNINTERACTIVE mode
only). Otherwise, the tuples will be removed from iitree, and the
user can get the original query text from iiqrytext.

SEE S_DU03lC.
10-64

DU Class Messages

S- DU162FNO
TREEBASE
The base table for tree entry does not exist. (table id = %Od, index id = %Id
Parameters:

%Od - base table id associated with tree (from iitree.treetabbase)
% ld - base table index id associated with tree (from
iitree. treetabidx)

Explanation:

VERIFY DB test #35 could not find an entry in iirelation with the
same (base, index) id. Views, permits and integrities are tied to
an entry in iirelation, so if this tree defines a view, an integrity or
a permit, it is useless and should be dropped. Stored procedures
are not tied to an entry in iirelation.

System Status:

VERIFY DB keeps running.

Recommendation:

VERIFY DB will automatically delete the tuples from iitree
unless VERIFYDB is in RUNINTERACTIVE mode, then it will
prompt the user for yes/no permission. In that case, the user
action is to give yes or no permission. Of course, no correction is
made if VERIFYDB is in REPORT mode.
SEE S_DU031C.

S- DU1630- NO - VIEW- RELSTAT
iirelation does not indicate that table %Oc (owner % Ic) is a view.
Parameters:

%Os -- name of table (from iirelation.relid)
% Is -- name of tables owner (from iirelation.relowner)

Explanation:

VERIFY DB test #38 found the iirelation tuple for the iitree entry
did not indicate that this is a view.

System Status:

VERIFY DB keeps running.

Recommendation:

Unless VERIFYDB mode = RUNINTERACTIVE, correction of
setting VIEW bit in iirelation.relstat is automatically performed.
Else, user must give yes/no permission to make this correction
when prompt is given. Of course, no correction is made if
VERIFY DB is in REPORT mode.
SEE S_DU03lD

S- DU1631- NO - PROTECT- RELSTAT
iirelation does not indicate that protections are defined for table %Oc (owner % Ic).
Parameters:

%Os -- name of table (from iirelation.relid)
% Is -- name of tables owner (from iirelation.relowner)

Explanation:

VERIFY DB test #38 found the iirelation tuple for the iitree entry
did not indicate that this table has protections defined for
it.ORVERIFYDB test #45 found the iirelation tuple for this
permission did not indicate that this table has permissions
defined for it.

System Status:

VERIFY DB keeps running.

DU Class Messages

10-65

Recommendation:

Unless VERIFYDB mode = RUNINTERACTIVE, correction of
setting PRTUPS bit in iirelation.relstat is automatically
performed. Else, user must give yes/no permission to make this
correction when prompt is given. Of course, no correction is
made if VERIFYDB is in REPORT mode.
SEE S_DU031E

S- DU1632- NO - INTEGS - RELSTAT
iirelation does not indicate that integrities are defined for table %Oc (owner % lc).
Parameters:

%Os -- name of table (from iirelation.relid)
% Is -- name of tables owner (from iirelation.relowner)

Explanation:

VERIFY DB test #38 found the iirelation tuple for the iitree entry
did not indicate that this table has integrities defined for it.
OR
VERIFY DB test #41 found the iirelation tuple for this integrity
did not indicate that this table has integrities defined for it.

System Status:

VERIFY DB keeps running.

Recommendation:

Unless VERIFYDB mode = RUNINTERACTIVE, correction of
setting INTEGS bit in iirelation.relstat is automatically
performed. Else, user must give yes/no permission to make this
correction when prompt is given. Of course, no correction is
made if VERIFYDB is in REPORT mode.
SEE S_DU031F

S_DU1633 _MISSING_TREE _SEQ
There is a sequence error in iitree for tree %Od % Id: for table/view %2c (owner %3c)
Missing tuple for sequence # %4d
Parameters:

%Od -- high portion of tree id (from iitree.treeidl)
% Id -- low portion of tree id (from iitree.treeid2)
%2c - name of table/view (from iirelation.relid)
%3c - owner of table/view (from iirelation.relowner)
%4d -- missing sequence number

Explanation:

A tree entry may be comprised of more than 1 tuple in iitree. In
such a case, each tree entry has identical treetabbase, treetabidx,
treeidl and treeid2 values, but has unique (and sequential)
treeseq values.VERIFYDB test # 39 determined that one (or
more) of the expected treeseq values are missing.
NOTE: VERIFYDB cannot determine if the last (or last N)
tuples are missing from the tree, as there is no place in iitree that
gives a count of the number of tree tuples expected.

System Status:

VERIFY DB keeps running.

Recommendation:

VERIFY DB will automatically drop the tree tuples from iitree
unless in runinteractive mode, where user must give yes/no

10-66

DU Class Messages

pennission for such a fix. Of course, no correction is made if
VERIFYDB is in REPORT mode.
SEE S_DU03IC.
S- DU1634- NO - BASE- FOR- INTEG
Base table id %Od, index id % ld that integrity is defined for is not listed in iirelation.
Parameters:

%Od - base table id (from iiintegrity.inttabbase)
% ld - index table id (from iiintegrity.inttabidx)

Explanation:

VERIFY DB test # 40 found that the table that is supposed to
receive this integrity doesn't exist (at least it's not listed in
iirelation.)

System Status:

VERIFY DB keeps running.

Recommendation:

VERIFY DB will automatically drop all tuples with this
base,index id from iiintegrity unless in RUNINTERACTIVE
mode. Then user must enter YES/NO pennission. Of course, no
correction is made if VERIFYDB is in REPORT mode.
SEE S_DU0320.

S- DU1635- NO - TREE- FOR- INTEG
WARNING: No tree exists for integrity %Od %ld on table %2c (owner %3c). The DBMS
cannot enforce this integrity.
Parameters:

%Od - high portion oftreeid (from iiintegrity.inttreeidl)
% ld - low portion of treeid (from iiintegrity.inttreeid2)
%2c - table name (from iirelation.relid)
%3c - table's owner (from iirelation.relowner)

Explanation:

VERIFY DB test # 42 found that the tree that defines this
integrity does not exist.

System Status:

VERIFY DB keeps running.

Recommendation:

S_DU1636_NO_INTEG_QRYTEXT
The query text for integrity %Od %ld (table %2c, owner %3c) does not exist.
Parameters:

%Od - high portion of qryid (from iiintegrity.intqryidl)
% ld - low portion of qryid (from iiintegrity.intqryid2)
%2c - table name (from iirelation.relid)
%3c - table's owner (from iirelation.relowner)

Explanation:

VERIFY DB test # 43 found that the query text used to define
this integrity does not exist. This does not hurt DBMS
functioning, but it effects some utility routines.
DU Class Messages

10-67

System Status:

VERIFYDB keeps running.

Recommendation:

user may wish to drop this integrity and redefine it, if s/he knows
what the definition should be.

S- DU1637- NO- BASE- FOR- PERMIT
Base table id %Od, index id % Id that permit is defined for is not listed in iirelation.
Parameters:

%Od - base table id (from iiprotect.protabbase)
% Id - index table id (from iiprotect.protabidx)

Explanation:

VERIFY DB test # 44 found that the table that is supposed to
receive this permit doesn't exist (at least it's not listed in
iirelation.)

System Status:

VERIFYDB keeps running.

Recommendation:

VERIFYDB will automatically drop all tuples with this
base,index id from iipermit unless in RUNINTERACTIVE
mode. Then user must enter YES/NO permission. Of course, no
correction is made if VERIFYDB is in REPORT mode.
SEE S_DU0321.

S- DU1638- NO - TREE - FOR- PERMIT
No tree exists for permit %Od % ld on table %2c (owner %3c). The DBMS cannot enforce
this integrity.
Parameters:

%Od - high portion of treeid (from iipermit.protreeidl)
% Id - low portion of treeid (from iipermit.protreeid2)
%2c - table name (from iirelation.relid)
%3c - table's owner (from iirelation.relowner)

Explanation:

VERIFYDB test # 46 found that the tree that defines this permit
does not exist.

System Status:

VERIFY DB keeps running.

Recommendation:

VERIFY DB will aut anatically drop all tuples with this
base,index id from iipermit unless in RUNINTERACTIVE
mode. Then user must enter YES/NO permission. Of course, no
correction is made if VERIFYDB is in REPORT mode.
SEE S_DU0321.

S_DU1639_NO_PERMIT_QRYTEXT
The query text for integrity %dd % ld (table %2c, owner %3c) does not exist.
Parameters:

%Od - high portion of qryid (from iiintegrity.intqryidl)
% Id - low portion of qryid (from iiintegrity.intqryid2)
%2c - table name (from iirelation.relid)
%3c - table's owner (from iirelation.relowner)

Explanation:

VERIFYDB test # 43 found that the query text used to define
this integrity does not exist. This does not hurt DBMS
functioning, but it effects some utility routines.

10-68

DU Class Messages

System Status:

VERIFYDB keeps running.

Recommendation:

User may wish to drop this integrity and redefine it, if s/he
knows what the definition should be.

S_ DU163A_UNKNOWN _ QRYMODE
iiqrytext id %Od %ld has unknown modes of %2d. Valid values are: view=17,
protection=19, integrity=20 stored_procedure=87 createlink=lOO, registerlink=lOl
Parameters:

%Od - Low portion of query id (from iiqrytext.txtidl)
% Id - High portion of query id (from iiqrytext.txtid2)
%2d - query mode (from iiqrytext.mode)

Explanation:

VERIFYDB test #48 found an entry in iiqrytext that has a mode
unknown to the DBMS. This is informational only, as the DBMS
Server does not act on iiqrytext. However, some DBMS utilities
to act on it. If possible, it is best to drop the view, permit,
integrity or stored procedure and recreate it.

System Status:

VERIFYDB keeps running.

Recommendation:

None required.

S_ DU163B _INVALID _QRYTEXT_ID
iiqrytext has entry in it with invalid query id of 0 O.
Parameters:

None.

Explanation:

VERIFYDB test #49 found an entry in iiqrytext that has an
invalid query id oftxtidl=O and txtid2 = 0

System Status:

VERIFY DB keeps running.

Recommendation:

none required. However, user may wish to manually drop these
tuples from iiqrytext. User may wish to examine the txt field and
determine what txtid 1 and txtid2 should be and manually correct
them.

S_ DU163C_ QRYTEXT_ VIEW_MISSING
iiqrytext tuples with txtidl = %Od, txtid2 = %ld define a view. However, this view is
missing from the database.
Parameters:

%Od - Low portion of query id (from iiqrytext.txtidl)
% ld - High portion of query id (from iiqrytext.txtid2)

Explanation:

VERIFY DB test #50 was unable to find the view definition in
iirelation that corresponds to this view query text. This is
informational only, as the DBMS Server does not act on
iiqrytext. However, the user may wish to redefine the view to the
database.

System Status:

VERIFYDB keeps running.

Recommendation:

None required.

DU Class Messages

10-69

S_ DU163D_ QRYTEXT _PERMIT_MISSING
iiqrytext tuples with txtidl = %Od, txtid2 = %ld define a permit. However, this permit is
missing from the database.
Parameters:

%Od - Low portion of query id (from iiqrytext.txtidl)
% Id - High portion of query id (from iiqrytext.txtid2)

Explanation:

VERIFYDB test #50 was unable to find the permit definition in
iirelation that corresponds to this permit query text. This is
informational only, as the DBMS Server does not act on
iiqrytext. However, the user may wish to redefine the permit to
the database. It is possible that the table the permit is for does
not exist in the database, but VERIFY DB is not able to
determine this, as iiqrytext does not have the equivalent of reltid
and reltidx.

System Status:

VERIFY DB keeps running.

Recommendation:

None required.

S_ DU163E_QRYTEXT_INTEG_MISSING
iiqrytext tuples with txtid 1 = %Od, txtid2 = %1d define an integrity. However, this
integrity is missing from the database.
Parameters:

%Od - Low portion of query id (from iiqrytext.txtidl)
% Id - High portion of query id (from iiqrytext.txtid2)

Explanation:

VERIFY DB test #50 was unable to find the integrity definition
in iirelation that corresponds to this integrity query text. This is
informational only, as the DBMS Server does not act on
iiqrytext. However, the user may wish to redefine the integrity to
the database. It is possible that the table the integrity is for does
not exist in the database, but VERIFYDB is not able to
determine this, as iiqrytext does not have the equivalent of reltid
and reltidx.

System Status:

VERIFY DB keeps running.

Recommendation:

None required.

S_ DU163F_ QRYTEXT _DBP_MISSING
iiqrytext tuples with txtidl = %Od, txtid2 = %ld define a database procedure. However,
this DBP is missing from the database.
Parameters:

%Od - Low portion of query id (from iiqrytext.txtidl)
% Id - High portion of query id (from iiqrytext.txtid2)

Explanation:

VERIFYDB test #52b was unable to find the database procedure
definition in iitree that corresponds to this DBP query text. This
is informational only, as the DBMS Server does not act on
iiqrytext. However, the user may wish to redefine the DBP to the
database.

10-70

DU Class Messages

System Status:

VERIFY DB keeps running.

Recommendation:

None required.

S- DU1640- NONEXISTENT- DEID
The table/view described in iidbdepends as deidl = %Od, deid2 = %Id does not exist.
Parameters:

%Od - dependent table id (from iidbdepends.deidl)
% Id - dependent table index id (from iidbdpends.deid2)

Explanation:

System Status:

VERIFY DB keeps running

Recommendation:

VERIFY DB will automatically delete the iidbdepends tuple
unless in RUNINTERACTIVE mode. Then it will prompt the
user for yes/no permission. The user must give yes or no
permission. Of course, no correction is made if VERIFY DB is in
REPORT mode.
SEE S_DU0322

S- DU1641- NONEXISTENTINDEP
-TBL
The table that %Oc (owner % Ic) is dependent on doesn't exist.
Parameters:

%Oc - table name from iirelation.relid (of iirelation that matches
on deid 1 and deid2)
% Ic - owner name from iirelation.relowner (of iirelation that
matches on deid 1 and deid2)

Explanation:

VERIFY DB test # 55 found an entry in iidbdepends that
describes a view or table with permit as dependent on another
table. However, the table/view that it is dependent on does not
exist (or is not defined in iirelation)

System Status:

VERIFY DB keeps running

Recommendation:

S- DU1642- INID - NO - VBASE
The independent table/view %Oc (owner % I c) does not indicate a view is based on it.
Parameters:

%Oc - Independent table's name from iirelation.relid (of
iirelation that matches on inidl and inid2)
%Ic - Independent table's owner name from iirelation.relid (of
iirelation that matches on inid I and inid2)
DU Class Messages

10-71

Explanation:

VERIFY DB test # 56 found an entry in iidbdepends that
describes a view as dependent on another table. However, the
table/view that it is dependent does not indicate that there is a
view based on it.

System Status:

VERIFYDB keeps running

Recommendation:

VERIFYDB will automatically set the VBASE bit in
iirelation/relstat of the independent table/view unless in
RUNINTERACTIVE mode. Then it will prompt the user for
yes/no permission. The user must give yes or no permission. Of
course, no correction is made if VERIFYDB is in REPORT
mode.
SEE S_DU0323.

NOT
VIEW
S- DU1643- DEPENDENTThe dependent table %Oc (owner % I c) should be marked as a view, and it is not
Parameters:

%Oc - table name from iirelation.relid (of iirelation that matches
on deidl and deid2)
% I c - owner name from iirelation.relowner (of iirelation that
matches on deid I and deid2)

Explanation:

VERIFY DB test # 57 found an entry in iidbdepends that
describes a view as dependent on another table. However, the
iirelation entry for this dependent view does not indicate that this
is a view.

System Status:

VERIFY DB keeps running

Recommendation:

VERIFY DB will automatically set the VIEW bit in
iirelation.relstat for the dependent view unless in
RUNINTERACTIVE mode. Then it will prompt the user for
yes/no permission. The user must give yes or no permission. Of
course, no correction is made if VERIFYDB is in REPORT
mode.
SEE S_DU03ID.

S_DU1644_MISSING_IIXDBDEPENDS
system catalog iixdbdepends missing the entry for Independent table: %Oc (owner % Ic)
Dependent table: %2c (owner %3c).
Parameters:

%Oc -- name of independent table
% Ic -- owner of independent table
%2c -- name of dependent table
%3c -- owner of dependent table

Explanation:

VERIFYDB test #58 found a table definition in iidbdepends that
does not have a corresponding entry in iixdbdepends.

System Status:

VERIFYDB keeps running.

10-72

DU Class Messages

Recommendation:

None is required unless VERIFYDB in RUNINTERACTIVE
mode. Then user must give yes/no permission to create a tuple in
iixdbdepends for this table. Of course, no correction is made if
VERIFY DB is in REPORT mode.
SEE S_DU0324.

S- DU1645- MISSING - IIDBDEPENDS
Table with deidl = %Od deid2=%ld is defined in iixdbdepends, but is missing from
iidbdepends.
Parameters:

%Od -- table id of dependent table (from iidbdpends.deid 1)
% ld -- index id of dependent table (from iidbdpends.deid2)

Explanation:

VERIFY DB test #59 found an entry in the index table for a
nonexistent table -- ie there is no corresponding entry in
iidbdepends for this table.

System Status:

VERIFY DB keeps running.

Recommendation:

None is required unless VERIFYDB in RUNINTERACTIVE
mode. Then user must give yes/no permission to drop this tuple
from iixdbdepends. Of course, no correction is made if
VERIFY DB is in REPORT mode.
SEE S_DU0325.

S- DU1646- INVALID - STATISTIC - COL
Statistics for %Oc (owner % lc) are for column # %2d, but this table only has %3d columns
Parameters:

%Oc - name of table that statistics are on
% 1c - owner of table that statistics are on

Explanation:

VERIFY DB test # 64 found that the statistics for this table were
performed on an invalid column number. Since the utility that
gathers these statistics would not gather statistics on a
non-existent column, this indicates that the iistatistics table has
probably been corrupted.

System Status:

VERIFY DB keeps running

Recommendation:

The best user action is to re-run the OPTIMIZEDB utility.
However, VERIFYDB will attempt to patch up the iistatistics
table by deleting the appropriate tuple(s) from iistatistics, unless
it is in RUNINTERACTIVE mode. Then the user must supply
yes/no permission to perform the fix. Of course, no correction is
made if VERIFYDB is in REPORT mode.
SEE S_DU0326.

S- DU1647- NO - OPSTATIN-BASE
Table %Oc (owner %lc) does not indicate that it has optimizer statistics
Parameters:

%Oc - name of table that statistics are on
% lc - owner of table that statistics are on
DU Class Messages

10-73

Explanation:

VERIFYDB test # 62 found that the iirelation entry for the table
that these statistics are based on does not indicate that there are
statistics for this table -- (ie iirelation.relstat's OPTSTAT bit flag
is not set).

System Status:

VERIFY DB keeps running

Recommendation:

Unless VERIFYDB is in RUNINTERACTIVE mode, it will
automatically set the iirelation.relstat's OPTSTAT bit. Of course,
no correction is made if VERIFYDB is in REPORT mode.
SEE S_DU0327.

S- DU1648- MISSING - HISTOGRAM
Mismatch in histogram cell count for table %Oc (owner % lc) on attribute #%2d iistatistics
expects histogram cells, but there are not any
Parameters:

%Oc - name of table that statistics are on
% lc - owner of table that statistics are on
%2d - attribute number statistics are on
%3d - number of cells iistatistics thinks there are from
(iistatistics. snumcells)
%4d - number of cells iihistogram has (actual count of tuples)

Explanation:

VERIFY DB test # 64 found that table iistatistics indicate there is
a histogram for this table, but no histogram can be found in
iihistogram.

System Status:

VERIFY DB keeps running

Recommendation:

Unless VERIFYDB is in RUNINTERACTIVE mode, it will
automatically modify the tuple in iistatistics to stop indicating
that there is a histogram. Of course, no correction is made if
VERIFYDB is in REPORT mode.
SEE S_DU0328.

ON
S- DU1649 - STATS-INDEX
There are statistics for index table %Oc (owner % lc) table id %2d, %3d. Statistics on
index tables are not permitted.
Parameters:

%Oc - index table name
%lc - index table's owner
%2d - base table id (from iihistogram.htabbase)
%3d - index table id (from iihistogram.htabindex)

Explanation:

VERIFY DB test # 61 found statistics defined on an index table.
This is strictly a no-no.

System Status:

VERIFYDB keeps running.

10-74

DU Class Messages

Recommendation:

VERIFY DB will automatically drop all tuples with this
base,index id from iistatistics unless in RUNINTERACTIVE
mode. Then user must enter YES/NO permission. Of course, no
correction is made if VERIFYDB is in REPORT mode.
SEE S_DU0326.

S- DU164A- NO- STATS- FOR- HISTOGRAM
There are no statistics associated with this histogram: htabbase = %Od, htabindex = % Id
Parameters:

%Od - base table id (from iihistogram.htabbase)
% Id - index table id (from iihistogram.htabindex)

Explanation:

VERIFY DB test # 65 could not find the entry in iistatistics for
this histogram.

System Status:

VERIFY DB keeps running.

Recommendation:

VERIFY DB will automatically drop all tuples with this
base,index id from iihistogram unless in RUNINTERACTIVE
mode. Then user must enter YES/NO permission. Of course, no
correction is made if VERIFYDB is in REPORT mode.
SEE S_DU0329.

S_DU164B_HISTOGRAM_SEQUENCE_ERR
There is a sequence error in iihistogram for table %Oc (owner % Ic) on attribute %2d.
Missing tuple for sequence # %3d. This means that part of the histogram is missing.
Parameters:

%Oc -- table name
% 1c -- table owner
%2d -- attribute number that histogram is for.
%3d -- missing sequence number

Explanation:

A histogram entry may be comprised of more than 1 tuple in
iihistogram. In such a case, each histogram entry has unique (and
sequential) hsequence values. VERIFY DB test #66 determined
that one (or more) of the expected seqvalues are missing.

System Status:

VERIFYDB keeps running.

Recommendation:

User should probably rerun the OPTIMIZEDB utility to.
regenerate this histogram. VERIFYDB will delete the histogram
tuples from iihistogram unless in RUNINTERACTIVE mode.
Then user must input Yes/No. Of course, no correction is made if
VERIFY DB is in REPORT mode.
SEE S_DU0329.

S_DU164C_NO_BASE_FOR_STATS
Base table id %Od, index id % Id that statistics are for is not listed in iirelation.
Parameters:

%Od - base table id (from iistatistics.stabbase)
% Id - index table id (from iistatistics.stabindex)

DU Class Messages

10-75

Explanation:

VERIFY DB test # 60 found that the table that these statistics are
compiled for doesn't exist (at least it's not listed in iirelation.)

System Status:

VERIFY DB keeps running.

Recommendation:

VERIFYDB will automatically drop all tuples with this
base,index id from iistatistics unless in RUNINTERACTIVE
mode. Then user must enter YES/NO permission. Of course, no
correction is made if VERIFYDB is in REPORT mode.
SEE S_DU0326.

S_DU164D _INVAL _SYS _CAT_ RELSPEC
DBMS system catalog %Oc has an invalid relspec of %ld
Parameters:

%Oc - name of DBMS system catalog
% Id - invalid relspec value (from iirelation.relspec)

Explanation:

VERIFY DB test # 4 found a system catalog with an invalid
relspec.

System Status:

VERIFY DB keeps running.

Recommendation:

VERIFYDB will automatically set the relspec to the correct
value unless in RUNINTERACTIVE mode. Then user must
enter YES/NO permission. Of course, no correction is made if
VERIFYDB is in REPORT mode.
SEE S_DU032A and S_DU032B.

S_DU164E_DUPLICATE_TREE_SEQ
There is a sequence error in iitree for tree %Od %ld: for table/view %2c (owner %3c)
Duplicate tuple for sequence # %4d
Parameters:

Explanation:

System Status:

VERIFY DB keeps running.

Recommendation:

VERIFYDB will automatically drop the tree tuples from iitree
unless in runinteractive mode, where user must give yes/no
permission for such a fix. Of course, no correction is made if
VERIFYDB is in REPORT mode.
SEE S_DU031C.

10-76

DU Class Messages

S_DU164F_QRYTEXT_SEQUENCE_ERR
There is a sequence error in iiqrytext for query id %Od %ld: Missing tuple for sequence #
%2d
Parameters:

%Od -- high portion of query id (from iiqrytext.txtid 1)
% Id -- low portion of query id (from iiqrytext.txtid2)
%2d -- missing sequence number

Explanation:

A query entry may be comprised of more than 1 tuple in
iiqrytext. In such a case, each query entry has identical txtid 1,
txtid2, and mode values, but has unique (and sequential) seq
values. VERIFYDB test #53 determined that one (or more) of
the expected seq values are missing.
NOTE: VERIFYDB cannot determine if the last (or last N)
tuples are missing from the query, as there is no place in iiqrytext
that gives a count of the number of query tuples expected.

System Status:

VERIFY DB keeps running.

Recommendation:

None required. However, user may wish to fix manually if user
knows how query should read. User may wish to delete the other
tuples for this query if user does not know how query should
read.

S_ DU16S0_ QRYTEXT_ DUP_ERR
There is a sequence duplication error in iiqrytext for query id %Od % Id: Duplicate tuple
for sequence # %2d
Parameters:

%Od -- high portion of query id (from iiqrytext.txtidl)
% Id -- low portion of query id (from iiqrytext.txtid2)
%2d -- missing sequence number

Explanation:

A query entry may be comprised of more than 1 tuple in iiqrytext.
In such a case, each query entry has identical txtid 1, txtid2, and
mode values, but has unique (and sequential) seq values.
VERIFYDB test #53 determined that one (or more) of the
expected seq values are duplicated.
NOTE: VERIFYDB cannot determine if the last (or last N)
tuples are missing from the query, as there is no place in iiqrytext
that gives a count of the number of query tuples expected.

System Status:

VERIFYDB keeps running.

Recommendation:

None required. However, user may wish to fix manually if user
knows how query should read. User may wish to delete the other
tuples for this query if user does not know how query should
read.

DU Class Messages

10-77

S_ DU1651_INVALID _IIHISTOGRAM
There are no statistics for any of the tables in this database. However, there are histograms.
Parameters:

None.

Explanation:

The tuples in iihistogram are used in conjunction with tuples in
iistatistics. If there are no tuples in iistatistics, then all of the
tuples in iihistogram are meaningless.

System Status:

VERIFYDB keeps running. However, it is unable to check each
tuple in iihistogram because the iihistogram logic requires the
iistatistics cache. And there is no cache for iistatistics. Therefore,
VERIFYDB does not check the status of each tuple in
iihistogram -- they're all useless anyhow, so skipping the checks
on them is harmless.

Recommendation:

VERIFY DB will automatically delete all tuples from iihistogram
in RUN or RUNSILENT modes. It will prompt the user for
permission to drop all iihistogram tuples in RUNINTERACTIVE
mode. The user must give or withhold permission. (I cant
imagine any reason in the world why the user would want to
withhold permission.)

S_ DU1652_HISTOGRAM _DUP _ERR
There is a sequence error in iihistogram for table %Oc (owner %lc) on attribute %2d.
Duplicate tuple for sequence # %3d.
Parameters:

%Oc -- table name
% 1c -- table owner
%2d -- attribute number that histogram is for.
%3d -- missing sequence number

Explanation:

A histogram entry may be comprised of more than 1 tuple in
iihistogram. In such a case, each histogram entry has unique (and
sequential) hsequence values. VERIFYDB test #66 determined
that one (or more) of the expected seq values are missing.

System Status:

VERIFY DB keeps running.

Recommendation:

User should probably rerun the OPTIMIZEDB utility to
regenerate this histogram. VERIFYDB will delete the histogram
tuples from iihistogram unless in RUNINTERACTIVE mode.
Then user must input Yes/No. Of course, no correction is made if
VERIFY DB is in REPORT mode. See S_DU0329.

S- DU1653RUN
-VERIFYDB

There are some dependencies on table %Oc (which is being dropped). To clean them up,
run: VERIFYDB -mruni -odbms -sdbn %lc
Parameters:

10-78

DU Class Messages

%Oc -- table name
% 1c -- database name

Explanation:

VERIFY DB is dropping this table. This will leave the database
in an inconsistent state because there will be a dependency on
this table in the system

System Status:

VERIFYDB keeps running.

Recommendation:

User must run VERIFYDB to clean up any inconsistencies left
over after this table is dropped.

S- DU1654- INVALID - USERNAME
ULTRIX/SQL user name '%Oc' is invalid.
Parameters:

%Oc -- user name

Explanation:

The user name has characters in it which are not legal for an
ULTRIX/SQL user name.

System Status:

VERIFY DB keeps running.

Recommendation:

SYSTEM Administrator should run ACCESSDB to see if any
users have been dropped. If so, use ACCESSDB to redefine them.

S- DU1655- INVALID - USERSTAT
Permissions for ULTRIX/SQL user' %Oc' are corrupted.
Parameters:

%Oc -- user name

Explanation:

iiuser.status has invalid bits set.

System Status:

VERIFYDB keeps running.

Recommendation:

Verifydb will clear invalid bits. However, there is a good chance
that the user's permissions may not be right if there were invalid
bits in the permission bitmap. SYSTEM Administrator should
run ACCESSDB to assure that user has correct permissions.

S- DU1656- INVALID - DBNAME
Database Name '%Oc' (owned by '%lc') is invalid.
Parameters:

%Oc -- database name
%Oc -- dba's name

Explanation:

The name of the database has been corrupted.

System Status:

VERIFY DB keeps running.

Recommendation:

Verifydb will ask for permission to remove this tuple from
iidatabase. In this case, the user should run finddbs to get the
database back. However, user must know which locations to tell
finddbs to search and also may need to use accessdb to assign
correct privileges to the db.

DU Class Messages

10-79

S- DU1657- INVALID- DBDEV

The default location name (%2c) for database '%Oc' (owned by '%Ic') is invalid.
Parameters:

%Oc -- database name
%Ic -- dba's name
%2c -- default location name (from iidatabase.dbdev)

Explanation:

The database's default data location in not known to the
INSTALLATION. This means that the server will not be able to
find the database.

System Status:

VERIFY DB keeps running.

Recommendation:

Verifydb will ask for permission to remove this tuple from
iidatabase. If the user thinks that the location is valid, they
should withhold permission to drop this database. Then they
should go in via ACCESSDB and add the location.

S- DU1658- INVALID - DBDEV

Database '%Oc' is owned by non-existent ULTRIX/SQL user: %Ic.
Parameters:

%Oc -- database name
% Ic -- database owner's name

Explanation:

The database's owner is not a valid ULTRIX/SQL user.

System Status:

VERIFYDB keeps running.

Recommendation:

Verifydb will ask for permission to remove this tuple from
iidatabase. If the user thinks that the user should exist, they
should not give permission to delete the database and should use
ACCESSDB to define the ULTRIX/SQL user.

S- DU1659 - MISSING - IIEXTEND

The default data location of %2c is not defined in the iiextend catalog for database %Oc
(owner % Ic).
Parameters:

%Oc -- database name
% Ic -- database owner's name
%2c -- default location

Explanation:

Every database has atleast one entry in iiextend for its default
location. There should be an entry for this database (its default
location has already been validated), but there is not. The correct
fix is to put the default location (from iidatabase.dbdev) into the
iiextend table. Verifydb will automatically do this for the user
unless in RUNINTERACTIVE mode. In that case, the user will
be prompted for yes/no permission.

System Status:

VERIFY DB keeps running.

Recommendation:

No action is required unless VERIFYDB is in runinteractive
mode. In that case the user must enter Yes/No permission before
verify will take any action.

10-80

DU Class Messages

S- DU165A- INVALID- CKPDEV
The checkpoint location name (%2c) for database '%Oc' (owned by '%lc') is invalid.
Parameters:

%Oc -- database name (from iidatabase.name)
% lc -- dba's name (from iidatabase.own)
%2c -- checkpoint location name (from iidatabase.ckpdev)

Explanation:

The database's checkpoint location in not known to the
INSTALLATION. This means that the server will not be able to
checkpoint this database.

System Status:

VERIFY DB keeps running.

Recommendation:

S_DU165B_INVALID_JNLDEV
The journal location name (%2c) for database '%Oc' (owned by '% lc') is invalid.
Parameters:

%Oc -- database name (from iidatabase.name)
% lc -- dba's name (from iidatabase.own)
%2c -- journal location name (from iidatabase.jn1dev)

Explanation:

The database's journal location in not known to the
INSTALLATION. This means that the server will not be able to
keep a journaling log for this database.

System Status:

VERIFY DB keeps running.

Recommendation:

S- DU165C- INVALID - SORTDEV
The sort location name (%2c) for database '%Oc' (owned by '%lc') is invalid.
Parameters:

%Oc -- database name (from iidatabase.name)
% lc -- dba's name (from iidatabase.own)
%2c -- sort location name (from iidatabase.sortdev)

Explanation:

The database's sort location in not known to the
INSTALLATION. This means that the server will not be able to
do sorts for this database.

System Status:

VERIFY DB keeps running.

Recommendation:

DU Class Messages

10-81

S- DU165D- DBA- HAS - NO - ACCESS
DBA %Oc does not have access to private DB % 1c.
Parameters:

%Oc -- database owner's name
% Ic -- database name

Explanation:

The only way to access a private database is to be explicately
permitted to access the db via a tuple in iidbaccess. CREATE DB
puts a tuple in iidbaccess for the DBA of a private database at
creation time. Any other users are given access to that DB via the
ACCESSDB utility. It is not reasonable for the owner of the
private database to be denied access to that DB. Therefore, the
missing iidbaccess tuple must be an error, and VERIFYDB will
automatically correct that, unless in RUNINTERACTIVE mode.
In that case, the user will be prompted for yes/no permission.

System Status:

VERIFY DB keeps running.

Recommendation:

No action is required unless VERIFY DB is in runinteractive
mode. In that case the user must enter Yes/No permission before
verify will take any action.

S- DU165EBAD
-DB
WARNING: Database %Oc (owner %lc) is inoperative. Use DESTROYDB to remove it
from the installation.
Parameters:

%Oc -- database name
%Ic -- database owner's name

Explanation:

The database is not usable. Either CREATEDB failed or
DESTROYDB failed. In either case, the user should run
DESTROYDB to remove it from the installation. If they want a
DB by that name, they can use CREATEDB to re-create it after
they have destroyed the inoperative version.

System Status:

VERIFYDB keeps running.

Recommendation:

No action is required. However, User may wish to remove
inoperative db from the installation via DESTROYDB.

S- DU165F- UNCONVERTED - DB
WARNING: 5.0 Database %Oc (owner %Ic) has not been converted yet. Use CONVT060
to make it operative in ULTRIX/SQL.
Parameters:

%Oc -- database name
% Ic -- database owner's name

Explanation:

The database is a 5.0 database and is not usable by the
ULTRIX/SQL installation. The user may wish to convert the
database to Vl.O (via CONVT060), or they may wish to leave it
a 5.0 database.

System Status:

VERIFYDB keeps running.

Recommendation:

No action is required.

10-82

DU Class Messages

S- DU1660- INCOMPATIBLE- DB
WARNING: Database %Oc (owner % Ic) is not compatible with ULTRIX/SQL 1.0.
Parameters:

%Oc -- database name
% Ic -- database owner's name

Explanation:

The database is not marked as operative, or as a convt060
candidate, and the database compatibility level is not valid. This
is a very serious corruption. First, try running "finddbs _rtf on the
db. If that does not work, attempt to recover the database from a
check-point. It may be possible to manipulate the iidbdb catalogs
to permit the server to access the db. If this is done, it is
imperative to unload the database, destroy it, recreate it, and
reload it.

System Status:

VERIFY DB keeps running.

Recommendation:

Try running "finddbs -r". If that does not pick up the DB
correctly, get the db back from a checkpoint/rollforward. If there
was not any checkpoint/joumaling on the db, please submit a
Software Performance Report (SPR).

S- DU1661- INOPERATIVE- DB
Database %Oc (owner % Ic) is not marked operative.
Parameters:

%Oc -- database name
% Ic -- database owner's name

Explanation:

The database is not marked operative, but there is not apparent
reason why it should not be marked operative. However, a
database may only be marked operative in RUNINTERACTIVE
mode if the user gives YES permission.

System Status:

VERIFYDB keeps running.

Recommendation:

User must give Yes/No permission in response to the prompt.

S DU1662 INCOMPAT MINOR

WARNING: Database %Oc (owner %Ic) has invalid minor compatibility level of %2d.
Parameters:

%Oc -- database name
% Ic -- database owner's name
%2d -- database's minor compatibility level

Explanation:

The database has an unreasonable minor compatibility level. The
minor compatibility level is how the server keeps track of what
the latest changes in the database are. This can be a serious or
trivial problem, depending on the reason that the compatibility
level is invalid.
The first thing to verify is that the user is running with the
correct version of VERIFYDB. This is the most likely reason for
this type of error if there is not much other corruption to the
iidatabase table. If the user is running with the correct version of

DU Class Messages

10-83

VERIFYDB, then it is the user should delete this tuple from
iidatabase and run finddbs -r to get the information back from
the config file.
System Status:

VERIFY DB keeps running.

Recommendation:

S- DU1663- ZERO- DBID
WARNING: Database %Oc (owner %Ic) has invalid database id of O. Run finddbs -r to
fix that problem.
Parameters:

%Oc -- database name
% Ic -- database owner's name

Explanation:

Each database should have a unique, nonzero database id. The
server uses database id to keep track of which database is
associated with a specific processing thread.

System Status:

VERIFY DB keeps running.

Recommendation:

Try running "finddbs -r". If that does not pick up the DB
correctly, get the db back from a checkpoint/rollforward.

S- DU1664- DUPLICATE- DBID
Database %Oc (owned by %Ic) has a database id of of %2d. This value should be unique
but is not. Run finddbs -r to fix that problem.
Parameters:

%Oc -- database name
% Ic -- database owner's name
%2d -- database id

Explanation:

Each database should have a unique, nonzero database id. The
server uses database id to keep track of which database is
associated with a specific processing thread.

System Status:

VERIFYDB keeps running.

Recommendation:

Try running "finddbs -r". If that does not pick up the DB
correctly, get the db back from a checkpoint/rollforward.

S- DU1665- NO - 2NDARY- INDEX
Database %Oc (owned by %Ic) does not have an entry in secondary index dbid_idx.
Parameters:

%Oc -- database name
% Ic -- database owner's name

Explanation:

The iidatabase table has a secondary index named iidbid_idx.
Each tuple in iidatabase must have a corresponding entry in
iidbid_idx. Either the entry is missing, or the tidp for the entry is
incorrect. In either case, iidbid_idx must be updated to match
iidatabase.

10-84

DU Class Messages

System Status:

VERIFY DB keeps running.

Recommendation:

None, unless in RUNINTERACTIVE mode. Then user must give
Yes/No permission before VERIFY DB can take corrective action.

S- DU1666- NO - IIDATABASE- ENTRY
There is no entry in iidatabase to correspond to the iidbid_idx tuple for db_id = %Od
Parameters:

%Od -- database id (from iidbid_idx.db_id)

Explanation:

The iidatabase table has a secondary index named iidbid_idx.
Each tuple in iidatabase must have a corresponding entry in
iidbid_idx. Each tuple in iidbid_idx must have a corresponding
entry in iidatabase. In this case, there was a tuple in iidbid_idx
with no corresponding tuple in iidatabase. In this case,
VERIFYDB will remove the entry form iidbid_idx.

System Status:

VERIFY DB keeps running.

Recommendation:

None, unless in RUNINTERACTIVE mode. Then user must give
Yes/No permission before VERIFYDB can take corrective action.

S- DU1667- WRONG- IIDBIDIDX - TID
The secondary index iidbid_idx (indexes iidatabase) has the wrong tid pointer for
database %Oc (owner % Ic). The tidp should be %2d, but is %3d.
Parameters:

%Oc -- name of database (from iidatabase.name)
% Ic -- database owner (from iidatabase.own)
% Id -- tid associated with iidatabase tuple
%2d -- iidbid_idx.tidp

Explanation:

The iidatabase table has a secondary index named iidbid_idx.
Each tuple in iidatabase must have a corresponding entry in
iidbid_idx. Each tuple in iidbid_idx must have a corresponding
entry in iidatabase. In this case, there was a tuple in iidbid_idx
had the wrong value for the tid pointer. Verifydb will update
iidbid_idx.tidp to the correct value.

System Status:

VERIFY DB keeps running.

Recommendation:

None, unless in RUNINTERACTIVE mode. Then user must give
Yes/No permission before VERIFYDB can take corrective action.

S_ DU1668_NONUSER_WITH_ACCESS
User '%Oc' has access to private database '%Ic'. However, this user is not a valid user.
Parameters:

% Ic -- name of private database (from iidbaccess.dbname)
%Oc -- ULTRIX/SQL user with access to private db (from
iidbaccess.usmame)

Explanation:

Table iidbaccess is used to specify which ULTRIX/SQL users
should have access to a private db. In this case, one of the users
specified does not happen to be a valid ULTRIX/SQL user in this
installation. Verifydb will automatically remove access for this

DU Class Messages

10-85

nonexistent user from the database, unless in
RUNINTERACTIVE mode.
System Status:

VERIFYDB keeps running.

Recommendation:

None, unless in RUNINTERACTIVE mode. Then user must give
Yes/No permission before VERIFYDB can take corrective action.

S- DU1669- NOSUCH - DB
User' %Oc' has access to private database ' % 1c'. However, there is no such database in
this installation.
Parameters:

%Oc -- ULTRIX/SQL user with access to private db (from
iidbaccess. usmame)
% Ic -- name of private database (from iidbaccess.dbname)

Explanation:

Table iidbaccess is used to specify which ULTRIX/SQL users
should have access to a private db. In this case, the specified
database does not exist in this installation. Verifydb will
automatically remove access for this user to the nonexistent
database, unless in RUNINTERACTIVE mode.

System Status:

VERIFY DB keeps running.

Recommendation:

None, unless in RUNINTERACTIVE mode. Then user must give
Yes/No permission before VERIFYDB can take corrective action.

S_DU166A_PRIV_NOT_GLOBAL
Private database '%Ic' (owned by '%Oc'), Is not marked as a private database.
Parameters:

%Oc -- ULTRIX/SQL user with access to private db (from
iidbaccess.usmame)
% Ic -- name of private database (from iidbaccess.dbname)

Explanation:

Table iidbaccess is used to specify which ULTRIX/SQL users
should have access to a private db. In this case, there is an entry
in iidbaccess for the owner of the database, which indicates a
private db. However, the iidatabase has this database marked as
GLOBAL (public). The database should be private if there is a
valid entry for it in iidbaccess. Verifydb will automatically mark
the database as a private database unless in R UNINTERACTIVE
mode.

System Status:

VERIFY DB keeps running.

Recommendation:

None, unless in RUNINTERACTIVE mode. Then user must give
Yes/No permission before VERIFYDB can take corrective action.

S_DU166B_INVALID _LOCNAME
'%Oc' is not a valid location name. (Associated area = '%Ic')
Parameters:

10-86

DU Class Messages

%Oc -- location logical name (from iilocations.lname)
% Ic -- physical translation of logical location name (from
iilocati ons. area)

Explanation:

Table iilocation keeps a list of ULTRIX/SQL location names and
what these names translate to. The user never refers to the
translated name, they always use the logical name to refer to a
location. Accessdb is the only utility that permits a user to
associate logical and physical names. ACCESSDB puts the
logical/physical pair into the config file when a database is
extended to a specific location. It uses the iilocations tuple to get
logical/physical values for this location.
In this case, the logical name has been corrupted to the point that
ULTRIX/SQL cannot use it to look up the physical area
associated with the logical. Verifydb will automatically remove
the tuple from iilocations. It will print the physical name (or
area) associated with the logical in the VERIFYDB log. The user
should use ACCESSDB to redefine the location.

System Status:

VERIFY DB keeps running.

Recommendation:

If in RUNINTERACTIVE mode, the user must give Yes/No

permission before VERIFY DB can take corrective action. After
the corrective action is taken, user should use ACCESSDB to
redefine the location.
NOTE: user must use same logical/physical names that the
location was previously defined at, as the location information is
in the config file. If the user does not know how the location
should be defined, do an ASCII dump on the config file to find
out. The config file resides in the database's default data location
and is file aaaaaaaa. cnf.
S- DU166C- BAD- LOC- STAT
Location' %Oc' has spurious bits set in the location status word. Status = % ld.
Parameters:

%Oc -- logical name of ULTRIX/SQL location (from
iilocations .lname)
% ld -- value of location status (fr an iilocations.status)

Explanation:

The status field indicates the type of location (DATA, SORT,
CKP, etc). Some of the bits that are not used have been set. This
means that the entire status for the location may be invalid, and
the user should use ACCESSDB to look at the location and
assure that it is defined correctly. Verifydb will clear unused bits
(to avoid confusing ACCESSDB), but this does not assure that
the location status is correct.

System Status:

VERIFYDB keeps running.

Recommendation:

None, unless in RUNINTERACTIVE mode. Then user must give
Yes/No permission before VERIFY DB can take corrective action.

DU Class Messages

10-87

S- DU166D- NOSUCH - DB
iiextend indicates that database '%Oc' is at location '% I c'. However, that database does
not exist.
Parameters:

%Oc -- database name (from iiextend.dname)
% Ic --location name (from iiextend.lname)

Explanation:

There is a tuple in iiextend for each location of each database in
the installation. If the database resides in only the default
location, there will be only one entry. If the database has been
extended to three locations, there will be 4 entries (one for the
default location, and one for each of the three extended
locations). Each entry consists of a database name and a location
name. The location name must also be in iilocations to be
meaningful. The database name must be in iidatabase to be
meaningful. Each location in iiextend for a database also resides
in the database configuration file (in the database's default
location.)
The config file is what the server uses to find extended locations,
but table iiextend is what ACCESSDB uses to define/display
them. Also, the server uses the entry for the default location from
iidatabase.dbdev to find the config file. This table must be in
synch with the config file and with table iidatabase. In this case,
the database name is not in iidatabase, or has been dropped by
VERIFYDB.

System Status:

VERIFY DB keeps running.

Recommendation:

If in RUNINTERACTIVE mode, the user must give Yes/No

permission before VERIFY DB can take corrective action. After
VERIFYDB has taken corrective action, the user should run
ACCESSDB to assure the database is defined correctly.
S- DU166E- NOSUCH- LOC
iiextend indicates that database '%Oc' is at location '% I c'. However, that location does
not exist.
Parameters:

%Oc -- database name (from iiextend.dname)
% Ic -- location name (from iiextend.lname)

Explanation:

10-88

DU Class Messages

The config file is what the server uses to find extended locations,
but table iiextend is what ACCESSDB uses to define/display
them. Also, the server uses the entry for the default location from
iidatabase.dbdev to find the config file. This table must be in
synch with the config file and with table iidatabase. In this case,
the location name is not in iilocations, or has been dropped by
VERIFYDB.
System Status:

VERIFY DB keeps running.

Recommendation:

If in RUNINTERACTIVE mode, the user must give Yes/No
permission before VERIFY DB can take corrective action. After
VERIFY DB has taken corrective action, the user should run
ACCESSDB to assure the database is defined correctly.

S_DU1700_NO_PURGE_AUTHORITY
WARNING: You C%Oc') do not have authority to purge database '%Ic' owned by '%2c'.
Parameters:

%Oc - name of ULTRIX/SQL user running VERIFY DB
% Ic - name of DB to be purged.
%2c - owner of db to be purged.

Explanation:

User does not have authority to purge this db. Only the DBA
may do so. However, any valid ULTRIX/SQL superuser may use
, -u' flag to become dba.

System Status:

Verifydb will not perform purge operation on this db, but will
continue on to attempt to process other dbs in scope list (if any).

Recommendation:

User should evoke VERIFYDB purge operation using "_u" flag
to specify proper dba name.

S- DU1701 - TEMP- FILE- FOUND
Temporary file %Oc found in location % 1c.
Parameters:

%Oc - file name
% Ic - location file resides in

Explanation:

Verifydb found a temporary file while purging a database.

System Status:

Verifydb will automatically purge this file in PURGE or
TEMP_PURGE operation unless mode restricts this. The
REPORT mode does not permit deletion of the file.
RUNINTERACTIVE mode requires user permission to drop the
file.

Recommendation:

If in RUNINTERACTIVE mode, user must enter YES/NO
permission. Otherwise no action is required.

S_DU1702_EXPIRED_TABLE_FOUND
Table %Oc (owned by % 1c) has expired.
Parameters:

%Oc - table name
% 1c - owner name

DU Class Messages

10-89

Explanation:

Verifydb found an expired relation while purging a database.

System Status:

Verifydb will automatically purge this table in PURGE or
EXPIRED_PURGE operation unless mode restricts this. The
REPORT mode does not permit destruction of this table.
RUNINTERACTIVE mode requires user permission to drop this
expired table.

Recommendation:

If in RUNINTERACTIVE mode, user must enter YES/NO

permission. Otherwise no action is required.
S_DU17FD _ CATALOG_PATCH_WARNING
WARNING: VERIFY operation DBMS_CATALOGS can result in loss of user tables
when used in the RUNINTERACTIVE mode. This program is designed to allow an
attempted recovery of an inconsistent database and is only for use by knowledgeable
users. This is not a supported utility.
If you do use the DBMS_CATALOGS operation of VERIFY DB in the
RUNINTERACTIVE mode, it is recommended that you back up your database before
proceeding.
Parameters:

None.

Explanation:

Legal disclaimer that should be printed every time the
DBMS_CATALOGS operation is specified. If the user has
selected the R UNINTERACTIVE mode, this will be followed by
a prompt asking the user if they wish to continue or abort.

System Status:

This is a warning message, not an error. Unless the user specifies
that they wish to stop VERIFYDB, VERIFYDB keeps
processing.

Recommendation:

If the user has not select RUNINTERACTIVE mode, no damage
will be done to the database, and no interaction is required. If the

user has specified the RUNINTERACTIVE mode, then the user
must answer a prompt asking whether or not they really want to
run VERIFYDB. If the user has NOT already backed up their
database, they should probably answer NO to the prompt, and go
do so. Then they can evoke VERIFYDB again. If the user was
running with checkpoints and journaling, it may be better to roll
back to the last checkpoint and recover their database via
journaling. The VERIFY DB patch option should NOT be used if
the user can recover via journaling.
S_DU17FE_FORCE_CONSISTENT_WARN
WARNING: VERIFYDB operation FORCE_CONSISTENT makes the database appear
consistent to the DBMS server but does not repair whatever caused the inconsistency to
occur. Users should immediately use UNLOADDB and move the data from this database
into a new database.
There is increased risk to data integrity if you continue using a database that has been
forced consistent.

10-90

DU Class Messages

Parameters:

None.

Explanation:

Legal disclaimer that the DBMS server cannot assure the
database will stay consistent after it has been marked
inconsistent and then forced consistent by VERIFYDB. If the
user continues using this database after forcing it consistent, it is
possible that the new work done may be lost at some future date.

System Status:

This is a warning message, not an error. Unless the user specifies
that they wish to stop VERIFYDB, VERIFY DB keeps
processing.

Recommendation:

If the user has not select RUNINTERACTIVE mode,

VERIFYDB will just print the warning message, and continue its
processing. If the user has specified the RUNINTERACTIVE
mode, then the user must answer a prompt asking whether or not
they really want to run VERIFYDB. If the user has journaling
enabled, they may perfer to roll back to the last checkpoint and
then use journaling to recapture the work they have done since
that checkpoint. If they do not have journaling enabled, then they
probably do want to force the database consistent. However,
once the database has been forced consistent, it should not be
used as though it had never been marked inconsistent.
The user is expected to use UNLOADDB to get their data out of
this database. They are expected to destroy this database and
recreate it, then run the reload.ing script that UNLOADDB
creates. If they keep using the database they have forced
consistent, they may run into future problems.

S_DU17FF_FIX_INTERACTIVELY
VERIFY DB cannot perform the recommended action unless the RUNINTERACTIVE
mode is selected. Please fix manually or rerun VERIFYDB with -mruninteractive
Parameters:

None.

Explanation:

The fix for this VERIFYDB test may only be performed in
runinteractive mode if the user gives Yes permission when
prompted for it. Since the current mode is not runinteractive, no
corrective active may be taken. This message is displayed in
Lieu of a prompt (by duve_talk) whenever the message type is
INTERACTIVE (permit fix only in interactive mode), and the
mode is liot RUNINTERACTIVE -- also will not be displayed if
mode is REPORT.

System Status:

VERIFY DB keeps running

Recommendation:

User may opt to manually take corrective action or to rerun
VERIFYDB in the runinteractive mode.

DU Class Messages

10-91

W - DU1800- STAR- CDB - NOT- FOUND
The coordinator database does not exist, destruction of '%Oc' continue ...
Parameters:

%Oc - distributed database name.

.Explanation:

Cannot finds the coordinator database in the system catalog. For
reasons unknown, the coordinator database name in the
iistar_cdbs was not found in the iidatabase.

System Status:

Aborts after removing entries of DDB from iistar_cdbs and
iidatabase.

Recommendation:

Only a warning, no action required.

W - DU1801 - SV- NO- DDB - SELECTED
No DDB has been selected yet, cannot 'Go' without a selected DDB Please Select a DDB.
Parameters:

None.

Explanation:

StarView: Select 'Go' when no DDB has being selected.

System Status:

Warning message.

Recommendation:

Select a DDB and then select 'Go' option.

W - DU1802- SV- BAD - NODENAME
Node name: '%Oc' is specified incorrectly.
Parameters:

%Oc - bad node name.

Explanation:

StarView: node name did not pass the valid name test.

System Status:

Warning message.

Recommendation:

Specify a node name correctly.

W - DU1803 - SV- BAD - DDBNAME
Distributed Database name: '%Oc' is specified incorrectly.
Parameters:

%Oc - bad DDB name.

Explanation:

StarView: DDB name did not pass the valid name test.

System Status:

Warning message.

Recommendation:

Specify a DDB name correctly.

W - DU1804- SV - CANT- GET - LDBLIST
Cannot obtain list of Local Databases from Distributed Database.
Parameters:

None.

Explanation:

StarView: Cannot get list of Local Database(LDB) information.

System Status:

Warning message.

Recommendation:

Check LDB permission or Network connection.

10-92

DU Class Messages

W - DU1805 - SV- CANT- OPEN- DDB
Cannot open Distributed Database '%Oc', check Lock.
Parameters:

DDB name.

Explanation:

StarView: Cannot open the specified DDB.

System Status:

Warning message.

Recommendation:

Check DDB lock, or existence.

W - DU1806- SV- CANT- DIRECT - CONNECT
Cannot direct connect to '%Oc'.
Parameters:

LDB orCDB.

Explanation:

StarView: Cannot direct connect to a LDB or CDB.

System Status:

Warning message.

Recommendation:

Check Server type.

W - DU1807- SV- CANT- GET- DDB- INFO
Cannot get information from Distributed Database '%Oc'.
Parameters:

Distributed Database Name.

Explanation:

StarView: Cannot obtain information from DDB.

System Status:

Warning message.

Recommendation:

Exit StarView and check the DDB.

W - DU1808- SV - CANT- GET- LDB - INFO
Cannot get information from Local Database '%Oc'.
Parameters:

Local Database Name.

Explanation:

StarView: Cannot obtain information from DDB.

System Status:

Warning message.

Recommendation:

Exit StarView and check the LDB.

W _DU1809 _SV _CANT_DIR_DISCONNECT
Cannot direct disconnect, please check if connected to STAR server.
Parameters:

None.

Explanation:

StarView: Having problem with direct connect.

System Status:

Warning message.

Recommendation:

Exit StarView and check the Name server, or Com Server.

DU Class Messages

10-93

W - DU180A- SV- CANT- OPEN- IIDBDB
Cannot connect to 'iidbdb', please check Local and Distributed installation.
Parameters:

None.

Explanation:

StarView: Cannot connect to iidbdb.

System Status:

Warning message.

Recommendation:

Exit StarView and check the Name server, or Com Server.

- DU180B- SV- CANT- DISCONNECT
Cannot disconnect, please check Local and Distributed server status.
Parameters:

None.

Explanation:

StarView: Can not disconnect.

System Status:

Warning message.

Recommendation:

Exit StarView and check the Name server, or Com Server.

W - DU180C - SV- CANT- OPEN- DDB
Cannot establish connection to Distributed Database
Parameters:

None.

Explanation:

StarView: Can not open DDB.

System Status:

Warning message.

Recommendation:

Exit StarView and check the Name server, or Com Server.

W - DU180D- SV- CANT- FIND- VNODE
Cannot find system attribute for II_GCNxx_LCL_ VNODE, please check STAR
installation.
Parameters:

None.

Explanation:

StarView: Can not obtain system attribute
II_GCNxx_LCL_VNODE.

System Status:

Warning message.

Recommendation:

Contact ULTRIX/SQL adminstrator of the installation.

BAD
W - DU180E- SV- ENTER-VNODE
Entered VNODE name is bad, please retry.
Parameters:

None.

Explanation:

StarView: Bad VNODE name encounter.

System Status:

Warning message.

Recommendation:

None.

10-94

DU Class Messages

W - DU180F- SV- CANT- DIRCONNECT- LDB
Cannot direct connect to Local Database ' %Oc' .
Parameters:

%Oc - Local database name.

Explanation:

StarView: Having problem with direct connect to local database.

System Status:

Warning message.

Recommendation:

Exit StarView and check the Name server, or Com Server.

W - DU1810- SV- CANT- CLOSE- DDB
Cannot disconnect from Distributed database, session could have been dropped.
Parameters:

None.

Explanation:

StarView: Can not disconnect.

System Status:

Warning message.

Recommendation:

Exit StarView and check the Name server, or Com Server.

W - DU1811 - SV- CURSOR- NOTIN-TABLE
Screen cursor is not in table field.
Parameters:

None.

Explanation:

StarView: The screen cursor in not in the appropriate table field.

System Status:

Warning message.

Recommendation:

Move cursor to the table field.

W - DU1812- SV- EMPTY- TABLE
Table is empty.
Parameters:

None.

Explanation:

StarView: Table is empty.

System Status:

Informational.

Recommendation:

None.

W - DU1813- SV- CANT- DROP- REG - TABLE
Error during remove operation on REGISTERED TABLE '%Oc'.
Parameters:

%Oc - object name.

Explanation:

StarView: Can not drop user specified registered object.

System Status:

Warning message.

Recommendation:

None.

DU Class Messages

10-95

W - DU1814- SV- CANT- DROP- TABLE
Error during remove operation on TABLE object '%Oc'.
Parameters:

%Oc - table name.

Explanation:

StarView: Can not drop table.

System Status:

Warning message.

Recommendation:

None.

W - DU1815- SV- CANT- DROP- VIEW
Error during remove operation on VIEW object '%Oc'.
Parameters:

%Oc - table name.

Explanation:

StarView: Can not drop view.

System Status:

Warning message.

Recommendation:

None.

W - DU1816- SV- CANT- REGISTER- TABLE
Error during remove operation on REGISTER object '%Oc'.
Parameters:

%Oc - table name.

Explanation:

StarView: Can not drop register table.

System Status:

Warning message.

Recommendation:

None.

W - DU1817- SV- ERROR-IN-CRITERIA
Error detected in the selection criteria, please reenter.
Parameters:

None.

Explanation:

StarView: Bad data encountered in Selection criteria.

System Status:

Warning message.

Recommendation:

Re-enter correct data.

W - DU1818- SV - DB - DOES - NOT- EXIST
Database does not exist, please try again with a different database.
Parameters:

None.

Explanation:

StarView: Database does not exist.

System Status:

Warning message.

Recommendation:

None.

10-96

DU Class Messages

W _DU1819 _SV _RM_NONE_REG_ OBJ
Cannot remove a none-register object.
Parameters:

%Oc - table name.

Explanation:

StarView: Can not remove registered object.

System Status:

Warning message.

Recommendation:

None.

W - DU181A- SV- CANT- REG - FROM- CRIT
Cannot register table from the given selection criteria, please try again.
Parameters:

None.

Explanation:

StarView: Can not register table from given criteria.

System Status:

Warning message.

Recommendation:

Re-enter criteria.

W - DU181B - SV- NONE- FUNCTIONAL
This part of StarView is not yet functional, but will be available in future releases.
Parameters:

None.

Explanation:

StarView: User come upon a option that is not yet functional.

System Status:

Warning message.

Recommendation:

Re-enter criteria.

W - DU181C - SV- CANT- REMOVE - INDEX
Star*View does not allow removal of INDEX objects
Parameters:

None.

Explanation:

StarView: Not allow removal of index object in Starview.

System Status:

Warning message.

Recommendation:

Re-enter criteria.

W - DU1830- STAR- DESTRY- CDB
Destroydb destroying a coordinator database.
Parameters:

None.

Explanation:

DDB in IIDATABASE has no matching tuple in IISTAR_CDBS.

System Status:

Warning message.

Recommendation:

No action.

DU Class Messages

10-97

W_DU1840_DDBTUPS_NOT_FOUND_FI
Distributed databases in IIDATABASE have no corresponding tuple in IISTAR_CDBS:
Parameters:

None.

Explanation:

CDB in IIDATABASE has no matching tuple in IISTAR_CDBS.

System Status:

Warning message.

Recommendation:

No action.

W - DU1841 - CDBTUPS- NOT- FOUND- FI
Coordinator databases in IIDATABASE have no corresponding tuple in IISTAR_CDBS:
Parameters:

None.

Explanation:

DDB in IISTAR_CDBS has no matching tuple in IIDATABASE.

System Status:

Warning message.

Recommendation:

No action.

W_DU1842_STARTUPS_NOT_FOUND_FI
Distributed entries found in IISTAR_CDBS not in the IIDATABASE catalog:
Parameters:

%Oc - database name.

Explanation:

IISTAR_CDBS contains more than one entry for the specified
database.

System Status:

Warning message.

Recommendation:

No action.

W - DU1843 - DUP- STARTUP- FI
The IISTAR_CDBS catalog in IIDBDB contains more than one entry for the database
'%Oc'.
Parameters:

None.

Explanation:

DDB in IIDATABASE has no corresponding coordinator
database inIISTAR_CDBS.

System Status:

Warning message.

Recommendation:

No action.

W - DU1844- DDBCDB - NOT- FOUND - FI
Distributed databases in IIDATABASE have no corresponding coordinator database:
Parameters:

%Oc - database name.

Explanation:

Failed because can not open database.

System Status:

Warning message.

Recommendation:

No action.

10-98

DU Class Messages

W - DU1845 - DBOPENFAIL
-FI
Unable to open database '%Oc' when testing for distributed database
Parameters:

%Oc - Distributed database name.

Explanation:

Can not restore distributed database in IIDATABASE.

System Status:

Warning message.

Recommendation:

No action.

W - DU1846- DDB - RESTOREFAIL
FI
>Unable to restore distributed database '%Oc' in IIDATABASE:
Parameters:

%Oc - distributed database name.

Explanation:

duplicate tuple was found in IIDATABASE when restoring
database.

System Status:

Warning message.

Recommendation:

No action.

W - DU1847- DDBDUPLICATEERROR
-FI
Duplicate tuple was found in IIDATABASE when restoring distributed database '%Oc':

E - DU2000BAD
-ERLOOKUP
Unknown database utility error number '%Ox'.

E - DU2001- BAD- ERROR- PARAMS
Bad error parameters passed to routine, ds_errorO.

E - DU2002- BAD - SYS- ERLOOKUP
Bad lookup of operating system error.

E_DU2003_BAD_ACT_JNL_DIR
Bad build of pathname for active journal directory %Oc % Ic

E - DU2004- BAD- CKPT- DIR
Bad build of pathname for checkpoint directory %Oc % Ic

E - DU2005- BAD - DFLTDB
-DIR
Bad build of pathname for default database directory %Oc % I c

E _ DU2006_BAD _XPIR _JNL _DIR
Bad build of pathname for expired journal directory %Oc % Ic

E- DU2007- BAD- EXT- DB - DIR
Bad build of pathname for extended database directory %Oc % Ic

DU Class Messages

10-99

E_DU2009_BAD _JNL_DIR
Bad build of pathname for journal directory %Oc % Ic
E - DU2410- GENCL
-FAIL
An unexpected error was returned from the CL routine '%Oc' when called from the
routine '% 1c ' .
E - DU2411BAD
-LOINGPATH
An error was encountered when trying to build an ULTRIX/SQL path to '%Oc %1c' .
E - DU2412- CANT- TRANSLATE- LOC
An error was encountered when trying to translate location '%Oc' into a pathname.
E - DU2414- BAD- CASE- LABEL
An unknown case label '%Od' was passed into the routine '% 1c' .
E - DU2415- BAD - DMP- DIR
Bad dump directory.
E - DU2FOO- TOO- MANY - ARGS
There were too many arguments, %Od, passed to the 6.0 phase of CONVT060.
E _ DU2008_BAD _FULL _JNL _DIR
Bad build of pathname for full journal directory %Oc % Ic
E - DU3000BAD
USRNAME
The user name, %Oc, is syntactically incorrect for the ULTRIX/SQL DBMS.
E - DU3001 - USER - NOT- KNOWN
The user, %Oc, is not known to this installation of the ULTRIX/SQL DBMS.
E - DU3002- ALIAS - NOT- KNOWN
The user alias, %Oc, is not known to this installation of ULTRIX/SQL.
E - DU3003- NOT - SUPER- USER
You are not authorized to use the super-user flag, '-s'.
E - DU3004- NO- ALIAS - FLAG
You are not authorized to use the alias flag, '-u'.
E - DU3010BAD
-DBNAME
The database name, %Oc, is syntactically incorrect for the ULTRIX/SQL DBMS.
E - DU3011 - NOT - DBA- DS
You, % Ic, cannot destroy a database whose DBA is, %Oc.

10-100

DU Class Messages

E - DU3012- NODS - DBDB- DS
The IIDBDB cannot be destroyed.
NO
DB NAME
E - DU3014No database name given.
E- DU3020- DB- NOT- FOUND
The database, %Oc, does not exist in this ULTRIX/SQL installation.
E - DU3021- DB - EXISTS - CR
The database, %Oc, already exists.
NO
E - DU3030-LOGNAME
There was no translation for the environment variable, %Oc.
E- DU3040- NO- DEF- DBLOC
The default data location, %Oc, for this database could not be found in the Illocations
catalog of the IIDBDB.
E_DU3041_NO_JNLLOC
The journaling location, %Oc, for this database could not be found in the Illocations
catalog of the IIDBDB.
E - DU3042NO
-CKPLOC
The checkpointing location, %Oc, for this database could not be found in the Illocations
catalog of the IIDBDB.
NO
E - DU3043-SORTLOC
The sorting location, %Oc, for this database could not be found in the Illocations catalog
of the IIDBDB.
E - DU3045BAD
-LOCNAME
Bad location name syntax, %Oc.
E- DU3046BAD
-DBLOC
The status for location, %Oc, indicates it is not configured for database files.
E - DU3047BAD
-CKPLOC
The status for location, %Oc, indicates it is not configured for checkpoint files.
E _ DU3048_BAD _JNLLOC
The status for location, %Oc, indicates it is not configured for journal files.
E - DU3049BAD
-SORTLOC
The status for location, %Oc, indicates it is not configured for sorting files.

DU Class Messages

10-101

E _ DU30S0_BAD _DMPLOC
Invalid dump location.
E- DU30S1NO
-DMPLOC
No dump location.
E- DU3060- NO- IIEXT- ENTRIES- DS
There were no entries in the IIextend system catalog of the IIDBDB for this database.
E - DU3064- NO- DBCAT- ENTRY - DS
There was no entry in the database system catalog of the IIDBDB for this database.
E - DU3070BAD
-COLLATION
The collation %Oc is invalid
Parameters:

Invalid collation name

Explanation:

The specified collation name was bad or did not exist

System Status:

Createdb does not continue

Recommendation:

Check installed collation sequences.

E- DU3080- DELETEDIR
-DS
The database directory, %Oc, could not be deleted.
E - DU3100- UCODE - OLDUSAGE
Old usage, '-u:', user codes are no longer recognized by the ULTRIX/SQL DBMS.
E - DU3101 - UNKNOWNFLAG
-DS
The command line flag, %Oc, is not known by the database utility, DESTROYDB.
E - DU3102- NO- CONFIRM- DS
Destruction of the database, %Oc, has been aborted.
E - DU3121 - UNKNOWNFLAG
CR
The flag '%Oc' is unknown to the database utility, CREATEDB.
E - DU3129- DBDB - NODMPLOC - CR
No dump location created.
E - DU3130- NO- CREATEDB- CR
You do not have 'CREATEDB' privilege.
E - DU3131 - MISSIING- DBDB
You must create the database database (iidbdb) before you may create any user databases.
Type: createdb -S iidbdb

10-102

DU Class Messages

E - DU3132- BAD - DBDBNAME- CR
The IIDBDB flag, '-S', cannot be used with database name, %Oc.

E - DU3133- NO- DBDB- FLAG- CR
The IIDBDB flag, '-S', must be used when creating the IIDBDB.

E - DU3134- DBDB - NOD BLOC - CR
You cannot specify a default data location for the IIDBDB.

E _DU3135 _ DBDB _ NOJNLLOC _ CR
You cannot specify a joumaling location for the IIDBDB.

E - DU3136- DB DB - NOCKPLOC- CR
You cannot specify a checkpoint location for the IIDBDB.

E - DU3137- DBDB - PRIVATE- CR
The IIDBDB cannot be made as a private database.

E - DU3138- DBDB - NOSORTLOC - CR
You cannot specify a default sorting location for the IIDBDB.

E - DU3140- DBDB- NOT- SUPERUSER- CR
Only a superuser can create the IIDBDB.

E - DU314A- CONFIG- TOO- BIG- CR
The configuration file was too large to be built.

E - DU3150- BAD - FILE- CREATE
The file, %Oc, couldn't be created.

E - DU3151- BAD - FILE- OPEN
The file, %Oc, couldn't be opened.

E - DU3152BAD
-SENSE
The header information for the file, %Oc, couldn't be read.

E - DU3153BAD
-READ
Bad read of the file, %Oc.

E - DU3154BAD
-ALLOC
Couldn't allocate a page for the file, %Oc.

E- DU3155BAD
-WRITE
Bad write to the file, %Oc.

DU Class Messages

10-103

E - DU3156BAD
-FLUSH
Couldn't flush the header for the file, %Oc.
E - DU3157BAD
-CLOSE
Couldn't close the file, %Oc.
E - DU3158- BAD - PAGE- NUM
Unexpected page number (%Od).
E - DU3170- BAD - USRF- OPEN
CL error, %Ox, opening the 'users' file.
E - DU3171 - USRF- NOT- FOUND
User, %Oc, was not found in the 'users' file.
E - DU3172- BAD- USRF- RECORD
Bad users record found in 'users' file.
E - DU3180- BAD - TEMPLATE- COpy
A CL error, %Ox, occurred in copying one of the template files.
E - DU3190BAD
-LKINIT
Couldn't initialize the locking system for this process.
Status returned was, %Ox.
Please insure that the process is properly installed and that
you have sufficient privilege and system resources to invoke it.
Parameters:

Value returned by call to LKinitialize.

Explanation:

DESTROYDB could not connect to the ULTRIX/SQL locking
system. Connection to the locking system may be rejected if
DESTROYDB is not installed (or run) with the proper privilege
or the lack of a critical system resource prevents
DESTROYDB's successful invocation.
For example, the former condition will occur on VMS if
DESTROYDB isn't installed with CMKRNL and on ULTRIX if
DESTROYDB isn't setuid ULTRIX/SQL. The latter condition
can occur on ULTRIX if the swap space available is insufficient
to allow DESTROYDB to map the shared memory segment used
for locking.

System Status:

Processing aborts.

Recommendation:

Consult your system administrator to insure proper
ULTRIX/SQL installation and ULTRIX configuration.

10-104

DU Class Messages

E_DU3191_BAD_LK_REQUEST
Bad lock request.
E - DU3192- BAD - LKLIST - RELEASE
Couldn't release active lock list.
E - DU3193- BAD - LKLIST - CREATE
Couldn't create the lock list.
E - DU3195DB
-LKBUSY
The database, %Oc, is currently unavailable.
E - DU31AO- BAD - DIRFILE- DELETE
A CL error, %Ox, occurred while deleting files of the directory, %2c, in the path, % I c.
E - DU31Al - BAD- DIR- DELETE
The directory, %Ic, in the path, %Oc, couldn't be deleted.
E - DU31A2- BAD- FILE- DELETE
The file, % Ic, in the directory, %Oc, couldn't be deleted.
E - DU31BO- BAD- DIR- CREATE
The directory, %Ic, in the path, %Oc, couldn't be created.
E - DU31COBAD
-LGOPEN
This utility could not open the log file.
E - DU31ClBAD
LGALTER
This utility could not alter infonnation in the log file.
E - DU31C2BAD
-LGADD
This database could not be added to the log file.
E - DU31C3BAD
-LGBEGIN
This utility could not start a transaction in the logging system.
E - DU31C4BAD
-LGEVENT
This utility was unable to wait for a logging event to occur.
E - DU31C5BAD
-LGCLOSE
This utility could not close the log file.
E - DU31C6BAD
-LGREMOVE
This utility was unable to remove the database from the log file.

DU Class Messages

10-105

E - DU31C7BAD
LGEND
This utility was unable to complete the transaction it had started.
E - DU31C8NO
-ARCHIVER
For a journaled database, the archiver has not finished journaling the data from the log to
the journals. Check to make sure archiver is still running.
E - DU31DO- DBID- MAXTRYS
A unique database id could not be determined.
E - DU3200BAD
-APPEND
Bad append to table, %Oc, in database, % 1c.
E- DU3201BAD
-REPLACE
Bad replace to table, %Oc, in database, % lc.
E - DU3202BAD
-DELETE
Bad delete from table, %Oc, in database, %Ic.
FLAG
E - DU3300- UNKNOWN-SY
The flag' %Oc' is unknown to the database utility, SYSMOD.
E DU3304 BAD SYSTEM CATALOG
There is no system catalog corresponding to the parameter' %Oc' .
E - DU3310- NOT- DBA- SY
You, % Ic, cannot SYSMOD a database whose DBA is, %Oc.
E - DU3312- DBDB - ONLY- CAT- SY
The system catalog '%Oc' can be sysmod only with the '%Ic' database.
E - DU3314- NOSUCHCAT
SY
The system catalog '%Oc' was listed as a parameter on the SYSMOD command line.
However, it doesn't exist in the database '%Ic'.
E - DU3400- BAD - MEM - ALLOC
Unable to allocate dynamic memory.
E - DU3500- TOO - MANY - ARGS - FI
Too many parameters were given on the command line for FINDDBS.
E - DU3501 - BAD - FLAG- FI
The flag '%Oc' is unknown to the database utility, FINDDBS.
E - DU3510- SAME- DBNAME- FI
If both db's are intended for this ULTRIX/SQL installation, one of them must be renamed.
10-106

DU Class Messages

E - DU3600- INTERRUPT
Interrupt -- aborting.
E - DU4000- BAD- STATF- READ
The contents of the CONVT060 status file could not be read.
FILE
E - DU4010- RENAME-EXISTS
The source file, %Oc, in the path, % 1c, could not be renamed to the target file, %2c. The
target file already exists.
E - DU4012- MAXAREA
The area, '%Oc' has a length greater than is allowed in ULTRIX/SQL V1.0.
E - DU4020- DATABASE- OPEN
The database (% Ic) was open when it should not have been. This error occurred in
procedure (%Oc) while attempting to reload QRYMOD definitions into the ULTRIX/SQL
database (% Ic).
E _ DU4021_CANT_OPEN _QRYMOD _FILE
CONVT060 could not open the file (%2) which should contain all the permit, view, and
integrity information to be reloaded into the database. This error occurred in procedure
(%Oc) called by (% Ic) while attempting to reload QRYMOD definitions into the
ULTRIX/SQL database (%3c).
E _ DU4022_BAD _QRYMOD_FILE_READ
CONVT060 could not read some portion of the file (%2) which should contain all the
permit, view, and integrity information to be reloaded into the database. This error
occurred in procedure (%Oc) called by (%Ic) while attempting to reload QRYMOD
definitions into the ULTRIX/SQL database (%3c).
E_DU4023_WRONG_DATABASE
CONVT060 encountered the wrong database name (%2c) in the QRYMOD reload file.
The correct database name should have been (% Ic). This error occurred in procedure
(%Oc) while attempting to reload QRYMOD definitions into the ULTRIX/SQL database
(%Ic).
E_DU4024_BAD_CHANGE_USER_FLAG
CONVT060 encountered a badly formated ULTRIX/SQL command in the QRYMOD
reload file. The scanned' -u' argument is (% Ic) but should have been (-uusemame). This
error occurred in procedure (%Oc) while attempting to reload QRYMOD definitions into
the ULTRIX/SQL database (%2c).

DU Class Messages

10-107

E_DUSOOO_INVALID_INPUT_NAME
INVALID NAME IN CMD INPUT LINE: %Oc
Parameters:

Null terminated character string containing input parameter

Explanation:

The database name or table name specified had a syntax error.
The correct syntax for database names is: "name1 name2 ...
name10" -- where 1 to 10 names may be specified The correct
syntax for specifying a table name is "tablename"

System Status:

Abort processing of VERIFY DB

Recommendation:

Rekey VERIFY DB command with correct syntax.

E - DUSOOI - INVALID- MODE- FLAG
INVALID MODE FLAG: %Oc
Parameters:

Null terminated character string containing input parameter

Explanation:

Valid values are: -mrun, -mrunsilent, .,mruninteractive, -mreport

System Status:

Abort processing of VERIFY DB

Recommendation:

Rekey VERIFY DB command with correct syntax.

E - DUS002- INVALID- SCOPE- FLAG
INVALID SCOPE FLAG: %Oc
Parameters:

Null terminated character string containing input parameter

Explanation:

Valid values are: -sdbname "name [name]", -sdba or
-sinstallation

System Status:

Abort processing of VERIFY DB

Recommendation:

Rekey VERIFY DB command with correct syntax.

E _DUS003 _INVALID_OPERATION_FLAG
INVALID OPERATION FLAG: %Oc
Parameters:

Null terminated character string containing input parameter

Explanation:

Valid values are: -odbms_catalogs, -oforce_consistent,
-opurge,-otemp_purge, -oexpired_purge, -otable name

System Status:

Abort processing of VERIFYDB

Recommendation:

Rekey VERIFY DB command with correct syntax.

E_DUS004_TOO_MANY_NAMES_IN_LIST
Too many names in list. Max is 10.
Parameters:

None.

Explanation:

A maximum of 10 names may be specified with the -sdbname
flag. Maximum of 1 name may be specified with the -otable flag.
The correct syntax is "name 1 name2 name3 name4 ... name 10"

10-108

DU Class Messages

or "name 1." The list starts and ends with a quote. There is
exactly one space separating each name in the list. Null lists are
not valid.
System Status:

Abort processing of VERIFYDB

Recommendation:

Rekey VERIFYDB command with correct syntax

E- DU5005- SPECIFY- ONLY 1 NAME
Only 1 table name may be specified with -otable.
Parameters:

None.

Explanation:

A maximum of 10 names may be specified with the -sdbname
flag. A maximum of 1 name may be specified with the -otable
flag. The correct syntax is "name 1 name2 name3 name4 ...
name 10" or "name 1" The list starts and ends with a quote. There
is exactly one space separating each name in the list. Null lists
are not valid.

System Status:

Abort processing of VERIFYDB

Recommendation:

Rekey VERIFY DB command with correct syntax

E- DU5006- UNKNOWN- PARAMETER
invalid parameter is VERIFYDB input line
Parameters:

None

Explanation:

A flag that VERIFYDB does not recognize was input The only
valid input flags for VERIFY DB are: -m or -mode, -s or -scope,
-0 or -operation, -u or -user (optional)

System Status:

Ignore flag, print warning

Recommendation:

None

E DU5007 SPECIFY ALL FLAGS
-VERIFYDB must be evoked with -m, -s and -0 flags: VERIFY DB -ModeXXX
-Scope YYY -OperationZZZ AME g where:
XXX = REPORT, RUN, RUNSILENT, RUNINTERACTIVE
YYY = DB NAME (followed by list of up to 10 names in double quotes),
DBA, INSTALLATION
ZZZ = DBMS_CATALOGS, FORCE_CONSISTENT, DROP_TABLE

< > denotes optional flag.
Parameters:

None

Explanation:

VERIFY DB must be evoked with -m, -s and -0 flags. Defaults
are not permitted

System Status:

Stop VERIFYDB processing

Recommendation:

Reenter VERIFY DB command with correct parameters
DU Class Messages

10-109

E - DU5008- SPECIFY- TABLE- NAME
You must specify a table along with the -otable flag: The format is -otable 'table_name'
Parameters:

None

Explanation:

When the table operation is selected, VERIFY DB must be
informed of the name of the table to operate on.

System Status:

Stop VERIFYDB processing

Recommendation:

Reenter VERIFYDB command with correct parameters

E - DU5009- SPECIFYDB
-NAME
You must specify at least one database along with the -sdbname flag: The format is
-sdbname 'tablel [table2 ... tablelO],
Parameters:

None

Explanation:

When the dbname scope is selected, VERIFY DB must be
informed of the name(s) of the database(s) to operate on. The
user may specify from 1 to MAX_NAMES (in duvdb.h)
databases. If more are specified, all database names in the list
that exceed the limit are ignored.

System Status:

Stop VERIFY DB processing

Recommendation:

Reenter VERIFYDB command with correct parameters

E - DU5010- NO- SYSCAT- FILE
Fatal error. The disk file for system catalog %Oc is not found. VERIFYDB will proceed as
far as it can before crashing.
Parameters:

%Oc - name of system catalog (from iirelation.relid)

Explanation:

A disk file for one of the system catalogs cannot be found. This
means that VERIFYDB will not be able to perform all of its
checks on system catalogs.

System Status:

VERIFY DB will keep running as long as it can -- the length of
time depends on which system catalog is missing. When it
cannot continue any longer, it will take an exception exit.

Recommendation:

Try to get a backup of the missing system catalog file

E - DU501A- CANT- CONNECT
Unable to connect with database %Oc.
Parameters:

%Oc - name of database (specified on VERIFYDB command line
with -t parameter)

Explanation:

Unable to connect to the specified database

System Status:

VERIFY DB could not connect to the database specified by the
user.

Recommendation:

Reevoke the VERIFYDB utility, but specify a valid database
name.

10-110

DU Class Messages

E - DUSOIB - CANT- CONNECT- AS - USER
Unable to connect with database %Oc as user % Ic.
Parameters:

%Oc - name of database (specified on VERIFY DB command line
with -t parameter)
% Ic - usemame (supplied on VERIFY DB command line with -u
parameter. )

Explanation:

Unable to connect to the specified database as specified user.

System Status:

VERIFY DB could not connect to the database specified by the
user.

Recommendation:

Reevoke the VERIFYDB utility, but specify a valid database
name and/or a valid user.

E - DUSOIC - EMPTY- IIRELATON
FATAL ERROR: the iirelation system catalog is empty. If database is checkpointed, use
ROLLFORWARDDB backup to recover.
Parameters:

None.

Explanation:

Table iirelation is a core DBMS catalog. Without it, it is not
possible to access the data in the database. This is a very severe
error.

System Status:

VERIFYDB will stop processing, as it is not possible to act on
this database.

Recommendation:

User should attempt to recover the contents of the iirelation file
using ROLLFORWARDDB utility (or the contents of a backup
tape for file aaaaaaab.tOI for location ii_database, if database not
checkpointed. )

E - DUSOID - SCOPENOT
-IMPLEMENTED
Sorry, this scope function is not implemented yet.
Parameters:

None.

Explanation:

Not all of the VERIFY DB features are implemented yet. The
only scope feature implemented at this time is dbname.

System Status:

VERIFY DB will stop processing

Recommendation:

User should rekey the VERIFYDB command using -sdbname
scope.

E - DUSOIE- OP- NOT- IMPLEMENTED
Sorry, this operation is not implemented yet.
Parameters:

None.

Explanation:

Not all of the VERIFY DB features are implemented yet. The
only operations implemented at this time are system catalog
checks and forcing a database consistent.

DU Class Messages

10-111

System Status:

VERIFY DB will stop processing

Recommendation:

User should rekey the VERIFYDB command using an
implemented"VERIFYDB operation.

E - DUSOIF- CATALOG- CHECK- ERR
VERIFYDB: Fatal error encountered while attempting to check/patch DBMS catalogs for
database %Oc
Parameters:

%Oc - name of database.

Explanation:

VERIFY DB was not able to check/patch the system catalogs
completely.

System Status:

VERIFY DB will stop processing

Recommendation:

User should attempt to use ROLLFORWARD from checkpoint to
recover db.

E - DUS020- DB - PATCH - ERR
VERIFY DB : fatal error encountered while attempting to patch database %Oc consistent.
VERIFY DB failed, and database is still inconsistent.
Parameters:

%Oc - name of database.

Explanation:

VERIFY DB was not able to patch the database consistent.

System Status:

VERIFY DB will stop processing

Recommendation:

User should attempt to use ROLLFORWARD from checkpoint to
recover db.

E - DUS021 - EMPTY- IITREE
FATAL ERROR: the iitree system catalog is empty. If database is checkpointed, use
ROLLFORWARDDB backup to recover.
Parameters:

None.

Explanation:

Table iitree is a core DBMS catalog that describes view
definitions for the standard catalogs. If it is empty, then the
standard catalogs are corrupted. This is a very severe error.

System Status:

VERIFY DB will stop processing, as it is not reasonable to act on
this database.

Recommendation:

User should attempt to recover the contents of the iitree file
using ROLLFORWARDDB utility.

10-112

DU Class Messages

E - DUS022- EMPTY - IIDBDEPENDS
FATAL ERROR: the iidbdepends system catalog is empty. If database is checkpointed,
use ROLLFORWARDDB backup to recover.
Parameters:

None.

Explanation:

Table iidbdepends is a core DBMS catalog that describes view
definitions for the standard catalogs. If it is empty, then the
standard catalogs are corrupted. This is a very severe error.

System Status:

VERIFY DB will stop processing, as it is not reasonable to act on
this database.

Recommendation:

User should attempt to recover the contents of the iitree file
using ROLLFORWARDDB utility.

E - DUS023- CANT- OPEN- LOG- FILE
Unable to open VERIFYDB log file. The log file may already be in use by another
VERIFY DB session. Try running VERIFYDB later, or run without the log file (use the -n
flag on command line).
Parameters:

None.

Explanation:

VERIFY DB was not able to open the VERIFYDB log file
(currently living at ii_config:iivdb.log). This is usually caused
because someone else is running a VERIFYDB session and is
using that log file. If you wait a while and try again, it will
probably work.
If you would rather not wait, it is possible to run VERIFYDB

without the log file (I don't recommend this as a regular
practice) by using the -n flag before any of the other VERIFYDB
parameters.
Example: if your command line was
VERIFY DB -mruni -sdbn testl -odbms
then type:
VERIFY DB -n -mruni -sdbn testl -odbms
System Status:

VERIFY DB considers it an error if it is unable to open its log
file. In such a case, VERIFYDB will print this error message and
terminate processing. VERIFYDB will never print this error if
the -n flag is used.

Recommendation:

The best thing to do is to see if anyone else in the installation is
running VERIFYDB. If so, wait til they're finished. If not, check
the logical ii_config to assure that its valid (an undefined or
improperly defined ii_config will also cause this message. Of
course, you can always bypass logging by using the -n flag.
However, VERIFYDB outputs lots of messages, so this is a last
resort.

DU Class Messages

10-113

E - DUS024- TBL - DROP- ERR
Unable to destroy table %Oc from database % Ic.
Parameters:

%Oc - name of table
% I c - name of database that table is in.

Explanation:

VERIFYDB was not able to open delete the table from the
system catalogs.

System Status:

VERIFY DB terminates

Recommendation:

The best thing to do is to verify that the table really exists,
because nonexistent tables are usually why VERIFY DB cant
drop the table.

E - DUS02S- NO- SUCH- TABLE
Table %Oc (owner % I c) does not exist.
Parameters:

%Oc - name of table
%Ic - name of table's owner

Explanation:

The table does not exist in the specified database.

System Status:

VERIFY DB terminates (it cannot drop a nonexistent table)

Recommendation:

Perhaps the table is owned by another user. Determine who the
owner is and run VERIFY DB again, this time using the -u flag.

E - DUS026- EMPTY- IIUSER
FATAL ERROR: the iiuser database database catalog is empty. If database is
checkpointed, use ROLLFORWARDDB backup to recover. Or, use accessdb to define
users for this installation.
Parameters:

None.

Explanation:

Table iiuser defines the users for an installation. If the table is
empty, then no one is authorized to run on this installation. THIS
IS A SEVERE ERROR. ACCESSDB should be usable (it can use
the $II_SYSTEM/sql/files/users table to recover system
administrator information. Then the system administrator will
need to manually add all of the users. It is better to recover the
iiuser table from backup, if possible.

System Status:

VERIFY DB will stop processing, as it is not reasonable to act on
this database.

Recommendation:

User should attempt to recover the contents of the iiuser file

10-114

DU Class Messages

E - DU5027- CMPTLVL- MISMATCH
Unable to run VERIFYDB on database %Oc due to Major Compatibility Level mismatch.
Verifydb is at level=% lc, and the database is at level=%2c
Parameters:

%Oc - database name
% lc - VERIFYDB's major compatibility level
%2c - database's major compatibility level

Explanation:

You are trying to run the wrong verision of VERIFYDB for this
database. Verifydb's minor and major compatibility levels must
be GREATER than or EQUAL TO the database's level.

System Status:

VERIFYDB will stop processing for this database, as it is not
reasonable to act on this database.

Recommendation:

User should restore the correct version of VERIFY DB from
distribution.

E - DU5028- CMPTMINOR- MISMATCH
Unable to run VERIFYDB on database %Oc due to Minor Compatibility Level mismatch.
Verifydb is at level=% ld, and the database is at level=%2d
Parameters:

%Oc - database name
% ld - VERIFYDB's minor compatibility level
%2d - database's minor compatibility level

Explanation:

You are trying to run the wrong verision of VERIFYDB for this
database. Verifydb's minor and major compatibility levels must
be GREATER than or EQUAL TO the database's level.

System Status:

VERIFY DB will stop processing for this database, as it is not
reasonable to act on this database.

Recommendation:

User should restore the correct version of VERIFYDB from
distribution.

E - DU5029- EMPTY- IIDATABASE
FATAL ERROR: the iidatabase catalog is empty. If database is checkpointed, use
ROLLFORWARDDB backup to recover. Or, use accessdb to define users for this
installation.
Parameters:

None.

Explanation:

Table iidatabase defines the dbs for an installation. If the table is
empty, then are no databases in the installation, including the one
we are currently examining.THIS IS A SEVERE ERROR.

System Status:

VERIFYDB will stop processing, as it is not reasonable to act on
this database.

Recommendation:

User should attempt to recover the contents of the iidatabass file

DU Class Messages

10-115

E - DUS02A- PURGE- ERR
VERIFY DB : Fatal error encountered while attempting to purge database %Oc
Parameters:

%Oc - name of database.

Explanation:

VERIFY DB was not able to purge temporary or expired relations
in db.

System Status:

VERIFYDB will stop processing

Recommendation:

User should attempt to rerun.

E - DUS02B - CANT- MAKE- PURGELIST
VERIFY DB : Fatal error encountered while attempting to build internal purgelist cache.
Parameters:

None.

Explanation:

VERIFY DB was not able to purge temporary or expired relations
in db.

System Status:

VERIFY DB will stop processing

Recommendation:

This is probably caused by lack of dynamic memory. User
should increase dynamic memory for this process, then attempt
to rerun.

E - DUS02C - UNABLE - TO- DELETE- FILE
VERIFYDB: FATAL ERROR. Unable to delete temporary file '%Oc' from directory
'%Ic' (database %2c, ULTRIX/SQL location '%3c')
Parameters:

%Oc - filename
% Ic - pathname to directory containing file
%2c - name of database file associated with
%3c - location file resides in.

Explanation:

Verifydb was attempting to purge a temporary file. DIdeleteO
failed to delete this file.

System Status:

This is a fatal error -- VERIFYDB stops processing

Recommendation:

User should retry VERIFYDB. If it still fails, user should start
looking at why -- is this a read only directory, is verifiydb
installed (on VMS) or suitable privileged, etc.

E - DUS02D - NOFREE- PURGETABLE
VERIFYDB: FATAL ERROR. Unable to create temp table in name-range of '%Oc to
'%Ie'
Parameters:

%Oe - lowest temp table name
% Ie - max temp table name

Explanation:

Verifydb must create a temporary table (owned by $ingres). The
name of that table must fall between the lower and upper table
names -- verifydb uses a lookup table of possible names. In this
case, the db already had tables owned by $ingres with all of the
names that verifydb has in its lookup table.

10-116

DU Class Messages

System Status:

This is a fatal error -- VERIFY DB stops processing

Recommendation:

User must free up one of these table names. If these are temp
tables, then delete them. If not, copy one table to something else,
drop that table, run verifydb, recreate the table and copy the data
back.

E - DU5100- STAR- CDB - DEST- ONLY
Cannot destroy coordinator database '%Oc'. Destroy the distributed database '% Ie'
instead.
Parameters:

%Oc - coordinator database name.
% Ie - distributed database name.

Explanation:

User can not destroy a coordinator database, the only way to
destroy a coordinator database is through destroying its
distributed database.

System Status:

Processing aborts, no destruction occur.

Recommendation:

User should consider destroying the distributed database if
he/she really wants to destroy the coordinator database.
NOTE: A DESTROYDB of a regular ULTRIX/SQL or BE will
destroy the coordinator database without knowing.

E - DU5101 - STAR- CANT- DEST- CDB
Can not destroy database '%Oc', which is a Coordinator database.
Parameters:

%Oc - coordinator database name.

Explanation:

User is attempting to destroy a database that is a Coordinator
datavbase.

System Status:

Processing aborts, no destruction occur.

Recommendation:

User cannot destroy a coordinator database without destroying a
distributed database.

E - DU5102- STAR- DDB - DONT- EXIST
Destributed entry of '%Oc' does not exist in iidatabase.
Parameters:

%Oc - distributed database name.

Explanation:

Can not destroy DDB because there is no DDB entry in
iidatabase.

System Status:

Processing aborts, no destruction occur.

Recommendation:

None.

E - DU5108- STAR- DDB - NAME - TOO- LONG
Distributed database name is longer then %Od characters, cannot construct coordinator
database name because the result will be too long. Please specify the coordinator database
name by: CREATEDB [-S] [-uname] [-p] [-ddb_Iocationname] [-cckp_Iocationname]
[-jjnl_Iocationname] ddbname/d [cdbname]
DU Class Messages

10-117

E_DUS109_STAR_INVALID_NAME

Parameters:

%Od - maximum length of distributed database name.

Explanation:

If the user does not supply a CDBname, distributed CREATEDB

will attempt to construct one from the DDBname by prepending
'ii' in front of it. This message means that the resulting
CDBname will be too long for a database name.
System Status:

Processing aborts.

Recommendation:

User can reenter the DDBname or specify a CDBname.

E - DU5109- STAR- INVALID- NAME
%Oc database name '% 1c' is an invalid database name.
Parameters:

%Oc - text, "Distributed" or "Coordinator".
% 1c - name of the distributed or coordinator database.

Explanation:

Encounters an invalid database name, will specify if it is the
DDBname or CDBname that's invalid.

System Status:

Processing aborts.

Recommendation:

User can reenter a valid DDBname and/or specify a valid
CDBname.

E - DU510A- STAR- CDB - ALREADY - EXIST
Database name' %Oc' already exists, cannot use as coordinator database.
Parameters:

%Oc - coordinator database name.

Explanation:

name specified as coordinator database name already exist as an
entry in the 'iidatabase' system catalog.

System Status:

Processing aborts.

Recommendation:

User can reenter the DDBname or specify a CDBname.

E - DU510B - STAR - DDB - ALREADY - EXIST
Database name '%Oc' already exists, cannot use as distributed database.
Parameters:

%Oc - distributed database name.

Explanation:

name specified as distributed database name already exist as an
entry in the 'iidatabase' system catalog.

System Status:

Processing aborts.

Recommendation:

User can reenter the DDBname or specify a CDBname.

E - DU510C - STAR- DBDB - NOT- LEGAL
Illegal distributed database name '%Oc'.
Parameters:

%Oc - distributed database name.

Explanation:

Can not use 'DBDB' or 'IIDBDB' as CDB or DDB name.

10-118 DU Class Messages

System Status:

Processing aborts.

Recommendation:

User can reenter the DDBname or specify a CDBname.

E_DUSI0D_STAR_DDB_EQS_CDB
Distributed database name is equal to the coordinator database name.
Parameters:

None.

Explanation:

When user specified distributed database name is equal to the
coordinator database name.

System Status:

Processing aborts.

Recommendation:

User can reenter the DDBname or specify a CDBname.

E- DUSI0E- STAR- TOO - MANY- ARGS
Too many database name specified.
Parameters:

None.

Explanation:

When encountering too many CDB names after DDB name on
the command line.

System Status:

Processing aborts.

Recommendation:

User can reenter the DDBname or specify a CDBname.

E - DUSI0F- STAR- CANT - FIND - VNODE
Cannot obtain value for II_GCNxx_LCL_VNODE, (xx is installation code). Please define
or check with DBA.
Parameters:

None.

Explanation:

NMgtAt on II_GCNxx_LCL_VNODE return illegal value. This
should be set to the node name.Example: on VMS node name is
rabbit and ii_installation = zz. define/group ii_gcnzz_lcl_vnode
"rabbit"

System Status:

Processing aborts.

Recommendation:

Check with DBA or define II_ GCNxx_LCL_VNODE.

E - DUSII0- SV- NOT- STAR- SERVER
Current server is not a STAR server.
Parameters:

None.

Explanation:

Current Server is a LDB server.

System Status:

Processing aborts.

Recommendation:

Check with Installation.

DU Class Messages

10-119

E- DU51111- SV- CANT- OPEN- IIDBDB
Cannot open iidbdb in the current installation, please check permission or locks ..
Parameters:

None.

Explanation:

can not open iidbdb.

System Status:

Processing aborts.

Recommendation:

Check with DBA for permissions.

E - DU5112- SV- BAD- START- NAME
Illegal database name to start Star*View..
Parameters:

None.

Explanation:

Bad database name construct for Star*View parameter.

System Status:

Processing aborts.

Recommendation:

Check with DBA for permissions.

10-120

DU Class Messages

EO Class Messages

E- EOOOOI - hcDEFINE

The #define statement may be used only with values, not names.Use typedef if you wish
to make '%Oc' a synonym for a type.
Explanation:

The #define directive accepts only integer, floating point or
string literals as the replacement token. You may not use
arbitrary text as the replacement token. To define type names you
should use typedef.
The embedded preprocessor #define is not as versatile as the C
#define.

E- E00002- hcIGNCAST

Cast of #define value is ignored.
Explanation:

The preprocessor ignores a cast of the replacement value in a
#define statement. Casts in general are not supported by the
embedded C preprocessor. Remove the cast from the #define
statement.

E- E00003 - hcINDIR

Incorrect indirection on variable '%Oc'.
Variable is subscripted, [], or dereferenced, *, %lc time(s) but declared with indirection
of%2c.
Explanation:

This error occurs when the address or value of a variable is
incorrectly expressed because of faulty indirection. For example,
the name of an integer array has been given instead of a single
array element, or, in the case of character string variables, a
single element of the string (ie, a character) has been given
instead of a pointer to the string or the name of the array. Either
redeclare the variable with the intended indirection, or change its
use in the current statement.

E- E00004- hcSTRUCTREF

Last component of structure reference '%Oc' is illegal.
Explanation:

This error occurs when the preprocessor encounters an
unrecognized name in a structure reference. The user may have

EO Class Messages

11-1

incorrectly typed the name of structure element, or may have
failed to declare it to the preprocessor.
Check for misspellings in component names and that all of the
structure components have been declared to the preprocessor.
E- EOOOOS- hcUNCLOSED

Unclosed C block - %Oc unbalanced left brace(s).
Explanation:

The preprocessor reached the end of the file still expecting one
or more closing curly braces '} , . Make sure that you have no '{'
in an unclosed character or string constant, or have not
accidentally commented out a closing curly brace.
Also remember that the preprocessor ignores #ifdef directives, so
having several '{' in alternate paths of an #ifdef will confuse the
preprocessor.
Balance curly braces declared to the preprocessor.

E- E00006- hcNOFUNCDEC

Unsupported forward declaration of C function '%Oc'.
Explanation:

The preprocessor does not support function declarations. For
example, the declaration:
##

int funcO;

will cause this error.
Remove the ## mark from the function declaration.
E- E00007 - hcNESTFUNCDEF

Unsupported definition of nested C function '%Oc'. Check for missing closing brace of
preceding function.
Explanation:

The preprocessor does not support nested function definitions.
This error commonly occurs when the user has omitted the ##
mark on the closing brace of the previous function definition.
Check that functions to be defined to the preprocessor have
opening and closing braces.

E_E00008_hcVCHIGNRE

Incorrect declaration of C varchar variable is ignored. The members of a varchar structure
variable may consist only of a short integer and a fixed length character array.
Explanation:

11-2

EO Class Messages

Varchar variables (variables declared with the varchar storage
class) must conform to an exact varying-length string template
so that ULTRIX/SQL can map to and from them at run-time. The
length field must be exactly two-bytes (derived from a short),
and the character string field must be a single-dimensioned C

E_E00009 _hcMISSEQUAL

character array. The varchar clause must be associated with a
variable declaration and a not a type definition or structure tag
declaration.
Check the varchar structure declaration. Make sure that both
structure members are declared properly.
E_E00009 _hcMISSEQUAL

Missing '=' in the initialization part of a C declaration.
Explanation:

The preprocessor allows automatic initialization of variables and
expects the regular C syntax. Insert an equals sign between the
variable and the initializing value.

EO Class Messages

11-3

E1 Class Messages

E EIOOOI hffiADTYPE

Unsupported FORTRAN type '%Oc' used. DOUBLE assumed.
ULTRIX/SQL does not support the FORTRAN types COMPLEX and DOUBLE
COMPLEX.
Explanation:

There is no ULTRIX/SQL type corresponding to COMPLEX or
DOUBLE COMPLEX, so the preprocessor does not map this
declaration to an ULTRIX/SQL type.

System Status:

The preprocessor will continue to generate code as if you had
declared the variable in question to be of type DOUBLE
PRECISION. Upon completion, the preprocessor will return a
FAIL status.

Recommendation:

Do not make this declaration visible to the preprocessor unless
necessary. If you want to store the two REAL (or DOUBLE
PRECISION) components of a COMPLEX (or DOUBLE
COMPLEX) variable then declare a pair of REAL (or DOUBLE
PRECISION) variables to the preprocessor, copy the components
to them, and then store the copies.

E- EI0002- hIDEFINE

FORTRAN PARAMETER may only be used with values.
Type names, variable names, and PARAMETER names are not allowed.
Explanation:

You have used the FORTRAN "PARAMETER name = value"
statement, but "value" is not an integer constant, a floating
constant, or a string constant. You may have used the name of a
FORTRAN data type, or a variable (or PARAMETER) name
instead of one of the legal constant types.

System Status:

The statement is ignored. Upon completion, the preprocessor
will return a FAIL status.

Recommendation:

Do not make this statement known to the preprocessor if you do
not use the name being defined in any ULTRIX/SQL statement.
If you do wish ULTRIX/SQL to know about this name then you
must change the "value" to be a constant.

E1 Class Messages

12-1

E- EI0003- hfiNDIR
Incorrect indirection on variable '%Oc'.
The variable is declared as an array and is not subscripted, or is subscripted but is not
declared as an array (% Ic, %2c).
Explanation:

This error occurs when the value of a variable is incorrectly
expressed because of faulty indirection. For example, the name
of an integer array has been given instead of a single array
element, or, in the case of string variables, a single element of
the string (ie, a character) has been given instead of the name of
the array.

System Status:

The preprocessor will continue to generate code, but the program
will not execute correctly if it is compiled and run. Upon
completion, the preprocessor will return a FAIL status.

Recommendation:

Either redeclare the variable with the intended indirection, or
change its use in the current statement.

E - EI0004 - hfSTRUCTREF
Last FORTRAN structure field referenced in '%Oc' is unknown.
Explanation:

This error occurs when the preprocessor encounters an
unrecognized name in a structure reference.

System Status:

The preprocessor will continue to generate code, but this
statement will either cause a run-time error or produce the wrong
result if the resulting program is compiled and run. Upon
completion, the preprocessor will return a FAIL status.

Recommendation:

Check for misspellings in field names and ensure that all of the
structure fields have been declared to the preprocessor.

E- EI0005 - hfUNCLOSED
Unclosed FORTRAN block - %Oc unbalanced END(s).
Explanation:

The preprocessor reached the end of the file still expecting one
or more closing END statements. Make sure that you have no
'ENDs' in an unclosed character or string constant, or have not
accidentally commented out a closing END.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Balance each PROGRAM, PROCEDURE, or FUNCTION
statement with a closing END.

E- EI0006- hfNESTFUNCDEF
Unsupported definition of nested FORTRAN function' %Oc'.
Explanation:

ESQL read the beginning of a subprogram (PROGRAM,
PROCEDURE, or FUNCTION) while still in a previous
subprogram definition.

System Status:

Upon completion, the preprocessor will return a FAIL status.

12-2

E 1 Class Messages

Recommendation:

Ensure that the END statement for a previous subprogram
definition is not missing. PASCAL programmers should
remember that FORTRAN does not allow nested subprogram
definitions.

E- EI0007- hIDECLARE

No ## DECLARE before first ESQL/FORTRAN statement '%Oc'.
Explanation:

You must issue a ## DECLARE statement lexically before any
ULTRIX/SQL statement.

System Status:

The generated will probably not compile. Upon completion, the
preprocessor will return a FAIL status.

Recommendation:

Issue a DECLARE statement anywhere a declaration would be
legal before you issue any ULTRIX/SQL statement.

E- EI0008- hfREDECLARE

Reissue of ## DECLARE in FORTRAN program unit.
The second declaration is ignored.
Explanation:

The DECLARE statement should be issued exactly once in each
FORTRAN program unit. This can also be caused by forgetting
to ## the PROGRAM, PROCEDURE, or FUNCTION line (and
the matching END).

System Status:

ESQL will ignore the extraneous DECLARE statement. Upon
completion, the preprocessor will return a FAIL status.

Recommendation:

Remove the extra DECLARE statement, or ## the subprogram
head and END.

E- EI0009 - hIDECFORMS

No ## DECLARE FORMS before forms statement '%Oc' in FORTRAN program unit.
Explanation:

You must issue a ## DECLARE FORMS statement lexically
before any FORMS statement.

System Status:

The generated will probably not compile. Upon completion, the
preprocessor will return a FAIL status.

Recommendation:

Issue a DECLARE FORMS statement anywhere a declaration
would be legal before you issue any FORMS statement.

E- EIOOOA- hfNOSTRUCT

Undefined structure name '%Oc' used in RECORD declaration.
Explanation:

You have declared a RECORD variable using the name of a
STRUCTURE that is unknown to the preprocessor.

System Status:

The preprocessor will continue to generate code, but the
resulting program will not run properly. Upon completion, the
preprocessor will return a FAIL status.

E 1 Class Messages

12-3

Recommendation:

If you do not use this variable with an ULTRIX/SQL statement

then remove the record declaration. Otherwise ensure that the
corresponding STRUCTURE declaration is made known to the
preprocessor.

E- EIOOOB - hfELEM
Field '%Oc' in record '%lc' is not an elementary variable.
Explanation:

RECORD variables used in SQL as a single object must contain
only scalar fields. Arrays and nested records are not allowed in
this context.
Example:
EXEC SQL BEGIN DECLARE SECTION
structure /object/
character* 10 oname
integer
ovals(4)
end structure
record /object/ obj
EXEC SQL END DECLARE SECTION
EXEC SQL SELECT * INTO :obj FROM objects
This will cause an error on "obj.oname", as it is an array variable.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Either flatten the record variable declaration or enumerate all
fields when using the variable.

E - EIOOOC - hffiADSIZE
Illegal length specified for FORTRAN numeric variable.
Explanation:

FORTRAN integer variables may be either 1,2, or 4 bytes, and
floating- point variables may be either 4 or 8 bytes. Specifying
any other value is illegal.

System Status:

Upon completion, the preprocessor will return a FAIL status.

12-4

E1 Class Messages

E6 Class Messages

E- E60001 - haMUSTINDIR
The ADA variable '%Oc' is an array and must be subscripted.
Explanation:

A variable declared as an array must be subscripted when
referenced. The preprocessor does not confirm that you use the
correct number of subscripts. A variable declared as a
I-dimensional array of characters, must not be subscripted as it
refers to a character string.

E- E60002- haCANTINDIR
The ADA variable' %Oc' is not an array and must not be subscripted.
Explanation:

A variable not declared as an array cannot be subscripted. You
cannot subscript string variables in order to refer to a single
character or a slice of a string (sub-string).

E- E60003 - haBADTYPE
The ADA identifier' %Oc' is not a declared type.
Explanation:

The identifier was used as an ADA type name in an object or
type declaration. This identifier has not yet been declared to the
preprocessor and is not a preprocessor-predefined type name.

E- E60004- haCHARDIMS
The ADA CHARACTER variable '%Oc' must be a I-dimensional array.
Explanation:

Variables of type CHARACTER can only be declared as
I-dimensional arrays. You cannot use a single character or a
multi-dimensional array of characters as an ULTRIX/SQL string.
Note that you can use a multidimensional array of type STRING.

E- E6000S - haDIGITS
The ADA DIGITS clause '%Oc' is out of the range 1..16.
Explanation:

Embedded ADA supports D_FLOAT floating point variables.
Consequently, all DIGITS specifications must be within the
specified range.

E6 Class Messages

13-1

E _ E60006_haINCPKG
Statement '%Oc' is embedded in INCLUDE file package specification.
Explanation:

Preprocessor INCLUDE files may only be used for ADA
package specifications. The preprocessor generates an ADA
WITH clause for the package. No executable statements may be
included in the file because the code generated will not be
accepted by the ADA compiler in a package specification.

E _ E60007 _ haNMOVERFLOW
Too many names (%Oc) in ADA identifier list. Maximum is %lc.
Explanation:

ADA identifier lists cannot have too many names in the
comma-separated name list. The name specified in the error
message caused the overflow, and the remainder of the list is
ignored. Rewrite the declaration so that there are fewer names in
the list.

E - E60008 - haNMUNDERFLOW
The ADA identifier list has come up short.
Explanation:

The stack used to store comma separated names in ADA
declarations has been corrupted. Try rearranging the list of
names in the declaration.

E - E60009 - haNOTINITED
The ADA CONSTANT declaration of '%Oc' must be initialized.
Explanation:

CONSTANT declarations must include an initialization clause.

E - E6000A- haNOTVAR
The ADA identifier '%Oc' is either a constant or an enumerated literal.
Explanation:

The named identifier was used to retrieve data from
ULTRIX/SQL. A constant, an enumerated literal and a formal
parameter with the IN mode are all considered illegal for the
purpose of retrieval.

E _ E6000B _ haBADRECALL
The ADA variable '%Oc' with' .ALL' clause is illegal.
Explanation:

The ADA .ALL clause, as specified with access objects, can be
used only if the variable is an access object pointing at a single
scalar-valued type. If the type is not scalar valued, or if the
access object is pointing at a record or array, then the use of
.ALL is illegal.

E _ E6000C _haSCALRECALL
The ADA variable '%Oc' with '.ALL' clause is not a scalar type.

13-2

E6 Class Messages

Explanation:

E - E6000D - haRECORDREF
Last component in ADA record qualification '%Oc' is illegal.
Explanation:

The last component referenced in a record qualification is not a
member of the record. If this component was supposed to be
declared as a record, the following components will cause
preprocessor syntax errors.

E - E6000E- haRNMBAD
In ADA RENAMES statement, '%Oc' must be a constant or a variable.
Explanation:

The target object of a RENAMES statement must be a constant
or a variable, and the item being declared is used a synonym for
the target object.

E - E6000F- haRNMCOMPAT
In ADA RENAMES statement, object is incompatible with type.
Explanation:

The type of the target object in the RENAMES statement must
be compatible in base type, size and array dimensions with the
type name specified in the declaration.

E - E60010- haRNMMANY
Only one name may be declared in an ADA RENAMES statement.
Explanation:

One object can rename only one other object.

E - E60011- haUNCLOSED
Unclosed ADA block. There are %Oc block(s) left open.
Explanation:

If a file is terminated early or the END statement closing an
ADA compilation unit is missing, this error will occur. If syntax

errors were issued while parsing the compilation unit header,
correct those errors first.

E - E60012- haUNDEC
The ADA variable '%Oc' has not been declared.
Explanation:

The named identifier was used where a variable must be used to
set or retrieve ULTRIX/SQL data. The variable has not yet been
declared.

E6 Class Messages

13-3

E_E60013_haTYPUNSUPP
The ADA type %Oc is not supported.
Explanation:

Some ADA types are not supported because they are not
compatible with the ULTRIX/SQL run-time system.

E - E60014- haVARRECORD
The ADA variable '%Oc' is a record, not a scalar value.
Explanation:

The named variable qualification refers to a record. It was used
where a variable must be used to set or retrieve ULTRIX/SQL
data. This error may also cause syntax errors on record
component references.

E - E60016 - ha UNSUPP
The ADA statement %Oc is not supported.
Explanation:

13-4

E6 Class Messages

Statements that modify the internal representation of variables
that interact with ULTRIX/SQL are not supported.

EQ Class Messages

E_EQOOOl_eqNOMEM

Fatal memory allocation error in routine '%lc'.
The product has run out of memory after requesting %Oc bytes for internal data.
Explanation:

A memory allocation or free error has occurred somewhere in the
code in a place where it was unexpected, or where it was not
possible to recover from the error. This may indicate an internal
coding error or a program that is too large.

System Status:

The preprocessor will abort.

Recommendation:

Check your system quotas. If you suspect they might be too low,
try to break up the input file or the embedded language blocks. If
the preprocessor still fails, please submit a Software 8
Performance Report (SPR).

E _EQ0002_ eqNOTABLE

Fatal attempt to access internal table.
No host code generator table is defined in the preprocessor.
Explanation:

A required internal data structure could not be accessed. This
may be caused by an incorrectly linked preprocessor image or an
internal coding error.

System Status:

The preprocessor will abort.

Recommendation:

Please submit a Software Performance Report (SPR).

E_EQ0003_eqNULL

Null type pointer in routine '%Oc'.
An internal symbol has not been initialized or has been reset.
Explanation:

An internal symbol can not be accessed. This may be caused by
an internal coding error.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

If the preprocessor reported syntax errors, correct them and
repreprocess your file. If the error occurs again, please submit a

Software Performance Report (SPR).

EQ Class Messages

14-1

E _ EQ0004_eqTRA CEFL
Conflicting %Oc '-to' and '-tl' options.
Explanation:

This error is caused by an inconsistent use of the internal trace -t
flag when invoking the preprocessor. Under normal
circumstances it should not be necessary to use trace flags.

System Status:

The preprocessor will exit without preprocessing the input file.

Recommendation:

Retype the preprocessor command line using the correct flags.

E _ EQOOOS_ eqINFILE
%Oc input file '% 1c' cannot be opened.
Error in location or name of file or you have no read permission.
Explanation:

The preprocessor cannot find the input file named on the
command line. The location/directory path specified may be
incorrect, the file name itself may be incorrectly entered, or the
file may be non-existent. An extremely long path name will also
cause this error.

System Status:

The preprocessor will exit without preprocessing the input file.

Recommendation:

Retype the preprocessor command line correctly specifying the
input file.

E _ EQ0006_ eqOUTOPT
Conflicting %Oc '-f' options.
You cannot direct both to the standard output channel and to a file.
Explanation:

This error occurs when the -f flag is used twice on the command
line, once without an argument and once with a file name. For
example:
preproc -f -foutfilename
Note that if the the -f flag is not used, the preprocessor will
create an output file with the default name.

System Status:

The preprocessor will exit without preprocessing the input file.

Recommendation:

Select the appropriate output option and retype the preprocessor
command line.

E _ EQ0007_ eqOUTFILE
Cannot open %Oc output file '% 1c' .
Check write permission and -f flag argument, if used.
Explanation:

14-2

EQ Class Messages

Output files cannot be opened if a user does not have write
privileges. If the -f flag was specified, the location or directory
path given must be a legal location. There may be other system
dependent reasons why a file cannot be opened.

System Status:

The preprocessor will exit without preprocessing the input file.

Recommendation:

Attempt to open a file with the same name at the system level
and take note of the system response.

E - EQ0008- eqLISTFILE
Cannot open %Oc listing file '% 1c ' .
Check write pennission.
Explanation:

The listing file is opened in the same directory as the input file,
and the user must have write pennission in this location. There
may be other system dependent reasons why a file cannot be
opened.

System Status:

The preprocessor will exit without preprocessing the input file.

Recommendation:

Attempt to open a file with the same name at the system level
and take note of the system response.

E - EQ0009- eqBADOPT
Invalid or missing %Oc option: % 1c.
Explanation:

The user has invoked the preprocessor with a non-existent flag
or missing command line option.

System Status:

The preprocessor will exit without preprocessing the input file.

Recommendation:

Retype the preprocessor command line with the correct flags.

E_EQOOI O_eqC APAB
No ULTRIX/SQL capability for the %Oc/% lc preprocessor.
Explanation:

Based on the installed ULTRIX/SQL authorization key you are
not allowed to use this preprocessor.

System Status:

The preprocessor will exit without preprocessing the input file.

Recommendation:

Check with your ULTRIX/SQL system administrator for
preprocessor usability.

E _ EQOOll_eqSAMEFLl
Input and Output files are both %Oc.
System Status:

The preprocessor will exit without preprocessing the input file.

Recommendation:

Retype the preprocessor command line specifying different input
and output files.

E- EQ0012- eqSAMEFL2
Input and Listing files are both %Oc.
System Status:

The preprocessor will exit without preprocessing the input file.

Recommendation:

Retype the preprocessor command line specifying different input
and listing files.

EQ Class Messages

14-3

E _ EQ0013_ eqSAMEFL3
Output and Listing files are both %Oc.
System Status:

The preprocessor will exit without preprocessing the input file.

Recommendation:

Retype the preprocessor command line specifying different
output and listing files.

E _ EQOOSl_grDISPTL
DISPLAY statement target list is not supported.
To retrieve run-time information from the FRS, use the INQUIRE_FRS command.
Explanation:

The ULTRIX/SQL DISPLAY statement arguments (such as
_FIELD and _TYPE) are no longer supported and you may not
use a target list in a DISPLAY statement. The INQUIRE_FRS
statement allows you to retrieve the equivalent information.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Correct the syntax of the DISPLAY statement in the embedded
program.

E - EQOOS2- grFMFUNC
Illegal context for Forms '%Oc' function.
You have incorrectly placed the '%Oc' function within another statement.
Explanation:

The forms functions, such as GETOPER, which retrieves
relational operators from fields and table fields, may be legally
used as follows:
GETFORM form (var = GETOPER(field), ... )
GETROW form table [row] (var = GETOPER(column), ... )
This also applies to the PUTOPER function.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Correct the syntax of the current statement.

E - EQOOS3 - grFMINTFUNC
Forms '%Oc' function is integer valued.
You must use an integer variable for the result of this function.
Explanation:

The variable used to receive the result of the above FRS function
has a type other than integer.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Correct the current syntax to use an integer variable which has
been declared to the preprocessor.

14-4

EQ Class Messages

E - EQ0054- grNOPARENS
Empty parentheses are ignored.
No parentheses are required on empty target lists.
Explanation:

Some statements have optional target lists. In some cases, when
empty target lists are used, this warning is displayed.

System Status:

The preprocessor will ignore the parentheses and will return a
SUCCESS status if no other errors occur during preprocessing.

Recommendation:

Remove the unnecessary parentheses.

E- EQ0055 - grFMPARAM
Illegal context for PARAM clause in forms statement.
You may not use the PARAM clause in this statement.
Explanation:

In the languages that support PAR AM target lists, not all forms
target lists have a PARAM equivalent. The statements that have a
PARAM equivalent are documented in the preprocessor manual.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Rewrite the forms target list using host variables declared to the
preprocessor instead of the PARAM clause.

E _ EQ0056_gr FORMNAME
Form name required for %Oc statement.
The %Oc statement used outside of a DISPLAY loop requires a form name.
Explanation:

A forms I/O statement that is syntactically outside of a DISPLAY
loop requires a form name specification. Inside the DISPLAY
loop the currently displayed form is assumed if no form is
specified. This error may also occur if the DISPLAY statement
contained a syntax error.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Check the syntax on the DISPLAY statement. Otherwise, include
a form name in the statement, or move the statement inside a
DISPLAY loop.

E - EQ0057 - grHOSTVAR
'%Oc' expected to be a simple variable.
Use a scalar numeric or character string variable instead of '%Oc'.
Explanation:

The named identifier was used in an I/O statement, but was not
declared to the preprocessor as a scalar numeric or character
string variable.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Declare the identifier as a variable to the preprocessor.

EQ Class Messages

14-5

E_EQ0058_grINLOOP
The %Oc statement must be in a % 1c loop.
Explanation:

Some statements (such as ENDLOOP) that syntactically belong
inside a specific loop or block cannot be issued outside the loop
or or block, as they generate host language GOTO statements.
Also, a syntax error on the block or loop statement will cause
this error to occur on subsequent statements.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Correct any bad syntax on the block (ie, DISPLAY) statement.
Otherwise, move the statement producing the error inside the
correct block statement.

E _ EQ0059_gr INT
Integer variable, constant or literal expected.
The identifier' %Oc' was used instead of an integer value.
Explanation:

The current statement requires an integer value or variable. You
have used a non-integer variable or an identifier which has not
been declared to the preprocessor as a variable.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Substitute an integer value or a variable which has been declared
to the preprocessor.

E _ EQ0060_gr INTSTRVAR
Integer or character string expected.
Type of variable' %Oc' should be an integer or a character string.
Explanation:

The current statement requires an integer or character string
variable or value. You have used a variable of some other type.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Substitute an integer or character string (variable or literal).

E _ EQ0061_gr INTVAR
Type of variable '%Oc' should be an integer.
Explanation:

You have used a variable of some other type than integer. The
current statement requires the use of an integer variable.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Substitute an integer variable for the wrongly-typed variable.

14-6

EQ Class Messages

E - EQ0062- grNAME
Variable '%Oc' used when name expected.
Try dereferencing the variable name by preceding it with a '#'.
Explanation:

This is a common error in ESQL, where an object name (ie,
database column or fonn field) has the same name as a numeric
variable.
The preprocessor will never issue this error when a character
string variable is used because object names can be stored inside
string variables.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Dereferencing the variable with the # sign will cause the name to
be used and not the contents of the named variable.

E - EQ0063- grNESTQUEL
Illegal nesting of database statements.
The '%Oc' statement appears in a data retrieval query loop.
Explanation:

This error occurs when a database query is coded within the
scope of a database data retrieval loop statement (SELECT or
RETRIEVE). The statements that may be placed within the data
retrieval loop are fonns statements, the INQUIRE/SET status
statements and the loop break statements (ENDSELECT or
ENDRETRIEVE).

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Move the flagged statement outside the scope of the data
retrieval loop.

E - EQ0064- grQRSTRVAR
'%Oc' expected to be a character string variable.
Query text can be replaced only by string variables.
Explanation:

When replacing parts of a query, such as a WHERE clause, the
specified replacement must be a string variable.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Replace the variable marked as an error with a string variable
declared to the preprocessor.

E _EQ0066_grSTR

String constant expected instead of '%Oc' .
Explanation:

Either a numeric variable or an unquoted name was used instead
of a string variable or quoted string.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Use quotation marks around the flagged name or a string
variable.
EQ Class Messages

14-7

E_EQ0067_grSTRVAR
Object named' %Oc' should be a character string variable.
Explanation:

The current statement requires the use of a character string
variable to retrieve results or replace a string literal.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Substitute a character string variable, declared to the
preprocessor, for the name flagged as an error.

E _ EQ0068_gr UNLOADTB
Illegal nesting of UNLOADTABLE statements.
You may not code an UNLOADTABLE statement within the scope of another
UNLOADTABLE statement.
Explanation:

Because of run-time implementation considerations, an
UNLOADTABLE statement cannot appear within the block of
another UNLOADTABLE.
Note that the dynamic nesting of UNLOADTABLE statements
(ie, via a subroutine call) is also not allowed and will cause a
run-time error.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Code UNLOADTABLE statements consecutively instead of
nesting them.

E_EQ0069_grBADWORD
Illegal word '%Oc' in % I c statement.
The keyword %2c is assumed.
Explanation:

Some statements have words that are reserved only within the
context of the statement. Misspelling or misplacing the word will
generate the above message.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Update the statement to use the correct keyword.

E_EQ0070_grMISSWORD
Missing word '%Oc' in % I c statement.
Explanation:

Some statements have "noise" words or operators that are
expected in some contexts.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Update the statement to reflect the correct syntax.

14-8

EQ Class Messages

E_EQ0071_grASSGNOP

Assignment operator should be '=', not '%Oc'.
Explanation:

This statement requires the use of the equals sign to indicate that
the value from a field in a form is to be assigned to a program
variable. Some older versions of the preprocessor allowed other
words (IS, BY) in this context.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Correct the statement to use the '=' assignment operator.

E _EQ0072_grNONULL
Incorrect use of indicator variable.
Indicators may be used only in conjunction with host program variables.
Explanation:

This error occurs when a null indicator is used with a variable or
identifier representing an object name. Null indicators may be
used only on I/O statements in conjunction with program
variables transmitting data. Their purpose is to send/receive null
data to or from the database or a form .

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Remove the flagged null indicator from the current statement.

E_EQ0073_grINDVAR

Indicator variable '%Oc' must be a 2-byte integer.
Explanation:

You have used an indicator variable which is either a non-integer
or is the wrong size.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Use an indicator variable which has been declared to the
preprocessor as a 2-byte integer.

E_EQ0074_grMISVAR

Incorrect use of variable '%Oc' in '% 1c' statement.
Explanation:

You have used a variable together with names or string literals in
a context Where the preprocessor expects either a single
character variable, a string literal, or one or more unquoted
identifiers.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Correct the syntax so that the clause in question appears as
unquoted identifiers, a quoted string literal or a string variable.

EQ Class Messages

14-9

E- EQ0075- grFUTUNSUPP
The '%Oc' statement will be discontinued.
Future releases of the preprocessor will not support this statement.
Explanation:

Refinements to the query language and forms system statements
are made from time to time. Functionality is always preserved by
offering alternate statements.

System Status:

The preprocessor will preprocess the current statement correctly
and will return a SUCCESS status if no other errors occur during
preprocessing.

Recommendation:

See the manual for an alternative to the statement you have used.

E_EQ0076_grNOWUNSUPP
The '%Oc' statement is not supported.
Its use has been discontinued or is not supported in this host language.
Explanation:

You have used a statement which is not supported in this release.
The statement has either been superseded by an alternate
statement or was never available in preprocessors in the
particular host language.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Remove the current statement and repreprocess.

E - EQ0077 - grISUNSUPP
This style of %Oc statement is not supported.
The syntax of this statement has been updated.
Explanation:

The statement is one that previously supported an old and a new
syntax. The old syntax is not supported anymore.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Refer to the manual for the correct syntax of this statement.

E _ EQ0078_grSTYUNSUPP
This style of %Oc statement will be discontinued.
In future releases, the preprocessor will expect an updated syntax.
Explanation:

The statement has been supported in two forms. In future, the old
syntax will not be supported.

System Status:

The preprocessor will preprocess the current statement correctly
and will return a SUCCESS status if no other errors occur during
preprocessing.

Recommendation:

See the manual for the alternative syntax for this statement.

14-10

EQ Class Messages

E _EQ0079_grCONNECTID
Incorrect WITH clause containing the distributed transaction id.
Explanation:

The 'with' clause on a connect statement is incorrectly specified.
When the 'with' clause is used to pass the distributed transaction
id to the dbms for reassociation, there must be no other
information in the with clause. Distributed transaction ids must
be represented as integer variables or values.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

See the manual for the correct syntax for this statement.

E- EQ0126- sqDIREC
'%Oc' incorrectly used to specify direction.
Use the words ASC or DESC.
Explanation:

The direction specified in the ORDER BY clause or a MODIFY
statement must be ASC or DESC.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Substitute the correct directional specification for the flagged
word.

E- EQ0127- sqEXECMD
Statement should begin 'EXEC %Oc % Ie'.
Explanation:

Database query and status statements should begin "EXEC SQL"
and forms statements should begin "EXEC FRS".

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Insert the correct statement demarker: "EXEC SQL" for database
query and status statements and "EXEC FRS" for forms
statements.

E- EQ0128- sqNOSQLCA
No INCLUDE SQLCA statement seen so far.
An INCLUDE SQLCA statement must precede a WHENEVER statement.
Explanation:

In response to the WHENEVER statement, the preprocessor
generates code which accesses fields in the SQLCA. Therefore
you must have included an SQLCA in your program module via
the INCLUDE SQLCA statement.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Put in an INCLUDE SQLCA statement preceding the first SQL
statement.

EQ Class Messages

14-11

E_EQ0129_sqVARCOLON
Variable name must be prefixed by a colon ':'.
The current SQL/FRS statement contains a variable used without a colon.
Explanation:

All variable names used with Embedded SQL and FRS
statements must be prefixed by a colon to indicate to the
preprocessor that they are variables and not object names.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Prefix all variables in embedded SQL/FRS statements with a
colon.

E - EQ0130- sqWCOND
Illegal WHENEVER condition '%Oc'.
The conditions must be SQLERROR, SQLWARNING or NOT FOUND.
Explanation:

The WHENEVER statement is used to test the status of SQLCA
variables to ascertain if the last executed SQL statement resulted
in an error (SQLERROR), a warning (SQLWARNING) or no
data matching the query (NOT FOUND).

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Correct the WHENEVER statement to reflect the correct
condition.

E_EQ0131_sqWSTOP
Incorrect WHENEVER NOT FOUND statement.
The WHENEVER NOT FOUND statement may not specify the STOP action.
Explanation:

The WHENEVER NOT FOUND is commonly used to break out
of a CURSOR FETCH loop. This is not a useful place to stop
execution of a program.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Change the specified action to CONTINUE, GOTO a label or
CALL a procedure.

E - EQ0132- sqILLSTRUCTEXPR
Illegal use of record variable.
A record (or structure) variable may not be a component of an expression.
Explanation:

This error occurs when a record variable is used as part of an
expression, ie, "1 + :record_var". Record variables may be used
in the INSERT, SELECT and FETCH statements but they must
be used alone.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Use an elementary variable in the expression.

14-12

EQ Class Messages

E - EQ0133- sqNOFROM
The SELECT statement requires a FROM clause.
You may not use a WHERE, GROUP BY, HAVING or FOR UPDATE clause in a
SELECT statement without a FROM clause.
Explanation:

In order for a WHERE or any of the other above clauses to
qualify the results of a query, a table name must be specified in a
FROM clause. The FROM clause is optional if you only
SELECT constants.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Insert a FROM clause into the current query.

E - EQ0134- sqNAME
Name or string variable expected instead of '%Oc'.
Do not use the colon if you mean to specify just a name.
Explanation:

A numeric variable has been used where a string variable or a
simple name was expected.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Change the statement to use a string variable (preceded by a
colon) or a simple name (with no colon).

E_EQ0135_sqXACT
SQL transaction syntax '%Oc' has been modified.
Version 5.0 syntax (BEGINIEND TRANSACTION, ABORT) should be updated. Ignore
this warning if you intend to use the run-time SET AUTO COMMIT option.
Explanation:

The SQL version 5.0 syntax was used (BEGIN
TRANSACTION, END TRANSACTION, ABORT). The BEGIN
TRANSACTION will generate a run-time error too, as an SQL
program is implicitly inside a transaction.
The END TRANSACTION should be replaced by COMMIT,
and the ABORT by ROLLBACK. This warning can be ignored if
you intend to use the SET AUTO COMMIT option at run-time,
implying that BEGIN TRANSACTION is necessary.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Change the statement to use the SQL transaction syntax.

E_EQ0151_fsBAD
Unknown identifier '%Oc' in SET/INQUIRE statement.
The object-type or FRS constant must be a legal name (not in a variable).
Explanation:

You have used an object-type or constant that is unknown to the
preprocessor in an INQUIRE_FRS or SET_FRS statement. You
may not use a variable name to specify the object you wish to
inquire about or set.

EQ Class Messages

14-13

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Check the manual for the FRS objects which may be legally
inquired about or set.

E _ EQ0152_fsCONSTSYN
Illegal SET/INQUIRE target list syntax '%Oc(%lc)'.
A non-existent FRS object '% lc' has been specified.
Explanation:

This error occurs when a non-existent FRS object is used with a
legal FRS constant.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Check the manual for the FRS objects which may be legally
inquired about or set.

E_EQ0153_fsREQOBJ
SET/INQUIRE constant '%Oc' requires an object.
Explanation:

This error occurs when a legal FRS constant has been used but
the FRS object has been omitted.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Refer to the manual for the list of objects, one of which must
follow the FRS constant.

E_EQ0154_fsNOTOBJ
Object name is not allowed for constant' %Oc' .
Some SET/INQUIRE objects have no associated constant values.
Explanation:

This error occurs when an object name is used with an FRS
constant, but the FRS constant is not one which takes an object.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Remove the FRS object name from the statement.

E_EQ0155_fsMAXPAR
The maximum number of FRS object parent names is %Oc.
You have used an extra form or table name in a SET/INQUIRE statement.
Explanation:

Some INQUIRE/SET statements require no parent-name, some
require a form name, and some a form name and a table name.
Refer to the manual for the correct syntax.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Remove the extra parent name from the INQUIRE/SET
statement.

14-14 EQ Class Messages

E_EQ0156_fsNOSET
Constant '%Oc' is only for the INQUIRE statement.
You have tried to SET constant '%Oc'.
Explanation:

There are many FRS constants (ie, field names and types) which
cannot be set. The common FRS features that may be set are
display attributes for fields, validations and mapping of keys.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Refer to the manual for a list of settable FRS features.

E_EQ0157_fsNUM
%Oc number must be within range I to % Ic.
The FRS object name specified in a SET/INQUIRE statement is out of range.
Explanation:

Specific object names and values, such as MENU I , FRSKEY3
and PF5 have numbers associated with them (ie, I, 3 and 5). The
numbers must be within the specified range, as that is the range
of run-time support.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Refer to the manual for the legal range of numbers that qualify
object names.

E _EQ0158_ fsOBJARG

SET/INQUIRE object '%Oc' requires %Ic parent name(s).
A form name or table name is required with object '%Oc'.
Explanation:

Different FRS object types require the user to specify a different
list of parent names.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Refer to the manual for the required parent names for this
statement.

E _EQ0159_ fsOBJCONST
Illegal use of SET/INQUIRE constant '%Oc'.
FRS constant '%Oc' cannot be used with object type '%Ic'.
Explanation:

An FRS object type (ie, FRS, FORM, FIELD, TABLE or
COLUMN) has an associated set of FRS constant values that
may be inquired about or set.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Refer to the manual for the list of FRS constants which may
associate with the FRS object used in the SET/INQUIRE
statement.

EQ Class Messages

14-15

E _ EQ0160_ fsPFCTRL
PF key number or control key character expected.
You have used identifier ~%Oc~.
Explanation:

Some FRS statements allow the assignment of a control key (ie,
controlF) or a function key (ie, PF2). You may not use a variable
to represent this assignment~ or use a control key character or
function key number which is out of range.

System Status:

Upon completion~ the preprocessor will return a FAIL status.

Recommendation:

Specify a legal control key or function key in the current
statement.

E _ EQ0201_ scBADINCEXT
Illegal or missing suffix on INCLUDE file ~%Oc~.
The correct suffix is ~. % 1c ~ .
Explanation:

INCLUDE files must be correctly specified. We do not support
system-dependent file specifications, such as the inclusion of
files from text libraries.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Correct the name of the file to be included.

E_EQ0202_scBADDEREF
Illegal character following dereference character.
The dereference character ~#~ should be immediately followed by a name.
Explanation:

The first character following the dereference character ~#~ was
not one of the characters which may legally start the name of an
ULTRIX/SQL object.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Correct the name to be dereferenced.

E_EQ0203_scDEREF
No name specified after dereference character ~#~.
The dereference character and the name must be on the same line.
Explanation:

This error will occur if a new line intervened between the
dereference character and the name to be dereferenced.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Update the statement so that the name to be dereferenced
immediately follows the dereference character.

E _ EQ0204_ scEOFCMT
Premature End Of File found in comment.
Explanation:

14-16

EQ Class Messages

The preprocessor unexpectedly encountered the end of the input
file when scanning an embedded comment.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Close the comment before the end of file.

E _EQ0205 _scEOFMIDLINE
End of file found in middle of line.
The current line will be ignored by the preprocessor.
Explanation:

This error may occur if you run the preprocessor interactively
using the -s flag. An input file containing a mid-line end of file is
usually one which has been created by a program and not by a
standard editor.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Correct the input file by completing the last statement.

E_ EQ0206_ scEOFSTR
End Of File found in string '%Oc'.
The closing quote is missing from the string.
Explanation:

This error occurs when the closing quote has been omitted from
a string. The preprocessor scans to the end of file searching for
the closing quote.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Correct the input file by terminating the string with a quote.

E_EQ0207_scILLINCNAM
Illegal syntax in INCLUDE file name '%Oc'.
Explanation:

The system is unable to open the included file because its name
does not have a legal format.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Correct the name of the file to be included.

E_EQ0208_scINCINOPN
Cannot open INCLUDE input file '%Oc'.
The file is non-existent or you do not have permission to read it.
Explanation:

An INCLUDE input file cannot be read because it does not exist,
because it is not in the current directory or the location specified
or because you do not have read privileges.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Check the existence, location and read privileges on the file you
wish to include.

EQ Class Messages

14-17

E_EQ0209_scINCRCRSVOPN
Attempt to recursively open INCLUDE input file '%Oc'.
Files may not include themselves, either directly or indirectly.
Explanation:

This error will occur if the included file contains an INCLUDE
file statement attempting to include itself. This error will arise if
a file in a hierarchy of included files attempts to include a file
already in the hierarchy.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Remove the INCLUDE statement in the file that includes the
included file.

E_EQ0210_scINCOUTOPN
Cannot open INCLUDE output file '%Oc'.
Check your permission to write a file in the current location.
Explanation:

Output files cannot be opened because a user does not have write
privileges. There may be other system dependent reasons.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Attempt to open a file with the same name at the system level
and take note of the system response.

E_EQ0211_scINCQUOTE
Illegal INCLUDE file name delimiter character '%Oc'.
Use legal delimiters or omit delimiters altogether.
Explanation:

This error occurs when a delimiter other than a single or double
quote is used. Note that embedded languages in C may also use
the " and " delimiters.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Replace the delimiters with the correct ones or omit delimiters
altogether.

E _ EQ0212_ scLINLONG
Input line exceeds maximum line length, %Oc.
The rest of line is ignored.
Explanation:

This error occurs on very long input lines. Note that the line
length acceptable to the preprocessor is the same as that
acceptable to many compilers.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Break up the flagged line into smaller lines. If the line contains a
SQL statement, use host language line continuation.

14-18

EQ Class Messages

E_EQ0213_scHEXLONG
Maximum hex constant length, %Oc, is exceeded by .
Explanation:

The hex constant used contains too many digits. Note that the
maximum number of digits allowed is extremely large and users
are unlikely to come up against this limit.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Substitute a smaller hex constant, or use an expression
comprised of smaller constants.

E_EQ0214_scNUMLONG
Maximum number length, %Oc, is exceeded by '%lc'.
Explanation:

The decimal number used contains too many digits. Note that the
maximum number of digits allowed is extremely large and users
are unlikely to come up against this limit.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Substitute a smaller numeric constant, or use an expression
comprised of smaller constants.

E_EQ0215_scSTRLONG
Maximum string length, %Oc, is exceeded by ....
Explanation:

The string literal used contains too many characters. Note that
the maximum suing length allowed is as big as that allowed by
most compilers.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

If the host language allows string continuation, try to split the

string over two lines.
E_EQ0216_scWRDLONG
Maximum word length, %Oc, is exceeded by '% 1c' .
Explanation:

The word used contains too many characters. Note that the
maximum number of characters allowed in an word is extremely
large and users are unlikely to come up against this limit.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Reduce the size of the name.

E_EQ0217_scIDLONG
Maximum identifier length, %Oc, is exceeded by '% 1c%2c' .
Explanation:

The variable name or object name used is too long. A variable
name in this context includes a fully qualified record variable or
a subscripted variable. An object name includes, for example, a
column name along with a correlation or range variable. The

EQ Class Messages

14·19

maximum identifier length is extremely large and users are
unlikely to come up against this limit.
System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Use a shorter variable or object name.

E _ EQ0218_ seMIS SRI G HT
Missing delimiter(s) (from line % lc).
Encountered End Of File when scanning ....
Explanation:

The preprocessor was scanning input looking for a terminating
or delimiting character (ie, a closing parenthesis or bracket or a
closing quotation mark) when it encountered an End of File. This
is probably a syntax error.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Check the flagged line for a syntax error or missing delimiter.

E _ EQ0219_ seNLSTR
New-line in string.
Use query language convention for continuing strings over multiple lines.
Explanation:

This error occurs when the user types a new-line in a quoted
string without using any form of line continuation. If the host
language permits string continuation, the SQL convention for
continuation follows the host language rules for string
continuation.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Continue string using appropriate query language convention if
the host language allows string continuation.

E _ EQ0220_ seNUMCONV
Conversion of '%Oc' to integer/float failed.
'%Oc' cannot be represented in an internal numeric format.
Explanation:

This error occurs when a very large numeric constant cannot be
converted into an internal numeric format. The preprocessor and
the run-time code use standard numeric storage. Very large
numbers, for instance floating point numbers requiring 16-byte
storage, will cause an error from the preprocessor and from the
run-time code.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Reduce the size of the numeric constant.

E_EQ022l_seOPERATOR
Unknown operator '%Oc'.

14-20

EQ Class Messages

E_EQ0225_scINCNULDIR

Explanation:

This error occurs when an operator used in an embedded
statement is not recognized by the preprocessor. The query
languages recognize specific operators for comparisons,
assignments and pattern matching.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Remove the operator from the embedded statement.

E _EQ0222_ scSCCMNT
Unknown Comment start' %Oc' .
Comment will be assumed to end with end of line.
Explanation:

The preprocessor recognizes embedded comment lines using the
host language comment indicator. For all host languages the
preprocessor recognizes the embedded comment delimiters.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Use the conventional host language comment delimiters or the
generic embedded comment delimiters.

E_EQ0223_scINCMANY
Too many directories for included files.
The number of locations of files to be included exceeds the maximum, %Oc.
Explanation:

This error occurs when the preprocessor command line specifies
with the -h flag too many directories to be searched for include
files.

System Status:

The preprocessor will exit without preprocessing the input file.

Recommendation:

Consolidate the files to be included into fewer directories.

E_EQ0224_scINCBADDIR
Invalid directory' %Oc' for included files.
Explanation:

The directory specified with the -h command line flag is not a
valid directory name on this system. The user may have typed
the complete path name incorrectly.

System Status:

The preprocessor will exit without preprocessing the user's input.

Recommendation:

Invoke the preprocessor again using a valid path and directory
name.

E_EQ0225_scINCNULDIR
Empty directory name specified for included files.
Explanation:

A null directory has been specified with the -h flag on the
preprocessor command line.

System Status:

The preprocessor will exit without preprocessing the user's input.

Recommendation:

Follow the -h flag with the name of a directory in which files to
be included can be found.
EQ Class Messages

14-21

E_EQ0226_scINCNOTFOUND
Cannot find INCLUDE input file '%Oc'.
The file '%Oc' is not in any of the directories specified by the '-h' flag.
Explanation:

This errors occurs when the INCLUDE statement is attempting
to include a file from one of the directories specified with the
'-h' flag on the command line, and that file does not exist in any
of the specified directories.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Either correct the directory named with the -h flag, or correct the
file name used in the INCLUDE statement.

E _EQ0227_ scHEXCHAR
Illegal character '%Oc' found in hex constant.
Explanation:

A hex constant (ie, X'IFFF') can contain digits and the
alphabetic characters A through F only.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Correct the syntax of the flagged hex constant.

E_ EQ0228_ scHEXODD
Odd number of characters in hex constant '%Oc'.
Use a leading zero.
Explanation:

The preprocessor expects the first character/digit of a hex
constant to map to a high order byte boundary.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

If your hex constant contains an odd number of characters,

include a leading zero. For example, X' IFF' becomes X'OIFF'.

E_EQ0229_scBADQUOTE
The correct delimiter for literal strings is .
Wrong string delimiter used.
Explanation:

Literal strings in Embedded SQL statements must be delimited
by the single quote '. Embedded host declarations follow the
rules of the host language for quoted strings.
The manual contains examples of quoted strings in both
embedded statements and embedded host declarations; it also
instructs on how to include a quotation within an embedded
string. This message is only a warning, so as to be compatible
with earlier versions of Embedded SQL.

System Status:

This message is just a warning.

Recommendation:

Change the string delimiter in the current statement to the legal
Embedded SQL string delimiter.

14-22

EQ Class Messages

E _ EQ0230_scEMBEDQUOTE
Illegal embedding of quote in a SQL string.
The string is truncated after the .
Explanation:

Some host language compilers do not allow the outer string
delimiter to appear inside a string. In Embedded SQL, the SQL
delimiter can always appear inside the string by doubling it.
However, in some languages the preprocessor does not allow a
non-SQL string delimiter to appear within an SQL string.
Note that because the preprocessor stops processing the string
upon encountering the illegal delimiter, the remainder of the
string is likely to produce a syntax error.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Use the doubled SQL delimiter if you wish to place a string
delimiter inside a string.

E _EQ0231_ scMISSEND
No matching END for BEGIN on line %Oc.
Encountered End Of File when scanning BEGIN/END block.
Explanation:

The preprocessor was scanning a BEGIN/END block, looking
for the END, when it encountered an End of File. This is
probably a syntax error.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Check for a mispelled END, or for a BEGIN without a matching
END.

E_EQ0240_yyOVFL
Internal error: Parser stack overflow.
Explanation:

An internal data structure is not big enough to allow the
preprocessor to complete the current statement. This may
indicate an internal coding error or an embedded statement that
is too complex.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Try to restructure your statement so that it is syntactically
simpler.

E _ EQ0241_yySYNTAX
Syntax error.
Explanation:

A syntax error has occurred on the current statement. Usually the
rest of the statement is ignored. However, some syntax errors
will confuse the preprocessor's syntactic recovery causing more
errors in subsequent statements.

EQ Class Messages

14-23

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Correct the statement causing the syntax error.

E _ EQ0242_yySYNHOST
Syntax error on host code.
Explanation:

This error occurs when host code appears in the middle of an
embedded statement.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Complete the embedded statement that appears before the
flagged host code line.

E_EQ0243_yySYNTERM
Syntax error on terminator or missing %Oc continuation indicator.
Explanation:

For those host languages that do not have SQL statement
terminators, the preprocessor allows the ';' terminator on most
embedded statements. (This proves useful when using the
preprocessor interactively.) However, a terminator is prohibited
on declarations and some statements and will produce the above
error.
This error is also caused when an embedded SQL statement is
continued over more than one line and the host continuation
indicator (if any) is omitted.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Remove the statement terminator or supply the host language
continuation indicator.

E _ EQ0244_yySYNWRD
Syntax error on '%Oc'.
Explanation:

The preprocessor has identified the word or symbol which is
syntactically incorrect.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Correct the syntax.

E _ EQ0245_yySYNEOF
Syntax error on End-of-File.
Explanation:

The preprocessor has unexpectedly encountered an End of File.
This error usually occurs if the end of file occurred in the middle
of a block-type embedded statement or an SQL declaration
section.

System Status:

Upon completion, the preprocessor will return a FAIL status.

Recommendation:

Complete the embedded block or statement.

14-24 EQ Class Messages

E- EQ0251- syBADLEVEL
Invalid record level %Oc in declaration for '% Ic'.
Explanation:

If record levels are required when declaring variables (ie, as in
PL/I or COBOL), they must be ordered correctly according to
the rules of the host language.

System Status:

Upon completion, the preprocessor will return a FAIL status.

E- EQ0252- syCHEKNULL
Symbol table: Null pointer to check-,-type_Ioop.
Explanation:

If you have defined a type and are referencing a variable of that

type, try to make the variable a base type. This may reduce the
complexity of the variable look-up. This is an internal error.

E - EQ0253- syDEEPIMPORT
Symbol table IMPORT of '%Oc' is too deep.
Explanation:

If your host language allows the IMPORT of variables from an

outer scope, you cannot import deeper than 20 levels.

E_EQ0254_syEXPORTVIS
Illegal attempt to EXPORT already visible name '%Oc'.
Explanation:

If your host language allows the EXPORT of variables to an

outer scope, you must confirm that the variable has not been
declared in the outer scope.

EEQ0255.
- syFSTAKOFLO
Symbol table record field stack overflow - fields discarded.
Explanation:

If you have qualified a structure variable, it should have less than

20 member names qualifying it.

E EQ0256 syLOOKANON
Symbol table lookup of an anonymous entry.
Explanation:

In a language in which you do not have to name a structure type
(such as C), the preprocessor is trying to reference the type
name. Try naming all your structure types (ie, use structure tags
or type declarations). This is an internal error.

E_EQ0257....syMODIFY
Symbol table modify of '%Oc' is neither imported nor exported.
Explanation:

The preprocessor is confused about what it thinks is either an
IMPORT or EXPORT statement. If you have any try changing
them to explicit declarations in their relevant scopes. This is an
internal error.

EQ Class Messages

14-25

E _ EQ02S8_ sy N OTVISIBL
'%Oc' is not visible for IMPORT statement.
Explanation:

If your language allows IMPORT from an outer scope, then the
name of the variable must be visible in the parent scope.

E _EQ02S9 _ syQNOTSUCC
Symbol table q_remove: q_elm not successor of q_before.
Explanation:

The symbol table data structures have been damaged. Try to use
fewer type and variable declarations. You may have to split your
file into two smaller files. This is an internal error.

E _ EQ0260_ sy RED ECLARE
Redeclaration of identifier' %Oc' is ignored.
Explanation:

The named identifier as been redeclared. The preprocessors
stores all declaration objects in a single name space,
consequently, type names, constant names and variable names
must be different.

E_EQ0261_syREIMPORT
Attempt to IMPORT already visible name '%Oc'.
Explanation:

If your language allows IMPORT from an outer scope, then the

imported name must not be an already-declared object in the
nested scope.
E _ EQ0262_sySSTKOFLO
Symbol table scope stack overflow - nesting limit is %Oc.
Explanation:

Rearrange the nesting of embedded blocks so that they are not so
nested.

E _ EQ0263_ sySSTKUFLO
Symbol table scope stack underflow.
Explanation:

If there were syntax error while preprocessing the current

statement then correct the errors and try again. Also try to
rearrange the nesting of embedded blocks. This is an internal
error.
E _ EQ0264_ sySVISZERO
Symbol table scope end: found '%Oc' with visibility of zero.
Explanation:

14-26

EQ Class Messages

The symbol table data structures have been damaged. Try
reducing the number of declarations in the module. This is an
internal error.

E _EQ0265_syTYPLOOP
Symbol table type loop for ('%Oc', '% Ic').
Explanation:

You have defined a type recursively causing confusion in the
symbol table data structures. This is an internal error.

E_EQ0266_syUNDECSTAT
'%Oc' is undeclared in IMPORT/EXPORT statement.
Explanation:

You have tried to IMPORT or EXPORT a name that was never
declared. All names must be declared before you can expand
their scope.

E_EQ0267_sySQREDEC
Redeclaration of identifier '%Oc' with incompatible type.
Explanation:

Embedded SQL allows the redeclarations of some variables. The
variables must be elementary variables (not structures or types).
Any redeclaration requires an exact type match.

E _ EQ0268_ syTYPEUNDEF
, %Oc' references ' % 1c', which is not yet defined.
Explanation:

If your host language allows forward declarations (ADA,

BASIC, PASCAL) your must make sure that you have declared
the forward-defined type before using a variable of that type.
E_EQ0301_actBAD
Illegal ACTIVATE type, %Oc, passed.
Explanation:

The preprocessor does not recognize the ACTIVATE type used.
This may be an internal error. If you have complex ACTIVATE
block control flow, try to flatten out any nested blocks and
reduce the number of RESUME statements.

E _ EQ0302_ actCOL
Missing ACTIVATE COLUMN name - table is '%Oc'.
Explanation:

This is a syntax error in an ACTIVATE COLUMN statement that
was caught too late. Add the column name to the ACTIVATE
statement.

E _ EQ0303_ actNEST
ACTIVATE blocks are nested too deeply -limit is %Oc.
Explanation:

Rearrange the nesting of DISPLAY and ACTIVATE blocks so
that there are fewer levels of nesting.

EQ Class Messages

14-27

E _ EQ0304_ actNULL
Null ACTIVATE object passed - type is %Oc.
Explanation:

If you used a variable name for an ACTIVATE object try to
replace it with a string literal. This is an internal error.

E_EQ030S_actUNDFL
ACTIVATE block underflow.
Explanation:

If there were syntax errors while processing DISPLAY and
ACTIVATE blocks but not within the code enclosed in the block,
correct the errors. If there were no syntax errors then this is an
internal coding error.

E_ EQ0306_ actARGS
Illegal ACTIVATE target list syntax (%Oc = %lc).
Explanation:

The target lists allowed with various ACTIVATE conditions must
be of the format: (object = value {, object = value}) with the
correct type and range for the value.

E _ EQ0307_ actRESNEXT
Cannot RESUME NEXT in an ACTIVATE %Oc block.
Explanation:

RESUME NEXT should be used to resume from an ACTIVATE
FIELD or an ACTIVATE COLUMN. RESUME NEXT within
other ACTIVATE blocks may generate this warning.

E_EQ0308_actTIMEOUT
Only one ACTIVATE TIMEOUT block is allowed in a display loop.
Explanation:

There may be only one activate block to handle timeout in a
display loop. Only the first ACTIVATE TIMEOUT block will be
used at run-time.

E_EQ0309 _actTARGET
An ACTIVATE %Oc block may not have a target list.
Explanation:

The optional target list may not be used on all ACTIVATE
statements. Consult the embedded language User's Guide for the
list of ACTIVATE statements which allow a target list.

E_EQ0316_argMAX
Statement has too many arguments. The limit is %Oc arguments.
Explanation:

14-28 EQ Class Messages

Reduce the number of arguments to the statement. This is
probably the SQL CONNECT statement, as most other
statements have a fixed number of arguments. The specified
limit may include internally generated arguments.

E _ EQ0317 _ argNOARGS
There are %Oc argument(s), statement requires more.
Explanation:

There was probably a syntax error in the current statement, and
the preprocessor error recovery routine did not supply enough
dummy arguments for code generation.

E_EQ0326_1blOVERFLOW
Too many nested blocks, maximum is %Oc.
Explanation:

Rearrange the nesting of embedded blocks (DISPLAY,
ACTIVATE, UNLOADTABLE, etc) so that they are not so
deeply nested.

E _ EQ0327_lbIUNDERFLOW
Label block manager underflow.
Explanation:

If there were syntax errors while processing embedded blocks

(DISPLAY, ACTIVATE, UNLOADTABLE, etc) but not within
the code enclosed in the block, th~n correct the errors. If there
were no syntax errors then this is an internal coding error.
E_EQ0328_1blUNKNOWNMOD
Unknown label mode - %Oc.
Explanation:

This is an internal error.

E_EQ0336_outFUNC
Null function pointer passed for Output state trap.
Explanation:

If you are declaring many cursors together with using repeated
queries, try rearranging their order. If there were syntax errors

during the cursor declarations and repeated queries then correct
the syntax errors. If there were no syntax errors then this is an
internal coding error.
E_EQ0341_strBADPTR
String Table pointer is out of bounds.
Explanation:

This is an internal coding error.

E _ EQ0342_ strSIZE
Illegal String Table size ini tializer, %Oc.
Explanation:

This is an internal coding error.

EQ Class Messages

14-29

E _ EQ0343_ strSPACE
Not enough String Table space for %Oc bytes.
Explanation:

If this occurs after an error indicating that an object has

exceeded its maximum size (such as a string literal that is too
long), then correct the previous error. Otherwise this is an
internal coding error.
E_EQ0344_strTRUNC
String '%Oc' too large for String Table buffer (% 1c bytes).
Explanation:

If the specified string refers to objects in the preprocessed file,

then try to break up the object names into smaller pieces (ie,
replacing large string literals with variables). If the specified
string does not include objects from the file, then this is an
internal coding error.
E _ EQ0377_repNOTIMP
REPEAT queries are not implemented with this version.
Explanation:

Some versions of the preprocessor do not support REPEAT
queries.

E _ EQ0386_ret VAR
Result column, '%Oc', for data retrieval must be a variable.
Explanation:

The result variable used in an SQL SELECT statement to collect
the data must have been properly declared to the preprocessor.

E _ EQ0396_ csBADTYPE
Retrieval of cursor '%Oc' into '%lc' conflicts with earlier retrieval.
Explanation:

The base type (numeric or string type) of a result variable in an
SQL FETCH statement conflicts with the type of the same
column on a preceding retrieval in the same file.

E_EQ0397_ csDECNULL
Declaration of a cursor without a name.
Explanation:

You have declared an empty string literal as a cursor name.
String literals can be used to declare cursors whose names are
reserved words, but they must not be null strings.

E_EQ0398_csNOCSR
Cursor named '%Oc' is not yet declared.
Explanation:

14-30 EQ Class Messages

You have issued a cursor statement (such as a retrieval) without
a preceding cursor declaration (DECLARE CURSOR) or the
named cursor.

E _ EQ0399_ csNOCURCSR
No cursor referenced in current statement.
Explanation:

If you used an empty string to declare a cursor then correct the

previous error. Otherwise the preprocessor has not retained the
current cursor name within a cursor statement, and then this is an
internal coding error.
E_EQ0400_csNOTUPD
%Oc of read-only cursor '%Ic' is not legal.
Explanation:

The specified cursor is can not be updated (ie, it may refer to a
join of multiple tables). The update operation specified in the
first argument (such as DELETE) is not allowed.

E _ EQ0401_csOBJNULL
In cursor '%Oc', object name is empty.
Explanation:

An empty string literal has been given as an object name in a
cursor declaration (other than for a cursor name). This may be a
table or a column name. Correct the object to correctly specify
the name.

E _ EQ0402_ csREDECCSR
Redeclaration of cursor '%Oc'.
Explanation:

The named cursor has already been declared. The scope of a
cursor declaration is the whole source file. The same cursor
name cannot be redeclared to the preprocessor. This does not
affect the executable OPEN statement, which can occur multiple
times.

E_EQ0403_csUPDEXPR
Cannot update column '%Oc' of cursor '%Ic'.
Result columns defined as expressions cannot be updated.
Explanation:

Some result columns may not specified for update. A result
column name that names a constant expression may not be
specified in the FOR UPDATE list.

E _ EQ0404_csUPDMANY
Cannot update column '%Oc' of cursor '% Ic' as it is not a unique name.
Explanation:

Some result columns may not specified for update. A result
column name that names two distinct columns within the cursor
declaration may not be specified in the FOR UPDATE list.

E _ EQ040S _ csUPDCONST
Cannot update column '%Oc' of cursor '%lc' as it is a constant.

EQ Class Messages

14-31

Explanation:

Some result columns may not specified for update. A result
column name that is an ULTRIX/SQL constant (such as
'usemame') may not be specified in the FOR UPDATE list.

E_EQ0406_csUPDXIST
Cannot update column '%Oc' of cursor '%lc' as it is not in the target list.
Explanation:

Some result columns may not specified for update. A result
column name that is not in the target list of the cursor declaration
may not be specified in the FOR UPDATE list.

E_EQ0407_ csUPDTABLES
Cannot declare cursor '%Oc' FOR UPDATE as it has more than one table.
Explanation:

A cursor declaration that refers to more than one table cannot be
updated.

E_EQ0408_csUPDUNIQ
Cannot declare cursor '%Oc' FOR UPDATE as it has a %lc clause.
Explanation:

The specified cursor cannot be updated as it includes a query
language clause, such as the SQL ORDER clause.

E _ EQ0409_ csUPDNOCOL
Cannot declare cursor '%Oc' FOR UPDATE as it has no updatable columns.
E _EQ0410_ csUPDFUNC
Cannot declare cursor '%Oc' FOR UPDATE as it has a function in the target list.
Explanation:

If a cursor has a function in the target list (ie, _dbms_infoO) then

the cursor cannot be updated.
E_EQ0411_csUPDALL
Cannot use ALL in the FOR UPDATE list for cursor' %Oc' .
Explanation:

You must enumerate all columns in the cursor result table in
order to update all of them.

E _ EQ0412_ csCLMNUPD
Cannot update cursor '%Oc' as no columns were named in the update clause.
Explanation:

Because there was no FOR UPDATE clause (or not columns
specified within the FOR UPDATE clause) the cursor cannot be
updated.

E_EQ0414_csCOLUPD
Cannot update column '%Oc' of cursor '%lc' as it is not updatable.
E_EQ0415_ csNOUPDCOLS
Cursor '%Oc' has no updatable columns.

14-32 EQ Class Messages

E_EQ0424_cSILLCORRELNAME

E _EQ0416_ csCOLNOSUCH
Cannot update column '%Oc' as it is not in cursor '% lc'.

E_EQ0417_csPARAMUPD
Cannot REPLACE PARAM cursor' %Oc' as there are no updatable columns.

E_EQ0418_csNOLISTUPD
Cannot update cursor '%Oc' as there was no list of updatable columns.

E_EQ0419 _csTBLUPD
Cannot %Oc cursor '%lc' as it has more than one table.

E _EQ0420_ csCSRNULL
Reference to a cursor without a name.
Explanation:

If you used an empty string to declare a cursor then correct the

previous error. Otherwise the preprocessor has not retained the
current cursor name within a cursor statement, and then this is an
internal coding error.

E_EQ0421_csGETMANY
Too many variables for retrieval from cursor '%Oc'.
Explanation:

The cursor declaration did not include as many result columns as
variables specified in the cursor retrieval statement. You must
retrieve exactly the same number of columns as specified in the
cursor declaration.

E_EQ0422_csGETFEW
Too few variables for retrieval from cursor' %Oc' .
Explanation:

The cursor declaration included more result columns than
variables specified in the cursor retrieval statement. You must
retrieve exactly the same number of columns as specified in the
cursor declaration.

E_EQ0423_csBADREPEAT
The cursor' %Oc' statement may not be a repeated query.
Explanation:

The cursor retrieval and update statements may not be specified
in the context of a repeated query.

E_EQ0424_csILLCORRELNAME
Correlation name '%Oc' is not allowed in a cursor '%lc' statement.
Explanation:

In SQL you cannot specify a correlation name for a cursor
DELETE or UPDATE. Only the table name is allowed and the
table name must be identical to the table referred to in the cursor
declaration.

EQ Class Messages

14-33

E_EQ042S_csUSINGDYN
A OPEN statement USING clause is legal only for a dynamic cursor.
Explanation:

The USING clause of the SQL OPEN statement:
USING DESCRIPTOR descriptor_name I variable
{, variable} is only allowed if the cursor was declared for a
statement_name, as specified for dynamic SQL.

E _ EQ0426_ csREPEAT
Cursor declarations for REPEATED queries are not supported.
Explanation:

The DECLARE CURSOR statement cannot refer to a
REPEATED query. The ULTRIX/SQL run-time system does not
yet support this construct.

E_EQ0427_csTBLBAD
Invalid table '%Oc' in cursor '% 1c' statement.
Explanation:

The table name referenced in the cursor DELETE or UPDATE
statement is not the same as the table name specified in the
DECLARE CURSOR statement.

E _ EQ0428_ csCURSORNAME
Reference to cursor '%Oc' is incompatible with declaration.
Explanation:

If a DECLARE CURSOR statement uses a variable to represent

the cursor name, all references to that cursor must also use the
same variable name. Similarly, if a DECLARE CURSOR
statement uses a static name, subsequent cursor operations must
also use the same static name.
E_ EQ0429_ csBADFROM
The cursor '%Oc' statement may not contain a FROM clause.
Explanation:

The optional FROM clause cannot be used in a cursor update
statement; it is only allowed in a non-cursor update statement.

E_EQ04S0_fwILLEGAL_FWC
This statement does not support the forms WITH clause.
Explanation:

The forms WITH clause is not supported by this statement.

Recommendation:

Refer to the manual for the statements supporting this feature.

E_EQ04S1_fwINVALID _ OP_SUBOP
Invalid WITH clause option or suboption: '%Oc = % 1c'
Explanation:

This option or suboption is invalid.

Recommendation:

Refer to the manual for valid options and suboptions in the forms
with clause.

14-34

EQ Class Messages

E_EQ04S2_fwBAD_COMBO
Invalid combination of statement, option, and suboption (current option: '%Oc = %Ic').
Explanation:

Although these are valid options, the combination of the
suboption and option are not valid for this statement.

Recommendation:

Refer to the manual for the correct syntax of this statement.

E_EQ04S3_fwTYPE_MISMATCH
Type of '%Oc' does not match the type required for suboption '% I c' .
Explanation:

The current statement requires a special word, constant, or
variable type other than that specified.

Recommendation:

Refer to the manual for the allowed types.

E_EQ04S4_fwOP_REDEF
Forms WITH clause option '%Oc' has been redefined.
The last definition will be used.
Explanation:

If a suboption is defined more than once in a forms WITH

clause, this warning is displayed.
System Status:

The preprocessor will ignore the earlier definitions and will
return a SUCCESS status if no other errors occur during
preprocessing.

Recommendation:

Remove the unnecessary definition(s).

E_EQ04SS_fwTABLE_FULL
Fatal attempt to access internal table.
An internal forms WITH clause table is full.
Explanation:

A required internal table could not be accessed. This is caused by
an internal coding error.

Recommendation:

Please submit a Software Performance Report (SPR).

E _ EQOSOl_hBADTYPE
Unsupported %Oc type '% Ic' used. Declaration is ignored.
Explanation:

Across all host languages, there are some types that are not
supported by the preprocessors, as they are not compatible with
an ULTRIX/SQL type. The declaration will either be ignored or
the variable will be treated as a simple integer.

E_EQOS02_hNOVAR
%Oc variable '% Ic' has not been declared.
Explanation:

The identifier was referenced as though it was a variable, but
was not declared to the preprocessor.

EQ Class Messages

14-35

E _ EQOS03_ hSQLCA
INCLUDE SQLCA must be issued before statement '%Oc'.
Explanation:

In most host languages, you must specify INCLUDE SQLCA
before any embedded SQL statement. The INCLUDE SQLCA
statement also generates host language statements to make the
generated calls acceptable to the host language compiler.

E_EQOS04_0PEN_WARN
The statement' %Oc' is not an OPEN SQL command.
This statement may not be portable to a non-ULTRIX/SQL DBMS.
Explanation:

When the' -wopen' flag is given, the esql preprocessor will
produce a warning message when it encounters a command that
is not an OPEN SQL command.

Recommendation:

If users wish to produce portable code to be used on

heterogeneous DBMS's, they should eliminate any commands
that produce this warning message.

14-36

EQ Class Messages

FR Class Messages

E _ FROOOl_IIFlag_D
HFlag -D: Cannot open
E _ FR0002_IIFlag_Z
HFlag -Z: Cannot open
E _ FR0003_Illegal_II_FRSFLAG
Illegal H_FRSFLAG Flag -%c
S- FR0004- TERM
TERMINAL
S- FROOOS- ERRN
ERRORNO
S- FR0006- VNXT
VALIDATE ON NEXT FIELD
S- FR0007- VPRV
VALIDATE ON PREVIOUS FIELD
S- FR0008- VMKY
VALIDATE ON MENU KEY
S- FR0009- VKYS
VALIDATE ON FRSKEY
S- FROOOA- VMNU
VALIDATE ON MENU ITEM
S- FROOOB - MUMP
MENUMAP
S- FROOOC- MAP
MAP
FR Class Messages

15-1

S- FROOOD- LABL
LABEL
S- FROOOE- MPFL
MAPFILE
S- FROOOF- PCST
PCSTYLE

S FROOIO STLN
STATUS LINE
S- FROOll - VFRK
FRSKEY VALIDATION

S FR0012 NORM
NORMAL
S- FR0013- RVVI
REVERSE

S- FR0014- BLNK
BLINK

S- FR0015- UNLN
UNDERLINE

S- FR0016- INTS
INTENSITY

S- FR0017- NAME
NAME
S- FR0018- CHNG
CHANGE

S- FR0019- MODE
MODE
S- FROOIA- FILD
FIELD

S- FROOIB - NUMB
NUMBER

15-2

FR Class Messages

S- FROOIC- LEN
LENGTH
S- FROOID- TYPE
TYPE

S- FROOIE- FMT
FORMAT
S- FROOIF- VALD
VALID

S- FR0020- TBL
TABLE

S- FR0021- RWNO
ROWNO
S- FR0022- MXRW
MAXROW

S- FR0023- LROW
LASTROW

S- FR0024- DR OW
DATAROWS
S- FR0025- MCOL
MAXCOL

S- FR0026- COLN
COLUMN·
S- FR0027- COLR
COLOR

S- FR0028- ANXT
ACTIVATE ON NEXT FIELD

S- FR0029- APRV
ACTIVATE ON PREVIOUS FIELD
S- FR002A- LCMD
COMMAND

FR Class Messages

15-3

S- FR002B - AMKY
ACTIVATE ON MENU KEY

S- FR002C- AMID
ACTIVATE ON MENU ITEM
S- FR002D- AKYS
ACTIVATE ON FRSKEY
S- FR002E- DTYP
DATATYPE

S_ FR002F_Enter _string_to _find
Enter string to find:

S- FR0030- Cannot- find
Cannot find ~%OC~
E FR0031 Can not. access form
Can not access fonn "helpfrom"

S- FR0032- HELP- Values- for
HELP -- Values for
S- FR0033- Column
Column

S- FR0034- Field
Field
S- FR0035- HELP- Field- Values
HELP -- Field Values Frame

E _FR0036_Error _formatting
Error fonnatting validation string

S- FR0037- Nullable
Nullable
S_ FR0038_ Datatype
Datatype: %s %s

S- FR0039- Format
Format: %s

15-4

FR Class Messages

S- FR003A- No- validation- check
No validation check in effect.
S- FR003B- ValidationCheck
is
Validation Check is:
S- FR003C- Validations
-- Validations
S_ FR003D_Error _filling
-- Error(s) filling values list.
S FR003E- Value- must be in
-- Value must be in list shown below...
S- FR003F- HELP- sub
HELP -- %s
S_ FR0040_HELP_Command _Key
HELP -- Command-Key Mapping for %s
S_FR0041_HELP_Help_Submenu
HELP -- Help Submenu
E _ FR0042_ Unexpected_gra phics
Unexpected graphics flag (vfrfiq = %d)
E - FR0043- Can- not- access- form
Can not access form "helpform"
S_FR0044_Sorry _No_help_avail
Sorry - No help available on "%s"
S_ FR0045_Sorry _Cannot_edit
Sorry - Cannot edit file \' %s\': Status %d
S_ FR0046_ HELP_ Main_Help
HELP -- Main Help Frame
E- FR0047- Can- not - access- form
Can not access form "help2form"
S_ FR0048_Sorry _N 0_hel p _avail
Sorry - No help available on "%s"

FR Class Messages

15-5

S_FR0049_Sorry _No_help_avail
,

Sorry - No help available on "%s"
E _ FR004A_ Can_not_access_form
Can not access form "keys form "
S_ FR004B _HELP_Command_Key
HELP -- Command-Key Mapping
S- FR004C- ETXT
Error Text
E - FR004D- Not on tf
Cursor not on table field. The "Find" function can only search a character datatype table
field column for a desired string. Please move the cursor to a table field and select "Find"
again.
Explanation:

User selecting the "Find" menuitem without having the cursor on
a table field.

System Status:

System will simply ignore request.

Recommendation:

Move the cursor to a table field and select "Find" again.

E _ FR004E_ TF_is_empty
The table field is empty. The cursor is on an empty table field. There is nothing to find.
Explanation:

User selected the "Find" menuitem with the cursor on a empty
table field.

System Status:

System will simply ignore request.

Recommendation:

User needs to move cursor to a table field with data in it.

E - FR004FNot
-char
Column does not contain character data. The "Find" function can only search a character
datatype table field column for a desired string. Please move the cursor to a table field and
select "Find" again.
Explanation:

User has cursor on a column that is not compatible with one of
the character datatypes when the "Find" menuitem was selected.

System Status:

System will simply ignore request.

Recommendation:

User needs to move cursor to a column that contains that that is
compatible with one of the character datatypes.

E_FROOSO_NegAlt
Bad parameters in IIFRgpinit (negative alt. value, or no default settings)
E _FROOSl_NegPid
Bad parameters in IIFRgpinit (negative pid)
15-6

FR Class Messages

E _ FR0052_BadType
Bad parameters in IIFRgpinit (Set entry %Od is unknown type %ld)

E- FR0053- BadPid
Illegal PID, %Od, IIFRgpset

E_ FR0054_BadType
Bad data type in parameter array, IIFRgpset

E- FR0055- Cony Fail
Failed conversion in IIFRgpset

E _FR0056_ BadOpen
Already open error, IIFRgpcontrol

E- FR0057- BadAlt
Bad parameter set, %Od, IIFRgpcontrol

E - FR0058- BadClose
Already closed error, IIFRgpcontrol

E _FR0059_BadState
Bad state, %Od, IIFRgpcontrol

S- FR005A- HGHT
Height (rows)

S- FR005B - WIDTH
Width (columns)

S- FR005C- SROW
Starting row

S- FR005D- SCOL
Starting column

S- FR005E- CROW
Current row

S- FR005F- CCOL
Current column
S- FR0060- TMOUT
Timeout

FR Class Messages 15-7

S- FR0061 - EACT
Entry activation
S- FR0062- DROW
Delete row
E_FROIOO_SQLDA_NULL
The address of the SQLDA in forms statement is a null pointer.
Explanation:

In a forms DESCRIBE statement, or forms USING clause with
an SQLDA the SQLDA object is pointing at a zero address.

System Status:

Run-time system will not execute the statement.

Recommendation:

Check the declaration and use of the SQLDA. The preprocessor
does not confirm that this is a valid SQLDA object.

E _ FROIOI_SQ_FORM_TABLE_BAD
Invalid or null form or table name in forms DESCRIBE statement.
Explanation:

In a forms DESCRIBE statement, the form or table name was
either null or invalid.

System Status:

Run-time system will not execute the statement.

Recommendation:

Confirm that you have initialized the form into the run-time
system before describing it.

E_FROI02_SQ_MODE_BAD
Unknown mode specification '%Oc' in fonns DESCRIBE statement.
Explanation:

In a forms DESCRIBE statement the specified mode was not one
of QUERY, READ or ALL.

System Status:

Run-time system will not execute the statement.

Recommendation:

Use the correct mode when describing a form.

E _ FROI03_ SQ_ NAME_BAD
Invalid syntax for name '%Oc' in forms SQLDA SQLNAME element %ld.
Explanation:

When using a SQLDA to execute a forms statement the name
specified in the SQLN AME field was invalid and could not be
processed.

System Status:

Run-time system will ignore this field/column and continue
processing the statement.

15-8

FR Class Messages

E_FROI04_SQ_NULL_IND
Indicator variable expected in fonns SQLDA SQLIND element %Od.
Explanation:

When using a SQLDA to execute a fonns statement the data type
(SQLTYPE) was negative, but no indicator variable (SQLIND)
was provided.

System Status:

Run-time system will ignore this field/column and continue
processing the statement.

E_FROI05_SQ_NULL_DATA
Data variable expected in fonns SQLDA SQLDATA element %Od.
Explanation:

When using a SQLDA to execute a fonns statement the data
address (SQLDATA) was zero. You must provide a data address
even if the value being assigned is null, as specified in the null
indicator.

System Status:

Run-time system will ignore this field/column and continue
processing the statement.

S- FR0150- cnoval- null
Column '%Oc', data type nullable % 1c, display fonnat %2c, has no validation check
S- FR0151 - cnoval
Column '%Oc', data type % 1c, display fonnat %2c, has no validation check
S- FR0152- chasval- null
Column '%Oc', data type nullable %lc, display fonnat %2c, has validation check '%3c'
S- FR0153- chasval
Column '%Oc', data type %lc, display fonnat %2c, has validation check '%3c'
S- FR0154- fnoval - null
Field '%Oc', data type nullable %Ic, display fonnat %2c, has no validation check
S- FR0155- fnoval
Field '%Oc', data type % Ic, display fonnat %2c, has no validation check
S- FR0156- fbasval - null
Field '%Oc', data type nullable %1c, display fonnat %2c, has validation check '%3c'
S- FR0157- fbasval
Field '%Oc', data type % Ic, display fonnat %2c, has validation check '%3c'
E - FR0158- Menuitemdoes
-not
No menuitem at position' %Od' in the current menu. You have pressed a key that is
mapped to a menuitem at a specific position. But the current menu does not contain a

FR Class Messages

15-9

menuitem at that position. Please check that you have pressed the correct key and make
another selection.
Explanation:

The user pressed a function/control key that is mapped to a
positional menuitem. Unfortunately there is no menuitem at that
position.

System Status:

Once user acknowledges the message, the forms system will
continue.

Recommendation:

User acknowledges message and continues on.

S- FR0159- RDONLY
Displayonly

S- FR015A- INVIS
Invisible
S- FR015B- SHELL
Shell
S- FR015F- LFRSK
LASTFRSKEY

15-10 FR Class Messages

FT Class Messages

S- FTOOOI - Number- of- fields to s
Number of fields to skip:
E- FT0002- Bad- value- entered- for
Bad value entered for SKIP FIELD command The input could not be converted to an
integer. Only numeric characters or the' -' may be entered.
Explanation:

Non-numeric characters probably entered.

System Status:

The skip field command will be aborted.

Recommendation:

User needs to select the skip field command again and enter a
proper numeric value.

E _FT0003 _FTbuild_passed_NULL_
Ffbuild: passed NULL pointer

E_FT0004

rFIELD_INIT_s_s_

\rFIELD INIT:(%s, %s) error in field window\r

E _ FTOOOS _rFIELD_INIT_s_ s_
\rFIELD INIT:(%s, %s) error in data window\r

E- FT0006TBL
-INIT

can t alloc

TBL INIT: can't allocate table field's window %s

E- FT0007

r FIELD- INIT- s s-

\rFIELD INIT:(%s,%s) error in data window\r

E - FT0008- Menuitem- d-does no
No menuitem at position '%Od' in the current menu. You have pressed a key that is
mapped to a menu item at a specific position. But the current menu does not contain a
menuitem at that position. Please check that you have pressed the correct key and make
another selection.
Explanation:

The user pressed a function/control key that is mapped to a
positional menuitem. Unfortunately there is no menuitem at that
position.
FT Class Messages

16-1

System Status:

Once user acknowledges the message, the forms system will
continue.

Recommendation:

User acknowledges message and continues on.

S_ FT0009 _Null_string_not_legal
No input found for menu selection. The current menu requires that you type in a
menuitem selection. Please enter a menuitem selection.
Explanation:

User has pressed the RETURN key with no characters in the
menu input area. The current menu requires that something be
typed in. This is really not an error since all menus should now
allow user to press the RETURN key with no problems.

System Status:

Once user acknowledges the message, the forms system will
continue.

Recommendation:

User acknowledges message and continues on.

E _ FTOOOA _ FTgtctl_called_when_1
Ffgtctl called when loaded against non-graphics framelib
file
name
S- FTOOOB - EnterEnter file name:
S_ FTOOOC _Error _ opening_file__
Error opening '%s' file [HIT RETURN]
S_ FTOOOD _ Writing_screen _ to _fll
Writing screen to '%s' file ...
S_ FTOOOE_ Appending_ screen_to _f
Appending screen to '%s' file ...
E _ FTOOOF_ Error

Current scree

Error: Current screen is empty.
S_ FTOOIO_Error _closing_file __
Error closing' %s' file [HIT RETURN]
S_ FTOOll_Error_attempting_to_p
Error attempting to print screen. [HIT RETURN]
E - FT0012- MENU
MENU
E _ FT0013 _ERR OR __bad_ editing_ mo
Unknown editing mode encountered. An unknown editing mode was passed to the forms
system while trying to run a display loop.
16-2

FT Class Messages

Please write down circumstances that led to the error and submit a Software Performance
Report (SPR).
Please retry operation or restart the application.
Explanation:

Unknown mode passed to Ffrun. Probably something is
corrupted.

System Status:

Returns control to runtime layer of forms system and continues
processing.

Recommendation:

User can retry the operation or restart the application.

S- FT0014- Number of fields to s
Number of fields to skip:
S- FT0015 - Bad- value- entered for
Bad value entered for SKIP FIELD command.
E _ FT0017 _Currently_unable_to _ e
Field is too wide to be edited Currently, only fields that are less than or equal to '%Od'
bytes wide may be edited by calling a system editor.
Explanation:

Field is too wide to be edited.

System Status:

Forms system will not call a system editor on the current field.

Recommendation:

User must continue editing field within the forms system.

E _ FT0018_Could_not _open _tempor
Could not open temporary edit file Please check that you have appropriate permissions
and quotas to call the system editor from the current directory.
Explanation:

Must be a permission or quota problem that prevents temp file
from being opened.

System Status:

Forms system will abort calling the system editor.

Recommendation:

User can continue editing within forms system.

S_ FT0019 _ nStarting_Editor __
Starting Editor ...

E - FTOOIA- Could- not start Editor
Could not start Editor. The system editor could not be started. Please check that
lNG_EDIT, if defined, points to a valid system editor. Also, make sure that your process
has appropriate quotas set.
Explanation:

lNG_EDIT may not be set correctly or process has low quotas.

System Status:

Forms system will abort calling the system editor.

Recommendation:

User can continue editing within forms system.

FT Class Messages

16-3

E _ FTOOIB _ Could_not_open _ tempor
Temporary editing file not found The forms system could not open the temporary editing
file for input. Please check that process quotas.
Explanation:

Couldn't open editing file for input.

System Status:

Field will not be changed.

Recommendation:

Changes made via the system editor is lost. User can try calling
the system editor again or remain in the forms system.

E _ FTOOIC _Data_in _file_too _hig_
Data in file too big for field Changes made in the system editor can not all fit into the
field.
Only data that fits will be placed back into field.
Explanation:

User entered too much data while in system editor.

System Status:

System will simply truncate the data.

Recommendation:

User should check field.

E_FTOOID _Data_in_file_too_hig_
Data in file too big for field Changes made in the system editor can not all fit into the
field. Only data that fits will be placed back into field.
Explanation:

User entered too much data while in system editor.

System Status:

System will simply truncate the data.

Recommendation:

User should check field.

E - FTOOIE- CANTOPEN
Can't open function key definition file.
E - FTOOIF- ERRSFND
Error(s) in mapping file. Error messages in '%Oc'. '% Ic'
E - FT0020- NUMCONV
An error occurred while converting a key number form its character representation.
E - FT0022- BSTART
Unknown keyword at beginning of a mapping line.
E - FT0023- FRSCTRL
No number specified for FRS/CONTROL key.
E - FT0024- FRSKEY
May not specify a FRS key greater than' %Od' .

16-4 FT Class Messages

E FT0025 UNKNOWN
Unknown command specified.
E_FT0026_NOEQUAL
Could not find the '=' character in a mapping line.

E- FT0027- PFKEY
Missing number for PF key after the '=' character.

E- FT0028- BPFKEY
PF key' %Od' does not exist for your terminal description.

E- FT0029- BADCMD
Invalid command found after the '=' character.

E- FT002A- OFFIGN
Ignoring excess characters after the 'OFF' keyword.

E- FT002B - BAD LABEL
A bad label was found in a mapping line.

E- FT002C - LBLIGN
Ignoring excess characters after a 'LABEL'.

E- FT002D- CTRLPF
No control or PF key specified in a mapping line.

E- FT002E- NODEFMAP
Could not open default system mapping file in the ULTRIX/SQL sql/files directory.

E - FT002F- NOMFILE
Could not open mapping file '%Oc'.

E - FT0030- INUSE
'%Oc' has already been mapped.

E- FT0031 - BADLCMD
Bad left hand size of '=' character passed to FKdomap.

E- FT0032- OVRRIDE
May not override mapping for' %Oc' .

E- FT0033- BADRCMD
Command on right hand size of '=' character may not be assigned to command of left
hand size of '=' character.

FT Class Messages

16-5

E - FT0034- KEYZERO
FRSkey/Menuitem numbers must start with one (1).

E - FT0035- MAXMENU
There is a current limit of '%Od' MENU positions that may be specified.

E - FT0036- NOESC
The ESCAPE key is not available for your terminal description.

E - FT0037- NOPFK
Your terminal description does not support function keys.

E - FT0038- RTMULEN
Can not display menuitems, it is longer than the width of the screen.

E - FT0039- TSTBADOPN
Can not open test file '%Oc'.

E - FT003A- IONOREDIR
Failed to redirect I/O for testing.

E - FT003B - INVALID - COMMAND
Not a valid command for BROWSE mode. You are currently in BROWSE mode. This
means that you may only move the cursor within and between fields. You may NOT
modify or enter values in fields. Your last command either tried to change a field value or
was a command not allowed in BROWSE mode. Please try again.
Explanation:

User tried to enter something into a field or entered a command
that is not supported by browse mode.

System Status:

System will just ignore the request and continue.

Recommendation:

User should make another request.

E - FT003C - NODISP
The forms system could not find desired form. The forms system was requested to display
a form that it could not find in its display list. This is probably due to memory corruption.
Please write down circumstances that led to this error and submit a Software Performance
Report (SPR).
This is a fatal error. You will need to restart your application.
Explanation:

The forms system tried to find a form in the list of display
structures but could not. This probably means something is
corrupted and we can not continue. This error is fatal.

System Status:

Once user acknowledges the error message, the application will
exit.

Recommendation:

User can do nothing since this is a fatal error.

16-6

FT Class Messages

E- FT003D- NOWIN
Structure allocation failed for forms system. The forms system could not allocate a
structure needed to display a popup style form. This may be caused by an out of memory
condition or by the size or starting position of the popup style form has been corrupted.
Please write down circumstances that led to this error and submit a Software Performance
Report (SPR). This is a fatal error. You will need to restart your application.
Explanation:

The forms system tried to allocate a new window structure for a
new form to be displayed in a popup style but failed.
This may be due to out of memory problem. This error is fatal.

System Status:

Once user acknowledges the error message, the application will
exit.

Recommendation:

User can do nothing since this is a fatal error.

E - FT003E - NOSWIN
Form data structure setup failed. The forms system failed to setup data structures needed
to display a popup style form. This may be due to the starting position of the popup style
form being corrupted.
Please write down circumstances that led to this error and submit a Software Performance
Report (SPR).
This is a fatal error. You will need to restart your application.
Explanation:

The forms system tried to create a subwindow for displaying just
the form area (excluding the border) for a popup style form but
failed. This may be due to errors in coordinate specifications and
should never happen. This error is fatal.

System Status:

Once user acknowledges the error message, the application will
exit.

Recommendation:

User can do nothing since this is a fatal error.

E_ FT003F_ is_ambiguous
Input "%Oc" is an ambiguous prefix. The current menu contains more than one menuitem
that begins with the string "%Oc". Please enter more characters to uniquely identify a
specific menuitem.
Explanation:

The user has entered a string that is not unique (i.e., more than
one menuitem start with the entered string. User must type in
more characters to make a selection.

System Status:

Once user acknowledges the message, the forms system will
continue.

Recommendation:

User acknowledges message and continues on.

FT Class Messages

16-7

E _ FT0040_is_not_prefix
Input "%Oc" is not a correct prefix. The current menu contains no menuitems that begin
with the string "%Oc". Please check what you have typed in and make any necessary
corrections.
Explanation:

User has entered a string that does not match any of the
menuitems in the current menu. User must correct his input.

System Status:

Once user acknowledges the message, the forms system will
continue.

Recommendation:

User acknowledges message and continues on.

16-8 FT Class Messages

FV Class Messages

E- FVOOOI- Internal- error

Internal error in datatype facility. An internal error occurred while checking datatype
compatibility in the validation string. This may indicate that the datatype manipulation
facility has been corrupted.
Please write down circumstances that led to the error and submit a Software Performance
Report (SPR). If a form is being initialized for use in an applicationthe form will not be
initialized and one may need to restart the application.
Explanation:

An error occurred while trying to compare field value againstthe
list of valid values.

System Status:

The field value will be rejected.

Recommendation:

User can try the operation again or may need to restart
theapplication.

E _ FV0002_ Bad_unary_function
Unknown operator found. While trying to check a field value,the system came across a
value that does not correspond to anyknown operators. This may be due to corrected data
structuresused by the validation system.
Please write down circumstances that led to the errorand submit a Software Performance
Report (SPR). One may try the operation again or try restarting the application.
Explanation:

Data structure did not have a known operator for usein validating
the field value.

System Status:

Field value will be rejected.

Recommendation:

User may retry the operation or restart the application.

E_FV0003_Inconsistency _in_data

Inconsistency in data structures found. The information needed to check the field value
was not found in the data structures used by the validation system. This may be due to an
error in the datatype manipulation facility.
Please write down circumstances that led to the error and submit a Software Performance
Report (SPR). One may try the operation again or try restarting the application.
Explanation:

The instance id for the comparison was not found.

System Status:

Field value will be rejected.

Recommendation:

User may retry the operation or restart the application.
FV Class Messages

17-1

E - FV0004- Internal- error
Fatal comparison error has occurred. An internal error occurred while trying to compare
the field value to a valid value. This may be due to an error in the datatype manipulation
facility.
Please write down circumstances that led to error and submit a Software Performance
Report (SPR). One can retry the operation or restart the application.
Explanation:

An error was returned from the comparison routine.

System Status:

Field value will be rejected.

Recommendation:

User may retry the operation or restart the application.

E - FV0005- Conversion error
Can not obtain field value. An error occurred while trying to obtain the field value to
check. This may be due to incorrect information in the data structures used by the
validation system.
Please write down circumstances that led to error and submit a Software Performance
Report (SPR). One can retry the operation or restart the application.
Explanation:

Error occurred while coercing field value to new typefor
comparison.

System Status:

Field value will be rejected.

Recommendation:

User may retry the operation or restart the application.

E _ FV0006_ Cant_get _ownercode
Can't get ownercode.
E_FV0007_table_not_found
Table '%Oc' not found.
E _ FV0008_ Cant_get_table _ attri
Can't get table attribute.
E_FV0009_No_attribute_found
No attribute found.
Table
E - FVOOOA-column
Table-column (%Oc. %lc) not found.
E _ FVOOOB _Bad_string
Bad string "%s" found
E _ FVOOOC _types_not _compat
type "%s" is not compatible with type "%s"
S- FVOOOD- MAKETREE
MAKETREE
17-2

FV Class Messages

E _ FVOOOE_parser _error
parser error

E- FVOOOF- Does- not - make- sense- t
Does not make sense to have constants on both sides of an operator

E- FVOOIO- Parser- error
Parser error

E_FVOOll_Unkown _operator_found
Unknown operator found

E_FV0012_Error_getting_operato
Error getting operator

E_ FV0013_Internal_parser _error
Internal parser error.

E- FV0014- Coercion- error
Coercion error

E- FV0015- Coercion error
Coercion error

E- FV0016- Coercion error
Coercion error

E- FV0017- Failed to convert
Failed to convert constant to appropriate datatype

E- FV0018- MAKETREE
MAKETREE

E - FV0019- Parser- error
Parser error

E _ FVOOIA_Can_only_use
Can only use '. 'with a table field

E- FVOOIB- Bad- column- name
Bad column name '%Oc' for table '% Ie'

E- FVOOI C- Unknown - constant
Unknown constant found

FV Class Messages

17-3

E_ FVOOID _parser _error
parser error

E _ FVOOIE_syntax_error
syntax error

17-4

FV Class Messages

GC Class Messages

E - GCOOOI - ASSOC - FAIL
Association failure
INV
E- GC0002-PARM
Invalid service request parameter
E - GC0003 - INV- SVC- CODE
Invalid service code in call sequence
E - GC0004- INV- PLIST - PTR
Invalid parameter list pointer
E - GC0005 - INV- ASSOC - ID
Invalid association identifier
E- GC0006DUP
-INIT
Duplicate initiate request
E - GC0007 - NO- PREY- INIT
No previous initiation request
E - GC0008- INV- MSG- TYPE
Invalid message type identifier
E - GC0009 - INV- BUF- AD DR
Invalid buffer address
E - GCOOOA- INT- PROT- LVL
Internal IPe prococollevel mismatch between client and server
E - GCOOOB - RMT- LOGIN - FAIL
Remote login failure: invalid password/userid
E - GCOOOD - ASSOCN - REFUSED
Association request refused by server
GC Class Messages

18-1

E- GCOOI0- BUF- TOO- SMALL
Buffer is too small: no room for data

E - GCOOllINV
-CONTENTS
Invalid buffer contents

E - GC0012 - LISTEN- FAIL
Failure to issue listen

E- GC0013- ASSFL- MEM
Association failure (memory allocation)

E- GC0014- SAVE- FAIL
Save failure: CL level system error

E - GC0015 - BAD - SAVE - NAME
Restore failure: save name not recognized

E- GC0016- RESTORE- FAIL
Restore failure: CL level system error

E - GC0017 - RSTR - OPEN
Restore failure: error opening restore file

E - GC0018 - RSTR - READ
Restore failure: error writing to restore file

E- GC0019 - RSTR- CLOSE
Restore failure: error closing restore file

E- GC0020- TIME- OUT
Time_out expiration: service request incomplete

E- GC002lNO
-PARTNER
Requested association partner is unavailable

E- GC0022NOT
-lACK
Association is in purge state due to expedited data receipt. Only GCA_IACK may be sent.

E - GC0023 - ASSOC - RLSED
Association was terminated by a GCA_RELEASE sent by one partner

E_GC0024_DUP _REQUEST
A duplicate request was currently outstanding on this association

18·2

GC Class Messages

E - GC0025NM
SRVR ID ERR
-

Unable to connect to Name Server: Name Server ID incorrect

E - GC0026 - NM - SRVR- ERR
Unable to connect to Name Server: system error during connection
E_ GC0027 _RQST_PURGED

Request was purged by interrupt message sent or received
E - GC0028- LISTEN- RESOURCE

GCA_LISTEN failed: server resource shortage.
Please see system administrator
E_GC0029_RQST_FAIL

GCA_REQUEST failed: unable to connect to server
E_GC002A_RQST_RESOURCE

GCA_REQUEST failed: server resource shortage.
Please see system administrator

E - GC002B - SNDl- FAIL
GCA_SEND failed: see system error status.
E - GC002C - SND2- FAIL

GCA_SEND failed: see system error status.
E - GC002D - SND3 - FAIL

GCA_SEND failed: see system error status.
E - GC002E - RCVl - FAIL

GCA_RECEIVE failed: see system error status.
E GC002F RCV2 FAIL
-

GCA_RECEIVE failed: see system error status.
E - GC0030- RCV3 - FAIL

GCA_RECEIVE failed: see system error status.
E GClOOl INTERNAL ERROR
-

Name Server internal error. invalid opcode %Od.
Please see system administrator.
E - GCl002DUP
-INIT

N arne Server internal error. Already initialized.
Please see system administrator.
GC Class Messages

18-3

E- GCI003- CANT- RESERVE- NS- ID
Name Server internal error. Can't reserve Name Server id.
Please see system administrator.
E- GCI004- SVRCLASS- NTFOUND
Name Service failed: Server Class %Oc is not found.
E- GCIOOSFILE
-OPEN
Cannot open file %Oc.
E- GCI006NOT
-USER
%Oc is not a valid name server user.
E- GCI007 - SYNTAX- ERR
Syntax Error: %Oc
E- GCI008- INV- SVC- CODE
N arne Server internal error. Invalid service code.
Please see system administrator.
E- GCI009 - INV- PLIST- PTR
N arne Server internal error. Invalid parameter list pointer
Please see system administrator.
E- GCIOIO- ALLOCATION- ERROR
N arne Server memory allocation error.
Please see system administrator.
E- GCIOllNS
-ERROR
Name Server returned error status:
E- GCI012BAD
-RECORD
Name Server read a bad record from file %Oc
E GCIIOO STARTUP

Name Server startup: rev level %Oc., process id %ld
E- GCIIOI - SHUTDOWN
Name Server normal shutdown, process id %Od
E- GCII02- ASSOC - BGIN
N arne Server association begins.
E GCII03 ASSOC END

Name Server association ends.

18-4 GC Class Messages

E - GCII04- SERVER- DEAD
N arne Server detected server %Oc % I c dead

E- GCII05- SERVER- ALIVE
Name Server detected server %Oc % Ic alive

E- GC2001 - STARTUP
Communication Server normal startup.

E - GC2002- SHUTDOWN
Communication Server normal shutdown., process id %Od

E - GC2003 - STARTUP- PARM
A Communication Server startup parameter was incorrectly specified.

E - GC2004 - ALLOCN- FAIL
Memory allocation failure in Communication Server.

E - GC2005INIT
-FAIL
Communication Server initialization failed.

E- GC2006- STARTUP
Communication Server startup: rev. level %Oc., process id %Id

E - GC2007 - NO- AUTH- INET
Communication Server startup failure: No authorization for ULTRIX/SQL/NET

E - GC2008- OUTOF
MEMORY
Comm Server memory shortage: unable to allocate object type %Oc.

E - GC2009 - IMMEDIATE- SHUTDOWN
Communication Server immediate shutdown., process id %Od

E - GC2010- PROTO- OPEN
Communication Server Protocol %Oc listening port % Ic

E - GC2011 - NUM- CONNS - MAX
Communication Server outbound %Od, inbound % I d

E- GC2201 - ASSOC - END
Normal local association termination: session end.

E - GC2202- AL- FSM- INP
AL internal error: Invalid input event in AL FSM

GC Class Messages

18-5

E - GC2203 - AL- FSM- STATE
AL internal error: Invalid state transition in AL FSM

E_GC2204_ASSOC_START
Normal local association initiation: session start.

E - GC2205RMT
-ABORT
Session failure: ABORT received from remote partner.

E - GC2206- LCL - ASSOC - FAIL
Session failure: association with local partner failed.

E - GC2207 - RMT- INIT- FAIL
Session failure: remote association initiation failed, status follows.

E - GC2208- CONNCTN- ABORT
Session failure: releasing local association.

E - GC2209SND
-FAIL
GCA send failure: reason follows.

E - GC220A- NRM - RCV- FAIL
GCA normal receive failure: reason follows.

E - GC220B - EXP- RCV - FAIL
GCA expedited receive failure: reason follows.

E - GC220C - AL - INIT- FAIL
GCC AL initialization failure: reason follows.

E - GC220D - AL - PASSWD- FAIL
GCC AL received an invalid user/password from a remote client.

E - GC220E - AL - FSM- STATE
AL internal error: Invalid state transition in AL FSM.
Input = %Od, state = % I d

E - GC220F- AL - INTERNAL- ERROR
GCC Comm Server AL internal error.
Please see system admimistrator.

E - GC2210LCL
ABORT
Session failure: Local ABORT condition.

E - GC2211- INCMG - ASSOC
Incoming association initiation from local user %Oc, as remote user % lc.
18-6

GC Class Messages

E - GC2212- OUTGNG- ASSOC
Outgoing local association initiation for remote user %Oc.

E - GC2213 - AL- NO - CCB
GCC internal error: CCB for connection %Od cannot be found.

E- GC2214- MAX IB CONNS
GCC server has exceeded max inbound connections.

E - GC2215- MAXOB
CONNS
GCC server has exceeded max outbound connections.

E - GC2216- GCA - LSN - FAIL
GCC AL processing of a GCA_LISTEN completion has failed.

E - GC2401 - CONNCTN - END
Normal Presentation Connection termination.

E - GC2402- PL- FSM- INP
PL internal error: Invalid input event in PL FSM

E - GC2403 - PL- FSM- STATE
PL internal error: Invalid state transition in PL FSM

E - GC2404 - PL- FSM- STATE
PL internal error: Invalid state transition in PL FSM.
Input = %Od, state = % 1d

E - GC2405 - PL- INTERNAL- ERROR
GCC Comm Server PL internal error. Please see system admimistrator.

E - GC2406 IE BAD- PC ONRSP
RSLT
PL internal error. P _CONNECT response result not ACCEPT or REJECT.
Please see system admimistrator.

E - GC2407 - IE- BAD- PCON- TYPE
PL internal error. P_CONNECT type not REQUEST or RESPONSE.
Please see system admimistrator.

E - GC2408 IE BADPRSL
-TYPE
PL internal error. P _RELEASE type not REQUEST or RESPONSE.
Please see system admimistrator.

GC Class Messages

18-7

E_ GC2409 _IE_BAD _SCON_RSP _RSLT
PL internal error. S_CONNECT confinn result not ACCEPT or REJECT.
Please see system admimistrator.

E- GC240A- IE- BAD- SCON- TYPE
PL internal error. S_CONNECT type not REQUEST or RESPONSE.
Please see system admimistrator.

E- GC240B - IE- BAD - SREL- CNF- RSLT
PL internal error. S_RELEASE confinn result not AFFIRMATIVE or NEGATIVE.
Please see system admimistrator.

E- GC240C - IE- BAD - SREL- TYPE
PL internal error. S_RELEASE type not INDICATION or CONFIRM.
Please see system admimistrator.

E - GC240D - IE- BAD - SUAB - PDU
PL internal error. S_U_ABORT PPDU_ID not ARP or ARU.
Please see system admimistrator.

E GC240E IE BAD
PL internal error. Bad INPUT event.
Please see system admimistrator.

E- GC240F- INIT - DOC - STACK
PL internal error. INIT_DOC_STACK Failed.
Please see system admimistrator.

E - GC2410 - PERF- CONY
PL internal error. PERFORM_CONVERSION Failed.
Please see system admimistrator.

E - GC2411 - OD- PTR- NULL
PL internal error. OD_PTR is NULL in INIT_DOC_STACK.
Please see system admimistrator.

E- GC2412- DOCEL
NULL
PL internal error. DOC_EL is NULL in PERFORM_CONVERSION.
Please see system admimistrator.

E- GC2413 - GET- NEXT - ATOM
PL internal error. GET_NEXT_ATOM failed in PERFORM_CONVERSION.
Please see system admimistrator.

18-8 GC Class Messages

E- GC2414- HETERONET
-DISABLED
PL internal error. Heterogeneous connections are not available
Please see system administrator.

E- GC2415 - PL- ADF- ERROR
PL internal error. Can't initiatlize ADF datatypes
Please see system administrator.

E- GC2601 - CONNCTN- END
Normal Session Connection termination.

E- GC2602- SL- FSM- INP
SL internal error: Invalid input event in SL FSM

E - GC2603- SL- FSM- STATE
SL internal error: Invalid state transition in SL FSM

E- GC2604- SL- FSM- STATE
SL internal error: Invalid state transition in SL FSM.
Input = %Od, state = % I d

E- GC2605- SL- INTERNAL- ERROR
GCC Comm Server SL internal error. Please see system admimistrator.

E- GC2801 - NTWK- CONNCTN- START
Normal Network Connection initiation.

E- GC2802 - NTWK- CONNCTN- END
Normal Network Connection termination.

E- GC2803- PROT- ID
Invalid (unknown) %Oc identifier.
Check NETU node and account information.

E- GC2805 - INTERNAL- ERROR
TL internal error: Invalid input event in TL FSM

E- GC2806- TL- FSM- INP
TL internal error: Invalid input event in TL FSM

E- GC2807 - TL- FSM- STATE
TL internal error: Invalid state transition in TL FSM

E- GC2808- NTWK- OPEN- FAIL
Network open failed for protocol %Oc, listen port %lc; status follows.
GC Class Messages

18-9

E - GC2809 - NTWK- CONNECTION- FAIL
Network connection failed for protocol %Oc, to node % Ie, port %2c; status follows.

E- GC280A- NTWK- INIT- FAIL
Network initialization failure: all protocol opens failed

E - GC280B - TL - INIT- FAIL
GCC TL initialization failure.

E - GC280C - TL- FSM- STATE
TL internal error: Invalid state transition in TL FSM.
Input = %Od, state = % I d

E - GC280D - NTWK- ERROR
Network operation error: See Comm. Server log for detail.

E- GC280E- TL - INTERNAL- ERROR
GCC Comm Server TL internal error. Please see system admimistrator.

E- GC280F- OUTGNG- NTWK- CONNCTN
Outgoing network connection: remote connection id = %Ox.

E- GC2810- INCMG - NTWK- CONNCTN
Incoming network connection: remote connection id = %Ox.

E- GC2811 - TL- INVALID - TPDU
TL internal error: Received invalid TPDU type %Ox.

E- GC2812 - TL- INVALID - CONNCTN
TL internal error: Received unknown connection id %Od from partner.

E- GC2813 - NTWKLSN
-FAIL
Network listen failed for protocol %Oc, listen port % lc; status follows.

E GCFFFF IN PROCESS
Request is not complete

18-10 GC Class Messages

IC Class Messages

E _ ICOOOl_must_be_ superuser
You must be an ULTRIX/SQL superuser to run this program.
E _IC0002_Cant _find_image
ACCESSDB: Couldn't find INGCNTRL image.
E - IC0003- Cant- delete- locations
Locations may no longer be deleted once they are created.
S- IC0004- Add- Locations- Form
Add Locations Form
E - ICOOOS- Invalid- location- name
Invalid location name.
S- IC0006- Unknown- loc- wanna- new
Unknown location - do you want to create a new one?
E _IC0007 _Ingres_path_not _exist
An ULTRIX/SQL %Oc path doesn't exist on % Ie
S_IC0008_Location _Appended
Location Appended.
E - IC0009- Cannot- delete- loc
Cannot delete location because a database directory exists there.
E - ICOOOA- Cannot- delete- locatio
Cannot delete location because journals or checkpoints are on this location.
E - ICOOOB- Location- Deleted
Location Deleted.

Ie Class Messages

19-1

S- ICOOOC - Cannotuse
-location
Use of location is specified as NO for Databases, Journals, & Checkpoints.
Cannot use location - Do you want to save anyway?
E_ICOOOD _ Cant_findJmage
CATALOGDB: Couldn't find INGCNTRL image.
E _ ICOOOE_Full_pathname_too_big
Pathname too long.
Full pathname %Oc for location % lc exceeds max length of %2d
S _I COOOF _ Starting_Target_DBMS
Starting up Target Database ...
E _ICOOIO_Error _ opening_target
Error opening database '%Oc' for extending
E - ICOOll - cannot- restart- iidbdb
Sorry, cannot restart the 'iidbdb'.
S_ IC0012_ Restarting_the_IIDBDB
Restarting the IIDBDB ...
E - IC0013 - cannot- restart- iidbdb
Can not restart the iidbdb database.
Error status returned: %Od
E - IC0014- defineloc
-error
Error(s) executing the DEFINE LOCATION command
S- IC0015 - INGRES - CONTROL- PROGRA
ULTRIX/SQL CONTROL PROGRAM
S_IC0016 _Catalog_listing
Catalog listing
S_IC0017 _Database_prompt
Database:
S_ IC0018_DBA_name _prompt
DBA name:
S_ IC0019 _Location_Name _prompt
Location Name:

19-2

Ie Class Messages

S_ICOOIA _ User _name _prompt
User name:
S_ICOOIB _Manager _Menu_Form
Manager Menu Form
S- ICOOIC - User- Menu- Form
User Menu Form
S- ICOOID-db-form
db form
S_ ICOOIE _ Retrieving_db _info
Retrieving database information ...
E - ICOOIF- Databasenot
exist
Database does not exist or is not owned by you.
E - IC0020- Database- doesnt - exist
Database does not exist.
S_IC0021_Validating_user _names
Validating user names ...
E - IC0022- User- doesnt- exist
User' %Oc' does not exist.
User authorization failure - user '%Oc' does not exist. A user must be defined as an
ULTRIX/SQL user before they can be authorized to access a database.
S_IC0023 _ Updating_database
Updating database ...
E _ IC0064_Err _getting_CDBinfo
Error selecting coordinator database info.
An error occurred while selecting information about the coordinator database for
distributed database '%Oc'. The error occurred while attempting to select from the
'iistar_cdbs' catalog.
E - IC0065- No - CDB - info found
No CDB. info found for Distributed Database
No coordinator information found for distributed database. There is an integrity problem
in your 'iidbdb' system catalogs: this distributed database does not have a corresponding
row in the 'iistar_cdbs' catalog to describe its Coordinator Database information.

IC Class Messages

19-3

E- IC0066- access- unknown
Database not public or private.
Accessdb was unable to determine whether this is a public or private database. The
public/private access information for this database will not be changed. Please note
exactly what you entered and submit a Software Performance Report (SPR).

S- IC0025- Database- table
Database Catalog

S_IC0026_Retrieving_db _names
Retrieving database names . . .

E- IC0027- Can t create- file
Can't create %Oc

E _IC0028_Can _t _copy _file
Can't copy %Oc

E- IC0029- Can t rename

s to

Can't rename %Oc to % I c

E - IC002A- Failed to write- file
Failed to write %Oc

E _IC002B _Cant _cre_temp_users_f
Cannot create temporary users file

E _IC002C _Cannot _replace _ usr _fi
Cannot replace usr file

E- IC002Dbad
-username
'%Oc' is not a valid usemame.
U semame must be alphanumeric and at most % 1d characters long

E - IC002Ebad
-name
'%Oc' is not a valid name.
N arne must be alphanumeric and at most % 1d characters long

E _IC0030_Cannot_open _Dump_file
Cannot open -D file %Oc.

E- IC0031 - Cannot- do-Z-test
Cannot do -Z test on %Oc.

E_IC0032_Bad_flag
Bad flag: %Oc
19-4

IC Class Messages

E _ IC0033_Bad_argument
Bad argument: %Oc
S_ IC0034 _accessdb _catalogdb
accessdb/catalogdb
start
INGRES
E- IC0035- CannotCannot start up ULTRIX/SQL.
E _IC0036_ no_authority
You do not have proper authority or privilege to run Accessdb.
E - IC0060- Not- INGRES - DBMS
ULTRIX/SQL database required
This program may only be run on an ULTRIX/SQL database. The 'iidbcapabilities'
catalog in your 'iidbdb' database does not contain a row indicating that it is an
ULTRIX/SQL database. Exiting ...
E - IC0037 be theiidbdb
-dba
You must run as the DBA of the 'iidbdb' to use manager mode.
S_IC0038 _Accessing_Databases
Accessing Databases ...
S_ IC0039 _ Exiting_ Accessdb
Exiting Accessdb ...
S_ IC003A_ Exiting_ Catalogdb
Exiting Catalogdb ...
S_IC003B _Usage_statement
Usage: %Oc [-m] [-uname]
Usage: %Oc [-m] [-uname], where -m means run as ULTRIX/SQL manager, and -uname
means run as the specified user name.
S_ IC003D _Location_Listing
Location Listing
S- IC003E - Extenddb- Form
Extenddb Form
S_ IC003F_ Looking_up_ Locations
Looking up Location Names ...

IC Class Messages

19-5

S_IC0040_ s_is_not _a_DBA
'%Oc' is not a DBA.
In order to extend databases to alternate locations, you must know the DBA's username
for the databases you wish to extend. '%Oc' is not the DBA forany database.

S_IC0041_Validating_DB _extens
Validating Database Extensions ...

E _IC0042_Location_already_exis
Location %Oc already exists for Database %Oc.

S_IC0043_ Attempting_Re _Extend
Attempting to Re-Extend the Database ...

S_IC0044_Creating_the _New_ Exte
Creating the New Extension(s) ...

E _IC0045 _Error _retrieving_area
Error(s) retrieving area data

E _IC0046_Errors_extending_db
Error(s) occurred extending the database

E _IC0047_ Missing_data
Missing data

E _IC0048_db_not _belong_to _dba
Data base doesn't exist or belong to this DBA

E - IC0049- Location- doesnt- exist
Location name '%Oc' does not exist.
You must create a new location before you can extend databases to it.The location '%Oc'
does not exist.

E - IC004A- Location is not avail
Location '%Oc' not available for databases.
Databases and database tables may not be created on location' %Oc' .

S- IC004BUser
form
User form

S- IC004C - Unknownuser
-want new
Unknown user - do you want to create a new user?
S_IC004D _ Working_dot_dot_dot
Working ...
19-6

IC Class Messages

E _IC004E_A_user _already_exists
A user already exists with that name.
E - IC004F- Cannotadd
user
Cannot add user '%Oc'.
E _ IC0050_list_has_ illegal_name
Database access list contains illegal database name: '%Oc'.
E _IC0051_cant_change_ingres
Changing the name of the $ingres user is not permitted
E - IC0052- Cant- delete - new- user
Cannot delete new user
E _ IC0053 _User _name_changed
User name changed. Delete ambiguous - not performed
E - IC0054- Cannot- delete- INGRES
Cannot delete the $ingres user
E - IC0055- User - is- a - DBA no del
User is a DBA. Delete not performed
E - IC0056- User - does- not- exist
User does not exist; cannot delete
S- IC0057User
-table
User table
S_IC0058_ Retrieving_user _names
Retrieving user names . . .
S- IC0059 - Get- Form- Error
An Error occurred while Initializing Forms.
This is a Fatal Error, as the forms necessary for the execution of this program cannot be
initialized.
E _IC0061_Other_startup_err
Error starting ULTRIX/SQL.
Error' %Ox' occurred when Accessdb/Catalogdb tried to connect to the database. The
preceeding error messages should explain what type of error occurred. If not, then please
submit a Software Performance Report (SPR).

IC Class Messages

19-7

S_ IC0062_User_Not _In_Group
User '%s' is not currently a member of Group '%s'. Do you want to add User '%s' to
Group '%s' (y or n)?
Parameters:

1st %s User name to be updated in system catalogs2nd %s
Group name to be updated in system catalogs3rd %s User
name to be updated in system catalogs4th %s Group name to
be updated in system catalogs

Explanation:

This string is to be used as input to an STprintf call which will
make the proper substitutions to produce a string suitable for
input to a prompt popup. Hence the %s's. User has specified a
default group to which (s)he is not a member.

System Status:

The user will be added as a member of the named group or the
update will be canceled, depending on the user's response.

Recommendation:

Answer yes or no.

E_IC0063_No_Such_Group
Group' %Oc' does not exist
Default group must have been created with an SQL 'CREATE GROUP' command.
Parameters:

%0 Group name user is trying to make the default group.

Explanation:

User has specified a default group which does not exist.

System Status:

No update will be performed. Frame is resumed.

Recommendation:

Specify a proper default group or none.

E _ I C0024_ A_grp _already_exists
A group already exists with that name.
User name/group name collisions are not allowed.
Parameters:

None

Explanation:

User has specified a user name which is identical to an already
existing group name. User name - group name collisions are not
allowed.

System Status:

Control reverts back to the main ctrl menu frame.

Recommendation:

Select User frame again and specify a different user name.

E _ IC002F_A_role_already _exists
A role already exists with that name.
User name/role name collisions are not allowed.
Parameters:

None

Explanation:

User has specified a user name which is identical to an already
existing role name. User name - role name collisions are not
allowed.

19-8

IC Class Messages

System Status:

Control reverts back to the main ctrl menu frame.

Recommendation:

Select User frame again and specify a different user name.

IC Class Messages

19-9

LC Class Messages

E - LCOOOI - SERVICE- FAIL
GCA protocol service (%Oc) failure.
Internal service status % 1c.
Explanation:

GCA protocol services are those used to communicate with a
gatewayor DBMS server. Most services are associated with
either sending or receiving data. The first parameter specifies the
internal service name. The second parameter specifies the status
that returned from GCA. This status may also include a
system-dependent statusreason, or, if unavailable, will just be a
hex number. Under most situations the front-end communication
interface will terminate processing.

E _ LCOOIO_ ASSOC _REJECT
Request to connect to server rejected (protocol message type %Oc).
Explanation:

In most cases connection errors are the result of the failure to
connect to the database (for example, the database did not
exist,you have no permission, etc). In some cases, the connection
error is due to a communication protocol error. In this case the
above error is returned. The parameter specifies the data type of
the protocol message that rejected the connection request.

E _ LCOOI2_ ASSOC _RESTORE_DATA
Error in internal DBMS session restoration data.
Missing '%Oc' operator in saved data string.
Explanation:

When you issue a CALL statement, or you are in an
ULTRIX/SQL front-end that calls up another ULTRIX/SQL
subsystem, the run-time system attaches both processes to the
same communication channel. The second invoked process
restores its communicate state from data passed in by the first
process. This data was not of the expected syntax and
consequently the second process could not be invoked.

LC Class Messages

20-1

E - LC0013 - ASSOCNO
-NAME
The symbol '%Oc' has not been assigned a value.
Unable to connect to DBMS session.
Explanation:

In order to connect to a database certain symbols must be
assigned a value. The specified symbol was not assigned a value
and the connection failed. Consult the ULTRIX/SQL Operations
Guide for moredetails on the meaning of the specified symbol.

E - LC0020- READ - SETUP- FAIL
Protocol read setup failure.
Expected to read message type %Oc, but read type % 1c with %2c bytes.
Explanation:

Certain queries require the application to read formatted data
from the DBMS. For example, a cursor FETCH reads a row from
the database. The attempt to read failed and the wrong
communications message type was returned. The type returned
and the number of bytes will help isolate the problem.

E - LC0021 - READ - SHORT- DATA
Protocol data read failure.
At end of message %Oc, expected to read % 1c bytes but read only %2c bytes.
Explanation:

Certain queries require the application to read formatted data
from the DBMS. For example, a cursor FETCH reads a row from
the database. The attempt to read failed due to the early
termination of the communications message. For example, the
cursor row was shorter than specified in the initial internal
descriptor.

E _ LC0022 _READ _ WRONG _MESSAG E
Protocol data read failure.
Found message %Oc while reading message % Ic, and read only %2c bytes.
Explanation:

Certain queries require the application to read formatted data
from the DBMS. For example, a cursor FETCH reads a row
fromthe database. The attempt to read failed due to the early
termination of the communications message and its continuation
into an unrelated communications message.
For example, an internal identifier overflowed into the data
portion of a cursor row.

E - LC0023 - READ - AFTER - EOD
Protocol data read failure.
Trying to read from message %Oc after detecting end of data.
Explanation:

20-2

LC Class Messages

Certain queries require the application to read formatted data
from the DBMS. For example, a cursor FETCH reads a row from
the database. The attempt to read failed because all the requested

results of the query were already processed and there are no
more.
For example, an internal row descriptorhas already been read but
an attempt is made to read more of it.

E - LC0024- READ - BAD- TYPE
Protocol read failure.
Ignoring invalid or unknown message type %Oc from OCA_INTERPRET.
Explanation:

All queries read something from the DBMS. Some queries read
formatted data (for example a cursor row) while others just read
a status. The attempt to read failed due to an undefined
communications message type being returned.

E _ LC0025 _READ _ASSOC _FAIL
Protocol read failure.
Association with database partner failed (OCA_RECEIVE) with status %Oc.
Explanation:

All queries read something from the DBMS. Some queries read
formatted data (for example a cursor row) while others just read
a status. The attempt failed due to a failure in the
communications system (for example, your network connection
may have failed).
The parameter specifies the status that returned from OCA. This
status may also include a system-dependent status reason, or, if
unavailable, will just be a hex number. Under all situations the
front-end communication interface will terminate processing.

E - LC0030 - WRITE - SEND- FAIL
OCA protocol service (%Oc) failure with message type % lc.
Internal service status %2c.
Explanation:

All queries and database requests are sent via the
communications system, OCA. The first parameter specifies the
internal OCA service name. The second parameter specifies the
message type that the application was trying to send (for
example, FETCH or QUERY). The last parameter specifies the
status that returned from OCA.This status may also include a
system-dependent status reason, or, if unavailable, will just be a
hex number. Under most situations the front-end communication
interface will terminate processing.

E - LC0031 - WRITE - ASSOC - FAIL
Protocol write failure.
Association with database partner failed (OCA_SEND) with status %Oc.
Explanation:

All queries and database requests are sent via the
communications system, OCA. The attempt failed due to a
failure in the communications system (for example, your
network connection may have failed). The parameter specifies
LC Class Messages

20-3

the status that returned from GCA. This status may also include a
system-dependent status reason, or, if unavailable, will just be a
hex number. Under most situations the front-end communication
interface will terminate processing.

20-4

LC Class Messages

LQ Class Messages

E_LQOOOl_ STARTUP

Failed to connect to DBMS session.
Explanation:

The attempt to connect to a DBMS failed. Prior to this error
message there should have been another error message
displayed. This message is only displayed if the failure was not
due to obvious reasons, such as non-existent database, wrong
permissions, or an invalid command-line flag. This message will
usually be displayed if the communications system failed.

E _LQ0002_ USTARTUP

Failure to connect to DBMS. Operating system error %Oc.
Explanation:

Under certain circumstances the failure to connect to a DBMS is
due to operation system reasons. For example lack of process
resources or quotas. If this is the reason, then an attempt will be
made to display the system error message text so that the system
administrator or DBA can be informed.

E_LQ0003_ADFINIT

System unsuccessful in initializing Abstract Data-Type Facility. Exiting ...
Explanation:

When connecting to a DBMS the above facility (ADF) must be
initialized in order to process queries and data values. If the
facility could not be initialized then it will display an error
message. Upon return the above message will be displayed and
the connection will not be made and the application will
terminate.

E_LQ0004_TWODB

Attempt to connect to DBMS twice in one process.
Explanation:

You are not allowed to connect to 2 ULTRIX/SQL databases at
the same time in one process. You must exit one database in
order to start up another (or the same one again).

LQ Class Messages

21-1

E _ LQOOOS_FLAGS
DBMS connection flag '%Oc' is no longer supported.
Explanation:

The specified connection startup flag is not supported in
ULTRIX/SQL. You should modify your application, or your
command line, so that it does not issue this startup flag any more.

E_LQ0006_ASSOC_BAD _FLAG
Unknown or null DBMS connection startup argument %Oc.
Explanation:

Each startup argument must correspond to a legal ULTRIX/SQL
startup flag as specified in the ULTRIX/SQL manual. The
specified argument is not a legal flag and should be removed
from the application or command line. This message is also
issued if no database name (or a null database name) is specified.

E_LQ0007 _PRINTQRY
Failed to open '%Oc' file in current directory.
Unable to provide internal query trace information.
Explanation:

When assigning the value "printqry" or "printgca" to the symbol
II_EMBED_SET, the run-time system records all your queries or
communication message into the specified file in the current
directory. For certain reasons (such as permissions or quotas) the
trace file could not be opened. This will not have any effect on
the processing of your queries.

E _ LQ0008_ XID
Syntax error in WITH clause on CONNECT statement.
The distributed transaction ids are incorrectly specified.
Explanation:

When reconnecting after a broken connection during two-phase
commit, the distributed transaction id must be the only
component of a WITH clause. Furthermore the HIGHDXID must
be specified before the LOWDXID.

E _ LQ0009_ GCFMT
Communications or transmission error received without text.
The generic error number is %Oc, the local error is % lc, and the number of parameters is
%2c (should be 1).
Explanation:

21-2

LQ Class Messages

A GCA communications error has occurred, but the error format
(incorrectly) included no text.

E_LQOOOA_EMBBAD
Conversion failure from column %Oc into program variable.
Explanation:

When retrieving data from the database, the data being assigned
into your result variable could not be converted to the correct
type. This could be due incompatibilities between types, lengths
or other data type issues. The parameter specifies which column
number in the retrieval the error occurred.

E _LQOOOB _ EMBOVFL
Overflow of numeric data from column %Oc into program variable.
Explanation:

When retrieving data from the database, the numeric data being
assigned into your result variable caused an overflow condition.
You should provide a larger result variable. The parameter
specifies which column number in the retrieval the error
occurred.

E_ LQOOOC _EMBCNV
Column %Oc can not be converted into program variable.
Data types are incompatible.
Explanation:

When retrieving data from the database, the data being assigned
into your result variable was incompatible with the data type of
the result variable. You should modify the data type of the result
so that it can retrieve the data. A general rule states that all
numerics are compatible with each-other, as are all strings.
Strings and numerics are not compatible. The parameter
specifies which column number in the retrieval the error
occurred.

E_ LQOOOD _EMBDTID
Column %Oc can not be converted into program variable.
Unrecognized internal data type in conversion routine.
Explanation:

When retrieving data from the database, the data could not be
assigned into your result variable as the data type of the variable
was invalid. You should reissue the retrieval (and rebuild the
application) to confirm that this error is not due to a coding error.
The parameter specifies which column number in the retrieval
the error occurred.

E _LQOOOE_EMBIND
No null indicator supplied with program variable.
Null data from column %Oc can not be converted.
Explanation:

When retrieving data from the database, the NULL data could
not be assigned into your result variable as there was no null
indicator provided. Nullable data can be assigned to a variable

LQ Class Messages

21-3

that does not have a null indicator, though if the data is NULL
then this error will be issued. The parameter specifies which
column number in the retrieval the error occurred.
E _ LQOOIO_ EMBNULLIN
Null address of program variable in input statement.
Variable cannot be used to set values.
Explanation:

When setting data in the database from a program variable, the
variable had a zero address. Consequently, no data could be
assigned into the database.

E _ LQOOl1_EMBNULLOUT
Null address of program variable in output statement.
Data cannot be retrieved from column %Oc into variable.
Explanation:

When retrieving data from the database, the data could not be
assigned into your result variable as there was a zero result
variable data address. The parameter specifies which column
number in the retrieval the error occurred.

E _ LQ0012_ DBTOOLONG
Length of result data (%Oc) is too long for processing.
Data cannot be retrieved from column %lc into variable.
Explanation:

When retrieving data from the database, the data could not be
assigned into your result variable as the internal data was too
long for processing. If the data to be retrieved is longer than your
result variable, then the communications interface uses a
temporary buffer to receive that data. This temporary buffer was
not long enough. The parameter specifies which column number
in the retrieval the error occurred.

E_LQ0014_DBVAR
Invalid type or length describing program data.
Unable to convert into internal format.
Explanation:

When setting data in the database from a program variable, the
variable had an invalid type or length associated with it.
Consequently, no data could be assigned into the database. You
should reissue the statement (and rebuild the application) to
confirm that this error is not due to a coding error.

E_LQ0015_DBOVF
Overflow on converting numeric program data into internal format.
Explanation:

21-4

LQ Class Messages

When setting data in the database from a program variable, an
overflow error occurred while converting from a program
variable to an internal representation. Consequently, no data
could be assigned into the database.

E_LQ0016_DBNULL
Unable to convert null program data.
Internal format is non-nullable.
Explanation:

When setting data in the database from a program variable, a
conversion error occurred while converting from a program
variable with a null indicator (which is set) to an internal
non-nullable representation. Consequently, no data could be
assigned into the database.

E_LQ0017_DBCONV
Conversion failure from program data into internal format.
Explanation:

When setting data in the database from a program variable, a
conversion error occurred. This could be due incompatibilities
between types, lengthS or other data type issues.

E _ LQ0018_ DBQRY_NULL
Run-time component of query is NULL valued.
Variables or fields used in parts of queries must not be NULL.
Explanation:

When using variables or fields to replace parts of a query you
must not use the NULL value. This can occur when using a 4GL
field to replace a query component. Replace the field with a valid
syntactic value.

System Status:

Query is ignored.

Recommendation:

Replace the field or variable with a valid query component.

E_LQ002A_NODB
The '%Oc' query has been issued outside of a DBMS session.
EXiting ...
Explanation:

The specified query was issued without any connection to a
DBMS. This error may occur if you either did not issue any
CONNECT or ULTRIX/SQL statement, or if the connection
failed and the application continued. If you are running an
Embedded SQL application, make sure you allow the printing of
errors as previous errors may help solve the source of this error
message.

E_LQ002B_INQUERY
'%Oc' may not be nested within a data retrieval loop.
Explanation:

No database statements may be issued within a
SELECT/RETRIEVE loop. In order to terminate a data retrieval
loop, you must either let it run to completion or issue an
ENDSELECT/ENDRETRIEVE statement.

LQ Class Messages

21-5

E_LQ002C_INPROC
'%Oc' may not be issued while a database procedure is being processed.
Explanation:

The specified query was issued during the processing of a
database procedure. Even if the procedure could not be invoked,
and this caused an error handled by the calling application, you
may not issue any database statements until database procedure
processing is complete. When control is returned to the run-time
system, the procedure processing will be terminated. A database
procedure must either run to completion or be terminated via the
WHENEVER OOTO action for Embedded SQL error handling.

E_LQ0030_UTBAD
Run-time CALL statement to subsystem '%Oc' failed.
Explanation:

The CALL statement failed. The called subsystem is either
non-callable, or when it started up it issued an error of its own
specifying why it failed to start.

E_ LQ0036_INTERRUPT
Attempt to interrupt query processing failed.
Explanation:

The current query could not be interrupted. Queries are
interrupted when an ENDSELECT/ENDRETRIEVE is issued
from within a data retrieval loop, or from a direct call to the
run-time procedure "IIbreak".

E_LQ003A_RETINIT
Cannot start up '%Oc' query.
Unexpected initial protocol response.
Explanation:

This error is issued if a SELECT/RETRIEVE statement could
not be processed, but did not issue any other, more specific error.
This error indicates that the data retrieval query was not
successfully processed in the DBMS.

E_LQ003B_RETDESC
Cannot execute '%Oc' command.
Unable to read query protocol result data description.
Explanation:

This error is issued if a SELECT/RETRIEVE statement could
not be processed, but did not issue another more specific error.
This error indicates that the initial internal response to the data
retrieval query was not formated correctly.

E_LQ0040_SHORTREAD
Protocol read-failure on internal data.
Execution of this query is stopped.
Explanation:

21-6

LQ Class Messages

When retrieving data from the DBMS, the data read did not
satisfy the read request. If there was no other more specific

communications-failure error message, then try to run the current
query in the Terminal Monitor to confirm that the error is not
data -dependent.
E_LQ004A_REPDEF
Error in reading or storing internal repeated query identifier.
Explanation:

When issuing a repeated query the run-time system stores the
query identifier for subsequent execution. This error implies that
either the query identifier could not be added to the internal list
because of memory resources, or that the DBMS was not able to
process the query and return the query identifier. Convert the
query to a regular non-repeated query.

E_LQ004B_UNDEFREP
Repeated query '%Oc' is not defined.
Unexpected protocol response when reading query identifier.
Explanation:

When issuing a repeated query the run-time system stores the
query identifier for subsequent execution. This error implies the
DBMS was not able to process
the query and return the query identifier, but returned no specific
error for this failure. Convert the query to a regular non-repeated
query.

E_LQ0055_CSOPEN
Cursor' %Oc' cannot be opened.
Unexpected initial protocol response.
Explanation:

This error is issued if a cursor OPEN statement could not be
processed, but did not issue any other, more specific error. This
error indicates that the request to open the named cursor was not
successfully processed in the DBMS.

E_LQ0056_CSDESC
Cursor '%Oc' cannot be opened.
Unable to read query protocol cursor row description.
Explanation:

This error is issued if a cursor OPEN statement could not be
processed, but did not issue another more specific error. This
error indicates that the initial internal response to the OPEN
request was not formated correctly.

E _ LQ0057_ CSALLOC
Cursor' %Oc' cannot be opened.
Unable to allocate memory for internal cursor state.
Explanation:

When opening a cursor an internal descriptor is allocated to
maintain the cursor state. The internal descriptor could not be
allocated due to the shortage of memory. If you have many

LQ Class Messages

21-7

cursors open at the same time, try to close some so that there will
be less memory demands.
E _ LQ0058_ CSNOTOPEN
Cursor '%Oc' not open for '% 1c' command.
Explanation:

In order to execute an cursor statement (other than OPEN) the
cursor must have been successfully opened.

E _ LQ0059_ CSINIT
Unable to start up '%Oc % 1c' command.
Unexpected initial protocol response.
Explanation:

This error is issued if the specified cursor statement could not be
processed, but did not issue any other, more specific error. This
error indicates that the request to execute the statement on the
cursor was not successfully processed in the DBMS.

E_LQ005A_ CSCOLS
Too few columns accessed with cursor '%Oc'.
Explanation:

A cursor retrieval must access all the columns specified in the
cursor declaration. The remaining unread result data will be
discarded.

E_LQ005B_CSXCOLS
Trying to access more columns than declared with '%Oc %lc' command.
Explanation:

A cursor retrieval must only access the columns specified in the
cursor declaration. The remaining result variables will be left
unchanged.

E_LQ005C_CSRDO
Incorrectly specified FOR READ ONLY clause in repeated cursor statement.
Explanation:

The FOR READONLY clause was specified in a host string
variable. The variable must either be empty or must specify the
FOR READONLY clause (case is ignored).

E _ LQ006A _SQMULTSEL
The result of a singleton SELECT query is a table of more than one row.
Explanation:

21-8 LQ Class Messages

An SQL singleton SELECT statement returned more than one
row. The result variables will be assigned the data from the first
row. The remaining rows will be discarded.

E _ LQ006B _ SQNULLDYN
The SQLDA field SQLIND for column %Oc should be a non-null pointer.
Explanation:

A Dynamic SQL descriptor was used to EXECUTE a prepared
statement or FETCH from a dynamic cursor. The data type of the
specified SQLVAR was negative, though no null indicator was
provided.

E_LQ006C_SQVARDYN
The SQLDA field SQLDATA for column %Oc contains a null data pointer.
Explanation:

A Dynamic SQL descriptor was used to EXECUTE a prepared
statement or FETCH from a dynamic cursor. The data address of
the specified SQLVAR was zero. The current column will be
skipped during processing.

E_LQ006D _SQDESC
Failed to DESCRIBE dynamic SQL statement.
Unable to read query protocol statement description.
Explanation:

This error is issued if a DESCRIBE statement could not be
processed, but did not issue another more specific error. This
error indicates that the initial internal response to the
DESCRIBE request was not formated correctly.

E_LQ006E_SQLDA
The address of the SQLDA is zero.
Explanation:

When using the DESCRIBE statement, or processing the
execution of a Dynamic SQL statement with an SQLDA, the
address of the descriptor is zero. If you are dynamically
allocating the descriptor then confirm that you have checked the
return values of allocation routines, and have initialized the
relevant fields of the SQLDA.

E_LQ0080_QRYID
Error in reading query or cursor internal identifier.
Explanation:

When opening a cursor, initially executing a repeated query, or
executing a database procedure, an internal query identifier is
returned from the DBMS. This error indicates that the identifier
did not arrive to the application.

E _ LQ008A_RDNODESC
No internal row descriptor for query data description.
Explanation:

Various statements require a DBMS row descriptor to be sent to
the application run-time system for processing. For example, a
data retrieval or a COpy statement require a row descriptor. This
error is returned if a request was made to read a row descriptor
without allocating a result area for storage.
LQ Class Messages

21-9

E _LQ008B _ RDTUPSIZE
Failed to read query protocol data description.
Error in row (tuple) size.
Explanation:

Various statements require a DBMS row descriptor to be sent to
the application run-time system for processing. For example, a
data retrieval or a COpy statement require a row descriptor. This
error is returned if an attempt to read the internal "row size" field
failed.

E_LQ008C_RDCOLS
Failed to read query protocol data description.
Error in number of result data columns.
Explanation:

Various statements require a DBMS row descriptor to be sent to
the application run-time system for processing. For example, a
data retrieval or a COpy statement require a row descriptor. This
error is returned if an attempt to read the internal "attribute
number" field failed.

E _ LQ008D _RDALLOC
Failed to complete reading query data description.
Memory allocation for internal data structure failed.
Explanation:

Various statements require a DBMS row descriptor to be sent to
the application run-time system for processing. For example, a
data retrieval or a COpy statement require a row descriptor. This
error is returned if there was a memory resource shortage when
allocating internal sub fields of the row descriptor.

E_ LQ008E_ RDTYPE
Failed to read query protocol data description.
Error in type of result data column %Oc.
Explanation:

Various statements require a DBMS row descriptor to be sent to
the application run-time system for processing. For example, a
data retrieval or a COpy statement require a row descriptor. This
error is returned if an attempt to read the internal "data type"
field of the numbered column failed.

E_LQ008F_RDCOLEN
Failed to read query protocol data description.
Error in length of result data column %Oc.
Explanation:

21-10

LQ Class Messages

Various statements require a DBMS row descriptor to be sent to
the application run-time system for processing. For example, a
data retrieval or a COpy statement require a row descriptor. This
error is returned if an attempt to read the internal "name length"
field of the numbered column failed.

E_LQ0090_RDCONAME

Failed to read query protocol data description.
Error in name of result data column %Oc.
Explanation:

Various statements require a DBMS row descriptor to be sent to
the application run-time system for processing. For example, a
data retrieval or a COpy statement require a row descriptor. This
error is returned if an attempt to read the internal "column name"
field of the numbered column failed.

E_LQ0091_RDFLAGS

Failed to read query protocol data description.
Error in internal flags field.
Explanation:

Various statements require a DBMS row descriptor to be sent to
the application run-time system for processing. For example, a
data retrieval or a COpy statement require a row descriptor. This
error is returned if an attempt to read the internal "modifier"
field failed.

E_LQ0092_ RDTOOBIG

Failed to read query protocol data description.
Too many result columns (%Oc) in description.
Explanation:

Various statements require a DBMS row descriptor to be sent to
the application run-time system for processing. For example, a
data retrieval or a COpy statement require a row descriptor. This
error is returned if an attempt to read too many columns
descriptors was encountered.

E _ LQ0093_ RDTID

Failed to read query protocol data description.
Error in internal row descriptor identifier.
Explanation:

Various statements require a DBMS row descriptor to be sent to
the application run-time system for processing. For example, a
data retrieval or a COpy statement require a row descriptor. This
error is returned if an attempt to read the internal "row network
identifier" field failed.

E_LQOOAO_ATTNOINQ

Attribute '%Oc' cannot be inquired about.
Explanation:

The specified attribute cannot be inquired about in the
INQUIRE_SQL statement.

E_LQOOAl_ATTNOSET

Attribute '%Oc' cannot be set.
Explanation:

The specified attribute cannot be set in the SET_SQL statement.

LQ Class Messages

21-11

E _ LQOOA2_ ATTBADTYPE
Program data can not be used for attribute '%Oc'.
Data types are incompatible.
Explanation:

The data type of the specified attribute is not compatible with the
data type of the application data for the INQUIRE_SQL or
SET_SQL statements.

E_LQOOA3_ATTSETDATA
Attribute '%Oc' cannot be set with value '%lc'.
Explanation:

An illegal value has been supplied to the SET_SQL statement to
set the specified attribute.

E_LQOOBO_PROCNAME
Database procedure name is null or empty.
Explanation:

The database procedure name passed in for CREATE,
EXECUTE or DROP PROCEDURE is not a valid string. If the
procedure name was specified in a host string variable, then
confirm that the variable is assigned a valid procedure name. If
the name was specified as a literal then repreprocess the source
file which accesses the procedure.

E_LQOOBl_PARAMNAME
Database procedure parameter name is invalid.
The name is either null, empty or has an invalid Dynamic SQL length.
Explanation:

The database procedure parameter name passed in with
EXECUTE PROCEDURE is not a valid string. If the parameter
name was specified in a host string variable, then confirm that
the variable is assigned a valid parameter name. If the name was
specified as a literal then repreprocess the source file which
executes the procedure. If the name was assigned to the Dynamic
SQL SQLNAME field verify that the length is correct.

E_LQOOBA_SESSDUP
Attempt to connect to existing database session %Oc.
Explanation:

The session identifier used with the CONNECT statement is the
same as the session identifier of an already connected database
session. Multiple database connections must be uniquely
identified by the user-specified session identifier. The current
CONNECT statement is ignored.

E _ LQOOBB _ SESSALLOC
Unable to allocate memory for database session %Oc.
Explanation:

21-12

LQ Class Messages

When connecting to the database, an internal descriptor is
allocated to maintain the session's state. The internal descriptor
could not be allocated due to the shortage of memory. If you

have many database connections in one program or many cursors
open at the same time, try to close some so that there will be
smaller memory demands.
E_LQOOBD_SESSNONCUR
Attempt to disconnect from non-current database session.
Explanation:

When using the an optional session identifier with the
DISCONNECT statement, the session specified must be the
current database session. This means that the specified session
must either be the one that was most recently switched to by the
SET_SQL statement or it must be the most recently connected
session with no intervening switching or disconnecting of
sessions. The current DISCONNECT statement is ignored.

E _ LQOOBE_ SESSNOTFOUND
Attempt to switch to a non-existent session.
Explanation:

The SESSION identifier used with the SET_SQL statement
refers to a database session that does not currently exist. The
session cannot be switched to.

S_LQ0200_DEBUGI
Last ULTRIX/SQL statement in file '%Oc', line %ld:
S_LQ0201_DEBUG2
Last ULTRIX/SQL statement in file '%Oc':
S_LQ0202_DEBUG3
Last ULTRIX/SQL statement:
S_LQ0210_QUIT
Exiting session because of communications failure.
S_ LQ0211_SINOTOPEN
%Oc: Cannot open standard program channels.
S_ LQ0212_CALL_CONTINUE
Press RETURN to continue:

LQ Class Messages

21-13

MF Class Messages

E _ MFOOOl_Unable_to _open _file

Unable to open file '%Oc' (rc=%ld)
S_ MF0002 _ FSTM_output _helptitIe

Interactive Terminal Monitor Output
S_ MF0003 _Run _ to_completion

Run the request to completion
E - MF0004 - Unable to close- file

Unable to close file' %Oc' (rc=% Id)
E _ MFOOOS _ Unable_open_file_read

Unable to open file '%Oc' for read (rc=%ld)
E _ MF0006_ Unexpect_ EOF_ on_file

Unexpected EOF on file '%Oc' (rc=%ld)
E _ MF0007 _Unable_open _file _apnd

Unable to open file '%Oc' for append (rc=%ld)
E _ MF0008 _ Unable_open_temp _edi t

Unable to open temporary edit file (rc=%dO)
S_ MF0009 _File_empty _table _ unch

File '%s' is empty; input table is unchanged
E _ MFOOOA _cant_open _f_ tbl_ unchg

Unable to open file '%Oc' for input (rc=%ld); input table is unchanged
E _MFOOOB _ cant_read_temp _file

Unable to read temporary file '%Oc'
E _ MFOOOC _cant_open _temp_browse

Unable to open temporary browse file (rc=% ld)
MF Class Messages

22-1

S- MFOOOD - Enter- filenam- to - read
Enter name of file to read:
E - MFOOOE- File- does- not- exist
File ' %Oc' does not exist
E _ MFOOOF _cant_open _file _input
Unable to open file '%Oc' for input (rc=%ld)
E - MFOOIO- Unable- to - read- file
Unable to read file '%Oc'
S- MFOOll - Enter- filename - write
Enter name of file to be written:
E _ MF0012 _cant_open _file_output
Unable to open file '%Oc' for output (rc=% Id)
E - MF0013 - Unable to write- file
Unable to write file '%Oc'(rc=%ld)
S_ MF0014_ FSTM _ Terminating_msg
FSTM Terminating - %s
S- MF0015- Enterfile
-name
Enter file name:
E _ MF0016 _Error _opening_file
Error opening file '%Oc'
S _MF0017 _ Writing_screen _to _fil
Writing screen to file '%s' ...
S_ MF0018_ Appending_screen _to _f
Appending screen to file '%s' ...
E _ MF0019 _ Unexpected_ EOF_ on _ fil
Unexpected EOF on file '%Oc' (code=%ld)
E _ MFOOIA _Error _ closing_file
Error closing file '%Oc'
E _ MFOOIB _ Error_printing_screen
Error attempting to print screen.

22-2

MF Class Messages

5 _MF0043_ExplContinue

S_ MFOOI C _no _query _req_ignored
There is no query - request ignored
S_ MFOOID _Run_the _request
Run the request
S_ MFOOIE_No_active_request
No active request; cannot 'Resume'
S_ MFOOIF_Resume_the_request
Resume the request
S- MF0031 - TERMINATE
TERMINATE
S- MF0032- CONTINUE
CONTINUE
S- MF0033- Curr Continue
Statement processing will CONTINUE on error.
Curr
S- MF0034-Terminate
Statement processing will TERMINATE on error.
S- MF0035- Select- Continue
Select CONTINUE and enter 'GO' if you wish to continue
S- MF0036- Select- Terminate
Select TERMINATE and enter 'GO' if you wish to terminate
S- MF0037- Choice- Terminate
Do not continue processing the remaining statements.
S- MF0038- Choice- Continue
Continue processing the remaining statements.
S_ MF0040_ ExplOnError
Specify action to take when an error is encountered.
S_ MF0042_ ExplTerminate
Invoke the TERMINATE option.
S_MF0043_ ExplContinue
Invoke the CONTINUE option.

MF Class Messages

22-3

S_ MFOOSl_ExplBlank
Erase the input screen.
S_ MFOOS2_ ExplEdit
Escape to editor.
S_ MFOOS3 _ ExplFile
Read/Write specified File.
S_ MFOOS4_ ExplQuit
End Session.
S_ MFOOSS _ ExplInsertLine
Insert blank line in input screen.
S_ MFOOS6 _ ExplDeleteLine
Delete line in input screen.
S_ MF0020 _ FSTM _File_help_banner
Interactive Tenninal Monitor File
S_ MF0021_ FSTM _input _ helpbanner
Interactive Tenninal Monitor Input
S_ MF0022_in _ a_trans _wanna _qui t
You are in a transaction. Do you wish to abort the transaction and quit?
S_ MF0024_ OnError_help_banner
Interactive Tenninal Monitor OnError
E _ MF0023 _ Couldn _ t _open _ debug_ f
Couldn't open debug file
E - MF0026- Bad- Get- Form
Can't initialize fonns
E _ MF2001_Syntax
database [DBMS flags]
E _ MF2002 _ TooMany Args
Too many arguments specified for ULTRIX/SQL. Last flag is '%Oc'
E _ MF2003 _ TooManyD Bs
Only one database may be specified. Last argument is '%Oc'

22·4

MF Class Messages

E _ MF2004 _DBrequired
Database name must be specified.
S_ MF2101_Pending_trans _aborted
A pending transaction was aborted.
S_ MF2102_ SQL_ stmt_committed
Your SQL statement(s) have been committed.

MF Class Messages

22-5

MO Class Messages

E- MOOOOI- Cant- init- ADF- ctrlblk
Tenninal Monitor: could not initialize ADF control block

E- M0002F- Cant- set- exc- handler
Tenninal Monitor: could not set exception handler

E- M00041- 1500100
In branch: %Oc

E- M00042- 1500200
In macro processor: %Oc

E- M00043 - 1500300
E- M00044- 1500400
E- M00045- 1500401
E- M00046- 1500402
E- M00047- 1500403
can't reopen editfile %Oc: %lc

E- M00048- 1500404
Error reading edit file: %Oc

E- M00049- 1500500
E- M0004A- 1500501
eval: q_ropen 1
MO Class Messages

23-1

E_M0004C_1500503

E- M0004C - 1500503
eval: q_ropen 2

E- M0004D - 1500600
exp_op: bad op %Od

E- M0004E- 1500601
popop: underflow

E- M0004F- 1500602
popnum: underflow

E- M00050- 1500700
go: ropen 1

E- M00051 - 1500701
go: ropen 2

E- M00052- 1500800
macro: bad primitive %Od

E- M00053- 1500900
monitor: bad code %Od

E- M00054- 1500901
monitor: bad $ code %Od

E- M00062- 1501301
ttymon: qbuf fail

E- M00063- 1501302
tm_intr: typ %Od

E- M00068- 1501400
print: q_ropen 1

E- M00069- 1501401
print: q_ropen 2

E- M0006D - 1501700
writeout: q_ropen

E- M0006E- 1501701
writeout: q_ropen 2

23-2

MO Class Messages

E_M00002_Cant_use_macros

E- M00002- Cantuse
-macros
Macro processing will not be performed when running the SQL terminal monitor, so
\\macro is being ignored.
Explanation:

The user has typed \macro. Since macro processing is not
supposed to exist in SQL, this command is ignored and the user
notified.

System Status:

No change.

Recommendation:

None.

MO Class Messages

23-3

OP Class Messages

E - OPOOOO- OK
successful completion

E - OPOOOI - USER - ERROR
user error has been reported by optimizer

E - OP0002- NOMEMORY
optimizer ran out of memory before generating execution plan

E - OP0003- ASYNCABORT
asynchronous abort was detected

E - OP0004RDF
-GETDESC
request for relation information failed - possibly because table was modified or deleted

E - OPOOOS - GRANGETABLE
global range table overflow - query too complex

E - OP0006- TIMEOUT
optimizer timeout warning - suboptimal solution found

E - OP0007 - INVALID - OPCODE
opf_call entry point received an invalid operation code

E - OP0008- NOEXECUTE
query optimized - trace flag indicates no execution should take place

E - OP0009- TUPLE- SIZE
query cannot be processed, - size of tuple intermediate node is too large for all cases

E - OP0080- ULM- CLOSESTREAM
consistency check - error deallocating a memory stream

E - OP0081 - NOSTATUS
consistency check - no status provided by error handling mechanism
OP Class Messages

24-1

E - OP0082- UNEXPECTED - EX
consistency check - unexpected exception occurred

E - OP0083 - UNEXPECTED - EXEX
consistency check - really bad, got an unexpected exception trying to recover from an
exception

E_OP0084_DEALLOCATION
consistency check - resource deallocation error

E_OP0085_QSO_LOCK
consistency check - query tree could not be retrieved from QSF

E - OP0086- ULM - STARTUP
consistency check - server startup error - cannot startup ULM

E - OP0087RDF
-INITIALIZE
consistency check - server startup error - cannot startup RDF

E _ OP0088_ ULM _SHUTDOWN
consistency check - server shutdown error - cannot shutdown ULM

E - OP0089 - ALTER
consistency check - invalid alter opcode

E - OP008A- SCF- SERVER- MEM
consistency check - error obtaining memory for OPF server control block

E - OP008B - SCF- SERVER- MEM
consistency check - error releasing memory for OPF server control block

E - OP008C - SEMAPHORE
consistency check - could not initialize optimizer server semaphore

E _ OP008D _ RDF _UNFIX
consistency check - could not unfix an RDF table

E - OP008ERDF
-INVALIDATE
consistency check - could not invalidate an RDF table

E - OP008FRDF
-MISMATCH
The RDF cache could not be synchronized with parser time stamp, SCF should reparse
query, this message should not be reported by SCF

E - OP0090- PAINE
consistency check - PAINE handling routine could not be initialized by OPF
24-2

OP Class Messages

E_OP0303_RTOVERFLOW

E - OP0091 - AIC
consistency check - AlC handling routine could not be initialized by OPF

E - OP0092- SEMWAIT
consistency check - semaphore wait error for OPF server control block

E- OP0093- ULM- ERROR
consistency check - memory manager error

E- OP0094RDF
-SHUTDOWN
consistency check - error shutting down RDF facility

E - OP0095 - PARSE- TREE
consistency check - invalid parse tree from PSF

E - OP0200- TUPLE OVERFLOW
the intermediate aggregate relation required too large a tuple size

E - OP0201 - ATTROVERFLOW
too many columns in aggregate temporary relation

E - OP0202VAR
-OVERFLOW
query too complicated too many tables referenced, subselects or aggregates specified

E - OP0280- SCOPE
consistency check - scoping rules for variables used in query were violated

E _ OP0281_SUBQ UERY
consistency check - unexpected subquery type in optimizer

E - OP0282- FAGG
consistency check - function aggregate structure inconsistent

E - OP0300- ATTRIBUTE- OVERFLOW
the joinop attributes array overflowed - query too complex

E_OP0301_EQCLS_OVERFLOW
equivalence class array overflowed - query too complex

E - OP0302- BOOLFACT- OVERFLOW
too many boolean factors defined in query - query too complex

E - OP0303- RTOVERFLOW
joinop range table does not have sufficient room for variables - query is too complex

OP Class Messages

24-3

E- OP0304- FUNCATTR- OVERFLOW
function attribute table overflowed - query too complex

E- OP030S - NOCONVERSION
cannot convert constant to key - warning, keyed access cannot be used

E_OP0380_JNCLAUS
Consistency check - left and right part of conditional are incompatible

E- OP0381 - FUNCATTR
consistency check - inconsistent typing error in function attributes

E- OP0382- FATTR- CREATE
consistency check - function attribute should have been created

E - OP0383 - TYPEMISMATCH
consistency check - unexpected type mismatch in equivalence class

E- OP0384- NOATTS
consistency check - no attribute in equivalence class

E_OP038S_EQCLS_MERGE
consistency check - more than one equivalence class in merge

E- OP0386- BFCREATE
consistency check - assumption about ordering of boolean factor list failed

E- OP0387 - VARNO
consistency check - varno from parser range table out of range

E- OP0388- VARBITMAP
consistency check - var bit map is invalid

E_OP0389_EQUIJOIN
consistency check - equi join, unexpected types for operands

E- OP038A- REPEAT
consistency check - repeat query parameter not available when expected

E - OP038B NO
-SUBSELECT
consistency check - cannot find subs elect for correlated variable

E- OP038C - UNION
consistency check - union subquery expected

24-4

OP Class Messages

E - OP038D - CORRELATED

consistency check - expecting correlated aggregate
E - OP0400 - MEMORY

ran out of enumeration memory, optimizer needs more memory
E OP0480 MISSING TEMP HISTO
--

consistency check - histogram from temporary relation expected
E - OP0481 - KEYINFO

Consistency check - cannot find OPB _BFKEYINFO pointer when expected
E - OP0482- HISTOGRAM

Consistency check - cannot find OPH_HISTOGRAM structure for equivalence class
E - OP0483 - HIST- BUFFER

Consistency check - overflow of temporary histogram buffer
E OP0484 HISTTYPE
-

Consistency check - unexpected histogram type
E - OP0485 - HISTAND

consistency check - attempt to AND two incompatible histograms
E OP0486 NOKEY
-

consistency check - no key found when one expected
E _ OP0487 _NOEQCLS

consistency check - no joining equivalence class found when expected
E_OP0488_JOINNOEQCLS

consistency check - no joining equivalence class found when expected
E - OP0489 - NOFUNCHIST

consistency check - no histogram found for function attribute when expected
E - OP048A- NOCARTPROD

consistency check - no joining equivalence class and there is not a cartesean product
E - OP048B - COST

consistency check - cpu or disk i/o cost is negative
E - OP048C - SORTCOST

consistency check - sort cost routine failed

OP Class Messages

24-5

E_OP048D_QUERYTYPE
consistency check - unknown subquery type

E - OP048E- COTYPE
consistency check - unknown CO node type

E - OP048F- NULL
consistency check - expecting IS NULL or IS NOT NULL operator id

E- OP0490- CSSTATISTICS
consistency check - CSstatistics called failed, so enumeration phase cannot be bounded

E_OP0491_NO_QEP
consistency check - no query plan was found

E - OP0492- ORIG- NODE
consistency check - orig node expected on end of CO list

E - OP0493- MULTIATTR- SORT
consistency check - invalid multi-attribute sort type

E - OP0494- ORDERING
consistency check - unexpected ordering present

E - OP0495CO
TYPE
consistency check - unexpected CO node type

E - OP0496- EXACT
consistency check - exact multi-attribute ordering expected

E - OP0497- INCOMPATIBLE
consistency check - incompatible orderings found in CO node

E_OP0498_NO_EQCLS_FOUND
consistency check - equivalence class not found when expected

E - OP049A- CSALTR- SESSION
consistency check - could not tum on/off cpu accounting via CSaltr_session

E - OP0680 - TARGETLIST
consistency check - target list has non PST_RESDOM nodes in it

E - OP0681 - UNKNOWN- NODE
consistency check - unknown query tree node type found

24-6

OP Class Messages

E OP0682 UNEXPECTED NODE

consistency check - unexpected query tree node - PST_ CURVAL
E_OP0683_DUMPQUERYTREE
consistency check - error dumping query tree
E_ OP0684_DUMPQUERYNODE
consistency check - error dumping query tree node
E - OP0685 - RESOLVE
consistency check - error resolving query tree node
E_OP0686_CQMODE
consistency check - Illegal query mode for compilation.
E_ OP0687 _NOQTREE
consistency check - No query tree when expected.
E - OP0688 - INEXACT

consistency check - expecting inexact ordering nesting in an exact ordering
E - OP0689BAD
-TREE

consistency check - bad query tree defined, applying deMorgan's laws
E - OP068ABAD
-TREE

consistency check - error converting query tree to text
E - OP068B - BAD - VAR - NODE
consistency check - error converting query tree to text; var node
E - OP068C - BAD - TARGET- LIST

A bad select (or subs elect) target list has been found
E_OP068D_QTREE
error copying query tree nodes
E OP0700 ADC CVINTO
-

cannot build key because conversion does not exist
E - OP0701ADF
-EXCEPTION

ADF exception - see error block for info, ADF exception warning
E - OP0702ADF
-EXCEPTION

ADF exception - user error number between 120 and 16F

OP Class Messages

24-7

E - OP0780ADF
-HISTOGRAM
consistency check - the ADF returned an unexpected error - adc_hg_dt~n

E - OP0781ADI
-FIDESC
consistency check - error calling adi_fidesc

E - OP0782ADI
CALCLEN
consistency check - error calling adi_calclen

E - OP0783ADI
-FICOERCE
consistency check - error calling adi_ficoerce

E - OP0784ADC
-KEYBLD
consistency check - error calling adc_keybld

E - OP0785ADC
HELEM
consistency check - error calling adc_helem

E - OP0786ADC
-DHMAX
consistency check - default upper bound for uniform histogram error from ADF

E - OP0787ADC
DHMIN
consistency check - default lower bound for uniform histogram error from ADF

E - OP0788ADC
-CVINTO
consistency check - conversion of histogram element unexpectedly failed

E - OP0789ADC
-HMIN
consistency check - error calling min histogram value function routine

E - OP078AADC
-HMAX
consistency check - error calling max histogram value function routine

E - OP078CADC
-COMPARE
consistency check - ADF compare routine failed

E - OP078DADI
-OPID
consistency check - ADF operator ID routine failed in startup

E - OP078EADE
-CXSPACE
consistency check - Error estimating the size of a ex.

E - OP078FADE
-BGNCOMP
consistency check - Error beginning a compilation.

24·8

OP Class Messages

E - OP0790ADE
-CONSTGEN
consistency check - Error generating a constant.

E- OP0791ADE
-INSTRGEN
consistency check - Error generating an instruction.

E- OP0792ADE
-INFORMSP
consistency check - Error informing ADF of a larger CX.

E- OP0793ADE
-ENDCOMP
consistency check - Error ending a compilation.

E - OP0794ADI
-OPNAME
consistency check - cannot get operator name from operator ID

E - OP0795ADF
-EXCEPTION
ADF exception - non-user error, ADF error return code returned in error block

E - OP0796NO
-COMPLEMENT
consistency check - no complement exists for function when one was expected

E- OP0797OP
-USE
consistency check - unexpected operator construction PREFIX, POSTFIX, or INFIX
mismatch

E - OP0798OP
-TYPE
consistency check - unexpected operator type

E - OP0800- NODEFAULT
The user has not specified all of the required columns for insertion.

E- OP0880NOT
-READY
This feature or section of code is not yet implemented.

E- OP0881 - DMUFUNC
Illegal DMU function type for compilation.

E_OP0882_QSF_CREATE
Error calling QSF to create a new object.

E _ OP0883_QSF_SETROOT
Error calling QSF to set the root of an object.

E _OP0884_RELEQC
Consistency error: Orig node returns an eqc that is not found in the originated relation.

OP Class Messages

24-9

E - OP0885- COTYPE
Consistency error: Illegal CO node type.
E _ OP0886_ QSF_ PALLOC
Error calling QSF to allocate a piece of memory.
E - OP0887- CONSTTYPE
Illegal datatype or length for a constant in a query tree.
E - OP0888- ATT- NOT- HERE
Attribute is not available at a CO node.
E _ OP0889 _ EQ_NOT_HERE
Eqc is not available at a CO node.
E - OP0890- MAX - BASE
Too many bases added to a QEN_ADF struct.
E - OP0891 - MAX- ROWS
Too large a row number used to add a base to a QEN_ADF struct.
E - OP0892- MAX- REPEATS
Too large a repeat query number used to add a base to a QEN_ADF struct.
E - OP0893NV
REPEAT
A repeat query number that is not valid is being added to a QEN_BASE.
E- OP0894- EXCESSATTS
Too many attributes are being returned from a subselect
E _ OP0895 _NO _ SEJQTREE
Consistency Check: There is no query tree for a subselect join.
E - OP0896- MODIFY- ATTR
Consistency Check: the default attribute number 1 to modify does not exist.
E _ OP0897 _BAD _ CONST _ RESDOM
Consistency Check: a query tree constant or resdom node uses an source/destination type.
ILL
E - OP0898-LVARNO
Consistency Check: An out of range local variable number was found in a query tree for a
DB procedure.
E - OP0899BAD
-TARGNO
A target number was found (in a query tree or otherwise) that is illegal.

24-10

OP Class Messages

E - OP0900- INTERRUPT
user interrupt detected.

E- OP0901 - UNKNOWN- EXCEPTION
unknown exception occurred in optimizer utility.

E- OP0902- ADFSTARTUP
%Oc: internal error occurred when starting up Abstract Data Type Facility.

E - OP0903 - ADFSESSION
%Oc: internal error occurred when starting up Abstract Data Type Facility session.

E - OP0904- OPENFILE
%Oc: cannot open input file '%lc', OS status:%2d.

E - OP090S - ARGUMENTS
%Oc: more than %ld arguments.

E- OP0906- STACK
%Oc: ran out of stack space.

E _ OP0907 _UNIQUE CELLS
%Oc: bad uniquecells value, -zu# range allowed % ld#, but got :%3d.

E - OP0908- HISTOCELLS
%Oc: bad histogram cell count, -zr# range allowed % ld#, but got :%3d.

E - OP0909 - INGRESFLAGS
%Oc: more than % ld ULTRIX/SQL flags, or unrecognizable flags.

E - OP090A- DATABASE
%Oc: unexpected parameter: '% 1c' .

E - OP090B - DBLENGTH
%Oc: database name length must be %ld :'%2c'.

E - OP090C - RELLENGTH
%Oc: relation name length must be %ld :'%2c'.

E - OP090D - ATTLENGTH
%Oc: attribute name length must be % ld :'%2c'.

E - OP090E - PARAMETER
%Oc: unrecognized parameter: '%lc'.

OP Class Messages

24-11

E- OP090F- TABLES
%Oc: more than %Id tables for database '%2c'.
E- OP0910- DUPTABID
%Oc: duplicate table IDs in database '%Ic', table '%2c'.
E- OP0911 - NOTABLE
%Oc: database '%Ic', table '%2c' cannot be found or is not owned by you.
E- OP0912- VIEW
%Oc: database '%Ic', table '%2c' is a view and will be ignored.
E- OP0913- ATTRIBUTES
%Oc: database '% Ic', table '%2c', more than %3d columns defined, more attributes
defined for table than is allowed.
E- OP0914- ATTRTUPLES
%Oc: database '%Ic', table '%2c', column %3c inconsistent system catalog, more than
one attribute tuple for attribute ID.
E- OP0915- NOATTR
optimizedb: database '%Oc', table '% I c', column '%2c' not found.
E- OP0916- TYPE
%Oc: bad datatype id =%Id in iiattribute.attfrmt, column name '%2c'.
E - OP0917 - HTYPE

%Oc: histogram type=%ld len=%2d in iiattribute. column name '%3c', error-%4c.
E- OP0918- NOCOLUMNS
optimizedb: no columns for database '%Oc', table '% I c' .
E- OP091B - TUPLECOUNT
optimizedb: bad retrieval, database '%Oc', table '%Ic', i:%2d.
E- OP091C - NOROWS
optimizedb: no rows for database '%Oc', table '% I c' .
E - OP091D - HISTOGRAM

optimizedb: histogram conversion failed, column' %Oc', code = % Id.
E - OP091F- DATATYPE

%Oc: error displaying type % Id, length %2d.
E- OP0920- DATATYPE
optimizedb: unsupported histogram datatype; type %Od, length % Id.
24-12

OP Class Messages

E- OP0921 - ERROR
consistency check - parameter count too large for optimizer utility.

E- OP0922BAD
-ERLOOKUP
cannot find optimizer utility error message.

E- OP0923- DMF- BIT
%Oc: statistics exist; this should be reflected in system catalogs, but is not.
E- OP0924NON
-BASE
%Oc: non-base relation has statistics '%Ic', data base '%2c'.
E- OP0925 - NOSTATS
statdump: database '%Oc', table '% Ic', column '%2c' - statistics not found.
E- OP0926- DUPLICATES
statdump: database '%Oc', table '%Ic', column '%2c' - %3d duplicate statistics found.
E- OP0927 - DUPLICATES
statdump: database '%Oc', table '% Ic', column '%2c' - %3d duplicate histograms found.

E- OP092A- STATSDELETED
statdump: statistics for database '%Oc', table '% I c' , column '%2c' deleted.

E- OP092B - COMPARE
optimizedb: data comparison failed, column '%Oc', code = % Id.

E- OP092C - NULL
optimizedb: Statistics for table '%Oc', column '% Ic' not created - NULL values found.

E- OP0930NOT
-BASE
%Oc: database '%Ic', table '%2c' is not a base table and will be ignored.
E- OP0931 NO
-FILE
-i/-o flag must be followed by a file name.

E- OP0932BAD
-PREC
Precision for floating point numbers should be in the [0,30] range.

E- OP0933BAD
-USER
-u flag must be followed by a user name.

E- OP0934- BAD - SCAT- TYPE
Table_type in iitables for 'iistats', 'iihistograms', 'iitables' or 'iiphysical_tables' has an
unexpected value of '%Oc'.

OP Class Messages

24-13

E_OP0935_LVSN_CERR
Error %Od occurred when converting SQL_LEVEL value of '%Ic'.

E- OP0936ADI
-TYID
An ADF error %Od occurred when converting data type' % Ic' .

E - OP0937 - OPEN- ERROR
%Oc: Error %2d when opening file '%Ic'.

E_ OP0938_CLOSE_ERROR
%Oc: Error %2d when closing file ' % I c' .

E- OP0939 - TOO- MANY - COLS
Internal query generated to retrieve MINMAX statistics data for ' % 1c' table in ' %Oc'
database' has too many columns in the target list. Rerun optimizedb for the table and
specify columns using -a flag.

E - OP093AADC
-LENCHK
An ADF error %Od occurred when computing result length for column ' % I c' .

E- OP093B - TOO - MANY- ROWS
More rows returned than expected.

E- OP093CINP
-FAIL
%Oc: Failed to read in statistics from '%lc' file.

E - OP093D - MINMAXNOT
ALLOWED
Requests to create minmax statistics and to read statistics from a file are incompatible.

E- OP093ENO
-STATS
%Oc: Database '%Ic', table '%2c' owned by '%3c' - no statistics found.

E- OP0940- READ - ERR
Error %Od occurred when reading in statistical information from a file.

E - OP0941 - TEXT- NOTFOUND
Text line described by '%Oc' not found in the input file when expected.

E - OP0942- ADI- PM- ENCODE
An ADF error %Od occurred when executing adi_pm_encodeO.

E - OP0943ADI
-FICOERCE
An ADF error %Od occurred when executing adi_ficoerceO.

E- OP0944ADF
-FUNC
An ADF error %Od occurred when executing adf_funcO.
24-14

OP Class Messages

E - OP0945 - HISTVALNOT
-INC
Histogram values for table '%Oc', column '%lc' are not in ascending order.
Problem occurs around cell number %2d.
E - OP0946- CELL- NO
Wrong cell number found; should start at 0 and should increase.
E - OP0947 - WRONG - COUNT
Cell count must be in the [0.0,1.0] range.
E - OP0948- CELL- TOO- FEW
There must be at least %Od cells in a histogram.
E- OP0949 - CELL- TOO- MANY
Maximum number of cells exceeded.
E- OP094A- TRUNC
Truncation occurred when assigning a character string to host language variable.
E - OP094B - COL- NO - MISMATCH
Mismatching number of result columns and result host language variables in a FETCH or
SELECT statement.
E - OP094C - ERR- CRE- SAMPLE
Could not create table for sample data;
E- OP094D- CANT- SAMPLE
Sampling feature can be used only on ULTRIX/SQL tables.
INV
E- OP094E-SAMPLE
'-zs' flag must be followed by a number in the (0.0,100.0) range expressing percentage of
table rows to be sampled.
NOT
E- OP094F- SAMPLE-ALLOWED
Requests to create statistics based on sample data and to read statistics from a file are
incompatible.
E - OP0950- NOSAMPLING
Sampling of '%Oc' is not possible; no statistics will be created.
E_ OP0951_BAD _NO _UNIQUE
Wrong input value '%Of' for statistics on table '%lc', column '%2c'; number of unique
values can never be less than 1.

OP Class Messages

24-15

E _ OP0952_BAD_NO _ROWS
Wrong input value '%Od' for statistics on table '%1c', column '%2c'; number of rows can
never be less than 1.
E_ OP0953_BAD _NO _PAGES
Wrong input value '%Od' for statistics on table '%Ic', column '%2c'; number of pages
can never be less than 1.
E _ OP0954_BAD _NO _ OVFLOW
Wrong input value '%Od' for statistics on table '% 1c', column' %2c'; number of overflow
pages can never be less than O.
E - OP0955 - BAD- NULL - COUNT
Wrong input value '%Of' for statistics on table '% Ic', column '%2c'; number of null
values can never be less than O.
E - OP0956- TOTAL- COUNT- OFF
The sum total of normalized cell counts for table '%1c', column '%2c' is '%Of'; expected
value is 1.0 +/- %3f.
E_OP0957 _INV _ROW _CNT
Sampled/detailed statistics cannot be created on '%Oc' table without a valid row count.
E - OP0958- COUNTING - ROWS
Row count for table '%Oc' not available from catalogs, attempting to count rows.
CAP
ERR
E - OP0959IIdbcapabilities catalog is inconsistent, DBMS_TYPE indicates STAR, but
DISTRIBUTED value is missing or its value is not equal to 'Y'.
E_OP095A_TUPLE_OVFLOW
Error when creating minmax statistics on ' %Oc' table: resulting row is too wide. Try
creating statistics using -a flag, one column at a time.
E _ OPOAOO_ MAX SITE
distributed user error - max number of sites in query exceeded
E - OPOAOI - USELESS - PLAN
distributed plan expected to be useful but it was not
E - OPOA80- UNSUPPORTED
distributed user error - this type of distributed query not supported
E - OPOA81 - SITE
site has not been selected for query plan

24-16

OP Class Messages

E - OPOAS2- RESULT- VAR
unexpected result variable number for update statement
E - OPOAS3- CONSTRAINT
consistency check - unexpected state for correlated subselect constraint
E_OPOAS4_TEMP_REQ
consistency check - temp table required but not a data transfer
E - OPOAS5- UPDATE- VAR
consistency check - expecting update variable to be defined
E_ OPOAS6_ EQCLASS
consistency check - cannot add attribute to equivalence class for update
E - OPOAS7- UPDT- MATCH
consistency check - new range variable for target relation expected to be the last item in
base relation list
E - OPOASS- REPEAT
consistency check - repeat query parameter is out of order
E - OPOAS9- SAGG
consistency check - simple aggregate constant count is inconsistent
E - OPOASA- OPCSAGG
consistency check - unexpected tree structure found for simple aggregate
E - OPOASB - OPCPARM
consistency check - parameter nodes out of order for simple aggregate
E - OPOASC- COST
consistency check - cost resolution for final query plan cannot be found
E- OPOASD- VARIABLE
consistency check - OPF variable list is not ordered
SUB
E - OPOASE-TYPE
consistency check - unexpected subquery type
E - OPOASF- UPDATE- MODE
consistency check - unknown update mode
E - OPOA90NO
-ATTRIBUTES
consistency check - no attributes in the for update list of the cursor

OP Class Messages

24-17

E- OPOA91 - CORELATED
consistency check - query tree corelation inconsistent
E - OPOA92BAD
-LANGUAGE
consistency check - bad language ID found for query tree to text convertion
E_OPOA93_BAD_QUERYMODE
consistency check - unexpected query mode
E_ OPOA94_OPCFPROJ
consistency check - projection/function aggregate error
E - OPOA95- OPCBYTARGET
consistency check - function aggregate has no by/target list
E _ OPOA96_ OPCSUBQTYPE
consistency check - unrecognized subquery type
E - OPOB80- UNKNOWN- STATEMENT
internal DB procedure error- unknown statement type

24-18

OP Class Messages

PS Class Messages

E - PSOOOO - OK
PSF sucessful return status
E - PSOOOI - USER- ERROR
User error in query
E - PS0002 - INTERNAL- ERROR
Internal error in PSF
E - PS0003 - INTERRUPTED
Query aborted due to user request.
E - PS0004- EXCEPTION
Exception occurred in PSF
E - PSOOOS - USER- MUST- ABORT
An event has occurred which requires the user to abort the current transaction.
E - PS0006 - UNKNOWN - OPERATION
The requested operation is unknown to PSF.
E - PS0007 - INT - OTHERFAC
ERR
PSF detected an internal error when calling other facility.
E - PS0008- RETRY
Operation should be retried.
E - PSOIOI - BADERRTYPE
psf_error: bad error type
E - PSOI02 - TOO - MANY - ERRS
PSF has lost track of some of the errors that have occurred in this request.
NOT
FOUND
E - PSOI03 - ERRORError message corresponding to error, %Od, not found.
PS Class Messages

25-1

E_PS0201_BAD_QLANG
psq_bgn_session: bad query language id
E _ PS0202_QLANG_NOT_ALLOWED
query language not allowed
E - PS0203NO
-DECIMAL
psq_bgn_session: decimal marker not specified
E - PS0204BAD
DISTRIB
psq_bgn_session: bad distributed/non-distributed id
E- PS0205- SRV- NOT- INIT
psq_bgn_session: parser facility has not been started up
E - PS0206- SES- NOT- FOUND
no such session in the parser facility
E - PS0207 - YACC - ALLOC
Could not allocate the YACC control block.
E- PS0208- TOO- MANY- SESS
Maximum number of sessions exceeded for parser facility
E- PS0309 - ALLOC - SYMTAB
Could not allocate the symbol table.
E - PS030A- MULT- STMT- ALT
Attempt to parse second statement in alternate query
E PS030B RETRY AND ALT

Attempt to retry an alternate query
E- PS030C - NO- PRE V- STMT
Attempt to parse the second statement of a query without doing the first
E_PS030D_NO_MORE_QRYS
No more queries in this go block
E - PS030F- BACKUP
Error while trying to back up a token
E- PS0311 - YACC- UNKNOWN
Unknown error from yacc

25-2

PS Class Messages

E - PS0351 - UNKNOWN - LOCKPARM
line %Od, Unknown internal parameter '%Id' for the SET LOCKMODE command.
This is an internal error. Please report it to your vendor.
BAD
E- PS035E-DECIMAL
An illegal decimal specifier was requested.
E - PS0365 - BAD- FUNC- INST
pstnorml.c: Bad function instance %Od.
E - PS0366NO
COMPLEMENT
pstnorml.c: Comparison operator '% Ic' with no complement.
E - PS0370- OPEN- TEXT- CHAIN
Could not open a memory stream for text chain.
E - PS0371 - ALLOC - TEXT - CHAIN
Could not allocate a new block from the text chain.
E - PS0372- CLOSE - TEXT - CHAIN
Could not close the text chain.
E _ PS0373 _ OPEN _ QSF_TEXT
Could not open a QSF stream for storing query text information.
E_PS0374_ALLOC_QSF_TXT
Could not allocate a block in QSF for query text information.
E _ PS0375 _ UNLOCK_ QSF_TEXT
Could not unlock the QSF object containing query text information.
E - PS0376 - INSUF- MEM
Newly allocated scanner symbol block too small to accomodate data.
E - PS0377 - ADI- PM- ERR
Unexpected error executing adi_pm_encode call.
E- PS0378- SCF- TERM- ERR
Unexpected error calling SCF to obtain terminal info.
E_PS0379 _QSF _T_OR_D _ERR
Error calling QSF to translate/define.
E _ PS037 A_QSF_TRANS_ERR
Error calling QSF to translate.

PS Class Messages

25-3

E - PS0401 - CUR- NOT- FOUND
no such cursor in the parser facility
E - PSOSOI - SESSION - OPEN
There were open sessions when trying to shut down the parser facility.
E - PSOS02 - LEFTOVER - MEM
psq_shutdown: After shutting down all sessions, there was still allocated memory in the
parser facility.
E _ PSOS19 _ QSF_INFO
Error getting QSF information on object.
E - PS0601 - CURSOR- OPEN
There were open cursors when ending a session.
E - PS0602- CORRUPT- MEM
PSF memory was discovered corrupted when ending a session.
E - PS0701 - SRV- ALREADY - UP
The parser facility was already initialized for the server when SCF asked to initialize it
again.
NO
E - PS0702-MEM
Error allocating the PSF memory pool.
E - PS0703RDF
-ERROR
Error occurred while calling RDF.
E - PS0901 - REDESC - RNG
An attempt was made to re-describe a range variable.
E - PS0902BAD
-DESCTYPE
An illegal description request was specified in a range table operation.
NOTFOUND
E - PS0903TAB
Requested table '%Oc' was not found in the database.
E - PS0904 - BAD - RDF- GETDESC
RDF error ocurred when getting description for an object.
E - PS090SDBP
-NOTFOUND
Requested procedure '%Oc' was not found in the database.
E _ PS0906 _TOO _MANY _ COLS
Result table has too many columns.
25-4

PS Class Messages

E - PS0907 - CANT- FREE- DESC
pstclrmg.c: Can't free a table description.
E - PS0908 - RANGEVAR
-MISSING
line %Od, Can't find range variable number %ld.
E - PS0909 - NO- RANGE- ENTRY
CREATE VIEW: Could not find range table entry for attribute associated with resdom
'%Oc'.
E - PS090A- NO - ATTR - ENTRY
CREATE VIEW: Could not find attribute description for attribute associated with resdom
'%Oc'.
E - PS090B - TABLE- EXISTS
Table '%Oc' already exists in the database.
E - PS090C - NONEXISTENT - TABLE
Table '%Oc' does not exist in the database.
E - PS090D - NO- LDB - TABLE
LDB table '%Oc' does not exist on node '%lc', database '%2c', dbms '%3c'.
E - PS090ECOL
-MISMATCH
Number of columns in LDB table is different from that specified for the LINK object.
E - PS090F- BAD- COL- NAME
LDB table column name '%Oc' is not a valid ULTRIX/SQL name and can not be used as a
LINK object column name.
E - PS0910 - DUP- LDB - TABLE
LDB table '%Oc' owned by you already exists on NODE '%lc', DATABASE '%2c'.
E - PS0911 - BAD- LDB - USER
You are not an authorized user on NODE '%Oc', DATABASE '%lc'.
E - PS0912- MISSINGLDB
TBL
There is no LDB table corresponding to STAR object '%Oc'.
E - PS0913- SCHEMA- MISMATCH
Structure of LDB table corresponding to STAR object '%Oc' has been changed since the
time '%Oc' was created.
LDB
W - PS0914- MISSING-TBL
DROP/DESTROY: LDB table has not been dropped.
There is no LDB table corresponding to STAR object '%Oc'.
PS Class Messages

25-5

E - PS0916- USER - NOT - OWNER
DROP/DESTROY: You do not own LDB object corresponding to STAR object '%Oc'.
You may use REMOVE to remove the registration.
E _ PS0917 _CANNOT_CONNECT
Cannot connect to node '%Oc', database '% 1c', dbms '%2c'.
E - PS0918- MULTI- SITE- DROP
Table '%Oc' was not dropped.
Dropping it would violate single-site update requirement.
E - PS0919 - BAD - CATALOG- ENTRY
Catalog entry for DDB object' %Oc' is inconsistent. Try 'REGISTER %Oc AS LINK
WITH REFRESH' or REMOVE and then REGISTER %Oc.
E - PS091A- CANNOT- CONNECT
DROP/DESTROY: Cannot establish connection with the site of LDB table corresponding
to STAR object '%Oc'.
You may use REMOVE to remove the registration.
E - PS091BNO
-CONNECTION
LDB is temporarily inaccessible or it does not exist.
E - PSOAOI - BADBLKSIZE
psf_mopen: bad block size
E - PSOA02 - BADALLOC
psf memory function couldn't allocate memory
E - PSOA03 - BADMEMTYPE
psf_mopen: unknown memory type
E_PSOA04_REQ_GT_BLOCK
psf_malloc: request for memory greater than block size for stream
E _ PSOAOS _ BADMEMREQ
PSF: bad memory request
E - PSOA06- CANTFREE
psf_mclose: can't free memory
E - PSOA07 - CANTCHANGE
Can't change object type in QSF memory.
E - PSOA08- CANTLOCK
Can't lock QSF object.
25-6

PS Class Messages

E PSOA09 CANTDESTROY

Can't destroy QSF object.
E - PSOAOA - CANTGETINFO
Can't get info about a QSF object.
E PSOAOB CANTGETHNDLE

Can't obtain QSF object handle.
E - PSOB04- CANT- GET - TEXT
Failed attempt to get the query text from SCF.
E - PSOB05- CANT- UNLOCK
Can't unlock the QSF object.
E - PSOB06- NOWHILE
Internal PSF error: corresponding while node not found.
E PSOC02 NULL PTR

Unexpected NULL pointer in query tree.
E PSOC03 BAD NODE TYPE

Unknown node type in query tree.
E PSOC04 BAD TREE
-

Bad query tree.
E - PSOC05 - BAD - ADF- STATUS
Unexpected status from ADF.
BAD
TREE IN VFIND
E - PSODOIA bad query tree was detected in psy_ vfind.
E - PSOD02- BAD - TID - NODE
An illegal TID node was discovered.
E - PSOD03 - ATT- NOT- FOUND
The view attribute was not found in the view tree.
E - PSOD05 - NULL- TREE
A NULL tree was found in psy _apql.
E_PSOD06_QUAL_NOT_NORML
An un-normalized qualification was discoverd.

PS Class Messages

25-7

E - PSOD07- VARNO - OUTOF
-RANGE
An out of sequence variable number was found.
E - PSOD08- RNGVAR - UNUSED
An attempt was made to use an undefined range variable.
E - PSOD09 - MRG - DIFF- TABS
An attempt was made to merge two different tables.
E - PSODOA - CANT- GET- EMPTY
Failed call to get an empty datatype from ADF.
E - PSODOB - RESDOM - EXPECTED
A non-resdom node was found where a resdom node was expected.
NOT
E - PSODOC-RESDOM
A non-resdom node was found.
E - PSODOD - NULL - LHS
A NULL target list was found where one was not expected.
E_PSODOE_BAD_QMODE
An illegal query mode was discovered.
E - PSODOFBAD
-AGGREGATE
An illegal node was discovered in an aggregate tree fragment.
E_PSODIO_BAD_QUALIFICATION
An illegal node was discovered in the qualification.
E - PSODll - NULL- TREE
An unexpected NULL query tree was found.
E - PSOD12- BYHEADOR
-AOP
An unexpected AGHEAD or AOP node was found in query tree.
E - PSOD13 - SCU- INFO - ERR
Failed attempt to get information from seu.
E - PSOD14 - VIEW - CLEANUP
An error occurred while cleaning up a view definition.
RDF
E - PSOD15-GETINFO
RDF error ocurred when getting information on an object.

25-8

PS Class Messages

E - PSOD16RDF
-UPDATE
Error updating object in RDF.
E PSOD17 RDF UNFIX

Error unfixing object in RDF.
E_ PSOD18_ QSF_LOCK
Error getting QSF lock on object.
E_PSOD19 _QSF_INFO
Error getting QSF information.
E_PSODIA_QSF_DESTROY
Error destroying QSF object.
E - PSODIB - PERMIT - CLEANUP
An error occurred cleaning up permit definition.
E _ PSODIC _ QSF_UNLOCK
Error unlocking QSF object.
E - PSODID - BAD- FUNC - NAME
An illegal aggregate function name was specified.
E _ PSODIE _ QEF_ERROR
An error occurred calling QEF while defining integrity.
E - PSODIFOPF
-ERROR
An error occurred calling OPF while defining integrity.
E _ PSOD20_ QEF_ERROR
An error occurred calling QEF while destroying view or table.
E _ PSOD21_QEF_ERROR
Access conflict occurred while dropping table - your previous activity resulted in
acquiring a lock that is still being held.
E_PSOD22_QEF _ERROR
Internal transaction error occurred while executing QRYMOD.
E_PSOD23_QEF_ERROR
Resource related error occurred while executing QRYMOD. Try again later, if problem
persists consult your system administrator.
E- PSOD24- BGNTX
ERR
Error beginning transaction during QRYMOD operation.
PS Class Messages

25-9

E - PSOD25 - CMTTX
-ERR
Error committing transaction during QRYMOD operation.
TX
E - PSOD26- ABT-ERR
Error aborting transaction during QRYMOD operation.
RDF
E - PSOD27-INITIALIZE
Error occurred while initializing RDF facility.
E - PSOD28RDF
-TERMINATE
Error occurred while terminating RDF facility.
RDF
E - PSOD29-INVALIDATE
Error occurred while invalidating a descriptor in the RDF cache.
E - PSOD30 - UNEXPECTED - NODE
Unexpected node found by protection checking routine.
NO
E - PSOD31 -TUPLES
No tree tuples retrieved for a QUERYMOD object due to concurrent activity. Try again
later.
E - PSOD32 - RDF - INV - NODE
The tree returned from RDF has a node with an invalid pst_len value.
E - PSOEOI - STMT- NFND
Dynamic SQL statement was not found.
E - PSOE02- NOEXEC
The select statement is not allowed to executed.
E - PSOE03- RGENT- ERR
Error %Od occurred when reentering table info into the range table.
E - PSOFOI - CACHE- FULL
The descriptor cache is currently full. Try again later.
E - PSOF02 - MEMORY - FULL
There is no more available memory. Try again later.
E - PSOF03 - TRANSACTION- ABORTED
Transaction had to be aborted. Try again later.
E - PSOF04 - RDF- RESOURCE- ERR
Resource error occurred while retrieving a table description.
Try again or consult your system administrator.
25-10

PS Class Messages

E - PSOF05 - BAD - MEM- SIZE
Possibly bad memory size: %Od.
E - PSIOOI - ERR - seu- INFO
Error ocurred on an SeD INFORMATION call.

PS Class Messages

25-11

QE Class Messages

E_QEOOOO_OK
QEF successful return.
E_QEOOOl_INVALID _ALTER
Invalid parameter in alter QEF setting array.
E_QE0002_INTERNAL_ERROR
A QEF internal error occurred.
E _ QE0003_INVALID _SPECIFICATION
An out-of-range parameter value was specified.
E _ QE0004_NO_TRANSACTION
No transaction is currently in progress.
E_QE0005_CANNOT_ESCALATE
Cannot convert the internal transaction to an SST or MST.
E_QE0006_TRANSACTION_EXISTS
A transaction is currently in progress.
E _ QE0007_ NO _ CURSOR
Single table cursor is not open.
E _ QE0008_ CURSOR_NOT_OPENED
The cursor specified has not been opened.
E _ QE0009 _NO _PERMISSION
The specified cursor does not support the requested action.
E _ QEOOOA _READ_ONLY
The cursor was opened read-only.
E_QEOOOB_ADF_INTERNAL_ERROR
An internal error occurred while executing an ADF function.
QE Class Messages

26-1

E _ QEOOOC _CURSOR_ALREADY _OPENED
The cursor is already opened.
E _ QEOOOD _NO_MEMORY _LEFT
QEF is out of memory.
E_QEOOOE_ACTIVE_COUNT_EXCEEDED
There are too many active query plans in QEF.
E_QEOOOF_ OUT_OF_OTHER_RESOURCES
QEF is out of resources.
E _ QEOOIO_DUPLICATE _ROW
This update duplicates a row in the table.
E_QEOOll_AMBIGUOUS_REPLACE
Attempted to update the same row twice.
E _ QE0012_DUPLICATE _KEY
This update duplicates a key in the table.
E_QE0013_INTEGRITY_FAILED
Update failed because an integrity constraint was violated.
E_QE0014_NO_QUERY_PLAN
The specified query plan is unknown to QEF.
E _ QE0015_ NO _MORE_ROWS
No more rows are available.
E_QE0016_INVALID_SAVEPOINT
Nonexistent savepoint.
E_QE0017_BAD_CB
An invalid control block was passed to QEF.
E_QE0018_BAD_PARAM_IN_CB
Illegal parameter in control block.
E_QE0019_NON_INTERNAL_FAILURE
An error occurred in a routine called by QEF.
E_QEOOIA_DATATYPE_OVERFLOW
Datatype overflow.

26-2

QE Class Messages

E_QEOOIB_COPY_IN_PROGRESS
A copy command is currently in progress.
E_QEOOIC_NO_COPY
An error in the copy command occurred.
E_QEOOID_FAIL
General failure in QEF (%Ox).
E_QEOOIE_NO_MEM
Unable to allocate memory from SeF.
E_QEOOIF_INVALID _REQUEST
An unsupported function was requested.
E _ QE0020_ OPEN_CURSOR
A cursor is currently open.
E_QE0021_NO_ROW
The cursor is not currently positioned on a row.
E_QE0022_QUERY_ABORTED
The query has been aborted.
E_QE0023_INVALID_QUERY
This query plan is no longer valid.
E _ QE0024_TRANSACTION_ABORTED
The transaction log file is full. The transaction will be aborted.
E _ QE0025_ USER_ERROR
A user error has occurred.
E_QE0026_DEFERRED_EXISTS
Only one deferred cursor can be open at a time.
E_QE0027_BAD _QUERY_ID
Query identifier is not valid.
E_QE0028_BAD_TABLE_NAME
Table name is not valid.
E_QE0029_BAD_OWNER_NAME
Owner name is not valid.

QE Class Messages

26-3

E _ QE002A_DEADLOCK
Deadlock detected.
E_QE002B_TABLE_EXISTS
The operation specified tried to create a table that already exists.
E_QE002C_BAD_ATTR_TYPE
Invalid attribute type specified.
E_QE002D _BAD _ATTR_NAME
A bad attribute name was specified.
E_QE002E_BAD_ATTR_SIZE
Invalid size for specified attribute type.
E _ QE002F_BAD _ATTR _PRECISION
Invalid precision for specified attribute type.
E_QE0030_BAD_LOCATION_NAME
The specified location name is invalid.
E_QE0031_NONEXISTENT_TABLE
The operation required the use of a table that does not exist.
E_QE0032_BAD_SAVEPOINT_NAME
An invalid savepoint name was specified.
E_QE0033_BAD_TID
An invalid TID was specified.
E _ QE0034_LOCK_QUOTA _EXCEEDED
The locking mechanism is out of locks.
E_QE0035_LOCK_RESOURCE_BUSY
The requested lock is not available.
E _ QE0036_LOCK_TIMER_EXPIRED
The requested lock could not be granted in during the time allotted.
E_QE0037_ERROR_DELETING_RECORD
An error occurred while deleting a record.
E_QE0038_DUPLICATE _RECORD
Duplicate records were found.

26-4

QE Class Messages

E _QE0039_DUPLICATE_KEY
Duplicate primary keys were found.

E _ QE003A _FOPEN _FROM
An error occurred opening the file in a COpy FROM command.

E _ QE003B _FOPEN_TO
An error occurred opening the file in a COpy INTO command.

E_QE003C_COLUMN_TOO_SMALL
A column is too small for data conversion in the COpy command.

E_QE003D_BAD_INPUT_STRING
The input string is not valid for the COPY command.

E_QE003E_UNEXPECTED_EOF
An unexpected end of file was encountered while reading the input file.

E _ QE003F_ UN TERMINATED _CO
An unterminated cO field was encountered.

E_QE0040_NO_FULL_PATH
The full path of the file must be specified.

E_QE0041_DUPLICATES_IGNORED
Duplicate tuples were encountered and ignored.

E_QE0042_CONTROL_TO_BLANK
Control characters were converted to blanks.

E_QE0043_TRUNC_CO
A cO format field was truncated.

E_QE0044_ILLEGAL_FTYPE
An illegal file type was specified.

E_QE004S_BINARY _F_TO
The use of the Text(O) format requires the use of binary files.

E_QE0046_ERROR_ON_ROW
An error occurred processing row.

E _ QE0047_INVALID_CHAR
Invalid character value found while processing row.

QE Class Messages

26-5

E_QE0048_TUP_TOO_WIDE
Tuple is too wide for query processing.
E_QE0049_ALL_KEY
All keys must be specified for this MODIFY operation.
E_QE004A_KEY_SEQ
An illegal key sequence was specified.
E_QE004B_NOT_ALL_ROWS
Could not SELECT all rows from the subselect.
E _ QE004C _NOT _ ZEROONE _ROWS
Subselect returned more that one row.
E_QE004D_DUPLICATE_KEY_UPDATE
The requested update was not perfonned because it would duplicate a key existing in the
table.
E _ QE004E_ ULH _INIT_FAILURE
An error occurred while initializing ULH for the DSH environment.
E _ QEOOSO_TEMP _ TABLE_EXISTS
An error occurred trying to create a temporary table.
E _ QEOOSl_ TABLE_ACCESS _CONFLICT
Table access conflict, table opened twice.
E_QEOOS2_RESOURCE_QUOTA_EXCEEDED
Out of disk space, disk quota, or open file quota.
E_QEOOSF_BAD_DB_ACCESS_MODE
Bad database access mode.
E_QE0060_BAD_DB_ID
Bad database identifier.
E _ QE0061_BAD _DB _NAME
Bad database name.
E_QE0062_BAD_INDEX
Corrupt index table found.
E_QE0063_BAD_TABLE_OWNER
Bad table owner.

26-6

QE Class Messages

E_QE0064_BAD _TRAN_ID
Bad transaction identifier.
E_QE0065_DB_ACCESS_CONFLICT
Database access conflict.
E_QE0066_DB_OPEN
Database is already open.
E_QE0067_DB_OPEN_QUOTA_EXCEEDED
Open database quota exceeded.
E_QE0068_DB_QUOTA_EXCEEDED
Server database quota exceeded.
E_QE0069 _DELETED _TID
Tuple at tid already deleted.
E _ QE006A_NONEXISTENT _DB
Nonexistent database.
E_QE006B_SESSION_QUOTA_EXCEEDED
Server quota on sessions exceeded.
E_QE006C_CANT_MOD_CORE_SYSCAT
User does not have enough privilege to modify the core system catalogs: iirelation,
iiattribute, iiindexes, ii_relidx, iidevices.
E_QE006D_CANT_INDEX_CORE_SYSCAT
User cannot place an index on the core system catalogs: iirelation, iiattribute, iiindexes,
ii_relidx, iidevices.
E_QE006E_TRAN_IN_PROGRESS
Transaction already in progress.
E_ QE006F_TRAN_NOT_IN_PROGRESS
Transaction in not in progress.
E _ QE0070_ TRAN_QUOTA_EXCEEDED
Session transaction quota exceeded.
E_QE0071_TRAN_TABLE_OPEN
Table still open at end of transaction.
E _ QE0072_LOCATIONS _TOO_MANY
Number of locations specified exceeds the maximum allowed for this operation.
QE Class Messages

26-7

E_QE0074_BAD_TABLE_CREATE

Could not create table.
E_QE007S_BAD_KEY_DIRECTION

Illegal key direction.
E_QE0076_BTREE_BAD_KEY

Invalid key length for btree table.
E_QE0077_LOCATION_EXISTS

Location already exists.
E_QE007S_ERROR_ADDING_DB

Error trying to add database to server.
E_QE0079_ERROR_DELETING_DB

Error deleting database from server.
E_QE007A_ERROR_OPENING_DB

Error opening database in server.
E_QE007B_ERROR_CLOSING_DB

Error closing database in server.
E_QE007C_ERROR_GETTING_RECORD

Error trying to get a record.
E_QE007D_ERROR_PUTTING_RECORD

Error trying to put a record.
E _QE007E_ERROR_REPLACING_RECORD

Error trying to replace a record.
E_QEOOSO_ERROR_POSITIONING

Error trying to position a table.
E_QE0081_ERROR_OPENING_TABLE

Error opening a table.
E_QEOOS2_ERROR_CLOSING_TABLE

Error closing a table.
E_QEOOS3_ERROR_MODIFYING_TABLE

Error modifying a table.

26-8

QE Class Messages

E_QEOOS4_ERROR_INDEXING_TABLE
Error creating an index for a table.
E_QEOOS5_ERROR_SORTING
Error sorting data.
E _ QEOOS6_ERROR _BEGINNING _ TRAN
Error beginning a transaction.
E_QEOOS7_ERROR_COMMITING_TRAN
Error committing a transaction.
E _ QEOOSS_ERROR_ABORTING _ TRAN
Error aborting a transaction.
E_QEOOS9_ERROR_SAVEPOINTING
An error occurred while trying to create a savepoint.
E_QEOOSA_BAD_TABLE_DESTROY
Error trying to destroy a table.
E _ QEOOSB _CANT_OPEN _ VIEW
Illegal attempt was made to open a view, base table(s) must be opened.
E _ QEOOSC _LOCK_MAN AG ER _ERROR
Error creating a server lock list.
E _ QEOOSD _BAD _ SYSCAT _MOD
Error trying to modify core system catalogs: iirelation,iiattribute, iiindexes, ii_relidx,
iidevices.
E_QEOOSE_ERROR_RELOCATING_TABLE
An error occurred trying to relocate a table.
E_QEOOSF_ERROR_DUMPING_DATA
An error occurred trying to truncate the data of a temporary file.
E _ QE0090_ERROR _LOADING_DATA
An error occurred while trying to load data into a file.
E_QE0091_ERROR_ALTERING_TABLE
An error occurred while alter the characteristics of a table.
E_QE0092_ERROR_SHOWING_TABLE
An error occurred while showing information about a table.

QE Class Messages

26-9

E_QE0093_ERROR_ALTERING_DB
An error occurred while altering the characteristics of a database.
E_QE0094_ISAM_BAD_KEY_LENGTH
Invalid key length for isam table.
E _ QE0095 _ COMP _BAD_KEY _LENG TH
Invalid key length for compressed table.
E_QE0096_MOD_IDX_UNIQUE
It is not allowed to modify a secondary index with non-unique keys to a unique structure.

E _ QE0097_NOT _ A_VIEW
Error trying to retrieve the query id for a relation which is not a view.
E_QE0098_SEM_FAILS
Error trying to acquire or to release QEF semaphore.
E _ QE0099 _ DB_INCONSISTENT
Database becomes inconsistent. The transaction will be aborted
E_QE009A_DUP_LOCATION_NAME
The same location has been specified twice.
E_QE009B_LOCATION_LIST_ERROR
The two location lists specified for table relocation have different number of entries.
E _ QEOIOO_ CREATE _DSH _OBJECT
Error trying to create DSH object in ULH table.
E _ QEOIOl_DESTROY _ DSH _OBJECT
Error trying to destroy DSH object in ULH table.
E_QEOI02_CATALOG_DSH_OBJECT
Error trying to catalog DSH object into a ULH class.
E_QEOI03_ACCESS_DSH_OBJECT
Error trying to access DSH object in ULH table.
E_QEOI04_RELEASE_DSH_OBJECT
Error trying to release DSH object in ULH table.
E_QEOIIO_NO_ROWS_QUALIFIED
No rows would satisfied the qualification specification.

26-10

QE Class Messages

E_QEOlll_ERROR_SENDING_MESSAGE
Error trying to send a database procedure message to the user's application.
E_QEOl13_PARAM_CONVERSION
Error converting user-supplied value for the database procedure parameter '%Oc'.
E_QEOl14_PARAM_MISSING
The values for one or more parameters of the database procedure are missing. Neither
default nor null values have been specified.
E_QEOllS_TABLES_MODIFIED
One or more tables referenced in the database procedure were modified. The execution of
the procedure is tenninated.
E_QEOl16_CANT_ALLOCATE_DBP_ID
Error allocating a database-wide unique id for the database procedure.
E _ QEOl18_COMPRESSION_CONFLICT
Table must be modified to take advantage of new tuple compression routines.
E _ QE0201_BAD _SORT_KEY
Illegal QP detected. A sort key is not one of sort tuple attributes.
E_QEOSOO_RQF_GENERIC_ERR
RQF reported an unspecified error.
E_QEOSOl_WRONG_COLUMN_COUNT
RQF detected a column-number mismatch.
E_QEOS02_NO_TUPLE_DESCRIPTION
RQF detected a missing tuple description.
E_QEOS03_TOO_MANY_COLUMNS
RQF detected an excessive column count.
E _ Q EOS04_BIND _B UFFER _ TOO _SMALL
RQF detected an excessively small bind buffer.
E_QEOSOS_CONVERSION_FAILED
RQF detected a data conversion failure.
E_QEOS06_CANNOT_GET_ASSOCIATION
Either the node or the database is not defined or cannot be reached.

QE Class Messages

26-11

E_QEOS07_BAD_REQUEST_CODE
RQF detected an invlaid operation.
E _ QEOS08_ SCU_ MALLOC _FAILED
RQF failed to allocate space from seu.
E_ QEOS09_ ULM_STARTUP _FAILED
RQF failed to start up ULM.
E_ QEOSI0_ ULM_OPEN_FAILED
RQF failed to open with ULM.
E _ Q EOSll_INVALID_READ
RQF detected an invalid read operation.
E_QEOS12_INVALID _WRITE
RQF detected an invalid write opeation.
E_QEOS13_ULM_CLOSE_FAILED
RQF failed to close with ULM.
E_ QEOS14_ QUERY _ERROR
An (LDB) query error or warning occurred.
E_QEOSlS_UNEXPECTED_MESSAGE
RQF detected an unexpected message.
E _ QEOS16_CONVERSION_ERROR
RQF detected a conversion error.
E_QEOS17_NO_ACK
RQF failed to obtain an acknowledgment.
E _ QEOS18_ SHUTDOWN_FAILED
RQF failed to shutdown.
E _ QEOS19 _COMMIT _FAILED
RQF failed to commit.
E_QEOS20_ABORT_FAILED
RQF failed to abort.
E_ QEOS21_BEGIN_FAILED
RQF failed to begin a transaction.

26-12

QE Class Messages

E _ Q E0522_END _FAILED
RQF failed to end a transaction.
E_QE0523_COPY_FROM_EXPECTED
RQF detected a missing COpy FROM operation.
E_QE0524_COPY_DEST_FAILED
RQF failed to copy to a destination LDB.
E_QEOS2S_COPY_SOURCE_FAILED
RQF failed to copy from a source LDB.
E _ QE0526_ QID_EXPECTED
RQF detected a missing query id.
E _ QE0527 _CURSOR_CLOSE_FAILED
RQF failed to close a local cursor.
E_QEOS28_CURSOR_FETCH_FAILED
RQF failed to fetch from a local cursor.
E _ QEOS29_CURSOR _EXEC _FAILED
RQF failed to open a local cursor.
E_QE0530_CURSOR~DELETE_FAILED

RQF failed to delete the current row of a local cursor.
E_QE0531_INVALID_CONTINUE
RQF detected an invalid CONTINUE operation.
E _ QE0532_ DIFFERENT_TUPLE _SIZE
The schema of a local table has been changed since it was created.
E_QEOS33_FETCH_FAILED
RQF failed to retrieve data.
E_QE0534_COPY_CREATE_FAILED
RQF failed to create a temporary LDB table.
E_QE053S_BAD_COL_DESC_FORMAT
RQF detected a column-description format mismatch.
E _ QEOS36_ COL _ DESC _EXPECTED
RQF detected a missing column description.

QE Class Messages

26-13

E _ Q EOS37_11_LD B_N OT_DEFINED
RQF detected an undefined LDB.
E _ QEOS38_ ULM _ ALLOC _FAILED
RQF failed to allocate space from ULM.
E _ Q EOS39 _INTERR UPTED
RQF was interrupted.
E_QEOS40_UNKNOWN_REPEAT_Q
RQF detected an unknown repeat query id.
E_QEOS41_ERROR_MSG_FROM_LDB
RQF detected an error message from an LDB.
E_QEOS42_LDB_ERROR_MSG
RQF detected an LDB error message.
E_QEOS43_CURSOR_UPDATE_FAILED
RQF detected a CURSOR UPDATE failure.
E_QEOS44_CURSOR_OPEN_FAILED
RQF detected a CURSOR OPEN failure.
E_QEOS4S_CONNECTION_LOST
RQF detected the loss of an LDB association.
E _ Q EOS46_ RECV _ TIMEO UT
RQF detected a timeout condition.
E _ QE0700_ TPF_GENERIC_ERR
TPF reported an unspecified error.
E_QE0701_INVALID_REQUEST
TPF detected an invalid operation.
E _ QE0702_ SCF_ MALLOC _FAILED
TPF failed to allocate space from SeF.
E_QE0703_SCF_MFREE_FAILED
TPF failed to free space with SCF.
E_QE0704_MULTI_SITE_WRITE
Updating more than 1 site is not allowed within a transaction.

26-14

QE Class Messages

E_QE070S_UNKNOWN_STATE
TPF detected an unknown transaction state.
E_QE0706_INVALID_EVENT
TPF detected an invalid transaction event.
E _ QE0707_INVALID _TRANSITION
TPF detected an invalid transaction transition.
E_QE0708_TXN_BEGIN_FAILED
TPF failed to begin a transaction.
E _ QE0709 _ TXN _FAILED
TPF detected a transaction failure.
E_QE0710_SAVEPOINT_FAILED
TPF failed to establish a savepoint.
E_QE0711_SP _ABORT_FAILED
TPF failed to abort to a savepoint.
E_ QE0712_SP_NOT_EXIST
TPF detected a non-existent savepoint.
E_QE0713_AUTO_ON_NO_SP
AUTOCOMMIT is not allowed since a savepoint exists.
E_QE0714_ ULM_STARTUP _FAILED
TPF detected a ULM startup failure.
E_QE071S_ULM_OPEN_FAILED
TPF detected a ULM open failure.
E_QE0716_ULM_ALLOC_FAILED
TPF detected a ULM allocation failure.
E_QE0717_ULM_CLOSE_FAILED
TPF detected a ULM close failure.
E _ QE0902_NO_LDB _TAB_ON _ CRE_LINK
Cannot register a non-existent LDB table.
E _ QE0960_CONNECT _ ON_CONNECT
Invalid nested DIRECT CONNECT.

QE Class Messages

26-15

E_QE0961_CON N ECT_ ON_XACTION

E_QE0961_CONNECT_ON_XACTION
DIRECT CONNECT is not allowed within a transaction.
E_QE0962_DDL_CC_ON_XACTION
DDL_CONCURRENCY cannot be changed within a transaction.
E_QE096E_INVALID_DISCONNECT
Invalid DIRECT DISCONNECT.
E_QE0970_BAD_USER_NAME
Invalid user name detected.
E_QE0980_LDB_REPORTED_ERROR
Error reported by LDB.
E_QEIOOl_NO_ACTIONS_IN_QP
QEF consistency check. There are no actions in the current QP.
E_QEI002_BAD_ACTION_COUNT
QEF consistency check. The count of actions does not agree with the list of action headers.
E _ QEI003 _ NO_VALID _LIST
QEF consistency check. The list of validation is missing from the current action.
E_QEI004_TABLE_NOT_OPEN
QEF consistency check. Error validating an action. Trying to position a table that has not
been opened.
E_QEIOOS_ WRONG_JOIN_NODE
QEF consistency check. Error in QP, qen_sort is being used by a node other than
qen_sijoin.
E_QEI006_BAD_SORT_DESCRIPTOR
QEF consistency check. The QEN_SHD structure is not clean. Some memory could be
lost.
E_ QEI007_BAD _SORT_COUNT
QEF consistency check. No tuples in the sort buffer or the list of DM_MDATA does not
agree wi th the count of tuples.
E_QEI009_DSH_NOTMATCH_QP
QEF consistency check. The number of sort nodes in the QP is not the same as the actual
count.
E_QEIOIO_HOLDING_SORT_BUFFER
QEF consistency check. The session termiantes while holding sort buffers.
26-16

QE Class Messages

E_QE1996_BAD_ACTION
QEF consistency check. Invalid action detected.
E _ QE1997 _NO_ACTION
QEF consistency check. No or invalid action detected.
E_QE1998_BAD_QMODE
QEF consistency check. Invalid query mode detected.
E_QE1999_BAD_QP
QEF consistency check. Invalid query plan detected.
E_QE7600_LDB_GENERIC_ERR
QEF detected a general failure reported by an LDB.
E_QE7601_LDB_BAD_SQL_QRY
QEF detected an SQL query that cannot be processed by an LDB.
E_QE7602_LDB_XACT_ENDED
QEF aborted the distributed transaction because of an LDB's unilateral abort action.

QE Class Messages

26-17

QG Class Messages

E _QGOOOl_No _Internal

Internal program error: Missing data structures.
The QG module is missing an internal data structure. Please submit a Software
Performance Report (SPR).
Explanation:

The query generator module was called to break out of a query
for which no internal data structure had been set-up. This is an
internal programming problem.

System Status:

No action.

Recommendation:

Please submit a Software Performance Report (SPR).

E _QG0002_ NoStart

Internal program error: No QG_START operation.
The QG module was called to fetch a row without a query having been started. This is an
internal problem resulting from incorrect query generator usage. Please submit a Software
Performance Report (SPR).
Explanation:

The query generator module was called to fetch a row without a
query having been started. The query generator module should
be called to start a query before calling it to fetch a row. This is
an internal programming problem.

System Status:

No rows will be fetched.

Recommendation:

Please submit a Software Performance Report (SPR).

E _ QG0003_ N oM emory
Internal program error: Memory allocation failure.
The QG module could not allocate anymore memory. Please submit a Software
Performance Report (SPR).
Explanation:

The query generator module attempted to allocate some memory
needed to execute a query or fetch the data for a query, but could
not. This is an internal programming problem.

System Status:

The query will not be executed or no data will be fetched for the
query.

Recolumendation:

Please submit a Software Performance Report (SPR).

QG Class Messages

27-1

E _ QG0004_NoSpec
Internal program warning:
Function did not generate any query specifications. Please submit a Software Performance
Report (SPR).
Explanation:

A function that the query generator module called to build a
dynamic query specification did not generate a query
specification. This is usually not an error, but if you see the error
message this is because of an internal programming error.

System Status:

An always true predicate will be generated, "I = 1".

Recommendation:

Please submit a Software Performance Report (SPR).

E _ QG0005 _ BadVersion
Internal program error: Incompatible versions.
The QG module was called to execute a query that was incompatible with the version of
the module. This is an internal problem resulting from incorrect query generator usage.
Please submit a Software Performance Report (SPR).
Explanation:

The query generator module detected a version incompatibility
in its usage. In particular, a version 0 query with '%a' format
(meaning DBDV data type) in its parameter list was passed to
the QG module. Queries with DBDV elements should be version
1, only. This is an internal programming problem.

System Status:

The query will not be executed.

Recommendation:

Please submit a Software Performance Report (SPR).

E_ QG0006_BadSpec
Internal program error: Bad query specification.
The QG module found a bad query specification for the query being executed. Please
submit a Software Performance Report (SPR).
Explanation:

The query generator module detected an invalid query
specification in a query it was attempting to execute. This is an
internal programming problem.

System Status:

The query will not be executed.

Recommendation:

Please submit a Software Performance Report (SPR).

E _ QGOOIO_ TempFile
Could not open temporary file.
The QG module could not open a temporary file needed to execute a query. Please check
that you have access rights and sufficient disk space available in the temporary directory
before submitting a Software Performance Report (SPR).
Explanation:

27-2

QG Class Messages

The query generator module could not open a temporary file
used to hold data fetched for the query being executed. This
could be for any number of reasons, but is most likely a disk
space or access problem.

E_QG0011_WriteFile

System Status:

No data will be fetched for the query.

Recommendation:

Make sure that the you have access rights to the temporary
directory and sufficient disk space before submitting a Software
Performance Report (SPR).

E _ QGOOll_WriteFile

Could not write to temporary file.
The QG module could not write to a temporary file needed to execute a query.
Please check your temporary directory access rights and disk space before submitting a
Software Performance Report (SPR).
Explanation:

The query generator module could not write to a temporary file
used to hold data fetched for the query being executed. This
could be for any number of reasons, but is most likely a disk
space problem.

System Status:

Query execution will be terminated with an error status.

Recommendation:

Make sure that the you have access rights to the temporary
directory and sufficient disk space before submitting a Software
Performance Report (SPR).

QG Class Messages

27-3

QR Class Messages

E _ QR0003 _PRINT _table_not _exist
PRINT: table does not exist or is not accessible by you.
E _ QR0004_PRINT_syntax _error
PRINT: syntax error.
E - QROOOS - Unable- to - open- sqhelp
Unable to open SQL help file, qrhlpsql.hlp
E _ QR0007 Jnvalid_help_syntax
Sorry, help %s is invalid help syntax.
E _ QR0008_Type_help_help _ stupid
Type "help help" for valid help syntax.
E _ QR0009 _adctmcvt_ internal_err
Internal Error from adc_tmcvt occurred, number %x
E _ QROOOA _Syntax_err _correct _is
Syntax error on %s, correct syntax is:
E _ QROOOB _PRINT _ tblname _ tblname
\tPRINT tablename[, tablename]
E _ QROOOC _end _stmt _with _semicln
\tTerminate all statements with a semicolon.
E _ QROOOD _Syntax_error _ on _ EOF
Syntax error on 'EOF', correct syntax is:
E _ QROOOE _HELP_tblname _tblname
\tHELP TABLE tablename[, tablename]
E _ QROOOF _ Error _allocing_mem
Sorry, an error occurred during memory allocation.
QR Class Messages

28-1

E _ QROOIO_Error _freeing_memory
Warning: an error occurred while freeing up memory.
E _ QROOll_Internal_help_error
Internal error in the help module, code %d
Explanation:

The help command has been called with a code (qrb-step) that
isn't known about (shouldn't have been set).

System Status:

The help command will not be processed further, but further
queries may be entered.

Recommendation:

The user might conceivably wish to report the error.

E _ QR0012 _no_help _permit
Help on table permissions is not available on this system.
Explanation:

The user has typed 'help permit' on a system for which such help
is unavailable--at time of writing, on gateways.

System Status:

Execution of the next query proceeds.

Recommendation:

None.

E_ QR0013 _no_helpJnteg
Help on table integrities is not available on this system.
Explanation:

The user has typed 'help integrity' on a system for which such
help is unavailable--at time of writing, on gateways.

System Status:

Execution of the next query proceeds.

Recommendation:

None.

E _QR0014 _HELP _thlname _thlname
\tHELP tablename [, tablename]
Explanation:

The user has mis-typed the help command.

System Status:

Display a syntax message to the user.

Recommendation:

Re-type the command.

E_ QR0015 _HELP _indexname
\tHELP INDEX indexname[, indexname]
Explanation:

The user has mis-typed the help command.

System Status:

Display a syntax message to the user.

Recommendation:

Re-type the command.

E _ Q R0006 _Index_does_not _exist
Index %s does not exist or is not owned by you

28-2

QR Class Messages

Explanation:

The user has requested help on a non-existent index. Note: It is
possible that the DBA owns an index by this name but that the
user has a table of the same name that takes precedence.

System Status:

Display error to the user.

Recommendation:

Regroup and press on.

E _ QR0016_HELP _procedure
\tHELP PROCEDURE procedure-name[, procedure-name]
Explanation:

The user has mis-typed the help command.

System Status:

Display a syntax message to the user.

Recommendation:

Re-type the command.

E _ QR0017 _HELP _link
\tHELP REGISTER tablename[, tablename]
Explanation:

The user has mis-typed the help command.

System Status:

Display a syntax message to the user.

Recommendation:

Re-type the command.

E - QR0018- no - help - dbproc
Help on database procedures is not available on this system.
Explanation:

The user has typed 'help procedure' on a system for which such
help is unavailable.

System Status:

Execution of the next query proceeds.

Recommendation:

None.

E _ QR0019 _Procedure_does not
Procedure %s does not exist or is not owned by you
Explanation:

The user has requested help on a non-existent procedure.

System Status:

Display error to the user.

Recommendation:

Regroup and press on.

E _ QROOIA_Link_ does_not exist
Registered object %s does not exist or is not owned by you
Explanation:

The user has requested help on a non-existent registration.

System Status:

Display error to the user.

Recommendation:

Regroup and press on.

E - QROOIB - no - help- link
Help on registered objects is not available on this system.

QR Class Messages

28-3

Explanation:

The user has typed 'help register' on a system for which such
help is unavailable.

System Status:

Execution of the next query proceeds.

Recommendation:

None.

E_QROOIC _err _ret_iiproc
Sorry, Error(s) occurred obtaining Help from iiprocedures
Explanation:

An error occurred doing the retrieve on the iiprocedures table.

System Status:

Apologize to the user.

Recommendation:

None.

E_QROOID _err _retJireg
Sorry, Error(s) occurred obtaining Help from iiregistrations
Explanation:

An error occurred doing the retrieve on the iiregistrations table.

System Status:

Apologize to the user.

Recommendation:

None.

E _ QROOIE _Table_not _a_link
Table %s is either not registered or its definition is unavailable
Explanation:

The object specified has no registration definition stored in
iiregistrations.

System Status:

Nothing special.

Recommendation:

None.

E _ QROOIF_err _ret _iiindex _col
Sorry, Error(s) occurred obtaining Help from iiindex_columns
Explanation:

An error occurred doing the retrieve on the iiindex_columns
table.

System Status:

Apologize to the user.

Recommendation:

None.

E_ QR0020_err _ret_ii_Ioghelp
Sorry, Error(s) occurred obtaining Help from iilog_help.
Explanation:

An error occurred doing the retrieve on the iilog_help table.

System Status:

Apologize to the user.

Recommendation:

None.

E_QR0021_not_a_table
%s is of type %s and is not a table

28-4

QR Class Messages

E _ QR0022_not _a_view
%s is of type %s and is not a view
E _ QR0023 _not_an _index
%s is of type %s and is not an index
Explanation:

User requested help TABLE on a view or index, or user
requested help VIEW on a table or index, or user requested help
INDEX on a table or view.

System Status:

Nothing special.

Recommendation:

None.

E _ QR0024_not _a _link
%s exists but is not a registered object
Explanation:

User requested help REGISTER on a non-registered object.

System Status:

Nothing special.

Recommendation:

None.

E_QR002S_err_ret_help_info
Sorry, Error(s) occurred obtaining Help from system catalogs.
Explanation:

An error occurred doing the retrieve on the system catalogs
through IIUlrel_help.

System Status:

Apologize to the user.

Recommendation:

None.

E _ QR0026_err_ret _ star _info
Sorry, Error(s) occurred obtaining Help from the STAR system catalogs.
Explanation:

An error occurred when retrieving information from the STAR
system catalogs iiddb_tableinfo, iiddb_catalogs, and
iiddb_ldbids for the help register command.

System Status:

Apologize to the user.

Recommendation:

None.

E _ QR0027 _no_help_rule
Help on database rules is not available on this system.
Explanation:

The user has typed 'help rule' on a system for which such help is
unavailable.

System Status:

Execution of the next query proceeds.

Recommendation:

None.

QR Class Messages

28-5

E _ QR0028_Rule_does _not_exist
Rule %s does not exist or is not owned by you
Explanation:

The user has requested help on a non-existent rule.

System Status:

Display error to the user.

Recommendation:

Regroup and press on.

E _ QR0029 _HELP _rule
HELP RULE rulename[, rulename]
Explanation:

The user has mis-typed the help command.

System Status:

Display a syntax message to the user.

Recommendation:

Re-type the command.

E_ QR002A_err_ret_iirul
Sorry, Error(s) occurred obtaining Help from iirules
Explanation:

An error occurred doing the retrieve on the iirules table.

System Status:

Apologize to the user.

Recommendation:

None.

28-6

QR Class Messages

as Class Messages

E_QSOOOO_OK
Normal QSF return status.
E _ QSOOOl_NOMEM
QSF dynamic memory pool is exhausted.
E _ QS0002_ SEMINIT
Could not initialize semaphore from SCF.
E _ QS0003_ OP_CODE
Unknown QSF op code.
E _ QS0004_ SEMRELEASE
Could not release semaphore from SCF.
E _ QSOOOS_ACTIVE_OBJECTS
Attempting to shut down QSF while there are still active objects.
E _ QS0006_ACTIVE_SESSIONS
Attempting to shut down QSF while there are still active sessions.
E _ QS0007 _ MEMPOOL_RELEASE
Could not release QSF's dynamic memory pool.
E_QS0008_SEMWAIT
Error while attempting to set a semaphore from SCF.
E _ QS0009 _BAD _ OBJTYPE
Unknown type of object. QSF only recognizes objects which are QUERY TEXTs,
QUERY TREEs, or QUERY PLANs.
E _ QSOOOA_ OBJ_ALREADY_EXISTS
An object with the requested name and type already exists in QSF memory.

as Class Messages 29-1

E _ QSOOOB _BAD _ OBJNAME
Illegal name for a QSF object.
E_QSOOOC_ULM_ERROR
Unexpected ULM error detected by QSE
E _ QSOOOD_CORRUPT
QSF's dynamic memory has been corrupted.
E_QSOOOE_SEMFREE
Could not free semaphore from SCE
E _ QSOOOF_BAD _HANDLE
The supplied object handle does not refer to a QSF object.
E_QSOOIO_NO_EXLOCK
QSF object is not exclusively locked by you.
E _ QSOOll_ULM _STREAM_NOT _CLOSED
Could not close a ULM memory stream.
E_QS0012_0BJ_NOT_LOCKED
QSF object is not locked by you.
E _ QS0013_BAD _ LOCKID
The lock ID supplied does not match the one assigned to the QSF object when it was
exclusively locked.
E_QS0014_EXLOCK
QSF Object is already locked exclusively.
E_QS0015_SHLOCK
QSF Object is already locked shared.
E_ QS0016_BAD _LOCKSTATE
Illegal lock state specified.
E_QS0017_BAD_REQUEST_BLOCK
QSF request control block is not set up properly.
E _ QS0018_ BAD_PIECE_SIZE
Request for an illegal piece size. Size must be a positive number of bytes.
E_QS0019_UNKNOWN_OBJ
No object with the supplied name and type exists in QSF's dynamic memory.

29-2

as Class Messages

E_QSOOIA_NOT_STARTED

QSF has not been started for the server.

E _QS0500_INFO _REQ
QSF info request #%Od: % 1c
E _ QS9001_ NOT_YET_AVAILABLE

This QSF function is not yet available.
E _QS9002_ UNEXPECTED _EXCEPTION

Unexpected exception detected by QSF.
E _QS9999_INTERNAL_ERROR

A QSF internal error has occurred.

as Class Messages 29-3

RD Class Messages

E - RDOOOO- OK
successful completion.
E - RDOOOI - NO- MORE- MEM
Not enough memory for RDF temporary work area.
E - RD0002- UNKNOWN - TBL
Requested table is not known to DMF.
E - RD0003BAD
PARAMETER
RDF function was called with bad parameters.
E- RD0006- MEM- CORRUPT
Memory allocation control structure was corrupted.
E - RD0007- MEM- NOT- OWNED
Not the owner of the memory block.
E - RD0008- MEM - SEMWAIT
Error in ULM waiting for a memory semaphore.
E - RD0009- MEM- SEMRELEASE
Error in ULM releasing a memory semaphore.
E RDOOOA MEM NOT FREE

Memory allocation control structure was corrupted, cannot reclaim memory.
E _ RDOOOB _ MEM _ERROR
General error from ULM.
E- RDOOOC - USER- INTR
User interrupts while requesting DMF function.
E - RDOOOD - USER - ABORT
User's abort detected.
RD Class Messages

30-1

E- RDOOOEDMF
-ERROR
General error from DMF.
E - RDOOOF- INFO- OUTOF
-DATE
The information block is out of date.
E_RDOOIO_QEF _ERROR
Internal error from QEF.
E - RDOOll - NO- MORE- ROWS
No more tuples in the current table.
E - RD0012- BAD - HISTO - DATA
Histogram tuples are out of sequence.
E - RD0013 - NO - TUPLE - FOUND
No tuples found in the current table.
E_RD0014_BAD_QUERYTEXT_ID
The requested query text is not found in the system catalog.
E - RD0015- AMBIGUOUS - REPLACE
Attempted to update the same fOW twice.
E_RD0016_KEY_SEQ
An illegal key sequence was specified.
E - RD0017- TABLE- EXISTS
The operation specified tried to create a table that already exists.
E - RD0018- NONEXISTENT - TABLE
The operation required the use of a table that does not exist.
E - RD0019 - TABLE- ACCESS - CONFLICT
Table access conflict, table opened twice.
E - RDOOIA - RESOURCE- ERROR
RDF received out-of-resource error from DMF
NOT
FOUND
E - RDOOIB - HISTOGRAMRDF could not found histogram associated with statistics tuple
E - RD0020- INTERNAL- ERR
RDF internal errOf.

30-2

RD Class Messages

E - RD0021 - FILE- NOT- FOUND
Underlying physical file for table not found

E - RD0025- USER- ERROR
error by caller, error has been reported or logged by RDF

E- RD0030SCF
-ERROR
General error from SCU.

E - RD003l - SEM- INIT - ERR
Error in SCU initializing a semaphore.

E - RD0032NO
-SEMAPHORE
The semaphore is not known to SCU.

E - RD0034- RELEASE- SEMAPHORE
Error releasing ULH semaphore

E - RD0040ULH
-ERROR
General error from ULH.

E - RD0041BAD
-FCB
RDF facility control block contains bad cache id.

E - RD0042- CACHENOT
-EMPTY
Error detected in cloasing a non-empty cache.

E - RD0043 - CACHE - FULL
No more space in cache to build or extend a descriptor block.

E - RD0044- BAD - INFO - BLK
User's information block is corrupted.

E - RD0045ULH
-ACCESS
Failed to gain access to a ULH object due to ULH error

E - RD0050- TRANSACTION- ABORTED
The transaction has been aborted.

E- RD0060- DMT- SHOW
Cannot access table information due to a non-recoverable DMT_SHOW error

E - RD0071 - NO- PROT- INT
error by caller asking for QTUPLES but no request for protect or integrity tuples

RD Class Messages

30-3

E - RD0072NOT
-OPEN
error by caller attempt to close PROTECTION or INTEGRITY tuple stream which was
not open
E - RD0073- TUPLE- COUNT
error by caller bad tuple count for qrymod retrieve
E - RD0076- OPEN
integrity or protection table already opened, but record access id not available
E _ RD0077 _ QEU_OPEN
QEU could not open query mod table
E_RD0078_QEU_GET
QEU could not get data from query mod table
E _ RD0079 _ QEU_CLOSE
QEU could not close query mod table
SYS
E - RDOI02-CATALOG
consistency check - more than one extended system catalog was opened at the same time
by RDF within the same thread
E - RDOI03NOT
-OPENED
consistency check - attempt to read system catalog which was not opened
E - RDOI04- BUFFER
consistency check - internal buffer for reading extended system catalogs not large enough
E _ RDOIOS _NO _QDATA
consistency check - QEF_QDATA structure not initialized
E - RDOI06- CELL- COUNT
consistency check - iistatistics tuple contains invalid cell count
E_RDOI07 _ QT_SEQUENCE
consistency check - query tree tuple out of sequence
ADI
E - RDOI08-FIDESC
consistency check - error calling the ADI_FIDESC routine
E_RDOIIO_QRYMOD
consistency check - internal error processing querymod operation
E - RDOlll - VIEW
consistency check - internal error processing view operation
30-4

RD Class Messages

E - RDOl12- ATTRIBUTE
consistency check - inconsistent attribute cache

E - RDOl13 - KEYS
consistency check - inconsistent keying info in attribute cache

E - RDOl14- HASH
consistency check - inconsistent attribute hash info

E - RDOl16- OINDEX
consistency check - request for 0 index tuples

E RDOl17 STREAMID
consistency check - cannot find stream id for memory allocation
E - RDOl18- ULMOPEN
consistency check - error calling ULM open

E - RDOIIAULH
-RELEASE
consistency check - error releasing ULH object

E- RDOIIB - PRIVATE
consistency check - private memory stream expected

E - RDOIICULM
-CLOSE
consistency check - error closing private memory stream

E - RDOIID - DAPERMIT
consistency check - error defining permit all to all

E - RDOIIE - DRPERMIT
consistency check - error defining retrieve permit to all

E - RDOIIF- DINTEGRITY
consistency check - error defining integrity

E - RD0120- DPERMIT
consistency check - error defining permit

E - RD0121 - DESTROY- VIEW
consistency check - error destroying view

E - RD0122- DESTROY- PERMIT
consistency check - error destroying permit

RD Class Messages

30-5

E RD0123 CREATE VIEW

consistency check - error creating view
E - RD0124- DESTROY- INTEGRITY
consistency check - error destroying integrity
E - RD0125 - EXCEPTION
consistency check - unexpected exception in RDF
E - RD0126- EXEXCEPTION
consistency check - unexpected exception processing exception in RDF
E - RD0127- ULM- PALLOC
consistency check - error calling ulm_palloc
E - RD0128- SERVER- MEMORY
consistency check - error releasing server memory to SCF
E - RD0129RDF
-STARTUP
consistency check - error obtaining memory on RDF startup
ULH
E - RD012A-CLOSE
consistency check - error shutting down ULH
ULM
E - RD012B-CLOSE
consistency check - error closing down ULM memory stream for facility
ULH
E - RD012C-SEMAPHORE
consistency check - cannot get access to ULH semaphore
ULH
E - RD012D-ACCESS
consistency check - error from ULH ALIAS command
E_RD012E_QUERY_TREE
consistency check - bad query tree
E_RD012F_QUERY_TREE
attempt to write out an invalid query tree symbol type
PST
LEN
E - RD0130attempt to write out an invalid query tree symbol type - pst_len incorrect
E_RD0131_QUERY_TREE
attempt to write out an invalid query tree header - an uninitialized field was found

30-6

RD Class Messages

E_RD0132_QUERY_TREE
consistency check - invalid tree node was read in from catalogs

E _ RD0133 _ QUERY_TREE
user error - old version of query tree, update views, integrities and permits

E - RD0134- INVALID- SECONDARY
consistency check - iirelation secondary index is inconsistent

E - RD013S - CREATE- PROCEDURE
consistency check - error writing procedure object to catalogs

E - RD0136- CONCURRENT- PROC
consistency check - invalid concurrent access to procedure object

E - RD0137- DUPLICATE - PROCS
consistency check - more than one procedure defined with same name

E _RD0138_QUERYTEXT
consistency check - error reading procedure text from iiqrytext

E- RD0139- DROP- PROCEDURE
consistency check - cannot drop procedure due to QEF error

E - RD013A- UNFIX - PROCEDURE
consistency check - cannot unfix procedure

E - RD013B - BAD- ATTR - COUNT
consistency check - bad attribute count of zero for relation

E- RD0200NO
TUPLES
user error - attempt to read query tree tuples but none were found
for the query ID, probable cause is associated table has been deleted

E - RD0201 - PROC- NOT- FOUND
procedure does not exist

E_RD02S0_DD_QEFQUERY
error occurs when calling QEF to process SQL query

E _RD02S1_DD _QEFFETCH
error occurs when calling QEF to fetch tuple

E_RD02S2_DD_QEFFLUSH
error occurs when calling QEF to flush buffer

RD Class Messages

30-7

E_RD0253_DD_NOOBJECT
no object was found in system catalog

E- RD0254DD
-NOTABLE
local table not found in local db

E RD0255 DD COLCOUNT

error occurs when retrieving column count information

E RD0256 DD COLMISMATCH

column count mismatch

E- RD0257DD
-NOLDB
local database was no defined in system catalog

E- RD0258DD
-NOINGTBL
object was not defined in system catalog

E- RD0259DD
-NOPHYTBL
object was not defined in system catalog

E- RD025A- ULMSTART
ulm error

E- RD025B - ULMSHUT
ulm error

E- RD025C - INVALID DATE
error occurs when converting date

E- RD025D - INVALID - DATATYPE
invalid attribute data type

E_RD025E_QEF_LDBINFO
error occurs when calling QEF for ldb information

E RD025F NO LDBINFO

ldb description was not defined in system catalog

E_RD0260_QEF _DDBINFO
error occurs when calling QEF for ddb information

E_RD0261_QEF _USRSTAT
error occurs when calling QEF for user stats

30-8

RD Class Messages

E _ RD0262 _ QEF_ IIDBDB
error occurs when calling QEF for iidbdb infonnation
E_RD0263_QEF_LDBPLUS
error occurs when calling QEF for ldb infonnation
E_RD0264_UNKOWN_OBJECT
undefined object type
E - RD0265 - STORAGETYPE
-ERROR
undefined storage type
E - RD0266NO
-INDEXTUPLE
index tuple not found
NO
E - RD0267-STATSTUPLE
statistics not found
E - RD0268- LOCALTABLE- NOTFOUND
local table not found in LDB
E _ RD0269 _ OBJ_ DATEMISMATCH
alter date in the local table mismatches alter date in CDB
E_RD026A_OBJ_INDEXCOUNT
consistency check error on index count
E - RD026B - UNKNOWN - UPDATEMODE
unknown update mode
E - RD026C - UNKNOWN - USER
unauthorized user
E - RD026D - USER - NOT - OWNER
user does not own the local table
E_RD026E_RDFQUERY
already in tuple fetching mode
E - RD026F- RDFFETCH
fetch tuple before sending query
E - RD0270- RDFFLUSH
invalid buffer flush request

RD Class Messages

30-9

E_RD0271_UNKNOWN_STORAGETYPE

E - RD0271 - UNKNOWN - STORAGETYPE
unknown storage type for an object
E_RD0272_UNKNOWN_DDREQUESTS
unknown distributed information requests
E - RD0273- LDBLONGNAME- NOTFOUND
unable to find ldb long name
E - RD0274- LDBDESC - NOTFOUND
unable to find ldb descriptor
E - RD0275- UNKNOWN - LDBCAPABILITY
unknown ldb capability
E - RD0276- INCONSISTENT- CATINFO
error detected in distributed catalog
E - RD0277 - CANNOTGET
ASSOCIATION
cannot get ldb association
E - RD0278- MISMATCH- ARCHITECT- ID
qtree was created by different architecture
E - RD0279 - NO - SESSION - CONTROL- BLK
unable to retrieve rdf session control block from scf
E - RD027A- GET- ARCHINFO - ERROR
error detected when calling qef for architecture info
E - RD027B - IITABLES - NOTFOUND
ii tables not found in local database

30-10

RD Class Messages

RQ Class Messages

E_RQOOOl_WRONG_COLUMN_COUNT
LDB return column count differs from STAR's.
E _ RQ0002 _NO_TUPLE _DESCRIPTION
Missing GCA_TD_DATA. STAR or LDB protocol error.
E_RQ0003_TOO_MANY_COLUMNS
LDB return column count differs from STAR's.
E_RQ0004_BIND_BUFFER_TOO_SMALL
QEF column bind buffer to small. STAR internal error.
E_RQ0005_CONVERSION_FAILED
Catalog column data conversion failed. STAR or LDB internal error.
E_RQ0006_CANNOT_GET_ASSOCIATION
Cannot establish connection to LDB server for node=%Oc, database=% 1c, DBMS=%2c.
E_RQ0007_BAD_REQUEST_CODE
Invalid RQF request code. STAR internal error.
E_RQ0008_SCU_MALLOC_FAILED
Cannot allocate memory from SCF. STAR internal error.
E_RQ0009_ULM_STARTUP_FAILED
Cannot start up ULM. STAR internal error.
E_RQOOIO_ULM_OPEN_FAILED
ULM stream open failed. STAR internal error.
E_RQOOll_INVALID_READ
GCA_RECEIVE failed.
E_RQ0012_INVALID _WRITE
GCA_SEND failed
RQ Class Messages

31-1

E_RQ0013_ULM_CLOSE_FAILED
ULM stream close failed.
E _ RQ0015 _UNEXPECTED _MESSAG E
Unexpected GCA message.
E_RQ0017_NO_ACK
Missing acknoledgement for GCA_ATTENTION message.
E_RQ0018_SHUTDOWN_FAILED
RQF shutdown failed
E_RQ0019_COMMIT_FAILED
RQF commit failed
E_RQ0020_ABORT_FAILED
Error occured during RQF abort.
E_RQ0021_BEGIN_FAILED
Cannot begin transaction.
E _ RQ0022 _END _FAILED
Cannot end transaction.
E_RQ0023_COPY_FROM_EXPECTED
Expecting COpy FROM indication from LDB.
E_RQ0024_COPY_DEST_FAILED
Table transfer failed at destination site.
E_RQ0025_COPY_SOURCE_FAILED
Table transfer failed at source site.
E _ RQ0026 _ QID _EXPECTED
Query ID expected from LDB.
E _ RQ0027 _ CURSOR_CLOSE_FAILED
Close cursor failed.
E_RQ0028_CURSOR_FETCH_FAILED
Cursor fetch failed.
E_RQ0029_CURSOR_EXEC_FAILED

31-2

RQ Class Messages

Execute cursor failed.
E_RQ0030_CURSOR_DELETE_FAILED
Cursor delete failed.
E_RQ0031_INVALID_CONTINUE
Direct connection protocol error.
E _ RQ0032 _DIFFERENT_TUPLE _SIZE
LDB and STAR differ on tuple size.
E_RQ0033_FETCH_FAILED
Data fetch from LDB message failed.
E_RQ0034_C OPY_C REATE_FAILED
Temporary table creation for a transfer failed.
E_RQ0035_BAD_COL_DESC_FORMAT
Cannot process tuple description.
E_RQ0037_II_LDB_NOT_DEFINED
II_LDB_SERVER not defined.
E _ RQ0038_ ULM_ ALLOC _FAILED
Memory allocation failed. Status %x.
E_RQ0039 _INTERRUPTED
LDB request was interrupted.
E _ RQ0040 _UNKNOWN_REPEAT _ Q
Invalid repeat query id used during repeat query execution.
E_RQ0041_ERROR_MSG_FROM_LDB
LDB reports error:
"%Oc"
E_RQ0042_LDB_ERROR_MSG
Preceding message is from LDB=%Oc, NODE=% Ic, DBMS=%2c
E_RQ0043_CURSOR_UPDATE_FAILED
Cursor update failed.
E_RQ0044_CURSOR_OPEN_FAILED
Cursor open failed.

RQ Class Messages

31-3

E _ RQ0045 _CONNECTION_LOST
RQF lost the connection to LOB
E_RQ0046_RECV_TIMEOUT
RQF receiver timed out, LOB did not respond.
E_RQ0047_UNAUTHORIZE_USER
Unauthorized user=%Oc, connecting to node=% Ic, database=%2c, OBMS=%3c

31-4

RQ Class Messages

SC Class Messages

E - SCOOOO- OK
System Control Facility operation has been successfully completed.
OP
E - SCOOOI-CODE
Operation code to scf_callO was not recognized.
BAD
E - SC0002-SEMAPHORE
Semaphore has not been initialized or has been corrupted.
E - SC0003- INVALID - SEMAPHORE
Indicated semaphore has not been initialized or has been corrupted.
E - SC0004- NO- MORE - MEMORY
No more available to the server.
E_SC0005_LESS_THAN_REQUESTED
Not all memory requested has been allocated.
NOT
E - SC0006-ALLOCATED
Attempt to free memory which has not been allocated.
E - SC0007 - INFORMATION
Request for an invalid item of information.
E - SC0008- INFO - TRUNCATED
Insufficient space for requested information. The result has been truncated.
E - SC0009- BUFFER
Buffer provided for information is not addressable.
NO
BUFFER
E - SCOOOARequest for information with no result buffer.
E_SCOOOB_NO_REQUEST
Pointer to/portion of SCI blk not addressable.
SC Class Messages

32-1

E - SCOOOC - BUFFER- LENGTH
Length of error message is invalid.
E - SCOOOD- BUFFER- ADDR
Specified scf_buffer address not accessible.
E - SCOOOE- AFCN - ADDR
AIC/PAINE address provided is not accessible.
E - SCOOOFIN-USE
Memory/semaphore not freed by allocator.
E - SC0010NO
-PERM
Facility not authorized to use SCS_ALWAYS_MASK.
E - SC0011 - NESTED - DISABLE
Attempt to disable AIC's while AIC's are disabled.
NOT SET
E - SC0012Attempt to release a semaphore which is not set.
E - SC0013- TIMEOUT
Out of time before operation completed.
E - SC0014 - INTERRUPTED
User interrupt while awaiting completion.
E - SC001S - BAD - PAGE- COUNT
Invalid ( 0) number of pages requested.
E - SC0016- BAD - PAGE- ADDRESS
Page address is improperly aligned.
E - SC0017BAD
-SESSION
Session id to SCF request is neither the current session nor the DB _NOSESSION value.
E - SC001SBAD
FACILITY
Facility id to SCF request is invalid.
E - SC0019 - BAD - FUNCTION - CODE
Function code is invalid.
E - SC0020- WRONG - PAGE- COUNT
Page count to be freed does not match allocated quantity.

32-2

SC Class Messages

E- SC0021 BAD
-ADDRESS

Attemp to free memory which had not been allocated.
E_SC0022 _BAD _REQUEST_BLOCK

Request block to scf_callO was incorrect format.
E- SC0023- INTERNAL- MEMORY- ERROR

SCF memory arena has been corrupted.
E- SC0024- INTERNAL - ERROR

Internal SCF coding error.
E SC0025 NOT YET AVAILABLE

Function requested has not yet been implemented. Contact the development team for
scheduling information.
E SC0026 SCB ALLOCATE

Unable to allocate SCB.
E- SC0027 - BUFFER - LENGTH

Invalid buffer length on SCU_INFORMATION call.
E SC0028 SEMAPHORE DUPLICATE

Attempt to set a semaphore which is currently set by requester.
E- SC0029 - HOLDING- SEMAPHORE

Attempt to scd_suspend while holding a semaphore.
E- SCOIOO- MULTIPLEMEM
-INIT

Attempt to initialize memory more than once.
E- SCOIOI - NO - MEM - INIT

Attempt to allocate memory before initializing it.
E- SCOI02- MEM- CORRUPT

SCF memory arena has been corrupted.
E- SCOI03 - MEM- PROTECTION

Error changing memory protection.
E- SCOI04- CORRUPT- POOL

Corrupted pool block found at %Ox.
E- SCOI05 - CORRUPT- FREE

Corrupted free block found at %Ox.

SC Class Messages

32-3

E - SCOI06- BAD - SIZE- REDUCE
Error reducing virtual size of server.
E - SCOI07 - BAD - SIZE- EXPAND
Error expanding virtual size of server.
E - SCOI08- UNEXPECTED - EXCEPTION
Unexpected exception (%Ox) trapped.
DB
E - SCOI09 - MULTI-ADD
Attempt to add database %Oc to the server by session % Ix. That database has already
been added to the server.
E - SCOIOA - RETRY
Operation should be attempted again.
E - SCOIOB - SCB - DBCB - LINK
The linkage between the database control block and the session control block has been
corrupted.
DB
E - SCOIOC-ADD
Error adding database. Name: %Oc Owner: %Ic Access Mode %2x Flags %3x
DB
E - SCOIOD-LOCATION
Database Location Name: %Oc Physical Specification: % Ic Flags: %2x
DB
E - SCOIOE-DELETE
Error deleting database. Name: %Oc Owner: %Ic Added Id %2x
E - SCOIOF- INCOMPLETE- DB - DELETE
SCF Database deletion incomplete. Name: %Oc Owner: % Ic
E - SCOl20- DBLIST- ERROR
SCF Error while attempting known database listing.
E - SCOl21 DB
OPEN
Error opening database. Name: %Oc Owner: % Ic Access Mode: %2x Flags %3x
E - SCOl22DB
-CLOSE
Error closing database. Name: %Oc Owner: % Ic
E - SCOl23 - SESSION- INITIATE
Error initiating session.
E - SCOl24- SERVER- INITIATE
Error initiating ULTRIX/SQL Server.
32-4

SC Class Messages

E - SC0125 - POOL- ADDITION
SCF Error adding memory pool.

E - SC0126- SCOM- CHECK
Error discovered in SCF Memory.

E- SC0127- SERVER- TERMINATE
Error terminating Server.

E - SC0128- SERVER- DOWN
ULTRIX/SQL Server Normal Shutdown., process id % Id

E - SC0129- SERVER- UP
ULTRIX/SQL Release 1.0 - %Oc Server -- Normal Startup., process id % Id

E- SC012A- BAD - MESSAGE- FOUND
Unable to format message number %Ox.

E - SC012B - SESSION- TERMINATE
Error terminating Session.

E - SC012CADF
-ERROR
Error encountered initiating ADF.

E - SC012D- DB - NOT- FOUND
Requested Database not found In SCF's known db list.

E_SC012E_QEP _INVALID
Database reorganization activity has rendered the query plan invalid. Try again after the
db activity is complete. In case of dynamic SQL, the statement must be prepared again.

E - SC012F- RETRY
Query plan has been rendered invalid. Retry.

E - SC0200SEM
-INIT
Error initializing semaphore.

E - SC0201SEM
-WAIT
Error waiting for semaphore.

E - SC0202SEM
-RELEASE
Error releasing semaphore.

E - SC0203SEM
-FREE
Error freeing semaphore.

SC Class Messages

32-5

E - SC0204- MEMORY- ALLOC
Error allocating memory.
E - SC020S- BAD- SCS - OPERATION
Sequencer called incorrectly.
E - SC0206- CANNOT - PROCESS
An internal error prevents further processing of this query.
Please contact the ULTRIX/SQL system administrator.
E - SC0207- UNEXPECTED - ERROR
Facility returned an undocumented error.
E - SC0208 - BAD - PSF - HANDLE
QSF Handle returned was unusable.
E_SC0209 _PSF _REQ_DISTRIBUTED
PSF requested a distributed query mode.
E_SC020A_UNRECOGNIZED_QMODE
The Query Mode %Od is unknown.
E - SC020B - UNRECOGNIZED - TEXT
Text is '%Oc'.
E_SC020C_INPUT_ OUT_OF_SEQUENCE
Sequencer received unrequested input.
NO
E - SC020D-DISTRIBUTED
Distributed operations are not supported in this server.
E - SC020E- MULTI- CURSOR- OPEN
I don't remember what this means.
E - SC020F- LOST- LOCK
The object lock for the input text is unavailable.
E_SC0210_SCS_SQNCR_ERROR
Sequencer Internal Error.
E - SC0211CLF
-ERROR
Error returned by eLF.
E - SC0212ADF
-ERROR
Error returned by ADF.

32-6

SC Class Messages

E - SC0213 - DMF- ERROR
Error returned by DMF.
E - SC0214OPF
-ERROR
Error returned by OPF.
E - SC0215PSF
-ERROR
Error returned by PSF.
E _ SC0216_ QEF_ERROR
Error returned by QEF.
E_SC0217 _QSF _ERROR
Error returned by QSF.
RDF
E - SC0218-ERROR
Error returned by RDF.
SCF
E - SC0219-ERROR
Error returned by SCF.
E - SC021AULF
-ERROR
Error returned by ULF.
E - SC021B - BAD - COpy- STATE
Saved COpy state is invalid.
E - SC021C - SCS - INPUT - ERROR
SCS_INPUT internal error.
E - SC021D- TOO - MANY - CURSORS
Number of open cursors exceeds the local limit.
E - SC021E- CURSORNOT
-FOUND
Specified cursor is not known to the server.
E_SC021F_BAD _SQNCR_ CALL
Internal Error: Call to sequencer is incorrect.
E - SC0220- SESSION - ERROR- MAX
Too many errors for this session.
E - SC0221 - SERVER- ERROR- MAX
Error count for server has been exceed.

SC Class Messages

32-7

E - SC0222- BAD- SCDNOTE- STATUS
Bad status passed to SCD_NOTEO -Status was %Ox (%Od), facility was % Ix (% Ix).
E - SC0223- BAD - SCDNOTE- FACILITY
Invalid facility code was passed to scd_noteO -Status was %Ox (%Od), facility was % Ix (% Ix).
E - SC0224- MEMORY- FREE
Unable to deallocate SCF memory.
E - SC0225- BAD - GCA- INFO
Unable to get information about a GCA block.
E - SC0226- BAD - GCA - TYPE
GCA block has an invalid block type -- %Ox (%Od.).
E - SC0227- MEM - NOT- FREE
Facility %Ox had not freed session memory at end of session.
E - SC0228- INVALID - TRACE
Invalid SCF trace flag specified.
ATTN
E - SC0229 - INVALID-CALL
Invalid AIC delivered to SCF session.
E - SC022A - SERVER- LOAD
Insufficient system/server resources to complete the current query. Consult the system
administrator and/or error log.
E - SC022B- PROTOCOL - VIOLATION
Improper GCA block type (or connection block) was sent.
MSG
END
E - SC022C - PREMATUREInternal Protocol Error: Message type %Ox (%Od.) ended with a dmm value of %ld.
E - SC022D - BLOCK- NOT - MD - ASSOC
Internal Protocol Error: First communication block from a new session was type %Ox
(%Od.). Must be GCA_MD_ASSOC (2).
E - SC022E- WRONG - BLOCK- TYPE
Internal Protocol Error: SCF received block type %Ox (%Od.) when expecting type %lx
(%ld.).
E - SC022F- BAD- GCA- READ
SCF was unable to read a GCF block.
32-8

SC Class Messages

E - SC0230- INVALID - CHG- PROT- LEN
A protection block was sent with a length (%Od.) not equal to 1.

E - SC0231 - INVALID - CHG- PROT- CODE
A protection block was sent with an invalid code of %Ox (%Od.). This code must be
GCA_SUPSYS.

E - SC0232- INVALID - STARTUP- CODE
A startup code(index %Ox (%Od.), value % Ix (% Id.)) was sent which is unknown to the
server. The server not start.

E - SC0233- SESSION- START
Session created for %Oc (real: %Ic) on database %2c for %3c%4c access.

E - SC0234- SESSION- END
Session ended.

E - SC0235 - AVERAGE - ROWS
On %Od. select/retrieve statements, the average row count returned was % Id.

E - SC0236- FAST- COMMIT- INVALID
Server must be started with SOLE_SERVER option in order to use Fast Commit.

E - SC0237 - FAST- COMMIT- ADD
Error adding Fast Commit thread to the server.

E - SC0238- FAST - COMMIT- EXIT
Fast Commit Thread terminated abnormally.

E - SC0239 - DBMS - TASK - ERROR
Internal error initializing a DBMS server task - task type (%Od.) not recognized.

E - SC0240- DBMS - TASK - INITIATE
Internal error initializing a session for a DBMS server task - Server Task name' %Oc' .

E - SC0241 - VITAL- TASK- FAILURE
A Server Task thread necessary to the server has terminated forcing the shutdown of the
DBMS server - Server Task name '%Oc'.

E - SC0242- ALTER- MAX- SESSIONS
Error altering Max Sessions count to allow for DBMS tasks - old count %Od, new count
%Id.

E - SC0243 - WRITE- BEHIND- ADD
Error adding Write Behind thread to the server.

SC Class Messages

32-9

E - SC0244- WRITE- BEHIND- EXIT
Write Behind Thread terminated abnormally.
E - SC0245- CANNOT- REGISTER
Unable to start server, failed to register with the nameserver.
E_SC0250_COPY_OUT_OF_SEQUENCE
A COpy data block was received when one was not expected (or not received when
expected).

E SC0251 COpy CLOSE ERROR

Error ending the COPY statement.
E - SC0252- COpy- SYNC - ERROR
Synchronization error with GCA COpy protocol.
E - SC0253- BAD - COpy- ERRMSG
Error message for COpy statement not found.
E _ SC0300_ EXDB _LOCK _ REQ
This operation requires an exclusive database lock.
E - SC0301LOC
-EXISTS
This location already exists.

32-10

SC Class Messages

TO Class Messages

E - TDOOOI - Buffer- overflow
Buffer overflow on push back
E _ TD0002 _ Cyclic_key_definition
Cyclic key definitions
E _ TD0003 _error _opening
TERMCAP: error(%d) in opening %s
E _ TD0004 _Termcap_entryJong
Termcap entry too long
E _ TD0005 _Bad_ tenncap _entry
Bad termcap entry
E _ TD0006_Infinite_ tc_loop
Infinite tc= loop
E - TD0007 - OPEN- ERR
Can't open file to output function key definition error messages.
E - TD0008- BADHAT
Invalid character after the '1\' character.
E _ TD0009 _BADBSQ
Back backslash C\') sequence.
E _ TDOOOA_ AFBSQ
No character found after a backslash C\').
E - TDOOOB - NONUM
No digits following a '#' character.
E - TDOOOC - BADNUM
A function key number must be identified by a 2 digit sequence.
TO Class Messages

33-1

E - TDOOOD - NUMCONV
An error occurred while converting a key number from its character representation.

E - TDOOOE - NOKEY
Function key '%Od' does not exist for the terminal you are using.

E - TDOOOF- NOALW
Function key' %Od' may not be use in a definition statement.

E - TDOOIO- KEYSELF
May not define a function key that references itself.

E - TDOOll - NOPFK
Your terminal description does not support function keys.

E - TD0012 - FIRSTCH
First character on a line must be the '#' character.

E - TD0013 - DIGITS
Function keys must be identified by a 1 or 2 digit character sequence.

E_TD0014_EQUAL
You must use the equal character C=') to assign a definition to a function key.

E - TD0015 - KEYRES
Function keys '%Od' and '%ld' are reserved and definitions be not be assigned to them.

E - TD0016- INSOVFL
Buffer overflow when installing expanded definition.

E - TD0017 - BNUMEX
An unknown function key number was encountered on macro expansion.

E - TD0018- OVFL
Buffer overflow during definition expansion.

E - TD0019 - REFDEF
Definition references a function key with no definition.

E - TDOOIA- NULLEXP
Result of a definition expansion was the null string.

E - TDOOIB - AFHAT
No character found after the 'I\' character.

33-2

TO Class Messages

E - TDOOIC - NO TERM
Can not determine user's terminal type.
Either TERM_INGRES is not defined or it is defined to nothing. Please check that
TERM_INGRES is defined correctly and restart.
Explanation:

Can't find TERM_INGRES or it is defined to be empty string.

System Status:

Forms system will not start up.

Recommendation:

Needs to check TERM_INGRES and restart.

E - TDOOID - UNKNOWN
An entry for terminal type '%Oc' can not be found in the termcap file. Please make sure
TERM_INGRES is properly defined. If the terminal you have does not match any existing
entries in the termcap file, you will need to write a termcap entry for your specific
terminal. Please refer to the Terminal Users Guide for directions.
Explanation:

Terminal type not found in termcap file.

System Status:

Forms system will not start up.

Recommendation:

User needs to make sure they defined TERM_INGRES correctly
or write a termcap entry for a new terminal type.

E - TDOOIE - NOTTERM
Can not open interactive communications.
Forms based applications can not be run in batch mode. Please make sure application is
running from an interactive terminal.
Explanation:

TEopen failed. Can't run forms in background or batch.

System Status:

Forms system will not start up.

Recommendation:

User needs to run a forms based application from an interactive
terminal.

E - TDOOIF- CURINIT
Error occurred while initializing current screen.
E - TD0020- MSGINIT
Error occurred while initializing standard message screen.
E - TD0021 - UNKNOWN
Terminal name '%Oc' is not understood. Please make sure TERM_INGRES is properly
defined. Refer to the ULTRIX/SQL Reference Manual for a list of accepted terminals.
Explanation:

Terminal type not found in term cap file.

System Status:

Forms system will not start up.

Recommendation:

User needs to make sure they defined TERM_INGRES correctly.

TO Class Messages

33-3

TP Class Messages

E_TPOOOl_INVALID _REQUEST
Invalid TPF request code.

E - TP0002 - SCF- MALLOC - FAILED
SCF_MALLOC failed.

E - TP0003 - SCF- MFREE- FAILED
SCF_MFREE failed.

E - TP0004- MULTI- SITE- WRITE
Multi -site update attempted.

E - TPOOOS - UNKNOWN- STATE
Unknown TPF transaction state.

E - TP0006- INVALID - EVENT
Unknown TPF event.

E - TP0007 - INVALID - TRANSITION
Invalid TPF event for the current state.

E - TP0008- TXN - BEGIN- FAILED
Unable to perform BEGIN TRANSACTION request.

E - TP0009TXN
FAILED
Transaction failed.

E - TPOOIO- SAVEPOINT- FAILED
Unable to complete savepoint request.

E - TPOOll SP ABORT- FAILED
Savepoint abort failed.

E - TP0012 SP NOT- EXIST
Unknown savepoint name.
TP Class Messages

34-1

E- TP0013 - AUTO - ON- NO - SP
Autocommit with savepoint is not permitted.

E- TP0014 - ULM- STARTUP- FAILED
ULM session startup failed.

E- TP0015 - ULM- OPEN- FAILED
ULM memory stream open failed.

E- TP0016- ULM - ALLOC - FAILED
ULM memory stream allocation failed.

E - TP0017 - ULM- CLOSE- FAILED
ULM memory stream close failed.

34-2

TP Class Messages

UD Class Messages

E_UDOOOl_Incorrect_language_sp
Incorrect language specification.
Explanation:

The user specified the DDL/DML language incorrectly.

System Status:

The default language for the installation is used.

Recommendation:

Check the language specifications and rerun if necessary.

E - UD0002- You- are- not- the- dba
You (%Oc) are not the dba for this database. Only the dba is allowed to run UNLOADDB.
Explanation:

A user other than the dba attempted to run Unloaddb.

System Status:

program terminates.

Recommendation:

Only the dba may run Unloaddb.

E UD0004- Cannotalloc
-username
Cannot allocate memory for usemame list.
System Status:

Program terminates.

Recommendation:

Make sure there is enough memory to run program.

S- UDOOOS- There is one user who
There is one user who owns tables in this database.
S- UD0006- There - are n users- who
There are %Od users who own tables in this database.
E _ UD0007 _Cannot_start _ name _gen
Cannot start name generator.
Explanation:

The file name generator cannot be initialized.

System Status:

Program terminates.

Recommendation:

Rerun, then please submit a Software Performance Report (SPR).

S_ UD0008_Completed_UNLOADDB _an
Completed UNLOADDB and built execs named UNLOAD and RELOAD.
UD Class Messages

35-1

S_ UD0009 _Don_t_forget_to_run_ U
Don't forget to run UNLOAD before destroying the database.

S_ UDOOOA_ Completed_unload_ing_
Completed unload.ing and reload.ing

S_ UDOOOB _Don _t _forget_to _run_ u
Don't forget to run unload.ing before destroying the database.
Explanation:

The reload script has been aborted because there are already
frontend objects in the database.

System Status:

Program terminates.

Recommendation:

Reloading data should only be run on an empty database.

E _ UDOOOC _abort_reload_script
There are existing frontend objects in this database. You cannot use the reload scripts on a
database that currently contains frontend objects.

E_ UDOOOD _Not_Ingres
This DBMS does not have the capability to run unloaddb. You must be running against an
ULTRIX/SQL DBMS to use these products.
Explanation:

Unloaddb is being run on a database that contains no user data to
unload.

System Status:

Program terminates.

Recommendation:

None. Unloaddb does not need to be run on an empty database.

E- UDOOOE-No-Users
This database does not contain any data to unload. Unload db does not need to be run on
this database.

35-2

UD Class Messages

UF Class Messages

S UFOOOI
Entering editor on field %s.
S UF0002
Edit file '%s' is empty; field/column value will be unchanged.
Bad
Create
E - UF0003Could not create temporary edit file.
A temporary file used to edit a field or column value could not be created or opened. The
field or column value will remain unchanged. Please check your temporary directory
access rights and disk quota.
The system status was %Od.
Explanation:

A temporary file used to edit the contents of a field or column
could not be created and opened. This could be for any number
of reasons, but is most likely a quota or access problem.

System Status:

The contents of the field or column will not be changed.

Recommendation:

Make sure that the you have access rights to the temporary
directory and sufficient disk quota to create files.

E - UF0004Bad
-Close
Could not close temporary edit file.
The temporary edit file' %Oc' could not be closed prior to calling the editor.
The field or column value will remain unchanged. Please check your temporary directory
access rights and disk quota before submitting a Software Performance Report (SPR).
The system status was % ld.
Explanation:

A temporary file used to edit the contents of a field or column
could not be closed after being created but before starting the
system editor. This is an unusual error that could be a quota or
access problem but could also be an internal programming error.

System Status:

The contents of the field or column will not be changed.

Recommendation:

Make sure that the you have access rights to the temporary
directory and sufficient disk quota to create files before
submitting a Software Performance Report (SPR).

UF Class Messages

36-1

E _ UF0005 _Bad_Open
Could not open temporary edit file for reading.
The temporary edit file' %Oc' could not be opened for input after it had been edited. The
field or column value will remain unchanged. Please check your temporary directory
access rights and disk quota before submitting a Software Performance Report (SPR).
The system status was % Id.
Explanation:

A temporary file used to edit the contents of a field or column
could not be re-opened for reading. This could be for any
number of reasons, but is most likely a quota or access problem.

System Status:

The contents of the field or column will not be changed.

Recommendation:

Make sure that the you have access rights to the temporary
directory and sufficient disk quota to create files before
submitting a Software Performance Report (SPR).

E - UF0006Bad Delete
Unable to close or delete temporary edit file.
The temporary edit file' %Oc' could not be closed or deleted, but the field or column value
was already changed. Please check your temporary directory access rights and disk quota
before submitting a Software Performance Report (SPR).
The system status was % 1d.
Explanation:

A temporary file used to edit the contents of a field or column
could not be closed or deleted after the field or column value(s)
had been read. This is an unusual error that could be a quota or
access problem but could also be an internal programming error.

System Status:

The contents of the field or column were already changed.

Recommendation:

Make sure that the you have access rights to the temporary
directory and sufficient disk quota to create files before
submitting a Software Performance Report (SPR).

E - UF0007- NOFRS
Unable to get form from form index file.
The forms system has not been started yet, so obtaining a form from the form index file
may not be done.
Explanation:

Before getting (and initializing) a form from the form index file,
the forms system must already have started up. This restriction is
necessary since initializing a form requires the forms system to
be running. The form index file is used by ULTRIX/SQL
products and should this condition occur, indicates a problem in
the product that outputs this error.

System Status:

The requested form is not available for use. Features that use the
requested form may not be accessed.

Recommendation:

Since the form index file is used by ULTRIX/SQL products, this
should be reported as a problem. Please submit a Software
Performance Report (SPR).

36-2

UF Class Messages

S_U F0008_End NoSavePrompt

S_ UF0008_ EndNoSavePrompt
Do you wish to End without saving changes?
Explanation:

Changes have been made to the current form that have not been
saved. You must confirm that you wish to end without saving the
changes by answering "yes" or "no".

U F Class Messages

36-3

UG Class Messages

E - UGOOOO- OK
UG returns ok

E _ UGOOOl_Bad_Language
A bad value of II_LANGUAGE was given.
Incorrect value of '%Oc' was specified for the name II_LANGUAGE. English will be
used instead. Set the ULTRIX/SQL name of II_LANGUAGE to a valid supported
language name.
Explanation:

This error occurs if a bad II_LANGUAGE is given. The message
system uses a directory with the name of the II_LANGUAGE,
and if that directory is not found, this error will occur. Since
english is always available, it will be used.

System Status:

English will be used as the language for the messages.

Recommendation:

Set a valid value for the II_LANGUAGE name.

E_UG0002 _Bad _Msgid
A bad message id was found.
An incorrect message identifier of '%Ox' was sent to the error processing routine. This is
an internal coding error. Please submit a Software Performance Report (SPR).
Explanation:

This error represents a missing error number which was found in
an internal call. This should never occur, so it should be reported
as a problem. customer support.

System Status:

Pro gram continues.

Recommendation:

Please submit a Software Performance Report (SPR).

E- UG0003Bad
-Classid
A bad class id for a message was found.
An incorrect class identifier for message '%Ox' was sent to the error processing routine.
This is an internal coding error. Please submit a Software Performance Report (SPR).
Explanation:

This error represents an incorrect class id, which was found in an
internal call. This should never occur, so it should be reported as
a problem.

UG Class Messages

37-1

System Status:

Program continues.

Recommendation:

Please submit a Software Performance Report (SPR).

E _ UG0004 _Yes_Response
Yes response given
E _ UG0005 _No_Response
No response given
E _ UG0006 _NULL_Response
Please answer with 'y' or 'n'.
An empty response was detected. You must respond with 'yes' Cy') or 'no' Cn') as no
default response has been defined.
Explanation:

This message is given if an empty response is given for a yes/no
question. Some of the frontends will require and response, and
this message will be given to tell the user to enter a 'yes' or a
'no'.

System Status:

The prompt will be redisplayed.

Recommendation:

You must enter a valid value.

E _ UG0007 _IUegal_Response
Please answer with 'y' or 'n'.
The answer given was not a valid 'yes' or 'no'. You may also answer with a simple
'y'Cyes') or 'n'Cno').
System Status:

The prompt will be redisplayed.

Recommendation:

You must enter a valid value.

E_UG0008 _Required_Response
Please enter a value in response to the prompt.
This prompt requires an answer as a response that is not empty or blank.
Please type something other than blanks or a return.
System Status:

The prompt will be redisplayed.

Recommendation:

You must enter a valid value.

E _ UG0009 _Bad_Memory_Allocation
Fatal memory allocation error in routine '%Oc'.
The product has run out of memory in trying to do the previous operation in such a way
that no recovery is possible. The program will stop. The internal routine in which the error
occurred is '%Oc'. Usually, restarting the program and trying the operation will succeed in
this case. If that is not the case, please submit a Software Performance Report (SPR).
Explanation:

37-2

UG Class Messages

A memory allocation or free error has occurred somewhere in the
code in a place where it was unexpected, or where it was not
possible to recover from the error. This may indicate a bug, or a
limitation which we would like to know about.

System Status:

The program will abort.

Recommendation:

You should restart the program and try the operation again. If it
still fails, please submit a Software Performance Report (SPR).

E - UGOOOA - No Form File

Could not find form index file, '%Oc'.
The form index file could not be found in the current installation. Please report this
installation problem to your system administrator.
Explanation:

ULTRIX/SQL front-ends read the forms that they will use from a
special file that contains all the ULTRIX/SQL forms. A separate
file exists for each ethnic language that ULTRIX/SQL supports.
The file for the current language and installation could not be
found. This is either because it does not exist for the language
specified through II_LANGUAGE
("$II_CONFIG/$II_LANGUAGE/rtiforms.fnx" ,) or the
pathname specified through II_FORMFILE is incorrect. This is
most likely because the installation is incorrect.

System Status:

No forms will be initialized. The program will terminate.

Recommendation:

Determine that the language installation is correct, and re-install
if necessary. Or, if II_FORMFILE was specified make sure that
it specifies a valid pathname.

E - UGOOOB - ExitsLimit

FEset_exit: too many module exits.
Please submit a Software Performance Report (SPR).
Explanation:

The number of exits supported by the exits module has been
exceeded. This is an internal programming problem.

System Status:

The program will terminate.

Recommendation:

Please submit a Software Performance Report (SPR).

E _ UGOOOC _ ExitsMissing

FEclr_exit: module exit not found.
Please submit a Software Performance Report (SPR).
E - UGOOOE - BadName

The name' %Oc' is not a valid ULTRIX/SQL name.
Valid names must begin with either an underscore' _' or a letter, and can consist of letters,
digits, and the characters _, $, @, and # up to a maximum of 32 characters.
Explanation:

A valid ULTRIX/SQL name must be entered as described in the
message. Examples of valid ULTRIX/SQL names are "_123",
"_$name", or "name1". Some invalid names are "%xyz",
"$name", or "Heft".

UG Class Messages

37-3

System Status:

The program will not accept the name until you enter a valid
ULTRlX/SQL name (or in some cases, no value.)

Recommendation:

Enter a valid ULTRlX/SQL name.

E - UGOOOF- NoDBconnect
Error connecting to database '%Oc'.
Explanation:

The program could not successfully connect to the named
database most likely because the database does not exist, or
possibly because the commands specified using the lNG_SET
environment logical are incorrect. Occasionally, successful
database connection may be precluded by other errors (e.g., GCA
errors, etc.) usually evidence of some sort of installation problem
or hardware or system failure.

System Status:

The program will not start up.

Recommendation:

Check that the database name was specified correctly and
re-enter the command line. Also, check that the commands
specified using the lNG_SET logical are correct.

E _ UGOOIO _NoPrompt
%Oc: No user response to request for parameter input.
E_UGOOll_ArgSyntax
Correct syntax:
%Oc %Ic
E _ UG0012 _NoArgValue
%Oc: Expects value.
E _ UG0013 _ TooMany Args
%Oc: Too many arguments.
E _ UG0014_BadArgument
%Oc: Bad argument.
E _ UG0015 _ ArgMissing
%Oc: not specified on command line.
E _ UG0016 _ArgConflict
%Oc: Conflicts with other arguments.
E - UG0017 - ListConflict
%Oc: Conflicts with '% Ie' list.
E - UG0018 - Override
'%Oc' specified, '% Ie' ignored.
37·4

UG Class Messages

E_UG0019 _ArglntReq
%Oc: Integer required.

E _ UGOOIA_ ArgFltReq
%Oc: Real number required.
E UGOOIB

FEutapfx: too many internal parameters, maximum is %Od.
Please check that your installation is correct before submitting a Software Performance
Report (SPR).
Explanation:

Too many parameter specifications were found in the system
specification file. This is an internal programming problem.

System Status:

The program execution will be terminated.

Recommendation:

Please submit a Software Performance Report (SPR).

E UGOOIC
FEutaget: unknown internal parameter name %Oc.
Please check that your installation is correct before submitting a Software Performance
Report (SPR).
Explanation:

The internal parameter name has not been specified in the
parameter specifications for this ULTRIX/SQL subsystem even
though the subsystem expects such a parameter. This is an
internal programming problem.

System Status:

The program execution will be terminated.

Recommendation:

Please submit a Software Performance Report (SPR).

E UGOOID

FEuta: no parameter specification for %Oc.
Please check that your installation is correct before submitting a Software Performance
Report (SPR).
Explanation:

No parameter specifications have been defined for the
ULTRIX/SQL subsystem even though the subsystem is using
the FE UTA module to parse expected command-line parameters.
This is an internal programming problem.

System Status:

The program execution will be terminated.

Recommendation:

Please submit a Software Performance Report (SPR).

E UGOOIE

FEuta: Could not open parameter specification file, '%Oc'.
The file used to parse command-line parameters for this ULTRIX/SQL subsystem could
not be opened. This subsystem will terminate execution.
Please verify that the ULTRIX/SQL files installation is correct and begin again.

UG Class Messages

37-5

E_UG001F

Explanation:

The file containing the execution and parameter specifications
for ULTRIX/SQL subsystems could not be opened. Without this
file the command- line parameters for this subsystem cannot be
parsed. This is likely an installation problem with the file,
"$ING_FILES/utexe.def'.

System Status:

The program execution will be terminated.

Recommendation:

Verify the ULTRIX/SQL installation and that the execution and
parameter specifications file exist in the installation, and then
begin execution of the ULTRIX/SQL subsystem again.

E UGOOIF

FEuta: syntax error in parameter specification, option %Od.
Please check that your installation is correct before submitting a Software Performance
Report (SPR).
Explanation:

The parameter specifications for this ULTRIX/SQL subsystem
contain an internal syntax error. The FE UTA module cannot
continue to parse any command-line parameters. This is an
internal programming problem.

System Status:

The program execution will be terminated.

Recommendation:

Please submit a Software Performance Report (SPR).

E UG0020 BadDateFormat

A bad name was given in II_DATE_FORMAT.
The name' %Oc' specified by the logical variable II_DATE_FORMAT is not recognized
as specifying a valid date format. The format specified by the name 'us' will be used
instead.
Set the ULTRIX/SQL logical variable II_DATE_FORMAT to a valid date format name.
Explanation:

The name given in II_DATE_FORMAT is not recognized as
corresponding to any known date formats. One of these formats
will be used to display or print dates on forms or reports.
Acceptable names are "multinational", "finland" (or "sweden" ,)
"iso", or "us".

System Status:

The date format specified by "us" will be used to display or print
dates.

Recommendation:

Set a valid name for the II_DATE_FORMAT name.

E _ UG0021_BadMnyFormat
A bad format was given in II_MaNEY_FORMAT.
The format' %Oc' specified by the logical variable II_MaNEY_FORMAT is not accepted
for money values. The format '1:$' will be used instead.
Set the ULTRIX/SQL logical variable II_MaNEY_FORMAT to a valid money format.
Explanation:

37·6

UG Class Messages

The format given in II_MaNEY_FORMAT is not accepted as a
valid for money values. This format is used to display or print
money values on forms or reports. Acceptable formats are of the
form: '[It]:$$$$' indicating whether the currency symbol

precedes ('1') or follows ('t') the money value, and the currency
symbol upto a maximum of 4 characters (following the colon':'.)
System Status:

The money format '1:$' will be used to display or print money
values.

Recommendation:

Set a valid format for the II_MONEY _FORMAT name.

E _ UG0022 _BadMny Prec
A bad value was given in II_MONEY _PREC.
The value' %Oc' specified by the logical variable II_MONEY_PREC is incorrect. Valid
precisions are 0, 1 or 2. A precision of 2 will be used instead.
Set the ULTRIX/SQL logical variable II_MONEY_PREC to a valid precision.
Explanation:

The precision given in II_MONEY_PREC is not a valid
precision for money values. This precision is used to display or
print money values on forms or reports. Valid precisions for
money values are 0, 1 or 2.

System Status:

A precision of 2 will be used to display money values.

Recommendation:

Set a valid precision for the II_MONEY_PREC name.

E - UG0023- BadDecimal
A bad value was given in II_DECIMAL.
The character '%Oc' specified by the logical variable II_DECIMAL is not an acceptable
decimal point character. The character' . ' will be used instead.
Set the ULTRIX/SQL logical variable II_DECIMAL to a valid decimal point character.
Explanation:

The character given in II_DECIMAL is not a valid decimal point
character. This character is used to display or print numbers that
can have (l, fractional part, such as money values or real numbers.
Valid decimal point characters are' . ' or ','.

System Status:

A decimal point character of ' . ' will be used to display or print
numbers.

Recommendation:

Set a valid single-character string for the II_DECIMAL name.

E _ UG002F_BadMemoryTag
Internal program error: Memory tag exceeded maximum.
An internal memory tag exceeded the maximum allowed for its type. No more memory
tags can be allocated by the tag allocation utility. Please submit a Software Performance
Report (SPR).
Explanation:

ULTRIX/SQL programs may allocate memory in tagged blocks
with the tags being allocated by an internal tag allocation utility.
This tag allocator has allocated all possible tags and cannot
allocate anymore tags when requested by an ULTRIX/SQL
program. This is an internal program problem.

Recommendation:

Please submit a Software Performance Report (SPR).

UG Class Messages

37-7

S_ UG0030 _Exiting
Exiting ...
S- UG0031 - Because
due to
S_ UG0032....;Interrupt
Interrupt
S- UG0033 - Termination
being terminated
S_ UG0034 _ Quit
Quit signal
S UG0035 EOF

EOF on input
S_ UG0036 _NoMemory
Front-End memory allocation failure
S_ UG0037 _ BugCheck
Front-End internal bug check
S_ UG0038 _ UnknownException
UNKNOWN SOFTWARE EXCEPTION - Ox%x
S_ UG0039 _Hardware_Exception
System/Hardware Exception
S_ UG003A _Software_Exception
Software Exception
S- UG003B - Routine
%c(in '%s')
S_ UG003C _ BugMessage
%cRoutine '%s'.
S- UG003F - Contact
Please submit a Software Performance Report (SPR).

37-8

UG Class Messages

UI Class Messages

E - UIOOOO- OK
Successful return from UI
E - UIOOOI- BLOCK- CLOSED
query block is currently closed
E - UI0002- EOS
no more records in set
E - UI0003 - TOO - MANY - TUP
too many tuples returned for a single tuple qualification
E - UI0004- INIT - ERR
Error in accessing database capabilities
E - UIOOIO- Transaction
ULTRIX/SQL sub-system committing open transaction.
An ULTRIX/SQL sub-system was called with an open transaction still active on the
DBMS session. Neither transactions nor cursors can remain open across sub-system calls.
Explanation:

ULTRIX/SQL sub-systems called through the OSL "call system
... " or the EQL "call system (database = ... )" statements share
the calling application's DBMS session. Since ULTRIX/SQL
sub-systems have their own transaction semantics (partly to
avoid locking system tables,) it is a mistake to call one while a
transaction is still active on the DBMS session.

System Status:

The open transaction will be committed and any open cursors
closed.

Recommendation:

Commit all transactions before calling any ULTRIX/SQL
sub-system.

UI Class Messages

38-1

E - UIOOll - Connect- err

Error in query language specified.
The database connection was created with the query language specified as QUEL. This is
not an option with this installation.
System Status:

38-2

UI Class Messages

A fatal error will be issued.

UL Class Messages

E - ULOOOO- OK
successful completion
E - ULOOOI - BAD- SYSTEM- LOOKUP
ULF error
E_UL0002_BAD_ERROR_LOOKUP
Could not find message in error message file
E- UL0003 - BADPARM
Bad parameter to error message lookup routine.
E - UL0004- CORRUPT
ULM has detected a corrupted memory pooL
E - UL0005 - NOMEM
Either ULM cannot get enough memory from SCF to initialize a memory pool, or the
memory pool has been exhausted.
E- UL0006- BADPTR
Bad pointer has been detected by ULM; pointer to piece of memory lies outside of the
supplied memory pooL
E - UL0007 - CANTFIND
ULM cannot find the block of memory in the pool's allocated list.
E - UL0008- MEM- SEMINIT
SCF would not initialize semaphore.
E - UL0009 - MEM- SEMWAIT
Error attempting to set semaphore.
E - ULOOOA - MEM- SEMRELEASE
Error attempting to release semaphore.

UL Class Messages

39-1

E - ULOOOB NOT
-ALLOCATED
Attempt to perform some ULM operation on a memory pool that was not allocated by you.
E_ULOOOC_BAD_ACK_MODE
ULF error
E - ULOOOD - NEWBLOCK
ULF error
E - ULOOOE - BAD- DO- BLOCK
ULF error
E - ULOOOF- BAD- BLOCK- TYPE
ULF error
E - ULOOIO - NEED- MORE
ULF error
E - ULOOll - MORETO
-SEND
ULF error
E - UL0012 - NETWORK- UNKNOWN
ULF error
E - UL0013 IN BLOCK- FULL
ULF error
E - UL0014 - BAD - ULM - PARM
Bad parameter supplied to one of the ULM routines.
E - UL0015 - BAD - STREAM- MARK
ULM was handed an invalid 'memory stream mark'.
E - ULOIOI - TABLE- ID
Invalid hash table id found in ULH request block.
E - ULOI02 - TABLE- SIZE
Invalid hash table size specified.
E - ULOI03NOT
-EMPTY
Trying to close a hash table containing locked or fixed objects.
E - ULOI04 - FULL- TABLE
No more space in the hash table.

39-2

UL Class Messages

E - ULOIOS - FULL- CLASS
No more space in the specified class.
E _ ULOI06 _OBJECT _ID
Invalid object id found in ULH request block.
E - ULOI07 - ACCESS
Invalid mode of access to the object.
E - ULOI08- DUPLICATE
Duplicate object id.
E - ULOI09 - NFND
Requested object/class not found in the hash table.
E - ULOIOA - MEMBER
The object is already a member of a class.
E - ULOIOB NOT
-MEMBER
The object is not a member of any class.
E - ULOIOC - UNKNOWN
Unknown information code.
E ULOIOD TABLE MEM

Error in openning a memory stream for the hash table.
TCB
E - ULOIOE-MEM
Error in allocating memory space for the hash table.
E - ULOIOF- BUCKET- MEM
Error in allocating memory space for hash buckets.
E - ULOIIO- CHDR- MEM
Error in allocating memory space for class headers
E_ULOl11_0BJ_MEM
Error in allocating memory for a hash object
INIT
SEM
E - ULOl12Error in initializing a semaphore.
E - ULOl13- TABLE- SEM
Error in locking the hash table semaphore.

UL Class Messages

39-3

E- ULOl14- BUCKET- SEM
Error in locking a bucket semaphore.

E- ULOl15- CLASS - SEM
Error in locking a class semaphore.

E - ULOl16LRU
-SEM
Error in locking the LRU queue semaphore.

E_ ULOl17_OBJECT_SEM
Error in locking an object semaphore.

E- UL0120DUP
ALIAS
Duplicated alias.

E - UL0121NO
-ALIAS
The hash table does not support alias.

E - UL0122 - ALIAS - REDEFINED
Object alias cannot be redefined.

E - UL0123 - NAME- TOO - LONG
The name string is too long.

E- UL0201 - ULM- FAILED
Unable to obtain memory from ULM to build tree for display.

39-4

UL Class Messages

US Class Messages

E USOOOI
Number of users has exceeded limit.

E US0002
User does not have permission to use one of the flags given ULTRIX/SQL.

E US0003
User does not have permission to access this database.

E US0004
Could not access the database. Make sure images are installed correctly.

E US0005
Could not open the iirelation table.

E US0006
Could not open the iiattribute table.

E US0007
Could not read the config file.

E US0008
This version of ULTRIX/SQL is incompatible with the version of your database. In order
to use this, the version 1.0 of ULTRIX/SQL, run 'convt060' on your database.

E US0009
Bad parameter given to ULTRIX/SQL.

E USOOOA
Iiuser table does not exist.

E USOOOB
Cannot open iiuser table.

US Class Messages

40-1

E_USOOOC

E USOOOC
You are not a valid ULTRIX/SQL user.

E USOOOD
The -u flag specified a nonexistent user.

E USOOOE
Iidatabase table does not exist.

E USOOOF
Could not open or read the iidatabase table.

E USOOI0
Database does not exist.

E USOOll
Table iidbaccess does not exist.

E US0012
Cannot open or read iidbaccess table.

E US0013
Request for a lock failed.

E US0014
Database not available at this time.
The database may be marked inoperable. This can occur if CREATEDB failed or
CONVT060 is in progress.
An exclusive database lock may be held by another session.
The database may be open by an exclusive (lSOLE) DBMS server.
To run FAST COMMIT only one DBMS can service the database.

E US0015
Error initializing transaction system.

E US0016
Error writing to CONFIG file.

E US0017
Couldn't find an CONFIG file.

E US0018
Couldn't find CONFIG file.

40-2

US Class Messages

E US0019
The database may be inconsistent; please contact the ULTRIX/SQL system manager
E USOOIA
Could not find database default AREA in IILOCATIONS.
E USOOIB
Could not tind database checkpoint AREA in IILOCATIONS.
E USOOIC
Could not find database journal AREA in IILOCATIONS.
E USOOID
Fatal in looking up an AREA in IILOCATIONS.
E USOOIE
Could not find an AREA for LOCATIONNAMES in IIEXTEND catalog.
E USOOIF
Could not open or read the IIEXTEND catalog.
E US0020
Could not open or read the IILOCATIONS catalog.
E US0021
Fatal error in forming list of available LOCATIONNAMES.
E US0022
Either the flag format or one of the flags is incorrect, or the parameters are not in proper
order.
E US0023
You are not authorized to use one of the specified flags.
E US0024
Couldn't access DB directory.
E US0025
Couldn't access JNL directory.
E US0026
Database is inconsistent. please contact the ULTRIX/SQL system manager
E US0027
The are no more journal logs available. Please try later.

US Class Messages

40-3

E_US0028

E US0028
Couldn't open or write to the journal file.

E US0029
The global section containing the page cache is incompatible with this version of the
software.

E US002A
Couldn't acquire cache lock, either privilege or quota problem.

E US002B
Could not open the iidbdb database.

E US002C
The iidbdb database is inconsistent; please contact the ULTRIX/SQL system manager

E US002D
An error occurred while closing a database in preparation for opening another one.

E US002E
An error occurred in trying to get a lock while opening a database.

E US002F
Could not map global section containing the global cache.

E US0030
An error occurred while initializing DMF.

E US0031
An error occurred while cleaning up from an error while opening a database.

E US0032
An error occurred while finding the name of the database directory.

E US0033
An error occurred while initializing the database directory.

E US0034
An error occurred while resetting the database directory.

E US0035
An error occurred while creating the DMF buffer.

E US0036
An error occurred while reading and processing the config file during database
initialization.
40-4

US Class Messages

E US0037
An error occurred while initializing the descriptor cache.

E US0038
An error occurred while setting a lock on the config file.

E US0039
An error occurred while opening the config file.

E US003A
An error occurred while initializing the transaction system. Please contact the
ULTRIX/SQL system manager

E US003B
An error occurred while re-writing the CONFIG file.

E US003C
An error occurred while closing the CONFIG file.

E US003D
An error occurred while unlocking the CONFIG file.

E US003E
An error occurred while opening the iirelation table.
Please contact the ULTRIX/SQL system manager

E US003F
An error occurred while opening the CONFIG table.

E US0040
ULTRIX/SQL can only be invoked from Application Processor 00.

E US0041
The user code of dba in CONFIG header does not match that in iidbdb.

E US0046
The environment variable, 11_TIMEZONE, is undefined.

E US0047
Database name invalid.

E US0048
Database quota for this server has been exceeded.

US Class Messages

40-5

E US0049
Server contains invalid control information for this database.
Re-start the server to clear this problem.

E US0067
Remote node not configured to run ULTRIX/SQL/Net.

E US0068
Local node not configured to run ULTRIX/SQL/Net.

E US006D
Local node not licensed to run ULTRIX/SQL/Net.

E US006E
Remote node not licensed to run ULTRIX/SQL/Net.

E US0070
Local node not licensed to run the DBMS.

E US0071
Remote node not licensed to run the DBMS.
E US0072

The IIEXTEND entry for the database is missing.
This can be caused by one of two events.
The IIDBDB is corrupted. Run FINDDBS.
The database was not build properly.
Destroy it and then recreate it.

E US0073
The IIDBDB is unavailable at this time, please try again later when it has been unlocked.
Could not open the iidbdb database.

E- USOOC8 - 200
Bad parameter format '%Oc' in repeat query.

E- US07Dl - 2001
CREATE TABLE: number of column names and number of target list elements in the
subselect do not match.

E- US07D2- 2002
CREATE TABLE: Bad storage structure '%Oc'. The valid storage structure names are
[c]btree, [c]isam, [c]hash, [c]heap.

40·6

US Class Messages

E - US07D3 - 2003
CREATE TABLE: invalid option '%Oc'. Try NOT NULL WITH DEFAULT.
E - US07D4- 2004
CREATE TABLE: invalid option '%Oc'. Try NOT NULL NOT DEFAULT.
E - US07D5 - 2005
CREATE TABLE: '%Oc' is either an invalid option or the syntax of the WITH subclause
is invalid. STRUCTURE is the only valid keyword for this type of subclause.
E - US07D6- 2006
CREATE TABLE: Location specified twice: ' %Oc' conflicts with ' % 1c' .
E - US07D7 - 2007
CREATE TABLE: '%Oc' is either an invalid option or the syntax of the WITH subclause
is invalid. The valid keywords for this type of subclause are: [NO] DUPLICATES,
[NO]JOURNALING.
E - US07D8- 2008
CREATE TABLE: excessive table width on column '%Oc'.
E - US07D9 - 2009
'%Oc' is a system table.
E - US07DA- 2010
Duplicate object name ' %Oc' .
E - US07DB - 2011
CREATE TABLE: the number of columns must not exceed 127.
E - US07DC - 2012
CREATE TABLE: invalid column name '%Oc'.
E - US07DD - 2013
CREATE TABLE/VIEW: duplicate column name '%Oc'.
E - US07DE - 2014
CREATE TABLE: invalid column format '%Oc' on column '%lc'.
E - US07DF- 2015
CREATE TABLE: Too many options in the WITH clause.
E - US07EO- 2016
CREATE TABLE: Improper use of NULL in the target list; use conversion function to
specify data type of the null value.

US Class Messages

40-7

E - US07E1 - 2017
CREATE TABLE: Invalid FILLFACTOR of '%Od' specified. Must be in 1 - 100 range
(inclusive).

E- US07E2- 2018
CREATE TABLE: Invalid MINPAGES of '%Od' specified. Must be greater than O.

E - US07E3- 2019
CREATE TABLE: Invalid MAXPAGES of '%Od' specified. Must be greater than O.

E - US07E4- 2020
CREATE TABLE: Invalid NONLEAFFILL of '%Od' specified.
Must be in 1 - 100 range (inclusive).

E- US07E5 - 2021
CREATE TABLE: Invalid LEAFFILL/INDEXFILL of '%Od' specified.
Must be in 1 - 100 range (inclusive).

E - US07E6- 2022
CREATE TABLE: '%Oc' is either an invalid option or the syntax of the WITH subclause
is invalid. The valid keywords for this type of subclause are: KEY, LOCATION.

E - US07E7 - 2023
CREATE TABLE: Number of key columns must not be greater than the number of
columns in the table.

E - US07E8- 2024
CREATE TABLE: Key column '%Oc' is undefined.

E - US07E9- 2025
CREATE TABLE: Duplicate key column '%Oc'.

E - US07EA- 2026
CREATE TABLE: WITH option '%Oc' allowed only in the version of the CREATE
TABLE statement using a subselect.

E - US07EB - 2027
CREATE TABLE: Illegal MINPAGES value '%Od' in a CREATE TABLE command. The
value must be less than or equal to the MAXPAGES value.

E - US07EC - 2028
CREATE TABLE: The '%Oc' entry in the WITH clause is incompatible with the storage
structure.

40-8

US Class Messages

E - US07ED - 2029
CREATE TABLE: '%Oc' is either an invalid option or the syntax of the WITH subclause
is invalid. The valid keywords for this type of subclause are: FILLFACTOR,
MINPAGES, MAXPAGES, NONLEAFFILL, LEAFFILL, MAXINDEXFILL.

E- US07EE- 2030
RETRIEVE/CREATE TABLE: Storage structure type may not be quoted.

E - US07EF- 2031
%Oc: In the with clause, NODE and DATABASE clauses are optional, but only as a unit.

E- US07FO- 2032
%Oc: duplicate column name '%lc'.

E - US07Fl - 2033
REGISTER INDEX: Syntax error on '%Oc'. The correct syntax is:
REGISTER INDEX indexname ON tablename AS LINK [FROM source]

E - US07F2 - 2034
CREATE: '%Oc = %lc' is not allowed by the syntax of the WITH clause.

E - US07F3 - 2035
CREATE: '%Oc' is either an invalid option or the syntax of the WITH subclause is
invalid. Valid keywords for this type of subclause are TABLE, NODE, DBMS, and
DATABASE.

E - US07F4- 2036
REGISTER: Syntax error on '%Oc'. The correct syntax is:
REGISTER [TABLEIVIEW] objname [(col_name {, col_name})]
AS LINK [FROM source] [with_clause] REGISTER objname AS LINK
WITH REFRESH

E - US07F5 - 2037
REGISTER/CREATE LINK: '%Oc' is an index. Indices may not be registered in this
release.

E - US07F6- 2038
REGISTER %Oc: '%lc' is of type '%2c'. You must use 'REGISTER [%2c]'

E- US07F7 - 2039
REGISTER/CREATE LINK: You have to specify column names. Converting to lower
case produced duplicate column name '%Oc'.

E - US07F8- 2040
'REGISTER INDEX' in not supported in this release.

US Class Messages

40-9

E - US07F9 - 2041
Syntax error on '%Oc' in the KEY option of the WITH clause. Correct syntax is:
WITH ... KEY = (key_name L key_name})

E - US07FA- 2042
Syntax error on '%Oc' in the LOCATION option of the WITH clause. Correct syntax is:
WITH ... LOCATION = (Ioc_name {, 10cJlame})

E - US07FB - 2043
REGISTER ... WITH REFRESH: %Oc is a view.

E - US07FC - 2044
REGISTER ... WITH REFRESH: Schema of the LDB object has changed.

E - US0803 - 2051
CREATE VIEW: number of column names and number of target list elements in the
subselect do not match.

E - US0804 - 2052
CREATE VIEW: invalid column name '%Oc'.

E - US081B - 2075
DIRECT DISCONNECT: no parameters may be specified

E - US081C - 2076
Syntax error. Last symbol read was: '%Oc'.

E - US081D - 2077
Syntax error on '%Oc', 'CONNECT' was expected. The correct syntax is:
DIRECT CONNECT [with_clause]

E - US081E - 2078
'DIRECT DISCONNECT' may only be issued if connected to a LDBMS via 'DIRECT
CONNECT'

E - US081F - 2079
Syntax error on ' %Oc'. The correct syntax of WITH clause is:
WITH
[NODE = [\']node_name[\'],
DATABASE = [\']ldb_name[\']]
[,DBMS = [\']dbms_namel\']]

E - US0820- 2080
Syntax error on '%Oc'. The correct syntax of WITH clause is:

40-10

US Class Messages

WITH
[NODE = [\']node_name[\'], DATABASE = [\']ldb_name[\']]
[,DBMS = [\']dbms_name[\']]
WITH REFRESH

E - US0823 - 2083
A with_clause is not allowed with DIRECT DISCONNECT command

E - US0826- 2086
%Oc command is not allowed in non-distributed ULTRIX/SQL.

E - US0827 - 2087
Syntax error on ' %Oc'. The correct syntax of WITH clause is:
WITH
[NODE = [\']node_name[\'],
DATABASE = [\']ldb_name[\']]
[,DBMS = [\']dbms_name[\']]
[,TABLE =[\']table_name[\']]

E - US0829 - 2089
Syntax error on '%Oc', 'CONNECT' was expected. The correct syntax is:
DIRECT CONNECT
[WITH
[NODE = ["]node_name["],
DATABASE = ["]database_name["]]
[,DBMS = ["]dbms_name["]]]

E - US082A- 2090
Syntax error on ' %Oc'. The correct syntax of WITH clause is:
WITH
[NODE = ["]node_name["],
DATABASE = ["]ldb_name["]]
[,DBMS = ["]dbms_name["]]

E- US082B - 2091
Syntax error on ' %Oc'. The correct syntax of WITH clause is:
WITH
[NODE = ["]node_name["],
DATABASE = ["]ldb_name["]]
[,DBMS = ["]dbms_name["]
[,TABLE = ["]table_name["]]

E- US0834- 2100
line %Od, Table '% Ic' owned by '%2c' does not contain column '%3c'.

US Class Messages

40-11

E- US0835 - 2101
line %Od, Column '% lc' found in more than one FROM list table.

E - US0836- 2102
line %Od, Column '%lc' not found in any specified table.

E- US0837 - 2103
line %Od, FROM clause is mandatory when a column ('% lc') has been specified in the
target list.

E - US0838 - 2104
line %Od, 'select *' type of subselect requires a FROM clause.

E- US0839 - 2105
line %Od, Column '% lc' must not be specified in this context.

E - US083B - 2107
line %Od, You are not allowed to update '% lc' table.

E - US083C - 2108
line %Od, Result table '%lc' for APPEND does not exist or cannot be accessed by you.

E - US083D - 2109
line %Od, The range variable '%lc' has not been defined.

E - US083E- 2110
line %Od, The construct '$number = name' may not be used except when defining a repeat
query. This error is usually caused by an internal error in the pre-processor. Please report
this error to your vendor if you have not explicitly used this construct yourself.

E - US083F- 2111
line %Od, Too many columns in key of INDEX.

E- US0840- 2112
line %Od, Invalid column name 'tid'.

E- US0841 - 2113
line %Od, Too many entries in argument list to process in this statement.

E - US0842 - 2114
line %Od, Attempt to specify location more than once.

E - US0843 - 2115
line %Od, Too many locations specified.

40-12

US Class Messages

E - US0844- 2116
line %Od, Location '%lc' has already been specified.

E - US0845 - 2117
Table '%Oc' does not exist.

E- US0846- 2118
Invalid qualifier' %Oc'. '%Oc' must be declared in the FROM clause or equivalent. If used
in a target list, '%Oc' must be declared at the current scope.

E - US0847 - 2119
User '%Oc' does not own table '%lc'.

E- US0848- 2120
The table(s) that the view is dependent upon does not exist.

E - US0849 - 2121
line %Od, Column '% I c' was declared 'for update', but is not updateable because it is
based on a constant or a calculation.

E - US084B - 2123
line %Od, '.ALL' is not allowed in the target list of a REPLACE command.

E - US084C - 2124
line %Od, Update of BTREE index '% lc' not allowed.

E- US0852- 2130
line %Od, Maximum number of columns exceeded for query.

E - US0857 - 2135
line %Od, You cannot duplicate the name of an existing relation' % I c'.

E - US0858- 2136
line %Od, There is no such hour as '% ld', use a 24 hour clock system.

E- US0859 - 2137
line %Od, There is no such minute as '%ld', use a 24 hour clock system.

E- US085A- 2138
line %Od, There is no such time as 24:% ld, use a 24 hour clock system.

E - US085B - 2139
RETRIEVE: line %Od, '%lc' is either an invalid option or the syntax of the WITH
subclause is invalid.
STRUCTURE is the only valid keyword for this type of subclause.

US Class Messages

40-13

E - US085C - 2140
RETRIEVE: line %Od, '%lc' is either an invalid option or the syntax of the WITH
subclause is invalid. The valid keywords for this type of subclause are: FILLFACTOR,
MINPAGES, MAXPAGES, NONLEAFFILL, LEAFFILL, MAXINDEXFILL.

E- US085D - 2141
You must not specify a WITH clause on a RETRIEVE command unless it is a RETRIEVE
INTO.

E - US085E- 2142
RETRIEVE INTO: Improper use of NULL in the target list; use conversion function to
specify data type of the null value.

E- US085F- 2143
RETRIEVE INTO: Illegal MINPAGES value '%Od' in a RETRIEVE command. The
value must be less or equal to the MAXPAGES value.

E - US0860- 2144
RETRIEVE INTO: Bad storage structure '%Oc'. The valid storage structure names are
[c ]btree, [c ]isam, [c ]hash, [c ]heap.

E- US0861 - 2145
RETRIEVE INTO: Invalid FILLFACTOR of '%Od' specified. Must be in 1 - 100 range
(inclusive).

E- US0862- 2146
RETRIEVE INTO: Invalid MINPAGES of '%Od' specified. Must be greater than O.

E- US0863 - 2147
RETRIEVE INTO: Invalid MAXPAGES of '%Od' specified. Must be greater than O.

E- US0864 - 2148
RETRIEVE INTO: Invalid NONLEAFFILL of '%Od' specified. Must be in 1 - 100 range
(inclusive).

E - US0865 - 2149
RETRIEVE INTO: Invalid LEAFFILL/INDEXFILL of '%Od' specified. Must be in 1 100 range (inclusive).

E- US0866- 2150
RETRIEVE INTO: Unrecognized option '%Oc' in the WITH clause.

E- US0867 - 2151
RETRIEVE INTO: duplicate key '%Oc'.

40-14

US Class Messages

E- US0868- 2152
RETRIEVE INTO: The '%Oc' entry in the WITH clause is incompatible with the storage
structure.

E- US0869 - 2153
Repeat query is unknown to server. Please send the definition.

E - US086A- 2154
RETRIEVE: line %Od, '% I c' is either an invalid option or the syntax of the WITH
subclause is invalid. The valid keywords for this type of subclause are:
[NO]DUPLICATES, [NO]JOURNALING.

E - US086B - 2155
RETRIEVE: line %Od, '% Ic' is either an invalid option or the syntax of the WITH
subclause is invalid. Valid keywords for this type of subclause are: STRUCTURE, NODE,
DATABASE, DBMS, and TABLE.

E - US0871 - 2161
Sort column '%Oc' not found in target list.

E - US0872- 2162
Sort column '%Od' not found in target list.

E - US0873 - 2163
line %Od, Unrecognized sort order '%lc' in a RETRIEVE command. Please use one of
the following: ascending, a, descending, d.

E - US0879 - 2169
Invalid name specified for a savepoint.

E - US087A - 2170
Attempt to abort to a non-existent savepoint.

E- US087B- 2171
You cannot abort when you are not in a multi-query transaction.

E - US087C - 2172
You are already in a transaction, try a savepoint.

E - US087D - 2173
There is no multi-query transaction to end.

E- US087E- 2174
You cannot declare a savepoint if you are not in a multi-query transaction.

US Class Messages

40-15

E- US0880- 2176
You cannot modify autocommit during a transaction.
E- US0881 - 2177
No transaction is currently in progress.
E- US0882 - 2178
You cannot declare a savepoint when autocommit is on.
E- US0898- 2200
line %Od. If an update column list in cursor '%lc' is not specified, the FOR UPDATE
clause must not contain DIRECT or DEFERRED keywords.

E- US0899 - 2201
line %Od, Cursor '%lc' already open.

E- US089 A- 2202
line %Od, Column '%2c' in cursor '%lc' is not updateable because it is based on a
constant or a calculation.
E- US089B - 2203
line %Od, Cursor '%lc' is not updateable because the cursor definition contains none or
more than one range variable.

E- US089C - 2204
line %Od, Cursor '%lc' is not updateable because the cursor definition contains a 'sort by'
or 'unique' clause.

E- US089D - 2205
line %Od, Cursor' %1c' is not currently open.
E- US089E- 2206
line %Od, Column '%2c' does not exist in cursor '%lc'.

E- US089F- 2207
line %Od, Column '%2c' in cursor '%lc' is not updateable.
E- US08AO - 2208
line %Od, Cursor' %1c' was declared 'for update', but uniqueness was specified in the
retrieve statement.
E- US08Al - 2209
line %Od, Cursor '%lc' was declared with a 'retrieve into' statement. No result table is
allowed with cursors.

40-16

US Class Messages

E - US08A2- 2210
line %Od, Cursor' % I c' is already defined.

E - US08A3 - 2211
line %Od, Cursor '% I c' does not have delete pennission.

E- US08A4- 2212
line %Od, Range variables are not allowed in REPLACE CURSOR statements.

E - US08A5 - 2213
line %Od, Cursor' % I c' was declared 'for update', but it is not updateable because the
cursor definition contains an aggregate with a BY list.

E - US08A6 - 2214
line %Od, Cursor '%lc' was declared 'for update', but it is not updateable because the
cursor definition contains an aggregate function with a GROUP BY clause.

E- US08A7- 2215
Cursor has been declared for table '%Oc' not '% lc'.

E - US08A8- 2216
Repeat queries cannot use 'where current of' clause.

E - US08A9 - 2217
Cursor '%Oc' has not been opened for update.

E - US08AA- 2218
The parameter in the target list of the repeat query is not allowed in this context.

E - US08AB - 2219
line %Od, Cursor '%lc' is not update able because of implied request to remove duplicates.

E - US08AC - 2220
line %Od, Cursor '%lc' is not updateable because of implied UNION.

E - US08AD - 2221
line %Od, Cursor '%lc' is not updateable because the specified variable is a view, which
contains either DISTINCT or UNION in its definition.

E - US08AE - 2222
line %Od, Cursor '%lc' is not updateable because the specified variable is an index.

E - US08AF - 2223
line %Od, Cursor' % I c' is not update able because resulting query has an aggregate in its
target list.

US Class Messages

40-17

E- US08BO- 2224
line %Od, 'for update' clause in cursor '%lc' contains nonupdateable column '%2c'.

E - US08B 1- 2225
Updateable cursor '%Oc' defined on an nonupdateable view '%lc'.

E - US08B2- 2226
Ambiguous dynamically specified cursor name '%Oc' in a DELETE or UPDATE
statement.
Parameters:

%Oc - the cursor name

Explanation:

The dynamically specified cursor name is not unique among
currently open cursors. It may be unique within the original
source module but must also be unique within the current
transaction.

System Status:

The UPDATE/DELETE statement is ignored. The cursor is left
open.

Recommendation:

Modify the original DECLARE CURSOR statement to specify a
unique cursor name if a dynamic DELETE/UPDATE statement
will be issued. This restriction does not apply to static cursor
DELETE/UPDATE statements.

E- US08FC - 2300
line %Od, Argument(s) missing.

E- US08FD - 2301
line %Od, Expecting more arguments.

E - US08FE - 2302
line %Od, The dynamically defined statement '%lc' is a SELECT statement.

E - US08FF - 2303
line %Od, Invalid keyword '%lc'. Only NAMES option allowed.

E- US0900- 2304
line %Od, The dynamically defined statement '%lc' not found.

E- US0901 - 2305
line %Od, The dynamically defined statement '% lc' is not a SELECT statement.

E- US0902 - 2306
line %Od, Parameter markers not allowed in this statement.

E - US0903 - 2307
line %Od, Parameter markers not allowed as both operands of a single operator.

40-18

US Class Messages

E - US0904- 2308
line %Od, Parameter markers not allowed as both the first and second operands used with
BETWEEN or IN.

E - US0905 - 2309
line %Od, Parameter markers not allowed in the target of a SELECT statement.

E - US0906 - 2310
Invalid attempt to execute Dynamic SQL statement '%Oc'. The statement refers to cursor
'%lc' that is already closed.
Parameters:

%Oc - the statement name % 1c - the cursor name

Explanation:

The statement was prepared from a cursor statement while the
specified cursor was open. By the time the statement was
executed the cursor was already closed.

System Status:

The EXECUTE statement is ignored.

Recommendation:

Only issue this statement while the cursor is open. This
statement may not apply to the same named cursor that is opened
twice. You must reprepare the statement to associate it with the
correct cursor.

E - US0915 - 2325
The GRANT statement is not allowed in distributed ULTRIX/SQL.

E- US0916- 2326
GRANT: only the DBA can use the GRANT statement.

E - US0917 - 2327
GRANT: Table ' %Oc' is not owned by you.

E - US0918 - 2328
GRANT: Object ('%Oc') must not be an index.

E - US0919 - 2329
GRANT: Only EXECUTE privilege may be granted on a DB procedure.

E - US091A - 2330
GRANT: EXECUTE privilege may not be granted on a table.

E - US091B - 2331
line %Od, Warning: creating non GRANT compatible permit on table '%lc'.

E - US092E- 2350
EXECUTE IMMEDIATE: a SELECT statement cannot be a target of this command.

US Class Messages

40-19

E - US0960- 2400
Procedure '%Oc' already exists.

E- US0961 - 2401
Parameter/local variable '%Oc' already exists.

E - US0962 - 2402
Invalid column format '%Oc'.

E - US0963 - 2403
Parameter/local variable '%Oc' has not been declared.

E- US0964- 2404
You are not the owner of '%Oc' procedure.

E - US0965 - 2405
Procedure '%Oc' not found.

E- US0966- 2406
Label '%Oc' already declared.

E- US0967 - 2407
Label '%Oc' not declared or out of scope.

E - US0968 - 2408
MESSAGE statement requires first parameter to be of INTEGER type.

E- US0969 - 2409
MESSAGE statement requires second parameter to be of character type.

E- US096A - 2410
MESSAGE statement can only be followed by a parameter of integer or character type.

E - US096B - 2411
This statement has not been implemented yet.

E - US096C - 2412
line %Od, The outermost target list of the first subs elect in a SELECT statement in a
database procedure must retrieve data into local variables/parameters. Target list element
'% 1c' violates this rule.

E- US096D - 2413
Local variable/parameter '%Oc' has not been declared or is out of scope.

E - US096E - 2414
Local variable/parameter': %Oc' can only be used within a database procedure.
40-20

US Class Messages

E_US097B_2427

E - US096F- 2415
Line %Od: This type of predicate is not allowed in a condition of a database procedure
control statement.

E - US0970- 2416
The assignment statement is not supported yet. Use SELECT statement instead.

E - US0971 - 2417
Target list expression of type '%Oc' cannot be coerced into local variable/parameter of
type '%lc'.

E - US0972- 2418
A target list with the INTO clause may be used only in the outermost level of a SELECT
statement.

E- US0973- 2419
A SELECT statement with the INTO clause in the target list must not be used outside of a
database procedure context.

E- US0974- 2420
Nesting of BEGIN END blocks is not supported yet.

E - US0975 - 2421
Return value must be of non-nullable data type.

E - US0976 - 2422
Message statement parameters must be of non-nullable data type.

E - US0977 - 2423
Number of arguments passed to a procedure must not exceed %Od.

E- US0978- 2424
Return value must be of INTEGER type.

E - US0979 - 2425
Empty statement blocks are not allowed.

E - US097 A- 2426
'ENDLOOP [label]' statement is only allowed in a WHILE.

E- US097B - 2427
INTO clause: number of elements in the parameter/local variable list doesn't match the
number of elements in the target list.

US Class Messages

40-21

E- US097C - 2428
INTO clause must appear only once in the SELECT statement in the outermost target list
of the first subselect.

E - US097D- 2429
line %Od, INTO clause must not be mixed with '[:]loc_var_name = expression' way of
assigning values to local variables.

E - US097E - 2430
line %Od, The outermost target lists of all subs elects other than the first one in a SELECT
with UNION statement in a database procedure must not retrieve data into local
variables/parameters. Target list element '%lc' violates this rule.

E- US097F- 2431
line %Od, Local variables/parameters can appear only in the SELECT statement in the
outermost target list of the first subselect.

E- US0980 - 2432
'%Oc' is not a valid database procedure name. Names starting with 'ii' are reserved for
system use.

E- US0981 - 2433
'%Oc' is not a valid parameter/local variable name. Name must not start with 'ii'.

E - US0982 - 2434
line %Od, IIROWCOUNT and IIERRORNUMBER built-in variables are read-only.

E- US0983 - 2435
SELECT..UNION .. SELECT is not supported in this release of STAR.

E_ US0984 _2436_ RSER_ TYPE
RAISE ERROR parameters must be of type integer and character respectively.
Parameters:

None

Explanation:

The parameters to the RAISE ERROR procedure statement, must
be a non-null able integer error number, optionally followed by a
non-null able error message string.

System Status:

Program continues and current statement is aborted.

Recommendation:

Redeclare your RAISE ERROR parameters as the correct data
types and with the NOT NULL attribute.

40-22

US Class Messages

E_US09C8_2504

E- US0985 - 2437- RSER- NUL
RAISE ERROR statement parameters must be of a non-null able data type.
Parameters:

None

Explanation:

The parameters to the RAISE ERROR procedure statement, must
be a non-null able integer error number, optionally followed by a
non-nullable error message string.

System Status:

Program continues and current statement is aborted.

Recommendation:

Redeclare your RAISE ERROR parameters with the NOT NULL
attribute.

E- US09C4 - 2500
Syntax error on line %Od. Last symbol read was: '% Ic'.

E- US09C5 - 2501
line %Od, Syntax error on '%lc'. The correct syntax is:
SELECT [ALLIDISTINCT] target_list
FROM table(s)
[WHERE search_cond]
[GROUP BY col(s)]
[HAVING search_cond]
[UNION subselect]
[ORDER BY col(s)]

E- US09C6- 2502
line %Od, Syntax error on '% Ic'. The correct syntax is:
CREATE TABLE tablename
[(columnname {, ... })]
AS subselect
[wi th_ clause]

E- US09C7 - 2503
line %Od, Syntax error on '% Ic'. The correct syntax is:
INSERT INTO tablename [(column {, ... })]
VALUES (select_expr {, ... })
INSERT INTO tablename [(column {, ... })] subselect

E- US09C8- 2504
line %Od, Syntax error on '% lc'. The correct syntax is:
UPDATE tablename
SET column = select_exprlNULL {, ... }
[WHERE search_condition]

US Class Messages

40-23

E - US09C9 - 2505
line %Od, Syntax error on '%lc'. The correct syntax is:
DELETE FROM tablename [WHERE search_condition]

E - US09CA - 2506
line %Od, Syntax error on '%lc'. The correct syntax is:
COpy TABLE tablename (columnname = foonat [null_clause] {, ... })
INTOIFROM 'filename' IPROGRAM
[with_clause]

E- US09CB - 2507
line %Od, Syntax error on '% Ic'. The correct syntax is:
CREATE TABLE tablename
(columnname foonat [null_default_clause] L ... })
[with_clause]
CREATE TABLE tablename [(colname_list)]
AS subselect
[with_clause]

E - US09CC - 2508
line %Od, Syntax error on '% lc'. The correct syntax is:
DROP [TABLEIVIEWIINDEXILINK] object_name {, object_name}

E - US09CE - 2510
line %Od, Syntax error on '%lc'. The correct syntax is:
CREATE [UNIQUE] INDEX indcxnamc
ON table (column [ASCIDESC] {, ... })
[with_clause]

E - US09CF- 2511
line %Od, Syntax error on ' % I c' .
MODIFY table TO storage-structure [UNIQUE]
[ON column [ASCIDESC] {, ... }]
[with_clause]

E - US09D2 - 2514
line %Od, Syntax error on '%Ic'.
SAVE tablename UNTIL month day year

E - US09D3 - 2515
line %Od, Syntax error on '%lc'.
OPEN CURSORID CURSOR FOR fullselect
[FOR [DIRECT I DEFERRED] UPDATE OF column {, ... }]
[FOR READONLY]
40-24

US Class Messages

E - US09D5 - 2517
line %Od, Syntax error on '%lc'.
CREATE VIEW viewname [ (column {, ... }) ]
AS subselect [WITH CHECK OPTION]

E - US09D6- 2518
line %Od, Syntax error on '%lc'.
ABORT [TO savepoint_name]

E - US09D7 - 2519
line %Od, Syntax error on ' % 1c' .
CREATE PERMIT SELECTIUPDATEIDELETEIINSERT
ONIOFITO table [ (column(s)) ]
TO user_name [AT term] [FROM time TO time]
[ON day TO day] [WHERE search_cond]
CREATE PERMIT ALL ...

E - US09D8- 2520
line %Od, Syntax error on '%lc'.
CREATE INTEGRITY ON tablename IS search_condition

E - US09D9 - 2521
line %Od, Syntax error on '%lc'.
CLOSE cursor_name

E - US09DA - 2522
line %Od, Syntax error on '%lc'.
RELOCATE tablename TO locationname

E - US09DB - 2523
line %Od, Syntax error on '%lc'.
DEFINE QUERY queryname IS deletelselectlupdate
DEFINE QUERY open_cursor

E - US09DC - 2524
line %Od, Syntax error on '%lc'.
EXECUTE stmnt_name USING const {, ... }

E - US09DE - 2526
line %Od Syntax error on '% lc'.
BEGIN TRANSACTION

US Class Messages

40-25

E - US09DF- 2527
line %Od, Syntax error on '% Ic'.
END TRANSACTION

E - US09EO- 2528
line %Od, Syntax error on ' % I c' .
SAVEPOINT savepoint_name

E - US09El - 2529
line %Od, Syntax error on '%Ic'.
ABORT [TO savepoint_name]

E - US09E2- 2530
line %Od, Syntax error on '%Ic'.
DROP INTEGRITY ON table integer {, ... }
DROP INTEGRITY ON table ALL

E - US09E3 - 2531
line %Od, Syntax error on '%Ic'.
DROP PERMIT ON table integer {, ... }
DROP PERMIT ON table ALL

E - US09E6- 2534
line %Od, Syntax error on ' % I c' .
EXECUTE stmnt_name USING const {, .. , }

E - US09EC - 2540
line %Od, Syntax error on '%Ic'.
UPDATE table
SET column = select_exprlNULL {, column = select_expr}
WHERE CURRENT OF cursor_name

E US09ED 2541
line %Od, Syntax error on ' % 1c' .
FETCH CURSOR cursor_name

E US09F3 2547
line %Od, Syntax error on '% Ic'.
SET CPUFACTOR integer

40-26

US Class Messages

E - US09F4- 2548
line %Od, Syntax error on '% lc'.
SET DATE_FORMAT "us" I "multinational"
I "iso" I "finland" I "sweden" I "german"
E - US09F6- 2550
line %Od, Syntax error on '%lc'.
SET DECIMAL "." I","
E - US09F8- 2552
line %Od, Syntax error on '%lc'.
SET JOINOP [NO]TIMEOUT [milliseconds]
E - US09F9 - 2553
line %Od, Syntax error on '%lc'.
SET [NO]JOURNALING [ON tablename]
E - US09FA - 2554
line %Od, Syntax error on '% lc'.
SET MONEY_FORMAT "TIL:string"
E - US09FB - 2555
line %Od, Syntax error on ' % I c' .
SET MONEY_PREC integer
E - US09FE - 2558
line %Od, Syntax error on '%lc'.
SET RESULT_STRUCTURE
"heap I cheap I heapsort I cheapsort I hash
I chash I isam I cisam I btree I cbtree"
E - USOA01 - 2561
line %Od, Syntax error on '%lc'.
SET [NO]STATISTICS
E - USOA02 - 2562
line %Od, Syntax error on '%lc'. The correct syntax is:
SET LOCKMODE SESSIONION table
WHERE [LEVEL=level_option]
[,READLOCK=readlock_option]
[,MAXLOCKS=maxlock_option]
[,TIMEOUT=timeout_option]

US Class Messages

40-27

E - USOA03 - 2563
line %Od, Syntax error on '% 1e' .
SET [NO]TRACE POINT DMnnnn [integer {, integer} ]
E USOA04 2564

line %Od, Syntax error on '% Ie' .
SET [NO]TRACE POINT PSnnnn [integer {, integer}]
E - USOA05 - 2565
line %Od, Syntax error on '%Ie'.
SET [NO]TRACE POINT SCnnnn [integer {, integer}]
E - USOA06- 2566
line %Od, Syntax error on '% 1e' .
SET [NO]TRACE POINT RDnnnn [integer {, integer}]
E USOA07 2567

line %Od, Syntax error on '%Ie'.
SET [NO]TRACE POINT QEnnnn [integer {, integer} ]
E - USOA08 - 2568
line %Od, Syntax error on ' % 1e' .
SET [NO]TRACE POINT OPnnnn [integer {, integer}]
E - USOA09 - 2569
line %Od, Syntax error on '% Ie'.
SET [NO]TRACE POINT QSnnnn [integer {, integer} ]
E - USOAOA - 2570
line %Od, Syntax error on '%Ie'.
SET [NO]TRACE POINT ADnnnn [integer {, integer}]
E - USOAOB - 2571
line %Od, Syntax error on '% Ie'.
SET [NO]TRACE ...
E - USOAOD - 2573
line %Od, Syntax error on ' % 1e' .
SET [NO]QEP

40-28

US Class Messages

E - USOAOE - 2574
line %Od, Syntax error on '% Ic'.
COMMIT [WORK]
E - USOAOF- 2575
line %Od, Syntax error on '% Ic'.
DESCRIBE stmnt_name [USING NAMES]
E - USOAI0 - 2576
line %Od, Syntax error on '%Ic'.
PREPARE stmnt_name [INTO name] FROM statement_text
E - USOAll - 2577
line %Od, Syntax error on '%Ic'.
PREPARE stmnt_name [INTO name] FROM statement_text
E USOA12 2578

line %Od, Syntax error on '%Ic'.
ROLLBACK [WORK] [TO savepoint]
E - USOA13 - 2579
line %Od, Syntax error on '%Ic'.
SET AUTO COMMIT ONIOFF
E - USOA14 - 2580
line %Od, Syntax error on '% Ic'.
ROLLBACK [WORK] [TO savepoint]
E USOA15 2581

line %Od, Syntax error on ' % I c' .
This SET statement is not supported.
E - USOA18- 2584
line %Od, Syntax error on '%Ic'.
GRANT ALLlprivilege(s) ON [obj_type] object(s)
TO {PUBLICI [grantee_type] grantee(s)}
privilege: SELECTIINSERTIDELETEIUPDATE[(col(s»]IEXECUTE.
E - USOA19 - 2585
line %Od, Syntax error on '% Ic'.
SET [NO]JOURNALING

US Class Messages

40-29

E - USOAIB - 2587
line %Od, Syntax error on '% Ic'. The correct syntax is:
[CREATE] PROCEDURE procedure[(panns)]
ASI=

[DECLARE local-variables]
BEGIN
DML/control statements
END
E - USOAIC - 2588
line %Od, Syntax error on '% Ic'. The correct syntax is:
DROP PROCEDURE procedure.
E - USOAID - 2589
line %Od, Syntax error on '% Ie'. The correct syntax is:
EXECUTE PROCEDURE procedure.
E - USOAIE - 2590
line %Od, Syntax error on '% Ie'. The correct syntax is:
IF [(] condition [)] THEN statement-list
{ELSEIF [(] condition D] THEN statement-list}
[ELSE statement-list]
ENDIF
E - USOAIF - 2591
line %Od, Syntax error on '%Ic'. The correct syntax is:
RETURN

[return-status].

E - USOA20- 2592
line %Od, Syntax error on '%Ic'. The correct syntax is:
MESSAGE message-number
I message-text
I message-number message-text
E - USOA21 - 2593
line %Od, Syntax error on '% Ie'. The correct syntax is:
DECLARE var_name {, var_name} [=] var_type;
{var_name {, var_name} [=] var_type;}
E - USOA22 - 2594
line %Od, Syntax error on '% Ic'. The correct syntax is:
[label:] WHILE [(] condition [)] DO
stement-list

40-30

US Class Messages

NDWHILE
Use of ENDLOOP [label] is allowed.
E- USOA23 - 2595

line %Od, Syntax error on '% lc'. The correct syntax is:
[:] parm/local var [:] = expression
E- USOA24- 2596

line %Od, Syntax error on '%lc'. The correct syntax is:
DIRECT CONNECT
[WITH
[NODE = [\']node_name[\'],
DATABASE = [\']database_name[\']]
[,DBMS = [\']ingres I db2 I ds I ims I dg ... [\']]]
E- USOA25 - 2597

line %Od, Syntax error on ' % 1c'. The correct syntax is:
DIRECT DISCONNECT
E- USOA27 - 2599

line %Od, Syntax error on '%lc'. The correct syntax is:
DIRECT EXECUTE IMMEDIATE \' query _text\'
[WITH
[NODE = [\']node_name[\'],
DATABASE = [\']ldb_name[\']]
[,DBMS = [\']dbms_name[\']]]
E USOA28 2600

Syntax error on line %Od. Last symbol read was: % I c.
E- USOA29 - 2601

line %Od, Syntax error on '%lc'.
RETRIEVE [[INTO] tablename] (target_list)
WHERE qual] [SORT [BY]
columnnamel [:sortorder] {, columnname2 [:sortorder]} ]
RETRIEVE UNIQUE (target_list) [WHERE qual] [SORT [BY]
columnnamel [:sortorder] {, columnname2 [:sortorder]} ]
E- USOA2A - 2602

line %Od, Syntax error on '% lc'.
RETRIEVE [[INTO] tablename] (target_list)
[WHERE qual] [SORT [BY]
columnnamel [:sortorder] {, columnname2 [:sortorder]} ]
RETRIEVE UNIQUE (target_list) [WHERE qual] [SORT [BY]
columnnamel [:sortorder] {, columnname2 [:sortorder]} ]
US Class Messages

40-31

E USOA2B 2603

line %Od, Syntax error on '% Ic'.
APPEND [TO] tablename (target_list) [WHERE qual]
E USOA2C 2604

line %Od, Syntax error on '%Ic'.
REPLACE row_variable (target_list) [WHERE qual]
E - USOA2D - 2605
line %Od, Syntax error on '% Ic'.
DELETE row_variable [WHERE qual]
E - USOA2E - 2606
line %Od, Syntax error on ' % I c' .
COpy tablename (columnname = format [null_clause] {, ... })
INTOIFROM "filename"IPROGRAM
[with_clause]
E - USOA2F - 2607
line %Od, Syntax error on '% Ic'.
CREATE tablename
(columnnamel = formatL columnnamc2 = format})
[with clause]
E - USOA30- 2608
line %Od, Syntax error on '% Ic'.
DESTROY [LINK] object_name {, objeccname}
E - USOA31 - 2609
line %Od, Syntax error on '%Ic'.
HELP
HELP tablename {,tablename}
HELP ALL
E - USOA32 - 2610
line %Od, Syntax error on '%Ic'.
INDEX ON tablename IS indexname (column I {, column2})
E - USOA33 - 2611
line %Od, Syntax error on '%Ic'.
MODIFY tablename TO storage-structure
[ON keyl [: sortorder] [{, key2 [:sortorder]}]]
[with_clause]
40-32

US Class Messages

E - USOA34 - 2612
line %Od, Syntax error on '%Ie'.
PRINT tablename {, tablename}
E - USOA35 - 2613
line %Od, Syntax error on '% Ie' .
RANGE OF variable IS tablename
E - USOA36 - 2614
line %Od, Syntax error on '% Ie'.
SAVE tablename UNTIL month day year
E - USOA37 - 2615
line %Od, Syntax error on '% Ie'.
PEN CURSOR CURSORID
statement [FOR [DIRECT I DEFERRED]
UPDATE [OF ( list)]] [FOR READONLY]
E - USOA38 - 2616
line %Od, Syntax error on '% Ie'.
RETRIEVE [[INTO] tablename] (target_list)
WHERE qual] [SORT [BY]
eolumnnamel [:sortorder] {, eolumnname2 [:sortorder]} ]
RETRIEVE UNIQUE (target_list) [WHERE qual] [SORT [BY]
eolumnnamel [:sortorder] {, eolumnname2 [:sortorder]} ]
E - USOA39 - 2617
line %Od, Syntax error on '% Ie'.
DEFINE VIEW name (target list) [WHERE qual]
E - USOA3A - 2618
line %Od, Syntax error on '% Ie'.
ABORT TO savepoint_name
E - USOA3B - 2619
line %Od, Syntax error on '% Ie' .
DEFINE PERMIT oplist ONIOFITO var [(eolumnlist)]
TO name [AT term] [FROM time TO time]
[ON day TO day] [WHERE qual]
E - USOA3C - 2620
line %Od, Syntax error on ' % Ie' .
DEFINE INTEGRITY ON var IS qual
US Class Messages

40-33

E USOA3D 2621

line %Od, Syntax error on '% I c'. The correct syntax is:
E USOA3E 2622

line %Od, Syntax error on '%Ic'.
RELOCATE tablename TO locationname
E - USOA3F- 2623
line %Od, Syntax error on '%lc'. The correct syntax is:
E - USOA40 - 2624
line %Od, Syntax error on '% lc'.
EXECUTE query_name [( parameter, ... )]
E - USOA41 - 2625
line %Od, Syntax error on '% Ic'. The correct syntax is:
E - USOA42 - 2626
line %Od Syntax error on '% I c' .
BEGIN TRANSACTION
E - USOA43 - 2627
line %Od, Syntax error on '%lc'.
END TRANSACTION
E - USOA44 - 2628
line %Od, Syntax error on '% lc'.
SAVEPOINT savepoint_name
E - USOA45 - 2629
line %Od, Syntax error on '%lc'.
ABORT
E - USOA46- 2630
line %Od, Syntax error on '% lc'.
DESTROY INTEGRITY tablename integer {, integer}
DESTROY INTEGRITY tablename ALL
E - USOA47 - 2631
line %Od, Syntax error on '% lc'.
DESTROY PERMIT tablename integer {,integer}
DESTROY PERMIT tablename ALL

40-34

US Class Messages

E - USOA48- 2632
line %Od, Syntax error on '% Ic'. The correct syntax is:
E - USOA49 - 2633
line %Od, Syntax error on '%Ic'. The correct syntax is:
E - USOA4A- 2634
line %Od, Syntax error on '%Ic'.
EXECUTE CURSOR CURSORID [( parameter, ... )]
E - USOA4B - 2635
line %Od, Syntax error on '% Ic'.
HELP INTEGRITY tablename[, tablename]
E - USOA4C - 2636
line %Od, Syntax error on '% lc'.
HELP PERMIT tablename[, tablename]
E - USOA4D - 2637
line %Od, Syntax error on '%Ic'.
HELP VIEW tablename[, tablename]
E - USOA4E - 2638
line %Od, Syntax error on ' % I c '. The correct syntax is:
E - USOA4F- 2639
line %Od, Syntax error on '%Ic'. The correct syntax is:
E - USOA50 - 2640
line %Od, Syntax error on '%lc'.
REPLACE CURSOR CURSORID (target list)
E - USOA51 - 2641
line %Od, Syntax error on '%Ic'.
RETRIEVE CURSOR CURSORID
E - USOA52- 2642
line %Od, Syntax error on ' % I c ' .
SET J_FREESZ I integer

US Class Messages

40-35

E USOA53 2643

line %Od, Syntax error on '%lc'.
SET J_FREESZ2 integer
E- USOA54- 2644

line %Od, Syntax error on ' % 1c' .
SET J_FREESZ3 integer
E- USOA55 - 2645

line %Od, Syntax error on '%lc'.
SET J _FREESZ4 integer
E- USOA56- 2646

line %Od, Syntax error on '%lc'.
SET AGGREGATE [NO]PROJECT
E- USOA57 - 2647

line %Od, Syntax error on '%lc'.
SET CPUFACTOR integer
E USOA58 2648

line %Od, Syntax error on '%lc'.
SET DATE_FORMAT "us" I "multinational"
I "iso" I finland " I "sweden" I "german"
II

E- USOA59 - 2649

line %Od, Syntax error on ' % 1c' .
SET [NO]DEADLOCK
E USOA5A 2650

line %Od, Syntax error on '%lc'.
SET DECIMAL "." I","
E- USOA5B - 2651

line %Od, Syntax error on '%lc'.
SET [NO]EMBEDDED
E- USOA5C - 2652

line %Od, Syntax error on '%lc'.
SET [NO]JOINOP

40-36

US Class Messages

E - USOA5D - 2653
line %Od, Syntax error on '% Ic'.
SET [NO]JOURNALING [ON tablename]
E - USOA5E - 2654
line %Od, Syntax error on '%Ic'.
SET MONEY_FORMAT "TIL:string"
E - USOA5F- 2655
line %Od, Syntax error on '% Ic'. The correct syntax is:
SET MONEY_PREC integer
E - USOA60- 2656
line %Od, Syntax error on '%lc'.
SET QBUFSIZE integer
E - USOA61 - 2657
line %Od, Syntax error on '%lc'.
SET QUERY_SIZE integer
E USOA62 2658

line %Od, Syntax error on '%lc'.
SET RET _INTO
:"heap I cheap I heapsort I cheapsort I hash
I chash I isam I cisam I btree I cbtree"
E - USOA63 - 2659
line %Od, Syntax error on '%lc'.
SET SORTBUFSIZE integer
E - USOA64- 2660
line %Od, Syntax error on ' % 1c' .
SET SQL
E - USOA65 - 2661
line %Od, Syntax error on '%lc'.
SET STATISTICS "tablename"
E USOA66 2662

line %Od, Syntax error on '%lc'. The correct syntax is:
SET LOCKMODE SESSIONION table
WHERE [LEVEL=PAGEITABLEISESSIONISYSTEM]

US Class Messages

40-37

[,READLOCK=NOLOCKISHAREDIEXCLUSIVEISESSIONISYSTEM]
[,MAXLOCKSITIMEOUT=intISESSIONISYSTEM]
E - USOA67 - 2663
line %Od, Syntax error on '%Ic'.
SET [NO]TRACE POINT DMnnnn [integer [, integer]]
E - USOA68- 2664
line %Od, Syntax error on '% Ic'.
SET [NO]TRACE POINT PSnnnn [integer [, integer]]
E- USOA69 - 2665
line %Od, Syntax error on '% Ic'.
SET [NO]TRACE POINT SCnnnn [integer [, integer]]
E - USOA6A - 2666
line %Od, Syntax error on '% Ic'.
SET [NO]TRACE POINT RDnnnn [integer [, integer]]
E - USOA6B - 2667
line %Od, Syntax error on '% Ic'.
SET [NO]TRACE POINT QEnnnn [integer [, integer]]
E - USOA6C - 2668
line %Od, Syntax error on '%Ic'.
SET [NO]TRACE POINT OPnnnn [integer [, integer]]
E - USOA6D - 2669
line %Od, Syntax error on '% Ic'.
SET [NO]TRACE POINT QSnnnn [integer [, integer]]
E - USOA6E - 2670
line %Od, Syntax error on '%Ic'.
SET [NO]TRACE POINT ADnnnn [integer [, integer]]
E - USOA6F- 2671
line %Od, Syntax error on '% Ic'.
SET [NO]TRACE ...
E - USOA79 - 2681
line %Od, Syntax error on '%Ic'.
This SET statement is not supported.
40-38

US Class Messages

E - USOA 7 A- 2682
line %Od, Syntax error on '% Ic'. The correct syntax is:
SET JOINOP [NO]TIMEOUT [milliseconds]
E - USOA 7B - 2683
line %Od, Syntax error on '% Ic'. The correct syntax is:
DEFINE LOCATION location_name WITH TYPE= DATA,
AREA = area_name
II

E - USOA 7D - 2685
line %Od, Syntax error on '% Ic'. The correct syntax is:
SET [NO]JOURNALING
E - USOA88 - 2696
line %Od, Syntax error on '% Ic'. The correct syntax is:
DIRECT CONNECT
[WITH
[NODE = ["]node_name["],
DATABASE = ["]database_name["]]
[,DBMS = ["]ingres I db2 I ds I ims I dg ... ["]]]
E - USOA89 - 2697
line %Od, Syntax error on '% Ic'. The correct syntax is:
DIRECT DISCONNECT
E - USOA8B - 2699
line %Od, Syntax error on '% Ic'. The correct syntax is:
DIRECT EXECUTE IMMEDIATE "query_text"
[WITH
[NODE = ["]node_name["],
DATABASE = ["]database_name["]]
[,DBMS = [tt]ingres I db2 I ds I ims I dg ... ["]]]
E - USOA8C - 2700
line %Od, Non-terminated string.
E - USOA8D - 2701
line %Od, String too long.
E - USOA8E - 2702
line %Od, Invalid operator '%Ic'.
E - USOA8F- 2703
line %Od, Name too long: '%Ic'.
US Class Messages

40-39

E USOA90 2704

Attempt to allocate symbol table space failed.
E - USOA91 - 2705
line %Od, Non-tenninated comment.
E - USOA93 - 2707
line %Od, Bad floating constant: '%lc'.
E - USOA94- 2708
line %Od, Unexpected character '%lc'.
E - USOA95 - 2709
line %Od, Bad value in hex constant: '% lc'.
E - USOA96- 2710
line %Od, Illegal character in string constant.
E - USOA97 - 2711
line %Od, Symbol stack overflow. Reduce target list complexity.
E - USOA98- 2712
line %Od, Illegal pattern matching notation.
E - USOA99 - 2713
line %Od, String constant '% lc' specified for the ESCAPE clause must be a single
character.
E - USOA9C - 2716
line %Od, Illegal binary value in query text.
E - USOA9D - 2717
line %Od, Illegal character in query.
E - USOA9E - 2718
line %Od, Illegal location type '%lc'. Use DATA.
E - USOA9F- 2719
line %Od, Illegal area name '%lc'.
E USOAAO 2720

line %Od, Syntax error on '% lc'. Make sure that the specified column name is not a
keyword and is a valid identifier.

40-40

US Class Messages

E - USOAA1 - 2721
line %Od, Syntax error on '%lc'. Make sure that the specified table location or table name
is not a keyword and is a valid identifier.
E - USOAA2- 2722
line %Od, Syntax error on '% I c' . An integer constant expected.
E - USOAA3- 2723
line %Od, Syntax error on '% I c' . A string constant expected.
E - USOAA4- 2724
line %Od, Syntax error on '% lc'. Make sure that the specified table name is not a
keyword and is a valid identifier.
E - USOAA5 - 2725
line %Od, Syntax error on '% lc'. Make sure that the specified index location or index
name is not a keyword and is a valid identifier.
E - USOABE- 2750
DROP TABLE: object '%Oc' is not a base table.
E - USOABF- 2751
DROP VIEW: object' %Oc' is not a view.
E - USOACO- 2752
DROP INDEX: object '%Oc' is not an index.
E - USOAC1 - 2753
%Oc: '%lc' does not exist or is not owned by you.
E - USOAC2- 2754
DROP: Too many objects specified.
E - USOAC3- 2755
DROP/DESTROY %Oc: STAR object '%lc' was created via CREATE %2c. Use DROP
[%2c] or DESTROY.
E - USOAC4- 2756
DROP/DESTROY %Oc: STAR object '%lc' was used to REGISTER an LDB object of
type '%2c'. Use DROP [%2c] or DESTROY.
E - USOAC5 - 2757
REMOVE %Oc: STAR object '%lc' corresponds to an LDB object of type '%2c'.
Use REMOVE [%2c].

US Class Messages

40-41

E USOAC6 2758

DROP LINK/REMOVE: STAR object '%Oc' was created using CREATE VIEW. Use
DROP [VIEW].
E - USOAC8- 2760
SET RESULT _STR UCTURE is not allowed in distributed ULTRIX/SQL.
E - USOAC9- 2761
SET: invalid storage structure '%Oc'.
E - USOACA- 2762
SET [NO]JOURNALING is not allowed on catalogs. '%Oc' is a catalog.
E - USOACB - 2763
REMOVE: syntax error on '%Oc'. The correct syntax is:
REMOVE [TABLEIVIEW] object_name {, object_name}
E - USOACC- 2764
%Oc: '% 1c' is not owned by %2c.
E - USOACD- 2765
You may not %Oc '%lc' owned by %2c.
E - USOAD6- 2774
INSERT: Duplicate column '%Oc' specified.
E - USOAD7 - 2775
INSERT: number of target columns must equal the number of specified values.
E - USOAD8- 2776
INSERT: number of target columns must equal the number of target list elements in the
specified subselect.
E - USOAD9 - 2777
INSERT: Must not insert NULL value into a nonnullable column '%Oc'.
E USOADA 2778

INSERT: Only constant expressions allowed in the value list.
E - USOADB - 2779
No value specified for mandatory column '%Oc'.
E - USOADC - 2780
UPDATE: Column '%Oc' is nonnullable and cannot accept a NULL value.

40-42

US Class Messages

E- USOADD- 2781

INSERT: No value specified for mandatory column '%Oc' of base table '% Ic' on which
view '%2c' is based.
E- USOAFO- 2800

line %Od, Stack overflow while parsing query. Please simplify the query.
E- USOAF2- 2802

line %Od, The RETRIEVE INTO statement is not allowed in OEM ULTRIX/SQL.
E- USOB5A - 2906

line %Od, There is no such function as '%Ic'.
E- USOB5B - 2907

line %Od, Function '% Ie' with an argument of type ' %2c' is not defined. Explicitly
convert the argument to the desired type.
E- USOB5C - 2908

line %Od, Function '% Ic' with arguments of type '%2c' and '%3c' is not defined.
Explicitly convert its arguments to the desired typc(s).
E- USOB5D - 2909

line %Od, Function '%Ic' with argument type '%2c' is ambiguous. Explicitly convert its
argument to the desired type.
E- USOB5E- 2910

line %Od, Operator '%lc' with operand(s) '%2c' and '%3c' is ambiguous.
E- USOB5F- 2911

line %Od, Datatype '%lc' can't be converted to '%2c'.
E- USOB60- 2912

line %Od, Aggregate function '%lc' with result type '%2c' is ambiguous. Explicitly
convert the function or its arguments to the desired type(s).
E- USOB61 - 2913

line %Od, You cannot assign a value of type '%lc' to a column of type '%2c'. Explicitly
convert the value to the required type.
E- USOB62- 2914

line %Od, You cannot have an aggregate function in a WHERE clause.
E - USOB63- 2915

line %Od, The columns in the SELECT clause must be contained in the GROUP BY
clause.

US Class Messages

40-43

E_USOB64_2916

E - USOB64- 2916
line %Od, Too many select items in SUBSELECT.
E - USOB65- 2917
line %Od, Number of target list elements in all UNIONed subselects must be the same.
E - USOB66- 2918
line %Od, SELECT item types '%lc' and '%2c' are not coercible to the same type.
E - USOB67 - 2919
line %Od, Conversion of types '%lc' and '%2c' to the same type is ambiguous.
E - USOB68- 2920
line %Od, Illegal expression in the HAVING clause.
E - USOB69- 2921
line %Od, Table reference '%lc' is ambiguous.
E - USOB6A - 2922
line %Od, Queries without from lists may not contain HAVING, WHERE, or GROUP BY
clauses.
E - USOB6B - 2923
line %Od, Aggregates cannot contain correlated variables.
E - USOB6C - 2924
line %Od, Syntax error. There are too many entries in the WITH or WHERE clause.
E - USOB6D - 2925
SELECT: FOR UPDATE clause found in non-update able SELECT statement.
May not use set function, GROUP, HAVING, DISTINCT, UNION, ORDER or more than
one variable in the FROM clause, at the outermost query level.
E - USOB6E- 2926
DESCRIBE: invalid USING '%Oc' clause. May specify NAMES only.
E - USOB6F- 2927
UNION and UNION ALL set operators must not be mixed.
E - USOB70- 2928
line %Od, aggregate function '%lc' not allowed in this context.
E - USOB71 - 2929
Value of host language variable of type '%Oc' must not be negative.

40-44

US Class Messages

E- USOCIC - 3100

Query requires too many range variables.
E- USOCE4 - 3300

Cannot update a view.
E- USOCEE- 3310

%Oc on view % 1c: can only update simple columns. No constants or expressions.
E- USOCF8- 3320

%Oc on view % Ic: column occurs in qualification of view.
E- USOCF9- 3321

%Oc on view % Ic: Appends on views with qualification and 'with option' in effect are not
allowed.
E- USOD02 - 3330

%Oc on view % Ic: update of a multi-variable view not allowed.
E- USODOC - 3340

%Oc on view % Ic: views do not have TID's.
E- USOD16- 3350

%Oc on view % Ic: cannot update views containing an aggregate.
E- USOD20- 3360

%Oc on view % Ic: that update might be non-functional.
E- USOD21 - 3361

%Oc on view % Ic: cannot update this view.
E- USOD2A - 3370

%Oc on view % Ic: base table %2c does not exist.
E- USOD34- 3380

No permission to update base table '%Oc'.
E- USOD35 - 3381

Permission on the subject table has qualification that references nonexistent table.
E- USOD36- 3382

User has no permission to execute database procedure '%Oc'.
E- USOD A2- 3490

INTEGRITY on %Oc: cannot handle aggregates.

US Class Messages

40-45

E - USODA3- 3491
INTEGRITY on %Oc: cannot handle multivariable constraints.
E - USODA4- 3492
INTEGRITY on %Oc: constraint does not initially hold.
E - USOD A5- 3493
INTEGRITY on %Oc: cannot define integrity on a view.
E - USODA6- 3494
INTEGRITY on %Oc: you must own %Oc.
E - USODA7 - 3495
The CREATEIDEFINE INTEGRITY command is not allowed in distributed
ULTRIX/SQL.
E - USOD A8- 3496
You cannot define an integrity constraint on a TID.
E - USODA9 - 3497
INTEGRITY on %Oc: cannot have subs elects in constraint.
E - USODAA- 3498
line %Od, You are not allowed to create integrity on '% Ic' table.
E - USODAC - 3500
%2c on table %Oc: protection violation.
E - USODAD - 3501
Number of protection qualifications for %Oc in this query exceeds maximum (% Id).
E - USODAE - 3502
%2c on table %Oc: no GRANT or GRANT compatible permit exists.
E - USOE06- 3590
PERMIT: bad terminal identifier' %Oc' .
E - USOE07- 3591
PERMIT: bad user name '%Oc'.
E - USOE08- 3592
PERMIT: Table '%Oc' not owned by you.
E - USOE09- 3593
PERMIT: Table '%Oc' must be a real table (not a view).

40-46

US Class Messages

E - USOEOA - 3594
PERMIT on %Oc: bad day-of-week '%lc'.
E - USOEOB - 3595
PERMIT on %Oc: only the DBA can use the PERMIT statement.
E - USOEOC - 3596
The CREATEIDEFINE PERMIT statement is not allowed in distributed ULTRIX/SQL.
E - USOEOD - 3597
PERMIT: Error on '%Oc'. Views are not allowed in the qualification.
E - USOEOF- 3599
CREATE PERMIT: This release of STAR only supports creation of ALL TO ALL and
SELECT TO ALL permits.
E - USOE74 - 3700
Tree buffer overflow in query modification.
E - USOE75- 3701
Tree build stack overflow in query modification.
E - USOED8- 3800
Line %Od, syntax error on '%Ic'. The correct syntax is:
CREATE LINK link_name [(col_list)]
[WITH
[NODE = [\']node_name[\'],
DATABASE = [\']ldb_name[\']]
[,DBMS = [\']dbms_name[\']
[,TABLE = [\']table_name[\']]]
E - USOED9 - 3801
Line %Od, syntax error on '% Ic'. The correct syntax is:
REGISTER [TABLEIVIEW] objname [(col_name {, col_name})]
AS LINK [FROM source] [with_clause]
REGISTER objname AS LINK WITH REFRESH
E - USOEDA - 3802
Line %Od, syntax error on '% Ic'. The correct syntax is:
REMOVE [TABLEIVIEW] object_name {, object_name}
E USOEDC 3804

Line %Od, syntax error on '% Ic'. The correct syntax is:
REGISTER objname AS LINK WITH REFRESH
US Class Messages

40-47

E - USOEDD - 3805
Line %Od, syntax error on '% I c'. The correct syntax is:
SET DDL_CONCURRENCY ON I OFF

E USOEE2 3810
Reserved for TERMINATOR.
E USOEE3 3811
Reserved for TERMINATOR.
E - USOEE5- 3813
Reserved for TERMINATOR.

E - USOEE6- 3814
Reserved for TERMINATOR.

E - USOEE7- 3815
Reserved for TERMINATOR.

E- USOEE8- 3816
Reserved for TERMINATOR.

E - USOEE9- 3817
Reserved for TERMINATOR.

E - USOEEA- 3818
Reserved for TERMINATOR.

E - USOEEB - 3819
Reserved for TERMINATOR.

E - USOEEC - 3820
Reserved for TERMINATOR.

E USOEED 3821
Reserved for Terminator

E - USOF3C - 3900
Line %Od, syntax error on '% Ic'. The correct syntax is:
DEFINE LINK link_name [(col_list)]
[WITH
[NODE = [1t]node_name[lt],
DATABASE = [1t]ldb_name[It]]
[,DBMS = [1t]dbms_name[lt]
[,TABLE = [1t]table_name[It]]]
40-48

US Class Messages

E USOF3D 3901
Line %Od, syntax error on '%lc'. The correct syntax is:
REGISTER [TABLEIVIEW] objname [(col_name {, col_name})]
AS LINK [FROM source] [with_clause]
. REGISTER objname AS LINK WITH REFRESH

E - USOF3E - 3902
Line %Od, syntax error on ' % 1c'. The correct syntax is:
REMOVE [TABLEIVIEW] object_name {, object_name}

E- USOF 40- 3904
Line %Od, syntax error on '%lc'. The correct syntax is:
REGISTER objname AS LINK WITH REFRESH

E - USOF41 - 3905
Line %Od, syntax error on ' % 1c'. The correct syntax is:
SET DDL_CONCURRENCY ON I OFF

E - US100F- 4111
String cannot be converted to numeric due to incorrect syntax.

E - US1036- 4150
Illegal filename for an ULTRIX/SQL table was specified: '%Oc'

E - US1068 - 4200
Integer overflow detected in query.

E - US1069 - 4201
Integer divide by zero detected in query.

E- US106A- 4202
Floating overflow detected in query.

E - US106B - 4203
Floating divide by zero detected in query.

E - US106C - 4204
Floating underflow detected in query.

E- US1071 - 4209
Invalid argument in call to math function.

US Class Messages

40-49

E- USI077 - 4215
Warning: %Od Integer overflows detected.
E- USI078- 4216
Warning: %Od Integer divide by zero operations detected.

E- USI079 - 4217
Warning: %Od Floating overflows detected.

E USI07 A 4218
Warning: %Od Floating divide by zero operations detected.
E- USI07B - 4219
Warning: %Od Floating underflows detected.

E- USI080- 4224
Warning: Non-printing character(s) converted to blank(s).

E- USI0CC - 4300
Addition of two absolute dates is undefined. Addition on dates must involve an absolute
date and an interval.
E- USI0CD - 4301
Subtracting an absolute date from an interval is not supported.

E- USI0CE - 4302
'%Oc' is not a valid date.

E- USI0CF- 4303
%Od is not a valid year for a date column.
E- USI0DO - 4304
%Od is not a valid month for a date column.
E- USI0Dl - 4305
%Od is not a valid day for a date column.

E- USI0D2- 4306
%Od:% Id:%2d is not a valid time for a date column.

E- USI0D3 - 4307
%Oc is not a valid time for use with the '% 1c' qualifier in a date column.

E USI0D4 4308
bad character found in date string beginning with '%Oc'.

40-50

US Class Messages

E- USI0D5 - 4309
cannot use am/pm specifications in a time interval.

E- USI0D6- 4310
%Od years is out of valid range for a date interval.
E- USI0D7 - 4311
date is out of range of valid years.
E- USI0D8- 4312
function dow (day-of-week) only valid on absolute dates.

E- USI0D9 - 4313
the date_trunc and date_part functions only work on absolute dates.
E- USI0DA - 4314
weeks are not implemented in dates.
E- USI0DB - 4315
the interval function recognizes no such unit as %Oc.
E- USI0DC - 4316
the interval function does not work on absolute dates.

E- USI0DD - 4317
Warning: %Od absolute dates ignored in sumO or avgO aggregate.
E- US1130- 4400
illegal character to integer conversion or non-numeric character in money field.
E- US1131 - 4401
exceeded the max. money value allowed.

E- US 1132- 4402
exceeded the min. money value allowed.

E- US1133- 4403
illegal blanks detected in money field.

E- US1134- 4404
multiple dollar signs detected in money field.

E- US1135 4405
multiple positive and/or negative signs detected in money field.
-)

US Class Messages

40-51

E US1136 4406
multiple decimal points detected in money field.
E - US1137- 4407
comma detected in money field - enter money values without commas.

E- US1138- 4408
positive or negative sign detected in numeric part of money field.

E - US1139- 4409
dollar sign detected in numeric part of money field.

E - US113A- 4410
money divide by zero detected.

E - US1194- 4500
Duplicate key on INSERT detected.

E - US1195 - 4501
Duplicate key on UPDATE detected.

E - US1196- 4502
SELECT returned multiple values.

E - US1197- 4503
line %Od, %Oc is a non-nullable datatype.

E - US1198- 4504
This update duplicates a row in the table.

E - US1199 - 4505
Update failed because an integrity constraint was violated.

E - USIIF7- 4599
Unexpected end of table during cursor update. Transaction is aborted.

E - US I1F8- 4600
Single table cursor is not open.

E- USIIF9- 4601
The cursor specified has not been opened.

E USIIFA 4602
The specified cursor does not support the requested action.

40-52

US Class Messages

E - USIIFB - 4603
The cursor was opened read-only.

E - USIIFC - 4604
The cursor is already opened.

E - USIIFD - 4605
The cursor is not currently positioned on a row.

E - USIIFF- 4607
Only one deferred cursor can be opened at a time.

E - US1200- 4608
Table name is not valid.

E - US1201 - 4609
Owner name is not valid.

E - US 1202- 4610
Invalid attribute type specified.

E - US1203 - 4611
A bad attribute name was specified.

E - US1204- 4612
Invalid size for specified attribute type.

E - US1205 - 4613
Invalid precision for specified attribute type.

E - US1206- 4614
The specified location name is invalid.

E - US1207 - 4615
An error occurred while deleting a record.

E - US 1208- 4616
Duplicate records were found.

E - US1209 - 4617
Database access conflict.

E - US120A- 4618
Database is already open.

US Class Messages

40-53

E - US120B - 4619
Nonexistent database.
E - US125C - 4700
Deadlock detected, your single or multi -query transaction has been aborted.
E- US125D - 4701
Ambiguous replace: you have specified several replacements for the same row.
E - US125E- 4702
Timeout occurred on lock request (see SET LOCKMODE command).
E - US125F- 4703
Out of locks in ULTRIX/SQL. Reduce number of tables referenced inside of multi-query
transaction or number of page locks allowed on a table (see SET LOCKMODE command).
E - US1260 - 4704
The IIDBDB is unavailable at this time because ULTRIX/SQL is out of locks. Please
reduce the number of locks being held or enlarge the lock table.
E - US1261 - 4705
Out of locks in ULTRIX/SQL. Reduce number of tables referenced inside of multi-query
transaction or number of page locks allowed on a table (see SET LOCKMODE command).
E - US1262 - 4706
Transaction has been aborted. The transaction log file filled up, requiring the oldest
transaction to be aborted. Consult your system administrator.
E - US1263 - 4707
Error allocating file system resource or bad file specification given. Check disk space,
disk quota, open file quota and the physical location.
E- US1264 - 4708
The query has been aborted.
E - US1265 - 4709
Database reorganization activity has rendered the query plan invalid. Try again after the
db activity is complete. In case of dynamic SQL, the statement must be prepared again.
E _ US1266 _4710_TRAN_ID _NOTUNIQUE
The distributed transaction ID is not unique in the local system.
E - US1267 - 4711 - DIS - TRAN- UNKNOWN
The distributed transaction ID is not known to the local system.

40-54

US Class Messages

E_USI268_4712_DIS_TRAN_OWNER
The distributed transaction is owned by another server in the local system. Disconnect the
previous association and try to re-connect later.
E _ US1269 _ 4713_ NOSECUREINCL USTER
Reserved for TERMINATOR.
E- US1270- 4714- ILLEGAL- STMT
Illegal statement specified. Only ROLLBACK or COMMIT statement is allowed
immediately after the RE-CONNECT statement.
E- US1271 - 4715- IIDBDB - TRAN- LIMIT
The IIDBDB is unavailable at this time because a Logging System quota has been
exceeded. Either reduce the number of active sessions or alter the logging system
parameters.
Parameters:

None.

Explanation:

The ULTRIX/SQL Logging System is configured with quotas on
the number of open databases in the installation and the number
of active transactions in the installation. One of these limits has
been reached. The exact quota which has been exceeded can be
determined from the error log - which will indicate either an
error opening/adding a database (database quota) or beginning a
transaction (transaction quota).

System Status:

Application or front end program will not start up.

Recommendation:

User must either wait for active sessions to complete so that the
system falls below its defined quotas, or the logging system must
be reconfigured with greater limits.

E - US1272 - 4716- DB - TRAN- LIMIT
The database cannot be opened at this time because a Logging System quota has been
exceeded. Either reduce the number of active sessions or alter the logging system
parameters.
Parameters:

None.

Explanation:

System Status:

Application or front end program will not start up.

Recommendation:

User must either wait for active sessions to complete so that the
system falls below its defined quotas, or the logging system must
be reconfigured with greater limits.

US Class Messages

40-55

E- US1389 - 5001
PRINT: bad table name %Oc.

E - US138A- 5002
PRINT: %Oc is a view and can't be printed.

E- US138B - 5003
PRINT: Table %Oc is protected.

E- US138C - 5004
The PRINT command is not allowed in distributed ULTRIX/SQL.

E - US138D - 5005
Table ' %Oc' is already in use. Close that table and try again.

E - US138E- 5006
Table is in use. Close that table and try again.

E - US13EE- 5102
%Oc: duplicate table name '%lc'.

E - US13EF- 5103
%Oc: ' % 1c' is a system table.

E - US13FO - 5104
CREATE %Oc: invalid column name '%lc'.

E - US13F1 - 5105
CREATE %Oc: duplicate column name '%lc'.

E- US13F2 - 5106
CREATE %Oc: invalid column format '%lc' on column '%2c'.

E - US13F3 - 5107
CREATE: It is not allowed to create a table with more than 127 columns.

E - US13F4- 5108
CREATE %Oc: excessive table width on column '%lc'.

E- US13F5 - 5109
CREATE %Oc: underscore not allowed in table names.

E- US13F6- 5110
CREATE %Oc: joumaling not allowed on this database.

40-56

US Class Messages

E- US13F7 - 5111
CREATE %Oc: You cannot create this table because the dba's table of the same name has
already been referenced by this query or multi-query transaction.

E- US13F8- 5112
CREATE %Oc: Disk error trying to create table. You are probably out of disk space or
disk quota.

E- US13F9 - 5113
CREATE: '%Oc' is an invalid locationname for your database. It is either not defined or
your database can't use it. Define it through ACCESSDB.

E- US13FA - 5114
The CREATE command is not allowed in distributed ULTRIX/SQL.

E- US13FB - 5115
The CREATE command does not recognize the parameter ' % 1c' .

E- US13FC - 5116
%Oc: Illegal tablename '%lc'. 'ii' is reserved for system catalogs.

E- US13FD - 5117
CREATE: %Oc: Joumaling will be enabled at the next checkpoint.

E- US13FE - 5118
%Oc is not allowed in distributed ULTRIX/SQL.

E- US141E- 5150
The EXCLUDE NODE command is not allowed in non-distributed ULTRIX/SQL.

E- US141F- 5151
The INCLUDE NODE command is not allowed in non-distributed ULTRIX/SQL.

E- US1420 - 5152
The DEFINE REFERENCE command doesn't recognize the parameter '%lc'.

E- US1451 - 5201
DESTROY: %Oc is a system table.

E- US1452 - 5202
DESTROY: %Oc does not exist or is not owned by you.

E- US1453 - 5203
DROPjDESTROY: %Od does not identify an existing integrity constraint.

US Class Messages

40-57

E- US1454- 5204
DROP/DESTROY: %Od does not identify an existing protection constraint.

E- US1455 - 5205
The DEFINE REFERENCE command is not allowed in non-distributed ULTRIX/SQL.

E- US1456- 5206
The DROP/DESTROY INTEGRITY command is not allowed in distributed
ULTRIX/SQL.

E- US1457 - 5207
The DROP/DESTROY PERMIT command is not allowed in distributed ULTRIX/SQL.

E- US1458 - 5208
DROP/REMOVE INDEX is not allowed in distributed ULTRIX/SQL.

E- US1459 - 5209
The maximum number of views in a HELP VIEW command is %Od.

E- US145A- 5210
DROP/DESTROY PERMIT: only the DBA can use the DROP/DESTROY PERMIT
statement.

E- US145B- 5211
Can not % Ic ' %Oc'. One may not % Ic a DDB object whose underlying LDB object is an
index.

E- US145C - 5212
QUEL queries are not supported in this release of ULTRIX/SQL.

E- US14B4- 5300
CREATE INDEX: cannot find primary table '%Oc'.

E- US14B5- 5301
CREATE INDEX: A secondary index may be created on at most 6 columns.

E- US14B6- 5302
CREATE INDEX: Invalid column '%Oc'.

E- US14B7- 5303
CREATE INDEX: Table '%Oc' not owned by you.

E- US14B8- 5304
CREATE INDEX: Table '%Oc' is already an index.

40-58

US Class Messages

E- US14B9 - 5305
CREATE INDEX: Table '%Oc' is a system table.

E- US14BA - 5306
CREATE INDEX: '%Oc' is a view and an index can't be built on it.
E- US14BB - 5307
CREATE INDEX: duplicate column '%Oc'.

E- US14BE- 5310
CREATE INDEX: index %Oc has been corrupted. It contains a pointer (tid:% 1d), which
points to a non-existent row in base table %2c. The error status was %3d.

E- US14BF - 5311
The INDEX statement is not allowed in distributed ULTRIX/SQL.

E- US14CO - 5312
CREATE INDEX: Location specified twice: '%Oc' conflicts with '%lc'.

E- US14Cl - 5313
CREATE INDEX: Bad storage structure '%Oc'. The valid storage structure names are
[c]btree, [c]isam, [c]hash.

E- US14C2- 5314
CREATE INDEX: '%Oc' is either an invalid option or the syntax of the WITH subclause
is invalid.
STRUCTURE is the only valid keyword for this type of subclause.

E- US14C3 - 5315
CREATE INDEX: Structure must be specified before '%Oc'.

E- US14C4- 5316
CREATE INDEX: Invalid FILLFACTOR of '%Od' specified. Must be in 1 - 100 range
(inclusive).

E- US14C5 - 5317
CREATE INDEX: FILLFACTOR can be specified only for [c]btree, [c]isam, [c]hash
storage structure.
E- US14C6- 5318
CREATE INDEX: Invalid MINPAGES of '%Od' specified.
Must be greater than O.
E- US14C7 - 5319
CREATE INDEX: MINPAGES can be specified only for [c]hash storage structure.

US Class Messages

40-59

E - US14C8- 5320
CREATE INDEX: Invalid MAXPAGES of '%Od' specified.
Must be greater than O.

E - US14C9 - 5321
CREATE INDEX: MAXPAGES can be specified only for [c]hash storage structure.

E - US14CA- 5322
CREATE INDEX: Invalid NONLEAFFILL of '%Od' specified.
Must be in 1 - 100 range (inclusive).

E- US14CB - 5323
CREATE INDEX: NONLEAFFILL can be specified only for [c]btree storage structure.

E - US14CC - 5324
CREATE INDEX: Invalid LEAFFILL/INDEXFILL of '%Od' specified.
Must be in 1 - 100 range (inclusive).

E - US14CD - 5325
CREATE INDEX: LEAFFILL/INDEXFILL can be specified only for [c]btree storage
structure.

E - US14CE - 5326
CREATE INDEX: '%Oc' is either an invalid option or the syntax of the WITH subclause
is invalid. Valid options for this type of subclause are: FILLFACTOR, MINPAGES,
MAXPAGES, NONLEAFFILL, LEAFFILL, MAXINDEXFILL.

E - US14CF- 5327
CREATE INDEX: Too many options in the WITH clause.

E - US14DO- 5328
CREATE INDEX: Too many columns in key of index.

E- US14Dl - 5329
CREATE INDEX: %Oc: Key '%lc' is out of sequence or is not in the column list. The key
list must be a prefix of the column list.

E - US14D3 - 5331
CREATE INDEX: The number of elements in the KEY clause must not be greater than
the number of indexed columns.

E - US14D4 - 5332
CREATE INDEX: Illegal MINPAGES value '%Od' in a CREATE INDEX command. The
value must be less or equal to the MAXPAGES value.

40-60

US Class Messages

E- US1518- 5400
HELP: Internal errors preclude further operation. Please report problem to product vendor.

E- US1519 - 5401
HELP: table %Oc does not exist.
E- US151A- 5402
HELP: cannot find manual section '%Oc'.

E- US151B - 5403
HELP: table %Oc is not a view.

E- US151C - 5404
HELP: table %Oc has no permissions granted on it.

E- US151D - 5405
HELP: table %Oc has no integrity constraints on it.

E- US1522 - 5410
HELP: tree buffer overflowed.

E- US1523 - 5411
HELP: tree stack overflowed.

E- US1524- 5412
The HELP INTEGRITY command is not allowed in distributed ULTRIX/SQL.

E- US1525 - 5413
The HELP PERMIT command is not allowed in distributed ULTRIX/SQL.
E- US1526- 5414
The HELP VIEW command is not allowed in distributed ULTRIX/SQL.
E- US157C - 5500
MODIFY: table %Oc does not exist.

E- US157D- 5501
MODIFY: you do not own table %Oc.
E- US157E- 5502
MODIFY %Oc: you may not provide keys on a heap.

E- US157F- 5503
MODIFY: It is not allowed to list more than 127 columns in a MODIFY command.

US Class Messages

40-61

E_ US i 580_5504

E - US1580- 5504
MODIFY %Oc: cannot modify system table.

E- US1581 - 5505
MODIFY %Oc: CHECKLINK and PATCHLINK are no longer part of the MODIFY
command. Check the reference manual for details.

E - US1583 - 5507
MODIFY %Oc: duplicate key '%lc'.

E - US1584 - 5508
MODIFY %Oc: key width (% 1d) too large for ISAM; maximum size is %2d.

E - US1586- 5510
MODIFY: Invalid option '%Oc'. Try one of the following: [C]ISAM, [C]HASH,
[C]HEAP, [C]HEAPSORT, [C]BTREE, MERGE, TRUNCATED, REORGANIZE,
REORGANISE, RELOCATE

E - US1587 - 5511
MODIFY %Oc: bad column name '%lc'.

E - US1588- 5512
MODIFY %Oc: '%lc' not allowed or specified more than once.

E - US1589 - 5513
MODIFY: Illegal FILLFACTOR '%Od' in a MODIFY command.
The value must be between 1 and 100, inclusive.

E - US158A - 5514
MODIFY: Illegal MINPAGES value '%Od' in a MODIFY command.The value must be
greater than zero.

E - US158B - 5515
MODIFY: column keys must not be specified unless storage structure is present.

E - US158C - 5516
MODIFY: Illegal MAXPAGES value '%Od' in a MODIFY command. The value must be
greater than zero.

E - US158D - 5517
MODIFY: Illegal MINPAGES value '%Od' in a MODIFY command. The value must be
less or equal to the MAXPAGES value.

E- US158E- 5518
MODIFY: invalid sequence specifier '%Oc' for column '%lc'.

40-62

US Class Messages

E_US159B_5531

E - US158F- 5519
MODIFY: %Oc is a view and can't be modified.

E - US1590 - 5520
MODIFY: %Oc: sequence specifier '%lc' on column %2c is not allowed with the
specified storage structure.

E - US1591 - 5521
MODIFY: table could not be modified because rows contain duplicate keys.

E - US1592- 5522
INDEX: table could not be indexed because rows contain duplicate keys.

E - US1593 - 5523
MODIFY: %Oc: ran out of disk space while performing modify.

E - US1594 - 5524
MODIFY: %Oc: key is % ld bytes; maximum size key for btrees is %2d bytes.

E- US1595 - 5525
MODIFY: %Oc: table is not a btree; only a btree table can be modified to merge.

E - US1596 - 5526
MODIFY: %Oc: all columns except the 'tidp' column should be part of the key in a btree
secondary index.

E - US1597 - 5527
MODIFY: %Oc: compressed row size can exceed maximum row width.

E - US1598- 5528
MODIFY: May not alter key sequence of secondary index table.

E- US1599 - 5529
MODIFY: '%Oc' is either an invalid option or the syntax of the WITH subclause is
invalid. The valid keywords for this type of subclause are: FILLFACTOR, MINPAGES,
MAXPAGES, NONLEAFFILL, LEAFFILL, MAXINDEXFILL.

E - US159A- 5530
The MODIFY command is not allowed in distributed ULTRIX/SQL.

E- US159B - 5531
MODIFY: %Oc: The '%lc' entry in the WHERE or WITH clause is incompatible with the
storage structure.

US Class Messages

40-63

E- US159C - 5532
INDEX: %Oc: The '%lc' entry in the WITH clause is incompatible with the storage
structure.

E- US159D - 5533
MODIFY: %Oc: Can't change the storage structure of this catalog.

E - US159E- 5534
INDEX: Unrecognized parameter '%Oc' in the WITH clause. Use one of the following:
STRUCTURE, KEY, FILLFACTOR, MINPAGES, MAXPAGES, LEAFFILL,
INDEXFILL, NONLEAFFILL, MAXINDEXFILL

E - US159F- 5535
INDEX: Unrecognized storage structure '%Oc' in an INDEX command. Please use one of
the following: [C]ISAM, [C]HASH, [C]BTREE

E- US15AO - 5536
MODIFY: %Oc: maximum size of a compressed row could exceed maximum row width.
Remember that the compressed C type uses an extra byte and the compressed CHAR type
uses two extra.

E- US15Al - 5537
INDEX: %Oc: key width (% Id) too large for ISAM; maximum size is %2d.

E- US15A2 - 5538
INDEX: %Oc: key is % Id bytes; maximum size key for btrees is %2d bytes.

E- US15A3 - 5539
INDEX: %Oc: maximum size of a compressed row could exceed maximum row width.
Remember that the compressed C type uses an extra byte.

E- US15A4 - 5540
MODIFY: %Oc: HEAP, CHEAP, and HEAPSORT are not valid storage structures for a
secondary index.

E- US15A5- 5541
MODIFY: %Oc: It is not allowed to modify a secondary index with non-unique keys to
one with unique keys. You can destroy and re-create the index with unique keys.

E- US15A6- 5542
MODIFY: The RELOCATE variant requires new and old location lists, they must be of
equal length.

E - US15A7 - 5543
MODIFY: Location clause must not be specified with MERGE or TRUNCATED.

40-64

US Class Messages

E - US15A8- 5544
MODIFY: line %Od, The WITH clause of the RELOCATE variant must have only
NEWLOCATION and OLDLOCATION subclauses.

E - US15A9 - 5545
MODIFY: line %Od, LOCATION keyword not allowed in the RELOCATE variant. Use
NEWLOCATION or OLDLOCATION instead.

E - US15AA - 5546
MODIFY: line %Od, '%lc' can be only used with RELOCATE variant.

E- US15AB - 5547
MODIFY: '%Oc' option has already been specified.

E - US15AC - 5548
MODIFY: REORGANIZE variant requires location(s) to be specified.

E - US15AD - 5549
MODIFY: line %Od, '%lc' option cannot be used with REORGANIZE variant.

E - US15EO- 5600
Save: Can't save system table '%Oc'.

E - US15El - 5601
Save: bad month '%Oc'.

E - US 15E2- 5602
Save: bad day '%Od'.

E - US15E3- 5603
Save: bad year '%Od'.

E - US15E4- 5604
Save: table '%Oc' does not exist or is not owned by you.

E - US15E5- 5605
The SAVE command is not allowed in distributed ULTRIX/SQL.

E US16A8 5800 '
COPY: table '%Oc' doesn't exist or is not owned by you.
E - US16A9 - 5801
COPY: column '%Oc' in table '%lc' doesn't exist or it has been listed twice.

E- US16AB - 5803
COPY: too many columns.
US Class Messages

40-65

E- US16AC - 5804
COPY: bad length for column '%Oc'. Length = '%lc'.
E- US16AD - 5805
COPY: can't open file ' %Oc' .
E- US16AE- 5806
COPY: can't create file '%Oc'.
E- US16AF- 5807
COPY: unrecognizable dummy domain '%Oc'.
E- US16BO- 5808
COPY: domain ' %Oc', size too small for conversion. There were %2c rows successfully
copied from '%3c' into '%4c'.
E- US16Bl - 5809
COPY: bad input string for domain '%Oc'. Input was '%lc'. There were %2c rows
successfully copied from '%3c' into '%4c'.

E- US16B2- 5810
COPY: unexpected end of file while filling domain ' %Oc' .

E- US16B3- 5811
COPY: bad type for column '%Oc'. Type = '%lc'.
E- US16B4- 5812
COPY: The table '%Oc' has a secondary index. The index(es) must be destroyed before
doing a ' copy from'.

E- US16B5 - 5813
COPY: You are not allowed to update the table '%Oc'.
E- US16B6- 5814
COPY: You do not own the table '%Oc'.

E- US16B7- 5815
COPY: An unterminated 'cO' or 'text(O)' field occurred while filling domain '%Oc'.

E- US16B8- 5816
COPY: The full pathname must be specified for the file '%Oc'.

E- US16B9- 5817
COPY: The maximum width of the output file cannot exceed 2008 bytes per row.

40-66

US Class Messages

E - US16BA - 5818
COPY: '%Oc' is a view and can't be copied.

E - US16BB - 5819
COPY: Warning: %Oc duplicate rows were ignored.

E - US16BC - 5820
COPY: Warning: %Oc domains had control characters which were converted to blanks.

E- US16BD - 5821
COPY: Warning: %Oc cO or text(O) character domains were truncated.

E- US16BE- 5822
COPY: Table '%Oc' is protected.

E - US16BF- 5823
COPY: Copy Into a text file must have 'dOni' delimiter as the last domain.

E - US16CO- 5824
COPY: '%Oc' is an invalid filetype. Filetype must be 'text', 'binary' ,or 'variable'.

E - US16Cl - 5825
COPY: The filetype must not be 'binary' when any of the columns are 'text(O)'.

E - US16C2- 5826
COPY: Error encountered while processing row %Oc.

E- US16C3 - 5827
COPY: Invalid character value (numeric value %Od) found while processing row % Ic.

E - US16C4- 5828
The COpy command is not allowed in distributed ULTRIX/SQL.

E - US16C5 - 5829
COPY: Computed row length exceeds allowable row length.

E - US16C6- 5830
COPY: Column '%Oc', cannot convert type '% I c' to type '%2c'.

E - US16C7 - 5831
COPY: Column '%Oc', bad delimiter '%lc'.

E - US16C8- 5832
COPY: Column '%Oc', delimiter not allowed. Use type 'dO' to specify delimiter.

US Class Messages

40-67

E - US16C9 - 5833
COPY: Column '%Oc', illegal column type

E - US16CA - 5834
COPY: Internal error initializing COPY.

E- US16CB - 5835
COPY: ULTRIX/SQL internal error processing row %Oc.

E- US16CC - 5836
COPY: Unexpected END OF FILE while processing row %Oc.

E - US16CD - 5837
COPY: Error allocating memory while processing row %Oc.

E - US16CE - 5838
COPY: underlying LDB object for '%Oc' is a view. You may not use COpy on views.

E - US16DO - 5840
COPY: Warning: Copy completed with %Oc warnings. % lc rows successfully copied.

E - US16Dl - 5841
COPY: Copy terminated abnormally. %Oc rows successfully copied.

E - US16D2 - 5842
COPY: Copy has been aborted.

E - US16D3 - 5843
COPY: %Oc rows could not be processed.

E - US16D4- 5844
COPY: %Oc rows were written to the Copy Log File '% I c' .

E - US16D5 - 5845
Table specified no longer exists.

E - US16D6- 5846
Table specified already exists.

E- US16D7 - 5847
COPY: Error writing to Copy Log File '%Oc' while processing row % 1c.

E - US16D8- 5848
COPY: Error closing Copy Log File '%Oc'.

40-68

US Class Message~

E- US16D9 - 5849
COPY: Error closing Copy File ' %Oc' .

E- US16DA- 5850
COPY: Bad data value for column '%Oc' encountered while processing row %lc.

E - US16DB - 5851
COPY: Invalid Copy option ' %Oc' .

E - US16DC - 5852
COPY: Invalid Copy option value '%Oc'.

E- US16DD - 5853
COPY: Ambiguous Copy options.

E - US16DE - 5854
COPY: Error opening Copy Log File '%Oc'.

E - US16DF- 5855
COPY: Error allocating memory while initializing Copy.

E- US16EO- 5856
COPY: Error allocating memory while processing row %Oc.

E - US16El - 5857
COPY: Error processing row %Oc. Cannot convert column '%lc' to tuple format.

E - US16E2- 5858
COPY: Error processing row %Oc. Cannot convert column '% lc' to row format.

E- US16E3- 5859
COPY: Error writing to Copy File while processing row %Oc.

E - US16E4- 5860
COPY: Error reading row from ULTRIX/SQL Application while processing row %Oc.

E - US 16E5- 5861
COPY: Error writing row to ULTRIX/SQL Application while processing row %Oc.

E - US16E6- 5862
COPY: NULL specification not allowed for the dummy column '%Oc'.

E - US16E7- 5863
COPY: Column ' %Oc' , NULL without null value may not be used with variable length
format.

US Class Messages

40-69

E- US16E8- 5864
COPY: Column '%Oc', NULL specification missing. Cannot copy rows containing nulls.

E- US16E9 - 5865
COPY: Column '%Oc', NULL value not compatible with fonnat specification.

E- US16EA- 5866
A copy command is currently in progress.

E- US16EB - 5867
An error in the copy command occurred.

E- US170C - 5900
SET: %Oc is not a valid set function.

E- US170D - 5901
SET JOURNALING: Setjoumaling does not have any parameters.

E- US170E- 5902
SET JOURNALING: Tables created during session will be logged.
E US170F 5903
SET JOURNALING: Tables create during session will NOT be logged.

E- US1710 - 5904
SET: Parameter must be constant or string name.

E- US1712 - 5906
SET TRACE: You do not have pennission to set trace flags.

E- US1713 - 5907
SET TRACE: Trace flag specification too long.

E- US1714 - 5908
SET JOURNAL_SIZE: This function no longer available.

E- US1715 - 5909
SET JOURNALING: Joumaling not enabled on this database.

E- US1716 - 5910
SET: This set command takes only a single argument (in quotes).

E- US1717 - 5911
SET: An integer argument is required (in quotes).

40-70

US Class Messages

E - US1718- 5912
SET: The merge factor must be between 3 and 15 inclusive.

E_US1719 _5913
SET: The sort buffer size must be between 1000 and 1000000 inclusive.

E_USI71A_5914
SET: The freespace buffer size must be between 1000 and 1000000 inclusive.

E - US171B - 5915
Unrecognized storage structure in a SET RET_INTO command. Please use one of the
following: HEAP, CHEAP, HEAPSORT, CHEAPSORT, HASH, CHASH, ISAM, CISAM,
BTREE,CBTREE

E - US171C - 5916
Unrecognized storage structure in a SET RESULT_STRUCTURE command. Please use
one of the following: HEAP, CHEAP, HEAPSORT, CHEAPSORT, HASH, CHASH,
ISAM, CISAM, BTREE, CBTREE

E - US1724- 5924
Unrecognized value for the LEVEL paremeter in a SET LOCKMODE command. Please
use one of the following: PAGE, TABLE, SESSION, SYSTEM

E - US1725 - 5925
Unrecognized value for the READLOCK parameter of a SET LOCKMODE command.
Please use one of the following: NOLOCK, SHARED, EXCLUSIVE, SESSION,
SYSTEM

E- US1726- 5926
Unrecognized value for the MAXLOCKS parameter of a SET LOCKMODE command.
Please use one of the following: a number, SESSION, SYSTEM

E- US1727 - 5927
Unrecognized value for the TIMEOUT parameter of a SET LOCKMODE command.
Please use one of the following: a number, SESSION, SYSTEM

E- US1728- 5928
Unrecognized parameter '%Oc' in a SET LOCKMODE command. Please use one of the
following: LEVEL, READLOCK, MAXLOCKS, TIMEOUT

E - US1729 - 5929
SET LOCKMODE: Invalid table name in a set command.

E - US172A- 5930
SET LOCKMODE: Cannot set session lock default to 'session'.

US Class Messages

40-71

E - US172B- 5931
SET LOCKMODE: Too many lockmode parameters.

E - US172C - 5932
SET LOCKMODE: This statement is not allowed in a multi-query transaction.

E- US172D - 5933
The SET [NO]JOINOP command is no longer supported. All queries now use JOINOP.

E - US172E- 5934
Bad date format '%Oc' in a SET DATE_FORMAT command. Please choose from one of
the following: "US", "MULTINATIONAL", "ISO", "FINLAND", "SWEDEN" I
"GERMAN"

E - US172F- 5935
Bad money format '%Oc' in a SET MONEY_FORMAT command. Please use the
following form: "L:xxxx" or "T:xxxx"
where xxxx is a zero to four character currency symbol. L indicates a leading currency
symbol, and T a trailing one. Example: "T:DM" would result in the value 10.85 displayed
as '10.85 DM'

E - US1730- 5936
Bad decimal indicator '%Oc' in a SET DECIMAL command. Please use either a comma
(",") or a period (".").

E - US1731 - 5937
Bad precision '%Od' in a SET MONEY _PREC command. Money precision determines
the number of digits displayed after the decimal indicator in a money value. Allowed
precision values are '0', '1', or '2'.
'0' indicates no digits after the decimal indicator (e.g., 10)
'1' indicates one digit (e.g. 10.8)
'2' indicates two digits (e.g. 10.85)

E - US1732 - 5938
SET CACHE: Invalid cache size. Legal range is 0 - 500. Setting the size of the cache to a
larger size than 500 will result in a cache size of 500.

E - US1733 - 5939
SET CACHE: You may not issue a SET CACHE command in a multi-query transaction.

E- US1734- 5940
The SET J_FREESZ1 command is no longer supported. This function is now done
automatically by the system.

E - US1735 - 5941
The SET J _FREESZ2 command is no longer supported. This function is now down
automatically by the system.
40-72

US Class Messages

E - US1736 - 5942
The SET J_FREESZ3 command is no longer supported. This function is now done
automatically by the system.

E - US1737 - 5943
The SET J_FREESZ4 command is no longer supported. This function is now done
automatically by the system.

E - US1738- 5944
The SET AGGREGATE command is not allowed in distributed ULTRIX/SQL.

E - US1739 - 5945
The SET CPUFACTOR command is not allowed in distributed ULTRIX/SQL.

E - US 173A- 5946
The SET DATE_FORMAT command is not allowed in distributed ULTRIX/SQL.

E - US173B - 5947
The SET [NO]DEADLOCK command is no longer supported.

E - US173C - 5948
The SET DECIMAL command is not allowed in distributed ULTRIX/SQL.

E- US173D - 5949
The SET EMBEDDED and SET EQUEL commands are not allowed in distributed
ULTRIX/SQL.

E - US173E- 5950
The SET [NO]JOINOP command is not allowed in distributed ULTRIX/SQL.

E - US173F - 5951
The SET [NO]JOURNALING command is not allowed in distributed ULTRIX/SQL.

E - US1740- 5952
The SET LOCKMODE command is not allowed in distributed ULTRIX/SQL.

E - US1741 - 5953
The SET MONEY_FORMAT command is not allowed in distributed ULTRIX/SQL.

E - US1742 - 5954
The SET MONEY_PREC command is not allowed in distributed ULTRIX/SQL.

E - US1743 - 5955
The SET QBUFSIZE command is not longer supported. This function is now done
automatically by the system.

US Class Messages

40-73

E- US1744- 5956
The SET RET_INTO command in not allowed in distributed ULTRIX/SQL.
E- US1745 - 5957
The SET SORTBUFSIZE command is not allowed in distributed ULTRIX/SQL.
E- US1746- 5958
The SET SQL command is not allowed in distributed ULTRIX/SQL.

E- US1747 - 5959
The SET [NO]STATISTICS command is not allowed in distributed ULTRIX/SQL.
E- US1748- 5960
The SET [NO]TRACE command is not allowed in distributed ULTRIX/SQL.
E- US1749 - 5961
The CREATEIDEFINE VIEW command is not allowed in distributed ULTRIX/SQL.

E- US174A - 5962
Unrecognized parameter '%Oc' given in a SET [NO]TRACE command. Please use one of
the following: TERMINAL, INPUT, OUTPUT, POINT
E- US174B - 5963
It is not allowed to give a file name with the SET NOTRACE TERMINAL command.

E- US174C - 5964
It is not allowed to give a file name with the SET NOTRACE INPUT and SET
NOTRACE OUTPUT commands.

E- US174D - 5965
The SET [NO]TRACE command must have a facility code and flag number.

E- US174E- 5966
Unrecognized facility code in SET [NO]TRACE %Oc. Please use one of the following:
DM - Data Manipulation Facility
PS - Parser Facility
SC - System Control Facility
RD - Relation Description Facility
QE - Query Execution Facility
OP - Optimizer Facility
QS - Query Storage Facility
AD - Abstract Datatype Facility

E- US174F- 5967
Bad flag number in SET [NO]TRACE %Oc. It must be between 0 and 9999, inclusive.

40-74

US Class Messages

E - US1750 - 5968
Integer parameters are not allowed in the SET [NO]TRACE TERMINAL, SET
[NO]TRACE OUTPUT, and SET [NO]TRACE INPUT commands.

E - US1751 - 5969
In a SET command, the non-integer '%Oc' was found where an integer was expected.

E - US1752- 5970
Unrecognized scope '%Oc' in a SET LOCKMODE command. Please use one of the
following: SESSION, ON tablename

E - US1753 - 5971
Unrecognized parameter in a SET AGGREGATE command. Please use one of the
following: PROJECT, NOPROJECT

E - US1754- 5972
The SET QUERY_SIZE command is no longer supported. This function is now done
automatically by the system.

E - US1755 - 5973
No file name was given for a 'SET TRACE INPUT' or 'SET TRACE OUTPUT'
command.

E - US1757 - 5975
The SET CACHE command is no longer supported.

E - US1758- 5976
The SET J_SORBUFSZ command is no longer supported.

E - US1759 - 5977
The SET RESULT_STRUCTURE command is no longer supported.

E - US175A - 5978
The SET RET_INTO command is no longer supported.

E - US175B - 5979
The SET AGGREGATE command is no longer supported.

E - US175C - 5980
The SET JOINOP [NO]TIMEOUT command is not allowed in distributed ULTRIX/SQL.

E - US175D - 5981
SET JOINOP: invalid option '%Oc'. Must be [NO]TIMEOUT.

E - US175E - 5982
The SET J_SORTBUFSZ command is no longer supported.
US Class Messages

40-75

E - US175F- 5983
SET AUTO COMMIT: invalid option '%Oc'. Must be ON or OFF.

E - US1760- 5984
A compressed table is not accessible due to a change in the tuple compression routines.
MODIFYing the table to a compressed structure under this version makes it accessible
once again.

E - US1761 - 5985
SET DDL_CONCURRENCY: invalid option '%oc'. Must be ON or OFF.

E - US1762- 5986
'SET LOCKMODE' on views is not supported in distributed ULTRIX/SQL

E - US1763 - 5987
SET LOCKMODE SESSION: parameter '%Oc' is not supported in distributed
ULTRIX/SQL

E - US 1839- 6201
RELOCATE: Table '%Oc' doesn't exist.

E - US183A - 6202
RELOCATE: Table '%Oc' can not be relocated.

E - US183B - 6203
RELOCATE: Locationname '%Oc' is not valid for this data base.

E - US183C - 6204
RELOCATE: Table '%Oc' does not belong to you.

E - US183D - 6205
RELOCATE: Table '%Oc' is a view.

E - US183E- 6206
The RELOCATE command is not allowed in distributed ULTRIX/SQL.

E - US183F - 6207
RELOCATE: To relocate table '%Oc', which resides in multiple locations, use
RELOCATE variant of the MODIFY command.
RELOCATE command can only be used on a table residing in a single location.

E - US1865 - 6245
Reserved for TERMINATOR.

E - US1866 - 6246
Reserved for TERMINATOR.
40-76

US Class Messages

E- US1867 - 6247
Reserved for TERMINATOR.

E- US1868 - 6248
Reserved for TERMINATOR.

E- US1869 - 6249
Reserved for TERMINATOR.

E- US186A- 6250
Reserved for TERMINATOR.
E- US186B - 6251
Reserved for TERMINATOR.
E- US186C - 6252
Reserved for TERMINATOR.
E- US186D - 6253
Reserved for TERMINATOR.
E- US186E- 6254
Reserved for TERMINATOR.

E- US186F- 6255
Reserved for TERMINATOR.

E- US1870- 6256
Reserved for TERMINATOR.
E- US1871 - 6257
Reserved for TERMINATOR.

E- US1872 - 6258
Reserved for TERMINATOR.

E- US1873 - 6259
Reserved for TERMINATOR.

E- US1874- 6260
Reserved for TERMINATOR.

E- US1875 - 6261
Reserved for TERMINATOR.

US Class Messages

40-77

E- US1876- 6262
Reserved for TERMINATOR.
E- US1877 - 6263
Reserved for TERMINATOR.

E- US1878- 6264
Reserved for TERMINATOR.

E- US1879 - 6265
Reserved for TERMINATOR.

E- US187 A- 6266
Reserved for TERMINATOR.

E- US187B - 6267
Reserved for TERMINATOR.

E- US187C - 6268
Reserved for TERMINATOR.

E- US187D - 6269
Reserved for TERMINATOR.

E- US187E- 6270
Reserved for TERMINATOR.

E- US187F - 6271
Reserved for TERMINATOR.

E- US1880 - 6272
Reserved for TERMINATOR.

E- US1881 - 6273
Reserved for TERMINATOR.

E- US1882- 6274
Reserved for TERMINATOR.

E- US1883 - 6275
Reserved for TERMINATOR.

E- US1884- 6276
Reserved for TERMINATOR.

40-78 US Class Messages

E- US1885 - 6277
Reserved for TERMINATOR.

E- US1886- 6278
Reserved for TERMINATOR.

E- US1887 - 6279
Reserved for TERMINATOR.

E- US1888- 6280
Reserved for TERMINATOR.

E- US1889 - 6281
Reserved for TERMINATOR.

E- US188A - 6282
Reserved for TERMINATOR.

E- US188B - 6283
Reserved for TERMINATOR.

E- US188C - 6284
Reserved for TERMINATOR.

E- US188D - 6285
Reserved for TERMINATOR.

E- US188E- 6286
Reserved for TERMINATOR.

E- US188F- 6287
Reserved for TERMINATOR.

EU
Reserved for TERMINATOR.

E- US1891 - 6289
Reserved for TERMINATOR.

E- US1892 - 6290
Reserved for TERMINATOR.

E- US1893 - 6291
Reserved for TERMINATOR.

US Class Messages

40-79

E- US1894- 6292
Reserved for TERMINATOR.
E- US1895 - 6293
Reserved for TERMINATOR.

E- US 1896- 6294
Reserved for TERMINATOR.

E- US1897 - 6295
Reserved for TERMINATOR.

E- US1898- 6296
Reserved for TERMINATOR.

E- US1899 - 6297
Reserved for TERMINATOR.

E- US189A- 6298
Reserved for TERMINATOR.

E- US189C - 6300- RULE- EXISTS
Reserved for TERMINATOR.

E- US189D - 6301 - RULE - ABSENT
Reserved for TERMINATOR.

E_USI89E_6302_RULE_QUAL
Reserved for TERMINATOR.

E- US189F- 6303- RULE - COL
Reserved for TERMINATOR.

E- US18AO - 6304- RULE - STAR
Reserved for TERMINATOR.

E- US18Al - 6305- RULE- II
Reserved for TERMINATOR.

E- VS18A2 - 6306- RULE- COLTAB
Reserved for TERMINATOR.

E- US18A3 - 6307- RULE- STMT
Reserved for TERMINATOR.

40-80

US Class Messages

E - US18A4- 6308- RULE- VIEW
Reserved for TERMINATOR.

E - US18AS - 6309- RULE- OWN
Reserved for TERMINATOR.
E - US18A6- 6310- RULE- OLDNEW

Reserved for TERMINATOR.
E - US18A7 - 6311 - RULE- WHEN

Reserved for TERMINATOR.

E - US18A8- 6312- RULE- DRPTAB
Reserved for TERMINATOR.

E - US18A9 - 6313- RULE- CAT
Reserved for TERMINATOR.

US Class Messages

40-81

XF Class Messages

E _ XFOOOl_ Cannot_generate_file
Cannot generate file name.
Explanation:

The file name generator (for user scripts and temp data file
names) is not working properly.

System Status:

Program terminates.

Recommendation:

Please submit a Software Performance Report (SPR).

E - XF0002- Cannot- create
Cannot create file %Oc!
Explanation:

The file whose name is given cannot be opened.

System Status:

Program terminates.

Recommendation:

Please submit a Software Performance Report (SPR).

E - XF0003- Cannot- write to file
Cannot write to file %Oc.
Explanation:

The file whose name is given cannot be written to.

System Status:

Program continues.

Recommendation:

Check disk space availability, then submit a Software
Performance Report (SPR).

S_ XF0004_Default_directory_is
Default directory is '%Oc'.
S_ XF0005 _Directory _is
Directory is '%Oc'.
E _ XF0006_Invalid_directory _pat
Invalid directory path.
Explanation:

The user specified an invalid path in which to place the files.

System Status:

Program terminates.

Recommendation:

The user should specify a valid directory.
XF Class Messages

41-1

E - XF0007- Cannot- alloc- view- buf

Cannot allocate buffer for view text.
Explanation:

This is a memory allocation error.

System Status:

Current view definition is not written.

Recommendation:

Rerun program, perhaps after checking memory availablility.

E - XF0008- Cannot- init view buf

Cannot initialize wrapping buffer for view text.
Explanation:

The routines to wrap the view text cannot be initialized.

System Status:

Current view definition is not written.

Recommendation:

Rerun program, then please submit a Software Performance
Report (SPR).

E _ XF0009 _Cannot _get_view _line

Cannot get next line of view text.
Explanation:

The routines to wrap the view text don't work properly.

System Status:

Current view definition is not written.

Recommendation:

Rerun program, then please submit a Software Performance
Report (SPR).

E _ XFOOOA _Cannot _alloc _intg_ buf

Cannot allocate buffer for integrity text.
Explanation:

This is a memory allocation error.

System Status:

Current integrity definition is not written.

Recommendation:

Rerun program, perhaps after checking memory availablility.

E _ XFOOOB _Cannot _init _intg_buf

Cannot initialize wrapping buffer for integrity text.
Explanation:

The routines to wrap the integrity text cannot be initialized.

System Status:

Current integrity definition is not written.

Recommendation:

Rerun program, then please submit a Software Performance
Report (SPR).

E _ XFOOOC _Cannot _get _intg_line

Cannot get next line of integrity text.
Explanation:

The routines to wrap the integrity text don't work properly.

System Status:

Current integrity definition is not written.

Recommendation:

Rerun program, then please submit a Software Performance
Report (SPR).

41-2

XF Class Messages

E_ XFOOOD _Cannot_alloe_prmt _ buf
Cannot allocate buffer for permit text.
Explanation:

This is a memory allocation error.

System Status:

Current permit definition is not written.

Recommendation:

Rerun program, perhaps after checking memory availablility.

E_ XFOOOE _Cannot _ init_prmt _buf
Cannot initialize wrapping buffer for permit text.
Explanation:

The routines to wrap the permit text cannot be initialized.

System Status:

Current permit definition is not written.

Recommendation:

Rerun program, then please submit a Software Performance
Report (SPR).

E_XFOOOF _Cannot_get _prmt _line
Cannot get next line of permit text.
Explanation:

The routines to wrap the permit text don't work properly.

System Status:

Current permit definition is not written.

Recommendation:

Rerun program, then please submit a Software Performance
Report (SPR).

S- XFOOI0- one- table- for user
There is one table for user %Oc.

S- XFOOll - n - tablesfor
-user
There are %Od tables for user % 1c.

S- XF0012- one- viewfor
user
There is one view for user %Oc.

S- XF0013- n - viewsfor
-user
There are %Od views for user % 1c.
Explanation:

There was a table or there were tables specified on the
commandline that does not exist or is not owned by the person
running copydb.

System Status:

Program continues looking for other tables specified on the
commandline.

Recommendation:

Re-run copydb specifying the correct table names.

E _ XF0019 _Cannot _find_table
There was a table specified on the command line that does not exist or is not owned by
you.

XF Class Messages

41-3

E _ XF0020_ Cannot_find_tables
There were tables specified on the command line that do not exist or are not owned by
you.
Explanation:

The routines to wrap the procedure text are not working correctly.

System Status:

Procedure definitions have not been written.

Recommendation:

Renin program, then please submit a Software Performance
Report (SPR).

E _ XF0014_Cannot _ alloe _proe _ buf
Cannot allocate buffer for procedure text.
E _ XF0015 _CannotJnit _proe _ buf
Cannot initialize wrapping buffer for procedure text.
E _ XF0016_Cannot _get _proe_line
Cannot get next line of procedure text.
S_ XF0017 _one _proe _for_user
There is one procedure for user %Oc.
S_ XF0018_ n _proes_for _user
There are %Od procedures for user % 1c.
Explanation:

The routines to wrap the link text are not working correctly.

System Status:

Link definitions have not been written.

Recommendation:

Rerun program, then please submit a Software Performance
Report (SPR).

E_XF0021_ Cannot _ alloe _reg_ buf
Cannot allocate buffer for link text.
E_XFOOIA _CannotJnit _reg_ buf
Cannot initialize wrapping buffer for link text.
E _ XFOOIB _Cannot _get _reg_line
Cannot get next line of link text.
S- XFOOI Cone
- tbl - for - user
There is one linked table for user %Oc.
S- XFOOID n tbls- for - user
There are %Od linked tables for user % 1c.

41-4

XF Class Messages

S- XFOOIE- one- indexfor
user
There is one linked index for user %Oc.
S- XFOOIF n indexes- for - user
There are %Od linked indexes for user % Ic.

S- XF0022- one- viewfor
-user
There is one linked view for user %Oc.
S- XF0023 n views- for - user
There are %Od linked views for user % I c.
Explanation:

The routines to wrap the rule text are not working correctly.

System Status:

Rule definitions have not been written.

Recommendation:

Rerun program, then please submit a Software Performance
Report (SPR).

E- XF0024- Cannot- alloe rule buf
Cannot allocate buffer for rule text.

E - XF0025- Cannot- init- rule- buf
Cannot initialize wrapping buffer for rule text.

E _ XF0026_Cannot_get _rule _line
Cannot get next line of rule text.

S- XF0027- one- rule- for - user
There is one rule for user %Oc.

S- XF0028- n- rulesfor
-user
There are %Od rules for user % Ic.

XF Class Messages

41-5

How to Order Additional Documentation

Technical Support
If you need help deciding which documentation best meets your needs, call 800-343-4040 before placing
your electronic, telephone, or direct mail order.

Electronic Orders
To place an order at the Electronic Store, dial 800-234-1998 using a 1200- or 2400-baud modem from
anywhere in the USA, Canada, or Puerto Rico. If you need assistance using the Electronic Store, call
800-DIGITAL (800-344-4825).

Telephone and Direct Mail Orders
Your Location

Call

Contact

Continental USA,
Alaska, or Hawaii

800-DIGITAL

Digital Equipment Corporation
P.O. Box CS2008
Nashua, New Hampshire 03061

Puerto Rico

809-754-7575

Local Digital Subsidiary

Canada

800-267-6215

Digital Equipment of Canada
Attn: DECdirect Operations KA02j2
P.O. Box 13000
100 Herzberg Road
Kanata, Ontario, Canada K2K 2A6

International
Internal*

Local Digital subsidiary or
approved distributor
SSB Order Processing - WMO/E15

or
Software Supply Business
Digital Equipment Corporation
Westminster, Massachusetts 01473

* For internal orders, you must submit an Internal Software Order Form (EN-01740-07).

Reader's Comments

ULTRIX
ULTRIXlSQL Error Message Dictionary
AA-PCAXA-TE

Please use this postage-paid form to comment on this manual. If you require a written reply to a software
problem and are eligible to receive one under Software Performance Report (SPR) service, submit your
comments on an SPR form.
Thank you for your assistance.

Please rate this manual:
Accuracy (software works as manual says)
Completeness (enough information)
Clarity (easy to understand)
Organization (structure of subject matter)
Figures (useful)
Examples (useful)
Index (ability to find topic)
Page layout (easy to find information)

Excellent

Good

Fair

Poor

0
0
0
0
0
0
0
0

What would you like to see more/less of!

What do you like best about this manual?

What do you like least about this manual?

Please list errors you have found in this manual:
Page

Description

Additional comments or suggestions to improve this manual:

What version of the software described by this manual are you using? _ _ _ _ __
Nameffitle _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __ Dept.
Company _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Date _ _ _ _ __
Mailing Address
_ _ _ _ _ _ _ _ _ _ _ _ Email _ _ _ _ _ _ _ _ _ __

Phone _ _ _ _ _ ___

.- - - - - .

Do Not Tear - Fold Here and Tape

Ilmallma™

-----------------------------lr1-lll----------:~:::::::--NECESSARY
IF MAILED IN THE
UNITED STATES

BUSI NESS RE·PLY MAl L
FIRST-CLASS MAIL PERMIT NO. 33 MAYNARD MA
POSTAGE WILL BE PAID BY ADDRESSEE

DIGITAL EQUIPMENT CORPORATION
OPEN SOFTWARE PUBLICATIONS MANAGER
ZK03-2/Z04
110 SPIT BROOK ROAD
NASHUA NH 03062-9987

11111111111111111111111 hllllllh hI hI hllllllllill
. - - - - - - . Do Not Tear - Fold Here . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ~

Cut
Along
Dotted
Line

Reader's Comments

ULTRIX
ULTRIXlSQL Error Message Dictionary
AA-PCAXA-TE

Excellent

Good

Fair

Poor

0
0
0
0
0
0
0
0

What would you like to see more/less of?

What do you like best about this manual? _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __

What do you like least about this manual? _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __

Please list errors you have found in this manual:
Page
Description

Additional comments or suggestions to improve this manual:

What version of the software described by this manual are you using? _ _ _ _ __
Name/fitle _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __ Dept. _ _ _ _ _ __
Company _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __ Date _ _ _ _ __
Mailing Address _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __
_ _ _ _ _ _ _ _ _ _ _ _ Email _ _ _ _ _ _ _ _ _ _ _ Phone _ _ _ _ _ __

I
I
I
I
I
I

•- - - - - .

Do Not Tear - Fold Here and Tape

IDrlDaml

-----------------------------[rl-[ll----------::::::A~:---I
NECESSARY
IF MAILED IN THE
UNITED STATES

BUSINESS REPLY MAIL
FIRST-CLASS MAIL PERMIT NO. 33 MAYNARD MA
POSTAGE WILL BE PAID BY ADDRESSEE

DIGITAL EQUIPMENT CORPORATION
OPEN SOFTWARE PUBLICATIONS MANAGER
ZK03-2/Z04
110 SPIT BROOK ROAD
NASHUA NH 03062-9987

111111111111111111111111111111111 111111 1111111111111
. - - - - - _.

Do Not Tear - Fold Here . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -)

Cut
Along
Dotted

Line