HP ALLBASE/SQL Message Manual

HP 9000 Computer Systems
ALLBASE/SQL
Message Manual
ABCDE
HP Part No. 36217-90009
Printed in U.S.A.
Eighth Edition
E0597
1997
The information contained in this document is subject to change
without notice.
Hewlett-Packard makes no warranty of any kind with regard to this
material, including, but not limited to, the implied warranties of
merchantability or tness for a particular purpose. Hewlett-Packard
shall not be liable for errors contained herein or for direct, indirect,
special, incidental or consequential damages in connection with the
furnishing or use of this material.
Hewlett-Packard assumes no responsibility for the use or reliability of
its software on equipment that is not furnished by Hewlett-Packard.
This document contains proprietary information which is protected
by copyright. All rights are reserved. Reproduction, adaptation, or
translation without prior written permission is prohibited, except as
allowed under the copyright laws.
Copyright c 1987-1997 by Hewlett-Packard Company
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 at DFARS
252.227-7013. Rights for non-DoD U.S. Government Departments and
agencies are as set forth in FAR 52.227-19 (c) (1,2).
Hewlett-Packard Company
3000 Hanover Street
Palo Alto, CA 94304 U.S.A.
Restricted Rights Legend
Printing History
The following table lists the printings of this document, together with the respective release
dates for each edition. The software version indicates the version of the software product
at the time this document was issued. Many product releases do not require changes to the
document. Therefore, do not expect a one-to-one correspondence between product releases
and document editions.
Edition
Date
First Edition (800)
First Edition (300)
Update 1 (800)
Update 1 (300)
Update Incorporated (800)
Update Incorporated (300)
Second Edition (800)
Second Edition (300)
Third Edition (800)
Third Edition (300)
Fourth Edition
March 1987
March 1987
June 1987
June 1987
August 1987
August 1987
February 1988
February 1988
November 1988
November 1988
September 1989
Update 1
October 1989
Fifth Edition
January 1991
Sixth Edition
September 1992
Seventh Edition
Eighth Edition
April 1994
May 1997
Product Number
36217-02A.01.00
79725 1.0
36217-02A.01.03
79725 1.0
36217-02A.01.03
79725 1.0
36217-02A.B2.00.03
79725 2.0
36217-02A.03.00
HP79725 Rev. 6.5
36217-02A.07.00
HP79725 Rev. 7.0
36217-02A.07.00
HP79725 Rev. 7.0
36217-02A.E1.00
36217-02A.E1.00
HP79725A.E1.00
HP79725A.E1.00
36217-02A.F0.00
36217-02A.F0.00
HP79725A.F0.00
HP79725A.F0.00
36217-02A.G0.00
36217-02A.G2.00
Hardware
HP-UX
Series
Release
800
300
800
300
800
300
800
300
800
300
800
300
800
300
800
700
400
300
800
700
400
300
700/800
700/800
1.0
1.0
1.3
1.0
1.3
1.0
2.0
6.5
3.0
6.5
7.0
7.0
7.0
7.0
8.0
8.0
8.0
8.0
8.0 and 9.0
8.0 and 9.0
8.0 and 9.0
8.0 and 9.0
9.0
10.0
iii
ALLBASE/SQL Manuals
Title
ALLBASE/ISQL Reference Manual
ALLBASE/NET User's Guide
ALLBASE/SQL Advanced Application Programming Guide
ALLBASE/SQL C Application Programming Guide
ALLBASE/SQL COBOL Application Programming Guide
ALLBASE/SQL Database Administration Guide
ALLBASE/SQL FORTRAN Application Programming Guide
ALLBASE/SQL Message Manual
ALLBASE/SQL Pascal Application Programming Guide
ALLBASE/SQL Performance and Monitoring Guidelines
ALLBASE/SQL Reference Manual
HP PC API User's Guide for ALLBASE/SQL
Up and Running with ALLBASE/SQL
ODBCLINK/SE Reference Manual
iv
Part Number
36217-90188
36217-90093
36217-90186
36217-90014
36217-90058
36217-90005
36217-90013
36217-90009
36217-90007
36217-90185
36217-90001
36217-90187
36389-90011
36217-90403
Preface
This manual explains the causes of warning and error conditions which may occur during the
use of the following components of ALLBASE/SQL: SQL, ISQL, SQLUtil, the preprocessors,
SQLMigrate, NET, or NETUtil as implemented on HP 9000 computers. It also presents
actions to be taken in response to these warning and error conditions. ALLBASE/SQL is the
basic component of Hewlett-Packard's relational database management system.
This manual is for database administrators, application programmers, and others who are
using ALLBASE/SQL. It presumes that the user already has a basic understanding of
database and ALLBASE/SQL concepts. The contents of this manual are as follows:
Chapter 1, \Introduction," discusses warning and error messages and how to use the
manual.
Chapter 2, \ALLBASE/SQL Warning Messages," describes ALLBASE/SQL warnings, and
indicates their probable cause and the appropriate user actions.
Chapter 3, \ALLBASE/SQL Error Messages," describes ALLBASE/SQL errors, and
indicates their probable cause and the appropriate user actions.
Chapter 4, \ALLBASE/SQL Console Error Messages," describes ALLBASE/SQL errors
that appear on the HP-UX system console, and indicates their probable cause and the
appropriate user actions.
v
What's New in this Release
G.1 and G.2 New Features
The following table highlights the new or changed functionality added in G.1 and G.2 releases,
and shows you where each feature is documented.
New Features in ALLBASE/SQL Releases G.1 and G.2
Feature (Category)
Description
Documented in
New operand to
Adds an operand to concatenate
concatenate strings character or binary strings in an
expression. New operand:
(Standards)
jj
...
ALLBASE/SQL Reference Manual ,
\Expressions."
RENAME Column Adds capability of dening a new ALLBASE/SQL Reference Manual ,
RENAME COLUMN and RENAME
name for an existing table or
or Table
column in a DBEnvironment. You TABLE in \SQL Statements."
(Usability)
cannot rename a table or column
that has check constraints or an
IMAGE/SQL table. New
commands: RENAME COLUMN,
RENAME TABLE.
CAST function
added to
Expression syntax
(Usability)
Adds the CAST function to allow ALLBASE/SQL Reference Manual , \Cast"
explicitly converting from one data in \Expressions."
type to another. It allows
conversion between compatible
data types and between normally
incompatible data types such as
CHAR and INTEGER. New
Expression function:
CastFunction .
Syntax added to
VALIDATE
(Usability,
Performance)
Automates execution of COMMIT ALLBASE/SQL Reference Manual ,
VALIDATE in \SQL Statements."
WORK after each module or
procedure is validated when WITH
AUTOCOMMIT is used. All
sections are revalidated whether
valid or invalid when FORCE is
used. This can reduce log space
and shared memory requirements
for the VALIDATE statement.
New syntax for VALIDATE:
FORCE, WITH AUTOCOMMIT.
vi
New Features in ALLBASE/SQL Releases G.1 and G.2 (continued)
Feature (Category)
Syntax added to
DELETE
(Usability,
Performance)
Description
Documented in
...
Automates execution of COMMIT ALLBASE/SQL Reference Manual ,
DELETE in \SQL Statements."
WORK at the beginning of the
DELETE and after each batch of
rows is deleted when WITH
AUTOCOMMIT is used. Reduces
log-space and shared-memory
requirements. WITH
AUTOCOMMIT cannot be used
in some cases (see the DELETE
statement). New syntax for
DELETE: WITH
AUTOCOMMIT.
Decimal operations Increases maximum precision from ALLBASE/SQL Reference Manual ,
\Decimal Operations" in \Data Types."
18 to 27.
(Usability)
Terminate a query Allows termination of a query for ALLBASE/SQL Reference Manual ,
a connection or transaction. New TERMINATE QUERY, SET SESSION, SET
(Usability,
TRANSACTION in \SQL Statements."
statement: TERMINATE
Performance)
QUERY. New syntax for SET
SESSION, SET TRANSACTION.
ALLBASE/SQL Reference Manual ,
TERMINATE TRANSACTION, SET
SESSION, SET TRANSACTION in \SQL
Statements."
Terminate a
transaction
(Usability,
Performance)
Allows stopping of a given
transaction. New statement:
TERMINATE TRANSACTION.
New syntax for SET SESSION,
SET TRANSACTION.
Timeout enhanced
to allow specifying
what is rolled back
or terminated
(Usability,
Performance)
Allows specifying the action when ALLBASE/SQL Reference Manual , SET
a timeout expires. New attributes SESSION in \SQL Statements."
for SET SESSION and SET
TRANSACTION:
TERMINATION AT LEVEL,
USER TIMEOUT, ON
TIMEOUT ROLLBACK.
New SQLUtil
command
CHKPTHLP
reduces time for
ushing data
(Performance)
Flushes the data in parallel to the ALLBASE/SQL Database Administration
Guide , CHKPTHLP in \SQLUtil"
CHECKPOINT command in
ISQL. New SQLUtil command:
CHKPTHLP.
Allow or disallow
SQLMON for
users.
(Usability)
Grants or revokes the ability to
run SQLMON for specic users.
New attribute for GRANT and
REVOKE: MONITOR.
ALLBASE/SQL Reference Manual ,
GRANT, REVOKE in \SQL Statements."
vii
New Features in ALLBASE/SQL Releases G.1 and G.2 (continued)
Feature (Category)
Description
Documented in
...
Allow or disallow
authority to create
modules.
(Usability)
Grants or revokes the ability to
create modules for specic users.
New attributes for GRANT and
REVOKE: INSTALL.
ALLBASE/SQL Reference Manual ,
GRANT, REVOKE in \SQL Statements."
Script for
migration to a new
release (Usability,
Tools)
Provides SQLINSTL script for
migration to a new release of
ALLBASE/SQL. Read the
SQLINSTL le on your system for
more information.
SQLINSTL le; Communicator 3000
MPE/iX Release 5.5 (Non-Platform Software
Release C.55.00) , \ALLBASE/SQL
Enhancements"; ALLBASE/SQL Database
Administration Guide in \SQLINSTL"
section of the \DBA Tasks and Tools"
chapter.
GENPLAN on a
Obtains an access plan of a stored ALLBASE/SQL Reference Manual ,
GENPLAN in \SQL Statements."
section (Usability) static query by specifying the
module and section number.
Changed syntax: GENPLAN.
POSIX support
(Tools)
Communicator 3000 MPE/iX Release 5.5
Starting with G.1, the
(Non-Platform Software Release C.55.00) ,
ALLBASE/SQL preprocessor
\ALLBASE/SQL Enhancements."
(PSQLCOB) supports
preprocessing and generation of
Microfocus COBOL source code
under POSIX (Portable Operating
System Interface).
Terminate a user's Terminates one or more
connections for a user. New
connections
syntax for TERMINATE USER:
(Connectivity)
CID ConnectionID .
ALLBASE/SQL Reference Manual ,
TERMINATE USER in \SQL Statements."
Run Queue
Control for
ALLBASE/NET
(Connectivity)
Allows running HPDADVR in D Communicator 3000 MPE/iX Release 5.5
(Non-Platform Software Release C.55.00) ,
queue for an MPE/iX session or
HP-UX connection or C queue for \ALLBASE/SQL Enhancements."
an MPE/iX job connection. New
environment variable:
HPSQLJOBTYPE.
PC ODBC 16-bit
and 32-bit support
(Connectivity,
Client/server)
ODBCLINK/SE allows
connectivity to ALLBASE and
IMAGE/SQL servers from a PC
running MS Windows using
ODBC.
ODBCLINK/SE Reference Manual
\Date/Time Functions" in the \Expressions"
Year 2000 solution Provides the JCW
HPSQLSPLITCENTURY to use chapter of the ALLBASE/SQL Reference
(Standards)
Manual
in setting a value between 0 and
99. This value is used to change
the century part of the DATE and
DATETIME functions to override
the default of 19.
viii
G.0 Features
The following table highlights the new or changed functionality in release G.0, and shows you
where each feature is documented.
New Features in ALLBASE/SQL Release G.0
Feature (Category)
Description
Documented in
...
Stored procedures
(Usability)
Provides additional stored
procedure functionality for
application programs. Allows
declaration of a procedure cursor
and fetching of multiple rows
within a procedure to applications.
New statement: ADVANCE.
Changed syntax: CLOSE,
CREATE PROCEDURE,
DECLARE CURSOR,
DESCRIBE, EXECUTE,
EXECUTE PROCEDURE,
FETCH, OPEN.
ALLBASE/SQL Reference Manual , \SQL
Statements" and \Using Procedures" in
\Constraints, Procedures and Rules;"
ALLBASE/SQL Advanced Application
Programming Guide , \Using Procedures in
Application Programs."
Case insensitivity
(Usability)
Adds an optional attribute to the
character and varchar type column
attributes of tables. Allows search
and compare of these columns in a
case insensitive manner. Four new
SQLCore data types are added.
Changed syntax: ALTER TABLE,
CREATE TABLE.
ALLBASE/SQL Reference Manual ,
\Comparison Predicate" in \Search
Conditions," CREATE TABLE in \SQL
Statements."
Support for 1023
columns
(Usability)
Increases the maximum number of
columns per table or view to 1023.
Increases maximum sort columns
and parameters in a procedure to
1023.
ALLBASE/SQL Reference Manual ,
CREATE TABLE and CREATE VIEW in
\SQL Statements;" ALLBASE/SQL
Database Administration Guide ,
\ALLBASE/SQL Limits" appendix.
ISQL HELP
improvements
(Usability)
Gives help for entire command
instead of only the verb.
ALLBASE/ISQL Reference Manual , HELP
in \ISQL Commands."
EXTRACT
command
(Usability)
Extracts modules from the
database and stores them in a
module le. Allows for creation of
a module le at any time based on
the current DBEnvironment
without preprocessing. New
command: EXTRACT. Changed
syntax: INSTALL.
ALLBASE/ISQL Reference Manual , \Using
Modules" in \Using ISQL for Database
Tasks," EXTRACT, INSTALL in \ISQL
Commands."
ix
New Features in ALLBASE/SQL Release G.0 (continued)
Feature (Category)
Description
Documented in
...
New SQLGEN
GENERATE
parameters
(Usability)
Generates SQL statements
necessary to recreate modied
access plans for module sections.
New syntax for GENERATE:
DEFAULTSPACE,
MODOPTINFO, PARTITION,
PROCOPTINFO, SPACEAUTH.
ALLBASE/SQL Database Administration
Guide , \SQLGEN Commands" appendix.
Row level locking
(Usability)
Permits multiple transactions to
read and update a table
concurrently because locking is
done at row level. Since the
transaction will obtain more locks,
the benets must be weighed
against the costs. (Previously
documented in an addendum after
F.0 release.)
ALLBASE/SQL Reference Manual ,
\Concurrency Control through Locks and
Isolation Levels;" ALLBASE/SQL Database
Administration Guide , \Eects of Page and
Row Level Locking" in \Physical Design."
Increased number
of users
(Usability)
Removes the limitation of 240
users supported by pseudotables.
(Maximum is system session
limits: 2000 on HP-UX; 1700 on
MPE/iX.)
ALLBASE/SQL Database Administration
Guide , \ALLBASE/SQL Limits" appendix.
POSIX support
(Usability)
ALLBASE/SQL Advanced Application
Improves application portability
Programming Guide , \POSIX Preprocessor
across MPE/iX and HP-UX.
Invocation" in \Using the Preprocessor."
Enhances the ALLBASE/SQL
preprocessors to run under POSIX
(Portable Operating System
Interface) on MPE/iX.
Application thread
support
(Performance,
Usability)
Provides the use of threads in an ALLBASE/SQL Advanced Application
Programming Guide , \Using the
application. Allows
ALLBASE/SQL to be used in an Preprocessor."
application threaded environment
on MPE/iX. Application threads
are light weight processes that
share some resources and last for
the duration of a transaction.
Threaded applications reduce the
overhead of context switching and
improve the performance of
OpenTP applications.
x
New Features in ALLBASE/SQL Release G.0 (continued)
Feature (Category)
High Availability
Description
Provides a collection of features to
keep systems available nonstop
including: Partial STORE and
RESTORE, Partial rollforward
recovery, DBEFiles in dierent
groups (MPE/iX), detaching and
attaching database objects,
CHECKPOINT host variable,
changing log les, console
messages logged to a le,
generating fewer log records by
using TRUNCATE TABLE to
delete rows, and new system
catalog information. See the
following features for new and
changed syntax.
Partial rollforward Supports partial rollforward
recovery through PARTIAL option
recovery
(High Availability) on SETUPRECOVERY. Used to
recover specic DBEFiles while
allowing access to other DBEFiles.
Documented in
...
ALLBASE/SQL Reference Manual , \SQL
Statements;" ALLBASE/SQL Database
Administration Guide , \Maintaining a
Nonstop Production System" in
\Maintenance" chapter and \SQLUtil"
appendix.
ALLBASE/SQL Database Administration
Guide , \Backup and Recovery" chapter and
SETUPRECOVERY PARTIAL in
\SQLUtil" appendix.
ALLBASE/SQL Database Administration
Gives more exibility in backup
Partial STORE
and recovery strategies by allowing Guide , \Backup and Recovery" chapter and
and RESTORE
\SQLUtil" appendix.
(High Availability) partial store and restore of
DBEFiles, DBEFileSets or
combinations of both. See \New
and changed SQLUtil commands
for increased availability" later in
this table.
Manages DBEFiles so they can be
DBEFile group
change on MPE/iX placed in a particular group or on
(High Availability) a particular volume (MPE/iX).
Use either CREATE DBEFILE or
MOVEFILE.
ALLBASE/SQL Reference Manual ,
CREATE DBEFile in \SQL Statements;"
ALLBASE/SQL Database Administration
Guide , \Maintaining a Nonstop Production
System" in \Maintenance" chapter and
MOVEFILE in \SQLUtil" appendix.
Detaches or attaches a DBEFile or
DBEFileSet from the
DBEnvironment. This is useful for
data that is accessed infrequently
such as tables containing historical
data only. New SQLUtil
commands: DETACHFILE,
ATTACHFILE.
ALLBASE/SQL Database Administration
Guide , \Maintaining a Nonstop Production
System" in \Maintenance" chapter and
DETACHFILE, ATTACHFILE in
\SQLUtil" appendix.
Detaching and
attaching database
objects
(High Availability)
xi
New Features in ALLBASE/SQL Release G.0 (continued)
Feature (Category)
New and changed
SQLUtil
commands for
increased
availability
(High Availability)
Description
Documented in
...
Adds support for high availability ALLBASE/SQL Database Administration
Guide , \SQLUtil" appendix.
and System Management
Intrinsics. Intended for non-stop,
continuously available operations.
New SQLUtil commands:
ATTACHFILE, CHANGELOG,
DETACHFILE, RESTORE
PARTIAL, STORE PARTIAL,
STOREINFO, STOREONLINE
PARTIAL, WRAPDBE.
Modied SQLUtil commands:
MOVEFILE, RESTORE,
RESTORELOG, SHOWDBE,
SETUPRECOVERY, STORE,
STORELOG, STOREONLINE.
List les on backup Lists physical names of les stored ALLBASE/SQL Database Administration
Guide , \Backup and Recovery" chapter and
on backup device with new
device
(High Availability) SQLUtil command: STOREINFO. STOREINFO in \SQLUtil" appendix.
Allows changing log les,
Log le
switching of console messages to a
improvements
(High Availability) le, and gives advance warning for
log full. Increased maximum size
of a single DBE log le to 4
gigabytes. A DBEnvironment can
have up to 34 log les congured.
Changed syntax: CHECKPOINT.
New SQLUtil command:
CHANGELOG.
ALLBASE/SQL Reference Manual ,
CHECKPOINT in \SQL Statements;"
ALLBASE/SQL Database Administration
Guide , \Maintaining a Nonstop Production
System" in \Maintenance" chapter,
CHANGELOG in \SQLUtil" appendix, and
\ALLBASE/SQL Limits" appendix.
New SET
SESSION and SET
TRANSACTION
statements
(Standards,
Performance)
Provides additional exibility and ALLBASE/SQL Reference Manual , SET
SESSION and SET TRANSACTION in
improved performance. Allows
setting and changing transaction \SQL Statements."
and session attributes.
FIPS agger
(Standards)
Meets Federal Information
Processing Standard (FIPS) 127.1
agger support. Flags
non-standard statement or
extension. Invoked with a agger
option in the preprocessor
command line or the SET
FLAGGER command in ISQL.
Updatability rules are dierent
when agger is invoked. New
syntax: DECLARE CURSOR,
WHENEVER. Changes to C and
COBOL host variable declaration.
xii
ALLBASE/SQL Reference Manual ,
DECLARE CURSOR in \SQL Commands"
and \Standards Flagging Support"
appendix; ALLBASE/SQL Advanced
Application Programming Guide , \Flagging
Non-Standard SQL with the FIPS Flagger;"
ALLBASE/ISQL Reference Manual , SET in
\ISQL Commands."
New Features in ALLBASE/SQL Release G.0 (continued)
Feature (Category)
Description
Documented in
...
Optimizer
enhancement
(Performance)
ALLBASE/SQL Performance and
Uses a more ecient algorithm
that signicantly reduces the time Monitoring Guidelines , \Optimization" in
\Basic Concepts in ALLBASE/SQL
to generate the access plan.
Performance."
Access plan
modication
(Performance)
Allows modication of access plans
for stored section to optimize
performance. View the plan with
SYSTEM.SETOPTINFO. New
statement: SETOPT.
ALLBASE/SQL Reference Manual ,
SETOPT in \SQL Statements;"
ALLBASE/SQL Database Administration
Guide , SYSTEM.SETOPINFO in \System
Catalog."
Syntax added to
disable access plan
optimization
(Performance,
Usability)
Species that the optimization
information in the module le is
not to be used. Changed syntax:
EXTRACT, INSTALL,
VALIDATE.
ALLBASE/SQL Reference Manual ,
VALIDATE in \SQL Statements;
ALLBASE/ISQL Reference Manual ,"
EXTRACT, INSTALL in \ISQL
Commands."
Application
Development
Concurrency
(Performance,
Usability)
Provides enhancements to improve
preprocessing performance when
simultaneously accessed by
multiple users. Page or row level
locking on any system base table
and processing without storing
sections. See the related features
in this table.
New SQL parameter: SET
DEFAULT DBEFileSet. SQL
changed syntax: ALTER TABLE,
GRANT, REVOKE, UPDATE
STATISTICS. ISQL changed
syntax: INSTALL. Changed
SYSTEM and CATALOG view.
New STOREDSECT tables.
Special owners HPRDBSS and
STOREDSECT. Changed syntax
for Full Preprocessing Mode.
ALLBASE/SQL Reference Manual ,
\Names" and \SQL Statements;"
ALLBASE/SQL Advanced Application
Programming Guide , \Using the
Preprocessor;" ALLBASE/ISQL Reference
Manual , \ISQL Commands;"
ALLBASE/SQL Database Administration
Guide , \Database Creation and Security"
and \System Catalog."
System Catalog
tables
(Performance)
Provides greater concurrency by
allowing users to specify table,
page, or row level locking of any
system table owned by
STOREDSECT through the
ALTER TABLE statement.
ALLBASE/SQL Reference Manual ,
\Names;" ALLBASE/SQL Database
Administration Guide , \System Catalog."
Preprocessors
(Performance)
Allows optional specication of a ALLBASE/SQL Advanced Application
DBEFileSet for storage of sections. Programming Guide , \Using the
Preprocessor."
Allows preprocessing without
storing sections in
DBEnvironment.
xiii
New Features in ALLBASE/SQL Release G.0 (continued)
Feature (Category)
I/O performance
improvement
(Performance)
Description
Optimizes I/O for initial load,
index build, serial scans, internal
data restructuring, le activity,
pseudo mapped les and
temporary les. See the following
features for new and changed
syntax.
Documented in
...
ALLBASE/SQL Reference Manual , \SQL
Statements."
Deletes all rows in a specied table ALLBASE/SQL Reference Manual ,
TRUNCATE
TRUNCATE TABLE in \SQL Statements."
TABLE statement leaving its structure intact.
Indexes, views, default values,
(Performance)
constraints, rules dened on the
table, and all authorizations are
retained. TRUNCATE TABLE is
faster than the DELETE
statement and generates fewer
logs. New statement:
TRUNCATE TABLE.
New scans
(Performance)
Reads tables with a new parallel ALLBASE/SQL Performance and
Monitoring Guidelines , \Using Parallel Serial
sequential scan. The tables are
partitioned and les are read in a Scans" in \Guidelines on Query Design."
round robin fashion to allow OS
prefetch to be more eective.
Allows the I/O for a serial scan to
spread across multiple disc drives.
Load performance
improvement
(Performance)
ALLBASE/SQL Reference Manual , SET
Improves performance with new
SESSION in \SQL Statements."
SET and SET SESSION
attributes, a new binary search
algorithm, and deferred allocation
of HASH pages. New attributes
for SET SESSION statement:
FILL, PARALLEL FILL.
ISQL enhanced to
improve the
performance of
LOADs
(Performance)
Uses new parameters of the ISQL ALLBASE/ISQL Reference Manual , SET in
SET command to set load buer \ISQL Commands."
size and message reporting.
Improves load performance.
Choose a procedure, command le,
or new ISQL command to set
constraints deferred, lock table
exclusively, and set row level DML
atomicity. Changed syntax: SET
(see the following feature).
xiv
New Features in ALLBASE/SQL Release G.0 (continued)
Feature (Category)
Description
Documented in
...
ALLBASE/ISQL Reference Manual , SET in
\ISQL Commands;" ALLBASE/SQL
Performance and Monitoring Guidelines ,
\Initial Table Loads" in \Guidelines on
Logical and Physical Design."
Modied SET
options
(Performance)
Provides better performance for
LOADs and UNLOADs. Specify
buer size, status reporting for
LOAD/UNLOAD or exclusive lock
for data table. AUTOSAVE row
limit increased to 2147483647.
New and changed SET options:
LOAD BUFFER, LOAD ECHO,
AUTOLOCK, AUTOSAVE.
SQLMON
(Tools)
ALLBASE/SQL Performance and
Monitors the activity of
ALLBASE/SQL DBEnvironment. Monitoring Guidelines , chapters 6-9.
Provides information on le
capacity, locking, I/O, logging,
tables, and indexes. Summarizes
activity for entire DBEnvironment
or focuses on individual sessions,
programs, or database
components. Provides read-only
information.
Audit
(Tools)
Provides a series of features to set
up an audit DBEnvironment
which generates audit log records
that you can analyze with the new
SQLAudit utility for security or
administration. Includes the
ability to set up partitions. See
ALLBASE/SQL Database
Administration Guide for
SQLAudit commands. Modied
statements: ALTER TABLE,
CREATE TABLE, START DBE
NEW, START DBE NEWLOG.
New statements: CREATE
PARTITION, DROP
PARTITION, DISABLE AUDIT
LOGGING, ENABLE AUDIT
LOGGING, LOG COMMENT.
ALLBASE/SQL Reference Manual , \SQL
Statements;" ALLBASE/SQL Database
Administration Guide , \DBEnvironment
Conguration and Security" chapter and
\SQLAudit" appendix.
Wrapper
DBEnvironments
(Tools)
Creates a DBEnvironment to wrap
around the log les orphaned after
a hard crash of DBEnvironment.
New SQLUtil command:
WRAPDBE.
ALLBASE/SQL Reference Manual ,
\Wrapper DBEnvironments" in \Using
ALLBASE/SQL;" ALLBASE/SQL Database
Administration Guide , WRAPDBE in
\SQLUtil."
HP PC API is now PC API is an application
HP PC API User's Guide for
bundled with
programming interface that allows ALLBASE/SQL.
ALLBASE/SQL. tools written with either the
GUPTA or the ODBC interface to
access ALLBASE/SQL and
IMAGE/SQL from a PC.
xv
New Features in ALLBASE/SQL Release G.0 (continued)
...
Feature (Category)
Description
Documented in
Increased memory
for MPE/iX
(HP-UX shared
memory allocation
is unchanged)
(Performance)
Increases memory up to 50,000
data buer pages and 2,000 run
time control block pages. Increases
the limits signicantly allowing
allocation of enough data buer
pages to keep the entire
DBEnvironment in memory if
desired for performance.
ALLBASE/SQL Reference Manual ,
STARTDBE, STARTDBE NEW, and
START DBE NEWLOG in \SQL
Statements;" ALLBASE/SQL Database
Administration Guide , \ALLBASE/SQL
Limits" appendix.
ALLBASE/NET
enhancements
(Connectivity,
Performance)
Improves performance of
ALLBASE/NET, allows more
client connections on server
system, and reduces number of
programs on MPE/iX.
ALLBASE/NET User's Guide , \Setting up
ALLBASE/NET."
ALLBASE/NET
commands and
options for
MPE/iX
(Connectivity,
Usability)
Adds option ARPA. Adds option ALLBASE/NET User's Guide , \Setting up
NUMSERVERS to check status of ALLBASE/NET" and \NETUtil Reference."
listeners and number of network
connections. Changed syntax:
ANSTART, ANSTAT, ANSTOP.
Changed NETUtil commands:
ADD ALIAS, CHANGE ALIAS.
ALLBASE/NET
and NetWare
(Connectivity)
ALLBASE/NET User's Guide , \Setting up
ALLBASE/NET listener for
NetWare now works with the 3.11 ALLBASE/NET."
version of Novell's NetWare for
UNIX (HP NetWare/iX).
Changed
restrictions for
executing NETUtil
commands for
MPE/iX
(Connectivity,
Usability)
Adds SM or AM (in the specied ALLBASE/NET User's Guide , \Setting up
account) to MANAGER.SYS for ALLBASE/NET."
adding, changing, or deleting users
for MPE/iX.
ARPA is only
TCP/IP interface
for data
communication
through
ALLBASE/NET
beginning with
HP-UX 10.0
(Connectivity)
ALLBASE/NET User's Guide , \Setting up
Remote database access
applications that specify NS will ALLBASE/NET" and \NETUtil Reference."
not work if the client and/or
server machine is an HP 9000
Series 700/800 running HP-UX
10.0 or greater. Server Node Name
entry must be changed from NS
node name to ARPA host name.
For the NETUsers le, the \Client
Node Name" must be changed
from the NS node name to the
ARPA host name. New NETUtil
commands: MIGRATE USER,
MIGRATE ALIAS.
xvi
Conventions
UPPERCASE
In a syntax statement, commands and keywords are shown in
uppercase characters. The characters must be entered in the order
shown; however, you can enter the characters in either uppercase or
lowercase. For example:
COMMAND
can be entered as any of the following:
command
Command
COMMAND
It cannot, however, be entered as:
comm
italics
com_mand
comamnd
In a syntax statement or an example, a word in italics represents a
parameter or argument that you must replace with the actual value.
In the following example, you must replace lename with the name
of the le:
COMMAND lename
punctuation
In a syntax statement, punctuation characters (other than brackets,
braces, vertical bars, and ellipses) must be entered exactly as shown.
In the following example, the parentheses and colon must be entered:
(lename):(lename)
underlining
Within an example that contains interactive dialog, user input and
user responses to prompts are indicated by underlining. In the
following example, yes is the user's response to the prompt:
Do you want to continue? >> yes
{
}
In a syntax statement, braces enclose required elements. When
several elements are stacked within braces, you must select one. In
the following example, you must select either ON or OFF:
COMMAND
[
]
ON
OFF
In a syntax statement, brackets enclose optional elements. In the
following example, OPTION can be omitted:
COMMAND lename [OPTION]
When several elements are stacked within brackets, you can select
one or none of the elements. In the following example, you can select
OPTION or parameter or neither. The elements cannot be repeated.
COMMAND lename
OPTION
parameter
xvii
Conventions (continued)
[ ... ]
In a syntax statement, horizontal ellipses enclosed in brackets
indicate that you can repeatedly select the element(s) that appear
within the immediately preceding pair of brackets or braces. In the
example below, you can select parameter zero or more times. Each
instance of parameter must be preceded by a comma:
[,parameter][...]
In the example below, you only use the comma as a delimiter if
parameter is repeated; no comma is used before the rst occurrence
of parameter :
[parameter][,...]
| ... |
In a syntax statement, horizontal ellipses enclosed in vertical bars
indicate that you can select more than one element within the
immediately preceding pair of brackets or braces. However, each
particular element can only be selected once. In the following
example, you must select A, AB, BA, or B. The elements cannot be
repeated.
A
| ... |
B
...
In an example, horizontal or vertical ellipses indicate where portions
of an example have been omitted.
In a syntax statement, the space symbol 1 shows a required blank.
In the following example, parameter and parameter must be
separated with a blank:
1
(parameter)1(parameter)
The symbol 4 5 indicates a key on the keyboard. For example,
4RETURN5 represents the carriage return key or 4Shift5 represents the
shift key.
4CTRL5character 4CTRL5character indicates a control character. For example, 4CTRL5Y
means that you press the control key and the Y key simultaneously.
4
xviii
5
Contents
1.
Introduction
ALLBASE/SQL Message Catalog . . . . . . . . . .
Types of Messages . . . . . . . . . . . . . . . .
Warning Messages . . . . . . . . . . . . . . .
Error Messages . . . . . . . . . . . . . . . . .
Console Error Messages . . . . . . . . . . . .
User Dened Messages . . . . . . . . . . . . . . .
RAISE ERROR . . . . . . . . . . . . . . . .
PRINT . . . . . . . . . . . . . . . . . . . .
How Messages are Returned . . . . . . . . . . . .
Understanding Message Manual Entries . . . . . . .
CAUSE and ACTION for Messages . . . . . . . .
Use of Exclamation Points . . . . . . . . . . . .
Using the HELP command . . . . . . . . . . . . .
Understanding Messages Returned from Remote Nodes
Connecting to a DBEnvironment . . . . . . . . . .
Native Language Support . . . . . . . . . . . . .
Using Other Manuals . . . . . . . . . . . . . . .
2.
ALLBASE/SQL Warning Messages
3.
ALLBASE/SQL Error Messages
4.
ALLBASE/SQL Console Error Messages
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-1
1-1
1-1
1-2
1-2
1-2
1-2
1-3
1-3
1-4
1-5
1-5
1-5
1-6
1-6
1-8
1-9
Contents-1
Figures
1-1. Connecting to a DBEnvironment . . . . . . . . . . . . . . . . . . .
Contents-2
1-7
1
Introduction
Information is returned to the user from ALLBASE/SQL in the form of messages, which
are displayed when an unusual condition occurs in ISQL, SQLUtil, SQLAudit, SQLGEN,
SQLMigrate, SQLMON, ALLBASE/NET, NETUtil, the preprocessors, or a user-written
application program that contains ALLBASE/SQL commands.
ALLBASE/SQL Message Catalog
Messages are stored in the ALLBASE/SQL message catalog , which must be installed on
your system. The pathname for the message catalog is /usr/lib/nls/$LANG/hpsqlcat,
where $LANG is the current language. The default message catalog is /usr/lib/nls/ncomputer/hpsqlcat. The default language is n-computer (US ASCII). For information about
selecting a native language other than the default, refer to \Native Language Support" in a
later section.
Types of Messages
This manual documents two basic types of messages:
Warning messages
Error messages
Warning Messages
Warning messages are followed by DBWARN and a number enclosed in parentheses. For
example:
Output will be truncated. (DBWARN 1)
Warnings do not cause your program or command to be aborted, but the entire command
or the incorrect part of the command is either ignored by ALLBASE/SQL or modied by
ALLBASE/SQL so that command processing may continue. In some cases, the transaction
may be completed in a way other than intended and will need to be corrected. In other cases,
warning messages are informational in nature and thus require no action to be taken. This
manual will inform the user whether action needs to be taken or not.
Introduction
1-1
Error Messages
Error messages are followed by DBERR and a number enclosed in parentheses. For example:
Number of copies must be in the range 1..20.
(DBERR 5)
Errors are usually caused by a user's attempting to perform a command with invalid
information or without the required capability or authority.
There are three basic types of errors. ALLBASE/SQL responds to them dierently depending
on the severity of the error.
The rst type of error is a syntax or authority-related error which keeps the current
command from executing. This is the most common type.
The second type of error causes the current transaction to be aborted. In addition, a
warning message is returned to inform you that the error was serious enough to terminate
the transaction. For example:
A transaction in progress was aborted.
(DBWARN 2010)
The third type of error, a DBCore internal system error, is the least common and sometimes
causes ALLBASE/SQL to be aborted.
Console Error Messages
In addition to messages with a DBWARN or DBERR number, you may receive unnumbered
messages returned to the HP-UX system console from the ALLBASE/SQL daemon process.
Console error messages typically alert the system administrator to a condition that aects the
DBEnvironment as a whole.
User Defined Messages
Two statements permit you to create your own messages in ALLBASE/SQL procedures and
applications:
RAISE ERROR
PRINT
RAISE ERROR
The RAISE ERROR statement permits users to dene their own message catalogs. The
number range 7000 - 7999 is reserved for use in RAISE ERROR. No errors in this range will
be generated by ALLBASE/SQL.
Each error caused by the RAISE ERROR statement is a regular error that generates a
message placed in the message buer. A raised error halts the execution of a rule, if issued
within a procedure invoked by a rule. A raised error does not cause transaction rollback or
disconnection from the DBEnvironment.
Any use of this statement will generate an error. The error number returned in SQLCODE
will be the specied error number or, if none is specied, the default error number (2350).
The error text returned will be the error text specied. If no text is specied, then no text is
returned. Messages stored in the message buer are available to application programs through
the use of the SQLEXPLAIN statement. Inside application programs, test SQLCODE, and
1-2
Introduction
if its value is less than zero, use SQLEXPLAIN to retrieve messages stored in the message
buer. SQLEXPLAIN cannot be used inside procedures.
The RAISE ERROR statement can be used to override the existing message catalog if the
user issues this statement with an existing error number dened in this manual. However, if
existing warning numbers are used, raised errors are not treated as warnings; they are always
treated as errors.
You should dene the action a user should take for each error number used with RAISE
ERROR. You can do this by including an explanation in the error text itself or in external
documentation. Refer to the ALLBASE/SQL Reference Manual for additional information on
using the RAISE ERROR statement.
PRINT
The PRINT statement, available only inside procedures, lets you place informational messages
in the message buer. PRINT is intended for informational messages that have the status
of warnings (though no actual warning may be intended). No numbers are assigned in the
PRINT statement. Inside application programs, test SQLWARN0 for a value of 'W', and if
this condition is true, use SQLEXPLAIN to retrieve messages stored in the message buer.
Refer to the ALLBASE/SQL Reference Manual for additional information on using the
PRINT statement.
How Messages are Returned
Depending on the way you are using ALLBASE/SQL, messages will be returned in one of the
following ways:
When you use ISQL, SQLUtil, SQLAudit, SQLGEN, SQLMigrate, SQLMON,
ALLBASE/NET, or NETUtil interactively, messages are returned to the standard
output, which is typically the terminal screen. These messages appear immediately after
ALLBASE/SQL encounters a problem. When using ISQL, SQLUtil, SQLAudit, SQLGEN,
SQLMigrate, SQLMON, NET, or NETUtil in background, messages are returned to the
standard output after processing.
When an error occurs during execution of an ISQL command le, one of two things will
occur. If SET CONTINUE is ON, the error message is displayed on the screen and the
subsequent commands are executed. If SET CONTINUE is OFF, a message is returned
to the terminal screen and none of the subsequent commands are executed. Refer to the
ALLBASE/ISQL Reference Manual for additional information on the CONTINUE option of
the SET command.
When you use the preprocessors, errors and warnings are returned to a le in your current
working directory called sqlmsg . A module is not stored when an error is encountered, and
your source code needs to be corrected before re-preprocessing. For additional information,
refer to the ALLBASE/SQL application programming guide for the language you are using.
An application program that contains embedded SQL commands must include error
handling routines to return runtime errors using the SQLEXPLAIN command. For
additional information on SQLEXPLAIN, refer to the ALLBASE/SQL application
programming guide for the language you are using.
Introduction
1-3
Some errors are written directly to a le named /tmp/hpsqlerr. Errors are written to this
le when they cannot be displayed on the terminal.
Errors from sqldaemon are returned to the system console.
While some messages will be self-explanatory, others will require additional information which
can be obtained from this manual, other ALLBASE/SQL manuals, or the ISQL, SQLUtil,
SQLAudit, SQLGEN, SQLMigrate, SQLMON, or NETUtil HELP command.
Understanding Message Manual Entries
Messages are presented in numerical order. The messages are categorized as follows:
1 - 499
500 - 699
700 - 799
1000 - 1999
2000 - 4999
7000 - 7999
8000 - 8999
9000 - 9999
10000 - 12999
13000 - 13499
13500 - 13699
13700 - 15999
16000 - 16999
20000 - 20999
25000 - 29999
30000 - 30999
31000 - 31899
31900 - 31999
32000 - 32999
33000 - 33499
34000 - 34999
(unnumbered)
1-4
ISQL messages
SQLAudit messages
SQLGEN messages
Parser and linearizer messages
SQLCore messages
Reserved for use in RAISE ERROR
SQLUtil messages
ACI messages
Preprocessor messages
DBCore messages
ALLBASE/Turbo CONNECT runtime messages
DBCore messages
DBECon messages
SQLMigrate messages
ALLBASE/NET messages
Data communication NetIPC messages
Data communication BSD messages
ALLBASE/NET common messages
ATCUtil messages
ALLBASE/DB2 CONNECT messages
SQLMON messages
Console error messages
Introduction
CAUSE and ACTION for Messages
Each message in this manual is followed by a CAUSE, which gives information as to why the
warning or error occurred. This is followed by an ACTION, which gives information on how
to resolve the problem, refers the user to an appropriate manual, or suggests contacting an HP
Service Representative or the Response Center. For example:
13
MESSAGE
! not a column name in table !. (DBERR 13)
CAUSE
The column you specied in the LOAD EXTERNAL command
does not exist in the table specied.
ACTION
Use the INFO command to check which columns are in the
specied table.
Use of Exclamation Points
Some messages contain one or more exclamation points (!), which are replaced by more
specic information (such as a number, lename, or subsystem name) when the condition
occurs. For example, if the lename you specied was PurchDF1, this message is received:
Error erasing file 'PurchDF1'. (DBERR 7)
The message is documented in this manual as:
Error erasing file '!'. (DBERR 7)
Using the HELP command
ISQL, SQLAudit, SQLGEN, SQLUtil, NETUtil, SQLMigrate, and SQLMON have HELP
commands. The help facility can be used for basic information such as correct syntax for a
specic command. For example:
isql=> help info;
=======================
ISQL INFO Command
=======================
The INFO command displays definitions of the columns of a table
or view.
--- SYNTAX --INF[O] {[Owner.]TableName}
{[Owner.]ViewName }
--- EXAMPLE --INFO System.Table
In ISQL, type HELP @ to obtain a list of all the ISQL and SQL commands.
Introduction
1-5
Understanding Messages Returned from Remote Nodes
If you are using ALLBASE/NET, you may receive error and warning messages from a version
of ALLBASE/SQL running under an operating system that is dierent from the operating
system of your local node. Although most ALLBASE/SQL error messages are similar
across operating systems, there are signicant dierences in details for messages dealing
with le names and user names. Also, some messages may appear only under a particular
operating system. When such dierences appear in a message, you may need to refer to the
ALLBASE/SQL Message Manual for both the client (local system) and the server (remote
system) in order to obtain a complete explanation of an error condition.
Connecting to a DBEnvironment
Attempting a CONNECT may result in the display of several messages. When an application
issues a command to connect to a DBEnvironment, ALLBASE/SQL rst attempts a local
connection. If one of the following conditions exists on the local node, ALLBASE/SQL
attempts a remote connection:
The CONNECT command is issued on a diskless node.
The /usr/lib/hpsqlproc le (database server process) does not reside on the local node.
There is no le with the DBEnvironmentName referred to in the CONNECT command on
the local system.
There is a le with that name, but it is not a DBECon le on the client system.
If the remote connection is not successful, one or two error messages are returned, as shown in
the following illustration.
1-6
Introduction
Figure 1-1. Connecting to a DBEnvironment
Introduction
1-7
Native Language Support
If your system has the proper message les installed, ALLBASE/SQL displays prompts,
messages and banners in the language you select; and it displays system dates and time
according to local customs. In addition, ISQL accepts responses to its prompts in the native
language selected. However, regardless of the native language used, the syntax of ISQL and
SQL commands|including punctuation|remains in ASCII.
In order to use a native language other than the default, you must follow the steps below:
1. Make sure your I/O devices support the character set you wish to use.
2. Set the HP-UX environment variable LANG to the native language (LanguageName ) you
wish to use. For the C shell, use the following command:
setenv LANG LanguageName
For the K shell, use the following command (no spaces before or after the equals sign):
typeset -x LANG=LanguageName
For the Bourne shell, use the following commands:
LANG=LanguageName
export LANG
This language then becomes the current language. (If LANG is not set, the current
language is n-computer.)
3. When you create a DBEnvironment, use the LANG=LanguageName option of the START
DBE NEW command to specify the language.
You can use native language characters in the DBEnvironment name. If you do so, you
must set the LANG environment variable to the same language before you can connect to
the DBEnvironment. To avoid confusion, you are advised to use the same language for the
DBEnvironment that you use in the LANG variable. Resetting the LANG variable while you
are connected to a DBEnvironment has no eect on the current DBE session.
1-8
Introduction
Using Other Manuals
In some cases, you may want to refer to one of the following documents for additional
information about ALLBASE/SQL:
All users should refer to the ALLBASE/SQL Reference Manual for in-depth information on
basic ALLBASE/SQL terms and concepts, and to the ALLBASE/ISQL Reference Manual
for information about interactive access to ALLBASE/SQL databases.
Database administrators should refer to the ALLBASE/SQL Database Administration Guide
for information on database creation and maintenance activities and how to use SQLAudit,
SQLUtil, SQLGEN, and SQLMigrate.
Database administrators should refer to the ALLBASE/SQL Performance and Monitoring
Guidelines for information on performance issues, monitoring activities, and how to use
SQLMON.
Application programmers should refer to the appropriate ALLBASE/SQL application
programming guide for details on embedding SQL commands in application programs.
Users of ALLBASE/NET should refer to the ALLBASE/NET User's Guide for information
on accessing a remote DBEnvironment.
Introduction
1-9
2
ALLBASE/SQL Warning Messages
1
MESSAGE
Output will be truncated. (DBWARN 1)
CAUSE
The SELECT statement generated rows that are longer than the
size specied by the PAGEWIDTH option of the SET command.
The pagewidth may be set to a maximum of 254 bytes.
Increase the pagewidth value using the ISQL SET command.
ACTION
2
3
4
MESSAGE
File '!' already exists. Next SELECT will overwrite.
(DBWARN 2)
CAUSE
You have specied a le name that already exists as the output
le for the results of a SELECT.
ACTION
No action is necessary if you want to overwrite the existing le.
Specify another output le name using the OUTPUT option of
the ISQL SET command if you want output to go to a dierent
le.
MESSAGE
Column name ! truncated to ! bytes. (DBWARN 3)
CAUSE
A column name specied in the ISQL INPUT command was
greater than 20 bytes. This probably occurred because you did
not leave a space between column names. If the bytes which
remained after the truncation formed an existing column name,
the command was executed for that column.
ACTION
Delete any rows that were incorrectly input. Issue the INPUT
command again, separating the column names with spaces.
MESSAGE
Parameter substitution caused overflow - command
truncated. (DBWARN 4)
CAUSE
Substitution of parameter values into the command caused the
command length to exceed 2048 bytes, necessitating truncation.
ACTION
Try to rewrite the command so that the command length after
parameter substitution will be no greater than 2048 bytes.
ALLBASE/SQL Warning Messages
2-1
5
6
7
8
9
2-2
MESSAGE
BULK not allowed interactively - ignored. (DBWARN 5)
CAUSE
You issued a BULK SELECT or BULK FETCH option while in
ISQL.
ACTION
Any SELECT performed in ISQL is automatically treated as
a BULK SELECT. BULK is an option for programming with
SQL only. Refer to the ALLBASE/SQL Reference Manual for
additional information.
MESSAGE
Transaction terminated. (DBWARN 6)
CAUSE
EOF was reached on input le.
ACTION
SQLCore automatically rolled back the transaction. No action is
necessary.
MESSAGE
Commands after START ignored. (DBWARN 7)
CAUSE
You may not have any additional commands on the command
line after a START command.
ACTION
Refer to the ALLBASE/SQL Reference Manual for more
information.
MESSAGE
Numeric field error on line !, column !. (DBWARN 8)
CAUSE
The line number specied contains non-numeric data in the
column indicated. The LOAD EXTERNAL command continues
executing and loads a 0 value for that column.
ACTION
Refer to the ALLBASE/ISQL Reference Manual for additional
information on the LOAD EXTERNAL command.
MESSAGE
Entire command has been deleted. (DBWARN 9)
CAUSE
You deleted the entire command using the REDO command.
ACTION
No action is necessary.
ALLBASE/SQL Warning Messages
10
11
12
13
14
MESSAGE
Load file is empty. (DBWARN 10)
CAUSE
The le that you named in the LOAD EXTERNAL command is
empty. No rows were processed.
ACTION
No action is necessary.
MESSAGE
LOAD command stopped because of error. (DBWARN 11)
CAUSE
An INTERNAL load could not be continued due to another error.
An additional message will be returned.
ACTION
Refer to the cause and action of the additional message.
MESSAGE
Starting row is beyond end of load file. (DBWARN 12)
CAUSE
The starting row number specied in the LOAD PARTIAL
command was beyond the last line of the le. No rows were
loaded.
ACTION
Issue the LOAD command again, specifying an appropriate
starting row.
MESSAGE
Number of rows specified exceeds number in load file.
(DBWARN 13)
CAUSE
The number of rows specied in the LOAD PARTIAL command
was greater than the number of rows between the starting row
and the end of the le.
ACTION
No action is necessary. All qualifying rows, from the starting row
to the end of the le, were loaded.
MESSAGE
User language and DBE language differ. (DBWARN 14)
CAUSE
You started or connected to a DBEnvironment with a language
other than your current language.
ACTION
Exit ISQL. Set your LANG environment variable and invoke
ISQL.
ALLBASE/SQL Warning Messages
2-3
15
16
17
18
19
2-4
MESSAGE
Local catalog is inaccessible. Default catalog in use.
(DBWARN 15)
CAUSE
The ALLBASE/SQL message catalog corresponding to your
language cannot be accessed, probably because it does not exist.
ACTION
Contact your system administrator.
MESSAGE
Unable to load all local response options. (DBWARN 16)
CAUSE
One or more of the local response options was missing from the
message catalog or contained invalid data.
ACTION
Contact your system administrator.
MESSAGE
Local response options are not unique. (DBWARN 17)
CAUSE
The local response options in the message catalog are not unique.
ACTION
Contact your system administrator.
MESSAGE
Field boundaries specified do not coincide with character
boundaries. (DBWARN 18)
CAUSE
The byte at a starting location specied in the LOAD command
is the second byte of a two-byte character, or the last byte of a
eld is the rst byte of a two-byte character.
ACTION
Delete the rows loaded. Issue the LOAD command again,
specifying eld boundaries that coincide with character
boundaries.
MESSAGE
Unable to upshift native language string. (DBWARN 19)
CAUSE
ISQL was unable to upshift a character string, probably because
the string contains one or more invalid bytes.
ACTION
Issue your command again, specifying valid input.
ALLBASE/SQL Warning Messages
20
21
22
23
24
MESSAGE
Unable to split string into lines. (DBWARN 20)
CAUSE
ISQL was unable to split a character string into lines, probably
because the string contains one or more invalid bytes.
ACTION
Issue your command again, specifying valid input.
MESSAGE
Unable to trim trailing blanks from multi-byte native
language string. (DBWARN 21)
CAUSE
ISQL was unable to trim trailing blanks from a character string,
probably because the string contains one or more invalid bytes.
ACTION
Issue your command again, specifying valid input.
MESSAGE
Unable to truncate multi-byte native language string.
(DBWARN 22)
CAUSE
ISQL was unable to truncate a character string, probably because
the string contains one or more invalid bytes.
ACTION
Issue your command again, specifying valid input.
MESSAGE
Unable to obtain user language. Default language
n-computer assumed. (DBWARN 23)
CAUSE
Your LANG environment variable is set to a language that is not
congured, or the support les for your language are missing.
ACTION
Contact your system administrator.
MESSAGE
No language set. Default language n-computer assumed.
(DBWARN 24)
CAUSE
Your LANG environment variable is not set.
ACTION
Set your LANG variable if desired.
ALLBASE/SQL Warning Messages
2-5
25
232
233
234
2-6
MESSAGE
Local welcome file is inaccessible. Default file in use.
(DBWARN 25)
CAUSE
The ISQL welcome le corresponding to your language cannot be
accessed, probably because it does not exist.
ACTION
Contact your system administrator.
MESSAGE
! conversion error on line !, column !. (DBWARN 232)
CAUSE
There is a problem converting Date, Time, DateTime, or Interval
eld to internal format when trying to load the data from an
external data le. The error messages following this one will give
more specic information on the problem.
ACTION
Check the load information specied for this eld (start position,
length, date/time/interval eld format) and the format of the
data value for possible problems. Correct problems and redo
LOAD operation.
MESSAGE
Default format not used for ! field, column !. (DBWARN
233)
CAUSE
You did not use the default format for a Date, Time, DateTime
or Interval eld in the load description le.
ACTION
Modify the format in the descriptor le. Make sure the data is in
the default format and redo the LOAD operation. Refer to the
ALLBASE/ISQL Reference Manual for format specications.
MESSAGE
Unable to convert ! value to a displayable format. (DBWARN
234)
CAUSE
Unable to convert a Date, Time, DateTime or Interval value to a
value that can be stored in the data le. This was probably due
to a bad format or length specied for the eld.
ACTION
Check the unload format and length given for this eld. Correct
any problems and redo the UNLOAD operation.
ALLBASE/SQL Warning Messages
235
236
302
502
MESSAGE
Only first ! rows can be displayed. (DBWARN 235)
CAUSE
More rows qualied for the SELECT statement than can be
viewed through ISQL.
ACTION
If all the rows of data need to be viewed, use the UNLOAD
EXTERNAL command to unload the data to an ASCII le.
MESSAGE
*WARNING*: DATA NOT COMPLETE - FIRST ! ROWS DISPLAYED.
(DBWARN 236)
CAUSE
This message is displayed on the last line of the outle when an
outle is specied with the OUTPUT option of the ISQL SET
command and more rows qualify for the SELECT than can be
viewed within ISQL. The outle will hold all the rows that can be
viewed within ISQL.
ACTION
If all the rows of data need to be viewed, use the UNLOAD
EXTERNAL command to unload the data to an ASCII le.
MESSAGE
File Device Full. (DBWARN 302)
CAUSE
Your storage medium (tape or disk) is full.
ACTION
If your storage is on tape, mount another tape. If your storage
is on disk, exit, clean up the le system, and try again. If the
problem persists, contact the system administrator.
MESSAGE
Nothing left to audit. (DBWARN 502)
CAUSE
This warning is returned if SQLAudit determines that there is
nothing left to audit in the DBEnvironment log les. This usually
is the case if there have been no new transactions committed
between the time the beginning audit point was dened and the
ending audit point was dened.
ACTION
This is not a real error, but you should check to make sure the
partitions that have been supplied to SQLAudit include all
partitions you wish to see transactions for.
ALLBASE/SQL Warning Messages
2-7
506
522
523
525
528
MESSAGE
Partition ! has no committed transactions. (DBWARN 506)
CAUSE
The partition being audited has no committed transactions. This
basically means that no committed transactions have touched
data belonging to the specied partition.
ACTION
No action required except to make sure the partition was
intended to be audited.
MESSAGE
Duplicate Partition Number entered. Ignored. (DBWARN
522)
CAUSE
The same partition was entered previously.
ACTION
No action necessary since the duplicate partition is ignored.
MESSAGE
No transactions exist for the given set of Partition
Numbers. (DBWARN 523)
CAUSE
No transactions have been committed which aect the list of
audited partitions.
ACTION
No action necessary.
MESSAGE
Partition ! has no transactions to audit. (DBWARN 523)
CAUSE
No transaction information was found in the ending audit point
for the given partition. This would be possible if no committed
transactions have touched the partition, or the transaction
information was removed through a hard resync.
ACTION
No action necessary.
MESSAGE
SET DBENVIRONMENT command has not been issued yet. (DBWARN
528)
Calling SET DBENVIRONMENT for you before proceeding with
command.
2-8
CAUSE
You do not currently have a DBEnvironment session active. This
would be established by using the SET DBENVIRONMENT
command. This command will automatically be issued on your
behalf.
ACTION
Enter the name of the DBEnvironment at the prompt to establish
the DBEnvironment session.
ALLBASE/SQL Warning Messages
700
701
703
704
705
MESSAGE
A DBE session is already started. (DBWARN 700)
Type 'RELEASE' if you wish to start a new DBE session.
CAUSE
A DBE session has already been started.
ACTION
Issue the RELEASE statement to end the current session
and then use the STARTDBE statement to begin a new
DBEnvironment session.
MESSAGE
A DBE session has not been started. (DBWARN 701)
Calling STARTDBE for you before proceeding with command.
CAUSE
A DBEnvironment session has not been started.
ACTION
The STARTDBE statement was automatically called to begin the
session. Enter the necessary DBEnvironment name.
MESSAGE
[RETURN] not allowed for UNLOAD/LOAD Schema File name.
(DBWARN 703)
CAUSE
A carriage return was entered at the UNLOAD/LOAD Schema
File name prompt. This is not allowed.
ACTION
Enter a valid UNLOAD/LOAD Schema File name.
MESSAGE
Prefix is required to be from 1 to 5 bytes long. (DBWARN
704)
CAUSE
Entered prex was an invalid length.
ACTION
Re-enter the prex name with a length of 1 to 5 bytes.
MESSAGE
Unrecognized command. (DBWARN 705)
CAUSE
An unknown command was entered.
ACTION
Enter a valid SQLGEN command.
ALLBASE/SQL Warning Messages
2-9
706
707
711
712
713
2-10
MESSAGE
No help for that command. (DBWARN 706)
HELP keywords are GENERAL, MAIN, OBJECT, and SUMMARY. Type
'//' to leave SQLGEN HELP.
CAUSE
An unrecognized command was entered for HELP.
ACTION
Enter a valid SQLGEN command at the HELP prompt.
MESSAGE
No View Names qualify for specified owner. (DBWARN 707)
CAUSE
The entered view name does not match any of the owner names
in the DBEnvironment.
ACTION
Enter a valid view name from the DBEnvironment.
MESSAGE
No owner names match the entered Owner Name. (DBWARN 711)
CAUSE
The entered Owner name does not match any of the Owner
names in the DBEnvironment.
ACTION
Enter a valid owner name from the DBEnvironment.
MESSAGE
No owners qualify for specified generate command. (DBWARN
712)
CAUSE
The owner name or DBEFileSet name entered does not match
any owner names or DBEFileSet names in the DBEnvironment.
ACTION
Reissue the command specifying valid Owner names or
DBEFileSet names found in the DBEnvironment.
MESSAGE
Unacceptable object name entered. (DBWARN 713)
For information on object names, type 'HELP OBJECT' at the
SQLGEN prompt.
CAUSE
An invalid object name was entered.
ACTION
Reissue the command specifying a valid object name. If more
detailed information is needed, issue the HELP command to
illustrate valid object names.
ALLBASE/SQL Warning Messages
714
715
716
717
719
MESSAGE
Unacceptable null indicator entered. (DBWARN 714)
Default null indicator used instead.
CAUSE
An invalid null indicator was entered.
ACTION
The default null indicator \?" was used. No additional user
response is necessary.
MESSAGE
User needs to have DBA authority to use SQLGEN. (DBWARN
715) Terminating the DBE session.
CAUSE
User does not have DBA authority to the DBEnvironment.
ACTION
Before using SQLGEN, the user must obtain DBA authority.
MESSAGE
No SQL commands generated. (DBWARN 716)
CAUSE
The executed SQLGEN command did not generate any
commands which were put into the Schema File.
ACTION
No response is necessary. If SQL commands should have been
generated, check for misspelled object names, etc.
MESSAGE
Please check object names entered. (DBWARN 717)
For information on object names, type 'HELP OBJECT' at the
SQLGEN prompt.
CAUSE
The entered object name may not have been correct.
ACTION
Reissue the command using the correct object name. Use the
HELP command to obtain more information on object names.
MESSAGE
No DBE session has been started. (DBWARN 719)
CAUSE
A RELEASE statement was issued on a session that had not been
started yet.
ACTION
Use the STARTDBE statement to start a DBEnvironment
session.
ALLBASE/SQL Warning Messages
2-11
721
723
724
725
730
MESSAGE
ALLBASE/SQL error occurred. Recovering file ! (DBWARN
721)
CAUSE
An error in executing an ALLBASE/SQL command occurred
while the Schema File was being modied.
ACTION
No response is necessary. The Schema File will be recovered to
the state prior to the SQLGEN command execution.
MESSAGE
Illegal character encountered in file name. (DBWARN 723)
CAUSE
An illegal character was entered in the le name.
ACTION
Re-type the le name without the illegal character.
MESSAGE
Designated Schema File has been purged from system.
(DBWARN 724) Will attempt to rebuild the Schema File.
CAUSE
The designated Schema File was non-existent when SQLGEN
tried to open the le. Will attempt to rebuild the Schema File.
ACTION
No response is necessary. SQLGEN will attempt to build a new
Schema File.
MESSAGE
Object name entered is too long. It will be truncated.
(DBWARN 725)
CAUSE
The object name entered was longer than 20 bytes.
ACTION
Enter a valid object name no more than 20 bytes in length.
MESSAGE
Native catalog not available. Using n-computer catalog.
(DBWARN 730)
CAUSE
The LANG environment variable was not set
or
the message catalog 'hpsqlcat' was not found in the
/usr/lib/nls/$LANG directory.
ACTION
If native language support is desired, verify that the LANG
environment variable is set correctly
or
contact your system administrator.
2-12
ALLBASE/SQL Warning Messages
731
732
733
736
1681
MESSAGE
Unable to load all native language information. (DBWARN
731)
CAUSE
There was a problem loading the native language responses from
the message catalog. Local language responses in the message
catalog were incorrect. Only default language responses will be
used.
ACTION
Contact your system administrator.
MESSAGE
User language and DBE language differ. (DBWARN 732)
CAUSE
The user's LANG environment variable and the DBEnvironment's
language are dierent.
ACTION
Exit SQLGEN. Set your LANG environment variable to match
the DBEnvironment language, then invoke SQLGEN.
MESSAGE
SQLGEN cannot be used on remote DBEnvironments. (DBWARN
733)
CAUSE
SQLGEN cannot access remote DBEnvironments.
ACTION
Do not execute SQLGEN on a remote DBEnvironment.
MESSAGE
No Users qualify for specified generate command. (DBWARN
736)
CAUSE
No users had the authority for the specied command.
ACTION
Check the authorization requirements.
MESSAGE
Local catalog is inaccessible. Default catalog in use.
(DBWARN 1681)
CAUSE
The ALLBASE/SQL message catalog corresponding to your
language cannot be accessed, probably because it does not exist.
ACTION
Contact your system administrator.
ALLBASE/SQL Warning Messages
2-13
1800
1801
1802
1803
1804
2-14
MESSAGE
Non-standard command or extension. (DBWARN 1800)
CAUSE
This is an ALLBASE/SQL extension to the ANSI SQL/89
standard.
ACTION
Do not use this command or extension if portability is a concern.
MESSAGE
Non-standard extension, label (!) needs to be preceded by
a COLON. (DBWARN 1801)
CAUSE
This is an ALLBASE/SQL extension to the ANSI SQL/89
standard.
ACTION
Add the colon in the front of the label if portability is a concern.
MESSAGE
Non-standard extension, lower case keyword (!) is used.
(DBWARN 1802)
CAUSE
Lower case keywords are not allowed in the ANSI SQL/89
standard.
ACTION
Use upper case keywords if portability is a concern.
MESSAGE
Non-standard extension, identifier (!) exceeds maximum
length of 18 bytes. (DBWARN 1803)
CAUSE
Identier exceeds maximum allowed in ANSI SQL/89 standard.
ACTION
Do not use this identier length if portability is a concern.
MESSAGE
Use of multiple DISTINCTs within a query or subquery is a
non-standard extension. (DBWARN 1804)
CAUSE
Allowing multiple distincts in a query or subquery is an
ALLBASE/SQL extension to the ANSI SQL/89 standard.
ACTION
Do not use this statement if portability is a concern.
ALLBASE/SQL Warning Messages
1805
1806
1807
1808
2005
MESSAGE
DDL statement outside a CREATE SCHEMA statement is a
non-standard extension. (DBWARN 1805)
CAUSE
ANSI SQL/89 requires DDL commands to be within a CREATE
SCHEMA AUTHORIZATION statement.
ACTION
Place all DDL commands within the CREATE SCHEMA
statement if portability is a concern.
MESSAGE
Use of keyword as an identifier is a non-standard
extension. (DBWARN 1806)
CAUSE
Use of keywords as identiers is an ALLBASE/SQL extension to
the ANSI SQL/89 standard.
ACTION
Do not use keywords as identiers if portability is a concern.
MESSAGE
Access to SYSTEM/CATALOG tables/views is a non-standard
extension. (DBWARN 1807)
CAUSE
ALLBASE/SQL system/catalog views and tables are
non-standard objects.
ACTION
Do not access these objects if portability is a concern.
MESSAGE
An object with owner (!) not equal to schema name (!) is a
non-standard extension. (DBWARN 1808)
CAUSE
This is an ALLBASE/SQL extension to the ANSI SQL/89
standard.
ACTION
Modify the syntax if portability is a concern.
MESSAGE
The index dropped is a clustering index. (DBWARN 2005)
CAUSE
The index you just dropped with the DROP INDEX statement
was created with the CLUSTERED attribute.
ACTION
No action is necessary.
ALLBASE/SQL Warning Messages
2-15
2006
2007
2008
2010
2011
2-16
MESSAGE
User ! already has ! authorization. (DBWARN 2006)
CAUSE
You tried to grant an authorization to a user that already has
that authorization.
ACTION
No action is necessary.
MESSAGE
User ! already has ! authorization on !.!. (DBWARN 2007)
CAUSE
You tried to grant authority on a table or a module to a user
that had already been granted authority on the specied table or
module. Either you granted the table authority before, or you are
the OWNER of the table or a DBA (and so you will be able to
revoke it even if you are not the grantor of it).
ACTION
No action is necessary.
MESSAGE
User ! already has ! authorization on !.!.!. (DBWARN 2008)
CAUSE
You tried to grant authority on a specic column to a user that
had already been granted authority on the specied column.
Either you granted the column authority before, or you are the
OWNER of the table or a DBA (and so you will be able to revoke
it even if you are not the grantor of it).
ACTION
No action is necessary.
MESSAGE
A transaction in progress was aborted. (DBWARN 2010)
CAUSE
You issued a RELEASE or STOP DBE statement without issuing
a COMMIT WORK or ROLLBACK WORK statement rst.
ACTION
No action is necessary.
MESSAGE
Use SQLUtil to purge physical file !. (DBWARN 2011)
CAUSE
When you issue a DROP DBEFILE statement, the actual
physical le is not deleted; it is only deleted from the system
catalog.
ACTION
Use the SQLUtil PURGEFILE command to purge the physical
le.
ALLBASE/SQL Warning Messages
2012
2014
2015
2016
MESSAGE
DBEFile already of specified DBEFile type. (DBWARN 2012)
CAUSE
The DBEFile you attempted to ALTER was already of the
specied type.
ACTION
No action is necessary.
MESSAGE
Module !.! not found. (DBWARN 2014)
CAUSE
The module specied in the EXECUTE or DROP MODULE
statement does not exist.
ACTION
Check your spelling. Ask your database administrator to check
the SYSTEM.SECTION view to make sure that the module
exists in the DBEnvironment to which the application is
connected.
MESSAGE
Row size of table !.! exceeds ! bytes. (DBWARN 2015)
CAUSE
The row size of the table you created exceeds the maximum
number of bytes.
ACTION
No action necessary. An error will occur only if you attempt an
operation that causes the row length of the table to exceed the
maximum number of bytes.
MESSAGE
Length of index ! on table !.! exceeds ! bytes. (DBWARN
2016 )
CAUSE
The index that you created exceeds the maximum key length and
contains a VARCHAR column.
ACTION
No action is necessary as long as the length of the VARCHAR
data does not cause the maximum key length to be exceeded.
The key length is determined using the actual data length in the
VARCHAR column. If the maximum key length is exceeded, an
error will occur when the index is accessed.
ALLBASE/SQL Warning Messages
2-17
2017
MESSAGE
The data updated/deleted is in the RC/RU transaction.
(DBWARN 2017)
CAUSE
You updated or deleted data in the transaction which is started
in RC or RU mode.
ACTION
If you are using a non-cursor UPDATE or DELETE statement,
you may ignore this message.
If you are using the UPDATE/DELETE WHERE CURRENT
statement, ALLBASE/SQL only guarantees that the data still
satises the cursor denition. To guarantee integrity, you might
wish to use the REFETCH statement to validate the data before
you actually update/delete the data.
2018
2019
2-18
MESSAGE
Length of hash key on table !.! exceeds ! bytes. (DBWARN
2018)
CAUSE
The key length of the hash dened on the table exceeds the
maximum key length and the key contains a VARCHAR column.
ACTION
No action is necessary as long as the actual length of the
VARCHAR data does not cause the maximum key length to be
exceeded. The key length is determined using the actual data
length in the VARCHAR column. If the maximum key length is
exceeded, an error will occur when the hash structure is accessed.
MESSAGE
ASCII definition of view !.! not available for storage.
(DBWARN 2019)
CAUSE
The stored module being executed contains a CREATE VIEW
that was prepared or preprocessed before the existence of the
SYSTEM.VIEWDEF table. Therefore, it is not possible to store
the select string that denes the view.
ACTION
If it is important that the ASCII view denition be stored, use
the PREPARE statement through ISQL to create a new version
of the module containing the CREATE VIEW statement or
preprocess the program again. Refer to the ALLBASE/SQL
Reference Manual for information on the PREPARE statement.
ALLBASE/SQL Warning Messages
2020
2021
2023
2025
MESSAGE
DBEnvironment corruption suspected - Rollforward recovery
required. (DBWARN 2020)
CAUSE
An error may have caused the DBEnvironment to be corrupted.
An additional message will be returned.
ACTION
Refer to the cause and action of the additional message. Do
not perform additional transactions at this time. Contact
your database administrator for rollforward recovery on the
DBEnvironment.
MESSAGE
Device name is ignored on HP-UX system. (DBWARN 2021)
CAUSE
The CREATE DBEFile command contained a device
specication. A device specication is only applicable to
MPE/iX.
ACTION
Ignore the warning, or resubmit the command without a device
specication.
MESSAGE
Please close all open scans before proceeding with RESUME.
(DBWARN 2023)
CAUSE
CREATE DBEFile command contained a DEVICE specication.
The MPE/iX system where the replicated database resides
does not have a volume with this name. DBEFile is create on
whatever volume the system chooses.
ACTION
Ignore the warning, or MOVE the DBEFile to a desired device
using SQLUtil.
MESSAGE
User ! has no grantable authority on !.!. (DBWARN 2025)
CAUSE
You issued a GRANT ALL statement but have no Owner or
DBA authority and have no grantable privileges on the table.
Nothing was granted.
ACTION
No action required.
ALLBASE/SQL Warning Messages
2-19
2026
2027
2028
2029
2-20
MESSAGE
REVOKE CASCADE has dropped a view or foreign key. (DBWARN
2026)
CAUSE
A view or foreign key depended on the SELECT or
REFERENCES privilege being revoked, so REVOKE CASCADE
dropped the dependent item.
ACTION
Rollback will recover the item if it needs recovery; otherwise, no
action is necessary.
MESSAGE
Column ! not found in table/view !.!. (DBWARN 2027)
CAUSE
A column included in a column-level GRANT was not found in
the table or view specied.
ACTION
If the column was mis-spelled, revoke that column authority and
grant on the correct column.
MESSAGE
User ! already has ! authorization on columns of !.! from a
different grantor. (DBWARN 2028)
CAUSE
Your GRANT of a table level authority has overridden one
performed by another grantor. The column authorities given by
that grantor are removed, and replaced with your table level
authorities (with you as the grantor).
ACTION
None necessary. The other grantor will not be able to revoke this
table level authority.
MESSAGE
User ! does not have any explicit authority on !.!.
(DBWARN 2029)
CAUSE
REVOKE ALL failed to nd any applicable authorities for the
given user.
ACTION
None necessary. REVOKE ALL will only include those
authorities which the revoker is authorized to revoke, so the user
may still have authorities from other grantors. Owner and DBA
are authorized to revoke all authorities.
ALLBASE/SQL Warning Messages
2030
2031
2040
2041
2042
MESSAGE
ALLBASE/SQL could not predrop user shared memory. HP-UX
errno (!) (DBWARN 2030)
CAUSE
There was an abnormal termination of an application and the
allocated shared memory still remains on the system.
ACTION
Refer to the system administration manual.
MESSAGE
Remove shared memory manually in case of abnormal
terminations. (DBWARN 2031)
CAUSE
There was an abnormal termination of an application and the
allocated shared memory still remains on the system.
ACTION
Contact your system administrator to remove the shared memory.
MESSAGE
Character string truncation during storage in host
variable. (DBWARN 2040)
CAUSE
A host variable character string was shorter than a character
column in the select list.
ACTION
Check the string returned to see if it needs to be longer in order
to capture all necessary information from the column. If so,
modify the declaration of the datatype.
MESSAGE
NULL values eliminated from the argument of an aggregate
function. (DBWARN 2041)
CAUSE
A NULL value occurred in a column where an aggregate (SUM,
AVG, MAX, MIN, COUNT) was evaluated, but was dropped
from the computation.
ACTION
Determine whether the information was needed for correct
computation. If it was, set the NULL column to the needed
value. To prevent future lapses, change the column to be NOT
NULL if possible.
MESSAGE
ADD_MONTHS result adjusted to last day of month. (DBWARN
2042)
CAUSE
Result of ADD MONTHS function was an invalid date, which
resulted in the day being adjusted to the last day of the month.
ACTION
No action required.
ALLBASE/SQL Warning Messages
2-21
2043
2044
2045
2046
2050
2-22
MESSAGE
Binary literal truncation during insert on column !.
(DBWARN 2043)
CAUSE
The binary input is longer than the column denition.
ACTION
No action is necessary; however, the extra data is lost.
MESSAGE
DEFAULT USER is specified, corresponding column length
should be at least 20 characters long. (DBWARN 2044)
CAUSE
You entered a column length less than 20 bytes.
ACTION
No action necessary.
MESSAGE
DEFAULT 'literal' truncated, length ! exceeds column
length !. (DBWARN 2045)
CAUSE
You specied a default constant length which is longer than the
column length dened when the table was created.
ACTION
Dene a default value whose length will not exceed the
corresponding column length.
MESSAGE
String concatenation result is truncated. (DBWARN 2046)
CAUSE
Result length of string concatenation exceeds the maximum.
ACTION
No action needed.
MESSAGE
LONG column data exceeds defined length. Truncated.
(DBWARN 2050)
CAUSE
The actual long column data is longer than the dened length.
The long column data was truncated.
ACTION
No action is necessary.
ALLBASE/SQL Warning Messages
2052
2053
2054
MESSAGE
Sort length of UNION may exceed maximum allowed ! bytes.
(DBWARN 2052)
CAUSE
The UNION command species a number of columns whose total
sort tuple length exceeds the maximum allowable and contains a
VARCHAR column.
ACTION
No action is necessary as long as the length of the VARCHAR
data does not cause the maximum sort tuple length to be
exceeded. The sort tuple length is determined using the actual
data length in the VARCHAR column. If the maximum sort
tuple length is exceeded, an error will occur when the sorting is
performed.
MESSAGE
Sort length of ORDER BY/GROUP BY/DISTINCT/UNION may
exceed maximum allowed ! bytes. (DBWARN 2053)
CAUSE
The ORDER BY, GROUP BY, DISTINCT, or UNION clause of
the SELECT statement species a number of columns whose total
sort tuple length exceeds the maximum allowable and contains a
VARCHAR column.
ACTION
No action is necessary as long as the length of the VARCHAR
data does not cause the maximum sort tuple length to be
exceeded. The sort tuple length is determined using the actual
data length in the VARCHAR column. If the maximum sort
tuple length is exceeded, an error will occur when the sorting is
performed. You can calculate the maximum sort tuple length
from the formula given in Appendix A of the ALLBASE/SQL
Database Administration Guide .
MESSAGE
Sort length of sort merge join may exceed maximum allowed !
bytes. (DBWARN 2054)
CAUSE
The sort merge join query species a number of columns whose
total sort tuple length exceeds the maximum allowable and
contains a VARCHAR column.
ACTION
No action is necessary as long as the length of the VARCHAR
data does not cause the maximum sort tuple length to be
exceeded. The sort tuple length is determined using the actual
data length in the VARCHAR column. If the maximum sort
tuple length is exceeded, an error will occur when the sorting is
performed.
ALLBASE/SQL Warning Messages
2-23
2056
2059
2060
2061
2062
2-24
MESSAGE
A cursor opened using KEEP CURSOR WITH NOLOCKS requires
sorting. You must ensure data integrity yourself. (DBWARN
2056)
CAUSE
You are using the KEEP CURSOR WITH NOLOCKS option on
a cursor requiring a sort operation such as the ORDER BY clause
or a join.
ACTION
You need to verify that the data is correct if you want to do an
update where your cursor is located.
MESSAGE
There are deferred UNIQUE/PRIMARY KEY and/or FOREIGN KEY
constraint violations that may not be resolvable. (DBWARN
2059)
CAUSE
There are UNIQUE/PRIMARY KEY constraint or FOREIGN
KEY constraint violations pending at deferred constraint checking
mode.
ACTION
Avoid truncating or dropping data when there are deferred
constraint violations.
MESSAGE
Audit logging already disabled. (DBWARN 2060)
CAUSE
You specied a redundant DISABLE AUDIT LOGGING
statement.
ACTION
Check the sequence of operations.
MESSAGE
Audit logging already enabled. (DBWARN 2061)
CAUSE
You specied a redundant ENABLE AUDIT LOGGING
statement.
ACTION
Check the sequence of operations.
MESSAGE
Partition not found. (DBWARN 2062)
CAUSE
A non-existent partition id was specied when retrieving
synchronization checkpoint data.
ACTION
Check and correct the specied partition ids.
ALLBASE/SQL Warning Messages
2063
2065
2066
2067
MESSAGE
Some partitions (but not all) failed on Open_Log_Scan.
(DBWARN 2063)
CAUSE
Open Log Scan failed to open the scan for some of the specied
partitions.
ACTION
Check the per partition return codes.
MESSAGE
DML ATOMICITY already set to ! level. (DBWARN 2065)
CAUSE
The DML ATOMICITY is already set to row or statement level.
ACTION
Determine whether the SET DML ATOMICITY statement is
needed.
MESSAGE
! constraints already set to !. (DBWARN 2066)
CAUSE
Constraints specied were already set to deferred or immediate.
ACTION
Determine whether the SET CONSTRAINTS statement is
needed.
MESSAGE
User timeout exceeds maximum timeout; maximum assumed (!
seconds). (DBWARN 2067)
CAUSE
The specied user timeout value is greater than the maximum
timeout value limit. When this error occurs, the user timeout
value is automatically set to the maximum timeout limit.
ACTION
Set the user timeout to a value less than or equal to the
maximum timeout limit
or
set the maximum timeout limit to a value greater than or equal
to the desired user timeout value.
2068
MESSAGE
Length of substring requested ! starting at ! exceeds
length of source string. (DBWARN 2068)
CAUSE
In the SUBSTRING function, (Length - StartPosition + 1) is
greater than the length of the SourceString parameter.
ACTION
No action is necessary. You should be aware that the substring
returned is shorter than expected.
ALLBASE/SQL Warning Messages
2-25
2069
2070
2071
2072
2073
2-26
MESSAGE
Length of substring requested ! exceeds maximum length
allowed !. (DBWARN 2069)
CAUSE
The length of the substring requested by the SUBSTRING
function is longer than the maximum length allowed.
ACTION
No action is necessary. You should be aware that the substring
returned is shorter than expected and that truncation may occur.
MESSAGE
The transaction was committed, since it is read only.
(DBWARN 2070)
CAUSE
The transaction that was being prepared for COMMIT was found
to have no associated updates. The transaction was therefore
committed.
ACTION
No action needed.
MESSAGE
The transaction was aborted due to deadlock. (DBWARN
2071)
CAUSE
A deadlock situation caused the transaction to abort.
ACTION
Refer to the ALLBASE/SQL Advanced Application Programming
Guide to determine ways to avoid deadlock situations.
MESSAGE
The transaction was aborted due to integrity violation.
(DBWARN 2072)
CAUSE
An unresolved integrity violation caused the transaction to abort.
ACTION
Check the application logic to ensure that all uniqueness and
referential constraint violations are resolved before attempting to
commit the transaction.
MESSAGE
The transaction was aborted due to timeout. (DBWARN 2073)
CAUSE
A timeout occurred while the application was waiting for a
resource.
ACTION
Check the application for possible cross-database deadlocks.
ALLBASE/SQL Warning Messages
2074
2075
2076
2077
2078
2079
MESSAGE
The transaction was aborted. (DBWARN 2074)
CAUSE
A database internal problem caused the transaction to abort.
ACTION
Retry the transaction.
MESSAGE
Cannot revalidate Section !.!(!). (DBWARN 2075)
CAUSE
Either you have recently performed a migration or you have
installed a module that was created on an earlier release of
ALLBASE/SQL.
ACTION
Preprocess or run the application to validate module. After you
have validated the module successfully in this manner, you will
then be able to use the VALIDATE statement on this module.
MESSAGE
Failed to validate module !.!. (DBWARN 2076)
CAUSE
The module specied does not exist.
ACTION
Check module name in the SYSTEM.SECTION view or with the
ISQL LIST INSTALL command.
MESSAGE
Failed to validate module !.!.(!). (DBWARN 2077)
CAUSE
An error occurred during validation process.
ACTION
Check the other error messages generated.
MESSAGE
No modules to be validated. (DBWARN 2078)
CAUSE
There are no modules to be validated.
ACTION
You specied the ALL option, but there are no modules to be
validated.
MESSAGE
Failed to validate procedure !.!. (DBWARN 2079)
CAUSE
A procedure specied by name in the VALIDATE statement does
not exist.
ACTION
Check your spelling, and verify the procedure owner and name,
then reissue the VALIDATE statement.
ALLBASE/SQL Warning Messages
2-27
2080
2081
2082
2083
2-28
MESSAGE
No procedure(s) to be validated. (DBWARN 2080)
CAUSE
You issued a VALIDATE ALL PROCEDURES statement, but
there are no procedures to be validated.
ACTION
No action is required.
MESSAGE
Warning(s) occurred processing statement ! during
procedure creation/validation. (DBWARN 2081)
CAUSE
An SQL statement in the procedure could not be compiled at
procedure creation or validation time. The procedure was created
or validated, but the section corresponding to the statement was
stored as an invalid section.
ACTION
Use the statement number in the message to determine which
procedure statement generated the warning. Refer to the
accompanying message or messages for more information.
MESSAGE
LABEL ! defined but not used. (DBWARN 2082)
CAUSE
A procedure statement label is not referenced in any GOTO
statement in the procedure.
ACTION
If this warning is accompanied by DBERR 2237, check your
spelling. Otherwise, the superuous label may be removed.
MESSAGE
Multiple rows returned in procedure. (DBWARN 2083)
CAUSE
A non-cursor SELECT in a procedure returned multiple rows.
Only the rst row of values was returned in the local variables or
parameters.
ACTION
Use a cursor in procedures for any query that will return more
than one row of data.
ALLBASE/SQL Warning Messages
2084
MESSAGE
Procedure returns multiple row result set(s). (DBWARN
2084)
CAUSE
A procedure that returns multiple row result sets was executed
directly, without using a procedure cursor.
or
A procedure that returns multiple row result sets was specied in
a CREATE RULE statement.
ACTION
If retrieval of the result sets is not required by the application,
no action is required. If retrieval is required, you must use a
procedure cursor.
or
No action is required.
2085
2087
2090
MESSAGE
Section !.! (!) being revalidated due to obsolete
execution code. (DBWARN 2085)
CAUSE
Obsolete execution code is causing the specied section to be
revalidated.
ACTION
No action is required.
MESSAGE
View !.! has been dropped. (DBWARN 2087)
CAUSE
The specied view has been dropped.
ACTION
No action is required if the view is no longer required.
MESSAGE
RAISE ERROR text truncated, length ! exceeds maximum
allowed (!). (DBWARN 2090)
CAUSE
The text given to the RAISE ERROR statement exceeded the
maximum allowed length.
ACTION
No action is necessary; however, the extra text is not returned.
ALLBASE/SQL Warning Messages
2-29
2091
2092
2093
2094
2095
2096
2-30
MESSAGE
Rule !.! fired on ! statement. (DBWARN 2091)
CAUSE
The named rule red while PRINTRULES was SET ON due to
execution of a statement of the given type (INSERT, UPDATE,
or DELETE).
ACTION
No action is necessary.
MESSAGE
Rules already disabled. (DBWARN 2092)
CAUSE
DISABLE RULES statement was in eect when this DISABLE
RULES statement was issued.
ACTION
No action is necessary.
MESSAGE
Rules already enabled. (DBWARN 2093)
CAUSE
ENABLE RULES statement was in eect when this ENABLE
RULES statement was issued.
ACTION
No action is necessary.
MESSAGE
PRINTRULES already ON. (DBWARN 2094)
CAUSE
SET PRINTRULES ON statement was in eect when this SET
PRINTRULES ON statement was issued.
ACTION
No action is necessary.
MESSAGE
PRINTRULES already OFF. (DBWARN 2095)
CAUSE
SET PRINTRULES OFF statement was in eect when this SET
PRINTRULES OFF statement was issued.
ACTION
No action is necessary.
MESSAGE
! on DBEFileSet ! already granted for !. (DBWARN 2096)
CAUSE
The SECTIONSPACE/TABLESPACE authority already granted
to the user.
ACTION
Delete the command.
ALLBASE/SQL Warning Messages
2097
2098
2344
2345
2531
MESSAGE
Default ! on DBEFileSet ! already set for !. (DBWARN 2097)
CAUSE
The default SECTIONSPACE/TABLESPACE authority already
set to the user.
ACTION
Delete the command.
MESSAGE
! on DBEFileSet ! is not granted for !. Default DBEFileSet
! used. (DBWARN 2098)
CAUSE
You do not have authority to store a table or section in the
specied DBEFileSet. The table or section was added to the
default DBEFileSet instead.
ACTION
No action is necessary. However, if it is not desirable to have the
table or section in the default DBEFileSet, then the table or
section can be dropped and recreated in another DBEFileSet for
which you do have authority to store the table or section.
MESSAGE
User ! already has INSTALL AS ! authority. (DBWARN 2344)
CAUSE
You granted INSTALL AS authority to a user who already has
the authority.
ACTION
No action required.
MESSAGE
User ! already has general INSTALL authority. (DBWARN
2345)
CAUSE
You granted INSTALL authority to a user who already has the
authority.
ACTION
No action required.
MESSAGE
Cursor, associated with the aborted query has been closed.
(DBWARN 2531)
CAUSE
The cursor has been closed.
ACTION
No action required for the closed cursor. Check the aborted
query.
ALLBASE/SQL Warning Messages
2-31
2880
3230
3231
3232
3233
5000
2-32
MESSAGE
! on DBEFileSet ! is not granted for !. Default DBEFileSet
used. (DBWARN 2880)
CAUSE
The authority is not previously granted to the user.
ACTION
Grant the authority to the user.
MESSAGE
SQLCore could not use the plan as specified. (DBWARN 3230)
CAUSE
The plan you specied is not applicable to the query.
ACTION
Use GENPLAN command to verify the plan produced by
SQLCore and reset SETOPT statement if it is necessary.
MESSAGE
The join order specified in SETOPT does not match with the
prefix join order of outer join query. (DBWARN 3231)
CAUSE
The plan you specied is not applicable to the query.
ACTION
Use GENPLAN command to verify the plan produced by
SQLCore and reset SETOPT statement if it is necessary.
MESSAGE
Section (!) could not be found on Module !.!. (DBWARN
3232)
CAUSE
The section you specied was not found in the Module.
ACTION
Check your source le to get the correct section number.
MESSAGE
Section (!) could not be found on Procedure !.!. (DBWARN
3233)
CAUSE
The section you specied was not found in the Procedure.
ACTION
Check your source le to get the correct section number.
MESSAGE
! (DBWARN 5000)
CAUSE
Message number 5000 is provided for passing the argument of a
procedure's PRINT statement back to the procedure caller.
ACTION
Take whatever action is recommended by the procedure writer.
ALLBASE/SQL Warning Messages
8001
8002
8003
8004
8005
MESSAGE
Unable to load all local response options. (DBWARN 8001)
CAUSE
One or more of the local response options was missing from the
message catalog or response contained invalid data.
ACTION
Contact your system administrator.
MESSAGE
Local response options are not unique. (DBWARN 8002)
CAUSE
The local response options in the message catalog are not unique.
ACTION
Contact your system administrator.
MESSAGE
Unable to upshift multi-byte native language string.
(DBWARN 8003)
CAUSE
SQLUtil was unable to upshift a character string, probably
because the string contains one or more invalid bytes.
ACTION
Issue your command again, specifying valid input.
MESSAGE
Unable to trim trailing blanks from multi-byte native
language string. (DBWARN 8004)
CAUSE
SQLUtil was unable to trim trailing blanks from a character
string, probably because the string contains one or more invalid
bytes.
ACTION
Issue your command again, specifying valid input.
MESSAGE
Unable to truncate multi-byte native language string.
(DBWARN 8005)
CAUSE
SQLUtil was unable to truncate a character string, probably
because the string contains one or more invalid bytes.
ACTION
Issue your command again, specifying valid input.
ALLBASE/SQL Warning Messages
2-33
8006
8007
8248
10600
10601
2-34
MESSAGE
Cannot obtain user's language id. Assuming !. (DBWARN
8006)
CAUSE
Your LANG environment variable is set to a language that is not
congured, or the support les for your language are missing.
ACTION
Contact your system administrator or set again with valid
language.
MESSAGE
Local message catalog is not available. Set to ! message
catalog. (DBWARN 8007)
CAUSE
The message catalog le corresponding to your language cannot
be accessed, probably because it does not exist.
ACTION
Contact your system administrator.
MESSAGE
Maximum Log files exceeded, last log name ignored.
(DBWARN 8248)
CAUSE
You entered more than 34 log le names when entering the log
le list for the WRAPDBE command.
ACTION
Check list to see what log les can be dropped from the list. The
list must contain 34 or fewer entries.
MESSAGE
No ending single quote: Single quote inserted. (DBWARN
10600)
CAUSE
One of your statements does not include an ending single quote.
ACTION
No action is necessary. The preprocessor inserted the required
ending single quote.
MESSAGE
No ending double quote: Double quote inserted. (DBWARN
10601)
CAUSE
An ending double quote was missing in one of your statements.
ACTION
No action is necessary. The preprocessor inserted the required
ending double quote.
ALLBASE/SQL Warning Messages
10603
10604
10605
10606
10607
MESSAGE
Cannot obtain user's language. Default language !
assumed. (DBWARN 10603)
CAUSE
The environment variable, LANG, is set to an unrecognized
language.
ACTION
Reset LANG to a supported language.
MESSAGE
Source line longer than allowed. Source line truncated.
(DBWARN 10604)
CAUSE
A source line is longer than supported.
ACTION
Consult the application programming guide for maximum allowed
source line length.
MESSAGE
User's and DBE's languages are different. (DBWARN 10605)
CAUSE
The environment variable, LANG, and the language of the
DBEnvironment are dierent.
ACTION
Set LANG to the proper language, if using native data.
MESSAGE
Native version of ALLBASE/SQL message catalog not
accessible. (DBWARN 10606)
CAUSE
The native version of hpsqlcat is not found under
/usr/lib/nls/$LANG.
ACTION
Install native hpsqlcat, if required.
MESSAGE
Program name exceeds maximum module name length.
Truncated to 20 bytes. (DBWARN 10607)
CAUSE
The program name is used as the module name when none is
specied in the program invocation line. A program name was
specied which is longer than the maximum allowed module name
length of 20 bytes.
ACTION
Modify the source le to specify a program name with a length of
20 bytes or less.
ALLBASE/SQL Warning Messages
2-35
10608
10609
10610
10611
10612
10613
2-36
MESSAGE
ALLBASE/SQL preprocessor warning. (DBWARN 10608)
CAUSE
A warning condition was detected by the preprocessor.
Additional warning messages will be returned.
ACTION
Refer to the cause and action of the additional warning messages.
MESSAGE
ALLBASE/SQL statement parser warning. (DBWARN 10609)
CAUSE
A warning condition was detected by the statement parser.
Additional warning messages will be returned.
ACTION
Refer to the cause and action of the additional warning messages.
MESSAGE
ALLBASE/SQL query processor warning. (DBWARN 10610)
CAUSE
A warning condition was detected by the query processor.
Additional warning messages will be returned.
ACTION
Refer to the cause and action of the additional warning messages.
MESSAGE
Cannot obtain user's language. Default language
NATIVE-3000 assumed. (DBWARN 10611)
CAUSE
The environment variable, LANG, is set to an unrecognized
language.
ACTION
Set LANG to a supported language.
MESSAGE
Native version of ALLBASE/SQL message catalog not
accessible. (DBWARN 10612)
CAUSE
The native version of the hpsqlcat message catalog is not found
under /usr/lib/nls/$LANG.
ACTION
Install the native version of hpsqlcat.
MESSAGE
User's and DBE's languages are different. (DBWARN 10613)
CAUSE
The environment variable, LANG, and the language of the
DBEnvironment are dierent.
ACTION
Set LANG to the proper language.
ALLBASE/SQL Warning Messages
10614
10621
10622
10700
10701
MESSAGE
Not enough space to return parse information. (DBWARN
10614)
CAUSE
The buer space passed to hold the returned parse information
was not sucient.
ACTION
Increase the buer space.
MESSAGE
***REDEFINES clause: Non-standard host variable
declaration. (DBWARN 10621)
CAUSE
A possible cause is that the REDEFINE clause was used.
ACTION
No action required. Only elementary level items are allowed in
ALLBASE/SQL calls. In order to pass an item with subitems
in the COBOL preprocessor, you can use a REDEFINE clause.
However, you will receive a warning because you are using a
non-standard host variable declaration.
MESSAGE
Cannot obtain user's language. Default language C
assumed. (DBWARN 10622)
CAUSE
The user's language is not found.
ACTION
Check the native language parameters.
MESSAGE
Filler added to adjust for odd-byte field. (DBWARN 10700)
CAUSE
The preprocessor generated in the preprocessor output le a
one-byte ller character for an odd-byte host variable declaration
to ensure that the data is aligned on word boundaries.
ACTION
No action is necessary. The preprocessor inserted the required
one-byte ller character in the preprocessor output le.
MESSAGE
Maximum COBOL work length exceeded. Truncated to 30 bytes.
(DBWARN 10701)
CAUSE
A word appears in the COBOL source le which is longer than
the maximum allowed length of 30 bytes.
ACTION
Modify the source le to shorten the word to a length of 30 bytes
or less.
ALLBASE/SQL Warning Messages
2-37
10750
10979
10980
13026
13343
2-38
MESSAGE
'INCLUDE SQLCA' is not declared for embedded SQL
statement. (DBWARN 10750)
CAUSE
You did not include an SQLCA common area in your program.
ACTION
Modify the source le specifying EXEC SQL INCLUDE SQLCA
and re-preprocess your program.
MESSAGE
ALLBASE/SQL query processor error. (DBWARN 10979)
CAUSE
An error condition was detected by the query processor.
Additional error messages will be returned.
ACTION
Refer to the cause and action of the additional error messages.
MESSAGE
Syntax check only due to severe ALLBASE/SQL query
processor error. (DBWARN 10980)
CAUSE
An unrecoverable error condition was detected by the query
processor. Only the syntax of the SQL statement was veried.
Validation of the SQL statement was not performed. Additional
error messages will be returned.
ACTION
Refer to the cause and action of the additional error messages.
MESSAGE
Missing log files from log file list. (DBWARN 13026)
CAUSE
WRAPDBE determined that log les were missing from the log
le list by checking the log sequence numbers. The log le names
can be entered in any order; as long as there is a correct and
continuous sequence; WRAPDBE puts them in the correct order.
ACTION
Check the log sequence numbers that were assigned on the
original DBEnvironment with the SQLUtil SHOWLOG command
to determine if all log les exist in the target area.
MESSAGE
Consistency point may not be exactly enforced by DBCORE.
(DBWARN 13343)
CAUSE
DBCORE is adjusting the consistency point.
ACTION
No action required.
ALLBASE/SQL Warning Messages
20010
20012
MESSAGE
Local catalog is inaccessible. Default catalog in use.
(DBWARN 20010)
CAUSE
The ALLBASE/SQL message catalog corresponding to your
language cannot be accessed, probably because it does not exist.
ACTION
Contact your system administrator.
MESSAGE
*** Bad environment variable MIGLOGSZ. Default log size
used. (DBWARN 20012)
CAUSE
The environment variable MIGLOGSZ has been set to an integer
value that is less than 400 (the default log size)
or
the environment variable MIGLOGSZ has not been set to a valid
integer value.
20014
20300
ACTION
Set the environment variable MIGLOGSZ again, but specify a log
le size that is no less than 400.
MESSAGE
Cannot verify ALLBASE/SQL license. Assuming IMAGE/SQL
(! !) (DBWARN 20014)
CAUSE
An error occurred during processing that determines whether or
not your system is licensed to use ALLBASE/SQL.
ACTION
If you have not purchased a license to use ALLBASE/SQL, no
action is necessary. Otherwise, record as much information as
possible and contact your HP Service Representative or Response
Center, because restrictions imposed by IMAGE/SQL are
currently in eect for your DBEnvironment.
MESSAGE
WARNING - No DBEnvironment has been referenced yet.
(DBWARN 20300).
CAUSE
Either the CREATE DBEFILE or the ADD DBEFILE statement
was issued before a DBEnvironment had been mentioned in a
command.
ACTION
Use either the SHOW 'DBEnvironmentName' VERSION
command or the PREVIEW command to indicate to SQLMigrate
which DBEnvironment should be used for this command.
ALLBASE/SQL Warning Messages
2-39
20550
20570
20580
MESSAGE
WARNING - Before continuing, please verify that a complete
backup of the DBEnvironment exists. (DBWARN 20550)
CAUSE
This warning is issued to insure that you do not accidentally
corrupt a DBEnvironment when using SQLMigrate and you
will be unable to recover your data. If an unexpected error is
encountered during the MIGRATE or PREVIEW command, it is
critical that a backup of the DBEnvironment be available.
ACTION
If you have not made a complete backup of the DBEnvironment,
type No at the prompt to prevent SQLMigrate from continuing.
Make a full backup of the DBEnvironment, and then issue the
MIGRATE or PREVIEW command again.
MESSAGE
WARNING - Table !.! contained the following columns which
are not supported under the target release of ALLBASE/SQL.
(DBWARN 20570)
CAUSE
A backward migration was in progress when this message was
issued. Column types that were only supported under the
newer release of ALLBASE/SQL were present in the user table
mentioned in the warning. The table was dropped during the
migration.
ACTION
If you need to recover the table, the backup version of the
DBEnvironment must be restored. The oending columns must
be eliminated or modied to be of types supported by the target
version before a migration is attempted again.
MESSAGE
WARNING - Views and stored sections created under later
releases of ALLBASE/SQL may not function correctly under
the target version of ALLBASE/SQL. (DBWARN 20580)
CAUSE
This message is issued as a warning whenever a backward
migration occurs.
ACTION
Drop all views created under later releases, and recreate them.
Also drop all stored sections created under later releases, and
either:
INSTALL backup installable module les that were created under
the target version of ALLBASE/SQL,
or
preprocess programs again to obtain stored sections that are
compatible with the target version of ALLBASE/SQL.
2-40
ALLBASE/SQL Warning Messages
20650
20660
20670
MESSAGE
WARNING - Table !.! has been created using the HASH
option, which is not supported under the target version of
ALLBASE/SQL (DBWARN 20650). This table is being dropped.
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
If you need to recover the table, the backup version of the
DBEnvironment must be restored. If you need to transfer this
data to the target release, use the ISQL UNLOAD EXTERNAL
command.
MESSAGE
WARNING - Table !.! has been created using INTEGRITY
CONSTRAINTS, which is not supported under the target
version of ALLBASE/SQL (DBWARN 20660). This table is
being dropped.
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
If you need to recover the table, the backup version of the
DBEnvironment must be restored. If you need to transfer this
data to the target release, use the ISQL UNLOAD EXTERNAL
command.
MESSAGE
WARNING - Table !.! has been created using DEFAULT column
values, which is not supported under the target version of
ALLBASE/SQL (DBWARN 20670). This table is being dropped.
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
If you need to recover the table, the backup version of the
DBEnvironment must be restored. If you need to transfer this
data to the target release, use the ISQL UNLOAD EXTERNAL
command.
ALLBASE/SQL Warning Messages
2-41
20680
20690
20700
20710
2-42
MESSAGE
WARNING - TEMPSPACE ! has been created using the CREATE
TEMPSPACE statement, which is not supported under the
target version of ALLBASE/SQL (DBWARN 20680). This
TEMPSPACE is being dropped.
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
No action is necessary.
MESSAGE
WARNING - Table !.! has been created with a REFERENTIAL
CONSTRAINT on a table that was dropped during the
migration. (DBWARN 20690) Table !.! is being dropped.
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
If you need to recover the table, the backup version of the
DBEnvironment must be restored. If you need to transfer this
data to the target release, use the ISQL UNLOAD EXTERNAL
command.
MESSAGE
WARNING - INDEX has been defined on sixteen (16) columns.
(DBWARN 20700). Index ! defined on table !.! is being
dropped.
CAUSE
In the target release, the maximum number of columns on which
an index may be dened is fteen (15). Functionality that is not
present in the target release has been detected.
ACTION
After migration to the target release, recreate the dropped index
using fewer columns.
MESSAGE
WARNING - DBEFile ! in DBEFileSet ! has been defined using
RAW I/O, which is not supported under the target version of
ALLBASE/SQL (DBWARN 20710).
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
You must use the SQLUtil MOVEFILE command to move this
DBEFile into a standard HP-UX le before a migration can be
attempted.
ALLBASE/SQL Warning Messages
20754
22530
22620
MESSAGE
SET NEWLOG OFF was previously issued. (DBWARN 20754)
CAUSE
The current value of the NEWLOG variable is OFF, so a START
DBE NEWLOG command was not performed during the
MIGRATE command.
ACTION
No action is necessary. If you want a START DBE NEWLOG
command to be performed during future MIGRATE commands,
issue a SET NEWLOG ON command.
MESSAGE
WARNING - Table !.! contains the following columns which
are not supported under the target release of ALLBASE/SQL.
(DBWARN 22530)
CAUSE
A backward migration is being PREVIEWed when this message is
issued. Column types that are only supported under the newer
release of ALLBASE/SQL are present in the user table mentioned
in the warning.
ACTION
The oending columns must be eliminated or modied to be
of types supported by the target version before a migration
is attempted. If they are not removed, then the table will be
dropped during the MIGRATE command.
MESSAGE
WARNING - Table !.! has been created using the HASH
option, which is not supported under the target version of
ALLBASE/SQL (DBWARN 22620). This table will be dropped
during the migration.
CAUSE
A backward migration was PREVIEWED when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
If you need to transfer this data to the target release, use the
ISQL UNLOAD EXTERNAL command.
ALLBASE/SQL Warning Messages
2-43
22630
22640
22650
22670
2-44
MESSAGE
WARNING - Table !.! has been created using INTEGRITY
CONSTRAINTS, which is not supported under the target
version of ALLBASE/SQL (DBWARN 22630). This table will be
dropped during the migration.
CAUSE
A backward migration was PREVIEWED when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
If you need to transfer this data to the target release, use the
ISQL UNLOAD EXTERNAL command.
MESSAGE
WARNING - Table !.! has been created using DEFAULT column
values, which is not supported under the target version of
ALLBASE/SQL (DBWARN 22640). This table will be dropped
during the migration.
CAUSE
A backward migration was PREVIEWED when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
If you need to transfer this data to the target release, use the
ISQL UNLOAD EXTERNAL command.
MESSAGE
WARNING - TEMPSPACE ! has been created using the CREATE
TEMPSPACE statement, which is not supported under the
target version of ALLBASE/SQL (DBWARN 22650). This
TEMPSPACE will be dropped during the migration.
CAUSE
A backward migration was PREVIEWED when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
No action is necessary.
MESSAGE
WARNING - INDEX has been defined on sixteen (16) columns.
(DBWARN 22670). Index ! defined on table !.! will be
dropped during the migration.
CAUSE
A backward migration was PREVIEWED when this message was
issued. In the target release, the maximum number of columns on
which an index may be dened is fteen (15). Functionality that
is not present in the target release has been detected.
ACTION
After migration to the target release, recreate the dropped index
using fewer columns.
ALLBASE/SQL Warning Messages
22680
22690
22695
MESSAGE
WARNING - DBEFile ! in DBEFileSet ! has been defined using
RAW I/O, which is not supported under the target version of
ALLBASE/SQL (DBWARN 22680). SQLMIGRATE will not perform
a migration on the DBEnvironment if this DBEFILE uses RAW
I/O when the MIGRATE command is issued.
CAUSE
A backward migration was PREVIEWED when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
Use the SQLUtil MOVEFILE command to move this DBEFile
into a standard HP-UX le before attempting the migration.
MESSAGE
WARNING - View !.! was not found, so it will not be dropped
during the migration (DBWARN 22690).
CAUSE
A PREVIEW command was in progress when this message was
issued. SQLMigrate could not nd a view that needs to be
dropped during the migration. The DBEnvironment is probably
being migrated a second time (i.e. backward after a forward
migration, or forward after a backward migration) without
performing a START DBE NEWLOG after the rst migration.
ACTION
No action is necessary.
MESSAGE
WARNING - View !.! was not found, so it was not dropped
(DBWARN 22695).
CAUSE
A MIGRATE command was in progress when this message was
issued. SQLMigrate could not nd a view that needs to be
dropped during the migration. The DBEnvironment is probably
being migrated a second time (i.e. backward after a forward
migration, or forward after a backward migration) without
performing a START DBE NEWLOG after the rst migration.
ACTION
No action is necessary.
ALLBASE/SQL Warning Messages
2-45
22700
22710
22720
2-46
MESSAGE
WARNING - View !.! is defined on a table or view that
will be dropped during the migration (DBWARN 22700).
This view will also be dropped. The SELECTSTRING from
SYSTEM.VIEWDEF for this view is: !
CAUSE
A PREVIEW command was in progress when this message was
issued. The view is being dropped because a structure that it is
dependent upon is being dropped.
ACTION
You may wish to recreate the view after the DBEnvironment
has been migrated by typing the command recorded in the
SELECTSTRING.
MESSAGE
WARNING - View !.! is defined on a table or view that is
being dropped (DBWARN 22710). This view is also being
dropped. The SELECTSTRING from SYSTEM.VIEWDEF for this
view is: !
CAUSE
A MIGRATE command was in progress when this message was
issued. The view is being dropped because a structure that it is
dependent upon is being dropped.
ACTION
You may wish to recreate the view after the DBEnvironment
has been migrated by typing the command recorded in the
SELECTSTRING.
MESSAGE
WARNING - Table !.! has been created using CHECK
CONSTRAINTS, which is not supported under the target
version of ALLBASE/SQL (DBWARN 22720). This table will be
dropped during the migration.
CAUSE
A backward migration was PREVIEWED when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
No action is necessary. If you need to transfer this data to the
target release, use the ISQL UNLOAD EXTERNAL command.
ALLBASE/SQL Warning Messages
22730
22740
MESSAGE
WARNING - Table !.! has been created using CHECK
CONSTRAINTS, which is not supported under the target
version of ALLBASE/SQL (DBWARN 22730). This table is
being dropped.
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
If you need to recover the table, the backup version of the
DBEnvironment must be restored. If you need to transfer this
data to the target release, use the ISQL UNLOAD EXTERNAL
command.
MESSAGE
WARNING - Table/view !.! is owned by user HPODBSS, and is
assumed to be part of the ObjectDB product (DBWARN 22740).
ObjectDB is not supported under the target version of
ALLBASE/SQL. This table/view will be dropped during the
migration.
CAUSE
A backward migration was PREVIEWED when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
If the object is a table and you need to transfer this data
to the target release, use the ISQL UNLOAD EXTERNAL
command. If the object is a view, then the SELECTSTRING
from SYSTEM.VIEWDEF for the view will be listed immediately
after this message. You may wish to recreate the view after the
DBEnvironment has been migrated by typing the command
recorded in the SELECTSTRING.
ALLBASE/SQL Warning Messages
2-47
22750
22760
2-48
MESSAGE
WARNING - Table/view !.! is owned by user HPODBSS, and is
assumed to be part of the ObjectDB product (DBWARN 22750).
ObjectDB is not supported under the target version of
ALLBASE/SQL. This table/view is being dropped.
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
If the object is a table and you need to recover the table, the
backup version of the DBEnvironment must be restored. If you
need to transfer this data to the target release, use the ISQL
UNLOAD EXTERNAL command. If the object is a view, then
the SELECTSTRING from SYSTEM.VIEWDEF for the view
will be listed immediately after this message. You may wish to
recreate the view after the DBEnvironment has been migrated by
typing the command recorded in the SELECTSTRING.
MESSAGE
WARNING - Table/view !.! is owned by user CATALOG, which
will become a special user under the target version of
ALLBASE/SQL (DBWARN 22760). New views owned by CATALOG
will be created during the START DBE command under the
target version of ALLBASE/SQL. To ensure that ALLBASE/SQL
is able to create all new views correctly, please take the
following steps using the target version of ALLBASE/SQL:
1) perform a START DBE NEWLOG command (to complete the
migration of this DBEnvironment), 2) perform a DROP TABLE
or DROP VIEW command to drop this table/view, 3) perform
a STOP DBE command, and 4) perform a START DBE command,
to ensure that all new views owned by CATALOG are created
correctly.
CAUSE
A forward migration was either PREVIEWED or in progress
when this message was issued. User data which may cause
unexpected problems within ALLBASE/SQL has been detected.
ACTION
Perform the steps listed in the message.
ALLBASE/SQL Warning Messages
22780
22900
22910
MESSAGE
WARNING - Table/view !.! is owned by user HPODBSS, which
will become a special user under the target version of
ALLBASE/SQL (DBWARN 22780). To ensure that unexpected
problems are not encountered, please take the following
steps using the target version of ALLBASE/SQL: 1) perform
a START DBE NEWLOG command (to complete the migration of
this DBEnvironment), and 2) perform a DROP TABLE or DROP
VIEW command to drop this table/view.
CAUSE
A forward migration was either PREVIEWED or in progress
when this message was issued. User data which may cause
unexpected problems within ALLBASE/SQL has been detected.
ACTION
Perform the steps listed in the message.
MESSAGE
WARNING - Procedure !.! has been detected in the system
catalog (DBWARN 22900). Procedures are not supported
under the target version of ALLBASE/SQL, so this
information will be dropped during the migration.
CAUSE
A backward migration was PREVIEWED when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
No action is necessary.
MESSAGE
WARNING - Procedure !.! has been detected in the system
catalog (DBWARN 22910). Procedures are not supported
under the target version of ALLBASE/SQL, so this
information is being dropped.
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
No action is necessary.
ALLBASE/SQL Warning Messages
2-49
22920
22930
22940
22950
2-50
MESSAGE
WARNING
(DBWARN
version
dropped
- Rule !.! has been detected in the system catalog
22920). Rules are not supported under the target
of ALLBASE/SQL, so this information will be
during the migration.
CAUSE
A backward migration was PREVIEWED when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
No action is necessary.
MESSAGE
WARNING - Rule !.! has been detected in the system catalog
(DBWARN 22930). Rules are not supported under the target
version of ALLBASE/SQL, so this information is being
dropped.
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
No action is necessary.
MESSAGE
WARNING - Module !.! is owned by user HPODBSS, and is
assumed to be part of the ObjectDB product (DBWARN 22940).
ObjectDB is not supported under the target version of
ALLBASE/SQL. This module will be dropped during the
migration.
CAUSE
A backward migration was PREVIEWED when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
No action is necessary.
MESSAGE
WARNING - Module !.! is owned by user HPODBSS, and is
assumed to be part of the ObjectDB product (DBWARN 22950).
ObjectDB is not supported under the target version of
ALLBASE/SQL. This module is being dropped.
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
No action is necessary.
ALLBASE/SQL Warning Messages
23020
23030
23040
MESSAGE
WARNING - Table !.! is currently defined as a PUBLICROW
table, which is not supported under the target version of
ALLBASE/SQL (DBWARN 23020). This table will be altered to
become a PUBLIC table during the migration.
CAUSE
A backward migration was PREVIEWED when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
No action is necessary.
MESSAGE
WARNING - Table !.! is currently defined as a PUBLICROW
table, which is not supported under the target version of
ALLBASE/SQL (DBWARN 23030). This table is being altered
to become a PUBLIC table.
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
No action is necessary.
MESSAGE
WARNING - Procedure !.! has a multiple row result set
(DBWARN 23040). In other words, the procedure includes
at least one SELECT statement with no INTO clause. This
feature is not supported under the target version of
ALLBASE/SQL, so this procedure will be dropped during the
migration.
CAUSE
A backward migration was PREVIEWED when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
If you need to transfer this procedure to the target release, use
the SQLGEN GEN PROCEDURE command.
ALLBASE/SQL Warning Messages
2-51
23050
23060
23070
2-52
MESSAGE
WARNING - Procedure !.! has a multiple row result set
(DBWARN 23050). In other words, the procedure includes
at least one SELECT statement with no INTO clause. This
feature is not supported under the target version of
ALLBASE/SQL, so this procedure is being dropped.
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
No action is necessary. If you need to recover the procedure,
the backup version of the DBEnvironment must be restored. If
you need to transfer this procedure to the target release, use the
SQLGEN GEN PROCEDURE command.
MESSAGE
WARNING - Table !.! has more than 255 columns, which is not
supported under the target version of ALLBASE/SQL(DBWARN
23060). This table will be dropped during the migration.
CAUSE
A backward migration was PREVIEWED when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
If you need to transfer this data to the target release, use the
ISQL UNLOAD EXTERNAL command.
MESSAGE
WARNING - Table !.! has more than 255 columns, which is not
supported under the target version of ALLBASE/SQL(DBWARN
23070). This table is being dropped.
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
No action is necessary. If you need to recover the table, the
backup version of the DBEnvironment must be restored. If you
need to transfer this data to the target release, use the ISQL
UNLOAD EXTERNAL command.
ALLBASE/SQL Warning Messages
23080
23090
23130
MESSAGE
WARNING - DBEFile ! (having FILEID '!') in DBEFileSet ! is
detached, which is not supported under the target version
of ALLBASE/SQL (DBWARN 23080).
CAUSE
A backward migration was PREVIEWED when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
SQLMIGRATE will not perform a migration on the
DBEnvironment if this DBEFILE is detached when the
MIGRATE command is issued. Use the SQLUtil ATTACHFILE
command to attach this DBEFile back to the DBEnvironment
before attempting the migration.
MESSAGE
WARNING - DBEFile ! (having FILEID '!') in DBEFileSet ! is
detached, which is not supported under the target version
of ALLBASE/SQL (DBWARN 23090).
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
You must use the SQLUtil ATTACHFILE command to attach
this DBEFile back to the DBEnvironment before a migration can
be attempted.
MESSAGE
WARNING - Constraint, procedure, or rule sections exist
in DBEFileSet !, which is not supported under the target
version of ALLBASE/SQL (DBWARN 23130).
CAUSE
A backward migration was PREVIEWED when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
SQLMIGRATE will not perform a migration on the
DBEnvironment if these sections remain in this DBEFileSet when
the MIGRATE command is issued. Use the ISQL EXTRACT
and INSTALL commands to move these sections into the
SYSTEM DBEFileSet before attempting the migration.
ALLBASE/SQL Warning Messages
2-53
23150
28027
29007
29009
2-54
MESSAGE
WARNING - Constraint, procedure, or rule sections exist
in DBEFileSet !, which is not supported under the target
version of ALLBASE/SQL (DBWARN 23150).
CAUSE
A backward migration was in progress when this message was
issued. User data which takes advantage of functionality that is
not present in the target release has been detected.
ACTION
You must use the ISQL EXTRACT and INSTALL commands
to move these sections into the SYSTEM DBEFileSet before a
migration can be attempted.
MESSAGE
Datacomm type must be ARPA if the client and/or server is
running HP-UX 10.0 or greater. (DBWARN 28027)
CAUSE
ARPA is the only valid datacomm type if the client and/or server
is running HP-UX 10.0 or greater.
ACTION
If HP-UX release on the client and/or server is 10.0 or greater,
then change datacomm type to ARPA, otherwise current entry is
valid.
MESSAGE
Local database connection failed with DBERR !. Remote
access attempted. (DBWARN 29007)
CAUSE
You specied a le name in the START DBE or CONNECT
statement that does not exist on the local node.
ACTION
If you wanted to access a local DBEnvironment, refer to the
DBERR returned in the error message.
MESSAGE
Diskless node. Remote access attempted directly. (DBWARN
29009)
CAUSE
This is the second of two messages. The rst message indicates a
failure to remotely connect to a DBEnvironment. This message
acknowledges that no attempt to connect to the local DBE was
made because you are on a diskless node.
ACTION
Resolve the remote access problem, as specied in the rst of the
two messages and try again.
ALLBASE/SQL Warning Messages
34073
MESSAGE
Number of tables exceeds internal maximum (max=!) (DBWARN
34073)
CAUSE
In shared memory, table ids are represented by TIDs. During
the SET DBENVIRONMENT command, SQLMON reads from
SYSTEM.TABLE and SYSTEM.COLUMN to obtain information
that maps each TID to an OWNER.TABLE name. There is a
limit to the number that can be mapped: if the number of tables
within the DBEnvironment exceeds the limit, then DBWARN
34073 is displayed. A table encountered after the limit has been
reached is treated as follows:
In the LOCK subsystem, the name of the table is displayed in
TID format, instead of as an OWNER.TABLE string, when locks
are acquired on the table.
In the SAMPLEIO subsystem, the table is never displayed on the
TABLES or TABINDEX screens, even though I/O activity might
have been observed for it, because the internal limit also aects
the number of tables for which historical I/O data is maintained.
The table can appear on the OBJECTS screen if it is observed
in the data buer pool: the name of the table is displayed in
TID format, instead of as an OWNER.TABLE string, and the
TOTALIO eld is always '???'.
In the STATIC subsystem, the table is never displayed.
ACTION
If you need the limit increased, please contact your HP Service
Representative or Response Center.
ALLBASE/SQL Warning Messages
2-55
34074
MESSAGE
Number of indexes exceeds internal maximum (max=!)
(DBWARN 34074)
CAUSE
In shared memory, B-tree index ids are represented by TIDs.
During the SET DBENVIRONMENT command, SQLMON
reads from SYSTEM.INDEX and SYSTEM.CONSTRAINT
to obtain information that maps each B-tree TID to an
OWNER.TABLE/INDEX name. There is a limit to the number
that can be mapped: if the number of B-tree indexes within the
DBEnvironment exceeds the limit, then DBWARN 34074 is
displayed. A B-tree index encountered after the limit has been
reached is treated as follows:
In the SAMPLEIO subsystem, the index is never displayed
on the INDEXES or TABINDEX screens, even though I/O
activity might have been observed for it, because the internal
limit also aects the number of indexes for which historical I/O
data is maintained. The index can appear on the OBJECTS
screen if it is observed in the data buer pool: the name
of the index is displayed in TID format, instead of as an
OWNER.TABLE/INDEX string, and the TOTALIO eld is
always '???'.
In the STATIC subsystem, the index is never displayed.
34075
ACTION
If you need the limit increased, please contact your HP Service
Representative or Response Center.
MESSAGE
Number of DBEFiles exceeds internal maximum (max=!)
(DBWARN 34075)
CAUSE
In shared memory, DBEFile ids are represented by integers.
During the SET DBENVIRONMENT command, SQLMON
reads from SYSTEM.DBEFILE to obtain information that
maps each integer to a DBEFile name. There is a limit to the
number that can be mapped: if the number of DBEFiles within
the DBEnvironment exceeds the limit, then DBWARN 34075
is displayed. A DBEFile encountered after the limit has been
reached is treated as follows:
In the SAMPLEIO subsystem, the DBEFile is never displayed
on the SAMPLEIO screen, even though I/O activity might have
been observed for it, because the internal limit also aects the
number of DBEFiles for which historical I/O data is maintained.
In the STATIC subsystem, the DBEFile is never displayed.
ACTION
2-56
If you need the limit increased, please contact your HP Service
Representative or Response Center.
ALLBASE/SQL Warning Messages
34078
MESSAGE
Number of referential constraints exceeds internal
maximum (max=!) (DBWARN 34078)
CAUSE
In shared memory, referential constraint (PCR) ids are
represented by TIDs. During the SET DBENVIRONMENT
command, SQLMON reads from SYSTEM.CONSTRAINT
to obtain information that maps each PCR TID to an
OWNER.TABLE/CONSTRAINT name. There is a limit to
the number that can be mapped: if the number of PCRs within
the DBEnvironment exceeds the limit, then DBWARN 34078 is
displayed. A PCR encountered after the limit has been reached is
treated as follows:
In the LOCK subsystem, the name of the PCR is displayed in
TID format, instead of as an OWNER.TABLE/CONSTRAINT
string, when locks are acquired on the PCR.
In the SAMPLEIO subsystem, the PCR is never displayed
on the INDEXES or TABINDEX screens, even though I/O
activity might have been observed for it, because the internal
limit also aects the number of PCRs for which historical I/O
data is maintained. The PCR can appear on the OBJECTS
screen if it is observed in the data buer pool: the name
of the PCR is displayed in TID format, instead of as an
OWNER.TABLE/CONSTRAINT string, and the TOTALIO eld
is always '???'.
In the STATIC subsystem, the PCR is never displayed.
34095
34096
ACTION
If you need the limit increased, please contact your HP Service
Representative or Response Center.
MESSAGE
*** Bad JOB CONTROL WORD 'COLUMNS'. Default Column Size
used. (DBWARN 34095)
CAUSE
Incorrect column size specication.
ACTION
No action required if default column size is acceptable.
MESSAGE
*** Bad JOB CONTROL WORD 'LINES'. Default Line Size used.
(DBWARN 34096)
CAUSE
Incorrect line size syntax.
ACTION
No action required if default line size is acceptable.
ALLBASE/SQL Warning Messages
2-57
34097
34098
34400
34401
34403
2-58
MESSAGE
*** Variable 'COLUMNS' badly set. 80 used. (DBWARN 34097)
CAUSE
Incorrect variable column syntax.
ACTION
No action required if 80 is acceptable.
MESSAGE
*** Variable 'LINES' badly set. 24 used. (DBWARN 34098)
CAUSE
Incorrect variable line syntax.
ACTION
No action required if 24 is acceptable.
MESSAGE
Specified lock is not currently held by any users. (DBWARN
34400)
CAUSE
The LOCK OBJECT screen was being accessed when this
message was displayed. The table, page, or row that you specied
is not locked.
ACTION
No action is necessary. Check that you specied the correct lock
object.
MESSAGE
PID not connected to the DBEnvironment. (DBWARN 34401)
CAUSE
The PID that you specied is not a valid PID.
ACTION
Check that you specied the correct PID.
MESSAGE
No locks qualify under the LOCKFILTER and LOCKTABFILTER.
(DBWARN 34403)
CAUSE
No locks were found that matched the selection criteria dened
by the LOCKFILTER and LOCKTABFILTER variables.
ACTION
No action is necessary. Use the SET command to check the
current value of each variable. If necessary, use the SET
LOCKFILTER or SET LOCKTABFILTER command to change a
value.
ALLBASE/SQL Warning Messages
34404
34405
34406
34500
MESSAGE
No other session is waiting on this session. (DBWARN
34404)
CAUSE
The LOCK IMPEDE screen was being accessed when this
message was displayed. The session that is being analyzed is not
holding any lock that is causing another session to wait.
ACTION
No action is necessary. Check that you have specied the correct
session.
MESSAGE
XID changed while collecting data! (DBWARN 34405)
CAUSE
The LOCK SESSION, LOCK IMPEDE, or LOCK
TABSUMMARY screen was being accessed when this message
was displayed. To minimize performance degradation of the
DBEnvironment, SQLMON itself never holds locks or latches in
the LOCK subsystem; it essentially performs \dirty" reads to
collect data. While data was being collected, the transaction id of
the session being analyzed changed.
ACTION
No action is necessary. When interpreting the screen, keep in
mind that the information displayed may represent locks from
two dierent transactions.
MESSAGE
Lock information changed while collecting data! (DBWARN
34406)
CAUSE
The LOCK OBJECT screen was being accessed when this
message was displayed. To minimize performance degradation of
the DBEnvironment, SQLMON itself never hold locks or latches
in the LOCK subsystem; it essentially performs \dirty" reads
to collect data. SQLMON has detected that an inconsistent
snapshot may have been taken.
ACTION
Ignore the information displayed on the screen.
MESSAGE
SET DBENVIRONMENT command has not been issued yet. (DBWARN
34500)
CAUSE
You tried to access an SQLMON screen without naming the
database that you wish to examine.
ACTION
Issue a SET DBENVIRONMENT command.
ALLBASE/SQL Warning Messages
2-59
34505
34510
34511
MESSAGE
DBEnvironment is not active (no other session in
progress). (DBWARN 34505)
CAUSE
Except for your SQLMON session, the database is idle.
ACTION
You can only access screens in the STATIC subsystem. All
other screens display information that is only available when the
database is active.
MESSAGE
DBEnvironment is in the process of shutting down (RC 215).
(DBWARN 34510)
CAUSE
The DBA has probably issued a STOP DBE command. Once it
has completed, the database will be idle.
ACTION
No action is necessary. When the database becomes idle, you will
only be able to access screens in the STATIC subsystem.
MESSAGE
DBEnvironment transaction limit has been reached. (DBWARN
34511)
CAUSE
A timeout occurred when SQLMON tried to begin a transaction,
probably because the congured limit for the maximum number
of active transactions has been reached.
ACTION
Access the OVERVIEW screen: the MAX XACT eld displays
the transaction limit, and the ACTIVE XACT eld displays the
current number of active transactions. You may wish to use the
SQLUtil ALTDBE command to increase the transaction limit.
Also, use the SET command to check the current value of the
USERTIMEOUT variable, which species the number of seconds
that SQLMON will wait before timing out. You may wish to use
the SET USERTIMEOUT command to increase the value, and
then issue your original command again.
34515
2-60
MESSAGE
Could not obtain share lock on SUBSYSTEM CATALOG. (DBWARN
34515)
CAUSE
SQLMON could not read from an internal table.
ACTION
Please contact your HP Service Representative or Response
Center.
ALLBASE/SQL Warning Messages
34518
34519
34520
MESSAGE
Not attempting to map information from SYSTEM.TABLE.
(DBWARN 34518)
CAUSE
In shared memory, table ids are represented by TIDs. During
the SET DBENVIRONMENT command, SQLMON normally
reads from SYSTEM.TABLE to obtain information that maps
each TID to an OWNER.TABLE name. Because of some error,
SQLMON is not able to read from SYSTEM.TABLE. Therefore,
table names will be displayed in TID format, instead of as
OWNER.TABLE strings.
ACTION
Resolve the error, and try again. If necessary, contact your HP
Service Representative or Response Center.
MESSAGE
Not attempting to map information from SYSTEM.INDEX.
(DBWARN 34519)
CAUSE
In shared memory, B-tree index ids are represented by TIDs.
During the SET DBENVIRONMENT command, SQLMON
normally reads from SYSTEM.INDEX to obtain information
that maps each TID to an OWNER.TABLE/INDEX name.
Because of some error, SQLMON is not able to read from
SYSTEM.INDEX. Therefore, index names will be displayed in
TID format, instead of as OWNER.TABLE/INDEX strings.
ACTION
Resolve the error, and try again. If necessary, contact your HP
Service Representative or Response Center.
MESSAGE
Not attempting to map information from SYSTEM.DBEFILE.
(DBWARN 34520)
CAUSE
In shared memory, DBEFile ids are represented by integers.
During the SET DBENVIRONMENT command, SQLMON
normally reads from SYSTEM.DBEFILE to obtain information
that maps each integer to a DBEFile name. Because of some
error, SQLMON is not able to read from SYSTEM.DBEFILE.
Therefore, DBEFile names will be displayed as integers, instead
of strings.
ACTION
Resolve the error, and try again. If necessary, contact your HP
Service Representative or Response Center.
ALLBASE/SQL Warning Messages
2-61
34521
34580
2-62
MESSAGE
Not attempting to map information from SYSTEM.CONSTRAINT.
(DBWARN 34521)
CAUSE
In shared memory, referential constraint (PCR) ids are represented by TIDs. During the SET DBENVIRONMENT command,
SQLMON normally reads from SYSTEM.CONSTRAINT
to obtain information that maps each PCR TID to an
OWNER.TABLE/CONSTRAINT name. Because of some error,
SQLMON is not able to read from SYSTEM.CONSTRAINT.
Therefore, PCR names will be displayed in TID format, instead
of as OWNER.TABLE/CONSTRAINT strings.
ACTION
Resolve the error, and try again. If necessary, contact your HP
Service Representative or Response Center.
MESSAGE
USERTIMEOUT exceeded maximum, so it was reset to !
seconds. (DBWARN 34580)
CAUSE
You probably tried to issue a SET USERTIMEOUT command
using a timeout value that was larger than the maximum
timeout value that has been congured for the database. The
USERTIMEOUT variable has automatically been reset to the
maximum timeout value, which is displayed in the message.
ACTION
No action is necessary.
ALLBASE/SQL Warning Messages
3
ALLBASE/SQL Error Messages
1
2
MESSAGE
Command buffer currently empty. (DBERR 1)
CAUSE
You issued a RECALL [CURRENT], CHANGE, or START
command before any commands had been stored in the command
buer.
ACTION
Use the HOLD, RECALL FILE, or RECALL HISTORY
command to put information into the command buer.
MESSAGE
Problem with large command. Maximum length is !. (DBERR
2)
CAUSE
New string replacement on CHANGE command caused an
overow of the command buer
or
the storage le could not be opened when trying to store the
large command.
ACTION
Modify the new string so that the length of the string in the
command buer is less than or equal to 2048 bytes
or
you may be out of disk space. Contact your system
administrator.
3
MESSAGE
'!' not found. (DBERR 3)
CAUSE
The search pattern you gave in the ISQL CHANGE command
was not found in the command buer.
ACTION
Check your spelling and issue the CHANGE command again,
specifying a valid search pattern.
ALLBASE/SQL Error Messages
3-1
4
5
7
8
11
3-2
MESSAGE
The requested editor could not be scheduled. (DBERR 4)
CAUSE
The editor you specied in the EDITOR option of the SET
command does not exist.
ACTION
Check your spelling and issue the SET command again,
specifying the correct name for the editor requested. If you still
receive this message, contact your system administrator.
MESSAGE
Number of copies must be in the range 1..20. (DBERR 5)
CAUSE
The number of copies you specied in the browse PRINT option
must be in the range of 1 to 20.
ACTION
Issue the PRINT command again, specifying a value from 1
through 20.
MESSAGE
Error erasing file '!'. (DBERR 7)
CAUSE
You do not have the required permission to delete the specied
le.
ACTION
Check your spelling and issue the command again. If you still
receive this message, no action is necessary; you cannot erase the
specied le.
MESSAGE
No help for command '!'. (DBERR 8)
CAUSE
The command name you entered does not exist or was entered
incorrectly.
ACTION
Issue the HELP command again, specifying a valid command
name. Enter HELP @ to obtain a list of the ISQL and SQL
commands.
MESSAGE
Column name list must be terminated by ')'. (DBERR 11)
CAUSE
The right parenthesis was missing after the last column name
specied in the INPUT command.
ACTION
Issue the command again, with column names enclosed in
parentheses.
ALLBASE/SQL Error Messages
12
13
14
15
17
MESSAGE
Column names must be enclosed in parentheses. (DBERR 12)
CAUSE
The list of column names in the INPUT command was not
surrounded by parentheses.
ACTION
Issue the command again, with column names enclosed in
parentheses.
MESSAGE
! not a column name in table !. (DBERR 13)
CAUSE
The column you specied in the LOAD EXTERNAL command
does not exist in the table specied.
ACTION
Use the INFO command to check which columns are in the
specied table.
MESSAGE
'!' is not acceptable as a name for a stored command.
(DBERR 14)
CAUSE
The name you specied for a command le did not conform to
operating system specications. The command was not stored.
ACTION
Refer to A Beginner's Guide to HP-UX for le naming
conventions.
MESSAGE
'!' is not acceptable as a file name. (DBERR 15)
CAUSE
The name you specied as a le name did not conform to
operating system specications.
ACTION
Refer to A Beginner's Guide to HP-UX for le naming
conventions.
MESSAGE
'!' cannot be found. (DBERR 17)
CAUSE
The le name you specied does not exist or was entered
incorrectly.
ACTION
Check your spelling. Use the HP-UX ls command to verify the
existence of the specied le.
ALLBASE/SQL Error Messages
3-3
18
19
20
21
27
3-4
MESSAGE
Error opening file '!'. (DBERR 18)
CAUSE
The le you specied is currently being accessed.
ACTION
Wait until a later time to access the le.
MESSAGE
Valid options are F[ILE], S[ET], H[ISTORY], I[NSTALL].
(DBERR 19)
CAUSE
The option you specied in the LIST command is not a valid
option.
ACTION
Issue the command again, specifying a valid option. Refer to the
ALLBASE/ISQL Reference Manual for additional information on
the LIST command.
MESSAGE
Valid options are F[ILE], C[URRENT], H[ISTORY]. (DBERR
20)
CAUSE
The option you entered for the RECALL command is not a valid
option.
ACTION
Issue the command again, specifying a valid option. Refer to the
ALLBASE/ISQL Reference Manual for additional information on
the RECALL command.
MESSAGE
Cannot continue with INPUT command. (DBERR 21)
CAUSE
Another error caused the INPUT command to be discontinued.
An additional error message will be returned.
ACTION
Refer to the cause and action of the additional error.
MESSAGE
No column selected from table !. (DBERR 27)
CAUSE
You did not specify a column name in the LOAD command.
ACTION
Issue the LOAD command again, specifying a column name.
ALLBASE/SQL Error Messages
28
29
30
31
MESSAGE
History number must be in the range 1..!. (DBERR 28)
CAUSE
The number you specied in the LIST HISTORY or RECALL
HISTORY command was out of the acceptable range.
ACTION
Issue the command again, specifying a number from 1 through 10.
MESSAGE
Valid options are Y[ES] and N[O]. (DBERR 29)
CAUSE
The option you entered for the END, LOAD, STORE, or EXIT
command is not a valid option.
ACTION
Issue the command again, specifying a valid option. Refer to the
ALLBASE/ISQL Reference Manual for additional information on
these commands.
MESSAGE
Column is beyond end of record in load file on line #!.
(DBERR 30)
CAUSE
At least part of one of the data elds that you specied was
beyond the end of the record in the load le. The record was
ignored and no data was loaded into the table from the record.
ACTION
Check the description given for the load le. Make sure the
starting location for each eld is not beyond the end of the
record. Also, check that the length specied for each eld does
not cause part of the eld to be beyond the end of the record.
The starting location plus the length should be equal to or less
than the record length. Unless the last eld in the load le record
is a VARCHAR eld, all load le records should be the same
length.
MESSAGE
Search pattern is beyond end of record on line #!. (DBERR
31)
CAUSE
The starting position of the search pattern you specied was
beyond the end of the record. The record was ignored and no
data was loaded into the table from the record.
ACTION
Verify the starting position of the search pattern and issue the
LOAD command again.
ALLBASE/SQL Error Messages
3-5
32
33
34
35
36
3-6
MESSAGE
Valid options are ON and OF[F]. (DBERR 32)
CAUSE
The option value you specied for the AUTOCOMMIT,
CONTINUE, or ECHO option of the SET command was not a
valid option.
ACTION
Issue the command again, specifying a valid option. Refer to the
ALLBASE/ISQL Reference Manual for additional information on
the SET command.
MESSAGE
Invalid command. (DBERR 33)
CAUSE
The command you entered while viewing the results of a
SELECT statement was not valid.
ACTION
Valid commands are u[p], d[own], l[eft], r[ight], t[op], b[ottom],
pr[int], e[nd], and p[ause].
MESSAGE
FETCH is not allowed in ISQL. (DBERR 34)
CAUSE
You issued a FETCH statement while in ISQL.
ACTION
The FETCH statement can only be used in application programs.
Refer to the ALLBASE/SQL Reference Manual for additional
information.
MESSAGE
Error reading from SelectFile. (DBERR 35)
CAUSE
One or more users are accessing the same output le that you
specied in the OUTPUT option of the SET command.
ACTION
Change the name of the output le using the OUTPUT option of
the SET command.
MESSAGE
Problem executing such a long command. (DBERR 36)
CAUSE
This is an internal error that occurs while executing an SQL
statement whose length is greater than 1.5 megabytes.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center. You can work around
this problem by shortening the length of your command to less
than 1.5 megabytes.
ALLBASE/SQL Error Messages
37
38
39
40
MESSAGE
ISQL command too long. (DBERR 37)
CAUSE
The number of characters in the ISQL command exceeded the
maximum limit of 2048 bytes.
ACTION
Issue the command again, within the valid limits.
MESSAGE
SYSTEM command unsuccessful. Return code is !. (DBERR 38)
CAUSE
The operating system command you issued from ISQL is valid
but cannot be executed.
ACTION
Refer to the /usr/include/sys/errno.h le for a brief explanation
of the error code returned.
MESSAGE
File '!' already exists. (DBERR 39)
CAUSE
The le name you specied to RENAME a le already exists.
ACTION
If you do not want to overwrite the existing le, reenter the
RENAME command specifying a unique le name. Otherwise,
either use the ERASE command to remove the existing le or use
the RENAME command to rename the existing le rst.
MESSAGE
Error attempting to rename '!' to '!'. (DBERR 40)
CAUSE
The ISQL RENAME failed because the le is being accessed
or
you do not have write permission to the le.
ACTION
Issue the command again, when the le is no longer being
accessed
or
contact a user who has write permission to the specied le.
41
MESSAGE
Internal error: Error on rename from '!' to '!'. (DBERR
41)
CAUSE
The ISQL RENAME command failed due to an internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
3-7
42
MESSAGE
Unable to open work file. (DBERR 42)
CAUSE
The le you specied in the SELECT statement cannot be
opened because it is being accessed already
or
you do not have write permission in the current directory
or
you are out of disk space.
ACTION
Wait until the le is not being accessed
or
contact your system administrator.
43
44
45
3-8
MESSAGE
Bad numeric input. (DBERR 43)
CAUSE
You entered a character where a numeric value was expected.
ACTION
Issue the command again, specifying a numeric value.
MESSAGE
Invalid option. (DBERR 44)
CAUSE
The option you specied in the SET command is not one of the
valid options. The command is aborted and no option is set.
ACTION
Issue the command again, specifying a valid option. The valid
options for the SET command are: autoc[ommit], autos[ave],
c[ontinue], ec[ho], ed[itor], es[cape], f[raction], n[ull], ou[tput],
ow[ner], pa[gewidth], and pr[ompt]. Refer to the ALLBASE/ISQL
Reference Manual for additional information on the SET
command.
MESSAGE
Column ! has already been specified. (DBERR 45)
CAUSE
You specied the same column name twice in the LOAD
command.
ACTION
Issue the LOAD command again, with each column name
specied only once. Refer to the ALLBASE/SQL Reference
Manual for more information on the LOAD command.
ALLBASE/SQL Error Messages
46
47
49
MESSAGE
Command buffer empty, STORE not performed. (DBERR 46)
CAUSE
The STORE command works only on information in the ISQL
command buer.
ACTION
Use the HOLD or RECALL command to put information into the
command buer, then issue the STORE command again.
MESSAGE
Missing parameters from command file. (DBERR 47)
CAUSE
The command le you specied in the START command was
missing parameters essential to its function.
ACTION
Check the command buer or command le specied in the
START command to make sure that all required parameters
are there. Refer to the ALLBASE/SQL Reference Manual or
ALLBASE/ISQL Reference Manual for additional information on
the command(s) specied.
MESSAGE
Last command not terminated in command file - ignored.
(DBERR 49)
CAUSE
The last command you executed in the command le was not
terminated with a semicolon (;)
or
the last line in the command le was a comment or blank line.
ACTION
Correct the command le so that all commands are terminated
with a semicolon (;)
or
reissue the commands which were not executed.
50
MESSAGE
Fraction length must be in the range 0..18 (DBERR 50)
CAUSE
The fraction length you specied in the FRACTION option of the
SET command was not within the acceptable range. The fraction
length was not changed.
ACTION
Issue the command again, specifying a fraction length between 0
and 18.
ALLBASE/SQL Error Messages
3-9
51
52
53
54
55
3-10
MESSAGE
Column ! can't be null. You MUST load this column. (DBERR
51)
CAUSE
The LOAD command did not specify a column that was created
with the NOT NULL attribute.
ACTION
Issue the command again, specifying any column created with the
NOT NULL attribute.
MESSAGE
Internal error trying to load data. (DBERR 52)
CAUSE
An unsuccessful BULK INSERT in DBCore. An additional error
message will be returned.
ACTION
Refer to the cause and action of the additional error message.
MESSAGE
Pagewidth must be in the range 10..254. (DBERR 53)
CAUSE
The PAGEWIDTH option you specied in the SET command
was not within the valid range. The page width was not changed.
ACTION
Issue the command again, specifying a page width in the range of
10 through 254.
MESSAGE
AutoSave count must be in the range 1..32767. (DBERR 54)
CAUSE
The AUTOSAVE option you specied in the SET command was
not within the valid range. The number of rows remains the
same.
ACTION
Issue the command again, specifying an Autosave count in the
range of 1 through 32,767.
MESSAGE
Problem getting help. (DBERR 55)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
56
57
58
60
61
MESSAGE
Output file name must be no more than ! bytes. (DBERR 56)
CAUSE
The output le name you specied in the command is not a valid
system le name.
ACTION
Refer to the A Beginner's Guide to HP-UX for additional
information on le naming conventions.
MESSAGE
Prompt must be no more than ! bytes. (DBERR 57)
CAUSE
The prompt you specied in the PROMPT option of the SET
command exceeded the maximum length of 16 bytes.
ACTION
Issue the command again, specifying a valid prompt length.
MESSAGE
Null character must be a single one-byte character.
(DBERR 58)
CAUSE
You specied more than a single one-byte character as the null
indicator in the LOAD or UNLOAD EXTERNAL command.
ACTION
Issue the command again, specifying only a single one-byte
character as the null indicator.
MESSAGE
Command file execution terminated. (DBERR 60)
CAUSE
Execution was terminated because of an error in the command
le. An additional error message will be returned.
ACTION
Refer to the cause and action of the additional error message.
MESSAGE
Escape character must be a single one-byte character.
(DBERR 61)
CAUSE
You specied more than a single one-byte character in the
ESCAPE option of the SET command. The ESCAPE option was
not changed.
ACTION
Issue the command again, specifying a single one-byte character
in the ESCAPE option.
ALLBASE/SQL Error Messages
3-11
62
63
64
66
67
3-12
MESSAGE
SQLCORE not available. (DBERR 62)
CAUSE
There is an ALLBASE/SQL linking problem.
ACTION
Contact your system administrator.
MESSAGE
Internal error: Unrecognized status code: !. (DBERR 63)
CAUSE
Internal error.
ACTION
Record the code returned and as much information as possible.
Contact your HP Service Representative or Response Center.
MESSAGE
Semantic error. (DBERR 64)
CAUSE
An additional message will be returned.
ACTION
Refer to the cause and action of the additional error message.
MESSAGE
Name of editor must not be more than ! bytes. (DBERR 66)
CAUSE
The editor name you specied in the EDITOR option of the SET
command exceeds the maximum limit of 255 bytes (including
slashes). The EDITOR option was not changed.
ACTION
Issue the SET command again, with a valid name specied in the
EDITOR option.
MESSAGE
Command buffer cannot be executed from command file.
(DBERR 67)
CAUSE
The command le you specied contains a START command to
execute the command buer. A command le can start other
command les, but cannot start the command buer.
ACTION
Remove the START command to execute the command buer
from the command le. Refer to the ALLBASE/ISQL Reference
Manual for additional information on the START command.
ALLBASE/SQL Error Messages
69
73
74
76
77
MESSAGE
Illegal table name. (DBERR 69)
CAUSE
The table name you specied in the INFO, UNLOAD, or INPUT
command was not a valid table name.
ACTION
Refer to the ALLBASE/SQL Reference Manual for table naming
conventions.
MESSAGE
Valid options are E[XTERNAL] and I[NTERNAL]. (DBERR 73)
CAUSE
The option you specied for the LOAD or UNLOAD command
was not a valid option.
ACTION
Issue the command again, specifying either EXTERNAL or
INTERNAL. Refer to the ALLBASE/ISQL Reference Manual for
additional information on the LOAD and UNLOAD commands.
MESSAGE
Invalid option '!'. (DBERR 74)
CAUSE
The option you specied in the SET command was not a valid
option.
ACTION
Issue the command again, specifying only valid options. Refer to
the ALLBASE/ISQL Reference Manual for valid options and
additional information on the SET command.
MESSAGE
End of file encountered on input. (DBERR 76)
CAUSE
You reached EOF on standard input. The program was
terminated.
ACTION
No action is necessary.
MESSAGE
Could not schedule !. (DBERR 77)
CAUSE
SQLUtil or SQLGEN could not be scheduled because execute
permission is denied
or
if ALLBASE/SQL was installed in a directory other than usr/bin,
SQLUtil and SQLGEN cannot be executed from within ISQL.
ACTION
Check to make sure that SQLUtil and SGLGEN are in usr/bin. If
they are not, contact your system administrator.
ALLBASE/SQL Error Messages
3-13
78
79
81
MESSAGE
Missing keyword FROM. (DBERR 78)
CAUSE
You tried to execute a LOAD or UNLOAD command without
specifying the keyword FROM.
ACTION
Issue the command again, specifying the FROM keyword.
Refer to the ALLBASE/ISQL Reference Manual for additional
information on the LOAD and UNLOAD commands.
MESSAGE
Missing keyword TO. (DBERR 79)
CAUSE
You tried to execute a LOAD or UNLOAD command without
specifying the keyword TO.
ACTION
Issue the command again, specifying the TO keyword. Refer
to the ALLBASE/ISQL Reference Manual for additional
information on the LOAD and UNLOAD commands.
MESSAGE
File is not in INTERNAL format. (DBERR 81)
CAUSE
The input le name you specied in the LOAD command was not
unloaded with the INTERNAL option
or
the le name you specied does not exist or was entered
incorrectly.
ACTION
Issue the LOAD command again, specifying the EXTERNAL
option
or
check your spelling. Use the HP-UX ls command to make sure
that the specied le exists.
82
3-14
MESSAGE
Unidentified error ! occurred on last command. (DBERR 82)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
83
84
85
86
MESSAGE
Command buffer cannot be executed from command buffer.
(DBERR 83)
CAUSE
The command buer contains a START command to execute the
command buer. The command buer can start a command le,
but cannot start itself recursively.
ACTION
Remove the START command to execute the command buer
from the command buer. The CHANGE command may be
used to make this modication. Refer to the ALLBASE/ISQL
Reference Manual for additional information on the START
command.
MESSAGE
New command exceeds maximum. (DBERR 84)
CAUSE
The maximum limit of 2048 bytes was exceeded when you used
the insert subcommand of the REDO command.
ACTION
Issue the command again, so that the total number of bytes in
the command is less than or equal to 2048.
MESSAGE
Bad bytes after delete command. (DBERR 85)
CAUSE
You entered an invalid option after the delete subcommand of the
REDO command.
ACTION
Issue the command again, specifying only valid options after the
delete subcommand. Refer to the ALLBASE/ISQL Reference
Manual for valid options and additional information on the
REDO command.
MESSAGE
Extra bytes. (DBERR 86)
CAUSE
The bytes that you entered after the i, h, x, b, or e subcommands
of the REDO command are invalid.
ACTION
Issue the REDO command again. Refer to the ALLBASE/ISQL
Reference Manual for additional information on the REDO
command.
ALLBASE/SQL Error Messages
3-15
87
88
89
90
91
3-16
MESSAGE
Must break line - too long. (DBERR 87)
CAUSE
The bytes you added to the command using the insert
subcommand of the REDO command caused the line to be
greater than the maximum limit of 80 bytes.
ACTION
Use the break subcommand before using the insert subcommand
again. Refer to the ALLBASE/ISQL Reference Manual for
additional information on the REDO command.
MESSAGE
No plus or minus sign. (DBERR 88)
CAUSE
You used more than one + or - sign in the same line in the
REDO command.
ACTION
If you want to go forward or backward more than one line, use
the +n or -n subcommand (where n is an integer). Refer to the
ALLBASE/ISQL Reference Manual for additional information on
the REDO command.
MESSAGE
No command to edit. (DBERR 89)
CAUSE
You attempted to execute a REDO command when the command
history buer was empty.
ACTION
No action is necessary.
MESSAGE
Redo not allowed in command buffer/command file - ignored.
(DBERR 90)
CAUSE
You included a REDO command in either the command buer or
command le.
ACTION
Remove the REDO command and execute the command buer or
command le again.
MESSAGE
Problem opening installation file. (DBERR 91)
CAUSE
Internal error.
ACTION
Record the le system error code returned and as much
information as possible. Contact your HP Service Representative
or Response Center.
ALLBASE/SQL Error Messages
92
93
94
MESSAGE
Problem reading from installation file. Code = !. (DBERR
92)
CAUSE
The installation le you specied did not contain a module. No
module was generated for the preprocessed application.
ACTION
No action is necessary. An installation was not required to run
this application.
MESSAGE
Empty installation file. (DBERR 93)
CAUSE
The installation le you specied is empty.
ACTION
No action is necessary.
MESSAGE
Installation stopped due to error. (DBERR 94)
CAUSE
The le name you specied in the INSTALL command was not a
valid le name
or
the le you specied is currently being accessed by another user.
ACTION
Issue the command again, specifying a valid le name
or
wait until the le is not being accessed before issuing the
command again.
95
MESSAGE
File is not an installation file or it is corrupted.
(DBERR 95)
CAUSE
The name of the le you specied in the ISQL INSTALL
command was not an installation le
or
the installation le is corrupted.
ACTION
Correct the le name and issue the INSTALL command again
or
regenerate the installation le by re-preprocessing the application.
ALLBASE/SQL Error Messages
3-17
96
97
150
151
MESSAGE
Host variables or dynamic parameters not allowed through
ISQL. (DBERR 96)
CAUSE
The command you submitted through ISQL contains a host
variable or a dynamic parameter.
ACTION
Substitute a constant value or column name for the host variable
or dynamic parameter. If you need to use variables or dynamic
parameters in SQL statements, you must do so via an application
program. Refer to the appropriate ALLBASE/SQL application
programming guide for additional information.
MESSAGE
Cannot continue with SELECT. (DBERR 97)
CAUSE
An error occurred which caused the SELECT statement to
terminate. An additional message will be returned.
ACTION
Refer to the cause and action of the additional error message.
MESSAGE
Invalid character for null indicator. (DBERR 150)
CAUSE
The character you specied for the null indicator in the LOAD or
UNLOAD EXTERNAL command was invalid.
ACTION
Issue the command again, specifying any single one-byte
character for the null indicator except a single quote, double
quote, semi-colon, blank, or the current escape character.
MESSAGE
File created with different product or version, or not an
INTERNAL file. (DBERR 151)
CAUSE
The input le you specied in the LOAD command was created
from a dierent product or a dierent version of ISQL
or
the le was UNLOADed using the EXTERNAL option.
ACTION
UNLOAD the data to create a le from the current version
specifying the INTERNAL option and issue the LOAD command
again
or
issue the LOAD command again, specifying the EXTERNAL
option.
3-18
ALLBASE/SQL Error Messages
152
175
176
177
MESSAGE
INSTALL file created with different product or version.
(DBERR 152)
CAUSE
The le you specied in the INSTALL command was created
from a dierent product or dierent version of the preprocessor
you are using.
ACTION
Re-preprocess your program to create an installable module le
from the current version, then issue the INSTALL command
again.
MESSAGE
EXECUTE IMMEDIATE cannot be used for !. (DBERR 175)
CAUSE
You cannot dynamically preprocess the specied command.
ACTION
Re-submit the command without using the EXECUTE
IMMEDIATE statement to host it. Refer to the ALLBASE/SQL
Reference Manual for a list of statements that can be executed
using EXECUTE IMMEDIATE.
MESSAGE
! cannot be used interactively. (DBERR 176)
CAUSE
The command you specied can only be used in an application
program.
ACTION
Refer to the ALLBASE/SQL Reference Manual for additional
information on the specied command.
MESSAGE
SELECT cannot be preprocessed interactively with PREPARE.
(DBERR 177)
CAUSE
You tried to PREPARE a SELECT statement interactively.
ACTION
You can either PREPARE a SELECT programmatically or
issue the SELECT statement directly or in a command le.
Refer to the ALLBASE/ISQL Reference Manual for additional
information.
ALLBASE/SQL Error Messages
3-19
193
201
202
211
212
3-20
MESSAGE
Number of nested start files exceeds maximum. (DBERR 193)
CAUSE
There are more than ten levels of nesting of command les. This
error may result from an unintended recursive START command.
A maximum of ten command les can be in use at one time.
ACTION
Rewrite your command les so that there are ten or fewer levels
of nesting. Remove any recursive START commands.
MESSAGE
Invalid starting row. (DBERR 201)
CAUSE
The value you specied for the starting row is not a positive
integer.
ACTION
Issue the LOAD command again, specifying a positive integer.
MESSAGE
Invalid number of rows. (DBERR 202)
CAUSE
The number of rows you specied is not a positive integer.
ACTION
Issue the LOAD command again, specifying a positive integer for
the starting row.
MESSAGE
Failed to free heap space. (DBERR 211)
CAUSE
Internal error.
ACTION
Report this error to your database administrator. If the problem
persists, record as much information as possible and contact your
HP Service Representative or Response Center.
MESSAGE
Failed to get heap space. (DBERR 212)
CAUSE
There was no memory available for your query.
ACTION
Report this error to your database administrator and try your
query later. If this problem persists, record as much information
as possible and contact your HP Service Representative or
Response Center.
ALLBASE/SQL Error Messages
213
220
230
231
237
MESSAGE
Insufficient file space on disc(s). (DBERR 213)
CAUSE
There is not enough le space on the disk(s) to complete the
transaction.
ACTION
Contact your system administrator.
MESSAGE
Security violation, permission denied. (DBERR 220)
CAUSE
You do not have the required capability for the operation
attempted.
ACTION
Check that you have write-access to the directory where you are
located. Contact your system administrator to get the required
capability.
MESSAGE
Total output width exceeds maximum of !. (DBERR 230)
CAUSE
The output length you specied in the UNLOAD EXTERNAL
command exceeded the maximum width of 7,990 bytes.
ACTION
Issue the UNLOAD command again, specifying an output length
less than or equal to 7,990. If you require a length greater
than 7,990 bytes, issue the UNLOAD command specifying the
INTERNAL option.
MESSAGE
Owner name must be no more than ! bytes. (DBERR 231)
CAUSE
The length of the Owner name you specied exceeds the
maximum length allowed for owner names.
ACTION
Issue the command again, specifying a shorter owner name.
MESSAGE
ISQL internal error. (! !) (DBERR 237)
CAUSE
An internal error has caused a Pascal runtime, operating system,
architected call interface (ACI), foreign data access (FDA) or
Switch layer error.
ACTION
The error message includes the type of error and error number.
Refer to the cause and action in the appropriate message manual.
ALLBASE/SQL Error Messages
3-21
238
250
251
252
253
256
3-22
MESSAGE
This session is not allowed to use the SYSTEM command.
(DBERR 238)
CAUSE
This session is not allowed to use the System command.
ACTION
No action is required.
MESSAGE
Write failed on file '!'. (! !). (DBERR 250)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for a brief explanation
of the error code returned.
MESSAGE
Read failed on file '!'. (! !). (DBERR 251)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for a brief explanation
of the error code returned.
MESSAGE
Seek failed on file '!'. (! !). (DBERR 252)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for a brief explanation
of the error code returned.
MESSAGE
LONG data types not allowed through UNLOAD INTERNAL.
(DBERR 253)
CAUSE
You attempted to use the UNLOAD command with the
INTERNAL option for LONG data type columns.
ACTION
Use the EXTERNAL option with the UNLOAD command.
MESSAGE
SELECT statement length exceeds maximum of ! bytes.
(DBERR 256)
CAUSE
The length of the SELECT statement in the UNLOAD command
exceeds the maximum of 2048 bytes.
ACTION
Use the SELECT statement to dene a view, and then unload
from the view.
ALLBASE/SQL Error Messages
257
263
284
300
301
MESSAGE
Unable to split error message into multiple lines. (DBERR
257)
CAUSE
There was an internal error.
ACTION
Record as much information as possible and contact you HP
Service Representative or Response Center.
MESSAGE
Invalid flagger name. (DBERR 263)
CAUSE
An invalid agger name was specied in the SET FLAGGER
statement.
ACTION
Specify a valid ag name. Currently, the only agger name
supported is \FIPS127.1". Do not include quotes. It is not case
sensitive.
MESSAGE
Invalid UNLOAD INTERNAL syntax after table name. (DBERR
284)
CAUSE
The UNLOAD INTERNAL syntax after the table name is
invalid.
ACTION
No action is required.
MESSAGE
Open failed on file '!'. (! !). (DBERR 300)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for a brief description of
the error code returned.
MESSAGE
Close failed on file '!'. (! !). (DBERR 301)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for a brief description of
the error code returned.
ALLBASE/SQL Error Messages
3-23
308
309
310
311
312
313
3-24
MESSAGE
This command is not valid for FDA usage. (DBERR 308)
CAUSE
You specied an ISQL command that cannot be used when
connected to a foreign database.
ACTION
No action necessary.
MESSAGE
Already connected. (DBERR 309)
CAUSE
You have already connected to the specied database.
ACTION
No action necessary.
MESSAGE
Invalid CHANGE syntax. (DBERR 310)
CAUSE
The parameter of the CHANGE command is either missing a
delimiter or contains an invalid character.
ACTION
Insert the missing delimiter or delete the invalid character and
issue the CHANGE command again.
MESSAGE
Invalid characters after RELEASE. (DBERR 311)
CAUSE
Non-blank characters follow the RELEASE statement.
ACTION
Issue the RELEASE statement with no trailing, non-blank
characters.
MESSAGE
Invalid EXIT syntax. (DBERR 312)
CAUSE
Non-blank characters follow the EXIT command.
ACTION
Issue the EXIT command with no trailing, non-blank characters.
MESSAGE
Invalid characters after SAVEPOINT. (DBERR 313)
CAUSE
Non-blank characters follow the SAVEPOINT statement.
ACTION
Issue the SAVEPOINT statement with no trailing, non-blank
characters.
ALLBASE/SQL Error Messages
314
315
340
341
MESSAGE
DO/REDO pattern not found. (DBERR 314)
CAUSE
The pattern you specied with the DO or REDO command is not
in the command history buer.
ACTION
Find the correct pattern with the \LIST HISTORY @" command
and issue the DO or REDO command again with the correct
pattern.
MESSAGE
Invalid keyword after PREPARE. (DBERR 315)
CAUSE
You can not use the REPEAT option in a PREPARE statement
in ISQL.
ACTION
Issue the PREPARE statement again without the REPEAT
option.
MESSAGE
Unsupported Format Type with CONVERT option. (DBERR 340)
CAUSE
The SET CONVERT option is not OFF, and the format type of
the input le data specied in the LOAD command is not valid
for the target ALLBASE/SQL column.
ACTION
Issue the LOAD command again with the correct format type. If
you did not intend to convert the data in the input le, execute
the SET CONVERT OFF command and issue the LOAD
command again.
MESSAGE
Description file not allowed with CONVERT option. (DBERR
341)
CAUSE
You specied a description le in the LOAD command when the
SET CONVERT option is not OFF.
ACTION
Issue the LOAD command again without the description le
parameter. If you did not intend to convert the data in the input
le, execute the SET CONVERT OFF command and issue the
LOAD command again.
ALLBASE/SQL Error Messages
3-25
342
343
400
401
402
3-26
MESSAGE
Unsupported Data Format. (DBERR 342)
CAUSE
The SET CONVERT option is not OFF, and the data type of
the ALLBASE/SQL column specied in the LOAD command is
unsupported.
ACTION
Issue the LOAD command with an ALLBASE/SQL data type
that is supported by the conversion operation. If you do not want
to convert the data in the input le, execute the SET CONVERT
OFF command and issue the LOAD command again.
MESSAGE
Data type of ! not supported with the CONVERT option.
(DBERR 343)
CAUSE
The SET CONVERT option is not OFF, and the data type of
the ALLBASE/SQL column specied in the LOAD command is
unsupported.
ACTION
Issue the LOAD command with an ALLBASE/SQL data type
that is supported by the conversion operation. If you do not want
to convert the data in the input le, execute the SET CONVERT
OFF command and issue the LOAD command again.
MESSAGE
Unable to load native language information. (DBERR 400)
CAUSE
The character set attribute and upshift tables for your language
could not be loaded.
ACTION
Contact your system administrator.
MESSAGE
Delimiter must be a single-byte character. (DBERR 401)
CAUSE
You used a multi-byte character as the delimiter in a CHANGE
command.
ACTION
Issue the CHANGE command again, using a single-byte character
as the delimiter.
MESSAGE
Invalid replacement/insertion string. (DBERR 402)
CAUSE
In the REDO command, you specied a replacement or insertion
string containing invalid bytes.
ACTION
Issue the insert or replace command again, specifying a valid
string.
ALLBASE/SQL Error Messages
403
501
503
504
MESSAGE
Internal native language support error. (DBERR 403)
CAUSE
An internal Native Language Support error occurred, probably
due to an invalid character in input.
ACTION
Issue your command again, specifying valid input. If this does
not solve the problem, contact your system administrator.
MESSAGE
Error ! occurred while opening file. (DBERR 501)
CAUSE
Error occurred while you were opening a le. Usually the error is
due to le permissions, or the name being misspelled.
ACTION
Check the name of the le to determine if it is spelled correctly,
and check the le permissions assigned.
MESSAGE
Invalid Command. (DBERR 503)
CAUSE
You entered a command that SQLAudit does not recognize.
ACTION
Check the last command entered.
MESSAGE
Invalid Lock Point found in Audit Point File. (DBERR 504)
CAUSE
The Audit Point File contains a log le lockpoint that is invalid.
You probably used a Recovery File (generated by the AUDIT
command) for the Audit Point le for the LOCK AUDITPOINT
command.
ACTION
LOCK AUDITPOINT should only use Audit Point les that were
generated by calling GET AUDITPOINT.
ALLBASE/SQL Error Messages
3-27
507
508
512
513
3-28
MESSAGE
Log history does not go back far enough for partition !.
(DBERR 507)
CAUSE
This error indicates that the log les have wrapped around and
overwritten some of the committed transactions for the partition.
If this is encountered, the specied partition will be dropped from
the list of auditable partitions.
ACTION
To prevent this from happening, LOCK AUDITPOINT can
be used to protect transactions committed after the beginning
audit point is dened. If it is necessary to get the unaudited
transactions, the SQLUtil command WRAPDBE can be used to
retrieve them. See the ALLBASE/SQL Database Administration
Guide to determine how best to do this.
MESSAGE
Unable to open scan for partition ! due to status of !.
(DBERR 508)
CAUSE
An unexpected error occurred while opening the log le scan for
the given set of partitions.
ACTION
Contact your HP Service Representative or Response Center.
MESSAGE
Log scan could not be successfully opened. (DBERR 512)
CAUSE
Due to previous errors, the log scan could not be opened. No
auditing is possible for the given list of partitions when this
happens.
ACTION
Verify the list of partitions is correct and check the previous
reported errors to determine possible actions.
MESSAGE
Error ! occurred while reading Audit Point File. (DBERR
513)
CAUSE
A le system error occurred while reading the Audit Point File.
Usually this may occur if an invalid Audit Point File has been
entered.
ACTION
Check the le name entered to determine if correct.
ALLBASE/SQL Error Messages
514
515
517
519
520
MESSAGE
File is not a valid Audit Point File. (DBERR 514)
CAUSE
SQLAudit has determined that the le is not an Audit Point File.
ACTION
Check the le name entered to determine if correct.
MESSAGE
Error ! occurred while writing Audit Point File. (DBERR
515)
CAUSE
You encountered a le system error while trying to create and
write out the audit point information into the le. Usually this is
caused by le permissions, or possibly lack of disk space.
ACTION
Check to make sure the le name used was correct. If the le
name is correct, make sure the le and/or directory permissions
are correct and that there is enough space to write the le.
MESSAGE
Native Language Support Error ! encountered. (DBERR 517)
CAUSE
A native language support (NLS) error was encountered by the
last command. This usually means that the proper language was
not correctly installed on the system, or that you may have an
invalid language specied.
ACTION
Check with the system administrator to insure that your language
has been installed on the system, and check the language to
ensure it is correct.
MESSAGE
Non Existent File entered. (DBERR 519)
CAUSE
You entered a le name that does not exist on the system.
ACTION
Check the le name that was entered to ensure it is correct.
MESSAGE
Error ! occurred while closing file. (DBERR 520)
CAUSE
A le system error occurred while closing a le. This may be due
to the le or directory permissions, or a lack of disk space on the
system.
ACTION
Check the le and directory permissions, and the amount of disk
space on the system.
ALLBASE/SQL Error Messages
3-29
521
524
526
527
3-30
MESSAGE
Invalid partition number entered. (DBERR 521)
CAUSE
You entered a partition number or name which is not allowed.
Partition numbers must be in the range of 1 to 32767 inclusive.
Valid partition names are DEFINITION, STORAGE,
AUTHORIZATION, and SECTION.
ACTION
Check the partition name or number that was entered.
MESSAGE
Ending Audit Point missing partition instance ! (!).
(DBERR 524)
CAUSE
This should only be possible if the database has been hard
resynced by an ALLBASE/REPLICATE user.
ACTION
Determine if the database is being used as a master or slave in
an ALLBASE/REPLICATE environment and whether it has
been hard resynced lately. If it has been hard resynced, a new
beginning audit point should be dened after the hard resync has
nished.
MESSAGE
Transaction encountered that is greater than ending
transaction for partition instance ! (!). (DBERR 526)
CAUSE
The only way this should be possible is if the ending audit point
was not generated on the database that is being audited. For
instance, if the ending audit point was generated using a dierent
database then used against the audited DBEnvironment, this
type of situation can arise.
ACTION
Determine if the ending audit point le was actually generated
against the DBEnvironment being audited.
MESSAGE
Error ! occurred while opening Recovery File. (DBERR 527)
CAUSE
A le system error occurred while trying to create the recovery
le. This is usually due to an incorrect name being used, or the
le/directory permissions are not set correctly. This may also be
due to a lack of disk space.
ACTION
Check the recovery le name specied and make sure it does not
exist before doing the audit. Also check disk space, and directory
permissions.
ALLBASE/SQL Error Messages
529
533
534
535
MESSAGE
Unacceptable response entered (will use default). (DBERR
529)
CAUSE
An invalid response was entered for the prompt. SQLAudit will
use the default response (which is the rst response listed).
ACTION
Check the response that was entered.
MESSAGE
SYSTEM command unsuccessful. Return code is !. (DBERR
533)
CAUSE
SQLAudit attempted to execute the system command that was
entered and it encountered an error returned from the operating
system.
ACTION
Check the command entered to determine if it is a valid operating
system command.
MESSAGE
No help for that command. (DBERR 534)
CAUSE
You attempted to obtain help from SQLAudit on an unknown
subject.
ACTION
Check the subject entered. Allowed subjects are any SQLAudit
command, or the keywords GENERAL, MAIN, or SUMMARY. If
you wish to leave the SQLAudit help facility, type '//'.
MESSAGE
The requested editor could not be scheduled due to error !.
(DBERR 535)
CAUSE
SQLAudit was unable to start the editor that is currently set.
ACTION
Check which editor is currently set (through the SET command).
If the editor does not seem valid, change it through the SET
EDITOR command. Also check to make sure it is possible to
start the editor from outside SQLAudit.
HELP keywords are GENERAL, MAIN, and SUMMARY.
Type '//' to leave SQLAUDIT HELP.
ALLBASE/SQL Error Messages
3-31
701
702
703
704
706
3-32
MESSAGE
SQLGEN Error detected. SQLExplain messages will follow.
(DBERR 701)
CAUSE
An unexpected ALLBASE/SQL error occurred.
ACTION
Read the accompanying SQLExplain message to determine
the reason for the error and take corrective action. If the error
persists, contact your database administrator.
MESSAGE
Internal error. Missing message for SQLCODE of !. (DBERR
702)
CAUSE
The ALLBASE/SQL message catalog does not contain the
message associated with error encountered.
ACTION
Contact your database administrator.
MESSAGE
Could not CONNECT to DBEnvironment. (DBERR 703)
CAUSE
SQLGEN could not connect to the DBEnvironment, possibly
because the name was not entered correctly or the AUTOSTART
option is OFF.
ACTION
Correct conditions that may have caused the error. If the error
persist contact your database administrator.
MESSAGE
Error occurred while RELEASING DBEnvironment. (DBERR
704)
CAUSE
An ALLBASE/SQL error occurred while releasing the
DBEnvironment.
ACTION
Contact your database administrator.
MESSAGE
Invalid Table Type encountered. RType = !. (DBERR 706)
CAUSE
Encountered an invalid RType in SYSTEM.TABLE.
ACTION
Contact your database administrator.
ALLBASE/SQL Error Messages
707
708
710
711
712
MESSAGE
Invalid DBEFile Type encountered. Type = !. (DBERR 707)
CAUSE
Encountered an invalid DBEFile in SYSTEM.DBEFILE.
ACTION
Contact your database administrator.
MESSAGE
Invalid Command Number encountered. Location = !. (DBERR
708)
CAUSE
An internal error has occurred.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Invalid SQLType encountered. SQLType = !. (DBERR 710)
CAUSE
An invalid column type was encountered for one of the tables
being described.
ACTION
Contact your database administrator.
MESSAGE
Error occurred while opening file.
CAUSE
Failed to open le as a new le.
ACTION
Read system error messages to determine the cause of the error
and take corrective action. If error persists, contact your system
administrator.
MESSAGE
Error occurred while calling !. (DBERR 712)
CAUSE
File system error occurred while retrieving information about the
schema.
ACTION
Read system error messages to determine the cause of the error
and take corrective action. If error persists, contact your system
administrator.
(DBERR 711)
ALLBASE/SQL Error Messages
3-33
714
715
716
717
719
3-34
MESSAGE
Error occurred while closing file. (DBERR 714)
CAUSE
File system error occurred while attempting to close a le.
ACTION
Read system error messages to determine the cause of the error
and take corrective action. If error persists, contact your system
administrator.
MESSAGE
Error occurred while calling ! !. (DBERR 715)
CAUSE
File system error occurred while trying to rename the le from
EXPSQLG to a schema le name.
ACTION
Read system error messages to determine the cause of the error
and take corrective action. If error persists, contact your system
administrator.
MESSAGE
SYSTEM command unsuccessful. Return code is !. (DBERR
716)
CAUSE
The operating system command you issued is valid but cannot be
executed.
ACTION
Refer to the /usr/include/sys/errno.h le for a brief description of
the error code returned.
MESSAGE
The requested editor could not be scheduled. (DBERR 717)
CAUSE
You may have entered an invalid editor name.
ACTION
Read system error messages to determine the cause of the error
and take corrective actions. If error persists, contact your system
administrator.
MESSAGE
Encountered ! ! while removing expsqlgn. (DBERR 719)
CAUSE
File system error occurred while purging the temporary le
EXPSQLGN used during le expansion.
ACTION
Read system error messages to determine the cause of the error
and take corrective action. If error persists, contact your system
administrator.
ALLBASE/SQL Error Messages
720
721
722
723
724
725
MESSAGE
Encountered Error # ! while retrieving DBECon info.
(DBERR 720)
CAUSE
An error occurred while calling a DBCore procedure.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Unacceptable editor name entered. (DBERR 721)
CAUSE
The editor name you entered is invalid. Check the spelling.
ACTION
Enter a valid editor name.
MESSAGE
Could not open specified file. (DBERR 722)
CAUSE
Failed to open an existing le.
ACTION
Read the le system error messages to determine the cause of the
error and take corrective action. If error persists, contact your
system administrator.
MESSAGE
Invalid option encountered on command line. (DBERR 723)
CAUSE
The option encountered on the command line contained an
invalid parameter.
ACTION
Make sure the command line contains only valid parameters.
MESSAGE
Invalid Schema File name entered. (DBERR 724)
CAUSE
The Schema File name you entered did not match operating
system naming conventions.
ACTION
Reenter, using a valid Schema File Name.
MESSAGE
Error occurred while writing to output file. (DBERR 725)
CAUSE
A le system error occurred while writing to the Schema File.
ACTION
Contact your system administrator.
ALLBASE/SQL Error Messages
3-35
726
727
728
729
730
3-36
MESSAGE
Error occurred while expanding file. (DBERR 726)
CAUSE
A le system error occurred while moving data from the Schema
File to the temporary le EXPSQLGN.
ACTION
Contact your system administrator.
MESSAGE
Error occurred while appending to file. (DBERR 727)
CAUSE
A le system error occurred while opening the Schema File in
APPEND mode.
ACTION
Contact your system administrator.
MESSAGE
Encountered EOF on input file. (DBERR 728)
CAUSE
The le you specied as redirected input ran out of commands
before exiting SQLGEN.
ACTION
Check the output and input to determine whether all commands
executed properly.
MESSAGE
Unacceptable response to prompt (will use default).
(DBERR 729)
CAUSE
You entered an invalid response to the last prompt.
ACTION
Enter a valid response.
MESSAGE
Encountered error during ROLLBACK WORK. (DBERR 730)
CAUSE
An ALLBASE/SQL error was encountered during ROLLBACK
WORK.
ACTION
Contact your database administrator. If necessary, record as
much information as possible, and contact your HP Service
Representative or Response Center.
ALLBASE/SQL Error Messages
744
745
746
747
748
MESSAGE
Invalid native language character encountered. (DBERR
744)
CAUSE
An unrecognized native language character was encountered. The
character does not belong to the present character set as specied
by the LANG environment variable.
ACTION
Reenter the user input using only characters found in the
character set of the current language.
MESSAGE
Unexpected internal native language error encountered.
(DBERR 745)
CAUSE
An unexpected error occurred while using an internal native
language procedure.
ACTION
Record as much information as possible and contact your
ALLBASE/SQL Service Representative or Response Center.
MESSAGE
Invalid Constraint Index Type encountered. (DBERR 746)
CAUSE
Internal Error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Invalid Default Type encountered TYPE=<val> (DBERR 747)
CAUSE
Internal Error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Invalid Constraint Type encountered. (DBERR 748)
CAUSE
Internal Error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
3-37
1001
1002
MESSAGE
Syntax error. (DBERR 1001)
CAUSE
You entered the Command incorrectly.
ACTION
Correct the syntax using the CHANGE or REDO command in
ISQL, or use an editor to correct your source code. You can use
the ISQL HELP command to verify your syntax.
MESSAGE
Identifier too long. (DBERR 1002)
CAUSE
One of the keywords you specied in the SQL statement was too
long. This was probably caused by a typographical error such as
not leaving a blank space between keywords
or
one of the variable names you specied was too long.
ACTION
Issue the command again correcting the keywords which were
entered incorrectly
or
choose a variable name that is less than or equal to 30 bytes.
1003
1004
3-38
MESSAGE
Single-quoted string too long. (DBERR 1003)
CAUSE
The string enclosed in single quotes in your SQL statement is too
long.
ACTION
Issue the command again, specifying a string which contains less
than or equal to 3,996 bytes.
MESSAGE
Expected end of string character. (DBERR 1004)
CAUSE
String was not terminated with a quotation mark.
ACTION
Issue the command again terminating the string with a quotation
mark.
ALLBASE/SQL Error Messages
1005
1006
1007
1008
1009
MESSAGE
Expected something between the double quotes. (DBERR
1005)
CAUSE
In the command where a database object was referenced, you did
not specify an object name within the quotes.
ACTION
Issue the command again, specifying an appropriate name within
quotes.
MESSAGE
Unexpected keyword. (DBERR 1006)
CAUSE
The syntax was incorrect for the command specied.
ACTION
Refer to the ALLBASE/SQL Reference Manual for the correct
syntax and issue the command again.
MESSAGE
DBEnvironment name is too long. (DBERR 1007)
CAUSE
A DBEnvironment name is restricted to operating system le
naming conventions.
ACTION
Refer to the A Beginner's Guide to HP-UX for le naming
conventions.
MESSAGE
Query too large. (DBERR 1008)
CAUSE
The internal buer space has been exceeded.
ACTION
Break the query into smaller units and issue the command again.
MESSAGE
Double-quoted string too long. (DBERR 1009)
CAUSE
The string enclosed in double quotes was too long.
ACTION
Issue the command again, specifying an object name containing
less than or equal to 20 bytes.
ALLBASE/SQL Error Messages
3-39
1010
1011
1012
1013
3-40
MESSAGE
Duplicate DBEFile0 clause defined. (DBERR 1010)
CAUSE
You specied the DBEFile0 clause twice in the START DBE
NEW statement.
ACTION
Issue the START DBE NEW statement again, specifying the
DBEFile0 only once. Refer to the ALLBASE/SQL Reference
Manual for additional information on the START DBE NEW
statement.
MESSAGE
Duplicate LOG DBEFile clause defined. (DBERR 1011)
CAUSE
You specied the LOG DBEFILE clause twice in the START
DBE NEW or START DBE NEWLOG statement.
ACTION
Issue the command again, specifying the LOG DBEFILE only
once. Refer to the ALLBASE/SQL Reference Manual for
additional information on the START DBE NEW and START
DBE NEWLOG statements.
MESSAGE
Duplicate TRANSACTION clause defined. (DBERR 1012)
CAUSE
You specied the transaction clause twice in the START DBE
NEW, START DBE, START DBE NEWLOG, or START DBE
RECOVER command.
ACTION
Issue the command again, specifying the transaction clause
only once. Refer to the ALLBASE/SQL Reference Manual for
additional information on the specic command.
MESSAGE
Duplicate BUFFER clause defined. (DBERR 1013)
CAUSE
You specied the BUFFER clause twice in the START DBE
NEW, START DBE, START DBE NEWLOG, or START DBE
RECOVER command.
ACTION
Issue the command again, specifying the BUFFER clause only
once. Refer to the ALLBASE/SQL Reference Manual for
additional information on the specic command.
ALLBASE/SQL Error Messages
1014
1015
1016
1017
1018
MESSAGE
Statement is not supported yet. (DBERR 1014)
CAUSE
The statement you specied is not supported by ALLBASE/SQL.
ACTION
Refer to the ALLBASE/ISQL Reference Manual and the
ALLBASE/SQL Reference Manual for descriptions of available
commands.
MESSAGE
Invalid file name. (DBERR 1015)
CAUSE
The le name you specied in the CREATE DBEFILE or START
DBE statement is too long.
ACTION
Refer to A Beginner's Guide to HP-UX for le naming
conventions.
MESSAGE
Owner id too long. (DBERR 1016)
CAUSE
The owner name you specied in the command(s) exceeds the
20-character maximum allowed for basic names.
ACTION
Issue the command again, specifying a valid owner name. Refer
to the ALLBASE/SQL Reference Manual for naming conventions.
MESSAGE
Column number for ORDER BY must be greater than 0. (DBERR
1017)
CAUSE
The column number in the ORDER BY clause was less than or
equal zero. The SELECT statement was aborted.
ACTION
Issue the SELECT statement again, specifying a column number
greater than zero.
MESSAGE
Aggregate functions not allowed in the WHERE clause.
(DBERR 1018)
CAUSE
You specied an aggregate function in the WHERE clause of the
query.
ACTION
Move the boolean expression using the aggregate from
the WHERE clause to the HAVING clause. Refer to the
ALLBASE/SQL Reference Manual for additional information on
aggregates.
ALLBASE/SQL Error Messages
3-41
1019
1020
1021
1022
1023
3-42
MESSAGE
Parameters not supported yet. (DBERR 1019)
CAUSE
You included a clause which is not valid for the specied
command.
ACTION
Refer to the ALLBASE/SQL Reference Manual for additional
information on the specied command.
MESSAGE
Statement not allowed in PREPARE statement. (DBERR 1020)
CAUSE
You included a statement in the PREPARE statement which is
not valid.
ACTION
Refer to the ALLBASE/SQL Reference Manual for additional
information on the PREPARE statement.
MESSAGE
Semantic error. (DBERR 1021)
CAUSE
You included a clause which is not valid for the specied
statement.
ACTION
Refer to the ALLBASE/SQL Reference Manual for additional
information on the statement.
MESSAGE
Constant number is out of representable range. (DBERR
1022)
CAUSE
The constant you gave in an INSERT statement or as part of an
expression is too large.
ACTION
Refer to the ALLBASE/SQL Reference Manual for additional
information on data data types.
MESSAGE
Duplicate tables in the FROM list. (DBERR 1023)
CAUSE
You specied the same table twice in the FROM clause of the
statement. The statement was not executed.
ACTION
Issue the SELECT statement again, specifying each table only
once. Refer to the ALLBASE/SQL Reference Manual for
additional information on the SELECT statement.
ALLBASE/SQL Error Messages
1024
1025
1026
1027
MESSAGE
Table in expression not in FROM list. (DBERR 1024)
CAUSE
You used a column from a table in an expression, but you did not
include the table in the FROM clause.
ACTION
Issue the SELECT statement again adding the specied table
to the FROM list or remove the expression referencing the
table before executing the command again. Refer to the
ALLBASE/SQL Reference Manual for additional information on
the SELECT statement.
MESSAGE
Number of columns does not match number of values. (DBERR
1025)
CAUSE
The number of columns you specied in an INSERT statement
does not match the number of values in the VALUES clause.
ACTION
Issue the INSERT statement again, specifying the same value
in the VALUES clause and the number of columns specied.
Refer to the ALLBASE/SQL Reference Manual for additional
information on the INSERT statement.
MESSAGE
Numeric value too long. (DBERR 1026)
CAUSE
You attempted to enter a TID eld greater than 80 digits long.
ACTION
Shorten any TID eld greater than 80 digits and reissue the
statement.
MESSAGE
Float precision specified not in valid range. (DBERR
1027)
CAUSE
You specied a precision outside the range 1 - 53 in a column
dened to be of type FLOAT(precision).
ACTION
Check your syntax and reissue the command with a legal
precision value.
ALLBASE/SQL Error Messages
3-43
1028
1030
1031
1032
3-44
MESSAGE
UPDATE not allowed with ORDER BY. (DBERR 1028)
CAUSE
You specied both an UPDATE clause and an ORDER BY
clause in the DECLARE CURSOR statement.
ACTION
Modify the command specifying either an UPDATE clause or an
ORDER BY clause, but not both. Refer to the ALLBASE/SQL
Reference Manual for additional information on the DECLARE
CURSOR statement.
MESSAGE
Host variables not allowed in CREATE VIEW. (DBERR 1030)
CAUSE
You specied a host variable in the SELECT statement of the
VIEW command.
ACTION
Remove the host variable from the command. Refer to the
ALLBASE/SQL Reference Manual for additional information
on the CREATE VIEW command and to the appropriate
ALLBASE/SQL application programming guide for additional
information on host variables.
MESSAGE
Host variables not allowed in the command to be PREPAREd.
(DBERR 1031)
CAUSE
You specied a host variable in the PREPARE statement.
ACTION
Remove the host variable and issue the command again.
Refer the ALLBASE/SQL Reference Manual for additional
information on the PREPARE statement and to the appropriate
ALLBASE/SQL application programming guide for additional
information on host variables.
MESSAGE
Aggregate function can not be nested. (DBERR 1032)
CAUSE
The aggregate function you specied in the SELECT statement
contained an aggregate function.
ACTION
Issue the command again without nesting aggregate functions.
Refer to the ALLBASE/SQL Reference Manual for additional
information on the SELECT statement.
ALLBASE/SQL Error Messages
1038
1039
1040
1041
1042
MESSAGE
Two log and file names needed if DUAL LOG. (DBERR 1038)
CAUSE
You specied only one log name and/or le name in the START
DBE NEW or you specied a START DBE NEWLOG statement
and DUAL LOG in the LOG clause.
ACTION
Issue the command again, specifying two log and le names.
Refer to the ALLBASE/SQL Reference Manual for additional
information on the START DBE NEW and START DBE
NEWLOG statements.
MESSAGE
Number of columns must match number of host variables or
dynamic parameters. (DBERR 1039)
CAUSE
The number of host variables did not match the number of
columns or dynamic parameters in the INSERT statement.
ACTION
Revise your program to modify the host variable declarations
and/or the INSERT statement references to host variables.
Refer to the ALLBASE/SQL Reference Manual for additional
information on the INSERT statement.
MESSAGE
User id is too long. (DBERR 1040)
CAUSE
The length of the DBEUserID you specied was not within the
range of 1 through 20 bytes.
ACTION
Issue the command again, specifying a valid DBEUserID.
MESSAGE
Duplicate type of authority specified. (DBERR 1041)
CAUSE
You specied the same type of authority twice in either the
GRANT or REVOKE statement.
ACTION
Issue the command again, specifying each type of authority only
once.
MESSAGE
Duplicate columns specified. (DBERR 1042)
CAUSE
The same column was specied twice in the UPDATE option of
either the GRANT or REVOKE statement.
ACTION
Issue the command again, specifying each column only once.
ALLBASE/SQL Error Messages
3-45
1043
1044
1045
1046
1047
3-46
MESSAGE
Column names required. (DBERR 1043)
CAUSE
You did not specify column names in the CREATE VIEW
statement.
ACTION
Issue the command again, specifying the column names in
parentheses. Refer to the ALLBASE/SQL Reference Manual for
additional information on the CREATE VIEW statement.
MESSAGE
Scale must not be larger than precision. (DBERR 1044)
CAUSE
The number of decimal places (scale) was greater than the the
number of digits (precision) specied in the CREATE TABLE
statement.
ACTION
Issue the command again, specifying the scale as less than or
equal to precision.
MESSAGE
DUAL LOG specified multiple times. (DBERR 1045)
CAUSE
The DUAL LOG option was specied more than once in the
START DBE NEW or START DBE NEWLOG statement.
ACTION
Issue the command again, specifying DUAL LOG only once.
Refer to the ALLBASE/SQL Reference Manual for additional
information.
MESSAGE
Failed to allocate heap space (DBERR 1046)
CAUSE
There was no memory available for your query.
ACTION
Report this error to your database administrator and try you
again later. If the problem persists, record as much information
as possible and contact your HP Service Representative or
Response Center.
MESSAGE
Failed to free heap space (DBERR 1047)
CAUSE
Internal error.
ACTION
Report this error to your database administrator. If the problem
persists, record as much information as possible and contact your
HP Service Representative or Response Center.
ALLBASE/SQL Error Messages
1048
1049
1050
1051
1052
MESSAGE
Number of precision digits for this decimal constant
exceeds 27. (DBERR 1048)
CAUSE
A constant specied in the INSERT, UPDATE, SELECT,
DELETE, or DECLARE CURSOR statement contained more
than 27 digits.
ACTION
Correct your query so that all constants contain less than or
equal to 27 decimal digits.
MESSAGE
Dynamic query size exceeds input buffer size. (DBERR
1049)
CAUSE
The query included in the dynamic SQL command (PREPARE or
EXECUTE IMMEDIATE) is larger than the input buer.
ACTION
Reduce the size of your query or put it in a host variable where it
can be up to 32,762 bytes in length.
MESSAGE
Statement not allowed in EXECUTE IMMEDIATE statement.
(DBERR 1050)
CAUSE
The statement included in the EXECUTE IMMEDIATE cannot
be used dynamically.
ACTION
Use the EXECUTE statement in the regular way through ISQL
or the preprocessor, not in EXECUTE IMMEDIATE.
MESSAGE
SQL Parser internal NLS error. (DBERR 1051)
CAUSE
An internal Native Language Support error occurred within the
parser, probably due to an invalid character in input.
ACTION
Check your input for invalid bytes, and try again.
MESSAGE
Invalid character found in SQL command. (DBERR 1052)
CAUSE
An SQL statement contained an invalid Native Language Support
(NLS) character.
ACTION
Check the NLS characters in the SQL statement and issue it
again.
ALLBASE/SQL Error Messages
3-47
1053
1054
1055
1057
1058
3-48
MESSAGE
Duplicate LANG clause defined. (DBERR 1053)
CAUSE
A command was issued with a duplicate LANG clause.
ACTION
Correct the command and issue it again.
MESSAGE
Invalid LANG specified. (DBERR 1054)
CAUSE
You attempted to specify a language that is not congured on the
system possibly because of misspelling.
ACTION
Specify a valid language, then reissue the command to create the
object.
MESSAGE
Language clause not valid with non-character column.
(DBERR 1055)
CAUSE
You tried to dene a non-character column as having a language
type.
ACTION
Specify the language type with the appropriate character column.
MESSAGE
DEFAULT NULL is specified, NOT NULL is not allowed. (DBERR
1057)
CAUSE
DEFAULT NULL and NOT NULL cannot be specied at the
same time.
ACTION
Either remove the DEFAULT NULL clause or remove the NOT
NULL clause.
MESSAGE
Number of referenced columns must match number of foreign
key columns. (DBERR 1058)
CAUSE
The number of columns in the column list following REFERENCES was greater than one for a column-level constraint, or did
not match the number of columns in a FOREIGN KEY column
list for a table level constraint in a CREATE TABLE statement.
ACTION
Check your syntax and correct the number of columns.
ALLBASE/SQL Error Messages
1059
1060
1061
1062
MESSAGE
Aggregate, subquery, or host variable disallowed in CHECK
constraint or rule. (DBERR 1059)
CAUSE
A CHECK constraint or RULE was dened with one of these
items in it.
ACTION
Check the syntax and remove the aggregate, subquery, or host
variable from your CHECK constraint or RULE.
MESSAGE
Constraint name beginning with SQLCON_ disallowed. (DBERR
1060)
CAUSE
A CONSTRAINT clause was specied with a name starting
with 'SQLCON ' in your CREATE TABLE or CREATE VIEW
statement.
ACTION
Remove the CONSTRAINT clause or choose a dierent
constraint name.
MESSAGE
The syntax PRIMARY KEY may only be used once in
CREATE/ALTER TABLE. (DBERR 1061)
CAUSE
The syntax PRIMARY KEY appears more than once in your
CREATE TABLE statement.
ACTION
Check the syntax and remove all but one of the PRIMARY KEY
specications, or change all but one to UNIQUE.
MESSAGE
HASH ON CONSTRAINT clause did not match any unique
constraint name. (DBERR 1062)
CAUSE
The constraint named in your HASH ON CONSTRAINT clause
was not found in the CREATE TABLE statement.
ACTION
Check the syntax and use the name of a named unique constraint
in the HASH ON CONSTRAINT clause.
ALLBASE/SQL Error Messages
3-49
1063
1064
1065
1066
3-50
MESSAGE
HASH/CLUSTERING ON CONSTRAINT used without a PRIMARY KEY.
(DBERR 1063)
CAUSE
The syntax HASH/CLUSTERING ON CONSTRAINT is used
without a constraint name, and no PRIMARY KEY was dened
in the CREATE TABLE statement.
ACTION
Check the syntax and either dene a PRIMARY KEY or
add a constraint name to the HASH/CLUSTERING ON
CONSTRAINT clause.
MESSAGE
CLUSTERING ON CONSTRAINT clause did not match any unique
or referential constraint name. (DBERR 1064)
CAUSE
The constraint named in your CLUSTERING ON CONSTRAINT clause was not found in the CREATE TABLE
statement.
ACTION
Check the syntax and use the name of a named unique or
referential constraint in the CLUSTERING ON CONSTRAINT
clause.
MESSAGE
Multiple definition of a column integrity constraint
disallowed. (DBERR 1065)
CAUSE
You used the syntax NOT NULL, LANG =, CHECK, UNIQUE,
PRIMARY KEY, or REFERENCES more than once in a column
denition in an ALTER TABLE or CREATE TABLE statement.
ACTION
Remove the extra constraint(s); if more than one CHECK exists,
the expressions within them can be ANDed together within a
single CHECK.
MESSAGE
Illegal hexadecimal number specified. (DBERR 1066)
CAUSE
You specied non-hexadecimal characters for the BINARY/VARBINARY eld.
ACTION
Refer to the chapter \Data Types" in the ALLBASE/SQL
Reference Manual for proper syntax.
ALLBASE/SQL Error Messages
1067
1068
1069
1071
1072
MESSAGE
Invalid location name. (DBERR 1067)
CAUSE
The location name specied in the CREATE TEMPSPACE
statement is too long.
ACTION
Refer to A Beginner's Guide to HP-UX for le naming
conventions.
MESSAGE
DEFAULT clause is not allowed for LONG data type column.
(DBERR 1068)
CAUSE
You specied a DEFAULT clause for a column which is dened as
LONG data type.
ACTION
Remove the DEFAULT clause.
MESSAGE
RECOVER option is not supported in START DBE command.
(DBERR 1069)
CAUSE
The START DBE RECOVER command is no longer available.
ACTION
No action necessary. Refer to the ALLBASE/SQL Database
Administration Guide for information on recovery.
MESSAGE
Syntax combination of dynamic parameter and host variable
disallowed. (DBERR 1071)
CAUSE
You used both a dynamic parameter and a host variable in the
statement.
ACTION
Modify your statement to contain only dynamic parameters or
only host variables.
MESSAGE
Dynamic parameter is allowed in the PREPARE command only.
(DBERR 1072)
CAUSE
You used a dynamic parameter in a statement that has not been
prepared.
ACTION
Either prepare the statement using the PREPARE statement or
remove the dynamic parameters from the statement.
ALLBASE/SQL Error Messages
3-51
1073
1074
1075
MESSAGE
Dynamic parameter as the argument of an aggregate function
disallowed. (DBERR 1073)
CAUSE
You used a dynamic parameter as the argument of an aggregate
function.
ACTION
Modify your statement to not use a dynamic parameter as the
argument of an aggregate function.
MESSAGE
Two log files specified without DUAL LOG. (DBERR 1074)
CAUSE
You have specied two log les without also specifying DUAL
LOG.
ACTION
Remove one of the log le specications or specify DUAL LOG.
MESSAGE
TID function cannot be used in a HAVING clause. (DBERR
1075)
CAUSE
You cannot specify the TID function in a HAVING clause.
Check and modify the command.
ACTION
1076
1077
1078
3-52
MESSAGE
TID function cannot be used along with aggregate function
in the SELECT list. (DBERR 1076)
CAUSE
ACTION
You cannot specify the TID function with an aggregate function
in t he select list.
Check and modify the command.
MESSAGE
HP SQL internal error in SPALEXI. (DBERR 1077)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
service representative or Response Center.
MESSAGE
HP/SQL internal error in SLNPRE. (DBERR 1078)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
service representative or Response Center.
ALLBASE/SQL Error Messages
1079
1080
1081
1082
1083
1084
MESSAGE
HP/SQL internal error in SLNMAIN. (DBERR 1079)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
service representative or Response Center.
MESSAGE
Duplicate DEFAULT PARTITION clause defined. (DBERR 1080)
CAUSE
More than one DEFAULT PARTITION clause appears in the
START DBE NEW or START DBE NEWLOG clause.
ACTION
Check the specied START DBE statement.
MESSAGE
Duplicate MAXPARTITIONS clause defined. (DBERR 1081)
CAUSE
The keyword MAXPARTITIONS appears more than once in the
START DBE NEW or START DBE NEWLOG clause.
ACTION
Check the specied START DBE statement.
MESSAGE
AUDIT LOG specified multiple times. (DBERR 1082)
CAUSE
You specied the AUDIT LOG clause more than once in the
START DBE NEW or START DBE NEWLOG statement.
ACTION
Check the specied START DBE statement.
MESSAGE
ARCHIVE LOG specified multiple times. (DBERR 1083)
CAUSE
You specied the ARCHIVE LOG clause more than once in the
START DBE NEWLOG statement.
ACTION
Check the specied START DBE statement.
MESSAGE
Duplicate AUDIT NAME clause defined. (DBERR 1084)
CAUSE
You specied the AUDIT NAME clause appears more than once
in the START DBE NEW or START DBE NEWLOG syntax.
ACTION
Check the specied START DBE statement.
ALLBASE/SQL Error Messages
3-53
1085
1086
1088
1089
1090
1091
MESSAGE
AUDIT NAME too long. (DBERR 1085)
CAUSE
You specied an AUDIT NAME longer than 8 bytes.
ACTION
Check the specied START DBE statement.
MESSAGE
INCREMENT size specified not in valid range. (DBERR 1086)
CAUSE
The INCREMENT size for DBEFile expansion cannot be zero.
ACTION
Make sure the INCREMENT size is within the valid range.
MESSAGE
Duplicate AUDIT ELEMENT specified. (DBERR 1088)
CAUSE
You specied an AUDIT ELEMENT more than once in the
AUDIT ELEMENTS clause of the START DBE NEW or START
DBE NEWLOG statement.
ACTION
Check the specied START DBE statement.
MESSAGE
Duplicate COMMENT PARTITION clause defined. (DBERR 1089)
CAUSE
You have more than one COMMENT PARTITION clause in the
START DBE NEW or START DBE NEWLOG statement.
ACTION
Check the specied START DBE statement.
MESSAGE
Dynamic Parameters cannot be used as both the first and the
second operands in a BETWEEN predicate. (DBERR 1090)
CAUSE
You specied dynamic parameters as both the rst and the
second operands in a BETWEEN predicate.
ACTION
Modify your statement to not contain dynamic parameters as
both the rst and second operands of the BETWEEN predicate.
MESSAGE
TID function cannot be used as the argument of the
aggregate function. (DBERR 1091)
CAUSE
You cannot use the TID function as the argument of an aggregate
function.
Check and modify the command.
ACTION
3-54
ALLBASE/SQL Error Messages
1092
1093
1094
1095
MESSAGE
Duplicate constraint type specified. (DBERR 1092)
CAUSE
You specied the same constraint type more than once in a SET
CONSTRAINTS statement.
ACTION
Remove the duplicate constraint type(s) and reissue the
statement.
MESSAGE
Default timeout value out of valid range. (DBERR 1093)
CAUSE
The default timeout value you specied is invalid.
ACTION
Verify that the default timeout value is within the valid range.
MESSAGE
Maximum timeout value out of valid range. (DBERR 1094)
CAUSE
The maximum timeout value you specied is invalid.
ACTION
Verify that the maximum timeout value is within the valid range.
MESSAGE
Default timeout value exceeds maximum timeout limit.
(DBERR 1095)
CAUSE
The default timeout value is greater than the maximum timeout
limit.
ACTION
Set the default timeout to a value less than or equal to the
maximum timeout limit
or
set the maximum timeout limit to a value greater than or equal
to the default timeout value.
1096
MESSAGE
DEFAULT TIMEOUT specified multiple times. (DBERR 1096)
CAUSE
You specied the DEFAULT TIMEOUT clause more than once
in either the START DBE, START DBE NEW, or STARTDBE
NEWLOG statement.
ACTION
Issue the statement again, specifying the DEFAULT TIMEOUT
clause only once.
ALLBASE/SQL Error Messages
3-55
1097
1098
1099
1100
1101
3-56
MESSAGE
MAXIMUM TIMEOUT specified multiple times. (DBERR 1097).
CAUSE
You specied the MAXIMUM TIMEOUT clause more than once
in either the START DBE, START DBE NEW, or STARTDBE
NEWLOG statement.
ACTION
Issue the statement again, specifying the MAXIMUM TIMEOUT
clause only once.
MESSAGE
User timeout value out of valid range. (DBERR 1098)
CAUSE
The specied user timeout is invalid.
ACTION
Verify that the user timeout value is within the valid range.
MESSAGE
GENPLAN accepts SELECT, UPDATE, and DELETE statements
only. (DBERR 1099)
CAUSE
A SELECT, UPDATE, or DELETE statement is expected.
ACTION
Issue GENPLAN for a statement of one of the above types.
MESSAGE
VariableName in WHERE clause has not been defined in the
WITH clause of GENPLAN. (DBERR 1100)
CAUSE
A VariableName in the WHERE clause of the statement
contained in GENPLAN has not been dened in the WITH
clause of the GENPLAN statement.
ACTION
Add the VariableName with the appropriate data type to the
WITH clause of the GENPLAN statement.
MESSAGE
A language, default, or column constraint clause is not
allowed in the WITH clause of GENPLAN. (DBERR 1101)
CAUSE
A language, default, or column constraint clause was found in the
WITH clause of GENPLAN.
ACTION
Remove the language, default, or column clause from the WITH
clause of GENPLAN.
ALLBASE/SQL Error Messages
1102
1103
1104
1105
1106
MESSAGE
SQL Linearizer internal NLS error. (DBERR 1102)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Duplicate VariableName found in the WITH clause of
GENPLAN. (DBERR 1103)
CAUSE
The WITH clause of GENPLAN has a duplicate VariableName .
ACTION
Rename or remove the duplicate VariableName from the WITH
clause of GENPLAN.
MESSAGE
Duplicate RUN BLOCK clause defined. (DBERR 1104)
CAUSE
You specied the RUN BLOCK clause twice in the START DBE
or START DBE NEW statement.
ACTION
Issue the command again specifying the RUN BLOCK clause
once.
MESSAGE
USER not permitted in table CHECK constraint. (DBERR
1105)
CAUSE
You specied a CHECK constraint with USER.
ACTION
Remove the use of USER in the CHECK constraint and reissue
the statement.
MESSAGE
CURRENT_DATE not permitted in table CHECK constraint.
(DBERR 1106)
CAUSE
You specied a CHECK constraint with CURRENT DATE.
ACTION
Remove the use of CURRENT DATE in the CHECK constraint
and reissue the statement.
ALLBASE/SQL Error Messages
3-57
1107
1108
1109
1110
1111
3-58
MESSAGE
CURRENT_TIME not permitted in table CHECK constraint.
(DBERR 1107)
CAUSE
You specied a CHECK constraint with CURRENT TIME.
ACTION
Remove the use of CURRENT TIME in the CHECK constraint
and reissue the statement.
MESSAGE
CURRENT_DATETIME not permitted in table CHECK constraint.
(DBERR 1108)
CAUSE
You specied a CHECK constraint with CURRENT DATETIME.
ACTION
Remove the use of CURRENT DATETIME in the CHECK
constraint and reissue the statement.
MESSAGE
! PARTITION value must be non-zero. (DBERR 1109)
CAUSE
You specied a DEFAULT, MAXPARTITIONS, or COMMENT
partition value of zero in the START DBE NEW or START DBE
NEWLOG statement.
ACTION
Check the specied START DBE statement and replace the zero
in the named partition value with a non-zero value.
MESSAGE
The label (!) is not an integer. (DBERR 1110)
CAUSE
For PASCAL and FORTRAN 77 applications, labels must be
integers. A label was found that was not an integer.
ACTION
Change the label to an integer.
MESSAGE
The label (!) is not an identifier name. (DBERR 1111)
CAUSE
For C and COBOL applications, labels must be identier names
which start with non-numeric characters. A label was found that
started with a numeric character.
ACTION
Change the label to start with a non-numeric character.
ALLBASE/SQL Error Messages
1120
1121
1122
1123
MESSAGE
Statement not allowed in stored procedure. (DBERR 1120)
CAUSE
The current statement is not permitted within a procedure.
ACTION
Issue the CREATE PROCEDURE statement again, omitting
the illegal statement. Refer to the description of the CREATE
PROCEDURE statement in the \SQL Statements" chapter of the
ALLBASE/SQL Reference Manual for a list of statements that
are not allowed in procedures.
MESSAGE
Local variable declarations must be at the beginning of a
stored procedure. (DBERR 1121)
CAUSE
The DECLARE statement was not at the beginning of the
procedure.
ACTION
Dene local variables with DECLARE statements at the
beginning of the procedure.
MESSAGE
Return Status in the RETURN statement must be an integer
value. (DBERR 1122)
CAUSE
The status value in the RETURN statement is not an integer
value.
ACTION
Use an integer value for the ReturnStatus in the RETURN
statement.
MESSAGE
Indicator variables are not allowed with parameters or
local variables used in a stored procedure statement.
(DBERR 1123)
CAUSE
You attempted to include an indicator variable with a
parameter declaration or with a local variable in the CREATE
PROCEDURE statement.
ACTION
Rewrite your CREATE PROCEDURE statement, eliminating
indicator variables.
ALLBASE/SQL Error Messages
3-59
1124
1125
1126
1127
3-60
MESSAGE
Element in Boolean expression is not allowed in current
procedure statement. (DBERR 1124)
CAUSE
The following elements are not allowed in the Condition of IF and
WHILE statements in a procedure: aggregate functions, TID
functions, long column functions, column references, DATETIME
conversion functions involving columns references, and subquery
expressions.
ACTION
Rewrite your CREATE PROCEDURE statement, eliminating the
illegal elements from the Condition.
MESSAGE
Undefined parameter, local variable or cursor. (DBERR
1125)
CAUSE
The parameter, variable, or cursor is referenced inside a
procedure without rst being dened.
ACTION
Dene the parameter, local variable, or cursor before referencing
it in the CREATE PROCEDURE statement.
MESSAGE
Doubly defined parameter, local variable or cursor.
(DBERR 1126)
CAUSE
You dened the parameter, local variable, or cursor more than
once.
ACTION
Check your parameter list, local variable declaration, or cursor
denition and reissue the CREATE PROCEDURE statement.
MESSAGE
Built-in-variable is not allowed in an SQL statement.
(DBERR 1127)
CAUSE
You used a built-in variable in an SQL statement. Built-in
variables can only be used in non-SQL statements inside a
procedure.
ACTION
Check the expressions in the procedure's SQL statements, and
reissue the CREATE PROCEDURE statement.
ALLBASE/SQL Error Messages
1128
1129
1130
1131
1132
MESSAGE
A local variable or parameter is required for this SQL
statement in a stored procedure. (DBERR 1128)
CAUSE
You used the SELECT, FETCH, or REFETCH statement inside
a procedure without specifying a local variable or parameter.
ACTION
Reissue the CREATE PROCEDURE statement including the
appropriate local variable or parameter along with the SELECT,
FETCH, or REFETCH.
MESSAGE
OUTPUT option is allowed only for host variables in
EXECUTE PROCEDURE. (DBERR 1129)
CAUSE
You attempted to use the OUTPUT option without specifying a
host variable in the EXECUTE PROCEDURE statement in an
application program.
ACTION
Check the actual parameters of your EXECUTE PROCEDURE
statement and eliminate the illegal use of the OUTPUT option.
MESSAGE
The LONG data type is not allowed for a parameter or local
variable in a stored procedure. (DBERR 1130)
CAUSE
You attempted to declare a parameter or local variable with the
LONG data type in the CREATE PROCEDURE statement.
ACTION
Reissue the CREATE PROCEDURE statement without the
LONG parameter or variable declaration.
MESSAGE
No LABEL is allowed for this procedure statement. (DBERR
1131)
CAUSE
No label is allowed in the DECLARE Variable statement, the
WHENEVER statement, or compound statements.
ACTION
Remove the illegal label and reissue the CREATE PROCEDURE
statement.
MESSAGE
Cursor name must be a single identifier. (DBERR 1132)
CAUSE
You attempted to qualify a cursor name with an owner or module
name.
ACTION
Delete the cursor name qualication in the specied statement
and reissue the CREATE PROCEDURE statement.
ALLBASE/SQL Error Messages
3-61
1133
1134
1135
1136
3-62
MESSAGE
No INTO clause is allowed in the SELECT statement of a
DECLARE CURSOR. (DBERR 1133)
CAUSE
You attempted to use an INTO clause inside a cursor declaration
in a procedure.
ACTION
Check the SELECT portion of your DECLARE CURSOR
statement to make sure there is no INTO clause, and reissue the
CREATE PROCEDURE statement. Use the INTO clause in the
FETCH statement.
MESSAGE
Local variable data type is invalid. (DBERR 1134)
CAUSE
You attempted to use a non-integer local variable or parameter in
a SAVEPOINT, ROLLBACK WORK TO SAVEPOINT, or SET
TIMEOUT statement in a procedure.
ACTION
Correct the data type for the local variable or parameter and
reissue the CREATE PROCEDURE statement.
MESSAGE
A local variable/host variable is not allowed in an inner
query block. (DBERR 1135)
CAUSE
You attempted to use a local or host variable in a nested query
block or in any query block in a UNION other than the rst
UNION block.
ACTION
Remove the illegal variable reference in the query.
MESSAGE
The number of parameters defined exceeds the maximum of
255. (DBERR 1136)
CAUSE
You attempted to specify more than the maximum of 255
parameters in a CREATE PROCEDURE or EXECUTE
PROCEDURE statement.
ACTION
Reissue the CREATE PROCEDURE or EXECUTE
PROCEDURE statement using 255 or fewer parameters.
ALLBASE/SQL Error Messages
1137
1138
1139
MESSAGE
The expression in a variable or parameter assignment
statement contains an element that is not allowed in a
stored procedure. (DBERR 1137)
CAUSE
You used one of the following elements, which are not allowed
in the expression of an assignment statement in a procedure:
column reference, subquery, dynamic parameter, aggregate
function, TID function, long column function, or date/time
conversion function involving a column reference.
ACTION
Reissue the CREATE PROCEDURE statement , eliminating the
illegal elements from the expression.
MESSAGE
The expression in an actual parameter contains an element
that is not allowed in the EXECUTE PROCEDURE statement.
(DBERR 1138)
CAUSE
The following elements are not allowed in an expression in an
actual parameter in the EXECUTE PROCEDURE statement:
column reference, subquery, dynamic parameter, aggregate
function, TID function, long column function, or date/time
conversion function involving a column reference.
ACTION
Rewrite your EXECUTE PROCEDURE statement, eliminating
the illegal element from the expression in the actual parameter.
MESSAGE
The OUTPUT option is not allowed for parameters that
contain an expression in the EXECUTE PROCEDURE statement.
(DBERR 1139)
CAUSE
You attempted to use the OUTPUT option with a parameter
that contains an expression in an EXECUTE PROCEDURE
statement within an application program.
ACTION
Check the actual parameters of your EXECUTE PROCEDURE
statement and eliminate the illegal use of the OUTPUT option.
ALLBASE/SQL Error Messages
3-63
1140
1141
1142
1143
3-64
MESSAGE
The language clause is not valid with a non-character
parameter or variable in the CREATE PROCEDURE statement.
(DBERR 1140)
CAUSE
You specied a language for a parameter, variable, or result of a
non-character data type in a CREATE PROCEDURE statement.
ACTION
Reissue the CREATE PROCEDURE statement, omitting the
language clause for any parameter, variable, or result of a
non-character data type.
MESSAGE
No value was provided for a named list parameter in the
EXECUTE PROCEDURE statement. (DBERR 1141)
CAUSE
You specied the name of a parameter in a named parameter list,
but you did not specify a value for the parameter.
ACTION
Check the parameter list included in the EXECUTE
PROCEDURE statement, and ensure that you supply a value for
each parameter. Then reissue the EXECUTE PROCEDURE
statement.
MESSAGE
Named list and ordered list parameters cannot be mixed in
the EXECUTE PROCEDURE statement. (DBERR 1142)
CAUSE
You specied one or more named parameters together with one or
more ordered parameters in the same EXECUTE PROCEDURE
statement. A parameter list must be either an ordered list or a
named list and cannot mix parameters of both types.
ACTION
Check the parameter list included in the EXECUTE
PROCEDURE statement, and ensure that you use a consistent
parameter type in the parameter list. Then reissue the
EXECUTE PROCEDURE statement.
MESSAGE
Multiple values provided for single parameter in the
EXECUTE PROCEDURE statement. (DBERR 1143)
CAUSE
You used the same parameter name more than once in a named
parameter list in the EXECUTE PROCEDURE statement.
ACTION
Correct the EXECUTE PROCEDURE statement, making sure
that each parameter name is assigned only one value. Then
reissue the EXECUTE PROCEDURE statement.
ALLBASE/SQL Error Messages
1144
1145
1146
1147
1150
MESSAGE
The number of result columns defined exceeds the maximum
num of 1024. (DBERR 1144)
CAUSE
You specied more that 1024 result columns in a CREATE
PROCEDURE statement.
ACTION
Reissue the CREATE PROCEDURE statement, specifying no
more than 1024 result columns.
MESSAGE
Dynamic parameters are not allowed in procedure
statements. (DBERR 1145)
CAUSE
You included a dynamic parameter in a statement inside a
parameter.
ACTION
Reissue the CREATE PROCEDURE statement, omitting any
dynamic parameter.
MESSAGE
The WITH RESULT clause is allowed only for a procedure
returning results. (DBERR 1146)
CAUSE
You included the WITH RESULT clause in a CREATE
PROCEDURE statement, but the procedure returns no result
sets.
ACTION
Reissue the CREATE PROCEDURE statement, omitting the
WITH RESULT clause.
MESSAGE
DEFAULT clause is not allowed for an OUTPUT ONLY
parameter. (DBERR 1147)
CAUSE
You provided a default value for an OUTPUT ONLY parameter
in the CREATE PROCEDURE statement.
ACTION
Reissue the CREATE PROCEDURE statement, either omitting
the default value, or specifying OUTPUT rather than OUTPUT
ONLY.
MESSAGE
Host variables not allowed in CREATE RULE. (DBERR 1150)
CAUSE
You dened a RULE containing a host variable.
ACTION
Check the syntax and remove the host variable from your
CREATE RULE statement.
ALLBASE/SQL Error Messages
3-65
1151
1152
1153
1154
1155
3-66
MESSAGE
Duplicate statement type specified in CREATE RULE. (DBERR
1151)
CAUSE
You dened a RULE with duplicate statement types.
ACTION
Check the syntax and remove the duplicate statement type from
your CREATE RULE statement.
MESSAGE
TID function disallowed in CHECK constraint or RULE.
(DBERR 1152)
CAUSE
A RULE or CHECK constraint contains a TID function.
ACTION
Check the syntax and remove the TID function from your
CREATE RULE statement or CHECK constraint.
MESSAGE
RETURN clause not permitted in EXECUTE PROCEDURE of
CREATE RULE. (DBERR 1153)
CAUSE
You included a RETURN clause in the EXEC PROCEDURE
clause of a CREATE RULE statement.
ACTION
Remove the RETURN clause from the EXEC PROCEDURE
clause.
MESSAGE
OUTPUT parameters not permitted in EXECUTE PROCEDURE of
CREATE RULE. (DBERR 1154)
CAUSE
You included a parameter dened for OUTPUT in the
EXECUTE PROCEDURE clause of a CREATE RULE
statement.
ACTION
Remove the key word OUTPUT from the EXECUTE
PROCEDURE clause.
MESSAGE
Negative Hexstring is not allowed. (DBERR 1155)
CAUSE
You attempted to enter a negative hexstring.
ACTION
Remove the minus sign from the hexstring and reissue the
statement.
ALLBASE/SQL Error Messages
1156
1157
1158
1159
1160
MESSAGE
Duplicate ISOLATION LEVEL clause defined. (DBERR 1156)
CAUSE
You have more than one IDOLATION LEVEL clause in the SET
TRANSACTION or SET SESSION statement.
ACTION
Check the specied SET TRANSACTION or SET SESSION
statement.
MESSAGE
Duplicate PRIORITY clause defined. (DBERR 1157)
CAUSE
You specied the PRIORITY clause more than once in the SET
TRANSACTION or SET SESSION statement.
ACTION
Check the specied SET TRANSACTION or SET SESSION
statement.
MESSAGE
Duplicate LABEL clause defined. (DBERR 1158)
CAUSE
You included more than one LABEL clause in the SET
TRANSACTION or SET SESSION statement.
ACTION
Check the specied SET TRANSACTION or SET SESSION
statement.
MESSAGE
Duplicate CONSTRAINTS clause defined. (DBERR 1159)
CAUSE
You included more than one CONSTRAINTS clause in the SET
TRANSACTION or SET SESSION statement.
ACTION
Check the specied SET TRANSACTION or SET SESSION
statement.
MESSAGE
Duplicate DML ATOMICITY clause defined. (DBERR 1160)
CAUSE
You included more than one DML ATOMICITY clause in the
SET TRANSACTION or SET SESSION statement.
ACTION
Check the specied SET TRANSACTION or SET SESSION
statement.
ALLBASE/SQL Error Messages
3-67
1161
1163
1164
1165
1166
3-68
MESSAGE
Duplicate FILL clause defined. (DBERR 1161)
CAUSE
You included more than one FILL clause in the SET SESSION
statement.
ACTION
Check the specied SET SESSION statement.
MESSAGE
Device name specified exceed 44 characters. (DBERR 1163)
CAUSE
The device name in the CREATE DBEFILE command is too
long.
ACTION
Correct the device specication and reissue the CREATE
DBEFile command.
MESSAGE
The [NOT] CASE SENSITIVE attribute is not applicable on
non-character column. (DBERR 1164)
CAUSE
You applied a CASE SENSITIVE or NOT CASE SENSITIVE
keyword to a column which is not dened as a character column.
ACTION
Avoid applying CASE SENSITIVE or NOT CASE SENSITIVE
keywords to non-character columns.
MESSAGE
Duplicate USER TIMEOUT clause defined. (DBERR 1165)
CAUSE
A duplicate USER TIMEOUT clause was specied.
ACTION
No action required. The duplicate USER TIMEOUT clause will
be ignored.
MESSAGE
Duplicate on TIMEOUT/DEADLOCK clause defined. (DBERR
1166)
CAUSE
A duplicate TIMEOUT/DEADLOCK clause was specied.
ACTION
No action required. The duplicate TIMEOUT/DEADLOCK
clause will be ignored.
ALLBASE/SQL Error Messages
1167
1168
1169
1170
1171
MESSAGE
Duplicate TERMINATION clause defined. (DBERR 1167)
CAUSE
A duplicate TERMINATION clause was specied.
ACTION
No action required. The duplicate TERMINATION clause will be
ignored.
MESSAGE
Table name required. (DBERR 1168)
CAUSE
You issued a RENAME TABLE statement without a valid table
name.
ACTION
See syntax for RENAME TABLE in \SQL Statements" chapter
of the ALLBASE/SQL Reference Manual .
MESSAGE
Data type ! not allowed for CAST. (DBERR 1169)
CAUSE
An incorrect data type was specied for CAST.
ACTION
See the table, \Data Types for CAST Function," in the
\Expressions" chapter of the ALLBASE/SQL Reference Manual .
MESSAGE
Format specification is only allowed for date/time data
types. (DBERR 1170)
CAUSE
An incorrect format was specied.
ACTION
See the \Expressions" chapter of the ALLBASE/SQL Reference
Manual for the correct syntax.
MESSAGE
Expression may not contain table or column reference.
(DBERR 1171)
CAUSE
An incorrect syntax was specied for the expression.
ACTION
See the \Expressions" chapter of the ALLBASE/SQL Reference
Manual for the correct syntax.
ALLBASE/SQL Error Messages
3-69
1600
1601
1602
1603
1604
1605
3-70
MESSAGE
Unidentified DBECON utility error. (RC !, !, !, !) (DBERR
1600)
CAUSE
An unexpected error was encountered.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Cannot open DBECON file. (! !, RC !, !, !) (DBERR 1601)
CAUSE
A le system error was encountered.
ACTION
Check the spelling of the DBEnvironmentName in the last
command that was issued. Refer to the /usr/include/sys/errno.h
le for an error description.
MESSAGE
Cannot close DBECON file. (! !, RC !, !, !) (DBERR 1602)
CAUSE
A le system error was encountered.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Cannot read DBECON file. (! !, RC !, !, !) (DBERR 1603)
CAUSE
A le system error was encountered.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Cannot update DBECON file. (! !, RC !, !, !) (DBERR 1604)
CAUSE
A le system error was encountered.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Cannot store DBECON file. (! !, RC !, !, !) (DBERR 1605)
CAUSE
A le system error was encountered.
ACTION
Refer to the /usr/include/sys/errno.h lefor an error description.
ALLBASE/SQL Error Messages
1606
1607
1608
1609
1610
1621
MESSAGE
DBCore INTERNAL error. (FNC !, RC !, ! !, !, !) (DBERR
1606)
CAUSE
An unexpected error was encountered.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Cannot open database or log file. (! !, RC !, !, !) (DBERR
1607)
CAUSE
A le system error was encountered.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Cannot update database or log file. (! !, RC !, !, !)
(DBERR 1608)
CAUSE
A le system error was encountered.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Cannot close database or log file. (! !, RC !, !, !) (DBERR
1609)
CAUSE
A le system error was encountered.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Cannot purge database or log file. (! !, RC !, !, !) (DBERR
1610)
CAUSE
A le system error was encountered.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Invalid DBECON file. Record length too small. (RC !, !, !,
!) (DBERR 1621)
CAUSE
The le specied is not a DBECON le.
ACTION
Check your spelling. Issue the command again, specifying a valid
DBECON le.
ALLBASE/SQL Error Messages
3-71
1622
1623
1624
1625
3-72
MESSAGE
Invalid DBECON file. Bad Brand. (RC !, !, !, !) (DBERR
1622)
CAUSE
The le specied is not a DBECON le.
ACTION
Check your spelling. Issue the command again, specifying a valid
DBECON le.
MESSAGE
DBEnvironment already exists. (RC !, !, !, !) (DBERR 1623)
CAUSE
You attempted to RESTORE a backup copy of a DBEnvironment, but it already exists on your system.
ACTION
You must purge all les associated with the DBEnvironment
before RESTORE will successfully execute.
MESSAGE
DBE on StoreFile doesn't match RESTORE parameter.
(RC !, !, !, !) (DBERR 1624)
CAUSE
You attempted to RESTORE a backup copy of a DBEnvironment, but the name of the DBEnvironment that is contained on
the backup is not the same as the name of the DBEnvironment
that you were attempting to restore.
ACTION
Issue the command again, specifying the correct StoreFile and
DBEnvironment names.
MESSAGE
Null or invalid StoreFile name. (RC !, !, !, !)
(DBERR 1625)
CAUSE
You attempted to either RESTORE a backup copy of a
DBEnvironment or RESTORELOG a backup copy of a log le,
but you provided an invalid name for the le or tape device
containing the backup.
ACTION
Check your spelling. Issue the command again, specifying a valid
StoreFileName.
ALLBASE/SQL Error Messages
1626
1627
1628
1629
MESSAGE
Security Violation. (RC !, !, !, !) (DBERR 1626)
CAUSE
You do not have the required capability for the operation that
was attempted.
ACTION
Refer to the ALLBASE/SQL Reference Manual or the
ALLBASE/SQL Database Administration Guide for information
about the capability that is required for the operation.
MESSAGE
Cannot update DBEnvironment Creator Id. (RC !, !, !, !)
(DBERR 1627)
CAUSE
You attempted a command that may only be executed by the
superuser.
ACTION
Issue the command again as the superuser.
MESSAGE
DBEnvironment Creator Id is not in /etc/passwd.
(RC !, !, !, !) (DBERR 1628)
CAUSE
You probably moved a DBEnvironment from one system to
another without using the SQLUtil STORE and RESTORE
commands, or you used the RESTORE command but you were
not superuser.
ACTION
You may do either of the following:
1. RESTORE the DBEnvironment as the superuser, specifying a
valid NEW DBECreator Name at the appropriate prompt, or
2. Use the SQLMigrate SHOW \DBEnvironmentName"
VERSION command to determine the Creator Id. Contact
your system administrator to add an entry to the /etc/passwd
le using this uid.
MESSAGE
Internal Error. Buffer too small. (RC !, !, !, !)
(DBERR 1629)
CAUSE
An unexpected error was encountered.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
3-73
1640
1680
1682
1683
1684
1685
3-74
MESSAGE
SystemFileName could not be CREATED (! !). (DBERR 1640)
CAUSE
A le system error was encountered.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
NLS routine failed. (!, !, !, !) (DBERR 1680)
CAUSE
An unexpected error occurred while using an internal native
language procedure.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Cannot open message catalog (!). (DBERR 1682)
CAUSE
An unexpected error was encountered when trying to open the
ALLBASE/SQL message catalog. It probably does not exist.
ACTION
Contact your system administrator.
MESSAGE
Message catalog read error. (set !, msg !, !) (DBERR 1683)
CAUSE
An unexpected error was encountered when trying to nd a
message in the ALLBASE/SQL message catalog.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Cannot close message catalog (!). (DBERR 1684)
CAUSE
An unexpected error was encountered when trying to close the
ALLBASE/SQL message catalog.
ACTION
Contact your system administrator.
MESSAGE
Failed loading keyword (!). (DBERR 1685)
CAUSE
An unexpected error occurred while trying to obtain information
from the ALLBASE/SQL message catalog. The version of the
message catalog is probably incompatible with the version of the
program.
ACTION
Contact your system administrator.
ALLBASE/SQL Error Messages
1686
1687
1813
1814
1815
MESSAGE
Failed to determine minimum uniqueness of keywords (!).
(DBERR 1686)
CAUSE
An unexpected error occurred while trying to obtain information
from the ALLBASE/SQL message catalog. The version of the
message catalog is probably incompatible with the version of the
program.
ACTION
Contact your system administrator.
MESSAGE
Failed to obtain string constant (set !, msg !, !). (DBERR
1687)
CAUSE
An unexpected error occurred while trying to obtain information
from the ALLBASE/SQL message catalog. The version of the
message catalog is probably incompatible with the version of the
program.
ACTION
Contact your system administrator.
MESSAGE
The statement is not valid in SETOPT. (DBERR 1813)
CAUSE
The statement is not supported with SETOPT.
ACTION
Do not use the statement in SETOPT.
MESSAGE
Conflict ! statements or conflict conditions on !
statement occur in SETOPT statement. (DBERR 1814)
CAUSE
! statements or conditions on ! statement in SETOPT are
conicting.
ACTION
Remove incorrect ! statement or incorrect conditions from
ACCESS statement and reexecute SETOPT and the query.
MESSAGE
WITH clause of GENPLAN is not allowed in the GENPLAN on a
section. (DBERR 1815)
CAUSE
You tried to specify a GENPLAN on a section with a WITH
clause.
ACTION
Remove WITH clause from GENPLAN statement.
ALLBASE/SQL Error Messages
3-75
2032
2033
2034
2035
2100
2101
3-76
MESSAGE
Cannot use WITH AUTOCOMMIT if rule enabled. (DBERR 2032)
CAUSE
WITH AUTOCOMMIT was used incorrectly.
ACTION
See the DELETE or VALIDATE statement in the \SQL
Statements" chapter of the ALLBASE/SQL Reference Manual .
MESSAGE
Cannot use WITH AUTOCOMMIT inside atomic block.(DBERR
2033)
CAUSE
WITH AUTOCOMMIT was used incorrectly.
ACTION
See the DELETE or VALIDATE statement in the \SQL
Statements" chapter of the ALLBASE/SQL Reference Manual .
MESSAGE
Cannot use WITH AUTOCOMMIT inside global transaction.
(DBERR 2034)
CAUSE
WITH AUTOCOMMIT was used incorrectly.
ACTION
See the DELETE or VALIDATE statement in the \SQL
Statements" chapter of the ALLBASE/SQL Reference Manual .
MESSAGE
Cannot use WITH AUTOCOMMIT if constraints are deferred.
(DBERR 2035)
CAUSE
WITH AUTOCOMMIT was used incorrectly.
ACTION
See the DELETE or VALIDATE statement in the \SQL
Statements" chapter of the ALLBASE/SQL Reference Manual .
MESSAGE
ALLBASE/SQL not running. (DBERR 2100)
CAUSE
An SQL statement was issued before a DBE session was started.
ACTION
Start a DBE session with the CONNECT or START DBE
statement, then issue the SQL statement again.
MESSAGE
ALLBASE/SQL already started. (DBERR 2101)
CAUSE
A START DBE or CONNECT statement was entered after a
DBE session was already started.
ACTION
No action is necessary.
ALLBASE/SQL Error Messages
2102
2103
2105
2106
2107
MESSAGE
Command requires a transaction to be in progress. (DBERR
2102)
CAUSE
A COMMIT WORK or ROLLBACK WORK statement was
issued before a transaction was started.
ACTION
No action is necessary. To begin a transaction, issue a BEGIN
WORK statement.
MESSAGE
Transaction already started. (DBERR 2103)
CAUSE
You attempted to start a second transaction before the current
transaction was committed.
ACTION
Issue a COMMIT WORK or ROLLBACK WORK statement to
terminate the previous transaction, then issue a BEGIN WORK
statement to start the next transaction.
MESSAGE
Specified DBEnvironment already exists. (DBERR 2105)
CAUSE
You tried to create a DBEnvironment that already exists.
ACTION
Issue the START DBE NEW statement again, specifying a
unique name.
MESSAGE
Backward migration is needed - use SQLMigrate. (DBERR
2106)
CAUSE
The release of the ALLBASE/SQL software does not match the
version of the DBEnvironment.
ACTION
Use the migration tool, SQLMigrate, to migrate the
DBEnvironment backward to the proper version or use a newer
release of the ALLBASE/SQL software.
MESSAGE
Forward migration is needed - use SQLMigrate. (DBERR
2107)
CAUSE
The release of the ALLBASE/SQL software does not match the
version of the DBEnvironment.
ACTION
Use the migration tool, SQLMigrate, to migrate the
DBEnvironment forward to the proper version or use an older
release of the ALLBASE/SQL software.
ALLBASE/SQL Error Messages
3-77
2108
2200
2201
2202
2203
3-78
MESSAGE
DBEnvironment corrupted during previous migration.
(DBERR 2108)
CAUSE
At some prior time, a migration attempt failed which corrupted
the DBEnvironment in the process.
ACTION
Restore the DBEnvironment from the backup.
MESSAGE
DBEFileSet ! not found. (DBERR 2200)
CAUSE
You tried to access a DBEFileSet that does not exist.
ACTION
Check your spelling. If you still receive this error ask your
Database Administrator to check the SYSTEM.DBEFILESET
system catalog to make sure that the DBEFileSet exists.
MESSAGE
DBEFileSet ! already exists. (DBERR 2201)
CAUSE
You tried to CREATE a DBEFileSet that already exists.
ACTION
Issue the CREATE DBEFILESET statement again, specifying a
unique name.
MESSAGE
DBEFile ! not found. (DBERR 2202)
CAUSE
You tried to access a DBEFile that does not exist in this
DBEnvironment by using the ADD DBEFILE, DROP DBEFILE,
or REMOVE DBEFILE statement.
ACTION
Check your spelling. Check the SYSTEM.DBEFILE view to
make sure that the specied DBEFile does exist.
MESSAGE
DBEFile ! already exists. (DBERR 2203)
CAUSE
You tried to create a DBEFile that was already created in this
DBEnvironment.
ACTION
Issue the command again, specifying a unique name.
ALLBASE/SQL Error Messages
2204
2205
2206
2207
2208
MESSAGE
DBEFile ! not associated with DBEFileSet !. (DBERR 2204)
CAUSE
The DBEFile named in the command is not associated with the
DBEFileSet named in the same command.
ACTION
Ask your database administrator to check the
SYSTEM.DBEFILE view to verify which DBEFileSet the
DBEFile is associated with.
MESSAGE
DBEFile ! already associated with DBEFileSet !. (DBERR
2205)
CAUSE
The ADD DBEFILE statement contained a DBEFile that is
already a member of the DBEFileSet specied.
ACTION
No action is necessary.
MESSAGE
Table/View !.! not found. (DBERR 2206)
CAUSE
The table or view specied in the query or command does not
exist in the DBEnvironment.
ACTION
Check your spelling, owner name, and system catalog. If you still
receive this error ask your database administrator to check the
SYSTEM.TABLE or SYSTEM.VIEW view to make sure that the
specied table does exist.
MESSAGE
Table/View !.! already exists. (DBERR 2207)
CAUSE
The table or view you specied in the CREATE TABLE or
CREATE VIEW statement already exists in the DBEnvironment.
ACTION
Create the table or view with a dierent name (same owner) or
dierent owner name (same table or view name).
MESSAGE
Column ! not found in table/view !.!. (DBERR 2208)
CAUSE
The column name you specied was not found in the specied
table or view.
ACTION
Check your spelling. If you still receive this error, use the ISQL
INFO command or ask your database administrator to check
SYSTEM.COLUMN to make sure that the specied column does
exist in the table.
ALLBASE/SQL Error Messages
3-79
2209
2210
2211
2212
MESSAGE
Duplicate column !. (DBERR 2209)
CAUSE
You specied a column name twice in the CREATE TABLE or
CREATE INDEX statement or you specied a column already
existing in the table in the ALTER TABLE statement.
ACTION
Issue the command again, specifying unique column names.
MESSAGE
Ambiguous column !. (DBERR 2210)
CAUSE
The column you specied in the query exists in more than one
table specied in the query.
ACTION
Execute your query again, specifying the table name as well as
the column name.
MESSAGE
Column ! not found. (DBERR 2211)
CAUSE
The column you specied in the query does not exist in any of
the specied tables.
ACTION
Check your spelling. If you still receive this error ask your
database administrator to check the SYSTEM.COLUMN view to
make sure that the specied column does exist.
MESSAGE
Index ! not found in table !.!. (DBERR 2212)
CAUSE
A non-existent index was specied in the DROP INDEX
statement
or
the index specied in the DROP command is not associated with
the specied table.
ACTION
3-80
Check your spelling. If you still receive this error, ask your
database administrator to check the SYSTEM.INDEX view to
make sure that the specied index does exist in the specied
table.
ALLBASE/SQL Error Messages
2213
2214
2215
2216
MESSAGE
Duplicate index !. (DBERR 2213)
CAUSE
The index you named in the CREATE INDEX statement already
exists for the specied table.
ACTION
Create the index with another name or DROP the old index
before you create the new one.
MESSAGE
Unrecognizable command or module !.!(!) not found. (DBERR
2214)
CAUSE
One of two error conditions has occurred. Either the command
you entered is not recognizable or the module specied cannot be
found.
ACTION
Check your spelling. Ask your database administrator to check
the SYSTEM.SECTION view to make sure that the module
exists in the DBEnvironment to which the application is
connected.
MESSAGE
Module !.!(!) already exists. (DBERR 2215)
CAUSE
You tried to PREPARE a module or declare a cursor which
already exists.
ACTION
Issue the command again, specifying a unique module name. Use
another integer or give the command a dierent name. Ask your
Database Administrator to check the SYSTEM.SECTION view
for names of existing modules.
MESSAGE
Module !.! not found. (DBERR 2216)
CAUSE
You tried to execute the OPEN CURSOR statement or the
DROP MODULE statement on a non-existent section
or
the module in the DROP MODULE statement does not exist.
ACTION
Check your spelling. If you still receive this error, ask your
Database Administrator to check the SYSTEM.SECTION
view to make sure that the module exists in the specied
DBEnvironment.
ALLBASE/SQL Error Messages
3-81
2218
2219
2220
2221
2222
3-82
MESSAGE
TempSpace name ! already defined. (DBERR 2218)
CAUSE
You tried to create a TEMPSPACE that was already created in
this DBEnvironment.
ACTION
Issue the CREATE TEMPSPACE statement again, specifying a
unique logical tempspace name.
MESSAGE
TempSpace name ! not found. (DBERR 2219)
CAUSE
You tried to access a TEMPSPACE that does not exist in this
DBEnvironment by using the DROP TEMPSPACE statement.
ACTION
Check your spelling. Check the SYSTEM.TEMPSPACE table to
make sure that the specied TEMPSPACE does exist.
MESSAGE
Duplicate column found in sort column list. (DBERR 2220)
CAUSE
The ORDER BY clause in the SELECT statement contains more
than one reference to the same column. The command is not
executed.
ACTION
Remove the duplicate column and execute the command again.
MESSAGE
Duplicate column found in insert column list. (DBERR
2221)
CAUSE
The column list in the INSERT statement contains more than one
reference to the same column.
ACTION
Remove the duplicate column and execute the command again.
MESSAGE
Table name required to drop index !.!. (DBERR 2222)
CAUSE
You attempted to drop an index with an ambiguous name. The
same index name was used in creating indexes on two tables with
the same owner.
ACTION
Use the syntax DROP INDEX IndexName FROM
[Owner .]TableName to specify which table's index should be
dropped.
ALLBASE/SQL Error Messages
2223
2224
2225
2227
MESSAGE
Index !.! not found. (DBERR 2223)
CAUSE
A non-existent index was specied in the DROP INDEX
statement without an associated table.
ACTION
Check your spelling. If you still receive this error, ask your
database administrator to check the SYSTEM.INDEX view to
make sure that the specied index does exist.
MESSAGE
! !.! must have same owner as table !.!. (DBERR 2224)
CAUSE
Dierent owners were given for the named INDEX, CONSTRAINT, or RULE and the named table, or the default table
owner was dierent from the specied INDEX, CONSTRAINT,
or RULE owner in the CREATE INDEX, DROP INDEX, DROP
CONSTRAINT, CREATE RULE, or DROP RULE statement.
ACTION
If both owners were specied, check your spelling. If the
table owner was not specied, either specify one or drop the
specication of the INDEX, CONSTRAINT, or RULE owner. If
you still receive this error, ask your database administrator to
check the SYSTEM.INDEX view, SYSTEM.CONSTRAINT view,
or SYSTEM.RULE view to determine the correct owner.
MESSAGE
Out of disc space for all TempSpaces. (DBERR 2225)
CAUSE
There is not enough space in the device to support your sorting
operation.
ACTION
Use a dierent device or contact your database administrator to
add more space to the current device.
MESSAGE
Duplicate SCHEMA !. (DBERR 2227 )
CAUSE
There are existing objects already owned by the AuthorizationName specied.
ACTION
Make sure the AuthorizationName specied is neither an
owner of existing objects in the DBEnvironment nor a grantor
of authority on existing objects. To check ownership, query
SYSTEM.TABLE and SYSTEM.GROUP. To check authorities,
query SYSTEM.TABAUTH and SYSTEM.COLAUTH.
ALLBASE/SQL Error Messages
3-83
2228
2229
2230
2231
3-84
MESSAGE
Duplicate column ! found in joined table. (DBERR 2228)
CAUSE
With an explicit three or more table join, a result table (which
participates in a subsequent join clause) has been produced
and it has more than one column with the same column name.
This same column name is either specied as a join column in
the \ON SearchCondition " clause of the explicit join, or if a
NATURAL . . . JOIN has been specied, the column has been
chosen by ALLBASE/SQL as a join column.
ACTION
When writing a three or more table join with explicit join
syntax make sure that for any single result table participating
in a join, there are no duplicate column names which will be
named as a join column. To ensure this, make each join clause
a NATURAL . . . JOIN or a JOIN . . . USING (ColumnList ),
except for the nal join, which may contain these types or a
JOIN . . . ON SearchCondition3 clause. Otherwise, ensure that
each join clause is a JOIN . . . ON SearchCondition3 clause.
MESSAGE
Duplicate column ! found in USING clause of JOIN. (DBERR
2229)
CAUSE
There is more than one column with the same name in the
USING (ColumnList ) clause of an explicit join.
ACTION
Remove the duplicate column name from the USING
(ColumnList ) clause of the explicit join.
MESSAGE
Maximum number of parameters (!) exceeded in procedure
!.!. (DBERR 2230)
CAUSE
The number of parameters you specied in the CREATE
PROCEDURE statement was greater than the maximum number
allowed.
ACTION
Issue the CREATE PROCEDURE statement again, limiting the
number of parameters to 255 or fewer.
MESSAGE
Procedure parameter data type may not be a LONG data type.
(DBERR 2231)
CAUSE
You specied a LONG data type as the parameter data type in a
CREATE PROCEDURE statement.
ACTION
Issue the statement again, specifying only a valid (non-LONG)
data type for each parameter.
ALLBASE/SQL Error Messages
2232
2233
2234
2235
2236
MESSAGE
Duplicate parameter !. (DBERR 2232)
CAUSE
You specied a parameter name twice in the CREATE
PROCEDURE statement.
ACTION
Issue the statement again, specifying unique parameter names.
MESSAGE
OUTPUT specified for a parameter not declared as OUTPUT.
(DBERR 2233)
CAUSE
In the EXECUTE PROCEDURE statement, you specied
OUTPUT for a non- OUTPUT parameter.
ACTION
Re-issue the EXECUTE PROCEDURE statement, specifying
OUTPUT only for parameters that were declared as OUTPUT
parameters in the CREATE PROCEDURE statement. If
necessary, recreate the procedure specifying OUTPUT for this
parameter.
MESSAGE
No value was provided for non-nullable parameter ! in
procedure !.!. (DBERR 2234)
CAUSE
A parameter declared as NOT NULL in the CREATE
PROCEDURE statement was not provided with a value in the
EXECUTE PROCEDURE statement.
ACTION
Re-issue the EXECUTE PROCEDURE statement, providing a
value for each parameter declared as NOT NULL.
MESSAGE
Error occurred executing procedure !.! statement !.
(DBERR 2235)
CAUSE
An error occurred during procedure execution.
ACTION
Refer to the accompanying error message. Use the statement
number to determine which procedure statement caused the error.
MESSAGE
Doubly defined LABEL !. (DBERR 2236)
CAUSE
You used the same label more than once in a CREATE
PROCEDURE statement.
ACTION
Remove the duplicate label denition, and reissue the CREATE
PROCEDURE statement.
ALLBASE/SQL Error Messages
3-85
2237
2238
2239
2240
3-86
MESSAGE
Undefined LABEL !. (DBERR 2237)
CAUSE
You refer to an undened label in a GOTO statement in the
CREATE PROCEDURE statement.
ACTION
Dene the label within the CREATE PROCEDURE statement.
MESSAGE
Error occurred during evaluation of the condition in an
IF or WHILE statement or the expression in a parameter or
variable assignment. Procedure execution terminated.
(DBERR 2238)
CAUSE
An error occurred in evaluating the condition or expression.
ACTION
Refer to the accompanying error message for additional
information.
MESSAGE
Procedure !.! not found. (DBERR 2239)
CAUSE
The procedure you specied in the statement does not exist in
the DBEnvironment.
ACTION
Check your spelling of the procedure name and the procedure's
owner name against the content of the CATALOG.PROCEDURE
view. If you still receive this error, ask your database
administrator to check the SYSTEM.PROCEDURE view to make
sure the specied procedure does exist.
MESSAGE
Procedure !.! already exists. (DBERR 2240)
CAUSE
The procedure you specied in the CREATE PROCEDURE
statement already exists in the DBEnvironment.
ACTION
Create the procedure with a dierent name and/or owner name.
ALLBASE/SQL Error Messages
2241
2242
2243
2244
MESSAGE
Too many parameter values provided for procedure !.!.
(DBERR 2241)
CAUSE
In the EXECUTE PROCEDURE statement, you provided
a greater number of parameter values than the number of
parameters in the procedure.
ACTION
Check the procedure specication or the parameter descriptions
in SYSTEM.PARAMETER. Reissue the EXECUTE
PROCEDURE statement, providing no more parameter values
than the number in the procedure.
MESSAGE
Error(s) occurred processing statement ! during procedure
creation/validation. (DBERR 2242)
CAUSE
One or more errors occurred while processing an SQL statement
in a procedure. The statement was not stored as an invalid
section, since it can never be validated. The procedure was not
created.
ACTION
Use the statement number in the message to determine
which procedure statement generated the error. Refer to the
accompanying messages for more information.
MESSAGE
Execution of procedure of !.! was invalidated. (DBERR
2243)
CAUSE
The procedure executed a statement that invalidated any further
execution of the procedure, such as DROP PROCEDURE or
TRANSFER OWNERSHIP of the procedure.
ACTION
Modify the procedure denition if you did not intend to
invalidate the procedure during its execution. Otherwise, no
action is required.
MESSAGE
Invalid parameter name ! provided for procedure !.!.
(DBERR 2244)
CAUSE
The name of a parameter in the EXECUTE PROCEDURE
statement is not dened in the parameter list of the CREATE
PROCEDURE statement.
ACTION
Check the parameter lists of both the EXECUTE PROCEDURE
statement and the CREATE PROCEDURE statement and
ensure that the two lists match. Then reissue the EXECUTE
PROCEDURE statement.
ALLBASE/SQL Error Messages
3-87
2245
2246
2247
2248
3-88
MESSAGE
OUTPUT ONLY specified for a parameter not declared as
OUTPUT ONLY. (DBERR 2245)
CAUSE
You specied OUTPUT ONLY for a parameter in an EXECUTE
PROCEDURE statement, but the parameter was not declared
OUTPUT ONLY in the CREATE PROCEDURE statement.
ACTION
Re-issue the EXECUTE PROCEDURE statement, specifying
OUTPUT instead of OUTPUT ONLY. Be sure to initialize the
parameter value.
MESSAGE
Number of items in select list does not match number of
result columns for procedure. (DBERR 2246)
CAUSE
The select list in a procedure SELECT statement with no INTO
clause is incompatible with the format specied in the WITH
RESULT clause of the CREATE PROCEDURE statement.
ACTION
Re-write the CREATE PROCEDURE statement, either omitting
the WITH RESULT clause, or ensuring that all multiple row
result sets returned from the procedure are compatible with the
format specied.
MESSAGE
The KEEP option is not allowed for a procedure cursor.
(DBERR 2247)
CAUSE
The KEEP option was included on an OPEN cursor command,
but the cursor was dened on an EXECUTE PROCEDURE
statement.
ACTION
Re-issue the OPEN command, omitting the KEEP option.
MESSAGE
The ADVANCE statement is allowed only for a procedure
cursor. (DBERR 2248)
CAUSE
The ADVANCE statement was issued against a cursor, but
the cursor was not dened on an EXECUTE PROCEDURE
statement.
ACTION
There is no need for the ADVANCE statement for a
non-procedure cursor. Use the OPEN, FETCH, and CLOSE
statements.
ALLBASE/SQL Error Messages
2249
2250
2251
2252
2253
MESSAGE
Duplicate column found in update set columns. (DBERR
2249)
CAUSE
The same column was specied twice in the SET clause of the
UPDATE statement.
ACTION
Remove one of the duplicate column assignments.
MESSAGE
CHECK constraint ! on column ! references other columns.
(DBERR 2250)
CAUSE
The named CHECK constraint you dened on a single column
contains references to other columns.
ACTION
Either remove the references to the other columns, or make the
check constraint a table level check constraint.
MESSAGE
CHECK constraint ! contains host variables. (DBERR 2251)
CAUSE
You dened the named CHECK constraint with host variables in
it.
ACTION
Remove the host variable from your CHECK constraint.
MESSAGE
CHECK constraint ! contains aggregate functions. (DBERR
2252)
CAUSE
You dened the named CHECK constraint with aggregate
functions in it.
ACTION
Remove the aggregate from your CHECK constraint.
MESSAGE
CHECK constraint ! contains subqueries. (DBERR 2253)
CAUSE
You dened the named CHECK constraint with subqueries in it.
ACTION
Remove the subquery from your CHECK constraint.
ALLBASE/SQL Error Messages
3-89
2254
2255
2256
2257
3-90
MESSAGE
Table CHECK constraint violated. (DBERR 2254)
CAUSE
A table CHECK constraint on the target table of the INSERT or
UPDATE was violated during its execution.
ACTION
Identify the constraint violated and determine the proper value
for the INSERT or UPDATE.
MESSAGE
View CHECK OPTION constraint violated. (DBERR 2255)
CAUSE
A check constraint on the view named for the INSERT or
UPDATE was violated during its execution.
ACTION
Identify the view denition violated (under the topmost WITH
CHECK OPTION view) and determine the proper value for the
INSERT or UPDATE.
MESSAGE
CHECK constraint ! invalid. (DBERR 2256)
CAUSE
The named CHECK constraint will not be executable and so is
not valid.
ACTION
Identify the problem with the CHECK constraint by examining
the error or errors prior to this one. Correct the problem of those
errors in order to make the CHECK constraint executable.
MESSAGE
View defined WITH CHECK OPTION contains non-updatable
query. (DBERR 2257)
CAUSE
The view denition cannot be part of a WITH CHECK OPTION
since no INSERT or UPDATE can be applied to the view.
ACTION
Either remove the WITH CHECK OPTION clause or modify
the view denition to make it updatable. Refer to the
ALLBASE/SQL Reference Manual for a denition of updatable
views.
ALLBASE/SQL Error Messages
2258
2259
2260
2261
MESSAGE
!.! (!) is not a procedure cursor. (DBERR 2258)
CAUSE
The USING clause was included in a CLOSE cursor statement,
but the cursor was not dened on an EXECUTE PROCEDURE
statement.
ACTION
Re-issue the CLOSE statement, omitting the USING clause, or
re-issue the CLOSE statement with the USING clause, specifying
the correct cursor name.
MESSAGE
The RESULT option is allowed only for a procedure
returning results. (DBERR 2258)
CAUSE
The RESULT option was specied in a DESCRIBE statement,
but the statement described is not an EXECUTE PROCEDURE
statement.
ACTION
For statements other than EXECUTE PROCEDURE, the
DESCRIBE RESULT statement is not necessary. If the sqlmproc
eld of the SQLDA is 0 after DESCRIBE OUTPUT, there is no
need to DESCRIBE RESULT.
MESSAGE
Unnamed CHECK constraint on column ! references other
columns. (DBERR 2260)
CAUSE
You dened an unnamed CHECK constraint on a single column
contains references to other columns.
ACTION
Identify the unnamed constraint which ts this condition and
either remove the references to the other columns or make the
check constraint a table level check constraint.
MESSAGE
Unnamed CHECK constraint contains host variables. (DBERR
2261)
CAUSE
You dened an unnamed CHECK constraint with host variables
in it.
ACTION
Identify the unnamed constraint which ts this condition and
remove the host variables from that CHECK constraint.
ALLBASE/SQL Error Messages
3-91
2262
2263
2264
2265
3-92
MESSAGE
Unnamed CHECK constraint contains aggregate functions.
(DBERR 2262)
CAUSE
You dened an unnamed CHECK constraint with aggregate
functions in it.
ACTION
Identify the unnamed constraint which ts this condition and
remove the aggregate functions from that CHECK constraint.
MESSAGE
Unnamed CHECK constraint contains subqueries. (DBERR
2263)
CAUSE
You dened an unnamed CHECK constraint with subqueries in
it.
ACTION
Identify the unnamed constraint which ts this condition and
remove the subqueries from it.
MESSAGE
Input value provided for OUTPUT ONLY parameter. (DBERR
2264)
CAUSE
In the EXECUTE PROCEDURE statement, an actual parameter
was provided for an OUTPUT ONLY parameter, but OUTPUT
ONLY was not specied.
ACTION
Re-issue the EXECUTE PROCEDURE statement, either
omitting the actual parameter completely, or passing an
OUTPUT ONLY host variable for the actual parameter.
MESSAGE
DEFAULT value provided for OUTPUT ONLY parameter !.
(DBERR 2265)
CAUSE
In the CREATE PROCEDURE statement, a default value was
provided for an OUTPUT ONLY parameter.
ACTION
Re-issue the CREATE PROCEDURE statement, either omitting
the default value, or specifying OUTPUT rather than OUTPUT
ONLY.
ALLBASE/SQL Error Messages
2266
2267
2268
2269
2270
MESSAGE
Unnamed CHECK constraint invalid. (DBERR 2266)
CAUSE
An unnamed CHECK constraint will not be executable and so is
not valid.
ACTION
Identify the unnamed constraint which ts this condition and
identify the problem with this CHECK constraint by examining
the error or errors prior to this one. Correct the problem of those
errors in order to make the CHECK constraint executable.
MESSAGE
Column ! must allow nulls since table !.! is not empty.
(DBERR 2267)
CAUSE
A NOT NULL specication in an ALTER TABLE statements
requires that the table be empty, or that a non-null DEFAULT
clause be used.
ACTION
Include a non-null DEFAULT clause.
MESSAGE
CONSTRAINT !.! for table ! not found. (DBERR 2268)
CAUSE
ConstraintID specied is not a valid constraintID stored in the
database.
ACTION
Re-issue the DROP CONSTRAINT statement with a valid
ConstraintID.
MESSAGE
PRIMARY KEY can not be dropped since it is referenced by a
FOREIGN KEY. (DBERR 2269)
CAUSE
PRIMARY KEY constraints can only be dropped when they are
not being referenced by any FOREIGN KEY.
ACTION
Verify whether you want to drop the FOREIGN KEY references
before executing this statement again.
MESSAGE
PRIMARY KEY already exists in table !.!. (DBERR 2270)
CAUSE
A PRIMARY KEY is already dened in the table, and only 1
PRIMARY KEY is allowed in a table.
ACTION
You may want to drop the dened PRIMARY KEY if it is not
the intended PRIMARY KEY for this table.
ALLBASE/SQL Error Messages
3-93
2275
2276
2277
2278
3-94
MESSAGE
Referenced table in foreign key cannot be a view (!.!).
(DBERR 2275)
CAUSE
The table named in a REFERENCES clause was a view.
ACTION
Change the table to the base table on which the view is based.
MESSAGE
User/group ! is using ! authority to support a foreign key.
(DBERR 2276)
CAUSE
You attempted to revoke an authority which is currently
depended on by the specied user, class or group (directly or
indirectly) to authorize a foreign key.
ACTION
Re-issue the revoke with CASCADE specied, or have your
DBA or the owner of the foreign key remove the table in which
the foreign key resides, or remove the foreign key (using DROP
TABLE or DROP CONSTRAINT) and then reissue the revoke.
MESSAGE
Table !.! does not have a primary key, or number of columns
in primary key does not match number in foreign key. (DBERR
2277)
CAUSE
The table specied in a REFERENCES clause without a column
list has no PRIMARY KEY to use as an implicit column list, or
the number of columns in the PRIMARY KEY does not match
the number specied in the foreign key list.
ACTION
Specify a column list with the table referenced, or check the
number of columns in the primary key of the table referenced.
MESSAGE
Referenced column list does not match any UNIQUE or
PRIMARY KEY constraint in table !.!. (DBERR 2278)
CAUSE
The column list given for a table in a REFERENCES clause does
not match any candidate key dened on the table.
ACTION
Check the order of the columns, as they must exactly match the
order of the candidate key columns. Specify a referenced column
list in the same order as some candidate key in the referenced
table.
ALLBASE/SQL Error Messages
2279
2280
2281
2282
2283
MESSAGE
User ! does not have ! authority on needed columns of
table/view !.!. (DBERR 2279)
CAUSE
You do not have the authority to access the columns of a table.
ACTION
Check with the database administrator for the needed authority,
sign on as a user with the required authority.
MESSAGE
PRIMARY KEY/UNIQUE constraint with HASH index can not be
dropped. (DBERR 2280)
CAUSE
You attempted to drop a constraint that was used in the HASH
ON CONSTRAINT clause in the CREATE TABLE statement.
These constraints cannot be dropped without dropping the whole
table.
ACTION
Check the constraint type in SYSTEM.CONSTRAINT and
ensure that the type of the constraint is not \H", for hash.
MESSAGE
Maximum number of columns allowed in a UNIQUE/PRIMARY
KEY/FOREIGN KEY is !. (DBERR 2281)
CAUSE
The unique or referential constraint exceeds the maximum
number of columns allowed in a unique or referential constraint.
ACTION
Dene the unique or referential constraint on columns within this
limit.
MESSAGE
UNIQUE/PRIMARY KEY/FOREIGN KEY length exceeds maximum
length (! bytes). (DBERR 2282)
CAUSE
Key length exceeds the maximum.
ACTION
Dene referential constraints which are within the key length
limit specied in the database administrator guide.
MESSAGE
Duplicate column name ! in UNIQUE/PRIMARY KEY/FOREIGN KEY
column list. (DBERR 2283)
CAUSE
You specied a column name more than once in a column list of a
unique or referential constraint.
ACTION
Re-issue the CREATE TABLE statement without duplicate
column names in the UNIQUE/PRIMARY KEY/FOREIGN
KEY column lists.
ALLBASE/SQL Error Messages
3-95
2284
2285
2286
2287
3-96
MESSAGE
Invalid data type ! found in column ! specified in a
UNIQUE/PRIMARY KEY/FOREIGN KEY constraint column list.
(DBERR 2284)
CAUSE
A column found in a unique or foreign key column list is of an
invalid data type.
ACTION
Re-issue the statement using columns of the allowed data types in
your constraints.
MESSAGE
FOREIGN KEY column ! data type ! doesn't match data type !
of referenced column. (DBERR 2285)
CAUSE
A pair of corresponding columns in the referencing column list
and referenced column list of a foreign key constraint have data
types which are incompatible for referential constraints.
ACTION
Check the data types of the corresponding columns in your
foreign key constraint declarations and make sure they are the
same data type.
MESSAGE
UNIQUE/PRIMARY KEY/FOREIGN KEY column ! not defined in
CREATE/ALTER TABLE. (DBERR 2286)
CAUSE
The named column appears in an integrity constraint but was not
dened in the CREATE TABLE.
ACTION
Re-issue the command with referential constraints dened on
columns being dened in the statement.
MESSAGE
Cannot drop a table with a UNIQUE/PRIMARY KEY constraint
supporting another table's FOREIGN KEY constraint.
(DBERR 2287)
CAUSE
You tried to drop a table with a UNIQUE or PRIMARY KEY
constraint. This constraint supports a foreign key in another
table.
ACTION
You cannot drop the table until the foreign key reference is
dropped.
ALLBASE/SQL Error Messages
2288
2289
2290
2291
MESSAGE
Unique constraints with identical unique column lists
specified. (DBERR 2288)
CAUSE
Table contains duplicate unique constraints.
ACTION
Re-issue command without redundant unique constraints.
MESSAGE
User ! is using membership in group ! to support a foreign
key. (DBERR 2289)
CAUSE
You attempted to remove the specied user from a group, and
that user has created a foreign key using authorities granted to
the group.
ACTION
Locate and drop the tables created by the user with foreign keys,
then reissue the REMOVE FROM GROUP.
MESSAGE
Group ! is being used to support a foreign key. (DBERR
2290)
CAUSE
The group or its members own a table containing a foreign key,
and that foreign key was allowed to exist due to authorities
granted to the group. Dropping the group would remove the
authority for the foreign key.
ACTION
Locate and drop the tables with foreign keys created by group
members, then reissue the DROP GROUP.
MESSAGE
2291 Constraint !.! already exists. (DBERR 2291)
CAUSE
A constraint by the specied name already exists, and therefore
the CREATE TABLE/TRANSFER OWNERSHIP statement
cannot be completed.
ACTION
If TRANSFER OWNERSHIP, transfer the table to a dierent
user. If CREATE TABLE, reissue the command with unique
constraint names. Or, drop the table with the conicting
constraint name.
ALLBASE/SQL Error Messages
3-97
2292
2293
2294
3-98
MESSAGE
INSERT/UPDATE/DELETE statement had no effect due to
execution errors. (DBERR 2292)
CAUSE
No rows were added, altered or removed by your statement
because of an error during execution. Examine the accompanying
error messages to determine the cause.
ACTION
Determine the row(s) causing the error and remove them from
the statement's eld of eect before reissuing the command. This
can be done by restricting the WHERE clause of an UPDATE,
DELETE, or format 2 INSERT, or removing the oending rows
from a bulk insert.
MESSAGE
FOREIGN KEY constraint violated. (DBERR 2293)
CAUSE
The statement you issued attempted to modify the data in a
way not allowed by a referential constraint on the target table.
You cannot delete or modify a primary key row if a foreign key
row references it. You cannot insert or modify a foreign key row
if there will be no matching primary key row unless the rows
contain NULL values.
ACTION
Determine the row causing the violation by examining the
constraints of the target table, and reissue the statement with
restrictions so that the oending rows are not within it.
MESSAGE
UNIQUE/PRIMARY KEY column ! must specify NOT NULL. (DBERR
2294)
CAUSE
You must dene all columns in a UNIQUE/PRIMARY KEY in
the CREATE TABLE statement as NOT NULL.
ACTION
Re-issue the CREATE TABLE specifying NOT NULL for all
columns in a UNIQUE/PRIMARY KEY constraint.
ALLBASE/SQL Error Messages
2295
2296
2297
2300
MESSAGE
Index uniqueness or UNIQUE/PRIMARY KEY/FOREIGN KEY
constraint violated. (DBERR 2295)
CAUSE
You tried to insert a duplicate key value into a column used in a
unique index or a unique constraint, or you attempted to insert,
update, or delete a unique constraint or foreign key constraint
in a manner which would leave a foreign key value without a
matching primary key value.
ACTION
A foreign key value may be set to NULL until the correct primary
key value is placed in the unique constraint it references; or
a duplicate unique constraint/unique index violation can be
determined. Once this is done, the command may be reissued
without the oending rows.
MESSAGE
Data type for LIKE predicate column must be CHAR or
VARCHAR. (DBERR 2296)
CAUSE
The data type of the LIKE predicate column is not a CHAR or
VARCHAR.
ACTION
Modify the query to have a CHAR or VARCHAR data type
column on the LIKE predicate.
MESSAGE
FOREIGN KEY column ! data type DECIMAL(!,!) doesn't match
PRIMARY KEY data type DECIMAL(!,!). (DBERR 2297)
CAUSE
You entered a value in the referencing column which has a
dierent precision and scale than the precision and scale of the
PRIMARY KEY referenced column.
ACTION
Check the precision and scale of the PRIMARY KEY and change
the value entered in the referencing column to match it.
MESSAGE
User ! does not have ! authorization. (DBERR 2300)
CAUSE
The DBEUserID under which the command was executed does
not have the authority (DBA, RESOURCE, or CONNECT) to
execute the command.
ACTION
Contact your database administrator to get the required
authority or sign on as a user who does have the required
authority.
ALLBASE/SQL Error Messages
3-99
2301
2302
2303
2304
3-100
MESSAGE
User ! does not have ! authority on !.!. (DBERR 2301)
CAUSE
The DBEUserID does not have the required table or view
authority to execute the command.
ACTION
Contact your database administrator to get the required
authority or sign on as a user who does have the required
authority.
MESSAGE
User ! does not have ! authority on column !.!.!. (DBERR
2302)
CAUSE
You do not have the specied authority needed to access the
column. UPDATE is needed in the UPDATE statement, or
REFERENCES is needed in the CREATE TABLE statement.
ACTION
Contact your database administrator to get the required
authority or sign on as a user who does have the required
authority.
MESSAGE
User ! does not have OWNER or DBA authority. (DBERR 2303)
CAUSE
The command requires either OWNER or DBA authority.
ACTION
Refer to the ALLBASE/SQL Database Administration Guide and
the ALLBASE/SQL Reference Manual for statements requiring
special authority. Contact your database administrator to get the
required authority.
MESSAGE
Cannot revoke DBA authority from session owner !. (DBERR
2304)
CAUSE
You tried to REVOKE DBA authority from yourself.
ACTION
Refer to the ALLBASE/SQL Database Administration Guide for
additional information on when you can revoke DBA authority.
ALLBASE/SQL Error Messages
2305
2306
2307
2308
MESSAGE
Use REVOKE ! to revoke GRANT !. (DBERR 2305)
CAUSE
The DBEUserID was granted the specied authority (UPDATE
or REFERENCES) on all columns using the GRANT statement
without specifying column names. You tried to revoke the
authority on individual columns in the table.
ACTION
Revoke the authority on all columns using the REVOKE
statement without specifying column names. If you want the user
to have the authority on some columns of the table, issue the
GRANT statement specifying the appropriate column names.
MESSAGE
Special GRANT/REVOKE disallowed for reserved user !.
(DBERR 2306)
CAUSE
The DBEUserID specied in the GRANT or REVOKE statement
is a reserved user (PUBLIC, TEMP, SYSTEM, HPRDBSS). The
GRANT or REVOKE statement is ignored.
ACTION
Refer to the ALLBASE/SQL Database Administration Guide
explanation of reserved users and their purposes.
MESSAGE
User ! does not have OWNER authority. (DBERR 2307)
CAUSE
The TRANSFER OWNERSHIP and DROP VIEW statements
are not allowed on system views.
ACTION
No action is necessary. Refer to the ALLBASE/SQL Database
Administration Guide for additional information on system views.
MESSAGE
Reserved user ! cannot be added to a group. (DBERR 2308)
CAUSE
You attempted to add a RESERVED user (PUBLIC, SYSTEM,
TEMP, or HPRDBSS) to a group using the ADD GROUP
statement.
ACTION
No action is necessary. Refer to the ALLBASE/SQL Database
Administration Guide for an explanation of reserved users and
their purposes.
ALLBASE/SQL Error Messages
3-101
2309
2310
2311
2312
2313
3-102
MESSAGE
User ! neither has DBA authority nor is a member of group
!. (DBERR 2309)
CAUSE
The AuthorizationName is dierent than the DBEUserID
executing the CREATE SCHEMA statement. You do not have
DBA authority, nor are you a member of a group whose name
is the AuthorizationName specied in the CREATE SCHEMA
statement.
ACTION
Ensure that you have proper authorization to execute the
CREATE SCHEMA statement.
MESSAGE
User ! does not have DBA authority. (DBERR 2310)
CAUSE
GRANT with BY clause done by someone without DBA
authority.
ACTION
This command requires DBA authority to be performed.
MESSAGE
Group ! not found. (DBERR 2311)
CAUSE
The group name specied in the DROP GROUP, ADD TO
GROUP, or REMOVE FROM GROUP statement, does not exist
in the DBEnvironment.
ACTION
Check your spelling. If you still receive this error, ask your
database administrator to check the SYSTEM.GROUP view to
determine if the group exists in the DBEnvironment.
MESSAGE
User or group ! already exists. (DBERR 2312)
CAUSE
The user or group name specied in the CREATE GROUP
statement already exists in the DBEnvironment.
ACTION
Issue the command again, specifying a unique user or group
name.
MESSAGE
User ! not found in group !. (DBERR 2313)
CAUSE
The DBEUserID specied in the REMOVE FROM GROUP
statement does not exist in the specied group.
ACTION
Check your spelling. If you still receive this error, ask your
database administrator to check the SYSTEM.GROUP view to
make sure that the specied user does exist in the group.
ALLBASE/SQL Error Messages
2314
2315
2316
2317
MESSAGE
User ! already a member of group !. (DBERR 2314)
CAUSE
The DBEUserID in the ADD command is already a member of
the group.
ACTION
No action is necessary.
MESSAGE
User or group ! conflicts with existing !. (DBERR 2315)
CAUSE
The group name specied in the CREATE GROUP statement
is already being used as a DBEUserID or group name in the
manner specied in the second parameter; or a CONNECT was
attempted with a DBEUserID equivalent to an existing group
name.
ACTION
Remove the existing usage before re-issuing the CREATE
GROUP, or issue it with a dierent group name; or drop the
group to permit the connection; or do not attempt to CONNECT
with that DBEUserID.
MESSAGE
User or group ! owns object(s) in the DBEnvironment.
(DBERR 2316)
CAUSE
The DBEUserID or group specied in the DROP command is the
owner name of either tables, views, modules, or groups in the
DBEnvironment.
ACTION
Drop the objects or transfer ownership to another DBEUserID or
group before dropping the user or group.
MESSAGE
User or group ! is (indirect) member of group !. (DBERR
2317)
CAUSE
You tried to add a group (or user) to a group which is already a
member of the group you tried to add.
ACTION
No action is necessary. If you specied more than one user or
group in the ADD TO GROUP statement, the valid names were
processed and the invalid names were ignored.
ALLBASE/SQL Error Messages
3-103
2318
2319
2321
2322
2323
3-104
MESSAGE
Cannot add group ! to itself. (DBERR 2318)
CAUSE
You tried to add a group (or user) to itself.
ACTION
Issue the command again, specifying a set of unique group or user
names which does not include the target group name.
MESSAGE
Cannot remove group ! from itself. (DBERR 2319)
CAUSE
You tried to remove a group from itself.
ACTION
Issue the command again, specifying a set of group names which
does not include the target group name.
MESSAGE
CONNECT disallowed. Group ! already exists. (DBERR 2321)
CAUSE
A group name that is the same as your DBEUserID name exists
in the DBEnvironment.
ACTION
Login using a dierent login id. Ask your database administrator
to change the group name to something dierent from your login
id so that this problem will not occur in the future.
MESSAGE
User ! already has ! authorization on !.! from a different
grantor. (DBERR 2322)
CAUSE
Attempted to GRANT the specied authority to a user who has
the authority from another grantor already, and you would not be
able to revoke that authority.
ACTION
Repeat the GRANT without that user and/or authorization.
MESSAGE
User ! already has ! authorization on !.!.! from a
different grantor. (DBERR 2323)
CAUSE
Attempted to GRANT the specied authority to a user who has
the authority from another grantor already, and you would not be
able to revoke that authority.
ACTION
Repeat the GRANT without that user and/or authorization.
ALLBASE/SQL Error Messages
2324
2325
2326
2327
MESSAGE
Cannot revoke ! authorization from ! on !.! without
CASCADE. (DBERR 2324)
CAUSE
Attempted to REVOKE the specied authority from a user who
has used the grantability of that authority to grant to another
user.
ACTION
Use REVOKE CASCADE if you wish to remove all the grants
that user has cascaded on the authority, or get a DBA to perform
the revoke on that user (this will leave all of that user's grants
intact). The DBA should use the BY option of the REVOKE
statement to avoid an orphaned privilege.
MESSAGE
Cannot revoke ! authorization from user ! on !.!.! without
CASCADE. (DBERR 2325)
CAUSE
Attempted to REVOKE the specied authority from a user who
has used the grantability of that authority to grant to another
user.
ACTION
Use REVOKE CASCADE if you wish to remove all the grants
that user has cascaded on the authority, or get a DBA to perform
the revoke on that user (this will leave all of that user's grants
intact).
MESSAGE
GRANT of ! authority to ! on !.! causes a cycle. (DBERR
2326)
CAUSE
Attempted to GRANT the specied authority which would cause
a cycle of grants in the authority list.
ACTION
Examine the chain of grants to determine if the cycle can be
broken, or have someone else perform the grant (if their doing so
would not cause a cycle).
MESSAGE
GRANT of ! authority to ! on !.!.! causes a cycle. (DBERR
2327)
CAUSE
Attempted to GRANT the specied authority which would cause
a cycle of grants in the authority list.
ACTION
Examine the chain of grants to determine if the cycle can be
broken, or have someone else perform the grant (if their doing so
would not cause a cycle).
ALLBASE/SQL Error Messages
3-105
2328
2329
2330
2331
3-106
MESSAGE
User ! does not have direct OWNER, DBA, or GRANTABLE !
authority on !.!. (DBERR 2328)
CAUSE
Attempted to GRANT the specied authority WITH GRANT
OPTION, but did not have the direct authority needed to do so.
ACTION
To grant WITH GRANT OPTION, the user must be authorized
to grant directly, not through group membership. Have the
system administrator or table owner grant you the authority with
the grant option directly, or perform the grant you wish done.
MESSAGE
User ! does not have direct OWNER, DBA, or GRANTABLE !
authority on !.!.!. (DBERR 2329)
CAUSE
Attempted to GRANT the specied authority WITH GRANT
OPTION, but did not have the direct authority needed to do so.
ACTION
To grant WITH GRANT OPTION, the user must be authorized
to grant directly, not through group membership. Have the
system administrator or table owner grant you the authority with
the grant option directly, or perform the grant you wish done.
MESSAGE
Group ! not allowed to grant privileges. (DBERR 2330)
CAUSE
Between the time the GRANT was compiled and executed, the
user performing the GRANT became a group. GRANTs cannot
be performed by groups, due to the need to store the user name
of the grantor.
ACTION
Drop the group or re-perform the GRANT with a valid user
name.
MESSAGE
Group ! cannot be granted privileges WITH GRANT OPTION.
(DBERR 2331)
CAUSE
You attempted to grant WITH GRANT OPTION to a group.
ACTION
Repeat the grant without the specied group, or without WITH
GRANT OPTION.
ALLBASE/SQL Error Messages
2332
2333
2334
2335
MESSAGE
User not authorized to revoke ! on !.! from user/group !.
(DBERR 2332)
CAUSE
You are not the OWNER, DBA, or grantor of the specied
privilege on the specied table to the specied user/group.
ACTION
Have the system administrator determine the grantor of the
privilege and have that person perform the revoke, or have the
table owner or a DBA perform the revoke.
MESSAGE
User not authorized to revoke ! on !.!.! from user !.
(DBERR 2333)
CAUSE
You are not the OWNER, DBA, or grantor of the specied
privilege on the specied column to the specied user/group.
ACTION
Have the system administrator determine the grantor of the
privilege and have that person perform the revoke, or have the
table owner or a DBA perform the revoke.
MESSAGE
GRANT/REVOKE of ALTER/INDEX/REFERENCES authority not
allowed on a view (!.!). (DBERR 2334)
CAUSE
You attempted to GRANT or REVOKE one of the privileges
ALTER, INDEX, or REFERENCES on the specied view.
ACTION
Repeat the command without any of the privileges listed above.
MESSAGE
User ! already has ! authorization on !.! with a different
grantability. (DBERR 2335)
CAUSE
You attempted to re-grant an authority with a dierent
grantability (WITH GRANT OPTION was specied on only one
of the grants).
ACTION
Re-issue the grant without the specied authorization, or revoke
the specied authorization and then reissue the grant.
ALLBASE/SQL Error Messages
3-107
2336
2337
2338
2339
3-108
MESSAGE
User ! already has ! authorization on !.!.! with a
different grantability. (DBERR 2336)
CAUSE
You attempted to re-grant an authority with a dierent
grantability (WITH GRANT OPTION was specied on only one
of the grants).
ACTION
Re-issue the grant without the specied authorization, or revoke
the specied authorization and then reissue the grant.
MESSAGE
User ! already has ! authorization on columns of !.! with a
different grantability. (DBERR 2337)
CAUSE
You attempted to grant a table level authority with a dierent
grantability from an existing column level authority which this
would override (WITH GRANT OPTION was specied on only
one of the grants).
ACTION
Re-issue the grant without the specied authorization, or revoke
the specied authorization and then reissue the grant.
MESSAGE
User ! does not have OWNER, DBA, or direct GRANTABLE !
authority on !.!. (DBERR 2338)
CAUSE
You attempted to perform a GRANT WITH GRANT OPTION
or REVOKE of the specied authority without having the
authority to do so.
ACTION
You need to have OWNER, DBA, or have been granted the
authority WITH GRANT OPTION in order to perform a
GRANT WITH GRANT OPTION or REVOKE of the authority.
MESSAGE
User ! does not have OWNER, DBA, or direct GRANTABLE !
authority on !.!.!. (DBERR 2339)
CAUSE
You attempted to perform a GRANT WITH GRANT OPTION
or REVOKE of the specied authority without having the
authority to do so.
ACTION
You need to have OWNER, DBA, or have been granted the
authority WITH GRANT OPTION in order to perform a
GRANT WITH GRANT OPTION or REVOKE of the authority.
ALLBASE/SQL Error Messages
2340
2341
2342
2343
MESSAGE
User ! already has ! authorization on columns of !.! from a
different grantor. (DBERR 2340)
CAUSE
You attempted to GRANT the specied authority on the table
level, and were unable to override column level authorities on that
table from another grantor.
ACTION
Only the DBA, OWNER, or direct grantor can override column
level authorities with table level authority. Have such a user
perform your grant, or reissue your grant without the specied
user and/or authority.
MESSAGE
TRANSFER OWNERSHIP of !.! to ! causes a cycle of !
authority. (DBERR 2341)
CAUSE
Attempted to transfer a table upon which the specied authority
existed, and that transfer would cause a cycle of grants in the
authority list for that authority on that table.
ACTION
Examine the chain of grants to determine if the cycle can be
broken, or transfer the table to a dierent user (if doing so would
not cause a cycle).
MESSAGE
TRANSFER OWNERSHIP of !.! to ! causes a cycle of !
authority on column !. (DBERR 2342)
CAUSE
Attempted to transfer a table upon which the specied authority
existed, and that transfer would cause a cycle of grants in the
authority list for that authority on that table.
ACTION
Examine the chain of grants to determine if the cycle can be
broken, or transfer the table to a dierent user (if doing so would
not cause a cycle).
MESSAGE
User ! does not have authority to install modules for owner
!. (DBERR 2343)
CAUSE
The user specied does not have the required authority.
ACTION
Use the GRANT INSTALL AS OwnerID TO DBEUserID
statement to give the proper authority to the user.
ALLBASE/SQL Error Messages
3-109
2346
2347
2350
2352
2353
3-110
MESSAGE
User ! does not explicit INSTALL AS ! authority. (DBERR
2346)
CAUSE
The user specied does not have INSTALL authority for this
owner.
ACTION
Use the GRANT INSTALL statement to grant INSTALL AS
authority to the user.
MESSAGE
User ! does not have INSTALL ! authority. (DBERR 2347)
CAUSE
The user specied does not have any INSTALL authority.
ACTION
Use the GRANT INSTALL AS OwnerID TO DBEUserID
statement to grant INSTALL authority to the user.
MESSAGE
!
CAUSE
A RAISE ERROR statement was specied without an error
number or with an error number of 2350.
ACTION
See the Section \User Dened Error Messages" in the
\Introduction" for discussion of RAISE ERROR generated errors.
Examine the error text to determine the action to take.
MESSAGE
RULE !.! WHERE condition invalid. (DBERR 2352)
CAUSE
The named RULE denition's WHERE condition will not be
executable and so is not valid.
ACTION
Identify the problem with the RULE denition by examining the
error or errors accompanying this one. Correct the problem of
those errors in order to make the RULE's WHERE condition
executable.
MESSAGE
RULE !.! EXECUTE PROCEDURE invalid. (DBERR 2353)
CAUSE
The named rule denition's EXECUTE PROCEDURE clause will
not be executable and so is not valid.
ACTION
Identify the problem with the rule denition by examining the
error or errors accompanying this one. Correct the problem
identied in those errors in order to make the rule's EXECUTE
PROCEDURE clause executable.
ALLBASE/SQL Error Messages
2354
2355
2356
MESSAGE
Rule !.! not found. (DBERR 2354)
CAUSE
The named rule was not found.
ACTION
Re-issue your DROP RULE statement after verifying that the
proper rule was named.
MESSAGE
Rule ! not found on table !.!. (DBERR 2355)
CAUSE
The named rule was not found on the named table.
ACTION
Re-issue your DROP RULE statement after verifying that the
proper table and rule were named, or issue the statement without
the table name.
MESSAGE
Rule !.! already exists. (DBERR 2356)
CAUSE
The name of the rule given in the CREATE RULE statement is
the name of an existing rule.
or
a TRANSFER OWNERSHIP on a table has resulted in a
duplicate rule name.
2357
2358
ACTION
Issue the CREATE RULE statement with a rule name unique for
the table owner.
MESSAGE
Name ! used for both OLD and NEW in rule !.!. (DBERR 2357)
CAUSE
You specied the same correlation name for both the OLD and
NEW correlation names.
ACTION
Reissue the statement using the default correlation names or with
distinct OLD and NEW correlation names.
MESSAGE
Duplicate column ! in update column list of rule !.!.
(DBERR 2358)
CAUSE
You specied the named column more than once in the UPDATE
statement type column list of your CREATE RULE statement.
ACTION
Re-issue your CREATE RULE statement after checking that
no column name is specied more than once in the UPDATE
statement type column list.
ALLBASE/SQL Error Messages
3-111
2360
2361
2362
2363
2364
3-112
MESSAGE
Error number cannot be NULL for RAISE ERROR. (DBERR 2360)
CAUSE
The error number given to the RAISE ERROR statement had the
NULL value.
ACTION
Check the value given to the RAISE ERROR statement and
ensure that it is not null.
MESSAGE
Error number must be positive for RAISE ERROR. (DBERR
2361)
CAUSE
The error number given to the RAISE ERROR statement was
negative or zero.
ACTION
Check the value given to the RAISE ERROR statement and
ensure that it is greater than zero.
MESSAGE
Error number for RAISE ERROR must have data type INTEGER or
SMALLINT. (DBERR 2362)
CAUSE
The error number for RAISE ERROR was an invalid data type.
ACTION
Ensure that the data type of the error number is INTEGER or
SMALLINT.
MESSAGE
Error text cannot be NULL for RAISE ERROR. (DBERR 2363)
CAUSE
The error text given to the RAISE ERROR statement had the
NULL value.
ACTION
Check the value given to the RAISE ERROR statement and
ensure that it is not null.
MESSAGE
Error text for RAISE ERROR must have data type CHAR or
VARCHAR. (DBERR 2364)
CAUSE
The error text for RAISE ERROR was an invalid data type.
ACTION
Ensure that the data type of the error text is CHAR or
VARCHAR.
ALLBASE/SQL Error Messages
2365
2366
2367
2370
2371
MESSAGE
Deadlock detected causing rollback query. (DBERR 2365)
CAUSE
Deadlock occurred.
ACTION
Determine the cause of the deadlock and take appropriate
actions to correct the problem. See \Resolving Conicts among
Concurrent Transactions" in the chapter \Currency Control
through Locks and Isolation Levels" in the ALLBASE/SQL
Reference Manual .
MESSAGE
Timeout expired (! seconds) causing rollback query.
(DBERR 2366)
CAUSE
The timeout expired.
ACTION
No action is required.
MESSAGE
RENAME COLUMN is not allowed on a check constraint column.
(DBERR 2367)
CAUSE
A RENAME COLUMN statement was issued for a check
constraint column.
ACTION
Check constraints on a renamed column will be disallowed.
Determine if an incorrect column was renamed or take other
appropriate action.
MESSAGE
Rule firing invalidated current section (!.!(!)). (DBERR
2370)
CAUSE
Upon completion of a rule, the current section was found to be
invalidated by actions taken by the rule.
ACTION
Check the rules red by the current statement and determine if
the procedures they invoke invalidate sections; or take no action.
MESSAGE
Rule firing invalidated user's statement. (DBERR 2371)
CAUSE
Upon completion of the rules red by the user's statement, the
statement was found to be invalidated by actions taken by the
rules.
ACTION
Check the rules red by the current statement and determine if
the procedures they invoke invalidate sections; or take no action.
ALLBASE/SQL Error Messages
3-113
2372
2373
2390
2400
2402
3-114
MESSAGE
Maximum rule firing depth (!) exceeded. (DBERR 2372)
CAUSE
Rules chained to a depth greater than the allowed maximum.
ACTION
Determine the cause of exceeding the maximum rule depth; or
take no action.
MESSAGE
Procedure executed by rule executed ! statement. (DBERR
2373)
CAUSE
A procedure invoked by a rule executed a COMMIT,
ROLLBACK, or SAVEPOINT statement.
ACTION
Alter the procedure to not invoke such statements when red by
a rule, or invoke a dierent procedure from the rule.
MESSAGE
User ! does not have the authority to create HPODBSS
table/view. (DBERR 2390)
CAUSE
You attempted to create a table or view with an owner name of
HPODBSS.
ACTION
Replace HPODBSS with a non-reserved name and reissue the
statement.
MESSAGE
Maximum number of columns (!) exceeded on table/view !.!.
(DBERR 2400)
CAUSE
The number of columns you specied in the ALTER TABLE,
CREATE TABLE, or CREATE VIEW statement was greater
than the maximum number of columns allowable.
ACTION
Issue the command again ensuring that the total number of
columns does not exceed 1023.
MESSAGE
Maximum number of tables per module exceeded. (DBERR
2402)
CAUSE
The maximum number of tables for a SELECT statement has
been exceeded.
ACTION
Issue the command again, specifying no more than 31 tables.
ALLBASE/SQL Error Messages
2404
2405
2406
2407
2408
MESSAGE
Maximum number of concurrent transactions exceeded.
(DBERR 2404)
CAUSE
The maximum number of concurrent transactions has been
exceeded.
ACTION
Retry the begin transaction statement again. If it fails, ask your
database administrator for assistance.
MESSAGE
Index ! on table !.! has more than ! columns. (DBERR 2405)
CAUSE
The index you specied contains more than 16 columns.
ACTION
Check the CREATE INDEX statement to make sure that the
number of columns specied is less than or equal to 16.
MESSAGE
SelectList contains more than ! columns. (DBERR 2406)
CAUSE
The number of items in the select list exceeded the maximum
number allowable.
ACTION
Check your SELECT statement to make sure that the number of
items in the select list is equal to or less than 1024.
MESSAGE
Length of column ! in table !.! exceeds ! bytes. (DBERR
2407)
CAUSE
The number of bytes in the specied column exceeded the
maximum number allowable.
ACTION
Issue the CREATE TABLE statement again with the maximum
number of bytes or less.
MESSAGE
Tuple length of table !.! exceeds ! bytes. (DBERR 2408)
CAUSE
You attempted to create a table with a minimum tuple length
greater than the maximum allowed.
ACTION
Reduce the minimum tuple length of the table and reissue the
statement.
ALLBASE/SQL Error Messages
3-115
2409
2410
2411
2412
MESSAGE
Length of index ! on table !.! exceeds ! bytes. (DBERR
2409)
CAUSE
The index you attempted to create exceeds the maximum key
length.
ACTION
Recreate your index using a column or combination of columns
that is less than the maximum number of bytes.
MESSAGE
Tuple exceeded maximum length. (DBERR 2410)
CAUSE
The maximum tuple length of 4,000 bytes has been exceeded.
ACTION
Check your input source (e.g. load le) and the original CREATE
TABLE statement to make sure that each tuple is less than or
equal to 4,000 bytes long.
MESSAGE
Number of sort columns (!) exceeds maximum !. (DBERR 2411)
CAUSE
The ORDER BY, GROUP BY, or DISTINCT clause of the
SELECT statement species a number of columns which exceeded
the maximum allowable.
ACTION
Issue the command again, specifying no more than the maximum
number of sort columns. Refer to the ALLBASE/SQL Reference
Manual for additional information on the SELECT statement.
MESSAGE
Index exceeded maximum length. (DBERR 2412)
CAUSE
The maximum index length of 1024 bytes has been exceeded
or
the ORDER BY or GROUP BY clause uses a column greater
than 1024 bytes.
ACTION
Check your input source (e.g. load le) and the original CREATE
INDEX command to make sure that each index entry is less than
or equal to 1024 bytes long
or
reduce the size of the column used by the ORDER BY or
GROUP BY to less than 1010 bytes.
3-116
ALLBASE/SQL Error Messages
2413
2414
2415
2416
2417
MESSAGE
Number of boolean factors in predicate expression exceeds
maximum (!). (DBERR 2413)
CAUSE
The number of factors in the WHERE clause exceeds the
maximum allowed.
ACTION
Try to reduce the number of factors.
MESSAGE
Length of column ! in table !.! below minimum ! bytes.
(DBERR 2414)
CAUSE
You tried to create a LONG or CHAR column of length 0.
ACTION
Create the column with at least the minimum length.
MESSAGE
Number of operators in internal predicate exceed maximum
(!). (DBERR 2415)
CAUSE
A predicate containing one or more OR operators was too
complicated. When additional factors were added to the
predicate internally for optimization, the total number of
operators exceeded the maximum.
ACTION
Try to rewrite the query, simplifying the predicate as much as
possible, and lowering the precedence of OR operators as much as
possible.
MESSAGE
Hash on table !.! has more than ! columns. (DBERR 2416)
CAUSE
You specied a hash containing more than 16 columns.
ACTION
Issue the CREATE TABLE statement again, specifying no more
than 16 columns for the hash key.
MESSAGE
Length of hash key on table !.! exceeds ! bytes. (DBERR
2417)
CAUSE
You specied a hash key which exceeds the maximum key length.
ACTION
Issue the CREATE TABLE statement again, specifying a hash
key with length no greater than the maximum.
ALLBASE/SQL Error Messages
3-117
2418
2419
2420
MESSAGE
Length of parameter ! in procedure !.! exceeds ! bytes.
(DBERR 2418)
CAUSE
The number of bytes in the specied parameter exceeded the
maximum allowed.
ACTION
Issue the CREATE PROCEDURE statement again, specifying a
parameter length no greater than the maximum specied.
MESSAGE
Length of parameter ! in procedure !.! below minimum !
bytes. (DBERR 2419)
CAUSE
The number of bytes in the specied parameter was less than the
minimum allowed.
ACTION
Issue the CREATE PROCEDURE statement again, specifying a
parameter length no less than the minimum allowed.
MESSAGE
INSERT rejected: Values do not match number of columns.
(DBERR 2420)
CAUSE
The number of values in the INSERT statement exceeded the
number of columns in the INSERT list
or
the number of select list items did not match the number of
columns in the insert list.
2421
3-118
ACTION
Issue the INSERT statement again, specifying a valid number of
columns. Use the INFO command to get a list of columns in the
table.
MESSAGE
Column number exceeds number of SelectList items. (DBERR
2421)
CAUSE
The ORDER BY clause contained a number greater than the
number of select list items.
ACTION
Issue the SELECT statement again, specifying no more columns
in the ORDER BY clause than in the select list. Refer to the
ALLBASE/SQL Reference Manual for additional information on
the SELECT statement.
ALLBASE/SQL Error Messages
2422
MESSAGE
Range violation on value !. Valid range is ! - !. (DBERR
2422)
CAUSE
The source constant number in the query was out of its valid
range
or
a host variable was not dened
or
one of the values in a format node was out of range.
ACTION
Correct your query so that the source constant is within the valid
range
or
make sure that the host variable has been declared
or
in Pascal or C programs, check the value you specied for data
types in the dynamic format nodes of SQLDA.
2423
2424
MESSAGE
Number of Selects in command exceeds maximum !. (DBERR
2423)
CAUSE
The maximum number of Selects in a command has been
exceeded.
ACTION
Issue the command again, specifying the maximum number or
fewer.
MESSAGE
SelectList counts are not equal in UNION command. (DBERR
2424)
CAUSE
The number of columns in the individual select lists in the
UNION command are not the same.
ACTION
Issue the command again with an equal number of columns in the
select lists.
ALLBASE/SQL Error Messages
3-119
2425
2426
2428
2429
3-120
MESSAGE
UNION operation disallowed within a Nested Query. (DBERR
2425)
CAUSE
You tried to include a UNION operation in a nested query.
ACTION
UNION of two nested queries is allowed but UNION cannot be
within a nested query.
MESSAGE
Tuple size exceeds maximum for UNION command ! bytes.
(DBERR 2426)
CAUSE
Your select list size is greater than the maximum currently
allowed for a UNION command.
ACTION
Re-issue the command with a valid tuple size.
MESSAGE
Sort length of UNION exceeds maximum allowed ! bytes.
(DBERR 2428)
CAUSE
The UNION command species a number of columns whose total
sort tuple length exceeds the maximum allowable.
ACTION
Issue the command again, specifying no more than the maximum
sort tuple length. Refer to the ALLBASE/SQL Reference Manual
for additional information on the SELECT statement.
MESSAGE
Sort length of ORDER BY/GROUP BY/DISTINCT/UNION exceeds
maximum allowed ! bytes. (DBERR 2429)
CAUSE
The ORDER BY, GROUP BY, DISTINCT, or UNION clause of
the SELECT statement species a number of columns whose total
sort tuple length exceeds the maximum allowable.
ACTION
Issue the command again, specifying no more than the maximum
length of the sort tuple. Refer to the ALLBASE/SQL Reference
Manual for additional information on the SELECT statement.
The maximum sort tuple size can be calculated from the formula
presented in Appendix A of the ALLBASE/SQL Database
Administration Guide .
ALLBASE/SQL Error Messages
2430
2431
2432
2433
2434
MESSAGE
Invalid decimal precision ! - Allowed range is ! - !.
(DBERR 2430)
CAUSE
The decimal precision you specied was not within the valid
range.
ACTION
Refer to the ALLBASE/SQL Reference Manual for valid decimal
precision.
MESSAGE
Invalid decimal column - Scale ! exceeds precision !.
(DBERR 2431)
CAUSE
The decimal scale was greater than the precision value.
ACTION
Refer to the ALLBASE/SQL Reference Manual for valid decimal
numbers.
MESSAGE
Invalid float precision !- Allowed range is ! - !. (DBERR
2432)
CAUSE
The oat precision you specied was not within the valid range.
ACTION
Refer to the ALLBASE/SQL Reference Manual for valid oat
precision.
MESSAGE
Sort length of sort merge join exceeds maximum allowed !
bytes. (DBERR 2433)
CAUSE
The sort merge join query species a number of columns whose
total sort tuple length exceeds the maximum allowable.
ACTION
Issue the command again, specifying no more than the maximum
length of the sort tuple. Refer to the ALLBASE/SQL Reference
Manual for additional information on the SELECT statement.
MESSAGE
Invalid section number. Valid range is ! - !. (DBERR
2434)
CAUSE
Your command included a value that was invalid. The rst
parameter in the error message indicates the value that was
invalid. The second and third parameters give you the valid
range.
ACTION
Re-issue your command, specifying a value within the valid range.
ALLBASE/SQL Error Messages
3-121
2435
2436
2437
2438
2439
3-122
MESSAGE
Invalid transaction priority. Valid range is ! - !.
(DBERR 2435)
CAUSE
You issued a BEGIN WORK with an invalid priority option.
ACTION
Reissue the BEGIN WORK with a priority within the valid
range.
MESSAGE
Invalid decimal parameter - Scale ! exceeds precision !.
(DBERR 2436)
CAUSE
The decimal scale was greater than the precision value.
ACTION
Refer to the \Data Types" chapter in the ALLBASE/SQL
Reference Guide for complete information about valid decimal
values.
MESSAGE
Invalid decimal result - Scale ! exceeds precision !.
(DBERR 2437)
CAUSE
The scale specied was greater than the precision specied for a
procedure result column.
ACTION
Issue the CREATE PROCEDURE statement again, specifying a
valid decimal result type. Refer to the ALLBASE/SQL Reference
Manual for valid decimal data type specications.
MESSAGE
Length of result ! in procedure !.! exceeds ! bytes.
(DBERR 2438)
CAUSE
The number of bytes you specied for a procedure result column
exceeded the maximum allowed.
ACTION
Issue the CREATE PROCEDURE statement again, specifying a
number of bytes no greater than the maximum.
MESSAGE
Length of result ! in procedure !.! below minimum ! bytes.
(DBERR 2439)
CAUSE
You tried to create a procedure result column with a length of 0
bytes.
ACTION
Issue the CREATE PROCEDURE statement again, specifying a
length of at least 1 byte.
ALLBASE/SQL Error Messages
2440
2449
2450
2452
MESSAGE
! should be ! to !. Number ! is invalid. (DBERR 2440)
CAUSE
The size you specied for one or more parameters of the START
DBE statement is invalid.
ACTION
Issue the START DBE statement again, specifying valid
numbers for the following parameters: DBEFile0 should be 50 to
16,777,215 pages long; DBELOG should be 250 to 16,777,215
pages long; Max Transactions should be 2 to 240 concurrent
transactions; Data Buer range is 15 to 50,000 pages and the Log
Buer range is 24 to 1024 pages.
MESSAGE
TRANSFER OWNERSHIP OF MODULE is not supported. (DBERR
2449)
CAUSE
You specied the MODULE option of the TRANSFER
OWNERSHIP statement. However, the ownership of modules
cannot be transferred.
ACTION
DROP the existing modules and preprocess the program with the
-o option.
MESSAGE
BEGIN WORK MULTI is not supported. (DBERR 2450)
CAUSE
You attempted to use the MULTI option for the BEGIN WORK
statement.
ACTION
You can have only one active transaction at a time. Issue a
COMMIT WORK or ROLLBACK WORK statement before
beginning the second transaction.
MESSAGE
Clustering index not allowed on table on which hash
structure has already been defined. (DBERR 2452)
CAUSE
You tried to create a clustering B-tree index on a table on which
a hash structure already existed.
ACTION
Issue the CREATE INDEX statement again, omitting the
CLUSTERING option
or
UNLOAD the data from the table. DROP the table. ReCREATE
the table, omitting the HASH option. Issue the CREATE INDEX
statement again to create a clustering B-tree index. LOAD the
data.
ALLBASE/SQL Error Messages
3-123
2453
2500
2501
2502
MESSAGE
Non-unique hash is not supported. (DBERR 2453)
CAUSE
You tried to create a table with a non-unique hash structure.
ACTION
Issue the CREATE TABLE statement again, including the
UNIQUE keyword with the HASH option.
MESSAGE
Cannot drop a non-empty DBEFileSet. (DBERR 2500)
CAUSE
You attempted to DROP a DBEFileSet which has DBEFiles
associated with it.
ACTION
Before dropping the DBEFileSet, drop the DBEFiles then remove
them. Remember that the DBEFiles must be empty before they
can be dropped.
MESSAGE
DBEFileSet has no DBEFiles. (DBERR 2501)
CAUSE
You created a table in an empty DBEFileSet and then tried to
INSERT into that table.
ACTION
ADD a DBEFile to the DBEFileSet before attempting an
INSERT statement.
MESSAGE
! space exhausted in DBEFileSet !. (DBERR 2502)
CAUSE
This message can have several meanings as follows:
1. All the space is exhausted in a DBEFileset if no expandable
DBEFiles are available.
2. All xed-length DBEFiles in the DBEFileSet have run out of
space, and all expandable DBEFiles have been fully expanded.
The rst parameter is the setting for the DBEFile's TYPE
attribute. Valid settings are INDEX, TABLE, and MIXED.
ACTION
3-124
Add new DBEFiles of the appropriate type to the DBEFileSet.
If space has been exhausted in the System.DBEFileSet during a
query, try adding more tempspace and more contiguous physical
disk space.
ALLBASE/SQL Error Messages
2503
2505
2506
2507
MESSAGE
DBEFile not empty. (DBERR 2503)
CAUSE
You attempted to REMOVE a non-empty DBEFile from its
DBEFileSet.
ACTION
The DBEFile must be empty before it can be removed from the
DBEFileSet.
MESSAGE
DBEFile size must be between ! and ! pages. (DBERR 2505)
CAUSE
The le size you specied in the CREATE DBEFILE statement
was not within the valid range.
ACTION
Issue the CREATE DBEFILE statement again, specifying a valid
le size.
MESSAGE
TempSpace file size limit must be between ! and ! pages.
(DBERR 2506)
CAUSE
The le size you specied in the CREATE TEMPSPACE
statement was not within the valid range.
ACTION
Issue the CREATE TEMPSPACE statement again, specifying a
valid le size.
MESSAGE
DBEFile must be empty or new type must be mixed. (DBERR
2507)
CAUSE
You attempted to ALTER a non-empty DBEFile to a type other
than mixed.
ACTION
The type of a non-empty DBEFile can be changed from TABLE
or INDEX to MIXED. No other changes are allowed.
ALLBASE/SQL Error Messages
3-125
2508
MESSAGE
DBEFileSet has no DBEFile of required DBEFile type.
(DBERR 2508)
CAUSE
You tried to insert rows into a table whose DBEFileSet has only
INDEX DBEFiles
or
you tried to create an index on a non-empty table whose
DBEFileSet contains only DATA DBEFiles.
2509
2510
2511
3-126
ACTION
Ask your database administrator to CREATE and ADD the
appropriate DBEFiles.
MESSAGE
Index uniqueness or UNIQUE/PRIMARY KEY constraint
violated. (DBERR 2509)
CAUSE
You tried to insert a duplicate key value into a column used in a
unique index or a unique constraint.
ACTION
Issue the INSERT or UPDATE statement again without the
duplicate row.
MESSAGE
Table is read only. (DBERR 2510)
CAUSE
You tried a LOCK or WRITE operation (DROP, DELETE,
INSERT, LOCK TABLE, UPDATE, UPDATE STATISTICS) on
a read only table.
ACTION
No action is necessary. These operations cannot be performed
on SYSTEM.CALL, SYSTEM.ACCOUNT, SYSTEM.USER,
SYSTEM.COUNTER, or SYSTEM.TRANSACTION.
MESSAGE
User ! does not exist. (DBERR 2511)
CAUSE
The DBEUserId you specied in the TERMINATE USER
or RESET SYSTEM.ACCOUNT command is not currently
connected to the DBEnvironment.
ACTION
Issue the command again, specifying a valid userid.
ALLBASE/SQL Error Messages
2512
2513
2514
2515
MESSAGE
Session ID ! does not exist. (DBERR 2512)
CAUSE
You attempted to terminate a session ID that does not exist, or
you do not have the authority to terminate it.
ACTION
Check that a valid session ID was used. If the session ID is valid,
have your DBA issue the statement.
MESSAGE
Number of primary pages must be between ! and !. (DBERR
2513)
CAUSE
You specied a number of primary pages for the hash in the
CREATE TABLE statement which was not within the valid
range.
ACTION
Issue the CREATE TABLE statement again, specifying a valid
number of primary pages.
MESSAGE
Hash key uniqueness or UNIQUE/PRIMARY KEY constraint
violated. (DBERR 2514)
CAUSE
You tried to insert a duplicate key value into a column used in
a unique hash structure, which might be supporting a unique
constraint.
ACTION
Issue the INSERT statement again without the duplicate row.
MESSAGE
DBEFile is currently associated with a DBEFileSet. (DBERR
2515)
CAUSE
You tried to DROP a DBEFile which was associated with a
DBEFileSet
or
you tried to ADD a DBEFile to a DBEFileSet which already is
associated with another DBEFileSet.
ACTION
You must REMOVE the DBEFile from the DBEFileSet before it
can be dropped
or
you must REMOVE the DBEFile from the DBEFileSet with
which it is currently associated before you can ADD it to a
dierent DBEFileSet.
ALLBASE/SQL Error Messages
3-127
2516
2518
2519
2520
3-128
MESSAGE
This table already has a clustering index. (DBERR 2516)
CAUSE
When you use the CREATE INDEX statement, no more than one
index per table can have the clustering attribute.
ACTION
Drop the existing clustering index or create the new index
without the clustering attribute.
MESSAGE
DBEFile in use for hash. (DBERR 2518)
CAUSE
You tried to DROP or ALTER a DBEFile that is allocated for
hash table data.
ACTION
First DROP the hash table. Then, the DBEFile may be
DROPped or ALTERed.
MESSAGE
Exceeded maximum number of DBEFiles for hash space (!).
(DBERR 2519)
CAUSE
The DBEFileSet specied for the hash table does not contain
DBEFiles large enough that the primary pages for the hash table
can be allocated using 16 or fewer DBEFiles.
ACTION
Create additional DBEFiles large enough that the primary pages
for the hash table can be allocated using 16 or fewer DBEFiles.
MESSAGE
Not enough space in DBEFileset for hash primary pages.
(DBERR 2520)
CAUSE
There is not enough space in the empty table or mixed DBEFiles
in the DBEFileSet specied for the number of primary pages
specied.
ACTION
Create additional DBEFile(s) with enough space for the primary
pages, and add them to the specied DBEFileSet. If you create
the les in the same transaction as you create the table with the
hash structure, you can ensure that no other transaction will be
able to use the les.
ALLBASE/SQL Error Messages
2521
2522
2523
2524
2525
MESSAGE
Maximum size for DBEFile expansion exceeds ! pages. (DBERR
2521)
CAUSE
The maximum size that a DBEFile can be expanded, as specied
in the MAXPAGES clause, exceeds the DBEFile maximum limit.
The maximum size may not be exactly the same size specied
with MAXPAGES, because it could be a rounded number.
ACTION
Make sure the maximum DBEFile size specied is within the
system limit.
MESSAGE
DBEFile INCREMENT size must be between ! and ! pages.
(DBERR 2522)
CAUSE
The size you specied in the INCREMENT clause for DBEFile
expansion is not within the range.
ACTION
Specify a valid INCREMENT size for the corresponding DBEFile.
MESSAGE
Maximum size ! pages for DBEFile expansion is less than the
initial size ! pages. (DBERR 2523)
CAUSE
The maximum size that a DBEFile can be expanded, as specied
in the MAXPAGES clause, is less than the initial DBEFile size
specied in the WITH PAGES clause. The maximum size may
not be exactly the same size specied with MAXPAGES, because
it could be a rounded number.
ACTION
Make sure the maximum DBEFile size specied is at least equal
to the initial DBEFile size, and that it is a multiple of the
INCREMENT size. If dynamic DBEFile expansion is required,
the maximum size must be greater than the initial size.
MESSAGE
Connection ID ! does not exist. (DBERR 2524)
CAUSE
The Connection ID specied does not exist.
ACTION
Use a valid Connection ID.
MESSAGE
Transaction ID ! does not exist. (DBERR 2525)
CAUSE
The Transaction ID specied does not exist.
ACTION
Use a valid Transaction ID.
ALLBASE/SQL Error Messages
3-129
2526
2527
2528
2529
2530
2600
3-130
MESSAGE
Attempting to terminate current query. (DBERR 2526)
CAUSE
The current query is being terminated.
ACTION
Take appropriate action for this query.
MESSAGE
There is no transaction for Connection ID !. (DBERR 2527)
CAUSE
There was an attempt to terminate a transaction for the specied
Connection ID, but no transaction was in progress.
ACTION
No action is required.
MESSAGE
Attempting to terminate persistent transaction. (DBERR
2528)
CAUSE
There is an attempt to terminate a persistent transaction.
ACTION
The SQLUtil command cannot be used to terminate a persistent
transaction.
MESSAGE
The user termination level does not allow this type of
termination. (DBERR 2529)
CAUSE
The user attempted to perform an unauthorized termination.
ACTION
A user can terminate a transaction or query if the user is the
owner or the user has DBA authority. No action required.
MESSAGE
Query was aborted externally. (DBERR 2530)
CAUSE
The query was aborted by an external process.
ACTION
Resume the query at an appropriate time.
MESSAGE
Integer overflow on operation !. (DBERR 2600)
CAUSE
The result of an integer arithmetic operation within an expression
was too big for the hardware to accommodate.
ACTION
Try to modify your expression so that divisions occur before
multiplications or break the expression into multiple expressions.
ALLBASE/SQL Error Messages
2601
2602
2603
2604
2605
MESSAGE
Integer divide by zero. (DBERR 2601)
CAUSE
The result of an arithmetic operation within an expression caused
an integer value to be divided by zero.
ACTION
Look at your data to nd where this error occurred and make any
necessary changes to your expression.
MESSAGE
Extended precision overflow on operation !. (DBERR 2602)
CAUSE
The result of a oat arithmetic operation within an expression
was too big for the hardware to accommodate.
ACTION
Try to modify your expression so that divisions occur before
multiplications or break the expression into multiple expressions.
MESSAGE
Extended precision underflow on operation !. (DBERR 2603)
CAUSE
The result of a oat arithmetic operation within an expression
was too small for the hardware to accommodate.
ACTION
Try to modify your expression so that multiplications occur
before divisions or break the expression into multiple expressions.
MESSAGE
Extended precision divide by zero. (DBERR 2604)
CAUSE
The result of an arithmetic operation within an expression caused
an extended precision value to be divided by zero.
ACTION
Look at your data to nd where this error occurred and make any
necessary changes.
MESSAGE
Packed decimal overflow on operation !. (DBERR 2605)
CAUSE
The result of an intermediate decimal operation was too big for
the hardware to accommodate.
ACTION
Try to modify your expression so that divisions occur before
multiplications or break the expression into multiple expressions.
ALLBASE/SQL Error Messages
3-131
2606
2607
2609
2610
2615
3-132
MESSAGE
Invalid decimal digit in operation !. (DBERR 2606)
CAUSE
The decimal number you included through the host variable in a
COBOL program was not valid.
ACTION
Correct the decimal so that it is within the range of 0 through 9
and contains either a + or - sign.
MESSAGE
Packed decimal divide by zero. (DBERR 2607)
CAUSE
The result of an arithmetic operation within an expression caused
a packed decimal value to be divided by zero.
ACTION
Look at your data to nd where this error occurred and make any
necessary changes.
MESSAGE
Incompatible data types ! and ! in expression. (DBERR
2609)
CAUSE
You attempted to mix numeric and character data types in an
expression in the select list, the WHERE clause, or the SET
clause.
ACTION
Issue the command again, specifying either numeric or character
data only.
MESSAGE
Operator ! invalid for data type !. (DBERR 2610)
CAUSE
You attempted to perform an arithmetic operation on char or
varchar data, or attempted the LIKE predicate on numeric data.
ACTION
Issue the command again using only appropriate operators on
data types.
MESSAGE
Datetime value contains a field greater than valid range
allowed. (DBERR 2615)
CAUSE
You tried to insert a datetime value which was not valid.
ACTION
Verify that all elds of all datetime literals are within the valid
range.
ALLBASE/SQL Error Messages
2616
2617
2618
2619
2620
MESSAGE
Datetime value contains a field less than valid range
allowed. (DBERR 2616)
CAUSE
You tried to insert a datetime value which was not valid.
ACTION
Verify that all elds of all datetime literals are within the valid
range.
MESSAGE
Datetime data value does not match default format
specification. (DBERR 2617)
CAUSE
You tried to insert a datetime value which did not meet the
default specication criteria of \YYYY-MM-DD HH:MI:SS.FFF."
ACTION
Verify that all elds of all datetime literals match the default
format specication.
MESSAGE
ALLBASE/SQL internal error in datetime conversion
routine. (DBERR 2618)
CAUSE
ALLBASE/SQL internal software problem.
ACTION
Contact your HP Service Representative or Response Center.
MESSAGE
Invalid date entered, February 29th invalid for non-leap
year. (DBERR 2619)
CAUSE
You tried to insert a datetime value which was not valid.
ACTION
Enter the correct date.
MESSAGE
Result of DATE/TIME arithmetic exceeds maximum value
allowed. (DBERR 2620)
CAUSE
The arithmetic produced a value greater than the maximum
allowed.
ACTION
Verify that the requested arithmetic should produce a result
which exceeds maximum values specied.
ALLBASE/SQL Error Messages
3-133
2621
2622
2623
2624
2625
3-134
MESSAGE
Result of DATE/TIME arithmetic less than minimum value
allowed. (DBERR 2621)
CAUSE
The arithmetic produced a value less than the minimum allowed.
ACTION
Verify that the requested arithmetic should produce a result
which is less than the minimum values specied.
MESSAGE
Size of datetime literal less than valid default size.
(DBERR 2622)
CAUSE
You tried to insert a datetime value of incorrect length.
ACTION
Verify that all datetime literals in the query are of the correct
size.
MESSAGE
Date value contains a field greater than valid range
allowed. (DBERR 2623)
CAUSE
You tried to insert a date value which was not valid.
ACTION
Verify that all elds of all date literals are within the valid range.
MESSAGE
Date value contains a field less than valid range allowed.
(DBERR 2624)
CAUSE
You tried to insert a date value which was not valid.
ACTION
Verify that all elds of all date literals are within the valid range.
MESSAGE
Date data value does not match default format specification. (DBERR 2625)
CAUSE
You tried to insert a date value which did not meet the default
specication criteria.
ACTION
Verify that all datetime literals in the query are specied in the
default specication \YYYY-MM-DD."
ALLBASE/SQL Error Messages
2626
2627
2628
2629
2630
2631
MESSAGE
Size of date literal less than valid default size. (DBERR
2626)
CAUSE
You tried to insert a date value of incorrect length.
ACTION
Verify that all date literals in the query are of the correct size.
MESSAGE
Time value contains a field greater than valid range
allowed. (DBERR 2627)
CAUSE
You tried to insert a time value which was not valid.
ACTION
Verify that all elds of all time literals are within the valid range.
MESSAGE
Time value contains a field less than valid range allowed.
(DBERR 2628)
CAUSE
You tried to insert a time value which was not valid.
ACTION
Verify that all elds of all time literals are within the valid range.
MESSAGE
Time data value does not match default format specification. (DBERR 2629)
CAUSE
You tried to insert a time value which did not meet the default
specication \HH:MI:SS."
ACTION
Verify that all time literals match the default format specication.
MESSAGE
Size of time literal less than valid default size. (DBERR
2630)
CAUSE
You tried to insert a time value of incorrect length.
ACTION
Verify that all time literals in the query are of the correct size.
MESSAGE
Interval value contains a field greater than valid range
allowed. (DBERR 2631)
CAUSE
You tried to insert an interval value which was not valid.
ACTION
Verify that all elds of all interval literals are within the valid
range.
ALLBASE/SQL Error Messages
3-135
2632
2633
2634
2635
2636
3-136
MESSAGE
Interval value contains a field less than valid range
allowed. (DBERR 2632)
CAUSE
You tried to insert an interval value which was not valid.
ACTION
Verify that all elds of all interval literals are within the valid
range.
MESSAGE
Interval data value does not match default format
specification. (DBERR 2633)
CAUSE
You tried to insert an interval value which did not meet the
default specication criteria.
ACTION
Verify that all interval literals in the query are specied in
the default specication \DDDDDDD HH:MI:SS.FFF" where
\DDDDDDD" can be 1 to 7 digits.
MESSAGE
Size of interval literal less than valid default size.
(DBERR 2634)
CAUSE
You tried to insert an interval value of incorrect length.
ACTION
Verify that all interval literals in the query are of the correct size.
MESSAGE
Real precision overflow on operation !. (DBERR 2635)
CAUSE
The result of a real arithmetic operation within an expression was
too big for the hardware to accommodate.
ACTION
Try to modify your expression to convert the real values in it to
oats or to have a target host variable of type FLOAT.
MESSAGE
Real precision underflow on operation !. (DBERR 2636)
CAUSE
The result of a real arithmetic operation within an expression was
too small for the hardware to accommodate.
ACTION
Try to modify your expression to convert the real values in it to
oats or to have a target host variable of type FLOAT.
ALLBASE/SQL Error Messages
2637
2638
2639
2641
2642
MESSAGE
Format specification exceeds maximum length (! bytes).
(DBERR 2637)
CAUSE
You specied a date/time format length which exceeds the
maximum length of 72 bytes.
ACTION
Issue the command again with the length less than 72 bytes.
MESSAGE
End of format specification detected before parsing end of
datetime literal. (DBERR 2638)
CAUSE
Datetime literal does not match format specication given. Extra
characters exist in datetime literal after parsing end of format
specication.
ACTION
Ensure the compatibility between the format specication and
datetime literal specied in the datetime input function.
MESSAGE
Invalid format specification in second parameter of
datetime function. (DBERR 2639)
CAUSE
A unit within the format specication is not a valid unit.
ACTION
Re-issue the command with a format specication.
MESSAGE
Redundant fields specified in format specification.
(DBERR 2641)
CAUSE
A unit in the format specication was specied twice, or two
units which contain identical units.
ACTION
Re-issue the command with a valid format specication.
MESSAGE
Invalid data type for second parameter of datetime
function. (DBERR 2642)
CAUSE
Data type of second parameter is not valid.
ACTION
Please check the documentation for valid format types.
ALLBASE/SQL Error Messages
3-137
2643
2644
2645
2646
2647
3-138
MESSAGE
Format specification contains an invalid unit for data
type !. (DBERR 2643)
CAUSE
A valid unit was specied in the format specication, but it is not
valid for this datetime type.
ACTION
Please check the documentation for valid format types for this
datetime data type.
MESSAGE
Datetime input function cannot parse input parameters.
(DBERR 2644)
CAUSE
When parsing datetime literal, invalid data was detected.
ACTION
Check validity of datetime literal in rst parameter of datetime
input function.
MESSAGE
Day of week specified does not match date supplied. (DBERR
2645)
CAUSE
Alphabetic day of week specied incorrect for date literal
specied.
ACTION
Re-issue command with valid datetime literal.
MESSAGE
End of datetime literal detected before parsing end of
format specification. (DBERR 2646)
CAUSE
Format specication does not match datetime literal.
ACTION
Re-issue command with correct input to datetime input function.
MESSAGE
Datetime literal contains a value outside the valid range
for a format specified. (DBERR 2647)
CAUSE
A unit in datetime literal is not within boundary of the unit
values allowed.
ACTION
Issue command with correct values for units specied in format
specication.
ALLBASE/SQL Error Messages
2650
2651
2652
2653
2654
MESSAGE
Invalid length in VARCHAR. (DBERR 2650)
CAUSE
An invalid length eld for a VARCHAR data type was detected
in SQLCORE. The most likely cause of this would be an
uninitialized VARCHAR host variable used in an insert or an
uninitialized VARCHAR length eld in the buer used in a bulk
insert.
ACTION
Make sure that all VARCHAR host variables are properly
initialized.
MESSAGE
DEFAULT literal type ! is not compatible with the
corresponding column data type !. (DBERR 2651)
CAUSE
The data type of the literal is not compatible with the one
specied for the corresponding column.
ACTION
Dene a valid default value for the corresponding column.
MESSAGE
DEFAULT ! is not compatible with the corresponding column
data type !. (DBERR 2652)
CAUSE
You specied a DEFAULT current function, USER, or
NULL, which is not compatible with the one specied for the
corresponding column.
ACTION
Dene a valid default value for the corresponding column.
MESSAGE
Non-supported DEFAULT value type !. (DBERR 2653)
CAUSE
You specied a DEFAULT value which is not a constant, a
current function, USER, or NULL.
ACTION
Dene a valid default value for the corresponding column.
MESSAGE
Data type ! invalid for the starting position of SUBSTRING
function. (DBERR 2654)
CAUSE
The StartPosition parameter of the SUBSTRING function is not
an integer constant or expression.
ACTION
Change the StartPosition parameter to an integer constant or
expression.
ALLBASE/SQL Error Messages
3-139
2655
2656
2657
2658
3-140
MESSAGE
Data type ! invalid for the substring length of SUBSTRING
function. (DBERR 2655)
CAUSE
The Length parameter of the SUBSTRING function is not an
integer constant or expression.
ACTION
Change the Length parameter to an integer constant or
expression.
MESSAGE
Source string must contain numeric value. (DBERR 2656)
CAUSE
The source character string of the CAST function contains invalid
characters for a numeric expression.
ACTION
Make sure the source character string contains an appropriate
representation of a numeric value with no extraneous characters
added.
MESSAGE
CAST target data type too small. (DBERR 2657)
CAUSE
The size in bytes of the specied target data type is too small to
hold the value being converted.
ACTION
Specify a larger target data type.
MESSAGE
Numeric/Binary conversion must be of equal length. (DBERR
2658)
CAUSE
In converting numeric data types to BINARY, the size in
bytes of the source and target must be equal. If the target is a
VARBINARY, the maximum size of the target must be equal or
exceed the source size invalid character based on the target data
type specied. This error will be reported if this is not true.
ACTION
When converting to BINARY, make sure that the specied size
of the BINARY matches the size of the source. If converting
to VARBINARY, make sure that the specied size of the
VARBINARY is at least the size of the source. When converting
from BINARY or VARBINARY to a numeric type, string
concatenation (jj) or the SUBSTRING function can be used to
make the source the correct size for the target.
ALLBASE/SQL Error Messages
2659
2660
2661
MESSAGE
Date/Binary conversion must be of equal length. (DBERR
2659)
CAUSE
In converting Date/Time data types to BINARY, the size in
bytes of the source and target must be equal. If the target is a
VARBINARY, the maximum size of the target must be equal or
exceed the source size invalid character based on the target data
type specied. This error will be reported if this is not true.
ACTION
When converting to BINARY, make sure that the specied size
of the BINARY matches the size of the source (16 bytes). If
converting to VARBINARY, make sure that the specied size
of the VARBINARY is at least the size of the source. When
converting from BINARY or VARBINARY to a Date/Time type,
the source should be 16 bytes.
MESSAGE
TID/Binary conversion must be of equal length. (DBERR
2660)
CAUSE
In converting TID data types to BINARY, the size in bytes of the
source and target must be equal. If the target is a VARBINARY,
the maximum size of the target must be equal or exceed the
source size invalid character based on the target data type
specied. This error will be reported if this is not true.
ACTION
When converting to BINARY, make sure that the specied size
of the BINARY matches the size of the source (8 bytes). If
converting to VARBINARY, make sure that the specied size
of the VARBINARY is at least the size of the source. When
converting from BINARY or VARBINARY to a Date/Time type,
the source should be 8 bytes.
MESSAGE
Invalid TID format. (DBERR 2661)
CAUSE
The character string being converted to a TID data type was not
properly formatted.
ACTION
The correct syntax for a character string representation of a TID
is:
2
3
0: lenumber:pagenumber:slot
where:
lenumber
pagenumber
slot
is the DBEle number (0-32767)
is the page number (0-16777215)
is the slot number (0-255)
ALLBASE/SQL Error Messages
3-141
2700
2701
2702
2703
3-142
MESSAGE
INSERT/UPDATE/DELETE disallowed on a join. (DBERR 2700)
CAUSE
You attempted to INSERT, UPDATE, or DELETE on a multiple
table view.
ACTION
You cannot perform an INSERT, UPDATE, or DELETE on
multi-table views. Refer to the specied command and the
CREATE VIEW statement in the ALLBASE/SQL Reference
Manual for additional information.
MESSAGE
INSERT/UPDATE disallowed on virtual column (!). (DBERR
2701)
CAUSE
You attempted to INSERT or UPDATE a computed column in a
view.
ACTION
Inserting rows through a view is not allowed if any column of
the view is computed in an arithmetic expression. Refer to the
ALLBASE/SQL Reference Manual for additional information.
MESSAGE
INSERT/UPDATE/DELETE disallowed on group operation.
(DBERR 2702)
CAUSE
You attempted to INSERT, UPDATE, or DELETE rows via a
view which contained a GROUP BY clause in its denition.
ACTION
A view denition for UPDATE, DELETE, and INSERT
operations cannot contain a GROUP BY clause. Refer to the
specied command and the CREATE VIEW statement in the
ALLBASE/SQL Reference Manual for additional information.
MESSAGE
INSERT/UPDATE/DELETE disallowed on ORDER BY. (DBERR
2703)
CAUSE
You attempted to declare a cursor containing both an ORDER
BY clause and a FOR UPDATE clause, or you attempted
an UPDATE or DELETE WHERE CURRENT on a cursor
containing an ORDER BY clause.
ACTION
Remove the ORDER BY from the cursor if updates and/or
deletes are to be performed with it, or remove the FOR UPDATE
clause from the cursor.
ALLBASE/SQL Error Messages
2705
MESSAGE
Illegal reference to column ! in group operation. (DBERR
2705)
CAUSE
A column you specied in the select list was not referenced in the
GROUP BY clause of the SELECT statement.
or
you are doing a GROUP BY with a SELECT * and you have
failed to reference all of the columns in the specied table in the
GROUP BY clause.
ACTION
Issue the SELECT statement again, specifying only aggregate
functions and columns referenced in the GROUP BY clause
In the case of SELECT *, be sure to reference all columns
produced by the expansion of the * in the GROUP BY clause.
2706
2707
2708
MESSAGE
INSERT/UPDATE/DELETE disallowed on DISTINCT operation.
(DBERR 2706)
CAUSE
UPDATE, INSERT, and DELETE operations through a view are
not allowed if the view denition involves a distinct clause.
ACTION
Perform the UPDATE, INSERT, or DELETE operation on the
base table or re-create the view without the DISTINCT clause.
MESSAGE
UPDATE/DELETE disallowed on a cursor containing a
subquery. (DBERR 2707)
CAUSE
You attempted to UPDATE or DELETE rows accessed through a
cursor which contained a subquery in its denition.
ACTION
Perform the UPDATE or DELETE only through a cursor which
does not contain a subquery.
MESSAGE
UPDATE/DELETE disallowed with subquery containing
update/delete table. (DBERR 2708)
CAUSE
You attempted to UPDATE or DELETE through a view or with
a search condition containing a subquery which references the
target table.
ACTION
Perform the UPDATE or DELETE only through views with
search conditions which do not reference the target table in any
subqueries.
ALLBASE/SQL Error Messages
3-143
2709
2710
2711
2712
3-144
MESSAGE
UPDATE/DELETE disallowed on UNION. (DBERR 2709)
CAUSE
You attempted to UPDATE or DELETE through a cursor
containing a UNION.
ACTION
Perform the UPDATE or DELETE only through cursors not
containing UNIONs.
MESSAGE
INSERT or FORMAT II INSERT disallowed on a view
referencing the insert table in a subquery. (DBERR 2710)
CAUSE
You attempted to insert through a view, where the view contains
a subquery which references the same base table the view is based
upon. Such an insert is not allowed.
ACTION
Insert directly through the base table, or use a view not
containing subqueries which reference the same table as the view.
MESSAGE
Qualifier !.! (column !) is different from input table.
(DBERR 2711)
CAUSE
The table name you specied in the select list or WHERE clause
is dierent from the table name specied in the FROM clause of
the SELECT statement.
ACTION
Issue the SELECT statement again, specifying the same table
name in both the select list or WHERE clause and the FROM
clause. Refer to the ALLBASE/SQL Reference Manual for
additional information on the SELECT statement.
MESSAGE
Hash key columns may not be updated. (DBERR 2712)
CAUSE
You tried to update the value of a column included in the key for
a hash.
ACTION
DELETE the tuple with the old key column value. Then,
INSERT a new tuple with the new key column value.
ALLBASE/SQL Error Messages
2716
2717
2718
2719
2720
MESSAGE
User ! does not have authority to GENPLAN on table/view
!.!.(!) (DBERR 2716)
CAUSE
You do not have run authority to GENPLAN on a specied
section.
ACTION
Contact your database administrator to get the required
authority or sign on as a user who does have the required
authority.
MESSAGE
The specified section !.!(!) is not a SELECT, UPDATE,
DELETE or type II INSERT statement. (DBERR 2717)
CAUSE
The specied section you included is not an allowed statement for
GENPLAN.
ACTION
Check the source le to nd the right section number.
MESSAGE
Optimizer did not generate an access plan for the query.
(DBERR 2718)
CAUSE
Internal Error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
User ! does not have authority to GENPLAN on table/view
!.!. (DBERR 2719)
CAUSE
You do not have the required authority to execute GENPLAN on
the named table or view.
ACTION
Contact your database administrator to obtain the required
authority or sign on as a user who does have the required
authority.
MESSAGE
INSERT/UPDATE/DELETE disallowed on system tables (!.!).
(DBERR 2720)
CAUSE
You attempted to INSERT, UPDATE or DELETE to a system
table.
ACTION
Re-issue the statement on a non-system table.
ALLBASE/SQL Error Messages
3-145
2724
2725
2726
2730
2731
3-146
MESSAGE
Command ! is not allowed for views (!.!). (DBERR 2724)
CAUSE
You specied a command (ALTER TABLE, UPDATE
STATISTICS, LOCK TABLE) that cannot be performed on a
view.
ACTION
No action is necessary. Refer to the ALLBASE/SQL Reference
Manual for additional information on these commands and the
ALLBASE/SQL Database Administration Guide for additional
information on views.
MESSAGE
Use DROP VIEW to drop view !.!. (DBERR 2725)
CAUSE
You attempted to drop a view using the DROP TABLE
statement.
ACTION
Use the DROP VIEW statement to drop a view.
MESSAGE
Use DROP TABLE to drop table !.!. (DBERR 2726)
CAUSE
You attempted to drop a table using the DROP VIEW
statement.
ACTION
Use the DROP TABLE statement to drop a table.
MESSAGE
Column ! does not accept nulls. (DBERR 2730)
CAUSE
You specied the NULL keyword for a non-null column in the
INSERT or UPDATE statement.
ACTION
Issue the command again, specifying a value for all non-null
columns.
MESSAGE
Reset command not valid for table !.!. (DBERR 2731)
CAUSE
You cannot issue the RESET statement on the specied table.
ACTION
No action is necessary. The only valid tables for the RESET
statement are SYSTEM.COUNTER and SYSTEM.ACCOUNT.
ALLBASE/SQL Error Messages
2732
2740
2741
2742
2743
MESSAGE
Invalid number of columns in view column list. (DBERR
2732)
CAUSE
The number of columns in the CREATE VIEW statement did
not match the number of columns in the SELECT statement for
the view.
ACTION
Issue the command again using the same number of columns in
both the CREATE VIEW statement and the SELECT statement.
MESSAGE
Invalid savepoint number. (DBERR 2740)
CAUSE
The ROLLBACK WORK statement included a non-existent
savepoint.
ACTION
Issue the command again, specifying a valid savepoint number.
Refer to the ALLBASE/SQL Reference Manual for additional
information on the ROLLBACK WORK statement.
MESSAGE
Archive not begun. (DBERR 2741)
CAUSE
You attempted to COMMIT ARCHIVE without a preceding
BEGIN ARCHIVE statement.
ACTION
Issue the BEGIN ARCHIVE statement rst followed by the
COMMIT ARCHIVE statement.
MESSAGE
Archive already begun. (DBERR 2742)
CAUSE
The BEGIN ARCHIVE statement was issued twice.
ACTION
No action is necessary.
MESSAGE
Archive checkpoint not found. (DBERR 2743)
CAUSE
The checkpoint was not found.
ACTION
Review the syntax for CHECKPOINT statement.
ALLBASE/SQL Error Messages
3-147
2744
2749
MESSAGE
ROLLBACK WORK TO savepointnumber when you have cursors
opened with KEEP CURSOR option. (DBERR 2744)
CAUSE
You opened a cursor with the KEEP CURSOR option and you
are trying to use the SAVEPOINT option of the ROLLBACK
WORK statement.
ACTION
Revise the program to open the cursor without the KEEP
CURSOR option, or eliminate the TO SAVEPOINT clause.
MESSAGE
Procedure cursor !.!(!) has no current result set. (DBERR
2749)
CAUSE
An attempt was made to fetch from a procedure cursor, either
without rst issuing an ADVANCE statement
or
after an ADVANCE returned an sqlcode of 200 (no more result
sets).
ACTION
Issue an ADVANCE statement after opening the cursor, and
before trying to fetch results.
or
Check for an sqlcode of 200 on an ADVANCE statement before
attempting to fetch results.
2750
2752
3-148
MESSAGE
Module !.!(!) has DBEFileSet error. (DBERR 2750)
CAUSE
You tried to use DECLARE CURSOR or to PREPARE a section
in a non-existent DBEFileSet.
ACTION
Check your spelling, and examine the SYSTEM.DBEFILESET
view to make sure that the DBEFileSet actually exists. Then
issue the command again, specifying a valid DBEFileSet.
MESSAGE
Module !.!(!) is a cursor. (DBERR 2752)
CAUSE
You tried to use the EXECUTE statement on a cursor.
ACTION
The only valid commands for a cursor are OPEN, CLOSE,
FETCH, DESCRIBE, and DECLARE CURSOR.
ALLBASE/SQL Error Messages
2753
2754
MESSAGE
Module !.!(!) is not a cursor. (DBERR 2753)
CAUSE
You tried to OPEN, CLOSE, FETCH, or DESCRIBE a section
which was not dened with a DECLARE CURSOR statement.
ACTION
A cursor must be declared using the DECLARE CURSOR
statement before you refer to it in the other cursor commands.
MESSAGE
Cursor !. ! (!) is not open. (DBERR 2754)
CAUSE
ALLBASE/SQL automatically rolled back your transaction
causing the cursors to be closed
or
the cursor was never opened.
2755
2756
2757
ACTION
Insure that the cursor was opened.
MESSAGE
Module !.!(!) already open. (DBERR 2755)
CAUSE
You attempted to OPEN the same cursor twice.
ACTION
No action is necessary.
MESSAGE
Cursor !.!(!) has no current tuple. (DBERR 2756)
CAUSE
You issued an UPDATE or DELETE statement with a
CURRENT OF CURSOR clause without preceding it with a
FETCH statement or you terminated the transaction between the
FETCH and DELETE or UPDATE statement.
ACTION
A FETCH statement must precede any DELETE or UPDATE
WHERE CURRENT operation within the transaction.
MESSAGE
Update column list not in cursor update column list.
(DBERR 2757)
CAUSE
You tried to update a column which was not specied when the
cursor was declared.
ACTION
A column must be listed in the DECLARE CURSOR statement
before an update operation can be performed on that column.
ALLBASE/SQL Error Messages
3-149
2758
2759
2760
MESSAGE
Update table different from cursor table. (DBERR 2758)
CAUSE
You tried to update a table which was not specied in the
DECLARE CURSOR statement.
ACTION
A table must be listed in the DECLARE CURSOR statement
before it can be updated using the UPDATE statement with a
CURRENT OF CURSOR clause.
MESSAGE
Cursor has no current tuple. (DBERR 2759)
CAUSE
You issued an UPDATE or DELETE statement with a
CURRENT OF CURSOR clause when the current tuple had
already been deleted.
ACTION
Modify your application so that no UPDATE or DELETE
WHERE CURRENT is attempted once the current tuple has
been deleted.
MESSAGE
Null value detected and indicator variable not declared
OR attempted to put null value into non-null column or
result. (DBERR 2760)
CAUSE
A SELECT or FETCH statement had no corresponding indicator
variable and a null value was fetched for an item
or
you attempted to put a null value into a non-null column using
the INSERT or UPDATE statement by setting the indicator
variable to a negative number.
or
You specied NOT NULL for a procedure result and a null value
was fetched.
ACTION
Modify your program to include indicator variables with columns
that might contain null values
or
issue the INSERT or UPDATE statement again, specifying only
non-null values for columns created with the NOT NULL option.
or
drop the procedure and recreate it, either omitting the NOT
NULL option in the WITH RESULT clause, or modifying the
procedure SELECT statements so that no null values will be
retrieved.
3-150
ALLBASE/SQL Error Messages
2762
2763
2764
2765
MESSAGE
Selectlist has ! items and host variable buffer has !.
(DBERR 2762)
CAUSE
The number of select list items in a DECLARE CURSOR or a
SELECT statement does not match the number of host variables
in the corresponding FETCH or SELECT statement or the
number of select list items in the SELECT statement does not
match the number of host variables in the SELECT statement.
ACTION
Modify your program so that the number of variables in the
select list or the SELECT statement matches the number of host
variables. Refer to the ALLBASE/SQL Reference Manual for
additional information on these commands.
MESSAGE
DISTINCT within aggregate functions cannot reference
multiple column names. (DBERR 2763)
CAUSE
The SELECT statement contains more than one aggregate
function containing the DISTINCT option and references more
than one column.
ACTION
Modify your statement so that it references only one column.
Refer to the ALLBASE/SQL Reference Manual for additional
information on the SELECT statement.
MESSAGE
DISTINCT within an aggregate function cannot reference an
expression. (DBERR 2764)
CAUSE
The SELECT statement contains an aggregate function
containing the DISTINCT option and references a column
containing computed values.
ACTION
Modify your statement so that only raw columns are referenced.
Refer to the ALLBASE/SQL Reference Manual for additional
information on the SELECT statement.
MESSAGE
DDL commands disabled. (DBERR 2765)
CAUSE
The DDL Enabled ag in the DBECon le was set to NO when
you attempted to execute DDL (data denition language)
commands.
ACTION
STOP the DBEnvironment, use the SQLUtil ALTDBE
command to set the DDL Enabled ag to YES, then START the
DBEnvironment and proceed with data denition.
ALLBASE/SQL Error Messages
3-151
2766
2768
2769
2770
3-152
MESSAGE
Unable to revalidate section while DDL commands are
disabled. (DBERR 2766)
CAUSE
The DDL Enabled ag in the DBECon le was set to NO when
ALLBASE/SQL encountered an invalid stored section.
ACTION
STOP the DBEnvironment, use the SQLUtil ALTDBE
command to set the DDL Enabled ag to YES, then START the
DBEnvironment and run the application again.
MESSAGE
Current tuple does not satisfy the predicate in the cursor
definition. (DBERR 2768)
CAUSE
After you fetched the data, the data was updated by another
transaction and no longer satises your cursor denition.
ACTION
No action is necessary.
MESSAGE
Cursor !.!(!) is not updatable. (DBERR 2769)
CAUSE
You tried to REFETCH or UPDATE using a cursor that is not
updatable.
ACTION
Make sure you declare the cursor FOR UPDATE in the
DECLARE CUSOR statement.
MESSAGE
INSERT rejected: FORMAT II INSERT cannot insert a table
into itself. (DBERR 2770)
CAUSE
The table you specied as the target table in the INSERT
statement was the same as one of the tables in the embedded
SELECT statement.
ACTION
Modify your command specifying a dierent target table or
remove the target table from the embedded SELECT statement.
ALLBASE/SQL Error Messages
2771
2772
2773
2774
MESSAGE
KEEP CURSOR with NOLOCKS is not supported on NON-UPDATABLE
CURSOR. (DBERR 2771)
CAUSE
You specied the KEEP CURSOR WITH NOLOCKS option
for a cursor which was declared as SELECT . . . ORDER BY or
SELECT DISTINCT. These operations need to build temporary
tables, and if KEEP CURSOR WITH NOLOCKS is in eect, the
consistency between permanent and temporary tables cannot be
guaranteed between transactions.
ACTION
Revise the program to open the cursor with the KEEP CURSOR
WITH LOCKS option.
MESSAGE
Cursor !.!(!) containing SUBQUERY is not allowed in the
REFETCH command. (DBERR 2772)
CAUSE
You attempted to perform a REFETCH on a cursor containing a
subquery.
ACTION
REFETCH cannot be done on cursors containing subqueries.
Either remove the subquery from the cursor, or do not perform
REFETCH on that cursor.
MESSAGE
Multiple-rows operation is NOT allowed in the REFETCH
command. (DBERR 2773)
CAUSE
You specied more than one record in the REFETCH statement.
ACTION
Make sure to specify only one record for the REFETCH
statement.
MESSAGE
Escape character in LIKE pattern must be followed by
escape character, underscore, or percent. (DBERR 2774)
CAUSE
There is an escape character in a LIKE predicate pattern that is
not followed by an escape character, underscore, or percent.
ACTION
Change the pattern to a legal pattern.
ALLBASE/SQL Error Messages
3-153
2775
2776
2777
2778
2779
MESSAGE
Escape character must be a single character. (DBERR 2775)
CAUSE
You specied a multi-character string for the escape pattern, or
passed in a host variable containing more than a single character.
ACTION
Correct the specication of the escape string to be a single
character, or make sure that the host variable is set to blanks
after the escape character.
MESSAGE
Dynamic parameters as both operands of a single binary
operator disallowed. (DBERR 2776)
CAUSE
You specied dynamic parameters for both operands of an
arithmetic or comparison operator.
ACTION
Modify your statement to not specify dynamic parameters for
both operands of the arithmetic or comparison operator.
MESSAGE
Dynamic parameter as the operand of a unary arithmetic
operator disallowed. (DBERR 2777)
CAUSE
You specied a dynamic parameter in a NULL predicate or a
minus sign is specied in front of the dynamic parameter.
ACTION
Modify your statement to not contain a dynamic parameter
in a NULL predicate nor a minus sign in front of a dynamic
parameter.
MESSAGE
Dynamic parameter in the SELECT list disallowed. (DBERR
2778)
CAUSE
You specied a dynamic parameter in the SELECT list.
ACTION
Modify your statement to not contain a dynamic parameter in a
SELECT list.
MESSAGE
TID data type is not supported. (DBERR 2779)
CAUSE
You specied a column of TID data type in the CREATE
TABLE or ALTER TABLE statement. There is no TID data
type.
Check and modify the statement.
ACTION
3-154
ALLBASE/SQL Error Messages
2780
2781
MESSAGE
Psuedotable can not be updated. (DBERR 2780)
CAUSE
You attempted to perform an update on a system pseudotable.
ACTION
Check that the correct table name has been specied.
MESSAGE
Illegal reference to TID function in group operation.
(DBERR 2781)
CAUSE
Within a single query block, you cannot specify the GROUP BY
clause when using the TID function in the select list.
Check and modify the command.
ACTION
2782
MESSAGE
TID function is not allowed for the pseudotable (!.!).
(DBERR 2782)
CAUSE
The parameter in the TID function is a system pseudotable.
Check and modify the command.
ACTION
2783
MESSAGE
TID function is not allowed for the non-updatable view
(!.!). (DBERR 2783)
CAUSE
The parameter in the TID function is not an updatable view.
Check and modify the command.
ACTION
2784
2785
MESSAGE
DDL statement not allowed in PREPARE REPEAT command.
(DBERR 2784)
CAUSE
Data denition language statements (CREATE TABLE,
CREATE INDEX, DROP TABLE, etc.) are not allowed in a
PREPARE command with the REPEAT option.
ACTION
Do not use the REPEAT option for DDL commands.
MESSAGE
The starting position is invalid for the SUBSTRING
function. (DBERR 2785)
CAUSE
The StartPosition parameter of the SUBSTRING function is less
than 1 or greater than the length of the SourceString.
ACTION
Change the StartPosition parameter to a value greater than
0, and less than or equal to the length of the SourceString
parameter.
ALLBASE/SQL Error Messages
3-155
2786
2787
2788
2790
3-156
MESSAGE
The substring length is invalid for the SUBSTRING
function. (DBERR 2786)
CAUSE
The Length parameter of the SUBSTRING function is less than 1
or greater than the length of the SourceString parameter.
ACTION
Change the Length parameter to a value greater than 0, and less
than or equal to the length of the SourceString parameter.
MESSAGE
Length of item ! in select list exceeds that of
corresponding procedure result column. (DBERR 2787)
CAUSE
An item in the select list in a procedure SELECT statement with
no INTO clause has a length greater than that specied for the
corresponding procedure result column in the WITH RESULT
clause of the CREATE PROCEDURE statement.
ACTION
Re-issue the CREATE PROCEDURE statement, either omitting
the WITH RESULT clause, or ensuring that all multiple row
result sets returned from the procedure are compatible with the
format specied.
MESSAGE
USING Clause is required for output dynamic parameters.
(DBERR 2788)
CAUSE
You tried to execute a prepared EXECUTE PROCEDURE
statement with output dynamic parameters, but no output
variables were provided in the USING clause of an EXECUTE or
CLOSE statement.
ACTION
Issue the EXECUTE or CLOSE statement again with the USING
clause, specifying output variables for output dynamic parameters
in the prepared statement.
MESSAGE
CANNOT use DROP PARTITION on DEFAULT partition. (DBERR
2790)
CAUSE
You attempted to drop the DEFAULT partition.
ACTION
This partition cannot be dropped. Its partition number can be
changed with the START DBE NEWLOG statement.
ALLBASE/SQL Error Messages
2791
2792
2793
2794
2800
MESSAGE
Cannot CREATE PARTITION !. (DBERR 2791)
CAUSE
You attempted to create a partition named NONE or DEFAULT.
This partition name cannot be used since it refers to the
nonexistent partition.
ACTION
No partition can be created with this name in the CREATE
PARTITION statement.
MESSAGE
Comment text for LOG COMMENT must have data type CHAR or
VARCHAR. (DBERR 2792)
CAUSE
The value for a log comment was not a character value.
ACTION
Check the type of the value and be sure it is CHAR or
VARCHAR.
MESSAGE
Cannot LOG COMMENT when AUDIT LOG not enabled. (DBERR
2793)
CAUSE
You specied a LOG COMMENT statement in a DBEnvironment
without audit logging or with audit logging disabled.
ACTION
Enable AUDIT LOG for the DBEnvironment or refrain from
issuing LOG COMMENT on the DBEnvironment.
MESSAGE
Cannot open log scan on AUDIT CHECKPOINT only DBEnvironment. (DBERR 2794)
CAUSE
Unable to open the log scan on the AUDIT CHECKPOINT.
ACTION
Enable AUDIT LOG for the DBEnvironment, not for AUDIT
CHECKPOINT.
MESSAGE
Table's language not compatible with DBE's language.
(DBERR 2800)
CAUSE
The language you specied for the table is neither the same as
DBEnvironment's language, nor n-computer.
ACTION
Make sure the table's language is either n-computer or the same
as the DBEnvironment's language.
ALLBASE/SQL Error Messages
3-157
2801
2802
2803
2804
2805
3-158
MESSAGE
Column's language not compatible table/DBE's language.
(DBERR 2801)
CAUSE
The language you specied for the column is neither
table/DBEnvironment's language nor n-computer.
ACTION
Make sure the column's language is either the same as
table/DBEnvironment's language or n-computer.
MESSAGE
Procedure result language is not compatible with
procedure/DBEnvironment language. DBERR 2802)
CAUSE
A language other than that of the DBEnvironment or n-computer
was specied for a procedure result.
ACTION
Re-issue the CREATE PROCEDURE statement, either omitting
the language clause, or specifying either the DBEnvironment
language or n-computer.
MESSAGE
Procedure language is not compatible with DBEnvironment
language. (DBERR 2803)
CAUSE
The language you specied for the procedure was neither the
DBEnvironment language nor n-computer.
ACTION
Issue the CREATE PROCEDURE statement again, specifying
either the DBEnvironment language or n-computer for the
procedure, or specifying no procedure language.
MESSAGE
Parameter language is not compatible with procedure/DBEnvironment language. (DBERR 2804)
CAUSE
The language you specied for the parameter was neither the
procedure/DBEnvironment language nor n-computer.
ACTION
Issue the CREATE PROCEDURE statement again, specifying
either the procedure/DBEnvironment language or n-computer for
the parameter, or specifying no parameter language.
MESSAGE
NLINFO error !. Language ID = !. (DBERR 2805)
CAUSE
An error was returned from the NLS library routine NLINFO,
with the specied language.
ACTION
Check the validity of your NLS data and reissue the statement.
ALLBASE/SQL Error Messages
2806
2807
2808
2809
2810
MESSAGE
Comment text cannot be NULL for LOG COMMENT. (DBERR 2806)
CAUSE
The value passed to a LOG COMMENT was NULL.
ACTION
Check the value and reissue the statement with a non-null value.
MESSAGE
Cannot drop a non-empty partition. (DBERR 2807)
CAUSE
You issued a DROP PARTITION on a partition that currently
contains tables.
ACTION
Remove the tables from the partition with the ALTER TABLE
SET PARTITION statement and reissue the statement.
MESSAGE
Partition ! already exists. (DBERR 2808)
CAUSE
A CREATE PARTITION attempted to create a partition with a
name of a partition that is already dened.
ACTION
Reissue the CREATE PARTITION statement with another
partition name or issue a DROP PARTITION to remove the
existing partition and then reissue the CREATE PARTITION
statement.
MESSAGE
Partition ! not found. (DBERR 2809)
CAUSE
The partition name you specied by a DROP PARTITION,
ALTER TABLE SET PARTITION, or CREATE TABLE
statement does not exist.
ACTION
Check the partition name against the system catalog table
SYSTEM.PARTITION and reissue the CREATE TABLE or
ALTER TABLE SET PARTITION statement with the name of
an existing partition.
MESSAGE
Audit logging not set for DBE. (DBERR 2810)
CAUSE
You issued an ENABLE AUDIT LOGGING statement for the
session, but audit logging is turned o for the DBEnvironment.
ACTION
Check the correctness of operations. Either audit logging for the
DBEnvironment should be turned on (this may be done through
the START DBE NEWLOG statement) or the ENABLE AUDIT
LOGGING statement is not valid.
ALLBASE/SQL Error Messages
3-159
2811
2812
2813
2814
3-160
MESSAGE
Insufficient size specified for the new SCR. (DBERR 2811)
CAUSE
Note that it is possible to change the MAXPARTITIONS
parameter through the START DBE NEWLOG statement. In
so doing, the product restores the current SCR slots into this
new log le (the current SCR value has an image stored in the
DBECon le). If the new MAXPARTITIONS specied is not
large enough to contain all the occupied slots from the old SCR,
this error is generated.
ACTION
Reissue the START DBE NEWLOG statement with the
appropriate MAXPARTITIONS.
MESSAGE
There are still some active transactions in the old SCR.
(DBERR 2812)
CAUSE
You attempted a START DBE NEWLOG, and the old SCR (out
of the DBECon le) still contains some active transactions. This
can only happen if the database was not shut down in a manner
such that all operations could be properly terminated.
ACTION
Connect to the database and release it. This allows
ALLBASE/SQL to terminate any uncommitted transactions.
Then you can reissue the START DBE NEWLOG statement.
MESSAGE
More than one slot found for the same partition. (DBERR
2813)
CAUSE
The partition was specied twice when opening a log scan.
ACTION
Eliminate the duplication.
MESSAGE
Open_Log_Scan failed on ALL specified partitions. (DBERR
2814)
CAUSE
Check the per partition return codes.
ACTION
Use the per partition return code information to determine your
action.
ALLBASE/SQL Error Messages
2815
2816
2817
2818
2819
MESSAGE
Hard resync record encountered in partition !. Scan
aborted. (DBERR 2815)
CAUSE
The master and slave databases are inconsistent.
ACTION
Resync the indicated partition.
MESSAGE
Open_Log_Scan could not reserve log for partitions found.
(DBERR 2816)
CAUSE
The specied starting point for opening a log scan has been
overwritten.
ACTION
Use a Wrapper DBE to recover the needed log records or hard
resync the partition.
MESSAGE
Invalid audit log record found. (DBERR 2817)
CAUSE
The log record being applied in an Apply Log was not a valid
audit log record.
ACTION
The log records being applied in an Apply Log command must
have come from an Transmit Log from a master instance. Check
your application to make sure that the log records from the
Transmit Log are being passed appropriately to the Apply Log
according to the External Specications.
MESSAGE
Apply_Log cannot find the tuple to be modified/deleted.
(DBERR 2818)
CAUSE
The master and slave databases are not synchronized.
ACTION
Perform a hard resync.
MESSAGE
Attempting to apply a log record while audit is not
enabled. (DBERR 2819)
CAUSE
The architecture of Apply Log requires audit to be turned on at
the slave (target).
ACTION
Use SQLUTIL (SHOWDBE) to check the startup parameters,
and turn audit on (through a START DBE NEWLOG) if
necessary.
ALLBASE/SQL Error Messages
3-161
2820
2821
2822
2823
2824
3-162
MESSAGE
Audit parameters not set. (DBERR 2820)
CAUSE
You tried to use audit logging without setting all of the required
parameters.
ACTION
Check that the AUDIT NAME, DEFAULT PARTITION, and
MAXPARTITIONS are all set in the DBEnvironment, or set
them (through a START DBE NEWLOG) if necessary.
MESSAGE
Active transactions found on partition !. (DBERR 2821)
CAUSE
An attempt is being made to hard resync an active partition.
ACTION
Terminate access to the partition and redo the hard resync.
MESSAGE
Duplicate partition instance found in SCR array. (DBERR
2822)
CAUSE
The duplicate partition instance (PID/DBID) was found in the
SCR array passed to modify SCR.
ACTION
Eliminate the duplicates and try again.
MESSAGE
Open log scan failed due to missing log file (sequence #!).
(DBERR 2823)
CAUSE
A log needed for the log scan being opened has been purged.
ACTION
For a resync application, perform a hard resync. Auditing cannot
be done.
MESSAGE
More than one tuple qualified for key column search.
(DBERR 2824)
CAUSE
Multiple tuples found during Apply Log with key column search
enabled.
ACTION
Try the Apply Log with key column search disabled.
ALLBASE/SQL Error Messages
2825
2826
2827
2828
2829
MESSAGE
Timeout expired (! seconds). (DBERR 2825)
CAUSE
A request for a database resource, such as a lock, could not be
granted before the user timeout was exceeded. The current
transaction was rolled back.
ACTION
Retry the transaction when the requested resource becomes
available, or increase the user timeout value.
MESSAGE
Insufficient number of transactions. (! is required)
(DBERR 2826)
CAUSE
An attempt to start the DBE with the maximum allowable
transactions less than or equal to the number of persistent
transactions currently present in the DBE.
ACTION
Specify a larger number of transactions to start the DBE.
MESSAGE
The function was invoked in an improper context. (DBERR
2827)
CAUSE
An XA function has been invoked in an invalid context.
ACTION
Correct the context and try again.
MESSAGE
Comment is disallowed. (DBERR 2828)
CAUSE
An attempt was made to log a comment for a transaction that is
already persistent.
ACTION
Retry the function without a comment.
MESSAGE
Blocking condition exists. (DBERR 2829)
CAUSE
A transaction join was attempted with the nowait option
specied. The function would have had to wait.
ACTION
Try again later or remove the nowait option.
ALLBASE/SQL Error Messages
3-163
2830
2831
2832
2833
2834
2836
3-164
MESSAGE
Duplicate global transaction identifier. (DBERR 2830)
CAUSE
Attempted to start a transaction with a global identier that
already exists.
ACTION
Try again with a unique GTRID.
MESSAGE
The global transaction identifier is unknown. (DBERR
2831)
CAUSE
The specied global transaction identied does not exist in the
DBE.
ACTION
Check the validity of the GTRID.
MESSAGE
A transaction scan is already opened. (DBERR 2832)
CAUSE
An attempt was made to open a recovery scan when was already
open. A session can have only one open recovery scan.
ACTION
Close the open scan before opening another.
MESSAGE
A transaction scan is not opened. (DBERR 2833)
CAUSE
A recovery scan is required for the requested function, but one is
not open.
ACTION
Open a recovery scan and try again.
MESSAGE
The transaction has already been heuristically committed.
(DBERR 2834)
CAUSE
A request was made to commit or abort a transaction that has
already been heuristically committed.
ACTION
None.
MESSAGE
Timeout. (DBERR 2836)
CAUSE
The requested function has timed out waiting for access to a
transaction.
ACTION
Try again when the transaction is available.
ALLBASE/SQL Error Messages
2837
3228
2881
2882
2884
2885
MESSAGE
The global transaction identifier is invalid. (DBERR
2837)
CAUSE
The specied global transaction id has an invalid format.
ACTION
Check the GTRID.
MESSAGE
Log lock point specified is invalid. (DBERR 3228)
CAUSE
The log location specied for a log lock is invalid.
ACTION
Check the location.
MESSAGE
Cannot drop ! default DBEFileSet !. (DBERR 2881)
CAUSE
You have the space default on the DBEFileSet you tried to drop.
ACTION
Change the space default or modify your command.
MESSAGE
Cannot revoke ! default on DBEFileSet ! from !. (DBERR
2882)
CAUSE
The authority you tried to revoke is a DEFAULT for the user.
ACTION
Change the space default or modify your command.
MESSAGE
User ! does not have explicit ! authority on DBEFileSet !.
(DBERR 2884)
CAUSE
The authority is not previously granted to you.
ACTION
Cannot REVOKE, please modify the command.
MESSAGE
! on DBEFileSet ! is not granted for !. (DBERR 2885)
CAUSE
The authority is not previously granted to you.
ACTION
You must grant the authority to the user before you run the
command.
ALLBASE/SQL Error Messages
3-165
2901
2902
2909
2910
3-166
MESSAGE
Multiple rows returned in subquery. (DBERR 2901)
CAUSE
A subquery within a comparison predicate returns more than one
row. Comparison predicates can only work with single values.
ACTION
For a subquery that returns more than one value, the EXISTS
predicate, IN predicate, or one of the quantied predicates
(SOME, ALL, ANY) must be used.
MESSAGE
Multiple columns returned in subquery. (DBERR 2902)
CAUSE
You specied more than one column in the select list of a
subquery. If an asterisk was specied, there was more than one
column in the table being queried. Only the EXISTS predicate
allows more than one column to be specied in a subquery.
ACTION
Change the subquery so that only one column is specied in the
select list.
MESSAGE
Number of output variables does not match the number of
output dynamic parameters in the referenced section.
(DBERR 2909)
CAUSE
The number of output values in the USING clause of an
EXECUTE or CLOSE statement is not equal to the number of
output dynamic parameters in the prepared statement.
ACTION
Modify either your EXECUTE or CLOSE statement or the
related PREPARE statement so that there is a one to one
mapping of output dynamic parameters.
MESSAGE
Number of input values does not match the number of dynamic
parameters in the referenced section. (DBERR 2910)
CAUSE
The number of input values in the USING clause of an OPEN
or EXECUTE statement is not equal to the number of dynamic
parameters in the prepared statement.
ACTION
Modify either your OPEN or EXECUTE statement or the related
PREPARE statement so that there is a one to one mapping of
dynamic parameters.
ALLBASE/SQL Error Messages
2912
2913
2914
2915
MESSAGE
Incompatible conversion from ! to ! for the dynamic
parameter (!). (DBERR 2912)
CAUSE
The data type of the input value in the USING clause of an
OPEN or EXECUTE statement is not compatible with the
default data type of the dynamic parameter in the prepared
statement.
ACTION
Modify the data type of the referenced input value to be
compatible with the default data type of the corresponding
dynamic parameter.
MESSAGE
Invalid conversion from ! to ! for the dynamic parameter
(!). (DBERR 2913)
CAUSE
You attempted an invalid conversion from one specied type to
another.
ACTION
Refer to the \CAST Function" in the \Expressions" chapter of
the ALLBASE/SQL Reference Manual for the correct conversion
types.
MESSAGE
Invalid conversion from DECIMAL (!,!) to DECIMAL (!,!) for
the dynamic parameter (!). (DBERR 2914)
CAUSE
The value length, precision, or scale of the decimal value you
specied in the USING clause of an OPEN or EXECUTE
statement is greater than that of the data type of the
corresponding dynamic parameter in the prepared statement.
ACTION
Modify the referenced decimal input value to be compatible with
the corresponding dynamic parameter.
MESSAGE
Invalid conversion from !(!) to !(!) for the dynamic
parameter (!). (DBERR 2915)
CAUSE
The length of the input value you referenced in the USING clause
of an OPEN or EXECUTE statement is greater than the length
of the data type of the corresponding dynamic parameter in the
prepared statement.
ACTION
Modify the denition of the referenced input value to be
compatible in length with the corresponding dynamic parameter.
ALLBASE/SQL Error Messages
3-167
2916
2917
2918
2919
2920
3-168
MESSAGE
Invalid Table/View/Column in the dynamic format
computation. (DBERR 2916)
CAUSE
A dynamic parameter is associated with an invalid table, view, or
column in the statement. Its format cannot be determined.
ACTION
Check that the query references existing tables, views, and
columns you are authorized to access and reissue the statement.
MESSAGE
No corresponding column for the dynamic parameter. (DBERR
2917)
CAUSE
A dynamic parameter in the VALUE clause of an INSERT
statement has no corresponding column.
ACTION
Check that the number of columns in the INSERT matches the
number of values specied, and reissue the statement.
MESSAGE
Using Clause is required for the input dynamic parameters.
(DBERR 2918)
CAUSE
You attempted to issue an OPEN or EXECUTE statement on a
section that contains dynamic parameters without passing the
values for the dynamic parameters via the USING clause.
ACTION
Add a USING clause to the statement and provide values for the
dynamic parameters with the USING clause.
MESSAGE
An invalid NLS data was encountered. (DBERR 2919)
CAUSE
NLS data is invalid.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
SQLCORE encountered error from (!) (!). (DBERR 2920)
CAUSE
SQLCORE has an error from the above routine.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
2921
2922
MESSAGE
Integer or float overflow or underflow on operation ADD.
(DBERR 2921)
CAUSE
The result of an addition operation with INTEGER or FLOAT
operands is either too big or too small for the hardware to
accommodate.
ACTION
Modify the expression to yield a result within the limits for the
data type.
MESSAGE
PUBLICROW is not allowed on a hash table. (DBERR 2922)
CAUSE
You are trying to dene a hash on a PUBLICROW table, and
this combination is not supported.
or
You are trying to alter a hash table to type PUBLICROW, but
this combination is not supported
3001
ACTION
Either use a table type of PUBLIC as you dene the hash
structure, or else convert to a non-hash PUBLICROW table by
dropping and recreating the table.
MESSAGE
Invalid ALLBASE/SQL request block. (DBERR 3001)
CAUSE
Internal error. The ALLBASE/SQL request block has an invalid
brand name in its rst eld. This could be caused by an invalid
request block pointer.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
3-169
3002
MESSAGE
Invalid parameter-buffer flag in ALLBASE/SQL request
block. (DBERR 3002)
CAUSE
Internal error. The ALLBASE/SQL request block (JRB) has
an invalid value for input parameter buer ag. There is a
discrepancy between a module in the program and the stored
module.
ACTION
If you moved a modied program to your DBEnvironment you
must drop the old module and reinstall a new module,
or
don't use ISQL to execute a module created with a preprocessor
or
record as much information as possible and contact your HP
service representative or Response Center.
3003
3004
3005
3-170
MESSAGE
Invalid parameter-buffer address in ALLBASE/SQL request
block. (DBERR 3003)
CAUSE
Internal error. The ALLBASE/SQL request block (JRB) has an
invalid pointer pointing to a parameter buer.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Invalid parameter-buffer length in ALLBASE/SQL request
block. (DBERR 3004)
CAUSE
Internal error. ALLBASE/SQL request block (JRB) has an
invalid parameter buer length.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Invalid data-buffer flag in ALLBASE/SQL request block.
(DBERR 3005)
CAUSE
Internal error. ALLBASE/SQL request block (JRB) has an
invalid data-buer ag.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
3006
MESSAGE
Invalid data-buffer address in ALLBASE/SQL request block.
(DBERR 3006)
CAUSE
The SQLRowBuf was set to an invalid address for a dynamic
query
or
an internal error occurred.
ACTION
Correct the SQLRowBuf and re-preprocess your program
or
record as much information as possible and contact your HP
Service Representative or Response Center.
3007
MESSAGE
Invalid data-buffer length in ALLBASE/SQL request block.
(DBERR 3007)
CAUSE
SQLBufLen was set to an invalid length for a dynamic query
or
an internal error occurred.
ACTION
Correct the SQLBufLen and re-preprocess your program
or
record as much information as possible and contact your HP
Service Representative or Response Center.
3008
MESSAGE
Invalid number of rows requested in ALLBASE/SQL request
block. (DBERR 3008)
CAUSE
SQLNRows was set to an invalid number for a dynamic query
or
an internal error occurred.
ACTION
Correct SQLNRows and re-preprocess your program
or
record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
3-171
3024
3025
3026
3040
3041
3-172
MESSAGE
Column number ! in node ! out of range. (DBERR 3024)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
service representative or Response Center.
MESSAGE
Null length of ! for value ! is invalid. (DBERR 3025)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Unsupported data format of type ! length !. (DBERR 3026)
CAUSE
Internal error. ALLBASE/SQL detected an unsupported data
type or invalid data length.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Command rejected - DBCore was terminated. (DBERR 3040)
CAUSE
Your database administrator issued a STOP DBE statement
causing your transaction to be terminated.
ACTION
Contact your database administrator to nd out when the
DBEnvironment will be available.
MESSAGE
Command rejected - DBCore is terminating now. (DBERR
3041)
CAUSE
Your database administrator issued a STOP DBE statement
causing the DBEnvironment to shut down.
ACTION
Contact your database administrator to nd out when the
DBEnvironment will be available.
ALLBASE/SQL Error Messages
3042
3043
3047
3050
MESSAGE
Command rejected - User session was terminated. (DBERR
3042)
CAUSE
Your database administrator or another user connected to the
DBEnvironment using your login name issued a TERMINATE
USER statement for your login name. Any active transactions for
your login name were terminated.
ACTION
Contact the person who issued the TERMINATE USER
statement and reconnect to the DBEnvironment.
MESSAGE
Command rejected - User session is terminating now. (DBERR
3043)
CAUSE
Your database administrator or another user connected to the
DBEnvironment issued a TERMINATE USER statement for your
login name. Any active transactions for your login name were
terminated.
ACTION
Contact the person who issued the TERMINATE USER
statement and reconnect to the DBEnvironment.
MESSAGE
Number of query sections exceeds system limit !. (DBERR
3047)
CAUSE
The number of PREPARE commands exceeded system limit per
session.
ACTION
Keep the number of PREPARE commands within the limit.
MESSAGE
File System Error - Privileged file violation. (DBERR
3050)
CAUSE
The ownership or le mode of a database or log le, or the
directory that contains the le, is incorrect.
ACTION
Check that user hpdb (uid 27) has at least read and write
permission to the directories that contain the database and log
les. Check that all database and log les are owned by hpdb,
and have a le mode of 600 (- r w - - - - - - -). If necessary,
contact your system administrator.
ALLBASE/SQL Error Messages
3-173
3051
3054
3059
3060
3061
3-174
MESSAGE
File System Error - Not enough space in device. (DBERR
3051)
CAUSE
There is not enough space in the device to support your
operation.
ACTION
Use a dierent device or contact your database administrator to
add more space to the current device.
MESSAGE
File System Error - Nonexistent DBEFile or log file.
(DBERR 3054)
CAUSE
You attempted to access a DBEFile or log le which is missing.
ACTION
Use the SQLUtil SHOWDBE command and/or SELECT
information from SYSTEM.DBEFILE to nd out the names of
DBEFile0, DBELog and other DBEFiles. Make sure they co-exist
with your DBECon le.
MESSAGE
File System Error - Security violation. (DBERR 3059)
CAUSE
The ownership or le mode of the DBEFile or executable
program les (SQLUtil or hpsqlproc) is incorrect. (hpsqlproc is a
process invoked whenever ISQL, the preprocessors, or application
programs are executed.)
ACTION
Refer to the ALLBASE/SQL Database Administration Guide for
additional information.
MESSAGE
File System Error - File already exists or file does not
have the permission expected by ALLBASE/SQL. (DBERR 3060)
CAUSE
The le name you specied in the CREATE DBEFILE statement
already exists, or the le does not have the permissions expected
by ALLBASE/SQL.
ACTION
If you are using HP-UX raw les for DBEFiles and logs, you must
set the permissions to mode 0600 for the raw le. Any other
mode will cause this error.
MESSAGE
File System Error - ! (!). (DBERR 3061)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the system administration manual.
ALLBASE/SQL Error Messages
3062
3063
3064
3065
MESSAGE
Location already used for another Tempspace. (DBERR 3062)
CAUSE
The physical location you specied by the CREATE
TEMPSPACE statement is already being used for another
tempspace.
ACTION
Issue the CREATE TEMPSPACE statement again with a
dierent physical location. Or, execute the DROP TEMPSPACE
statement to remove the original tempspace from the physical
location, and issue the CREATE TEMPSPACE statement again.
MESSAGE
DBECon Error - Cannot use CONNECT command with autostart
off. (DBERR 3063)
CAUSE
You tried to initiate a single-user session with the CONNECT
statement and the autostart ag is OFF.
ACTION
Either use the START DBE statement to initiate the session or
ask your database administrator to change the autostart ag to
ON.
MESSAGE
DBECon Error - This DBEnvironment does not have !. (DBERR
3064)
CAUSE
You tried to CONNECT to a DBEnvironment which is not an
ALLBASE/SQL DBEnvironment.
ACTION
No action is necessary. You can only CONNECT to an
ALLBASE/SQL DBEnvironment.
MESSAGE
DBECon Error - User attempted NEWLOG and is not creator of
DBECon file. (DBERR 3065)
CAUSE
You attempted to execute the START DBE NEWLOG statement
and you are not the creator of the specied DBEnvironment.
ACTION
Contact your database administrator to nd out who the
DBECreator is and have the DBECreator issue the appropriate
command.
ALLBASE/SQL Error Messages
3-175
3066
3068
3071
3076
3-176
MESSAGE
DBECon Error - File is invalid. (DBERR 3066)
CAUSE
The le specied is not a DBECon le.
ACTION
Check your spelling. Issue the command again, specifying a valid
DBECon le.
MESSAGE
DBECon Error - Not enough space in device. (DBERR 3068)
CAUSE
There is not enough space in the device to support your
operation.
ACTION
Use a dierent device or contact your database administrator to
add more space to the current device.
MESSAGE
DBECon Error - Nonexistent file name. (DBERR 3071)
CAUSE
You specied a non-existent le name on the local node in the
START DBE or CONNECT statement. This message may be
the rst of two messages received. ALLBASE/SQL attempted a
remote connection but was unsuccessful.
ACTION
If your CONNECT statement is for a DBEnvironment on the
local node, check your spelling. If you still receive this error, use
the HP-UX ls command to make sure that the le really exists in
your current working directory. If your CONNECT statement is
for a remote DBEnvironment, read the second message for further
action to be taken.
MESSAGE
DBECon Error - Security violation. (DBERR 3076)
CAUSE
The ownership or le mode of the DBECon le or the directory
that contains the DBECon le is incorrect.
ACTION
Check that user hpdb (uid 27) has at least read and write
permission to the directory that contains the DBECon le.
Check that the DBECon les is owned by hpdb, and has a
le mode of 600 (- r w - - - - - - -). If necessary, contact your
system administrator. Refer to the ALLBASE/SQL Database
Administration Guide for additional information.
ALLBASE/SQL Error Messages
3077
3078
3079
MESSAGE
DBECon Error - File already exists. (DBERR 3077)
CAUSE
The le name you specied already exists.
ACTION
Issue the command again, specifying a unique le name.
MESSAGE
DBECon Error - (! !). (DBERR 3078)
CAUSE
An HP-UX le system error occurred on the DBECon le.
ACTION
Refer to the system administration manual.
MESSAGE
DBECon error - Permission denied. (DBERR 3079)
CAUSE
The DBECon le is inaccessible because: the owner or access
mode of the DBECon le have been changed (the owner should
be 'hpdb', and the access mode should be 600)
or
the owner or access mode of the database process
/usr/lib/hpsqlproc have been changed (the owner should be
'hpdb', and the access mode should be 4555).
ACTION
Use the chmod and/or chown commands to restore the correct
owner and access mode to the DBECon le.
or
Contact your system administrator.
3080
MESSAGE
DBECon error - Attempted a MULTI user session on a SINGLE
user DBEnvironment. (DBERR 3080)
CAUSE
You tried to initiate a multi-user session on a single user
DBEnvironment
or
your database administrator has started the DBEnvironment in
single-user mode in order to make changes through SQLUtil.
ACTION
Ask your database administrator to change the DBECon le user
mode to MULTI
or
ask your database administrator to notify you when the
DBEnvironment is again accessible in multi-user mode.
ALLBASE/SQL Error Messages
3-177
3086
3087
3088
3100
3-178
MESSAGE
DBECon Error - File is NFS mounted. (DBERR 3086)
CAUSE
You attempted to create or access a DBEnvironment on an NFS
mounted disk.
ACTION
To create the DBEnvironment, log onto the server where the
DBEnvironment will reside. Install ALLBASE/NET to access the
remote DBEnvironment.
MESSAGE
DBECon Error - File mounted on another node in the cluster.
(DBERR 3087)
CAUSE
You attempted to create or access a DBEnvironment on a disk in
the cluster that is not mounted locally.
ACTION
To create the DBEnvironment, log onto the system on which the
disk is mounted locally. Install ALLBASE/NET to access the
remote DBEnvironment.
MESSAGE
MOVEFILE cannot be used to move DBECon. (DBERR 3088)
CAUSE
You tried to move the DBECon le using the MOVEFILE
statement.
ACTION
The DBECon le stores the start up parameters for the
DBEnvironment dened by the START DBE NEW statement
and must remain in the same location as the DBEnvironment.
MESSAGE
COMMIT ARCHIVE attempt was not preceded by a successful
BEGIN ARCHIVE. (DBERR 3100)
CAUSE
Some user has already got a BEGIN ARCHIVE in progress, and
some other user attempts to COMMIT ARCHIVE. This is illegal.
ACTION
Refrain from performing a COMMIT ARCHIVE if you were not
the one to have a BEGIN ARCHIVE in the rst place.
ALLBASE/SQL Error Messages
3101
3102
3103
3106
MESSAGE
START DBE NEWLOG disallowed. Need rollforward recovery.
(DBERR 3101)
CAUSE
You are most probably trying a START DBE NEWLOG on a
DBEnvironment that has incomplete transactions in its log. The
only operations permitted are START DBE or CONNECT (if
AutoStart is enabled); either of these will roll back incomplete
transactions and force completed transactions to disk.
ACTION
First, issue a START DBE statement or a CONNECT (if
AutoStart is enabled). Next, stop the DBEnvironment. Finally,
attempt the START DBE NEWLOG again.
MESSAGE
START DBE disallowed. Need rollforward recovery. (DBERR
3102)
CAUSE
The DBEnvironment is still in a fuzzy state. Either you are
attempting a START DBE or START DBE NEWLOG on a
restored version of an online backup of the DBEnvironment, OR
you have performed some but not all the necessary rollforward
recovery on this DBEnvironment.
ACTION
Check the previous rollforward steps if any. Perform as many
RECOVERLOG steps with as many logs as necessary to reach
the matching COMMIT ARCHIVE point in the log le.
MESSAGE
There are no more logs to switch to. (DBERR 3103)
CAUSE
This is dierent from a log full condition. Essentially, if the user
attempts to overwrite an archive checkpoint, DBCore will rst try
to switch to the next log. If this operation fails, the above error is
generated.
ACTION
Check to see if indeed an attempt was made to overwrite an
existing archive checkpoint. If the need is genuine, use the
ADDLOG command in SQLUtil to add one or more new logs.
MESSAGE
START DBE disallowed: DBEnvironment points to a wrong log
file. (DBERR 3106)
CAUSE
You did not follow your static restore of a DBEnvironment with
the NEWLOG command.
ACTION
Restore DBEnvironment again and perform a NEWLOG
command.
ALLBASE/SQL Error Messages
3-179
3200
3201
3204
3205
3206
3207
3-180
MESSAGE
Invalid LONG column I/O syntax. (DBERR 3200)
CAUSE
You specied a long column input or output target which is not
correct.
ACTION
Check the > or < I/O redirection syntax.
MESSAGE
Invalid LONG column file name. (DBERR 3201)
CAUSE
The le name is incorrect.
ACTION
Refer to A Beginner's Guide to HP-UX for le naming
conventions.
MESSAGE
LONG column file path length too long. ! maximum. (DBERR
3204)
CAUSE
The pathname exceeds the maximum length allowed.
ACTION
Shorten the pathname.
MESSAGE
LONG column file access error in module !(!), status code
!. (DBERR 3205)
CAUSE
There is a problem with the le used as the input or output
device in a LONG column operation. Either the le does not
exist, cannot be read, or cannot be written to.
ACTION
Ensure that the le exists and has the appropriate permissions.
MESSAGE
LONG column file already exists. (DBERR 3206)
CAUSE
The output le exists but the OVERWRITE option was not
specied.
ACTION
Remove the le or add the OVERWRITE option.
MESSAGE
LONG column shared memory failed. (DBERR 3207)
CAUSE
The shared memory id cannot be attached. The shared memory
id may be missing or is incorrect.
ACTION
Verify that you are using the correct shared memory id. Use the
ipcs command to double-check the allocated shared memory.
ALLBASE/SQL Error Messages
3208
3210
3211
3220
3221
3222
MESSAGE
LONG columns exceed maximum 40 columns. (DBERR 3208)
CAUSE
You entered more than 40 LONG columns.
ACTION
Reduce the number of LONG columns.
MESSAGE
Negative length value not allowed for LONG column INSERT.
(DBERR 3210)
CAUSE
You specied a negative value for the length of the long value to
be read from the shared memory.
ACTION
Remove the unary minus sign from the length specication and
reissue the statement.
MESSAGE
Length specified is greater than allowed. (DBERR 3211)
CAUSE
The length of the long value to be read from the shared memory
is too large.
ACTION
Specify a shorter length for the shared memory and reissue the
statement.
MESSAGE
LONG column disallowed from remote access. (DBERR 3220)
CAUSE
You tried to access a long column on another machine.
ACTION
This feature is not supported yet.
MESSAGE
LONG column disallowed on ORDER BY/DISTINCT/UNION.
(DBERR 3221)
CAUSE
You tried to use an ORDER BY, DISTINCT or UNION on a
column dened as a long data type.
ACTION
Remove the long column from ORDER BY, DISTINCT or
UNION clause.
MESSAGE
LONG column disallowed on GROUP BY. (DBERR 3222)
CAUSE
You tried to use the GROUP BY clause with a column dened as
a long data type.
ACTION
Remove the long column from the GROUP BY clause.
ALLBASE/SQL Error Messages
3-181
3223
3224
3225
3226
3227
3228
3-182
MESSAGE
LONG column disallowed on Expression. (DBERR 3223)
CAUSE
You tried to use an expression with a column that has been
dened as a long data type.
ACTION
Remove the long column from the expression.
MESSAGE
LONG column disallowed on INDEX. (DBERR 3224)
CAUSE
You tried to create an index on a column dened as a long data
type.
ACTION
Remove the long column from the column list in the CREATE
INDEX statement.
MESSAGE
LONG column disallowed on HASH. (DBERR 3225)
CAUSE
You tried to specify a hash structure on a column that has been
dened as a long data type.
ACTION
Remove the UNIQUE HASH clause from the CREATE TABLE
syntax, or the long column from the UNIQUE HASH clause.
MESSAGE
LONG column disallowed on INSERT from SELECT. (DBERR 3226)
CAUSE
You tried to insert a column dened as a long data type in a type
II INSERT statement.
ACTION
Remove the long column from the SELECT clause in the
INSERT statement.
MESSAGE
Long fields cannot be replicated. (DBERR 3227)
CAUSE
You attempted to replicate a long data type eld.
ACTION
Remove the long column from the replicate statement.
MESSAGE
Log lock point specified is invalid. (DBERR 3228)
CAUSE
An invalid log lock point was specied.
ACTION
Change to a valid log lock point.
ALLBASE/SQL Error Messages
3241
3242
3244
3245
3248
3300
MESSAGE
Invalid node type ! not allowed inside atomic block.
(DBERR 3241)
CAUSE
The specied node type is not valid inside an atomic block.
ACTION
Change to a valid node type.
MESSAGE
Atomic block does not exist while requesting end atomic
operation. (DBERR 3242)
CAUSE
There is an end for an atomic operation without it being started.
ACTION
Correct the atomic block commands.
MESSAGE
Execution failed causing rollback work inside atomic
block. (DBERR 3244)
CAUSE
The execution failed within an atomic block.
ACTION
Review the commands within the atomic block and correct the
problem.
MESSAGE
Atomic block started already. Nested atomic block is not
allowed. (DBERR 3245)
CAUSE
You have specied a nested atomic block.
ACTION
Remove the nested atomic block.
MESSAGE
Incorrect data type declared for input/output parameter.
(DBERR 3248)
CAUSE
The input or output parameter has an incorrect data type.
ACTION
Change to the correct data type.
MESSAGE
DBEFile ! is currently DETACH-ed. (DBERR 3300)
CAUSE
You attempted to DETACH an already DETACHed DBEFile.
ACTION
None.
ALLBASE/SQL Error Messages
3-183
3301
3302
3303
3304
3305
3-184
MESSAGE
Attempting to ATTACH an already attached DBEFile !. (DBERR
3301)
CAUSE
You attempted to ATTACH an already ATTACHed DBEFile.
ACTION
None.
MESSAGE
Cannot DETACH the SYSTEM DBEFileset or any DBEFile in it.
(DBERR 3302)
CAUSE
You attempted to DETACH a SYSTEM DBEFileset or a
DBEFile in the SYSTEM DBEFileset.
ACTION
If the reason for DETACHment is media failure, perform a
complete rollforward recovery.
MESSAGE
DBEFileset ! is currently DETACH-ed. (DBERR 3303)
CAUSE
You attempted to DETACH an already DETACHed DBEFileset.
ACTION
None.
MESSAGE
Attempting to ATTACH an already attached DBEFileset !.
(DBERR 3304)
CAUSE
You attempted to ATTACH an already ATTACHed DBEFileset.
ACTION
None.
MESSAGE
Cannot DROP DBEFile ! while online backup is in progress.
(DBERR 3305)
CAUSE
You attempted to DROP a DBEFile after the online backup has
started, but before it has nished.
ACTION
Wait until the online backup completes and resubmit the
command.
ALLBASE/SQL Error Messages
3306
3307
3308
3309
3310
3311
MESSAGE
Attempting to access DBEFile ! which is currently
DETACH-ed.(DBERR 3306)
CAUSE
You attempted to read/write data from a detached DBEFile.
ACTION
ATTACH a DBEFile (partial or full rollforward recovery may be
needed before ATTACHing), and restart the transaction.
MESSAGE
Cannot partially rollforward the SYSTEM DBEFileset or any
DBEFile in it. (DBERR 3307)
CAUSE
You attempted to perform a partial rollforward on the
SYSTEM.DBEFileSet or a DBEFile in the SYSTEM DBEFileSet.
ACTION
Perform a complete rollforward recovery.
MESSAGE
OMNIBACK error !. (DBERR 3308)
CAUSE
OMNIBACK has encountered some problem trying to
store/restore DBEnvironment le(s).
ACTION
Please refer to the OMNIBACK manual.
MESSAGE
DBECreator ! does not exist on the system. (DBERR 3309)
CAUSE
The DBECreator named does not exist on the system.
ACTION
Use a correct DBECreator name for this system.
MESSAGE
Cannot specify pseudo-mapped access for DBECon or
DBEFile0. (DBERR 3310)
CAUSE
Pseudo-mapped was specied for DBECon or DBEFile0. They
cannot be pseudo-mapped.
ACTION
Remove pseudo-mapping from the DBECon or DBEFile0 le.
MESSAGE
Command disallowed: user not DBECreator or does not have
maintenance word. (DBERR 3311)
CAUSE
You are not the creator of the DBEnvironment, or the
maintenance word was not supplied.
ACTION
Log on as DBECreator, or supply the maintenance word.
ALLBASE/SQL Error Messages
3-185
3500
3501
3550
3551
3552
3-186
MESSAGE
Maximum IMAGESQL DBEFILESET can not exceed ! pages. (DBERR
3500)
CAUSE
You attempted to add a DBEFile to IMAGESQL DBEFileSet
which would cause the DBEFileSet to exceed its maximum size.
ACTION
Add a DBEFile which does not violate the maximum number of
pages with IMAGESQL DBEFileSet.
MESSAGE
Grant TABLESPACE on ! DBEFILESET is not allowed. (DBERR
3501)
CAUSE
You attempted to modify default table space. This command is
not allowed for users without ALLBASE/SQL license.
ACTION
No action.
MESSAGE
!.!(!) is not a permanent section or it is a procedure.
(DBERR 3550)
CAUSE
You attempted to EXTRACT a section which is not a permanent
section, or it is a procedure.
ACTION
EXTRACT a section which is a permanent section and it is not a
procedure.
MESSAGE
TBL of ! is needed to EXTRACT !.!(!). (DBERR 3551)
CAUSE
The tuple buer length is too small for the linear tree.
ACTION
EXTRACT the section with larger buer.
MESSAGE
Section !.!(!) is a view. (DBERR 3552)
CAUSE
The specied section is a view. Views can not be extracted.
ACTION
No action.
ALLBASE/SQL Error Messages
4000
4001
4002
4003
4004
MESSAGE
ALLBASE/SQL code buffer overflow at !. Query aborted.
(DBERR 4000)
CAUSE
ALLBASE/SQL internal code buer overow. Input command
was too long or too complicated.
ACTION
Try to simplify the input command.
MESSAGE
ALLBASE/SQL static buffer overflow at !. Query aborted.
(DBERR 4001)
CAUSE
ALLBASE/SQL internal static buer overow. Input command
was too long or too complicated.
ACTION
Try to simplify the input command.
MESSAGE
ALLBASE/SQL module buffer overflow at !. Query aborted.
(DBERR 4002)
CAUSE
ALLBASE/SQL internal module buer overow. The executable
tree for the module was too long.
ACTION
Try to simplify the input command by breaking up your large
query into multiple queries.
MESSAGE
ALLBASE/SQL max query buffers exceeded. Query aborted.
(DBERR 4003)
CAUSE
ALLBASE/SQL internal query buer overow. Input command
was too long or too complicated.
ACTION
Try to simplify the input command. Refer to base tables instead
of to views as much as possible.
MESSAGE
ALLBASE/SQL input heap overflow at ! - Query aborted.
(DBERR 4004)
CAUSE
ALLBASE/SQL internal input heap overow. Input command
was too long or too complicated.
ACTION
Try to simplify the input command. Reduce the amount of table
and column qualications as much as possible. If necessary,
record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
3-187
4005
4006
4007
3-188
MESSAGE
ALLBASE/SQL memory allocation failed. (DBERR 4005)
CAUSE
ALLBASE/SQL cannot allocate run-time memory. This may
be an internal ALLBASE/SQL problem or an operating system
problem.
ACTION
The requested operation cannot be performed. Try starting
the database later, issuing the problem operation earlier in the
session. Report this problem to your database administrator and
system administrator.
MESSAGE
ALLBASE/SQL memory deallocation failed. (DBERR 4006)
CAUSE
ALLBASE/SQL cannot deallocate (return for re-use) run-time
memory. This may be an internal ALLBASE/SQL or an
operating system problem.
ACTION
After this error occurs, you may continue normal processing. The
problem becomes a serious one when a long session eventually
uses up all space and can not obtain any more space. Report
this problem to your database administrator and system
administrator.
MESSAGE
ALLBASE/SQL UPDATE STATISTICS ! mismatch with DBCore.
(DBERR 4007)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
4008
MESSAGE
ALLBASE/SQL shared memory lock allocation failed in
DBCore. (DBERR 4008)
CAUSE
ALLBASE/SQL ran out of run-time control block space. Your
transaction was rolled back.
ACTION
In multi-user mode, try your query again later
or
issue the ALTDBE command in SQLUtil to increase the number
of control block pages
or
use LOCK TABLE so that individual pages are not locked
or
you may be able to use BEGIN WORK CS or BEGIN WORK
RU to prevent this error.
4009
MESSAGE
ALLBASE/SQL shared memory allocation failed in DBCore.
(DBERR 4009)
CAUSE
ALLBASE/SQL ran out of run-time control block space. Your
transaction was rolled back.
ACTION
In multi-user mode, try your query again later
or
issue the ALTDBE command in SQLUtil to increase the number
of control block pages
or
use LOCK TABLE so that individual pages are not locked
or
you may be able to use BEGIN WORK CS or BEGIN WORK
RU to prevent this error.
4010
MESSAGE
ALLBASE/SQL lock limit for session exceeded. (DBERR 4010)
CAUSE
The total number of locks currently in place for your user session
is at the limit specied in the hpsqldebug environment variable.
ACTION
Either delete the environment variable or else set it to a higher
value.
ALLBASE/SQL Error Messages
3-189
4012
4013
4050
4051
4053
3-190
MESSAGE
ALLBASE/SQL pseudocode error. (DBERR 4012)
CAUSE
Internal error. ALLBASE/SQL opcode is invalid.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
ALLBASE/SQL tmp buffer overflow at !. Query aborted.
(DBERR 4013)
CAUSE
A temporary, internal SQL buer overowed.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
ALLBASE/SQL internal error at !(!) (Node ! out of
context). (DBERR 4050)
CAUSE
Internal error. The node in question is not a valid one in current
context.
ACTION
If you have performed a backward migration, the view or stored
section that you are accessing needs to be dropped and recreated
under the current release. If you continue to see this message,
record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
ALLBASE/SQL internal error at ! (! ). (DBERR 4051)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
ALLBASE/SQL internal error (! !). (DBERR 4053)
CAUSE
Internal error, possibly caused by the incorrect handling of
installed sections after database migration.
ACTION
Re-preprocess the application and install the new module into the
migrated database.
ALLBASE/SQL Error Messages
4054
4059
4101
4102
4103
4104
MESSAGE
ALLBASE/SQL internal error (! !). (DBERR 4054)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
ALLBASE/SQL internal error (!,!,!,!,!). (DBERR 4059)
CAUSE
Internal error.
ACTION
Record the le system error code returned and as much
information as possible. Contact your HP Service Representative
or Response Center.
MESSAGE
ALLBASE/SQL shared memory allocation failed. (! !).
(DBERR 4101)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the system administration manual.
MESSAGE
ALLBASE/SQL unable to fork. (! !). (DBERR 4102)
CAUSE
An HP-UX error occurred.
ACTION
Refer to the system administration manual.
MESSAGE
ALLBASE/SQL unable to execute hpsqlproc. (! !). (DBERR
4103)
CAUSE
An HP-UX le system error occurred or you do not have
hpsqlproc on the client node.
ACTION
Refer to the system administration manual, reinstall
ALLBASE/SQL if local access is desired, or use NETUtil to
congure an AliasDB le for ALLBASE/NET remote access.
MESSAGE
ALLBASE/SQL shared memory attachment failed. (! !).
(DBERR 4104)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the system administration manual.
ALLBASE/SQL Error Messages
3-191
4105
4111
4112
4118
4121
3-192
MESSAGE
hpsqlproc process terminated prematurely. (DBERR 4105)
CAUSE
The process, hpsqlproc, has been terminated prematurely.
(hpsqlproc is a process invoked whenever ISQL, the preprocessors,
or application programs are executed.)
ACTION
Issue your command or run your program again. If this problem
persists, record as much information as possible and contact your
HP Service Representative or Response Center.
MESSAGE
Cannot get ALLBASE/SQL system pointer. (DBERR 4111)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Cannot set ALLBASE/SQL system pointer. (DBERR 4112)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Invalid JRB version is found. (DBERR 4118)
CAUSE
The application being run is linked to a newer version of
ALLBASE than what is currently installed on your system.
ACTION
The application needs to be relinked with the current version
which is currently installed on your system, or a version of
ALLBASE consistent with the application needs to be installed
on your system. Contact your system administrator.
MESSAGE
hpsqlproc shared memory attachment failed. (! !). (DBERR
4121)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the system administration manual.
ALLBASE/SQL Error Messages
4122
4127
4128
4130
4131
MESSAGE
hpsqlproc detected premature termination of application.
(DBERR 4122)
CAUSE
ISQL, the preprocessor, or an application program terminated
prematurely causing hpsqlproc to terminate. (hpsqlproc is
a process invoked whenever ISQL, the preprocessors, or an
application program is executed.)
ACTION
If you were running an application program, check for a
programming error. If it was not a programming error, record
as much information as possible and contact your HP Service
Representative or Response Center.
MESSAGE
Back-end data segment increment failed. (! !). (DBERR
4127)
CAUSE
An HP-UX error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Back-end data segment decrement failed. (! !). (DBERR
4128)
CAUSE
An HP-UX error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
ALLBASE/SQL internal error. (! !) (DBERR 4130)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
ALLBASE/SQL internal error. (! !) (DBERR 4131)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
3-193
4132
4133
4134
4150
4170
3-194
MESSAGE
ALLBASE/SQL internal error. (! !) (DBERR 4132)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
ALLBASE/SQL internal error. (! !) (DBERR 4133)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
ALLBASE/SQL internal error. (! !) (DBERR 4134)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
ALLBASE/SQL already started. (! !) (DBERR 4150)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
hpsqlproc unable to get a semaphore. (HP-UX errno !)
(DBERR 4170)
CAUSE
The system limit on semaphores may have been reached.
ACTION
Increase the values of the semmni and semmns system
parameters. If the problem persists, refer to the
/usr/include/sys/errno.h le for an error description, record
as much information as possible, and contact your HP Service
Representative or Response Center.
ALLBASE/SQL Error Messages
4171
4172
4173
4174
4175
MESSAGE
ALLBASE/SQL unable to post a semaphore. (HP-UX errno !)
(DBERR 4171)
CAUSE
An HP-UX error occurred.
ACTION
Refer to /usr/include/sys/errno.h le for an error description.
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
hpsqlproc failed while waiting on a semaphore. (HP-UX
errno !) (DBERR 4172)
CAUSE
An HP-UX error occurred.
ACTION
Refer to /usr/include/sys/errno.h le for an error description.
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
hpsqlproc failed to get attributes of a semaphore. (HP-UX
errno !) (DBERR 4173)
CAUSE
An HP-UX error occurred.
ACTION
Refer to /usr/include/sys/errno.h le for an error description.
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
hpsqlproc failed to set attributes of a semaphore. (HP-UX
errno !) (DBERR 4174)
CAUSE
An HP-UX error occurred.
ACTION
Refer to /usr/include/sys/errno.h le for an error description.
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Multi-connect not supported using signal IPC. (DBERR
4175)
CAUSE
The front-end and back-end processes are communicating with
signals, but multi CONNECT requires a fastipc environment.
Fastipc is supported on HP-UX 7.08 and later.
ACTION
Update HP-UX to a version that supports fastipc.
ALLBASE/SQL Error Messages
3-195
4200
8101
8102
8103
8111
3-196
MESSAGE
ALLBASE/SQL alignment error on column ! in buffer !.
(DBERR 4200)
CAUSE
The formatting information on host variables was generated
incorrectly.
ACTION
Check the format node information in your application program.
If the problem was not caused by a programming error, record
as much information as possible and contact your HP Service
Representative or Response Center.
MESSAGE
Unrecognized command. (DBERR 8101)
CAUSE
The command name you entered does not exist or was entered
incorrectly.
ACTION
Use the SQLUtil HELP command or refer to the ALLBASE/SQL
Database Administration Guide to obtain a list and description of
valid SQLUtil commands.
MESSAGE
Command not yet implemented. (DBERR 8102)
CAUSE
The command name you entered does not exist or was entered
incorrectly.
ACTION
Use the SQLUtil HELP command or refer to the ALLBASE/SQL
Database Administration Guide to obtain a list and description of
valid SQLUtil commands.
MESSAGE
File '!' not found. (DBERR 8103)
CAUSE
The le name specied in the MOVEFILE or PURGEFILE
command was entered incorrectly or does not exist.
ACTION
Check your spelling. Use the HP-UX ls command to verify the
existence of the specied le.
MESSAGE
Re-typed maintenance word doesn't match.
word not changed. (DBERR 8111)
CAUSE
The maintenance word was not changed because SQLUtil was
unsure what the new maintenance word should be.
ACTION
Issue the SETDBEMAINT command.
ALLBASE/SQL Error Messages
Maintenance
8115
8116
8118
8131
8132
8133
MESSAGE
Value must be in the range !..!. (DBERR 8115)
CAUSE
The value specied for one or more parameters of the ALTDBE is
invalid.
ACTION
Issue the ALTDBE command again, specifying valid numbers for
following parameters: Number of Runtime Control Block Pages
should be 17 to 128 pages; Number of Data Buer Pages should a
minimum of 15; Number of Log Buer Pages should be 24 to 120
pages; and Max. Transactions should be 2 to 240 transactions.
MESSAGE
Bad numeric input. (DBERR 8116)
CAUSE
You entered non-numeric input where numeric input was
expected.
ACTION
Issue the ALTDBE command again, specifying valid numbers.
MESSAGE
Cannot open file. (! !). (DBERR 8118)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the system administration manual.
MESSAGE
File '!' is not a DBEFile. (DBERR 8131)
CAUSE
The specied le is not a DBEFile.
ACTION
Issue the command again, specifying a valid DBEFile.
MESSAGE
File '!' not accessible. (! !). (DBERR 8132)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the system administration manual.
MESSAGE
Internal error occurred. (! !). (DBERR 8133)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the system administration manual.
ALLBASE/SQL Error Messages
3-197
8201
8202
8203
8204
8205
8206
3-198
MESSAGE
Open failed on DBECon file. (! !). (DBERR 8201)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le.
MESSAGE
Close failed on DBECon file. (! !). (DBERR 8202)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le.
MESSAGE
Read failed on DBECon file. (! !). (DBERR 8203)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le.
MESSAGE
Write failed on DBECon file. (! !). (DBERR 8204)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le.
MESSAGE
STORE failed. (! !). (DBERR 8205)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le.
MESSAGE
RESTORE failed. (! !). (DBERR 8206)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le.
ALLBASE/SQL Error Messages
8207
8208
8209
8210
8211
8212
MESSAGE
Operation not performed; illegal capability. (DBERR
8207)
CAUSE
You do not have the capability to perform the specied
command.
ACTION
Contact a user who has the required capability. Refer to the
ALLBASE/SQL Database Administration Guide for additional
information on SQLUtil.
MESSAGE
Invalid DBECon file. (DBERR 8208)
CAUSE
The le you specied in the ALTDBE, MOVEFILE, or
PURGEDBE command is not a DBECon le.
ACTION
Check your spelling. Issue the command again, specifying a valid
DBECon le.
MESSAGE
GETINFO failed. (! !). (DBERR 8209)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le.
MESSAGE
Open failed on a DBEFile. (! !). (DBERR 8210)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le.
MESSAGE
Close failed on a DBEFile. (! !) (DBERR 8211)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le.
MESSAGE
Read failed on a DBEFile. (! !) (DBERR 8212)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le.
ALLBASE/SQL Error Messages
3-199
8213
8214
8215
8216
8217
8219
3-200
MESSAGE
Write failed on a DBEFile. (! !) (DBERR 8213)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le.
MESSAGE
Unable to access System Catalog due to error #!. (DBERR
8214)
CAUSE
You cannot access the System Catalog due to another error.
ACTION
Refer to the cause and action of the additional error.
MESSAGE
BUILD failed. (! !) (DBERR 8215)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le.
MESSAGE
Permission denied. (DBERR 8216)
CAUSE
You tried to issue PURGEFILE with superuser but the
DBEnvironment directory does not have correct permission.
ACTION
Set the DBEnvironment directory correctly. Refer to the
ALLBASE/SQL Database Administration Guide .
MESSAGE
Specified DBEFile is not associated with specified
DBEnvironment. (DBERR 8217)
CAUSE
The DBEFile you specied in the MOVEFILE command exists,
but is not associated with the specied DBEnvironment.
ACTION
Issue the command again, specifying the correct DBEnvironment
MESSAGE
Internal error #!, detail #!. (DBERR 8219)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your
ALLBASE/SQL Service Representative or Response Center.
ALLBASE/SQL Error Messages
8220
8221
8222
8223
8224
MESSAGE
Not a valid ALLBASE/SQL DBEnvironment. (DBERR 8220)
CAUSE
You tried to access an HP IMAGE DBEnvironment through
SQLUtil.
ACTION
Use HPIUtil to access HP IMAGE DBEnvironments, and
SQLUtil to access ALLBASE/SQL DBEnvironments.
MESSAGE
Internal NLS error. (DBERR 8221)
CAUSE
The local language table corresponding to your language
cannot be accessed, probably because the environment le or
custdatatable le does not exist.
ACTION
Contact your system administrator.
MESSAGE
Message catalog not available - see system administrator.
(DBERR 8222)
CAUSE
The message catalog le cannot be accessed, probably because it
does not exist.
ACTION
Contact your system administrator.
MESSAGE
Invalid Syntax. (DBERR 8223)
CAUSE
The syntax of the command is invalid.
ACTION
Refer to the ALLBASE/SQL Database Administration Guide for
the correct syntax.
MESSAGE
Integer overflow, maximum value = ! (DBERR 8224)
CAUSE
The integer value specied exceeds the maximum value.
ACTION
Issue the command again with a valid integer value.
ALLBASE/SQL Error Messages
3-201
8225
8226
8227
8229
8231
3-202
MESSAGE
Backward migration is needed - use SQLMIGRATE. (DBERR
8225)
CAUSE
The release of the ALLBASE/SQL software does not match the
version of the DBEnvironment.
ACTION
Use the migration tool, SQLMigrate, to migrate the
DBEnvironment backward to the proper version or use a newer
release of the ALLBASE/SQL software.
MESSAGE
Forward migration is needed - use SQLMIGRATE. (DBERR
8226)
CAUSE
The release of the ALLBASE/SQL software does not match the
version of the DBEnvironment.
ACTION
Use the migration tool, SQLMigrate, to migrate the
DBEnvironment forward to the proper version or use an older
release of the ALLBASE/SQL software.
MESSAGE
DBEnvironment corrupted during previous migration.
(DBERR 8227)
CAUSE
At some prior time, a migration attempt failed which corrupted
the DBEnvironment in the process.
ACTION
Restore the DBEnvironment from the backup.
MESSAGE
Keyword required for this command. (DBERR 8229)
CAUSE
The command you entered requires a keyword for completion.
ACTION
Enter an appropriate keyword as shown in the help message
syntax for the command you entered.
MESSAGE
Illegal input - invalid Unit or Keyword (DBERR 8231)
CAUSE
The responses to the maximum timeout or default timeout
prompts of the ALTDBE command contain an incorrect unit or
keyword.
ACTION
Refer to the ALLBASE/SQL Database Administration Guide for
the correct syntax of the ALTDBE command.
ALLBASE/SQL Error Messages
8232
8233
8234
8235
8238
8249
MESSAGE
Index exceeds buffer size (DBERR 8232)
CAUSE
An SQLUtil internal error occurred.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Unknown option: ! (DBERR 8233)
CAUSE
The option specied is invalid.
ACTION
Refer to the ALLBASE/SQL Database Administration Guide for
the correct syntax.
MESSAGE
Restorelog on device '!' failed. (DBERR 8234)
CAUSE
You specied an invalid input device when issuing a
RESTORELOG command.
ACTION
Check with your system administrator to obtain the correct
device name.
MESSAGE
No such user exists on system. (DBERR 8235)
CAUSE
The user name you specied in the RESTORE command does
not exist.
ACTION
Check your spelling and the HP-UX password le for legal names
and enter the command again, specifying a valid name.
MESSAGE
File name must be no more than ! bytes. (DBERR 8238)
CAUSE
File name is more than 256 characters.
ACTION
Change the le name to have a maximum of 256 characters only.
MESSAGE
No Log file name was specified. (DBERR 8249)
CAUSE
There is no log le name specied.
ACTION
Please specify a log le name to convert to a wrapper
DBEnvironment.
ALLBASE/SQL Error Messages
3-203
8270
8271
8273
MESSAGE
Cannot make DBEFile0 pseudo-mapped. (DBERR 8270)
CAUSE
You cannot convert DBEFile0 to a pseudo-mapped le.
ACTION
No action required. If you wish, choose a dierent DBEFile for
conversion, then issue the MOVEFILE command again.
MESSAGE
Pseudo-mapped file exists in DBEnvironment. Cannot
perform STOREONLINE. (DBERR 8271)
CAUSE
One or more DBEFiles within the DBEnvironment has the
le access mode set to pseudo-mapped. The DBEnvironment
must contain only mapped access les in order to use the
STOREONLINE command.
ACTION
Use the SQLUtil SHOWACCESS command to determine
which les have pseudo-mapped access. If desired, change
the access mode of each le from pseudo-mapped to mapped
using the SQLUtil MOVEFILE command. Then reissue the
STOREONLINE command.
MESSAGE
Too many files, MAX = 128 files. (DBERR 8273)
CAUSE
Number of les exceeds the limit.
ACTION
Keep the number of les to be within 128.
MESSAGE
Too many files, MAX = 256 files. (DBERR 8274)
CAUSE
Number of les while restoring exceeds the limit.
ACTION
Keep the number of les within 256 while restoring.
MESSAGE
Chkpthlp Failed. (DBERR 8275)
CAUSE
Chkpthlp help command failed. Error occurred while ushing
dirty pages from buer pool.
ACTION
Checkpoint process is not done. Try this again after giving the
checkpoint command in ISQL.
.
8274
8275
3-204
ALLBASE/SQL Error Messages
9126
10000
10001
10002
10003
MESSAGE
Allbase Server Error. Invalid format node data type
encountered.(DBERR 9126)
CAUSE
An incorrect node data type was used.
ACTION
Change to a correct data type.
MESSAGE
Internal error detected at run time. (DBERR 10000)
CAUSE
SQLCA is corrupt. The command was not executed.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Internal error detected at run time. (DBERR 10001)
CAUSE
SQLCA.SQLEXT is corrupt. The command was not executed.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
More than one row qualifies for SELECT INTO. (DBERR 10002)
CAUSE
This form of the SELECT statement in a program can handle
only single row query results.
ACTION
Modify the program to use BULK SELECT or FETCH via a
cursor.
MESSAGE
EXECUTE IMMEDIATE invalid for a SELECT statement. (DBERR
10003)
CAUSE
You attempted to use a SELECT statement with an EXECUTE
IMMEDIATE statement.
ACTION
Use the DESCRIBE statement to distinguish between queries
and non-queries. Refer to the ALLBASE/SQL application
programming guide for the language you are using for additional
information on handling dynamic queries.
ALLBASE/SQL Error Messages
3-205
10004
10005
10006
3-206
MESSAGE
EXECUTE IMMEDIATE invalid with host variable. (DBERR
10004)
CAUSE
The EXECUTE IMMEDIATE statement contained a host
variable.
ACTION
Eliminate the host variable from the EXECUTE IMMEDIATE
statement in the source le and re-preprocess your program.
MESSAGE
Too many columns in dynamic FETCH. (DBERR 10005)
CAUSE
There was not enough buer space for the number of columns
specied in the FETCH statement.
ACTION
Reduce the number of columns specied in the select list or
increase your buer space, then re-preprocess your program.
MESSAGE
Bad starting index. (DBERR 10006)
CAUSE
The value stored in the StartIndex host variable named in the
INTO clause of a BULK SELECT, BULK FETCH, or BULK
INSERT statement was either less than 1 or greater than the
number of records the host variable array can accommodate.
Control returns to the calling program, but the command is not
executed.
ACTION
Modify the source le constructs that assign a value to StartIndex
to ensure that the value is from 1 through the maximum
number of records that the host variable can accommodate and
re-preprocess your program.
ALLBASE/SQL Error Messages
10007
MESSAGE
Bad row count. (DBERR 10007)
CAUSE
The value stored in the NumberOfRows host variable you named
in the INTO clause of a BULK SELECT or BULK FETCH or
the VALUES clause of a BULK INSERT statement is negative
or
the NumberOfRows plus the StartIndex minus 1 is greater than
the number of rows the host variable array can accommodate.
Control returns to the calling program, but the command is not
executed. No rows were retrieved or inserted.
10008
10010
10011
ACTION
Modify the source le constructs that assign a value to StartIndex
to ensure that the value is from 1 through the maximum
number of records that the host variable can accommodate and
re-preprocess your program.
MESSAGE
Message catalog not available - see system administrator.
(DBERR 10008)
CAUSE
The message catalog may not be installed on your system.
ACTION
Contact your system administrator.
MESSAGE
DBEnvironment name too long. (DBERR 10010)
CAUSE
The DBEnvironment name specied at run-time exceeds the
maximum of 128 bytes fully qualied.
ACTION
Re-run your application, specifying a valid DBEnvironment name.
MESSAGE
PREPARE invalid with host variable. (DBERR 10011)
CAUSE
The PREPARE statement contained a host variable.
ACTION
Eliminate the host variable from the PREPARE statement in the
source le and re-preprocess your program.
ALLBASE/SQL Error Messages
3-207
10012
10013
10014
10015
10016
3-208
MESSAGE
Internal error. Cannot get language information table for
user's language. (DBERR 10012)
CAUSE
The character set table for the language you specied is not
accessible.
ACTION
Install NLS onto system.
MESSAGE
Invalid number of columns specified in SQLDA.SQLN (DBERR
10013)
CAUSE
The number of columns you specied is less than zero, equal to
zero, or greater than 1024.
ACTION
Change the number of columns to a value greater than zero and
less than 1025.
MESSAGE
Invalid format array address in SQLDA.SQLFMTARR. (DBERR
10014)
CAUSE
SQLDA.SQLFMTARR is not pointing to the buer.
ACTION
Initialize SQLDA.SQLFMTARR.
MESSAGE
Invalid version number specified in the SQLX TABLE
parameter. (DBERR 10015)
CAUSE
An unknown TABLE.VERSION setting was passed to the SQLX
interface.
ACTION
Correct the TABLE.VERSION setting.
MESSAGE
Invalid version number specified in the SQLX COLUMNS
parameter. (DBERR 10016)
CAUSE
An unknown COLUMNS.VERSION setting was passed to the
SQLX interface.
ACTION
Correct the COLUMNS.VERSION setting.
ALLBASE/SQL Error Messages
10017
10018
10019
10020
10021
MESSAGE
Internal error. Could not allocate or deallocate the
linear tree node. (DBERR 10017)
CAUSE
The linear tree node could not be allocated or deallocated. This
may be caused by a memory resource failure.
ACTION
Try your program again later. If the condition persists, then
record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Invalid setting in PARMCB.CODE_FLAG. (DBERR 10018)
CAUSE
An unknown PARMCB.CODE FLAG setting was passed to the
SQLX interface.
ACTION
Correct the PARMCB.CODE FLAG setting.
MESSAGE
Invalid setting in PARMCB.SECTION.SECTION_NUM. (DBERR
10019)
CAUSE
The PARMCB.SECTION.SECTION NUM specied is 0, less
than -32767, or greater than 32767.
ACTION
Specify a valid RMCB.SECTION.SECTION NUM value.
MESSAGE
Cannot change current connection because a transaction is
active. (DBERR 10020)
CAUSE
A transaction is still active when issuing a CONNECT, SET
CONNECTION, START DBE, START DBE NEW, or START
DBE NEWLOG statement in single-transaction mode.
ACTION
Either commit or rollback the transaction, or change to
multi-transaction mode. Then retry the operation.
MESSAGE
The SQLX function code setting is not supported or
invalid. (DBERR 10021)
CAUSE
An unknown CODE parameter setting was passed to the SQLX
interface.
ACTION
Specify a valid CODE parameter.
ALLBASE/SQL Error Messages
3-209
10022
10023
10024
10025
10026
3-210
MESSAGE
Invalid version number specified in the SQLX AREAS
parameter. (DBERR 10022)
CAUSE
An unknown AREAS.VERSION setting was passed to the SQLX
interface.
ACTION
Specify a valid AREAS.VERSION setting.
MESSAGE
Invalid version number specified in the SQLX SQLEA
parameter. (DBERR 10023)
CAUSE
An unknown SQLEA.VERSION setting was passed to the SQLX
interface.
ACTION
Specify a valid SQLEA.VERSION setting.
MESSAGE
Invalid version number specified in the SQLX SQLPA
parameter. (DBERR 10024)
CAUSE
An unknown SQLPA.VERSION setting was passed to the SQLX
interface.
ACTION
Specify a valid SQLPA.VERSION setting.
MESSAGE
Invalid version number specified in the SQLX PARMCB
parameter. (DBERR 10025)
CAUSE
An unknown PARMCB.VERSION setting was passed to the
SQLX interface.
ACTION
Specify a valid PARMCB.VERSION setting.
MESSAGE
Invalid version number specified in the SQLX SECTION
parameter. (DBERR 10026)
CAUSE
An unknown SECTION.VERSION setting was passed to the
SQLX interface.
ACTION
Specify a valid SECTION.VERSION setting.
ALLBASE/SQL Error Messages
10027
10028
10029
10030
10031
MESSAGE
Invalid version number specified in the SQLX STATEMENT
parameter. (DBERR 10027)
CAUSE
An unknown STATEMENT.VERSION setting was passed to the
SQLX interface.
ACTION
Specify a valid STATEMENT.VERSION setting.
MESSAGE
Invalid version number specified in the SQLX PARMS
parameter. (DBERR 10028)
CAUSE
An unknown PARMS.VERSION setting was passed to the SQLX
interface.
ACTION
Specify a valid PARMS.VERSION setting.
MESSAGE
Invalid version number specified in the SQLX DATABUF
parameter. (DBERR 10029)
CAUSE
An unknown DATABUF.VERSION setting was passed to the
SQLX interface.
ACTION
Specify a valid DATABUF.VERSION setting.
MESSAGE
SQL statement not allowed. (DBERR 10030)
CAUSE
The SQL statement you specied is not allowed in the SQLX
routine called.
ACTION
Specify a valid SQL statement for the SQLX routine called.
MESSAGE
Number of PARMS formats did not match the SQL command.
(DBERR 10031)
CAUSE
The PARMS.PARMBUF FMT is passed when not needed, or is
not passed when needed, or does not match the number of input
host variables.
ACTION
Correct the PARMS.PARMBUF FMT parameter.
ALLBASE/SQL Error Messages
3-211
10032
10033
10034
10035
10036
3-212
MESSAGE
Number of DATABUF formats did not match the SQL command.
(DBERR 10032)
CAUSE
The DATABUF.BUFFER FMT is passed when not needed, or is
not passed when needed, or does not match the number of input
host variables.
ACTION
Correct the DATABUF.BUFFER FMT parameter.
MESSAGE
No input host variables specified for BULK INSERT. (DBERR
10033)
CAUSE
You have not specied input host variables for a BULK INSERT
statement.
ACTION
Specify input host variables in the BULK INSERT statement.
MESSAGE
No output host variables specified for FETCH or SELECT.
(DBERR 10034)
CAUSE
You have not specied output host variables for FETCH or
SELECT statements.
ACTION
Specify output host variables in the FETCH or SELECT
statements.
MESSAGE
The SQL statement is unknown. (DBERR 10035)
CAUSE
The SQL statement you specied cannot be processed by the
SQLX interface.
ACTION
Specify a valid SQL statement.
MESSAGE
The specified connection name is already in use. (DBERR
10036)
CAUSE
You have specied a connection name that is already used by
another CONNECT.
ACTION
Specify a unique connection name.
ALLBASE/SQL Error Messages
10037
10038
10039
10040
10041
10042
MESSAGE
The specified connection name is not open. (DBERR 10037)
CAUSE
You specied a connection name that is not associated with a
CONNECT.
ACTION
Specify a valid connection name.
MESSAGE
Invalid number of columns in PARMCB.COLUMNS.NUM_COLUMNS.
(DBERR 10038)
CAUSE
The number of columns you specied in
PARMCB.COLUMNS.NUM COLUMNS is less than 0
or greater than 255.
ACTION
Correct the value of PARMCB.COLUMNS.NUM COLUMNS.
MESSAGE
Invalid number of formats specified. (DBERR 10039)
CAUSE
The number of format elements you specied is either less than or
equal to 0, or greater than 1024.
ACTION
Specify the correct number of format elements.
MESSAGE
No more WSL records to transmit. (DBERR 10040)
CAUSE
A Transmit Log reader has encountered the end of log. No more
log records can be transmitted beyond this point until some more
get written.
ACTION
Wait for a certain period and then retry.
MESSAGE
Invalid MODE specified. (DBERR 10041)
CAUSE
The mode specied is invalid. Each intrinsic has a specied set of
valid modes.
ACTION
Check the specied mode.
MESSAGE
Invalid FLAG specified. (DBERR 10042)
CAUSE
The ag specied in the arglist is invalid. Each intrinsic has a
specied set of valid ags.
ACTION
Check the specied ag.
ALLBASE/SQL Error Messages
3-213
10043
10044
10045
10046
3-214
MESSAGE
Invalid log scan id passed. (DBERR 10043)
CAUSE
This error can be seen by either Transmit Log or Close Log Scan
when the scan id specied in the arglist does not match that of a
valid log scan currently open by this process.
ACTION
Check the scan id specied in the arglist against the scan ids
previously returned by Open Log Scan.
MESSAGE
Invalid log buffer size. (DBERR 10044)
CAUSE
The buer size specied in the arglist is not large enough
to contain even the smallest WSL record. This error can be
encountered by Transmit Log and Apply Log.
ACTION
Check the buer size eld in the arglist to determine if it has
been properly initialized. If it has been, then a larger buer
should be dened since it is too small to receive any WSL
records.
MESSAGE
Invalid value of used log buffer space. (DBERR 10045)
CAUSE
Apply Log has determined that the size used specied in the
arglist is invalid. This indicates that either the size used is
smaller than the smallest WSL record possible, or that the
size used is greater than the number of bytes reserved in the log
buer (as indicated by the buer size eld in the arglist).
ACTION
Check that the size used is less than or equal to the buer size
eld in the arglist. The size used being passed to Apply Log
should also be checked against the value that was returned by
Transmit Log.
MESSAGE
Invalid buffer offset passed. (DBERR 10046)
CAUSE
Apply Log has determined that the buer oset eld specied
in the arglist does not point to a valid position in the log buer.
This will occur if the buer oset contains a negative value, or a
number greater than the size used eld specied in the arglist.
ACTION
Check the application.
ALLBASE/SQL Error Messages
10047
MESSAGE
A WSL record in the log buffer has an invalid record length
specified. (DBERR 10047)
CAUSE
The Apply Log intrinsic attempts consistency checking on the
lengths of records encountered in the log buer. If the current
position in the buer plus the length of the next log record
takes it beyond the end of the used buer space, Apply Log
will generate this error. On BEGIN WORK, if the op code of
the next log record allows predetermining its correct length, the
specied record length is checked against this value.
Check the parameters set up by the application.
ACTION
10048
MESSAGE
A BEGIN WORK WSL record encountered out of sequence.
(DBERR 10048)
CAUSE
This error is generated when Apply Log encounters the BEGIN
WORK WSL record for a new transaction while a previous
Apply Log transaction is still in progress. A possible cause is if
an application started applying transaction T1 (which spanned
multiple log buers) and tried to apply transaction T2 before
applying the COMMIT WORK WSL record for T1. This error is
most likely encountered when a single Apply-Log server process is
applying transactions received from multiple open scans. Another
possible cause is if a transmission error occurred and the end of
the transaction (containing the COMMIT WORK WSL record)
was lost.
ACTION
Check the application. If the application is handling transactions
correctly (especially ones that span multiple log buers) then you
may try transmitting again the transactions being applied.
ALLBASE/SQL Error Messages
3-215
10049
10050
10051
3-216
MESSAGE
No apply WSL records transaction currently active. (DBERR
10049)
CAUSE
Apply Log encountered a WSL record that was not a BEGIN
WORK record, and the BEGIN WORK WSL record has not been
processed for the transaction. One cause is if the Apply Log
transaction was aborted and the user tries to continue applying
log records without starting at the beginning of the transaction.
Another cause is if a transmission error has occurred and the
beginning of the transaction has been lost.
ACTION
Check the application to determine if transactions are correctly
reapplied (especially transactions which span multiple log
buers). Then try to transmit the transactions and apply them
again. If the condition persists, try closing and reopening the log
scan.
MESSAGE
WSL records applied did not match transaction length.
(DBERR 10050)
CAUSE
Apply Log determined that applying the WSL record will lead
to a mismatch between the number of bytes applied for the
transaction and the length of the transaction specied in the
BEGIN WORK WSL record. For all records, except a COMMIT
WORK WSL record, this indicates that the record length plus
the number of bytes previously applied would be greater than the
transaction length specied in the BEGIN WORK record. For
COMMIT WORK records, this error indicates that the length of
the COMMIT WORK record plus the number of bytes previously
applied does not exactly equal the required transaction length.
This is encountered if part of the transaction has been lost (due
to transmission errors, buering schemes, etc.).
ACTION
Check the application to make sure complete transactions are
being buered and transmitted correctly. Then try to transmit
the transactions and apply them again. If the condition persists,
try closing and reopening the log scan.
MESSAGE
Invalid number of partitions specified. (DBERR 10051)
CAUSE
Get Scr or Modify Scr encountered an invalid num partitions
in the arglist. The acceptable values for this eld are somewhat
dependent on the procedure being called in conjunction with the
mode specied.
ACTION
Check the num partitions specied in the arglist.
ALLBASE/SQL Error Messages
10052
10053
10054
10055
MESSAGE
Invalid partition id encountered. (DBERR 10052)
CAUSE
Get Scr or Modify Scr encountered an invalid partition id passed
in from the user. For Get Scr, the partition id in error must be
in the array pointed to be the partition array eld in the arglist.
For Modify Scr, the partition id must be in the SCR array for
mode 1 (UPDATE SCR), or the partition array for mode 2
(DELETE SCR). All partition ids are required to be positive,
non-zero numbers.
ACTION
Check the partition ids specied by the application.
MESSAGE
Invalid number of SCR slots specified. (DBERR 10053)
CAUSE
An invalid num SCR was specied in the arglist. In most cases,
a non-positive value was specied. In the case of Get Scr using
mode 1 (SOFT RESYNC), this error can also be encountered if
the num SCR value is less than the value of num partitions.
ACTION
Check the parameters specied by the application.
MESSAGE
Invalid specification for number of SCR slots used.
(DBERR 10054)
CAUSE
The num SCR used eld specied in the arglist is invalid
so Open Log Scan or Modify Scr generates this error. For
Open Log Scan and Modify SCR (mode 1 only), num SCR used
must be within the range from 1 to num SCR.
ACTION
Check the parameters specied by the application.
MESSAGE
Invalid specification for maximum number of log
files.(DBERR 10055)
CAUSE
An invalid number of max logles for the backward scan during
Open Log Scan was specied. This parameter can be either -1
(the default) or a non-positive number.
ACTION
Check the parameters specied by the application.
ALLBASE/SQL Error Messages
3-217
10056
10057
10058
10059
3-218
MESSAGE
Could not allocate heap space needed for procedure. (DBERR
10056)
CAUSE
Open Log Scan gives this error while allocating control blocks
needed for opened scans. This error states that the routine
was unable to allocate the necessary heap space to be able to
open the log scan. If multiple scans are opened on the same
DBEnvironment, each opened scan receives a new set of control
blocks (which are allocated in the heap), and this problem could
be due to having many scans opened (instead of combining them
into one open scan).
ACTION
Determine the amount of heap space used by the application. If
an excessive amount is used, the application should be modied
to use less. If the heap allocation has previously worked on the
system, rst check the number of users on the system, then use
SQLMON to see global swap space utilization plus heap usage
for individual user processes. If numerous scans are open on the
same DBE, the problem could be alleviated if the open scans
are combined into one open scan (and thus only one set of scan
control blocks).
MESSAGE
Invalid exception number. (DBERR 10057)
CAUSE
You specied an invalid exception number when requesting
diagnostic information.
ACTION
Specify a valid exception number.
MESSAGE
Invalid DBEnvironment or connection name length. (DBERR
10058)
CAUSE
You specied a DBEnvironment or connection name length which
is less than or equal to 0, or greater than 128.
ACTION
Specify a valid DBEnvironment or connection name.
MESSAGE
Invalid BEGIN WORK setting. (DBERR 10059)
CAUSE
You specied a bad transaction priority or isolation level when
starting a transaction.
ACTION
Specify a valid transaction priority or isolation level in the
BEGIN WORK statement.
ALLBASE/SQL Error Messages
10060
10061
10062
10063
10064
10065
MESSAGE
Invalid format node data type encountered. (DBERR 10060)
CAUSE
The data type you specied in one of the format array elements is
not a valid SQL data type.
ACTION
Specify a valid SQL data type.
MESSAGE
Invalid format string specified. (DBERR 10061)
CAUSE
The format string you specied is invalid.
ACTION
Specify a valid format string.
MESSAGE
Invalid setting in PARMCB.CURSOR_NUM. (DBERR 10062)
CAUSE
The cursor number you specied in PARMCB.CURSOR NUM is
either 0, less then -32767, or greater than 32767.
ACTION
Specify a valid cursor number in PARMCB.CURSOR NUM.
MESSAGE
Invalid format node type encountered. (DBERR 10063)
CAUSE
The format node type you specied in one of the format array
elements is invalid.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Invalid PARMCB.PARMS.PARMBUF_LEN specified. (DBERR
10064)
CAUSE
The length you specied in PARMCB.PARMS.PARMBUF LEN
is less than or equal to zero.
ACTION
Specify a valid length in PARMCB.PARMS.PARMBUF LEN.
MESSAGE
Invalid PARMCB.DATABUF.ROW_LEN specified. (DBERR 10065)
CAUSE
The length you specied in PARMCB.DATABUF.ROW LEN is
less than or equal to zero.
ACTION
Specify a valid length in PARMCB.DATABUF.ROW LEN.
ALLBASE/SQL Error Messages
3-219
10066
10067
10068
10069
10071
10074
3-220
MESSAGE
Invalid savepoint specified. (DBERR 10066)
CAUSE
The savepoint number you specied is negative.
ACTION
Specify a valid savepoint number.
MESSAGE
Invalid setting in PARMCB.DATABUF.USE_FLAG. (DBERR
10067)
CAUSE
The data buer use ag you specied in
PARMCB.DATABUF.USE FLAG is invalid.
ACTION
Specify a valid data buer use ag in
PARMCB.DATABUF.USE FLAG.
MESSAGE
Invalid setting in SQLEA. (DBERR 10068)
CAUSE
You specied an invalid SQLX environment control setting.
ACTION
Correct the value of SQLEA.
MESSAGE
The maximum number of DBEnvironments have been connected.
(DBERR 10069)
CAUSE
An attempt to connect to a DBEnvironment was rejected because
the maximum number of database connections has been reached.
ACTION
Release some existing connections.
MESSAGE
SQLX internal error - Pascal escapecode !.(DBERR 10071)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Invalid offset for last record passed. (DBERR 10074)
CAUSE
This can be returned by audit log when the last rec oset eld
contains an invalid value.
ACTION
Check the application to determine what value is being passed
and whether it is within the domain of the log buer space.
ALLBASE/SQL Error Messages
10075
10076
10077
10080
10081
MESSAGE
Invalid number of records in column array. (DBERR 10075)
CAUSE
The num columns eld in the Arglist has been initialized to a
negative number.
ACTION
Check the application program to determine whether this eld is
being initialized properly.
MESSAGE
Invalid number of records in update column array. (DBERR
10076)
CAUSE
The num upd cols eld in the Arglist has been initialized to a
negative number.
ACTION
Check the application program to determine whether this eld is
being initialized properly.
MESSAGE
Insufficient space in log buffer to return next log
record. (DBERR 10077)
CAUSE
Transmit log was unable to transmit the log record into the
log buer because there was insucient space to hold it. This
warning can only be encountered if the rst record to transmit
will not t into the log buer.
ACTION
Allocate a larger log buer space and call transmit log again.
MESSAGE
XA Interface protocol error occurred. (DBERR 10080)
CAUSE
You specied incorrect XA call interface protocol.
ACTION
Refer to the X/OPEN XA Interface standard for possible causes.
MESSAGE
Internal error. Could not allocate or deallocate the DCB.
(DBERR 10081)
CAUSE
The DBE Control Block could not be allocated or deallocated,
possibly because of a memory resource failure.
ACTION
Try your program later. If the condition persists, then record
as much information as possible and contact your HP Service
Representative or Response Center.
ALLBASE/SQL Error Messages
3-221
10082
10083
10084
10085
10086
3-222
MESSAGE
Internal error. Could not allocate or deallocate the GCB.
(DBERR 10082)
CAUSE
The Global Control Block could not be allocated or deallocated,
possibly because of a memory resource failure.
ACTION
Try your program later. If the condition persists, then record
as much information as possible and contact your HP Service
Representative or Response Center.
MESSAGE
Internal error. Could not get the Star/Externals KPO.
(DBERR 10083)
CAUSE
The SQLX runtime interface is unable to obtain the
Star/Externals KPO.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Internal error. Could not set the Star/Externals KPO.
(DBERR 10084)
CAUSE
The SQLX runtime interface is unable to set the Star/Externals
KPO.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Internal error. Could not allocate the Star/Externals
KPO. (DBERR 10085)
CAUSE
The Star/Externals KPO could not be allocated, possibly because
of a memory allocation failure.
ACTION
Try your program later. If the condition persists, then record
as much information as possible and contact your HP Service
Representative or Response Center.
MESSAGE
XA Interface ALLBASE/SQL protocol error occurred. (DBERR
10086)
CAUSE
An incorrect combination of XA call interface and ALLBASE/SQL protocol was performed.
ACTION
Refer to the X/OPEN XA Interface standard for possible causes.
ALLBASE/SQL Error Messages
10087
10088
10089
10090
10091
MESSAGE
A transaction is active in another DBEnvironment
connection. (DBERR 10087)
CAUSE
A SET MULTITRANSACTION OFF statement was rejected
because at least one transaction is active outside of the current
DBEnvironment connection.
ACTION
Complete any active transactions associated with other
DBEnvironment connections using either COMMIT WORK or
ROLLBACK WORK, and retry the statement.
MESSAGE
XA Interface rmfail error occurred.
CAUSE
A resource manager failure has occurred in the XA interface.
ACTION
Refer to the X/OPEN XA Interface standard for possible causes.
MESSAGE
Error occurred opening the module file. (DBERR 10089)
CAUSE
The specied module le could not be opened.
ACTION
Ensure that the module le exists, and that it can be read
and written to. If the condition persists, then record as
much information as possible and contact your HP Service
Representative or Response Center.
MESSAGE
The module file is empty. (DBERR 10090)
CAUSE
The specied module le to be installed is empty.
ACTION
Specify the correct module le name, or create new module le.
MESSAGE
The file is not a module file, or it is corrupted. (DBERR
10091)
CAUSE
The specied module le to be installed is either corrupt or is not
a module le.
ACTION
Specify the correct module le name, or create new module le.
(DBERR 10088)
ALLBASE/SQL Error Messages
3-223
10092
MESSAGE
Incorrect protocol when installing or creating a module
file. (DBERR 10092)
CAUSE
You attempted to install and create a module le simultaneously
or
the le identier passed to the install is dierent from the one
assigned when the module le was opened.
ACTION
Do not attempt to install and create a module le simultaneously
or
pass the le identier set when the module le was opened.
10093
10094
10095
3-224
MESSAGE
Error occurred reading the module file. (DBERR 10093)
CAUSE
The specied module le could not be read.
ACTION
Ensure that the module le exists and that it has the correct
read/write permissions. If the condition persists, then record
as much information as possible and contact your HP Service
Representative
MESSAGE
Error occurred closing the module file. (DBERR 10094)
CAUSE
The specied module le could not be closed.
ACTION
Ensure that the module le exists. If the condition persists, then
record as much information as possible and contact your HP
Service Representative
MESSAGE
Module file created with with different product or
version. (DBERR 10095)
CAUSE
The specied module le to be installed was created from an
incompatible version of ALLBASE/SQL.
ACTION
Recreate the module le with the current version of
ALLBASE/SQL.
ALLBASE/SQL Error Messages
10096
10900
10901
10902
10903
MESSAGE
Error occurred writing the module file. (DBERR 10096)
CAUSE
The specied module le could not be written to.
ACTION
Ensure that the module le exists and that it can be written to.
If the condition persists, then record as much information as
possible and contact your HP Service Representative
MESSAGE
PRESERVE or REVOKE may not be used without DROP option.
(DBERR 10900)
CAUSE
The preprocessor INFO string contained the NODROP option (or
defaulted to NODROP because DROP was not specied) and also
contained a PRESERVE or REVOKE option.
ACTION
The PRESERVE and REVOKE options only apply when the
DROP option is also specied. Invoke the preprocessor again,
specifying only valid combinations of options in the INFO string.
MESSAGE
DROP or NODROP option may only be specified once. (DBERR
10901)
CAUSE
The preprocessor INFO string contained both DROP and
NODROP options or duplicate DROP or NODROP options.
ACTION
Invoke the preprocessor again eliminating the invalid DROP and
NODROP combination or specifying the DROP or NODROP
option only once.
MESSAGE
DBEnvironment name too long. (DBERR 10902)
CAUSE
The DBEnvironment name specied in the invocation line for the
preprocessor was too long.
ACTION
Invoke the preprocessor again, specifying a valid DBEnvironment
name. Refer to the ALLBASE/SQL Reference Manual for
naming conventions.
MESSAGE
DBEnvironment name missing. (DBERR 10903)
CAUSE
The preprocessor invocation line contained neither a
DBEnvironment name nor the -s option.
ACTION
Invoke the preprocessor again, specifying one of these two
options.
ALLBASE/SQL Error Messages
3-225
10904
10905
10906
10907
10908
10920
3-226
MESSAGE
Invalid DBEnvironment name. (DBERR 10904)
CAUSE
The DBEnvironment name you specied in the preprocessor
invocation line is invalid.
ACTION
Invoke the preprocessor again, specifying a valid DBEnvironment
name.
MESSAGE
MODULE name too long. (DBERR 10905)
CAUSE
The module name you specied in the preprocessor invocation
line exceeded the maximum length of 20 bytes.
ACTION
Invoke the preprocessor again, specifying a valid module name.
MESSAGE
OWNER name too long. (DBERR 10906)
CAUSE
The owner name you specied in the preprocessor invocation line
exceeded the maximum length of 20 bytes.
ACTION
Invoke the preprocessor again, specifying a valid owner name.
MESSAGE
File open error. (DBERR 10907)
CAUSE
The source le you specied in the preprocessor invocation line
does not exist.
ACTION
Check your spelling. Use the HP-UX ls command to make sure
the specied le exists.
MESSAGE
Error in preprocessor command line. (DBERR 10908)
CAUSE
An error occurred in the preprocessor invocation line. An
additional error message will be returned.
ACTION
Refer to the cause and action of the additional error message.
MESSAGE
Memory allocation failed. (DBERR 10920)
CAUSE
The preprocessor was unable to obtain the additional memory it
needed.
ACTION
Try preprocessing your program later or reduce the size of the
program.
ALLBASE/SQL Error Messages
10921
10922
10923
10925
10926
10927
MESSAGE
Input source file not found. (DBERR 10921)
CAUSE
The preprocessor could not locate the specied input source le
name.
ACTION
Check your spelling and the pathname specied, then invoke the
preprocessor again.
MESSAGE
System error in opening input source file. (DBERR 10922)
CAUSE
The source le you specied is currently being accessed.
ACTION
Wait until the source le is no longer being accessed, then invoke
the preprocessor again.
MESSAGE
Processing terminated prematurely. (DBERR 10923)
CAUSE
An error occurred which caused preprocessing to be terminated.
An additional error message will be returned.
ACTION
Refer to the cause and action of the additional error message.
MESSAGE
Integer value too large. (DBERR 10925)
CAUSE
You specied an integer value in the source program that exceeds
the largest legal integer on the system.
ACTION
Correct the integer value and re-preprocess your program.
MESSAGE
Comment not ended before end of file. (DBERR 10926)
CAUSE
A comment line was not closed before the end of the le.
ACTION
Close the comment line with \*) " and re-preprocess your
program.
MESSAGE
Illegal character. (DBERR 10927)
CAUSE
The preprocessor detected a control character before the end of
the le. The character was skipped and no module was stored.
ACTION
Delete the control character and re-preprocess your program.
ALLBASE/SQL Error Messages
3-227
10929
10931
10932
10933
10934
3-228
MESSAGE
No ending semicolon before end of file. (DBERR 10929)
CAUSE
An SQL statement was not ended with a semicolon.
ACTION
Check your Pascal program to make sure that all SQL statements
are ended with a semicolon and then re-preprocess your program.
MESSAGE
Syntax error in program header. (DBERR 10931)
CAUSE
Your program statement contained a syntax error.
ACTION
Refer to the appropriate host language reference manual for
correct syntax.
MESSAGE
Syntax error in host variable declaration. (DBERR 10932)
CAUSE
Declarations that appear in the declare section of the source le
are not allowed by the preprocessor. No module was stored.
ACTION
Correct the host variable declaration in the source le and
re-preprocess your program. Refer to the ALLBASE/SQL
application programming guide for the language you are using for
additional information on host variable declaration syntax.
MESSAGE
Unsupported type syntax for host variable. (DBERR 10933)
CAUSE
The host variable type you specied in the BEGIN or DECLARE
section of your program was invalid.
ACTION
Refer to the ALLBASE/SQL application programming guide for
the language you are using for valid host variable types.
MESSAGE
Semicolon expected. (DBERR 10934)
CAUSE
There was a semicolon missing on the specied line of your C or
Pascal program.
ACTION
Add the semicolon and re-preprocess your program.
ALLBASE/SQL Error Messages
10935
10936
10937
10938
10939
MESSAGE
Unmatched END DECLARE SECTION. (DBERR 10935)
CAUSE
You did not include a BEGIN DECLARE SECTION in your
source le.
ACTION
Add BEGIN DECLARE SECTION before your rst host variable
declaration and re-preprocess your program.
MESSAGE
Syntax error. (DBERR 10936)
CAUSE
An unrecognized syntax error occurred.
ACTION
Correct the syntax in either the line specied in the error message
or the line immediately preceding or immediately following
the specied line. Refer to the ALLBASE/SQL application
programming guide for the language you are using for additional
information.
MESSAGE
Syntax error caused skip to end of DECLARE SECTION. (DBERR
10937)
CAUSE
An unrecognized syntax error occurred in the host variable
declaration section.
ACTION
Correct the syntax in either the specied line in the error message
or the line immediately preceding or immediately following
the specied line. Refer to the ALLBASE/SQL application
programming guide for the language you are using for additional
information.
MESSAGE
This host variable was previously declared. (DBERR 10938)
CAUSE
You specied the same name for more than one host variable.
ACTION
Either delete one occurrence of the variable or correct one of the
host variables to specify a unique name and re-preprocess your
program.
MESSAGE
Table element must occur one or more times. (DBERR 10939)
CAUSE
You specied a table declaration in the DECLARE section with
an invalid value in the OCCURS clause.
ACTION
Specify an integer value greater than zero in the table declaration
OCCURS clause.
ALLBASE/SQL Error Messages
3-229
10940
10941
10942
10943
3-230
MESSAGE
Array lower bound may not exceed upper bound. (DBERR
10940)
CAUSE
The array lower bound was greater than the array upper bound.
ACTION
Correct the host variable declare section specifying valid
array bounds, and re-preprocess your program. Refer to the
ALLBASE/SQL application programming guide for the language
you are using for additional information.
MESSAGE
Invalid STRING size. (DBERR 10941)
CAUSE
The size of the string you specied is invalid for a Pascal
program.
ACTION
Modify your Pascal program so that the string is from 1 through
32,767 bytes long, then re-preprocess your program.
MESSAGE
Invalid size for variable of that type. (DBERR 10942)
CAUSE
The size you specied for the FORTRAN host variable is not
valid for that type of host variable.
ACTION
Modify the declaration of the host variable so that it is a valid
size. Refer to the ALLBASE/SQL FORTRAN Application
Programming Guide for additional information on host variables.
MESSAGE
Include file open error. (DBERR 10943)
CAUSE
You encountered a system error while attempting to open the
specied include le.
ACTION
Verify that the specied include le exists; if so, check the
spelling of the include le name. Verify that all components of
the specied path exist. Verify that appropriate read privileges
exist for the specied include le.
ALLBASE/SQL Error Messages
10944
10945
10947
10948
10949
MESSAGE
Unrecognized syntax encountered. Parse aborted. (DBERR
10944)
CAUSE
An unrecognized syntax error occurred. The preprocessor was
unable to continue.
ACTION
Correct the syntax in either the line specied in the error message
or the line immediately preceding. Refer to the ALLBASE/SQL
application programming guide for the language you are using for
additional information.
MESSAGE
Illegal type for record field. (DBERR 10945)
CAUSE
The host variable type you specied in the DECLARE section of
your program was invalid.
ACTION
Refer to the ALLBASE/SQL application programming guide for
the language you are using for valid host variable types.
MESSAGE
Preprocessor does not support this statement. (DBERR
10947)
CAUSE
You included an SQL statement which cannot be embedded in
the language you are using.
ACTION
Delete the SQL statement and re-preprocess your program.
MESSAGE
Unrecognized WHENEVER action. (DBERR 10948)
CAUSE
The condition or action you specied in the WHENEVER clause
is invalid or the label specied for a GOTO action is invalid.
ACTION
Correct the syntax in your WHENEVER clauses and
re-preprocess your program. Keep in mind that valid conditions
are SQLWARNING, SQLERROR, and NOT FOUND. Valid
actions are STOP, GOTO, and CONTINUE.
MESSAGE
Undeclared host variable. (DBERR 10949)
CAUSE
The SQL statement you specied a host variable which was either
not declared or was incorrectly declared in the host variable
declaration section.
ACTION
Either enter the host variable if it was not declared or correct it if
it was entered incorrectly and re-preprocess your program.
ALLBASE/SQL Error Messages
3-231
10950
10951
10953
MESSAGE
Indicator variable type must be SQLIND. (DBERR 10950)
CAUSE
The host variable you used as an indicator variable in an SQL
statement was not declared as SQLIND in the host variable
declaration.
ACTION
Either modify the SQL statement to use a host variable declared
as SQLIND or modify the declaration of the host variable to be
SQLIND and re-preprocess your program.
MESSAGE
Stand-alone SELECT statement requires INTO clause.
(DBERR 10951)
CAUSE
Your embedded SELECT statement did not include the required
INTO clause which denes the host variables for holding rows
returned to the application program.
ACTION
Modify the SELECT statement to include the required
INTO clause and re-preprocess your program. Refer to the
ALLBASE/SQL Reference Manual for additional information on
the SELECT statement.
MESSAGE
Cannot connect to DBEnvironment. (DBERR 10953)
CAUSE
The DBEnvironment you specied does not exist
or
the DBEnvironment you specied is in use and the user mode is
set to SINGLE
or
you do not have the required authority to access the
DBEnvironment.
ACTION
Check your spelling
or
wait until the DBEnvironment is not being accessed
or
contact your database administrator to obtain the required
CONNECT authority.
3-232
ALLBASE/SQL Error Messages
10954
10955
MESSAGE
Cannot begin transaction. (DBERR 10954)
CAUSE
A transaction could not begin. An additional message will be
returned.
ACTION
Refer to the cause and action of the additional message.
MESSAGE
Cannot drop module. (DBERR 10955)
CAUSE
You do not have the required authority to drop the specied
module
or
an additional message will be returned.
ACTION
No action is necessary. You must either be the owner or the
database administrator to drop a module
or
refer to the cause and action of the additional message.
10956
10957
MESSAGE
Cursor name must be a single identifier. (DBERR 10956)
CAUSE
You attempted to qualify a cursor with an owner or module
name.
ACTION
Delete the cursor name qualication in the specied statement
and re-preprocess your program.
MESSAGE
Indicator variables not allowed in this statement. (DBERR
10957)
CAUSE
You specied an indicator variable in a statement that does not
allow indicator variables.
ACTION
Remove the indicator variable from the statement
or
verify that the host variables have the correct data types.
ALLBASE/SQL Error Messages
3-233
10958
10959
10960
10961
10962
3-234
MESSAGE
A query is already defined with this cursor name. (DBERR
10958)
CAUSE
You attempted to declare a cursor which was already declared.
ACTION
Modify one occurrence of the DECLARE CURSOR statement to
specify a unique cursor name and re-preprocess your program.
MESSAGE
There is no declared query with this cursor name. (DBERR
10959)
CAUSE
The SQL statement referenced a cursor which had not been
declared.
ACTION
Insert a DECLARE CURSOR statement before referencing the
cursor and re-preprocess your program.
MESSAGE
Insufficient input host variables. (DBERR 10960)
CAUSE
You specied too few input host variables in the OPEN statement
to cover the columns specied in the cursor declaration.
ACTION
Make sure that there is a host variable listed for each column
specied and re-preprocess your program.
MESSAGE
Too many input host variables. (DBERR 10961)
CAUSE
You specied too many host variables in the OPEN statement for
the number of columns specied in the cursor declaration.
ACTION
Make sure that there is a column specied for each host variable
listed and re-preprocess your program.
MESSAGE
Command name must be a single identifier. (DBERR 10962)
CAUSE
You qualied a command name with the owner or module name.
ACTION
Delete the command name qualication.
ALLBASE/SQL Error Messages
10963
10964
10965
10966
MESSAGE
This command already used. (DBERR 10963)
CAUSE
You attempted to PREPARE a statement using a command
name which has already been used in another PREPARE
statement.
ACTION
Modify one of the PREPARE statements to specify a unique
command name and re-preprocess your program.
MESSAGE
The host variable must be of type STRING or PAC. (DBERR
10964)
CAUSE
You specied host variables which were not of the string or
packed array type.
ACTION
Modify the DECLARE section of your host variable so that the
host variable is of the string or packed array type. Refer to the
ALLBASE/Pascal Application Programming Guide for additional
information.
MESSAGE
Character string is too long. (DBERR 10965)
CAUSE
A string literal you specied in a PREPARE or EXECUTE
IMMEDIATE statement exceeded the maximum limit of 2048
characters.
ACTION
Modify the command to specify a value within the valid limits.
MESSAGE
No prepared query found by this command name. (DBERR
10966)
CAUSE
The EXECUTE statement contained a command name which was
not prepared in the same subprogram unit.
ACTION
Check your spelling. If the command name is correct, insert
an appropriate PREPARE statement before the EXECUTE
statement and re-preprocess your program.
ALLBASE/SQL Error Messages
3-235
10967
10968
10969
10970
10971
3-236
MESSAGE
Cannot open command with host variable parameters. (DBERR
10967)
CAUSE
You specied a host variable in your DECLARE CURSOR
statement.
ACTION
Remove the host variable from your DECLARE CURSOR
statement and re-preprocess your program.
MESSAGE
A cursor on a PREPAREd command is illegal for non-dynamic
queries. (DBERR 10968)
CAUSE
The cursor you specied was associated with a PREPAREd
dynamic query. A cursor with a non-dynamic query should be
used.
ACTION
Change the query to use a cursor associated with a non-dynamic
query or change the query to a dynamic query. Refer to the
ALLBASE/SQL application programming guide for the language
you are using for additional information.
MESSAGE
A cursor on a PREPAREd command is required for dynamic
queries. (DBERR 10969)
CAUSE
The cursor you specied was not associated with a PREPAREd
dynamic query. A cursor associated with a dynamic query should
be used.
ACTION
Change the query to use a cursor associated with a dynamic
query or change the query to a non-dynamic query. Refer to the
ALLBASE/SQL application programming guide for the language
you are using for additional information.
MESSAGE
Warnings when connecting to DBEnvironment. (DBERR 10970)
CAUSE
Additional messages will be returned.
ACTION
Refer to the cause and action of the additional messages.
MESSAGE
Warnings when beginning transaction. (DBERR 10971)
CAUSE
Additional messages will be returned.
ACTION
Refer to the cause and action of the additional messages.
ALLBASE/SQL Error Messages
10972
10973
10974
10975
10976
MESSAGE
Fields of type SQLIND must follow non-SQLIND fields.
(DBERR 10972)
CAUSE
Fields of type SQLIND cannot be the rst eld in a host variable
record declaration nor immediately follow another SQLIND eld.
ACTION
Resequence the elds in the record declaration and check for
missing or duplicated elds, then re-preprocess your program.
MESSAGE
Host variable type must be integer. (DBERR 10973)
CAUSE
The host variable type you specied in your BULK command was
invalid.
ACTION
Declare the host variable as integer and then re-preprocess your
program.
MESSAGE
Too many INTO parameters found in bulk statement. (DBERR
10974)
CAUSE
You named more than three host variables in the INTO clause of
a BULK FETCH or BULK SELECT statement. Preprocessing
terminates and no module is stored.
ACTION
Correct the INTO clause so that it contains at most three
host variables: Buer, StartIndex, and NumberOfRows and
re-preprocess your program.
MESSAGE
Illegal host variable type. (DBERR 10975)
CAUSE
The host variable type you specied was invalid.
ACTION
Declare the host variable specifying a valid type. Refer to the
ALLBASE/SQL application programming guide for the language
you are using for additional information on host variable types.
MESSAGE
Variable must be compatible with CHAR(n), n > 1. (DBERR
10976)
CAUSE
The declaration for a host variable you named in an
SQLEXPLAIN, PREPARE, or EXECUTE statement is not valid.
ACTION
Specify a valid type in the host variable declaration. Refer to the
ALLBASE application programming guide for the language you
are using for additional information.
ALLBASE/SQL Error Messages
3-237
10977
10978
10982
10983
3-238
MESSAGE
ALLBASE/SQL preprocessor error. (DBERR 10977)
CAUSE
An error condition was detected by the preprocessor. Additional
error messages will be returned.
ACTION
Refer to the cause and action of the additional error messages.
MESSAGE
ALLBASE/SQL statement parser error. (DBERR 10978)
CAUSE
An error condition was detected by the statement parser.
Additional error messages will be returned.
ACTION
Refer to the cause and action of the additional error messages.
MESSAGE
No ending single quote before end of line. (DBERR 10982)
CAUSE
A string literal was not properly terminated before the end of the
line or end of the le. No ending single quote was found to match
a beginning single quote.
ACTION
Verify that the string literal is terminated by an ending single
quote on the same line as the beginning single quote. If the string
literal is longer than a single line, verify that the line is properly
continued following conventions specied in the ALLBASE/SQL
application programming guide for the language you are using.
MESSAGE
No ending double quote before end of line. (DBERR 10983)
CAUSE
A string literal was not properly terminated before the end of
the line or end of the le. No ending double quote was found to
match a beginning double quote.
ACTION
Verify that the string literal is terminated by an ending double
quote on the same line as the beginning double quote. If the
string literal is longer than a single line, verify that the line
is properly continued following conventions specied in the
ALLBASE/SQL application programming guide for the language
you are using.
ALLBASE/SQL Error Messages
10984
10985
10990
10992
10993
MESSAGE
Error in continuation of string literal. (DBERR 10984)
CAUSE
A string literal was not properly continued across lines.
ACTION
Verify that the line continuation follows conventions specied
in the ALLBASE/SQL application programming guide for the
language you are using.
MESSAGE
Heap allocation failed. (DBERR 10985)
CAUSE
The preprocessor was unable to obtain the additional memory it
needed.
ACTION
Try preprocessing your program later or reduce the size of the
program.
MESSAGE
Error while writing to file. (DBERR 10990)
CAUSE
An error occurred while the preprocessor was writing to a le.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Host variable type must be integer or short integer.
(DBERR 10992)
CAUSE
The data type of the host variable is invalid.
ACTION
Declare the host variable as an integer or a small integer.
MESSAGE
Embedded savepoint requires a host variable. (DBERR
10993)
CAUSE
A host variable was not specied in your SAVEPOINT statement.
ACTION
Modify your command specifying a valid host variable and
re-preprocess your program. Refer to the ALLBASE/SQL
Reference Manual for additional information on the SAVEPOINT
statement.
ALLBASE/SQL Error Messages
3-239
10994
10995
10996
10998
MESSAGE
Syntax error in option specification. (DBERR 10994)
CAUSE
A syntax error was encountered in a compiler option.
ACTION
Verify that the specied compiler option follows conventions
specied in the ALLBASE/SQL application programming guide
for the language you are using.
MESSAGE
Invalid array size. (DBERR 10995)
CAUSE
A string or array size you specied was greater than the
maximum allowable.
ACTION
Modify the declaration of the string or array so that the length is
less than or equal to 32764 bytes.
MESSAGE
Host variable buffer required. (DBERR 10996)
CAUSE
You did not specify a host variable buer in the value eld of the
BULK INSERT statement.
ACTION
Modify the command within your program to specify a host
variable buer in the value eld and re-preprocess your program.
MESSAGE
Output filename too long. (DBERR 10998)
CAUSE
The output lename you specied in the invocation string is
greater than 9 bytes (excluding extensions)
or
if no output lename was specied, the input source le name
(the default) is greater than 9 bytes (excluding extensions).
10999
3-240
ACTION
Reinvoke the preprocessor specifying an output lename
containing less than or equal to 9 bytes (excluding extensions).
MESSAGE
Preprocessor Internal Error (!). (DBERR 10999)
CAUSE
Unknown escape occurred in the preprocessor.
ACTION
Record the number returned and as much information as possible
and contact your HP Service Representative or Response Center.
ALLBASE/SQL Error Messages
11000
11001
11002
11003
11004
MESSAGE
-d option may only be specified once. (DBERR 11000)
CAUSE
You specied the -d option more than once in the preprocessor
invocation line.
ACTION
Invoke the preprocessor again, specifying the -d option only once.
MESSAGE
-r option may only be specified once. (DBERR 11001)
CAUSE
You specied the -r option more than once in the preprocessor
invocation line.
ACTION
Invoke the preprocessor again, specifying the -r option only once.
MESSAGE
-s option may only be specified once. (DBERR 11002)
CAUSE
You specied the -s option more than once in the preprocessor
invocation line.
ACTION
Invoke the preprocessor again, specifying the -s option only once.
MESSAGE
-m option may only be specified once. (DBERR 11003)
CAUSE
You specied the -m option more than once in the preprocessor
invocation line.
ACTION
Invoke the preprocessor again, specifying the -m option only once.
MESSAGE
-o option may only be specified once. (DBERR 11004)
CAUSE
You specied the -o option more than once in the preprocessor
invocation line.
ACTION
Invoke the preprocessor again, specifying the -o option only once.
ALLBASE/SQL Error Messages
3-241
11005
11006
11007
11008
11009
3-242
MESSAGE
Unrecognized option. Valid options are -d, -r, -s, -m, -o
and -p. (DBERR 11005)
CAUSE
You specied an invalid option in the preprocessor invocation
line. Valid options are -d, -r, -s, -m, -o and -p.
ACTION
Invoke the preprocessor again, specifying one or more of the valid
options. Refer to the ALLBASE/SQL application programming
guide for the language you are using for additional information on
preprocessor invocation.
MESSAGE
-s option may not be used with any other option. (DBERR
11006)
CAUSE
You specied additional options in the preprocessor invocation
line along with the -s option.
ACTION
Invoke the preprocessor again, specifying the -s option as the only
option if you want to run the preprocessor in syntax checking
mode. Do not specify the -s option if you want to run the
preprocessor in full preprocessing mode.
MESSAGE
Invalid module/owner name. (DBERR 11007)
CAUSE
The module or owner name you specied in the preprocessor
invocation line was invalid.
ACTION
Invoke the preprocessor again, specifying a valid module or
owner name. Refer to the ALLBASE/SQL Reference Manual for
naming conventions.
MESSAGE
-i option may only be specified once. (DBERR 11008)
CAUSE
You specied the -i option more than once in the preprocessor
invocation line.
ACTION
Invoke the preprocessor again, specifying the -i option only once.
MESSAGE
-p option may only be specified once. (DBERR 11009)
CAUSE
You specied the -p option more than once in the preprocessor
invocation line.
ACTION
Invoke the preprocessor again, specifying the -p option only once.
ALLBASE/SQL Error Messages
11010
11013
11014
11015
11016
MESSAGE
-r option may not be used without the -d option. (DBERR
11010)
CAUSE
You specied the -r option without the -d option in the
preprocessor invocation line.
ACTION
Invoke the preprocessor again, specifying the -d option if you
specify the -r option.
MESSAGE
Cannot get language information. See System Administrator. (DBERR 11013)
CAUSE
Native language support error occurred. Most likely language
environment le is not accessible.
ACTION
Verify that native language support is properly installed.
MESSAGE
Cannot get Asian language information. (DBERR 11014)
CAUSE
Native language support error occurred. Most likely language
environment le is not accessible.
ACTION
Verify that native language support is properly installed.
MESSAGE
Internal error. Could not truncate line correctly.
(DBERR 11015)
CAUSE
Native language support error occurred during truncation of
source line.
ACTION
Verify that native language support is properly installed.
MESSAGE
Internal error. Cannot upshift characters in invocation
line. (DBERR 11016)
CAUSE
Native language support error occurred while processing the
invocation line.
ACTION
Verify that native language support is properly installed.
ALLBASE/SQL Error Messages
3-243
11017
11018
11019
11020
11021
3-244
MESSAGE
Out of preprocessor symbol table memory. (DBERR 11017)
CAUSE
You used too many host variables or cursor names.
ACTION
Reduce the number of host variables or cursor names or use
subprograms.
MESSAGE
File ! open error. (Paserr 692). (DBERR 11018)
CAUSE
You tried to open a le with a Pascal statement.
ACTION
Check the status of the le named in the error message. For
information on the Pascal error message, refer to the Pascal
Reference Manual .
MESSAGE
Insufficient heap area to allocate variable. (Paserr 600)
(DBERR 11019)
CAUSE
The heap memory space is exhausted.
ACTION
Allocate more heap space.
MESSAGE
Unexpected internal error. (DBERR 11020)
CAUSE
An unexpected internal error was detected.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Statement not supported when dynamic-only option is
specified. (DBERR 11021)
CAUSE
You specied an SQL statement which is not supported when
preprocessing with the dynamic-only option.
ACTION
Modify the SQL statement, or perform preprocessing without the
dynamic-only option.
ALLBASE/SQL Error Messages
11022
11023
11024
11025
MESSAGE
Statement supported only when dynamic-only option is
specified. (DBERR 11022)
CAUSE
You specied an SQL statement which is supported only when
preprocessing with the dynamic-only option.
ACTION
Modify the SQL statement, or perform preprocessing with the
dynamic-only option.
MESSAGE
Host variable declaration larger than maximum DBE name
length. (DBERR 11023)
CAUSE
You specied a host variable with a declared length greater than
the maximum DBEnvironment name length.
ACTION
Specify a host variable with a declared length less than or
equal to the maximum DBEnvironment name length. Consult
the ALLBASE/SQL Reference Manual for the maximum
DBEnvironment name length.
MESSAGE
Host variable declaration too large for this usage. (DBERR
11024)
CAUSE
You specied a host variable with a declared length greater than
the maximum allowed length.
ACTION
Specify a host variable with a declared length less than or equal
to the maximum allowed length. Consult the ALLBASE/SQL
Reference Manual for the maximum allowed length.
MESSAGE
Character string too large for this usage. (DBERR 11025)
CAUSE
You specied a character string which is longer than the
maximum allowed length.
ACTION
Specify a character string which is less than or equal to the
maximum allowed length. Consult the ALLBASE/SQL Reference
Manual for the maximum allowed length.
ALLBASE/SQL Error Messages
3-245
11026
11028
11200
11201
11202
3-246
MESSAGE
DYNAMIC option may be specified only once. (DBERR 11026)
CAUSE
The preprocessor was invoked with the DYNAMIC option
specied more than once in the command line.
ACTION
Invoke the preprocessor specifying the DYNAMIC option only
once.
MESSAGE
DBEnvironment name not allowed for DYNAMIC preprocessing.
(DBERR 11028)
CAUSE
You specied a DBEnvironment name when invoking the
preprocessor with the DYNAMIC option.
ACTION
Omit the DBEnvironment name when invoking the preprocessor
with the DYNAMIC option.
MESSAGE
No ending END-EXEC before end of file. (DBERR 11200)
CAUSE
SQLIN contains an SQL statement that is preceded by EXEC
SQL but is not followed by END-EXEC.
ACTION
Insert END-EXEC in the appropriate location in SQLIN and
process SQLIN again.
MESSAGE
Missing or incorrect PROGRAM-ID paragraph. (DBERR 11201)
CAUSE
The preprocessor did not nd a PROGRAM-ID in SQLIN.
ACTION
Insert a PROGRAM-ID label in SQLIN or check your spelling on
the existing label and re-preprocess your program.
MESSAGE
Host variable must have USAGE COMPUTATIONAL. (DBERR
11202)
CAUSE
The declaration for the StartIndex or NumberOfRows value in a
BULK command is invalid.
ACTION
Declare the host variable as PIC S9(4) or PIC S9(9) and
re-preprocess your program.
ALLBASE/SQL Error Messages
11203
11204
MESSAGE
Host variable must not be a table. (DBERR 11203)
CAUSE
You specied a host variable name in an SQL statement that is
declared as a table but should be declared as an elementary data
item.
ACTION
Correct the host variable declaration and re-preprocess your
program.
MESSAGE
Host variable must be a one-dimensional table. (DBERR
11204)
CAUSE
The declaration of the rst host variable you named in the INTO
clause of a BULK SELECT, BULK FETCH, or BULK INSERT
statement is invalid.
ACTION
Declare the host variable as follows, and use the ARRAY-NAME
in the INTO clause:
01 ARRAY-NAME.
05 ROW-NAME
10 COLUMN1-NAME
.
.
.
10 COLUMNn-NAME
11206
11207
OCCURS n TIMES.
Valid data clause.
Valid data clause.
MESSAGE
Syntax error in COPY statement. (DBERR 11206)
CAUSE
A syntax error was encountered in a COBOL COPY statement.
ACTION
Verify that the COPY statement follows conventions specied in
the COBOL/HP-UX Language Reference Manual .
MESSAGE
Syntax error in REPLACE statement. (DBERR 11207)
CAUSE
A syntax error was encountered in a COBOL REPLACE
statement.
ACTION
Verify that the REPLACE statement follows conventions specied
in the COBOL/HP-UX Language Reference Manual .
ALLBASE/SQL Error Messages
3-247
11208
11209
11210
11211
3-248
MESSAGE
COPY not allowed within another COPY statement. (DBERR
11208)
CAUSE
The keyword COPY was encountered within another COPY
statement. COPY is a keyword which can only be used to specify
the start of a COPY statement.
ACTION
Terminate previous COPY statement before beginning another
COPY statement. Verify that the COPY statement follows
conventions specied in the COBOL/HP-UX Language Reference
Manual .
MESSAGE
Copy file open error. (DBERR 11209)
CAUSE
A system error was encountered while attempting to open the
specied copy le.
ACTION
Check the spelling of the copy le. Verify that the specied copy
le exists. Verify that all components of the specied path exist.
Verify that appropriate read privileges exist for the specied copy
le.
MESSAGE
Statement not properly terminated; period expected.
(DBERR 11210)
CAUSE
A terminating period for a COBOL statement was expected but
not found.
ACTION
Verify that the COBOL statement follows conventions specied in
the COBOL/HP-UX Language Reference Manual .
MESSAGE
No ending '==' before end of line. (DBERR 11211)
CAUSE
A REPLACE/REPLACING parameter literal was not properly
terminated before the end of the line or end of the le. No ending
'==' was found to match a beginning '==' literal delimiter.
ACTION
Verify that the REPLACE/REPLACING parameter literal
is terminated by a '==' on the same line as the beginning
'==' literal delimiter. If the parameter literal is longer than a
single line, verify that the line is properly continued following
conventions specied in the COBOL/HP-UX Language Reference
Manual .
ALLBASE/SQL Error Messages
11212
11213
11300
11301
11400
MESSAGE
Error in continuation of parameter. (DBERR 11212)
CAUSE
A REPLACE/REPLACING parameter literal was not properly
continued on the following line.
ACTION
Verify that the REPLACE/REPLACING parameter literal is
continued following conventions specied in the COBOL/HP-UX
Language Reference Manual .
MESSAGE
Too many characters. (DBERR 11213)
CAUSE
The copy le specication exceeds the allowed maximum number
of characters.
ACTION
Change the copy le specication so that it does not exceed the
maximum number of characters for a valid le name.
MESSAGE
Illegal continuation line, ignored. (DBERR 11300)
CAUSE
The statement contains an illegal continuation character. The
current line is ignored.
ACTION
Specify a valid continuation character in the source le.
MESSAGE
Statement too long for FORTRAN. (DBERR 11301)
CAUSE
Your FORTRAN statement included more than the maximum
number of continuation lines allowable.
ACTION
Modify your FORTRAN statement to include no more than
19 continuation lines (20 lines if you add an initial line) and
re-preprocess your program.
MESSAGE
Type must be array [1..n] of record. (DBERR 11400)
CAUSE
Your BULK command did not contain the required host variable
type.
ACTION
Refer to the ALLBASE/SQL Pascal Application Programming
Guide for additional information on host variables.
ALLBASE/SQL Error Messages
3-249
11500
11502
11503
11504
11506
3-250
MESSAGE
Type must be a structure array. (DBERR 11500)
CAUSE
The host variable used in your bulk command was not a structure
array.
ACTION
Modify the DECLARE section of your program so that the host
variable is a structure array.
MESSAGE
The host variable must be an array of CHAR. (DBERR 11502)
CAUSE
The host variable you specied in the DECLARE section of your
program was not an array of char.
ACTION
Modify the DECLARE section of your program so that the host
variable is a char array.
MESSAGE
Illegal host variable array type. (DBERR 11503)
CAUSE
The host variable array you specied in the DECLARE section of
your program was not a char type or a structure.
ACTION
Modify the DECLARE section and re-preprocess your program.
MESSAGE
Illegal type for structure field. (DBERR 11504)
CAUSE
The host variable you specied in the DECLARE section of your
program had an invalid eld type.
ACTION
Modify the DECLARE section of your program specifying a valid
eld type.
MESSAGE
Label must start with alphabetic character. (DBERR 11506)
CAUSE
A label in a WHENEVER statement started with a number or
some other non-alphabetic character.
ACTION
Change the label to start with an alphabetic character.
ALLBASE/SQL Error Messages
11507
11508
12008
13130
13131
MESSAGE
Nested structures disallowed in host variables. (DBERR
11507)
CAUSE
A host variable was declared in the DECLARE section as a
structure with a structure as one of its elds.
ACTION
Modify the DECLARE section and re-preprocess your program.
MESSAGE
The host variable must be an array type with minimum size
1. (DBERR 11508)
CAUSE
You specied a host variable for sqlvarbinary without an array
specication or with an array size less than 1.
ACTION
Specify the sqlvarbinary host variable with an array size greater
than zero.
MESSAGE
Message catalog not available - see system manager. (DBERR
12008)
CAUSE
The message catalog 'hpsqlcat' was not found in the
/usr/lib/nls/n-computer directory.
ACTION
See your system manager.
MESSAGE
User does not have authority to wrap DBE. (DBERR 13130)
CAUSE
You are not the creator of the original DBEnvironment or the
superuser (HP-UX) or a system administrator (MPE/iX).
ACTION
Only the original DBEnvironment creator or superuser (HP-UX)
or system administrator (MPE/iX) can use the WRAPDBE
command.
MESSAGE
Log file list contains non-existing log file. (DBERR
13131)
CAUSE
You specied a log le(s) that could not be found or opened on
the system.
ACTION
Check the list of log les specied and determine if they are
actually on the system. If so, check the security on the log les.
ALLBASE/SQL Error Messages
3-251
13132
13153
13261
13262
3-252
MESSAGE
Log file list contains duplicates. (DBERR 13132)
CAUSE
When entering the WRAPDBE command, you specied the same
log le more than once.
ACTION
Check the list of log les and reenter the new list with no
duplicates.
MESSAGE
DBEFile does not belong to specified DBEFileSet. (DBERR
13153)
CAUSE
The specied DBEFile does not belong to the specied
DBEFileSet as required by the requested function.
ACTION
Check the specied DBEFile and DBEFileSet.
MESSAGE
DBCore could not find free page buffer. (DBERR 13261)
CAUSE
Due to the number of current users, DBCore was unable to nd
free page buer space. CAUTION: Transaction not necessarily
rolled back.
ACTION
Try your transaction again later. You can lock your table
explicitly using the LOCK TABLE statement to decrease the size
of page buers required or use the SQLUtil ALTDBE command
to allocate more buer space. If the problem persists, record
as much information as possible and contact your HP Service
Representative or Response Center.
MESSAGE
DBCore internal error !. (DBERR 13262)
Please record the above message including both numbers.
CAUSE
An internal error caused your query to be terminated.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
13310
MESSAGE
The log directory is full. (DBERR 13310).
CAUSE
The log directory allows for 34 log ids (single log names or pairs
of log names in DUAL LOG mode). Any attempt to add the 35th
log will fail. Note that this error can happen during ADDLOG or
during SETUPRECOVERY In SQLUtil. The latter also adds a
log to the log directory.
ACTION
Check the log directory (use the SHOWLOG command for that
purpose) to see if there were any logs that you could have backed
up that you did not. If so, use STORELOG to back up these
logs. Now you have two options. If it was a direct ADDLOG,
then maybe you do not need to ADDLOG any more.
or
If it was an implicit ADDLOG during SETUPRECOVERY, use
the SQLUtil PURGELOG command to purge the backed up log
les BEFORE attempting SETUPRECOVERY again.
13313
13317
MESSAGE
Wrong number of log file names specified. (DBERR 13313)
CAUSE
The ADDLOG command expects either one le name in single
logging mode or two le names in dual logging mode. You may
have tried to enter more or less than the permitted number of
names.
ACTION
Check the logging mode and number of log names you specied.
MESSAGE
DBEnvironment has already finished recovery. (DBERR
13317)
CAUSE
You issued a TerminateRecovery command, but recovery has
already ended.
ACTION
Eliminate the extra TerminateRecovery command.
ALLBASE/SQL Error Messages
3-253
13318
13319
13320
13322
3-254
MESSAGE
Attempted ENDRECOVERY in an inconsistent state. (DBERR
13318)
CAUSE
You are trying to end recovery at a time before the DBEnvironment was consistent after a STOREONLINE operation. When
you enable archive mode with the STOREONLINE command, an
archive checkpoint record is written to the log le after the online
backup is nished. This process can take some time, during which
other DBEnvironment activity continues to be logged. You can
only recover to a point beyond the archive checkpoint record.
ACTION
Do not terminate recovery. Continue to apply more logs through
RECOVERLOG at least until the archive checkpoint record is
reached. At that time, ENDRECOVERY will be successful.
MESSAGE
The specified file is not a log file. (DBERR 13319)
CAUSE
The log le name specied in response to RECOVERLOG is not
an ALLBASE log le.
ACTION
Specify the correct log le name.
MESSAGE
The specified log file does not have the desired sequence
number. (DBERR 13320)
CAUSE
You specied a le name with an inappropriate sequence number.
During RECOVERLOG, the log manager expects log sequence
numbers in order (starting with the number specied in the
DBECon le of the online backup).
ACTION
Specify the log le name with the correct sequence number.
MESSAGE
SETUPRECOVERY is not done. (DBERR 13322)
CAUSE
You attempted a RECOVERLOG or ENDRECOVERY without
rst having done a SETUPRECOVERY.
ACTION
Issue the SETUPRECOVERY command before the
RECOVERLOG or ENDRECOVERY commands.
ALLBASE/SQL Error Messages
13323
13324
13325
13326
13331
MESSAGE
Log does not contain an archive checkpoint. (DBERR 13323)
CAUSE
An archive checkpoint was not written to the log le, so the log
le cannot be used for rollforward recovery.
ACTION
Refer to the ALLBASE/SQL Database Administration Guide
for additional information on archive checkpoints, and to the
ALLBASE/SQL Reference Manual for information on the BEGIN
ARCHIVE and COMMIT ARCHIVE statements.
MESSAGE
Archive mode was never enabled on this DBEnvironment.
(DBERR 13324)
CAUSE
You attempted a SETUPRECOVERY on this DBEnvironment,
but archive mode was never turned on.
ACTION
Check the sequence of operations. Perhaps this log is a
non-archival log, and has always been so. If that is the case, do
not attempt rollforward recovery on this log.
MESSAGE
Log mode specification should be SINGLE or DUAL. (DBERR
13325)
CAUSE
You entered an incorrect log mode in response to a prompt from
SETUPRECOVERY in SQLUtil.
ACTION
Response with either SINGLE or DUAL.
MESSAGE
Specified log id is out of range. (DBERR 13326)
CAUSE
The specied log id is either < 1 or > 35 when you issued either
the PURGELOG or STORELOG command.
ACTION
Use the SHOWLOG command to get the appropriate log id.
MESSAGE
SHOWLOG internal error in computing free log blocks.
(DBERR 13331)
CAUSE
Internal corruption.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
3-255
13338
13339
14024
14027
14028
14029
3-256
MESSAGE
FORMAL Designator is Invalid. (DBERR 13338)
CAUSE
The group and account do not match.
ACTION
Supply the correct MPE/iX group and account name.
MESSAGE
SETUPRECOVERY has already been done (DBERR 13339)
CAUSE
You attempted a SETUPRECOVERY followed by either another
SETUPRECOVERY or by a set of RECOVERLOG commands
and then another SETUPRECOVERY.
ACTION
Remove the extra SETUPRECOVERY command.
MESSAGE
Deadlock detected. (DBERR 14024)
CAUSE
Deadlock was detected between your transaction and another.
Your current transaction was rolled back.
ACTION
Issue your command again.
MESSAGE
Session terminated by DBA. (DBERR 14027)
CAUSE
Your session was terminated by a user with DBA capability.
ACTION
Access the DBE again when the system is available.
MESSAGE
No updates are allowed on a Wrapper DBE. (DBERR 14028)
CAUSE
You attempted to do an operation that would try to update
a wrapper DBEnvironment. No updates are allowed once
the DBEnvironment has been converted to a wrapper
DBEnvironment.
ACTION
Do not try to update the wrapper DBEnvironment.
MESSAGE
Your current transaction was rolled back by DBCore. (DBERR
14029)
CAUSE
Your transaction was rolled back due to another error. An
additional message will be returned.
ACTION
Refer to the cause and action of the additional message.
ALLBASE/SQL Error Messages
14031
14035
14038
14044
14045
MESSAGE
DBCore shared memory access error. (DBERR 14031)
CAUSE
Unable to access DBCore shared memory segments. Your current
transaction was rolled back.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
DBCore shared memory overflow. (DBERR 14035)
CAUSE
There was not enough space in DBCore shared memory to
complete the transaction. Your current transaction was rolled
back.
ACTION
Increase the number of run-time control block pages using the
SQLUtil ALTDBE command and try your transaction again. If
the problem persists, record as much information as possible and
contact your HP Service Representative or Response Center.
MESSAGE
DBCore shared memory allocation failed. (DBERR 14038)
CAUSE
ALLBASE ran out of space for runtime control blocks.
ACTION
Use SQLUtil to increase the number of runtime control block
pages allocated.
MESSAGE
DBCore unable to allocate local heap space. (DBERR 14044)
CAUSE
The application may have too many cursors open at one time.
ACTION
Close cursors as soon as they are no longer needed since they
require a large amount of local heap space.
MESSAGE
Log file corruption detected in DBCore. (DBERR 14045)
CAUSE
Warm start could not nd a checkpoint in any log le.
ACTION
Perform a roll forward recovery.
ALLBASE/SQL Error Messages
3-257
14046
14047
MESSAGE
Log full. (DBERR 14046)
CAUSE
The log le is full. Your current transaction was rolled back.
ACTION
Shut down the database and issue a START DBE NEWLOG
statement.
MESSAGE
Current clock lower than highest in log. (DBERR 14047)
CAUSE
The system clock was set forward incorrectly, used by one or
more databases, and then reset backward.
or
The system clock was set backward incorrectly.
To ensure that recovery works correctly, ALLBASE/SQL requires
that the date/time of the current action is later than the
date/time of the preceding action. If the date/time of the current
action is earlier than the date/time of the previous action (as is
the case when this message is returned), ALLBASE/SQL will not
function until the date/time of the current action is later than the
date/time of the previous action.
ACTION
For example, if the year 1990 is entered instead of 1989, the
database system will wait for a year, unless the action below is
followed.
1. If the system clock was set forward incorrectly, used by
databases, and then set backward, do the following:
a. Kill all database processes.
b. Set the system clock ahead of the incorrect date used by
the data.
c. Back up all the DBEnvironments that were accessed while
the incorrect date was in eect. Use the SQLUtil STORE
command on each DBEnvironment.
d. Shut down the DBEnvironments.
e. Reset the system clock to the correct time.
f. Issue the START DBE NEWLOG statement.
g. Resume operations.
2. If the system clock was set backward incorrectly:
a. Set the system clock forward to the correct time.
b. Resume operations.
Consult your system administrator for assistance in resetting the
system clock.
3-258
ALLBASE/SQL Error Messages
14052
14056
14059
14066
14067
MESSAGE
Failed to start DBCORE. (DBERR 14052)
CAUSE
You are trying to use a command which causes the database to
be started in single user mode, but the database is already being
accessed by other users
ACTION
Make sure all users are logged o the database before you issue
the command that starts the database in single user mode.
MESSAGE
File System Error in DBEnvironment. (DBERR 14056)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
DBCore File Close error. (DBERR 14059)
CAUSE
ALLBASE was not able to close the le. File name may not be
correct.
ACTION
Supply the correct le name.
MESSAGE
DBECon Error - File is invalid. (DBERR 14066)
CAUSE
The DBECon le name specied in the START DBE, START
DBE NEW, or START DBE NEWLOG statement is invalid.
ACTION
Refer to the ALLBASE/SQL Reference Manual for DBECon le
naming conventions.
MESSAGE
DBECon error - File System Error. (DBERR 14067)
CAUSE
Internal error.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
3-259
14071
14072
14073
14074
3-260
MESSAGE
Database already started in single user mode. (DBERR
14071)
CAUSE
You tried to initiate a multi-user session on a single user
DBEnvironment.
ACTION
Ask your database administrator to change the DBECon le user
mode to MULTI.
MESSAGE
Database already started in multi-user mode. (DBERR
14072)
CAUSE
You tried to issue a START DBE or START DBE NEWLOG
statement when someone was already connected to the database.
ACTION
Make sure that no one is currently connected to the
DBEnvironment. The SQLMON OVERVIEW SESSION screen
can be used to see who is connected to the DBEnvironment.
MESSAGE
Attempted to connect to more than one DBEnvironment.
(DBERR 14073)
CAUSE
You tried to connect to a second DBEnvironment while still
connected to another DBEnvironment. Your current transaction
was rolled back.
ACTION
Issue a RELEASE statement to disconnect from the rst
DBEnvironment and then issue a START DBE or CONNECT
statement for the second DBEnvironment.
MESSAGE
DBCore internal error ! - Transaction rolled back. (DBERR
14074) Please record the above message including both
numbers.
CAUSE
An internal error caused your current transaction to be rolled
back.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
14075
14076
14081
MESSAGE
DBCore internal error ! - Rollforward recovery required.
(DBERR 14075) Please record the above message including
both numbers.
CAUSE
An internal error may have caused the DBEnvironment to be
corrupted. Your current transaction was rolled back.
ACTION
Do not perform additional transactions at this time. Contact
your database administrator for rollforward recovery on the
DBEnvironment. Record as much information as possible and
contact your HP Service Representative or Response Center.
MESSAGE
No next log to switch to. (DBERR 14076)
CAUSE
There is no valid log le to change log to.
ACTION
Use ADDLOG to create a new log le then try the
CHANGELOG command again.
MESSAGE
Log directory is empty. (DBERR 14081)
CAUSE
An internal error occurred when you executed the STORELOG
command
or
an internal error occurred when you executed the PURGELOG
command,
or
you specied an invalid logid.
14082
ACTION
Use the SQLUtil SHOWLOG command to verify the logid. If
the log id is correct, record as much information as possible and
contact your HP Service Representative or Response Center.
MESSAGE
Log file cannot be purged - backup pending (DBERR 14082)
CAUSE
You attempted to use the PURGELOG command on a log le
that has not been backed up.
ACTION
Use the STORELOG command to store the log le, and then
purge it.
ALLBASE/SQL Error Messages
3-261
14083
14084
14092
14093
14101
3-262
MESSAGE
Log file is not in use. (DBERR 14083)
CAUSE
Note that the STORELOG command operates in two modes one in which the user may specify a log id and one in which the
user does not. In the latter case, DBCore will simply scan the
log directory looking for the oldest log ready to back up. This
error will occur in the former case where DBCore will look for the
specied slot number in the log directory (the log id is a subscript
into the directory entries). If that slot is currently unoccupied,
this error is generated.
ACTION
Check the log id specied.
MESSAGE
Log file is not ready to be backed up. (DBERR 14084)
CAUSE
You attempted to STORELOG the current log le.
ACTION
The user must wait till this log is no longer current.
MESSAGE
Transaction was externally aborted. (DBERR 14092)
CAUSE
The transaction was aborted by another user.
ACTION
None.
MESSAGE
OMNIBACK/ALLBASE STORE on UX error. (DBERR 14093)
CAUSE
Any of the following could cause the problem: not able to
read/open DBEFILE, not enough space, or DBEFILE to be
restored is already existing.
ACTION
The action depends on what is determined to be the cause. Note
that ALLBASE/SQL no longer supports OMNIBACK as the
backup routine for SQLUtil. Check that the DBEFILE to be
stored can be opened/read. Check that there is enough space to
restore on the disk. For RESTORE, check if the DBEFILE is
already existing.
MESSAGE
Insufficient authorization for DBA operation. (DBERR
14101)
CAUSE
The user does not have the proper authorization.
ACTION
Check the authorization and change if appropriate.
ALLBASE/SQL Error Messages
14102
14103
14200
14201
14202
MESSAGE
DBCORE version mismatch with session already started.
(DBERR 14102)
CAUSE
DBCORE version does not match with the DBCORE for the
session.
ACTION
Check DBCORE versions.
MESSAGE
Current log file cannot be purged. (DBERR 14103)
CAUSE
The le to be purged is in use.
ACTION
Issue the SHOWLOG command in SQLUtil to inquire if the log
le is in use.
MESSAGE
New partition instance found, and the current SCR does not
have any more slots. (DBERR 14200)
CAUSE
This typically happens on a system with a large number of
partition numbers. Further, if this system has switched masterreplicate roles with a number of other systems, it has a large
number of non-empty partitions.
ACTION
The transaction is aborted by ALLBASE/SQL but the
application needs to terminate at this point. Issue a START DBE
NEWLOG with a larger MAXPARTITIONS.
MESSAGE
Multiple database environments updated in the same
transaction. (DBERR 14201)
CAUSE
A transaction attempted to replicate logging against more than
one database id.
ACTION
Check the transaction logic.
MESSAGE
Log full error due to warm standby log scan. (DBERR 14202)
CAUSE
Logging cannot be done because a log lock would be overwritten.
ACTION
Remove the log lock to resume logging.
ALLBASE/SQL Error Messages
3-263
15047
15048
20013
20027
MESSAGE
DBCore internal I/O error - ! (!). (DBERR 15047)
CAUSE
An unexpected le system write error occurred during a
transaction. Your current transaction was rolled back.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description,
and contact your system administrator to check for possible disk
drive physical I/O problems.
MESSAGE
DBCore internal I/O error - ! (!). (DBERR 15048)
CAUSE
An unexpected le system write error occurred during a
transaction. Your current transaction was rolled back.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description,
and contact your system administrator to check for possible disk
drive physical I/O problems.
MESSAGE
*** Installation error detected. Check permissions and
owner. (DBERR 20013)
CAUSE
The permissions, owner, or group of /usr/bin/sqlmig are
incorrect.
ACTION
Change the attributes of /usr/bin/sqlmig so that the permission
is 4555, the owner is hpdb, and the group is bin.
MESSAGE
*** Cannot update DBECON file. (! !, !, !, !) (DBERR
20027)
CAUSE
20030
3-264
A le system error was encountered.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
*** Cannot purge log file /tmp/SQLMIG.(! !, !, !) (DBERR
20030)
CAUSE
A le system error was encountered when trying to purge the le
named /tmp/SQLMIGxxxxxx. (The string xxxxxx is unique for
each run of SQLMigrate.)
ACTION
Take the necessary steps to purge this le before reattempting the
SQLMigrate command which caused this error.
ALLBASE/SQL Error Messages
20031
20032
20034
20035
20036
MESSAGE
Cannot purge existing user log file (! !, !, !) (DBERR
20031)
CAUSE
An error occurred while trying to purge a log le named in the
DBECon le. It may not exist on the system where the migration
is being performed. The ownership or le mode of the log le, or
the directory that contains the log le, may be incorrect.
ACTION
Check that user hpdb (uid 27) has at least read and write
permission to the directories that contain the database and log
les. Check that all database and log les are owned by hpdb,
and have a le mode of 600 (-rw- - - - - - -). If necessary, contact
your system administrator. Because the log le could not be
purged, SQLMigrate did not attempt to execute the START DBE
NEWLOG command. The migration has completed successfully, but
you will not be able to use the DBEnvironment until you have
run ISQL and issued a START DBE NEWLOG command.
MESSAGE
*** Cannot purge DBECON file. (! !, !) (DBERR 20032)
CAUSE
A le system error was encountered.
ACTION
Refer to the system administration manual.
MESSAGE
*** Cannot start DBCore. (RC !, !, !, !) (DBERR 20034)
CAUSE
An unexpected error occurred while trying to establish a single
user session with the DBEnvironment.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
*** DBCore error. (FNC !, RC !, !, !, !) (DBERR 20035)
CAUSE
An unexpected internal error was encountered.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Unexpected INTERNAL error (!, !, !, !) (DBERR 20036)
CAUSE
An unexpected internal error was encountered.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
3-265
20040
20041
20042
20043
20044
20045
3-266
MESSAGE
*** Cannot open expanded DBECON file. (errno !) (DBERR
20040)
CAUSE
A le system error was encountered.
ACTION
Refer to the system administration manual.
MESSAGE
*** Cannot close expanded DBECON file. (! !, !) (DBERR
20041)
CAUSE
A le system error was encountered.
ACTION
Refer to the system administration manual.
MESSAGE
*** Cannot purge expanded DBECON file. (! !, !) (DBERR
20042)
CAUSE
A le system error was encountered.
ACTION
Refer to the system administration manual.
MESSAGE
*** Cannot write to expanded DBECON file. (! !, !) (DBERR
20043)
CAUSE
A le system error was encountered.
ACTION
Refer to the system administration manual.
MESSAGE
*** Cannot rename DBECON file to BBSQLMIG file. (! !, !)
(DBERR 20044)
CAUSE
A le system error was encountered.
ACTION
Refer to the system administration manual.
MESSAGE
*** Cannot allocate expanded DBECON file. (! !, !) (DBERR
20045)
CAUSE
A le system error was encountered. There probably is not
enough extra disk space on your system.
ACTION
Refer to the system administration manual. Try to create more
free disk space before using SQLMigrate again.
ALLBASE/SQL Error Messages
20046
20047
20048
20049
20050
20051
MESSAGE
*** Cannot open BBSQLMIG file. (! !, !) (DBERR 20046)
CAUSE
A le system error was encountered when trying to create a le
named BBSQLMIG in the same directory as the DBECon le. It
probably already exists.
ACTION
Refer to the /usr/include/sys/errno.h le. Remove any les
named BBSQLMIG from the same directory as the DBECon le
before using SQLMigrate again.
MESSAGE
*** Cannot close BBSQLMIG file. (! !, !) (DBERR 20047)
CAUSE
A le system error was encountered.
ACTION
Refer to the system administration manual.
MESSAGE
*** Cannot purge BBSQLMIG file. (! !, !) (DBERR 20048)
CAUSE
A le system error was encountered.
ACTION
Refer to the system administration manual.
MESSAGE
*** Cannot write to BBSQLMIG file. (! !, !) (DBERR 20049)
CAUSE
A le system error was encountered.
ACTION
Refer to the system administration manual.
MESSAGE
*** Cannot rename BBSQLMIG file to DBECON file. (! !, !)
(DBERR 20050)
CAUSE
A le system error was encountered.
ACTION
Refer to the system administration manual.
MESSAGE
*** Illegal command. (DBERR 20051)
CAUSE
SQLMigrate did not recognize the command that was entered.
ACTION
Use the HELP command or refer to the ALLBASE/SQL
Database Administration Guide to determine the valid
SQLMigrate commands.
ALLBASE/SQL Error Messages
3-267
20052
20053
20054
20055
20056
3-268
MESSAGE
Input too long. Maximum length is !. (DBERR 20052)
CAUSE
The total length of the input line exceeded the allowed limit.
ACTION
Issue the command again.
MESSAGE
*** Input limit reached. No semicolon found. (DBERR
20053)
CAUSE
SQLMigrate commands must be terminated with a semicolon.
None was found in the input string submitted.
ACTION
Issue the command again.
MESSAGE
*** Unexpected semicolon found. (DBERR 20054)
CAUSE
A semicolon was found in the input string in an unexpected
location. Semicolons are allowed either: 1) at the end of the
command or 2) in the DBEnvironmentName, when the operating
system le naming convention allows it.
ACTION
Issue the command again without the illegal semicolon.
MESSAGE
*** Unexpected end of input. (DBERR 20055)
CAUSE
An error was encountered trying to retrieve the next command.
ACTION
Check the output and input to determine if all commands
executed properly.
MESSAGE
*** Illegal syntax. (DBERR 20056)
CAUSE
Command was entered incorrectly.
ACTION
Issue the command again. You can use the HELP command to
verify your syntax.
ALLBASE/SQL Error Messages
20070
20080
20200
20201
MESSAGE
*** SQLMIGRATE log file (AASQLMIG) already exists. (DBERR
20070)
CAUSE
AASQLMIG, a temporary le used by SQLMigrate, already
exists in the same location as the DBECON le. Another user is
probably running SQLMigrate on another DBEnvironment at the
same time.
ACTION
Try again later.
MESSAGE
*** Cannot create BBSQLMIG file. (! !, !) (DBERR 20080)
CAUSE
BBSQLMIG, a temporary le used by SQLMigrate, already
exists in the same location as the DBECON le. Another user is
probably running SQLMigrate on another DBEnvironment at the
same time.
ACTION
Try again later.
MESSAGE
*** Invalid target version. Use the SHOW VERSIONS
command. (DBERR 20200)
CAUSE
The release of SQLMigrate being used does not support the
version that was specied in the last command.
ACTION
Use the SHOW VERSIONS command to determine the valid
versions that may be used with this release of SQLMigrate.
MESSAGE
*** DBEnvironmentName is too long. Maximum length is !.
(DBERR 20201)
CAUSE
A DBEnvironmentName is restricted to operating system le
naming conventions.
ACTION
Refer to the A Beginner's Guide to HP-UX for information on le
naming conventions.
ALLBASE/SQL Error Messages
3-269
20202
20203
20204
20205
3-270
MESSAGE
*** Cannot MIGRATE FORWARD to earlier version. (DBERR
20202)
CAUSE
A logic error was encountered in the command. The keyword
FORWARD is only used when migrating an older version
DBEnvironment to one that is compatible with a newer release of
ALLBASE/SQL.
ACTION
Either change the keyword FORWARD to BACKWARD, or
change the target version. Issue the command again.
MESSAGE
*** Cannot MIGRATE BACKWARD to later version. (DBERR
20203)
CAUSE
A logic error was encountered in the command. The keyword
BACKWARD is only used when migrating a newer version
DBEnvironment to one that is compatible with an older release of
ALLBASE/SQL.
ACTION
Either change the keyword BACKWARD to FORWARD, or
change the target version. Issue the command again.
MESSAGE
*** Cannot PREVIEW FORWARD to earlier version. (DBERR
20204)
CAUSE
A logic error was encountered in the command. The keyword
FORWARD is only used when previewing an older version
DBEnvironment to one that is compatible with a newer release of
ALLBASE/SQL.
ACTION
Either change the keyword FORWARD to BACKWARD, or
change the target version. Issue the command again.
MESSAGE
*** Cannot PREVIEW BACKWARD to later version. (DBERR
20205)
CAUSE
A logic error was encountered in the command. The keyword
BACKWARD is only used when previewing a newer version
DBEnvironment to one that is compatible with an older release of
ALLBASE/SQL.
ACTION
Either change the keyword BACKWARD to FORWARD, or
change the target version. Issue the command again.
ALLBASE/SQL Error Messages
20206
20207
20208
20209
20210
MESSAGE
*** DBEnvironment is already compatible with target
version. (DBERR 20206)
CAUSE
The version of the DBEnvironment is already the same as the
target version of the command.
ACTION
If the target version was incorrectly specied, modify it and issue
the command again.
MESSAGE
*** Existing DBEnvironment not supported by SQLMigrate
(DBERR 20207)
CAUSE
The release of SQLMigrate being used does not support
migrations for the DBEnvironment specied in the command.
ACTION
Contact your HP Service Representative or Response Center to
determine if another release of SQLMigrate is available that will
migrate your DBEnvironment.
MESSAGE
*** DBEnvironment version is not recognized by
SQLMigrate. (!) (DBERR 20208)
CAUSE
The release of SQLMigrate being used does not recognize the
version number of your DBEnvironment, and cannot support
migrations for it.
ACTION
Contact your HP Service Representative or Response Center to
determine if another release of SQLMigrate is available that will
migrate your DBEnvironment.
MESSAGE
*** DBEFileName is too long. Maximum length is !. (DBERR
20209)
CAUSE
The allowable length for the DBEFileName was exceeded.
ACTION
Issue the command again, using a valid DBEFileName.
MESSAGE
*** SystemFileName name is too long. Maximum length is !.
(DBERR 20210)
CAUSE
The allowable length for the SystemFileName was exceeded.
ACTION
Issue the command again, using a valid SystemFileName.
ALLBASE/SQL Error Messages
3-271
20211
3-272
MESSAGE
*** Migration path is not supported by SQLMIGRATE
(!,!).(DBERR 20211)
CAUSE
SQLMigrate can only be used for a migration path to/from the
release of ALLBASE/SQL on which SQLMigrate came. The
attempted migration was for a path that did not involve the
current release of ALLBASE/SQL.
ACTION
Specify a valid migration path.
ALLBASE/SQL Error Messages
20220
MESSAGE
Log full. (DBERR 20220)
CAUSE
The log le is full.
ACTION
If you see this message, you should notify your HP Service
Representative or Response Center, because a problem probably
exists in SQLMIGRATE.
During the MIGRATE, PREVIEW, CREATE DBEFILE,
and ADD DBEFILE commands, SQLMIGRATE \connects"
to the DBEnvironment by performing a START DBE
NEWLOG command using a temporary log le. On MPE/iX,
the le is named \AASQLMIG" and is created in the same
group as the DBECON le. On HP-UX, the le is named
\/tmp/AASQLMIGxxxxxx", where \xxxxx" is a unique id for
each SQLMIGRATE process.
SQLMIGRATE needs to create it's own log le for several
reasons, but the most important ones are 1) the existing log
le(s) may not be compatible with the newest release, and 2)
the existing log le(s) may not have enough free space on them.
SQLMIGRATE creates the log in non-archive mode (so it is
circular), and tries to use it eciently so that a log full condition
does not occur.
As a workaround, you can increase the size of the temporary log
le (the default size is 400 pages) by issuing one of the following
before running SQLMIGRATE:
On MPE/iX:
: setjcw MIGLOGSZ 1000
On HP-UX (csh):
% setenv MIGLOGSZ 1000
On HP-UX (sh or ksh):
$ MIGLOGSZ=1000
$ export MIGLOGSZ
In the examples above, the size of the temporary log le will be
1000 pages. Set the MIGLOGSZ variable to the value needed to
accomplish a migration for your DBEnvironment.
20330
MESSAGE
ERROR - DBEFileName already exists in !. (DBERR 20330)
CAUSE
A row exists in SYSTEM.DBEFILE which has a DBEFNAME
that is the same as the DBEFileName that was specied.
ACTION
Issue the CREATE DBEFILE statement again, using a dierent
DBEFileName.
ALLBASE/SQL Error Messages
3-273
20335
20336
20340
20350
20360
3-274
MESSAGE
ERROR - DBEFILE size is too small. Minimum size is !.
(DBERR 20335)
CAUSE
The \WITH PAGES = " parameter did not meet minimum
requirements.
ACTION
Issue the CREATE DBEFILE statement again, using a larger
value in the \WITH PAGES = " parameter.
MESSAGE
ERROR - DBEFILE size is too large. Maximum size is !
(DBERR 20336)
CAUSE
The \WITH PAGES = " parameter exceeded maximum
requirements.
ACTION
Issue the CREATE DBEFILE statement again, using a smaller
value in the \WITH PAGES = " parameter.
MESSAGE
ERROR - SystemFileName already exists. (DBERR 20340)
CAUSE
Either the SystemFileName already exists as a physical le, or a
row exists in SYSTEM.DBEFILE which has a FILEID that is the
same as the SystemFileName.
ACTION
Use a dierent SystemFileName, and issue the CREATE
DBEFILE statement again.
MESSAGE
ERROR - DBEFileName has not been CREATED in !. (DBERR
20350)
CAUSE
You issued an ADD DBEFILE statement before a CREATE
DBEFILE statement had been issued.
ACTION
Issue the CREATE DBEFILE statement, and then issue the
ADD DBEFILE command again.
MESSAGE
ERROR - DBEFileName has already been ADDED to a
DBEFILESET. (DBERR 20360)
CAUSE
The row for DBEFileName in SYSTEM DBEFILE indicates that
the DBEFSNAME has already been assigned.
ACTION
The name specied in the ADD DBEFILE statement was
probably incorrect. Modify it, and issue the command again.
ALLBASE/SQL Error Messages
20518
20520
20530
MESSAGE
ERROR - User is not DBECreator. (DBERR 20518)
CAUSE
Only the DBECreator or the superuser is authorized to use
SQLMigrate.
ACTION
Contact someone having the proper capabilities to use
SQLMigrate.
MESSAGE
ERROR - Invalid DBECON file format detected. (DBERR
20520)
CAUSE
Migration is not supported for this DBEnvironment using
SQLMigrate.
ACTION
UNLOAD and LOAD your data to install another release of
ALLBASE/SQL.
MESSAGE
ERROR - Previous failed attempt to MIGRATE detected.
(DBERR 20530)
CAUSE
SQLMigrate was used is the past to migrate the DBEnvironment,
but the migration was unsuccessful.
ACTION
Purge the DBEnvironment and restore the backup version before
attempting migration again.
ALLBASE/SQL Error Messages
3-275
22540
MESSAGE
ERROR - Insufficient space in the SYSTEM DBEFileSet.
(DBERR 22540)
DBEFile(s) containing ! pages need to be added to the
SYSTEM DBEFileSet before attempting the migration.
CAUSE
The space estimate calculated during the PREVIEW command
indicates that more space is needed for the migration than is
currently present in the SYSTEM DBEFileSet.
ACTION
Issue a CREATE DBEFILE statement followed by an ADD
DBEFILE statement to add space to the SYSTEM DBEFileSet.
If you are concerned about the amount of additional space
being added, CREATE and ADD multiple small DBEFiles,
rather than one large one. After the migration is complete,
perform an UPDATE STATISTICS on SYSTEM.TABLE. Review
SYSTEM.DBEFILE to determine the empty DBEFiles in the
SYSTEM DBEFileset, and remove them. Remember to leave
about 20% of the pages free for the temporary processing needs of
ALLBASE/SQL.
22800
23005
3-276
MESSAGE
DBEnvironment has already been started (DBERR 22800)
CAUSE
A REPAIR command was in progress when this message was
issued. Another user is currently accessing the DBEnvironment.
The REPAIR command may only be issued when the database is
idle.
ACTION
Please try again later.
MESSAGE
START DBE NEWLOG disallowed. Need rollforward recovery.
(DBERR 23005)
CAUSE
SQLMIG cannot be used on a DBEnvironment that has
incomplete transactions in its log. You probably did not follow
the steps required for forward migration, which are documented
in the \DBA Tasks and Tools" chapter of the ALLBASE/SQL
Database Administration Guide .
ACTION
Restore the old version of the operating system and the old
version of ISQL onto your machine. Run the old version of ISQL
and issue a START DBE statement to resolve the incomplete
transactions in the log.
ALLBASE/SQL Error Messages
25000
26002
26003
26004
26005
26006
MESSAGE
System error in Listener on the server node. (HP-UX errno
!) (DBERR 25000)
CAUSE
An HP-UX error occurred within the listener.
ACTION
Refer to the usr/include/errno.h le for an error description.
MESSAGE
No matching profile found in the NETUsers file. (DBERR
26002)
CAUSE
ALLBASE/SQL attempted to connect to a remote DBEnvironment. Two error messages may be displayed. This is the second
message and indicates that the NETUser prole either does not
exist or was entered incorrectly in the NETUsers le.
ACTION
Add the NETUser name to the NETUsers le or use the SHOW
USER command to check for correct spelling of NETUser names
in the NETUsers le.
MESSAGE
New value(s) already exists in NETUsers file, operation
not performed. (DBERR 26003)
CAUSE
The NETUser name you specied is already in the NETUsers le.
ACTION
Enter a unique NETUser name.
MESSAGE
Lock on NETUsers file failed. (! !) (DBERR 26004)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Unlock on NETUsers file failed. (! !) (DBERR 26005)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Read failed on NETUsers file. (! !) (DBERR 26006)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
ALLBASE/SQL Error Messages
3-277
26007
26008
26009
26010
26011
3-278
MESSAGE
Write failed on NETUsers file. (! !) (DBERR 26007)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
File system error on NETUsers file. (! !) (DBERR 26008)
CAUSE
ALLBASE/SQL attempted to connect to a remote DBEnvironment. Two error messages may be displayed. This is the second
message and indicates that there is no NETUsers le or that the
permissions are not set correctly.
ACTION
If the DBEnvironment you want to connect to is on the local
node, check the spelling of the DBEnvironment name. If the
DBEnvironment you want to connect to is on a remote node,
have the system administrator set up the NETUsers le.
MESSAGE
The NETUsers file is empty. (DBERR 26009)
CAUSE
You tried to \show" proles in an empty NETUsers le. Proles
in the NETUsers le have been deleted.
ACTION
Contact the system administrator to add proles to the
NETUsers le.
MESSAGE
Open failed on temporary NETUsers file. (! !) (DBERR
26010)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Write failed on temporary NETUsers file. (! !) (DBERR
26011)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
ALLBASE/SQL Error Messages
26012
26013
27002
MESSAGE
Insufficient memory to allocate buffer. (DBERR 26012)
CAUSE
There is not enough memory to allocate buer space for a new
prole.
ACTION
Do not complete the operation. Record as much information as
possible and contact your HP Service Representative or Response
Center.
MESSAGE
The NETUsers file is being accessed. Operation could not
be performed. (DBERR 26013)
CAUSE
The NETUsers le is currently open by someone else and cannot
be deleted.
ACTION
Try again later.
MESSAGE
No matching profile found in the AliasDB file. (DBERR
27002)
CAUSE
ALLBASE/SQL attempted to connect to a remote
DBEnvironment. Two error messages may be displayed. This is
the second message and indicates that the alias prole either does
not exist or was entered incorrectly in the AliasDB le.
If this is the only error message returned, you are using a diskless
machine to access a DBEnvironment on another machine.
27003
ACTION
Ask the system administrator to enter an alias prole in the
AliasDB le or check the spelling of the DBEnvironment name
in the AliasDB le. For more information on conguring
ALLBASE/NET in order to access a remote DBEnvironment,
refer to the ALLBASE/NET User's Guide
MESSAGE
New value(s) already exists in AliasDB file, operation not
performed. (DBERR 27003)
CAUSE
The alias name which you are trying to add or change already
exists in the AliasDB le.
ACTION
Enter a unique alias name.
ALLBASE/SQL Error Messages
3-279
27004
27005
27006
27007
27008
27009
3-280
MESSAGE
Lock on AliasDB file failed. (! !) (DBERR 27004)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Unlock on AliasDB file failed. (! !) (DBERR 27005)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Read failed on AliasDB file. (! !) (DBERR 27006)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Write failed on AliasDB file. (! !) (DBERR 27007)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
File system error on AliasDB file. (! !) (DBERR 27008)
CAUSE
ALLBASE/SQL attempted to connect to a remote
DBEnvironment. Two error messages may be displayed. This is
the second message and indicates that there is no AliasDB le or
that the permissions are not set correctly.
ACTION
If the DBEnvironment you want to connect to is on the local
node, check the spelling of the DBEnvironment name. If the
DBEnvironment you want to connect to is on a remote node,
have the system administrator set up the AliasDB le.
MESSAGE
The AliasDB file is empty. (DBERR 27009)
CAUSE
You tried to \show" proles from an empty AliasDB le. Proles
in the AliasDB le have been deleted.
ACTION
Contact the system administrator.
ALLBASE/SQL Error Messages
27010
27011
28001
28002
28003
28004
MESSAGE
Open failed on temporary AliasDB file. (! !) (DBERR
27010)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Write failed on temporary AliasDB file. (! !) (DBERR
27011)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Invalid NETUtil command. (DBERR 28001)
CAUSE
An invalid command was entered.
ACTION
Type HELP for a list of valid NETUtil commands.
MESSAGE
Insufficient capability, command disallowed. (DBERR
28002)
CAUSE
You must have superuser capability to execute this command. A
non-superuser can use only the EXIT, HELP, QUIT, SHOW ALIAS,
and SYSTEM commands.
ACTION
Ask the system administrator to execute the command.
MESSAGE
Open failed on NETUsers file. (! !) (DBERR 28003)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Open failed on AliasDB file. (! !) (DBERR 28004)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
ALLBASE/SQL Error Messages
3-281
28005
28006
28007
28008
28009
28010
3-282
MESSAGE
Backup failed on NETUsers file. (! !) (DBERR 28005)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Backup failed on AliasDB file. (! !) (DBERR 28006)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Read failed on message catalog. (! !) (DBERR 28007)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Invalid Machine Type. (! !) (DBERR 28008)
CAUSE
An invalid machine type was entered. Valid machine types are
HP 3000 S900, HP 9000 S800, or HP 9000 S300.
ACTION
Re-enter the machine type.
MESSAGE
Invalid Datacom Type. (DBERR 28009)
CAUSE
You entered an invalid data communication type. The data
communication type must be NS or ARPA.
ACTION
Re-enter the data communication type.
MESSAGE
Invalid Database Server Type. (DBERR 28010)
CAUSE
You entered an invalid database management system type.
Currently, the only valid database management system is
ALLBASE/SQL.
ACTION
Re-enter the database management system type.
ALLBASE/SQL Error Messages
28011
28012
28019
28020
28022
28024
MESSAGE
The AliasDB file has not been created. (DBERR 28011)
CAUSE
The AliasDB le does not exist.
ACTION
Ask the system administrator to use the ADD ALIAS command
to create the AliasDB le.
MESSAGE
Name cannot start with the wildcard character. (DBERR
28012)
CAUSE
You tried to add a name to the AliasDB le or NETUsers le
beginning with an '*'.
ACTION
Re-enter the AliasName or NETUser name without the wildcard
character.
MESSAGE
Name is too long. (DBERR 28019)
CAUSE
You entered a DBEnvironment name, node name or login name in
the AliasDB or NETUsers le which was too long.
ACTION
Enter the name again. The maximum length for a
DBEnvironment name is 128 bytes; the maximum length for a
node name is 256 bytes; and the maximum length for a login
name is 56 bytes.
MESSAGE
Database server type must be ALLBASE/SQL. (DBERR 28020)
CAUSE
You entered an invalid database server type.
ACTION
Re-enter a valid database server type.
MESSAGE
Machine type must be HP9000 {S300, S400, S700 or S800} or
HP3000 S9000. S900. (DBERR 28022)
CAUSE
You entered an invalid machine type.
ACTION
Re-enter a valid machine type.
MESSAGE
Datacomm type must be ARPA or NS. (DBERR 28024)
CAUSE
You entered an invalid datacomm type.
ACTION
Re-enter a valid datacomm type.
ALLBASE/SQL Error Messages
3-283
28028
28029
28030
28031
28032
28033
3-284
MESSAGE
Datacomm type must be ARPA. (DBERR 28028)
CAUSE
ARPA is the only valid datacomm type if the client and/or server
is running HP-UX 10.0 or greater.
ACTION
Change datacomm type to ARPA.
MESSAGE
Cannot migrate alias (!) for server (!). (DBERR 28029)
CAUSE
ACTION
This error could occur due to the following reasons :
1. Client and/or server already has HP-UX 10.0 installed.
2. Release patch was not installed.
3. Remote loopback was not enabled on the server.
The actions correspond to the above causes.
1. Use manual migration.
2. Install release patch from IND or use manual migration.
3. Enable remote loopback on the server or use manual
migration.
MESSAGE
Cannot migrate NETUsers file backward. (DBERR 28030)
CAUSE
No previous migration of NETUsers le has occurred.
ACTION
No action is necessary.
MESSAGE
Cannot migrate AliasDB file backward. (DBERR 28031)
CAUSE
No previous migration of AliasDB le has occurred.
ACTION
No action is necessary.
MESSAGE
Cannot migrate client login (!) for client node name (!).
(DBERR 28032)
CAUSE
An error occurred attempting to migrate client prole.
ACTION
Check previous error message, which indicates where error
occurred during migration.
MESSAGE
Open failed on log file. (! !) (DBERR 28033)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
ALLBASE/SQL Error Messages
28034
28035
28036
28037
28038
28039
28040
MESSAGE
Lock failed on log file. (! !) (DBERR 28034)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Unlock failed on log file. (! !) (DBERR 28035)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Write failed on log file. (! !) (DBERR 28036)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Open failed on server list file. (! !) (DBERR 28037)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Lock failed on server list file. (! !) (DBERR 28038)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Unlock failed on server list file. (! !) (DBERR 28039)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Write failed on server list file. (! !) (DBERR 28040)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
ALLBASE/SQL Error Messages
3-285
28041
29001
29002
29003
29004
3-286
MESSAGE
Backup failed (! !) on file !. (DBERR 28041)
CAUSE
An HP-UX le system error occurred.
ACTION
Refer to the /usr/include/sys/errno.h le for an error description.
MESSAGE
Invalid message type received. (DBERR 29001)
CAUSE
An internal error occurred. The client node or the server node
received an invalid message type.
ACTION
Contact your HP Service Representative or Response Center.
MESSAGE
Insufficient memory to allocate buffer for message.
(DBERR 29002)
CAUSE
There is not enough memory to allocate a buer for the outgoing
message.
ACTION
Try again later.
MESSAGE
CONNECT or START DBE command expected. (DBERR 29003)
CAUSE
A CONNECT or START DBE statement is expected.
ACTION
Add the appropriate statement to the application.
MESSAGE
The ALLBASE/SQL and ALLBASE/NET software on the server
machine are older than the ALLBASE/SQL and ALLBASE/NET
software on the client machine. (DBERR 29004)
CAUSE
You are running incompatible releases of ALLBASE/SQL and
ALLBASE/NET on the client and server machines.
ACTION
Ensure that the release of ALLBASE/NET and ALLBASE/SQL
on your client node is not more recent than the software on the
server node.
ALLBASE/SQL Error Messages
29005
29010
29011
29440
29441
MESSAGE
Cannot create a DBE or new log files from a diskless node
(DBERR 29005)
CAUSE
You have executed a START DBE NEW or START DBE
NEWLOG statement from a diskless node.
ACTION
Create the DBE or new log les on the server node in the diskless
cluster. Then set up ALLBASE/NET to remotely access the
database from the diskless node.
MESSAGE
Invalid SQLX message buffer pointer. (DBERR 29010)
CAUSE
An ALLBASE/SQL internal error was encountered.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Unsupported remote command. (DBERR 29011)
CAUSE
The command is not supported by ALLBASE/NET.
ACTION
Refer to the ALLBASE/NET User's Guide for a list of supported
commands.
MESSAGE
Incorrect machine type in AliasDB file. (DBERR 29440)
CAUSE
You are trying to access an HP3000 system but your AliasDB le
specied an HP 9000 system.
ACTION
Change the machine type eld of the AliasDB le prole to \HP
3000 S900."
MESSAGE
Security violation detected on server machine. (DBERR
29441)
CAUSE
Security violation on the server.
ACTION
Check the server.
ALLBASE/SQL Error Messages
3-287
30000
MESSAGE
Datacommunication NS failure. NetIPC Error Code (!).
(DBERR 30000)
CAUSE
NetIPC returned an error. Some NetIPC errors which have been
mapped to DBERRs are listed here:
30004 NetIPC Error: Network transport not initialized.
(DBERR 30004)
30009 NetIPC Error: Protocol is not active. (DBERR 30009)
30015 NetIPC Error: Attempt to exceed limit of sockets per
process. (DBERR 30015)
30016 NetIPC Error: Out of path descriptors or
extensions. (DBERR 30016)
30031 NetIPC Error: Duplicate socket name. (DBERR 30031)
30036 NetIPC Error: Table of names is full. (DBERR 30036)
30037 NetIPC Error: Socket name not found. (DBERR 30037)
30040 NetIPC Error: Unknown node. (DBERR 30040)
30043 NetIPC Error: Unable to contact remote registry
server. (DBERR 30043)
30044 NetIPC Error: No response from remote registry
server. (DBERR 30044)
30055 NetIPC Error: Exceeded socket limit. (DBERR 30055)
30059 NetIPC Error: Socket timeout. (DBERR 30059)
30064 NetIPC Error: Remote protocol module aborted
connection. (DBERR 30064)
30065 NetIPC Error: Local protocol module aborted
connection. (DBERR 30065)
30067 NetIPC Error: Connection failure detected. (DBERR
30067)
30068 NetIPC Error: Received graceful release of
connection. (DBERR 30068)
30110 NetIPC Error: Unanticipated protocol error. (DBERR
30110)
30116 NetIPC Error: Destination unreachable. (DBERR
30116)
30117 NetIPC Error: Attempt to establish connection
failed. (DBERR 30117)
30118 NetIPC Error: Incompatible version. (DBERR 30118)
30131 NetIPC Error: Protocol module does not have
sufficient resources. (DBERR 30131)
30158 NetIPC Error: Connection request rejected by
remote. (DBERR 30158)
ACTION
3-288
Refer to the NetIPC Error Codes in the HP 9000 NetIPC
Programmer's Guide .
ALLBASE/SQL Error Messages
31000
31004
31009
31014
31022
31023
MESSAGE
Datacommunication BSD failure. (DBERR 31000)
CAUSE
A data communication error occurred.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
The connect sequence was interrupted before completion.
(DBERR 31004)
CAUSE
The connect sequence could not be completed.
ACTION
Restart the application.
MESSAGE
Invalid virtual circuit descriptor. (DBERR 31009)
CAUSE
An internal error occurred. The internal virtual circuit descriptor
is not the one from the successful connect call.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Invalid data pointer specified in ARPA sockets call.
(DBERR 31014)
CAUSE
An internal error occurred.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Invalid parameter specified in ARPA sockets call. (DBERR
31022)
CAUSE
An internal error occurred.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
The system's table of open files is full. (DBERR 31023)
CAUSE
The socket call cannot be accepted because the system's table is
full.
ACTION
Try to connect again later.
ALLBASE/SQL Error Messages
3-289
31024
31032
31216
31219
31221
3-290
MESSAGE
The peer-process descriptor table is full. (DBERR 31024)
CAUSE
The socket call cannot be accepted because the application's open
le exceeds the per-process limit.
ACTION
Close some les, then try to connect again.
MESSAGE
The send cannot be completed, because the connection has
been shutdown either by the remote peer or by the client
process. (DBERR 31032)
CAUSE
A data communication error occurred or the peer process does
not exist.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
The virtual circuit descriptor is a file, not a socket.
(DBERR 31216)
CAUSE
An internal error occurred.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
The type of socket and protocol do not match. (DBERR
31219)
CAUSE
An internal error occurred.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
The specified protocol is not supported. (DBERR 31221)
CAUSE
An internal error occurred.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
31222
31223
31225
31226
31227
MESSAGE
The specified socket type is not supported. (DBERR 31222)
CAUSE
An internal error occurred.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
ARPA network services have not been installed on this
system. (DBERR 31223)
CAUSE
An attempt has been made to access a remote database from a
system where networking services have not been installed.
ACTION
Install networking services on the system.
MESSAGE
The specified address family is not supported. (DBERR
31225)
CAUSE
An internal error occurred.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
The address is already in use. (DBERR 31226)
CAUSE
You tried to start the listener daemon, but it has already been
started.
ACTION
No action necessary.
MESSAGE
The specified address is not available. (DBERR 31227)
CAUSE
The /etc/hosts le is not set up correctly or there is an data
communication error
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
3-291
31229
31232
31233
31235
31238
3-292
MESSAGE
The network cannot be reached from this host. (DBERR
31229)
CAUSE
The network has not been set up.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
The connection was reset by peer process. (DBERR 31232)
CAUSE
A data communication error occurred or the peer process was
terminated.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Insufficient resources available to complete socket
operation. (DBERR 31233)
CAUSE
The cause depends on which ARPA sockets function called failed.
However, this error is an indication that there are not enough
system resources available to complete the system call.
ACTION
Try again later.
MESSAGE
The socket is not connected or the socket has not completed
the connect sequence with its peer. (DBERR 31235)
CAUSE
The application ignored the error message from the connect call
and continued to run the application which caused the internal
usage of the descriptor from the failed call.
ACTION
Check the application error messages. Try to connect after
correcting the error.
MESSAGE
The connection timed out due to a transmission timeout.
(DBERR 31238)
CAUSE
Internal timeout reached.
ACTION
Try to connect again.
ALLBASE/SQL Error Messages
31239
31241
31243
31900
31992
MESSAGE
The attempt to connect to a remote system was rejected.
(DBERR 31239)
CAUSE
An internal error occurred. The listener daemon is down.
ACTION
Remove the tmp/hpdaARPA.log or the tmp/hpdaNS.log le
and restart the listener daemon. Verify that the ARPA listener
is running. Refer to the ALLBASE/NET User's Guide for
more information. If this does not solve the problem, record
as much information as possible and contact your HP Service
Representative or Response Center.
MESSAGE
The server node is down. (DBERR 31241)
CAUSE
Unable to communicate with the server.
ACTION
Reboot the system. If this does not solve the problem record
as much information as possible and contact your HP Service
Representative or Response Center.
MESSAGE
Hardware error on interface card. (DBERR 31243)
CAUSE
There is a hardware error on the interface card.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Invalid login in NETUsers file. (DBERR 31900)
CAUSE
Incorrect syntax for server login in NetUsers le.
ACTION
Check 'Idtfy clnt INVALID LOGIN' message in server log le
hpdanslg.pub.sys for server login used. Run NETUtil to correct
server login.
MESSAGE
Corresponding ALLBASE/NET error not found for error (!)
(DBERR 31992)
CAUSE
An error number has been generated that cannot be handled by
the client.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
3-293
31994
31995
MESSAGE
No entry found in password file on server node. (DBERR
31994)
CAUSE
The user name you specied by the PC API logon is not dened
on this server.
ACTION
Verify that the user name sent by the PC is the correct user
name. If it is the correct user name, add it to the server's
password le.
MESSAGE
Hostname not found or the hosts file cannot be opened.
(DBERR 31995)
CAUSE
The hostname cannot be found in the /etc/hosts le or the
/etc/hosts le does not exist.
ACTION
Check the hosts le for the correct hostname. Make sure it is
spelled correctly in the AliasDB le.
or
ask the system administrator to set up the le.
31996
31997
3-294
MESSAGE
The protocol file cannot be opened or the protocol name
'tcp' is not found. (DBERR 31996)
CAUSE
The /etc/protocols le does not exist or 'tcp' is not in the
/etc/protocols le.
ACTION
Ask the system administrator to set up the le or to correct the
le. Refer to the LAN installation manual for information on this
le.
MESSAGE
The services file cannot be opened or the profile for
'DAServer' is not in the services file. (DBERR 31997)
CAUSE
The /etc/services does not exist or the denition of the
ALLBASE/SQL RDA server is not in the /etc/services le.
ACTION
Ask the system administrator to set up the services le or
to correct the le. Refer to the LAN installation manual for
information on this le.
ALLBASE/SQL Error Messages
31998
31999
MESSAGE
Remote hpsqlproc process terminated prematurely. (DBERR
31998)
CAUSE
The server process terminated before the application nished.
ACTION
Restart the application.
MESSAGE
The data communication service is undefined. (DBERR
31999)
CAUSE
The data communication type you specied in the AliasDB le is
undened
or
an abnormal situation occurred.
ACTION
Correct the prole in the AliasDB le or
contact your HP Service Representative or Response Center.
34001
34002
34003
MESSAGE
Installation error detected. Check permissions and owner.
(DBERR 34001)
CAUSE
The permissions, owner, or group of /usr/bin/sqlmon are
incorrect.
ACTION
Change the attributes of /usr/bin/sqlmon so that the permission
is 4555, the owner is hpdb, and the group is bin.
MESSAGE
Cannot create temporary file under /tmp. (! !) (DBERR
34002)
CAUSE
A le system error was encountered. /tmp is probably full.
ACTION
Contact your system administrator.
MESSAGE
TERMINFO data error. Using default HP terminal values.
(DBERR 34003)
CAUSE
An unexpected error was encountered while obtaining valid
escape sequences for your terminal.
ACTION
Check the value of the TERM environment variable. Contact
your system administrator to verify that your terminal type has
been added to the /usr/lib/terminfo database.
ALLBASE/SQL Error Messages
3-295
34004
34005
34006
34008
34009
34010
3-296
MESSAGE
Cannot start session. (RC !, !, !, !) (DBERR 34004)
CAUSE
An unexpected error was encountered when trying to connect to
the DBEnvironment.
ACTION
Look for an additional message that provides more information.
MESSAGE
Cannot terminate session. (RC !, !, !, !) (DBERR 34005)
CAUSE
An unexpected error was encountered when trying to release from
the DBEnvironment.
ACTION
Look for an additional message that provides more information.
MESSAGE
DBCORE error. (FNC !, RC !, !, ! !) (DBERR 34006)
CAUSE
An unexpected internal error was encountered.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Unexpected INTERNAL error. (!, !, !, !) (DBERR 34008)
CAUSE
An unexpected internal error was encountered.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Cannot attach to shared memory (RC !, !) (DBERR 34009)
CAUSE
An unexpected error was encountered.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Cannot detach from shared memory (!) (DBERR 34010)
CAUSE
An unexpected error was encountered.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
34020
34021
34022
34023
34030
MESSAGE
Cannot allocate memory for data buffer structure (! !, !)
(DBERR 34020)
CAUSE
An unexpected error was encountered.
ACTION
Contact your system administrator.
MESSAGE
Cannot get data buffer pool head! (DBERR 34021)
CAUSE
An unexpected error was encountered while trying to nd the
data buer pool in memory.
ACTION
The database administrator might have issued a STOP DBE
statement. If not, record as much information as possible and
contact your HP Service Representative or Response Center.
MESSAGE
Number of data buffers not equal to DBECON value! (!, !, !)
(DBERR 34022)
CAUSE
The size of the data buer pool in memory does not match the
size that is recorded in the DBECON le.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Cannot get current buffer information! (DBERR 34023)
CAUSE
An unexpected error was encountered while sampling the data
buer pool.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Could not find DBEFILE statistics in JMACRE buffer (DBERR
34030)
CAUSE
An unexpected error was encountered.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
ALLBASE/SQL Error Messages
3-297
34031
34071
34072
34076
34077
3-298
MESSAGE
Could not find INDEX statistics in JMACRE buffer (DBERR
34031)
CAUSE
An unexpected error was encountered.
ACTION
Record as much information as possible and contact your HP
Service Representative or Response Center.
MESSAGE
Number of sessions exceeds internal maximum (max=!)
(DBERR 34071)
CAUSE
A limit has been reached.
ACTION
If you need the limit increased, please contact your HP Service
Representative or Response Center.
MESSAGE
Number of latches exceeds internal maximum (max=!) (DBERR
34072)
CAUSE
A limit has been reached.
ACTION
If you need the limit increased, please contact your HP Service
Representative or Response Center.
MESSAGE
Number of data buffers exceeds internal maximum (max=!)
(DBERR 34076)
CAUSE
A limit has been reached.
ACTION
If you need the limit increased, please contact your HP Service
Representative or Response Center.
MESSAGE
Number of qualifying locks exceeds internal maximum
(max=!) (DBERR 34077)
CAUSE
A limit has been reached.
ACTION
Use the SET LOCKFILTER or SET LOCKTABFILTER
commands to reduce the number of locks that qualify. If
you need the limit increased, please contact your HP Service
Representative or Response Center.
ALLBASE/SQL Error Messages
34100
34102
34103
34104
34105
34106
MESSAGE
Input too long. Maximum length is !. (DBERR 34100)
CAUSE
The total length of the input line exceeded the allowed limit.
ACTION
Issue the command again.
MESSAGE
Unexpected end of input. (DBERR 34102)
CAUSE
An error was encountered trying to retrieve the next command.
ACTION
Check the output and input to see if all commands executed
properly.
MESSAGE
Illegal syntax. (DBERR 34103)
CAUSE
Command was entered incorrectly.
ACTION
Issue the command again. You can use the help facility to verify
your syntax.
MESSAGE
Illegal integer. (DBERR 34104)
CAUSE
Numeric value was entered incorrectly.
ACTION
Issue the command again.
MESSAGE
Integer value out of range. (min=!,max=!) (DBERR 34105)
CAUSE
The number specied was not between the min and max values
listed in the message.
ACTION
Issue the command again.
MESSAGE
Illegal OWNER.TABLE value. (DBERR 34106)
CAUSE
You did not specify a valid table name.
ACTION
Issue the command again.
ALLBASE/SQL Error Messages
3-299
34107
34120
34121
34122
34501
34502
3-300
MESSAGE
Illegal PAGE/ROW ID value. (DBERR 34107)
CAUSE
You did not specify a valid value.
ACTION
Issue the command again.
MESSAGE
SystemFileName name is too long. Maximum length is !.
(DBERR 34120)
CAUSE
The allowable length for the SystemFileName was exceeded.
ACTION
Issue the command again.
MESSAGE
DBEFile name is not valid for this DBEnvironment. (DBERR
34121)
CAUSE
You did not specify a valid DBEFile name.
ACTION
Issue the command again.
MESSAGE
DBEFileSet name is not valid, or has no DBEFiles. (DBERR
34122)
CAUSE
You did not specify a valid DBEFileSet name.
ACTION
Issue the command again.
MESSAGE
DBEnvironmentName is too long. Maximum length is !.
(DBERR 34501)
CAUSE
The allowable length for the DBEnvironmentName was exceeded.
ACTION
Issue the command again.
MESSAGE
MAINT is too long. Maximum length is !. (DBERR 34502)
CAUSE
The allowable length for the maintenance word was exceeded.
ACTION
Issue the command again.
ALLBASE/SQL Error Messages
34503
34504
34507
34530
34531
34540
MESSAGE
Incompatible DBEnvironment version (!). (DBERR 34503)
CAUSE
The version of the DBEnvironment is incompatible with the
version of the program.
ACTION
Contact your database administrator, who probably needs to use
SQLMigrate.
MESSAGE
Not authorized to use SQLMONITOR on this DBEnvironment.
(DBERR 34504)
CAUSE
You are not the DBECreator or superuser.
ACTION
Sign on as a user who does have the required authority.
MESSAGE
Database in SINGLE-USER MODE. Cannot use SQLMONITOR.
(DBERR 34507)
CAUSE
The DBEnvironment must be started in multi-user mode in order
for SQLMonitor to connect to it.
ACTION
Try again later.
MESSAGE
DBEFileSetName is too long. Maximum length is !. (DBERR
34530)
CAUSE
The allowable length for the DBEFileSetName was exceeded.
ACTION
Issue the command again.
MESSAGE
DBEFileName is too long. Maximum length is !. (DBERR
34531)
CAUSE
The allowable length for the DBEFileName was exceeded.
ACTION
Issue the command again.
MESSAGE
OWNER.TABLE is too long. Maximum length is !. (DBERR
34540)
CAUSE
The allowable length for the OWNER.TABLE was exceeded.
ACTION
Issue the command again.
ALLBASE/SQL Error Messages
3-301
34541
34550
34551
34552
34553
34557
3-302
MESSAGE
PAGE/ROW ID is too long. Maximum length is !. (DBERR
34541)
CAUSE
The allowable length for the PAGE/ROW ID was exceeded.
ACTION
Issue the command again.
MESSAGE
SystemFileName is too long. Maximum length is !. (DBERR
34550)
CAUSE
The allowable length for the SystemFileName was exceeded.
ACTION
Issue the command again.
MESSAGE
SystemFileName could not be opened. (! !, !, !, !) (DBERR
34551)
CAUSE
A le system error was encountered.
ACTION
Refer to the system administration manual.
MESSAGE
SystemFileName could not be created. (! !, !, !, !) (DBERR
34552)
CAUSE
A le system error was encountered.
ACTION
Refer to the system administration manual.
MESSAGE
SystemFileName could not be rewritten. (DBERR 34553)
CAUSE
A le system error was encountered.
ACTION
Refer to the system administration manual.
MESSAGE
SystemFileName could not be closed. (! !, !, !, !) (DBERR
34557)
CAUSE
A le system error was encountered.
ACTION
Refer to the system administration manual.
ALLBASE/SQL Error Messages
34559
34560
34585
34610
MESSAGE
Environment variable is too long. Maximum length is !.
(DBERR 34559)
CAUSE
The total length of the environment variable name exceeded the
allowed limit.
ACTION
Issue the command again.
MESSAGE
Could not write to SystemFileName. (FSERR !, !, !, !)
(DBERR 34560)
CAUSE
A le system error was encountered.
ACTION
Refer to the system administration manual.
MESSAGE
Timeout expired (! seconds, FNC !) (DBERR 34585)
CAUSE
SQLMON was not able to obtain some internal resource that
was needed to complete the last command (for example, perhaps
another session had obtained an X (exclusive) or an IX (intent
exclusive) lock on a table that SQLMON was trying to read
from).
ACTION
You may wish to use the SET USERTIMEOUT command to set
a higher timeout value and issue your original command once
again.
MESSAGE
The timeout expired during an attempt to "Get Statistics"
on table !.!, which exists within DBEFileset ! (DBERR
34610).
CAUSE
SQLMON was not able to obtain some internal resource that
was needed to complete the last command (for example, perhaps
another session had obtained an X (exclusive) or an IX (intent
exclusive) lock on the table that SQLMON was trying to read
from).
ACTION
You may wish to use the SET DBEFILESET command to specify
another DBEFileset, and issue your original command once again.
You can visit the STATIC screen to determine the DBEFileSets
that exist within your DBEnvironment, and the tables that exist
within them.
ALLBASE/SQL Error Messages
3-303
34630
35404
35412
35414
140336
MESSAGE
The timeout expired during an attempt to "Get Statistics"
on a temporary table within DBEFileset ! (DBERR 34630).
CAUSE
SQLMON was not able to obtain some internal resource that was
needed to complete the last command.
ACTION
You may wish to use the SET DBEFILESET command to specify
another DBEFileset, and issue your original command once again.
You can visit the STATIC screen to determine the DBEFileSets
that exist within your DBEnvironment, and the tables that exist
within them.
MESSAGE
Incorrect user password. (DBERR 35404)
CAUSE
The password given for the logon user is not valid.
ACTION
Determine what the correct password is.
MESSAGE
Login string format is invalid. (DBERR 35412)
CAUSE
The login string received does not conform to the MPE login
syntax.
ACTION
Supply a correct login string.
MESSAGE
Invalid function code, !, received. (DBERR 35414)
CAUSE
The server received a function code from the PC that it was not
expecting.
ACTION
Record all error information and call your HP representative.
MESSAGE
Out of system resources. (DBERR 140336)
CAUSE
The system is overloaded and new processes cannot be created.
ACTION
Check for hung processes
or
run the process when fewer processes are running.
3-304
ALLBASE/SQL Error Messages
4
ALLBASE/SQL Console Error Messages
The following error messages are generated by sqldaemon and appear on the HP-UX console.
MESSAGE
Problem encountered in database.
CAUSE
The sqldaemon process (ALLBASE/SQL background cleanup
process) has encountered a problem in an active database.
ACTION
Read the following messages.
Note that this message is followed by the name of the DBECon
le of the database experiencing the problem.
MESSAGE
Database is closed or possibly corrupted. Shutting down.
CAUSE
The sqldaemon process has determined that the problem
encountered is severe enough to warrant shutting down the
database.
ACTION
Read the following message, if any. Verify that the database is in
a consistent state and then restart.
Note that sometimes, owing to timing problems, when a database
has been properly shutdown and deleted, the sqldaemon may
return the above message. This is because the database has been
removed before the sqldaemon process was aware that it has
already been shut down. In such cases the above message is not
signicant.
MESSAGE
Database appears to be hung. No actions are completed.
CAUSE
The database has been deadlocked for a signicant amount of
time.
ACTION
Restart the database after the sqldaemon process shuts it down.
ALLBASE/SQL Console Error Messages
4-1
4-2
MESSAGE
A database process died in a critical section.
CAUSE
The sqldaemon process has discovered that one of the database
processes has failed while holding important resources.
ACTION
Restart the database after the sqldaemon process shuts it down.
MESSAGE
sqldaemon cannot get appropriate privileges. Check
installation.
CAUSE
The sqldaemon process has been denied the necessary authorities.
ACTION
Terminate all DBE sessions. Do an ll on /usr/bin/sqldaemon.
Check that the mode is -r-sr-xr-x. If the mode is not correct,
use the chmod command to change the permissions to 4555.
Check that the owner is hpdb and that the group is bin. If not,
use the appropriate HP-UX command to correct the ownerships.
MESSAGE
sqldaemon has encountered a fatal error.
CAUSE
The sqldaemon process is unable to get the run-time information
it needs because of problems within the database.
ACTION
Restart the database after the sqldaemon process shuts it down.
MESSAGE
sqldaemon has failed unexpectedly.
CAUSE
The sqldaemon process has failed due to some internal
inconsistency.
ACTION
Restart the database after the sqldaemon process shuts it down.
MESSAGE
Current Log (Sequence No. !) is full. Changed to next log
file.
CAUSE
A log le became full.
ACTION
No action required.
MESSAGE
Log Identifier ! (Sequence No. !) is ready for backup.
CAUSE
A log le is ready for backup.
ACTION
The log must be backed up before it can be reused.
ALLBASE/SQL Console Error Messages
MESSAGE
Error reading/writing to log file ! (Sequence No. !). Log
unusable.
CAUSE
An error occurred during read or write operations on a log le.
ACTION
A switch was made to the next log le.
ALLBASE/SQL Console Error Messages
4-3
">