Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Messages and Codes - Supra
Document related concepts
Transcript
SQL ACCESS FOR SUPRA
SERVER PDM®
Messages and Codes
P25-9502-04
SQL Access for SUPRA Server PDM®
Messages and Codes
Publication Number P25-9502-04
© 2006, 2007, 2009, 2011 Cincom Systems, Inc.
All Rights Reserved
This document contains unpublished, confidential, and proprietary information of Cincom. No
disclosure or use of any portion of the contents of these materials may be made without the
express written consent of Cincom.
See http://www.cincom.com/legal/terms.html for a list of Cincom trademarks and other
trademarks that may appear in Cincom product documentation.
All other trademarks are trademarks or registered trademarks of their respective companies.
Cincom Systems, Inc.
55 Merchant Street
Cincinnati, Ohio 45246-3732
USA
PHONE: (513) 612-2300
FAX: (513) 612-2000
WORLD WIDE WEB: http://www.cincom.com
Attention:
Some Cincom products, programs, or services referred to in this publication may not be
available in all countries in which Cincom does business. Additionally, some Cincom products,
programs, or services may not be available for all operating systems or all product releases.
Contact your Cincom representative to be certain the items are available to you.
Release information for this manual
SQL Access for SUPRA Server PDM Messages and Codes, P25-9502-04, is dated
September 1, 2011. This document supports Release 2.0 of SQL Access for
SUPRA Server PDM.
Cincom Technical Support for SQL Access for SUPRA Server PDM
All customers
Web:
http://supportweb.cincom.com
U.S.A customers
Phone:
1-800-727-3525
Fax:
(513) 612-2000
Attn: SQL Access for SUPRA Server PDM
Support
Mail:
Cincom Systems, Inc.
Attn: SQL Access for SUPRA Server PDM
Support
55 Merchant Street
Cincinnati, OH 45246-3732
USA
All:
Visit the support links at
http://www.cincom.com to find contact
information for your nearest Customer
Service Center.
Outside of U.S.A.
Using this manual
$ORDB refers to the directory identified by the ORDB environment variable.
This will be set to the installation directory.
This document may use both UNIX ($ORDB/..) and Windows (%ORDB%\..)
notations. Please adjust the environment variable and slashes accordingly for
your platform.
Contents
1. Numeric error messages .............................................................. 5 Overview .................................................................................................... 5 Messages with numeric codes ........................................................................... 6 2. CID Adapter Server and Adapter Client error messages .................... 166 Overview ................................................................................................. 166 CID Adapter Server and Adapter Client error messages .......................................... 167 3. JDBC error messages ............................................................... 232 Overview ................................................................................................. 232 JDBC error messages ................................................................................... 233 4. OrdbXML Java error messages ................................................... 239 Overview ................................................................................................. 239 OrdbXML Java error messages ........................................................................ 240 Messages and Codes, P25-9502-04
Contents
4
1. Numeric error messages
Overview
This chapter includes messages prefaced by a 4-character numeric code.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Overview
5
Messages with numeric codes
The following messages can be returned by Cincom SQL Access:
0001
0002
0003
0004
0005
Internal system failure:
available.
no more specific information is
Description
An internal error was generated.
User action
Contact Cincom Technical Support.
Out of virtual memory:
bytes.
unable to allocate nnnn memory
Description
The Cincom SQL Access client runtime was not able to acquire
nnnn bytes of memory.
User action
Enlarge the available memory by increasing the value of
Cincom SQL Access system parameters max_block_size and/or
max_block_count. If the error continues to occur, you will
need to increase the memory (either real and/or virtual) on the
client machine.
Undefined environment variable env-var.
Description
Required environment variable env-var is not set.
User action
Set the environment variable name env-var and try again.
Interrupt.
Description
User requested interrupt has occurred.
User action
None, information only.
Key = key-value was not found in hash table table-name.
Description
The indicated key value was not located in the named hash
table. This is only a warning.
User action
None, warning only.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
6
0007
0008
0009
0010
Trying to format disk volume volume-name with an incorrect
value nnnn for number of pages.
Description
The number of pages specified during createdb or addvoldb is
invalid.
User action
Please confirm the number of pages specified with createdb or
addvoldb.
Unable to format disk volume volume-name with nnnn pages
(byte-count bytes).
Description
The error occurred in the specified disk volume.
User action
Please confirm the disk volume displayed by the error message.
Unable to format disk volume volume-name with nnnn pages
(byte-count bytes) due to insufficient space. Current space
available is avail-pages pages (avail-bytes bytes).
Description
There is not enough free area in the specified disk volume.
User action
Free up space on the named volume, or specify other disk
partitions where enough free area exists.
Unable to mount disk volume volume-name.
Description
Cannot open the database file volume-name.
User action
Please confirm the content of:
1. Database location file (ordblist.txt)
2. Database volume information file
(<database-name>.orv):
0011
Unable to mount disk volume volume-name. The database
database-name, to which the disk volume belongs, is in use
by user user-name on process process-id of host hostname
since timestamp.
Description
It was not possible to open the database file because it is
already open by the processes.
User action
Terminate the other processes before opening the database.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
7
0012
0013
0014
0015
Problems dismounting volume volume-name.
Description
The database file failed during the dismount.
User action
Please confirm the disk partition output in the error message.
An I/O error occurred while reading page page-number of
volume volume-name
Description
An I/O error occurred when reading from the database volume.
User action
Please confirm the disk partition where the database volume
exists.
An I/O error occurred while writing page page-number of
volume volume-name
Description
An I/O error occurred when writing to the database volume.
User action
Please confirm the disk partition where the database volume
exists.
Unable to write page page-number of volume volume-name due
to insufficient space in system device.
Description
Writing to the database volume failed because there was not
enough free area in the specified disk partition.
User action
Please allocate enough free area to the disk partition to write
the database volume displayed in the error message.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
8
0016
Unable to rename disk volume old-volume-name to newvolume-name.
Description
There are two possible reasons why the database volume name
could not change:
1. There was not enough free area in the disk volume.
2. You do not have write authorization for the
specified directory.
User action
Perform one of the following tasks:
1. Allocate enough free area to the disk partition to
write the database volume displayed in the error
message.
2. Contact your DBA for write authority to the
specified directory.
0017
INTERNAL ERROR: fetching deallocated pageid page-id of
volume volume-name.
Description
The specified page of the specified volume is already allocated,
or there was an error obtaining the specified page.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0018
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
All page buffers are fixed.
Description
Unable to extend the page buffer because all page buffers are
fixed.
User action
Contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
9
0019
INTERNAL ERROR: pageptr = page-pointer of page page-number
of volume volume-name is not fixed.
Description
The pointer to the specified page has not been fixed.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0020
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
INTERNAL ERROR: unknown pageptr = page-pointer.
Description
The specified page pointer is invalid.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
10
0021
INTERNAL ERROR: unknown sector sector-id of volume volumename.
Description
The specified sector was not found in the specified volume.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0022
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
INTERNAL ERROR: unknown page page-id of volume volume-name.
Description
The specified page is invalid for the specified volume.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
11
0023
INTERNAL ERROR: trying to deallocate disk system page
system-page of volume volume-name.
Description
An error occurred while attempting to deallocate the specified
system page from the specified volume.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0024
0025
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
Almost out of space in volume volume-name. Total number of
pages = page-count, total number of free pages = free-pagecount.
Description
The number of available pages in the specified volume is less
than the threshold specified by the Cincom SQL Access system
parameter warn_outofspace_factor.
User action
Add database volume with the addvoldb utility.
Almost out of space in volumes with “data” as the main
storage purpose. Total number of pages = page-count, total
number of free pages = free-page-count.
Description
The total number of available pages in the database is less than
the threshold specified by the Cincom SQL Access system
parameter warn_outofspace_factor.
User action
Add database volume with the addvoldb utility.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
12
0026
0027
0028
Almost out of space in volumes with “index” as the main
storage purpose. Total number of pages = page-count, total
number of free pages = free-page-count.
Description
The total number of available pages in the database is less than
the threshold specified by the Cincom SQL Access system
parameter warn_outofspace_factor.
User action
Add database volume with the addvoldb utility.
Almost out of space in volumes with “generic” as the main
storage purpose. Total number of pages = page-count, total
number of free pages = free-page-count.
Description
The total number of available pages in the database is less than
the threshold specified by the Cincom SQL Access system
parameter warn_outofspace_factor.
User action
Add database volume with the addvoldb utility.
Almost out of space in volumes with “temporary data” as the
main storage purpose. Total number of pages = page-count,
total number of free pages = free-page-count.
Description
The total number of available pages in the database is less than
the threshold specified by the Cincom SQL Access system
parameter warn_outofspace_factor.
User action
When free area of the 'temp' volume becomes insufficient, an
additional 'temp' volume is created.
This additional 'temp' volume will be deleted when the
database is shut down.
0029
Last out of space notification for volume volume-name.
Total number of pages = page-count, total number of free
pages = free-page-count.
Description
Last notification that the specified volume is out of space.
User action
Add database volume with the addvoldb utility.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
13
0030
0031
0032
Last out of space notification for volumes with “data” as
the main storage purpose. Total number of pages = pagecount, total number of free pages = free-page-count.
Description
The database is out of space and the database cannot
automatically extend its available storage because the Cincom
SQL Access system parameter auto_volext_factor is set to 0.
User action
Add database volume with the addvoldb utility, you may also
want to consider allowing the database to automatically extend
its storage by setting the Cincom SQL Access
auto_volext_factor system parameter.
Last out of space notification for volumes with “index” as
the main storage purpose. Total number of pages = pagecount, total number of free pages = free-page-count.
Description
The database is out of space and the database cannot
automatically extend its available storage because the Cincom
SQL Access system parameter auto_volext_factor is set to 0.
User action
Add database volume with the addvoldb utility, you may also
want to consider allowing the database to automatically extend
its storage by setting the Cincom SQL Access
auto_volext_factor system parameter.
Last out of space notification for volumes with “generic”
as the storage purpose. Total number of pages = page-count,
total number of free pages = free-page-count.
Description
The database is out of space and the database cannot
automatically extend its available storage because the Cincom
SQL Access system parameter auto_volext_factor is set to 0.
User action
Add database volume with the addvoldb utility, you may also
want to consider allowing the database to automatically extend
its storage by setting the Cincom SQL Access
auto_volext_factor system parameter.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
14
0033
Last out of space notification for volumes with “temporary
data” as the main storage purpose. Total number of pages =
page-count, total number of free pages = free-page-count.
Description
The total number of available pages in the database is less than
the threshold specified by the Cincom SQL Access system
parameter warn_outofspace_factor.
User action
When free area of the 'temp' volume becomes insufficient, an
additional 'temp' volume is created.
This additional 'temp' volume will be deleted when the
database is shut down.
0034
INTERNAL ERROR: page-id nthpage is out of range for file
file-id in volume volume-name. Current number of pages are
page-count.
Description
The specified page is invalid.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
15
0035
INTERNAL ERROR: Unknown volume identifier volume-id.
Description
The specified volume identifier is invalid for the database.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0036
0037
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
Out of disk space in database. Number of requested page(s)
= page-count.
Description
The database is out of space and the database cannot
automatically extend its available storage because the Cincom
SQL Access system parameter auto_volext_factor is set to 0.
User action
Add database volume with the addvoldb utility, you may also
want to consider allowing the database to automatically extend
its storage by setting the Cincom SQL Access
auto_volext_factor system parameter.
Out of disk space in volume volume-name. Number of
requested page(s) = page-count.
Description
Unable to allocate temporary space in specified volume.
User action
Please free some space on the specified volume, or set the
Cincom SQL Access voltmp_path system parameter to specify a
disk partition that contains enough free area.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
16
0038
INTERNAL ERROR: Unknown file VFID virtual-file-id.
Description
An invalid virtual file id was encountered.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0039
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
INTERNAL ERROR: Page page-id (volume volume-name) of file
VFID virtual-file-id (volume virtual-volume) is
invalid/deallocated according to allocation map.
Description
The database detected an inconsistent page mapping for the
specified virtual file.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
17
0040
INTERNAL ERROR: expected-pages expected pages, actual-pages
found pages for file VFID virtual-file-id(volume virtualvolume).
Description
The database detected an inconsistent page count for the
specified virtual file.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0041
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
INTERNAL ERROR: Page page-id (volume volume-name) is not
part of file VFID virtual-file-id (volume virtual-volume).
Description
The database detected an inconsistent page mapping for the
specified virtual file.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
18
0042
Cannot reorder anchored records on page page-id of volume
volume-name.
Description
This internal error indicates a problem was encountered when
attempting to re-organize the records in a page.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0043
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
INTERNAL ERROR: incorrect number passed-slot-count of slots
passed for reordering records on page page-id of volume
volume-name. There are actually actual-slot-count slots.
Description
The database detected an inconsistent number of record slots
for the specified page/volume.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
19
0045
Slot slot-id on page page-id of volume volume-name is
allocated to an anchored record. A new record cannot be
inserted here.
Description
This internal error indicates that the specified slot is already
allocated.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0046
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
INTERNAL ERROR: slot slot-id on page page-id of volume
volume-name is not allocated.
Description
Unable to allocate specified slot.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
20
0047
Unable to create a heap file in volume volume-name.
Description
Failed to create a heap file in the specified volume.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0048
0049
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
Accessing deleted object object-id.
Description
The specified object refers to an invalid database object. The
most common cause of this error is passing a pointer to a
deleted object. This error code can be set by any function that
accepts a DB_OBJECT pointer as an argument.
User action
Care should be taken to ensure that object references to
objects being deleted are set to null. For instance if object A
holds a pointer to object B, the reference to object B held by
object A should be updated to null when object B is deleted.
INTERNAL ERROR: class of object object-id is unknown.
Description
The specified object refers to an unknown database class. The
most common cause of this error is passing a pointer to an
object whose class has been dropped. This error code can be
set by any function that accepts a DB_OBJECT pointer as an
argument.
User action
Care should be taken to ensure that object references to
objects of a class being dropped are set to null. For instance if
class A holds pointers to objects of class B, the references to
objects of B held by instances of class A should be updated to
null when class B is dropped.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
21
0050
INTERNAL ERROR: relocation record of object object-id may
be corrupted.
Description
There is a possibility that the relocation record of the specified
object is corrupt.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0051
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
INTERNAL ERROR: object object-id may be corrupted.
Description
There is a possibility that the specified object is corrupt.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
22
0052
INTERNAL ERROR: object overflow address object-id may be
corrupted.
Description
There is a possibility that the specified object is corrupt.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0053
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
Fetching object object-id when only its OID has been
assigned.
Description
The specified object is invalid. An object identifier was
allocated for the object, but the object data does not exist.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
23
0055
INTERNAL ERROR: A page cycle reference was detected on page
page-id of heap file file-id.
Description
Inconsistent heap file detected.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0063
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
INTERNAL ERROR: a temporary page was corrupted during
sorting.
Description
A page used during sorting was corrupted.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
24
0064
0065
0066
Unknown class class-name.
Description
The specified class does not exist.
User action
Please specify a valid class name.
Class class-name already exists.
Description
The specified class already exists in the database.
User action
Please specify a valid class name not already defined in the
database.
INTERNAL ERROR: unknown force operation operation-id for
object object-id.
Description
The specified operation on the specified object is not defined.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
25
0067
INTERNAL ERROR: a heap file has not been allocated to store
object object-id.
Description
Cannot allocate the heap file to store the specified object.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0068
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
INTERNAL ERROR: different classnames for class with oid =
object-id were found. Found classnames are hash-class,
heap-class using classname hash table and heap,
respectively.
Description
The specified object has inconsistent class names.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
26
0069
INTERNAL ERROR: different class object identifiers were
found for class with name class-name. Found OIDS are hashobject-id, heap-object-id using classname hash table and
heap, respectively.
Description
The specified class has objects with inconsistent class
identifiers.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0070
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
INTERNAL ERROR: Class with name class-name and oid =
object-id does not exist in classname hash table.
Description
The specified class name of the specified object does not exist
in the class-name hash table.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
27
0071
INTERNAL ERROR: Class with name class-name and oid =
object-id does not exist in its heap.
Description
The specified class name of the specified object does not exist
in the heap.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0072
0073
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
Your transaction (index transaction-id) has been
unilaterally aborted by the system.
Description
The specified transaction was rolled back because a deadlock
was detected.
User action
Wait for the server to become available again. Then execute
the client application process.
Your transaction (index transaction-id) timed out waiting
on lock-type lock on object object-id. You are waiting for
user(s) user-names to finish.
Description
The specified transaction was rolled back because the specified
lock request has timed out. The lock could not be acquired
because the specified users displayed in the error message
already held the lock.
User action
Wait until the commit and the rollback for the transaction is
done by the other user(s), and attempt the operation again.
You may also want to validate the lock_timeout_in_secs
Cincom SQL Access system parameter.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
28
0074
0075
0076
0077
Your transaction (index transaction-id) timed out waiting
on lock-type lock on class class-name. You are waiting for
user(s) user-names to finish.
Description
The specified transaction was rolled back because the specified
lock request has timed out. The lock could not be acquired
because the specified users displayed in the error message
already held the lock.
User action
Wait until the commit and the rollback for the transaction is
done by the other user(s), and attempt the operation again.
You may also want to validate the lock_timeout_in_secs
Cincom SQL Access system parameter.
Your transaction (index transaction-id) timed out waiting
on lock-type lock on instance instance-id. You are waiting
for user(s) user-names to finish.
Description
The specified transaction was rolled back because the specified
lock request has timed out. The lock could not be acquired
because the specified users displayed in the error message
already held the lock.
User action
Wait until the commit and the rollback for the transaction is
done by the other user(s), and attempt the operation again.
You may also want to validate the lock_timeout_in_secs
Cincom SQL Access system parameter.
Your transaction (index transaction-id) timed out waiting
on lock-type lock on page page-id. You are waiting for
user(s) user-names to release the page lock.
Description
The specified transaction was rolled back because the specified
lock request has timed out. The lock could not be acquired
because the specified users displayed in the error message
already held the lock.
User action
Wait until the commit and the rollback for the transaction is
done by the other user(s), and attempt the operation again.
You may also want to validate the lock_timeout_in_secs
Cincom SQL Access system parameter.
INTERNAL ERROR: all buffers are fixed.
Description
Failed trying to extend the log buffer.
User action
Contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
29
0078
0079
0080
0081
INTERNAL ERROR: an I/O error occurred while reading logical
log page log-page (physical page-id) of volume-name.
Description
There is a possibility that the log volume is corrupted.
User action
Please validate the state of the disk partition where the
database log volume resides.
INTERNAL ERROR: an I/O error occurred while writing logical
log page log-page (physical page-id) of volume-name.
Description
There is a possibility that the log volume is corrupted.
User action
Please confirm the state of the disk partition where the
database log volume resides.
Insufficient space in operating system device when writing
logical log page log-page (physical page-id) of volumename. Could not write more than bytes bytes.
Description
Out of disk space for the log volume.
User action
Please secure enough disk space for partition in which the
database log volume is resides.
INTERNAL ERROR: logical log page page-id may be corrupted.
Description
The system detected an error in the specified log page.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
30
0082
0083
0084
0085
0086
Unable to mount log disk volume/file file-id.
Description
Unable to access the log volume.
User action
Please confirm the database log volume exists. Use the
renamedb utility to change the database to another database
name. Then, use the renamedb utility to return the database
to former database name.
Length of path pathname plus length of prefix logname
logprefix is too long; the combined length must be less
than max-length.
Description
The length of the database name is too long.
User action
Shorten the length of the database name.
Length of prefix logprefix is too long; the length must be
less than max-length.
Description
The length of the database name is too long.
User action
Shorten the length of the database name.
The prefix name logprefix is not the same as actual-prefix
on the log disk. The log may have been renamed outside the
database domain.
Description
The log volume name specified when the database was created
is different from the present log volume name.
User action
Use the renamedb utility to change the database to another
database name. Then, use the rename utility again to return
the database to the former database name.
Database is incompatible with current release releasenumber.
Description
The release of the Cincom SQL Access client program or the
Cincom SQL Access utility and the release of Cincom SQL Access
database are different.
User action
Use the same release of Cincom SQL Access that created the
database.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
31
0087
0088
There are recovery actions that must be recovered using
database release needed-release instead of release currentrelease. After the recovery, the database can be run on
release valid-release.
Description
The release of Cincom SQL Access executing the backupdb
utility and the release of Cincom SQL Access executing the
restoredb utility are different.
User action
Use the restoredb utility from the same release of Cincom SQL
Access that executed the backupdb utility.
Release string release is larger than max-length. INTERNAL
ERROR: must change header log.
Description
The number of characters of Cincom SQL Access release
information stored in the header of the database are longer
than number of characters of the release information which
Cincom SQL Access manages.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0089
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
Log log-volume does not belong to the given database.
Description
The specified log volume does not correspond to the database.
It is possible that the log volume file was overwritten.
User action
Contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
32
0090
Redo logging is always a page level logging operation. A
data page pointer must be given as part of the address.
Description
An invalid or missing data page pointer was encountered during
the rollback and/or recovery processing of the database.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0091
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
Postpone logging is always a page level logging operation.
A data page pointer must be given as part of the address.
Description
An invalid or missing data page pointer was encountered during
the log processing of the database.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
33
0092
Compensate logging is always a page level logging
operation. A data page pointer must be given as part of
the address.
Description
An invalid or missing data page pointer was encountered during
the rollback and/or recovery processing of the database.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0094
0095
0096
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
WARNING: postpone logging is ignored during redo recovery
and normal rollbacks.
Description
The Postpone logging processing is not executed during the
rollback processing or the recovery execution of the database.
User action
None, warning only.
WARNING: undo logging is ignored during recovery and normal
rollback.
Description
The undo logging processing is not executed during the rollback
processing or the recovery execution of the database.
User action
None, warning only.
Media recovery may be needed on volume volume-name.
Description
The specified volume may have errors.
User action
Please validate that the disk partition of the specified database
volume exists. Recover media if broken.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
34
0097
INTERNAL ERROR: unable to find log page log-page in log
archives.
Description
The specified log page could not be found in the archive log.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0098
0099
0101
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
Unable to create archive log archive-log-volume to archive
pages from start-page to end-page.
Description
Could not create the archive log volume.
User action
Please confirm free area of the disk partition where the archive
log volume resides, and also check the write authority of the
directory.
Unable to create backup directory information file filename.
Description
The backup directory information file could not be created
during execution of the backupdb utility.
User action
Please confirm free area of the disk partition where the backup
directory information file resides, and check the write
authority of the directory.
Unknown user file file-name.
Description
The specified file does not exist or cannot be opened.
User action
Please validate the specified path.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
35
0102
0103
0105
0106
File file-name does not have enough entries:
entries expected.
num-entries
Description
Internal error encountered during log processing.
User action
Contact Cincom Technical Support.
File file-name seems to have unordered entries. Entry
entry-id with values: value-list, was found when entry with
values expected-values was expected.
Description
Internal error.
User action
Contact Cincom Technical Support.
Cannot access backup file file-name. Restore or Backup is
cancelled.
Description
The specified file cannot be accessed.
User action
Please confirm the volume information file and its location.
Cannot prepare to commit the current transaction with
global transaction identifier transaction-id because that
transaction identifier is in use by another transaction.
Description
Unable to commit the transaction because the transaction is
already in use.
User action
Use lockdb to identify which user process has the specified
transaction.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
36
0107
There is no global distributed transaction associated with
transaction identifier transaction-id.
Description
Unable to process the transaction commit because the
corresponding transaction does not exist.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0108
0110
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
Current transaction transaction-id must be committed or
aborted before attempting to join to the distributed
transaction with global identifier global-id.
Description
Unable to connect for a ORDB server because there is an
uncommitted transaction.
User action
Commit/abort the current transaction before attempting to
join.
Isolation level value must be between level-1 and level-2.
Description
The isolation level is not valid.
User action
Check the Cincom SQL Access isolation_level system parameter
and make sure the parameter is set to a valid value.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
37
0111
Your transaction has been aborted by the system due to
server failure.
Description
Because the database server has ended in the transaction by
the forced ending etc., the transaction is rolled back.
User action
Confirm the situation of the database server.
After the server is restarted, it is necessary to execute the aborted transaction
again.
0112
0113
0114
0115
Host host-name is not authorized to run database.
Description
The host trying to execute the server does not have database
execution authority.
User action
Verify that the license key in file admin\license.key is valid.
Contact Cincom Technical Support if the license appears to be
valid.
Unable to restart/initialize the database server.
Description
The server host machine was not able to respond to network
requests.
User action
Make sure the database you are trying to initialize is not
already running. Check the network connectivity of your
database server machine.
Unable to interpret file-name as a database. The database
volumes/files may have been renamed/copied outside the
database domain.
Description
The existing database file does not appear to be formatted
properly. It is possible that the database file was overwritten
by another type of file.
User action
If the database volume name was renamed, change it back.
The database can be copied in correct manner by using the
copydb utility; the name of the database can be changed using
the renamedb utility; or if the object file was accidentally
overwritten, use the unloaddb utility.
Database database-name already exists.
Description
The specified database name already exists.
User action
Change the database name to the different name.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
38
0116
Database database-name is unknown, or the file file-name cannot
be accessed.
Description
The database name is not valid or it is not in the location
specified in ordblist.txt file.
User action
Validate the data in file ordblist.txt.
Confirm that the environment variable ORDB_DATABASES is set
to the path that contains the ordblist.txt file.
0117
0118
0119
0120
Absolute pathname for the database is too long. The
combined length of the path path-name plus the name
database-name is length; the combined length must be less
than max-length.
Description
The database path name derived from the ordblist.txt file was
too long to be a valid path name for the operating system. This
may indicate corruption of the ordblist.txt database directory
file.
User action
Validate the contents of ordblist.txt file.
Failed to locate current working directory.
Description
An error was detected while attempting to get the current
working directory.
User action
Try specifying the full pathname along with the file name.
Unable to find local hostname.
Description
An error was detected while attempting to get the current
hostname.
User action
Try specifying the hostname explicitly. Make sure the network
is configured properly.
The maximum number of volumes max has been exceeded.
Description
The maximum number of volumes that Cincom SQL Access can
process has been exceeded.
User action
The database should be unloaded then allocate more space by
using fewer volumes with more pages. Then reload the
database.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
39
0121
Trying to remove volume-name a permanent volume from the
database.
Description
During shutdown, the database was trying to delete what was
thought to be a temporary volume, and the volume was
permanent.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0122
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
Unable to access system message catalog.
Description
The error occurred when accessing the message file during
initialization of the database.
User action
The message file in the admin\msg directory of the Cincom SQL
Access installation may be missing or destroyed.
1. Verify that the environment variable ORDB_LANG is
set to the proper value for your installation.
(En_US for English, Ja_JP for Japanese).
2. Please confirm that the file
admin\msg\<ORDB_LANG>\er.msg exists.
(<ORDB_LANG> is the environment variable
setting.)
Please reinstall Cincom SQL Access if the above steps did not
resolve the issue. (Make sure to backup important files in your
current installation, or install to different location and copy
the er.msg file(s) to your current installation).
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
40
0123
Unable to create file-name for database database-name.
Description
The specified file could not be created.
User action
Confirm that write access is granted to the specified directory.
Ensure that the specified volume has space for another file
descriptor.
0124
0125
0126
Volume volume-name already exists.
Description
Specified volume name already exists.
User action
Please use a different volume name.
An automatic volume extension volume-name of page-count
pages and generic storage purpose was created.
Description
Additional database space was required; the specified generalpurpose volume was automatically added to the database.
User action
None, information only.
Unknown purpose purpose given on line line-number.
Description
The createdb utility was unable to parse the volume commands
contained in the file specified with the –mv option of createdb.
The purpose given on the specified line is unknown.
User action
0127
Correct the purpose on the specified line number of the file
given with the –mv option of createdb utility.
Incorrect value page-count for number of pages given on
line line-number.
Description
The createdb utility was unable to parse the volume commands
contained in the file specified with the –mv option of createdb.
The number of pages on the specified line is invalid.
User action
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
Correct the page count on the specified line number of the file
given with the –mv option of createdb utility.
41
0128
Number of pages was not given on line line-number.
Description
The createdb utility was unable to parse the volume commands
contained in the file specified with the –mv option of createdb.
The number of pages on the specified line was not specified.
User action
0129
Add the page count on the specified line number of the file
given with the –mv option of createdb utility.
Unknown token token was found on line line-number.
Description
The createdb utility was unable to parse the volume commands
contained in the file specified with the –mv option of createdb.
The specified token on the specified line is invalid.
User action
0130
0131
0134
Correct the specified line number of the file given with the –mv
option of createdb utility.
Out of virtual memory.
Description
Insufficient memory.
User action
Please expand the size of the swap file or increase the physical
memory available.
Database system error.
Description
A fatal error occurred in the database.
User action
Please acquire the error log file, and contact Cincom Technical
Support.
It is illegal to mix class attributes and non-class
attributes in the same update.
Description
Attempt was made to update instance and class attributes at
the same time.
User action
Please use separate SQL commands to perform the updates.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
42
0137
Corrupted authorization objects.
Description
The user authority class is corrupted.
User action
The database system classes may be corrupted.
Please execute checkdb utility to validate the integrity of the
database.
0138
Authorization class class-name not found.
Description
The user authority class was not found.
User action
The database system classes may be corrupted.
Please execute checkdb utility to validate the integrity of the
database.
0139
0140
0141
Access error on authorization attribute auth-id of class
class-name.
Description
Read access could not be obtained on an internal authorization
object to process the operation.
User action
Wait until the object is no longer in contention and try the
operation again. If the problem still exists after restarting the
database, please contact Cincom Technical Support.
Operation operation can only be performed by the DBA or a
DBA group member.
Description
A call was made to a privileged function that can only be called
by the DBA or a member of the DBA group.
User action
You must be logged in as user DBA or as a member of the DBA
group in order to perform the specified operation.
Cannot add user-name as a member of group-name.
Description
The user object given for the new member is invalid.
User action
Enter a valid user object pointer for the new member.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
43
0142
0143
Adding member causes the user hierarchy to become a cyclic
graph.
Description
The given member cannot be added because it would cause
cycles in the user hierarchy. For example, a user cannot be
added as a member of itself.
User action
Do not attempt to add a user to a group that already contains a
group that the user is a member of or contains the user.
Encountered class with no owner.
Description
Encountered a class that has no owner.
User action
The database system classes may be corrupted.
Please execute checkdb utility to validate the integrity of the
database.
0145
0146
0147
0148
Cannot issue grant/revoke commands to yourself.
Description
You can only grant permissions to other users. Your grant
status for a particular class can be changed only by the owner
of that class, or by another user who has the appropriate
authorization.
User action
Please set the authority by the third people other than me.
Contact the class owner, or another user who has the
appropriate authorization, to grant you permission.
Cannot issue GRANT/REVOKE to owner of a class.
Description
A GRANT operation cannot be performed on the owner of a
given class. A class owner always has complete authority on a
class.
User action
None, information only.
No GRANT option.
Description
If the currently logged in user is not the owner of the class, the
GRANT option can be performed only if the current user has
also been given the GRANT option.
User action
Please set a proper value in grant_option of the parameter of
the db_grant function.
Cannot obtain write lock on authorization object.
Description
Write access could not be obtained on internal authorization
objects during processing of the operation.
User action
Confirm that lockdb did not lock the transaction and execute
processing again.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
44
0150
0151
0152
0153
Cannot revoke privileges from self.
Description
A revoke operation cannot be performed on yourself. Your
grant status can be changed only by the owner of the class or
by the user who supplied you with the original grant.
User action
Please have the class owner, user who granted the authority,
or the DBA user revoke the privilege.
Cannot revoke privileges from owner of a class.
Description
A revoke operation cannot be performed on the owner of a
particular class. A class owner always has complete authority
on the class.
User action
The right cannot be deleted from the class owner.
GRANT not found.
Description
The given authorization was never granted and therefore
cannot be revoked.
User action
None, information only.
No authorization privileges in effect for the database.
Description
No authority objects were identified.
User action
The database system classes may be corrupted.
Please execute checkdb utility to validate the integrity of the
database.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
45
0154
Incomplete authorization installation - no authorization
privileges in effect for the database.
Description
No authority objects were identified.
User action
The database system classes may be corrupted.
Please execute checkdb utility to validate the integrity of the
database.
0155
Multiple authorization roots.
Description
Invalid authority objects were identified.
User action
The database system classes may be corrupted.
Please execute checkdb utility to validate the integrity of the
database.
0156
0157
Authorization failure.
Description
The currently logged-in user does not have authorization to
perform the attempted operation.
User action
Contact the class owner or your DBA to grant you authorization
on the attempted operation.
SELECT authorization failure.
Description
The currently logged-in user does not have authorization to
read the given object. You must have SELECT authorization for
a class in order to perform any operations on that class or its
instances, including any target class of a class trigger. This
error code can be set by any function that accepts a
DB_OBJECT pointer as an argument.
User action
Contact the class owner or your DBA to grant you SELECT
authorization.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
46
0158
ALTER authorization failure.
Description
The currently logged-in user does not have authorization to
change the definition of the given class. You must have ALTER
authorization for a class in order to change its definition. This
error code can be set by any function that modifies the
schema.
This error code may also be returned when the user does not
have the ALTER privilege for the target class of a trigger.
User action
0159
0160
0161
Contact the class owner or your DBA to grant you ALTER
authorization.
UPDATE authorization failure.
Description
The currently logged-in user does not have authorization to
update the given object. This error code can be set by any
function that modifies a database object. You must have
UPDATE authorization for a class in order to change the values
of its attributes.
User action
Contact the class owner or your DBA to grant you UPDATE
authorization.
INSERT authorization failure.
Description
The currently logged-in user does not have authorization to
create an instance of the given class. You must have INSERT
authorization for a class in order to create instances.
User action
Contact the class owner or your DBA to grant you INSERT
authorization.
DELETE authorization failure.
Description
The currently logged-in user does not have authorization to
delete an instance of the given class. You must have DELETE
authorization for a class in order to remove instances.
User action
Contact the class owner or your DBA to grant you DELETE
authorization.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
47
0162
0163
0164
0165
0167
INDEX authorization failure.
Description
The currently logged-in user does not have authorization to add
indexes to the class. You must have INDEX authorization for a
class in order to add indexes.
User action
Contact the class owner or your DBA to grant you INDEX
authorization.
EXECUTE authorization failure.
Description
The currently logged-in user does not have authorization to
execute methods for the given class. You must have EXECUTE
authorization for a class in order to call methods.
User action
Contact the class owner or your DBA to grant you EXECUTE
authorization.
User user-name already exists.
Description
A user with the specified name is already defined in the
database.
User action
Use a different user-name, or update the existing user
definition.
User user-name is invalid.
Description
The user name or object was not valid. For functions that
accept object pointers, this error code indicates that the
supplied value is not a valid user object. For functions that
accept user names, this error is returned when the given user
name is not found, or when the name does not conform to the
requirements established for user names. Names cannot
contain embedded blanks and must be from 1–255 characters in
length.
User action
Please verify the user name or user object.
Must be class owner to perform operation.
Description
To add a member to a group user, you must be either log in as
that group user or as the DBA, or a member of the DBA group.
User action
Contact the class owner or your DBA for privileges.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
48
0168
0169
Member not found.
Description
The user group does not have the given user member.
User action
Please confirm whether the user is a member of the group.
Cannot remove user from the database.
Description
User action
0170
0171
0172
This error can be generated for one of two reasons:
♦
The user is logged on.
♦
The user is the public user or the DBA user.
Depending on the circumstances, perform one of the following
actions:
♦
Have the user logoff and then delete the user.
♦
None, user public and user DBA cannot be deleted.
No user logged in.
Description
The application must register an initial user using the
db_login() function before calling the db_restart() function.
User action
Please execute the db_login() function.
Incorrect or missing password.
Description
The password supplied in the call to the db_login() function
does not match the password that is stored in the database for
the registered user.
User action
Please correct the password.
Password string cannot have more than 8 characters.
Description
The password exceeded eight characters.
User action
Make sure the password is not more than eight characters.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
49
0173
Could not locate database file file-name.
Description
Could not find the specified file.
User action
Make sure write access is granted to the specified
file/directory.
If the specified file is ordblist.txt, make sure that the
ORDB_DATABASES environment variable is set to the proper
directory path, and that write authority is granted to the
directory.
0174
Could not obtain write access to database file file-name.
Description
Could not create and/or update the specified file.
User action
Make sure write access is granted to the specified
file/directory.
If the specified file is ordblist.txt, make sure that the
ORDB_DATABASES environment variable is set to the proper
directory path, and that write authority is granted to the
directory.
0176
Conversion error in date format.
Description
Error was encountered when converting the data to a date,
time, or timestamp.
User action
Please correct data to a valid date, time, or timestamp
representation.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
50
0178
Temporary OID encountered without MOP.
Description
Illegal OID was encountered.
User action
This could be either a database corruption or an algorithmic
problem in the database. Perform the following actions:
1. Shut down the database server.
2. Execute checkdb:
0179
0181
0182
0183
0184
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
Domain source-domain is not compatible with domain targetdomain.
Description
Invalid cast operation. Domains are not compatible.
User action
Correct code or SQL to use compatible domains.
Cannot coerce value of domain source-domain to domain
target-domain.
Description
Cast to the specified domain failed.
User action
Validate the source data and/or target domain.
Cannot coerce value of domain source-domain to domain
target-domain without overflow.
Description
The cast operation would result in an overflow.
User action
Modify either the value or the target domain so the overflow
will not occur.
Unexpected amount of received data; bytes-expected
expected, bytes-received received.
Description
Communication error encountered.
User action
Internal error, please contact Cincom Technical Support.
Cannot allocate communications buffer.
Description
Allocation of the communication buffer failed.
User action
Internal error, please contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
51
0185
Error receiving data from client.
Description
Communication error encountered.
User action
The communication error occurred between the server and the
client. Please end the client at once, and attempt to
reconnect to the server.
If the reconnect fails, the server may be down.
0186
Error receiving data from server.
Description
Communication error encountered.
User action
The communication error occurred between the server and the
client. Please end the client at once, and attempt to
reconnect to the server.
If the reconnect fails, the server may be down.
0187
Communications buffer not used.
Description
Communication error encountered.
User action
The communication error occurred between the server and the
client. Please end the client at once, and attempt to
reconnect to the server.
If the reconnect fails, the server may be down.
0188
Unknown database database-name.
Description
The specified database was not found.
User action
Please confirm the database name.
Verify the contents of the ordblist.txt file.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
52
0189
Invalid host name host-name.
Description
The machine registered as a host of the database server did not
exist.
User action
Verify that the client machine can access the server machine
(via ping or some other tool). If network access is OK, then
confirm that the master process is up and running on the server
machine.
Verify the contents of the ordblist.txt file.
0190
Server host not identified.
Description
The specified server hostname was not found.
User action
Verify that the client machine can access the server machine
(via ping or some other tool). If network access is OK, then
confirm that the master process is up and running on the server
machine.
Verify the contents of the ordblist.txt file.
0191
Cannot connect to server database-name on host-name.
Description
It was not possible to connect with the database server.
User action
Please confirm the database server is started.
Please confirm the version of the client and the server.
Make sure the client and server machine are both using the
same TCP/IP port number by verifying the Cincom SQL Access
master_port_id system parameters on both machines.
0193
0194
Server received shutdown command from client.
Description
The shutdown request was received from the client process.
User action
Please contact Cincom Technical Support.
Unknown server request id request-id.
Description
The request from the client is illegal.
User action
Please contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
53
0195
0196
0197
Server communications error: error-id.
Description
The communication error occurred between the server and the
client.
User action
Examine the error log to see if any other errors were detected.
Server name not identified.
Description
When the client process confirmed the connection with the
server, the hostname was invalid.
User action
There is a possibility of the error in the network. Please
confirm network configuration.
Could not make contact with master server.
Description
It was not possible to connect with the master process.
User action
Verify that the client machine can access the server machine
(via ping or some other tool). If network access is OK, then
confirm that the master process is up and running on the server
machine.
Make sure the client and server are of the same release
Make sure the client and server machine are both using the
same TCP/IP port number by verifying the Cincom SQL Access
master_port_id system parameters on both machines.
0198
0199
Receive buffer too small, data truncated.
Description
The communication buffer overflowed.
User action
Please contact Cincom Technical Support.
Server no longer responding.
Description
The client process had issued the request for the server but
there was no response.
User action
Please verify that the client machine can access the server
machine (via ping or some other tool). If the server machine
can be accessed, verify that the database master and server
processes are up and running.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
54
0202
0203
0204
0205
0208
0210
Attribute attr-name was not found.
Description
The specified attribute was not found in the object.
User action
Please validate the class definition and check the attribute
name for spelling errors.
Value for attribute attr-name must be of type expecteddomain, not type given-domain.
Description
The value supplied for the specified attribute is the wrong
domain.
User action
Please check the definition of the attribute and supply a value
of the appropriate domain.
Function called with missing or invalid arguments.
Description
The function or method was called with incorrect arguments.
User action
Please check the arguments of the method or function. Make
sure that DB_OBJECT pointers passed to the function are valid.
Attribute attr-name cannot be made NULL.
Description
The specified attribute cannot accept the NULL value because
it has the NON_NULL constraint.
User action
Either pass a valid non-null value, or change the definition to
remove the NON_NULL constraint.
Method method-name not found.
Description
The specified method did not exist in this class.
User action
Check the class definition and make sure the method specified
is not miss-spelled. Also, ensure that you are using the proper
calling syntax based on the method being a class or instance
method.
Internal error processing object template.
Description
The database attempted to obtain a lock on the class
associated with the template.
User action
Use lockdb utility to determine what users/applications are
holding locks. Retry after locks have been released.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
55
0214
0217
0218
0219
0220
0221
0222
A domain conflict exists on attribute attr-name.
Description
The domain of the specified attribute is not of the expected
object type. The specified attribute was defined to be an
object reference to a particular class, the value supplied is not
an object reference, or it is an object reference of a wrong
class.
User action
Verify the attribute definition. Make sure the value being
passed is an instance of the expected class or an instance of a
subclass of the expected class.
Operation can only be performed on class objects.
Description
The specified function expected a class object pointer, but
received an instance object.
User action
Please correct the code to pass the class object pointer.
Invalid object in db_get path expression.
Description
The path expression contained an invalid object pointer.
User action
Check the definition of the schema to make sure the path
expression is valid based on the schema.
Invalid db_get path expression.
Description
The path expression is invalid.
User action
Check the definition of the schema to make sure the path
expression is valid based on the schema.
Invalid set in db_get path expression.
Description
The path expression referenced a collection attribute that
cannot be found.
User action
Check the definition of the schema to make sure the path
expression is valid based on the schema.
Invalid set index in db_get path expression.
Description
The path expression referenced a non-numeric collection
index.
User action
Correct the index in the path expression.
Attempt to assign string greater than byte-count characters
to attribute attr-name.
Description
The value supplied overflowed the length of the specified
attribute.
User action
Correct the length of the value, or redefine the attribute to
accept a string at least as large as the specified byte-count.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
56
0224
A database has not been restarted.
Description
User action
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
All the following causes are possible:
♦
A connection could not be established with the
database.
♦
The database server has not been started.
♦
The database is not registered in ordblist.txt file.
♦
The connection to the database was lost by an
abnormal communication or other failure.
Depending on the cause of this error, perform one of the
following actions:
♦
Use ping or some other tool to verify that the
network communication is OK.
♦
Verify that the database server is running.
♦
Verify that the database is present in the
ordblist.txt file and that the ORDB_DATABASES
environment variable is set to the directory path
that contains the ordblist.txt file.
♦
Use commdb –h <database host> <database name>
to validate that the database client can
communicate with the database server machine. If
this fails, make sure that the master process is
running on the server machine, and also make sure
that the client and server are both communicating
on the same TCP/IP port number.
57
0225
0226
0227
0228
0229
Missing value for attribute attr-name with the NON NULL
constraint.
Description
The specified attribute cannot accept the NULL value because
it has the NON_NULL constraint. No value was supplied for the
specified attribute.
User action
Either supply a valid non-null value, or change the definition to
remove the NON_NULL constraint.
Empty component list in class.
Description
This is a warning that indicates the requested list is null. This
warning can be returned by functions, which return class
information such as SQLX_get_attributes and
SQLX_get_superclasses.
User action
None, warning only.
Attempt to assign value to attribute attr-name more than
once.
Description
An attribute in an object template was assigned a value more
than once before the object template was finished.
User action
Modify the code to ensure that the attribute is set only once
prior to completing the template.
Method method-name called with arg-count arguments.
system allows a maximum of max arguments.
The
Description
The system cannot pass all the specified arguments to the
specified method.
User action
Reduce the argument count, or you may be able to pass an
argument list as a parameter.
Method method-name requires argument arg-num to be within
the domain domain-name. An invalid value of domain valuedomain was given.
Description
The specified method argument is not of the proper domain.
User action
Make sure that you use the proper domain, or modify the
method definition to accept the passed domain.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
58
0231
0232
0233
0234
0235
Invalid API operation attempted on a temporary object.
Description
An object template was passed to an API function that expects
an object instance.
User action
Correct the code by finishing the template before calling the
API function.
Attempt to use object template over a transaction.
Description
An object template is not valid across transaction boundaries.
User action
Correct the code to ensure that object templates are obtained
within the same transaction they are used.
Cannot create class with basic type name reserved-name.
Description
The specified name is reserved and cannot be used without
enclosing in double quotes.
User action
Please use a different class name, or enclose class name with
double quotes (").
Method file file-name not found.
Description
The specified method implementation file was not found.
User action
Verify the method definition to make sure the proper
implementation file is specified. If definition is correct, ensure
that the file exists.
count unresolved method functions after linking.
Description
One or more method functions could not be dynamically
loaded.
User action
Verify the method definitions to make sure the proper
implementation files are specified. If definitions are correct,
ensure that the files and all dependent libraries are on the
library path of the client application.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
59
0236
0239
0240
0241
0242
0243
0244
Unresolved method method-name.
Description
The method function was not found in the implementation file.
User action
Verify the method definitions to make sure the proper
implementation functions are specified. If definitions are
correct, ensure that the files and all dependent libraries are on
the library path of the client application.
Attribute attr-name was not found.
Description
The attribute with the given name is not defined in the class.
User action
Check the class definition and the spelling of the attribute
name.
Method method-name was not found.
Description
The method with the given name is not defined in the class.
User action
Check the class definition and the spelling of the method
name.
There is no attribute or method with name name.
Description
The specified name is not a defined method nor attribute in
the class.
User action
Check the class definition and the spelling of the specified
name.
Signature for function-name not found for method methodname.
Description
The function specified for the method could not be found in
the method implementation file(s).
User action
Check the definition of the method to make sure the proper
function name is specified.
Argument arg-number of method method-name is undefined.
Description
The method definition does not contain the specified
argument.
User action
Check the definition of the method to make sure the proper
arguments are specified.
Domain name domain is not the name of a class or basic
type.
Description
The domain must be a valid class name or built in type.
User action
Correct the statement to specify the proper domain.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
60
0245
0246
0247
0248
0251
0252
0253
The name attr-name has already been used as the name of an
attribute.
Description
The specified attribute name already exists for this class (or in
a super-class of this class).
User action
Provide an attribute name that is unique within this class and
the super-classes of this class.
The name method-name has already been used as the name of a
method.
Description
The specified method name already exists for this class (or in a
super-class of this class).
User action
Provide a method name that is unique within this class and the
super-classes of this class.
Invalid arguments to schema manager internal function.
Description
An internal error was encountered when processing schema
information.
User action
Contact Cincom Technical Support.
The attribute domain domain-name is not suitable for use
with the UNIQUE integrity constraint.
Description
The specified domain cannot be used in conjunction with the
UNIQUE constraint.
User action
Either remove the UNIQUE constraint or specify a different
domain.
Signature function-name already exists for method methodname.
Description
The specified method function already exists for this method.
User action
Provide a function name for is unique for this method.
Attribute attr-name must have a set domain for that
operation.
Description
The domain of the specified attribute is not a collection type.
User action
Modify the statement to provide a collection for the operation
that is expecting a collection.
Attribute attr-name cannot be defined with a nested set
domain.
Description
A collection may not contain other collections.
User action
Correct the statement in error so that a collection will not
contain another collection.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
61
0254
0256
0257
0258
Unable to remove domain domain-name from attribute attrname.
Description
The specified domain is not a valid domain in the specified
collection attribute.
User action
Verify the collection domain that you are trying to remove.
Superclass already exists.
Description
The class already inherits from the superclass.
User action
Validate the superclass name.
Superclass addition would cause cycles in class hierarchy.
Description
A recursive definition has been encountered; a class cannot be
a sub-class of itself.
User action
Verify your class hierarchy.
Superclass not found.
Description
The superclass is not defined.
User action
Make sure the superclass is defined before inheriting from it.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
62
0259
0260
0261
0263
0266
0269
0271
Multiple signatures exist for method method-name.
Description
More than one identical method function was found in the
method implementation file(s).
User action
Identify the duplicate entry points and remove or rename the
identical names.
Argument arg-number of method method-name is not of a set
domain.
Description
The specified argument to the method is not a valid collection
domain.
User action
Verify the method definition and make sure the method call is
passing a value of the proper domain.
Resolution for name not found.
Description
The name specified in the conflict resolution cannot be found.
User action
Check the schema definition and make sure the attribute or
method that was in conflict exists in the class specified in the
conflict resolution clause (i.e., inherit name of <class>).
Schema manager internal corruption detected.
Description
An internal error was encountered when processing schema
information.
User action
Contact Cincom Technical Support.
Name conflict on attribute attr-name with classes class-1
and class-2.
Description
The specified attribute name exists in both of the specified
classes, the system cannot resolve the multiply inherited
attribute.
User action
Review the schema definition and the resolve the conflict by
explicitly inheriting the attribute from the proper class.
Cannot define index on domain domain-name.
Description
The specified domain cannot be included in an index definition.
User action
You will not be able to include the attribute of the specified
domain in the index.
Detected cycle in class hierarchy; subclass is a super
class of superclass.
Description
A recursive definition has been encountered; a class cannot be
a subclass of itself.
User action
Verify your class hierarchy.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
63
0272
0273
0274
0275
0276
0278
Index already defined for attribute attr-name.
Description
An index already exists for the specified attribute.
User action
None, information only.
Index index-name does not exist.
Description
The specified index is not defined.
User action
Check the schema definition and verify the index name.
Illegal characters in name: illegal-name.
Description
Illegal characters were encountered in the specified name.
User action
Verify the use of the name. You need enclose the class name
in double quotes if the specified name is a valid class name.
Illegal operation on attribute attr-name inherited from
class superclass.
Description
The attempted alteration of the specified inherited attribute
cannot be performed as an operation on this class.
User action
Perform the operation on the superclass specified. Be sure to
verify that the change will not adversely affect other
subclasses.
Illegal operation on method method-name, inherited from
class superclass.
Description
The attempted alteration of the specified inherited method
cannot be performed as an operation on this class.
User action
Perform the operation on the superclass specified. Be sure to
verify that the change will not adversely affect other
subclasses.
Class class-name has incompatible domains for attr-name,
inherited from classes superclass1 and superclass2.
Description
The specified attribute, inherited from the specified
superclasses, does not have compatible domains. The class
cannot inherit from both of the specified superclasses.
User action
If you need to inherit from both classes, then the definition of
one of the superclasses has to be modified. You may want to
rename the attribute in one of the superclasses, or you can
alter the domain of one or both of the conflicting attributes to
be compatible.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
64
0279
0280
0281
In class class-name, name inherited from class superclass1
cannot be used as requested. The definition from class
superclass2 has a more specific domain.
Description
Only the most specific domain of the specified attribute may
be inherited.
User action
You have to inherit the more specific definition of the specified
attribute. You may also inherit the less specific attribute by
using an alias name on the inherit clause (e.g., INHERIT name
OF superclass2 AS new-name).
In class class-name, attr-name cannot be inherited from
class superclass because there is a local definition with
an incompatible domain.
Description
The specified attribute does not have a compatible domain
with the attribute with the same name in the specified
superclass.
User action
You may want to rename the attribute in one of the classes, or
you can alter the domain of one or both of the conflicting
attributes to be compatible.
In class class-name, name inherited from class superclass
is aliased but no substitute from another source was found.
Description
The specified attribute or method name is not in conflict.
User action
Remove the INHERIT clause for the specified name.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
65
0282
0283
0284
0285
In class class-name, name inherited from class superclass1
cannot serve as an alias substitute for class superclass2.
The domains are incompatible.
Description
The specified attribute does not have a compatible domain
with the attribute with the same name in the specified
superclass. (This is identical to error number 0280 except an
alias was specified on the INHERIT clause).
User action
You may want to rename the attribute in one of the classes, or
you can alter the domain of one or both of the conflicting
attributes to be compatible.
In class class-name, name inherited from class superclass1
cannot serve as an alias substitute for class superclass2.
It has a less specific domain.
Description
Only the least specific domain of the specified attribute may
be aliased.
User action
You have to inherit the more specific definition of the specified
attribute without an alias. You may also inherit the less
specific attribute by using an alias name on the inherit clause
(e.g., INHERIT name OF superclass2 AS new-name).
Cannot request inheritance of attr-name because it is
defined locally in the class.
Description
You cannot inherit an attribute with the same name as an
attribute in the class.
User action
You can change the name of the attribute in one of the classes,
or you can use an alias to inherit the specified attribute (e.g.,
INHERIT attr-name OF superclass AS new-name).
Cannot use alias-name as an alias for inherited component
inherited-component because there is already a locally
defined component with that name.
Description
The specified alias name is already defined.
User action
Please choose a different alias name.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
66
0286
0291
0293
0294
0296
Cannot use alias-name as an alias for inherited-component
of superclass1. A component with that name is already
inherited from superclass2.
Description
The specified alias name is already defined in the specified
superclass.
User action
Please choose a different alias name.
name is defined in class superclass1 as an attribute and in
class superclass2 as a method.
Description
The specified name is an attribute in one superclass and a
method in the other superclass.
User action
You should rename the attribute or method in one of the
superclasses.
Operation not allowed for this class type.
Description
The attempted operation is not valid for this type of class. For
example, you can only add a query to a virtual class or a
foreign table.
User action
Verify the class definition and make sure the operation is valid.
Undefined environment variable env-var referenced in method
file.
Description
The method definition uses the specified environment variable,
and the environment variable is not defined.
User action
Make sure the environment variable is defined on all machines
that will execute the method.
Invalid property list encountered.
Description
This error occurs when multiple clients are running with the
TRAN_COMMIT_CLASS_UNCOMMITED_INSTANCE isolation level,
and the clients are maintaining database collections. The
“dirty” collections have caused an error to be encountered in
the database.
User action
Use a more restrictive isolation level.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
67
0297
0298
0300
0305
0308
0309
Alias name alias-name is used more than once.
Description
The specified alias name is already defined.
User action
Please choose a different alias name.
In class class-name, a resolution for name of superclass is
not allowed. That class is not a super class.
Description
The superclass specified in the INHERIT clause is not a
superclass of the class being altered or created.
User action
Verify the superclass name in the INHERIT clause.
Attribute attr-name cannot be defined with both a DEFAULT
value and the UNIQUE integrity constraint.
Description
An attribute cannot be defined using both the DEFAULT value
and the UNIQUE constraint.
User action
Remove the DEFAULT value or remove the UNIQUE constraint.
Sequence index %1$d is out of bounds.
Description
The specified index is not valid for collection.
User action
Make sure the specified index is not negative, and it is not
equal to or greater than the number of elements in the
collection. (Collections start at element 0).
Element value is not within the domain of the set.
Description
The domain of the value is not valid for the collection.
User action
Make sure the value is valid for the collection, or you could
consider modifying the acceptable domains of elements in the
collection.
Illegal set element index given: %1$d.
Description
The specified index is not valid for the collection.
User action
Make sure the specified index is not negative, and it is not
equal to or greater than the number of elements in the
collection. (Collections start at element 0).
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
68
0311
0312
0313
0314
Element not found in sequence.
Description
The specified value was not found in the collection.
User action
This is an information message, no action required.
domain is not a valid set domain.
Description
The database has detected a collection value container, which
is not a valid collection type (e.g. it is not a SET, SEQUENCE, or
MULTISET).
User action
Check your code to insure the value container has not been
erroneously modified.
Object buffer underflow while reading.
Description
Internal database error encountered.
User action
Please contact Cincom Technical Support.
Object buffer overflow while writing.
Description
Internal database error encountered.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0315
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
Illegal metaclass definition encountered.
Description
Internal database error encountered.
User action
Please contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
69
0316
Transformer size calculation mismatch, expected sizeexpected calculated size-calculated.
Description
Internal database error encountered.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0317
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
Invalid disk representation encountered for class classname
Description
Internal database error encountered.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
70
0318
Out of sync during object loading. Database is likely
corrupted or out of date.
Description
Internal database error encountered.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0321
0322
0323
0324
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
Possible corruption in the workspace detected.
Description
Internal database error encountered.
User action
Please contact Cincom Technical Support.
MOP not found in the workspace.
Description
Internal database error encountered.
User action
Please contact Cincom Technical Support.
Attempt to upgrade non-temporary MOP in workspace.
Description
Internal database error encountered.
User action
Please contact Cincom Technical Support.
Object found in workspace without class.
Description
Internal database error encountered.
User action
Please contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
71
0325
0326
0327
0328
0330
0331
Attempt to garbage collect a MOP in the dirty list.
Description
Internal database error encountered.
User action
Please contact Cincom Technical Support.
Changing class pointer for object in workspace.
Description
The workspace object instance and the actual instance do not
agree on their owning class. The database has automatically
corrected the problem.
User action
This is an informational message only, and no corrective action
is necessary.
Cannot create MOP with NULL OID.
Description
Internal database error encountered.
User action
Please contact Cincom Technical Support.
Instance encountered in workspace without class.
Description
Internal database error encountered.
User action
Please contact Cincom Technical Support.
Workspace pin violation.
Description
Internal database error encountered.
User action
Please contact Cincom Technical Support.
Could not allocate workspace block from OS, out of virtual
memory. Aborting transaction.
Description
The transaction has been rolled back because the operation
could not obtain workspace memory required.
User action
Allocate more workspace, or wait until other transactions have
release some memory.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
72
0332
0333
0334
0335
0336
0337
0338
Original workspace size estimate exceeded.
extension has been made.
An automatic
Description
The workspace size has been increased.
User action
This is an informational message only, and no corrective action
is necessary.
Out of memory during workspace storage allocation.
Aborting transaction.
Description
The transaction has been rolled back because the operation
could not obtain workspace memory required.
User action
Allocate more workspace, or wait until other transactions have
release some memory.
Attempted allocation of size bytes is larger than maximum
workspace block size. Try adjusting max_block_size
parameter. Transaction aborted.
Description
The transaction needed more workspace than the maximum
allowed by the Cincom SQL Access system parameter
max_block_size.
User action
Adjust the value of the max_block_size system parameter.
Ignoring attempt to free object not allocated within the
workspace.
Description
The object attempting to be released does not exist in the
workspace.
User action
Verify your use of the API.
Ignoring attempt to free an object more than once.
Description
An attempt was made to release memory that has already been
released.
User action
Verify your use of the API.
Ignoring attempt to allocate object with negative size.
Description
Internal allocation error.
User action
Please contact Cincom Technical Support.
Map entry identifier overrun.
Description
Internal error.
User action
Please contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
73
0340
0343
0344
0345
0347
Cannot fork child process.
Description
Error encountered while attempting to create a process.
User action
Reduce the load of the machine and try again.
Request_id's used up.
Description
Error encountered while attempting to allocate a request
identifier for client server communications.
User action
Please check the network connection between the client(s) and
server.
process-name.
Description
The specified process was shut down.
User action
This is an informational message only, and no corrective action
is necessary.
Error reading shutdown message from master.
Description
Error encountered when attempting to read the shutdown
message received from the master process.
User action
Verify communications between master and server.
Could not establish a pipe to the master server.
Description
Error establishing network communication between master and
server.
User action
Verify communications between master and server.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
74
0348
0349
0350
0351
0352
Must specify either service or port identifier.
Description
The master and servers must have either a network service
name or a TCP/IP port number specified.
User action
Check the TCP/IP port and service configuration on the server
machine. Confirm the settings of the Cincom SQL Access
system parameters master_port_id and network_service_name.
Unknown service for TCP: %1$s.
Description
The specified TCP/IP service was not found.
User action
Check the TCP/IP port and service configuration on the server
machine. Confirm the settings of the Cincom SQL Access
system parameters master_port_id and network_service_name.
Error getting local host by name for host "%1$s". Host not
found.
Description
Unable to find specified host.
User action
Please confirm the TCP/IP settings of the host machine.
Cannot create TCP socket.
Description
Unable to create TCP socket.
User action
Make sure there are enough network resources on the machine.
Verify network communications between the client and server
machine.
tcp_open: cannot get a reserved TCP port.
Description
The TCP port was unable to be reserved.
User action
Make sure there are enough network resources on the machine.
Verify network communications between the client and server
machine.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
75
0353
0355
0356
0357
0358
0359
0360
Cannot make connection to master server.
Description
The master service could not be found.
User action
Verify that the client and master are using the same port id for
communications.
Cannot create socket stream.
Description
Unable to create TCP/IP socket stream.
User action
Make sure there are enough network resources on the machine.
Verify network communications between the client and server
machine.
Cannot bind local address... retrying.
Description
Message that is generated when TCP/IP socket binding is reattempted after failure.
User action
This is an informational message only, and no corrective action
is necessary.
Cannot bind local address... aborting.
Description
Unable to bind to the TCP/IP socket.
User action
Make sure there are enough network resources on the machine.
Verify network communications between the client and server
machine.
Accept failed.
Description
Network communication error has been detected.
User action
Make sure there are enough network resources on the machine.
Verify network communications between the client and server
machine.
Datagram bind error.
Description
Network communication error has been detected.
User action
Make sure there are enough network resources on the machine.
Verify network communications between the client and server
machine.
Datagram accept error.
Description
Network communication error has been detected.
User action
Make sure there are enough network resources on the machine.
Verify network communications between the client and server
machine.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
76
0361
0362
0363
0364
Datagram connect error.
Description
Network communication error has been detected.
User action
Make sure there are enough network resources on the machine.
Verify network communications between the client and server
machine.
Datagram socket error.
Description
Network communication error has been detected.
User action
Make sure there are enough network resources on the machine.
Verify network communications between the client and server
machine.
Recvmsg from master socket failed.
Description
Network communication error has been detected.
User action
Make sure there are enough network resources on the machine.
Verify network communications between the client and server
machine.
Sending a new request to server.
Description
Network communication error has been detected.
User action
Make sure there are enough network resources on the machine.
Verify network communications between the client and server
machine.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
77
0367
0368
0369
0373
0374
0375
0376
Server server-name already exists.
Description
The specified server is already running.
User action
Verify the server name. It is possible to run more than one
server with the same name as long as both servers have their
own ordbinit.txt file and ordbIist.txt file. Each server would
need to have different master processes using unique port ids
(See master_port_id system parameter). The clients would
have to ensure that they specify the proper port id of the
master process that is controlling connections to the desired
server.
Communication error during connect for server-name.
Description
Network communication error has been detected while
attempting to connect to the specified server.
User action
Make sure there are enough network resources on the machine.
Verify network communications between the client and server
machine.
Cannot allocate more MOPs.
Description
The client interface could not allocate memory.
User action
Either allocate more memory for the machine, or reduce the
amount of memory in use.
Premature EOF during read: error-code.
Description
Unexpected end of file encountered for the X11 bitmap.
User action
Verify that the file is a valid X11 bitmap..
Premature EOF during read of code1 or code2.
Description
Unexpected end of file encountered for the X11 bitmap.
User action
Verify that the file is a valid X11 bitmap.
Conversion error on (hexval) nibble1 and nibble2 converted
to value.
Description
Invalid data encountered in the X11 bitmap.
User action
Verify that the file is a valid X11 bitmap.
Error finding class public.
Description
The public user could not be found.
User action
Make sure the default public user is defined.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
78
0377
0378
0379
0380
0381
Error error-code adding attribute attr-name to multimedia
hierarchy.
Description
The specified error code was received while attempting to add
the attribute to the multimedia class hierarchy.
User action
Re-attempt the createdb command.
Error error-code adding method method-name implemented as
function-name to multimedia hierarchy.
Description
The specified error code was received while attempting to add
the method to the multimedia class hierarchy.
User action
Re-attempt the createdb command.
Error error-code adding superclass to multimedia hierarchy.
Description
The specified error code was received while attempting to add
a superclass to the multimedia class hierarchy.
User action
Re-attempt the createdb command.
Dynamic loader already initialized.
Description
An attempt has been made to re-initialize the dynamic loader.
User action
Please contact Cincom Technical Support.
Dynamic loader not initialized.
Description
The dynamic loader could not be initialized.
User action
Check your environment variables required by your operating
system to ensure that the Cincom SQL Access libraries can be
loaded.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
79
0382
0383
0384
0385
0386
0387
Dynamic loader improperly initialized.
Description
The dynamic loader has encountered an error during
initialization.
User action
Please contact Cincom Technical Support.
file-name is not an object file or an archive.
Description
When attempting to load the specified file, the dynamic loader
detected that the file is not valid.
User action
Verify that the files required for pre-loaded methods are valid.
Cannot determine absolute path for file-name.
Description
The dynamic loader could not determine the path for the
specified file.
User action
Check your environment variables required by your operating
system to ensure that the Cincom SQL Access libraries can be
loaded.
ld process exited with code error-code.
Description
The dynamic loader received the specified error.
User action
Make sure that the machine has enough resources to handle the
number of processes required.
ld process exited due to signal signal-code.
Description
The dynamic loader received the specified signal.
User action
Make sure that the machine has enough resources to handle the
number of processes required.
ld process exited with unknown waitval code.
Description
The dynamic loader received the specified code.
User action
Make sure that the machine has enough resources to handle the
number of processes required.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
80
0388
Cannot access initial image for image-name.
Description
The dynamic loader encountered an error during the load of
the specified image.
User action
Make sure that the machine has enough resources to handle the
number of processes required.
Check your environment variables required by your operating
system to ensure that the Cincom SQL Access libraries can be
loaded.
0389
0390
0392
0393
SYSTEM ERROR: error-code.
Description
Specified system error detected.
User action
Please contact Cincom Technical Support.
Problem with file-name: error-text.
Description
The dynamic loader encountered the specified error while
loading the specified file.
User action
Verify that the file is a valid object file.
Unable to spawn dynamic loader daemon.
Description
The dynamic loader process could not be created.
User action
Make sure that the machine has enough resources to handle the
number of processes required.
Dynamic loader daemon has disappeared.
Description
The dynamic loader process could not be located.
User action
Make sure that the machine has enough resources to handle the
number of processes required.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
81
0406
Invalid B+tree index identifier: (vfid = (file-id, volumeid), rt_pgid: page-id).
Description
The system detected an invalid index page.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0407
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
Unknown key index-key referenced in B+tree index { vfid =
(file-id, volume-id), rt_pgid: page-id, key_type: keytype}.
Description
The system detected an invalid index entry.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
82
0409
Duplicate value (oid) volume-id|page-id|slot-id|new slot
mark referenced.
Description
A duplicate object identifier has been encountered.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0410
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
Null key referenced.
Description
The system has encountered a null B+tree key.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
83
0412
Invalid range search specification.
Description
The system has encountered an invalid B+tree index range.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0416
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
Unknown representation identifier: rep-id.
Description
The system detected an invalid identifier.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported, this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time and
contact Cincom Technical Support.
-
If checkdb found problems, you should restore
the database from your current backup.
84
0423
0424
0425
0427
0428
0429
Invalid session.
Description
The API program passed an invalid DB_SESSION.
User action
Confirm that the program is passing a valid DB_SESSION
pointer.
No statement to execute.
Description
The API program has passed an empty SQL statement for
compilation.
User action
Confirm that the program is passing an SQL statement.
Incompatible data type for attribute attr-name of class
class-name.
Description
The parser has detected an incompatible data-type for the
specified attribute of the specified class.
User action
Please correct the SQL statement.
Data overflow on data type domain-name.
Description
The parser has detected that data passed for the specified
domain would overflow the domain.
User action
Please correct the SQL statement.
Statement is not updateable.
Description
The attempted operation could not be performed because the
object is not updateable.
User action
Examine the schema and code. Make sure you have the proper
permissions to update the entity in question.
Unknown command.
Description
The specified command is not recognized.
User action
Examine and correct the SQL command.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
85
0430
0431
0434
0440
0441
0442
0443
Unknown variable variable-name.
Description
The specified variable could not be identified during the
method call.
User action
Validate the method call to make sure proper parameters are
being passed.
Error in SQL/X interpreter or parser.
Description
The parser has encountered an inconsistent definition in the
ORDB server.
User action
Make sure that the foreign table mappings between your ORDB
server and foreign database are valid.
Cannot find correct column names from a query.
Description
The query result does not contain the requested column(s).
This error occurs when the API program is attempting to access
a column from the current result set row by column heading
name of the result set.
User action
Verify the spelling of the requested name.
Invalid cursor position.
Description
The cursor of the result set is not valid for the attempted
operation.
User action
Verify that the program is properly handling the cursor state.
Invalid cursor operation.
Description
SQLX_get_query_oid API function was invoked but the OID was
not included in the query result set.
User action
Use SQLX_execute_oid() or SQLX_include_oid() functions so
that the OID will be included in the query result set.
Unknown cursor position.
Description
The cursor of the result set is not valid for the attempted
operation.
User action
Verify that the program is properly handling the cursor state.
Tuple value index column-index is out of range.
Description
The specified index is not valid for the result set. This can
occur when requesting the data from an invalid column number
of the result set.
User action
Check the code to make sure the index is valid for the result
set.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
86
0444
0445
0447
0449
Invalid attribute name: column-name.
Description
The specified column name is not valid for the result set. This
can occur when requesting the data from an invalid heading
name of the result set.
User action
Check the code to make sure the name is valid for the result
set.
Value list index index-number is out of range.
Description
The specified index is not valid for the result set. This can
occur when requesting the data from an invalid column number
of the result set.
User action
Check the code to make sure the index is valid for the result
set.
An operation has been attempted on a closed query result
structure.
Description
The requested operation is only valid on open query result sets.
User action
Update the code to make sure the operation is only performed
when the query result set is open.
Unknown query identifier: query-id
Description
The specified query identifier was invalid.
User action
Make sure the query identifier passed to the API function has
not been modified by the program.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
87
0452
0454
0455
0456
0457
0458
Invalid XASL tree node content.
Description
The database has detected an internal error in the execution
tree.
User action
Please contact Cincom Technical Support.
Invalid data type referenced.
Description
The database encountered an invalid data type during the
operation. This is often caused by passing incorrect data to a
DB_VALUE container construction function.
User action
Analyze the program to make sure valid data is being used.
No more query file pages left.
Description
The query processor ran out of temporary pages when
attempting to build the result set.
User action
Please increase the temporary volume space available to the
database.
Data type references are incompatible.
Description
Internal error. The query processor has encountered
incompatible data types during query execution.
User action
Please contact Cincom Technical Support.
Invalid query result type.
Description
Internal error. The query processor has encountered an invalid
query result type during query execution.
User action
Please contact Cincom Technical Support.
Overflow happened in addition context.
Description
The addition of two values caused an overflow during query
processing.
User action
Modify the SQL statement to use a larger domain.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
88
0459
0461
0462
0463
0464
0465
Query result does not contain a single value.
Description
The context of the query or subquery expects a single result,
and more than one result was found.
User action
Review the SQL statement for correctness. You may be able to
add the DISTINCT keyword to achieve the desired results.
More host variables are given than result columns.
Description
The number of output host variables exceeds the number of
columns in the result set.
User action
Correct the esqlx program to make the number of output host
variables match the number of columns in the result set of the
SQL statement.
Result value is NULL, but there is no indicator variable.
Description
Internal error.
User action
Please contact Cincom Technical Support.
Cursor statement has not yet been prepared.
Description
The SQL statement name associated with the cursor has not
been prepared.
User action
You must issue a EXEC SQLX PREPARE for the statement in
question prior to using the cursor.
Cursor should be a SELECT statement.
Description
Attempted to use a cursor on an SQL statement that does not
produce a result set.
User action
Make sure that cursors are only used for SQL SELECT
statements.
The cursor is not yet opened.
Description
The cursor operation is only valid on an open cursor.
User action
Modify the program to make sure that the cursor is open.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
89
0466
0467
0468
0469
0470
0472
0473
The cursor should be closed before re-opening.
Description
An attempt is being made to open a cursor that is already
open.
User action
Close the open cursor before re-opening it.
Result should return a single object.
Description
The SQL command expects a single result, and more than one
result was found.
User action
Review the SQL statement for correctness. You may be able to
add the DISTINCT keyword to achieve the desired results.
No positional markers are allowed in EXECUTE IMMEDIATE
statements.
Description
SQL Commands that are processed with EXEC SQLX EXECUTE
IMMEDIATE may not use input markers.
User action
Either change the program to use PREPARE and EXECUTE, or
get rid of the input markers by placing the actual values in the
statement.
Invalid data type used.
Description
When the DB_VALUE container was initialized, the data type of
the domain was invalid.
User action
Modify the code to use compatible domains.
Query involves too many items for optimizer.
Description
The SQL statement is too complicated to be processed by the
query optimizer.
User action
Reduce the complexity of the query.
adapter-name adapter for foreign database fdb-name on host
host-name has died.
Description
The foreign database adapter process is no longer available.
User action
Check the status of the host machine. Make sure the master
process is available on the client and host machine.
Reported from fdb_name on host host-name error-text.
Description
The foreign database adapter running on the specified host
machine is reporting the specified error. The error-text is the
error message received from the foreign database.
User action
Consult the error documentation for the foreign database.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
90
0474
0475
0476
0477
Error error-text detected during adapter-type functionname.
Description
The specified error occurred while the ORDB server was
attempting the specified function for the foreign database
adapter.
User action
Verify your ORDB server definition. Make sure the adapters are
available on their registered host. Consult the foreign
database error documentation.
No query specification with index query-statement-number.
Description
The specified query-statement-number passed to the
SQLX_change_query_spec is not a valid query index for the
virtual class.
User action
Check the schema and make sure a valid index is used.
Foreign database fdb-name already exists.
Description
The specified foreign database is already defined in this
schema.
User action
Choose a new name that is unique within the schema.
Could not connect to master on host host-name to access
foreign database fdb-name.
Description
The system was unable to establish a connection to the master
process on the specified host.
User action
Make sure the master process is started on the host machine.
Make sure the client and host machine are using the same
TCP/IP port number for Cincom SQL Access communications.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
91
0478
0479
0480
0483
0484
The foreign database fdb-name is not a registered FDB.
Description
The specified foreign database is not registered in the schema.
User action
Verify the foreign database name.
The foreign database fdb-name is currently being accessed
by other clients, alteration or drop is not allowed.
Description
The operation on the specified foreign database definition
cannot be carried out because the foreign database is currently
being used.
User action
Retry the operation after other transactions have completed.
The foreign database fdb-name is not empty and cannot be
dropped.
Description
You cannot drop the specified foreign database because foreign
tables are still defined on the foreign database.
User action
You will have to drop all the foreign tables on the specified
foreign database before you can drop the foreign database.
attribute-name is not an attribute of the class class-name.
Description
The specified attribute is not an attribute of the specified
class.
User action
Check the schema definition and correct the attribute or class
name accordingly.
The object_id for foreign table foreign-table-name is
already set.
Description
The specified foreign table already has an object_id specified.
User action
Check the schema for the foreign table in question.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
92
0485
0486
0489
0490
0491
One or more object_id attributes are NULL for instance of
foreign table foreign-table-name.
Description
One of the attribute values that compose the object_id for the
foreign table is null. This is invalid.
User action
The attribute values that make up the object_id cannot be
null. Check the foreign database documentation to see if you
can define a unique constraint for the attribute that maps to
the object_id. If the object_id is composed of multiple
attributes, you may be able to define a unique index on the
attributes that make up the object_id.
Object is not an updateable virtual class instance.
Description
The virtual object cannot be updated.
User action
Verify the virtual class is defined in a way that allows updating.
An attribute of a foreign table may not be a class, virtual
class, or object.
Description
The domain of an attribute in a foreign table cannot reference
a (non-foreign table) virtual class, or a base class. The generic
OBJECT domain is also invalid.
User action
Modify the foreign table. An attribute in a foreign table can
have a domain that maps to another foreign table.
The superclass super-name must be of the same type of class
as class-name.
Description
The class and super-class must be the same type (foreign table,
virtual class, or base class).
User action
Correct the schema operation.
Cannot extract entity name from foreign table query
specification query-spec.
Description
One or more of the attributes referenced in the query-spec
could not be found in the foreign database schema.
User action
Correct the foreign table definition.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
93
0492
0493
0494
0495
0501
0502
0503
error-text
Description
Internal error detected during parsing.
User action
Please contact Cincom Technical Support.
Syntax: error-text
Description
The parser detected the specified syntax error.
User action
Please correct the syntax.
Semantic: error-text
Description
The parser detected the specified semantic error.
User action
Please correct the syntax.
Execute: error-text
Description
Internal error detected during execution.
User action
Please contact Cincom Technical Support.
Invalid trigger priority.
Description
The priority level of the trigger is invalid.
User action
Please specify a positive value or 0 for the priority of the
trigger.
Missing target class in trigger.
Description
The trigger could not be created because the target class or
attribute was not specified.
User action
Correct the trigger definition.
Trigger trigger-name was not found.
Description
The specified trigger was not found.
User action
Check the schema for the proper trigger name.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
94
0505
0506
0507
0508
0511
0512
A trigger with the name trigger-name already exists.
Description
A trigger with the specified name already exists.
User action
Choose a new, unused trigger name.
A trigger cannot be defined on vclass-name because it is a
virtual class.
Description
Triggers cannot have a virtual class as a target.
User action
Use triggers on base classes only.
Inappropriate trigger target class class-name.
Description
This trigger event cannot have a class target.
User action
Correct the trigger definition.
Inappropriate trigger target attribute attribute-name.
Description
This trigger event cannot have an attribute target.
User action
Correct the trigger definition.
Not authorized to access trigger trigger-name.
Description
The current user does not have authority to access the
specified trigger. If the trigger is for a particular class event,
SELECT authority to the target class is required. User triggers
can only be accessed by their owner.
User action
Please give an appropriate authority to the user.
Not authorized to delete trigger trigger-name
Description
The current user does not have authority to delete the
specified trigger. If the trigger is for a particular class event,
DELETE authority to the target class is required. User triggers
can only be deleted by their owner.
User action
Please give an appropriate authority to the user.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
95
0514
0515
0516
0517
0518
Not authorized to alter trigger trigger-name
Description
The current user does not have authority to alter the specified
trigger. If the trigger is for a particular class event, ALTER
authority to the target class is required. User triggers can only
be altered by their owner.
User action
Please give an appropriate authority to the user.
Trigger action execution time of action-time cannot be
earlier than condition execution time of condition-time.
Description
The specified action-time conflicts with the specified
condition-time. Example of this error would be to define a
DEFERRED condition-time and AFTER action-time.
User action
Correct the definition so that the action time is later than the
condition time.
Maximum trigger depth max-depth exceeded at trigger
trigger-name.
Description
The maximum number of triggers executed for a single
statement was reached.
User action
Verify that your triggers will not result in an infinite loop. You
can modify the maximum depth with the ‘SET TRIGGER
MAXIMUM DEPTH <max-depth>’ command. Specify the keyword
INFINITE for <max depth> to bypass trigger depth checking.
The operation has been rejected by trigger trigger-name.
Description
The command or transaction was rejected by the specified
trigger.
User action
None, informational only.
Internal error processing trigger trigger-name.
Description
The system detected an error while processing the trigger
operation.
User action
Please check the uclient.err file of the current directory for
details of the error.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
96
0519
0520
0521
0523
0524
Illegal trigger condition type.
Description
The trigger condition must be a BOOLEAN expression. This
trigger condition is either non-BOOLEAN or the data-types of
the items being compared are incompatible.
User action
Please correct the trigger to make sure the expression returns a
BOOLEAN and that the data-types being compared are
compatible.
The REJECT action cannot be used with an action time of
AFTER or DEFERRED.
Description
The REJECT action is only valid with an action time of BEFORE.
User action
Use BEFORE as the action time.
The REJECT action cannot be used with the ABORT or TIMEOUT
events.
Description
The REJECT cannot be specified with the ABORT nor the
TIMEOUT events.
User action
Correct the trigger definition.
Trigger action expression was not given.
Description
The trigger action is invalid.
User action
Correct the trigger definition. The valid actions are: REJECT,
INVALIDATE TRANSACTION, PRINT, CALL, INSERT, UPDATE,
DELETE, and EVALUATE.
The specified activity cannot be removed because it is
owned by another user.
Description
An authorization error was encountered when executing the
SQLX_drop_deferred_activities() function. This can happen
when the user executing the function does not have
authorization on the classes referenced by the trigger.
User action
Verify the user authorization for the classes involved in the
trigger.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
97
0525
0526
0527
0528
0529
0530
Error compiling condition for trigger-name: error-msg
Description
The specified error was generating while compiling the
condition expression of the specified trigger.
User action
Correct the condition expression of the trigger.
Error compiling action for trigger-name, error-msg
Description
The specified error was generating while compiling the action
expression of the specified trigger.
User action
Correct the action expression of the trigger.
Error evaluating condition for trigger-name: error-msg
Description
The specified error was generating while evaluating the
condition expression of the specified trigger.
User action
Correct the condition expression of the trigger.
Error evaluating action for trigger-name, error-msg
Description
The specified error was generating while evaluating the action
expression of the specified trigger.
User action
Correct the action expression of the trigger.
Transaction cannot be committed, it was invalidated by
trigger trigger-name.
Description
The specified trigger has marked this transaction as invalid,
transaction cannot be committed.
User action
This is an informational message only, and no corrective action
is necessary.
Missing regular expression.
Description
A regular expression was expected and not found for the
operation being attempted.
User action
Modify the code to pass a proper regular expression.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
98
0531
0532
0534
0535
0536
0537
0538
0539
Regular expression is too long or complex.
Description
The system does not have enough resources to analyze the
regular expression.
User action
Simplify the expression, or use multiple operations.
Unbalanced parenthesis or brackets in regular expression.
Description
The number of left and right parentheses or brackets in the
regular expression does not match.
User action
Correct the regular expression.
Illegal character or syntax in regular expression.
Description
Syntax error was found in the regular expression.
User action
Correct the regular expression.
No text given for regular expression search.
Description
The regular expression function was not supplied with any text
to search.
User action
Modify the code to make sure you pass the buffer to be
searched.
Illegal opcode found in regular expression.
Description
The regular expression contains an illegal operation.
User action
Correct the regular expression.
Illegal search command code for regular expression
compiler.
Description
Internal error encountered while executing the regular
expression.
User action
Please contact Cincom Technical Support.
Regular expression working buffer needs to be initialized.
Description
This could mean that the system is running short on memory
and the needed buffers could not be allocated.
User action
Verify the memory during the processing, try to free some up if
memory is low.
Attempt to divide by zero.
Description
The system detected a divide by zero condition.
User action
Correct the code.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
99
0540
0541
0542
0543
0544
0545
0547
error-text
Description
The specified error was encountered by the server during
trigger processing.
User action
Refer to the documentation for the specified error.
Number of free pages for volume volume-name is
inconsistent. free-header and free-bitmap were found
according to volume header and bitmap, respectively.
Description
Checkdb detected the specific database problem.
User action
Restore the database from a previous backup.
Number of free sectors for volume volume-name is
inconsistent. free-header and free-bitmap were found
according to volume header and bitmap, respectively.
Description
Checkdb detected the specific database problem.
User action
Restore the database from a previous backup.
Disk header for volume volume-name is inconsistent.
Description
Checkdb detected the specific database problem.
User action
Restore the database from a previous backup.
INTERNAL ERROR: Btree key keyvalue entry for object OID:
object-id was not found on B+tree: BTree-id.
Description
Checkdb detected an index error.
User action
Drop the index and then recreate the index.
INTERNAL ERROR: Key and OID: object-id entry on B+tree:
BTree-id is incorrect. The object does not exist.
Description
Checkdb detected an index error.
User action
Drop the index and then recreate the index.
Server release server-release is different from client
release client-release.
Description
The specified client and server releases of Cincom SQL Access
are not compatible.
User action
Make sure you are using the proper version of the client and/or
server.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
100
0549
0550
0551
0552
0553
The foreign table instance was not found.
Description
A specific instance of a foreign database could not be accessed
to complete the processing. This can happen when other
applications of the foreign database are updating the foreign
database concurrently.
User action
Retry the operation.
Unknown savepoint name savepoint
Description
A partial rollback to the specified savepoint was requested, but
the savepoint could not be identified.
User action
Verify the code to make sure the proper savepoint id is being
used.
Unable to locate volume information path file file-name...
Continue reading from internal tables
Description
The database information file could not be found.
User action
Make sure the information file was nor inadvertently moved or
renamed. The database may need to be recreated.
Date arithmetic underflow.
Description
An underflow was detected when processing a date.
User action
Check the data for valid dates.
Time arithmetic underflow.
Description
An underflow was detected when processing a time.
User action
Check the data for valid times.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
101
0554
0555
0556
0559
0560
0561
The loader has entered an invalid state.
operations are possible.
No further
Description
The database loader has detected a severe error.
User action
Contact Cincom Technical Support.
Memory allocation error during database loading.
Description
The database loader ran out of memory.
User action
Use the –c option of loaddb to increase the frequency that
COMMITs are issued by the loader. Verify the memory status of
the machine.
Too many values supplied.
Expecting value-count.
Description
The loaddb input file contains more attribute values for a class
than there are actual attributes in the class.
User action
Verify the loader input file against the database schema.
For attribute attr-name of class-name, expected type
expected-domain, got received-domain.
Description
The loaddb process detected the specific domain
incompatibility.
User action
Correct the loader input file or database schema definition for
the attribute.
For attribute attr-name of class-name, domain is not
specific enough to support unqualified object references.
Description
The specified attribute is an object reference, but the domain
was not specified.
User action
Correct the loader input file to make sure the attribute is
referencing a valid class name.
Nested sets are not allowed.
Description
A collection cannot contain collections.
User action
Please correct the definition and/or data in the database.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
102
0562
0563
0565
0567
0568
System class system-classname cannot be populated using the
database loader.
Description
The specified system class cannot be loaded with the loaddb
utility.
User action
Please delete the description of the system class from the
loader input file.
Reference to internal class class-name converted to NULL.
Description
A reference to the specified class was set to null because the
load utility cannot be used to load the specified class.
User action
Your schema should be modified to not hold references to the
special internal (system) class specified.
Constructor method method-name is not defined on class
class-name.
Description
The specified constructor method could not be loaded.
User action
Verify that the proper method name is used in the loaddb input
statements. Make sure the method implementation file can be
loaded.
Too many constructor method arguments supplied.
arg-count.
Expected
Description
There constructor was invoked with too many arguments.
User action
Verify that the proper method arguments are used in the
loaddb input statements.
Missing constructor method parameters.
count, found found-count.
Expected expected-
Description
There constructor was invoked with too few arguments.
User action
Verify that the proper method arguments are used in the
loaddb input statements.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
103
0569
0570
0571
0576
0579
Missing attribute values.
found-count.
Expected expected-count, found
Description
The number of attribute values in the loaddb input file is fewer
than the number of attributes defined in the schema for the
class.
User action
Correct the schema or the input file.
Could not access Glo data file file-name.
Description
The path of the GLO file specified in loaddb input file is not
correct.
User action
Make sure the input file is referencing the proper file, and
make sure the data file exists.
Instance was previously created through a forward
reference. This is not allowed for instances created using
constructor methods.
Description
A constructor cannot exist for an instance that was already
created by a forward reference.
User action
Restructure the input file.
Reference to class invalid-class-name is not compatible
with the domain of attr-name of class-name.
Description
Invalid class domain was encountered.
User action
Verify the schema definition and correct the loader input file.
Target domain must include type "object" to allow
references to classes.
Description
In order to assign a class reference (as opposed to an instance
reference), to an attribute, the domain must include “object:”
User action
Correct the input file.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
104
0581
0582
0583
0584
0585
0586
0587
Attempt was made to update the database when updates are
disabled.
Description
A method made an illegal attempt to update the database.
Updates are currently disabled. Methods invoked in queries
cannot modify the database.
User action
Fix the method so that it does not attempt to update the
database.
Unknown storage purpose purpose-code. Valid range is from
min to max.
Description
The purpose specified for the volume is invalid.
User action
Please specify any of data, index, temp, and generic for the
storage purpose of the volume.
Trying to allocate an invalid number (count) of pages.
Description
An illegal number was specified for the page count for the new
database volume.
User action
Make sure a positive value is used.
INTERNAL ERROR: A loop was detected in the file table of
file file-id in volume volume-name. The loop may be caused
by page page-id.
Description
The system detected an error in the file table.
User action
Please contact Cincom Technical Support.
Unknown heap heap-identifier
Description
Invalid heap file was encountered.
User action
Please contact Cincom Technical Support.
INTERNAL ERROR: Unable to update chain header in VPID pageid for heap heap-id in volume volume-name.
Description
Internal error encountered while attempting to update the
heap file header.
User action
Please contact Cincom Technical Support.
Entries of permanent volumes are unsorted in your file-name
volinfo file. Entry entry-id is out of sequence.
Description
An error was encountered in the database volume information
file. The database expects the entries in this file to be are in
alphabetic sequence.
User action
Please sort the content of the database-volume information
file.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
105
0588
0589
0590
0591
0595
0596
0597
INTERNAL ERROR: Failed optimizer assertion. Optimization
aborted.
Description
Internal error encountered during optimization.
User action
Please contact Cincom Technical Support.
Invalid user name name.
Description
The specified name cannot be used as a user name.
User action
Please choose a new name.
The attribute domain domain of a class may not be a virtual
class or a foreign table.
Description
Object references in base classes can reference only base
classes.
User action
Please verify the schema definition and correct the domain.
The attribute domain domain of a foreign table must be a
foreign table.
Description
Object references in foreign tables can reference only foreign
tables.
User action
Please verify the schema definition and correct the domain.
The database name dbname is too long. Name of database
should be less than maxlength characters.
Description
The specified database name is too long.
User action
Please use a database name with a length less than the
specified maximum.
The page-count pages of total temporary space allowed have
been exceeded.
Description
Query processing has exceeded the maximum number of
temporary pages allowed.
User action
Please add additional temporary space, or increase the
maxtmp_pages system parameter in the ordbinit.txt file.
Number of pages for heap file heap-file-id is inconsistent.
count1 and count2 were found according to heap chain and
file table, respectively.
Description
Database consistency error was encountered by checkdb utility.
User action
Please restore the database from a recent backup.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
106
0598
0599
0600
0601
0602
Number of files is inconsistent. expected-count were
expected, found-count were found
Description
Database consistency error was encountered by checkdb utility.
User action
Please restore the database from a recent backup.
An I/O error occurred while synchronizing state of volume
volume-name.
Description
A system error (hardware, operating system, or network) was
encountered during an I/O operation on the specified volume.
User action
Check the disk for hardware errors, if using NFS, check the
network drive status. You may have to restore the database
from a recent backup once the error has been corrected.
Function function-name not implemented under Windows.
Description
The specified function is not supported in Windows.
User action
Remove the function call from the windows version of the
code.
error-message.
Description
The specified error message was given by the operating system
when attempting to load a shared library.
User action
Please deal with error code from the system.
dl error: entry is multiply defined.
Description
The specified entry is defined more than once in the shared
library.
User action
Please confirm the shared library.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
107
0603
INTERNAL ERROR: Sector/page table of file VFID file-id
seems corrupted.
Description
The database system has encountered a corrupted virtual file.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
108
0604
INTERNAL ERROR: An allocation set for file VFID file-id
(Volume volume-name) seems inconsistent in page-count
deleted or marked deleted pages and hole-count page holes
in table
Description
The database system has encountered a corrupted virtual file.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0605
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
INTERNAL ERROR: Inconsistent number of marked deleted pages
for file VFID file-id (Volume volume-name). Expected
expected-count, Found found-count.
Description
The database system has encountered a corrupted virtual file.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
109
0609
Your transaction cannot be rolled back since logging was
ignored. Your database may be corrupted.
Description
A rollback was issued and the database is running with logging
disabled.
User action
The following actions should be taken:
1. Shut down the database server.
2. Execute checkdb.
0610
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
Your database is likely to be corrupted since logging was
turned off when your database crashed.
Description
The database crashed when it was running with logging
disabled.
User action
The following actions should be taken:
1. Shut down the database server.
2. Execute checkdb.
0612
0613
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
Logging cannot be disabled at this moment since there are
pending actions to recover.
Description
An attempt to disable logging was made when there are
outstanding transactions in progress.
User action
Please wait until all transactions have completed.
In class class-name, local component entity-name cannot
serve as an alias substitute for class super-class. The
domains are incompatible.
Description
The specified entity name found in both of the specified classes
must have compatible domains.
User action
Modify the class definition so the domains are compatible.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
110
0614
0615
0616
0617
Number of active log archives has been exceeded the max
desired number of archive-count.
Description
The maximum number of archive log volumes was exceeded.
User action
Remove un-needed log archives
Cannot establish contact with the Winsock interface.
WINSOCK ERROR: error-code.
Description
The specified network error was returned from the Winsock
interface.
User action
Check the network status and network configuration of the
machine.
Cannot determine machine name using Winsock interface.
WINSOCK ERROR: error-code.
Description
The specified network error was returned from the Winsock
interface.
User action
Check the network status and network configuration of the
machine.
Cannot determine machine id using Winsock interface. There
must be an entry in the host name table for this machine.
WINSOCK ERROR: error-code.
Description
The specified network error was returned from the Winsock
interface.
User action
Check the network status and network configuration of the
machine.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
111
0618
0619
0620
0621
0622
0625
Attribute is not updateable.
Description
An attempt was made to update a read-only, or WORM
attribute.
User action
Do not attempt to update read-only attributes.
Bad source codeset.
Description
Invalid source character set in conversion.
User action
Verify the character set. Verify the client/server character
set configurations.
Bad destination codeset.
Description
Invalid destination character set in conversion.
User action
Verify the character set. Verify the client/server character
set configurations.
Invalid data type. The arguments contain an invalid data
type.
Description
The argument was not of the proper data type.
User action
Verify the arguments.
Incompatible code sets. The code sets of the arguments are
incompatible.
Description
The character codes are incompatible.
User action
Please confirm the character-code of data.
INTERNAL ERROR: Trying to update the wrong instance object
template-id attribute information template with instance
object object-id.
Description
System encountered an unexpected object identifier mismatch.
User action
Please contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
112
0626
INTERNAL ERROR: count requested attributes were not found.
Description
The system detected an internal object definition error.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0627
0629
0630
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
Invalid trim operand.
greater than 1.
The trim operand has a length
Description
The trim operand cannot contain more than one character.
User action
Correct the operation.
Pagesize size is not a power of 2 or pagesize is too small.
Pagesize of new-size is used instead.
Description
The Cincom SQL Access system parameter value for the page
size is invalid.
User action
You should correct the invalid size to prevent further
informational messages. The system has substituted an
appropriate value.
Conversion not supported by function.
Description
The specified function attempted to perform an illegal
conversion.
User action
Modify the code to make sure the domains of the source and
destination are compatible.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
113
0631
0632
0633
0634
0635
Statement would violate one or more attribute NOT NULL
constraints.
Description
The attempted operation violates the NOT NULL constraint.
User action
Check the schema definition and make sure to provide valid
values for all attributes that have the NOT NULL constraint.
volume-name does not seem to be a backup volume.
Description
The specified volume is not a valid backup volume.
User action
You will not be able to restore the database until the proper
backup volumes are provided.
volume-name is a backup of database database-name1 created
on database-date1 instead of given database database-name2
created on database-date2
Description
The backup volume provided is for the wrong database.
User action
You will not be able to restore the database until the proper
backup volumes are provided.
A database volume/file was expected in backup.
Description
The backup volume is invalid, file does not contain expected
data.
User action
You will not be able to restore the database until the proper
backup volumes are provided.
WARNING: Log Buffer pool of bufcount buffers seems very
small for current environment. It is possible that some
buffers are not freed by the system due to an UNKNOWN ERROR
or that there are many concurrent transactions being
aborted at the same time. The log buffer pool is expanded
with expanded-count more buffers.
Description
The system was running low on log buffers and has
automatically extended the number of buffers.
User action
Increase the Cincom SQL Access system parameter
num_log_buffers to prevent this informational message.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
114
0636
0637
WARNING: Num_buffers bufcount is too small. The minimum
value of actual-count was assumed.
Description
Invalid value for the Cincom SQL Access system parameter
num_log_buffers was found.
User action
Increase the Cincom SQL Access system parameter
num_log_buffers to prevent this informational message.
SYSTEM ERROR: freeing a log buffer too much. Fix count is
set to zero.
Description
Internal system error encountered during log processing.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0638
0639
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
WARNING: Flushing a non-updateable log archive pageid =
page-id.
Description
The specified log page is not updateable and is being flushed.
User action
This is an informational message only, and no corrective action
is necessary.
SYSTEM ERROR: Previous log sequence page page-id1 is not
the delayed flush page page-id2.
Description
Internal error detected while processing log buffers.
User action
Please contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
115
0640
0641
0642
0643
0644
0645
0646
SYSTEM ERROR: a savepoint cannot be added when the
transaction is not active (e.g., during commit or
rollback).
Description
A savepoint cannot be established while the current transaction
is being committed or rolled back.
User action
Please allow the current transaction to finish before issuing the
savepoint.
A name must be given for a savepoint.
Description
The save point requires a name.
User action
Please specify the name for the save point name.
SYSTEM ERROR: there is not an active top system operation
for current transaction.
Description
Internal system logging error.
User action
Please contact Cincom Technical Support.
May be a system error: Committing/Aborting transaction =
%1$d (index = %2$d) which has permanent operations attached
to it. Will attach those system operations to the
transaction.
Description
Internal system logging error.
User action
Please contact Cincom Technical Support.
SYSTEM ERROR: Log manager does not known either undo/redo
function for rcvindex = recovery-index.
Description
Internal logging error.
User action
Please contact Cincom Technical Support.
SYSTEM ERROR: State = tran-state of Transaction = tid
(index = tindex) is not the correct state to apply client
postpone/undo actions... ignored
Description
Internal logging error.
User action
Please contact Cincom Technical Support.
SYSTEM ERROR: It seems that a compensating record is
missing for logical logging rcvindex = recovery-index.
Without this compensating record crash recovery will not be
done correctly
Description
Internal logging error.
User action
Please contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
116
0648
0649
0652
Backup is incompatible with current product-name release
release-string.
Description
The backup file(s) are for a different release than the current
release.
User action
Please make sure the proper files are used, or restore using the
proper release.
Given precision of precision is invalid; it should be
greater than min and no greater than max.
Description
The specified precision is invalid for the domain.
User action
Please provide a valid precision value.
Wrong offset offset was given to split the record of length
reclen stored on slot slot-id
Description
Error encountered during record management.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
117
0653
Wrong offset offset or length reclen was given to remove a
portion of the data of the record of length data-len stored
on slot slot-id
Description
Error encountered during record management.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0654
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
Wrong offset offset or length reclen was given to overwrite
a portion of the data of the record of length length stored
on slot slot-id
Description
Error encountered during record management.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
118
0655
0656
0657
0658
0660
0661
Cannot open the event handler configuration file, filename.
Description
The event handler could not open the specified configuration
file.
User action
Please make sure the event handlers' configuration file is
available.
WARNING: Null id/name in event handler configuration file,
file-name, line line-number
Description
The error event identifier is missing. The error was detected on
the specified line number of the specified configuration file.
User action
Correct the configuration file.
WARNING: Illegal event name, event, in event handler
configuration file, file-name, line line-number.
Description
The error event identifier is invalid. The error was detected on
the specified line number of the specified configuration file.
User action
Correct the configuration file.
WARNING: event id id-number, not in error id range min <>
max, file "%4$s", line %5$d file-name, line line-number.
Description
The error event identifier is invalid. The error was detected on
the specified line number of the specified configuration file.
User action
Correct the configuration file.
Cannot open/connect the event handler process, process-name
Description
Cannot connect to the event handler process.
User action
Please confirm the event handler process.
Failed to write to the event handler process, process-name
Description
Error encountered while attempting to write to the pipe
established with the event handler process.
User action
Please confirm the event handler process.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
119
0662
0663
0664
0665
0666
0669
0670
Failed to initialize event handling mechanism.
Description
Error trying to initialize event handler process.
User action
Make sure the machine resources are adequate to start the
process.
WARNING: Line too long in event handler configuration file,
file-name, line line-number, truncating.
Description
The line in the event handlers' configuration file is too long.
User action
Please correct the configuration file.
NOTIFICATION: Database Server up.
Description
Event notification message.
User action
This is an informational message only, and no corrective action
is necessary.
Event handler pipe broken, "%1$s"
Description
Error encountered while attempting to write to the pipe
established with the event handler process.
User action
Please confirm the event handler process.
WARNING: Event Notification Mechanism disabled"
Description
Event handler is disabled.
User action
The previous error caused the event notification to be
disabled.
Server refused client connection: max clients max-count
exceeded
Description
You have exceeded the maximum number of concurrent
connections to the server. Both the license key and the
Cincom SQL Access max_clients system parameter control the
maximum number of clients.
User action
If you have exceeded the maximum clients allowed by your
license key, please contact your Cincom Account Executive. If
the max_clients system parameter is less than the maximum
allowed by your license, then increase the max_clients
parameter.
Operation would have caused one or more unique constraint
violations.
Description
The attempted operation violates a uniqueness constraint.
User action
Check the schema definition and make sure to provide unique
values for all attributes that have the uniqueness constraint.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
120
0671
0672
0673
0675
A network read/write error occurred for socket socket-id
associated with your transaction (index transaction-index)
Description
Network communication error.
User action
Make sure the server is still running. Check the status of the
network.
Socket socket-id associated with your transaction (index
transaction-index) is closed.
Description
Network communication error.
User action
Make sure the server is still running. Check the status of the
network.
Your connection to the server has been closed since the
server is going down immediately.
Description
The server was terminated immediately or the connection to
the server was closed by the network error.
User action
Check the status of the network if the database server is still
running.
Cannot read the database location file, file-name.
Description
The database location file could not be read.
User action
Verify that the ORDB_DATABASES environment variable
identifies the proper directory. Make sure the file has proper
authorization settings.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
121
0676
0677
0678
0683
0684
Database dbname, cannot be found in the database location
file, file-name
Description
The specified database is not registered in the database
location file.
User action
Please confirm the setting of the specified database name and
the environment variable ORDB_DATABASES.
Failed to connect to database server, dbname, on the
following host(s): hostnames
Description
Could not find the specified database on any of the specified
host machines.
User action
Check the following:
♦
Make sure the database is running on (one of) the
host machine.
♦
Make sure the maximum number of clients has not
been exceeded for the database.
♦
Verify the network status.
♦
Make sure the hostname(s) are correct; update the
db_hosts and/or database location file if needed.
INTERNAL ERROR: Client restart module received NULL
database server name.
Description
The database name is NULL.
User action
Please contact Cincom Technical Support.
Attempt to create string with illegal length -%d.
Description
The length of the input string is invalid.
User action
Correct the application to pass a proper string.
Method returned user-defined error code %d.
Description
The specified error code was returned by the user method.
User action
Contact your system administrator.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
122
0685
0686
0693
0694
Class "%1$s" is invalid.
Description
The specified class name is invalid.
User action
Verify that the spelling of the class name is correct.
NOTIFICATION:
The event handler has been restarted.
Description
The user-defined event handler has been restarted.
User action
This is an informational message, no user action is required.
Overflow occurred on data type Numeric.
Description
The Numeric data overflowed.
User action
Make sure that the maximum precision of 38 digits is not
exceeded.
SYSTEM ERROR: Unable to load Btree.
Description
Severe B-tree error encountered.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0695
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
Bad interface to kill client has been used.
Description
Invalid parameter was passed to the killtran utility.
User action
Please correct the invalid parameter.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
123
0696
0697
0698
Unknown transaction (index transaction-index).
Description
The specified transaction could not be found, it may have
terminated right before the killtran utility attempted to
terminate it.
User action
Please verify the transaction identifier.
Given transaction index (transaction-index) does not match
with current transaction index (current-index). Likely, the
given transaction has finished and its transaction index
was re-assigned to another transaction.
Description
The specified transaction index has been re-assigned.
User action
This is an informational message only, and no corrective action
is necessary.
INTERNAL ERROR: the number of OIDs in the unique hierarchy:
oid-count does not equal the number of OIDs: found-count
found in the unique B+tree plus the number of NULLs: nullcount found in the unique hierarchy for B+tree: tree-id.
Description
Internal B-tree error encountered.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
124
0699
INTERNAL ERROR: the number of OIDs in the unique hierarchy:
oid-count does not equal the number of OIDs: found-count
found in the unique B+tree root statistics for B+tree:
tree-id.
Description
Internal B-tree error encountered.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0700
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
INTERNAL ERROR: the number of OIDs: oid-count does not
equal the number of NULLs: null-count plus the number of
keys: key-count in the unique B+tree: tree-id.
Description
Internal B-tree error encountered.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
125
0702
INTERNAL ERROR: the number of NULLs in the unique
hierarchy: null-count does not equal the number of NULLs:
found-count found in the unique B+tree root statistics for
B+tree: tree-id.
Description
Internal B-tree error encountered.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0703
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
INTERNAL ERROR: OID: object-id found in unique B+tree:
tree-id does not belong to one of the classes for the
unique constraint.
Description
Internal B-tree error encountered.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
126
0704
Evaluation of generic server function failed.
Description
Internal error encountered during query processing.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0705
0706
0707
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
Inconsistent found permanent volumes were found when
expected were expected.
Description
Inconsistency between the number of database volumes
contained in the volume in the information file and the actual
database volumes.
User action
Please confirm the volume configuration file of the database.
Cannot expand permanent volumes. Permanent volume volumename with purpose purpose was given.
Description
An attempt was made to expand a permanent volume.
User action
Please contact Cincom Technical Support.
Unable to expand temporary volume "%1$s" with %2$d pages
Description
Although it tried to extend the temporary volume , it could not
extend it.
User action
Please confirm there is an enough disk area in extending a
temporary volume.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
127
0708
0709
0710
0711
0712
0713
0714
Unable to expand temporary disk volume volume-name with
page-count pages (byte-count bytes) due to insufficient
space. Current space available is avail-pages pages (availbytes bytes).
Description
System could not allocate additional pages in the specified
volume.
User action
Please free up space on the device, or use a different device
that has the required space available.
Constraint constraint-name not found.
Description
The specified constraint is not defined.
User action
Check the schema definition to verify the constraint name.
Invalid constraint.
Description
The constraint could not be established because existing data
violates the constraint.
User action
You will have to resolve the data conflict before the constraint
can be defined.
An object with the supplied attribute value could not be
located.
Description
The SQLX_find_unique function did not find an object
containing the supplied value in the unique attribute.
User action
This is an informational message only, and no corrective action
is necessary.
Constraint constraint-name already exists.
Description
The specified constraint already exists.
User action
Use a different name for the constraint.
An index does not exist on this attribute.
Description
The attribute name passed to the SQLX_find_unique function
does not have a UNIQUE constraint.
User action
Validate the attribute name, create a unique constraint for the
attribute.
Query failed due to insufficient temporary file space.
Description
Query processor ran out of temporary file space.
User action
Increase the temporary volume space available for query
processing.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
128
0716
0717
0718
0719
NOT NULL constraints are not allowed in a virtual class or
foreign table.
Description
In foreign tables and virtual classes, the NOT NULL constraint
can only be specified for class attributes and shared attributes,
not instance attributes.
User action
Constraint is not allowed. You may be able to add the
constraint to the underlying foreign database table attribute or
base class attribute.
UNIQUE constraints are not allowed in a virtual class or
foreign table.
Description
The UNIQUE constraint is not allowed for attributes in foreign
tables nor virtual classes.
User action
Constraint is not allowed. You may be able to add the
constraint to the underlying foreign database table attribute or
base class attribute.
Invalid gadget.
Description
Internal error in esqlx interface.
User action
Please contact Cincom Technical Support.
The number of attributes (attr-count) and values (valuecount) are not equal.
Description
Internal error in esqlx interface.
User action
Please contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
129
0720
0721
0723
0724
Cannot use a gadget to insert into a virtual class or
foreign table.
Description
Internal error in esqlx interface.
User action
Please contact Cincom Technical Support.
Insert results in more than one row.
Description
The insert statement is invalid because the INTO clause was
specified, and the insert specified multiple rows.
User action
Correct the insert statement.
Cannot modify the domain of an existing attribute.
Description
You cannot use the ALTER statement to modify the domain of
an existing attribute.
User action
You will have to drop the existing attribute, and then re-add it
with the new domain.
Invalid parameter(s) for default constraint name
generation.
Description
The class name or the attribute name specified in the
constraint definition is missing or invalid.
User action
Correct the constraint definition.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
130
0725
INTERNAL ERROR: expected temporary oid and encountered
permanent oid.
Description
Internal error encountered.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0727
0728
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
Invalid trigger event.
Description
The trigger event is invalid.
User action
Correct the trigger definition.
Query failed because temporary file vfid is invalid for
transaction transaction-id.
Description
Query processor internal error.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0729
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
Overflow happened in subtraction context.
Description
DB_VALUE overflow occurred during arithmetic operation.
User action
Correct the calculation to utilize a larger precision for the
arithmetic result.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
131
0730
0731
0732
0733
Overflow happened in multiplication context.
Description
DB_VALUE overflow occurred during arithmetic operation.
User action
Correct the calculation to utilize a larger precision for the
arithmetic result.
Overflow happened in division context.
Description
DB_VALUE overflow occurred during arithmetic operation.
User action
Correct the calculation to utilize a larger precision for the
arithmetic result.
Overflow happened in unary minus context.
Description
DB_VALUE overflow occurred during arithmetic operation.
User action
Correct the calculation to utilize a larger precision for the
arithmetic result.
Overflow happened in coercion context.
Description
DB_VALUE overflow occurred while converting the string to a
numeric value.
User action
Use a larger domain for the conversion target.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
132
0734
INTERNAL ERROR: Header of file VFID file-id (Volume volumename) is corrupted.
Description
System detected an invalid file header.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0735
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
Unknown transaction index transaction-id.
Description
The specified transaction record could not be found.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0736
0737
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
Must specify either service or port identifier. WINSOCK
ERROR: error-code.
Description
The specified Windows TCP/IP error occurred.
User action
Please validate your network configuration. Refer to the
winsock documentation about the specific error-code.
Unknown service for TCP: service-name. WINSOCK ERROR:
error-code.
Description
The specified Windows TCP/IP error occurred.
User action
Please validate your network configuration. Refer to the
winsock documentation about the specific error-code.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
133
0738
0739
0740
0741
Cannot create socket stream. WINSOCK ERROR: error-code.
Description
The specified Windows TCP/IP error occurred.
User action
Please validate your network configuration. Refer to the
winsock documentation about the specific error-code.
Cannot bind local address... retrying. WINSOCK ERROR:
error-code.
Description
The specified Windows TCP/IP error occurred.
User action
Please validate your network configuration. Refer to the
winsock documentation about the specific error-code.
Cannot bind local address... aborting. WINSOCK ERROR:
error-code.
Description
The specified Windows TCP/IP error occurred.
User action
Please validate your network configuration. Refer to the
winsock documentation about the specific error-code.
Accept failed. WINSOCK ERROR: error-code.
Description
The specified Windows TCP/IP error occurred.
User action
Please validate your network configuration. Refer to the
winsock documentation about the specific error-code.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
134
0743
Internal error registering client handshake.
Description
The client and server encountered a communication protocol
error.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0744
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
Error in rehashing a foreign table/vclass MOP.
Description
Internal error encountered when processing an OID for a
foreign table or virtual class.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
135
0749
0750
0751
0752
0753
0754
0755
Number of fetched instances do not match: expected-count
expected, received-count received.
Description
During processing of a set of foreign table object identifiers,
some foreign table objects could not be found.
User action
Make sure that the foreign table definition correctly identifies
the attribute or attributes that make up the object identity.
Make sure that the attributes are indeed unique on the
underlying database.
Number of fetched attributes do not match: expected-count
expected, received-count received.
Description
The number of the attribute specified by the foreign table and
the number of attributes fetched for the foreign table object
do not match.
User action
Verify the foreign table definition.
The OID of a new object isn't available in a BEFORE INSERT
trigger.
Description
You cannot reference the object identifier in the trigger before
it has been created.
User action
Correct the trigger definition.
Error restoring backup unit_num backup-id.
Description
I/O error encountered on backup volume.
User action
Please contact Cincom Technical Support.
Error restoring backup unit_num backup-id, pageid page-id
exceeds total number of pages page-count for volid volumeid.
Description
Error encountered on backup volume.
User action
Please contact Cincom Technical Support.
OO foreign table instance has non-string-type or null key.
Description
A foreign table object identifier is invalid.
User action
Verify the foreign table definition.
This operation cannot be executed in stand-alone mode.
Description
The operation requested can only execute in client-server
mode.
User action
Please start the server and execute the operation.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
136
0756
0757
0758
0759
0760
Specified string buffer is too small to encode this object.
Description
The string representation of the oid cannot fit in the allocated
buffer.
User action
Please pass a larger buffer for the string representation.
INTERNAL ERROR: cannot assign permanent OID during object
encode.
Description
Invalid OID assignment attempted.
User action
Please contact Cincom Technical Support.
Specified string is not valid for decoding object.
Description
The string format of the oid is invalid.
User action
Please correct OID character string.
The target object has been deleted.
Description
Requested object has been deleted.
User action
Make sure the OID you are passing to the function is valid. If it
is, the object was probably deleted by another task.
INTERNAL ERROR: foreign table object instance has NULL key
during object encode.
Description
Data that makes up the object identifier for the foreign table is
null.
User action
Verify the foreign table definition and the object identifier
value.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
137
0761
0762
0763
0764
0765
0766
0767
0768
INTERNAL ERROR: vclass object instance maps to invalid real
instance.
Description
The virtual class object does not map to an underlying base
object.
User action
Verify the virtual class definition.
Internal error in resolving vclass instance to a real
instance.
Description
Internal error encountered while processing virtual class object
identifier.
User action
Please contact Cincom Technical Support.
Internal error in encoding non-updateable object instance.
Description
Internal error encountered while processing object identifier.
User action
Please contact Cincom Technical Support.
Internal error in encoding object into internal vobj form.
Description
Internal error encountered while processing object identifier.
User action
Please contact Cincom Technical Support.
Output object argument has a NULL address.
Description
The result address passed to the function is null.
User action
Please correct the code.
Internal error in decoding object.
Description
Internal error encountered while processing object identifier.
User action
Please contact Cincom Technical Support.
Cannot create a level level backup without first creating a
level level-1 backup.
Description
You cannot have gaps in the incremental backup number. If
you request level n, level n-1 must already exist as a backup
increment.
User action
Correct or remove lvl option of the backupdb command.
The foreign database fdb-name has been accessed in this
session, alteration or drop is not allowed.
Description
Because there are open transactions accessing the foreign
database, the specified foreign database cannot be dropped or
altered.
User action
Re-try after existing transactions have completed.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
138
0769
0770
0771
0772
0773
Attribute attr-name, of class class-name is not a valid
class or shared attribute.
Description
The specified attribute is not a shared attribute or a class
attribute in the specified class. This message is generated by
the loaddb utility.
User action
Verify the schema information and the loader input file.
Illegal use of table-generating function.
Description
Internal query processor error.
User action
Please contact Cincom Technical Support.
Illegal use of table-generating native expression.
Description
Internal query processor error.
User action
Please contact Cincom Technical Support.
IGNORE is only allowed on a single attribute
Description
The IGNORE constraint can only be applied to a single attribute
at a time.
User action
Correct the function call.
IGNORE is only allowed on instance attributes of a vclass
or foreign table
Description
The IGNORE constraint can only be applied to instance
attributes of virtual classes and foreign tables.
User action
Correct the class definition or function call.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
139
0774
0775
0776
0777
0779
Flushing of attribute attr-name fails.
Description
A foreign database operation failed while attempting to process
updates of the specified attribute.
User action
Please contact Cincom Technical Support.
An inheritance view cannot have a non-inheritance view
superclass
Description
You cannot add a non-inheritance view super class to an
inheritance view class.
User action
Please check the class definition that you are attempting to
add the superclass to.
A non-inheritance view cannot have an inheritance view
superclass
Description
You cannot add an inheritance view super class to a noninheritance view class.
User action
Please check the class definition that you are attempting to
add the superclass to.
Attempting to update an attribute that has IGNORE UPDATE
specified.
Description
An update operation was attempted on an attribute that has
the IGNORE UPDATE constraint.
User action
Verify that the constraint is valid.
Building view instance fails.
Description
Internal error encountered while trying to construct the virtual
view instance.
User action
Please contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
140
0780
0783
0784
0785
0786
0787
View is not updateable.
Description
An attempt was made to update a virtual class that cannot be
updated.
User action
Please check the schema definition of the virtual class. Refer
to the SQL Access for SUPRA Server PDM Administration Guide,
P25-9501, for information about updateable virtual classes.
Inheritance view query specification is not a SELECT.
Description
The query specification of the inheritance view was not
SELECT.
User action
Pleas update the schema definition of the virtual class.
Relationship attribute value cannot be set to NULL.
Description
Attributes that are used to uniquely identify a foreign database
instance cannot contain a NULL value.
User action
Verify the foreign table definitions. Do not set attributes that
are part of object identifier (or other candidate key) to NULL.
Relationship attribute value cannot have a NULL element.
Description
Attributes that are used to uniquely identify an foreign
database instance cannot contain a NULL value.
User action
Verify the foreign table definitions. Do not set attributes that
are part of object identifier (or other candidate key) to NULL.
Invalid arguments to function-name internal function.
Description
Internal error encountered while validating internal function
arguments.
User action
Please contact Cincom Technical Support.
Instance number required when inserting into class with
constructor.
Description
The instance number was not set in the argument to the class
constructor.
User action
Correct the loaddb input file.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
141
0788
0790
Error converting value to string.
Description
The DB_VALUE passed could not be converted to a string.
User action
Make sure the DB_VALUE parameter is constructed properly.
SYSTEM ERROR: Class locks were lost during XASL generation.
Description
The system has encountered errors with class locks.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0791
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
Lock for class class-name needed for XASL generation, but
not found in parser lock list.
Description
The system has encountered errors with class locks.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
142
0792
0794
0795
0796
Streaming query window too small. Page (page-id version
version-number) no longer available on server.
Description
An attempt was made to access a query result page that has
been released by the server.
User action
Please increase the size of the query_stream_window system
parameter. That will allow additional space for the server to
retain result buffers. Ann alternative would be to restructure
your application code so that scrolling backward in a result set
is no longer required.
Streaming query window must be greater than or equal to
zero.
Description
An invalid number was used for the query_stream_window size.
User action
Correct the query_stream_window parameter.
Illegal characters in string: str-value
Description
Invalid characters for the current character set are contained
in the specified string.
User action
Correct the string to contain only legal characters for the
character set being used.
Logging can be disabled only from stand-alone (not client)
applications.
Description
You cannot turn off logging when running in client-server
mode.
User action
Correct the program or run the application in stand-alone
mode.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
143
0797
0798
0799
0800
Index on class class-name, attribute attr-name, while fully
functional, is probably reducing performance because it has
only count distinct attribute values. This gives an average
selectivity higher than 5 percent, which is not usually
helpful during queries. The index will increase the costs
of insert, update and delete. It is recommended that for
classes with over 1000 instances, only index attributes
with at least 20 distinct values.
Description
The specified index is inefficient because the percentage of
distinct values contained in the attribute is low.
User action
You should drop the index unless you expect that there will be
an increase in the percentage of distinct values.
Invalid loader input for class or shared attribute attrname of class class-name.
Description
Invalid input encountered for the specified attribute.
User action
Correct the loaddb input file.
Connection to db-name1 already open; additional connection
to db-name2 not supported.
Description
You are already connect to the specified database, you cannot
have concurrent connections.
User action
Use the new API, or disconnect your open connection first.
Checkdb error-text.
Description
Checkdb utility returned the specified error.
User action
Restore the database from a previous backup.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
144
0801
Invalid class index in lockset request.
Description
The system has encountered errors with index locks.
User action
This could be either a database corruption or an algorithmic
problem in the database. The following actions should be
taken:
1. Shut down the database server.
2. Execute checkdb:
0802
0803
0804
-
If no errors are reported this was an algorithm
error and problem report should be opened
with Cincom Technical Support. You should
also backup the database at this time.
-
If checkdb found problems, you should restore
the database from your current backup.
Active log file log-name not found. Assuming that archive
logs exist.
Description
No active log file was found for the database. The restore
operation will continue using the archive logs.
User action
Ensure the integrity of the database.
Invalid -tf file file-name: line line-number contains
field-count fields instead of expected-count fields.
Description
The to/from volume information file passed to the copydb
utility has the specified error.
User action
Please correct the to/from volume information file.
Invalid -tf file %1$s file-name: line line-number refers to
volume volume-number when volume should be greater than
volume-number.
Description
The to/from volume information file passed to the copydb
utility has the specified error.
User action
Please correct the to/from volume information file.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
145
0805
0806
0807
0808
0809
Invalid -tf file %1$s file-name: line line-number refers to
inaccessible previous volume volume.
Description
The to/from volume information file passed to the copydb
utility has the specified error.
User action
Please correct the to/from volume information file.
Invalid -tf file file-name: line line-number refers to
inaccessible new directory directory-name.
Description
The to/from volume information file passed to the copydb
utility has the specified error.
User action
Please correct the to/from volume information file.
Invalid -tf file file-name: line line-number specifies
invalid rename from old-name to new-name.
Description
The to/from volume information file passed to the copydb
utility has the specified error.
User action
Please correct the to/from volume information file.
NOTIFICATION: Database is from an older version. Use
"upgradedb <dbname>" to upgrade the database to this
version. Once you upgrade, you will no longer be able to
run older version server or standalone programs on this
database.
Description
An attempt was made to start up a database that is from an
earlier version of the product.
User action
Use upgradedb to migrate your old database version to the
latest level. All database client runtimes will have to be
updated to the latest version as well.
Column not found.
Description
An invalid column number was sent to one of the ODBC fetch
routines.
User action
Send a valid column number.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
146
0810
0811
0812
0813
0814
0815
Invalid column number.
Description
An invalid column number was sent to odbc_set_parameter,
odbc_get_column, odbc_describe_column, or
odbc_column_attributes.
User action
Send a valid column number.
Invalid option.
Description
An invalid statement option was sent to odbc_free_statement.
User action
Send SQL_CLOSE, SQL_DROP, SQL_UNBIND, or
SQL_RESET_PARAMS as the statement option.
Invalid argument value.
Description
An invalid argument was sent to one of a number of
odbc_functions.
User action
Check the function parameters and send valid arguments.
Function sequence error.
Description
An ODBC request was made that was logically out of order. For
example, odbc_more_results() was called before results are
even created.
User action
The ODBC model must be followed for running queries and
checking results.
Descriptor out of range.
Description
odbc_column_attributes was called with an invalid
SQL_COLUMN_OP.
User action
Send a valid SQL_COLUMN_OP.
Invalid transaction code.
Description
odbc_transact was called with an invalid transaction operation.
User action
Send one of SQL_COMMIT, SQL_ROLLBACK, SQL_TP_COMMIT, or
SQL_TP_ROLLBACK.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
147
0816
0817
0818
0819
0820
0821
SQL data type out of range.
Description
An invalid SQL_TYPE was sent to the ODBC interface.
User action
Send a valid SQL_TYPE.
Program type out of range.
Description
odbc_is_valid_c_type was called with an invalid SQL_C_TYPE.
User action
Send a valid SQL_C_TYPE.
Disconnect error.
Description
odbc_disconnect had an error while shutting down the client.
User action
Use killtran utility to make sure the client application is
disconnected.
Restricted type violation.
Description
An invalid cast from a database type to an SQL_C_TYPE or and
invalid parameter bind or set.
User action
Make sure the SQL_C_TYPE is correct for the database column
and make sure you are sending the correct SQL_C_TYPE for
parameter settings and bindings.
Connection in use.
Description
The user is trying to connect using an odbc_connection that is
already connected to a server.
User action
Get a new connection to use to connect to another database
server.
Unable to connect to server.
Description
The odbc_connect call failed while attempting to connect to
the server.
User action
Make sure that the server and master are running. Verify
network connectivity between the client and server.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
148
0822
0823
0824
0825
0826
0828
0829
0830
Server rejected.
Description
This is a catch all for any error that happened while connecting
that was not ER_SS_UNABLE_TO_CONNECT_TO_SERVER or
ER_SS_INVALID_AUTHORIZATION_SPEC.
User action
Please contact Cincom Technical Support.
Connection failure.
Description
This is a general error for failures during odbc_transact.
User action
Please contact Cincom Technical Support.
Connection not open.
Description
The user is attempting an ODBC call that requires a valid
connection before that connection has been established.
User action
The user must first connect to a database server before making
the offending ODBC call.
Invalid cursor state.
Description
An SQL cursor is in an invalid state. This could happen if the
user closes the cursor and then attempts to continue using it.
User action
Make sure that cursor usage follows the ODBC model.
Invalid transaction state.
Description
An error occurred during auto commit during shutdown.
User action
Please contact Cincom Technical Support.
Invalid authorization spec.
Description
The user trying to connect to the database server is not
authorized for that server.
User action
Use an authorized user to connect to the database server.
Duplicate cursor name.
Description
This occurs when you attempt to set the name of the cursor
associated with a statement to the name it already has.
User action
Use a different cursor name.
Syntax error or rule violation.
Description
The SQL statement was empty, or failed to compile due to a
syntax error.
User action
Correct the syntax error
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
149
0831
0832
0833
Data truncation during binding.
Description
A value of one type was bound to another type resulting in
truncation or loss of precision. For example a string of length
10 is bound to a column that was defined as char(8), or a
floating point number is bound to an int.
User action
Possible remedies are to change the schema to accommodate
the larger values, or if truncation is acceptable, explicitly cast
values down to less precise types before binding.
Numeric value out of range/loss of significant digits.
Description
An attempt has been made to bind numeric value to a type that
cannot accept that value (for example attempting to bind a
value of 1000000 to a column whose type is SQL_SMALLINT).
User action
Either value is in error, or schema must be altered.
String truncation.
Description
Either of the following
ptions may apply:
Descri
1. An attempt to stringify an OID or collection results
in a string that is longer than the system limit of
255 characters.
2. A DB type of DB_TIMESTAMP is being converted into
a C type of SQL_C_DATE or SQL_C_TIME resulting in
a loss of either the date or the time information.
User action
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
None, information only.
150
0834
0835
0836
0837
0838
0839
Wrong number of descriptors.
Description
Set when the number if bound columns in an SQL statement is
greater than the number of columns in the result
User action
The number of bound columns should be the same as the
number of columns in the result.
Data value is not a numeric value.
Description
An attempt to convert a string to a numeric value failed
because the string does not contain numeric data
User action
Bind value to a string.
Operation not supported by driver.
Description
User has called an ODBC function that the ORDB driver does not
implement.
User action
Do not call unsupported functions.
Connect option out of range.
Description
The user has attempted to get or set an unknown ODBC
connect option.
User action
Only use supported connect options.
Invalid string or buffer length.
Description
A negative value was passed to an ODBC function where a
buffer length was required (e.g. the fourth parameter to
SQLGetInfo).
User action
Buffer lengths must be non-negative.
Driver not capable of option.
Description
The user has attempted to get or set an ODBC connect option
that is a known connect option but is not supported by the
driver.
User action
Only use supported connect options.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
151
0840
0841
0842
0843
0844
0845
0848
Syntax error in connection string.
Description
An error was encountered while parsing the connect string
passed to SQLConnect.
User action
Correct syntax error in connect string.
Statement option out of range.
Description
The user attempted to set or get an unknown ODBC statement
option.
User action
Only use supported statement options.
Invalid parameter number.
Description
Set by SQLBindParameter if parameter number passed is
invalid. Set by SQLDescribeParameter if the parameter number
is not one of the bound parameters.
User action
Pass valid parameter numbers to these functions.
Invalid parameter type.
Description
The parameter type passed to SQLBindParameter was not a
parameter type supported by ODBC.
User action
Use one of the supported parameter types:
♦
SQL_PARAM_INPUT
♦
SQL_PARAM_OUTPUT
♦
SQL_PARAM_INPUT_OUTPUT
Row value out of range.
Description
Row value passed to SQLParamOptions must be > 0.
User action
Pass valid value to SQLParamOptions.
Unable to access results.
Description
The ODBC query result structure pointer was null; most likely
the statement was not executed successfully.
User action
Make sure statement is executed successfully before
attempting to access results.
Syntax error in date literal.
Description
An error occurred parsing an ODBC date literal.
User action
Correct the date literal syntax.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
152
0849
Syntax error in time literal.
Description
The ODBC time was specified in an incorrect format. The
format should be specified as:
hh:mm:ss.[fff[fff]]
User action
0850
Correct the format of the time and reissue the statement.
Syntax error in timestamp literal.
Description
The ODBC timestamp was specified in an incorrect format. The
format should be specified as:
yyyy-mm-dd hh:mm:ss[.fff[fff]]
User action
0851
0853
0854
0855
0856
Correct format and reissue the statement
No default database supported.
Description
Attempting to connect via ODBC without specifying a server
name. Default names are not supported.
User action
Specify a server name and attempt the connection again.
Unexpected thread cancellation.
Description
Fatal System error. The operation of an internal thread was
cancelled, probably due to a system error.
User action
This error will cause the server to terminate. Check
system/server error logs for errors to diagnose. Restart the
server.
Unexpected thread exception.
Description
Fatal System error. An internal thread received an unexpected
exception. This will cause the server to terminate.
User action
Check system/server error logs for errors to diagnose. Restart
the server.
Unable to start thread for thread-purpose.
Description
Fatal System error. An internal thread failed to start.
User action
Check system/server error logs for errors to diagnose. Look
especially for inadequate system resources messages. This will
cause the server to shutdown. Restart server.
Thread found in invalid state.
Description
Fatal System error: An internal thread was found to be in an
invalid state.
User action
Check system/server error logs for errors to diagnose. This will
cause the server to shutdown. Restart server.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
153
0858
0859
0862
0863
0864
Unable to cancel thread for %1$.
Description
Internal system error received when attempting to cancel the
specified thread.
User action
Please contact Cincom Technical Support.
Duplicate fd = descriptor-id found.
Description
When attempting to create a new connection to a client the
file descriptor returned was a duplicate of a pre-existing file
descriptor.
User action
Stop and restart the server and please contact Cincom
Technical Support.
Applications may not link to more than one API version.
Description
The application attempted to link in more than one version of
the Cincom SQL Access API.
User action
Ensure that only use one version of the API is specified.
Environment attribute out of range.
Description
An invalid environment attribute was specified for the
odbc_set_env_attr function call.
User action
Only the program name attribute (SQL_ATTR_PROGRAM_NAME)
is supported.
Your transaction (index transaction-id) timed out waiting
on lock-type lock on Btree slot Btree-id. You are waiting
for user(s) user-list to finish.
Description
The transaction timed out waiting on a btree slot resource that
another transaction was holding.
User action
Repeat transaction. The LOCK_TIMEOUT_IN_SECS parameter
can be modified to increase the timeout period.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
154
0865
Failed to connect to database server, server-name, on host:
hostname, via portid tcp-ip_port
Description
Failed attempting to connect server on a specific port.
User action
Verify that the client machine can access the server machine
(via ping or some other tool). If network access is ok, then
confirm that the master process is up and running on the server
machine.
Make sure the client and server are of the same release.
Make sure the client and server machine are both using the same TCP/IP port
number by verifying the Cincom SQL Access master_port_id
system parameters on both machines.
0866
0867
Java method method-name failed: message-text
Description
A java method call failed, and no error was returned.
User action
Check error logs to look for errors that could cause the method
to fail. Repeat the transaction.
Cannot load Java VM java-library-name
Description
The java virtual machine shared library/DLL could not be
loaded.
User action
Check installation of java on host. Check error logs for
previous messages relating to the VM. Shutdown and restart
the Java method broker.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
155
0868
0869
0870
0871
Cannot locate Java VM entry java-symbol
Description
A java symbol could not be located in the java virtual machine
shared library/DLL.
User action
Check the spelling of the symbol. Check for proper installation
of the java libraries. Shutdown and restart the Java method
broker.
Cannot create Java VM (JNI_CreateJavaVM failed)
Description
The java virtual machine, shared library/dll initialization
failed.
User action
Check installation of java libraries. Check error logs for recent
messages from the Java VM. Shutdown and restart the Java
method broker.
Spawn of ordbmb process by process-name failed on host
hostname
Description
A client's java method call could not initiate the Java Virtual
Machine.
User action
Check error logs. Check the installation of Java. Check for
inadequate system resources.
Failed to connect to ordbmb on host hostname, via portid
tcp-port-number
Description
The client failed to connect to the Java Method Broker.
User action
Check to see if the method broker is up and running. If it was
not running before the client's java method call, the broker
may have been slow coming up and the client failed to
connect. Repeating the operation may find the broker
successfully. Check error logs, the installation of Java, and
verify network and system resources.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
156
0872
0873
0874
0875
All system request threads, sys-request-thread-count, have
been suspended. Attempting to use the system deadlock
detector to resolve the deadlock. To prevent future system
resource deadlocks it is recommended that the value of the
active_requests parameter be increased.
Description
This is a notification message. There are system threads that
are set aside for system work like (killtran). These are all
busy. The system threads are a percentage of the active
request threads.
User action
Increase the value of the active_requests parameter for your
installation.
All system request threads, active-thread-count, are
currently active, with a backlog of backlog-count requests.
To improve system performance and resource utilization it
is recommended that the value of the active_requests
parameter be increased.
Description
Threads available to service client requests are all busy.
User action
This is an information message. Increase the value of the
active_requests parameter for your installation.
The system was unable to resolve the following resource
deadlock at the current time. One or more queued requests
are waiting for thread resources to become available. One
or more currently active requests are waiting on one or
more transactions that have no queued or active requests.
Description
All threads are blocked and waiting on transactions that are not
currently active. It is also possible that a request which could
possibly resolve the blocks is pending in the request queue.
User action
Increase the active_requests parameter for your installation.
There are not enough threads to service the request volume.
Client is not valid VAR client.
Description
A client has attempted to connect to a database that is
intended for a particular VAR client.
User action
Either the client installation needs a new key for the VAR
installation, or the server is being started with a VAR key when
it should use a more general mechanism. Please contact your
Cincom account executive if you require a new license key.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
157
0876
0878
0879
0880
0881
0882
Your license will expire in expiration-days days.
Description
Your product license is about to expire.
User action
Please contact your Cincom Account Executive.
Java methods have been disabled
Description
The java method broker (ordbmb) has been disabled by
request.
User action
Enable the java method broker.
The variable variable-name is not defined in the server
environment.
Description
A server FBO has a pathname that contains an embedded
environment variable (e.g. $PICTURES/mypic.jpg). The
variable (PICTURES in this case) is not defined in the server's
environment.
User action
Define the environment variable before starting server process.
The fbo_root parameter is not defined on the server.
Description
The server parameter FBO_ROOT is not set, effectively
disabling all access to server FBOs.
User action
Define the fbo_root parameter.
The fbo_root element path is not a full pathname
Description
The specified element of the fbo_root list is not a full
pathname.
User action
Make sure that all elements of fbo_root contain full
pathnames.
The server fbo pathname path contains a parent directory
(parent-element) element.
Description
A server FBO was created whose pathname contained the
parent directory element (parent-element).
User action
Drop the server FBO and re-create it without the parent
directory element.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
158
0883
0884
0885
0886
The server fbo pathname path is not allowed.
Description
An attempt was made to create or access a server FBO whose
pathname was not prefixed with an element of the fbo_root
list.
User action
Move the location of the Server FBO to an allowed directory, or
change the value of the fbo_root server parameter and restart
the server.
Failed to recover fbo-file from shadow file shadow-file.
Description
During recovery after an abort or server crash, the server was
not able to recover the last committed version of the server
FBO.
User action
Restore the FBO file from a backup.
Failed to unlink server fbo file file-name.
Description
During rollback or crash recovery a newly created but
uncommitted server FBO could not be unlinked for some
reason.
User action
The system administrator should recover the disk space by
manually removing the FBO file.
string-value cannot be cast to an object.
Description
An attempt was made to cast a string, which could not be
interpreted as either an OID or a VID. Either the literal syntax
is incorrect, or the literal does not convert to a valid OID or VID
in the database.
User action
Do not edit OID or VID literals printed by the database.
Do not read OID or VID literals printed by one database
database.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
into another
159
0887
string-value cannot be cast to a set/sequence/multiset.
Description
An attempt was made to cast a string, which could not be
interpreted as a SET, a SEQUENCE or a MULTISET. Either the
literal syntax is incorrect, or an element of the literal does not
convert to a valid OID or VID in the database.
User action
Do not edit OID or VID literals printed by the database.
Do not read OID or VID literals printed by one database
into another database.
0888
0889
0890
0891
Database is already at the current format level.
upgrade is necessary.
No
Description
upgradedb was run on a database that is currently at the
correct format.
User action
There is no need to run upgradedb on databases that are at the
current format level.
Java methods are prohibited from performing schema
modifications.
Description
A java server method attempted to modify database schema.
User action
Do not make schema modifications from java methods.
Server has started log recovery at start-time
Description
This message is output by the server to its error log file and to
stdout just before starting a database recovery process. The
variable in the message will contain the time at which recovery
was started.
User action
None, information only. No corrective action is necessary.
Server has completed log recovery at completion-time
Description
This message is output by the server to its error log file and to
stdout just after completing a database recovery process.
User action
This is an informational message only, and no corrective action
is necessary.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
160
0892
0893
0894
Could not open the server fbo pathname path.
Description
While servicing a server FBO request, the server unsuccessfully
attempted to open the specified Server FBO data file.
User action
Correct the cause of the open failure. Some possible problems
are that the server has inadequate permissions to open the file,
or that the parent directory does not exist.
NOTIFICATION: The class class-name could not be created.
Skipping creation of the MM class hierarchy.
Description
When upgrading the database from a previous version, one or
more classes of the Multimedia class hierarchy could not be
created, probably because of a name conflict with an existing
class.
User action
If you do not plan to use the Multimedia class hierarchy, there
is no action needed. Otherwise, you can rename the
conflicting class and reapply upgradedb, or use the supplied
script in admin/make_mm.sql.
The current transaction has not been committed or rolled
back. Privileged login or logout is invalid while the
transaction is dirty.
Description
The user attempted to login as the privileged user or logout
from the privileged user when the active transaction had
uncommitted dirty data.
User action
The user must commit or rollback the transaction before
attempting to login or logout as the privileged user.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
161
0895
0896
0897
Transaction (index transaction-id) is retrying a B+tree
insert (retry number) on B+tree index {vfid: virtual-fileid), rt_pgid: page-number} for key key.
Description
A btree insert needed to be retried. This can happen at
different isolation levels when btree page/slot locks cannot be
synchronized.
User action
None, information only. Although, the system administrator
may want to kill the client if:
♦
A heavily loaded system has a client that appears
to be hung, and
♦
This message is in the server log with a high retry
number.
Transaction (index transaction-id) is retrying a recovery
undo, index = index number, after error error-number,
(retry number: retry-number).
Description
A recovery undo operation needed to be rerun. This can occur
if the system is busy and the recovery operation had to wait on
resource locks, which, subsequently, timed out.
User action
None, information only. If the retry attempts reach the retry
limit, the server will shutdown in an attempt to maintain
integrity of the database (see message 0897).
Transaction (index transaction-id) transaction recovery
failed with error error-number, terminating to maintain the
integrity of the database.
Description
In an attempt to maintain the integrity of the database, the
will system shutdown since a rollback operation failed.
User action
The system needs to be restarted so that recovery can take
place via the system privileged user. Clients will need to
reconnect to the server once it has completed its recovery and
restarted. Any transaction active during the shutdown will be
rolled back; this includes data from committed transactions
that may not have been flushed to disk. Some transactions
may have to be reissued when the server restarts.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
162
0899
0900
0901
0902
0904
0912
Character coding conversion error in string '%1$s'.
Description
Error encountered while attempting to convert the specified
string to unicode format.
User action
Verify that the string is valid.
Error granting privileges on xml hierarchy to public user.
Description
The public user cannot be found.
User action
Please contact your system administrator.
Error %1$d adding attribute "%2$s" to xml hierarchy.
Description
Internal system error encountered.
User action
Please contact Cincom Technical Support.
Error %1$d adding class "%2$s" to xml hierarchy.
Description
Internal system error encountered.
User action
Please contact Cincom Technical Support.
Internal error in locale initialization.
Description
The createdb utility received an error when it validated the
algorithm, locale, and codeset specified.
User action
Check the algorithm, locale, and codeset specified and make
changes as specified in the createdb documentation (refer to
the SQL Access for SUPRA Server PDM Administration Guide,
P25-9501).
There is not a database collation object for codeset %1$d.
All codesets must be defined during database creation.
Description
The character set specified in the CHARSET parameter was not
found in the database.
User action
Check the CHARSET parameter in the ordbinit.txt file or the
ORDB_CHARSET environment variable. The character set must
be one of the character sets specified with the -lc option of
createdb when the database was created.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
163
0913
0914
0918
0919
%1$d is not a currently supported locale code.
Description
The algorithm specified in the -na or -ca parameters of the
createdb utility is not supported.
User action
Check the -ca or -na parameters and correct as necessary
(refer to the SQL Access for SUPRA Server PDM Administration
Guide, P25-9501, for detailed information on createdb
parameters).
Unsupported combination of algorithm, locale, and codeset
(%1$s, %2$s, %3$s).
Description
The algorithm, locale, codeset combination specified on the
createdb command line is invalid.
User action
Check the -ca, -na, -cl,, -nl, and -lc parameters in the createdb
command line. Refer to the SQL Access for SUPRA Server PDM
Administration Guide, P25-9501, for a list of supported
algorithms.
Invalid codeset list. Codeset list must be a comma
separated list of codeset specifiers.
Description
The codeset list specified in the -lc parameter of createdb was
invalid.
User action
Check the -lc parameter and correct. Refer to the SQL Access
for SUPRA Server PDM Administration Guide, P25-9501, for
detailed information on the createdb -lc parameter and
codeset lists.
Maximum rows exceeded.
Description
The query has exceeded the maximum number of rows allowed.
User action
Verify the coding of the query. Change the query and rerun if
the query criteria are too general. If the query is specified as
desired, but returns more rows than the query_max_rows
parameter allows, increase this parameter. Cincom
recommends setting query_max_rows to a very high value that
prevents a "run away" query.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
164
0920
0921
Query time limit exceeded.
Description
The query has exceeded the maximum time allowed.
User action
Verify the coding of the query. Change the query and rerun if
the query criteria are too general. If the query is specified as
desired, but takes longer than the query_timeout parameter
allows, increase this parameter. Cincom recommends setting
query_timeout to a very high value that prevents a "run away"
query.
Socket recv time limit exceeded.
Description
A socket receive has exceeded the maximum wait time
allowed.
User action
Verify the setting for the socket_recv_timeout parameter.
Increase this parameter and rerun if the socket receive was
waiting on a request that requires more time than the specified
value, such as a long running query. If this parameter is set
higher than the time any request should require, contact the
administrator responsible for the server regarding its status.
Cincom recommends setting socket_recv_timeout to a very high
value that prevents a task from an endless stall waiting for a
server response from a server that is not operational.
Messages and Codes, P25-9502-04
Chapter: 1. Numeric error messages
Section: Messages with numeric codes
165
2. CID Adapter Server and Adapter
Client error messages
Overview
This chapter presents 8–character codes in alphanumeric sequence. The eighth
character identifies the error type and severity as follows:
♦
E = Error
♦
I = Information
♦
W = Warning
Messages are written by the client component to the file sup1drvr.err (this file
is created in the directory where the Cincom SQL Access master process was
started). Messages from the client are also returned to the application that
may also write the message into a file called uclient.err. This file is in the
directory where the application is running.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: Overview
166
CID Adapter Server and Adapter Client error messages
The following messages can be returned by the CID (Cincom Integrative Data)
Adapter Server and Adapter Client components:
CSHP170E
CSHP171E
CSHP172E
CSHP173E
Information for host with hostname host-name not
found
Description
An attempt was made to obtain information for the host-name
specified in the database connect string.
User action
Add information to the local or area host information services
for this host. The information will typically allow the hostname to be bound to a network address.
Cannot create TCP/IP socket. errno: nnn.
Description
An error occurred during the creation of an endpoint for
communication with the listener process.
User action
The creation of the endpoint failed for the specified reason. If
the error is not due to a limit on UNIX system resources,
contact Cincom Technical Support.
Cannot make connection to server database-name on
host hostname at port nnn. errno: nnn.
Description
Usually, this message means that the listener process on the
specified host has not been started.
User action
Ensure that the listener on the host has been started. If it has
been started, verify that the port number specified in the error
message is the same one the listener process is monitoring.
The connection failed for the specified reason. If the reason is
not due to a refused connection, contact Cincom Technical
Support.
Communication error during connect for server
database-name. errno: nnn.
Description
Communications with the specified database server failed
during establishment of the connection. The CID Adapter
Server may have connected to a process other than the
listener.
User action
Check that the port number used by the listener process is the
same one your CID Adapter Server is trying to use. If the ports
are the same, contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
167
CSHP174E
Connection to server database-name on host hostname
rejected. code: n.
Description
The CID Adapter Server connected to a listener process on the
specified host, but was rejected because the listener process
did not know the specified database server. The codes have
the following meanings:
1: The maximum number of concurrent client connections to
the server has been reached.
2: The server is not active.
3: The server has been shut down.
4: The PDM database name does not match the name of the
PDM database that the server was started for.
5: TCP/IP error
User action
Verify that your foreign database registration contains the
correct database name. In addition, the CID Adapter Server
may be connecting to the wrong listener. Verify that your
database connect string has the correct host name and port
number. Also, check the error log of the listener process.
Perform the following actions for the following codes:
1: Increase the maximum number of client connections the
server will allow, or wait for a connection to be freed by
another user.
2: Restart the server.
3: Check that the database name specified in the foreign
database registration is correct.
4: Check the server error log for more information on the
TCP/IP error.
5: Check the server error log for more information on the
error.
CSHP175E
Network read/write error occurred. socket: nnn errno:
nnn.
Description
Communications failed between the CID Adapter Client and the
listener after the establishment of the connection. This could
be due to a network problem or a problem on the machine
where the database server is running.
User action
Check that the machine where the database server is running
can be reached from the machine where the CID Adapter Client
is running.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
168
CSHP177E
CSHP179E
CSHP190E
CSHP201E
CSHP202E
CSHP203E
Server has closed the connection. socket: nn.
Description
The database server has closed the connection to the CID
Adapter Client.
User action
Check the error log of the database server to find out what
caused the database server to close the connection.
Unrecognized option specified in database connect
string (option)
Description
The database connect string contained an unrecognized option.
The unrecognized option is specified in the error message as
option.
User action
Correct or remove the unrecognized option from the database
connect string.
Trace options string is malformed
Description
The trace options string contains an unrecognizable trace
option. The trace options are numeric values in the range 1–
255 separated by a range character(–) or a separator character.
User action
Correct the trace option string.
Driver caught signal and died. signal: nnn.
Description
The CID Adapter Client received the specified signal. The
signal may have been sent by a user or may have been
generated by an internal error.
User action
If the signal was not sent to the CID Adapter Client by a user,
an internal error occurred. Contact Cincom Technical Support.
Driver caught signal and produced a core dump.
signal: nnn.
Description
The CID Adapter Client received the specified signal. The
signal may have been sent by a user or may have been
generated by an internal error.
User action
If the signal was not sent to the CID Adapter Client by a user,
an internal error occurred. Contact Cincom Technical Support.
Driver for database database-name is read-only.
Description
The db_database-name_read_only parameter has been set to
only allow read-only queries to the specified database. Data
may not be manipulated through the CID Adapter Client.
User action
None, information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
169
CSHP204E
CSHP205E
CSHP212W
CSHP213E
CSHP214E
CSHP220E
Data modification is not supported on views.
Description
Data modification language is not permitted on views.
User action
None, information only.
Delete is not supported for ESDS or RRDS VSAM files.
Description
Data modification language is not permitted on ESDS and RRDS
VSAM files.
User action
None, information only.
Maximum physical data unit size is too small.
max_rcv_pdu: nnnnn.
Description
The CID Adapter Client parameter max_rcv_pdu is set to a size
less than the minimum size for a response physical data unit
(1024 bytes).
User action
Set the max_rcv_pdu parameter to a size greater than the
1024.
Communication with the server component has failed
Description
The network connection between the CID Adapter Server client
component and the CID Adapter server component has been
broken and communication has failed.
User action
Contact your network administrator and reconnect your session
when the network problem is resolved.
Message de-compression failed. Calculated length
nnnnnn, transmitted length nnnnnnnn
Description
An error occurred de-compressing a message from the CID
Adapter Server.
User action
Contact Cincom Technical Support.
Overflow during insert/update of class class-name
attribute attribute-name.
Description
The value specified is outside the precision of the attribute and
cannot be used to insert or update the value of the attribute.
User action
Make sure the value specified is within the precision of the
attribute.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
170
CSHP221E
CSHP222E
CSHP230E
CSHP250E
Illegal data values class class-name attribute
attribute-name position nn: hex-data.
Description
The data selected for the specified attribute is unacceptable at
the specified position in the hexadecimal representation of the
value.
User action
Make sure the value contains valid data before the value is
selected.
Incompatible domain in foreign table foreign-tablename attribute attribute-name: nn.
Description
There is an incompatible domain defined in the foreign table
for the specified class and attribute. The DB_TYPE of the
domain used in the foreign table is shown at the end of the
message.
User action
Change the domain in the foreign table to one that is
compatible.
Class class-name does not exist in the schema.
Description
The specified class does not exist in the schema for the
database server. The CID Adapter Server builds a schema
containing all the valid class names that exist on the database
server. An additional class may have been created on the
database server since the CID Adapter Server created the
schema.
User action
Check that the correct class name was specified. If the class
was created on the database server, then it will be necessary
to ensure all the CID Adapter processes have finished execution
and that they are cleared from the process list. It may also be
necessary to ensure that the schema has been deleted from
memory.
WHERE clause must contain a search condition.
Description
The SELECT statement contains a WHERE clause that contains
an invalid search condition. The search condition must contain
at least one predicate to be valid.
User action
Examine the search condition and make a correction.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
171
CSHP251E
CSHP253E
CSHP254E
CSHP270W
CSHP272E
Element of path expression is not an object. element:
element-name path: path-expression.
Description
The specified path expression contains an element that is not
an object. Only the last element to be named in the path
expression may not be an object.
User action
Examine the path expression and make a correction.
Path attribute path-attribute does not exist in class
class-name.
Description
The specified path attribute does not exist in the specified
class. The path expression contains an attribute that cannot be
found in the schema.
User action
Examine the path expression and make a correction.
Views do not support sequence attributes.
Description
The join query or CID Adapter View query cannot contain any
sequence attributes.
User action
Remove the sequence attributes from the select clause of the
query.
Object-identifier cache size limit reached.
oid_cache_max > nnnnnn.
Set
Description
The object-identifier cache, used internally by the CID Adapter
Client, had to expand in order to accommodate new objectidentifiers. The expansion increased the size of the cache
beyond the preset default limit or the limit set in the
parameter oid_cache_max. The default size of the objectidentifier cache is 16,384 bytes.
User action
Set the oid_cache_max parameter to a size greater than the
minimum.
Special OID is without a control key or rrn and
cannot be used.
Description
An instance has been created without either the control key (if
the instance is in a primary file) or relative record number (if
the instance is in a related file).
User action
Finish the instance or rollback the transaction.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
172
CSHP280E
CSHP291E
CSHP293E
CSHP294E
CSHP295E
String OID is invalid and cannot be converted to
binary OID: string-oid.
Description
An internal error has occurred. An internal representation of
an object-identifier (represented by the specified string-OID) is
not in a format recognizable by the CID Adapter Client.
User action
Contact Cincom Technical Support.
INSERT/UPDATE is not allowed on class class-name
attribute attribute-name.
Description
The specified attribute may not have a value specified for
insert/update in the INSERT/UPDATE statement. The
attributes that may not be inserted/updated are: in coded
files, the ffffCODE attribute; in primary files, the ffffLKxx,
F_ffffLKxx, and L_ffffLKxx attributes.
User action
Examine the INSERT/UPDATE statement and specify an
attribute list that does not contain the unauthorized attributes.
Value specified for attribute attribute-name cannot
be NULL.
Description
The specified attribute does not allow the NULL value to be
inserted.
User action
Examine the statement and specify a value.
Only one positional attribute (N_ffffLKxx or
P_ffffLKxx) may be specified.
Description
An INSERT into a relative file may be positioned on one linkpath
only. Only one positional attribute may therefore be specified
in the statement.
User action
Examine the INSERT statement and specify only one positional
attribute.
Cannot INSERT into a coded file base attribute set.
Specify an overlay instead.
Description
An INSERT into a base file that is coded is not allowed.
User action
Specify a record code on the file.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
173
CSHP296E
CSHP297E
CSHP298E
Attribute overlaps: attribute-name. Please eliminate
the overlapping attribute(s) from the attribute list.
Description
The attributes specified in the INSERT attribute list overlap,
with the result that the actual values inserted in the PDM or
VSAM file cannot be predicted. Nonoverlapping attribute
names must be specified.
User action
Examine the INSERT statement and correct the attribute list.
Primary link path unknown. Please specify positional
attribute (N_ffffLKxx or P_ffffLKxx).
Description
An INSERT into a related file has failed because a positional
attribute was not specified and a default primary link path was
not associated with the related file. A positional attribute
must be specified.
User action
Examine the INSERT statement and add a positional attribute to
the attribute list.
Key attribute attribute-name or all the sub-elements
must be specified.
Description
An INSERT requires certain attributes to have a value specified.
The specified attribute required a value, or all the subdefined
elements of the attribute must be specified with values. For a
primary file, the ffffCTRL attribute must be specified with a
value. For a related file, all the referback keys must be
specified with values.
User action
Examine the INSERT statement and add the attribute together
with a value.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
174
CSHP320E
CSHP321E
CSHP322E
CSHP323E
Failed to create object named object-name
Description
A semaphore object or shared memory object could not be
created under Windows NT. The name of the object is
specified in the error message as object-name. If the name
resembles “… File Mapping” then there may be a message that
indicates that the file mapping was not possible because the
paging file was not large enough.
User action
The virtual memory on your Windows NT machine may need to
be increased if you had the message that is described above.
For information on how to increase the virtual memory, refer
to the SQL Access for SUPRA Server PDM Installation Guide,
P25-9500. Otherwise, contact Cincom Technical Support.
Operation failed on object name object-name
Description
An operation on a semaphore object or shared memory object
could not be performed under Windows NT. The name of the
object is specified in the error message as object-name.
User action
Contact Cincom Technical Support.
Windows sockets initiation failed
Description
Startup of Windows Sockets Architecture has failed. An
extended status message will explain the reason.
User action
Examine the extended status and determine a course of action
to remedy the startup failure.
Protocol name unrecognized protocol-name
Description
A database connect parameter specifies a protocol name that is
unrecognized. The protocol name is displayed in the message.
User action
Correct the protocol name. The only protocol supported is
tcpip.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
175
CSHP324E
CSHP325E
CSHP330E
CSHP332E
Could not load protocol library: protocol-library
Description
The CID Adapter client component for Windows NT attempted
to load the DLL named in the error message, but could not
locate the file. The DLL should exist in the %ORDB% directory,
which should be listed in the PATH environment variable.
User action
Check that the PATH environment variable includes the
%ORDB% directory in the list. Add %ORDB% to the list if
required. Also, check that the named DLL file exists in the
%ORDB%; if it does not, the DLL will need to be restored by
reinstalling the client.
Could not get procedure address for procedure-name in
protocol-library
Description
The CID Adapter Client loaded the DLL file named in the error
message and then attempted to lookup the address of the
name procedure within the DLL, but the attempt failed.
User action
The DLL may have been corrupted and reinstalling the client
may correct the problem. If reinstalling does not correct the
problem, contact Cincom Technical Support.
SNA CPI-C startup failure
Description
Startup of Windows CPI-C has failed.
User action
Examine the extended status and determine a course of action
to remedy the startup failure.
SNA CPI-C verb failure: verb-name returns: returncode code: cm-identifier
Description
The SNA CPI-C verb named in the error message has failed. A
return code, together with the symbolic identifier for the
return code, is provided in the message. The verb may have
failed because the network link has failed.
User action
Examine the information provided in the message and
determine a course of action to remedy the failure. Check the
status of the network with your network administrator.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
176
CSHP333E
Could not set partner LU name: partner-LU-name
Description
The partner logical unit name specified in the database
connect parameter could not be used. The partner logical unit
name can contain a maximum of 17 ASCII characters. The
allowed characters are:
♦
Uppercase letters
♦
Numerals 0–9
The partner logical unit name can either be an alias consisting
of 1–8 characters, or a fully qualified network name containing
a maximum of 17 characters.
User action
CSHP334E
Could not set mode name: mode-name
Description
User action
CSHP335E
Correct the partner logical name specification in the database
connect parameter and reattempt connection.
The mode name specified in the database connect parameter
could not be used. The mode name contains a maximum of
eight ASCII characters. The allowed characters are:
♦
Uppercase letters
♦
Numerals 0–9
Correct the mode name specification in the database connect
parameter and reattempt connection.
Allocate conversation failure (partnerLUname:
partner-LU-name modeName: mode-name)
Description
An attempt was made to allocate a conversation between the
CID Adapter client component and the CID Adapter server
component using the partner logical unit name and mode name
specified in the database connect parameter, but the attempt
failed.
User action
Check with your network administrator that the network is
available and reattempt the connection. Also, examine the
extended status message for further information describing the
cause of the failure, and determine a course of action to
remedy the failure.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
177
CSHP337E
Server has rejected connection to database databasename: reason rc:code
Description
The CID Adapter client component managed to connect with
the server component, but the server component rejected the
connection. The reason for the rejection and the code for the
rejection are provided in the error message. The codes have
the following meanings:
1: The maximum number of concurrent client connections to
the server has been reached.
2: The server is not active.
3: The server has been shut down.
4: The PDM database name does not match the name of the
PDM database for which the server was started.
5: TCP/IP error
User action
Check that the partner logical name and mode name specified
in the database connect parameter are the correct choices;
they may specify an incorrect CID Adapter server component.
Perform the following actions for the following codes:
1: Increase the maximum number of client connections the
server allows, or wait for a connection to be freed by
another user.
2: Restart the server.
3: Restart the server.
4: Check that the database name specified in the foreign
database registration is correct.
5: Check the server error log for more information on the
TCP/IP error.
6: Check the server error log for more information on the
APPC error.
7: Check the server error log for more information on the
error.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
178
CSHP338I
Automatic retry of allocate (partnerLUname: partnername modeName: mode-name)
Description
The CID Adapter client component tried to allocate the
conversation with the server component using APPC. However,
allocate failed and the return code classification indicated to
retry allocating.
The client will attempt three successive attempts to allocate a
conversation when there is in an indication that the attempt
should be retried each time.
User action
CSHP339E
CSHP340E
CSHP341E
None, information only.
Failure to allocate after nn retries (partnerLUname:
partner-name modeName: mode-name)
Description
The CID Adapter client component tried unsuccessfully nn
times to allocate a conversation when the return code each
time indicated that a retry should be attempted.
User action
Check the status of the network and links with your network
administrator.
From clause may not contain a view name.
Description
The FROM clause of a join query may not contain a foreign
name for a CID Adapter View.
User action
Replace foreign table names for CID Adapter Views names in
the FROM clause with foreign table names for single PDM
datasets. Alternatively, a new CID Adapter View may be
written to accommodate the current join query.
View definition production failed.
Description
The CID Adapter client was unable to produce a temporary CID
Adapter View for the join query submitted.
User action
Contact Cincom Support.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
179
CSHP342E
CSHP350E
CSHP360E
CSHP380E
CSHP381E
Unique constraint not found for class class.
Description
The CID Adapter client was unable to find the primary KSDS
access method for a VSAM file. The primary KSDS access
method is created automatically by the CID Adapter Server
during startup.
User action
Contact Cincom Support.
WIN32 extended error status: extended-status
Description
Describes in extended detail the cause of an earlier failure
during a Windows NT system-call.
User action
Use the information to diagnose the failure and to correct the
cause of the failure.
Native expression error: error-message.
Description
The native expression submitted to the CID Adapter could not
be processed due to an error.
User action
Examine the error message and correct the native expression.
Message file cannot be opened. path: path-name.
Description
The message file with the specified path cannot be opened.
User action
Verify that the message file exists.
Message file cannot be opened. path: path-name errno:
nn.
Description
The message file with the specified path cannot be opened for
the specified reason. The parameter LANG specifies the
language directory under $ORDB/admin/msg in which the
message file is found. The default for lang is En_US and the
message file is named sup1drvr.msg.
User action
Verify that the message file exists. Verify that the parameter
LANG specifies a language directory that exists under
$ORDB/admin/msg.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
180
CSHP401W
CSHP402E
CSHP403E
CSHP404E
CSHP405E
Schema table is exhausted.
nn.
Set schema_table_size >
Description
The CID Adapter Server created a schema for a database
server. The CID Adapter Server could not add information that
a schema existed to the schema table because space in the
schema table had run out. The parameter schema_table_size
defaults to 10.
User action
Set the parameter schema_table_size to a value greater than
the value specified in the error message.
GETMAIN_U() call failed for shared-memory. size: nnn
sub-pool: nnn.
Description
There was not enough memory available for the sharedmemory.
User action
Decrease the SHARED_MEM parameter in the initialization file,
or change the REGION parameter for the job.
Out of process memory: mem_alloc failed. requested
size: nnn.
Description
An internal error has occurred. A request to allocate memory
has failed because no memory was available.
User action
Contact Cincom Technical Support.
Shared-memory not initialized: mem_alloc failed.
Description
An internal error has occurred. A request to allocate sharedmemory has failed because the shared-memory manager has
not been initialized.
User action
Contact Cincom Technical Support.
Out of shared-memory: mem_alloc failed. requested
size: nnn.
Description
A request to allocate shared-memory of the specified size has
failed. The parameter schema_segment_size sets the size of
the shared_memory segment used by the CID Adapter Server.
The parameter schema_segment_size defaults to 2,097,152.
User action
Set the parameter schema_segment_size to a higher value.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
181
CSHP406E
CSHP407E
CSHP408E
CSHP409E
CSHP415E
Invalid address for mem_realloc. address: 0xaddress
expected: 0xaddress.
Description
An internal error has occurred. A request to reallocate and
change the size of an already allocated memory failed because
the address in the specified memory header block did not
match the expected address.
User action
Contact Cincom Technical Support.
Out of process memory: mem_realloc failed. requested
new size: nnnn.
Description
An internal error has occurred. A request to reallocate and
change the size of an already allocated memory failed because
no memory was available.
User action
Contact Cincom Technical Support.
Invalid address for mem_free. address: 0xaddress
expected: 0xaddress.
Description
An internal error has occurred. A request to free allocated
memory failed because the specified address in the memory
header block did not match the expected address.
User action
Contact Cincom Technical Support.
Invalid memory identifier found on block-id block.
Description
An internal error has occurred. The memory header was
expected to have the specified memory header identifier.
User action
Contact Cincom Technical Support.
System abort: file(line): message
Description
A fatal error has occurred in the CID Adapter Server.
User action
Contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
182
CSHP420E
CSHP421E
CSHP430E
CSHP431W
Dynamic load failed: dl-error.
Description
The dynamic library loader attempted to find a shared-library
to load and failed for the specified reason.
User action
Verify that the library shown in the error message is on the
load path. Set the parameter load_path to the directory where
the library is expected to be. Also, check that the environment
variable LIB_PATH or LD_LIBRARY_PATH is set to include the
directory where the library is expected to be. The library is
usually expected to be in $ORDB/lib.
Dynamic context symbol missing: dl-error.
Description
The dynamic library loader attempted to find a symbol in a
shared library and failed for the specified reason.
User action
Contact Cincom Technical Support.
Parameter initialization file cannot be opened. path:
path-name errno: error-number.
Description
The initialization file with the specified path cannot be opened
for the specified reason. The initialization file is
$ORDB/admin/sup1drvr.init.
User action
Check the initialization file.
Parameter initialization on line line-number is too
long. path: path-name.
Description
The initialization file with the specified path has a line that is
too long to be read.
User action
Check the initialization file.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
183
CSHP432W
CSHP433E
CSHP440E
CSHP441E
Parameter initialization syntax is incorrect on line
line-number. path: path-name.
Description
The initialization file with the specified path has a line that
contains a parameter initialization with incorrect syntax.
User action
Check the initialization file.
Parameter db_database-name must be set to establish
connection with server.
Description
The specified parameter must be set to allow a connection to
the specified database.
User action
Set the parameter in the initialization file.
Creation of semaphore set failed. key: 0xsemaphorekey errno: nnn.
Description
The CID Adapter Server failed to create a semaphore set with
the specified key for the specified reason. There may be a
problem with the UNIX kernel configuration; SEMMNI or SEMMNS
values may be too small and may have to be reconfigured in
the kernel.
User action
Check the reason returned in the errno variable.
Attach to semaphore set failed. key: 0xsemaphore-key
errno: nnn.
Description
The CID Adapter Server failed to attach to an existing
semaphore set with the specified key for the specified reason.
User action
Check the reason returned in the errno variable.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
184
CSHP442E
CSHP443E
CSHP444E
Semaphore operation failed. id: semaphore-id errno:
nnn.
Description
The CID Adapter failed to perform an operation on an attached
semaphore set with the specified semaphore identifier for the
specified reason.
User action
Check the reason returned in the errno variable.
Delete semaphore identifier failed. identifier:
semaphore-id errno: nnn.
Description
The CID Adapter Server failed to delete a semaphore set with
the specified semaphore identifier for the specified reason.
User action
Check the reason returned in the errno variable.
Creation of shared-memory segment failed. key: 0xshmem-key size: nnnnn errno: nnn.
Description
The CID Adapter Server attempted to create a shared-memory
segment with the specified key and of the specified size. It
failed for the specified reason. There may be a problem with
the UNIX kernel configuration; SHMMAX may be too small and
may have to be reconfigured in the kernel.
User action
Check the reason returned in the errno variable. The schema
segment size may be set to a smaller size by setting the
parameter schema_segment_size. The parameter
schema_segment_size defaults to 2,097,152.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
185
CSHP445E
CSHP446E
CSHP447E
Get shared-memory segment failed. key: 0xsh-mem-key
size: nnnnn errno: nnn.
Description
The CID Adapter Server attempted to get an existing sharedmemory segment with the specified key. It failed for the
specified reason.
User action
Check the reason returned in the errno variable.
Attach shared-memory segment to process space failed.
address: 0xaddress errno: nnn.
Description
The CID Adapter Server attempted to attach a shared-memory
segment into the specified address-space of the CID Adapter
Server. It failed for the specified reason. The address at
which the schema table is attached is set in the parameter
schema_table_address and defaults to 0xefff000. The address
at which the schema segment is attached is set in the
parameter schema_segment_address and defaults to 0xeff0000.
User action
Check the reason returned in the errno variable. Change the
address to attach the schema table or schema segment in the
schema_table_address and schema_segment_address
parameters.
Detach shared-memory segment failed. address:
0xaddress errno: nnn.
Description
The CID Adapter Server attempted to detach the sharedmemory segment at the specified address and failed for the
specified reason.
User action
Check the reason returned in the errno variable.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
186
CSHP448E
CSHP449E
CSHP450I
CSHP451I
CSHP452I
Delete shared-memory segment identifier failed.
identifier: sh-mem-id errno: nnn.
Description
The CID Adapter Server attempted to delete the specified
shared-memory segment and failed for the specified reason.
User action
Check the reason returned in the errno variable.
Status shared-memory segment request failed.
identifier: sh-mem-id errno: nnn.
Description
The CID Adapter Server attempted to get the status of the
specified shared-memory segment and failed for the specified
reason.
User action
Check the reason returned in the errno variable.
The list of initialization parameters follows.
Description
A list of all initialization parameters and their current values
follows this message.
User action
None, information only.
Parameter parameter-name parameter-value.
Description
This message is used to display the value of a string
initialization parameter.
User action
None, information only.
Parameter parameter-name parameter-value.
Description
This message is used to display the value of a numeric
initialization parameter.
User action
None, information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
187
CSHP453I
CSHP454I
CSHP455W
CSHP456W
CSHP457W
CSHP458W
Parameter parameter-nameFALSE.
Description
This message is used to display the value of a Boolean
parameter with the value FALSE.
User action
None, information only.
Parameter parameter-nameTRUE.
Description
This message is used to display the value of a Boolean
parameter with the value TRUE.
User action
None, information only.
Initialization file line line-number too long.
Description
An initialization file line is greater than 127 characters.
User action
Retype the line with less (or no) white space.
Cannot open file-name for read. errno: nnn.
Description
The specified file cannot be opened.
User action
Check the JCL. The file DD card may be missing, or the DCB
attributes may be incorrect.
Invalid keyword keyword-name on line line-number.
Description
The specified keyword is unknown. It is located at the
specified line in the INIT file.
User action
Correct the keyword.
Invalid numeric parameter parameter-name on line
line-number.
Description
The value in the specified parameter on the specified line is
not numeric.
User action
Correct the parameter.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
188
CSHP459W
CSHP460W
CSHP461W
CSHP462W
CSHP463W
CSHP464W
Input parameter parameter-name on line line-number is
longer than max.
Description
The value of the specified parameter on the specified line is
larger than the allowed maximum.
User action
Correct the value.
Input parameter parameter-name on line line-number is
invalid.
Description
The value of the specified parameter on the specified line is
invalid.
User action
Correct the value.
Invalid environment symbol symbol-name.
Description
The specified environment symbol is unknown.
User action
Correct the environment symbol.
Invalid numeric parameter parameter-name.
Description
The value in the specified parameter, specified in an
environment symbol, is not numeric.
User action
Correct the parameter.
Input parameter parameter-name is longer than max.
Description
The value of the specified parameter, specified in an
environment symbol, is larger than the allowed maximum.
User action
Correct the parameter.
Parameter parameter-name value parameter-value out of
range. Min: minimum-legal-value. Max: maximum-legalvalue.
Description
The specified parameter, specified in an environment symbol,
has a value outside of the legal range.
User action
Correct the parameter.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
189
CSHP465W
CSHP466W
CSHP467E
CSHP468E
CSHP470E
CSHP471E
Invalid Boolean value parameter-name on line linenumber.
Description
The specified parameter on the specified line has an unknown
Boolean value.
User action
Correct the value to be Yes/No/True/False/1/0.
Invalid Boolean value parameter-name.
Description
The specified parameter, specified in an environment symbol,
has an unknown Boolean value.
User action
Correct the value to be Yes/No/True/False/1/0.
Parameter parameter-name value value on line linenumber out of range. Min: min-value. Max: max-value.
Description
The specified parameter has a value outside the legal range.
User action
Correct the parameter.
Parameter parameter-name must be greater or equal to
parameter-name.
Description
The first specified parameter must have a value greater than or
equal to the value of second specified parameter.
User action
Correct the parameter.
Parameter parameter-name must be specified.
Description
A required parameter is missing.
User action
Add the required parameter to the init file.
The combined length of TCP_HOSTFILE and TCP_PREFIX
must be reduced by length characters.
Description
A number of parameters must be passed into the TCP/IP
listener. The total length of these parameters must be less
than 100 bytes (MVS limit). The values in the TCP_HOSTFILE
and/or TCP_PREFIX parameters must be reduced by the
specified number of characters in order to reach the limit.
User action
Change one or both parameters in the init file.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
190
CSHP472E
CSHP473E
CSHP500I
CSHP501I
CSHP502I
The STATISTICS= parameter xxxxxxxx can be NO, SYSTEM,
LUW, or FUNCTION only.
Description
A STATISTICS= parameter has been found in the CID Adapter
Server initialization file, but the keyword NO, SYSTEM LUW or
FUNCTION was not found. xxxxxxxx shows the STATISTICS=
parameter found in the file.
User action
Correct the STATISTICS= parameter in the CID Adapter Server
initialization file and restart the CID Adapter Server.
The AUTHORIZATION_KEY does not allow access to xxxxx.
Description
The AUTHORIZATION_KEY parameter has been found in the CID
Adapter Server initialization file, but the key provided does not
allow access to the feature specified by xxxxx.
User action
Contact your Cincom sales representative to obtain the proper
authorization key for the feature.
CID Adapter Server Release n.n.nn.nx started.
Description
The CID Adapter has started.
User action
None, information only.
CID Adapter Server Release n.n.nn.nx shutdown
accepted.
Description
The CID Adapter Server has received a shutdown command.
The command passed validation and the shutdown will occur.
User action
None, information only.
CID Adapter Server Release n.n.nn.nx terminated.
Description
The CID Adapter Server has terminated. This is the last
message from the CID Adapter Server.
User action
None, information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
191
CSPH503I
Transid: nnnn, Task: nnn, Force Purged because of Cics
shutdown.
Description
CICS operator issued a CEMT P SHUT command to shutdown the
CICS region. The CICSSHUT PLTD program has Forced purged all
the outstanding DAK server transactions. A CICS SYNCPOINT
ROLLBACK will be issued by CICS to back out all uncommitted
work. You will also see a CICS transaction abend of AEXY in the
CICS joblog.
User action
If this is the desired action then nothing is required.
If this is not desired action you can remove the CICSSHUT PLTD
program but be aware that CICS will not shutdown until all DAK
server transactions timeout or sign off. This may take an
extended period of time to get CICS shutdown.
CSHP510E
Attach failed for process subtask-type. Reason:
reason-string.
Description
The CID Adapter Server attempted to start a subtask of the
specified type during CID Adapter Server startup. However,
attach failed.
User action
Use the reason string to determine and correct the problem.
The reason string specifies what operating system request
failed, and the return codes. The problem is usually an
environment problem, such as incorrect JCL, not enough
memory, and so on.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
192
CSHP511E
CSHP512I
CSHP513I
CSHP514I
CSHP515E
Process subtask-type failure during startup. Post:
nnnnnn.
Description
A CID Adapter Server subtask of the specified type failed during
startup. The MVS attach postcode specifies the abend code for
the failure. The upper 3 digits comprise a system abend code,
the lower three digits comprise a user abend code in
hexadecimal.
User action
Use the post code to determine and correct the problem. The
problem is usually an environment problem, such as incorrect
JCL, not enough memory, and so on. You may have to call
Cincom Technical Support.
Process process-type started.
Description
A process of the specified type has successfully initialized.
User action
None, information only.
Process process-type terminated.
Description
A process of the specified type has terminated during
shutdown.
User action
None, information only.
Signed off dangling task task-name.
Description
During startup, the specified dangling task was signed off.
User action
None, information only.
Load failed for module-name. Reason: reason-string.
Description
Load of the specified module failed.
User action
Use the reason string to determine and correct the problem.
The reason string specifies what operating system request
failed, and the return codes. The problem is usually an
environment problem, such as incorrect JCL, not enough
memory, and so on.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
193
CSHP516E
CSHP517E
CSHP518E
CSHP519E
Delete failed for module-name. Reason: reason-string.
Description
The delete of the specified module failed.
User action
Use the reason string to determine and correct the problem.
The reason string specifies what operating system request
failed, and the return codes. The problem is usually an
environment problem, such as not enough memory, and so on.
Could not allocate shared memory for PRBs. Size:
nnnnnnn.
Description
There was not enough shared memory to allocate all of the
process request blocks.
User action
Increase the memory in the SHARED_MEM= initialization
parameter. There are as many PRBs as there are concurrent
connections (specified in the PDM_CONNECTIONS parameter)
times 680 bytes for each PRB.
Could not allocate shared memory for ECBs. Size:
nnnnnn.
Description
There was not enough shared memory to allocate the ECB and
wait list.
User action
Increase the memory in the SHARED_MEM= initialization
parameter. There must be enough memory for
PDM_CONNECTIONS times 16 bytes per entry.
Process process-name failure. PID: nnn. Post: nnnnnn.
Description
The specified process failed. The PID parameter specifies
which server process failed. The ECB post code specifies the
abend code for the failure. The upper 3 digits is a system
abend code, the lower three digits is a user abend code in
hexadecimal.
User action
Use the post code to determine and correct the problem. You
may have to contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
194
CSHP520E
CSHP521E
CSHP522I
CSHP523I
CSHP524I
Driver terminating due to unrecoverable error.
Description
The CID Adapter Server is terminating due to an unrecoverable
failure. This is a failure of the Coordinator, PDM task, a
communications task, or the last or only SERVER task.
User action
Restart the CID Adapter Server. You may have to contact
Cincom Technical Support.
Unexpected Status from PDM function function-name.
Stat: status-code.
Description
The PDM returned an unexpected status from the specified
function call.
User action
Use the status to help determine and correct the problem. You
may have to contact Cincom Technical Support.
CID Adapter Server Release n.n.nn.nx waiting for
connections.
Description
The CID Adapter Server has finished initialization and is waiting
for connections.
User action
None, information only.
requested-bytes of shared memory were requested.
used-bytes were used.
Description
Information only. This message indicates how much shared
memory was used by the CID Adapter Server. You can use this
value to tune the SHARED_MEM parameter in the initialization
file.
User action
None, information only.
Database Name: database-name.
Description
Information only. Specifies the name of the database
connected to this CID Adapter Server.
User action
None, information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
195
CSHP525E
CSHP526I
CSHP527E
CSHP528E
Console init failed. R15: return-code.
Description
The MVS QEDIT macro failed.
User action
Use the return code to determine and correct the problem.
You may have to contact Cincom Technical Support.
requested-bytes were requested for parameter
parameter. used-bytes were used.
Description
Information only. This message indicates how much memory
was used by the CID Adapter Server for the MAX_DATAAREA,
MAX_DATALIST, MAX_DATBAS_PDU, and MAX_RCV_PDU
parameters. You can use these values to tune these
parameters in the initialization file.
User action
None, information only.
CSIRESOURCES environment variable not set.
Description
The CID Adapter Server was unable to find the environment
variable CSIRESOURCES.
User action
The CSIRESOURCES environment variable must be set to the
path of the SUPRA PDM resource directory for the SUPRA PDM
system to which you want to connect.
Error creating logical name logical-name value.
Description
The CID Adapter Server was unable to create the logical name
specified.
User action
When the PDM database is prefixed, the CID Adapter Server
attempts to create its own process logical name for CSI_PREFIX.
This error indicates that there was a problem creating this
process logical name. Check the permissions on the PDM
resource directory. The CID Adapter Server process must have
read/write permission on this directory. Contact Cincom
Support for further assistance with this error.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
196
CSHP529E
CSHP530E
CSHP531E
CSHP532E
CSHP533E
Schema reload failed reason.
Description
The CID Adapter Server was unable to reload the schema for
the reason specified.
User action
In order to reload the schema, the CID Adapter Server must
quiet the system by blocking all new transactions from starting
and allowing all existing transactions to complete. The server
will wait for 30 seconds for the system to quiet before giving up
and returning this error to the requesting client. Other errors
require that the CID Adapter Server be restarted.
Could not allocate shared memory for task-name.
Requested size nnn.
Description
There was not enough shared memory available to allocate the
specified task.
User action
Increase the memory in the SHARED_MEM= initialization
parameter.
Could not allocate local memory for table-name.
Requested size nnn.
Description
There was not enough memory available to allocate the
specified table.
User action
Increase the region parameter on the JOB or EXEC card.
DIM failure in function-name at line-number. Status:
status.
Description
The DIM returned an unexpected status from the specified
function call.
User action
Use the status to determine and correct the problem. You may
have to contact Cincom Technical Support.
Schema logic failure in routine-name at line-number.
Reason: reason.
Description
The schema processor found an internal logic error in the
specified routine.
User action
Contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
197
CSHP534E
CSHP535I
CSHP536I
CSHP537E
CSHP538I
Schema build error: error name.
Description
The schema processor found an internal logic error.
User action
Contact Cincom Technical Support.
BIND_SCHEMA option disabled. Building schema from
directory.
Description
The BIND_SCHEMA option is set to FALSE. The schema will be
generated from the directory.
User action
None, information only.
BIND_SCHEMA option enabled. Building schema from
file.
Description
The BIND_SCHEMA option is set to TRUE. The schema will be
generated from the bound schema file.
User action
None, information only.
Unable to open bound schema file. Building schema
from directory.
Description
Although the BIND_SCHEMA option is set to TRUE, the bound
schema file could not be opened. The schema will be
generated from the directory.
User action
This message will be printed if there is no SCHEMA DD
statement or if the schema data set is new (a bound schema
has not been written to it). If there is no DD statement, and
schema binding is desired, add a SCHEMA DD card. If this is the
first time the schema has been bound, ignore the error.
Bound schema mismatch. Building schema from
directory.
Description
Although the BIND_SCHEMA option is set to TRUE, the bound
schema could not be used. The bound schema contained in the
file is for a different schema or environment
Descri
ption than the one that is currently active. The active schema
may have a later consistency check date than the bound
version, indicating that maintenance has been done to the
schema.
User action
CSHP539I
None, information only.
Writing bound schema to file.
Description
The schema has been bound. It is now being written to the
bound schema file.
User action
None, information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
198
CSHP540E
CSHP541E
CSHP542E
CSHP543E
CSHP544E
Bound schema file read error. errno: error-number.
error-text.
Description
The operating system returned an error when reading the
bound schema file.
User action
Use the error number and error text to determine and correct
the problem. You may have to contact Cincom Technical
Support.
Bound schema file write error. errno: error-number.
error-text.
Description
The operating system returned an error when writing the bound
schema file.
User action
Use the error number and error text to determine and correct
the problem. You may have to contact Cincom Technical
Support.
Error closing bound schema file. errno: error-number.
error-text.
Description
The operating system returned an error when closing the bound
schema file.
User action
Use the error number and error text to determine and correct
the problem. You may have to contact Cincom Technical
Support.
Error from RDESC status was status function was
function
Description
A call to the PDM for RDESC information has failed.
User action
Use the PDM error code returned to determine the problem,
then contact Cincom Technical Support.
Directory error - Unable to retrieve Date/Time
compiled of dir
Description
An attempt was made to determine the date and time the
Dbmod was compiled from the directory, but the date and time
was unavailable.
User action
Use CSIDBA to validate and compile the Dbmod, and retry the
operation.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
199
CSHP545E
CSHP546I
CSHP547I
CSHP548E
CSHP549E
CSHP550E
Date/Time mismatch between Dbmod and Directory Please recompile
Description
The Dbmod date/time stamp does not match the directory
date/time stamp.
User action
Use CSIDBA to validate and compile the Dbmod, and retry the
operation.
Dbmod: date_time Directory: date_time
Description
This error displays additional information for message
CSHP545E relating to the Dbmod date/time stamp and the
directory date/time stamp.
User action
None, information only.
Schema build from file
Description
The schema is being loaded from a file rather than being built
from RDESC and directory information.
User action
None, information only.
Failed to read schema file
Description
The schema file could not be read and the schema was not
built.
User action
Delete the schema file and allow the CID Adapter Server to
build a new one using RDESC and directory information.
Error status: status-code Dbmod: database-name
Function: function-name.
Description
A call to the PDM has failed with an unexpected status.
User action
Check the status and act accordingly.
function-name error. Errno: nnn. Server PID: nnn.
Description
The socket library for the TCP communication processor
returned an error when performing the specified function.
User action
Use the error number and error text to determine and correct
the problem. You may have to contact Cincom Technical
Support.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
200
CSHP551E
CSHP552I
CSHP553I
CSHP554E
CSHP555E
CSHP556E
CSHP557I
function-name error on socket-name socket. Errno:
nnn. Server PID: nnn.
Description
The TCP socket library returned an error when performing the
specified function on the specified socket.
User action
Use the error number and error text to determine and correct
the problem. You may have to contact Cincom Technical
Support.
Connection request received from host-name. Port:
port-number.
Description
A connection request was received from the specified host on
the specified port.
User action
None, information only.
Connection rejected for host-name. Reason nnn reasontext.
Description
A connection request from the specified host was rejected.
User action
None, information only.
PDU larger than receive buffer. PDU len: nnn. Buf
len: nnn. Server PID nnn.
Description
A received message is larger than the receive buffer.
User action
Increase the value in initialization parameter RCV_PDU.
Zero length message received. Client disconnected.
Server PID nnn.
Description
A zero-length message was received. Typically, this means the
connection was broken unexpectedly.
User action
None, information only.
Expected database name: expected. Actual database
name: actual.
Description
If the connection was rejected because of a database name
mismatch, the expected and actual names are printed in this
message.
User action
None, information only.
Session canceled for hostname. Server PID nnn.
Description
The session was canceled by the server.
User action
None, information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
201
CSHP558E
CSHP559I
CSHP560I
CSHP600E
CSHP601E
CSHP602E
Server unable to obtain service information for
service name.
Description
The server was not provided a TCP port in the configuration
and was not able to obtain service information via
getservbyname().
User action
Define a TCP port for the server to use. This can be
accomplished with the command line argument, configuration
file, environment variables, or by specifying the service in
/etc/services.
Hostname hostname: IPaddress
Description
If TCP_HOSTNAME_LOOKUP=YES is set in the adapter server
init file, this message displays the hostname and IP address of
the adapter client machine.
User action
None, information only.
PDU has been re-allocated to size bytes
Description
If the incoming message received by the CID Adapter Server is
larger than the current receive buffer size, the receive buffer
is expanded to accommodate the larger message.
User action
None, information only.
Unable to allocate memory for receive PDU. Requested
size: nnn. Server PID: nnn.
Description
There is not enough memory to allocate a receive buffer.
User action
Increase the region size on the JOB or EXEC card.
Unable to allocate memory for command-name response
PDU. Requested size: nnn. Server PID: nnn.
Description
There is not enough memory to allocate a response buffer for
the specified command.
User action
Increase the region size on the JOB or EXEC card.
FAP version mismatch. Received nnn. Expected nnn.
Description
The client and server are at different, incompatible service
levels.
User action
Check the installation and correct whichever is at the incorrect
level.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
202
CSHP603E
CSHP604E
CSHP605E
CSHP606I
pdm-function returned unexpected status. Stat:
status. Server PID: nnn.
Description
The specified PDM function returned an unexpected status.
User action
Use the error status to determine and correct the problem.
You may have to contact Cincom Technical Support.
Request opcode not in range. Received: nnn.
PID: nnn.
Server
Description
A communications request opcode is not in the expected range.
User action
Contact Cincom Technical Support.
Expected Connect request not received. Opcode: nnn.
Description
A communications request opcode is not in the expected range.
User action
Contact Cincom Technical Support.
Extended status: status-code. Server PID: nnn.
Description
The PDM returned an extended status code. This message
comes out in conjunction with message CSHP603E.
User action
Use the error status to determine and correct the problem.
You may have to contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
203
CSHP607E
CSHP608E
CSHP609E
CSHP610I
CSHP611I
Unable to allocate context memory for command-name.
Requested size: nnn. Server PID: nnn.
Description
There was not enough memory to allocate context for the
specified command.
User action
Increase the region size on the JOB or EXEC card.
command-name Response PDU size request is too small.
Requested size: nnn. Minimum: nnn. Server PID: nnn.
Description
The requested size for a response buffer is less than the
minimum required.
User action
Enlarge the response size by changing the setting of the
environment variable ORDB_V1_MAX_RCV_PDU in the client.
Unexpected DIM error in command-name. Status: status.
Server PID: nnn.
Description
The DIM returned an error in the specified command.
User action
Use the error status to determine and correct the problem.
You may have to contact Cincom Technical Support.
Connection accepted from hostname. Client PID: nnn.
Server PID: nnn.
Description
The server accepted the connection from the client.
User action
None, information only.
Shutdown accepted from hostname. Client PID: nnn.
Description
The server accepted the shutdown request from the client.
User action
None, information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
204
CSHP612I
CSHP613E
CSHP614E
CSHP615I
Disconnect from hostname. Server PID: nnn.
Description
The server accepted the disconnect request from the client.
User action
None, information only.
User name or password mismatch.
Description
The user ID or password for a shutdown or an XML file operation
did not match the user ID and password specified in the CID
Adapter Server’s init file. The request was ignored.
User action
None, information only.
Request cancelled.
Record limit nnnnn exceeded
Description
The number of select records read reaches the maximum
record limit (see MAX_RECORDS_LIMIT parameter).
User action
None, information only.
Cannot shutdown due to nn active connections
Description
The CID Adapter client has nn active connections to the CID
Adapter Server and so the CID Adapter Server cannot be
shutdown.
User action
Stop the adapter clients using the stopfdb utility. Alternatively,
in OpenVMS and UNIX you may force the shutdown of the CID
Adapter Server.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
205
CSHP616E
CSHP617E
CSHP618E
CSHP619E
Access module unavailable for file type type
Description
The query has requested information from a file that does not
have an access module in the CID Adapter Server. Currently
only PDM and VSAM file types are supported. VSAM file types
are supported only in the CICS CID Adapter Server.
User action
Contact Cincom Technical Support.
KSDS access method not found for VSAM File file
Description
The CID Adapter Server cannot find the primary KSDS access
method associated with the file. The primary KSDS access
method is created automatically by the CID Adapter Server
during startup
User action
Contact Cincom Technical Support.
XML file request failed, reason.
Description
The CID Adapter Server encountered an error processing an XML
file operation.
User action
Determine the cause of the problem by examining the reason.
Correct the problem and retry the request.
Schema revision number mismatch, expecting revisionnumber, received revision-number.
Description
The CID Adapter Server received a request from a CID Adapter
Client with an obsolete version of the schema.
User action
This error occurs when there are active CID Adapter Clients
running on different machines connected to the same CID
Adapter Server. The CID Adapter Client that requests a RELOAD
of the schema will automatically reload its own schema with no
interruption in service. Other CID Adapter Clients running on
other machines, however, must be restarted in order to reload
their schemas. This configuration is not recommended during
XML file maintenance. A single CID Adapter Client with a single
user is recommended.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
206
CSHP620E
CSHP621E
CSHP630E
Unknown file name file-name.
Server PID: nnn.
Description
The GETFILE command requested information on an unknown
file.
User action
This is usually caused by defining a foreign table with an
incorrect file name. Correct the foreign table.
Response PDU is not large enough to hold all external
fields. Max size: nnn. Server PID: nnn.
Description
There is not enough room in a response buffer to hold all of the
information for a GETFILE command.
User action
Enlarge the response size by changing the setting of the
environment variable ORDB_V1_MAX_RCV_PDU in the client.
Unknown class name class-name.
Server PID: nnn.
Description
When using the Visual Editor, there was a request for
information on an unknown file or class (a file_rc name).
User action
Specify a correct file or class name.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
207
CSHP640E
CSHP641E
CSHP642E
CSHP643E
CSHP644E
Unknown class name class-name. Server PID: nnn.
Description
A read or update request specified an invalid class name.
User action
This is usually caused by defining a foreign table with an
incorrect file or class name. Correct the foreign table.
Unable to parse view.
Description
The CID Adapter Server was unable to parse the view string
supplied.
User action
Examine the CID Adapter Server log file for more information
on the cause of this problem. Contact Cincom Support.
Unable to allocate space for DAT. Required entries:
nnn. Server PID: nnn.
Description
There was not enough space to allocate the datalist table in
the server. The required size is approximately
(30 ∗ the number of data elements) + the size of all paths.
User action
Increase the region size on the JOB or EXEC card.
Required record greater than requested data area
size. Record size: nnn. Data area size: nnn. Server
PID: nnn.
Description
The size needed to return a record is greater than the size of
the allocated data area.
User action
Increase the value in the MAX_DATAAREA parameter.
Invalid client datalist item element-name. Server
PID: nnn.
Description
The specified data element from the client is too long or
unknown.
User action
Probable client internal error. Contact Cincom Technical
Support.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
208
CSHP645E
CSHP646E
CSHP647E
Unable to insert DAT entry. Server PID: nnn.
Description
The datalist attribute table ran out of room. This is caused by
the server running out of memory.
User action
Increase the region size on the JOB or EXEC card.
Requested attribute attribute-name not found in
server attributes. Server PID: nnn.
Description
A requested attribute could not be found in the server schema.
User action
Probable server internal error. Contact Cincom Technical
Support.
Buffer overflow writing sequence. Buffer size:
buffer-size. Server PID: nnn.
Description
A sequence was too long to fit in the data buffer.
User action
Do one of the following:
♦
Enlarge the response size by changing the setting of the
environment variable ORDB_V1_MAX_RCV_PDU in the client
♦
Request fewer sequences in the SELECT statement (if more
than one was selected)
♦
Use OO-access rather than sequence access to reduce the
number of OIDs returned
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
209
CSHP648E
View plan execution error: message
Description
User action
CSHP649E
CSHP660E
CSHP661E
CSHP670I
An error occurred while executing a CID Adapter View
execution plan. Message is one of the following error messages:
♦
Non-aliased attribute xxxxxxxx is ambiguous - use
alias:attribute in the SELECT clause
♦
plan not found for access xxxxxxxx
♦
planrc not found for access xxxxxxxx
♦
plan not found to extract key attribute xxxxxxxx
♦
dat entry not found for attribute name %s
The first message is a usage error. This error may be corrected
by adding an alias name to the referenced attribute in the CID
Adapter View foreign table. The remaining messages are
internal errors. Contact Cincom Technical Support.
DAT entry not found, reason
Description
An internal error has occurred in the CID Adapter Server while
attempting to copy data to or from the internal data area used
for non-PDM fields and dates defined in the XML file.
User action
Internal error. Contact Cincom Technical Support.
Commit tranid mismatch. Received TranID: nnn, Current
TranID: nnn. Server PID: nnn.
Description
When a commit was issued, the transaction ID shared by the
client and server did not match. The transaction may be out of
synchronization.
User action
Internal error. Contact Cincom Technical Support.
Reset tranid mismatch. Received TranID: nnn, Current
TranID: nnn. Server PID: nnn.
Description
When a rollback was issued, the transaction ID shared by the
client and server did not match. The transaction may be out of
synchronization.
User action
Internal error. Contact Cincom Technical Support.
All Vsam paths for a base must be defined before the next
base, Base: nnnnnnnn, Path: nnnnnnnn
Description
All path/index files for a base file must be defined before the
next base file. A good practice is to start each base file on a
new VSAM_FILE_LIST parameter.
User action
Correct the VSAM_FILE_LIST parameters.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
210
CSHP671I
Vsam file (Base or Path) requested not located in current
Cics, File: nnnnnnnn.
Description
The file requested was not located in the active CICS.
User action
Ignore message or remove the file from the VSAM_FILE_LIST=
parameter.
Define the file to CICS and restart CICS.
CSHP672I
CSHP673I
Vsam file located but not a Base or Path, File: nnnnnnn
Description
File was located in the current CICS but is not a base or path
type file. Only base and paths can be defined on the
VSAM_FILE_LIST parameter.
User action
Remove the file or correct the file type in CICS.
Vsam file located but could not be opened, File: nnnnnnnn
Description
To build the schema, we must be able to open the file to get
some required information. The file could not be opened.
User action
Correct the file definition to CICS and make sure the file is
available to CICS.
The file is not added to the schema. If you expect this, ignore
the message.
CSHP674I
Vsam file located but not available for use, File: nnnnnnn
Description
File was located but is marked by CICS as DISABLED. File is not
added to the schema.
User action
Enable the file or ignore the message.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
211
CSHP675I
CSPH676I
CSHP677I
CSHP680W
CSHP681E
CSHP682E
CSHP700E
Vsam file located but not a type KSDS, RRDS, ESDS, or Path,
File nnnnnnn
Description
File is not a supported type.
User action
Remove the file from the VSAM_FILE_LIST parameter.
Included Vsam File: nnnnnnnn Type: nnnn Object: nnnn
Dsname: nnnnnnnnnnnn
Description
This file has been added to the schema.
User action
None.
Included Vsam File: nnnnnnn Object: nnnn To File: nnnnnnnn
Dsname: nnnnnnnnnnnn
Description
This path/index file has been added to the schema.
User action
None.
Floating point overflow/underflow. Element: elementname. Server PID: nnn.
Description
When converting floating-point data from client to server
format, the value was out of the range that can be held by the
server.
User action
None. The server stores the PDM default value.
Not all fields have been copied to the internal
database I/O area, expecting nnnn, copied nnnn.
Description
An internal error occurred while copying external data fields to
the internal I/O area. The CID Adapter Server did not copy all
of the external fields specified in the DAT.
User action
Internal error. Contact Cincom Technical Support.
Base field not found for class class.
Description
The base field for a VSAM file was not found. The base field is
created automatically by the CID Adapter Server during
startup.
User action
Contact Cincom Technical Support.
Could not allocate shared memory for PDM areas.
Size: nnn.
Description
There was not enough shared memory to build the PDM areas.
The required size is specified.
User action
Increase the memory in the SHARED_MEM= initialization
parameter.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
212
CSHP701E
Load failed for CSTEDCMT. Reason: reason-code.
Description
Load of module CSTEDCMT failed.
User action
Use the MVS reason code to determine and correct the
problem. The problem is usually an environment problem, such
as incorrect JCL, not enough memory, and so on.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
213
CSHP702E
CSHP703E
CSHP720E
CSHP750E
Delete failed for CSTEDCMT. Reason: reason-code.
Description
The delete of module CSTEDCMT failed.
User action
Use the MVS reason code to determine and correct the
problem. The problem is usually an environment problem, such
as not enough memory, and so on.
function-name returned unexpected status. Options:
options-parameter. Stat: status.
Description
The PDM returned an unexpected status in the PDM task.
User action
Use the status code to help determine the problem. You may
have to contact Cincom Technical Support.
SHOWCB error for function function-name. R15: returncode. R0: error-code. Server PID: nnn.
Description
A VTAM SHOWCB macro returned an error.
User action
Use the status codes to help determine the problem. You may
have to contact Cincom Technical Support.
Date/Time error: reason
Description
An error occurred in the CID Adapter Server while converting a
database field to or from a date, time or timestamp. This can
be caused by incorrect data in the database or an incorrect
Date_format string in the XML file.
User action
Examine the reason to determine the problem. If the problem
is incorrect data in the database, it will be necessary to clean
the data before date conversion can be used. If the problem is
in the Date_format string, correct the Date_format string in
the XML file and reload the schema or restart the CID Adapter
Server.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
214
CSHP751E
CSHP820I
CSHP821I
CSHP822I
Date/Time internal error: reason
Description
An internal error occurred in the CID Adapter Server while
converting a database field to or from a date, time or
timestamp.
User action
Internal error. Contact Cincom Technical Support.
FUNCTIONS EXECUTED BY THE DRIVER.
Description
This is a header for the statistics information.
User action
None, information only.
SELECT.
Description
This is a header for the select statistics information. It will be
followed by messages CSHP828I, CSHP829I, CSHP830I, and
CSHP831I.
User action
None, information only.
SEARCHED UPDATE.
Description
This is a header for the searched update statistics information.
It will be followed by messages CSHP828I, CSHP829I, CSHP830I,
and CSHP831I.
User action
None, information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
215
CSHP823I
CSHP824I
CSHP825I
CSHP826I
CSHP827I
CSHP828I
CSHP829I
SEARCHED DELETE.
Description
This is a header for the searched delete statistics information.
It will be followed by messages CSHP828I, CSHP829I, CSHP830I,
and CSHP831I.
User action
None, information only.
OO FETCH
nnnnnnnnnn.
Description
This is the number of OO-based fetch requests.
User action
None, information only.
OO UPDATE
nnnnnnnnnn.
Description
This is the number of OO-based update requests.
User action
None, information only.
OO INSERT
nnnnnnnnnn.
Description
This is the number of OO-based insert requests.
User action
None, information only.
OO DELETE
nnnnnnnnnn.
Description
This is the number of OO-based delete requests.
User action
None, information only.
by Direct
nnnnnnnnnn.
Description
This is the number of functions processed by direct
(READM/READD) access.
User action
None, information only.
By Index
nnnnnnnnnn.
Description
This is the number of functions processed by following the
index.
User action
None, information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
216
CSHP830I
CSHP831I
CSHP832I
CSHP840I
CSHP841I
CSHP842I
CSHP843I
CSHP844I
By LinkPath
nnnnnnnnnnd.
Description
This is the number of functions processed by following the
linkpath.
User action
None, information only.
By Scan
nnnnnnnnnn.
Description
This is the number of functions processed by scanning the file.
User action
None, information only.
TOTAL
nnnnnnnnnn.
Description
This is the total function of a particular type.
User action
None, information only.
OPTIMIZER EXPLANATION for Class class-name.
Description
This is the explain header message. It identifies the class being
processed.
User action
None, information only.
Qualifier:
Description
This message is the header message for the qualifier. The
qualifier is listed below using prefix notation.
User action
None, information only.
Strategy Selected: strategy-name.
Description
This message identifies the strategy selected by the optimizer.
The strategy number refers to the strategy number identified in
CSHP854I.
User action
None, information only.
PDM READX Qualifier value:
Description
This message shows the READX qualifier field (in hex and
EBCDIC/ASCII) that is passed to the PDM for indexed access.
User action
None, information only.
PDM READX Options value:
Description
This message shows the READX options field (in hex and
EBCDIC/ASCII) that is passed to the PDM for indexed access.
User action
None, information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
217
CSHP845I
CSHP846I
CSHP847I
CSHP849I
CSHP850I
No optimization: No qualifier, or bypass enabled.
Description
This message indicates that the file will be scanned, either
because there is no qualifier (requiring all records to be
returned) or because one of the optimizer bypass options is
turned on for debugging.
User action
None, information only.
Control key or linkpath access on field field-name.
Description
This message indicates that the optimizer will use the named
control key (primary file) or referback control key (related file)
for access.
User action
None, information only.
No key or linkpath access found.
Description
This message indicates that the optimizer was unable to find a
direct (key-based or RRN-based) access method.
User action
None, information only.
Primary access-method/linkpath linkpath-name access
found.
Description
This message indicates that the optimizer found a path
expression optimization.
User action
None, information only.
PDM RDNXT Qualifier value:
Description
This message shows the RDNXT qualifier (in hex and
EBCDIC/ASCII) that is passed to the PDM for scan access.
User action
None, information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
218
CSHP851I
CSHP852I
CSHP853I
PDM READV Linkpath: linkpath-name.
Description
This message shows the READV linkpath name that is used for
linkpath access.
User action
None, information only.
PDM READM/READV CTRL key value: key-value.
Description
This message shows the READV control key (in hex and
EBCDIC/ASCII) that is passed to the PDM for linkpath access.
User action
None, information only.
All possible strategies
Description
Identifies the beginning of the strategy
ptions of the optimizer explain output in the log file.
User action
CSHP854I
CSHP855I
CSHP856I
Descri
None, information only.
Strategy n
Description
Identifies the strategy number of each strategy identified by
the optimizer. Strategies are numbered 1–n. The strategy
selected by the optimizer is identified in the message
CSHP842I.
User action
None, information only.
<access-type> access
Description
This message defines the type of PDM access identified: direct,
linkpath, index, primary direct/linkpath, primary
indexed/linkpath, primary scan/linkpath, or scan.
User action
None, information only.
Cost for strategy n = nnnnnnn
Description
Identifies the estimated cost of executing a strategy based on
the sum of all access methods identified for the strategy.
User action
None, information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
219
CSHP857I
CSHP858I
CSHP859I
No key or linkpath access found
Description
Indicated that the optimizer was unable to find a direct access
method.
User action
None, information only.
Linkpath or key access selected over index due to
partial index mapping.
Description
Indicates that the optimizer has chosen a direct access method
over an indexed access method because the index was only
partially mapped.
User action
None, information only.
Indexed access selected due to full index mapping
Description
Indicates that the optimizer has chose an indexed access
method over a direct access method because the index was
fully mapped.
User action
None, information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
220
CSHP860I
xxxxxx...
BEGIN
..COMPARE HISTTLNM = ‘2F2H’
OR
.BEGIN
..COMPARE HISTTLNM = ‘SFGD’
AND
..COMPARE HISTODMO <= ‘12’
.AND
..COMPARE HISTODYR <= ‘97’
..COMPARE HISTODMO >= ‘01’
..COMPARE HISTODYR >= ‘94’
..COMPARE HISTCCNO = ‘4911’
.END
END
CSHP861I
CSHP862I
Description
This message is used to print the WHERE clause of the query in
BEGIN/END format.
User action
None, information only.
Scan access required.
Description
The optimizer has not been able to identify any access methods
except scan.
User action
None, information only.
The best strategy contains a scan access.
Only one scan access will be executed.
Description
The optimizer has selected a strategy that contains a scan
access method. If the strategy contains any other access
methods or any additional scan access methods, only 1 scan
access will be executed.
User action
None, information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
221
CSHP870I
CSHP871I
CSHP872I
CSHP873I
CSHP874I
CSHP875I
CSHP876I
CSHP877I
RECORDS READ BY THE CURRENT xxxxx FUNCTION
Description
This message marks the beginning of an abbreviated statistics
block. In the message, xxxxx will be replaced by "SELECT",
"SEARCHED UPDATE" or "SEARCHED DELETE" (see STATS=
parameter).
User action
None. Information only.
RECORDS READ BY THE CURRENT LOGICAL UNIT OF WORK
Description
This message marks the beginning of an abbreviated statistics
block (see STATS= parameter).
User action
None. Information only.
CID ADAPTER STATISTICS
Description
This message marks the beginning of a full statistics block (see
STATS= parameter).
User action
None. Information only.
SELECT FUNCTIONS EXECUTED nnnnnnnn
Description
Identifies the number of select functions executed.
User action
None. Information only.
RECORDS READ BY THE SELECT FUNCTION
Description
Identifies the number of records read by a select function.
User action
None. Information only.
SEARCHED UPDATE FUNCTIONS EXECUTED nnnnnnnn
Description
Identifies the number of searched update functions executed.
User action
None. Information only.
RECORDS READ BY THE SEARCHED UPDATE FUNCTION
Description
Identifies the number of records read by a searched update
function.
User action
None. Information only.
SEARCHED DELETE FUNCTIONS EXECUTED nnnnnnnn
Description
Identifies the number of searched delete functions executed.
User action
None. Information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
222
CSHP878I
CSHP879I
CSHP880I
CSHP881I
CSHP882I
CSHP883I
RECORDS READ BY THE SEARCHED DELETE FUNCTION
Description
Identifies the number of records read by a searched delete
function.
User action
None. Information only.
Strategy
Records Read Qualified
Description
Column header for the following messages.
User action
None. Information only.
Direct
nnnnnnnn
nnnnnnnn
Description
Identifies the number of records read and the number of
records qualified for all direct access methods executed.
User action
None. Information only.
Index
nnnnnnnn
nnnnnnnn
Description
Identifies the number of records read and the number of
records qualified for all indexed access methods executed.
User action
None. Information only.
Linkpath
nnnnnnnn
nnnnnnnn
Description
Identifies the number of records read and the number of
records qualified for all linkpath access methods executed.
User action
None. Information only.
Scan
nnnnnnnn
nnnnnnnn
Description
Identifies the number of records read and the number of
records qualified for all scan access methods executed.
User action
None. Information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
223
CSHP884I
CSHP885I
CSHP886I
CSHP887I
CSHP888I
CSHP889I
CSHP890I
Path Records
nnnnnnnn
Description
Identifies the number of records read to satisfy the path
expressions of queries.
User action
None. Information only.
Set
Records
nnnnnnnn
Description
Identifies the number of records read to satisfy the sets
specified in queries.
User action
None. Information only.
TOTAL
nnnnnnnn
nnnnnnnn
Description
Identifies the number of records read and records qualified for
all queries.
User action
None. Information only.
OO
FETCH FUNCTIONS EXECUTED nnnnnnnn
Description
Identifies the number of oo_fetch functions executed.
User action
None. Information only.
OO UPDATE FUNCTIONS EXECUTED nnnnnnnn
Description
Identifies the number of oo_update functions executed.
User action
None. Information only.
OO INSERT FUNCTIONS EXECUTED nnnnnnnn
Description
Identifies the number of oo_insert functions executed.
User action
None. Information only.
OO DELETE FUNCTIONS EXECUTED nnnnnnnn
Description
Identifies the number of oo_delete functions executed.
User action
None. Information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
224
CSHP900E
CSHP901E
CSHP902E
CSHP903I
CSHP905I
CSHP906I
CSHP907I
CSHP908I
System service: vms-system-service failure code:
status-code, message: message-text.
Description
This message shows the status code and message associated
with the VMS system service failure.
User action
Examine the message and correct the fault.
Mandatory parameter missing.
Description
The server or coordinator function was issued with less then
two parameters.
User action
Correct the command and re-execute.
Incorrect function specified (SERVER or COORDINATOR).
Description
The first parameter passed for server or coordinator initiation
must be SERVER or COORDINATOR.
User action
Correct the command and re-execute.
HUB COORDINATOR REQUEST Release n.n.nn.n - TCP PORT
nnnn.
Description
This message reports an operator request associated with the
coordinator shutdown function. The port number uniquely
identifies the coordinator.
User action
None, information only.
ELS=nnn, CPU=nnn, DirIO=nnn, BuffIO=nnn, PFlts=nnn.
Description
This message provides statistics before a message send.
User action
None, information only.
ELS=nnn, CPU=nnn, DirIO=nnn, BuffIO=nnn, PFlts=nnn.
Description
This message provides statistics after a message send.
User action
None, information only.
ELS=nnn, CPU=nnn, DirIO=nnn, BuffIO=nnn, PFlts=nnn.
Description
This message provides statistics before a message receive.
User action
None, information only.
ELS=nnn, CPU=nnn, DirIO=nnn, BuffIO=nnn, PFlts=nnn.
Description
This message provides statistics after a message receive.
User action
None, information only.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
225
CSHP910I
CSHP911E
CSHP912E
CSHP913I
CSHP914E
CSHP950E
Peak working set = nnnn, Peak virtual memory usage =
nnnn.
Description
This message provides statistics at the end of the server run.
User action
None, information only.
Port number in INIT file file-name does not match
server port nnnn.
Description
The port in the initialization file does not match the port
entered on the command line.
User action
Check the logical name CSI_INIT_FILE to determine whether the
coordinator is using an incorrect initialization file. Check the
command line to determine whether the entered port number
is incorrect.
Size/Address mismatch between loaded schema
size/address and server process size/address.
Description
The size of the schema does not match the size of the global
section.
User action
Check the logical name for CSI_SERVER_SCHEMA.
Foreign key file not found.
Description
The coordinator was unable to locate the foreign key file
during the schema build.
User action
If the foreign key file should exist, check the logical name for
CSI_FOREIGN_KEY.
Insufficient privileges to run a server.
Description
The process initiating the server or coordinator does not have
sufficient privileges.
User action
Check the current privileges and modify the user authorization
file if necessary.
Schema build error: reason-text.
Description
The coordinator failed to build the schema.
User action
Check the reason and make the appropriate correction.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
226
CSHP951E
CSHP952E
Prefix: xxxx Version: nnnn Name: xxxxxxx.
Description
This message identifies the directory key causing the problem
identified in message CSHP549E.
User action
Contact Cincom Technical Support.
Error Process ID: pid Status: pdm-status Function:
pdm-function.
Description
An unexpected status was returned by PDM.
User action
Contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
227
CSHP953E
View parsing error on line nnnn: message
Description
An error occurred while parsing CID Adapter Views or type
overrides in the foreign key file. The line number refers to the
line number in the foreign key file. The message refers to one
of the following error messages:
♦
Type override syntax error, expecting datasetname.data-item xxxxxxxx.
♦
Type override class xxxxxxxx not found.
♦
Type override attribute xxxxxxxx not found.
♦
View name xxxxxxxx in DEFINE statement is too
long, expecting 1 - 32 characters.
♦
Invalid view name xxxxxxxx, class name already
exists.
♦
Invalid view name xxxxxxxx, view name already
exists.
♦
schema_build_class failed for view xxxxxxxx.
♦
Alias name %s too long in VIEW xxxxxxxx, expecting
1 - 32 characters.
♦
Dataset name xxxx invalid in VIEW xxxxxxxx,
expecting 4 characters.
♦
Class name xxxxxxxx not found in VIEW xxxxxxxx.
♦
Invalid record code xx expecting 2 characters in
ACCESS xxxxxxxx, VIEW xxxxxxxx.
♦
Class xxxxxxxx not found in ACCESS xxxxxxxx, VIEW
xxxxxxxx.
♦
Cannot use ACCESS clauses on the first ACCESS of a
view. Use a WHERE clause in the SELECT statement
instead. ACCESS xxxxxxxx, VIEW xxxxxxxx.
♦
Cannot use FROM and USING in the same ACCESS
statement xxxxxxxx, VIEW xxxxxxxx.
♦
Only one FROM clause may be specified in ACCESS
xxxxxxxx, VIEW xxxxxxxx.
♦
Cannot use FROM and VIA index in the same ACCESS
statement, xxxxxxxx, VIEW xxxxxxxx.
♦
ACCESS xxxxxxxx referenced in FROM clause not
found in ACCESS xxxxxxxx, VIEW xxxxxxxx.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
228
♦
Invalid record code xx in ACCESS xxxxxxxx, VIEW
xxxxxxxx.
♦
Record code xx specified in FROM clause is not
defined for referenced ACCESS in ACCESS xxxxxxxx,
VIEW xxxxxxxx.
♦
The target ACCESS xxxxxxxx specified in the FROM
clause contains multiple record codes. ACCESS %s,
View %s.\n"
♦
, pVacc->pVACCFrom->szName, accessName,
viewName)
♦
Invalid record code specification in FROM clause,
ACCESS xxxxxxxx, VIEW xxxxxxxx.
♦
Only one VIA clause may be specified in ACCESS,
xxxxxxxx, VIEW xxxxxxxx.
♦
Access method xxxxxxxx in VIA clause is not found
in ACCESS xxxxxxxx, VIEW xxxxxxxx.
♦
Access method xxxxxxxx in VIA clause is not valid in
ACCESS xxxxxxxx, VIEW xxxxxxxx, expecting SK or
LK.
♦
Cannot use a FROM clause with an indexed access
method in ACCESS xxxxxxxx, VIEW xxxxxxxx.
♦
Cannot use a USING clause with a FROM clause in
ACCESS xxxxxxxx, VIEW xxxxxxxx.
♦
Only one USING clause may be specified in ACCESS
xxxxxxxx, VIEW xxxxxxxx.
♦
Quote mismatch xxxxxxxx in ACCESS xxxxxxxx,
VIEW xxxxxxxx.
♦
Attribute xxxxxxxx specified in USING clause was
not found in ACCESS xxxxxxxx, VIEW xxxxxxxx.
♦
The USING key xxxxxxxx must not refer to itself in
ACCESS xxxxxxxx, VIEW xxxxxxxx.
♦
Syntax error in access xxxxxxxx, view xxxxxxxx.
♦
Attribute xxxxxxxx required for key target in FROM
clause was not found in ACCESS xxxxxxxx, VIEW
xxxxxxxx.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
229
User action
CSHP954I
CSHP955I
♦
Attribute xxxxxxxx required for implied USING
clause was not found in ACCESS xxxxxxxx, VIEW
xxxxxxxx.
♦
Literal length referenced in USING clause does not
match the data item length for the access method
in ACCESS xxxxxxxx, VIEW xxxxxxxx.
♦
Data item length referenced in USING clause does
not match the data item length for the access
method in ACCESS xxxxxxxx, VIEW xxxxxxxx.
Review the text of the message and make appropriate changes
in the foreign key file at the referenced line number.
Entity entity-name added to schema.
Description
Reports that an entity such as a view or VSAM file has been
successfully added to the schema.
User action
None, information only.
XML parser error: error-type, File: file-name, Line: linenumber, Column: column-number Message: reason.
Description
The XML parser in the CID Adapter Server has detected an error
while parsing the XML file or buffer.
User action
Examine the reason and determine the cause by viewing the
XML file at the line number and column specified. Correct the
problem and restart the server or re-issue the reload command.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
230
CSHP956I
CSHP957I
CSHP958E
CSHP959I
CSHP960E
CSHP961I
XML syntax error on line nnnn: reason.
Description
A syntax error was detected by the CID Adapter server while
processing the XML file.
User action
Examine the reason and view the XML file at the line specified.
Correct the problem and restart the CID Adapter server or reissue the reload command.
XML error: reason.
Description
An error was encountered in the CID Adapter Server while
processing the XML file.
User action
Examine the reason code and correct the problem. Re-start the
CID Adapter Server or re-issue the reload command.
XML internal error error near line line number: reason.
Description
An internal error was encountered in the CID Adapter Server
while processing the XML file.
User action
Internal error. Contact Cincom Technical Support.
message.
Description
Reports information regarding Adapter Extensions XML file
operations and the progress of schema RELOAD requests in the
CID Adapter Server.
User action
None, information only.
Foreign Key parsing error on line nnnnnn: reason
Description
An error was encountered while parsing the foreign key
information in the foreign key file.
User action
Examine the reason code and correct the problem. Re-start the
CID Adapter Server or re-issue the reload command.
Foreign Key process error: reason
Description
An error was encountered while processing a foreign key. The
foreign key was not added to the internal schema.
User action
Examine the reason code and correct the problem. Re-start the
CID Adapter Server or re-issue the reload command.
Messages and Codes, P25-9502-04
Chapter: 2. CID Adapter Server and Adapter Client error messages
Section: CID Adapter Server and Adapter Client error messages
231
3. JDBC error messages
Overview
This chapter lists the error messages that the Cincom SQL Access JDBC driver
can return. Messages are in alphabetic order.
Messages and Codes, P25-9502-04
Chapter: 3. JDBC error messages
Section: Overview
232
JDBC error messages
The following JDBC messages can be returned in an SQLException raised by the
Cincom SQL Access JDBC Driver:
BLOB and CLOB can only be created from object derived from class glo.
Description
The getBlob and getClob methods are only valid for ResultSet
columns that contain an object reference to a Cincom SQL
Access glo object (or subclass of glo).
User action
Verify that you are specifying the proper column name or
number for the method. Verify the schema definition to make
sure the object in question is a Cincom SQL Access glo.
Cannot convert to requested type
Description
The method failed because the specified conversion is illegal.
This can happen on setXXX or getXXX methods (XXX is the jdbc
data type). The driver could not convert from/to the database
type and the specified jdbc type.
User action
Modify the code to use a valid data type for the conversion.
Consult the documentation for legal data type conversion.
Current ResultSet contains no results
Description
The method cannot be carried out on an empty ResultSet.
User action
Modify the code to check for a non-empty ResultSet before
attempting the method call.
executeInsert requires a non-NULL SQL statement
Description
This method requires a valid SQL statement.
User action
Provide a valid SQL statement.
executeQuery called with SQL that does not return a result set
Description
The executeQuery method is designed for SQL statements that
return a ResultSet. The SQL statement passed to this method
does not return a ResultSet.
User action
Validate the SQL statement. Use the executeInsert method to
perform SQL statements that do not return a ResultSet.
executeQuery requires a non-NULL SQL statement
Description
This method requires a valid SQL statement.
User action
Provide a valid SQL statement.
Messages and Codes, P25-9502-04
Chapter: 3. JDBC error messages
Section: JDBC error messages
233
executeQuery(string) and executeUpdate(String) can only be called by a
Statement object
Description
An SQL statement cannot be passed to the executeQuery nor
executeUpdate methods of a prepared statement.
User action
Either use the executeQuery() or executeUpdate() methods of
PreparedStatement, or use a Statement instead of a
PreparedStatement.
executeUpdate called with an SQL statement which returns a result set.
Description
The executeUpdate method is designed for SQL statements that
do not return a ResultSet. The SQL statement passed to this
method returns a ResultSet.
User action
Validate the SQL statement. Use the executeQuery method to
perform SQL statements that return a ResultSet.
executeUpdate called with SQL that returns a result set
Description
The executeUpdate method is designed for SQL statements that
do not return a ResultSet. The SQL statement passed to this
method returns a ResultSet.
User action
Validate the SQL statement. Use the executeQuery method to
perform SQL statements that return a ResultSet.
executeUpdate requires a non-NULL SQL statement
Description
This method requires a valid SQL statement.
User action
Provide a valid SQL statement.
Internal system failure: no more specific information can be retrieved
Description
Internal Error.
User action
Please contact Cincom technical Support.
Messages and Codes, P25-9502-04
Chapter: 3. JDBC error messages
Section: JDBC error messages
234
Invalid argument(s) arg in function
Description
An invalid argument was passed to the method.
User action
Please correct the arguments.
Invalid column index or name
Description
The column name or index passed to the method is not valid for
the ResultSet.
User action
Verify the ResultSet column names and/or indices and correct
the code.
Invalid cursor position
Description
The ResultSet is not positioned on a valid row.
User action
Make sure the ResultSet is positioned on a valid row before
invoking the method that raised the exception.
Invalid insert results
Description
The insert statement returned more than one result object.
This is an internal error.
User action
Please contact Cincom technical Support.
Invalid isolation level
Description
The isolation level passed in the setIsolationLevel method of
the Connection interface is invalid.
User action
Please pass a valid isolation level.
Maximum field size must be greater than or equal to 0
Description
The value passed to the setMaxFieldSize method is invalid.
User action
Please pass a size that is greater than or equal to 0.
Maximum row limit must be greater than or equal to 0
Description
The value passed to the setMaxRows method is invalid.
User action
This is not supported by the Cincom SQL Access JDBC Driver.
Either remove the method call, or pass 0 for the parameter.
Messages and Codes, P25-9502-04
Chapter: 3. JDBC error messages
Section: JDBC error messages
235
Operation failed with SQLSTATE sqlstate, native error code errnum:
error-text
Description
The specified error was returned by the database.
User action
Please refer to the documentation for the specified errnum.
Parameter at index parm-index has not been set
Description
The PreparedStatement does not have a value for the specified
parameter index.
User action
Make sure that all parameters of the SQL statement have been
assigned values with the setXXX methods before attempting to
execute the SQL.
PreparedStatement requires a non-NULL SQL statement
Description
This method requires a valid SQL statement.
User action
Provide a valid SQL statement.
Primitive cannot be null
Description
The getArray method was invoked on a homogeneous Cincom
SQL Access collection that has a primitive domain. The JDBC
specification states that a collection of primitives should be
returned as an array of primitives. One or more of the
elements in the collection is null, which cannot be handled by
a primitive java data type.
User action
Use the ordbCollection.getAlwaysReturnsObjects method to tell
the Cincom SQL Access JDBC Driver to return the data as an
array of java objects instead of java primitives.
Problem creating temp file for BLOB and CLOB inputstream
Description
A system error was encountered when attempting to allocate a
temporary file.
User action
Make sure that the file system is not full, and that the
application has permission to create temporary files.
Messages and Codes, P25-9502-04
Chapter: 3. JDBC error messages
Section: JDBC error messages
236
ResultSet closed, collection size has changed
Description
The Cincom SQL Access JDBC Driver has determined that a
ResultSet opened from a Cincom SQL Access collection (via the
Array interface of ordbCollection) no longer has the same
number of elements as when the ResultSet was opened. The
ResultSet has been closed.
User action
The ResultSet will have to be re-opened.
System attributes are currently not accessible
Description
The Cincom SQL Access object being accessed with custom
mapping only contains attributes derived from built-in system
classes. These attributes are not exposed with custom
mapping.
User action
Consider using method calls in conjunction with the ordbObject
methods to access the system information.
Unimplemented method
Description
The Cincom SQL Access JDBC driver does not support this
method.
User action
The method is not supported by the Driver. Please remove the
invocation.
Unknown Connection object – not implemented by ordbConnection
Description
The ordbCollection constructor was called with an invalid
Connection parameter. The Connection parameter must be a
valid Cincom SQL Access Database connection (e.g. an instance
of ordbConnection).
User action
Correct the code to pass a valid Connection object to the
constructor.
Unknown error in JNI layer initialization
Description
Error was encountered during initialization of the native code
interface layer of the Cincom SQL Access JDBC Driver.
User action
Make sure that the Cincom SQL Access client runtime is
properly configured on the machine.
Messages and Codes, P25-9502-04
Chapter: 3. JDBC error messages
Section: JDBC error messages
237
Unsupported parameter type type-code at index parm-index
Description
The specified parameter of the PreparedStatement has an
invalid data type.
User action
Correct the input parameter passed to the PreparedStatement.
Unsupported type type-code in get method
Description
The data type used in getXXX method is invalid for the Cincom
SQL Access data being requested.
User action
Use a getXXX method that is a compatible data type for the
data being requested.
Messages and Codes, P25-9502-04
Chapter: 3. JDBC error messages
Section: JDBC error messages
238
4. OrdbXML Java error messages
Overview
This chapter presents error codes in alphabetic sequence.
Messages and Codes, P25-9502-04
Chapter: 4. OrdbXML Java error messages
Section: Overview
239
OrdbXML Java error messages
The following OrdbXML Java messages can be returned:
Attribute %s mapped more than once as a property of %s.
Description
The map contains a ClassMap definition where two attribute
definitions have the same name.
User action
Correct the attribute definitions in the ClassMap.
Bad value for '%s' attribute: %s.
Description
This value for the specified attribute is not allowed in its
current context.
User action
Correct the attribute definitions in the ClassMap.
Binary data not supported.
Description
Binary data is not supported for setting a String parameter in a
PreparedStatement.
User action
Check for proper data type usage. If you suspect this is an
OrdbXML issue, then please gather reproduction details and
contact Cincom Technical Support.
Character required: %s.
Description
In parsing the DTD, the given character was expected.
User action
Correct the DTD.
ChildList has parallel entries.
Description
The internal components of the ChildList collection are out of
synchronization. Memory may have become corrupted.
User action
If this error persists, then please gather reproduction details
and contact Cincom Technical Support.
Messages and Codes, P25-9502-04
Chapter: 4. OrdbXML Java error messages
Section: OrdbXML Java error messages
240
ChildList sizes different.
Description
The internal components of the ChildList collection are out of
synchronization. Memory may have become corrupted.
User action
If this error persists, then please gather reproduction details
and contact Cincom Technical Support.
ClassAttribute %s not found in ClassName %s.
Description
The database Class does not have the ClassAttribute defined.
User action
Correct the database Class definition, or correct the map.
ClassName not found: %s.
Description
The Class is not defined on the database.
User action
Define the Class on the database, or correct the ClassName in
the map.
ClassName %s not mapped as a root element.
Description
The ClassName “Result Set” is either not mapped or is not
mapped properly.
User action
Be sure the map contains a mapping for the ClassName “Result
Set”. Also, be sure any GenRootElementType has its
SubElementName properly defined with the “Result Set”
ElementName.
Conversion from %s to %s not supported.
Description
The attempted data type conversion is not supported for
setting a parameter in a PreparedStatement.
User action
Check for proper data type usage. If you suspect this is an
OrdbXML issue, then please gather reproduction details and
contact Cincom Technical Support.
Conversion resulted in truncation of significant digits.
Description
A larger data type was attempted to be converted to a smaller
data type and would not fit. For example, a FLOAT value of
1,000,000 cannot be converted to a SMALLINT.
User action
Use larger data type where appropriate.
Messages and Codes, P25-9502-04
Chapter: 4. OrdbXML Java error messages
Section: OrdbXML Java error messages
241
Date/time value %s does not match format %s
Description
The value does not match the format defined in the options.
User action
Correct the DateTimeFormats pattern in the map options, or
correct the value.
Date/time value %s does not match specified format (or default format
if no format was specified).
Description
The value does not match the format defined in the options.
User action
Correct the DateTimeFormats pattern in the map options, or
correct the value.
Element in class map file is not supported in this version map: %s.
Description
The specified Element is not supported in the specified version
of the map. For example, obsolete version 1.0 elements are
not supported in version 2.0 and new version 2.0 elements are
not supported in version 1.0.
User action
Verify the map syntax is consistent and matches the version
specified with <ORDBXML Version="x.x">.
Element in class map file is out of order: %s.
Description
The specified Element is used in an improper order. For
example, an <AttributeMap> must be defined within the
definition of a <ClassMap>.
User action
Correct the order of the element definitions in the ClassMap
file.
Element type %s is referenced in element type %s but is never defined.
Description
The given Element is referenced as a child of this Element but
it is not defined.
User action
Add an Element definition to the DTD or remove the reference.
Element type %s mapped more than once.
Description
The map contains two ClassMaps for this element.
User action
Correct the map so that each element mapping definition has a
unique name.
Element type %s mapped more than once as a ChildMap or AttributeMap of
%s.
Description
A ClassMap contains two mappings for this element. These may
be ChildMaps or AttributeMaps.
User action
Correct the map.
Messages and Codes, P25-9502-04
Chapter: 4. OrdbXML Java error messages
Section: OrdbXML Java error messages
242
Element type %s was listed as a ChildMap but was never mapped.
Description
The Element is referenced in a ChildMap but no ClassMap exists
for the Element.
User action
Define a ClassMap for the element, or correct the ChildMap.
Element type %s was listed as a related class but was never mapped.
Description
A ClassMap defines this element in a ChildMap, but there is no
ClassMap for this element.
User action
Add a ClassMap for this element to the map, or correct the
ChildMap.
Enumerated values must be unique: %s
Description
Enumerated values defined in a DTD must be unique.
User action
Correct the DTD for the given value.
Inputsource does not have a character stream, byte stream, or system
ID.
Description
Cannot recognize the input source.
User action
Please validate that the input source is properly created.
Invalid argument(s) %s in %s
Description
An internal sanity check has failed.
User action
Please gather reproduction details and contact Cincom
Technical Support.
Messages and Codes, P25-9502-04
Chapter: 4. OrdbXML Java error messages
Section: OrdbXML Java error messages
243
Invalid attribute default: %s
Description
The specified attribute default is not valid for Attribute
declarations.
User action
Declare the attribute using one of the following:
♦
#REQUIRED
♦
#IMPLIED
♦
#FIXED
Invalid attribute type: %s
Description
The specified attribute type within <!ATTLIST is not a valid
attribute type.
User action
Declare the attribute using one of the following:
♦
♦
♦
♦
♦
CDATA
ID
IDREFS
ENTITY
♦
♦
♦
♦
NMTOKEN
NMTOKENS
NOTATION
[Enumerations, this is not a keyword]
ENTITIES
Invalid Boolean value: %s
Description
An invalid Boolean value was used for setting a String
parameter in a PreparedStatement.
User action
The accepted string forms of true are: “1”, “yes”, and “true”.
The accepted string forms of false are: “0”, “no”, and “false”.
All are case-insensitive.
Invalid character in encoding name: ‘%s’.
Description
The XML declaration contains an invalid encoding character
sequence.
User action
Specify a valid XML encoding.
Messages and Codes, P25-9502-04
Chapter: 4. OrdbXML Java error messages
Section: OrdbXML Java error messages
244
Invalid character in public identifier: ‘%s’.
Description
The public identifier specified within the <!DOCTYPE, and
preceded by PUBLIC, is not a valid Uniform Resource Identifier
(URI).
User action
Specify a valid URI.
Invalid character reference type: %s
Description
The specified character reference within &# is not valid.
User action
Please validate that the character reference is comprised of a
decimal or hexadecimal number, preceded by &# or &#x.
Invalid commit mode value: %s.
Description
User action
An attempt was made to set the commit mode to an invalid
value. Valid values are:
♦
COMMIT_AFTERINSERT
♦
COMMIT_AFTERDOCUMENT
♦
COMMIT_NONE
Be sure the application is using one of the above-predefined
symbols. These are defined in interface
OrdbXml.dom.DBDom.DBNode.
Invalid conditional section.
Description
A string that follows <
