R
E )> #40-> 57657(9054 !(*7(3,495 (20-5740( #! 22 70./98 7,8,7;,+ 7049,+ 04
9/, #409,+ !9(9,8 5- 3,70*(
5 6(79 5- 9/08 +5*:3,49 3(> ), 7,675+:*,+ 97(483099,+ 97(48*70),+ 8957,+ 04 ( 7,970,;(2 8>89,3 57
97(482(9,+ 0495 (4> 2(4.:(., 57 *536:9,7 2(4.:(., 04 (4> -573 57 )> (4> 3,(48 ,2,*97540* 3,*/(40*(2
3(.4,90* 5690*(2 */,30*(2 3(4:(2 57 59/,7<08, <09/5:9 9/, 67057 <7099,4 *548,49 5- #40-> 57657(9054
#40-> 57657(9054 3(1,8 45 7,67,8,49(90548 57 <(77(490,8 <09/ 7,86,*9 95 9/, *549,498 5- 9/08 +5*:3,49
(4+ 86,*0-0*(22> +08*2(038 (4> 03620,+ <(77(490,8 5- 3,7*/(49()0209> 57 -094,88 -57 (4> 6(790*:2(7 6:7658,
:79/,7 #40-> 57657(9054 7,8,7;,8 9/, 70./9 95 7,;08, 9/08 +5*:3,49 (4+ 95 3(1, */(4.,8 -753 903, 95
903, 04 098 *549,49 <09/5:9 ),04. 5)20.(9,+ 95 4590-> (4> 6,7854 5- 8:*/ 7,;080548 57 */(4.,8
"/, !5-9<(7, +,8*70),+ 04 9/08 +5*:3,49 08 -:7408/,+ :4+,7 ( !5-9<(7, 0*,48, .7,,3,49 "/, !5-9<(7,
3(> ), :8,+ 57 *560,+ 542> 04 (**57+(4*, <09/ 9/, 9,738 5- 9/, 20*,48, .7,,3,49 9 08 (.(0489 9/, 2(< 95
*56> 9/, !5-9<(7, 54 9(6, +081 57 (4> 59/,7 3,+0:3 -57 (4> 6:7658, 59/,7 9/(4 9/(9 +,8*70),+ 04 9/,
20*,48, (.7,,3,49
#40-> 57657(9054 ;(2:,8 (4+ (667,*0(9,8 (4> *533,498 >5: 3(> /(;, *54*,7404. 5:7 675+:*98 57 9/08
+5*:3,49 2,(8, (++7,88 *533,498 95
75+:*9 (4(.,7
#40-> 57657(9054
7,4( 5:2,;(7+ !9, !(*7(3,495 & #' $! (4+ 9/, #40-> 5.5 (7, 7,.089,7,+ 97(+,3(718 5- #40-> 57657(9054 #40->
(9(!,7;,7 08 ( 97(+,3(71 5- #40-> 57657(9054 #& 08 ( 7,.089,7,+ 97(+,3(71 5- 9/, 6,4 75:6 04
9/, #409,+ !9(9,8 (4+ 59/,7 *5:4970,8 "/, & %04+5< !>89,3 08 ( 675+:*9 5- 9/, (88(*/:8,998 48909:9, 5",*/4525.> 590- ! (4+ !590- (7, 97(+,3(718 5- 6,4 !5-9<(7, 5:4+(9054 4* !'! 08 (
7,.089,7,+ 97(+,3(71 (4+ ! !,7;,7 @0)7(7> (4+ 6,4 !,7;,7 (7, 97(+,3(718 5- !>)(8, 4*
& 08 ( 7,.089,7,+ 97(+,3(71 5- 4-5730= !5-9<(7, 4* ( 8:)80+0(7> 5- ! 08 (
97(+,3(71 5- 536:9,7 885*0(9,8 49,74(9054(2 4* 08 ( 7,.089,7,+ 97(+,3(71 5- 7(*2,
57657(9054 !:4 08 ( 7,.089,7,+ 97(+,3(71 (4+ !:4$0,< !:4@
!:4@ &,%! !:4! @! (4+
6,4 %04+5<8 (7, 97(+,3(718 5- !:4 0*758>89,38 22 ! 97(+,3(718 (7, 97(+,3(718 57 7,.089,7,+
97(+,3(718 5- ! 49,74(9054(2 4* ! 89(9054 08 20*,48,+ ,=*2:80;,2> 95 !:4 0*758>89,38 4*
5;,22 08 ( 7,.089,7,+ 97(+,3(71 5- 5;,22 4* (*04958/ 08 ( 97(+,3(71 5- 662, 536:9,7 4*
0*7585-9 ! !@! (4+ %04+5<8 (7, 7,.089,7,+ 97(+,3(718 5- 0*7585-9 57657(9054 22 59/,7
675+:*98 57 8,7;0*,8 3,49054,+ /,7,04 3(> ), 7,.089,7,+ 97(+,3(718 97(+,3(718 57 8,7;0*, 3(718 5- 9/,07
7,86,*90;, 3(4:-(*9:7,78 *536(40,8 57 57.(40?(90548
(79 :3),7 2
Contents
Error Message Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
3
4
Contents
About This Manual
This Unify DataServer: Error Messages manual lists the errors that can
be produced by the Unify DataServer RDBMS. It is intended to help you
quickly resolve the cause of error messages you may receive during the
design and use of a Unify DataServer database.
The body of this manual is the “Error Message Descriptions”. This “Error
Message Descriptiond” is made up of entries for each Unify DataServer
error message. Each entry is introduced with a header that contains the
error message number and text. This header has the format shown here:
–1521
Cannot drop PUBLIC schema.
The error message number is a number that represents the error message
text in the Unify DataServer message file, unify.msg. This error message
number appears in parentheses at the end of the error message text.
The unify.msg file should reside in the directory named by the UNIFY
configuration variable.
The error message text is the actual text of the message. It describes the
error condition. Items in the error message text that are italicized are
substitution points. When the error message is displayed, Unify
DataServer replaces the substitution points with actual string or numeric
values that apply to your error condition.
To use this manual, look up the error message number of your error
message in the “Error Message Descriptions.” Error messages with
positive error numbers are listed first, in ascending order. They are
followed by error messages with 0 and negative numbers. The negative
error codes are presented in ascending order of the numeric values. So for
example, error message -2 is listed before -3, which again precedes –4,
and so on.
5
Once you have found the entry for your error message in the “Error
Message Descriptions,” refer to the “Explanation” and “Correction”
sections. The “Explanation” section provides a more complete
description of the condition that caused the error message. The
Correction section describes how to resolve the error condition.
Some error message entries also have an “Additional Help” section that
refers to other manuals. If you follow the instructions in the “Correction”
and “Additional Help” sections and are still unable to resolve the error,
please call Customer Support for assistance. Make sure that you have the
error message number ready when you call.
6
+100
End of scan (or ordered access).
Explanation
Correction
0
The end of the select set of rows has been reached and there are no more
rows to be retrieved.
In RHLI, the scan can be restarted, or a new scan can be started. In
embedded SQL/A, the cursor can be reused.
No error occurred.
Explanation
–1
No error occurred during the operation.
Internal inconsistency – fatal.
Explanation
Correction
Additional Help
An abnormal condition has been detected in shared memory. For
instance, a numeric value that is always positive now has a negative
value.
Try shutting down the database and restarting, or running the irma utility.
Also, you can check for database corruption by using the dbchk utility.
Call Customer Support for assistance with the dbchk utility. This utility
is not documented in the Unify DataServer manual set.
–2
Not enough user memory space; try increasing ‘SHMOFFSET’.
Explanation
An attempt to allocate user memory failed because a related call to
malloc, calloc, or realloc failed. The process may have reached a
system-imposed limit.
Correction
Additional Help
Error Messages
Try reducing the values of the configuration variables that control the
size of process memory (INITMEM, SQLSMEM, SQLPMEM or TIMEM) or
increasing the value of the configuration variable that controls the shared
memory scanning offset, SHMOFFSET (remember that SHMOFFSET has
no effect if SHMKIND is 1).
Unify DataServer: Configuration Variable and Utility Reference
7
–3
Not enough shared memory; try increasing ‘SHMMAX’ or decreasing
‘SHMFULL’.
Explanation
Correction
An attempt to allocate a structure in shared memory failed because the
size of the shared memory segment was exceeded.
Try to determine which partition is full by using the –p option on the
shmmap command.
If the full partition is in
the:
Try these steps:
Transaction manager
Reduce the number of active transactions
Lock manager
Reduce the number of locks
Decrease the setting for the LMPROMO
variable
Commit transactions more frequently
File manager
Synchronize the database more often by
adjusting the FREQUENCY and FREQTYPE
variables
Reduce the number of pages modified between
synchronizations
If the error persists, try moving the overflowing segment into its own
shared memory area or increasing the associated shared memory
configuration variable (SHMMAX, TMSHMKEY, LMSHMKEY, FMSHMKEY,
CMSHMKEY).
Additional Help
8
Unify DataServer: Configuration Variable and Utility Reference
Error Messages
–4
The database appears to be corrupted (is the root volume really a
database?).
Explanation
A database file, such as a volume, physical log, B-tree index file, can be
read but the file header does not indicate that the file is a Unify
DataServer database file.
Correction
Use file * in the database directory (DBPATH) to determine which file is
corrupted. For this command to be effective, the magic file must be
correctly installed in the /etc directory of your release.
Additional Help
–5
Unify DataServer: Configuration Variable and Utility Reference
Your operating system documentation
This feature is not implemented yet.
Explanation
Correction
Additional Help
–6
A feature is not yet supported or implemented.
Check the availability of RHLI features in the RHLI documentation.
Unify DataServer: RHLI Reference
The software version does not match the database version.
Explanation
Correction
–7
The version number in the header of a database file does not match the
version number expected by the database software.
Convert the database to the new version.
An invalid memory address was supplied as a parameter to an RHLI
function.
Explanation
Correction
Additional Help
Error Messages
An RHLI function was called with an invalid memory pointer.
Verify the parameters passed to the RHLI function. Check the placement
of pointer references.
Unify DataServer: RHLI Reference
9
–8
Partial success; see the individual status list.
Explanation
Correction
Additional Help
–9
One or more errors occurred on multi–valued parameter; the actual errors
are contained in the status list which was passed to the function.
Examine the RHLI function’s status list to determine the actual errors.
Check for the correct number of parameters.
Unify DataServer: RHLI Reference
Invalid argument/options.
Explanation
Correction
Additional Help
–10
An RHLI function received an invalid argument or option.
Verify the parameters passed to the RHLI function.
Unify DataServer: RHLI Reference
Valid, but no work was done.
Explanation
A list element in an RHLI status list was valid but that no action was
taken due to an error in another element of the list. This error is usually
accompanied by another error in the status list.
Correction
Check the status list errors. Find the RHLI function causing the error and
correct the offending list element.
Additional Help
–11
Unify DataServer: RHLI Reference
An interrupt has occurred.
Explanation
Correction
Additional Help
10
This error is returned by most RHLI functions after an interrupt is set by
the default Unify DataServer signal handler or by the function usetitr.
Use the uclritr function to resume processing after the interrupt.
Unify DataServer: RHLI Reference
Error Messages
–12
Database file type mismatch – possibly not a database file?
Explanation
Correction
A database file, such as a volume, physical log, or B-tree index file is not
the type of file expected. For example, when attempting to open the log
file, the file header indicates that the file is actually a database volume.
Check the location of all files and verify file names and paths in related
configuration parameters. Use the file * command to check for corrupt
files.
If the database files are Unix files, try using the fsck command to check
the file system.
You may need to recover your database from a backup version.
Additional Help
–13
Unify DataServer: Configuration Variable and Utility Reference
Your operating system documentation
Database file ID mismatch – possibly wrong database version?
Explanation
The database file opened does not have the expected file ID. For
example, the file which should contain volume two of the database does
not have an ID of two in the file header.
Correction
Use the file * command to identify which file is incorrect. For this
command to be effective, the magic file must be correctly installed in the
/etc directory of your release.
Additional Help
–14
Unify DataServer Installation documentation.
The ‘$UNIFY’ configuration variable is not defined.
Explanation
Correction
Additional Help
Error Messages
The UNIFY configuration variable must be defined so that the database
system can locate the message files and the default configuration file.
Set the UNIFY configuration variable to the path name of the lib directory
in the installed Unify DataServer release.
Unify DataServer: Configuration Variable and Utility Reference
11
–15
Invalid error code.
Explanation
Correction
Additional Help
–16
An attempt has been made by the RHLI function ufchmsg to fetch an
error message using an invalid error code.
Verify the error code used with the ufchmsg function.
The rhlierr.h file in the include directory of your release.
The ‘$UNIFY’ directory does not exist or is not accessible.
Explanation
Correction
The database system is not able to access the directory indicated by the
UNIFY configuration variable.
Verify the value of the UNIFY variable. Make sure that read access is
allowed on the $UNIFY directory.
Additional Help
Unify DataServer: Configuration Variable and Utility Reference
–17
The ‘$UNIFY/unify.msg’ message file does not exist or is not
accessible.
Explanation
Correction
Additional Help
–18
The database system is unable to open the message file, unify.msg.
Verify that the UNIFY variable is set to the lib directory of the release.
Make sure that read access is allowed on the directory and the message
file, $UNIFY/unify.msg.
Unify DataServer Installation documentation.
Process terminated at user request (typically using ‘shutdb’ utility).
Explanation
Correction
12
When two or more processes are accessing the database, one of them
might be running a process which forces the database to shut down, while
others are still trying to access the database. The latter processes will get
this error.
None.
Error Messages
–21
Not owner.
Explanation
You have attempted to access a file that you do not own. Check the errlog
file to see if the file name is listed there.
Correction
Correct the access permissions of the file. Also, check the error message
documentation for error number 1 in your Unix system documentation.
–22
No such file, directory, or program.
Explanation
Correction
–23
This error occurs when a file name is specified and the file does not exist,
or when one of the directories in a path name does not exist.
Check the errlog file to determine which file could not be found. Also,
check the error message documentation for error number 2 in your Unix
system documentation.
There is no process with the specified process ID.
Explanation
Correction
–24
A process has abnormally terminated.
Check the errlog file for information. Search for any core files.
Interrupted system call.
Explanation
Correction
–25
A system call was interrupted.
This is an internal error and should not occur during normal operations.
Call Customer Support if this error occurs.
I/O error.
Explanation
Correction
Error Messages
An I/O error has occurred.
Since it is usually a hardware problem, user must resolve the situation
independent of the database, usually.
13
–26
No such device or address.
Explanation
This is an internal error only and should not occur.
Correction
If this error occurs, please call Customer Support.
–27
The argument list is too long (Consult operating system manual for
limit).
Explanation
This is an internal error and should not occur in the normal execution of
the database.
Correction
Check the error message documentation for error number 7 in your Unix
system documentation.
–28
Exec format error.
Explanation
This is an internal error and should not occur in the normal execution of
the database.
Correction
Check the error message documentation for error number 8 in your Unix
system documentation.
–29
Bad file descriptor.
Explanation
This is an internal error and should not occur in the normal execution of
the database.
Correction
Check the error message documentation for error number 9 in your Unix
system documentation.
–30
No children.
Explanation
Correction
14
This is an internal error and should not occur in the normal execution of
the database.
Check the error message documentation for error number 10 in your
Unix system documentation.
Error Messages
–31
No more processes.
Explanation
Correction
–32
This is an internal error and should not occur in the normal execution of
the database.
Check the error message documentation for error number 11 in your Unix
system documentation.
Not enough memory; try increasing ‘SHMOFFSET’.
Explanation
Correction
Additional Help
–33
An attempt to allocate user memory failed because a related call to
malloc, calloc, or realloc failed.
Try reducing the values of the configuration parameters that control the
size of process memory (INITMEM, SQLSMEM, SQLPMEM or TIMEM) or
increasing the value of the configuration parameter that controls the
shared memory scanning offset, SHMOFFSET (remember that
SHMOFFSET has no effect if SHMKIND is 1).
Unify DataServer: Configuration Variable and Utility Reference
Access permission denied on file.
Explanation
An attempt has been made to open a file or shared memory in a mode not
allowed by the permissions on the file.
Correction
Check the errlog file to determine which file could not be accessed.
Also, check the error message documentation for error number 13 in your
Unix system documentation.
–34
Bad operating system call address.
Explanation
Correction
Error Messages
This is an internal error and should not occur in the normal execution of
the database.
Check the error message documentation for error number 14 in your
Unix system documentation.
15
–35
Block device required.
Explanation
Correction
–36
This is an internal error and should not occur in the normal execution of
the database.
Check the error message documentation for error number 15 in your
Unix system documentation.
Object busy.
Explanation
Correction
–37
Some internal resource is being used.
Check the error message documentation for error number 16 in your
Unix system documentation.
File already exists.
Explanation
Correction
–38
This is an internal error and should not occur in the normal execution of
the database.
Check the error message documentation for error number 17 in your
Unix system documentation.
Cross-device link.
Explanation
Correction
–39
This is an internal error and should not occur in the normal execution of
the database.
Check the error message documentation for error number 18 in your
Unix system documentation.
No such device.
Explanation
Correction
16
This is an internal error and should not occur in the normal execution of
the database.
Check the error message documentation for error number 19 in your
Unix system documentation.
Error Messages
–40
Not a directory.
Explanation
Correction
–41
A non-directory name was specified where a directory name was
required, such as for the configuration variables DBPATH or UNIFY.
Check the errlog file to determine which file caused the error. Also,
check the error message documentation for error number 20 in your Unix
system documentation.
Object is a directory.
Explanation
Correction
–42
An attempt has been made to open a directory as a file.
Check the errlog file to determine which file caused the error. Also,
check the error message documentation for error number 21 in your Unix
system documentation.
Invalid OS function argument.
Explanation
Correction
–43
This is an internal error and should not occur in the normal execution of
the database.
Check the error message documentation for error number 22 in your
Unix system documentation.
File table overflow.
Explanation
Correction
Error Messages
The system file table is full, and temporarily no more files can be opened.
Reconfigure the operating system to support more open files or reduce
the number of open files. Also, check the error message documentation
for error number 23 in your Unix system documentation.
17
–44
Too many file descriptors open (> operating system limit?) This
sometimes indicates a problem attaching shared memory segments.
Explanation
Correction
–45
An attempt has been made to open more files than are allowed by the
operating system for each process.
Reconfigure the operating system to support more open files per process
or reduce the number of open files. Also, check the error message
documentation for error number 24 in your Unix system documentation.
Not a typewriter.
Explanation
Correction
–46
This is an internal error and should not occur in the normal execution of
the database.
Check the error message documentation for error number 25 in your
Unix system documentation.
Text file busy.
Explanation
Correction
–47
This is an internal error and should not occur in the normal execution of
the database.
Check the error message documentation for error number 26 in your
Unix system documentation.
File too large.
Explanation
Correction
18
An attempt has been made to make a file larger than the system imposed
maximum. This is an internal error and should not occur in the normal
execution of the database.
Check the error message documentation for error number 27 in your
Unix system documentation.
Error Messages
–48
No space left on device.
Explanation
Correction
–49
No free space remains on the device in which to write an ordinary file.
This is an internal error and should not occur in the normal execution of
the database.
Check the error message documentation for error number 28 in your
Unix system documentation.
Illegal seek.
Explanation
Correction
–50
This is an internal error and should not occur in the normal execution of
the database.
Check the error message documentation for error number 29 in your
Unix system documentation.
Read-only file system.
Explanation
Correction
–51
An attempt has been made to modify a file or directory on a device
mounted as read-only.
Check the errlog file to determine which file caused the error. Also,
check the error message documentation for error number 30 in your Unix
system documentation.
Too many links.
Explanation
Correction
–52
This is an internal error and should not occur in the normal execution of
the database.
Check the error message documentation for error number 31 in your
Unix system documentation.
Broken pipe.
Explanation
Correction
Error Messages
This is an internal error and should not occur in the normal execution of
the database.
Check the error message documentation for error number 32 in your
Unix system documentation.
19
–53
Generic operating system error.
Explanation
Correction
–54
An operating system error has occurred that cannot be mapped to a
standard RHLI error.
Try to determine the statement of statements causing the error. Examine
the error that occurred just after this one, if any.
Not enough resources.
Explanation
Correction
Your application has run out of stream file descriptors.
Try to reserve lower-numbered file descriptors for the functions that need
them.
If possible, set SCHEMA to FALSE to turn off schema merging.
Additional Help
–55
Unify DataServer: Configuration Variable and Utility Reference
End-of-file reached.
Explanation
An attempt has been made to read past the end of a database file. A file
may have been truncated.
Correction
By using the ls –l command, check that the current size of the .db file is
the expected size. Also, check for zero-length files.
Additional Help
–56
Your operating system documentation.
Partial read/write encountered.
Explanation
Correction
20
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Error Messages
–57
The software version does not match the shared memory partition
version.
Explanation
Correction
Additional Help
–58
The software version that created the shared memory was not the same
version as the current software.
Make sure you are using the correct release of database software. You
can check the release of the current software with the –version option of
a database executable. This option should list out the partition numbers
that the software expects. Use the shmmap utility to list the current
partition version numbers.
Unify DataServer: Configuration Variable and Utility Reference
The software version does not match the shared memory segment
version.
Explanation
Correction
Additional Help
–59
The software version that created the shared memory was not the same
version as the current software or the shared memory segment is not a
Unify DataServer shared memory segment.
Make sure that the shared memory segment being used is a Unify
DataServer shared memory segment. If not, you probably need to change
the shared memory key, SHMKEY, to a value unique to this software.
Unify DataServer: Configuration Variable and Utility Reference
Could not attach shared memory at required address.
Explanation
Correction
Additional Help
Error Messages
Shared memory could not be attached at the required address. The
required attach address would probably overlap the data space of the
process. This problem is usually caused by starting the database with a
small program, such as shmmap, and later attempting to open the
database with a much larger program, such as SQL or startdb.
Shut down the database and either increase the value of the SHMOFFSET
configuration parameter or restart the database using the larger program.
Unify DataServer: Configuration Variable and Utility Reference
21
–60
The shared memory segment is already attached.
Explanation
Correction
–61
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Could not create shared memory – incorrect SHMKEY value?
Explanation
Correction
–62
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Could not create a shared memory segment >= SHMMIN and <=
SHMMAX.
Explanation
Correction
The database system was unable to create a shared memory segment with
a size greater than or equal to the SHMMIN configuration parameter
setting due to some operating system limitation or because SHMMIN is
greater than the SHMMAX configuration parameter.
Try to make more shared memory available by reducing the size of
SHMMIN, reconfiguring the operating system, or reducing shared memory
usage by other databases.
Additional Help
–63
Unify DataServer: Configuration Variable and Utility Reference
File synchronization failed.
Explanation
Correction
22
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Error Messages
–64
A process has abnormally terminated while updating shared
memory; database recovery using the ‘irma’ utility is now necessary.
Explanation
Correction
Additional Help
–65
This error occurs when a database program detects that another process
has terminated while holding a shared memory critical section lock.
Since the process terminated while updating shared memory, the database
program assumes that shared memory is now corrupt.
Recover the database by using the irma utility.
Unify DataServer: Configuration Variable and Utility Reference
Cannot open or create the shared memory lock file
($SHMDIR/shmlk#####).
Explanation
Correction
Additional Help
–66
The shared memory lock file, used to control access to shared memory,
could not be created. Only versions of Unify DataServer that use
disk-based locking create this file.
Make sure the SHMDIR configuration variable is set correctly. Make sure
the directory indicated by SHMDIR has appropriate permissions.
Unify DataServer: Configuration Variable and Utility Reference
Specified processor ID does not exist.
Explanation
Correction
–67
The processor specified in the PROCESSOR configuration variable does
not exist.
Set PROCESSOR to a valid processor ID.
Process is running on the wrong processor ID.
Explanation
Correction
Error Messages
A process called uopndb while running on the wrong processor.
See information on migrate in Unify DataServer: Configuration Variable
and Utility Reference.
23
–70
Executable is not licensed.
Explanation
Correction
–71
The executable has not been properly licensed.
License the executable using the instlic utility. See the Unify/Net
Installation instructions for details on licensing executables.
Executable license has expired.
Explanation
Correction
–72
Your license for this executable has expired.
Contact Customer Support to renew your license.
Unable to determine current time.
Explanation
Correction
–73
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Executable is not licensed for this machine.
Explanation
Correction
–74
An attempt was made to run an executable on a machine for which it was
not licensed.
Check your command name and PATH configuration variable to make
sure you are running the correct version of the software. Call Customer
Support to resolve the problem.
File seek error.
Explanation
Correction
24
An attempt has been made to perform a file seek operation on a file that
is not seekable or has an invalid specified seek address. This is an
internal error and should not occur in the normal execution of the
database.
If this error occurs, please call Customer Support.
Error Messages
–75
Unable to install license.
Explanation
Correction
–76
The license cannot be installed in the executable.
Make sure that the license is being installed in the correct executable.
License installation error.
Explanation
Correction
–77
The license has been incorrectly installed. This is an internal error and
should not occur in the normal execution of the database.
If this error occurs, please call Customer Support.
Database Server unable to respond; too many users.
Explanation
The remote database cannot be opened because the Database Server is
already servicing its licensed maximum number of users.
Correction
Verify all existing users. If all users are valid, try to open the database
later. Use the operating system utilities to remotely log into the server
machine and perform the operation as a local user. Contact Customer
Support to increase your license.
–78
Invalid date.
Explanation
Correction
–81
The input date value is invalid.
Make sure that the specified value is in correct format and range.
No messages in specified range (user changed message file
incorrectly?).
Explanation
Correction
Error Messages
This error occurs when a Unify DataServer utility attempts to retrieve a
set of messages from the message file, unify.cmf, and the desired
messages do not exist.
Make sure that the UNIFY configuration variable is set to the lib directory
of the release and that the file unify.cmf exists with the correct
permissions in the $UNIFY directory.
25
–100
Additional Help
–101
End of scan (or ordered access).
UEEOSCN
See error message +100.
Bad column count (exceeds maximum column limit).
Explanation
Correction
–102
The specified number of columns in a column group must be greater than
0 and less than 9.
Correct the number of component columns.
Invalid or conflicting options.
Explanation
The options specified for the RHLI function are invalid or contain
conflicting values.
Correction
Verify the options of the function.
Additional Help
Unify DataServer: RHLI Reference
–103
Invalid segment size specified.
Explanation
Correction
–104
The specified table segment size is less than 1 byte or greater than the
largest possible segment size for the host machine. The value in the
SHMMIN configuration parameter may be too large.
Choose a more reasonable segment size, or specify the value 0 to specify
no segment size. When choosing a segment size, be sure to specify the
size in bytes.
Invalid volume ID.
Explanation
Correction
Additional Help
26
The specified Volume ID does not exist in the database.
Check the Volume ID using the volume statistics utility volstats. The root
volume should have a Volume ID of “1”.
Unify DataServer: Configuration Variable and Utility Reference
Error Messages
–105
File may not be block-special file.
Explanation
Correction
–106
The specified file is a block-special device, which is invalid for the
operation.
Use a character-special device for files such as the physical log file and
the transaction log file.
No direct table key column specified.
Explanation
Correction
–107
No primary key column was specified for a table designated as being a
direct table.
Designate one of the columns in the table as the table’s primary key
column. The alternative is to make the table non-direct.
Invalid column type for direct table (must be type INTEGER
[U_HINT]).
Explanation
Correction
–108
An attempt has been made to define the primary key for a direct table
using a column type other than U_HINT or INTEGER.
A direct table requires that the primary key column be of type U_HINT.
In SQL/A, use the SQL type INTEGER. In RHLI, use the type U_HINT.
Transaction-log is not a file (directory or pipe?).
Explanation
An attempt has been made to reference a database transaction log file (.lg
suffix) that is not a Unix regular file, or a block-special or
character-special device.
Correction
Make sure the database transaction log file specified by the configuration
parameter LOGFILE specifies either a Unix regular file or a block-special
or character-special device. The transaction log cannot be a directory,
named pipe, or non-seekable device, such as a magnetic tape device.
Error Messages
27
–109
Transaction-log size is too small (should be at least MAXSYSTX
blocks).
Explanation
The size of the database transaction log file (.lg suffix), as specified by
the LOGBLK configuration parameter, is smaller than the minimum
required size.
Correction
The database transaction log file size is specified in number of blocks.
The transaction log must have at least as many blocks as the maximum
concurrent transactions specified by the MAXSYSTX configuration
parameter.
–110
Too many primary key columns specified.
Explanation
An attempt has been made to specify more than one primary key column
or column group for a table.
Correction
A table may only have one primary key. The table’s current primary key
can be obtained from the operating system shell using the schlst utility,
or from the RHLI using the uinftbl function.
–111
Exceeded maximum B-tree key length.
Explanation
Correction
–112
An attempt has been made to specify a B-tree index whose combined
length exceeds the maximum allowable index size.
The maximum B-tree index size differs for each type of hardware. Try to
reduce the size of the B-tree index by reducing the number of component
columns, or by decreasing the size of any character or U_STR columns.
No column group information specified.
Explanation
Correction
28
An attempt has been made to reference a column group explicitly.
Use the column group’s component columns instead.
Error Messages
–113
Invalid database ID.
Explanation
Correction
–114
An attempt has been made to reference a Database ID that does not
correspond to an open database.
Make sure the Database ID is the one returned from the RHLI uopndb
function. Make sure the RHLI uopndb function has returned the
USUCCESS status.
Invalid direction specification.
Explanation
Correction
–115
An invalid direction parameter was specified. The valid direction
parameters are: UFIRST, ULAST, UNEXT, and UPREV. These parameters
are located in the RHLI header file rhli.h.
Make sure you specified a valid direction parameter and that you have
only specified a single direction parameter.
No database information specified.
Explanation
Correction
–116
An attempt has been made to create a database without specifying any
database information. The DBINFO structure passed to the RHLI uadddb
function is a zero pointer.
Make sure the DBINFO data structure is correctly initialized.
Invalid link ID.
Explanation
Correction
Error Messages
An attempt has been made to reference a non-existent Link ID.
Make sure the Link ID was obtained using runtime name binding or
retrieved using the uinflnk RHLI function.
29
–117
No volume preference found.
Explanation
Correction
Additional Help
–118
An attempt has been made to drop a non-existent volume preference from
a table.
Make sure that the volume ID representing the volume preference does
exist. You can use the uinfvol RHLI function to perform this validation.
Unify DataServer: RHLI Reference
No user information specified.
Explanation
Correction
–119
An attempt has been made to reference a zero-length list of users.
Make sure the count of the number of user entries in the user information
list accurately reflects the actual user count.
No volume information specified.
Explanation
Correction
–120
An attempt has been made to reference zero-length volume information.
Make sure the count of the number of volume entries in the volume
information list accurately reflects the actual volume count.
Column cannot be combination to itself.
Explanation
An attempt has been made to define a column group with a component
column member that is also a column group.
Correction
Make sure the component members of a column group do not reference
other column groups.
–121
Schema has been modified – cannot open database.
30
Explanation
One or more of the tables or columns referenced in uld were modified in
some manner. Creating an access method does not count as a
modification. This message only appears if the database is not using ID
mapping.
Correction
Either relink the executable with uld or use ID mapping on the database.
Error Messages
–122
Beginning-of-set reached.
Explanation
Correction
–123
An attempt has been made to reference a row before the first row in a
selected set. The beginning of the selected set of rows has been reached
— there are no more rows to be retrieved.
In RHLI, the scan can be restarted, or a new scan can be started. In
embedded SQL/A, the cursor can be reused.
End-of-set reached.
Explanation
Correction
–124
An attempt has been made to reference a row after the last row in a
selected set. The end of the selected set of rows has been reached —
there are no more rows to be retrieved.
In RHLI, the scan can be restarted, or a new scan can be started. In
embedded SQL/A, the cursor can be reused.
Volume appears to be active or in use.
Explanation
An attempt has been made to add a volume whose physical device file is
already in use on a database, not necessarily the database to which the
volume is being added.
Correction
The volume status can be examined using the Unix file utility, if the
identification information has been installed. For more information on
installing the file identification information, see the product installation
instructions. Volumes residing on block-special or character-special
devices cannot be reused unless they have been properly dropped and a
subsequent file system synchronization has occurred. Until the
synchronization occurs, a deleted volume is considered in use but not
accessible.
–125
Bad volume pre-allocate option (length).
Error Messages
Correction
An attempt has been made to specify the preallocated option for a volume
whose length is zero, or the forced option for a volume whose type is
device.
Correction
Correct the volume specifications.
31
–126
Bad volume group ID.
Explanation
An attempt has been made to specify a negative value for a Unix group
ID.
Correction
For information on how to specify Unix group IDs, see your operating
system manuals.
–127
Bad volume length.
Explanation
Correction
Additional Help
–128
An attempt has been made to specify one of the following: a volume
length that is too short to fix database headers, a negative value for the
volume length of a UNIX regular file, or zero for a block-special or
character-special device.
Correct the volume length specifications. The length of the volume must
be greater than or equal to zero.
“Creating and Removing Database Objects” in Unify DataServer: Writing
Interactive SQL/A Queries.
Bad volume access mode (0777).
Explanation
Correction
Additional Help
–129
An attempt has been made to specify a Unix file access mode that does
not fit the bit pattern 0777 (octal).
Correct the file mode.
Your operating system documentation.
Bad volume offset.
Explanation
Correction
32
An attempt has been made to specify a volume offset when the volume is
the root volume or the volume is a regular Unix file.
Volume offsets can only be used volumes whose type is device.
Error Messages
–130
Bad volume options.
Explanation
An attempt has been made to specify an invalid volume option.
Correction
Verify the options on the volume creation statement or function.
–131
Bad volume owner ID.
Explanation
Correction
–132
An attempt has been made to specify a negative value for a Unix user ID.
For further information on how to specify Unix user IDs, see your
operating system manuals.
Bad volume page size.
Explanation
Correction
–133
An attempt has been made to specify an invalid size for a volume file.
Verify the size option you specified on the volume creation statement or
function.
Bad volume device type.
Explanation
An attempt has been made to specify a volume file type that does not
correspond to the actual file type. The volume file was specified as being
a device when the volume file is actually a Unix regular file, or the file
was specified as being a Unix regular file when the volume file is
actually a device.
Correction
Make sure that the file type specified for the volume and the file type for
the actual file match.
–134
There are orphan rows in the child table.
Explanation
Correction
Error Messages
An attempt has been made to add a link index. A link index cannot be
added because there are rows in the child table that cannot reference a
corresponding parent row.
Identify the orphan rows in the child table and either delete them, change
the referencing columns to the value of an existing parent, or insert a new
parent with the orphan’s values.
33
–135
Invalid buffer index (file too small).
Explanation
An attempt has been made to specify a text/binary buffer index that is
invalid, according to other information in the text/binary descriptor
structure. For instance, this error can occur if the input buffer is a file and
the text/binary descriptor structure indicates that m bytes are to be read,
starting at the nth byte in the file, when file size is smaller than n + m
bytes.
Correction
Check the indicated text/binary descriptor structure for accuracy. Specify
a smaller index or fewer number of bytes.
–136
An invalid expected number of rows was supplied.
Explanation
An attempt has been made to specify a negative value as the expected
number of rows for a table.
Correction
The expected number of rows for a table must be a positive number or
“0” when the expected number of records is unknown.
–137
The supplied index into a variable length data value is past the end of
the actual value.
Explanation
Correction
–138
An attempt has been made to specify an offset into a column’s text or
binary data buffer that exceeds the size of the data.
Specify a smaller index to be retrieved or written.
Unknown TEXT/BINARY update mode.
Explanation
Correction
34
An attempt has been made to specify a text or binary operation mode that
is invalid.
Verify the operation.
Error Messages
–139
Scan (or ordered access) ID is not found (Has the scan been closed?).
Explanation
An attempt has been made to reference a Scan ID that does not exist.
Correction
Make sure the Scan ID was returned from a successful RHLI ubegscn
function call. Also make sure this scan was not closed with the RHLI
uendscn function call.
–140
Column type mismatch.
Explanation
Correction
–141
An attempt has been made to reference an index using columns that do
not match the columns used to create the index.
Make sure the Column IDs match the Column IDs used to create the
index. Make sure the Column IDs do not reference a column group.
Unable to back out operation – fatal.
Explanation
Correction
–142
The database system detected an internal, non-recoverable error while
trying to back out a failed operation. See the errlog file for an entry
describing the cause of the error.
Recover the database using the irma utility.
Fatal error in B-tree access; rebuild.
Explanation
Correction
–143
An internal error was detected while scanning a B-tree index. This is an
internal error and should not occur in the normal execution of the
database.
If this error occurs, please call Customer Support.
Error opening B-tree.
Explanation
Correction
Error Messages
The system was unable to open a B-tree index file.
Make sure the B-tree index file (.idx suffix) has not been removed. If the
B-tree index file exists and you still receive this error, please call
Customer Support.
35
–144
Combination group not allowed.
Explanation
An attempt has been made to reference a Column Group ID, instead of
the component members’ Column IDs. In most RHLI functions, the
Column Group ID may not be referenced.
Correction
Use the Column IDs for the member columns in the column group.
–145
Expected a column group, but columns are not members of any
column group.
Explanation
An attempt has been made to reference a column group, but the specified
Column IDs do not belong to any known column group. This error occurs
when trying to retrieve rows based on an index key.
Correction
Make sure the Column IDs are in the same sequence as those used to
create the index. Make sure the number of columns specified matches the
number specified when the index was created.
–146
Invalid column length.
Explanation
Correction
–147
An attempt has been made to specify an invalid column length or an
invalid column display precision and scale.
Make sure the internal column length corresponds to the limits of the data
type. Verify the column’s precision and scale.
Invalid column type.
Explanation
Correction
36
An attempt has been made to specify a data type that is invalid for a
particular operation.
Verify the data types available to you and the restrictions associated with
each data type.
Error Messages
–148
Data value conversion error.
Explanation
An attempt has been made to perform a an invalid data conversion. This
error occurs when the data to be converted does not conform to the
constraints for the column’s data type. For instance, the date 88/88/88
would produce this error because the month “88” is invalid.
Correction
Make sure the data to be converted conforms to the column’s data type
restrictions.
–149
Database is closed; attempt to access database which is not open.
Explanation
Correction
–150
An attempt has been made to access a database that has not yet been
opened or that has since been closed.
Perform the operation after the database has been opened and before the
database has been closed. Make sure the open database operation
succeeded before attempting other database activities.
The column data type internal length is larger than maximum
length.
Explanation
Correction
–151
An attempt has been made to specify an internal column data type length
that is larger than the maximum allowable data length.
Check the restrictions for the data types you are using.
Database already opened.
Explanation
Correction
Error Messages
An attempt has been made to open, or create with the “overwrite” option,
a database that is already opened by the process.
A database may only be opened once. The database must be closed
before it may be reopened or recreated. A database can be reopened as
many times as desired as long as the database is subsequently closed.
37
–152
Unknown column type.
Explanation
Correction
Additional Help
An attempt has been made to reference a column data type that is invalid.
Verify the data types available to you.
“Working With the Data Types and Null Values” in Unify DataServer:
RHLI Reference
–153
Invalid description length (too long).
Explanation
Correction
–154
An attempt has been made to specify a description that is longer than the
maximum size description.
Shorten the description. Be sure to enclose the description in quotes.
Duplicate column in column group list.
Explanation
An attempt has been made to create a column group have component
member columns with duplicate Column IDs.
Correction
Make sure the number of component member column IDs is correct so
that invalid memory is not inadvertently referenced.
–155
Attempt to store duplicate value in unique column.
Explanation
Correction
Additional Help
38
An attempt has been made to insert or update a unique column with data
that matches data in an existing unique column. If a column group
generates this error, the error applies to all component member columns
in the column group. This error can occur for both primary keys and
non-primary keys, since primary keys require a uniqueness constraint.
Insert or update unique data. An alternative would be to evaluate the
uniqueness constraint placed on the columns to determine if the
uniqueness constraint is accurate or necessary.
Unify DataServer: RHLI Reference or Unify DataServer: Writing
Interactive SQL/A Queries
Error Messages
–156
Duplicate table ID.
Explanation
Correction
–157
An attempt has been made to create a link between the same table. Links
must exist between two different tables.
Correct the link.
Invalid database name syntax.
Explanation
Correction
–158
The database name string contains a format error.
Verify that the correct separator characters are used and that all necessary
separator characters are present.
Failed to create error log name.
Explanation
Correction
–159
An attempt to create the errlog file failed. The database system requires
the errlog file.
Check that the directory specified by DBPATH has write permission. If
this error occurs, please call Customer Support.
Failed to open error log file.
Explanation
Correction
–160
An attempt to open the errlog file failed. The database system requires
the errlog file.
If this error occurs, please call Customer Support.
Denied access to file.
Explanation
Correction
Error Messages
An attempt has been made to access a database file for which the process
does not have access permission. This is an internal error and should not
occur in the normal execution of the database.
If this error occurs, please call Customer Support.
39
–161
Failed to close a file.
Explanation
Correction
–162
An attempt has been made to close a file that is already closed. This is an
internal error and should not occur in the normal execution of the
database.
If this error occurs, please call Customer Support.
File create error.
Explanation
Correction
–163
An attempt has been made to create a volume file which already exists.
If you still want to create a new volume file, remove or move the file that
currently exists before creating the volume.
File read error.
Explanation
Correction
–164
An attempt has been made to read a file that is not readable, or to read
past the end of file. This is an internal error and should not occur in the
normal execution of the database.
If this error occurs, please call Customer Support.
File seek error.
Explanation
Correction
–165
An attempt has been made to perform a file seek operation on a file that
is not seekable, or with an invalid specified seek address. This is an
internal error and should not occur in the normal execution of the
database.
If this error occurs, please call Customer Support.
File write error.
Explanation
Correction
40
An attempt has been made to write a file that is not writable, or to write
when there is no more available disk space. This is an internal error and
should not occur in the normal execution of the database.
If this error occurs, please call Customer Support.
Error Messages
–166
Tried to free a nil UNIPCOLL structure pointer.
Explanation
Correction
–167
An attempt has been made to free a nil pointer to a UNIPCOLL structure.
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Operation not allowed on tables with data.
Explanation
Correction
–168
An attempt has been made to perform an operation that cannot be
performed on a table that has data in it.
Remove the data before performing the operation.
Bad hash table options (only “unique” hash tables supported
currently).
Explanation
An attempt has been made to specify hash table creation options that are
not valid or that conflict with other options. Currently, only unique hash
tables are supported.
Correction
Specify the hash table as being UNIQUE, or use a duplicates B-tree index
instead. Validate that none of the hash table creation options conflict with
one another.
–169
Illegal argument.
Explanation
Correction
–170
An attempt has been made to specify an option that is invalid or conflicts
with another specified option. This is an internal error and should not
occur in the normal execution of the database.
If this error occurs, please call Customer Support.
Invalid menu-line position (must be >= 1).
Explanation
Correction
Error Messages
An attempt has been made to specify a menu line item whose menu line
position is less than “1”.
All menu line items must be positioned starting at line 1.
41
–171
Link already exists on child column.
Explanation
Correction
–172
An attempt has been made to add a link to a child column that already
has a link. A column may only be the child column of one link.
Remove the existing link before attempting to add the new link.
Invalid list size specified; verify the ‘count’ parameter.
Explanation
An attempt has been made to call an RHLI function with a list size that is
less than or equal to zero. All RHLI functions that accept lists need at
least one item in the list.
Correction
Make sure the parameters to the RHLI function are correct. On some
machines, an invalid parameter can be masked as another error due to the
method in which parameters are passed to functions.
–173
Menu-lines already exist.
Explanation
An attempt has been made to delete a menu which still has menu line
items attached to it; all line items must be dropped before the menu may
be deleted.
Correction
Drop the menu line items before attempting the menu delete operation.
–174
An attempt has been made to create a btree index with too many
component columns.
Explanation
Correction
42
An attempt has been made to specify a B-tree index column list that
exceeded the maximum number of columns for a B-tree key. This is an
internal error and should not occur in the normal execution of the
database.
If this error occurs, please call Customer Support.
Error Messages
–175
Too many scans (and/or ordered accesses) active at once.
Explanation
Correction
Additional Help
–176
An attempt has been made to start a scan which would exceeds the
maximum number of simultaneous scans permitted per process.
Make sure scans are properly closed using the RHLI uendscn function.
Unify DataServer: RHLI Reference
Database Object Name is required.
Explanation
An attempt has been made to add or modify an object which requires a
name, and the specified name was either a nil pointer or pointed to an
empty string.
Correction
Make sure the data structure for the operation was properly initialized.
All object names require non-null strings.
–177
The ‘not null’ column attribute is required for unique columns.
Explanation
Correction
–178
An attempt has been made to specify a column as being UNIQUE without
also specifying that the column is NOT NULL. This error also applies to
the creation of a unique column group, when one or more of the
component member columns does not have NOT NULL specified.
Before attempting to add the uniqueness constraint, make sure all
columns having the uniqueness constraint applied to them also have the
NOT NULL attribute.
Invalid B-tree ID.
Explanation
Correction
Error Messages
An attempt has been made to reference a B-tree index ID that does not
exist. This B-tree index may have been deleted just before being
referenced.
Make sure the B-tree ID was obtained using the correct name binding
interfaces, such as the RHLI name binding function ubndbt, through the
RHLI functions such as uinftbl or uinfbt, or through the ucc compiler.
43
–179
This program only operates on remote databases.
Explanation
A program that has been linked to access remote databases only is being
used to open a local database.
Correction
Check the setting of the DBHOST configuration variable or make sure that
the host machine portion of the qualified database name is given.
–180
This program only operates on local databases.
Explanation
Correction
–181
A program that has been linked to access only local databases is being
used to open a remote database.
Check the setting of the DBHOST configuration variable or make sure that
the host machine portion of the qualified database name is “.” (local
access).
Invalid column ID/not part of common table.
Explanation
An attempt has been made to reference a column ID that does not exist.
This column may have been deleted just before being referenced.
Correction
Make sure the Column ID was obtained using the correct name binding
functions such as the RHLI name binding function ubndcol, through the
RHLI functions such as uinftbl or uinfcol, or through the ucc compiler.
–182
Invalid number of columns specified.
Explanation
Correction
44
An attempt has been made to perform an operation requiring one or more
columns, but the number of specified columns was less than one.
Make sure the data structures have been properly initialized.
Error Messages
–183
Not a column group.
Explanation
An attempt has been made to reference a column group, but the specified
Column IDs do not belong to any known column group. This error occurs
when trying to retrieve rows based on an index key.
Correction
Make sure the Column IDs are in the same sequence as those used to
create the index. Make sure the specified number of columns matches the
number specified when the index was created.
–184
No row current.
Explanation
Correction
–185
An attempt has been made to access a row, but no row is current. This is
an internal error and should not occur in the normal execution of the
database.
If this error occurs, please call Customer Support.
The row was NOT deleted.
Explanation
Correction
–186
An attempt has been made to insert a row into a direct table, where the
specified primary value was mapped to a row that already exists. You can
only insert rows into a direct table at locations occupied by deleted or
non-existent rows. This error only occurs when the primary key value is
specified in the UNIPCOLL data structure.
Use an update operation to update a direct table row.
File does not exist.
Explanation
Correction
Error Messages
An attempt has been made to open a file that does not exist. This is an
internal error and should not occur in the normal execution of the
database.
If this error occurs, please call Customer Support.
45
–187
Invalid hash table ID.
Explanation
Correction
–188
An attempt has been made to reference a Hash Table ID that does not
exist. This hash table may have been deleted just before being referenced.
Make sure the Hash Table ID was obtained using the correct name
binding functions such as the RHLI name binding function ubndhsh,
through the RHLI functions such as uinftbl or uinfhsh, or through the
ucc compiler.
Invalid hash table ID.
Explanation
Correction
–189
An attempt has been made to reference a Hash Table ID that does not
exist. This hash table may have been deleted just before being referenced.
Make sure the Hash Table ID was obtained using the correct name
binding functions such as the RHLI name binding function ubndhsh,
through the RHLI functions such as uinftbl or uinfhsh, or through the
ucc compiler.
Key column(s) required.
Explanation
Correction
–190
An attempt has been made to perform an operation requiring a primary
key column on a table which does not contain a primary key.
Add a primary key column to the table, or perform an operation that does
not require a primary key column, such as through use of a scan.
Invalid link ID.
46
Explanation
An attempt has been made to reference a Link ID that does not exist. This
link may have been deleted just before being referenced.
Correction
Make sure the Link ID was obtained using the correct name binding
functions such as the RHLI name binding function ubndlnk, through the
RHLI functions such as uinftbl or uinflnk, or through the ucc compiler.
Error Messages
–191
No privilege for the attempted operation.
Explanation
Correction
–192
An attempt has been made to perform an operation for which the user has
not been granted the necessary privilege. This error typically relates to
DDL operations performed against a schema the user has not been
granted access to, but the error can also occur performing DML
operations on tables or columns that are not accessible to the user. In
certain DDL operations, the user is required to be in the schema upon
which the operation is being performed.
Verify and correct access and privileges as necessary.
Attempt to reference nonexistent row through use of a link.
Explanation
Correction
–193
An attempt has been made to insert or update a row containing one or
more columns that are children of links. The corresponding row in the
parent table cannot be found using the value of the child column’s data.
Make sure the parent table’s row containing the data corresponding to the
child column’s data has been inserted before inserting or updating the
child column’s row.
Operation not allowed on a remote database.
Explanation
Correction
Additional Help
Error Messages
An attempt was made to perform an operation that is not allowed on a
remote database.
Use operating system utilities to remotely log into the server machine and
perform the operation as a local user.
Unify/Net Guide
47
–194
Row does not exist (invalid row ID or row has been deleted).
Explanation
Correction
–195
An attempt has been made to reference a row which does not exist. This
row may have been deleted just before being referenced. A Row ID is
less than “1” or greater than the highest allocated Row ID in the table
(Row ID < 1 and Row ID > max Row ID) indicates that the row “does not
exist”. A Row ID is greater than or equal to “1” and less than or equal to
the highest allocated Row ID (Row ID 1 and Row ID max Row ID)
indicates that the row has been deleted.
Make sure the Row ID represents a reasonable row. If a scan is being
used, you may need to restart the scan.
Invalid table ID.
Explanation
Correction
–196
An attempt has been made to reference a Table ID that does not exist.
Make sure the Table ID was obtained using the correct name binding
functions such as the RHLI name binding function ubndtbl, through the
RHLI functions such as uinfath, or through the ucc compiler. This table
may have been deleted just before being referenced.
Unique column required.
Explanation
Correction
–197
An attempt has been made to perform an operation requiring a unique
column or column group, for which no unique column or column group
exists.
Before attempting this operation, you must first add the unique column or
column group.
Invalid volume ID.
48
Explanation
An attempt has been made to reference a Volume ID that does not exist.
Correction
Make sure the Volume ID was obtained using the correct name binding
functions such as the RHLI name binding function ubndvol, through the
RHLI functions such as uinftbl or uinfvol, or through the ucc compiler.
This volume may have been deleted just before being referenced.
Error Messages
–198
Invalid executable ID.
Explanation
An attempt has been made to reference an Executable ID that does not
exist. This executable may have been deleted just before being
referenced.
Correction
Make sure the Executable ID was obtained using the correct name
binding functions such as the RHLI name binding function ubndxec,
through the RHLI functions such as uinfath or uinfxec, or through the
ucc compiler.
–199
Adding null key value to a unique hash table index.
Explanation
Correction
–200
An attempt has been made to insert a null value key into a unique hash
table index. A no-duplicates hash table cannot contain a null value key
because the comparison of null values results in an undefined value.
Specify non-null values for columns in unique hash tables.
A null value was specified for a column with the ‘not-null’ attribute.
Explanation
An attempt has been made to insert or update a column’s data value to
null when the column has been specified as NOT NULL.
Correction
Make sure the valopts field of the UNIPCOLL structure is correctly
initialized before performing the insert or update operation. Non-null
default values can be assigned to null columns using the Data Integrity
Subsystem (DIS).
–201
Row does not have read permission.
Explanation
Correction
Error Messages
An attempt has been made to read a row from a volume for which the
user does not have read access. This is an internal error and should not
occur in the normal execution of the database.
If this error occurs, please call Customer Support.
49
–202
The column cannot be changed due to references to it.
Explanation
Correction
–203
An attempt has been made to delete a row that either has a lock on it or is
a parent link column with existing child links.
Delete all of the child table rows before attempting to delete the parent
table row. The rows can be identified using a “link” scan.
The ‘REKEY’ executable has abnormally terminated, probably
because of a signal.
Explanation
Correction
–204
The rekey utility was killed while attempting to add a hash table on a
table containing data. This error usually indicates that rekey caught a
signal that prematurely terminated the operation.
Check the errlog file for an entry describing the signal caught. The hash
table index will not have been added. If the hash table index is still to be
created, restart the operation.
Too many tables specified.
Explanation
An attempt has been made to redefine the table on which a scan is to be
performed, or to specify a column which does not belong to the table on
which the scan is to be performed.
Correction
Make sure the table is specified using the RHLI uinstbl function, before
attempting any other scan operations. Make sure all of the columns
specified for the scan, including the projection list, the sort list, and the
or-groups, all belong to the table specified in the uinstbl function.
Additional Help
50
Unify DataServer: RHLI Reference
Error Messages
–205
Operation cannot be done with active transaction.
Explanation
Correction
Additional Help
–206
An attempt has been made to perform an operation while the process still
has active transactions. This error usually occurs when the RHLI uclsdb
function is called with the DB_NORMAL option, before all active
transactions have been committed or aborted.
All active transaction must be committed or aborted before attempting
the RHLI uclsdb function call using the DB_NORMAL option. If the
DB_ABTTX option is used, all active transactions are automatically
committed or aborted by the system.
Unify DataServer: RHLI Reference
Invalid transaction type.
Explanation
Correction
Additional Help
–207
An attempt has been made to perform an operation using a transaction
whose type does not allow the operation being performed. This error
typically occurs when the operation is performed using the read-only
transaction type (identified by the constant UTXTYPE0 defined in the
RHLI header file rhli.h).
Perform the operation using one of the updateable transaction types
available.
Unify DataServer: RHLI Reference
None or too many data buffers specified.
Explanation
An attempt has been made to insert, update, or retrieve text/binary data
when too few or too many buffers were specified. The error for too few
text/binary buffers occurs when the vd_buf and vd_filnm members of the
RHLI UTP_VDDS data structure are both nil. The error for too many
text/binary buffers occurs when the vd_buf and vd_filnm members of the
RHLI UTP_VDDS data structure are both not nil.
Correction
The vd_buf and vd_filnm members of the RHLI UTP_VDDS data structure
are mutually exclusive — one of the members must be not nil while the
other must be nil.
Additional Help
Error Messages
Unify DataServer: RHLI Reference
51
–208
Row does not have write permission.
Explanation
Correction
–209
An attempt has been made to write a row to a volume for which the user
does not have write access. This is an internal error and should not occur
in the normal execution of the database.
If this error occurs, please call Customer Support.
Invalid size specified.
Explanation
Correction
Additional Help
–210
The value specified for the configuration variable RMTROWBUFSIZ is
invalid.
Make sure the value of RMTROWBUFSIZ is not less than zero (0).
Unify DataServer: Configuration Variable and Utility Reference
Operation not allowed on views.
Explanation
An attempt has been made to perform an operation on a table which is an
SQL/A view. Views may only be accessed from SQL/A, and are not
available for use by the RHLI functions.
Correction
–211
If possible, perform the operation on the database tables that make up the
view. Otherwise, perform the operation using SQL/A.
Attempt to remap previously mapped object.
Explanation
Correction
An attempt has been made to perform ID mapping on an object which is
currently already mapped. This error also occurs if the object is remapped
to the same value it was originally mapped to.
Reset the object’s ID mapping before attempting to remap the object.
If the object has been remapped to the same value it was originally
mapped to, you can ignore this error.
52
Error Messages
–212
Object has not been re-mapped.
Explanation
An attempt has been made to reset the mapped ID of an object that has
not been mapped, or whose mapped ID has been previously reset.
Correction
An object’s mapped ID can only be reset once. Subsequent attempts to
reset the ID will fail, unless a new ID is mapped to the object.
–213
Attempt to multiply map database object.
Explanation
Correction
–214
An attempt has been made to map more than one compile-time ID to the
same runtime object. For instance, an attempt to map the IDs 20 and 21 to
the table cust_table will cause this error.
A runtime object may only be mapped to one compile-time ID at a time.
Compiled object does not match mapped object.
Explanation
An attempt has been made to map a compile-time ID to a runtime object
whose MAPID no longer reflects the same physical characteristics as the
compile-time object. The runtime object has probably had schema
modifications made to it since the compile-time object was referenced.
Correction
The application source files which reference the object need to be
recompiled using the ucc utility, and relinked using the uld utility.
Depending on the changes made to the object, source code modifications
may be necessary.
–215
Invalid number of bytes to read.
Explanation
Correction
Error Messages
An invalid number of bytes has been requested in a text/binary operation.
This error can be caused by an attempt to fetch a negative number of
bytes or to update a value by reading “to end-of-file” from a memory
buffer.
Specify a non-negative number of bytes to fetch or specify the exact
number of bytes to use from a memory buffer.
53
–216
Cannot delete current schema.
Explanation
Correction
–217
You cannot drop the current schema for a user.
The user must set another schema to be current before dropping the
current schema.
The text/binary input/output buffer file must be a Unix regular file.
Explanation
An attempt has been made to specify a text/binary input/output buffer file
that is not a Unix regular file. This error usually occurs when an attempt
is made to read from the terminal or a pipe.
Correction
The vd_filnm member of the RHLI UTP_VDDS data structure contains the
name of the offending file.
Additional Help
–218
Unify DataServer: RHLI Reference
File is not a “regular” file.
Explanation
Correction
Additional Help
–219
An attempt has been made to specify to the Unify DataServer linker, uld,
an intermediate file (.u suffix) that is not a Unix regular file.
Change the format of the file.
Unify DataServer: Configuration Variable and Utility Reference
Both DDL and DML operations not allowed in the same transaction.
Explanation
Correction
54
An attempt has been made to perform a DDL operation in a DML
transaction, or a DML operation in a DDL transaction. A transaction is
identified as being either a DDL or DML transaction by the first operation
performed against the transaction. A data retrieval operation, such as
retrieving a row from a table, is not considered a DML operation against
the transaction.
Commit the transaction and start a new one.
Error Messages
–220
Cannot delete the database creator.
Explanation
An attempt has been made to delete the user that created the database.
Correction
The database creator cannot be dropped.
–221
Duplicate volume preference for table.
Explanation
Correction
–222
An attempt has been made to add a preference for a volume to a table that
already has a volume preference. A table can have only one volume
preference.
The volume preference cannot be added.
Duplicate database schema name.
Explanation
Correction
–223
An attempt has been made to add an authorization that already exists.
The authorization name cannot be added.
Duplicate database user name.
Explanation
Correction
–224
An attempt has been made to add a user that already exists.
The user name cannot be added.
Cannot find or access required file ‘file.err’ file (aka ‘errlog’) in
database directory.
Explanation
The errlog file is a required database file that records informational
messages to the database administrator. This error indicates that the
errlog file cannot be found in the directory specified by the DBPATH
configuration variable. Note that the database will not be opened until the
errlog file exists and is writable.
Correction
Make sure that the DBPATH configuration variable is correctly defined
and that you have appropriate permissions set on the catalog. Verify that
the errlog file exists and that it has write permission. If the errlog file
does not exist, create one using the command:
cp
Error Messages
/dev/null
$DBPATH/errlog
55
–225
Duplicate column specified in index key list.
Explanation
Correction
–226
An attempt has been made to specify an index on a table for which a
column has been multiply specified. An index key may only contain one
occurrence of any column.
Validate the column list to make sure that the columns are unique, and
make sure the column list indicator accurately reflects the number of
columns in the list.
Table DIS definitions must be removed prior to dropping table.
Explanation
Correction
–227
An attempt has been made to drop a table that currently contains Data
Integrity Subsystem (DIS) information.
All DIS information must be removed from the table, using the disc
utility, prior to attempting to drop the table.
Bad format in Backup Device info (BUDEV or JOURNAL). Should
be: ”DEVNM=xx, BLKSZ=xx, MAXBLK=xx,
TYPE=<mount/nomount>”.
Explanation
Correction
Additional Help
–228
An attempt has been made to specify a BUDEV or JOURNAL
configuration parameter that contained one or more invalid components.
This error message applies to both the back-up device (specified by
BUDEV) and the transaction journals (specified by JOURNAL and
JOURNAL2). Either one or both of these configuration parameters is
specified incorrectly.
Correct the parameter format.
Unify DataServer: Configuration Variable and Utility Reference
A direct key may not be updated.
56
Explanation
An attempt has been made to update the primary key of a row in a table
that is defined as DIRECT.
Correction
To update a primary key column in a table defined as DIRECT, you must
first delete the old row and then insert the new row.
Error Messages
–229
Volume still has active table preferences attached to it.
Explanation
Correction
–230
An attempt has been made to drop a volume for which one or more tables
still have active volume preferences.
You must first delete the volume preferences for all tables that have a
preference for the volume you want to drop.
Cannot drop a column group that is the primary key for the table.
Explanation
Correction
–231
A column group cannot be dropped when it is the primary key of the
table.
Do not drop the column group.
User name is reserved for the database.
Explanation
An attempt has been made to create a database by a user whose login
name is reserved for use by the database. The user login name is obtained
from the operating system file /etc/passwd.
Correction
Change the Unix user name, located in the Unix /etc/passwd file, or have
another user create the database.
–232
A read-only table or column cannot be updated or inserted into.
Explanation
Correction
–233
An attempt has been made to insert or update data in a table or column
that is defined as READ-ONLY.
Remove the READ-ONLY restriction of the column or table before
attempting to insert or update the data.
The schema cannot be deleted while there are users accessing it.
Explanation
An attempt has been made to delete a schema while users are currently
residing in the schema. Schemas may only be deleted when no user is
actively accessing the schemas.
Correction
Check that the data in the schema is not being used. Wait until all users
have terminated their database session, or have the users fetch another
schema prior to attempting to delete the schema.
Error Messages
57
–234
Cannot start an update transaction for a read-only database.
Explanation
Correction
–235
An attempt has been made to begin an update transaction while the
database has been opened for read-only access.
When a database is opened for read-only access, the only valid
transaction type is UTXTYPE0.
NOZBYTE option not allowed for the operation.
Explanation
Correction
–237
The NOZBYTE option may not be used with pattern matching operators
when calling uinsor().
Remove the NOZBYTE option.
Not enough user memory space on server.
Explanation
Correction
Additional Help
–238
An attempt to allocate memory on the server failed because the process
reached some system-imposed limit.
Try reducing the values of the configuration variables that control the
size of process memory: INITMEM, SQLSMEM, SQLPMEM, or TIMEM.
Unify DataServer: Configuration Variable and Utility Reference
The ‘$UNIFY’ configuration variable is not defined on the server.
Explanation
Correction
–239
The UNIFY configuration variable on the server must be defined so that
the database system can locate the message files and the default
configuration file.
Set the UNIFY configuration variable to the path name of the lib directory
in the Unify DataServer release installed on the server.
The ‘$UNIFY’ directory does not exist or is not accessible on server.
Explanation
The database system is not able to access the directory indicated by the
UNIFY configuration variable on the server.
Correction
58
Make sure that UNIFY is set correctly and that read access is allowed on
the server $UNIFY directory.
Error Messages
–240
The ‘$UNIFY/unify.msg’ message file does not exist or is not
accessible on server.
Explanation
Correction
–241
The database system is unable to open the message file, unify.msg, on
the server.
Make sure that UNIFY is set to the lib directory of the release installed on
the server and that the permissions are correct for the UNIFY directory
and the $UNIFY/unify.msg message file.
No such file, directory, or program on server.
Explanation
Correction
–242
This error occurs when a file name is specified and the file does not exist
on the server, or when one of the directories in a path name does not exist
on the server.
Check the server error log file to determine which file cannot be found.
No children on server.
Explanation
Correction
–243
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
No more processes on server.
Explanation
Correction
–244
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
File too large on server.
Explanation
Correction
Error Messages
An attempt has been made to make a file larger than the system imposed
maximum on the server. This is an internal error and should not occur in
the normal execution of the database.
If this error occurs, please call Customer Support.
59
–245
No space left on device on server.
Explanation
Correction
–246
No free space remains on the device in which to write an ordinary file.
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Too many open files on server.
Explanation
Correction
–247
An attempt has been made to open more files than are allowed by the
operating system for each process.
Reconfigure the operating system to support more open files per process
or reduce the number of open files.
Failed to open error log file on server.
Explanation
Correction
–248
An attempt to open the server error log file failed. This error is fatal
because the database system requires the error log file.
If this error occurs, please call Customer Support.
Permission denied on file on the server.
Explanation
Correction
–249
An attempt has been made to open a server file in a mode not allowed by
the permissions on the file.
Check the server error log file to determine which file could not be
accessed.
The ‘$CLIENTINFO’ directory is not accessible.
Explanation
The database system is not able to access the directory specified the
CLIENTINFO configuration variable.
Correction
Additional Help
60
Make sure that CLIENTINFO is set correctly. Make sure that read access is
allowed on the $CLIENTINFO directory.
Unify DataServer: Configuration Variable and Utility Reference
Error Messages
–250
Cannot find or access required file ‘dbname.err’ in $CLIENTINFO
directory.
Explanation
Correction
–251
The dbname.err file on the server cannot be accessed because it does not
exist or write permission is denied on it.
Get the server’s system administrator to check for above condition and
take corrective action; create or modify permission.
Not a directory on the server.
Explanation
Correction
–252
A non-directory name was specified where a directory name was
required, such as the configuration variables DBPATH or UNIFY.
Check the server error log file to determine which file caused the error.
String value is too long.
Explanation
Correction
–253
An attempt has been made to enter too many characters into a character
field.
Enter fewer characters.
The Unify release ‘bin’ directory is not on your path or is not
accessible.
Explanation
The required database utility programs cannot be found in the directories
specified in the PATH configuration variable.
Correction
Make sure that the Unify DataServer release bin directory is specified in
the PATH configuration variable. Make sure that the names of all
components of the Unify DataServer release bin directory are spelled
correctly. And make sure that you have execute permission on the
directories leading to the Unify DataServer release bin directory.
Error Messages
61
–254
A different database is already open.
Explanation
This error can occur in an application that uses both RHLI and Embedded
SQL/A to access a database. The message indicates that the RHLI code
and the Embedded SQL/A code are attempting to access different
databases.
Correction
–255
Make sure that the database name given to uopndb and the database
name given to embedded SQL/A (in the DBHOST, DBPATH, and DBNAME
configuration variables) are the same. If you want to use different
databases, make sure that you close the first database before trying to
open the second database.
Too many B–tree scans (and/or ordered accesses) active at once.
Explanation
Correction
–256
The value set for the MAXBTSCAN configuration variable has been
exceeded.
Either increase the setting for MAXBTSCAN, or reduce the number of
active B-tree scans.
Cannot revoke access while user is in the database.
Explanation
Correction
–257
You cannot revoke database access from a user that has a current SQL/A
session.
The user must end the SQL/A session before you can revoke database
access.
Function cannot be called from a signal handler.
Explanation
Correction
Additional Help
62
The RHLI function cannot be called from a signal handler.
Restructure the function. The usetitr function can be called from a signal
handler.
Unify DataServer: RHLI Reference
Error Messages
–258
Explanation
Correction
DDL operations require compiled–schema merging to be enabled
(SCHEMA=TRUE).
The SCHEMA configuration must be set to TRUE for this operation.
Change the SCHEMA setting.
Additional Help
Unify DataServer: Configuration Variable and Utility Reference
–260
Unable to correctly close database, database closed anyway.
Explanation
An error occurred late in uclsdb(). The error log entry will have more
information.
Correction
This is an internal error and should not occur during normal operations.
Please call Customer Support.
–261
Operation not allowed on a local database.
Explanation
Correction
Error Messages
Some operations are not allowed on a local database. For example,
querying the state of the network connection is meaningless on a local
database.
Perform only the operations that are allowed on a local database.
63
–301
The database is still active.
Explanation
Correction
–302
An attempt has been made to activate a virtual sync unit (VSU) for a
database that is already active. This is an internal error and should not
occur in the normal execution of the database.
If this error occurs, please call Customer Support.
The file is already attached to the database.
Explanation
Correction
–303
An attempt has been made to attach a file to a database virtual sync unit
(VSU) that already contains the file. This may be caused by attempts to
use linked files. This is an internal error and should not occur in the
normal execution of the database.
If this error occurs, please call Customer Support.
The database still has attached files.
Explanation
Correction
–304
An attempt has been made to deactivate a database virtual sync unit
(VSU) which still has files attached to it. This is an internal error and
should not occur in the normal execution of the database.
If this error occurs, pleaese call Customer Support.
An invalid database ID was supplied.
Explanation
Correction
–305
An attempt has been made to reference a database virtual sync unit
(VSU) function using an invalid ID. This is an internal error and should
not occur in the normal execution of the database.
If this error occurs, please call Customer Support.
File Manager cannot find configuration file.
Explanation
Correction
64
The file manager daemon fmdmn is not able to locate the database
configuration file. This is an internal error and should not occur in the
normal execution of the database.
If this error occurs, please call Customer Support.
Error Messages
–306
File has been disabled.
Explanation
Correction
–307
An attempt has been made to attach a file to a database virtual sync unit
(VSU) when the file has already been attached to the system VSU. This is
an internal error and should not occur in the normal execution of the
database.
If this error occurs, please call Customer Support.
File is not attached to database.
Explanation
Correction
–308
An attempt has been made to reference a file that has not yet been
attached to either the database virtual sync unit (VSU) or the system VSU.
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Database already exists.
Explanation
Correction
–309
An attempt has been made to create a virtual sync unit (VSU) for a
database when one already exists. This is an internal error and should not
occur in the normal execution of the database.
If this error occurs, please call Customer Support.
Update already initiated.
Explanation
Correction
Error Messages
An attempt has been made to begin a non-nested (root) atomic update
operation on the database virtual sync unit (VSU) when such an operation
already exists. This is an internal error and should not occur in the normal
execution of the database.
If this error occurs, please call Customer Support.
65
–310
File is still in use.
Explanation
Correction
–311
An attempt has been made to delete a database virtual sync unit (VSU)
while there are still users actively using it. This is an internal error and
should not occur in the normal execution of the database.
If this error occurs, please call Customer Support.
Database is a directory.
Explanation
Correction
–312
The database virtual sync unit (VSU) name specified references a
directory instead of a file. The VSU cannot be created. This is an internal
error and should not occur in the normal execution of the database.
If this error occurs, please call Customer Support.
File name is too long.
Explanation
Correction
–313
The full path name of a database file is longer than 256 characters.
Attempt to shorten the file name, if possible, by moving the file to a
directory with a shorter path name, or shorten the database name used in
the configuration variable DBNAME.
Too many file descriptors open (> operating system limit?).
Explanation
Correction
Additional Help
66
An attempt has been made to open a file that results in the number of
open file descriptors exceeding the per-process limit allowed by the
operating system.
Try to reduce the number of simultaneously open files through the
various configuration parameters which control file descriptor allocation,
such as the configuration parameters MAXBTSCAN or OPNARCHS.
It may be possible to reconfigure the operating system to support more
simultaneously open files.
Unify DataServer: Configuration Variable and Utility Reference
Your operating system manuals.
Error Messages
–314
Database not active.
Explanation
Correction
–315
An attempt has been made to reference a database virtual sync unit (VSU)
that exists but has not yet been activated. This is an internal error and
should not occur in the normal execution of the database.
If this error occurs, please call Customer Support.
File has not been disabled.
Explanation
Correction
–316
An attempt has been made to reenable a file for which recovery has not
been disabled. This is an internal error and should not occur in the normal
execution of the database.
If this error occurs, please call Customer Support.
Database does not exist.
Explanation
Correction
–317
An attempt has been made to reference a database which does not exist.
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Physical file system recovery is not needed.
Explanation
An attempt has been made to perform file system recovery on a database
that did not need recovery. The database is physically consistent.
Correction
No correction needed because the database is physically consistent. Note
that the database may not be logically consistent.
–318
File name is too short.
Explanation
Correction
Error Messages
A file name consisting of a null string has been specified.
A file name must contain at least one character.
67
–319
Device is not block/character-special.
Explanation
Correction
–320
An attempt has been made to reference a character- or block-special
device that is actually a regular file.
Check the file to validate that the file is not a device. If the file is not a
device, remove the device specification.
Database has not yet been suspended.
Explanation
Correction
–321
An attempt has been made to resume processing on a database virtual
sync unit (VSU) that has not been suspended. This is an internal error and
should not occur in the normal execution of the database.
If this error occurs, please call Customer Support.
Update not yet initiated.
Explanation
Correction
–322
An attempt has been made to terminate a user’s atomic update operation
on a database virtual sync unit (VSU) for which the user does not have
any active updates. This is an internal error and should not occur in the
normal execution of the database.
If this error occurs, please call Customer Support.
No such user process.
Explanation
Correction
68
An attempt has been made to become an agent for a process that does not
exist. This is an internal error and should not occur in the normal
execution of the database.
If this error occurs, please call Customer Support.
Error Messages
–323
Open File Manager file.
Explanation
Correction
–324
An attempt has been made to attach a file to a database virtual sync unit
(VSU) when the file is currently open. A file may only be attached when
it is closed. This is an internal error and should not occur in the normal
execution of the database.
If this error occurs, please call Customer Support.
File has been attached to another database.
Explanation
Correction
–325
An attempt has been made to attach a file to a database virtual sync unit
(VSU) while the file is currently attached to another database. This is an
internal error and should not occur in the normal execution of the
database.
If this error occurs, please call Customer Support.
A process has abnormally terminated while modifying the database;
database recovery using the ‘irma’ utility is now necessary.
Explanation
Correction
Additional Help
–326
A user process has aborted while in an atomic update operation, or the
database has detected an inconsistency which cannot be corrected.
Recover the database using the irma utility.
Unify DataServer: Configuration Variable and Utility Reference
Reserved File Manager file.
Explanation
An attempt has been made to reference a file that has the same full path
name as one of the required database files. For example, the user tried to
create a database with the same name as the physical log file (file.pl).
Correction
Change the name of the file to something other than one of the reserved
database file names.
Additional Help
Error Messages
Unify DataServer: Managing a Database
69
–327
File is not seekable.
Explanation
An attempt has been made to reference a B-tree or volume file that is not
a seekable device, such as a magnetic tape device. All database files must
be seekable.
Correction
Non-disk devices such as terminal ports or magnetic tape devices cannot
be used as database files.
–328
Database already has been suspended.
Explanation
Correction
–329
An attempt has been made to suspend a database virtual sync unit (VSU)
that has already been suspended. This is an internal error and should not
occur in the normal execution of the database.
If this error occurs, please call Customer Support.
Cannot recover file system, physical log is empty/missing/corrupted.
Explanation
Correction
The physical log associated with your database is missing. The irma
utility should report a recommended action when this occurs.
Follow the actions recommended by the irma utility.
Additional Help
Unify DataServer: Configuration Variable and Utility Reference
–330
Operation cannot be performed while backup is in progress.
Explanation
Correction
70
An attempt is made to perform a sync while a backup is in progress.
Wait until the backup finishes, and restart the sync.
Error Messages
–401
Invalid database.
Explanation
An attempt has been made to access a database virtual sync unit (VSU)
with the wrong database name. This is an internal error and should not
occur in the normal execution of the database.
Correction
Check your DBPATH and DBNAME configuration variables to verify that
the database name is correct. If the database name is correct, please call
Customer Support.
Additional Help
–402
Unify DataServer: Configuration Variable and Utility Reference
Operator abort.
Explanation
Correction
–403
The database operator terminated the read or write operation to a
database backup or journal device.
Since the database backup/journal operation has been intentionally
terminated, this message does not require correction.
Internal code:Bad media.
Explanation
Correction
–404
The database backup/journal driver is unable to read or write to the
device header. This situation usually occurs when a bad or incorrect tape
or disk is mounted. This is an internal error and should not occur in the
normal execution of the database.
Check the label on the tape or disk mounted.
Invalid backup control block.
Explanation
Correction
The magic number on the backup/journal device is not valid. This error
occurs when the tape or file opened by the backup device driver is not a
backup/journal tape or file.
Try mounting a tape that was generated by the backup utility. Check the
BUDEV and JOURNAL configuration variables.
Additional Help
Error Messages
Unify DataServer: Configuration Variable and Utility Reference
71
–405
Invalid backup device type.
Explanation
Correction
Additional Help
–406
The database backup driver accepts two device types — mountable and
non-mountable. The device type is specified by one of the configuration
variables BUDEV or JOURNAL. This error occurs if one of these
configuration variable is not set correctly.
Check the BUDEV and JOURNAL configuration variables.
Unify DataServer: Configuration Variable and Utility Reference
Backup device name is Null.
Explanation
Correction
Additional Help
–407
The backup device name is set to a null string. The device name should
be specified by one of the configuration variables: BUDEV (for the
backup device) and JOURNAL (for the transaction log journal).
Check the BUDEV and JOURNAL configuration variables.
Unify DataServer: Configuration Variable and Utility Reference
BUDEV configuration variable not set.
Explanation
Correction
–408
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Fatal internal error, ‘file.err’ (aka ‘errlog’) updated.
Explanation
Correction
72
This error usually occurs when the backup device driver fails to
communicate with its child process, or fails to perform an I/O operation,
or fails to close a device or a pipe. This is an internal error and should not
occur in the normal execution of the database.
If this error occurs, please call Customer Support.
Error Messages
–409
Too few blocks per tape.
Explanation
The number of blocks specified for backup/journal device is insufficient
for writing the header and data.
Correction
Check the BUDEV and JOURNAL configuration variables and the tape or
file capacity.
Additional Help
–410
Unify DataServer: Configuration Variable and Utility Reference
Block size too large.
Explanation
The block size for the transaction journal/backup device is larger than the
limit set by the database. The limit is the maximum value that can fit in a
long type variable.
Correction
Check the BUDEV and JOURNAL configuration variable settings.
Additional Help
Unify DataServer: Configuration Variable and Utility Reference
–411
Invalid I/O mode.
Explanation
Correction
–412
The journal/backup device has not been opened in the proper I/O mode.
This is an internal error only and should not occur in the normal
execution of the database.
If this error occurs, please call Customer Support.
Unable to open message device.
Explanation
Correction
Additional Help
Error Messages
The backup/journal device driver needs to have an operator message
device specified to be able to display operator messages. This error
message occurs if the message device cannot be opened for writing.
Check the permissions on the operator message device. Check the
configuration variables OPMSGDEV and OPNOTIFY.
Unify DataServer: Configuration Variable and Utility Reference
73
–413
Unable to open backup device.
Explanation
Correction
Additional Help
–415
The backup/journal device driver is unable to open the backup/journal
device.
Check the BUDEV and JOURNAL configuration variables. Also check that
the permissions on the backup/journal devices allow the operation being
performed.
Unify DataServer: Configuration Variable and Utility Reference
Unable to install response signals.
Explanation
Correction
Additional Help
–416
The backup/journal driver is unable to correctly install operator signals.
Check that the BUSIGYES and BUSIGNO configuration variables are set to
valid operating system signals: SIGUSER1 and SIGUSER2.
Unify DataServer: Configuration Variable and Utility Reference
Block size too small.
Explanation
The block size specified for the transaction journal/backup device is too
small to hold the header structures.
Correction
Check the BUDEV and JOURNAL configuration variables and the block
size.
Additional Help
–417
Unify DataServer: Configuration Variable and Utility Reference
Incorrect tape mounted.
74
Explanation
Each backup/journal tape or file contains the database version, sequence
number, and volume number. This error occurs if this tape or file is not
mounted or is not set in the correct order.
Correction
Check the labels on the tapes or volumes to make sure you are reading
the volumes in the correct order. Also, verify that the tape being read is
of the correct type: either a backup tape or a journal tape depending upon
the operation you are performing.
Error Messages
–418
Unknown backup module error.
Explanation
Correction
–419
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Write to backup device failed.
Explanation
Correction
–420
If the backup/journal device reaches the end of the device, the write fails.
This condition should be detected before the device actually runs out of
space. This is an internal error and should not occur in the normal
execution of the database.
Check for write permission on the backup/journal device.
Internal code:Wrong volume mounted.
Explanation
The backup/journal device driver keeps track of the backup/journal
volumes by assigning database version number, sequence number and
tape number. This error is displayed if the volumes are not mounted in
the correct order.
Correction
Check the version, sequence, and tape/volume number on the tape/file
mounted.
–421
Sort/merge file open/creation failed.
Explanation
Correction
Error Messages
Failed to create or open a sort/merge file. You may have run out of file
descriptors.
Manage your file descriptors so that you don’t exceed the limit. You may
want to reconfigure your operating system if you encounter a consistent
shortage of file descriptors.
75
–422
Log file block is different from system’s.
Explanation
The transaction log file has a different block size than the one used by the
DBMS.
Correction
Additional Help
–423
Recreate the log file using the mklog utility.
Unify DataServer: Configuration Variable and Utility Reference
Failed to seek to sorted list file.
Explanation
Correction
–424
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Invalid log file descriptor.
Explanation
Correction
–425
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Illegal transaction ID.
Explanation
Correction
The database failed to validate a Transaction ID.
Check the validity of the Transaction ID passed to an RHLI function in
your program.
Also, check that the logical log file (file.lg) is not running out of space.
Your transaction could have been aborted if it was the oldest open
transaction in the log and another transaction needed space in the log.
–426
Invalid database ID passed.
Explanation
Correction
76
An internal database structure has not been properly initialized. This is an
internal error and should not occur in the normal execution of the
database.
If this error occurs, please call Customer Support.
Error Messages
–427
Invalid database name.
Explanation
Correction
–428
Invalid database name is specified to an RHLI function.
Check the validity of the database name specified, including the
pathname.
Invalid log read direction.
Explanation
Correction
–429
The transaction log read direction has two valid directions: forward and
backward. Any other value for read direction is invalid. This is an
internal error and should not occur in the normal execution of the
database.
If this error occurs, please call Customer Support.
Invalid log offset passed to read log.
Explanation
Correction
–430
The transaction log reading interfaces accept a log file offset that is a
multiple of block size and is between the beginning and end of the log.
Any other offset is invalid. This is an internal error and should not occur
in the normal execution of the database.
If this error occurs, please call Customer Support.
Invalid log name passed in sync log function.
Explanation
Correction
Additional Help
Error Messages
When a database is synchronized, all the transaction buffers are forced to
the log file. The log synchronization interface validates the name of the
transaction log file name before actually performing log synchronization.
If the log file name is not in the transaction manager’s list, then it is an
invalid log file name.
Check the DBPATH and DBNAME configuration variables.
Unify DataServer: Configuration Variable and Utility Reference
77
–431
Invalid magic number.
Explanation
Correction
–432
This error indicates that the magic number in the log file is not valid.
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Invalid log operation.
Explanation
Correction
–433
This error occurs when an invalid transaction log operation is requested.
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Invalid process ID to set proc environment.
Explanation
Correction
–434
This error occurs if the process ID does not exist in the transaction
manager’s list of processes. This is an internal error and should not occur
in the normal execution of the database.
If this error occurs, please call Customer Support.
Invalid read mode for read log.
Explanation
Transaction read log interfaces accept one of the following three read
modes:
Read log record header only
Read log record for undo operation
Read log record for redo operation
Any other mode is invalid. This is an internal error only and should not
occur in the normal execution of the database.
Correction
78
If this error occurs, please call Customer Support.
Error Messages
–435
Invalid log file seek mode.
Explanation
Correction
–437
Transaction log reading interfaces accept relative and absolute log file
seeking modes. Other seeking modes are invalid. This is an internal error
and should not occur in the normal execution of the database.
If this error occurs, please call Customer Support.
Invalid sync information record.
Explanation
Correction
–438
This error occurs if the log record at this offset is not a sync record. This
is an internal error and should not occur in the normal execution of the
database.
If this error occurs, please call Customer Support.
End of journal.
Explanation
Correction
–439
This is an internal message and should not occur in the normal execution
of the database.
If this error occurs, please call Customer Support.
Log buffer too small.
Explanation
Correction
–440
The log buffer is the same size as a log block. If the log block size is too
small, then it cannot hold the block header and data. This is an internal
error and should not occur in the normal execution of the database.
If this error occurs, please call Customer Support.
Currently at the beginning of log file.
Explanation
Correction
Error Messages
This is an internal message and should not occur in the normal execution
of the database.
If this error occurs, please call Customer Support.
79
–441
Failed to start the log daemon.
Explanation
Correction
Additional Help
–442
This error occurs when the database system is unable to find and start the
log daemon, lgdmn.
Make sure the lgdmn executable is on your PATH. Also make sure this
executable has executable permission.
Unify DataServer: Managing a Database
Log file empty.
Explanation
Correction
–443
An attempt has been made to read an empty log file. This is an internal
message and should not occur in the normal execution of the database.
If this error occurs, please call Customer Support.
End of log file.
Explanation
Correction
–444
Transaction log reading routines have reached the end of the log file. This
is an internal error only and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Log file not open.
Explanation
This error occurs when the transaction log read/write routines detect that
the log file is not yet open for reading or writing. Logging is turned off.
Correction
Turn transaction logging on by setting the LOGTX configuration variable
to TRUE and then retry the operation.
Additional Help
80
Unify DataServer: Configuration Variable and Utility Reference
Error Messages
–445
Transaction log off globally.
Explanation
Correction
Additional Help
–446
An attempt has been made to start transaction logging when logging is
turned off for the entire transaction processing system.
Turn transaction logging on by setting the LOGTX configuration variable
to TRUE and then retry the operation.
Unify DataServer: Configuration Variable and Utility Reference
Log overflow.
Explanation
There is not enough space in the transaction log or the log is corrupted.
Correction
Increase the size of your log file by setting the LOGBLK configuration
variable to a higher value, then run the mklog utility to recreate the log
file. Also try decreasing the database sync frequency with the
FREQUENCY and FREQTYPE configuration variables.
Additional Help
–447
Unify DataServer: Configuration Variable and Utility Reference
Log read error.
Explanation
Correction
–448
This error occurs when a read transaction log routine fails. This is an
internal error and should not occur in the normal execution of the
database.
Check permissions on the log file. If this error occurs, please call
Customer Support.
Failed seek to log file.
Explanation
Correction
Error Messages
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
81
–449
Write to log file failed.
Explanation
Correction
–450
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Transaction logging not turned on.
Explanation
Correction
Additional Help
–452
An attempt has been made to request a transaction log operation when
logging is not turned on for the process.
Turn on transaction logging by setting the LOGTX configuration variable
to TRUE and retry the operation.
Unify DataServer: Configuration Variable and Utility Reference
Negative offset from the beginning of the file specified.
Explanation
Correction
–453
An attempt has been made to set the current log file position backwards
from the beginning of log file. This is an internal error code and should
not occur in the normal execution of the database.
If this error occurs, please call Customer Support.
Transaction manager not initialized.
Explanation
Correction
82
An attempt has been made to start an operation that requires the services
of the transaction manager and the transaction manager has not been
initialized yet. This is an internal error and should not occur in the
normal execution of the database.
If this error occurs, please call Customer Support.
Error Messages
–454
The back–up message device/console is not found (is OPMSGDEV
correct?).
Explanation
The operator message device specified in the OPMSGDEV configuration
variable is not writable.
Correction
Check the OPMSGDEV configuration variable and the read/write
permissions on the message device.
Additional Help
Unify DataServer: Configuration Variable and Utility Reference
–455
Database control block does not exist.
Explanation
Correction
Additional Help
–456
This error occurs if the database name is wrong or an operation is
attempted before the database is open.
Check your DBPATH and DBNAME configuration variables to make sure
you are accessing the correct database. Verify that the database is open
with the lmshow utility.
Unify DataServer: Configuration Variable and Utility Reference
Database name not set.
Explanation
One of the get database control block functions did not receive the name
of the database.
Correction
Check your DBPATH and DBNAME configuration variables to make sure
you are accessing the correct database.
Additional Help
–457
Unify DataServer: Configuration Variable and Utility Reference
Log file control block non–existent.
Explanation
Correction
Error Messages
An attempt has been made to perform a log operation without first
opening the transaction log. The transaction log file control block is
initialized by an open log function when the database is opened. This is
an internal error and should not occur in the normal execution of the
database.
If this error occurs, please call Customer Support.
83
–458
Log header not allocated/initialized.
Explanation
Correction
–459
The transaction log header is initialized when the database is opened and
is updated at each synchronization of the database. Referring to the log
header before it is allocated or initialized produces this error.
If this error occurs, please call Customer Support.
Log name not set.
Explanation
Correction
–460
An attempt has been made to get the database control block using the
corresponding log file name. This error occurs if the log file name is not
passed to this routine. This is an internal error and should not occur in the
normal execution of the database.
If this error occurs, please call Customer Support.
Log file does not exist.
Explanation
Correction
Additional Help
–461
The transaction log file does not exist in the DBPATH directory.
Check that the DBPATH environment variable is set correctly. Create the
transaction log file using the mklog utility.
Unify DataServer: Configuration Variable and Utility Reference
Last sync point not in the log file.
Explanation
Correction
84
This error occurs when a program cannot find the last sync point in the
log file. This is an internal error and should not occur in the normal
execution of the database.
If this error occurs, please call Customer Support.
Error Messages
–462
Database name not set.
Explanation
Correction
–463
An attempt has been made to get the database control block using the
name of the VSU(Virtual Sync Unit). This error occurs if the VSU name
is not passed to the routine attempting to get the database control block.
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Recovery is in progress elsewhere.
Explanation
Correction
–464
If more than one user attempts database recovery at the same time, only
one user is allowed to proceed. This message informs the user that the
recovery is already in progress.
Check with the database administrator to find out who is performing
recovery. Only one user can perform database recovery at a time.
Lock requested by the same recovery process.
Explanation
Correction
–466
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Redo operation failed.
Explanation
Correction
Error Messages
This is an internal error only and should not occur in the normal
execution of the database.
If this error occurs, please call Customer Support.
85
–467
Unable to allocate shared memory partition.
Explanation
Correction
–468
This error occurs when the user program or application is unable to
allocate a shared memory partition for the transaction manager.
Check shared memory status and permissions with the operating system
shared memory utilities. If you are sharing the shared memory segment
with some one else, make sure you are using a unique shared memory
key by checking the setting of the SHMKEY configuration variable.
File system sync failed before start log.
Explanation
If you are starting transaction logging for the entire database (globally),
then a file system synchronization will be performed before starting
transaction logging. This error occurs if this sync fails.
Correction
Check the disk space. This error message should be accompanied by
other error messages that describe in more detail the cause of the error.
Check for these other error messages.
–469
Failed to open sorted list file.
Explanation
Correction
–470
This is an internal error only and should not occur in the normal
execution of the database.
If this error occurs, please call Customer Support.
Row delete failed.
86
Explanation
If you are starting transaction logging for the entire database (globally),
then a file system synchronization will be performed before starting
transaction logging. This error occurs if this sync fails.
Correction
Check the disk space. This error message should be accompanied by
other error messages that describe in more detail the cause of the error.
Check for these other error messages.
Error Messages
–471
Transaction IDs do not match.
Explanation
Correction
–472
This is an internal error only and should not occur in the normal
execution of the database.
If this error occurs, please call Customer Support.
Exceeded maximum number of active transactions per user.
Explanation
An attempt has been made to exceed the maximum number of concurrent
transactions allowed per user.
Correction
Try committing some of the active transactions that are no longer needed.
Extend the limit of user transactions by setting the MAXUSRTX
configuration variable.
Additional Help
–474
Unify DataServer: Configuration Variable and Utility Reference
Write request to a file failed.
Explanation
Correction
–475
This is an internal error only and should not occur in the normal
execution of the database.
If this error occurs, please call Customer Support.
The system crashed, or shared memory was removed, while a process
had active transactions; logical database recovery using the ‘irma’
utility is now necessary.
Explanation
Correction
Additional Help
Error Messages
If this is the first time you are opening the database since the last shared
memory initialization, the database is checked for physical and logical
(transaction) consistency. If there were active transactions at or after the
last database synchronization, logical recovery is required. Sometimes
this recovery just cleans up the log file.
Recover the database by using the irma utility.
Unify DataServer: Configuration Variable and Utility Reference
87
–476
No begtx log record to match commit/abort log record entry,
recovery needed.
Explanation
Correction
Additional Help
–478
This error indicates a possible log file corruption.
Recover the database by using the irma utility.
Unify DataServer: Configuration Variable and Utility Reference
Bigger log file is needed for this operation.
Explanation
Correction
Additional Help
–479
The attempted operation needs more log space than is available in the log
file.
Shut down the database and create a new log file with the mklog utility.
Unify DataServer: Configuration Variable and Utility Reference
Remove shared memory and daemons before starting recovery.
Explanation
Correction
Additional Help
88
The database recovery program requires that no other operations are
active on the database during recovery. All pre-existing data structures
and daemons should be removed before recovery starts.
Before starting recovery, remove daemons and clean shared memory with
the shutdb utility. If this utility does not work, you must use the
operating system shared memory utilities.
Unify DataServer: Configuration Variable and Utility Reference
Error Messages
–480
Transaction aborted by system due to lack of adequate log space.
Explanation
When it runs out of room in the log file, the log daemon aborts the oldest
transaction, as recorded in the log. With this transaction aborted, the log
daemon is able to recycle the log file.
Correction
Avoid long transactions. Try increasing the size of the transaction log file
by changing the setting of the LOGBLK configuration variable. Also try
committing transactions more frequently. You can also use batch
transaction mode.
Additional Help
Unify DataServer: Configuration Variable and Utility Reference
Unify DataServer: RHLI Reference
Unify DataServer: SQL/A Reference
–481
Too small a log file size (LOGBLK). Must be at least equal to
maximum system transaction (MAXSYSTX).
Explanation
The size of the log file should be big enough to provide one block for
each transaction, up to the maximum number of transactions allowed on
the database. The maximum number of transactions allowed is specified
by the MAXSYSTX configuration variable.
Correction
Try increasing the size of the transaction log file by changing the
LOGBLK configuration variable or decreasing the maximum number of
transactions by changing the MAXSYSTX configuration variable.
Additional Help
–482
Unify DataServer: Configuration Variable and Utility Reference
Transaction not active, may have been aborted or committed.
Explanation
Correction
Error Messages
An attempt has been made to refer to a transaction that is not active in the
transaction processing system. If a transaction is blocking log space
recycling, then it may get aborted by the log daemon.
Make sure that your Transaction ID is valid. Avoid long transactions.
89
–483
Can’t roll back a DDL transaction in this release.
Explanation
DDL transactions are not logged in this release and therefore cannot be
rolled back.
Correction
This is a current release restriction. Manually undo the DDL operation
(drop the database object).
–484
Transaction log not empty, to overwrite use –Ooverwrite.
Explanation
Correction
Additional Help
–485
An attempt has been made to overwrite an non-empty log file. By default,
the mklog utility does not overwrite a non-empty log file.
You have to use the –Ooverwrite option of mklog utility if you want to
overwrite a non-empty log file.
Unify DataServer: Configuration Variable and Utility Reference
Transaction recovery was not required.
Explanation
Correction
Additional Help
–486
You have attempted recovery on a database that does not require
transaction recovery. No transaction recovery was performed. However,
the recovery (irma) utility may clean up the log file.
No correction needed.
Unify DataServer: Configuration Variable and Utility Reference
budb unable to suspend log daemon, timed out.
Explanation
Correction
Additional Help
90
The database backup utility, budb, attempted to suspend the log daemon.
After the suspend request, it waits 60 seconds for the log daemon to
suspend. If the log daemon does not suspend in 60 seconds, budb times
out.
Check if the log daemon is waiting for operator response and restart
budb.
Unify DataServer: Configuration Variable and Utility Reference
Error Messages
–487
Transaction type ‘batch’ cannot be aborted.
Explanation
Correction
–488
An attempt has been made to abort a batch transaction. Batch transactions
cannot be aborted.
None.
Transaction logging has not been enabled – transactions cannot be
aborted.
Explanation
Correction
Additional Help
–489
An attempt has been made to abort a transaction when the transactions
are not logged.
To be able to abort future transactions, turn on transaction logging by
setting TXLOG configuration variable to TRUE. You could commit
transactions instead of aborting, but the updates will affect the database.
Unify DataServer: Managing a Database
Transaction log block retrieved from blist has wrong txid.
Explanation
Correction
–490
An internal error has been detected in managing the transaction log.
This is an internal error and should not occur during normal operations.
Call Customer Support.
Illegal Undo/Redo transaction structure.
Explanation
Correction
–491
This is an internal error and should not occur during normal operations.
If this error occurs, call Customer Support.
Journal is not open.
Explanation
Correction
Error Messages
ufchjrn() or uclsjrn() is called with no journal open.
Call uopnjrn() first.
91
–492
A journal is already open.
Explanation
Correction
–493
uopnjrn is called where a journal is already open.
Call uclsjrn to close previous journal before calling uopnjrn.
Bad journal header, (is the file really a journal?)
Explanation
Correction
–494
uopnjrn is passed a file that does not have the correct header information
to be a journal.
Make sure that the file to be opened is really a journal.
FD used is not for a journal.
Explanation
Correction
–495
The FD passed to ufchjrn or uclsjrn is not the journal FD.
Pass the correct FD returned from uopnjrn to ufchjrn.
End of journal file.
Explanation
Correction
–498
ufchjrn reached the end of the current journal file.
None.
Bad journal record info.
Explanation
Correction
–601
ufchjrn has detected an inconsistency between the journal being read and
the current database.
Make sure that the database is compatible with the journal.
Bad database cache name.
Explanation
Correction
92
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Error Messages
–602
Bad file descriptor.
Explanation
Correction
–603
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Bad file name.
Explanation
Correction
–604
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
An attempt has been made to open a file differently than other
processes (check ‘FMOPNMODE’ or ‘LOGOPNMODE’).
Explanation
Correction
–605
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Internal cache manager error (non–fatal).
Explanation
Correction
–606
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
File descriptor not mapped.
Explanation
Correction
Error Messages
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
93
–607
The file descriptor is already mapped.
Explanation
Correction
–701
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Invalid segment Size.
Explanation
Correction
–702
An attempt has been made to specify a segment size that is not a power
of two (1, 2, 4, 8, ...). This is an internal error and should not occur in the
normal execution of the database.
If this error occurs, please call Customer Support.
No segments in volume/database.
Explanation
All volumes in the database, or all volumes in a table preference list, are
full and cannot be expanded.
Correction
Possible alternatives include adding more volumes, adding more volume
preferences to the table, or changing the table’s volume preference list
from required to preferred.
Additional Help
–703
Unify DataServer: RHLI Reference
Unify DataServer: SQL/A Reference
Segment size out of bounds.
Explanation
Correction
94
An attempt has been made to specify a segment size that is either too
small or too large. This is an internal error and should not occur in the
normal execution of the database.
If this error occurs, please call Customer Support.
Error Messages
–704
Row addressibility violation (not able to compute address for row in
table).
Explanation
Correction
You have tried to add a row to table and the address of the new row is
beyond the range of addressable row identifiers for the table.
Increase the table’s segment size. The tables’s segment size is specified
when the table is created, so the table must be dropped and then
recreated. The table segment size cannot be altered for an existing table.
You can obtain the current table segment size by using the tblstats utility.
Additional Help
–800
Unify DataServer: Configuration Variable and Utility Reference
Cannot get login name.
Explanation
Correction
Additional Help
–801
The user name for accessing the remote database is not specified in the
DBUSER configuration variable, so the user name of the current user
cannot be determined. On the UNIX operating system, this error can
occur if the user ID associated with the process is not in the password file
because the user ID has been set incorrectly or the password file has been
changed or damaged. On the Windows operating system, this error can be
ignored.
On the UNIX operating system, check the setting of DBUSER. If it is
correct, ask the system administrator of the host or client machine to
check the /etc/passwd file and take corrective action.
Unify/Net Guide
Database Server: no such remote user entry.
Explanation
Correction
Error Messages
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs please call Customer Support.
95
–802
User is not known on server.
Explanation
The user attempting to access the database is not known in the password
file on the server system.
Correction
Make sure that the user name given either in the qualified database name
or in the DBUSER variable is correct. If the user name is correct but is
not in the server password file, ask the server system administrator to add
the user name to the password file.
–803
Password invalid for user on server.
Explanation
The password given for the user attempting to access the database is not
the same as the Unix password for that user on the server.
Correction
Make sure that the encrypted password is correct by using ucrypt to
regenerate the encrypted password. The encrypted password is specified
either in the qualified database name or in the DBUSER configuration
variable.
Additional Help
–804
Unify DataServer: Configuration Variable and Utility Reference
Database Server unable to assume user’s id and group.
Explanation
The attempt to set the database server process to the ID and group of the
user attempting to access the database was unsuccessful. If the master
database server is running with root privilege, this can occur only if a
system administration problem exists.
Correction
Make sure that the master database server was started with root privilege.
If so, make sure that the server machine does not have system
administration problems.
–805
Another server is already running.
Explanation
Correction
Additional Help
96
A server is already running under this server name. Or, dbdmn is started
from inetd.
If the currently running server is not the one you want to use, shut the
server down. Then start the server you want to use.
“Starting the Master Server” in the Unify/Net Guide
Error Messages
–806
Database Server unable to install signal handlers.
Explanation
Correction
–807
The initsig call has failed.
If this happens, please call Customer Support.
Database Server is in the process of being shut down.
Explanation
Correction
–808
A user has initiated the database server shutdown procedure. This
message tells other users to close the database or exit the application.
The normal response is to close the database or exit the application.
Unable to send interrupt signal to Database Server.
Explanation
–809
The kill command that sends a SIGINT to the database process has failed.
The process sending the kill and the database process are both owned by
the user attempting to access the database. Therefore the kill can fail only
if the database process no longer exists or if the process ID (which is
saved on the client) has been corrupted.
Unable to find Database Server; server name not known.
Explanation
Correction
–810
This is an internal error only and is not reported to users.
If this error occurs, please call Customer Support.
Not enough user memory to perform remote call.
Explanation
A malloc failed while allocating memory for a network communications
call data structure, or during packing or unpacking.
Correction
Check the available user memory on the host machine and try again. Try
reducing the values of configuration parameters that control the size of
process memory.
Error Messages
97
–811
Remote call failed due to trying to send bad integer data.
Explanation
Correction
–812
An integer value cannot be packed correctly. Although very unlikely, this
error can result from a corrupted value.
If this error occurs, please call Customer Support.
Remote call failed due to trying to send bad float data.
Explanation
Correction
–813
A floating-point value cannot be packed correctly. This error can result
from a corrupted value or a value that cannot be properly encoded.
If this error occurs, please call Customer Support.
Remote call failed due to an error while packing the data.
Explanation
Correction
–814
A pack error other than a bad integer or bad floating-point value has
occurred. This error can be the result of a lack of memory, an internal
error caused by a program bug, a network problem where some data has
been corrupted, or a user problem where some user data is invalid.
If this error occurs, please call Customer Support.
Unable to write to Database Server.
Explanation
Correction
–815
The database server for this client is no longer executing, or a hardware
or network problem exists.
Verify above conditions and take corrective action.
Unable to read from Database Server.
Explanation
Correction
98
The database server for this client is no longer executing, or a hardware
or network problem exists.
If the database server has stopped running, try to restart the server.
Otherwise, please call Customer Support.
Error Messages
–816
INTERNAL: Remote call failed due to bad header data.
Explanation
Correction
Not a user error, this error is probably the result of a hardware or network
problem or an internal program bug.
If this error occurs, please call Customer Support.
–817
INTERNAL: Remote call failed due to old sequence number.
Explanation
Not a user error, this error is probably the result of a hardware or network
problem or an internal program bug.
Correction
–818
Explanation
Correction
–819
If this error occurs, please call Customer Support.
INTERNAL: Remote call failed due to bad sequence number.
Not a user error, this error is probably the result of a hardware or network
problem or an internal program bug.
If this error occurs, please call Customer Support.
Remote call failed due to reading bad integer data.
Explanation
Correction
–820
An integer value cannot be unpacked correctly. This error can occur
because a value is corrupted or because the client machine supports a
smaller range of integer values than does the server machine.
If this error occurs, please call Customer Support.
Remote call failed due to reading bad float data.
Explanation
Correction
Error Messages
A floating-point value cannot be unpacked correctly. This error can occur
because a value is corrupted, or because a valid value on the server
machine cannot be represented on the client machine.
If this error occurs, please call Customer Support.
99
–821
Remote call failed due to an error while unpacking the data.
Explanation
Correction
–822
An unpack error other than a bad integer or bad floating-point value has
occurred. This error can occur because of a lack of memory, an internal
error caused by a program bug, a network problem where some data has
been corrupted, or a user problem, where some user data is invalid.
If this error occurs, please call Customer Support.
Unable to successfully close the connection with the Database Server.
Explanation
This error is probably the result of hardware or network problems.
Correction
Verify that hardware and network is working correctly. If problem
persists, please call Customer Support.
–823
Unable to connect to the Database Server.
Explanation
This error generally occurs when the server is not running on the
specified machine, or if the server is running but for some reason is not
accepting requests. This error can also result from hardware or network
problems.
Correction
Make sure that the server is running and no hardware problems or
network problems between the host and server machine exists. Try the
request after corrective action is taken. If problem persists please call
Customer Support.
–824
INTERNAL: Unable to initialize the network library.
Explanation
Correction
–825
An internal problem with the network library, this error is probably the
result of a problem with the underlying network.
If this error occurs, please call Customer Support.
INTERNAL: Unknown remote procedure call error code.
Explanation
Correction
100
This is an internal error that should not occur.
If this error occurs, please call Customer Support.
Error Messages
–826
Database Server: not enough user memory to perform remote call.
Explanation
Correction
–827
A malloc failed on the server.
Try the request at a later time. If problem persists, please call Customer
Support.
Database Server: unable to read from client.
Explanation
Correction
–828
The server cannot read a message from the client, even though the client
is still running. Although unlikely, this error can result from hardware or
network problems.
Verify that hardware and network is working correctly. If problem
persists, please call Customer Support.
INTERNAL: Database Server: remote call failed due to bad header
data.
Explanation
Correction
–829
The server cannot read a message header, probably because of hardware
or network problems.
Verify that hardware and network is working correctly. If problem
persists, please call Customer Support.
Database Server: incompatible client version.
Explanation
On the initial connection to the server, the server’s version is
incompatible with the client’s. Version numbers consist of a version,
release, and subrelease part. The version and release must be equivalent
on the client and server, and the server’s subrelease must be greater than
or equal to the client’s.
Correction
Verify that compatible versions of the software are installed on the server
and host machines. If you have questions, please call Customer Support.
Error Messages
101
–830
Explanation
Correction
–831
INTERNAL: Database Server: unknown remote procedure called.
The client has requested a network communications remote procedure
that is not known to the server. This error can result from incompatible
clients and servers (which should have been caught with version number
checking), or from hardware or network problems.
Verify that hardware and network is working correctly. If problem
persists, please call Customer Support.
Database Server: remote call failed due to an error while unpacking
the data.
Explanation
Correction
–832
As on the client, an unpacking error on the server can result from several
problems, including lack of space, corrupted data, smaller range of
integers, or inability to represent a floating-point value. The server error
log contains more information.
If this error occurs, please call Customer Support.
Database Server: remote call failed due to an error while packing the
data.
Explanation
Correction
–833
As on the client, a packing error on the server can result from several
problems, including lack of space or corrupted data. The server error log
contains more information.
If this error occurs, please call Customer Support.
INTERNAL: Database Server: unknown remote procedure call error
code.
Explanation
Correction
102
This is an internal error and should not occur.
If this error occurs, please call Customer Support.
Error Messages
–834
The server name is not registered with the system.
Explanation
The server cannot find the server name. In a TCP/IP network, this means
that the server name is not known on the server system; that is, the server
name is not in the /etc/services file or is not known to the yellow pages.
Correction
Make sure that the installation instructions for identifying the Unify/Net
server were followed. Also make sure that the port number is unique on
the server machine.
–838
No connection available on client.
Explanation
Correction
The client has exhausted the table of network connections. This can
happen if client applications are not correctly cleaning up network
connections on exit or if too many client applications are running.
Try one or more of the following solutions:
Stop some client applications.
Exit and restart Windows.
Reconfigure your network software to allow for more connections.
Reboot the system.
Error Messages
103
–1001
The specified lock kind is not allowed in the specific transaction.
Explanation
Correction
–1002
An attempt has been made to place a lock against a transaction which
does not allow the requested lock type. For example, an exclusive or
write lock (UXLCK) may not be placed against a read-only (UTXTYPE0)
transaction.
Make sure that the lock kind and transaction type are compatible.
INTERNAL: Lock manager initialization failure.
Explanation
Correction
–1003
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Unable to grant lock request; object locked by another user.
Explanation
Correction
–1004
A lock request has timed out because another transaction is holding a
conflicting lock.
Try the operation again later.
INTERNAL: Request was not a demotion request.
Explanation
Correction
–1005
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Requested object not locked.
Explanation
Correction
Error Messages
A request was made to unlock an object which was not locked by the
transaction.
Either ignore the message since the object was already unlocked or make
sure that the unlock request was issued against the same transaction as
the corresponding lock request.
104
–1006
INTERNAL: Transaction has no locks.
Explanation
Correction
–1007
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Lock granted due to upper level lock.
Explanation
Correction
–1008
This is an advisory message indicating that a lock was granted because
the transaction already holds an enclosing upper level lock. For example:
requesting a row lock while a table lock is already held on the table to
which the row belongs.
No correction needed.
INTERNAL; Lock not granted – conflict upper lock.
Explanation
Correction
–1009
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Unlock request not allowed in type 2 transaction.
Explanation
Correction
–1101
An attempt was made to release a lock held by a type 2 transaction. The
only way to release locks held by a type 2 transaction is to commit or
abort the transaction.
Commit or abort the current type 2 transaction.
Bad bucket address.
Explanation
Correction
Error Messages
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
105
–1102
Invalid primary bucket ID.
Explanation
Correction
–1103
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Hash table bucket cache is full.
Explanation
Correction
–1104
There are not enough hash table bucket buffers to complete a hash table
operation.
Increase the value of the configuration variable NBUCKET.
Duplicate key (unique hash table).
Explanation
Correction
–1105
A duplicate key value is being inserted into a unique-key hash table. The
user may also see error –155 (the UEDUPK error code), indicating the
violation of a uniqueness constraint in general (not hash table specific).
The hash table key value may not be used. Choose another key value.
Cannot create unique hash table on object.
Explanation
An index may not be created on the specified column(s) because there are
exception rows. For hash tables, an attempt has been made to create a
unique hash index on a column where some rows have duplicate values.
Correction
Identify the rows causing the exception and modify them. For hash
tables, delete or modify rows with duplicate key values. For link indexes,
add parents for orphan children, delete orphan children, or change the
value of orphan children.
–1106
Routine failure (underlying error).
Explanation
Correction
106
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Error Messages
–1107
Hash table already exists.
Explanation
Correction
–1108
A hash index already exists on the column or group of columns.
The existing hash index must be dropped with udrphsh0 before a new
one can be created. Use the umodhsh0 function to modify the hash
index.
Key already exists in hash table.
Explanation
Correction
–1109
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Hash table cannot be enlarged.
Explanation
Correction
–1110
The hash index has reached the maximum size and cannot grow any
larger. This is an internal error and should not occur in the normal
execution of the database.
If this error occurs, please call Customer Support.
INTERNAL: No empty bucket cache buffers.
Explanation
Correction
–1111
This is an internal error and should not occur in the normal execution of
the database. See error –1103 (the UE_BKTCHFL error code) for more
information.
If this error occurs, please call Customer Support.
No hash table with specified ID.
Explanation
Correction
Error Messages
The specified hash index ID is not an ID for an existing hash table index.
Either the operation should be performed before the hash index is
dropped, or name binding should be used to get the ID for the desired
hash index.
107
–1112
INTERNAL: Key not found.
Explanation
Correction
–1113
A duplicate key value is being inserted into a unique-key hash table. The
user may also see error –194 (the UENOROW error code), indicating an
invalid Row ID in general (not hash table specific). This is an internal
error and should not occur in the normal execution of the database.
If this error occurs, please call Customer Support.
REKEY failed.
Explanation
Correction
The hash index rekey process failed.
Make sure the database release bin directory is included in the PATH
environment variable and that the rekey executable is in the release bin
directory. Make sure that no rekey executable is on the PATH before the
rekey in the bin directory.
Another possibility is that there were too many processes active. Reduce
the number of processes and try rekey again.
–1114
INTERNAL: Split condition – internal hash table code.
Explanation
Correction
–1115
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
INTERNAL: Hash code ‘‘0’’.
Explanation
Correction
–1201
This is an internal error and is not reported to users.
If this error occurs, please call Customer Support.
Incorrect number of arguments for BLDBI.
Explanation
Correction
108
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Error Messages
–1202
Bad B-tree column’s options in B-tree header.
Explanation
Correction
–1203
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Bad key definition, invalid column ID.
Explanation
Correction
–1204
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
The column specified as the primary key is not part of the table.
Explanation
Correction
–1205
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Bad dynamic portion of B-tree header.
Explanation
Correction
–1206
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Bad key definition, invalid column value length.
Explanation
Correction
Error Messages
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
109
–1207
Bad B-tree column rank in B-tree header.
Explanation
Correction
–1208
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Bad B-tree file name.
Explanation
There is an insufficient amount of memory to allocate space for the
B-tree file name, or the desired B-tree file name is an invalid length, or
the database is closed
Correction
Verify that the database is open, the B-tree file exists, and the specified
B-tree file name is valid. Retry the operation.
–1209
Bad B-tree options in B-tree header.
Explanation
Correction
–1210
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Duplicate key found in No duplicate B-tree.
Explanation
Correction
–1211
An attempt has been made to insert a duplicate key into a B-tree that does
not allow duplicates. This row must already exist in the B-tree.
You cannot add the duplicate key into the B-tree. If you want to add this
duplicate key, you must rebuild the B-tree, allowing duplicates.
The‘BLDBI’ executable has abnormally terminated, probably
because of a signal.
Explanation
Correction
110
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Error Messages
–1212
Bad gett of B-tree row.
Explanation
Correction
–1213
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Bad gett of B-tree columns row.
Explanation
Correction
–1214
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Bad B-tree ID in B-tree header.
Explanation
Correction
–1215
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Keygroup load failed.
Explanation
Correction
–1216
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Unable to load key group.
Explanation
Correction
Error Messages
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
111
–1217
Seek into B-tree file fails.
Explanation
Correction
–1218
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
B-tree mapping failed.
Explanation
Correction
–1219
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
B-tree Manager exact match rid and key–value.
Explanation
Correction
–1220
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
An attempt has been made to create a btree index with too many
component columns.
Explanation
Correction
–1221
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Bad key definition, invalid key length.
Explanation
Correction
112
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Error Messages
–1222
B-tree index file does not exist.
Explanation
Correction
–1223
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
bldbi not invoked.
Explanation
Correction
The B-tree index bldbi process was not successfully invoked.
Make sure the database release bin directory is included in the PATH
configuration variable and that the bldbi executable is in the release bin
directory. Make sure that no bldbi executable is on the PATH before the
bldbi in the release bin directory.
Another possibility is that there were too many processes active. Reduce
the number of processes and try again.
–1224
B-tree file cannot be opened.
Explanation
Correction
–1225
A B-tree index file cannot be opened for scanning or information.
Reduce the number of open files.
B-tree manager key value not found.
Explanation
Correction
–1226
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Bad nxrow of B-tree row.
Explanation
Correction
Error Messages
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
113
–1227
Bad nxrow of B-tree columns row.
Explanation
Correction
–1228
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Reading B-tree file fails.
Explanation
Correction
–1229
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Bad B-tree file header write.
Explanation
Correction
–1230
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
B-tree manager cannot set to parent’s environment.
Explanation
Correction
–1231
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
B-tree manager cannot open database.
Explanation
Correction
114
An attempt has been made by the B-tree index manager to open a B-tree
index file that does not exist, or does not have valid read/write
permissions. This is an internal error and should not occur in the normal
execution of the database.
If this error occurs, please call Customer Support.
Error Messages
–1232
B-tree manager cannot get child information.
Explanation
Correction
–1233
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
B-tree manager cannot open as parent in child process.
Explanation
Correction
–1234
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
B-tree manager cannot reset to child’s environment.
Explanation
Correction
–1235
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
B-tree manager cannot close the database.
Explanation
Correction
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
–1271 XML parse internal error
Explanation
Correction
Error Messages
An internal error has occurred while parsing the XML.
Make sure the xml is valid and call uXMLGetErrorInfo to get detailed
message.
115
–1272 I nvalid XML
Explanation
Correction
Invalid XML; the XML is either not wellformed or is invalid.
The XML is not well formed. Make sure the structure of XML follows
the XML standard.
–1273 General Exception
Explanation
Correction
General error thrown during XML processing by XML Parser.
Call uXMLGetErrorInfo to get a detailed message.
–1274 I nvalid argument
Explanation
Correction
Invalid argument. One of the required arguments passed to the function is
null.
Verify the required argument value is not NULL.
–1275 No childs of current node
Explanation
Correction
The current element does not have a child element .
Make sure that the current node is not the leaf node before calling the
function to access the child of this element.
–1276 Node is not an element
Explanation
Correction
116
The current node is not an element.
Make sure that current node is a valid element .
Error Messages
–1277 Can only select column vals
Explanation
Invalid projected column for XML. A system function, such as
LOGNAME, or ROWID cannot be specified in the SELECT statement.
Correction
Correct the syntax.
–1278 Node not found
Explanation
Correction
The specified node cannot be found.
Verify that the argument name that identifies the node is correct.
–1279 Binary xml output not allowed
Explanation
Correction
BINARY output is invalid with AS XML. You can’t specify INTO
BINARY <filename> with AS XML.
Correct the syntax.
–1280 Can’t UNION different XML fmt
Explanation
Correction
Can’t UNION different XML formats.
All SELECT statements in a UNION must have the same XML format,
that is, they must all be XML AUTO or XML RAW.
–1281 XML file not found
Explanation
Correction
Error Messages
The specified xml file does not exist. (#)
The file or specified path does not exist. Make sure the file name and
path specified are correct.
117
–1282
XML exception
Explanation
Correction
Error in initializing the XML Parser.
Check the XML. Call uXMLGetErrorInfo to get a detailed message.
–1283 No Node Value
Explanation
Correction
The node does not have any value.
Make sure that node is valid before making modification or deletion.
–1284 No Siblings
Explanation
Correction
The current element does not have a sibling.
Make sure that current node has siblings before calling the function.
–1285 NO Parent Node
UENOPELM
Explanation
Correction
The node does not have a parent node. i.e. the pointer (#).
Make sure that the current node is not be the root node.
–1286 No Attribute Found
Explanation
Correction
118
A valid attribute could not be found by this name.
Make sure that the name supplied to the function represents a valid
attribute.
Error Messages
–1301
Cannot close if domain checking off.
Explanation
Correction
–1302
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
The column value has failed the required domain check.
Explanation
Correction
Additional Help
–1303
The value provided for a field in an insert or update operation does not
fall into any of the ranges of values allowed by the Data Integrity
Subsystem (DIS).
Change the provided value to a legal value or change the DIS valid
values.
Unify DataServer: Configuration Variable and Utility Reference
Conversion error.
Explanation
Correction
–1304
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Configuration variable Bad format.
Explanation
Correction
–1305
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Configuration variable not found.
Explanation
Correction
Error Messages
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
119
–1307
Invalid default type.
Explanation
Correction
–1308
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
No current row for CROW type default.
Explanation
Correction
–1309
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
No current row for ‘column type’ default.
Explanation
Correction
–1310
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
No default for this column.
Explanation
Correction
–1311
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
The ‘binary’ data type is not a supported DIS data type.
Explanation
An attempt was made to define a DIS default or domain constraint on a
BINARY column.
Correction
Additional Help
120
Remove the entry for the BINARY column from the DIS source file.
Unify DataServer: Configuration Variable and Utility Reference
Error Messages
–1312
The ‘byte’ data type is not a supported DIS data type.
Explanation
An attempt was made to define DIS default or domain constraint on a
BYTE column.
Correction
Remove the entry for the BYTE column from the DIS source file.
Additional Help
Unify DataServer: Configuration Variable and Utility Reference
–1313
The ‘text’ data type is not a supported DIS data type.
Explanation
An attempt was made to define DIS default or domain constraint on a
TEXT column.
Correction
Remove the entry for the TEXT column from the DIS source file.
Additional Help
Unify DataServer: Configuration Variable and Utility Reference
–1314
A column not specified in the column list has failed the required
domain check.
Explanation
Correction
–1376
When performing an INSERT with some of the columns not specified,
one of these columns which was not provided a value violated a DIS
domain constraint.
Provide values for all of the required columns.
Unable to access configuration source file (i.e. ‘file.cf’) typically due
to inadequate operating system resources or permissions.
Explanation
Correction
Error Messages
An error occurred while trying to access a configuration source file.
Check the errlog file for the name of the configuration file that generated
the error, and for more information on the nature of the error. Look for
–1376 in errno field.
121
–1377
Unable to access compiled configuration source file (i.e. ‘file.cfg’)
typically due to inadequate operating system resources or
permissions.
Explanation
Correction
–1378
An error occurred opening the compiled configuration source file.
Make sure you are accessing the correct database and that you have read
permission on the compiled configuration source file.
Error initializing configuration.
Explanation
Correction
–1379
Fatal internal error initializing configuration.
If this error occurs, please call Customer Support.
Configuration not initialized.
Explanation
Correction
–1401
Attempt to use a config variable before config is initialized.
If this error occurs, please call Customer Support.
Bad selection criteria.
Explanation
Correction
–1402
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Illegal test for value type.
Explanation
Correction
122
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Error Messages
–1403
Test requires a value.
Explanation
Correction
–1404
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Selection table full.
Explanation
Correction
–1501
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
The schema name is invalid.
Explanation
Correction
–1502
The current schema cannot grant itself privileges.
Change schemas and try the operation again.
Bad descriptor parameter.
Explanation
Correction
–1503
The UGRNTDS descriptor contains an invalid object or capabilities. This
is an internal error and should not occur in the normal execution of the
database.
Check the descriptor for a valid object and capabilities and retry the
operation. If this error occurs, please call Customer Support.
Duplicate user name.
Explanation
Correction
Error Messages
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
123
–1504
Duplicate schema.
Explanation
Correction
–1505
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Error in getting defid for cache.
Explanation
Correction
–1506
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
No schema for this ID.
Explanation
The specified schema ID does not exist or is not permitted to be seen.
Correction
If the schema is known to exist, your current schema may not be
permitted to see this schema. Assume another schema and try again.
–1507
Has no privilege to grant privileges.
Explanation
Correction
–1508
The current schema does not own the object that privileges are being
requested for.
Assume a schema that owns the object and retry.
Grantee does not exist.
Explanation
Correction
124
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Error Messages
–1509
Cannot find grantor.
Explanation
Correction
–1510
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Object does not exist.
Explanation
Correction
–1511
The specified object does not exist or is not permitted to be seen.
If the object is known to exist, your current schema may not be permitted
to see this object. Assume an schema that owns the object and try again.
No permissions.
Explanation
Correction
–1512
The current user or current schema does not have permission to perform
the desired operation.
Assume another schema and attempt the operation again.
Privilege does not exist.
Explanation
This message displays in the following cases:
the current schema is not permitted to see the specified objects
the current schema cannot add or drop desired permissions
DBA authority is required to run this utility, as is the case for budb
Correction
–1513
Move to the schema that owns the object and retry. Or make sure you
have DBA authority before trying to run the utility.
Unknown or missing user ID (has user been dropped?).
Explanation
Correction
Error Messages
Desired user does not exist in database.
Add the desired user.
125
–1514
Error in updating defid for cache.
Explanation
Correction
–1515
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Unknown object type.
Explanation
Correction
–1516
The specified object type is unknown to the database.
Check the object type and specify a known database type.
Invalid user name.
Explanation
Correction
–1517
The user name is invalid or when granting privileges, the privilege
already exists for specified user.
Verify that the password file on your system has the appropriate read
permissions.
Unknown operation.
Explanation
Correction
–1518
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Unknown privileges for object.
Explanation
Correction
126
The specified privilege is not valid for desired object.
Change the specified privileged to a valid privilege for the desired object.
Error Messages
–1519
Privileges cannot be granted/revoked or verified on a column group.
Explanation
The column specified is a column group. Privileges cannot be granted or
revoked on this column, nor can this column be specified in a
UNIPCOLL structure.
Correction
Replace the column group with all the columns that make up the column
group.
Additional Help
–1520
Unify DataServer: RHLI Reference
The software version does not match the shared memory version.
Explanation
The software which created the shared memory was not the same version
as the current software.
Correction
Make sure that the correct release of the database software is being used.
–1521
Cannot drop PUBLIC schema.
Explanation
Correction
–1522
The schema specified is the PUBLIC schema and it cannot be dropped.
Verify the name of the schema you want to drop.
Only SELECT privilege allowed on Views.
Explanation
Correction
Additional Help
–1523
The privilege specified is not allowed on Views.
Use the SELECT privilege and retry.
Unify DataServer: SQL/A Reference
Only SELECT privilege allowed on columns in a View Table.
Explanation
Correction
Additional Help
Error Messages
The privilege specified is not allowed on a View Table or on a column in
a View Table.
Use the SELECT privilege and retry.
Unify DataServer: SQL/A Reference
127
–1586
Can’t truncate a table that is a child in a link index.
UETTLINK
Explanation
Correction
–1587
Explanation
Correction
–1588
A truncate table operation cannot be performed on a table that is a child
in a link index.
Drop the link index if possible.
TRUNCATE cannot be mixed with other DML or DDL operations.
UETTDML
A truncate table operation must be performed within its own transaction.
The current transaction must be committed.
Can’t roll back a truncate operation in this release.
UETTRLBK
Explanation
Correction
–1589
A transaction that contains a truncate table operation cannot be rolled
back.
The current transaction must be committed.
Can’t truncate a table with old–style btree (.idx) files.
UETTBIDX
Explanation
Correction
–1601
A table that uses B–trees from before release 6.0 cannot be truncated.
The B-tree must be dropped before the table can be truncated.
Object name is ambiguous or multiply defined.
Explanation
Correction
–1602
The name passed to a name binding function was ambiguous. It could
refer to more than one object.
Use a more fully qualified name.
Invalid name (Name not supplied or name contains reserved
characters).
Explanation
Correction
128
The database object name specified included reserved characters or was
of zero length.
Correct the object name.
Error Messages
–1603
Unable to parse the name, too many delimiters.
Explanation
Correction
–1604
A database object name specified contained too many delimiters.
Correct the object name.
Name does not exist.
Explanation
Correction
–1605
There is no database object with the supplied name.
Verify the correct name of the object being referenced.
Duplicate database object name.
Explanation
Correction
–1606
An attempt was made to add a duplicate database object name.
Choose a different object name to use.
Invalid name length (too long).
Explanation
Correction
–1690
An object’s name is too long.
Choose a shorter object name to use.
Cannot truncate a table when rows exist in a child table. (#)
Explanation
Correction
Error Messages
Only tables that are a parent in a link index with no children can be
truncated..
The table cannot be truncated unless you delete all child rows, or truncate all
child tables, first.
129
–1701
A Bad scan (or ordered access) test operator was supplied.
Explanation
Correction
Additional Help
–1702
This error occurs when an invalid comparison operator is supplied to the
RHLI uinsor function. Usually this is an attempt to use a pattern match
operator (UNOTGLOB, UGLOB, ULIKE or UREGEXP) with an
incompatible data type.
UNOTGLOB, UGLOB, ULIKE are only allowed with U_STR or U_VTXT
columns. UREGEXP is only allowed with U_STR columns.
Unify DataServer: RHLI Reference
A Bad scan test value was supplied.
Explanation
Correction
Additional Help
–1703
This error occurs when an invalid comparison value is supplied to the
RHLI uinsor function. Usually, the wrong number of values was
supplied.
The unary operators (UISNULL, UNOTNUL) require (UDBVAL *)0 for
both values, val1 and val2. The binary operators (UEQTST, UNETST,
UGETST, etc.) require a value for val1 and (UDBVAL *)0 for val2. The
range operators (URNGOO, URNGOC, etc.) require a value for both
values, val1 and val2.
Unify DataServer: RHLI Reference
Bad access type attempted.
Explanation
Correction
–1704
Either a scan ID was specified to an ordered access function or an ordered
access ID was specified to a scan function.
Specify the appropriate ID for the scan or ordered access function.
No supporting access method.
Explanation
Correction
130
An ordered access was attempted that references columns that do not
have a supporting access method. Supporting access methods for ordered
accesses are B-trees or direct keys.
Add the supporting access method to the specified columns.
Error Messages
–1801
The resulting string has been truncated.
Explanation
Correction
–1802
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
The resulting string has overflowed the display format.
Explanation
Correction
–1803
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
The date value to format represents an invalid date.
Explanation
Correction
–1804
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
The input string is invalid for the given data type.
Explanation
Correction
–1805
The ASCII value provided for conversion to a database type is not valid
for the specified type. For example: non-numeric characters for a
numeric column.
Either provide a valid ASCII value or change the destination type to
something that will allow the data provided.
Invalid data type was specified.
Explanation
Correction
Error Messages
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
131
–1807
C printf() style formats are not supported for CURRENCY values.
Explanation
Correction
–1851
Use a Unify style of printing instead.
The stored procedure compile failed.
Explanation
An error in the stored procedure text prevented the stored procedure from
compiling. Secondary messages will outline the exact statement that is
failing.
Correction
Use the information in secondary messages to find the problem statement
and correct the syntax or semantic error and then recompile the stored
procedure.
–1852
Explanation
Correction
–1853
Explanation
Correction
–1854
Explanation
Correction
132
The C printf() style of display is not supported for the CURRENCY data
type values.
The stored procedure compiler executable could not be run.
The stored procedure compiler (spcpl) could not be found.
Make sure that spcpl is on your path and has the correct execute
permissions.
The stored procedure compiler was terminated due to a signal.
The stored procedure compiler (spcpl) was terminated due to a signal.
Compiling some stored procedures may take some time. Allow the stored
procedure compiler to complete the compile.
The spcpl executable aborted abnormally.
The stored procedure compiler aborted while processing your 4GL.
Check for a core file and obtain a stack trace. Forward this information to
Customer Support.
Error Messages
–1855
Explanation
Correction
–1856
The spcpl executable encountered an internal error.
This error should not occur in the normal compiler execution.
If this error occurs, please contact Unify Customer Support.
A conversion error occurred while converting the return value.
Explanation
An error occurred when the stored procedure tried to return a value to the
calling function. For example, this error would occur if a stored
procedure was declared as a char(10), but a numeric value was returned.
Correction
Check the types of the stored procedure definition and the return
statement. This error will also occur if you try to return an UNDEFINED
value.
–1857
Explanation
Correction
–1858
Explanation
Correction
–1859
A conversion error occurred while converting a result value.
An error occurred when the stored procedure tried to return one of the
RESULT parameters to the calling function.
Make sure that the types of the RESULT parameters are compatible with
the type specified when the stored procedure was created. This error will
also occur if you have a RESULT parameter set to UNDEFINED on return
from the procedure.
A conversion error occurred while converting an input value.
One of the input values could not be converted to the appropriate data
type.
Check the call to the stored procedure against the definition of the stored
procedure.
The stored procedure or trigger p-code appears invalid.
Explanation
The p-code associated with the stored procedure does not have the
correct format.
Correction
Try to drop and recreate the stored procedure or trigger. If this fails,
contact Unify Customer Support.
Error Messages
133
–1860
Explanation
Correction
–1861
Explanation
The stored procedure that you are trying to execute has exceeded the
maximum nesting level for stored procedures as defined by the
SPMAXNEST configuration variable.
If you are using stored procedures recursively, make sure that you do not
have a coding error that causes the stored procedure to recurse
indefinitely. If no such error exists, you may need to increase the value of
SPMAXNEST.
Transaction aborted due to excessive trigger nesting.
The database operation that you attempted has caused the trigger nesting
level defined by the TRIGGERMAXNEST configuration variable to be
exceeded. The entire transaction has been rolled back.
Correction
If you are using recursive triggers, make sure that you do not have a
coding error that causes the trigger to recurse indefinitely. If no such
error exists, you may need to increase the TRIGGERMAXNEST value.
–1862
The stored procedure static SQL statements cannot be prepared.
Explanation
The stored procedure that you are trying to execute cannot be executed
because the schema that owns the stored procedure can no longer prepare
the SQL statements in it. For example, a table may have been dropped or
a permission may have been revoked.
Correction
Make sure that the schema can execute the static statements in the stored
procedure. Once this schema executes the stored procedure, you will be
able to execute the stored procedure again. Alternatively, rewrite the
stored procedure to use dynamic statements.
–1863
134
Stored procedure nesting level exceeded.
Transaction aborted due to failure to prepare trigger SQL
statements.
Explanation
The database operation that you have attempted has tried to execute a
trigger that contains a static statement that could not be prepared. For
example, a table may have been dropped or a permission may have been
revoked.
Correction
Make sure that the schema can execute the static statements in the trigger.
Alternatively, rewrite the trigger to use dynamic statements.
Error Messages
–1864
Explanation
Correction
–1865
Explanation
Correction
–1866
Explanation
Correction
There is no stored procedure with this name.
An attempt was made to execute a stored procedure that does not exist.
Verify the spelling of the stored procedure name or create a stored
procedure with the indicated name.
A database table cannot be used in an EXECUTE statement.
An attempt was made to EXECUTE a table.
Use SELECT to get the data from the table, or use EXECUTE to execute
a stored procedure.
One or more of the trigger types already exist.
An attempt was made to create a trigger, and one or more of the trigger
operations already has a trigger. For example, if an AFTER DELETE
trigger already exists and you try to create a trigger for AFTER UPDATE
and AFTER DELETE, you will get this error.
Drop the conflicting trigger and then recreate the trigger. To determine
which triggers exist for a specific table, you can use the following
command:
dumpdd –t table_name
–1901
The database root volume (i.e. ’file.db’) cannot be accessed.
Explanation
Correction
Additional Help
Error Messages
Unify DataServer cannot open the database root volume.
Make sure that the DBPATH and DBNAME configuration variables are set
correctly. Make sure that you have the required operating system
permissions on the file.
Unify DataServer: Configuration Variable and Utility Reference
135
–1902
The database text/binary file (i.e. ’file.dbv’) cannot be accessed.
Explanation
Correction
Additional Help
–1903
Unify DataServer cannot open the text/binary data file.
Check the errlog file to determine the full name of the file. Make sure
that the DBVFILE configuration variable is set correctly. Make sure that
you have the required operating system permissions on the file.
Unify DataServer: Configuration Variable and Utility Reference
The database physical log file (i.e. ’file.pl’) cannot be accessed.
Explanation
Correction
Additional Help
–1904
Unify DataServer cannot open the physical log file.
Make sure that the PHYFILE configuration variable is set correctly. Make
sure that you have the required operating system permissions on the file.
Unify DataServer: Configuration Variable and Utility Reference
The database transaction log file (i.e. ’file.lg’) cannot be accessed.
Explanation
Correction
Additional Help
–1905
Unify DataServer cannot open the transaction log file.
Check the errlog file to determine the full name of the file. Make sure
that the LOGFILE is set correctly. Make sure that you have the required
operating system permissions on the file.
Unify DataServer: Configuration Variable and Utility Reference
The database compiled DIS file (i.e. ’file.dis’) cannot be accessed.
Explanation
Correction
Additional Help
136
Unify DataServer cannot open the compiled DIS file.
Check the errlog file to determine the full name of the file. Make sure
that the DISFILE is set correctly. Make sure that you have the required
operating system permissions on the file.
Unify DataServer: Configuration Variable and Utility Reference
Error Messages
–1906
The database compiled schema file (i.e. ’file.sch’) cannot be accessed.
Explanation
Correction
Additional Help
–1907
Unify DataServer cannot open the compiled schema file.
Check the errlog file to determine the full name of the file. Make sure
that the SCHFILE configuration variable is set correctly. Make sure that
you have the required operating system permissions on the file.
Unify DataServer: Configuration Variable and Utility Reference
The database backup device/file (i.e. ’file.bu’) cannot be accessed.
Explanation
Correction
Additional Help
–1908
Unify DataServer cannot open the backup device.
Check the errlog file to determine the full name of the file. Make sure
that the BUDEV configuration variable is set correctly. Make sure that you
have the required operating system permissions on the file.
Unify DataServer: Configuration Variable and Utility Reference
The database compiled config file (i.e. ’file.cfg’) cannot be accessed.
Explanation
Correction
Unify DataServer cannot open the compiled configuration file.
Check the errlog file to determine the full name of the file. Make sure
that the CFGFILE is set correctly. Make sure that you have the required
operating system permissions on the file.
Additional Help
Unify DataServer: Configuration Variable and Utility Reference
–1909
The database message file (i.e. ’file.msg’) cannot be accessed.
Explanation
Correction
Additional Help
Error Messages
Unify DataServer cannot open the message file.
Check the errlog file to determine the full name of the file. Make sure
that the OPMSGDEV configuration variable is set correctly. Make sure
that you have the required operating system permissions on the file.
Unify DataServer: Configuration Variable and Utility Reference
137
–1910
The database state file (i.e. ’file.dbs’) cannot be accessed.
Explanation
Correction
–1911
Unify DataServer cannot open the state file.
Check the errlog file to determine the full name of the file. Make sure
that DBSFILE configuration variable is set correctly. Make sure that you
have the required operating system permissions on the file.
A database text/binary user data file cannot be accessed.
Explanation
Correction
–1912
A file passed to an RHLI function such as uinsrow or ufchrow as a
variable length data buffer cannot be accessed.
Check the errlog file to determine the full name of the file. Make sure
that you have the required operating system permissions on the file.
A database non-root volume cannot be accessed.
Explanation
Correction
–1913
Unify DataServer cannot open a non-root volume.
Check the errlog file to determine the full name of the non-root volume
file. Make sure that you have the required operating system permissions
on the file.
A database B-tree index file cannot be accessed.
Explanation
Correction
138
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Customer Support.
Error Messages
–1951
Database is in the process of being shut down using shutdb utility.
Explanation
Correction
Additional Help
–1952
A user has initiated the database shut down procedure using the shutdb
utility. This message informs other users to close the database or to exit
the application.
The normal response is to close the database or exit the application. If the
shutdb operation was inadvertently terminated by a user, however, the
database state can be reset using the command: shutdb –Oreset.
Unify DataServer: Configuration Variable and Utility Reference
Database is not in correct state to be reset.
Explanation
Correction
Additional Help
–1953
The attempt has been made to reset the database state to down with the
shutdb –Oreset command. The database state is currently either up or
down.
To determine the current state of the database, use the Unix file command
on the file.dbs database file, or use the startdb or shutdb utilities.
Unify DataServer: Configuration Variable and Utility Reference
Only the database creator may use this utility.
Explanation
Correction
Additional Help
Error Messages
The configuration variable OWNERSTART is set to TRUE and a user who
is not the database creator attempted to use the startdb or shutdb utility.
Contact the database creator to execute the startdb or shutdb utility
desired. Otherwise, change the OWNERSTART configuration variable to
FALSE.
Unify DataServer: Configuration Variable and Utility Reference
139
–1954
The startdb utility has not yet been used to start up the database.
Explanation
Correction
Additional Help
–1955
The configuration variable AUTOSTART is set to FALSE, which means that
the startdb utility must be used to start up the database. An attempt has
been made to start up the database with some utility other than startdb.
Changing the AUTOSTART configuration variable value to TRUE will
allow any utility to start up the database automatically. Otherwise, the
startdb utility should be used to start up the database.
Unify DataServer: Configuration Variable and Utility Reference
The database is in the process of being shut down or started up.
Explanation
An attempt has been made to execute either the startdb or the shutdb
utility while another user is executing one of those utilities. Concurrent
database start up or shut down is not allowed.
Correction
Find out who is shutting down or starting up the database so that your
actions can be synchronized. Setting the OWNERSTART configuration
variable value to TRUE will help prevent this type of conflict.
Additional Help
–1956
Unify DataServer: Configuration Variable and Utility Reference
Database daemon cannot be terminated since process is not the
“owner”.
Explanation
An attempt has been made to use the shutdb utility to terminate the
database daemons. However, the user executing the utility does not have
Unix permission needed to shut down the daemons. Therefore, the
daemons cannot be terminated and the shutdb utility exits.
Correction
The user who initially started up the database is the only Unix user who
may run the shutdb utility to terminate the daemons. Have this user
execute the shutdb utility. To determine the name of the user who
initially started up the database, use the Unix ps command to display the
user name of the database daemons.
Additional Help
140
Unify DataServer: Configuration Variable and Utility Reference
Error Messages
–1957
Database state file is old. Run the ’dbs34–35’ utility on the database.
Explanation
The version of the database state file does not correspond to the version
of the software.
Correction
Convert the database state file by using the dbs34–35 utility.
Additional Help
ACCELL/SQL: Upgrading Release 1 Applicatons document.
–1958
Database cannot be opened on this machine.
Explanation
Correction
Error Messages
The database was created on another machine or the database is
associated with another machine through the dbs34–35 utility.
If possible, run your application on the machine associated with the
database. Alternatively, move your database to the appropriate machine.
141
–2000
Ambiguous match error.
Explanation
A cursor name has been specified which is the same as other cursors in
different source files.
Correction
Qualify the name of the cursor with the source file name in which the
cursor is declared.
–2001
Syntax error in SQL statement.
Explanation
Correction
–2002
The statement being prepared has a syntax error.
Check the syntax of the statement being prepared. You can verify the
statement in its interactive form during an interactive SQL/A session.
Bad communications line number.
Explanation
Correction
–2003
An internal error has been detected. An invalid communication line
number has been specified.
If this error occurs, please call Customer Support.
The number of constants does not match the number of columns.
Explanation
The list of constants specified in the SQL/A INSERT statement does not
contain the same number of values as list of columns being inserted into.
Correction
Verify the number of elements in the constant list and the column list of
the INSERT statement.
–2004
Statement cannot be prepared.
Explanation
The SQL/A statement specified as input to the PREPARE statement
cannot be prepared.
Correction
Enter the statement in interactive mode or use a different statement.
Additional Help
142
PREPARE in Unify DataServer: SQL/A Reference
Error Messages
–2005
Query processor incompatible with client version.
Explanation
The backend query processor started by an Embedded SQL/A application
was incompatible with another active process.
Correction
Make sure that the ”SQL” executable on you path ($PATH) is
from the appropriate Unify release. Relink your Embedded SQL
application by using sqla.ld.
Additional Help
Unify DataServer: Configuration Variable and Utility Reference
–2006
Error starting transaction.
Explanation
Correction
–2007
An attempt has been made to start a new transaction while the database is
being shut down. No new transactions can be started once the database
shut down begins.
Try the application later when the database is on-line again.
Too big a string for substitution.
Explanation
If this error occurs while opening a cursor, then the query text cannot fit
in the buffer whose size is controlled by the value of the configuration
variable MXQRYTXT.
If this error occurs for a FETCH operation, then the host variable size is
not large enough.
Correction
Error Messages
If the error occurred because the OPEN CURSOR operation failed,
modify the MXQRYTXT configuration variable. Otherwise, increase the
size of the host variable into which data is being fetched and then try the
application again.
143
–2008
SELECT INTO fetched more than one row.
Explanation
The query involves an operation which requires only one row. However,
the subquery that is used for obtaining the value returns more than one
row.
Correction
Modify your query so that the subquery selects only one row or change
the operator to be one which is suitable for a multi-row return (i.e. IN
rather than “=”).
Additional Help
–2009
Unify DataServer: Writing Interactive SQL/A Queries
SET TRANSACTION locking LEVELS processing incomplete.
Explanation
This is an internal error. The SET TRANSACTION LEVEL statement
changes transaction locking levels, and passes this error to the front end
to indicate that the transaction levels have been changed.
Correction
Try to isolate the error-causing statement and notify Customer Support.
Alternatively, try other statements to accomplish the operation.
–2010
Cannot open input file.
Explanation
Correction
–2011
The input file specified in an SQL/A INSERT statement cannot be
opened.
Verify the spelling and existence of the input file in the VALUES clause
of the INSERT statement.
Communication line is not open.
Explanation
Correction
144
An internal error has been detected. An invalid communication line
number has been specified.
If this error occurs, please call Customer Support.
Error Messages
–2012
Indicator value overflow.
Explanation
Correction
Additional Help
–2013
The value being stored in the indicator variable is larger than allowed by
the data type of the indicator variable. This is most common when
working with TEXT, BINARY, and CHARACTER columns.
Change the data type of the indicator variable.
Unify DataServer: Embedding SQL/A Into C
Cannot rewind file.
Explanation
SQL/A could not successfully reset a file pointer to the beginning of the
file.
Correction
–2014
If this error occurs, please call Customer Support.
The cursor is already open.
Explanation
An attempt has been made to open a cursor that is already open.
Correction
Correct the duplicate OPEN CURSOR statement condition in the
embedded SQL/A application.
–2015
Delete aborted. All locks could not be obtained.
Explanation
All rows which were to be deleted could not be locked with an XLOCK.
The current transaction level specifies that the delete operation is to be
aborted if this situation occurs.
In general, an XLOCK cannot be obtained if either another transaction
already holds a lock (SLOCK or XLOCK) on the row or table, or the
maximum number of locks held on the database has been exceeded.
Correction
Error Messages
If locking conflicts are the cause, then retry the operation when all locks
can be obtained. If no more locks could be obtained on the database, then
configure the database to allow more locks.
145
–2016
Data type conversion error.
Explanation
Correction
–2017
The data type of the column value being retrieved is incompatible with
the data type of the associated host variable or descriptor area field.
Change the data type of the host variable or the descriptor area field.
Verify that the correct column value is being retrieved.
Data conversion error.
Explanation
Correction
This warning occurs when the data is fetched into a host variable that is
not large enough to hold the data value, and so may contain invalid data.
Correct the declaration of the host variable in the BEGIN/END
DECLARE section.
–2018
Data exception error.
Explanation
This warning occurs when the data fetched is a null value and no host
indicator variable has been explicitly declared.
Correction
Declare the corresponding indicator variable(s) in a BEGIN/END
DECLARE section. Otherwise, check the value of SQLCODE for this
error number to verify whether data is NULL or not.
–2019
Invalid format for a column.
Explanation
Correction
–2020
An invalid data format was specified in the input data file.
Check that the format of the data for the specified column and row
number in the external file is correct.
Invalid range for a column.
146
Explanation
The value specified in the input file at the given line for the given column
is too large or too small.
Correction
Check the value at that line and column in the external file. This column
value may have to be changed or the column being updated may have to
be redefined to accept this type of data value.
Error Messages
–2021
Syntax error. Expecting constant expression.
Explanation
This occurs when an INSERT statement does not specify a constant
expression for the values. For example,
INSERT INTO table VALUES (abce);
INSERT INTO table VALUES (”abcd”);
INSERT INTO table VALUES (col1 + 15);
This may also occur in the constant list operand of the IN operator. For
example,
SELECT * FROM table WHERE column IN (abcd);
SELECT * FROM table WHERE column IN (”abcd”);
UPDATE table SET column = value
WHERE column IN (”foo”, ’abc’);
Correction
–2022
Change the statement to have a constant expression. If the intention was
to provide a string constant, be sure that the string literal is quoted in
single quotes and not double quotes. Double quotes delimit identifiers in
SQL/A.
Dirty data was used in the preceding operation.
Explanation
This warning occurs when the data used in inserting or updating a table
was retrieved as dirty data. Some other user may have been updating the
particular data.
Correction
If dirty data should not be used, the application should abort the UPDATE
or INSERT command and change the transaction level for scans. Refer to
the SQL/A manuals for more information about how the SET
TRANSACTION statement can be used to control scanning and updating
of data.
Additional Help
–2023
Unify DataServer: SQL/A Reference
Error while restoring current schema.
Explanation
Correction
Error Messages
Before executing each statement, the query processor ensures that the
statement is executed in the correct schema. If it encounters any error in
restoring the correct schema, this error is the result.
Retry the application later. If problem persists, check errlog for the
corresponding log entry, which should explain the error.
147
–2024
Dynamic parameters allowed only in prepared statements.
Explanation
Correction
A dynamic parameter, represented by a question mark (?), can be used in
a prepared statement only.
Either replace the dynamic parameter with a host variable or use a
prepared statement.
Additional Help
Unify DataServer: Embedding SQL/A Into C
–2025
Invalid placement of dynamic parameter.
Explanation
Correction
Additional Help
–2026
Dynamic parameters can be used in place of host variables only.
Correct the placement of the dynamic parameter.
Unify DataServer: Embedding SQL/A Into C
Syntax error in expression.
Explanation
Correction
Additional Help
–2029
The SQL/A statement being parsed contains a syntax error.
Verify the syntax of the statement.
Unify DataServer: SQL/A Reference
Unable to fork a new process.
Explanation
Correction
–2030
A required query processor for the embedded SQL/A application could
not be started.
Modify the application to keep all unnecessary cursors closed and try
running the application later. If problem persists, call Customer Support.
A fatal system error has previously occurred. SQL/A processing
suspended.
Explanation
Correction
148
A fatal error was encountered for a previous embedded SQL/A statement.
All subsequent embedded SQL/A statements will fail until the fatal error
is resolved.
Resolve the cause of the previous fatal error.
Error Messages
–2031
Cannot group by view columns which are expressions.
Explanation
Correction
–2032
The GROUP BY clause of the SELECT statement has specified a column
in a view that is defined as an expression. View columns defined as
expressions cannot be used in a GROUP BY clause.
Rewrite the SELECT statement so that it does not use this particular
column.
GROUP BY not allowed.
Explanation
Correction
–2033
The SELECT statement contains a GROUP BY clause and the FROM
clause contains a view which also contains a GROUP BY clause, a
HAVING clause, or an aggregate function in its definition.
Rewrite the SELECT statement so that it does not use this particular view
or does not use a GROUP BY clause.
Unexpected error reading binary data file.
Explanation
Correction
–2034
An unexpected error has occurred in reading an input file (either internal
or user-supplied).
If this error occurs, please call Customer Support.
HAVING clause not allowed.
Explanation
The SELECT statement contains a HAVING clause and the FROM clause
contains a view which also contains a GROUP BY clause, a HAVING
clause, or an aggregate function in its definition.
Correction
Rewrite the SELECT statement so that it does not use this particular view
or does not use a HAVING clause.
–2035
Invalid date.
Explanation
Correction
Error Messages
The constant value specified for a column of data type DATE is invalid.
Correct the syntax of the DATE data.
149
–2036
An internal error has occurred.
Explanation
Correction
–2037
This is an internal error and should not occur in the normal processing of
an SQL/A query.
If this error occurs, please call Customer Support and report the query
that caused the error.
INSERT from file not allowed.
Explanation
An attempt has been made to use an INSERT statement with the input
data coming from an external file. Using input data from an external file
is only allowed in interactive SQL/A.
Correction
Rewrite the application to read each row from the input file and, for each
row, perform an INSERT statement.
–2038
Invalid host id syntax.
Explanation
A host variable reference in the statement is invalid. Host variables are
identifiers which begin with the “:” character.
Correction
Verify the spelling of all host variables in the statement and perform the
appropriate modifications.
–2039
Invalid number of columns.
Explanation
Correction
–2040
SQL/A has detected an internal error while updating a table.
If this error occurs, please call Customer Support.
The number of columns being inserted into does not match number
of projected columns.
Explanation
Correction
150
The number of projected columns from a subquery must not be greater
than the number of columns being inserted into a row.
Check the column references in the INSERT statement and the subquery.
Error Messages
–2041
Invalid ORDER BY column number.
Explanation
Correction
–2042
A sort column number specified in the ORDER BY clause of a SELECT
statement is not valid. Valid sort column numbers are between 1 and the
number of select expressions in the select list.
Correct the ordinal number specification.
Invalid ORDER BY specification.
Explanation
The ORDER BY clause contains a column specification which is not
projected in the select list. All columns specified in an ORDER BY clause
of a SELECT statement must be columns which are projected in the
select list.
Correction
Modify the SELECT statement to project the column(s) which are used in
the ORDER BY clause, or modify the ORDER BY clause to omit the
offending columns.
–2043
Invalid time.
Explanation
Correction
Additional Help
–2045
The constant value specified for column of data type TIME is invalid.
Correct the syntax of the TIME data.
“Working With the Data Types and Null Values” in Unify DataServer:
Writing Interactive SQL/A Queries
Invalid transaction update level.
Explanation
Correction
Additional Help
Error Messages
An invalid transaction level for update operations has been specified.
Specify a correct transaction level.
SET TRANSACTION LEVEL Unify DataServer: SQL/A Reference
151
–2046
Invalid table name.
Explanation
Correction
–2047
The table name referenced in the query specification is not known.
Check the spelling of the table name. In Interactive SQL/A, you can use
the TABLES command to find the names of all known tables.
Message too large.
Explanation
Correction
–2048
Unable to allocate amount of memory needed for communication
between the application and the query processor.
A process size or system limit may have been exceeded. Check the
console for system errors. Trying the application later may also correct
the situation.
Maximum allowed backends exceeded.
Explanation
Correction
The maximum allowed query processors does not match the maximum
number of cursors allowed to be open.
Increase the number of allowed open cursors by increasing the setting for
MXOPENCURSORS configuration variable.
Additional Help
MXOPENCURSORS in Unify DataServer: Configuration Variable and
Utility Reference.
–2049
Maximum communications lines exceeded.
Explanation
Correction
152
The maximum allowed communications lines does not match the
maximum number of cursors allowed to be open. This is an internal error
and should not occur in the normal processing of an SQL/A query.
If this error occurs, please call Customer Support.
Error Messages
–2050
Maximum open cursors exceeded.
Explanation
Correction
Additional Help
The number of cursors opened by the embedded SQL/A application has
exceeded the maximum allowed.
Check the setting of the configuration variable MXOPENCURSORS.
MXOPENCURSORS in Unify DataServer: Configuration Variable and
Utility Reference
–2052
Non-grouping column.
Explanation
Correction
The SELECT expression contains a reference to an invalid column. If a
SELECT statement contains a GROUP BY or HAVING clause, then all
references to non-outer-reference columns must be within aggregate
functions or be columns specified in the GROUP BY clause.
Rewrite the query to use a subquery or add the necessary columns to the
GROUP BY clause.
–2053
The SQL/A runtime system has not been initialized yet.
Explanation
Correction
–2056
When SQLCODE is set to this error code, no SQL/A statements have yet
been executed. This message is just informational.
None.
Unable to acquire the desired lock.
Explanation
The table specified could not be locked with the specified lock type.
An XLOCK cannot be obtained if another transaction already holds an
SLOCK or an XLOCK on the table or on any row in the table. An SLOCK
cannot be obtained if another transaction already holds an XLOCK on the
table or on any row in the table.
Error Messages
153
Another possibility is that the maximum number of locks held on the
database has been exceeded.
Correction
If locking conflicts are the cause, then retry the operation when all locks
can be obtained.
If no more locks could be obtained on the database, then configure the
database to allow more locks.
–2058
Column is not a grouping/having column.
Explanation
The SELECT expression or HAVING clause contains a reference to an
invalid column. If a SELECT statement contains a GROUP BY or
HAVING clause, then all references to non-outer-reference columns must
be within aggregate functions or be columns specified in the GROUP BY
clause.
Correction
Rewrite the query to use a subquery or add the necessary columns to the
GROUP BY clause.
–2060
Invalid cursor name; cursor does not exist.
Explanation
Correction
–2061
The cursor name used in the embedded SQL/A statement does not match
a currently allocated cursor.
Check the spelling of the name being used in the statement. Verify that
the cursor has been allocated and not subsequently deallocated.
Invalid cursor name; cursor already exists.
Explanation
Correction
An attempt has been made to allocate a cursor with the same name as an
existing allocated cursor.
If the existing allocated cursor can be used, remove the additional
ALLOCATE CURSOR statement. If a new cursor is needed, use a unique
cursor name.
154
Error Messages
–2062
Cursor not open.
Explanation
Correction
–2063
Before a FETCH, UPDATE, DELETE or CLOSE CURSOR request is
made, the required cursor must be opened.
Check the application to verify that the required cursor is opened (using
the OPEN CURSOR statement) before one of these requests is made
against it.
Not positioned to a row.
Explanation
An UPDATE or DELETE CURRENT OF CURSOR statement can only be
done after the specified cursor is opened. Opening the cursor positions
the cursor to the required row.
Correction
Check the application to verify that the UPDATE or DELETE CURRENT
OF statement is requested on a successfully opened cursor.
–2064
Invalid cursor state; cursor is active.
Explanation
Correction
–2065
A dynamic statement cannot be re-prepared while it is being used in an
active transaction.
Use a different name for the dynamic statement or close the cursor before
re-preparing its associated dynamic statement.
Not enough room in output buffer. Increase SQLPBUFSIZ.
Explanation
Correction
Additional Help
Error Messages
The size of the select list has exceeded the specified output buffer size.
Increase the size of the output buffer by increasing the setting for the
configuration variable SQLPBUFSIZ.
Unify DataServer: Configuration Variable and Utility Reference
155
–2066
Unable to establish communication with backend. Too many open
files.
Explanation
Correction
–2067
This error occurs when the system fails to open files for communication
between the application and the query processor.
Modify the application so that cursors are closed as soon as possible.
Keep files open only if they are required.
Only view table can be in the FROM clause.
Explanation
Correction
–2068
The FROM clause of a SELECT statement contains a view which
contains a GROUP BY clause, a HAVING clause, or an aggregate
function in its definition. In this case, the only table allowed in the
FROM clause is this table.
Rewrite the SELECT statement so that it does not use this particular view
or the other tables in the FROM clause.
The executable cannot be found on your path.
Explanation
Correction
Additional Help
–2070
The query processor, SQL, cannot be found on your path.
Make sure the software release bin directory is included in the PATH
configuration variable and that the SQL executable is in the this release
bin directory. Make sure that no other SQL executable is on the PATH
before the SQL located in the release’s bin directory.
Unify DataServer: Configuration Variable and Utility Reference
Error receiving message from query processor.
Explanation
Correction
156
A fatal error occurred in receiving a message from the query processor,
SQL. All operations following the statement being evaluated will return
an error indicating that a fatal error has been encountered earlier.
If this error occurs, please call Customer Support.
Error Messages
–2071
Select aborted. All locks could not be obtained.
Explanation
All rows which were to be selected could not be locked with an SLOCK.
The current transaction level specifies that the select operation is to be
aborted if this situation occurs.
In general, an SLOCK cannot be obtained if another transaction already
holds an XLOCK on the row or table, or if the maximum number of locks
held on the database has been exceeded.
Correction
If locking conflicts are the cause, retry the operation when all locks can
be obtained.
If no more locks could be obtained on the database, then configure the
database to allow more locks.
–2072
An expression cannot be compared with a literal tuple list.
Explanation
Correction
Additional Help
–2073
The query involves a comparison between an expression and a literal
tuple list. Such a comparison is invalid.
Correct the syntax of the tuple.
Unify DataServer: Writing Interactive SQL/A Queries
Aggregate function imbalance in the SELECT clause.
Explanation
Correction
–2074
The projected expressions in the SELECT clause must have the same
level of nesting for aggregate functions.
If a nested aggregate expression appears in the SELECT clause, nest all
other aggregate function references in the SELECT clause.
Aggregate functions nested too deeply in the SELECT clause.
Explanation
Aggregate functions are allowed to be at most two levels deep in a
SELECT clause.
Correction
Error Messages
Rewrite the SELECT statement so that the aggregate functions are not
nested more than two levels deep.
157
–2075
Aggregate functions may not be nested without a GROUP BY clause.
Explanation
Correction
–2076
To nest aggregate functions, you must use a GROUP BY clause.
Rewrite the SELECT statement so that the nested aggregate functions
only appear in the GROUP BY clause or remove the nested aggregate
functions.
Aggregate operators are not allowed in a SET expression.
Explanation
Correction
–2077
The right hand side of a SET clause in the UPDATE statement cannot
contain aggregate functions.
Rewrite the SET clause so that no aggregate functions appear on the right
hand side.
Aggregate functions are not allowed in the WHERE clause.
Explanation
Correction
–2078
A WHERE clause cannot contain aggregate functions.
Rewrite the SELECT statement so that the aggregate functions do not
appear in the WHERE clause.
Subquery returns more than one row.
Explanation
Correction
Additional Help
158
The query involves an operation which requires only one row. However,
the subquery that is used for obtaining the value returns more than one
row.
Modify your SQL/A query so that it only selects a single value for the
requested operation, or change the operator to be one which is suitable
for a multi-row return (IN rather than “=”).
Unify DataServer: SQL/A Reference
Error Messages
–2079
A HAVING clause cannot contain nested aggregate functions.
Explanation
A HAVING clause of a SELECT statement cannot contain nested
aggregate functions. Nested aggregates are only allowed in SELECT
expressions.
Correction
Rewrite the SELECT statement so that the nested aggregate functions
only appear in a SELECT expression or in the GROUP BY clause, or
remove the nested aggregate functions.
Error Messages
159
–2080
Invalid SQL identifier; no characters.
Explanation
Correction
Additional Help
–2081
Object name is an empty string. The object name here refers to a
statement name, a cursor name, or a descriptor area name.
Correct the name, or the host variable which contains the object name.
“Creating and Removing Database Objects” in Unify DataServer: Writing
Interactive SQL/A Queries.
Invalid SQL identifier; invalid initial character.
Explanation
Object names must start with a letter or an underscore.
Correction
Correct the name, or the name containing host variable.
Additional Help
–2082
“Creating and Removing Database Objects” in Unify DataServer: Writing
Interactive SQL/A Queries. Also refer to error message –2080.
Invalid SQL identifier; invalid body character.
Explanation
Object names can be composed only of letters (a–z, A–Z), numbers
(0–9), and underscores (_).
Correction
Correct the name, or the host variable containing the object name.
Additional Help
–2083
“Creating and Removing Database Objects” in Unify DataServer: Writing
Interactive SQL/A Queries.Also refer to error message –2080.
Invalid SQL identifier; identifier too long.
Explanation
Correction
Additional Help
160
The length of the object name depends on the associated object; most
objects have a length restriction of128 characters.
Correct the name, or the host variable containing the name.
“Creating and Removing Database Objects” in Unify DataServer: Writing
Interactive SQL/A Queries.Also refer to error message –2080.
Error Messages
–2084
Invalid column name.
Explanation
The column name does not exist in the data dictionary as specified.
If the column name has been specified as a column to be inserted into,
then the column does not exist in the table being inserted into.
Correction
–2085
Check the spelling of the column name. The COLUMNS command will
give a list of columns for a table.
The FROM clause is missing or invalid.
Explanation
Correction
Additional Help
–2086
The statement does not contain a valid FROM clause.
Check the syntax of the statement containing the FROM clause.
Unify DataServer: SQL/A Reference
Invalid GROUP BY clause.
Explanation
Correction
Additional Help
–2087
The GROUP BY clause is incorrectly used.
Verify the syntax of the clause.
Unify DataServer: SQL/A Reference
Invalid HAVING clause.
Explanation
Correction
Additional Help
–2088
The HAVING clause is incorrectly used.
Verify the syntax of the clause.
Unify DataServer: SQL/A Reference
Invalid query block.
Explanation
Correction
Additional Help
Error Messages
The SELECT statement syntax is not correct. It may have an incorrect
ordering of clauses, such as a HAVING clause before a GROUP BY
clause.
Rewrite the SELECT statement with the correct ordering of clauses.
Unify DataServer: SQL/A Reference
161
–2089
Invalid SELECT list syntax.
Explanation
Correction
–2090
The list of column names for the SELECT statement is incorrect.
Check the column names and expressions in the SELECT list.
Invalid table name in the SELECT clause.
Explanation
A table name has been referenced within a SELECT statement but it has
not been specified in the FROM clause.
Correction
Add the table name to the FROM clause. Non-unique table names must
be prefixed by the schema name.
–2091
A literal tuple contains the wrong number of items.
Explanation
Correction
–2092
Incorrect usage of the IN clause. This error occurs when the number of
constants in a literal tuple list does not match the number of value
expressions.
Correct the tuple expression.
Invalid WHERE clause.
Explanation
Correction
Additional Help
–2093
The WHERE clause is used incorrectly.
Check the syntax of the WHERE clause and the location of the WHERE
clause within the statement.
Unify DataServer: SQL/A Reference
An internal SQL/A error has occurred. Check the error log.
162
Explanation
An internal error occurred causing SQL/A has terminated abnormally due
to an internal error. The database errlog file should contain information
about the error condition.
Correction
Please refer to the errlog for information about the cause of the internal
error.
Error Messages
–2094
Aggregate function not allowed.
Explanation
Correction
–2095
View definitions may not contain aggregate functions.
Remove the aggregate function from the CREATE VIEW statement.
STRING type is required.
Explanation
When using the REGLIKE, SHLIKE, or LIKE predicates, the string
pattern following the predicate must be a string value.
Correction
Check the syntax of the string pattern. A string is delimited by single
quotation marks. You must escape quotation marks appearing in the
pattern.
–2096
Syntax error in pattern. ESCAPE character appears at the end.
Explanation
Correction
–2098
The ESCAPE character must always be followed by the character which
is being escaped. In this case, an ESCAPE character was found at the end
of the pattern string for the LIKE predicate. This violates the condition
that all ESCAPE characters must be followed by an additional character.
Correct the pattern string.
Type conversion error.
Explanation
Correction
–2100
The query is attempting to convert column data with incompatible data
types.
Convert data between compatible data types only.
Invalid transaction level specified.
Explanation
Correction
Additional Help
Error Messages
An invalid scan/update level has been specified.
Correct the specification.
Unify DataServer: SQL/A Reference
163
–2102
Unable to commit work.
Explanation
Correction
–2103
The current transaction could not be committed. The error message
following this message provides more information about how this
occurred.
Refer to the description of the last error and correct the problem.
Update aborted. All locks could not be obtained.
Explanation
All rows which were to be updated could not be locked with an XLOCK.
The current transaction level specifies that the update operation is to be
aborted if this situation occurs.
In general, an XLOCK cannot be obtained if either another transaction
holds an SLOCK or XLOCK on the row or table already, or the maximum
number of locks held on the database has been exceeded.
Correction
If locking conflicts are the cause, then retry the operation when all locks
can be obtained.
If no more locks could be obtained on the database, then configure the
database to allow more locks.
–2104
Cursor is not updatable.
Explanation
The cursor referenced in an UPDATE or DELETE statement was not
declared as an updatable cursor.
Correction
Use an updatable cursor in the UPDATE or DELETE statements. An
updatable cursor is created with a restricted form of the SELECT
statement.
–2105
Positioned statement is not operating on same table as cursor.
Explanation
Correction
164
An UPDATE or DELETE statement references a table name other than
the table name that is referenced in the DECLARE CURSOR statement
for the specified cursor name.
Use a separate updatable cursor for each table you access through an
UPDATE or DELETE statement.
Error Messages
–2106
Not enough space for variable length data.
Explanation
The value for the given TEXT or BINARY column is too large to process.
SQL/A must be able to write the variable length value to a temporary file
in the directory indicated by the UNIFYTMP configuration variable.
SQL/A must also be able to hold the entire value in memory. If either of
these fail, this error occurs.
Correction
–2107
Check for free disk space in the UNIFYTMP directory. Also check the
system console for error messages. The data file could also be loaded
using the Unify DataServer utility, dbld, which can insert TEXT and
BINARY values directly into the database and does not require temporary
storage.
Non-updatable view table.
Explanation
Correction
–2108
Update was tried on a table that is a non-updatable view.
Either recreate the view as an updatable view, or make the updates to the
base table of the view.
WHERE clause not allowed.
Explanation
Correction
–2109
A WHERE clause cannot be used when selecting from a grouped view.
Specify any WHERE conditions when the view is created.
Error sending message to query processor.
Explanation
Correction
Error Messages
A fatal error occurred while sending a message to the query processor.
All operations following the statement being evaluated will return an
error indicating that a fatal error has been encountered earlier.
If this error occurs, please call Customer Support.
165
–2110
Arithmetic overflow/underflow occurred.
Explanation
Correction
–2111
An arithmetic overflow or underflow occurred while trying to convert
data for a target. Check the data types of the value expressions. Maybe
the value of computing some data results in such a case.
If this error occurs, please call Customer Support.
Column values failed the WITH CHECK constraint.
Explanation
An insert or update operation on a view that was created with the WITH
CHECK option failed because the new column values did not meet the
restrictions specified in the WHERE clause.
Correction
Provide column values that satisfy the restrictions in the WHERE clause
specified in the CREATE VIEW statement.
–2112
UNIONed SELECTs must have the same number of items projected.
Explanation
All SELECT statements connected by the UNION keyword must select
the same number of columns.
Correction
Either change the SELECT clauses or specify the SELECT statements
separately.
–2113
Explanation
Correction
–2114
UNIONed SELECTs must have identical data types and lengths.
The corresponding columns selected by SELECT statements connected
by a UNION keyword must have compatible data types and lengths.
Check the order of columns and reorder them appropriately.
Invalid outer reference.
Explanation
Correction
166
In the select list or the GROUP BY clause of a subquery, you cannot have
references to columns in the outer SELECT or UPDATE statement.
Check the column names referenced in the statement.
Error Messages
–2115
Schema name does not match target schema.
Explanation
Correction
–2116
In a CREATE SCHEMA or ALTER SCHEMA statement, referenced
objects must be in the schema being created or altered.
Verify the schema names preceding object references.
Outer reference was expected.
Explanation
Correction
–2117
Explanation
Correction
–2118
An aggregate function in a WHERE clause must be a reference to an
aggregate value in the outer query.
Check the aggregate function and column names referenced in the
statement.
WHERE clause must be within HAVING clause to use aggregate func.
When an aggregate function appears in a WHERE clause, the subquery
that contains the WHERE clause must be within a HAVING clause.
Check the structure of the subquery.
Transaction aborted due to atomic SQL–DML error.
Explanation
Correction
–2119
An operation of a DML statement failed after some operations completed
successfully. The transaction was rolled back. This error occurs only
when the SQLATOMICDML configuration variable is set to TRUE.
None.
Aggregate expression must contain column name only if outer
reference.
Explanation
Correction
Error Messages
If an aggregate function appears in a subquery, the arguments to the
function must be column names.
Remove or change the aggregate function reference.
167
–2120
Invalid type for indicator variable.
Explanation
Correction
–2121
An indicator variable must be of type int, short, or long.
Use a host variable that has a data type of int, short, or long.
Attempt to divide by zero.
Explanation
Correction
–2122
An expression appearing in the SQL/A statement has a divisor of zero.
Check the value of the expression.
MAX occurrences must be exact numeric.
Explanation
Correction
–2123
In the ALLOCATE DESCRIPTOR statement, the value specified for the
MAX clause must be of data type integer.
Correct the value in the MAX clause.
Database name must be character string type.
Explanation
Correction
–2124
The database name must be a character string.
Check the type of the constant or host variable identifying the name of
the database.
Invalid SQL statement identifier; statement does not exist.
168
Explanation
The dynamic statement name used in the embedded statement does not
match a currently prepared statement.
Correction
Check the spelling of the name being used. Verify that the dynamic
statement with that name was prepared and has not been subsequently
deallocated.
Error Messages
–2125
Invalid SQL descriptor name; descriptor area does not exist.
Explanation
The descriptor area name used in the embedded statement does not match
a currently allocated descriptor area.
Correction
Check the spelling of the name being used. Verify that the descriptor area
has been allocated and not subsequently deallocated.
–2126
Invalid SQL/A descriptor name; descriptor area already exists.
Explanation
Correction
Additional Help
–2127
An attempt has been made to allocate a descriptor area with the same
name as an existing descriptor area.
If the existing descriptor area can be used, remove the extra ALLOCATE
DESCRIPTOR statement. If a new descriptor area is needed, use a unique
name.
Unify DataServer: Embedding SQL/A Into C
Descriptor area must have at least one item.
Explanation
An attempt has been made to allocate a descriptor area with fewer than
one item.
Correction
Make sure that the integer value specified in the MAX clause is greater
than or equal to one.
–2128
Attempt to allocate descriptor area with too many items.
Explanation
Correction
Additional Help
Error Messages
An attempt has been made to allocate a descriptor area with more items
than will fit in memory.
Reduce the integer value specified in the MAX clause of the ALLOCATE
SQL DESCRIPTOR statement.
Unify DataServer: Embedding SQL/A Into C
169
–2129
Descriptor area item number out of range.
Explanation
Correction
The statement attempted to reference an item that does not exist in the
descriptor area.
Check the number in the VALUE clause of the GET or SET
DESCRIPTOR statement. It should be in the range 1 to N, where N is the
value specified for the MAX clause of the ALLOCATE SQL
DESCRIPTOR statement.
Additional Help
Unify DataServer: Embedding SQL/A Into C
–2130
Descriptor area NAME field cannot be set.
Explanation
Correction
Additional Help
–2131
An attempt was made to set the NAME field in a SET DESCRIPTOR
statement.
Do not set the NAME field.
Unify DataServer: Embedding SQL/A Into C
Syntax error in SQL dynamic statement.
Explanation
Correction
–2132
The dynamic statement given to a PREPARE or EXECUTE IMMEDIATE
statement contains a syntax error.
Check the statement text being prepared or executed.
USING clause does not match dynamic parameters.
Explanation
The number and types of the items in the descriptor area do not match the
number and types of the dynamic parameters in the prepared statement.
Correction
Verify that the COUNT in the descriptor area matches the number of
dynamic parameters in the prepared statement. Verify that the data types
of the items in the descriptor area match the types of the corresponding
dynamic parameters. The DESCRIBE INPUT statement can be used to
obtain information about the dynamic parameters in a prepared statement.
Additional Help
170
Unify DataServer: Embedding SQL/A Into C
Error Messages
–2133
Too many prepared statements.
Explanation
Correction
–2134
The application has too many dynamic statements prepared at one time.
Deallocate some prepared statements by using the DEALLOCATE
PREPARE statement.
Dynamic SQL schema is out of sync.
Explanation
Correction
–2135
This is an internal error. A dynamic operation changed the current
schema and the application was unable to process the change.
Try to isolate the error-causing statement and notify Customer Support.
Alternatively, try other statements to accomplish the operation.
Locks can only be demoted in COMMIT AND BEGIN statement.
Explanation
The DEMOTING LOCKS clause can be used only when the COMMIT
statement includes the AND BEGIN.
Correction
Either remove the DEMOTING LOCKS clause or add the AND BEGIN
clause.
–2136
Transaction not completely terminated.
Explanation
Correction
–2137
This is an internal error. When a COMMIT WORK statement is executed,
the query processor passes this error to the front end to indicate that the
transaction has been committed.
Try to isolate the error-causing statement and notify Customer Support.
Alternatively, try other statements to accomplish the operation.
Empty SQL dynamic statement.
Explanation
Correction
Error Messages
The variable that contains the statement is of zero-length.
Check the statement text being prepared or executed.
171
–2138
Comment in SQL dynamic statement.
Explanation
Correction
–2139
You cannot place a comment in a SQL/A dynamic statement.
Check the statement text being prepared or executed.
ROWID may not be used for multi-table SELECT or non-updatable
view.
Explanation
Correction
–2140
The ROWID variable cannot be used in SELECT statements that select
from more than one table or from a non-updatable view.
Correct the SELECT statement.
Invalid usage of the ROWID function.
Explanation
You cannot specify the ROWID variable in an aggregate function or in a
HAVING clause.
Correction
–2141
Correct the SELECT statement.
Cursor specification not prepared.
Explanation
Correction
Additional Help
–2142
An attempt was made to open a cursor whose associated dynamic
statement is not prepared.
Prepare the associated dynamic statement before opening a dynamic
cursor.
Unify DataServer: Embedding SQL/A Into C
Prepared statement not a cursor specification.
Explanation
Correction
Additional Help
172
An attempt was made to open a cursor whose associated dynamic
statement is not a cursor specification.
Prepare a SELECT statement in the associated dynamic statement or
associate the cursor with a dynamic statement that has a prepared cursor
specification.
Unify DataServer: Embedding SQL/A Into C
Error Messages
–2143
Explanation
Correction
Additional Help
–2144
USING clause required to specify dynamic parameter values.
The prepared statement contains dynamic parameters. A USING clause is
needed to specify values for the dynamic parameters.
Add the USING clause.
Unify DataServer: Embedding SQL/A Into C
USING clause required in dynamic OPEN to specify dynamic
parameter values.
Explanation
Correction
Additional Help
–2145
The prepared statement contains dynamic parameters. A USING clause is
needed to specify values for the dynamic parameters.
Add the USING clause.
Unify DataServer: Embedding SQL/A Into C
INTO clause required for projected values.
Explanation
Correction
Additional Help
–2146
The prepared statement selects values from the database. An INTO clause
is needed to specify where to put the returning values.
Use the INTO clause.
Unify DataServer: Embedding SQL/A Into C
INTO clause does not match projected columns.
Explanation
Correction
Additional Help
Error Messages
The number and types of the items in the descriptor area do not match the
number and types of the projected columns in the prepared statement.
Verify that the COUNT in the descriptor area matches the number of
projected columns in the prepared statement. Verify that the TYPE of
each item in the descriptor area matches the type of the corresponding
projected column. The DESCRIBE OUTPUT statement can be used to
obtain information about the projected columns in a prepared statement.
Unify DataServer: Embedding SQL/A Into C
173
–2147
Cursor specification cannot be executed.
Explanation
Correction
Additional Help
–2148
Dynamic SELECT statements cannot be executed with an EXECUTE
IMMEDIATE statement and only single row SELECT statements can be
executed with an EXECUTE statement.
If a single row is expected, prepare the dynamic SELECT and execute it
(be sure to use the INTO clause in the EXECUTE statement). If more than
one row is expected, prepare the statement, associate the prepared
statement with a dynamic cursor, open the cursor, and fetch the rows
from the cursor.
Unify DataServer: Embedding SQL/A Into C
Warning: unexpected local cursor name, assumed to be an allocated
cursor name.
Explanation
Correction
Additional Help
–2149
An UPDATE or DELETE statement was prepared with a static cursor
name in the WHERE CURRENT OF clause.
Place single quotation marks around the cursor name when generating
dynamic UPDATE or DELETE statements with the WHERE CURRENT
OF clause.
Unify DataServer: Embedding SQL/A Into C
Prepared statements cannot reference host variables.
Explanation
Correction
Additional Help
174
A prepared statement cannot reference a host variable.
Use a dynamic parameter in the statement instead and substitute the host
variable when executing the statement. See the USING clause of the
EXECUTE statement or the USING clause of the (dynamic) OPEN
CURSOR statement.
Unify DataServer: Embedding SQL/A Into C
Error Messages
–2150
Value of COUNT is out of range.
Explanation
Correction
Additional Help
–2151
An attempt was made to set the COUNT field of a descriptor area to an
invalid value.
The value of the COUNT field must be in the range 0 to N, where N is the
value specified for the MAX clause of the ALLOCATE SQL
DESCRIPTOR statement.
Unify DataServer: Embedding SQL/A Into C
TYPE set to unknown data type.
Explanation
Correction
Additional Help
–2152
An attempt was made to set the TYPE field of a descriptor area to an
invalid value.
Correct the TYPE field value.
Unify DataServer: Embedding SQL/A Into C
Warning: information retrieved from undefined descriptor area
item.
Explanation
Correction
Additional Help
Error Messages
A questionable item was used in a GET DESCRIPTOR statement. While
the item is within the allocated range of the descriptor area, it is not
within the range of meaningful items, as indicated by the COUNT field.
This is only a warning.
Verify that the item number specified in the VALUE clause is correct.
Verify that the correct descriptor area is being used.
Unify DataServer: Embedding SQL/A Into C
175
–2153
Warning: setting value in undefined descriptor area item.
Explanation
A questionable item was used in a SET DESCRIPTOR statement. While
the item is within the allocated range of the descriptor area, it is not
within the range of meaningful items, as indicated by the COUNT field.
This is only a warning.
Correction
Verify that the item number specified in the VALUE clause is correct.
Verify that the correct descriptor area is being used. Change the COUNT
field before initializing new items.
Additional Help
–2154
Unify DataServer: Embedding SQL/A Into C
Warning: LENGTH is not meaningful when TYPE is not a string type.
Explanation
Correction
The LENGTH field is meaningful for character types only.
Verify that the correct descriptor area and item are being used. Set the
TYPE field to an appropriate type before setting the LENGTH field.
Additional Help
–2155
Unify DataServer: Embedding SQL/A Into C
Warning: PRECISION is not meaningful when TYPE is not a numeric
type.
Explanation
Correction
The PRECISION field is meaningful for numeric types only.
Verify that the correct descriptor area and item are being used. Set the
TYPE field to an appropriate type before setting the PRECISION field.
Additional Help
–2156
Unify DataServer: Embedding SQL/A Into C
Warning: SCALE is not meaningful when TYPE is not a numeric
type.
Explanation
Correction
Additional Help
176
The SCALE field is meaningful for numeric types only.
Verify that the correct descriptor area and item are being used. Set the
TYPE field to an appropriate type before setting the SCALE field.
Unify DataServer: Embedding SQL/A Into C
Error Messages
–2157
Invalid value for LENGTH.
Explanation
Attempt to set the LENGTH field of a descriptor area to an invalid value.
Correction
Correct the LENGTH field value. The LENGTH field indicates the length
of the column data if the data is a character or bit string.
Additional Help
–2158
Unify DataServer: Embedding SQL/A Into C
Invalid value for PRECISION.
Explanation
Correction
Attempt to set the PRECISION field of a descriptor area to an invalid
value.
Correct the PRECISION field value. The PRECISION field indicates the
precision of the column data it the data is of type AMOUNT, DECIMAL,
DOUBLE PRECISION, FLOAT, HUGE AMOUNT, INTEGER, NUMERIC,
REAL, or SMALLINT.
Additional Help
–2159
Unify DataServer: Embedding SQL/A Into C
Invalid value for SCALE.
Explanation
Attempt to set the SCALE field of a descriptor area to an invalid value.
Correction
Correct the SCALE field value. The SCALE field indicates the scale of
the column data if the data is of type AMOUNT, DECIMAL, DOUBLE
PRECISION, FLOAT, HUGE AMOUNT, INTEGER, NUMERIC, REAL, or
SMALLINT.
Additional Help
–2160
Unify DataServer: Embedding SQL/A Into C
Invalid value for NULLABLE.
Explanation
Correction
Additional Help
Error Messages
Attempt to set the NULLABLE field of a descriptor area to an invalid
value.
Correct the NULLABLE field value.
Unify DataServer: Embedding SQL/A Into C
177
–2161
Data type of value does not match data type of the descriptor area
field.
Explanation
Correction
Additional Help
–2162
A descriptor area field has an incompatible data type to the associated
host variable.
If you are storing data into or retrieving data from the DATA field, change
the data type of the DATA field (the TYPE field) to correspond to the data
type of the associated host variable or constant. Alternatively, change the
data type of the receiving host variable to match the data type of the
TYPE field.
Unify DataServer: Embedding SQL/A Into C
Unexpected characters after dynamic statement.
Explanation
Correction
Additional Help
–2163
A valid SQL/A statement was parsed but additional characters appeared
before the end of the statement.
Check the statement text being prepared or executed.
Unify DataServer: Embedding SQL/A Into C
Warning: DATA is not meaningful when INDICATOR is null.
Explanation
Correction
Additional Help
178
The DATA field of an SQL/A descriptor area is being set but the
INDICATOR field is not being set and it indicates a null value. When the
INDICATOR field indicates a null value, the DATA field is ignored.
If the intent was to set the descriptor area item to a non-null data value,
then specify INDICATOR= 0 in the SET statement.
Unify DataServer: Embedding SQL/A Into C
Error Messages
–2164
Invalid EXECUTE IMMEDIATE statement.
Explanation
Correction
Additional Help
–2165
The statement text used in an EXECUTE IMMEDIATE statement is
invalid.
Some SQL/A statements are invalid in the context of an EXECUTE
IMMEDIATE statement. The SELECT statement, for example, cannot be
used in an EXECUTE IMMEDIATE statement.
Unify DataServer: Embedding SQL/A Into C
Unify DataServer: SQL/A Reference (statements listed as preparable)
Expecting database name.
Additional Help
See error number –10480.
–2166
Invalid database option.
Additional Help
See error number –10471.
–2167
Expecting volume name.
Additional Help
See error number –10492.
–2168
Additional Help
–2169
Additional Help
Error Messages
Invalid volume option.
See error number –10698.
Expecting schema name.
See error number –10486.
179
–2170
Additional Help
–2171
Additional Help
–2172
Additional Help
–2173
Additional Help
–2174
Additional Help
–2175
Additional Help
–2176
Additional Help
–2177
Additional Help
180
Invalid ALTER DEFAULT statement.
UEALTDFL
See error number –10426.
Invalid link index syntax.
UELNKSYN
See error number –10529.
Invalid hash index syntax.
UEHSHIDX
See error number –10505.
Invalid hash index configuration option.
UEHSHCG
See error number –10504.
Invalid B–tree index syntax.
UEBTRSYN
See error number –10443.
Invalid B–tree column specification.
UEBTRCOL
See error number –10441.
Invalid B–tree configuration option.
UEBTRCG
See error number –10440.
Invalid link index name specification.
UELNKNM
See error number –10528.
Error Messages
–2178
Additional Help
–2179
Additional Help
–2180
Additional Help
–2181
Additional Help
–2182
Additional Help
–2183
Additional Help
–2184
Additional Help
–2185
Additional Help
Error Messages
Invalid hash index name specification.
UEHSHINM
See error number –10506.
Invalid B–tree index name specification.
UEBTRNMS
See error number –10442.
Invalid ALTER VOLUME configuration option.
UEAVOLCG
See error number –10430.
Invalid GRANT statement syntax.
UEGRTS
See error number –10500.
Invalid REVOKE statement syntax.
UERVKSYN
See error number –10572.
Expecting table name.
UEETBLN
See error number –10490.
Invalid table element option.
UETBLEO
See error number –10638.
Invalid column specification.
UECSPEC
See error number –10457.
181
–2186
Additional Help
–2187
Additional Help
–2188
Additional Help
–2189
Additional Help
–2190
Additional Help
–2191
Additional Help
–2192
Additional Help
–2193
Additional Help
182
Invalid column configuration option.
See error number –10447.
Invalid table configuration option.
See error number –10637.
CREATE VIEW may only contain SELECT statements.
See error number –10459.
Invalid CREATE VIEW syntax.
See error number ––10460.
Invalid SYNONYM syntax.
See error number –10634.
Invalid DROP SYNONYM syntax.
See error number –10477.
Invalid RENAME TABLE syntax.
See error number –10569.
Invalid ALTER TABLE option.
See error number –10429.
Error Messages
–2194
Additional Help
–2195
Additional Help
–2196
Additional Help
–2197
Additional Help
–2198
Additional Help
–2199
Additional Help
–2200
Additional Help
–2201
Additional Help
Error Messages
Unable to add constraint.
See error number –10424.
CREATE DATABASE is not allowed in a runtime statement.
See error number –10730.
CREATE TABLE is not allowed in a runtime version.
See error number –10731.
Select expression is not a column name.
See error number –10484.
SQLDDLSIZ is zero or non–numeric.
See error number –10444.
Not enough DDL workspace, increase SQLDDLSIZ.
See error number –10509.
DROP TABLE is not allowed in a runtime version.
See error number –10732.
DIRECT specified multiple times...
See error number –10431.
183
–2202
Additional Help
–2203
Additional Help
–2204
Additional Help
–2205
Additional Help
–2206
Additional Help
–2207
Additional Help
–2208
Additional Help
–2209
Additional Help
184
Column names must be unique.
See error number –12219.
All column names cannot be dropped; at least one must remain.
See error number –10462.
Supplied name is not a synonym for this table.
See error number –10642.
All table names cannot be dropped; at least one must remain.
See error number –10463.
ORDER BY clause is not allowed in a view definition.
See error number –10725.
WITH CHECK option not allowed for non–updatable views.
See error number –10745.
Can’t project TEXT or BINARY columns in a unique view.
See error number –10727.
Column count mismatch in view.
See error number –10448.
Error Messages
–2210
Additional Help
–2211
Additional Help
–2212
Additional Help
–2213
Additional Help
–2214
Additional Help
–2215
Additional Help
–2216
One of the tables for the link must be in the current schema.
See error number –12211.
Number of columns for parent and child are not the same.
See error number –10546.
Unknown system user specified.
See error number –10434.
Unknown system group specified.
See error number –10433.
Columns are not permitted on Schemas.
See error number –10455.
INDEX privilege not permitted on tables.
See error number –10519.
Unable to successfully prepare a statement.
Explanation
Correction
Additional Help
Error Messages
This is an internal error related to the optimization of simple prepared
statement execution.
Try running your application with the optimization disabled
(SQLPREPARE set to FALSE). If the error persists, call Customer Support.
Unify DataServer: Configuration Variable and Utility Reference
185
–2217
Cost option not allowed in views.
Explanation
Correction
Additional Help
–2218
The COST or NOCOST option cannot be specified in a query expression
used in a CREATE VIEW statement.
Change the query expression.
Unify DataServer: SQL/A Reference
Invalid cost option.
Explanation
Correction
Additional Help
–2219
The COST or NOCOST option must be specified following the USING
keyword in a SELECT statement.
Verify the SELECT statement syntax.
Unify DataServer: SQL/A Reference
Invalid hash folding algorithm specified.
Explanation
An incorrect value for a hash folding algorithm was specified. This
usually means that a value was specified, but it did not correspond to an
existing hash folding algorithm.
Correction
Use a value hash folding algorithm. For a list of the possible values for
hash folding algorithms, see the Unify DataServer: SQL/A Reference and
Unify DataServer: RHLI Reference manuals.
–2220
Warning: The value specified for the LENGTH field is valid for
constants, but not data values of this type.
Explanation
Correction
186
The LENGTH field value is greater than the maximum allowed to store
data values of this type in the database. If the dynamic parameter updates
a database value, the value would be truncated. But it is valid to have
dynamic parameter of this LENGTH in the context of a constant in the
WHERE clause.
Check the LENGTH field value and correct it if necessary.
Error Messages
–2221
Invalid SQL descriptor handle: not associated with an SQL
descriptor area.
Explanation
A valid SQL/A descriptor area handle is expected. The specified host
variable is not a valid SQL/A descriptor handle.
Correction
You can get the handle of an SQL/A descriptor by using GET handle
statement.
–2222
Explanation
Correction
–2500
DATAPTR is an invalid SQL descriptor field for this descriptor area.
DATAPTR fields are allowed only for descriptor areas allocated with
USING DATAPTR clause.
If you intend to use DATAPTR field, you need to allocate the descriptor
area with USING DATAPTR clause. Otherwise, you should use the DATA
field rather than DATAPTR field.
Operation unsuccessful.
Explanation
Correction
–2501
This is an internal error.
Try to isolate the error-causing statement and notify customer support.
Alternatively, try other statements to accomplish the operation.
View not found.
Explanation
Correction
–2502
This is an internal error.
Try to isolate the error-causing statement and notify customer support.
Alternatively, try other statements to accomplish the operation.
Invalid query specification.
Explanation
Correction
Error Messages
An inconsistency was encountered while expanding the view definition.
Drop and recreate the view.
187
–2503
Invalid parameter list.
Explanation
This is an internal error. Invalid parameters were passed to an internal
view management function.
Correction
Try to isolate the error-causing statement and notify customer support.
Alternatively, try other statements to accomplish the operation.
–2505
Unknown data type.
Explanation
This is an internal error. The view manager encountered a constant with
an unknown data type.
Correction
Try to isolate the error-causing statement and notify customer support.
Alternatively, try other statements to accomplish the operation.
–2506
View definition invalid.
188
Explanation
The view you are referencing is invalid. A view can become invalid
when the column, table, or view that is referenced in the CREATE VIEW
statement is no longer accessible.
Correction
Check the that the tables or views used to create the view have not been
dropped or had their permissions changed.
Error Messages
–9720
Explanation
Correction
Additional Help
–9722
Explanation
Correction
Additional Help
Unable to open unicap file specified by configuration variables.
An executable could not open the unicap file.
Make sure the UNICAP configuration variable is set correctly.
“Configuring Applications” in Unify DataServer: Managing a Database
UNICAP description in Unify DataServer: Configuration Variable and
Utility Reference
The UNIFY configuration variable is not set.
An executable could be find a setting for the UNIFY configuration
variable.
Set the UNIFY configuration variables.
“Configuring Applications” in Unify DataServer: Managing a Database
UNIFY description in Unify DataServer: Configuration Variable and
Utility Reference
–9727
Explanation
Correction
Additional Help
–9729
Explanation
Correction
Error Messages
Unable to open the termcap file.
An executable could be open the termcap file.
Make sure the TERMCAP configuration variable is set correctly.
“Configuring Applications” in Unify DataServer: Managing a Database
TERMCAP description in Unify DataServer: Configuration Variable and
Utility Reference
Reached EOF for standard input.
A compatibility archive function which accepts keyboard input received
an end-of-file from the keyboard. If you don’t consider it an error you
can ignore this error.
To avoid this error, your application must provide a way to exit other
than end-of-file. Create some exit code like Ctrl C and exit when this
character is received from the keyboard.
189
–9730
Explanation
Correction
Additional Help
–9731
Explanation
Correction
Additional Help
The TERM configuration variable is not set.
An executable could not find a setting for the TERM configuration
variable.
Set the TERM configuration variable to the terminal type for your
terminal. The terminal type must be defined in the termcap file specified
by the TERMCAP configuration variable.
“Configuring Applications” in Unify DataServer: Managing a Database
TERMCAP description n Unify DataServer: Configuration Variable and
Utility Reference
The terminal type ’terminal_name’ is not in the termcap file.
The terminal type defined by the TERM configuration variable was not
found in the specified termcap file. The termcap file is defined by the
TERMCAP configuration variable.
Make sure both TERM and TERMCAP are set correctly.
“Configuring Applications” in Unify DataServer: Managing a Database
TERMCAP, TERM in Unify DataServer: Configuration Variable and
Utility Reference
–9732
Explanation
A compatibility archive function which accepts keyboard input received
a keyboard error when attempting to read from the keyboard. The status
status_code is the error number returned by the RDBMS. It is one of the
errors defined in rhli.h. This number indicates why the read failed.
Correction
Take appropriate action based on the status returned by the data base. If
the error number refers to a broken pipe make sure that each executable
in the pipeline functions correctly.
–9811
Explanation
Correction
190
Unable to read standard input.
Unable to change signal_name (signal_number) signal handler.
This is an internal error and should not occur during normal execution.
If this error occurs, please call Customer Support.
Error Messages
–9815
Explanation
Correction
–9816
Explanation
Correction
–9818
Explanation
Correction
–9819
Explanation
Correction
–9823
Explanation
Correction
Error Messages
Journal/Backup volume volume_number was opened/mounted.
A volume has been opened or mounted out of sequence. The volume
could be a transaction journal, a full backup tape, an incremental backup
tape or some other backup media. This error is usually followed by the
“Please mount ...” prompt.
Unmount the current volume and mount the volume with the correct
sequence number.
Opened/Mounted media is not part of this backup.
The opened or mounted volume belongs to a different backup series. This
error will usually be followed by the “Please mount ...” message.
Unmount the current volume and mount the appropriate volume.
Only number blocks written to backup media. Continue?
Fewer blocks are written to a volume than were specified in the BUDEV
configuration variable.
A “no” response will abort the program, allowing the process to be
restarted without the faulty media volume. A “yes” response allows the
program to continue with the faulty volume. The fact that there are fewer
blocks should be recorded on label of a faulty volume for future use.
Only number blocks read from backup media. Continue?
Fewer blocks were read from a volume than were specified when the
volume was written.
A “yes” response allows the program to continue with the faulty volume.
This response is acceptable if the volume had been written with fewer
blocks. A “no” response aborts the program.
Media too small: unable to write data blocks.
The media volume is too small to hold at least two blocks. This error is
followed by the “Please mount ...” message. This problem is detected
early enough for you to replace the faulty media with a new one.
Unmount the faulty media and mount another media to take its place.
191
–9824
Bad media: unable to read/write header block.
Explanation
The media cannot be read from or written to. This error is usually
followed by the “Please mount ...” message. This error may be caused
by mounting a media for a different device, an uninitialized media, or a
seriously damaged or faulty media.
Correction
If you are writing to the media, unmount the faulty media and mount a
new media.
If you are reading, make sure that the media is the one requested. If this
error occurs on the first volume, reset the block size in the device’s
configuration variable to a smaller number of bytes and restart the
program.
–9825
Explanation
Correction
Backup device is off-line or not write enabled. Retry?
The backup or journal device cannot be opened.
Make sure the BUDEV or JOURNAL configuration variable is correct.
Make sure you have read/write permission on the device. Make sure the
device is turned on and on-line. If writing, make sure the media is
write-enabled.
When the problem is fixed, respond with “yes” if you want to continue
the program. The program can be aborted with a “no” response.
Additional Help
–9827
Explanation
Correction
–9828
Explanation
Correction
192
Unify DataServer: Configuration Variable and Utility Reference
Backup device read/write failed. Mode is mode_number.
A user-defined error from a user “read” or “write” C-hook was
receieved during the backup.
Consult your database application administrator.
Backup device close failed.
A user-defined error from a user “close” C-hook was received during the
backup.
Consult your database application administrator.
Error Messages
–9830
Explanation
Correction
–9831
Pipe close failed.
This is an internal error only and should not occur during normal
backups.
If this error occurs, please call Customer Support.
Opened/Mounted media is not a backup volume.
Explanation
The opened or mounted media is not a Unify DataServer backup volume.
It will usually be followed by the “Please mount ...” message.
Correction
Unmount the current volume and mount the requested Unify DataServer
volume.
–9832
Explanation
Correction
–9836
Backup device open failed.
A user-defined error from a user “open” C-hook was received during the
backup.
Consult your database application administrator.
Current volume is full. Create new zero-length file.
Explanation
The backup or journal device is not mountable and the end of the device
has been reached.
Correction
Copy the data from the device to some other available storage. The
device can then be used for the additional data. Respond with “yes” if
you want to continue the program. A “no” response aborts the program.
–9840
Explanation
Correction
–9854
Explanation
Correction
Error Messages
Child process killed by signal.
Someone terminated the backup with a signal.
Restart the backup.
Incorrect Unify media version.
The mounted volume was written with an earlier version of the product
and the format is no longer compatible. It is followed by the “Please
mount ...” message.
If possible, perform the appropriate conversion process on the old
volumes.
193
–9858
Explanation
Correction
–9872
Explanation
Correction
–9873
Explanation
Correction
–9874
Explanation
Correction
–9896
Explanation
Correction
–9897
Explanation
Correction
194
Non-empty file, device must be zero length file. Continue?
A regular file is being used as a backup or journal device. The file must
be zero length before it can be written to.
Create a backup copy of the file and then recreate the regular file with
zero length.
Unable to ignore signal_name (signal number) signal.
This error occurs when the program is unable to ignore a signal.
None. This is an internal error.
Backup_driver_name: cannot be invoked from shell.
This is again part of an error message which tells that the backup driver
cannot be executed from the shell.
Don’t run the backup driver from the shell.
Argument error. status fd = fd_number, data fd = fd_number.
This is an internal error and should not occur during normal execution.
If this error occurs, please call Customer Support.
sfltts.c: Illegal mantissa value generated by frexp().
While sorting float values, the compatibility archive converts a float
value into an ASCII representation consisting of a sign, followed by
exponent, followed by mantissa. The exponent is normalized and the
mantissa is normalized if it is negative. This error occurs if the mantissa
does not fall in the range –1.0 to 1.0.
Check the data values.
Too many selsort sets are current
The compatibility archives allow only a limited number of selsort scans.
Modify the application to reduce the number of open selsort scans.
Error Messages
–9898
–9899
Explanation
Correction
–9900
Explanation
Correction
–9905
Explanation
Correction
–9906
Explanation
Correction
–9907
Explanation
Correction
–9908
Explanation
Correction
selsort: tag row too large
selsort: column too large
This is an internal error and should not occur in normal operation.
If this error occurs, please call Unify Customer Support.
sort not found.
The compatibility archive’s sorting function executes the operating
system sort command. This error occurs if the sort command is not
found.
Make sure that there is a sort command on the system and on your PATH.
Too many unisort sets are current
The compatibility archives allow only a limited number of unisort scans.
Modify the application to reduce the number of open unisort scans.
unisort: tag row too large
This is an internal error and should not occur in normal operation.Need
explanation
If this error occurs, please call Unify Customer Support.
unisort: column too large
This is an internal error and should not occur in normal operation.
If this error occurs, please call Unify Customer Support.
unisort: unable to create tagfile.
The compatibility archive’s column select facility creates a tag file and
stores the column values and row positions of all rows found in the tag
file. This error occurs if the select function cannot create and open the tag
file.
Check for permissions on the temporary directory specified by the
UNIFYTMP configuration variable. Also check that there is sufficient disk
space.
Error Messages
195
–9909
Explanation
Correction
–9915
Explanation
Correction
–9916
Explanation
Correction
–9917
Explanation
Correction
–9918
Explanation
Correction
–9919
Explanation
Correction
196
selsort: unable to create tagfile
selsort must create a temporary file but cannot do so.
Make sure that the $UNIFYTMP directory is writeable and has enough
space.
Duplicate key not allowed.
The compatibility archive function which accepts an input value and
stores in the data base encountered an input value that is a duplicate key
value.
Don’t give duplicate values as input.
flush – write failed.
The compatibility archive function failed to write a data buffer and a new
line at the end to the specified device.
Check the validity of the device being written to.
Illegal integer value.
The compatibility archive function expected an integer input value from
the user but received input that is not an integer.
Make sure the input is an integer value.
Illegal numeric value.
The compatibility archive function expected a numeric input value from
the user but received input that is not a valid numeric value.
Make sure the input is a valid numeric value.
Invalid long date.
The compatibility archive function expected a long date value from the
user but received input that is not a valid long date.
Make sure the input is a valid long date value.
Error Messages
–9920
Invalid type.
Explanation
A compatibility archive function attempted to convert an input value into
an invalid data base data type.
Correction
Check that the data type you are converting into is a valid data base type.
–9921
Illegal column number.
Explanation
The compatibility archive function that gets input or stores the value in
the data base has received a column ID for which the user does not have
authorization or that is an illegal value.
Correction
Make sure the column ID is valid and verify that the user has the correct
permissions on the column.
–9922
Explanation
Correction
–9923
Explanation
Correction
–9924
Explanation
Correction
–9925
Explanation
Correction
Error Messages
Illegal value.
This error occurs when the value entered at the terminal is not valid.
Check for valid values for the command or column.
Record key is in use.
The key value being input is already in the data base and is therefore a
duplicate key.
Don’t input the duplicate key value.
table _name not found.
The compatibility archive function was unable to find the table_name
table in the function.
Check the name and authorization on the table.
form_file is corrupt.
The compatibility archive function that displays a form from an external
file was unable to get form length. Either the file name was wrong or the
file is corrupted.
Check the name of the file or regenerate the form file.
197
–9926
Explanation
Correction
–9927
Explanation
Correction
–9973
Explanation
Correction
Additional Help
–9974
Explanation
Correction
Additional Help
–9975
Explanation
Correction
198
Pform error no error_number from function_name.
Compatibility archive routine that displays form from an external file
reports this error when something is wrong with the external text file.
Check the name of the file. The file may have been corrupted. Regenerate
if possible.
Value too large.
The input value is too large for the length specified.
Increase the length of the value.
Column group not allowed as input column.
You cannot specify a column group as an input column to dbld.
Replace the column group with the group members you are loading.
Unify DataServer: Configuration Variable and Utility Reference
Invalid format for column column_name, row row_number.
The dbld utility detected a value that is not compatible with the format of
the column column_name in row row_number.
Correct the value by editing the input.
Unify DataServer: Configuration Variable and Utility Reference
Input file not specified.
The dbld utility found that the input file name is missing from the
command line.
Supply the correct input file name to dbld.
Error Messages
–9976
Explanation
Correction
–9977
Explanation
Correction
Additional Help
–9978
Explanation
Correction
Additional Help
–9979
Explanation
Correction
–9981
Explanation
Correction
Error Messages
dbld: Insufficient memory.
There was not enough memory on the system for dbld to continue.
Check the status of the system and user limits and restart dbld.
Update only and insert only are incompatible.
You cannot specify both the –n and the –u options to dbld at the same
time.
Correct your command line, using only one of these options.
Unify DataServer: Configuration Variable and Utility Reference
Invalid range for column column_name, row row_number.
The dbld utility found that the column value column_name in row
row_number does not fall within the legal values for the column.
Check for any Data Integrity Subsystem specifications for the column.
Correct the column value if necessary.
Unify DataServer: Configuration Variable and Utility Reference
dbld: Loading from standard input.
This is a message to tell you that the input for dbld is taken from the
standard input. This is only a message and not an error.
None.
Missing value for column = column_name at line line_number.
The dbld utility could not a value for the column <column name> on line
line_number. This utility expects values or nulls for all the columns
specified in the specification file.
Supply values or nulls for the specified column.
199
–9982
Explanation
Correction
–9983
This error usually occurs when a TEXT/BINARY update operation fails
because of the lack of space or an error during TEXT/BINARY data
operation.
Check the space availability for TEXT/BINARY data files.
Blanks not allowed as the separation chars.
Explanation
The dbld utility does not allow spaces to separate column names or data
values.
Correction
Use some other character to specify the column separator. Column
separators are specified with the dbld command line option
–Osepchar=char where char is the column separator character. Note that
if you want to use a character that is special to the operating system shell
(such as “*” or “?”), you must escape the char by preceding it with a
backslash (“\”).
Additional Help
–9984
Explanation
Correction
–9985
Explanation
Correction
Additional Help
–9986
Explanation
Correction
Additional Help
200
Ran out space in the table at row row_number.
Unify DataServer: Configuration Variable and Utility Reference
Can’t open specification file: file_name.
The dbld utility is unable to open the specification file file_name.
Check the name of the specification file. Verify that the specification file
has the correct permission.
The separator must be a single character.
Multi-character separators are not allowed.
Make the separator a single character.
The dbld specification file description in Unify DataServer:
Configuration Variable and Utility Reference.
Table name not specified to dbld.
The name of the table to be loaded is missing from the command line.
Check your command line.
Unify DataServer: Configuration Variable and Utility Reference
Error Messages
–9988
Explanation
Correction
Additional Help
–9989
Explanation
Correction
Additional Help
–9990
Unexpected input at line line_number.
There are more input values on a line than expected by the specification
file. The dbld utility skips the line line_number.
Check your input file for extra input values.
The dbld input file description in Unify DataServer: Configuration
Variable and Utility Reference.
Null column names are not allowed.
The dbld utility encountered a separator immediately followed by
another separator in the specification file and treated it as a null column
value.
Supply the missing column name or check for errors in your specification
file.
The dbld specification file description in Unify DataServer:
Configuration Variable and Utility Reference.
Table: table_name does not have a key.
Explanation
The dbld utility in the default mode (neither –n or –u options specified)
expects the table table_name to have a primary key.
Correction
You cannot do updates if the table does not have a primary key. Use the
–n option for inserting rows into the table.
–9991
Explanation
Correction
–9992
Explanation
Correction
Error Messages
Failed to open the exception file.
The dbld utility could not open the exception file. Diagnostic messages
can optionally go into an exception file specified on the command line.
Check for permissions and existence of the exception file.
Reject this row.
The current row has been rejected and dbld is proceeding to the next row.
Check the validity of the row and exception file. Also check the errlog
file for more information.
201
–9993
Explanation
The –s option requires the schema name to be specified.
Correction
If the table you are loading is in your default schema, you don’t have to
specify –s option. Otherwise, you must specify a schema name.
Additional Help
The dbld utility syntax description in Unify DataServer: Configuration
Variable and Utility Reference.
–9994
Explanation
Schema ID required along with –S option.
This error occurs if the Schema ID is not specified when using the –S
option of dbld.
Correction
If the table you are loading is in your default schema, you don’t have to
specify –S option. Otherwise, you must specify a Schema ID.
Additional Help
The dbld utility syntax description in Unify DataServer: Configuration
Variable and Utility Reference.
–9995
Explanation
Correction
Additional Help
–9996
202
Schema name required along with –s option.
No access method to enforce uniqueness, use –q option for sequential.
This error occurs when no access method exists to assist in enforcing
uniqueness. Without an access method, such as B-tree, hash table or a
direct key, sequential access must be used to enforce uniqueness. To use
sequential access, dbld requires the –q override option.
Add an access method on the unique column if you can, otherwise use
the –q option to override the restriction.
The dbld utility syntax description in Unify DataServer: Configuration
Variable and Utility Reference.
Invalid row ID (value is null).
Explanation
The dbld utility with the –u option expects the row ID at the beginning
of the line. This error occurs if this row ID is missing.
Correction
Check your data file for the existence of the row IDs. You may want to
change dbld options so that row IDs are not required.
Additional Help
The dbld utility syntax description in Unify DataServer: Configuration
Variable and Utility Reference.
Error Messages
–9997
Insert only mode not allowed for direct tables. Use default mode
(Don’t specify –n or –u).
Explanation
If the table you are loading has a direct key then the –n option of the
dbld utility is not compatible.
Correction
Additional Help
–9998
Explanation
Correction
–9999
Use the default mode of dbld.
The dbld utility syntax description in Unify DataServer: Configuration
Variable and Utility Reference.
Extra input past the specified columns at line line_number.
The input contains more columns of data than expected.
Check the input file at the indicated line and remove the excess data. (In
some cases, the solution is to insert a linefeed where one was
inadvertantly deleted.)
Invalid row ID (value cannot be determined).
Explanation
If a direct table is being loaded, you must include the primary key in the
specification and input files.
Correction
Make sure that the primary key column name is in the specification file
and that the data is in the input file.
–10038
Explanation
Correction
–10043
Explanation
Correction
Error Messages
Invalid date.
An invalid date was entered using the CHLI function gdate().
Enter a valid date.
Invalid time.
An invalid date was entered using the CHLI function ghr().
Enter a valid time.
203
–10044
Explanation
Correction
–10071
–10072
–10073
Explanation
Correction
–10074
Explanation
Correction
–10076
Explanation
Correction
–10077
Explanation
Correction
204
’table_name’ is an invalid table, i.e. not found in data dictionary.
An invalid table name was specified for columns.
Make sure that the table name is spelled correctly and that the table is in
the current schema, and re-enter the command.
Unable to determine database name.
Problems in initializing configuration file.
Unable to retrieve recovery log filename.
This is an internal error and should not occur in normal operation.
If this error occurs, please call Unify Customer Support.
Recovery log file ’file_name’ exists: remove it or save it.
The file specified by the LOGRC configuration variable already exists.
The recovery log file may contain some transactions that need to be
rolled forward.
If a previous backup was aborted, you may want to move the .rc file into
the .lg file. If not, remove the .rc file before you start recovery.
Unable to fork redb reader process.
A required query processor for the redb process could not be started.
Retry the restore later. If the problem persists, please call Unify Customer
Support.
Unable to start burd process.
The burd process could not be started.
Make sure that the burd executable file is on your path and that you have
execute permission for it.
Error Messages
–10078
–10079
–10080
Explanation
Correction
–10081
–10082
–10083
Explanation
Correction
–10084
–10085
–10090
Explanation
Correction
Error Messages
Unable to get/create VSU.
Unable to retrieve VSU information for VSU.
Unable to initialize transaction manager.
This is an internal error and should not occur in normal operation.
If this error occurs, please call Unify Customer Support.
Unable to create transaction log.
Unable to create database state file.
Unable to create database errlog file.
Contained in message.
Make sure that you have write permission for the directory where the file
will reside and that enough disk space is available.
Unable to close file.
Unable to set VSU frequency for VSU.
Member of column group is missing.
This is an internal error and should not occur in normal operation.
If this error occurs, please call Unify Customer Support.
205
–10120
Explanation
Correction
–10131
Explanation
Correction
–10132
Explanation
Correction
–10133
Explanation
Correction
–10134
206
File open failed: file_name.
This message is generated when repoint fails to open the specified file.
Make sure the file name is spelled correctly. Check for read/write
permissions on the file or its directory.
The create on intermediate file ’file_name’ failed.
The RPT intermediate file named file_name could not be created.
Make sure that the file exists, that you have read and write permission on
the file, and that the file is in the directory. Make sure that i-nodes are
available in the file system.
The create on tag file ’file_name’ failed.
The RPT tag file named file_name could not be created.
Make sure that the file exists, that you have read and write permission on
the file, and that the file is in the directory. Make sure that i-nodes are
available in the file system.
An error was encountered writing to the intermediate file
’file_name’.
An attempt has been made to write to the file_name file.
Make sure that space is available in the file system.
Invalid column number column_number generated by PRINT
statement on line line_number.
Explanation
The column number specified in the IN COLUMN clause of the PRINT
statement is greater than the set page width. The line number
line_number identifies the approximate location of the PRINT statement;
the actual statement can occur before the line number indicated.
Correction
Increase the width for the report by modifying the WIDTH statement or
change the column position in the PRINT statement.
Error Messages
–10135
Explanation
Correction
–10136
Explanation
Correction
The input line buffer is too small.
A line in the input was too large to fit in the input line buffer.
Increase the input line buffer by setting the RPTINBUFSZ internal table.
There is a phase error in the input file.
The format of an input line does not match the INPUT section of the
script. For example, the input line may contain more or less fields than
are declared in the INPUT section of the RPT script.
Examine the input file for extra values on each line. Make sure that each
line of the input file contains a value for each input column listed in the
INPUT section. Also verify that the data types of the value and the input
column match.
Look for non-escaped separator characters, such as “|” or “\”, embedded
in a column value. For example, if a “|” character is embedded in a string
column, RPT interprets the character as the end of the column, so that the
remainder of the column is interpreted as the next column.
–10137
Explanation
Correction
–10138
Explanation
Correction
Error Messages
Insufficient memory for argument list.
When describing a user function call in a script, too many arguments
were used to call the function.
Use fewer arguments or reset the RPT internal tables to reduce the
overall memory requirements for the script.
There is insufficient memory for the output line buffer.
Not enough memory is available for the buffer to print an output line.
Use the WIDTH statement to decrease the output width, if possible, or
reset the RPT internal tables to decrease the amount of memory allocated
for the various tables.
207
–10139
Explanation
Correction
There is insufficient memory to hold variables.
Not enough memory is available to store all the variable values.
Increase the number of variables allowed by setting the RPTFLDCNT
internal table. You can also reduce the total memory requirements by
decreasing the lengths of output strings and report columns
decreasing the number of variables
reducing the complexity of the report script
–10140
Explanation
Correction
–10141
Explanation
Correction
There are no input records.
The specified input file is empty.
Verify that the specified file exists, is readable, and contains the
appropriate data.
The open on tag file ’file_name’ failed.
RPT cannot open the tag file (file_name) that has already been created.
Make sure the file_name file exists. It may have been removed by
another user.
–10142
There was an output width overflow from the print expression on
line line_number.
Explanation
The print expression on line line_number tried to print past the report
width.
Correction
Try one of these solutions:
Increase the output width.
Reduce the size of the information being output.
Break the information into two or more lines.
Move the information to the left on the line (reduce its col
position).
208
Error Messages
–10143
Explanation
Correction
–10144
Explanation
There is a saved string overflow.
An excessively long string is being formatted by the USING option of the
PRINT statement.
Try reducing the length of the input string.
There are too many saved strings.
Too many strings are being formatted with the USING option of the
PRINT statement.
Correction
–10145
Explanation
Correction
–10146
Explanation
Correction
–10147
Explanation
Correction
–10150
Explanation
Correction
Error Messages
Reduce the number of using formats in the report PRINT statements.
Internal error: Unexpected command type number in docom.
This is an internal error and should not occur in the normal execution of
an RPT script.
If this error occurs, please call Customer Support.
Unable to execute the sort command.
RPT could not execute the system sort command.
Make sure that the UNIFY configuration variable is set correctly. Also
verify that the sort command is in your directory search path (specified
by the PATH configuration variable).
Input value out of range.
The input value that was specified for a NUMERIC or AMOUNT column
type cannot be represented in the specified input column length.
Verify that the input value is correct, and increase the input column
length if necessary.
Type conversion error. Left type is type1, right type is type2, operator
is operator.
The data types of the type1 and type2 operands in the expression do not
match and cannot be converted.
Make sure that you have used the correct column and variable names.
Change the operands so that their data types are compatible.
209
–10151
Explanation
An attempt has been made to set the value of an input column on line
line_number. You cannot use the same name for a variable and an input
column in the same report script.
Correction
Make sure you are not setting the value of an input column. Choose a
different name for either the variable or the input column.
–10152
’name’ in the section header on line line_number is not an existing
sort expression.
Explanation
Correction
–10153
Explanation
Correction
–10154
–10155
–10156
–10157
Explanation
Correction
–10158
Explanation
Correction
210
There is an assignment to a non–variable on line line_number.
A BEFORE or AFTER section on line line_number of the report script is
referring to a name that is not listed as a sort element.
Add the name to the sort list or remove the incorrect section.
This was detected in the column expression for the print statement
on line line_number.
The message merely gives the line_number in which the error occurred in
processing a PRINT statement; a second message, with a different
number, will indicate the cause of the error.
See the description for the second message.
This was detected in the expression on line line_number.
This was detected on line line_number.
This was detected in the print statement on line line_number.
This was detected in a set expression on line line_number.
The message merely gives the line_number in which the error occurred; a
second message, with a different number, will indicate the cause of the
error.
See the description for the second message.
An explicit column position was combined with the ’CENTERED’
keyword.
You cannot use both the CENTERED keyword and an absolute column
position.
Remove either the column position or the CENTERED keyword.
Error Messages
–10159
Explanation
The IF clause on line line_number does not contain an integer
expression.
RPT could not recognize the expression in the IF statement on the line
line_number.
Correction
Make sure you use a relational operator in the IF expression.
–10160
Unrecognized type in SET statement. Expression type type1, variable
type type2.
Explanation
An attempt has been made to set a variable to an unrecognized data type
in a SET statement.
Correction
–10161
Explanation
Error Messages
Correct the part of the statement that has the unrecognized data type.
Input column table.column_name does not have its type specified, and
it is not a database column.
RPT could not find the column table.column in the database.
211
Correction
If the input column is an arbitrary name, you may have omitted the data
type and length specification.
If this input column is a database column name, make sure that the
configuration variables describe the correct database. Also, make sure
that the column name is spelled correctly and is sufficiently qualified so
that it is not ambiguous.
If the input column name is correct, make sure that the database type is
correct, and on systems that require users to log into the database, make
sure that the user name and password are valid.
–10162
There is insufficient memory for the input columns.
Explanation
Not enough memory is available to process your report.
Explanation
Increase the size of the input buffer by setting the RPTINBUFSZ internal
table. You may need to decrease another table size as well. You can also
reduce the total memory requirements by
decreasing the lengths of output strings and report columns
decreasing the number of variables
reducing the complexity of the report script
–10163
Explanation
Correction
The variable_name variable cannot be used in this context. This error can
occur as the result of a misspelled function, keyword, variable, or column
name.
Do not use a local variable in this context. Also, make sure that the
variable name is spelled correctly.
–10164
There is a type mismatch in the set statement on line line_number.
Explanation
An attempt has been made on line line_number to assign a value of an
incompatible data type to a variable that has already been set.
Correction
212
Illegal use of variable ’variable_name’.
Use a different local variable for the new data type.
Error Messages
–10165
Explanation
Correction
–10167
Explanation
Correction
–10168
Explanation
Correction
–10169
Explanation
Correction
–10170
Explanation
Correction
Error Messages
There is a nested aggregate operator on line line_number.
An attempt has been made on line line_number to use an aggregate
function as an argument for another aggregate function.
Assign the aggregate function value to a variable and use this variable as
the second aggregate function’s argument.
There is an aggregate expression embedded in a sort expression on
line line_number.
An attempt has been made on line line_number to use an aggregate
function in a sort expression.
Remove the aggregate function from the sort expression.
This occurred in the print expression on line line_number.
The message merely gives the line_number in which the error occurred in
processing a PRINT expression; a second message, with a different
number, will indicate the cause of the error.
See the description for the second message.
There is a variable used in a sort expression on line line_number.
An attempt has been made on line line_number to use a variable as a sort
element.
Make sure that you have not used variables as sort elements and check
for misspellings in the SORT statement.
’Function_name’ is an unrecognized function name.
The function_name function does not exist or cannot be read.
Make sure that the function name is spelled correctly.
213
–10171
Explanation
Correction
–10172
Explanation
Correction
–10173
Explanation
Internal error: Unexpected type in comptyp type.
This is an internal error and should not occur in the normal execution of
an RPT script.
If this error occurs, please call Customer Support.
The variable type is variable_type and the expression type is
expression_type.
This error in processing a SET statement qualifies error –10164 by
describing the data types of the variable (variable_type) and the
expression (expression_type) that caused the data type mismatch.
See the correction for error message –10164.
The value of variable ’variable_name’ is never set.
This error can be caused by one of the following conditions:
The variable_name variable should be a string, but the required
quotes have been omitted.
The value of the variable_name variable has not been initialized
with a SET statement
The variable has not been included as a input column in the INPUT
section.
Correction
–10174
Explanation
Correction
–10175
Explanation
Correction
214
Make sure that the variable is not supposed to be a quoted string. If it is
not a string, make sure that the variable name is spelled correctly.
Initialize the variable or correct the syntax error.
The width has been set to a value less than or equal to the left
margin.
The width must be set to a value larger than the left margin value.
Increase the width or decrease the left margin.
Type conversion error.
An error occurred while trying to convert the input value to a print
expression.
Use a different local variable for the new data type.
Error Messages
–10176
Explanation
Correction
–10177
Explanation
Correction
Internal error: Unrecognized style in settyp.
This is an internal error and should not occur in the normal execution of
an RPT script.
If this error occurs, please call Customer Support.
Invalid input column type table_name.column_name.
RPT does not support the data type of the input column
table_name.column_name. For example, this message is displayed if an
input column is of type BYTE or BINARY.
Make sure that input columns are of data types that are supported by
RPT.
–10181
Explanation
Correction
–10183
Explanation
Correction
–10184
Explanation
Correction
–10204
Explanation
Correction
Error Messages
Unable to open specified input file ’file_name’.
RPT could not find or open the input file file_name.
Make sure that the file name is spelled correctly and that the file has the
correct read permission.
Errors were found while processing the report script.
One or more errors occurred in processing the report script. A second
message, with a different number, will indicate the actual cause.
See the description for the second message.
Syntax error(s) were found in the report script.
One or more syntax errors occurred in processing the report script. A
second message, with a different number, will indicate the actual cause.
See the description for the second message.
Unrecognized character: ’character’.
RPT could not recognize the character character.
If the character is part of a string constant, insert the missing single
quote. If the character is not valid, remove it.
215
–10205
Explanation
There is an invalid non-section statement.
This error can be caused by the following conditions:
misspelling a statement keyword
omitting a comma
trying to print a multiple-word heading without enclosing it in
single quotation marks
omitting the END statement to terminate the report script
not putting the SET statement in a section
Correction
–10206
Explanation
Correction
–10207
An integer constant was expected.
The syntax for the statement requires an integer constant.
Make sure that an integer constant is specified.
A sort command is not allowed on presorted input.
Explanation
An attempt was made to use both the SORT statement and the SORTED
option. RPT does not allow the SORT statement to be used when the
SORTED option is used with the INPUT statement.
Correction
Either remove the unnecessary SORT statement or remove the SORTED
keyword from the INPUT statement.
–10208
Explanation
Correction
216
Make sure that the RPT script does not contain any of the preceding
syntax errors in a non-section statement.
A string constant was expected.
The syntax for the statement requires a a string constant enclosed in
single quotation marks (’constant’).
Make sure that the constant value is not missing one of the single
quotation mark.
Error Messages
–10209
Explanation
There is an invalid input item.
RPT could not recognize an input column name in the INPUT statement.
This error can also be caused by including a comma after the last input
item. RPT then reads the next line as part of the INPUT statement.
Correction
–10210
Explanation
Correction
–10211
Explanation
Correction
–10212
Explanation
Correction
–10213
Explanation
Correction
Error Messages
Make sure that you are not using an RPT keyword or function name as an
input column name. Also make sure that there is no comma at the end of
the INPUT statement.
There is an invalid type expression.
RPT could not recognize the data type of an input column listed in the
INPUT statement.
Make sure that input column data types are specified with the correct data
type keyword spelling.
There is an integer constant expected for the length.
An attempt was made to specify a non-integer length for an input
column. When a data type and length is assigned to an input column in
the INPUT statement, the length must be an integer.
Use an integer to specify the input column length.
There is an invalid statement.
RPT could not recognize the word as a section identifier.
Often this error is caused by a misspelling of the first word on a
statement line following a section statement.
There is an error in an ’IF’ expression.
RPT found an incorrect expression in an IF statement.
Examine the syntax of the IF statement to make sure that the IF, THEN,
and ELSE keywords are used correctly. For the syntax and usage
description of the IF statement, see Unify DataServer: Creating Reports
with RPT Report Writer.
217
–10214
Explanation
Either ’desc’ or a named expression was expected.
RPT found a syntax error in a SORT statement or in one of its
expressions.
Correction
–10215
Explanation
Correction
–10216
There is an invalid print item.
RPT found a syntax error in a PRINT expression.
Make sure that the print expression does not contain keywords. To print
out the string value for a keyword, you must enclose the word in single
quotation marks (’word’). For the syntax and usage description of the IN
COLUMN clause in the PRINT statement, see Unify DataServer:
Creating Reports with RPT Report Writer
There is an invalid ’IN COLUMN’ clause.
Explanation
An integer constant or variable must follow the IN COLUMN clause.
Correction
Examine the PRINT statement for a missing position value in the IN
COLUMN clause. For the syntax and usage description of the IN
COLUMN clause in the print statement, see Unify DataServer:
Creating Reports with RPT Report Writer.
–10217
Explanation
Correction
–10218
Explanation
Correction
218
Look for an extra comma at the end of the SORT statement. For the
syntax and usage description of the SORT statement, see Unify
DataServer: Creating Reports with RPT Report Writer.
There is an invalid ’USING’ clause.
RPT found a syntax error in the USING clause of a print statement.
Examine the syntax of the USING clause in the print statement. For the
syntax and usage description of the USING clause in the print statement,
see Unify DataServer: Creating Reports with RPT Report Writer.
There is an invalid aggregate expression.
RPT found a syntax error for an aggregate expression in an aggregate
function.
Examine the argument list for an invalid aggregate expression. For
information about using aggregate expressions in report scripts, see Unify
DataServer: Creating Reports with RPT Report Writer.
Error Messages
–10219
Explanation
Correction
–10220
Explanation
Correction
–10222
Explanation
Correction
–10225
There is an invalid function argument list.
RPT found a syntax error in the argument list of a function.
Examine the argument list for a missing parenthesis, a missing comma,
or missing single quotation mark.
Unable to open script file ’file_name’.
RPT could not find or open the file_name report script file.
Make sure that report script file name is spelled correctly and that the file
has correct file permissions.
Column data type length greater than maximum length.
The length specified in the INPUT statement for a column is greater than
the maximum length supported
Check the restrictions for the data types that you are using.
Illegal use of ’need’ statement.
Explanation
The NEED statement cannot be used in the HEADER or FOOTER section
or in an IF statement. Nor can the NEED statement be used more than
once in an event section where its use is valid.
Correction
If you are using a NEED statement in a HEADER or FOOTER section or
in an IF statement, remove the NEED statement. If you are using more
than one NEED statement in any other event section, correct your script
to use only one NEED statement
–10226
Explanation
Correction
Error Messages
An event section can be used only once in a report format.
An event section, such as HEADER, FOOTER, or BEFORE REPORT,
can be used only once in a report format script.
Find the duplicate event section and remove it, rewriting the report
format script if necessary
219
–10230
Explanation
Correction
The internal_table_name table has overflowed.
The capacity of the internal_table_name table has been exceeded.
Reduce the number of elements of the indicated type in the script or
increase the size of the indicated table by using the specified
internal_table_name.
See the Unify DataServer: Creating Reports with RPT Report Writer
“Report Writer Basics” for a listing of the internal tables and the
configuration variables (with the default sizes) to increase the value of
the variable associated with the table.
For example, the following message indicates that you should either
reduce the number or size of the string constants in the script or increase
the size of the RPTCONCNT internal table.
The String table has overflowed
–10231
Explanation
There is insufficient memory to store the constants.
Not enough memory is available to store all data associated with the
PRINT statement.
Correction
Increase the number of constants allowed by using the RPTCONCNT
internal table, or reduce the total memory requirements by
decreasing the lengths of output strings and input columns
decreasing the number of variables
reducing the complexity of the report script
–10250
Explanation
Correction
–10260
Explanation
Correction
220
Output width overflow from function ’function_name’.
This is an internal error and should not occur in the normal execution of
an RPT script.
If this error occurs, please call Customer Support.
Operator not found.
This is an internal error and should not occur in the normal execution of
an RPT script.
If this error occurs, please call Customer Support.
Error Messages
–10261
Explanation
Correction
–10263
Explanation
Correction
–10264
Explanation
Unknown string expression type.
This is an internal error and should not occur in the normal execution of
an RPT script.
If this error occurs, please call Customer Support.
Unexpected type in intsize number.
This is an internal error and should not occur in the normal execution of
an RPT script.
If this error occurs, please call Customer Support.
Unable to execute FNDFLD –– error_message.
RPT could not execute the FNDFLD program. The following error
message provides more information on the problem.
Correction
–10265
Explanation
Make sure that the UNIFY configuration variable is set correctly. Also
make sure that the FNDFLD program is on the directory search path
specified by your PATH configuration variable.
The write to FNDFLD failed –– error_message.
RPT could not write to the FNDFLD program. The specified error
message provides more information about the problem.
Correction
–10290
Explanation
Correction
Error Messages
Make sure that the UNIFY configuration variable is set correctly and that
there is write permission on the directory.
–c option not supplied in command line.
The command line to config?dbld?EPP?SQL?uperf is missing the –c
argument, although one was expected given the command line that was
entered.
Re-enter the command line with the –c argument
221
–10300
Explanation
Correction
–10310
Explanation
Correction
–10311
Explanation
Correction
–10312
Explanation
Correction
–10314
Explanation
Correction
–10315
Explanation
Correction
222
is not a file.u; check the input file list for uld.
The file.u file that was output from ucc is corrupt.
Recompile the corresponding .c file.
Unable to begin a transaction.
uld cannot begin a transaction.
Verify that the database is up and that enough resources are available.
argument error, schema multiply defined
The –s schema_name argument was specified more than once on the
command line to upp.
Specify only one schema name on the command line.
invalid schema
The schema name specified on the command line to upp was invalid.
Make sure that the schema name is spelled correctly, exists, and that you
have correct access permissions.
Unable to open file: file_name
Contained in the message.
Make sure that the file name is spelled correctly, that the file exists, and
that you have the correct access permissions for the file.
Unable to create file: file_name
Contained in the message.
Make sure that you have write permission for the directory where the file
is to be created.
Error Messages
–10316
Explanation
Correction
–10384
Explanation
Correction
–10385
Explanation
Correction
–10386
Unable to open database volume
The volstats utility cannot open the specified volume.
Make sure that the volume name or volume ID is specified correctly on
the command and that you have read permission for the database file.
Could not start budb reader process.
The burd program cannot be started.
Make sure that the burd program is on your path and that you have
execute permission for it.
Unable to determine database name.
This is an internal error and should not occur in normal operation.
If this error occurs, please call Unify Customer Support.
Backup aborted.
Explanation
A fatal error occurred while the database was being backed up. This
message was preceded by a message that indicated the cause of the
problem.
Correction
Depending on the problem that generated this error message, either
restart the backup or call unify Customer Support.
–10387
Explanation
Correction
Unable to get user response.
A response that was needed for performing the backup could not be
obtained.
Make sure that input has not been redirected incorrectly.
–10388
Unable to open database.
Explanation
Contained in the message.
Correction
Error Messages
Make sure that DBPATH and DBNAME are set correctly and that you have
the correct access privileges. If the environment is set up correctly and
this error persists, please call Unify Customer Support.
223
–10389
Explanation
Correction
–10391
Explanation
Correction
Additional Help
–10401
Explanation
Correction
–10402
Explanation
Unable to continue database backup.
A fatal error occurred while the database was being backed up. The
message that immediately preceded this one indicated the cause of the
problem.
Depending on the problem that generated this error, either restart the
backup or call Unify Customer Support.
Database is not available.
The specified database cannot be opened by SQL/A.
make sure that the DBPATH, DBNAME, DBHOST, and DBUSER
configuration variables are set correctly. If these variables are set
correctly, you can create a database by using CREATE DATABASE.
For the syntax and description for the CREATE DATABASE statement,
see Unify DataServer: SQL/A Reference.
Syntax error: skipping to next statement.
A syntax error has occurred on the line specified which prevents the
preprocessor from processing that statement. The preprocessor skips the
statement and continues to the next line.
Fix the syntax error(s) and try preprocessing again.
column_name is an invalid column name.
The column name does not exist in the data dictionary as specified.
If the column name has been qualified with a table name, then the
column does not exist in that table. If the column name does not have a
qualifier, then the column cannot be found in any table listed in the
FROM clause or in any table listed in the FROM clause of an outer
SELECT.
Correction
Additional Help
224
Check the spelling of the column name. The COLUMNS command will
give a list of columns for a table.
Unify DataServer: SQL/A Reference
Error Messages
–10404
Explanation
Correction
Additional Help
–10405
Explanation
Correction
Additional Help
–10407
Explanation
Correction
Additional Help
–10411
Explanation
Invalid query block.
The syntax used for SELECT statement is incorrect. It may have an
incorrect ordering of sections such as HAVING before GROUP BY.
Correct the syntax of the SELECT statement.
Unify DataServer: SQL/A Reference
Invalid WHERE clause.
A WHERE clause specified is incorrect.
Correct the syntax or location of the WHERE clause.
SELECT statement in Unify DataServer: SQL/A Reference
There were no rows selected.
No rows where found which meet the specified selection criteria (if any).
If this is not the expected result, check the selection criteria for
correctness. Further checks on the actual contents of the database may
also be useful.
SELECT statement in Unify DataServer: SQL/A Reference
syntax error.
The statement specified contains a syntax error.
Correction
Correct the syntax of the statement.
Additional Help
Unify DataServer: SQL/A Reference
–10413
Explanation
Correction
Error Messages
on or about line line_number.
An error occurred on or about the indicated line. An accompanying
message indicates the type of error.
See the correction for the accompanying message.
225
–10414
’table_name’ is an invalid table, i.e. not found in data dictionary.
Explanation
The specified table does not exist in the data dictionary or has an
exclusive lock on it from another transaction. If the table was qualified
with a schema name, then the table does not exist in that schema. If no
qualifier was specified, then the table does not exist in the current
schema.
Correction
Verify the spelling of the table name. The TABLES command displays a
listing of accessible tables.
For locked tables, wait for the lock to be released.
Additional Help
–10415
Explanation
Correction
Additional Help
–10416
Explanation
Left type is type1, right type is type2, operator is operator.
An invalid combination of data types has been specified for the operator.
Left and right types are the data types of the operands for the operator.
Correct the data type combinations.
“Compatible Data Types” in Unify DataServer: Writing Interactive SQL/A
Queries
Unable to open script file ’file_name’.
The script file file_name cannot be found or opened.
Correction
Verify the spelling of the script file name and check that the file exists in
the current directory.
–10417
Table ’table_name’ is locked by another user and cannot be accessed.
Explanation
Correction
226
Unify DataServer: SQL/A Reference
The indicated table is locked by another user and cannot be locked for
reading or writing at this time.
Wait and retry the operation.
Error Messages
–10421
Warning: The database is being shut down.
Explanation
A database shutdown (shutdb) is in progress.
Correction
–10422
Complete your operation and exit SQL/A so that the shutdown can be
completed.
Too many columns in statement.
Explanation
In an Embedded SQL/A statement, the maximum number of columns
referenced has been exceeded.
Correction
Remove any unnecessary columns or try breaking the statement down
into smaller statements. Or, change the setting for the SQLFLDCNT
configuration variable.
Additional Help
–10423
Explanation
Correction
Additional Help
–10424
Explanation
Correction
Additional Help
Error Messages
Unify DataServer: Configuration Variable and Utility Reference
Too many tables in statement.
In an Embedded SQL/A statement, the maximum number of tables
referenced has been exceeded.
Remove any unnecessary tables or try breaking the statement down into
smaller statements. Or, change the setting for the SQLTABCNT
configuration variable.
Unify DataServer: Configuration Variable and Utility Reference
Unable to add constraint.
The UNIQUE or PRIMARY constraint specified could not be added.
Refer to the description of the subsequent specific error (if any) which
has occurred. Remove the constraint or change the column’s other
attributes.
“Creating and Removing Database Objects” in Unify DataServer: Writing
Interactive SQL/A Queries.
227
–10425
Explanation
Unable to allocate memory.
SQL/A was unable to allocate the amount of memory needed to perform
the specified operation.
Correction
–10426
Explanation
Correction
Additional Help
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
Invalid ALTER DEFAULT statement.
The ALTER DEFAULT statement specified is incorrect.
Correct the statement.
ALTER DEFAULT SCHEMA statement in Unify DataServer: SQL/A
Reference
–10427
Explanation
Correction
Additional Help
–10428
Explanation
Correction
Additional Help
–10429
Explanation
Correction
Additional Help
228
Unable to add new column names.
The column names specified could not be added.
Refer to the description of the subsequent specific error (if any) which
has occurred. Correct the syntax of the statement.
CREATE TABLE statement in Unify DataServer: SQL/A Reference
Unable to add new table names.
The table names specified could not be added.
Refer to the description of the subsequent specific error (if any) which
has occurred. Correct the syntax of the statement.
CREATE TABLE statement in Unify DataServer: SQL/A Reference
Invalid ALTER TABLE option.
An invalid operation was specified in the ALTER TABLE statement.
Correct the statement.
ALTER TABLE statement in Unify DataServer: SQL/A Reference
Error Messages
–10430
Explanation
Correction
Invalid ALTER VOLUME configuration option.
An invalid operation was specified in the ALTER VOLUME statement.
Refer to the Interactive SQL/A manual for proper usage of the ALTER
VOLUME statement.
–10431
DIRECT specified multiple times in column ’column_name’ in table
’table_name’.
Explanation
The table was specified as having more than one column with the
DIRECT configuration option. A table can only contain one column with
this option.
Correction
Redefine the table as having only one column with the DIRECT option.
–10432
The number of constants does not match the number of columns.
Explanation
The number of constants specified in the INSERT statement does not
match the number of columns being inserted into.
Correction
Additional Help
–10433
Explanation
Correction
–10434
Explanation
Correction
Error Messages
Verify the constant list has the same number of values as the number of
columns being inserted into. Note that a column list may be specified if
the constant list does not contain a value for each column in the table.
Unify DataServer: Writing Interactive SQL/A Queries
Unknown system group specified.
The GROUP specified for the group option in the CREATE DATABASE
command, is not a valid group for your system.
Check the spelling of the group specified. Also make sure an entry for the
group specified is in the /etc/group file.
Unknown system user specified.
The user specified for the user option in the CREATE DATABASE
command, is not a valid user for your system.
Check the spelling of the user specified. Also make sure an entry for the
user specified is in the /etc/passwd file.
229
–10435
bldti: error inserting into temp index index_number.
Explanation
A temporary index being built for a join or subquery could not be
successfully updated.
Correction
Verify that there is enough disk space for the temporary index file.
–10436
Explanation
Correction
–10437
Explanation
Correction
–10438
Explanation
bldsrt: error opening project file.
A temporary file used for sorting could not be successfully opened or
created.
A process or system file limit may have been exceeded. There may also
not be enough disk space or inodes in the UNIFYTMP directory. Check the
system console for messages. If it appears to be that SQL/A has tried to
open too many files, try simplifying the offending statement or
reconfigure the system to allow more open files.
bldsrt: error opening sort file.
A temporary file used for sorting could not be successfully opened or
created.
A process or system file limit may have been exceeded. There may also
not be enough disk space or inodes in the UNIFYTMP directory. Check the
system console for messages. If it appears to be that SQL/A has tried to
open too many files, try simplifying the offending statement or
reconfigure the system to allow more open files.
bldjti: error in closing temp index.
SQL/A was unable to successfully close a temporary index being used for
a join.
Correction
–10439
Explanation
If this error occurs, please call Customer Support.
bldjti: not enough memory.
SQL/A was unable to allocate the required amount of memory to use a
temporary index.
Correction
230
A process size or system limit may have been exceeded. Check the
system console for messages. Exiting SQL/A and then retrying the
offending statement may also correct the situation.
Error Messages
–10440
Explanation
Correction
Additional Help
–10441
Explanation
Correction
Additional Help
–10442
Explanation
Correction
Invalid btree configuration option.
An invalid option has been specified in the CONFIGURATION section of
a CREATE BTREE statement.
Correct the syntax of the statement.
CREATE BTREE statement in Unify DataServer: SQL/A Reference
Invalid btree column specification.
The column list specified in a CREATE BTREE statement is invalid.
Check the column names and syntax of the statement.
CREATE BTREE statement in Unify DataServer: SQL/A Reference
Invalid btree index name specification.
The name specified in a DROP BTREE statement is invalid.
Check the spelling of the index name and the syntax of the DROP
BTREE statement.
Additional Help
–10443
Explanation
Correction
Additional Help
–10444
Explanation
Correction
Additional Help
Error Messages
DROP BTREE statement in Unify DataServer: SQL/A Reference
Invalid btree index syntax.
The syntax used for the CREATE BTREE statement is incorrect.
Correct the syntax of the statement.
CREATE BTREE statement in Unify DataServer: SQL/A Reference
SQLDDLSIZ is zero or non-numeric.
The SQLDDLSIZ configuration parameter must be a positive nonzero
value. It is used to define the size work the workspace used by SQL/A
DDL operations.
Check the current value of SQLDDLSIZ using the config utility and
change appropriately.
Unify DataServer: Configuration Variable and Utility Reference
231
–10445
Explanation
getval: could not malloc number bytes.
SQL/A was unable to allocate the amount of memory needed to perform
the specified operation.
Correction
–10447
Explanation
Correction
Additional Help
–10448
Invalid column configuration option.
The CONFIGURATION section of the column specification contains an
invalid option.
Correct the syntax of the statement.
CREATE TABLE statement in Unify DataServer: SQL/A Reference.
Column count mismatch in view.
Explanation
The number of selection expressions in the SELECT statement of a view
definition does not match the number of column names specified for the
view.
Correction
Verify that the column name list and selection expressions have the same
number of items.
–10449
Explanation
Correction
–10450
Explanation
Correction
232
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
Couldn’t find a * column.
An error has been detected in the preprocessor’s symbol table. This is an
internal error and should not occur in the normal execution of SQL/A.
If this error occurs, please call Customer Support.
Cannot open input file ’file_name’.
The input file specified in an INSERT statement cannot be opened.
Verify the spelling of the specified file. Also check for the existence of
the input file.
Error Messages
–10451
Explanation
Correction
–10452
Explanation
Correction
Additional Help
–10453
Explanation
Correction
Additional Help
–10455
Unable to close database.
SQL/A could not close the database.
Refer to the description of the subsequent specific error which has
occurred.
Reference to undeclared cursor ’cursor_name’.
An Embedded SQL/A statement has referenced a cursor which has not
previously been defined in a DECLARE CURSOR statement. All
references to a cursor must follow the declaration of the cursor in the
source file.
Verify the spelling and declaration of the cursor being referenced.
DECLARE CURSOR statement in Unify DataServer: SQL/A Reference
Cursor ’cursor_name’ is not updateable.
The cursor being updated is not an updatable cursor. A cursor is
updatable if it is declared with a restricted version of the SELECT
statement.
Correct the cursor declaration.
DECLARE CURSOR in Unify DataServer: SQL/A Reference
Columns are not permitted on Schemas.
Explanation
A column list can only be specified for a particular privilege when the
granting or revoking table level privileges. Column lists cannot be
specified when granting or revoking schema level privileges, not on
schemas.
Correction
Check the spelling and ordering of options. Also check for an invalid
option.
Additional Help
Error Messages
GRANT statement in Unify DataServer: SQL/A Reference
233
–10456
Explanation
Correction
–10457
SQL/A was unable to reset a file pointer to the beginning of the file.
If this error occurs, please call Customer Support.
Invalid column specification.
Explanation
A column definition in a CREATE TABLE statement is invalid.
Correction
Check the ordering of options. Also check for an invalid option.
Additional Help
–10459
CREATE TABLE statement in Unify DataServer: SQL/A Reference
CREATE VIEW may only contain SELECT statements.
Explanation
The definition of a view can only contain one or more SELECT
statements.
Correction
Check the ordering of options. Also check for an invalid option.
Additional Help
–10460
Explanation
Correction
Additional Help
234
Cannot rewind file.
CREATE VIEW statement in Unify DataServer: SQL/A Reference
Invalid CREATE VIEW syntax.
The syntax for a CREATE VIEW statement is incorrect.
Check the ordering of options. Also check for an invalid option.
CREATE VIEW statement in Unify DataServer: SQL/A Reference
Error Messages
–10461
Delete aborted. All locks could not be acquired.
Explanation
All rows which were to be deleted could not be locked with an XLOCK.
The current transaction level specifies that the delete operation is to be
aborted if this situation occurs. An XLOCK cannot be obtained if either
another transaction holds an SLOCK or XLOCK on the row or table
already, or the maximum number of locks held on the database has been
exceeded.
Correction
If the delete failed due to locking conflicts, then retry the operation when
all locks can be obtained.
If no more locks could be obtained on the database, then configure the
database to allow more locks.
Additional Help
Unify DataServer: Managing a Database
–10462
All synonyms for column ’column_name’ cannot be dropped. At least
one must remain.
Explanation
Every column in a table must have one or more names associated with it.
This error occurs when you attempt to drop the last name for a column.
Correction
Additional Help
–10463
Explanation
Correction
Additional Help
–10464
Check the column names and synonyms for a column.
COLUMNS command in Unify DataServer: SQL/A Reference
All table names cannot be dropped. At least one must remain.
Every table in the database must have one or more names associated with
it. This error occurs when you attempt to drop the last name for a table.
Check the table names and synonyms that exist for a table.
TABLES command in Unify DataServer: SQL/A Reference
Unable to drop all table names.
Explanation
An attempt to drop a name for a table has failed. The exact cause of the
failure is displayed in the message that follows this message.
Correction
Refer to the description of the specific error which has occurred. Check
the syntax of the statement.
Additional Help
Error Messages
DROP SYNONYM statement in Unify DataServer: SQL/A Reference
235
–10470
Explanation
The particular operation specified requires that the database is open.
Correction
Open the appropriate database and then retry the specified operation.
Additional Help
–10471
OPEN DATABASE statement in Unify DataServer: SQL/A Reference
Invalid database option.
Explanation
An invalid option has been specified in a CREATE DATABASE
statement.
Correction
Check the ordering of options. Also check for an invalid option.
Additional Help
–10472
Explanation
Correction
–10473
Explanation
Correction
–10474
236
Database is not open.
CREATE DATABASE statement in Unify DataServer: SQL/A Reference
Invalid format for column column_name, row row_number.
An invalid data format was specified in the input data file.
Check the format of the data for the specified column for row_number in
the input data file.
Invalid range for column ’column_name’, row row_number.
The value in the input file for the row row_number for the column
column_name is either too large or too small.
Check the value for the specified row and column in the input file. This
value may have to be changed or the column being updated may have to
be redefined to accept this type of data value.
Valid value for ’lines’ is 0 or integer > 3. Current value is number.
Explanation
The valid value for lines is 0 or a positive integer greater than three (3).
With “lines 0”, no header is printed. This is useful for dumping data to a
binary/ASCII output file with Interactive SQL/A. If you do not use a lines
value of 0, a minimum value of 4 is required: 2 lines are used for the
header, one line for the data, and one line to separate the data from the
next header line.
Correction
Change the current lines value of number so that it is a valid lines value.
Make sure you specify a lines value of 0, if you do not want headings, or
at least 4, if you do want headings.
Error Messages
–10475
Explanation
Not enough space for column ’column_name’, row row_number.
The value for the given TEXT or BINARY column is too large to process.
SQL/A must be able to write the variable length value to a temporary file
in the directory indicated by UNIFYTMP and must also be able to hold the
entire value in memory. This error occurs if either of these conditions
fail.
Correction
Additional Help
–10476
Explanation
Correction
–10477
Explanation
Correction
Additional Help
–10478
Explanation
Correction
Error Messages
Check for free disk space in the UNIFYTMP directory. Also check the
system console for error messages. The data file could also be loading
using dbld, which inserts TEXT and BINARY values directly into the
database and does not require temporary storage.
Unify DataServer: Configuration Variable and Utility Reference
doload: out of memory.
SQL/A was unable to allocate the amount of memory needed to perform
the specified INSERT or UPDATE operation.
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
Invalid DROP SYNONYM syntax.
The syntax used for the DROP SYNONYM statement is incorrect.
Check the spelling and placement of options.
DROP SYNONYM statement in Unify DataServer: SQL/A Reference.
Duplicate declare cursor ’cursor_name’.
The cursor cursor_name has previously been declared in the source file.
Each cursor declared within a source file must have a unique name.
Verify that all cursor names are unique. Check the spelling of the
conflicting cursors and make the appropriate correction.
237
–10479
Explanation
Duplicate host declaration: ’variable_name’ ignored.
The host variable variable_name has been previously declared in the
source file. All host variables within a source file must have unique
names.
The preprocessor is ignoring this declaration and continuing to the next
line.
Correction
–10480
Explanation
Correction
Additional Help
–10481
Explanation
Correction
Additional Help
Check the spelling of the conflicting host variables and make the
appropriate changes.
Expecting database name.
The CREATE DATABASE statement requires a database name to be
specified.
Check the spelling and placement of the database name.
The CREATE DATABASE statement in Unify DataServer: SQL/A
Reference.
Error in regular expr pattern.
The pattern specified in a REGLIKE expression is invalid.
Correct the pattern.
“Selecting Rows and Columns” in Unify DataServer: Writing Interactive
SQL/A Queries
–10482
Explanation
Correction
238
SQL: Error initializing backend error_number.
A backend query processor could not be started for an Embedded SQL/A
application. The error code error_number is the error message number of
the specific error that has occurred.
Refer to the description of the error identified by error_number.
Error Messages
–10483
Explanation
Error notifying application of end-of-scan.
A backend query processor was unable to send a message to the
Embedded SQL/A application it was servicing.
This error can occur if the application exits abnormally while the
backend is still performing work for the application. In this case, this
error can be ignored.
Correction
–10484
Explanation
Correction
Additional Help
–10485
If the application receives an SQLCODE value signifying that an error
has occurred while trying to receive a message from a backend, and the
backend logs this error. In this case, please call Customer Support.
Select expression expression_number is not a column name.
The CREATE VIEW statement does not include a column name list for
the view being defined. Therefore, each select expression in the select list
must contain only a column name. The SELECT statement specified
contains one or more expressions in the select list.
Column names must be specified for the new view or you must modify
the SELECT statement to project only columns.
CREATE VIEW statement in Unify DataServer: SQL/A Reference
Nested aggregates cannot be projected with other types of
expressions.
Explanation
The projected list includes a nested aggregate function and another type
of expression. It is invalid to project a nested aggregate function (like
AVG(MAX(salary))) with another value expression or with a column.
Correction
Change your query so that nested aggregates are not projected with other
types of expressions.
–10486
Explanation
Correction
Additional Help
Error Messages
Expecting schema name.
The CREATE SCHEMA statement requires a schema name for the
schema being created.
Check the placement and spelling of options and keywords.
CREATE SCHEMA statement in Unify DataServer: SQL/A Reference.
239
–10487
Explanation
Error notifying application of error error_number.
A backend query processor was unable to send a message to the
Embedded SQL/A application it was servicing.
This error can occur if the application exits abnormally while the
backend is still performing work for the application. In this case, this
error can be ignored.
Correction
–10489
Explanation
Correction
–10490
Explanation
Correction
Additional Help
–10491
syntax error in pattern.
ESCAPE character escape_char appears at the end.
This error occurs when the escape character escape_char was found at
the end of the pattern string. This violates the condition that all escape
characters must be followed by an additional character.
Correct the pattern string.
Expecting table name.
The CREATE TABLE and ALTER TABLE statements require the name of
the table to be operated on.
Check the spelling and placement of keywords and options.
The CREATE TABLE and ALTER TABLE statements in Unify
DataServer: SQL/A Reference.
Undeclared host variable: variable_name.
Explanation
An Embedded SQL/A statement has referenced the host variable
variable_name and this variable has not been previously declared in a
DECLARE SECTION.
Correction
Verify the spelling of the host variable and make sure all references to
host variables appear after they are declared in the source file.
Additional Help
240
If the application receives an SQLCODE value signifying that an error
has occurred while trying to receive a message from a backend, and the
backend logs this error. In this case, please call Customer Support.
The DECLARE SECTION statement in Unify DataServer: SQL/A
Reference.
Error Messages
–10492
Explanation
Correction
Additional Help
–10493
Explanation
Expecting volume name.
The CREATE VOLUME statement requires that a name be specified for
the volume being created.
Check the spelling and placement of keywords and options.
The CREATE VOLUME statement in Unify DataServer: SQL/A Reference
.
Error fetching default schema information for current user.
SQL/A was unable to retrieve information for the current user. The error
message following this one describes the specific error that has occurred.
Correction
–10494
Explanation
Correction
–10495
Explanation
Refer to the description of the specific error which has occurred.
The first time was column ’column_name’.
This message always appears with message –10431 to indicate the first
column that had a DIRECT clause.
See message –10431.
Error fetching information about current user.
SQL/A was unable to retrieve information concerning the current user.
The error message following this one describes the specific error which
has occurred.
Correction
–10496
Explanation
Refer to the description of the specific error which has occurred.
Unable to grant access to user ’user_name’. error_message
SQL/A was unable to GRANT ACCESS on the specified schema or
database to the user user_name. The error message following this one
describes the specific error that has occurred.
Correction
Additional Help
Error Messages
Refer to the description of the specific error that has occurred.
GRANT ACCESS statement in Unify DataServer: SQL/A Reference.
241
–10497
Explanation
Correction
Additional Help
–10498
Explanation
Correction
Additional Help
–10499
Explanation
Correction
Additional Help
–10500
Explanation
Correction
Additional Help
242
Unable to grant access to user ’user_name’.
SQL/A was unable to GRANT ACCESS on the database to the specified
user because the user does not exist. The message following this one
describes the specific error which has occurred.
Refer to the description of the specific error which has occurred.
GRANT ACCESS statement in Unify DataServer: SQL/A Reference.
Cannot group by view columns which are expressions.
The GROUP BY clause has specified a column from a view. In the view,
this column is defined as an expression. View columns which are defined
as expressions cannot be used in a GROUP BY clause.
Rewrite the SELECT statement to not use this particular column.
SELECT statement in Unify DataServer: SQL/A Reference.
GROUP BY not allowed.
The SELECT statement has a GROUP BY clause and a FROM clause
containing a view which also contains a GROUP BY, HAVING, or
aggregate function in its definition.
Rewrite the SELECT statement to not use this particular view or not use a
GROUP BY statement.
SELECT statement in Unify DataServer: SQL/A Reference.
Invalid GRANT statement syntax.
The syntax used for the GRANT statement is incorrect.
Check the spelling and placement of keywords and options.
GRANT statements in Unify DataServer: SQL/A Reference.
Error Messages
–10501
Explanation
Unable to retrieve user name.
SQL/A was unable to retrieve information concerning the current user.
The error message following this one describes the specific error which
has occurred.
Correction
–10502
Explanation
Correction
–10503
Explanation
Correction
Additional Help
–10504
Explanation
Correction
Additional Help
–10505
Explanation
Correction
Additional Help
Error Messages
Refer to the description of the specific error which has occurred.
Error from getval in binary mode.
An unexpected error has occurred in reading an input file (either internal
or user-supplied).
If this error occurs, please call Customer Support.
HAVING clause not allowed.
The SELECT statement has a HAVING clause and a FROM clause
containing a view which also contains a GROUP BY, HAVING, or
aggregate function in it’s definition.
Rewrite the SELECT statement to not use this particular view or not use a
HAVING statement.
SELECT statement in Unify DataServer: SQL/A Reference.
Invalid hash index configuration option.
The CREATE HASH statement contains an invalid option in the
CONFIGURATION section.
Check the spelling and placement of keywords and options.
CREATE HASH INDEX statement in Unify DataServer: SQL/A Reference.
Invalid hash index syntax.
The syntax used for the CREATE HASH statement is incorrect.
Check the spelling and placement of keywords and options.
CREATE HASH INDEX statement in Unify DataServer: SQL/A Reference.
243
–10506
Explanation
Correction
Additional Help
–10507
Explanation
Invalid hash index name specification.
The index name specified in the DROP HASH statement is invalid.
Check the spelling and placement of keywords and options.
DROP INDEX statement in Unify DataServer: SQL/A Reference.
Unable to invalidate all dependent objects.
SQL/A was unable to invalidate all views which were dependent on the
schema or table being dropped. Most likely, there are other applications
which are currently using one or more of these objects, and are therefore
preventing the objects from being dropped or invalidated.
Correction
–10508
Explanation
Correction
Additional Help
–10509
Explanation
Wait for all objects to be free and then repeat the operation.
Invalid schema name ’schema_name’.
The schema name schema_name specified on the preprocessor command
line cannot be found or switched to by the current user. The error
message following this one gives the specific error which has occurred.
Check the syntax of the command. Also refer to the description of the
specific error which has occurred.
Unify DataServer: Configuration Variable and Utility Reference
Not enough DDL workspace. Increase SQLDDLSIZ – current: size.
SQL/A does not have sufficient workspace for the specified DDL
operation. The workspace size can be set with the configuration
parameter SQLDDLSIZ.
Correction
Additional Help
244
Check the current setting of SQLDDLSIZ with the utility config and
increase accordingly.
Unify DataServer: Configuration Variable and Utility Reference
Error Messages
–10511
Explanation
Correction
Additional Help
–10512
Explanation
Correction
Additional Help
–10513
inisrt: error opening project file.
SQL/A was unable to open a temporary file used for sorting.
A process or system limit may have been exceeded for maximum number
of open files. Check the console for system errors. Disk space or inode
count may also have been exceeded in the directory indicated by the
UNIFYTMP configuration parameter. Exiting SQL/A and then retrying the
statement may also correct the situation.
Unify DataServer: Configuration Variable and Utility Reference
Insertion from file not allowed.
Using an INSERT statement with the input data coming from a file is
allowed only in Interactive SQL/A.
Rewrite the application to read from the file. Perform an INSERT
statement for each row read in.
INSERT statement in Unify DataServer: SQL/A Reference.
Invalid host id syntax.
Explanation
A host variable reference in the statement is invalid. Host variables are
identifiers which begin with the “:” character.
Correction
Verify the spelling of all host variables in the statement and perform the
appropriate modifications.
–10515
Explanation
Correction
–10516
Explanation
Correction
Error Messages
SQL: Invalid number of backend parms.
A backend query processor started by an Embedded SQL/A application
has received invalid parameters on its command line. This is an internal
error and should not occur in the normal execution of SQL/A.
If this error occurs, please call Customer Support.
doload: invalid number of columns number_of_columns.
SQL/A has detected an error while updating a table. This is an internal
error and should not occur in the normal execution of SQL/A.
If this error occurs, please call Customer Support.
245
–10517
Explanation
Correction
–10518
Explanation
Correction
–10520
Explanation
Correction
Additional Help
–10521
Explanation
Error recovering from interrupt error_number.
A backend query processor was unable to recover from an interrupt. This
is an internal error and should not occur in the normal execution of
SQL/A.
If this error occurs, please call Customer Support.
NULL is not allowed in a constant list.
Constant lists may contain only non-null values.
Modify the query to use the IS NULL operator and remove NULL from
the constant list.
column_number is an invalid column number in ORDER BY.
A column number specified in the ORDER BY clause is invalid. Valid
column numbers must be between 1 and the number of select expressions
in the select list.
Check the syntax of the statement.
SELECT statement in Unify DataServer: SQL/A Reference.
inisrt: no memory.
SQL/A was unable to allocate the amount of memory needed to perform a
sort operation.
Correction
–10522
Explanation
Correction
Additional Help
246
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
Invalid ORDER BY: ’column_name’ is not a projected column.
The ORDER BY clause in the statement contains a column specification
which is not projected in the select list. All columns specified in an
ORDER BY clause must be columns projected in the select list.
Modify the SELECT statement to project the column(s) used in the
ORDER BY clause, or modify the ORDER BY to omit the offending
columns.
SELECT in Unify DataServer: SQL/A Reference.
Error Messages
–10523
Explanation
****INTERNAL SQL/A SYSTEM ERROR .
This is an internal error and should not occur in the normal execution of
SQL/A.
Correction
–10524
Explanation
If this error occurs, please call Customer Support.
Invalid transaction scan level (level), must be between level1 and
level2.
The transaction scan level level is invalid. Transaction scan levels must
be within the specified range: level1 and level2.
Correction
Check the syntax of the statement; check the list of valid transaction
levels in the documentation.
Additional Help
SET TRANSACTION LEVEL in Unify DataServer: SQL/A Reference
–10525
Invalid transaction update level (level).
Explanation
The transaction scan level level is invalid.
Correction
Check the syntax of the statement; check the list of valid transaction
levels in the documentation.
Additional Help
SET TRANSACTION LEVEL in Unify DataServer: SQL/A Reference
–10528
Explanation
Correction
Additional Help
–10529
Explanation
Correction
Additional Help
Error Messages
Invalid link index name specification.
An invalid link index name has been specified in a DROP LINK
statement.
Check the syntax of the statement. Query the data dictionary to determine
existing link names.
“Using the Data Dictionary” in Unify DataServer: Writing Interactive
SQL/A Queries.
Invalid link index syntax.
The syntax used for the DROP LINK statement is incorrect.
Check the syntax of the statement.
DROP LINK in Unify DataServer: SQL/A Reference.
247
–10530
Explanation
Correction
–10531
Explanation
Correction
Additional Help
–10532
Explanation
syntax error near line line_number.
A syntax error has occurred in a statement on or near line <line number>.
Verify the statement at this line and check the syntax.
Must close the current database.
The current database must be closed to perform the operation specified.
Close the database using the CLOSE DATABASE statement then retry the
operation.
CLOSE DATABASE in Unify DataServer: SQL/A Reference
mrgsrt: no memory.
SQL/A was unable to allocate the amount of memory needed to perform a
sort operation.
Correction
–10533
Explanation
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
Unable to modify user entry for ’user_name’.
SQL/A was unable to modify the user information for the user
user_name. The error message following this one gives the specific error
which has occurred.
Correction
–10534
Explanation
Correction
Additional Help
248
Refer to the description of the specific error which has occurred.
The number of columns being inserted into do not match the number
of projected columns.
In the INSERT command, the number of columns to be inserted into,
does not match the number of columns being projected in the SELECT
(subquery) list.
Check the syntax of the statement.
SELECT and INSERT in Unify DataServer: SQL/A Reference.
Error Messages
–10535
Explanation
Correction
Additional Help
–10536
Explanation
Correction
Number of host vars (actual_number) does not match number of
projected columns (projected_number).
The number of host variables in the INTO clause must match the number
of columns projected by the SELECT statement.
Check the syntax of the statement.
SELECT and INSERT in Unify DataServer: SQL/A Reference.
Column column_number is not a grouping column.
A select expression contains a reference to an invalid column
column_name. If a statement contains a GROUP BY or HAVING clause,
then all references to non-outer-reference columns must be within
aggregate functions or be columns specified in the GROUP BY clause.
Rewrite the query to use a subquery or add the necessary columns to the
GROUP BY clause. Refer to the SQL/A manuals for the proper usage of
the statement.
–10537
Explanation
No memory for file header.
SQL/A was unable to allocate the amount of memory needed to perform
the specified operation.
Correction
–10538
Explanation
Correction
Error Messages
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
Nonexistent column name ’table_name.column_name’.
An error has been detected in the symbol table of the preprocessor. This
is an internal error and should not occur in the normal execution of
SQL/A.
If this error occurs, please call Customer Support.
249
–10539
Explanation
No help is available on this subject.
SQL/A does not have HELP available on the requested topic. Enter HELP
to get a list of all help topics available.
Correction
Additional Help
–10540
Explanation
Check the SQL/A manuals for entries corresponding to the requested
topic.
Unify DataServer: SQL/A Reference
Unable to acquire the desired lock.
The table specified could not be locked with the specified lock type.
An XLOCK cannot be obtained if another transaction holds an SLOCK or
XLOCK on the table or row in the table already. An SLOCK cannot be
obtained if another transaction holds an XLOCK on the table or row in the
table already. Another possibility is that the maximum number of locks
held on the database has been exceeded.
Correction
If locking conflicts are the cause, then retry the operation when all locks
can be obtained.
If no more locks could be obtained on the database, then configure the
database to allow more locks.
Additional Help
–10541
Explanation
Correction
250
Unify DataServer: Configuration Variable and Utility Reference
Internal Error – No node expr for column_number.
An error has been detected in the query block of the statement. This is an
internal error and should not occur in the normal execution of SQL/A.
If this error occurs, please call Customer Support.
Error Messages
–10542
Column ’column_name’ is not an outer reference or grouping
column.
Explanation
A select expression or HAVING clause contains a reference to an invalid
column <column_name>. If a statement contains a GROUP BY or
HAVING clause, then all references to non-outer-reference columns must
be within aggregate functions or be columns specified in the GROUP BY
clause.
Correction
Rewrite the query to use a subquery or add the necessary columns to the
GROUP BY clause.
Additional Help
–10543
Explanation
Correction
–10544
Explanation
Correction
–10545
Explanation
Correction
Additional Help
Error Messages
SELECT in Unify DataServer: SQL/A Reference.
Internal Error – No query blocks.
An error has been detected in the query block of the statement. This is an
internal error and should not occur in the normal execution of SQL/A.
If this error occurs, please call Customer Support.
Nonexistent table name ’table_name’.
An error has been detected in the symbol table of the preprocessor. This
is an internal error and should not occur in the normal execution of
SQL/A.
If this error occurs, please call Customer Support.
oupd: No memory for file buffer.
SQL/A was unable to allocate the amount of memory needed to perform
the specified operation on TEXT or BINARY data.
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation. The utility dbld may also be able to
perform the operation since it operates directly on TEXT and BINARY
data in the database and does not require temporary storage.
Unify DataServer: Configuration Variable and Utility Reference
251
–10546
Explanation
Correction
Additional Help
–10547
Explanation
Correction
–10550
Explanation
Number of columns for parent and child are not the same for
’link_name’.
Link indexes require that the same number of columns be specified for
the parent and the child tables.
Verify the column lists specified for the parent and child tables.
Unify DataServer: SQL/A Reference
No active user transaction.
There is currently no active transaction to base mode information on. If
no error has previously occurred in beginning a new transaction, then this
is an internal error.
If this error occurs, please call Customer Support.
Not enough room in output buffer. Increase SQLPBUFSIZ.
The size of the select list has exceeded the specified output buffer size.
The configuration parameter SQLPBUFSIZ controls the size of the output
buffer.
Correction
Increase the size of the output buffer by modifying SQLPBUFSIZ
appropriately.
Additional Help
Unify DataServer: Configuration Variable and Utility Reference
–10551
Explanation
ofval: No memory.
SQL/A was unable to allocate the amount of memory needed to perform
the specified operation.
Correction
–10554
Explanation
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
Out of memory trying to add a column descriptor.
SQL/A was unable to allocate the amount of memory needed to perform
the specified operation.
Correction
252
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
Error Messages
–10555
Explanation
Correction
–10556
Explanation
Correction
–10557
Explanation
Correction
–10558
Explanation
Correction
–10559
Explanation
Correction
Error Messages
Out of memory, couldn’t declare cursor ’cursor_name’.
The preprocessor was unable to allocate the amount of memory needed to
perform the specified operation.
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting the preprocessor and then retrying the
statement may also correct the situation.
Out of memory, couldn’t declare host variable ’variable_name’.
The preprocessor was unable to allocate the amount of memory needed to
perform the specified operation.
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting the preprocessor and then retrying the
statement may also correct the situation.
Out of memory building projected column descriptors.
The preprocessor was unable to allocate the amount of memory needed to
perform the specified operation.
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting the preprocessor and then retrying the
statement may also correct the situation.
Out of memory building project descriptors.
The preprocessor was unable to allocate the amount of memory needed to
perform the specified operation.
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting the preprocessor and then retrying the
statement may also correct the situation.
Out of memory: skipping to next file.
The preprocessor was unable to allocate the amount of memory needed to
preprocess the source file. It is now trying to continue to the next source
file.
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting the preprocessor and then retrying the
statement may also correct the situation.
253
–10560
Explanation
Correction
Additional Help
Only the view table can be in FROM clause.
The FROM clause contains a view with a GROUP BY or HAVING clause,
or with an aggregate function in its definition. In this case, the only table
allowed in the FROM clause is the view table.
Rewrite the SELECT statement so that only the view table is used in the
FROM clause.
SELECT in Unify DataServer: SQL/A Reference.
–10561
Required privilege for ’table_or_column_name’ does not exist.
Explanation
The privileges required to perform the specified operation on the
specified table or column do not exist for the current schema.
Correction
–10562
Verify the privileges for the current schema. Also, verify the statement to
ensure its correctness. If necessary, the schema must be granted the
required privileges by an authorized user or schema.
Required privilege for ’table_name.column_name’ does not exist.
Explanation
The privileges required to perform the specified operation on the column
table_name.column_name do not exist for the current schema.
Correction
Verify the privileges for the current schema. Also, verify the statement to
ensure its correctness. If necessary, the schema must be granted the
required privileges by an authorized user or schema.
–10563
Explanation
Unable to revoke all privileges.
SQL/A was unable to revoke all of the privileges specified. The error
message following this one gives the specific error which has occurred.
Correction
–10564
Explanation
Refer to the description of the specific error which has occurred.
Unable to revoke permissions from user ’user_name’.
SQL/A was unable to revoke the specified permissions from the user
user_name. The error message following this one gives the specific error
which has occurred.
Correction
254
Refer to the description of the specific error which has occurred.
Error Messages
–10565
Explanation
Unable to revoke access from user ’user_name’.
SQL/A was unable to revoke the specified permissions from the user
user_name. The error message following this one gives the specific error
which has occurred.
Correction
–10567
Explanation
Refer to the description of the specific error which has occurred.
Unable to rollback work.
SQL/A was unable to rollback the current transaction. The error message
following this one gives the specific error which has occurred.
Correction
–10569
Explanation
Refer to the description of the specific error which has occurred.
Invalid RENAME TABLE syntax.
The syntax used for the ALTER TABLE statement is incorrect.
Correction
Check the placement and spelling of statement options.
Additional Help
ALTER TABLE in Unify DataServer: SQL/A Reference.
–10570
Explanation
Error retrieving table information. error_message
SQL/A was unable to retrieve information on a table in the specified
statement. The error error_message gives the specific error that has
occurred.
Correction
–10572
Refer to the description of the specific error which has occurred.
Invalid REVOKE statement syntax.
Explanation
The syntax used for the REVOKE statement is incorrect.
Correction
Check the placement and spelling of statement options.
Additional Help
Error Messages
Unify DataServer: SQL/A Reference
255
–10573
Explanation
Select aborted. All locks could not be acquired.
All rows which were to be selected could not be locked with an SLOCK.
The current transaction level specifies that the select operation is to be
aborted if this situation occurs.
In general, an SLOCK cannot be obtained if either another transaction
holds an XLOCK on the row or table already, or the maximum number of
locks held on the database has been exceeded.
Correction
If locking conflicts are the cause, then retry the operation when all locks
can be obtained.
If no more locks could be obtained on the database, then configure the
database to allow more locks.
Additional Help
–10574
Explanation
Correction
Additional Help
Unify DataServer: Configuration Variable and Utility Reference
An expression cannot be compared with a literal tuple list.
The query involves a comparison between an expression and a literal
tuple list. Such an comparison is not valid.
Change the statement.
“Selecting Rows and Columns” in Unify DataServer: Writing Interactive
SQL/A Queries
–10575
Explanation
Correction
Additional Help
Aggregate function imbalance in the SELECT clause.
The projected expressions in the SELECT list must have the same level
of nesting for aggregate functions.
Change the statement.
“Selecting Rows and Columns” in Unify DataServer: Writing Interactive
SQL/A Queries
–10576
Explanation
Correction
Additional Help
256
Aggregate functions nested too deeply in the SELECT clause.
Aggregate functions are allowed to be at most two levels deep.
Modify the query so that nesting of aggregate functions is at most two
levels deep.
SELECT in Unify DataServer: SQL/A Reference.
Error Messages
–10577
Explanation
Correction
Aggregate functions may not be nested without a GROUP BY clause.
Aggregate functions incorrectly used in the query.
Modify the query so that aggregate functions are only nested using a
GROUP BY clause.
Additional Help
–10578
Explanation
SELECT in Unify DataServer: SQL/A Reference.
Out of memory: program_name.
SQL/A was unable to allocate the amount of memory needed to perform
the specified operation.
Correction
–10579
Explanation
Correction
Additional Help
–10580
Explanation
Correction
Additional Help
–10581
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
Aggregate operators are not allowed in a SET expression.
The right hand side of a SET expression cannot contain aggregate
functions.
Modify the query so that the right hand side of a SET expression does not
contain aggregate functions.
Unify DataServer: SQL/A Reference
Aggregate functions are not allowed in the WHERE clause.
The usage of the WHERE clause is incorrect.
Modify the query so that the WHERE clause does not contain any
aggregate functions.
SELECT in Unify DataServer: SQL/A Reference
Subquery returned more than one row.
Explanation
The query involves an operation which requires only one row. However,
the subquery that is used to obtain the value returns more than one row.
Correction
Modify your query accordingly or change the operator to be one which is
suitable for a multi-row return (i.e. IN rather than ’=’).
Additional Help
Error Messages
SELECT in Unify DataServer: SQL/A Reference
257
–10583
Explanation
dosrch: out of memory.
SQL/A was unable to allocate the amount of memory needed to perform
the specified operation.
Correction
–10584
Explanation
Correction
–10585
Explanation
Correction
Additional Help
–10586
Explanation
Correction
Additional Help
258
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
Double stack overflow.
The space used by constants in the current statement has exceeded the
current limit.
Modify your query or increase the size of the constant pool.
Warning: Buffer size specified is invalid. Minimum required will be
used.
The value specified for the buffer size in the USING BUFFER SIZE
clause of the OPEN statement is less than or equal to zero. The buffer
must be large enough to hold at least two rows. In the preprocessing
stage, only zero or negative values for buffer size give this warning. A
nonzero value may still not be used if the size if not large enough for two
rows.
Modify the USING BUFFER SIZE clause to specify a buffer size that is
nonzero and large enough to hold two rows. To determine row size, use
list backend status command (lbs) in the SQL/A Debugger.
Unify DataServer: SQL/A Reference
Column space overflow. Increase SQLFLDCNT.
The space used by columns in the current statement has exceeded the
current limit.
Modify your query or increase the size of the pool by changing the value
of SQLFLDCNT.
Unify DataServer: Configuration Variable and Utility Reference
Error Messages
–10587
Explanation
Correction
Additional Help
–10588
Explanation
Correction
Additional Help
–10589
Explanation
Correction
Additional Help
–10590
Explanation
Correction
Additional Help
–10591
Explanation
Correction
Additional Help
Error Messages
A HAVING clause cannot contain nested aggregate functions.
The query involves a HAVING clause that has nested aggregate functions.
Nested aggregates are only allowed in select expressions.
Change the statement.
SELECT in Unify DataServer: SQL/A Reference
Invalid command. You do not have insert privileges.
You do not have permission to insert data into the specified table.
Change the permissions on the table.
GRANT statement in Unify DataServer: SQL/A Reference.
Invalid command. You do not have delete privileges.
You do not have permission to delete data from the specified table.
Change the permissions on the table.
GRANT statement in Unify DataServer: SQL/A Reference.
Invalid command. You do not have select privileges.
You do not have permission to select data from the specified table.
Change the permissions on the table.
GRANT statement in Unify DataServer: SQL/A Reference.
Invalid command. You do not have update privileges.
You do not have permission to update data contained in the specified
table.
Change the permissions on the table.
GRANT statement in Unify DataServer: SQL/A Reference.
259
–10592
Explanation
Correction
Additional Help
–10593
Explanation
Correction
Additional Help
–10594
Explanation
Correction
Additional Help
–10595
Explanation
Correction
Additional Help
–10596
Explanation
Correction
Additional Help
260
’file_name’ is an invalid file name.
The file file_name is not a valid file name for the values of an insert.
Check the spelling of the file. Also check that the file has read
permission.
Your UNIX operating system documentation.
The FROM clause is missing or invalid.
The statement does not contain a valid FROM clause.
Check the spelling and placement of keywords and other items.
SELECT in Unify DataServer: SQL/A Reference
Invalid GROUP BY clause.
The GROUP BY clause is incorrectly used.
Check the spelling and placement of keywords and other items.
SELECT in Unify DataServer: SQL/A Reference
Invalid HAVING clause.
The HAVING clause is incorrectly used.
Check the spelling and placement of keywords and other items.
SELECT in Unify DataServer: SQL/A Reference
Invalid SELECT list syntax.
Incorrect SELECT statement used.
Check the spelling and placement of keywords and other items.
SELECT in Unify DataServer: SQL/A Reference
Error Messages
–10597
Explanation
Correction
–10598
Explanation
Integer stack overflow.
The space used by constants in the current statement has exceeded the
current limit.
Modify your query or increase the size of the constant pool.
Invalid table specification in the SELECT clause: table_name.
Specified table is referenced in the query but has not been specified in the
FROM clause of the query.
Correction
Additional Help
–10599
Explanation
Correction
Additional Help
Error Messages
Check the spelling and placement of keywords and other items.
SELECT in Unify DataServer: SQL/A Reference
A literal tuple contains the wrong number of items.
The number of constants in a literal tuple list does not match the number
of value expressions. This error is often caused by an incorrect usage of
the IN keyword.
Check the spelling and placement of keywords and other items.
“Selecting Rows and Columns” in Unify DataServer: Writing Interactive
SQL/A Queries
SELECT in Unify DataServer: SQL/A Reference
261
–10600
Explanation
Correction
–10601
Explanation
dosrch: key value not found.
This is an internal error and should not occur during the normal execution
of SQL/A. If this error is encountered, SQL/A logs the error to the data
base errlog file and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
There is insufficient memory for search arguments.
SQL/A was unable to allocate the amount of memory needed to perform
the specified operation.
Correction
–10602
Explanation
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
tabop: no memory for keybuf.
SQL/A was unable to allocate the amount of memory needed to perform
the specified operation.
Correction
–10603
Explanation
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
There is insufficient memory for this query.
SQL/A was unable to allocate the amount of memory needed to perform
the specified operation.
Correction
–10604
262
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
bldti: nil returned from bfrew.
Explanation
Either user memory is not available or a binary file could not be
rewound. If this error is encountered, SQL/A logs the error to the data
base errlog file and exits.
Correction
Verify that enough user memory is available on the system. If there is,
please call Customer Support.
Error Messages
–10605
Explanation
Correction
–10606
Explanation
Correction
Additional Help
–10607
Explanation
Correction
Additional Help
–10608
Explanation
Correction
–10609
Explanation
Correction
Error Messages
dosrch: no selection criteria for index key.
This is an internal error and should not occur during the normal execution
of SQL/A. If this error is encountered, SQL/A logs the error to the data
base errlog file and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
Nested START statements are not allowed.
The input script has nested START commands. This is not allowed.
Correct your input script.
“Entering SQL/A Statements” in Unify DataServer: Writing Interactive
SQL/A Queries
Value specified for 1 must be a positive non-zero integer value.
You have specified an invalid value for TEXT length.
Make sure the TEXT length is a positive non-zero integer.
Unify DataServer: SQL/A Reference
Standard output is zero.
This is an internal error and should not occur during the normal execution
of SQL/A. If this error is encountered, SQL/A logs the error to the data
base errlog file and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
Output file descriptor is zero.
This is an internal error and should not occur during the normal execution
of SQL/A. If this error is encountered, SQL/A logs the error to the data
base errlog file and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
263
–10610
Explanation
outfunc: out of memory.
SQL/A was unable to allocate the amount of memory needed to perform
the specified operation.
Correction
–10611
Explanation
Correction
–10612
Explanation
Correction
–10613
Explanation
Correction
–10614
Explanation
Correction
264
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
please retain responsible query.
This is an internal error and should not occur during the normal execution
of SQL/A.
If this error occurs, please call Customer Support and report the query
that caused this error.
An internal SQL error has occurred. Please check the error log.
This is an internal error and should not occur during the normal execution
of SQL/A. If this error is encountered, SQL/A logs the error to the
database errlog file and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
Unable to drop current schema.
Current schema could not be dropped. Refer to the following error
message to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
SQL error – see notes
The notes for this message are in the associated error log entry in file.err.
Follow the instructions in the notes.
Error Messages
–10617
Explanation
Correction
–10618
Explanation
String overflow.
The space used by constants in the current statement has exceeded the
current limit.
Modify your query or increase the size of the constant pool.
Temp file write error.
The output of a query could not be written. This is a fatal error, causing
SQL/A to exit after logging the error in the database errlog file.
Correction
–10619
Explanation
A process or system file limit may have been exceeded. There may also
not be enough disk space or inodes in the UNIFYTMP directory. Check the
system console for messages. If it appears to be that SQL/A has tried to
open too many files, try simplifying the offending statement or
reconfigure the system to allow more open files.
No memory for sort structure.
SQL/A was unable to allocate the amount of memory needed to perform
the specified operation.
Correction
–10620
Explanation
Correction
Additional Help
–10621
Explanation
Correction
Error Messages
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
Set functions not allowed.
The definition of this view cannot have a set function because the query
that defined it does not allow it.
Correct the statement.
CREATE VIEW, SELECT in Unify DataServer: SQL/A Reference.
STRING type required.
The query involves a pattern matching operator. The data type of the host
variable representing the pattern must be of type string.
Check the query and correct the declaration of the host variable.
265
–10622
Explanation
Correction
–10623
Explanation
Correction
–10624
Explanation
Correction
–10625
Explanation
Correction
–10626
Explanation
Correction
266
Error starting trx : error_number.
A transaction could not be started by the preprocessor. The above
message is followed by another message describing the specific error that
has occurred.
Refer to the description of the specific error which has occurred.
Unexpected combination in tabop.
This is an internal error and should not occur during the normal execution
of SQL/A. If this error is encountered, SQL/A logs the error to the
database errlog file and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
bldti: unexpected eof.
This is an internal error and should not occur during the normal execution
of SQL/A. If this error is encountered, SQL/A logs the error to the
database errlog file and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
Unexpected op in txtop.
This is an internal error and should not occur during the normal execution
of SQL/A. If this error is encountered, SQL/A logs the error to the
database errlog file and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
Unexpected style in comival style_number.
This is an internal error and should not occur during the normal execution
of SQL/A. If this error is encountered, SQL/A logs the error to the
database errlog file and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
Error Messages
–10627
Explanation
Correction
–10628
Unrecognized style – settyp –
This is an internal error and should not occur during the normal execution
of SQL/A. If this error is encountered, SQL/A logs the error to the
database errlog file and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
Unable to open temporary file ’file_name’.
Explanation
A temporary file used for performing the specified statement could not be
successfully opened or created.
Correction
A process or system file limit may have been exceeded. There may also
not be enough disk space or inodes in the UNIFYTMP directory. Check the
system console for messages. If it appears to be that SQL/A has tried to
open too many files, try simplifying the offending statement or
reconfigure the system to allow more open files.
–10629
Explanation
Correction
–10630
Explanation
Correction
–10631
Unable to switch current schema to ’schema_name’.
Could not change current schema to schema_name. The reason for the
failure follows this text.
Refer to the description of the specific error which has occurred.
Unable to switch to schema ’schema_name’.
Could not switch to the schema schema_name. The reason for the failure
follows this text.
Refer to the description of the specific error which has occurred.
Unexpected end of file from temporary table.
Explanation
In materializing a view, an unexpected end of file (temp file) was
encountered. This is an internal error and should not occur during the
normal execution of SQL/A. If this error is encountered, SQL/A logs the
error to the database errlog file and exits.
Correction
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
Error Messages
267
–10634
Explanation
Correction
Additional Help
–10635
Explanation
Correction
–10637
Explanation
Correction
Additional Help
–10638
Explanation
Correction
Additional Help
–10641
Explanation
Correction
268
Invalid SYNONYM syntax.
Incorrect statement was used for adding synonyms to a table.
Correct the statement..
CREATE SYNONYM statement in Unify DataServer: SQL/A Reference.
Internal System Error, aborting.
This error causes the preprocessor to exit. This is an internal error and
should not occur during the normal execution of SQL/A.
If this error occurs, please call Customer Support.
Invalid table configuration option.
The configuration section for creating/altering a table is invalid.
Correct the statement.
ALTER TABLE and CREATE TABLE statements Unify DataServer:
SQL/A Reference.
Invalid table element option.
The options specified for creating a table is invalid.
Correct the statement.
CREATE TABLE statement Unify DataServer: SQL/A Reference.
cleanup: error closing temporary index index_number.
If the temporary index file cannot be closed, SQL/A reports this error in
the database errlog file and exits.
Refer to the description of the specific error which has occurred.
Error Messages
–10642
Explanation
Correction
Additional Help
Table name ’synonym_name’ is not a synonym for ’table_name’.
When dropping synonyms for a table, verification is made that all the
names being dropped are synonyms of the same table. This error is
returned if synonym_name is not a synonym for the table table_name.
Correct the statement.
DROP SYNONYM statement Unify DataServer: SQL/A Reference.
–10644
Target table ’table_name’ is not same as cursor ’cursor_name’s target
table.
Explanation
The preprocessor verifies that the UPDATE or DELETE WHERE
CURRENT OF has the same target table name as the table name referred
to in the corresponding cursor. This error occurs if these two table names
do not match.
Correction
Additional Help
–10647
Explanation
Correction
Additional Help
–10648
Explanation
Correction
Error Messages
Correct the statements.
“Inserting, Updating, and Deleting Rows” in Unify DataServer: SQL/A
Reference.
Type mismatch between host var variable_name and projected
column column_number.
The preprocessor returns this error for incompatible data types of a host
variable and the projected column being assigned to the host variable.
Correct the data types of the variables.
“Declaring Host Variables” in Unify DataServer: Embedding SQL/A Into
C
Unable to commit work.
The current transaction could not be committed. The error message
following this one gives the specific error which has occurred.
Refer to the description of the specific error which has occurred.
269
–10649
Explanation
The preprocessor output file could not be successfully opened or created.
Correction
A process or system file limit may have been exceeded. There may also
not be enough disk space or inodes in the UNIFYTMP directory. Check the
system console for messages. If it appears to be that SQL/A has tried to
open too many files, try simplifying the offending statement or
reconfigure the system to allow more open files.
–10650
Explanation
Correction
–10651
Explanation
Correction
–10652
270
Unable to open object file ’file_name’.
Unable to open source file ’file_name’.
The input source file file_name could not be successfully opened or
created.
A process or system file limit may have been exceeded. There may also
not be enough disk space or inodes in the UNIFYTMP directory. Check the
system console for messages. If it appears to be that SQL/A has tried to
open too many files, try simplifying the offending statement or
reconfigure the system to allow more open files.
Unable to open symbol file ’file_name’.
The symbol file file_name could not be successfully opened or created.
A process or system file limit may have been exceeded. There may also
not be enough disk space or inodes in the UNIFYTMP directory. Check the
system console for messages. If it appears to be that SQL/A has tried to
open too many files, try simplifying the offending statement or
reconfigure the system to allow more open files.
Unable to open temporary file;
Explanation
A temporary file used by SQL/A could not be successfully opened or
created. Refer to the accompanying error message for more information.
Correction
A process or system file limit may have been exceeded. There may also
not be enough disk space or inodes in the UNIFYTMP directory. Check the
system console for messages. If it appears to be that SQL/A has tried to
open too many files, try simplifying the offending statement or
reconfigure the system to allow more open files.
Error Messages
–10653
Explanation
Correction
–10654
Explanation
Correction
–10655
Explanation
Unable to read configuration file.
This error is reported if the configuration environment could not be
initialized.
Check to make sure UNIFY is set correctly and unify.cf file exists under
the directory pointed to by UNIFY. Also verify that the file has read
permission. If all these check out, then verify that enough user memory is
available.
Unable to create/read temporary file.
A temporary file used by SQL/A could not be successfully opened or
created.
A process or system file limit may have been exceeded. There may also
not be enough disk space or inodes in the UNIFYTMP directory. Check the
system console for messages. If it appears to be that SQL/A has tried to
open too many files, try simplifying the offending statement or
reconfigure the system to allow more open files.
Unable to rewind temporary file;
SQL/A may use a temporary file for delete, update and insert commands.
This error is reported when the temporary file cannot be rewound. The
error is logged in the database errlog file and SQL/A exits. Refer also to
the accompanying error message for more information.
Correction
–10656
Explanation
Please call Customer Support and give them the information in the errlog
file.
Unable to write to temporary file;
SQL/A uses a temporary file for execution. If it is unable to write to the
temporary file, SQL/A logs this error in the database errlog file and exits.
Also refer to the accompanying error message for more information.
Correction
Error Messages
A process or system file limit may have been exceeded. There may also
not be enough disk space or inodes in the UNIFYTMP directory. Check the
system console for messages. If it appears to be that SQL/A has tried to
open too many files, try simplifying the offending statement or
reconfigure the system to allow more open files.
271
–10657
Explanation
Update aborted. All locks could not be acquired.
All rows which were to be updated could not be locked with an XLOCK.
The current transaction level specifies that the update operation is to be
aborted if this situation occurs.
In general, an XLOCK cannot be obtained if either another transaction
holds an SLOCK or XLOCK on the row or table already, or the maximum
number of locks held on the database has been exceeded.
Correction
If locking conflicts are the cause, then retry the operation when all locks
can be obtained.
If no more locks could be obtained on the database, then configure the
database to allow more locks.
–10658
Explanation
Correction
–10659
Explanation
Correction
–10660
Explanation
Correction
–10661
Explanation
Correction
272
Unable to add view ’view_name’.
The view view_name could not be created. The reason for the failure
follows this text.
Refer to the description of the specific error which has occurred.
Unable to grant all privileges.
All privileges could not be granted. Refer to the following error message
to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to add schema ’schema_name’.
The schema schema_name could not be created. The reason for the
failure follows this text.
Refer to the description of the specific error which has occurred.
Unable to add volume ’volume_name’.
The volume volume_name could not be added. Refer to the following
error message to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Error Messages
–10662
Explanation
Correction
–10663
Explanation
Correction
–10664
Explanation
Correction
–10665
Explanation
Correction
–10666
Explanation
Correction
–10667
Explanation
Correction
Error Messages
Unable to create btree ’B-tree_name’.
The B-tree index B-tree_name could not be added. Refer to the following
error message to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to create table ’table_name’.
The table table_name could not be added. Refer to the following error
message to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to drop b-tree index ’B-tree_index_name’.
The B-tree index B-tree_index_name could not be dropped. Refer to the
following error message to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to drop old column names. error_message
Old column names could not be dropped. Refer to the error_message to
determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to drop constraint. error_message
Specified constraint could not be dropped. Refer to the error_message to
determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to drop hash index ’hash_name’. error_message
The hash index hash_name could not be dropped. Refer to the
error_message to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
273
–10668
Explanation
Correction
–10669
Explanation
Correction
–10670
Explanation
Correction
–10671
Explanation
Correction
–10672
Explanation
Correction
Additional Help
–10673
Explanation
Correction
274
Unable to drop link index ’link_name’. error_message
The link link_name could not be dropped. Refer to the error_message to
determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to drop schema ’schema_name’. error_message
The schema schema_name could not be dropped. Refer to the
error_message to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to drop table ’table_name’. error_message
The table table_name could not be dropped. Refer to the error_message
to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to drop volume ’volume_name’. error_message
The volume volume_name could not be dropped. Refer to the
error_message to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to drop view. error_message
A view could not be dropped. Refer to the error_message to determine
the cause of the failure.
Refer to the description of the specific error which has occurred.
DROP VIEW in Unify DataServer: SQL/A Reference.
Unable to end system transaction.
A system transaction could not be committed. Refer to the following
error message to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Error Messages
–10674
Explanation
Correction
–10675
Explanation
Correction
–10676
Explanation
Correction
–10677
Explanation
Correction
–10678
Explanation
Correction
–10679
Explanation
Correction
Error Messages
Unable to end user transaction.
A user transaction could not be committed. Refer to the following error
message to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to find btree ’B-tree_index_name’. error_message
Could not bind to the B-tree index, B-tree_index_name. Refer to the
error_message to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to find column column_name. error_message
Could not bind to the column, column_name. Refer to the error_message
to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to find hash ’hash_name’. error_message
Could not bind to the hash index, hash_index. Refer to the error_message
to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to find link ’link_name’. error_message
Could not bind to the link, link_name. Refer to the error_message to
determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to find schema ’schema_name’. error_message
Could not bind to the schema, schema_name. Refer to the error_message
to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
275
–10680
Explanation
Correction
–10681
Could not bind to the table, table_name. Refer to the error_message to
determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to find user ’user_name’. error_message
Explanation
Error occurred in binding the user name, user_name. The user is
probably not registered to access the database. Refer to the
error_message to determine the cause of the failure.
Correction
Refer to the description of the specific error which has occurred.
–10682
Explanation
Correction
–10683
Explanation
Correction
–10684
Explanation
Correction
–10685
Explanation
Correction
276
Unable to find table ’table_name’. error_message
Unable to find volume ’volume_name’. error_message
Could not bind to the volume, volume_name. Refer to the error_message
to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to get Schema ID. error_message
Could not obtain the current schema ID. Refer to the error_message to
determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to get schema information.
Could not get information on the current schema. This message is
followed by the error message indicating the cause of the problem.
Refer to the description of the specific error which has occurred.
Unable to get valid schemas.
Could not get information about the schemas that you are allowed to
access.
If this error occurs, please call Customer Support.
Error Messages
–10686
Explanation
Correction
Additional Help
–10687
Explanation
Correction
–10689
Explanation
Correction
Additional Help
–10691
Unable to create hash ’hash_name’. error_message
Could not create the hash index, hash_name. Refer to the error_message
to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unify DataServer: SQL/A Reference
Error getting user info error number. error_message
Information about the user could not be obtained. Refer to the
error_message to determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unable to create link ’link_name’. error_message
Could not create the link, link_name. Refer to the error_message to
determine the cause of the failure.
Refer to the description of the specific error which has occurred.
Unify DataServer: SQL/A Reference
Unrecognized SQL command.
Explanation
An invalid SQL/A command has been entered.
Correction
Check the spelling and placement of keywords.
Additional Help
–10694
Explanation
Correction
Error Messages
Unify DataServer: SQL/A Reference
Unable to verify column synonyms.
An error occurred in verifying the currently defined synonyms for
specified column.
Refer to the description of the specific error which has occurred.
277
–10695
Explanation
Correction
–10697
Explanation
Correction
–10698
Explanation
Correction
Additional Help
–10699
Explanation
Correction
–10700
278
Unable to verify table synonyms.
The existence of table synonyms could not be verified.
Refer to the description of the specific error which has occurred.
The view table, ’view_name’, is not updateable.
Update was tried on a table that is a non-updatable view.
You cannot update this view. Refer to the section on views in the
Interactive SQL/A manual for more information.
Invalid volume option.
The volume option used is incorrect.
Check the spelling and placement of keywords.
CREATE VOLUME statement in Unify DataServer: SQL/A Reference.
Error expanding view: error_number.
There was an error encountered in expanding a view involved in the
query. The error status error_number should be referred to for more
corrective action.
Take corrective action for the error status.
Unable to initialize the view manager.
Explanation
The view manager could not be initialized. This is an internal error and
should not occur during the normal execution of SQL/A. If encountered,
SQL/A logs the error to the database errlog file and exits.
Correction
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
Error Messages
–10701
Explanation
Correction
Additional Help
–10702
Explanation
Correction
Additional Help
–10703
Explanation
Correction
–10704
Explanation
Correction
–10705
Explanation
Correction
Error Messages
Number of view columns is number, number in SELECT expr is
SELECT_number.
The number of columns defined for the view does not match the number
of expressions projected in the SELECT expression.
Correct the view definition.
Unify DataServer: SQL/A Reference
WHERE clause not allowed.
The definition of the view involved in the query is such that the WHERE
clause is not valid.
Correct the view definition.
Unify DataServer: SQL/A Reference
Can’t create (or open) file: file_name.
If trying to edit the query file, the file could either be not opened or
created. If output was being redirected, the output file could not be
opened. This can happen if too many files are open or disk space is full.
Check for the above conditions and take corrective action.
The file ’file_name’ already exists.
The redirection of the output of the SQL/A query is to a file that already
exists.
Give a different file name or remove the existing file.
Invalid date.
The constant specified for a column of type DATE or HUGE DATE is
invalid.
Use a compatible constant for DATE and/or HUGE DATE columns.
279
–10706
Explanation
Correction
–10707
Explanation
Invalid column type for sorting.
This is an internal error and should not occur during the normal execution
of SQL/A. If encountered, SQL/A logs the error to the database errlog file
and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
There is insufficient memory.
SQL/A was unable to allocate the amount of memory needed to perform
the specified operation.
Correction
–10708
Explanation
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
Insufficient memory available.
SQL/A was unable to allocate the amount of memory needed to perform
the specified operation.
Correction
–10709
Explanation
Correction
Additional Help
280
A process size or system limit may have been exceeded. Check the
console for system errors. Exiting SQL/A and then retrying the statement
may also correct the situation.
The internal_table_name table has overflowed.
The query has exceeded the maximum allowed number of structures in
the internal_table_name table.
Most of the maximum values are controlled by configuration variables. If
internal_table_name is Field, then you need to increase the value of the
SQLFLDCNT configuration parameter. Check the values of related
configuration variables values. Also, in some cases, you may be able to
rewrite the query so as not to use that many structures.
Configuration variables beginning with SQL in Unify DataServer:
Configuration Variable and Utility Reference.
Error Messages
–10710
Explanation
Correction
–10711
Explanation
Correction
–10712
Explanation
Correction
Additional Help
–10713
Explanation
Correction
Additional Help
–10714
Explanation
Correction
Error Messages
Invalid time.
The constant value specified for the column of type TIME is invalid.
Correct the value.
Operator not found.
This is an internal error and should not occur during the normal execution
of SQL/A. If encountered, SQL/A logs the error to the database errlog file
and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
SQL: There is insufficient memory for structure_name.
Memory required for initialization of SQL/A structures is not available.
Check the value of the configuration variables. Check related
configuration variables. If appropriate correct the values to be reasonable.
Also check available user memory on your system.
Unify DataServer: Configuration Variable and Utility Reference
Type conversion error.
The SQL/A query involves incompatible data conversion for specified
operation.
Choose a compatible data type.
“Appendix B: Compatible Data Types” in Unify DataServer: Writing
Interactive SQL/A Queries.
Unrecognized character: ’0octal_value’.
The input had some unprintable characters.
Check your input and remove any invalid characters.
281
–10715
Explanation
Correction
–10716
Explanation
Correction
–10717
The input script file name file_name could not be opened with read
permission. Check the name of the input file, and the file system
permissions for the file. Also check the number of files that may have
been opened for the process.
Get appropriate permission on the file and make sure that all unnecessary
files are closed.
Unknown string expression type.
This is an internal error and should not occur during the normal execution
of SQL/A. If encountered, SQL/A logs the error to the database errlog file
and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
Database ’database_name’ is not available.
Explanation
The specified database could not be opened. Possibly the path name is
incorrect or the database file was removed. The error message following
this one gives the specific error which has occurred.
Correction
Refer to the description of the specific error which has occurred. Check
for existence of appropriate files. You may also not be registered user of
the database. If you are not, talk to the creator or database administrator
about giving you access to the database.
–10720
Explanation
Correction
–10721
Explanation
Correction
282
Unable to open file: file_name.
Data value not specified for column ’column_name’, row row_number.
The input ASCII data file is missing column value for column
column_name for specified row.
Check your input data file.
Could not fork new process.
A new process could not be forked.
If the current system load is high, try to run the application again later. If
not, please call Customer Support.
Error Messages
–10723
Explanation
Correction
–10725
Explanation
Correction
Additional Help
–10726
Explanation
Correction
–10727
Unable to start a new transaction.
A new transaction could not be started.
Maybe too many transactions are active for the process or SQL/A has run
out of shared memory. Check the number of transactions that are active
and then call Customer Support if more information is required to correct
the problem.
ORDER BY clause is not allowed in a view definition.
A view cannot be defined with an ORDER BY clause.
Check your definition of the view.
CREATE VIEW in Unify DataServer: SQL/A Reference.
INTERNAL: trying to allocate zero length buffer.
This is an internal error and should not occur during the normal execution
of SQL/A. If encountered, SQL/A logs the error to the database errlog file
and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
Cannot project TEXT or BINARY columns in a unique view.
Explanation
You have tried to define a unique view containing base columns that are
either TEXT or BINARY. This is not allowed.
Correction
Either do not make the view unique, or remove the offending columns.
Additional Help
–10728
Explanation
Correction
Error Messages
CREATE VIEW in Unify DataServer: SQL/A Reference.
Cannot retrieve sql table information.
This is an internal error and should not occur during the normal execution
of SQL/A. If encountered, SQL/A logs the error to the database errlog file
and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
283
–10729
Explanation
Correction
–10730
Explanation
Cannot find column in the table list.
This is an internal error and should not occur during the normal execution
of SQL/A. If encountered, SQL/A logs the error to the database errlog file
and exits.
Check the errlog file for an entry describing the cause of the error. Call
Customer Support.
CREATE DATABASE is not allowed in a runtime version.
This version of the runtime environment software does not allow the
CREATE DATABASE command.
Correction
–10731
Explanation
Correction
–10732
Explanation
Do not use the CREATE DATABASE command in your application.
CREATE TABLE is not allowed in a runtime version.
This version of the runtime environment software does not allow any
DDL operations that create or drop a table.
You cannot include a DDL operation that creates or drops a table.
DROP TABLE is not allowed in a runtime version.
This version of the runtime environment software does not allow any
DDL operations that create/drop a table.
Correction
–10733
Number of items on right hand side does not match number on left.
Explanation
The number of columns (value expressions) projected in the subquery
does not equal the number on the left hand side of the restriction clause.
Correction
284
You cannot include a DDL operation that creates or drops a table.
Check your SQL/A query. Refer to the SQL/A manuals for proper usage of
the statement.
Error Messages
–10734
Explanation
Correction
Incompatible data types on the left and right hand side.
The data type of the left-hand side elements and those of the right-hand
side elements are not compatible.
Check the data types of the columns (value expressions) involved in the
SQL/A query.
–10735
Explanation
Correction
–10738
Explanation
Correction
–10740
Explanation
Correction
–10741
Explanation
Correction
Error Messages
Arithmetic overflow/underflow occurred.
An arithmetic overflow/underflow occurred in trying to convert data for
the target. Check the data types of the value expressions. Maybe the
value of computing some data results in such a case.
If this error occurs, please call Customer Support.
column_name is an ambiguous column name.
The specified column has not been qualified and belongs to more than
one table in the FROM clause.
Qualify the column with the table to which it belongs.
Interactive SQL/A commands cannot be used during Embedded
SQL/A sessions.
An Interactive SQL/A command was included in an Embedded SQL/A
statement.
See the accompanying message(s) to determine the offending statement.
Embedded SQL commands cannot be used during Interactive SQL
sessions.
An Embedded SQL/A command was included in an Interactive SQL/A
statement.
See the accompanying message(s) to determine the offending statement.
285
–10745
WITH CHECK option not allowed for non–updatable views.
Explanation
The WITH CHECK OPTION clause is not allowed in this view
definition.
Correction
–10746
Explanation
Correction
–10747
Explanation
Correction
–10748
Explanation
Correction
–10749
The view must be updatable to specify WITH CHECK.
procwck: unexpected node style.
An internal error has occurred. Please retain the responsible query and
data base.
Try writing the query in a different manner which achieves the same
result.
Unable to create view dependencies.
An internal error has occurred. Please retain the responsible query and
data base.
Try writing the query in a different manner which achieves the same
result.
UNIONed SELECTs must have the same number of projected items.
The number expressions in each select list of the UNIONed SELECTs
must be the same.
Either remove the extra columns from the SELECT which has too many
columns, or add constant values to the SELECT which has too few
columns.
UNIONed SELECTs must have identical data types and lengths
projected.
Explanation
Correction
286
The data types of each corresponding select expression of the UNIONed
SELECTs must be compatible.
Change one of the SELECT statements so that each corresponding
expression has the same data type as the others.
Error Messages
–10763
There are no options on that menu.
Explanation
The menu selected does not have any options registered on it, or the user
does not have privileges to execute any of the options.
Correction
Remove the empty menu from the menu handler, or register options on it.
–10767
Explanation
Correction
Unable to find help documentation for this selection.
A menu handler help file was not found.
Refer to the Menu Handler manual for information on locating and
creating help documentation.
–10788
Unable to find default schema, ’syncauth’ may need to be run.
Explanation
The menu handler was unable to find the schema specified on the
command line or the user’s default schema.
Correction
Additional Help
–10812
Explanation
Correction
Error Messages
If the schema is specified on the command line, check for misspellings.
Otherwise run the syncauth utility and try again.
Unify DataServer: Configuration Variable and Utility Reference
Unable to find menu/program by that name.
The specified executable name was not found.
Check for misspelling. Try fully qualifying the name as
“schema_name.!executable_name”.
287
–11761
Explanation
Correction
–11762
Explanation
–11763
Explanation
–11764
Explanation
–11765
Explanation
–11766
Explanation
Correction
–11767
redb: Error accessing a transaction log file.
An error occurred while renaming, opening, reading or writing either
file.lg, file.rlg, or file.rc.
Check the existence of the files and permissions.
budb: Invoking user backup utility <cmdline>
Information only. Shows the complete command line passed to the native
system() function.
budb: User backup utility returned N (error | no error)
Information only. Displays the return value of the native system()
function after invoking the user backup utility.
redb: Invoking user restore utility <cmdline> ()
Information only. Shows the complete command line passed to the native
system() function.
redb: User restore utility returned N (error | no error) ()
Information
only. Displays the return value of the native system()
function after invoking the user restore utility.
redb: The .bul file cannot be accessed or is corrupt. ()
An error occurred while accessing file.bul. Check the permissions and
existence of the file.
Examine the contents of file.bul to try and locate the problem.
The restored file ”%s” is not the expected size (%s).
Explanation
Correction
288
The user backup utility returned non–zero, indicating an error.
Check your user–defined utility for problems.
Error Messages
–11768
The restored file ”%s” is not the expected size (%s).
Explanation
Correction
– 12200
Explanation
Correction
–12201
Explanation
Check your user–defined utility for problems.
stcldsc: unexpected style of SELECT expression.
An internal error has occurred. Please retain the responsible query and
data base.
Try writing the query in a different manner which achieves the same
result.
Outer reference not allowed for column: column_name.
A column name has been specified which is an outer reference. Outer
references may not be used in the GROUP BY clause or in a SELECT list
expression. Also, if the outer reference is contained in a subquery of a
HAVING clause, then the column referenced must be a GROUP BY
column in the SELECT which is referenced.
Correction
Refer to Unify DataServer: SQL/A Reference for more information.
–12202
Schema schema_name must match target schema schema_name.
Explanation
Correction
–12203
Explanation
Correction
Error Messages
The user restore utility returned non–zero, indicating an error.
A table name was qualified with a schema name. The schema name does
not match the name of the schema being altered or created.
The schema name specified must match the name of the schema being
created or altered.
Aggregate func in WHERE clause requires outer reference.
An aggregate function was specified in a WHERE clause, and the column
specified was not an outer reference.
Aggregate functions is WHERE clauses must have operand which are
outer reference column names.
289
–12204
Explanation
Correction
–12205
Explanation
Correction
–12206
Explanation
Correction
–12208
Explanation
Correction
–12209
Explanation
Correction
290
WHERE clause must be within HAVING clause to use aggregate func.
An aggregate function is allowed in a WHERE clause only if the WHERE
clause is part of a SELECT, which contains a HAVING clause. In this
case, the operand of the aggregate function must be a column name
which is an outer reference to the SELECT that contains the HAVING
clause.
Correct the syntax accordingly.
Setting for SQLATOMICDML is incompatible. Logging must be
enabled. Defaulting to FALSE.
Atomic DML (SQLATOMICDML=TRUE) can only be enabled when
transaction logging is enabled (LOGTX=TRUE).
None. This is a warning only.
Setting for SQLATOMICDML is incompatible. Not allowed for
BATCH transactions. Defaulting to FALSE.
Atomic DML (SQLATOMICDML=TRUE) cannot be enabled when batch
mode (–m) has been specified.
None. This is a warning only.
Unable to recover from atomic SQL–DML errors.
An internal error has occurred trying to recover from a DML error.
See the accompanying message for more details.
Unable to undo modifications.
An internal error has occurred in trying to undo the current DML
operation.
See the accompanying message for more details.
Error Messages
–12210
Explanation
Correction
–12211
Explanation
Correction
–12212
Explanation
Correction
–12213
Explanation
Correction
–12214
Explanation
Correction
Error Messages
Aggregate expression must contain outer reference only.
The operand of the aggregate function must be a column name in this
case.When the operand of an aggregate function contains a column
reference which is an outer reference, then the operand must not be an
expression. It may only be a column name.
Correct the syntax accordingly.
One of the tables for link_index_name must be in the current schema.
When adding a LINK index, at least one of the tables in the index must
be present in the current schema.
Change current schema to one that contains one of the tables in the LINK
index, before adding the index.
Invalid type for indicator variable variable_name.
Indicator variables must be type SHORT, INT, or LONG.
Change the declaration of the indicator variable, or use a different host
variable of the correct type.
Attempt to divide by zero.
An expression in an SQL statement resulted in an attempt to divide by
zero.
Rewrite the expression to eliminate the cause.
so that the error does not occur.
Or limit the selected data
Descriptor area name cannot be an identifier.
EPP detected use of an identifier as the name of a descriptor area.
Check Unify DataServer: Embedding SQL/A Into C for correct naming
conventions of descriptor areas.
291
–12215
Explanation
Correction
–12216
Explanation
Correction
–12217
Explanation
Correction
–12219
Explanation
Correction
–12220
Explanation
Correction
–12221
Explanation
Correction
292
Statement statement was never prepared.
The statement name specified is not a prepared statement.
Check the statement name and be sure it is prepared before it is
referenced in this statement.
Warning: Statement statement was prepared but never executed.
A statement was prepared but never executed.
Check for misspellings of the prepared statement name.
Warning: Cursor cursor_name declared but never opened.
A cursor was declared but never opened.
Check for misspellings of the cursor name in your application.
Column names must be unique.
A VIEW definition includes duplicate column names.
Rename one of the columns.
Column name column_name is duplicated.
The column name mentioned has been used for more than one column in
the view definition.
Rename one of the duplicated column names.
Error deallocating dynamic statement ’statement’.
This is an internal error and should not occur in normal operation.
If this error occurs, please call Unify Customer Support.
Error Messages
–12223
Explanation
Correction
–12224
Explanation
Correction
–12225
Explanation
Correction
–12226
Too many embedded SQL DML statements.
The current Embedded SQL/A source file contains too many host variable
declarations.
Divide the Embedded SQL/A source into multiple source files.
Too many host variables generated.
The current Embedded SQL/A source file contains too many host variable
declarations.
Remove some of the host variables or divide the Embedded SQL/A
source into multiple source files.
Invalid target variable, expected ”INTO host variable list” or ”INTO
sql descriptor”.
A syntax error occurred in the INTO clause of a FETCH statement.
Check the syntax of the INTO clause.
ROWID may not be used for multi-table SELECT or non-updateable
view.
Explanation
Correction
–12227
Explanation
Correction
–12228
Explanation
Correction
Error Messages
The ROWID pseudocolumn is not defined for JOINs or non-updatable
views.
Remove the ROWID reference from the statement.
Invalid usage of the ROWID function.
ROWID may not be used in a HAVING clause, nor as the target of an
aggregate function.
Do not use ROWID.
Host variable type must be char array.
In a context where a host variable can be used to provide a name or other
string, the type of the host variable must be character array.
Check the spelling and declaration of the host variable.
293
–12229
Explanation
Correction
–12230
Explanation
Correction
–12231
Explanation
Correction
The COUNT field is being set or retrieved following a VALUE clause in a
SET SQL DESCRIPTOR or GET SQL DESCRIPTOR statement.
Do not use the VALUE clause when setting or retrieving the COUNT
field. Do not set or retrieve the COUNT field when setting or retrieving
fields from a descriptor area item.
SQL descriptor area item must be identified.
Only the COUNT field is set or retrieved from a descriptor area. Other
fields must use the VALUE clause to identify which descriptor area item
to set or retrieve the field from.
Specify the VALUE clause or change the field to COUNT.
Allocated cursor cannot have a local name.
An attempt has been made to name an allocated cursor with an identifier.
Allocated cursors must have dynamic names.
Give the allocated cursor a dynamic name, or use a dynamic declared
cursor if a local name is required.
–12232
Allocated cursor cannot be associated with a local statement name.
Explanation
An attempt has been made to associate an allocated cursor with a local
statement name. Allocated cursors must be associated with dynamic
statement names.
Correction
Associate the allocated cursor with a dynamic statement name, or use a
dynamic declared cursor if a local statement name is required.
–12233
294
COUNT is not a field of an SQL descriptor area item.
Declared cursors can only have local names.
Explanation
An attempt has been made to name a declared cursor with a dynamic
name. Declared cursors must have local names.
Correction
Give the declared cursor a local name, or use an allocated cursor if a
dynamic name is required.
Error Messages
–12234
Declared cursors can only be associated with local statement names.
Explanation
An attempt has been made to associate a declared cursor with a dynamic
name. Declared cursors must be associated with local statement names.
Correction
Associate the declared cursor with a local statement name, or use an
allocated cursor if a dynamic statement name is required.
–12235
Only dynamic cursors can be opened with dynamic parameter values
specified.
Explanation
A static declared cursor is being opened with a USING host_variable_list
or USING SQL_descriptor clause. Static declared cursors identify
parameters by using host variable references directly in the cursor
definition.
Correction
Check your cursor name. Remove the offending USING clause, or open a
dynamic declared cursor.
–12236
Explanation
Correction
–12237
Explanation
Correction
–12238
Explanation
Correction
Error Messages
Only dynamic cursors can fetch into an SQL descriptor area.
Static declared cursors must fetch into a host variable list.
Check the cursor name. Either fetch into a host variable list or fetch from
a dynamic declared cursor.
Unable to fetch name for column column_number;
number of columns is number
operation error is ’error_text’
This is an internal error and should not occur in normal operation.
If this error occurs, please call Unify Customer Support.
Buffer size must be an integer.
An open cursor statement with a ”BUFFER SIZE” clause specified a
non–integer value for the buffer size.
See the accompanying message(s) to determine the offending statement.
295
–12239
Table table_name multiply specified in FROM clause.
Explanation
The same table name has been used more than once in the FROM clause
of a SELECT statement.
Correction
If you are performing a self-join of a table, use a correlation variable for
one of the table references. Otherwise, check the spelling of the table
references and any schema references.
–12243
Error in preparing statement in BackEnd.
Explanation
Need explanation
Correction
Need correction
–12244
DATAPTR value expression must be a string constant.
Explanation
DATAPTR fields can only be initialized to a string constant containing a
C expression returning an appropriate type pointer.
Correction
Use a string constant containing a C expression returning the appropriate
type pointer.
–12245
Host variable to hold SQL descriptor handle is not UDAHNDL type.
Explanation
Correction
–12246
Descriptor area handle can only be assigned to UDAHNDL type host
variables.
Declare a host variable of type UDAHNDL and use it to hold the
descriptor area handle.
Cannot specify SQL descriptor area handle.
Explanation
Correction
296
The host variable of type UDAHNDL is not allowed here.
You are using UDAHNDL type host variable when a host variable of
different type is expected. For example, you may really have to use a
descriptor area name, a statement name, cursor name or a data value
instead of descriptor area handle. Use an embedded host variable
appropriate to the context.
Error Messages
–12247
Host variable type must be char array or UDAHNDL.
Explanation
Only char array holding a descriptor name or descriptor area handle is
allowed.
Correction
Check the host variable type and make sure that it is either a char array
holding a descriptor area name or descriptor area handle associated with
a descriptor area.
–12248
Invalid USING clause in ALLOCATE [SQL] DESCRIPTOR statement.
Explanation
Correction
–12249
Explanation
Correction
–12250
Explanation
Correction
Error Messages
Missing or misspelled keywords in USING clause.
Check the syntax of the ALLOCATE [SQL] DESCRIPTOR with USING
clause.
Warning: 64bit long data type not supported, changing to int.
Your hardware supports 64-bit longs, but Unify DataServer does not.
This is merely to let you know that each long will be converted to an int.
No correction is needed. To avoid this message in the future, change all
instances of long to int.
Host variable type may not be char *. Use char array.
char * types are not supported.
Use an array instead.
297
–14001
Explanation
Correction
–14002
Illegal command action attribute value. Expected ’ENABLED’ or
’DISABLED’.
The compiler found an invalid action specifier (enable_string) value
while parsing the COMMAND section. The valid action specifier values
are the ENABLED or DISABLED strings.
Find the COMMAND section that has the invalid action specifier and
rewrite the specifier.
Ambiguous USING clause.
This could be either USING ’format_expression’
for the DISPLAY statement or USING ’connection’
for the next statement. Will compile as USING ’format_expression’.
To avoid this ambiguity:
Supply ; (semicolon) after USING ’format_expression’, or
Rewrite USING ’connection’ as USING CONNECTION ’connection
Explanation
The compiler cannot distinguish between the following two script
fragments:
DISPLAY expression USING ’format_expression’
statement
DISPLAY expression USING ’connection’
statement
Correction
–14003
Explanation
Correction
298
Make sure that if the USING clause is being used to specify a connection
that the DISPLAY keyword is followed by the CONNECTION keyword.
Unexpected syntax in APPLICATION clause.
Unable to diagnose exact syntax error; APPLICATION header is
obsolete, recommended action is to replace it with FORM CLASS
syntax.
An ACCELL/SQL APPLICATION declaration appears to contain a syntax
error.
Correct the error or convert the declaration to a FORM CLASS
declaration.
Error Messages
–14004
An array attribute was not expected.
Explanation
An attempt was made to use an array attribute with an identifier that has
been used as a non-array object.
Correction
If it is an array that is being referenced, make sure that it has been
defined correctly and that it has not been incorrectly reference earlier in
the script.
–14005
Explanation
Invalid LIST attribute usage. Not applicable to a MATRIX.
An attempt was made to reference a MATRIX attribute with a LIST array
variable.
Correction
Change either the attribute or the variable so that they match.
–14006
Invalid MATRIX attribute usage. Not applicable to a LIST.
Explanation
Correction
–14007
Explanation
Correction
–14009
An attempt was made to reference a LIST attribute with a MATRIX array
variable.
Change either the attribute or the variable so that they match.
Invalid LIST or MATRIX attribute usage. Not applicable to a scalar.
An attempt was made to reference an array attribute with a scalar
variable.
Change either the attribute or the variable so that they match.
Array subscript out of bounds.
Explanation
One of the subscripts of an array reference was out of bounds. The
compiler can check for out-of-bound references only for local arrays that
are defined in one of the script’s LOCAL statements. Also, when using
unbounded arrays, only the first dimension is unbounded. Thus, the
compiler checks for out-of-bound references on the second dimension of
bound as well as unbounded matrix arrays.
Correction
The first dimension of arrays can be referenced beyond the upper bounds
if the array is explicitly defined as an unbounded array by using the
UNKNOWN keyword when defining the upper bound of the array’s first
dimension. If the reference is correct, then expand the array dimensions
in the array definition in the LOCAL statement.
Error Messages
299
–14010
Explanation
Correction
–14011
Explanation
Cannot refer to OBJECT_ID attribute of an array.
You referred to variable:OBJECT_ID where variable is defined to be a
LIST or a MATRIX. Such arrays do not have a 4GL-accessible
OBJECT_ID attribute.
Refer to the array by name instead of by OBJECT_ID.
Array self-reference in wrong context. Must be in a field-level event
section belonging to a FIELD LIST or FIELD MATRIX.
A array self reference (array_name[ ]) was made outside that array’s
FIELD event section. A self reference references the current screen
array’s cell.
Correction
–14012
Explanation
Correction
300
For screen array references that are not used in that array’s FIELD event
section, use explicit array subscripts. The subscripts for the current screen
array cell can also be referenced by using the COLUMN_INDEX,
ROW_INDEX, and LIST_INDEX array attributes. The following two
array references reference the same array cell:
Inappropriate number of array subscripts, doesn’t match this
variable’s declaration.
A list array was referenced with two subscripts, or a matrix array was
referenced with one subscript.
Make sure that the array reference uses the correct number of subscripts.
–14013
Left bracket unexpected. Is this an array declaration with the LIST
or MATRIX keyword omitted?
Explanation
A LOCAL clause includes a variable name followed by what appears to
be a declaration of its subscript range(s), but the variable name was not
identified as a LIST or MATRIX.
Correction
Find the LOCAL clause that has the unidentified subscript and add the
LIST or MATRIX keyword.
Error Messages
–14014
Explanation
Correction
–14015
Explanation
Did not expect array subscripts.
An array subscript was used in an array reference where it is not needed
or valid. The array subscript is not valid when referencing the
DIMENSION array attribute. Subscripts cannot be used for variables that
have been used as scalar (non-array) variables in the script.
If the script references the DIMENSION array attribute, remove the
subscripts. If the script is referencing a scalar variable with array
attributes, the reference needs to be rewritten.
Expected a LIST or MATRIX attribute, not a form attribute.
An attempt was made to use a form attribute with an array.
Correction
When referencing form attributes, the form attribute should follow the
form name and a colon.
–14017
Attribute applies to a different object class than that of the default
object.
Explanation
Correction
The object is the OBJECT_NAME for the default object. A reference to
an attribute did not explicitly specify the object to use, and this attribute
is not meaningful for the default object. For example: an ON FIELD
section contains ”SET FIND_ACTION TO TRUE”. FIND_ACTION
applies only to command objects, but the default object can be only the
field (data object) or the form.
Explicitly reference the object name, for example:
SET my_command: FIND_ACTION TO TRUE
–14018
Explanation
Correction
Error Messages
Attribute inapplicable. Applies only to objects with a different class
than that of the object.
Contained in the message.
Remove all references to the inapplicable attribute.
301
–14019
Explanation
Correction
–14020
Explanation
Correction
–14021
Explanation
Correction
–14022
Explanation
Correction
–14023
Explanation
Correction
–14024
Explanation
Correction
302
Attribute reference out of context. Current context has no default
object of the class to which this attribute applies.
A stored procedure refers to an attribute but does not qualify the attribute
name by object name, and the attribute does not apply to any object in the
current 4GL context.
Make sure that all attribute references are in the correct context.
Attribute isn’t accessible from 4GL.
Contained in the message.
Remove all references to the inaccessible attribute.
Inappropriate number of subscripts.
Contained in the message.
Find the problem subscript reference and correct it.
Unable to convert constant to internal representation.
A numeric constant has a value outside the range that can be represented
in the host machine’s hardware architecture.
Find a way to reduce the size of the constant.
Invalid action specified for NEXT ACTION statement.
The operand of a NEXT ACTION statement was neither the name of a
predefined command that is valid in this context nor a RECORD clause.
Find the NEXT ACTION statement with the invalid operand and make
sure that the command name is valid. Use only valid predefined
command names.
Invalid data type specified for RETRIEVE statement.
The RETRIEVE statement simply reads TEXT or BINARY values from
files. The compiler expected the next token to be either the TEXT
keyword or the BINARY keyword.
Find the RETRIEVE statement that is missing the TEXT or BINARY
keyword and rewrite the statement.
Error Messages
–14025
Explanation
Correction
–14026
No system variable with this name exists.
The compiler expected the next token to be a system variable but found
instead an invalid variable name.
Find the statement that has the incorrect system variable name and
correct the variable name.
BEFORE APPLICATION and BEFORE FORM in same script. Both
sections translate to ON CREATE, will produce duplicate ON CREATE
sections. Edit script to merge both sections into a single ON CREATE
section.
Explanation
Correction
–14027
Explanation
Contained in the message.
Follow the instructions in the message.
Expected END to terminate block of statements.
Check for END omitted or garbled syntax.
Following the statements in an EXECUTING clause of the SELECT
statement, the compiler expected the next token to be the END keyword.
Correction
Find the statement that is missing the END keyword, and rewrite the
statement. See Unify DataServer: SQL/A Reference for the syntax and
usage of stored procedure statements.
–14028
BREAK always returns UNDEFINED. Use RETURN if you want to
specify a return value.
Explanation
Correction
–14029
Explanation
Correction
Error Messages
A BREAK statement in a function but not in a loop specified an operand
that probably was intended as a RETURN value. In this case, BREAK
does not return a value, but instead returns UNDEFINED.
Use RETURN instead of BREAK.
Can’t call a DBMS_ERROR function directly.
A function declared to be a DBMS error-handler was called. This is
illegal from Unify 4GL; only the runtime manager can call a DBMS error
handler.
Find the reference to the wrong function name and either change the
name or delete the call.
303
–14030
Explanation
Correction
Can’t call a TIMER function directly.
The compiler found an invalid timer function reference in which the
timer function was called by using the format function_name(parameter).
Try either or both of these solutions:
Find the timer function call and rewrite the call by using the
CREATE TIMER EVENT statement before referencing the timer
function.
Make sure that the timer function declaration uses the EXTERN
SCRIPT TIMER statement.
–14031
Explanation
Correction
–14032
Explanation
User cancelled compilation(s).
This error message indicates that compilation was cancelled interactively.
If the cancellation was unintentional, restart the compilation(s).
USING clause in unexpected context.
Have you confused a CHOOSE FORM statement with the ON
CHOOSE NEXT FORM event section or its ACCELL/SQL equivalents,
CHOOSE NEXT FORM or CHOOSE FIRST FORM?
Contained in the message. This error is more likely to occur when you
import ACCELL/SQL applications.
Correction
Find the CHOOSE FORM statement or ON CHOOSE NEXT FORM event
section that has the inappropriate USING clause and correct the
statement.
–14033
Cannot use SET or SELECT to set CLEAR TO ADD/FIND expressions.
Explanation
Because clear to find and clear to add expressions are not evaluated until
the corresponding command is executed, the CLEAR_FIND_EXP and
CLEAR_ADD_EXP attributes cannot be set with a SET . . . SELECT
statement. Only simple SET statements can be used to set these attributes.
Correction
To achieve the same results as setting a CLEAR_FIND_EXP attribute
from a SELECT statement, use this technique:
1. In the ON CLEAR TO FIND section set a general variable to the
value returned by a SELECT statement.
2. Set the CLEAR_FIND_EXP attribute to the value of the variable,
for example:
304
Error Messages
ON CLEAR TO FIND
SET tmp_id TO SELECT id FROM id_table;
SET emp_id:CLEAR_FIND_EXP TO tmp_id;
Because clear to find expressions are evaluated immediately after
the ON CLEAR TO FIND section is executed, the attribute must be
set in the ON CLEAR TO FIND section. Any change to the value
of tmp_id changes the value that is assigned to emp_id.
A similar technique can be used to set a CLEAR_ADD_EXP attribute in
the ON CLEAR TO ADD section.
–14034
Explanation
Correction
–14035
Unable to recognize operand as a command attribute.
A COMMAND statement contains an operand that does not start with the
name of a command attribute. This can also apply to compatible parsing
of ACCELL/SQL DEFINE COMMAND sections or SET COMMAND
statements.
Find the problem COMMAND statement and correct it.
Command name in SET COMMAND has invalid form. Inconsistent
with ACCELL/SQL 2.1 syntax.
Explanation
An ACCELL/SQL SET COMMAND statement appears to use a command
name whose syntax was illegal in ACCELL/SQL. This error prevents the
compiler from compiling the statement as an equivalent SET statement.
Correction
Either identify the error in the ACCELL/SQL SET COMMAND statement
or rewrite the statement as a SET statement.
–14036
Explanation
Correction
Error Messages
Command attribute in SET COMMAND is invalid, inconsistent with
ACCELL/SQL 2.1 syntax.
This message applies only to scripts that are compiled with one of the
vcpl compatibility feature sets. The compiler found an invalid command
action attribute or an invalid prompt attribute while parsing the SET
COMMAND statement.
Either find the SET COMMAND statement that contains the invalid
command attribute and rewrite the statement, or preferably, convert the
statement to the COMMAND section.
305
–14037
Explanation
Correction
–14038
Explanation
Correction
–14039
This is an error on the vcpl command line. The command line contains
both a -script argument and a -form or -function argument for a form or
function in an application or in a library. This specifies two separate
sources for the script to compile.
Remove the inappropriate argument(s) from the vcpl command line.
Command name identifies a predefined command. Can’t use this
name.
Developer-defined commands cannot have the same name as any
predefined command.
Use a different name for the developer-defined command.
Command not defined.
Explanation
The compiler found an invalid command name in either a COMMAND or
a QUEUE COMMAND statement. The command name must be either a
command that is defined on this form or the name of a valid command.
Correction
Change the command name to a valid developer-defined command name
or a command.
–14040
Explanation
Correction
–14041
Explanation
Correction
306
Command specifies two module sources; Use either source in an
object library or source in a file, not both.
Code image has invalid format.
An internal logic error has occurred in formatting of a compiled stored
procedure into a code image. The code image is invalid.
Please contact Unify Customer Support.
Input error reading P-code.
Under normal conditions, this message should never be generated by the
compiler. It indicates that an intermediate layer of software identified a
system input error when reading compiler output (P-code). However, the
compiler never reads its own output.
If this message is displayed, please call Unify Customer Support.
Error Messages
–14042
Explanation
Correction
–14043
Explanation
Correction
–14044
Explanation
Correction
–14045
Explanation
Logic error: Unknown error code for P-code i/o.
This error should not normally occur.
If this error occurs, please contact Unify Customer Support.
Insufficient memory for P-code input/output.
Dynamic memory allocation failed when trying to write out the compiled
stored procedure module.
Increase swap space or kill unneeded processes and rerun.
Output error writing 4GL P-code.
Check permissions for directory being used for .uvo output file
to assure that it allows write access.
The compiler was unable to write out compiled p-code.
Make sure that you have sufficient disk space and no hardware errors.
Expected a ”:” (colon).
The compiler expected a colon (:) in a statement. The colon is required
in these locations:
after the constant specified in a CASE clause of a SWITCH
statement
after the DEFAULT keyword in a SWITCH statement
Correction
–14046
Explanation
Find the statement that is missing the colon, and rewrite the statement.
See Unify DataServer: SQL/A Reference for the syntax and usage of 4GL
statements.
Expected a ”,” (comma).
The compiler expected a comma (,) in a stored procedure statement. The
comma is required in these locations:
in the MATRIX declaration between the row and column
specifications
between parameters in a function definition
Correction
Error Messages
Find the stored procedure statement that is missing the comma, and
rewrite the statement. See Unify DataServer: SQL/A Reference for the
syntax and usage of stored procedure 4GL statements.
307
–14047
Explanation
Correction
–14048
Expected a command name.
The compiler expected the next word to be the name of a command. The
command name must follow the COMMAND keyword in the
COMMAND section.
Find the COMMAND section that is missing the command name and
write in the command name.
USING CONNECTION clause in wrong context.
Next input should be a stored procedure call, but it isn’t.
Explanation
Correction
–14049
Explanation
Correction
–14050
Explanation
Correction
308
In the current context, the only thing that can possibly follow the USING
CONNECTION clause is a stored procedure call, but no call was made.
Either make sure that the next statement is a stored procedure call or
change the context of the USING CONNECTION clause.
USING CONNECTION clause in wrong context.
Next input should be a 4GL statement, but it isn’t.
In the current context, the only thing that can possibly follow the USING
CONNECTION clause is a VISION 4GL statement, but no statement was
found.
Either make sure that the next statement is a VISION 4GL statement or
change the context of the USING CONNECTION clause.
This expression must be constant-valued.
The compiler expected the next token to be a constant. The compiler
expects a constant expression in the value following the CASE keyword
in the SWITCH statement.
Find the SWITCH statement that is missing the constant in a CASE
clause, and rewrite the statement. See Unify DataServer: SQL/A Reference
for the syntax and usage of the SWITCH statement.
Error Messages
–14051
Explanation
Correction
–14052
This expression must be constant-valued.
Did you mean to use ’single quotes’ instead of ”double quotes”?
Single quotes enclose a string constant,
double quotes enclose an identifier.
Contained in the message.
Follow the guidelines in the message.
Invalid date constant.
September 3 through September 13 didn’t exist in 1752.
Explanation
The stored procedure contains a date constant in which the specified date
is in the range of 9/3/1752 through 9/13/1752; these dates which did not
exist because the calendar was converted and standardized.
Correction
Find the invalid date constant and make sure that the date does not fall in
the range of 9/3/1752 through 9/13/1752.
–14053
Explanation
Correction
–14054
Explanation
Correction
–14055
Explanation
Correction
Error Messages
Invalid date constant.
Day out of range.
The stored procedure contains a date constant in which the day is out of
range, for example, 1/39/93.
Find the invalid date constant and make sure that the day value is not
greater than the maximum number of days in the month.
Invalid time constant.
Hours out of range (0 to 23).
A time constant contains an invalid hour specification.
Find the invalid time constant and make sure that the hour is in the range
of 0 to 23.
Invalid time constant.
Minutes out of range (0 to 59).
A time constant contains an invalid minute specification.
Find the invalid time constant and make sure that the minute is in the
range of 0 to 59.
309
–14056
Explanation
The stored procedure contains a date constant in which the month is out
of range, for example, 14/15/93.
Correction
Find the invalid date constant and make sure that the month value is in
the range of 1 through 12.
–14057
Invalid date constant.
Year has unexpected number of digits - should be 2 digits (YY) or 4
digits (YYYY).
Explanation
The stored procedure contains a date constant in which the year is out of
range, for example, 1/15/193.
Correction
Find the invalid date constant and make sure that the year value is either
two or four valid digits.
–14058
Statement is illegal in this event section.
Explanation
Contained in the message.
Correction
Use a different statement.
–14059
Explanation
Correction
–14060
310
Invalid date constant.
Month out of range (1 to 12).
Preprocessor failed.
Before compiling the script file, the compiler runs the C preprocessor on
the script. This error occurs if the C preprocessor finds many errors in the
stored procedure named stored_proc.
This error should be preceded by other error messages from the C
preprocessor. See your operating system documentation on the C
preprocessor for assistance.
Unable to execute preprocessor, CPP.EXE.
Error Messages
Explanation
This applies only to the DOS product and indicates that the compiler
could not successfully run the C preprocessor. The compiler will continue
compilation but will not process any preprocessor directives, such as
#include and #define.
Possible causes of this problem are these:
The preprocessor is corrupted.
The system cannot find the preprocessor because the user’s path is
incorrect or damaged.
The system can find the preprocessor but cannot run it because of
something specific to the system.
Correction
If this error occurs, pleas contact Unify Customer Support.
–14061
CREATE operand is unrecognized.
Expected FORM, LOCAL, PIPELINE, SCHEMA, TABLE, or VIEW.
Explanation
The operand that follows CREATE at the start of a statement does not
correspond to a valid statement.
Correction
Find the invalid CREATE statement and make sure that it has a valid
operand.
–14062
Explanation
Correction
–14063
Explanation
Correction
–14064
DB interface reports error of type unknown to compiler.
The error reported by the DBMS cannot be recognized by the compiler.
See the database error log for clues about the cause of the error. Examine
your stored procedure for errors and correct them.
DB interface reports a database error of unrecognized type.
Contained in the message.
Determine which database operation is involved (use your DBMS
manuals), then contact Unify Customer Support.
DB interface reports a database error of unrecognized type.
Explanation
An internal error has occurred, although this type of error should not
normally occur.
Correction
Determine which database operation is involved, then contact Unify
Customer Support.
Error Messages
311
–14065
DB interface reports invalid or corrupted index.
Explanation
One of the indexes used with the application database is corrupted or out
of date. This error should not normally occur.
Correction
See your database error log for related information. If all index files are
available and appear to be in sync with the database, but the error
persists, please call Unify Customer Support.
–14066
Explanation
Correction
–14067
Explanation
Correction
–14068
Explanation
Correction
–14069
Explanation
DB interface reports invalid or corrupted buffer cache.
A DBMS buffer cache is corrupted or cannot be found.
See your database error log for related information. Also make sure that
all DBMS variables that refer to cache use are set correctly and that
enough memory has been allocated for the cache. If the error persists,
please call Unify Customer Support.
DB interface reports no space in DB from some resource.
The database has run out of resources. This error is probably because the
maximum number of tables, columns, buffers, indexes, partitions, or files
has been exceeded, or the maximum amount of space has been exceeded.
Determine which resource has been exhausted. Find the instructions in
Unify DataServer: Managing a Database to increase the resource, then
try the operation again.
DB interface reports required process not active.
The DBMS needs a process but cannot start it.
Examine your database error log for related information. Make sure that
all processes that are required by the DBMS are available. If the error
persists, call Unify Customer Support.
DB interface reports binding error.
An internal error occurred while performing a bind operation in the
DBMS interface.
Correction
312
Determine which database operation is involved, then contact Unify
Customer Support.
Error Messages
–14070
DB interface reports attempt to use an unusable view.
Please verify that you reference only tables and updatable views.
Explanation
The attempted operation was not valid for the specified view. For
example, a delete operation was attempted on a view that cannot support
this operation.
Correction
Determine which database operation is involved. Then either change your
stored procedure so that it does not perform the invalid operation, or
change the stored procedure so that it operates on a database object where
the operation is valid.
–14071
Explanation
Correction
DB interface reports date conversion or format error.
A date constant was specified in an illegal format. The database may
have an unconverted UNIFY 4.0 or 5.0 format DATE value that has not yet
been converted to Unify DataServer format.
See the database error log for related information. Make sure that all
DATE values have been converted to Unify DataServer format.
–14072
DB interface reports database has been modified since the
application was built and is no longer compatible
with the application.
1. Verify that you are referencing the correct database
2. Verify that other users are not modifying the database schema
3. Check the types of target fields to assure match with DB columns
4. Rebuild the application
Explanation
The database design has been modified since the stored procedure was
created and is incompatible with the stored procedure. For example, a
column data type may have been changed. Or you may be accessing the
database from the wrong schema.
Correction
–14074
Follow the instructions in the message.
DB interface reports that a DB resource has been exhausted.
Explanation
A list element in an RHLI status list was valid but that no action was
taken due to an error in another element of the list. This error is usually
accompanied by another error in the status list.
Correction
Check the status list errors. Find the RHLI function that causes the error
and correct the offending list element.
Error Messages
313
–14075
Explanation
The specified database login information is either misspelled or is for a
user who has not been granted database access. The user name and
password can be specified on the command line or by the DBUSER and
DBPASSWORD configuration variables.
Correction
Make sure that the user name and password are correctly spelled for the
user and that the user has been granted database access permission.
–14076
Explanation
Correction
–14077
Explanation
Correction
–14078
Explanation
Correction
314
DB interface reports an invalid DB user name or password.
DB interface reports an internal interface error.
Please contact Unify Customer Support.
The DBMS interface is using the database in an invalid way. This is error
should not normally occur.
Determine which database operation is involved, then contact Unify
Customer Support.
DB interface reports a network error while accessing the DB.
A DBMS network error has occurred.
Make sure that you are running the correct version of the DBMS software
and that the network hardware and software are working correctly.
DB interface reports that a deadlock has been detected.
The transaction has been aborted, please retry.
Deadlock has occurred because two or more users are waiting for
resources that cannot be freed because they are held by the waiting users.
The DBMS has detected this situation and aborted your transaction.
Repeat all the operations in the aborted transaction.
Error Messages
–14079
DB interface reports “cannot open database”.
Check database setup in DCM file, application profile,
environment variables, and command line options.
If setup is correct check DB server for incorrect setup
or resource limitations, such as insufficient memory,
disk space, network connections, processes, etc.
Explanation
Correction
The compiler was unable to make a connection to the specified database.
Try these solutions:
Make sure that database connection information is specified
correctly and that the corresponding section of the database
connection map file contains the correct information.
Make sure that all related configuration variables are set correctly.
Make sure that the user has the correct database access
permissions.
–14082
Explanation
Correction
–14087
Explanation
Correction
Error Messages
DB interface reports a stored-procedure parameter error.
An UNDEFINED parameter was passed when no default value
for the parameter had been specified in the stored procedure.
UNDEFINED was specified as an argument to a stored procedure that did
not have a default defined for that argument. UNDEFINED can be used as
an argument only when a default is defined.
Fix the application so that it does not pass UNDEFINED unless the
argument has a default.
DB interface reports detecting a NULL timestamp.
A timestamp field was left empty. Because timestamp fields are
date-time fields that are automatically updated, this error should not
normally occur.
If this error occurs, please call Unify Customer Support.
315
–14088
DB interface reports an implicit type conversion error
in a stored procedure call.
Check the 4GL script to assure that the definition and invocation
of the stored procedure use compatible types.
Explanation
Correction
–14089
The types of arguments in a stored procedure call do not match.
Verify that the arguments in all stored procedure calls match the stored
procedure definitions.
DB interface reports an operand type clash
in a stored procedure call.
Check the 4GL script to assure that the definition and invocation
of the stored procedure use compatible operand types.
Explanation
Correction
–14090
Explanation
Correction
The types of arguments in a stored procedure call do not match.
Verify that the arguments in all stored procedure calls match the stored
procedure definitions.
DB interface reports a column insert or update rule violation.
The user has entered data that violates the rules set in the DBMS for this
database column.
Enter data that does not violate the rules for this column.
If the ACLDBDBG configuration variable is set to a file name, the print or
raiserror information is printed in the specified file.
If the ACLDBDBG configuration variable is set to a file name, the print
or raiserror information is printed in the specified file. The ACLDBDBG
configuration variable is described in Configuration Variable and Utility
Reference.
316
Error Messages
–14094
DB interface reports an invalid column specification.
This can occur if an attempt is made to insert a value into a
pseudo-column or to update a pseudo-column. Note that only
SELECT operations are valid with pseudo-columns.
Explanation
Correction
–14096
Explanation
Correction
–14097
Although column specification errors are not limited to pseudocolumns,
this error can occur if you try to update a pseudocolumn or insert a value
into a pseudocolumn (ROWID). You can display (SELECT)
pseudocolumn values, but you cannot insert or update them.
Do not update or insert values into a pseudocolumn.
DB interface reports arithmetic overflow.
While the compiler was converting a value from a data type
to a database column type or another data type, an arithmetic
overflow occurred.
Change the statement to prevent the conversion of values that could
cause overflow.
DB interface reports obsolete error, MBUDVSQL.
Explanation
This error should never occur in normal operation.
Correction
If this error occurs, call Unify Customer Support.
–14098
Explanation
Correction
–14099
Explanation
Correction
Error Messages
DB interface reports attempt to divide by 0.
A stored procedure statement contained an expression that tried to divide
a value by zero.
Find the problem expression and make sure that the divisor cannot
evaluate to 0.
DB interface reports attempt to use a NULL value in an expression.
An expression contained a null operand; null values cannot be used in
expressions.
Find the problem expression and make sure that none of the operands can
evaluate to null.
317
–14100
DB interface reports ambiguous object name.
Found in more than one schema
Explanation
Correction
–14101
Explanation
Correction
–14102
Explanation
Correction
–14103
Explanation
Correction
–14104
Explanation
Correction
318
The specified object name was ambiguous because it could refer to more
than one object.
Use a more fully qualified name.
DB interface reports invalid column name.
1. Verify that you are referencing the correct database.
2. Verify that the target table contains a column
for each target field on the current form.
The database has been modified since this application was built.
Make sure that you are referencing the correct database. Also make sure
that the target table contains matching columns for all target fields
defined for the current form.
DB interface reports invalid unlock option.
The UNLOCK statement contained an invalid option.
Find the UNLOCK statement that contains the invalid option and correct
the error.
DB interface reports internal error accessing ASQLCRSR pool.
Unify DataServer uses internal structures to store information on its
currently active cursors. This error indicates that an internal error has
occurred in the management of these structures.
If this error occurs, please call Customer Support.
DB interface reports internal error accessing ASQLINFO pool.
Unify DataServer uses internal structures to store information used to
process an SQL command. This error indicates that an internal error has
occurred in the management of these structures.
If this error occurs, please call Unify Customer Support.
Error Messages
–14105
DB interface reports invalid use of a text field.
1. You cannot search on a text field in interactive queries.
2. You cannot use a text field in the WHERE clause of a DML
statement.
Explanation
Correction
–14106
Explanation
Correction
–14107
Explanation
Correction
–14108
Explanation
Correction
Contained in the message.
If the DBMS does not allow searches on variable-length text type data,
make sure that users know that they cannot search on TEXT fields and
make sure that no DBMS SQL statement includes a TEXT field name in a
WHERE clause.
DB interface reports string literal too long.
String literals in DML statements must be no more than 256
characters.
Contained in the message.
Find the statement that contains the STRING literal that is over 256
characters and reduce the number of characters.
DB interface reports record insertion error
. . . trying to insert a record with a duplicate key value
on a column which has a unique index.
Contained in the message.
Add stored procedure statements, if necessary, to ensure that users cannot
enter duplicate values to unique index key fields.
DB interface reports nonexistent schema or database name.
Contained in the message.
Try these solutions:
Examine the stored procedure to make sure that schema names or
database names are spelled correctly.
Make sure that all related configuration variables are set correctly.
Make sure that the user has the correct database access
permissions.
Error Messages
319
–14109
DB interface reports table not accessible.
Either the table name does not exist in this schema/database
or you do not have permission to access this table.
Explanation
Correction
–14110
Explanation
Correction
–14111
Explanation
Correction
–14112
Explanation
Correction
–14113
Explanation
Correction
320
Contained in the message.
Examine the stored procedure to make sure that table names are spelled
correctly, and make sure that the user has the correct database access
permissions.
DB interface reports internal error, invalid SQLID.
Unify DataServer uses internal structures to manage memory used to
process an SQL command. This error indicates that an internal error has
occurred in the management of these structures.
If this error occurs, please call Unify Customer Support.
DB interface reports error in number of columns returned
. . . number returned does not match number expected.
When the record was fetched from the database, the number of columns
returned did not match the number expected. This error indicates that an
internal error has occurred.
If this error occurs, please call Unify Customer Support.
DB interface reports internal type error.
ACCELL_TYPE is not supported by database.
maps each of its various data types to corresponding Unify
DataServer data types. An invalid type was found when doing
this mapping. This error indicates that an internal error has occurred.
If this error occurs, please call Unify Customer Support.
DB interface reports attempt to use undefined variable.
Undefined Unify 4GL variables cannot be used in SQL statements.
An UNDEFINED value was encountered when processing a stored
procedure call.
Determine which value is UNDEFINED and set it to a defined value.
Error Messages
–14114
DB interface reports internal DB-type error.
Database type is illegal or unsupported.
Explanation
maps each of its various data types to corresponding Unify
DataServer data types. A database type that is not mapped to a type (is not supported by ) was found.
Correction
Remove the reference to the column that has the unsupported data type.
–14115
Explanation
Correction
–14116
Explanation
Correction
–14117
DB interface reports text of an SQL statement is too long.
An SQL statement is longer than allowed by the DBMS.
Reduce the size or number of search criteria, and reduce the number of
columns updated or inserted.
DB interface reports internal error, unknown signal.
Unify DataServer found an unknown signal in the interrupt handler area.
If this error occurs, please call Unify Customer Support.
DB interface reports heap memory exhausted.
Explanation
Unify DataServer keeps a variety of internal information in an area called
the heap. The current heap size is too small to run the current application.
Correction
To increase the heap size, set the AMGR_HPSZ configuration variable to a
higher value.
–14118
Explanation
Correction
DB interface reports memory exhausted.
Unify DataServer has run out of memory for the stored procedure.
Try these solutions:
Commit transactions frequently.
Reduce the size or complexity of the stored procedure.
As a last resort, the system administrator can reconfigure the
memory parameters of your operating system.
Error Messages
321
–14119
DB interface reports unable to open/create a data file
. . . data file is variable length (text/binary).
Explanation
Correction
Unify DataServer stores TEXT and BINARY values that have lengths
greater than the value specified by the ACLVARMEMLIM configuration
variable in temporary files. An attempt to open or create a one of these
files failed.
Try these solutions:
Make sure that the directory that is specified by the ACLVARDIR
configuration variable has read/write permissions.
Make sure that enough disk space is available for the file.
Make sure that the number of variable length data files being used
is not excessive.
–14120
Explanation
Unify DataServer stores TEXT and BINARY values that have lengths
greater than the value specified by the ACLVARMEMLIM configuration
variable in temporary files. An attempt to close one of these files failed.
Correction
Make sure that you have enough disk space. If you have plenty of disk
space, this error may indicate an internal error, in which case you should
call Unify Customer Support.
–14121
322
DB interface reports unable to close a data file
. . . data file is variable length (text/binary).
DB interface reports data file read error
. . . data file is variable length (text/binary).
Explanation
Unify DataServer stores TEXT and BINARY values that have lengths
greater than the value specified by the ACLVARMEMLIM configuration
variable in temporary files. The user can also read TEXT and BINARY
values from user files by using the RETRIEVE statement. An attempt to
read or access one of these temporary or user files failed.
Correction
Make sure that the directory that is specified by the ACLVARDIR
configuration variable exists and has correct read permissions. If the file
is used in a C function, make sure that its length is set correctly.
Error Messages
–14122
DB interface reports data file write error
. . . data file is variable length (text/binary).
Explanation
Correction
–14124
Explanation
Correction
–14125
Explanation
Correction
–14126
Explanation
Correction
–14127
Explanation
Correction
Error Messages
Unify DataServer stores TEXT and BINARY values that have lengths
greater than the value specified by the ACLVARMEMLIM configuration
variable in temporary files. The user can also store TEXT and BINARY
values in user files by using the STORE statement. An attempt to write to
one of these temporary or user files failed.
Make sure that the directory that is specified by the ACLVARDIR
configuration variable exists and has correct write permissions. Also
make sure that enough disk space is available for the file.
DB interface reports invalid row id.
The columns that were specified as the row ID cannot be used.
Make sure that the row ID columns are of valid data types and that the
resulting row ID value is unique for each row.
DB interface reports dirty data was used.
Data that was locked by another user was used for this operation; the data
may have been in the process of being changed.
Wait and retry the operation.
DB interface reports a row or table is locked by another user.
Contained in the message.
Retry the operation at a later time.
DB interface reports nonexistent table or user name.
The specified table or user name cannot be found in the database.
Make sure that the table name or user name is spelled correctly. For a
table name, make sure that the user has the correct access permissions for
the table.
323
–14128
Explanation
You attempted to use a DBMS feature that has not been implemented, for
example, you tried to use the UNIFY 2000 Data Integrity Subsystem with
an ORACLE database.
Correction
Make sure that you use only the features that are implemented for and
recognized by the DBMS. And make sure that the DBTYPE configuration
variable is set to the type of database being used.
–14129
Explanation
Correction
–14130
Explanation
Correction
–14131
Explanation
Correction
–14132
Explanation
Correction
324
DB interface reports feature not implemented.
DB interface reports no user information specified.
For remote database access, the DBMS requires users to log in to the
database, but either no user name was specified or the specified user
name is illegal or unknown.
Make sure that the DBUSER configuration variable is set correctly.
DB interface reports unknown database type.
Either the DBMS that was specified by the DBTYPE configuration
variable is not supported, or the DBMS version is not licensed.
Make sure that the DBTYPE configuration variable is set correctly and
that the DBMS version is licensed.
DB interface reports invalid argument or options.
An invalid argument was specified for a Unify DataServer SQL/A
statement. For example, a statement may include ORACLE extensions.
Find the SQL/A statement that has the invalid argument and correct it and
make sure that the database connection is correct.
DB interface reports database conversion error.
An attempt was made to convert between incompatible data types, for
example, a TEXT value cannot be stored in a database FLOAT type
column.
Examine the script for and eliminate incompatible data type conversions.
Error Messages
–14133
DB interface reports blobs not allowed in WHERE clause.
Eliminate text columns from selection criteria.
Explanation
Correction
–14134
Explanation
Correction
–14135
Explanation
Correction
–14136
Explanation
Correction
–14137
Explanation
Correction
Error Messages
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Unify Customer Support.
DB interface reports SQL server aborted command.
The DBMS aborted the command, for example because the user pressed
Control-C.
Examine your database error log and transaction log for information.
DB interface reports invalid number of columns specified.
The number of columns specified in the statement exceeds the maximum
allowed.
Make sure that the number of columns specified is valid.
DB interface reports SQL server terminating “the proc”.
Contained in the message.
Examine the messages in the database error log file to determine why the
database process was terminated.
DB interface reports unable to open database.
The NULL database option (–nodb) cannot be used with an
application that requires a database.
Contained in the message.
Make sure that the correct database type is specified.
325
–14138
DB interface reports invalid NULL value specified.
A NULL value was specified for a column
which is defined with the NOT NULL constraint.
Explanation
An attempt has been made to insert or update a column’s data value to
null when the column has been specified as NOT NULL. Non-null default
values can be assigned to null columns with the Data Integrity Subsystem
(DIS).
Correction
Make sure that the valopts field of the UNIPCOLL structure is correctly
initialized before performing the insert or update operation.
–14139
Explanation
Correction
–14140
DB interface reports invalid data value specified.
The ASCII value provided for conversion to a database type is not valid
for the specified type. For example, this error can occur if non-numeric
characters are provided for a numeric column.
Either provide a valid ASCII value or change the destination type to
something that will allow the data provided.
DB interface reports invalid value in a DB column.
Value is outside the range specified as valid for the column.
Explanation
326
An attempt was made to write an out-of-range value to a database
column. For example, an INTEGER 6 value cannot be stored in an
INTEGER 4 column.
Correction
Make sure that database columns can accommodate the values that you
are trying to store.
–14141
DB interface reports compiled object doesn’t match mapped object.
Explanation
An attempt has been made to map a compile-time ID to a runtime object
whose MAPID no longer reflects the same physical characteristics as the
compile-time object. The runtime object has probably had schema
modifications made to it since the compile-time object was referenced.
Correction
The application source files that reference the object need to be
recompiled using the ucc utility, and relinked using the uld utility.
Depending on the changes made to the object, source code modifications
may be necessary.
Error Messages
–14142
Explanation
Correction
–14143
Explanation
Correction
–14144
Explanation
Correction
–14145
Explanation
Correction
–14146
Explanation
Correction
Error Messages
DB interface reports invalid name.
The database object name specified included reserved characters or was
of zero length.
Correct the object name.
DB interface reports ”scnid” is not found.
An attempt has been made to reference a Scan ID that does not exist.
Make sure that the Scan ID was returned from a successful RHLI ubegscn
function call. Also make sure that this scan was not closed with the RHLI
uendscn function call.
DB interface reports invalid selection criteria.
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Unify Customer Support.
DB interface reports column type mismatch.
An attempt has been made to reference an index using columns that do
not match the columns used to create the index.
Make sure that the Column IDs match the Column IDs used to create the
index. Make sure that the Column IDs do not reference a column group.
DB interface reports failure to back out a column change.
The database system detected an internal, non-recoverable error while
trying to back out a failed operation. See the errlog file for an entry
describing the cause of the error.
Recover the database using the irma utility.
327
–14147
Explanation
Correction
–14148
Explanation
Correction
–14149
Explanation
Correction
–14150
Explanation
Correction
–14151
Explanation
Correction
328
DB interface reports fatal error in B-tree access.
An internal error was detected while scanning a B-tree index. This is an
internal error and should not occur in the normal database execution.
If this error occurs, please call Unify Customer Support.
DB interface reports error opening B-tree.
The system was unable to open a B-tree index file.
Make sure that the B-tree index file has not been removed. If the B-tree
index file exists and you still receive this error, please call Unify
Customer Support.
DB interface reports combination column not allowed.
An attempt has been made to reference a Column Group ID, instead of
the component members’ Column IDs. In most RHLI functions, the
Column Group ID may not be referenced.
Use the Column IDs for the member columns in the column group.
DB interface reports nonfatal internal error.
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Unify Customer Support.
DB interface reports internal conversion error.
An attempt has been made to perform a an invalid data conversion. This
error occurs when the data to be converted does not conform to the
constraints for the column’s data type. For instance, the date 88/88/88
would produce this error because the month “88” is invalid.
Make sure that the data to be converted conforms to the column’s data
type restrictions.
Error Messages
–14152
Explanation
Correction
–14153
Explanation
Correction
–14154
Explanation
Correction
–14155
Explanation
Correction
–14156
Explanation
Correction
Error Messages
DB interface reports conversion error.
This is an internal error and should not occur in normal database
execution.
If this error occurs, please call Unify Customer Support.
DB interface reports open/create failed for sort/merge file.
Unify DataServer failed to create or open a sort/merge file. You may have
run out of file descriptors.
Manage your file descriptors so that you do not exceed the limit. You
may need to reconfigure your operating system if you encounter a
consistent shortage of file descriptors.
DB interface reports database already closed.
An attempt has been made to access a database that has not yet been
opened or that has since been closed.
Perform the operation after the database has been opened and before the
database has been closed. Make sure that the open database operation
succeeded before you try other database activities.
DB interface reports invalid Unify length.
An attempt has been made to specify an internal column data type length
that is larger than the maximum allowable data length.
Check the restrictions for the data types that you are using.
DB interface reports generic operating system error.
An operating system error has occurred.
Try to determine the statement of statements causing the error. Examine
the error that occurred just after this one, if any.
329
–14157
Explanation
Correction
–14158
–14159
Explanation
Correction
–14160
Explanation
Correction
An attempt has been made to insert a duplicate key into a B-tree that does
not allow duplicates. This row must already exist in the B-tree.
You cannot add the duplicate key into the B-tree. If you want to add this
duplicate key, you must rebuild the B-tree, allowing duplicates.
DB interface reports invalid format, environment variable.
DB interface reports environment variable not found.
These are internal errors and should not occur in the normal execution of
the database.
If any of these errors occurs, please call Unify Customer Support.
DB interface reports end of scan.
The end of the selected set of rows has been reached, and no more rows
remain to be retrieved.
No correction needed.
–14161
DB interface reports invalid memory address.
Explanation
This error should not occur in normal operation.
Correction
–14162
Explanation
Correction
–14163
Explanation
Correction
330
DB interface reports duplicate key found ”in no dup bt”.
If this error occurs, please call Unify Customer Support.
DB interface reports denied access to file.
Contained in message.
Make sure that the file has the appropriate read/write permissions
specified for the user and the operations that the user is performing.
DB interface reports unable to close a file.
An attempt has been made to close a file that is already closed. This is an
internal error and should not occur in the normal execution of the
database.
If this error occurs, please call Unify Customer Support.
Error Messages
–14164
Explanation
Correction
–14165
DB interface reports file create error: DB already exists.
Contained in the message.
Make sure that the database name is correct. If you are replacing an
existing database, remove the old database files.
DB interface reports row not inserted.
Check for valid reference values.
Explanation
One or more errors occurred on a multi-valued parameter; the actual
errors are contained in the status list that was passed to the function.
Correction
Examine the RHLI function’s status list to determine the actual errors.
Check for the correct number of parameters.
–14166
Explanation
Correction
–14167
Explanation
Correction
–14170
Explanation
Correction
Error Messages
DB interface reports file seek error.
An attempt has been made to perform a file seek operation on a file that
is not seekable, or with an invalid specified seek address. This is an
internal error and should not occur in the normal execution.
If this error occurs, please call Unify Customer Support.
DB interface reports lock granted due to upper level lock.
This is an advisory message that indicates that a lock was granted
because the transaction already holds an enclosing upper level lock. For
example, this message can be displayed when a row lock is requested
while a table lock is already held on the table that contains the row.
No correction needed.
DB interface reports severe internal error.
Possibilities include exhaustion of some resource,
such as memory, shared memory, disk space, and space on the log
device.
Contained in the message.
Determine whether any resources have been exhausted.
331
–14171
Explanation
Correction
–14172
Explanation
Correction
–14173
Explanation
Correction
–14174
Explanation
Correction
–14175
Explanation
Correction
332
DB interface reports illegal argument.
An attempt has been made to specify an option that is invalid or conflicts
with another specified option. This is an internal error and should not
occur in the normal execution of the database.
If this error occurs, please call Unify Customer Support.
DB interface reports illegal test for value type.
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Unify Customer Support.
DB interface reports invalid transaction id.
The database failed to validate a Transaction ID.
Check the validity of the Transaction ID passed to an RHLI function in
your program. Also, make sure that the transaction log file (dbname.lg) is
not running out of space. Your transaction could have been aborted if it
was the oldest open transaction in the log and another transaction needed
space in the log.
DB interface reports current operation interrupted.
This error is returned by most RHLI functions after an interrupt is set by
the default Unify DataServer signal handler or by the function usetitr.
Use the uclritr function to resume processing after the interrupt.
DB interface reports row does not have read permission.
An attempt has been made to read a row from a volume for which the
user does not have read access. This is an internal error and should not
occur in the normal execution of the database.
If this error occurs, please call Unify Customer Support.
Error Messages
–14176
Explanation
Correction
–14177
Explanation
Correction
–14178
Explanation
Correction
–14179
Explanation
Correction
–14180
Explanation
Correction
Error Messages
DB interface reports invalid default type.
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Unify Customer Support.
DB interface reports key cannot be changed.
This row’s key is referred to by related rows;
those references in the related rows must be changed first.
An attempt has been made to delete a row that either has a lock on it or is
a parent link column with existing child links.
Delete all of the child table rows before attempting to delete the parent
table row. The rows can be identified using a link scan.
DB interface reports SIGTERM signal received.
Another user has started to shut down the database, for example, by using
the shutdb utility.
If possible, save your work and exit the database immediately.
DB interface reports lminit failure.
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Unify Customer Support.
DB interface reports key not found.
A duplicate key value is being inserted into a unique-key hash table. The
user may see error -194 (the UENOROW error code), which indicates an
invalid row ID in general (not hash table specific).This is an internal error
and should not occur in the normal execution of the database.
If this error occurs, please call Unify Customer Support.
333
–14181
Explanation
Correction
–14182
Explanation
Correction
–14183
DB interface reports transaction logging not turned on.
An attempt has been made to request a transaction log operation when
logging is not turned on for the process.
Turn on transaction logging by setting the LOGTX configuration variable
to TRUE and retry the operation.
DB interface reports too many open files.
You have tried to open more files than you have file descriptors for.
Close some of the files.
DB interface reports too many DB commands active at once.
1. If too many forms are active use Start Transaction
or Restart Transaction more often.
2. Reduce the level of nesting of DML SET/SELECT EXECUTING
statements.
Explanation
Correction
–14184
Explanation
Correction
–14185
Explanation
Correction
334
An attempt has been made to start a scan that would exceed the
maximum number of simultaneous scans permitted per process.
Follow the instructions in the message. Use the RHLI uendscn function
to make sure that scans are properly closed.
DB interface reports selection table full.
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Unify Customer Support.
DB interface reports could not attach shared memory.
Shared memory could not be attached at the required address. The
required attach address would probably overlap the data space of the
process. This problem is usually caused by starting the database with a
small program, such as shmmap, and later attempting to open the
database with a much larger program, such as SQL or startdb.
Shut down the database and either increase the value of the SHMOFFSET
configuration variable or restart the database using the larger program.
Error Messages
–14186
DB interface reports invalid column id
. . . not part of common table.
Explanation
Correction
–14187
An attempt has been made to reference a column ID that does not exist.
This column may have been deleted just before being referenced.
Make sure that the Column ID was obtained by using the correct name
binding functions such as the RHLI name binding function ubndcol,
through the RHLI functions such as uinftbl or uinfcol, or through the ucc
compiler.
DB interface reports not a column group.
Explanation
An attempt has been made to reference a column group, but the specified
Column IDs do not belong to any known column group. This error occurs
when trying to retrieve rows based on an index key.
Correction
Make sure that the Column IDs are in the same sequence as those used to
create the index. Make sure that the specified number of columns
matches the number specified when the index was created.
–14188
–14189
Explanation
Correction
–14190
Explanation
Correction
Error Messages
DB interface reports no current row for CROW type default.
DB interface reports no current row for ’column type’ default.
These are internal errors and should not occur in the normal execution of
the database.
If either of these errors occurs, please call Unify Customer Support.
DB interface reports ’file.db’ does not exist.
The RDBMS is unable to open the database root volume.
Make sure that the DBPATH and DBNAME configuration variables are set
correctly. Make sure that you have the required operating system
permissions on the file.
335
–14191
Explanation
Correction
–14192
–14193
Explanation
Correction
–14194
An attempt has been made to insert a row into a direct table, where the
specified primary value was mapped to a row that already exists. You can
only insert rows into a direct table at locations occupied by deleted or
non-existent rows. This error only occurs when the primary key value is
specified in the UNIPCOLL data structure.
Use an update operation to update a direct table row.
DB interface reports request was not a demotion request.
DB interface reports no default for this column.
These are internal errors and should not occur in the normal execution of
the database.
If either of these errors occurs, please call Unify Customer Support.
DB interface reports transaction logging not enabled.
Explanation
An attempt has been made to abort a transaction when the transactions
are not logged.
Correction
To be able to abort future transactions, turn on transaction logging by
setting TXLOG configuration variable to TRUE. You can commit
transactions instead of aborting, but the updates affect the database.
–14195
DB interface reports no such file, directory, or program.
Explanation
This error occurs when a file name is specified and the file does not exist,
or when one of the directories in a path name does not exist.
Correction
Check the errlog file to determine which file could not be found. Also,
check the error message documentation for error number 2 in your UNIX
system documentation.
–14196
Explanation
Correction
336
DB interface reports the row was NOT deleted.
DB interface reports file does not exist.
An attempt has been made to open a file that does not exist. This is an
internal error and should not occur in the normal execution of the
database.
If this error occurs, please call Unify Customer Support.
Error Messages
–14197
Explanation
Correction
–14198
DB interface reports mismatch between lpkmgr code and (sic).
The software version that created the shared memory was not the same
version as the current software or the shared memory segment is not a
Unify DataServer shared memory segment.
Make sure that the shared memory segment being used is a Unify
DataServer shared memory segment. If not, you probably need to change
the shared memory key, SHMKEY, to a value unique to this software.
DB interface reports primary key column(s) needed.
The current database operation requires a primary key column
or columns. This is either a search or an insert request.
Change the statement to use all elements of the primary key.
Explanation
Correction
–14199
Explanation
Correction
–14200
An attempt has been made to perform an operation requiring a primary
key column on a table that does not contain a primary key.
Add a primary key column to the table, or perform an operation that does
not require a primary key column, such as through use of a scan.
DB interface reports unable to lock requested object.
The requested object may be locked by another user.
Wait and try again.
DB interface reports log file does not exist.
Explanation
The transaction log file does not exist in the directory that is specified by
the DBPATH configuration variable.
Correction
Make sure that the DBPATH configuration variable is set correctly. Create
the transaction log file using the mklog utility.
–14201
Explanation
Correction
Error Messages
DB interface reports incorrect (old?) version.
The software that created the shared memory was not the same version as
the current software.
Make sure that the correct release of the DBMS software is being used.
337
–14202
Explanation
Correction
–14203
Explanation
Correction
–14204
Explanation
DB interface reports object does not exist.
The specified object does not exist or is not permitted to be seen.
If the object is known to exist, your current database, owner, schema, or
user may not be permitted to see this object. Assume the database, owner,
schema, or user that owns the object and try again.
DB interface reports no privilege for attempted operation.
An attempt has been made to perform an operation for which the user has
not been granted the necessary privilege. This error typically relates to
DDL operations performed against a schema the user has not been
granted access to, but the error can also occur by performing DML
operations on tables or columns that are not accessible to the user. In
certain DDL operations, the user is required to be in the schema (or
database, owner, or user) under which the operation is being performed.
Verify and correct access and privileges as necessary.
DB interface reports permission denied.
You lack permission to access a schema, table, or column.
This message displays in the following cases:
The current schema is not permitted to see the specified objects.
The current schema cannot add or drop desired permissions.
DBA authority is required to run this utility, as is the case for
budb.
Correction
–14205
338
Move to the schema that contains the object and retry. Or make sure that
you have DBA authority before trying to run the utility.
DB interface reports invalid reference column value.
Reference columns must contain the key of a row in the reference
table.
Explanation
An attempt has been made to insert or update a row containing one or
more columns that are children of links. The corresponding row in the
parent table cannot be found using the value of the child column’s data.
Correction
Make sure that the parent table’s row containing the data corresponding
to the child column’s data has been inserted before inserting or updating
the child column’s row.
Error Messages
–14206
Explanation
DB interface reports row does not have write permission.
An attempt has been made to write a row to a volume for which the user
does not have write access. This is an internal error and should not occur
in the normal execution of the database.
Correction
If this error occurs, please call Unify Customer Support.
–14207
DB interface reports key already exists in hash table.
Explanation
Correction
–14208
Explanation
Correction
This is an internal error and should not occur in the normal execution of
the database.
If this error occurs, please call Unify Customer Support.
DB interface reports shared memory exhausted.
An attempt to allocate a structure in shared memory failed because the
size of the shared memory segment was exceeded.
Try to determine which partition is full by using the –p option on the
shmmap command. Then try the following solutions:
If the full partition is in the transaction manager, reduce the
number of active transactions.
If the full partition is in the lock manager, reduce the number of
locks, decrease the setting for the LMPROMO configuration
variable, and commit transactions more frequently.
If the full partition is in the file manager, synchronize the database
more often by adjusting the FREQUENCY and FREQTYPE
configuration variables and reduce the number of pages modified
between synchronizations.
If the error persists, try moving the overflowing segment into its own
shared memory area or increasing the associated shared memory
configuration variable (SHMMAX, TMSHMKEY, LMSHMKEY, FMSHMKEY,
CMSHMKEY).
Error Messages
339
–14209
Explanation
Correction
DB interface reports no space left on device.
No free space remains on the device in which to write an ordinary file.
This is an internal error and should not occur in the normal execution of
the database.
Check the error message documentation for error number 28 in your
UNIX operating system documentation.
–14210
Explanation
Correction
–14211
–14212
Explanation
Correction
–14213
DB interface reports invalid table id.
An attempt has been made to reference a Table ID that does not exist.
Make sure that the Table ID was obtained by using the correct name
binding functions such as the RHLI name binding function ubndtbl,
through the RHLI functions such as uinfath, or through the ucc compiler.
This table may have been deleted just before being referenced.
DB interface reports file descriptor not mapped.
DB interface reports test requires a value.
These are internal errors and should not occur in the normal execution of
the database.
If either of these errors occurs, please call Unify Customer Support.
DB interface reports data value too long.
Reduce length of data value or increase size of database column.
Explanation
Correction
–14214
Explanation
Correction
340
Contained in the message.
Follow the instructions in the message.
DB interface reports modes of parameters do not match.
(This probably refers to a stored procedure call.)
This error can occur when the parameters that are passed to the stored
procedure have different data types than the stored procedure expects.
Make sure that all calls to the stored procedure pass the correct types of
parameters.
Error Messages
–14215
DB interface reports number of parameters does not match.
(This probably refers to a stored procedure call.)
Explanation
The number of parameters that are specified in the stored procedure
declaration does not match the number in the stored procedure definition.
Correction
Make sure that the stored procedure is declared in the EXTERN statement
with the same number of parameters as in the stored procedure definition.
–14216
Explanation
Correction
–14217
Explanation
Correction
–14219
DB interface reports invalid SP
A stored procedure call refers to a stored procedure that was not defined.
Make sure that the stored procedure has been defined and that the
declaration in the EXTERN statement matches the stored procedure
definition in the database.
DB interface reports record insertion error.
Attempting to insert a record with a duplicate value of the key
on which a unique index is created on the table, or, a null value
was specified for a column with the NOT NULL constraint specified.
Contained in the message.
Make sure that index key values are unique for each record; add stored
procedure statements to ensure uniqueness. Also make sure that fields are
always updated with at least a default value if the target table column
cannot be null-valued.
DB interface reports undefined connection name.
Connection name does not match any specified in the DCM file.
Explanation
The specified connection name does not have a corresponding connection
name in the database connection map (DCM) file.
Correction
Make sure that the connection name is spelled correctly and that it exists
in the DCM file. Also make sure that the correct DCM file is being used.
Error Messages
341
–14220
DB interface reports unable to open the DCM file.
Explanation
The database connection map (DCM) file cannot be opened, either
because it does not have the correct permissions set or it does not exist in
the directory specified by the –dcmfile command line argument.
Correction
Make sure that the DCM file is in the specified directory and that the file
has the read permission set for the application users.
–14221
Explanation
DB interface reports syntax error in DCM file.
The DCM file entries must follow the correct format:
Section names must be enclosed in brackets ([section_name]).
Each variable setting (variable_name=value) must start on a new
line.
The variable name must be one of the allowed names.
Variable values are case sensitive.
If included, the [default] section must be the last one in the file.
Correction
–14226
Explanation
Make sure that the DCM file entries are in the correct format. For more
information about the DCM file format, including an example, see Unify
VISION: Application Reference.
Unable to change database [authorization] name.
Unify DataServer was unable to access the specified schema for one of
the following reasons:
The current user does not have the required permissions.
The schema does not exist.
The correct database has not been specified.
Correction
To solve the problem, take these steps:
1. Verify that you have permission to access the specified schema.
2. Verify that the DBUSER and DBPASSWORD configuration variables
are set correctly.
3. Verify that the configuration variables used to identify the database
(for example, DBNAME, DBPATH, and so on) are set correctly.
342
Error Messages
See Unify DataServer: Configuration Variable and Utility Reference for
information about these configuration variables.
–14227
Explanation
Correction
–14228
Explanation
Database (column) type is invalid.
This error indicates that the corresponding database column’s data type is
not a type that can be converted to the type specified in the LOCAL
clause.
Find the problem LOCAL clause, and correct the error.
Unable to close database.
Contained in the message. The message includes the DBMS error
message.
Correction
Correct whatever problem the DBMS reports.
–14229
This function must have 1 LIST parameter.
Explanation
The interface to DBMS error handler functions requires that they accept
one LIST parameter. This list contains information concerning the DBMS
error, and its contents are defined in the file dbmserrs.h.
Correction
Revise the definition or declaration of this DBMS error handler function,
to show that it accepts one list parameter.
–14232
Explanation
Correction
–14233
Explanation
Correction
Error Messages
DBMS reports . . . dbtext
The connected database issued the error or a warning message,
dbms_message.
Read the message text and perhaps the DBMS documentation for
clarification of the message.
Database interface initialization failed.
. . . WILL COMPILE WITHOUT DATABASE CONNECTION.
Check DCM file, application profile, and command line options.
Initialization failed for the interface to the DBMS.
Verify that the database exists and that you have the correct access
privileges.
343
–14234
Explanation
Correction
–14235
Explanation
Correction
–14236
Explanation
Correction
–14237
Explanation
Correction
–14238
Explanation
Correction
–14239
Explanation
344
Unable to retrieve database [authorization] name.
Contained in the message. (DBMS status text is appended.)
Identify and correct the problem that was reported in the DBMS error
status.
Database type not specified, check DBTYPE preference.
This error should not normally occur.
If the error soccurs, please contact Unify Customer Support.
Unable to retrieve database current-user information.
Contained in the message. (DBMS status text is appended.)
Identify and correct the problem that was reported in the DBMS error
status.
Unable to open database.
The compiler was unable to open a connection to a database. If possible,
the cause for the failure is reported in the DBMS message dbtext.
Follow the instructions reported in dbtext.
Unable to reset database interface. DB error status is dberror.
Contained in the message. (DBMS status text is appended.)
Identify and correct the problem that was reported in the DBMS error
status.
Unable to identify database-type characteristics.
This error occurs only in a version of the product that does not support
heterogeneous database access (HDA). The message indicates that the
compiler was unable to recognize the value of the DBTYPE configuration
variable. The database type can also be specified in the database
connection map (DCM) file, but this file is read only when using HDA.
Correction
Make sure that the DBTYPE configuration variable is set correctly.
Correction
Add an EXTERN declaration for the DBMS_ERROR function.
Error Messages
–14240
Incorrect function parameter list
DDE_EVENT handler function for TERMINATE_LINK requires one
VALUE parameter; either the function named uses a different
number of parameters or the parameter is of a different type (e.g.,
REFERENCE instead of VALUE).
Explanation
An INSTALL statement for a DDE_EVENT HANDLER indicated that the
specified function was to handle an INITIATE_LINK event. The handler
for this event must accept three VALUE parameters, but the function
named has an incompatible list of formal parameters. Either it uses a
different number of parameters or the type of at least one parameter is
incorrect (for example, REFERENCE instead of VALUE).
Correction
Make sure that the statement refers to the correct event-handler function
and that this function correctly interprets an INITIATE_LINK event.
–14241
Incorrect function parameter list
DDE_EVENT handler function for INITIATE_HOT_LINK,
TERMINATE_HOT_LINK, REQUEST DATA, or
EXECUTE_COMMAND requires two VALUE parameters; either the
function named uses a different number of parameters or at least one
parameter is of a different type.
Explanation
An INSTALL statement for a DDE_EVENT HANDLER indicated that the
specified function was to handle an INITIATE_HOT_LINK,
TERMINATE_HOT_LINK, or REQUEST DATA event. The handler for
this event must accept two VALUE parameters, but the function named
has an incompatible list of formal parameters. Either it uses a different
number of parameters or the type or at least one parameter is incorrect
(for example, REFERENCE instead of VALUE).
Correction
Make sure that the statement refers to the correct event-handler function
and that this function correctly interprets an INITIATE_HOT_LINK,
TERMINATE_HOT_LINK, or REQUEST_DATA event.
Error Messages
345
–14242
Explanation
An INSTALL statement for a DDE_EVENT HANDLER indicated that the
specified function was to handle an INITIATE_LINK event. The handler
for this event must accept three VALUE parameters, but the function
named has an incompatible list of formal parameters. Either it uses a
different number of parameters or the type of at least one parameter is
incorrect (for example, REFERENCE instead of VALUE).
Correction
Make sure that the statement refers to the correct event-handler function
and that this function correctly interprets an INITIATE_LINK event.
–14243
Explanation
Correction
–14244
346
Incorrect function parameter list
DDE_EVENT handler function for INITIATE_LINK or
RECEIVE_DATA requires three VALUE parameters; either the
function named uses a different number of parameters or at least one
parameter is of a different type.
Cannot use ALL EVENTS clause with a DDE_EVENT handler
Unable to install a DDE_EVENT handler for multiple events
Write one INSTALL statement for each DDE_EVENT to be handled.
An INSTALL statement for a DDE_EVENT HANDLER specified
installation FOR ALL EVENTS. This is possible only for a
DBMS_ERROR handler, not for a DDE_EVENT handler.
Write one INSTALL statement for each DDE_EVENT to be handled.
Incorrect function return type
DDE_EVENT handler function for INITIATE_LINK,
INITIATE_HOT_LINK, RECEIVE_DATA, or EXECUTE_COMMAND
must return value of type BOOL
Explanation
An INSTALL statement for a DDE_EVENT HANDLER indicated that the
specified function was to handle an INITIATE_LINK,
INITIATE_HOT_LINK, or RECEIVE_DATA event. The handler for this
event must return a value of type BOOL, but the function named was
declared or defined to have a different return value type.
Correction
Make sure that the statement refers to the correct event-handler function
and that this function correctly interprets an INITIATE_LINK,
INITIATE_HOT_LINK or RECEIVE_DATA event.
Error Messages
–14245
Explanation
Correction
–14246
Explanation
Correction
–14247
Invalid DDE_EVENT name
A DDE_EVENT name must be one of these: EXECUTE_COMMAND,
INITIATE_HOT_LINK, INITIATE_LINK, RECEIVE_DATA,
REQUEST_DATA, TERMINATE_HOT_LINK, or TERMINATE_LINK
An INSTALL statement for a DDE_EVENT HANDLER specified an
unrecognized event name in its FOR EVENTS clause.
Make sure that the list of event names in the FOR EVENTS clause has no
spelling errors.
Cannot use EXCEPT clause with a DDE_EVENT handler
Unable to install a DDE_EVENT handler for multiple events. Write
one INSTALL statement for each DDE_EVENT to be handled.
An INSTALL statement for a DDE_EVENT HANDLER specified
installation FOR EVENTS EXCEPT those listed. This is possible only for
a DBMS_ERROR handler, not for a DDE_EVENT handler.
Write one INSTALL statement for each DDE_EVENT to be handled.
Function can’t be used as a DDE_EVENT HANDLER.
DDE_EVENT HANDLER functions should be ordinary local or global
functions, not TIMER or DBMS_ERROR functions
Explanation
An INSTALL statement for a DDE_EVENT HANDLER specified a
function of a type that is incompatible with this usage. DDE_EVENT
HANDLER functions should be ordinary local or global functions, not
TIMER or DBMS_ERROR functions.
Correction
Make sure that the function name in the INSTALL statement is correct
and that this function has been correctly declared or defined.
–14248
Incorrect function return type
DDE_EVENT handler function for REQUEST_DATA must return a
value of type TEXT
Explanation
An INSTALL statement for a DDE_EVENT HANDLER specified that the
given function was to handle a REQUEST_DATA event. The handler for
this event must return a value of type TEXT, but the function named was
declared or defined to have a different return value type.
Correction
Make sure that the statement refers to the correct event-handler function
and that this function correctly interprets a REQUEST_DATA event.
Error Messages
347
–14249
Explanation
An INSTALL statement for a DDE_EVENT HANDLER indicated that the
specified function was to handle a TERMINATE_LINK or
TERMINATE_HOT_LINK event. The handler for this event must return
no value; its type should be VOID, but the function named was declared
or defined to have a different return value type.
Correction
Make sure that the statement refers to the correct event-handler function
and that this function correctly interprets the TERMINATE_LINK or
TERMINATE_HOT_LINK event.
–14250
Explanation
Correction
–14251
Explanation
Correction
–14252
Explanation
Correction
–14253
Explanation
Correction
348
Incorrect function return type
DDE_EVENT handler function for TERMINATE_LINK or
TERMINATE_HOT_LINK must return no value (return type should
be VOID)
Invalid object reference data class,
term on left must be SCALAR, LIST, or MATRIX.
The object reference is pointing to a form or object instead of a variable.
Make sure that the object reference points to a variable.
Invalid reference.
Cannot refer to object_ref –> THIS_INSTANCE
or object_ref –> PREV_INSTANCE.
Contained in the message.
Remove the references to THIS_INSTANCE and PREF_INSTANCE.
Invalid reference.
Cannot refer to object_ref –> form:variable.
Contained in the message.
Remove the “form_name:” from the reference.
Invalid object reference data type,
term on left must be of type OBJECT_REF.
Contained in the message.
Make sure that the term on the left is of object type OBJECT_REF.
Error Messages
–14254
Explanation
Correction
–14255
Check field identification. FOR operand is OBJECT_REF of field in
Unify 4GL, was name of field in ACCELL/SQL.
This is a compatibility warning message. A DISPLAY statement’s FOR
clause refers to a field name. If this is an ACCELL/SQL application being
converted, the reference is probably incorrect. ACCELL/SQL required the
name of the field, while Unify 4GL requires an OBJECT_ID value, which
is an OBJECT_REF. The DISPLAY statement will probably fail when the
application executes.
Change FOR field_name to FOR field_name: OBJECT_ID.
Preprocessor command line too long.
DOS limits command lines to at most 127 characters,
vcpl needs to generate a longer command for the preprocessor
(CPP.EXE). Possible bypasses:
1. Force use of a log file with a shorter path.
2. Move the application or library to a project
with a shorter DOS pathname.
3. Reduce the number of –I options
(merge .h files into fewer directories).
4. Reduce the number of –D options.
Explanation
Correction
–14256
Contained in the message.
Follow the instructions in the message.
Display variables may not have event sections.
Explanation
The compiler found a system information field while parsing a FIELD
section. System information fields (such as zoom_indicator and
record_state) are not permitted as field names in a FIELD section.
Correction
Find the FIELD section that has the system information field name, and
rewrite the section to use a developer-defined field name.
Error Messages
349
–14257
Explanation
Correction
–14259
Explanation
Duplicate AUD_ACTION attribute value specified
New value ignored.
The compiler found more than one instance of an AUD_ACTION
command attribute in a COMMAND section. Only one occurrence of an
AUD_ACTION command attribute is permitted in a COMMAND section.
Find the COMMAND section that has the multiple AUD_ACTION
command attributes and remove all but one of the AUD_ACTION
command attributes.
Duplicate definition of this field.
Field names must be unique within their form.
A FIELD section in the script uses a field name that has already been
defined in a prior FIELD section. Field names must be unique. The error
report points out the duplicate field name. For example, in a form that
contains two FIELD sections that each say FIELD foo, the second gets
this report:
vcpl error, line 8:
Duplicate definition of this field
Field names must be unique within their form
\___/
FIELD foo
Correction
–14260
350
Change the name of one of the fields to assure that field names are
unique. If both FIELD definitions were intended to refer to the same
field, delete one and move any field-level event sections that followed it
to the part of the script that follows the first FIELD definition.
Duplicate FIND_ACTION attribute value specified. New value
ignored.
Explanation
The compiler found more than one instance of a FIND_ACTION
command attribute in a COMMAND section. Only one occurrence of a
FIND_ACTION command attribute is permitted in a COMMAND section.
Correction
Find the COMMAND section with the multiple FIND_ACTION command
attributes and remove all but one of the FIND_ACTION command
attributes.
Error Messages
–14261
Explanation
Correction
Option is specified more than once.
Will use rightmost instance, ignore prior instances.
The vcpl command line contained more than one instance of an option
that can occur only once. Only the -I and -D options can have multiple
occurrences. This is a warning message. vcpl will proceed as if only the
last (rightmost) instance of the option had been used.
Remove the extra option definition from the command line.
–14262
Duplicate section, At most one section of this type may occur in a
form script.
Explanation
The compiler found an event section that has already been processed.
Each event section can occur only once in a stored procedure file.
Correction
–14263
Explanation
Correction
–14264
Find the duplicate event section and determine which section to delete.
Environment variable is undefined.
Unable to substitute for this variable in a command line option.
Contained in the message.
Define variable_name in the environment and retype the command line.
EXECUTING clause in incorrect context.
Can only be used with a ROW_VALUED stored procedure.
Explanation
An EXECUTING block can be used as part of a SET statement only if the
stored procedure called by the SET statement is ROW_VALUED.
NUMERIC stored procedures cannot be used with an EXECUTING
block.
Correction
Make sure that the referenced stored procedure is correctly defined in the
EXTERN statement. Remove the EXECUTING block if the stored
procedure is correctly defined as NUMERIC. Otherwise, redefine the
procedure as ROW VALUED.
Error Messages
351
–14266
Explanation
Expected ’archive_name’.
vcpl command contained a -library argument, but the next argument is
another option identification (-option), instead of the name of a library
file.
Correction
–14267
Explanation
Correction
–14268
Explanation
Correction
–14269
352
Include a library name in the vcpl command line.
Expected CASE or DEFAULT keyword.
The compiler expected the next token to be either the CASE or DEFAULT
keyword. Either the CASE or DEFAULT keyword must follow the BEGIN
keyword in the SWITCH statement.
Find the SWITCH statement that is missing the CASE and DEFAULT
keywords, and rewrite the statement to use one of them. See Unify
DataServer: SQL/A Reference for the syntax and usage of the SWITCH
statement.
Expected a consistency keyword: SET_CONSISTENCY,
RECORD_CONSISTENCY or NO_CONSISTENCY.
The compiler expected the next token to be the SET_CONSISTENCY,
RECORD_CONSISTENCY, or NO_CONSISTENCY keyword, after the
keyword TX in the CONTINUE TX or START TX consistency level
clauses of a ON CHOOSE NEXT FORM statement.
Find the ON CHOOSE NEXT FORM statement that is missing the
SET_CONSISTENCY, RECORD_CONSISTENCY, or
NO_CONSISTENCY keyword in the consistency level clause. If the
transaction level is either CONTINUE TX or START TX, the consistency
keyword must be SET_CONSISTENCY, RECORD_CONSISTENCY, or
NO_CONSISTENCY.
Expected function name for a HANDLER,
either DBMS_ERROR or DDE_EVENT.
Explanation
The compiler expected the next word to be the name of a DBMS
error-handler function or DDE event-handler function. These functions
must be declared in the EXTERN statement before being referenced. The
function name is required in the INSTALL statement.
Correction
Find the INSTALL statement that is missing the function name and
rewrite the statement or rewrite the EXTERN declaration if that is wrong.
Error Messages
–14270
Explanation
Correction
–14271
Expected variable or attribute as “–>” operand,
trying to locate object or attribute through an OBJECT_REF.
Contained in the message.
Make sure that the dereference operator operand is a variable or attribute.
Expected a display location.
This should be either FYI_MESSAGE or an OBJECT_REF
referring to a screen field.
Explanation
The compiler expected the next token to be a display location: either a
screen field name or the FYI_MESSAGE keyword. The display location
must follow the FOR keyword in the DISPLAY statement.
Correction
Find the DISPLAY statement that is missing the display location, and
rewrite the statement. Omit the FOR clause or follow the FOR keyword
with either a field name or the FYI_MESSAGE keyword.
–14272
Expected something else following $ (dollar sign).
$ is a prefix for either an identifier or an amount constant.
The character immediately following this $ is neither an alphabetic
character (start of an identifier) nor a numeric digit (start of an
amount constant).
Explanation
Correction
–14273
Explanation
Correction
Error Messages
Contained in the message.
Make sure that the dollar sign is followed by an identifier name or an
amount constant.
Expected an expression.
When setting a clear-to-find expression, the right side of the assignment
must be an expression.
Add an expression to the clear-to-find expression setting.
353
–14274
Explanation
Correction
–14275
Explanation
Expected a form choice option.
Should begin with [NEW] CHILD FORM.
A CREATE FORM, CHOOSE FORM, or ENABLE ZOOM statement
expected a form choice option clause to identify a form instance. This
clause should begin with [NEW] CHILD FORM, but those keywords are
not present.
Find the statement that is missing the form choice options and add the
option.
Expected FORM, NEXT FORM, or PREVIOUS FORM keywords.
The compiler expected the next token to be the FORM keyword. The
FORM keyword is required in these locations:
after the NEXT keyword in an ON CHOOSE NEXT FORM section
after the CREATE keyword in a CREATE FORM section
after the DISMISS keyword in an ON DISMISS FORM section or
in a DISMISS FORM statement
after the CANCEL keyword in an ON CANCEL FORM section or
in a CANCEL FORM statement
after the CHOOSE keyword in an CHOOSE FORM USING
statement
Correction
–14276
Explanation
Correction
354
Find the stored procedure statement or section that is missing the FORM
keyword, and rewrite the section.
Expected object_ref-valued expression to identify a form.
The ACTIVE_FORM clause of a CHOOSE FORM USING statement
expects an OBJECT_REF-valued expression that evaluates to the
OBJECT_ID of an active form. The tokens that follow the
ACTIVE_FORM keyword do not represent an OBJECT_REF-valued
expression.
Find the CHOOSE FORM USING statement and correct the
OBJECT_REF-valued expression.
Error Messages
–14277
Explanation
Expected event section name beginning with ON.
The compiler found the ON keyword where a form-level event section
was expected, but the ON was not followed by a valid event section
keyword. The ON keyword is the first word in these event sections:
ON CANCEL FORM
ON CHOOSE NEXT FORM
ON CREATE
ON CLEAR TO ADD
ON CLEAR TO FIND
ON CURRENT
ON DESTROY
ON DISMISS FORM
ON DOUBLE CLICK
ON EXIT
Correction
–14278
ON FIND
ON MESSAGE
ON NEW CHILD
ON NEXT FORM
ON NEXT RECORD
ON NOT CURRENT
ON PREVIOUS FORM
ON PREVIOUS RECORD
ON RETURN VALUES
ON ZOOM
Find the ON keyword in question and make sure that it is followed by a
valid keyword.
Expected a function name.
Explanation
Syntax of the form name( suggests that this should be the start of a call to
the named function. However, that name is neither declared nor defined
as a function.
Correction
Find the function call and make sure that the function has been declared
correctly in the EXTERN statement. For the syntax for the EXTERN
statement and the FUNCTION clause, see Unify DataServer: SQL/A
Reference.
–14279
Explanation
Expected a handler type: DBMS_ERROR or DDE_EVENT
An INSTALL statement or a DEINSTALL ALL statement must contain a
DBMS_ERROR keyword or a DDE_EVENT keyword to identify the type
of handler to be installed or the type of handlers to be deinstalled. The
source did not include one of these keywords following the INSTALL or
DEINSTALL ALL keywords.
Correction
Error Messages
Find the INSTALL statement or DEINSTALL statement that omitted or
misspelled the DBMS_ERROR or DDE_EVENT keyword and correct the
statement.
355
–14280
Explanation
Correction
–14281
Explanation
Expected “ (double quote) at end of identifier.
An identifier preceded by “ (double quote) to indicate that it is a
variable name, not a 4GL keyword, should be followed by a matching
“ (double quote) character.
Contained in the message.
Add a closing quotation mark to the identifier name used as a variable
name.
Expected IS UNDEFINED keywords.
The compiler expected to find the keywords IS UNDEFINED instead of =
UNDEFINED.
Correction
Find the string = UNDEFINED and replace it with the string IS
UNDEFINED.
–14282
Explanation
Expected a justification specification (LEFT, RIGHT, CENTERED).
The compiler expected the next token to be a justification specification:
LEFT, RIGHT, CENTERED, or a string. A justification specification
follows the DISPLAY_JUSTIFY keyword in the DISPLAY statement.
Correction
–14283
356
Find the DISPLAY statement that has the incorrect DISPLAY_JUSTIFY
clause. Omit the DISPLAY_JUSTIFY clause or add a valid justification
specification.
Expected keyword.
Explanation
The compiler expected a keyword in the current context, but did not find
it.
Correction
Find the statement that is missing a keyword and insert the keyword. For
the syntax for all statements, see Unify DataServer: SQL/A Reference.
Error Messages
–14284
Explanation
Correction
–14285
Explanation
Expected a ”[” (left bracket).
Either an array definition or reference is being used where a left bracket
is expected. In an array definition, if the LIST or MATRIX keyword is
used before an identifier, the compiler expects the array dimensions after
the identifier. Array references, in most cases, need subscripts enclosed in
brackets after the array identifier.
Enclose the array dimensions or array subscripts in brackets.
Expected a ”(” (left parenthesis).
The compiler expected a left parenthesis, “(”, in a stored procedure
statement. The left parenthesis is required in these locations:
after the keyword FOR in a FOR statement
after the function name or stored procedure name and before any
arguments in a function call or stored procedure call (The
parentheses are required even if the function or stored procedure
has no arguments.)
after the function name and before any function parameters in a
FUNCTION statement. (The parentheses are required even if the
function has no parameters.)
Correction
–14286
Explanation
Find the stored procedure statement that is missing the parenthesis and
rewrite the statement. See Unify DataServer: SQL/A Reference for the
syntax and usage of stored procedure statements and sections.
Expected LIST or MATRIX keyword.
An array definition in a LOCAL clause is missing the required LIST or
MATRIX keyword.
Correction
When you define an array in a LOCAL clause, precede the array name by
the array type, LIST or MATRIX, as shown in this example:
LOCAL LIST array_list[1 TO 10],
MATRIX array_matrix[1 TO 10, 1 TO 10]
function_name:attribute_name
Error Messages
357
–14288
Explanation
Correction
–14289
Explanation
Correction
–14290
Explanation
A function call to a local or global function that takes a matrix reference
parameter is being passed something other than a matrix. Individual array
cells may not be passed as reference parameters.
Replace the parameter with a matrix array reference or change the
parameter type in the function declaration.
Expected start of a form or global function definition.
The compiler could not find a valid statement at the beginning of the
stored procedure text. An external declaration must appear in the
EXTERN and FUNCTION statements.
Start the stored procedure text with an external declaration (the EXTERN
and FUNCTION statements). See Unify DataServer: SQL/A Reference for
the syntax and usage of stored procedure statements.
Expected a numeric constant.
The current context (for example, defining array bounds) requires a
numeric constant, but none was found.
Correction
Find the statement or array reference that is missing the numeric constant
and correct it. For information about defining arrays, see the LOCAL
clause description in Unify DataServer: SQL/A Reference.
–14291
Expected identifier following “ (double quote).
Enclosing an identifier in double quotes means that the identifier
is used as a variable name, even if it matches a 4GL keyword.
However, the first character after this double quote is not alphabetic,
and therefore cannot be the start of a variable name.
Explanation
Correction
358
Expected a MATRIX name.
Contained in the message.
Either remove the quotation mark or make sure that an identifier name
follows the quotation mark.
Error Messages
–14292
Explanation
Expected RECORD or OPERATION keyword.
The compiler expected the next token to be the RECORD keyword or
OPERATION keyword. The RECORD keyword is required in these
locations:
after the CURRENT keyword in the DELETE CURRENT
RECORD statement
after the CURRENT keyword in the UPDATE CURRENT
RECORD statement
after the REJECT keyword in the REJECT RECORD statement
after the NEXT keyword in the ON NEXT RECORD section
The OPERATION keyword is required in the REJECT OPERATION
statement.
Correction
–14293
Explanation
Correction
–14294
Find and correct the statement that is missing the RECORD or
OPERATION keyword.
Expected RECORD keyword.
The current input appears to be the beginning of an ON NEXT RECORD
or ON NEXT FORM section, but RECORD does not follow the ON NEXT
keywords.
Find the statement that is missing the RECORD keyword and add the
keyword.
Expected a REFERENCE parameter.
Explanation
A function call to a function that takes a reference parameter is being
passed an invalid object as a reference parameter. Scalar (non-array) or
array variables can be passed to local or global functions as reference
parameters. Individual array cells cannot be passed as reference
parameters.
Correction
Replace the invalid reference parameter. If the reference parameter is an
array cell, change the function to receive an array reference parameter
and pass the entire array.
Error Messages
359
–14295
Explanation
Correction
–14296
Explanation
Correction
–14297
Explanation
Expected a RESULT parameter.
The compiler found a function or stored procedure call that contains a
constant argument where the compiler expected a variable. The compiler
builds a table that contains information about all functions and stored
procedures. This information also indicates whether each parameter was
declared as a RESULT parameter. A RESULT parameter requires a
variable as an argument.
Find the stored procedure statement that contains the function or stored
procedure call that contains the incorrect argument. Make sure that you
are using the correct function or stored procedure name and the
appropriate argument for each parameter. Use a variable for a RESULT
parameter and a constant or variable for a non-RESULT parameter.
Expected a ”]” (right bracket).
An array reference or definition has a left bracket, but no closing right
bracket.
Close the array reference or definition with a right bracket.
Expected a ”)” (right parenthesis).
The compiler expected a right parenthesis, “)”, in a stored procedure
statement or section. The right parenthesis is required in these locations:
after the last expression to be evaluated in a FOR statement
after the arguments in a function call or stored procedure call (The
parentheses are required even if the function or stored procedure
has no arguments.)
after the function parameters in a FUNCTION statement (The
parentheses are required even if the function has no parameters.)
at the end of an expression that is introduced by a left parenthesis,
“(”
Correction
360
Find the stored procedure statement that is missing the right parenthesis,
and rewrite the statement. See Unify DataServer: SQL/A Reference for the
syntax and usage of stored procedure statements and sections.
Error Messages
–14298
Expected a ROW_VALUED stored procedure.
Explanation
A SET statement makes an assignment to a list of variables. This makes
sense only if the TO clause refers to a ROW_VALUED stored procedure.
However, the TO clause operand is not a ROW_VALUED stored
procedure.
Correction
Find the SET statement that contains the problem TO clause and correct
the operand.
–14299
Expected number of seconds for timer event.
Explanation
The compiler expected the next word to be a valid floating point
expression for the number of seconds. The expression is required after
the IN keyword in the CREATE TIMER EVENT statement.
Correction
Find the CREATE TIMER EVENT statement and rewrite it with a valid
floating point expression for the number of seconds.
–14300
Explanation
Expected a ”;” (semicolon).
The compiler expected a semicolon (“;”) in a stored procedure statement.
The semicolon is required in these locations:
at the end of DBMS SQL statements that are not in a BEGIN SQL
. . . END SQL statement block.
at the end of the DELETE SELECTED ROW, SLOCK, UNLOCK,
and XLOCK statements
after the expression to be evaluated once at the beginning of the
loop in a FOR statement (The semicolon is required even if no
expression is specified.)
after the expression to be evaluated at the beginning of each loop
iteration in a FOR statement (The semicolon is required even if no
expression is specified.)
Correction
Error Messages
Find the stored procedure statement that is missing the semicolon and
rewrite the statement. See Unify DataServer: SQL/A Reference for the
syntax and usage of the DELETE SELECTED ROW, FOR, SLOCK,
UNLOCK, and XLOCK statements.
361
–14301
Expected a Unify 4GL statement.
Explanation
The compiler expected the next token to be the start of a new stored
procedure statement. This error can occur in control flow statements
(FOR, IF, REPEAT, WHILE, and SWITCH), when the statement being
controlled by the control flow statement is not specified.
Correction
Find the stored procedure control statement with the missing statement
and be sure to specify the statement under control of the control flow
statement. See Unify DataServer: SQL/A Reference for the syntax and
usage of the stored procedure control statements.
–14302
Wrong data type, expected a string.
Explanation
The syntax requires a string, but the actual script used a non-string
constant.
Correction
Supply an appropriate string constant or an expression that will be
string-valued when the stored procedure is executed.
–14303
Explanation
Expected a subexpression with at most a unary operator.
An expression contains a *, /, or % operator (multiply, divide, or
modulo). This suggests an operation such as a * b, where a and b usually
are variables or constants. In fact they can be subexpressions optionally
prefixed by a unary operator.
This error indicates that the stored procedure did not have a token
following the *, /, or % operator that can represent a valid subexpression
in this context.
Correction
362
Examine the stored procedure for typographical errors, and make sure
that the operand of a multiply, divide, or modulo represents a numeric
subexpression.
Error Messages
–14305
Explanation
Expected a table name.
The compiler expected the next token to be a table name. A table name is
required after an SLOCK, XLOCK, or UNLOCK keyword in a lock
statement.
A table name can be specified in either the table_name or
schema.table_name format. The schema argument is the name of the
schema that contains the table.
Correction
–14304
Explanation
Correction
–14306
Find the stored procedure statement that is missing the table name, verify
the spelling of specified tables, and rewrite the statement. See Unify
DataServer: SQL/A Reference for the syntax and usage of stored
procedure statements.
Expected name of a table, or schema.table.
The table name specified should be a simple table name (table) or a
qualified table name (schema.table). The specified table name did not
match this requirement.
Find the table name specification in question and replace it with a valid
table name.
Expected function name for a timer handler.
Explanation
The compiler expected the next word to be the name of a timer function.
A timer function must be declared in the EXTERN SCRIPT TIMER
statement before being referenced. The timer function name is required in
the CREATE TIMER EVENT statement.
Correction
Find the CREATE TIMER EVENT statement that is missing the function
name and rewrite the statement or rewrite the EXTERN declaration if that
is wrong.
Error Messages
363
–14307
Explanation
Correction
Expected a Unify 4GL type.
The compiler expected the next token to be a valid type
keyword. This message is displayed when an invalid return type is
specified in a declaration for a function.
If the problem is in a function declaration, make sure that the return type
is specified by using one of the following keywords:
AMOUNT
BINARY
BOOL
DATE
–14308
Explanation
Correction
–14309
Explanation
FLOAT
NUMERIC
STRING
TEXT
TIME
VOID
Expected name of a variable.
The compiler expected the next token to be a variable name. This error
can occur wherever the grammar calls for a variable specification and
one is not found.
Find the stored procedure statement that has the missing or incorrect
variable name. See Unify DataServer: SQL/A Reference for the syntax and
usage of stored procedure statements.
Can’t recognize Unify 4GL syntax.
Compiler is confused, possibly due to a prior error
or a local function placed in the wrong context.
This error has several causes:
the omission of the comment terminator (*/)
an attempt to nest comments
Correction
–14310
Explanation
Correction
364
Examine the script for typographical errors and make sure that both
comment delimiters (/* and */) surround each comment.
Event section in wrong context.
Attempting to use a FIELD section as a FORM section.
One of the field-level sections (AFTER FIELD, BEFORE FIELD, INIT
FIELD, ON DOUBLE CLICK, ON FIELD, WHEN FIELD CHANGES)
did not follow a FIELD definition. These sections must be associated
with individual fields.
Supply the omitted FIELD definition.
Error Messages
–14311
Unable to create subprocess (fork) to run /lib/cpp.
Explanation
The UNIX operating system could not create a process. This is necessary
to run cpp.
Correction
Try to identify the limiting system resource. It may help to kill unneeded
processes (other applications).
–14312
Explanation
Correction
–14313
Explanation
Expected a form class name.
The compiler expected the next token to be a form name. A form name is
expected in the CHOOSE FORM USING statement, the CREATE FORM
statement, the DISABLE ZOOM TO statement, the ENABLE ZOOM TO
statement, the FORM section, and the ON CHOOSE NEXT FORM
section.
Find and correct the section or statement that is missing the form name.
Expected a form event section name.
The compiler expected the next token to identify an AFTER event or
BEFORE event section such as BEFORE FORM, AFTER ZOOM, and so
on. The second keyword must follow the AFTER keyword or BEFORE
keyword in one of the following event sections:
AFTER ADD
AFTER DELETE
AFTER FIELD
AFTER FIND
AFTER FORM RETURN
AFTER UPDATE
AFTER ZOOM
Correction
Error Messages
BEFORE ADD
BEFORE DELETE
BEFORE FIELD
BEFORE FIND
BEFORE FORM
BEFORE RECORD
BEFORE UPDATE
Find the AFTER or BEFORE section that is missing the second keyword,
and rewrite the section.
365
–14314
Explanation
Correction
–14315
Explanation
Correction
–14316
Explanation
Correction
Form name cannot begin with ”dbo.”
Form names use standard syntax for identifiers,
cannot contain ”.”. This name appears to have been generated
to match a SYBASE table name qualified by ”dbo” (”DataBase
Owner”);
Please remove the ”dbo.” prefix.
This compilation will proceed as if ”dbo.” had not been present.
Contained in the message.
Follow the instructions in the message.
Invalid character in form name.
Form names use standard syntax for identifiers,
using only alphanumeric characters and underscore.
The stored procedure contained an invalid character in a reference to a
form name.
Make sure that the form name reference contains no characters other than
alphanumeric characters and underscores.
Ambiguous compatibility feature set name.
Supply more characters to uniquely identify feature set.
Too few characters were entered as the initial substring of a feature set
name to uniquely identify the option. For example, a can refer to either
all or app or attrs.
Use additional characters to represent a unique initial substring of the
feature set name.
array_name[ ]
array_name[array_name:ROW_INDEX, array_name:COL_INDEX]
–14317
366
Unrecognized compatibility feature set.
Explanation
The vcpl command line included an -accept, -warn, or -reject argument
followed by a name that does not match any compatibility feature set
argument.
Correction
Make sure that the -accept, -warn, or -reject argument is followed by a
valid compatibility feature set argument.
Error Messages
–14318
Invalid external function language name. Expected SCRIPT, C, or
STORED.
Explanation
The compiler expected the next token to be the C, SCRIPT, or STORED
keyword. One of these function type keywords must follow the EXTERN
keyword in a developer-defined function declaration.
Correction
Find the EXTERN statement at the beginning of the script file and make
sure the function type is C for C functions, SCRIPT for stored procedure
functions, or STORED for stored procedures. See Unify DataServer:
SQL/A Reference for the syntax and usage of the EXTERN statement.
–14319
Explanation
Correction
–14320
Explanation
Correction
–14321
Type cannot be specified in a function’s local clause.
A data type was found in the LOCAL clause of a local or global function,
which is invalid.
Find the problem LOCAL clause, and correct the error.
Trying to call a message handler as a function.
Use SEND MESSAGE instead.
A function call used a message name as the function name.
Contained in the message.
Attempting to redeclare function.
Explanation
The compiler found a declaration for a function or stored procedure that
has already been declared in the script. The function or stored procedure
can be declared only once in the script.
Correction
Find the EXTERN statement with the duplicate declaration and delete it.
See Unify DataServer: SQL/A Reference for the syntax and usage of the
EXTERN statement.
–14322
Explanation
Correction
Error Messages
DDL commands do not accept Unify 4GL objects.
objects, such as variables and functions, cannot be used in the
text of an SQL DDL command. These are example DDL commands:
GRANT, REVOKE, CREATE, DROP, and ALTER.
Rewrite the DDL statement so that it contains no objects.
367
–14323
Illegal command on non-updatable table or view.
Explanation
The UPDATE SELECTED ROW and DELETE SELECTED ROW
commands can be used only to modify tables that can be updated,. In the
SET . . . SELECT statement that contains the EXECUTING block with
the UPDATE SELECTED ROW or DELETE SELECTED ROW statement,
either the table specified cannot be updated or several tables are specified
in the FROM clause.
Correction
If a single table is specified in the SELECT statement, verify that the
permissions on the table allow the current user to perform updates and/or
deletes. If several tables are listed in the FROM clause, write separate
SQL UPDATE or DELETE statements to modify the individual tables.
If a view is specified in the FROM clause and that view is built from
several base tables, then separate SQL UPDATE or DELETE statements
must be written for each of the base tables.
–14324
Illegal character in Unify 4GL source, ignored.
Explanation
The script file contains an ASCII character that the compiler could not
interpret.
Correction
Search the script file for invalid or non-printable ASCII characters and
remove them.
–14325
Explanation
Operation cannot be performed on this command.
The compiler found a command name that poses one of these problems:
The command name appears after the COMMAND keyword in a
COMMAND statement, but the command cannot be set.
The command name appears after the QUEUE COMMAND
keyword in a QUEUE COMMAND statement, but the command
cannot be queued.
Correction
368
Find the COMMAND or the QUEUE COMMAND statement that has the
problem command name and rewrite the statement using a valid
command name.
Error Messages
–14326
Explanation
Correction
–14327
Explanation
Correction
A target attribute is not allowed.
The compiler found a target variable attribute in a variable name, but this
variable is not a target or target field variable.
Find the stored procedure statement that contains the incorrect target
attribute. Either correct the variable name or change the attribute name.
Unable to open file for input.
The compiler tried to open the file named input_file_name and failed.
This error occurs if the compiler could not open the script file to be
compiled.
Take these actions:
Make sure that you have write and execute permission on the
current directory.
Make sure you have read and write permission on the file being
opened.
Make sure that the operating system has enough resources (open
file descriptors and inodes) to open a file.
–14328
Explanation
Correction
–14329
Explanation
Correction
Error Messages
Invalid array reference.
The stored procedure contains an array reference that is missing required
subscripts; for example, a stored procedure tries to pass an array without
subscripts to a function as a value or result parameter.
If the intent was to reference an entire array, try using a FOR loop that
references each cell of the array.
Invalid value for CONSISTENCY attribute.
Use RECORD, SET, or NONE.
A CONSISTENCY IS clause must have an operand of RECORD, SET, or
NONE. The operand was something else.
Use only RECORD, SET, or NONE.
369
–14330
Invalid number of dimensions.
Explanation
The number of dimensions specified in an array reference or definition
do not match the number of array dimensions specified in a FIELD
[LIST | MATRIX] statement.
Correction
Modify the FIELD [LIST | MATRIX] statement or the array reference or
definition so that the two specify the same number of dimensions.
–14331
Explanation
Correction
–14332
Explanation
Correction
Invalid array dimension type.
When you define an array in a LOCAL clause, the array dimension
expressions must be of numeric type.
Find the LOCAL clause that has the invalid dimension expression and
change it to a numeric expression.
The keyword NULL is not permitted in this context.
The compiler found the NULL constant as an operand in an arithmetic,
relational, logical, or bitwise operation.
Find the expression that contains the NULL keyword, and remove the
NULL keyword.
–14334
Explanation
A CHOOSE FORM, CREATE FORM, or ENABLE ZOOM statement
contains a TRANSACTION IS clause with an operand that is not
COMMIT or CONTINUE. These are the only legal values for
TRANSACTION.
Correction
Find the problem TRANSACTION IS clause and make sure that the
operand is either COMMIT or CONTINUE.
–14335
Explanation
Correction
370
Invalid value for TRANSACTION attribute.
Use COMMIT or CONTINUE
DBMS_ERROR functions cannot be local.
A DBMS_ERROR function definition appears as a local function, but
DBMS_ERROR functions must be global.
Define the function as a global function in a separate script.
Error Messages
–14336
Timer functions cannot be local.
Explanation
The compiler found a timer event handler function that was declared as a
local function; it must be declared as a global function. The name of a
global timer function must follow the USING TIMER HANDLER clause
of the CREATE TIMER EVENT statement.
Correction
Declare the timer function globally with an EXTERN statement before it
is referenced in a script.
–14337
Explanation
Correction
–14338
Explanation
Correction
–14339
Explanation
Expected either KEY or VALUES keyword.
The presence of a RETURN keyword in the current context indicates the
start of a RETURN KEY or RETURN VALUES clause. However, the
token that follows RETURN is neither KEY nor VALUES.
Use only KEY or VALUES in this context.
Unexpected keyword.
If this is the name of a variable, field, or other object,
use $ prefix or surrounding quotes ($name or ”name”)
to identify it without ambiguity.
A keyword appears in a context where it was not expected.
Follow the instructions in the message.
Didn’t expect ”[” (left bracket).
An array reference was followed by a colon and another array reference,
for example:
SET array_name[1]:array_name[2] TO 1
This syntax is not allowed by the compiler.
Correction
Error Messages
Change the statement to use valid array reference syntax.
371
–14340
Explanation
Correction
–14341
Form name mismatch.
Name in script differs from name in directory of library library.
This warning indicates that the FORM CLASS statement in the script
specifies a form name other than the one used in the application or library
directory.
Either rename the form in its application or library, or change the form
name in the FORM CLASS statement.
Function name mismatch.
Name in script differs from name in directory of library library.
Explanation
This warning indicates that the FUNCTION definition in a function gives
a function name other than the one used in the database directory.
Correction
Either rename the function in database directory or change the form name
in the FUNCTION statement.
–14342
LOCAL declaration in wrong context.
Definitions of local functions and local variables must follow the
FUNCTION prototype declaration of a global function.
Explanation
Correction
372
A function or variable list that is explicitly defined as LOCAL is at the
beginning of a function. Such definitions must follow the FUNCTION
definition for a stored procedure.
Make sure that the LOCAL declaration follows the FUNCTION definition
for a stored procedure.
Error Messages
–14343
–14344
–14345
–14346
–14347
–14348
–14349
–14350
Explanation
Correction
–14352
Compiler logic error.
Couldn’t find attribute name to match internal attribute code.
Compiler logic error.
Cursor command counter, always positive, incremented to 0.
Compiler logic error. cslctinf( ) returned FALSE.
Compiler logic error. Impossible case for ENDSQL_OPR operand.
Compiler logic error.
Can’t identify token found in set sscode1, to identify a field-level
event section.
Compiler logic error.
Impossible case in field-level section identification.
Compiler logic error.
Impossible case for JMPABS_OPR operand.
Compiler logic error.
Can’t identify a specific token that’s already classified as a
loop-statement token.
These errors should not normally occur.
If any of these errors occurs, please contact Unify Customer Support.
Compiler logic error. Couldn’t find function.
Explanation
The compiler found an undefined function. The compiler builds a table
that contains information about all developer-defined functions. This
error occurs if the compiler cannot find an entry in this table for a
function that was called from a stored procedure statement.
Correction
Find the stored procedure statement that contains the undefined function
name. Make sure that the function is defined and declared, that it is
spelled the same way it was defined, and that it is linked into the
application.
Error Messages
373
–14351
–14353
–14354
–14355
–14356
–14357
–14358
–14359
–14362
–14363
–14364
–14365
–14366
–14367
Compiler logic error.
Attempting to unget current token while next token is prefetched,
will lose next token.
Compiler logic error. Unknown operator code in parse tree.
Compiler logic error. Unknown event section id given for new parse
tree node.
Compiler logic error.
Statement identified as a lock statement but first token isn’t XLOCK,
SLOCK or UNLOCK.
Explanation
These errors should not occur in the normal compiling of a stored
procedure.
Correction
If any of these errors occurs, please call Unify Customer Support.
–14368
Explanation
Correction
374
Compiler logic error. Unknown node type in parse tree, found in
trwalk( ).
Compiler logic error.
Trying to check attribute compatibility with nonexistent symbol.
Compiler logic error.
Command name marked as obsolete in command table, not
recognized as obsolete in parsing logic.
Compiler logic error.
Invalid value for oldCode (–o switch setting).
Compiler logic error. Invalid operand type in parse tree.
Compiler logic error. poslstck( ) returned FALSE.
Compiler logic error.
Current tokens must be SELECTED ROW, but aren’t.
Compiler logic error. Internal error in SRCF_ENT list.
Compiler logic error. Lookup of system function failed.
Compiler logic error.
Token not expected in code but expected in a token-set definition.
CONTINUE statement isn’t within a loop.
Contained in the message.
Find the misplaced CONTINUE statement and make sure that it is in a
loop.
Error Messages
–14369
Explanation
Correction
–14370
Explanation
Correction
–14372
Explanation
Correction
–14374
Explanation
Correction
Error Messages
Number of user functions exceeds maximum allowed.
The stored procedure contains too many developer-defined functions. A
single stored procedure can include up to 1,000 developer-defined
functions.
Reduce the number of functions in the stored procedure.
Exceeded maximum allowed nesting level.
The compiler found control statements nested more than eight levels
deep. As the compiler processes control statements in which nesting can
occur (FOR, IF, REPEAT, SWITCH, WHILE), it keeps track of the
nesting level.
Find the stored procedure control statements that are nested for more than
eight levels and rewrite the statements to reduce the number of nesting
levels. See Unify DataServer: SQL/A Reference for the syntax and usage
of the stored procedure control statements.
Trying to call a function as a message handler.
Use standard function call syntax instead.
A SEND MESSAGE statement used a function name as the message
name. This is illegal because message handlers and functions have
different internal linkage.
Use the standard function call syntax to call the function.
Message parameters conflict with prior declaration.
Compare EXTERN MESSAGE_HANDLER with ON MESSAGE section.
An ON MESSAGE section (message handler definition) gives a different
number of parameters or a different type for at least one parameter than
was specified in a prior EXTERN declaration for this message handler.
Find the ON MESSAGE section and change the incorrect definition of
formal parameters.
375
–14375
Message name conflict
A prior declaration or definition identifies function_name as the name
of a function, not a message handler; Check for a typo or inadvertent
use of a function name
Explanation
A message name in an EXTERN declaration or a message handler
definition is the same as a name that was previously declared or defined
as a global or local function. For example, this message is generated for
an ON MESSAGE section if the message_name in ON MESSAGE
message_name is an existing function name.
Correction
Find all function declarations or definitions that have the same name and
change the names to make them unique.
–14376
Explanation
Correction
–14377
Explanation
Return value type conflicts with prior definition.
Compare EXTERN MESSAGE_HANDLER with ON MESSAGE section.
An ON MESSAGE section defined a different data type for the message
handler’s return value than was previously declared in an EXTERN
declaration.
Change either the EXTERN or the ON MESSAGE section to use the same
data type for the return value.
Mixed Unify VISION and ACCELL/SQL syntax.
Use all-old or all-new syntax within statement.
An ENABLE ZOOM statement mixes syntax that was formerly used by
ACCELL/SQL and now by Unify VISION. vcpl can compile either old
syntax or new, but it cannot compile a mixture of both.
Correction
–14378
Explanation
Correction
376
Modify the statement to use only Unify VISION syntax.
More than one DEFAULT button specified.
A DISPLAY NOTICE statement identifies more than one button label as
the default button. Only one button can be the default.
Delete the extra DEFAULT keywords.
Error Messages
–14379
Explanation
Correction
–14380
Explanation
Correction
–14381
Explanation
Correction
–14383
Explanation
Correction
Error Messages
Clear to Add/Find expressions cannot be used in nested set
statements.
Because clear to find and clear to add expressions are not evaluated until
the corresponding command is executed, CLEAR_FIND_EXP and
CLEAR_ADD_EXP attributes cannot be set in a nested SET statement.
Only simple SET statements can be used to set these attributes.
Divide the nested SET statement into several simple SET statements.
Using keyword new to Unify VISION.
Check for conflicting use as an identifier in old 4GL code.
This warning is displayed only when –warn attr is in effect. The script
contains a keyword that would have been an identifier, possibly a
variable, in ACCELL/SQL.
Verify the identifier usage. If appropriate, change the identifier name, use
a dollar sign prefix ($), or enclose the identifier name in double quotation
marks (”name”) to prevent vcpl from interpreting the identifier as a
keyword.
Expected a command name identifier.
A QUEUE COMMAND statement is expected to find an identifier naming
a command. Either the token in error is not an identifier, or it is an
identifier that names an object known not to be a command.
Find the invalid QUEUE COMMAND statement and make sure that it
contains a valid command identifier.
Expected a field name.
The compiler expected the next token to be the name of a field variable
or a target field variable. A field variable name or target field variable
name must be specified in a FIELD section.
Find the stored procedure statement or section that is missing the field
name. Also verify the use of variable names that are not field names.
Rewrite the statement or section. See Unify DataServer: SQL/A Reference
for the syntax and usage for stored procedure statements and sections.
377
–14384
Explanation
Correction
–14385
No FROM clause in SELECT statement.
The FROM clause is missing from a SELECT statement.
Add a FROM clause, with an appropriate table, to the SELECT statement
and recompile the script.
Name has not been declared as a FUNCTION.
Explanation
A name is used as a function name in an apparent function call, but no
function by that name has been declared or defined.
Correction
Make sure that you have not omitted an EXTERN declaration for this
function or have misspelled the function name.
–14386
Explanation
Correction
–14387
Explanation
Unable to access library.
Check to be sure that library name is correct
and that library permissions allow both read and write access.
The compiler was unable to open the library or application named on the
command line in order to compile a form, or a global function within that
library or application.
Make sure that the operand of the -application or -library argument is
spelled correctly on the command line.
Unable to allocate sufficient memory!
The compiler tried to allocate memory for its internal use and failed to
allocate the memory. An internal compiler function found the failed
memory allocation.
This error is not caused by a syntax error in your stored procedure.
Correction
Try one of the following solutions:
If the system did not have enough system memory or swap space
available when you executed the compiler, try executing the
compiler again. This situation can occur on heavily loaded
systems.
If the compiler ran out of memory on a large stored procedure
(over 1000 lines), try reducing the complexity of the stored
procedure. Create global stored procedure functions to perform
tasks that are repeated. If you still have memory allocation
problems, call Unify Customer Support.
378
Error Messages
–14388
Message-handler undefined.
Use EXTERN declaration at beginning of script.
Explanation
A SEND MESSAGE statement specifies a message name that does not
appear in an EXTERN declaration in this script. The declaration is
necessary to identify the types of parameters used in the message.
Correction
Add an EXTERN declaration for the message handler that services this
message.
–14389
Expected a message name identifier.
Explanation
A SEND MESSAGE statement requires an identifier that names a
message. Either the token in error is not an identifier, or it has not been
named in a previous message handler declaration or definition.
Correction
Declare the message handler in the EXTERN statement if the message
handler has not been declared, and correct any mistakes in the SEND
MESSAGE statement.
–14391
Explanation
Correction
–14392
Explanation
Correction
–14393
Required operand missing for option.
A vcpl command line argument that must be followed by a value was
followed instead by the start of another variable.
Retype the command line with the correct value.
Unable to access 4GL script in library.
The compiler was unable to obtain the function to be compiled from its
library.
Make sure that access to that function is not locked by another user.
Library does not contain 4GL script.
Explanation
The vcpl command line specified a form or global function (in a -form or
-function argument), and this name is not defined in the directory of the
library or application named in the -library or -application argument.
Correction
Make sure that all form and function names and directory path names are
correct in the vcpl command line.
Error Messages
379
–14394
Explanation
Correction
–14395
Explanation
Correction
–14396
Explanation
Correction
–14397
Explanation
No subscript supplied for an array reference.
An attempt was made to reference an array without subscripts when not
allowed, for example, attempting to pass an array without subscripts to a
function as a value or result parameter.
If the intent was to reference an entire array, try using a FOR loop that
references each cell of the array.
Identifier cannot be subscripted,
not previously declared as LIST or MATRIX.
A script uses a variable as a list or matrix, but did not declare it as such.
Make sure that the variable is declared and that the syntax is correct.
Subscripted attribute isn’t array-valued
An array subscript was used in an array reference where it is not needed
or valid. The array subscript is not valid when referencing the
DIMENSION array attribute. Subscripts cannot be used for variables that
have been used as scalar (non-array) variables in the script.
If the script references the DIMENSION array attribute, remove the
subscripts. If the script is referencing a scalar variable with array
attributes, the reference needs to be rewritten.
Assignment to non-data object. Assigning a value to objects such as
forms or commands would be meaningless.
The script contains a statement that tries to assign a value to a form
object or a command object. These object classes do not use a VALUE
attribute and cannot receive a data value.
For example, if do_update is a developer-defined command, then SET
do_duplicate TO TRUE produces this error. However, a reference to an
attribute used by commands is allowed, for example, SET do_update:
AUD_ACTION TO TRUE.
Correction
380
Correct the statement that tries to assign a value to a form object or
command object.
Error Messages
–14398
Explanation
Correction
–14399
Expected a button label (string expression).
A DISPLAY NOTICE statement contains a LABELS clause, which should
define one or more button labels as string-valued expressions. But a
token that can’t belong to a string expression was found instead.
Check for and fix editing errors and misunderstandings of the syntax.
Expected text to display in notice
(string constant or string-valued expression)
Explanation
The DISPLAY NOTICE statement requires a string-valued expression to
define the text to display in a notice box. The token following DISPLAY
NOTICE is not a string-valued expression.
Correction
Find the DISPLAY NOTICE statement that is missing the string-valued
expression and correct the statement.
–14400
Explanation
Correction
–14401
Attempting to set an unsettable attribute.
The script contains a statement that tries to set the value of an attribute
that is read-only.
Find the statement that tries to set a read-only attribute and either remove
the statement or change the attribute to one that can be set from a stored
procedure.
Too many program names (pipes) in the program list.
Explanation
The compiler found more than eight program names in the program list
of a CREATE PIPELINE statement. Up to eight program names are
allowed in a program list.
Correction
Find the CREATE PIPELINE statement, and rewrite the program list so
that no more than eight program names are listed.
Error Messages
381
–14402
Explanation
Correction
Statement must be within an executing block.
The UPDATE SELECTED ROW and DELETE SELECTED ROW
commands can be used only in the EXECUTING block of a SET . . .
SELECT statement.
To update or delete a record that was not retrieved by using a SET . . .
SELECT statement use the SQL UPDATE or DELETE statement. To
update or delete the current record in the selected set use the UPDATE
CURRENT RECORD or DELETE CURRENT RECORD command.
Use the UPDATE SELECTED ROW or DELETE SELECTED ROW
statement only to alter records that have first been selected by using a
SET . . . SELECT statement. The UPDATE SELECTED ROW or
DELETE SELECTED ROW statement must always be used in the
EXECUTING block in a SET . . . SELECT.
–14403
Explanation
Correction
–14404
Explanation
Correction
NULL or UNDEFINED unexpected.
The compiler expected either the NULL or UNDEFINED keyword to be
used as the rightmost operand of an IS or an IS NOT operator.
Find the IS or IS NOT operator that is missing the NULL or UNDEFINED
keyword, and replace the rightmost operand with either NULL or
UNDEFINED. For more information on the IS and IS NOT operators, see
Unify DataServer: SQL/A Reference.
No parameters in ON MESSAGE parameter list.
Compiling as if no USING clause is present.
Contained in the message.
Make sure that the compiler action is satisfactory. If it is not, correct the
ON MESSAGE parameter list to prevent the default compiler action.
382
Error Messages
–14405
Parameter mismatch, number of parameters in call doesn’t match
number in declaration or definition of function, or stored procedure.
Explanation
The compiler found a function or stored procedure call that contains a
different number of arguments from the number of parameters defined in
the function or stored procedure definition.
Correction
–14406
Explanation
Correction
–14407
Explanation
Correction
–14408
Explanation
Correction
Error Messages
Find the stored procedure statement that has the function or stored
procedure call with the incorrect number of arguments. Make sure that
you are using the correct function or stored procedure name and the
correct number of arguments in the function or stored procedure call.
The number of set variables and selected columns do not match.
The compiler found a SET statement and SELECT clause in which the
number of variables in the variable list does not match the number of
column names in the database column list.
Find the SET statement and SELECT clause in which the lists do not
match, and rewrite the statement. See Unify DataServer: SQL/A Reference
for the syntax and usage of the SET and SELECT statements.
Obsolete syntax, AFTER APPLICATION section.
Use 1st form’s ON DESTROY section for application cleanup.
Compatibility action: Compiling as ON DESTROY.
Contained in the message.
Follow the instructions in the message.
Obsolete syntax, APPLICATION header.
Unify VISION has no Master Application Form,
any form can be the first form of the application.
Compatibility action: Compiling as FORM CLASS header.
A stored procedure contains an ACCELL/SQL Release 2 APPLICATION
statement instead of a FORM CLASS statement.
Replace the APPLICATION statement with a FORM CLASS statement. If
either the –warn app or –accept app argument was used to start the
compiler, vcpl will compile the statement as the equivalent FORM
CLASS statement.
383
–14409
Explanation
Obsolete command attribute, ACTION.
Use AUD_ACTION and FIND_ACTION instead.
Compatibility action: None; this reference is in syntax that was not
used in ACCELL/SQL.
Contained in the message. This attribute would appear only in an
ACCELL/SQL DEFINE COMMAND or SET COMMAND statements.
Correction
–14410
Explanation
Correction
–14411
Explanation
Follow the instructions in the message.
Obsolete attribute, HELP_ARCHIVE.
Unify VISION uses a different Help system.
Compatibility action: Attribute value is always ’NONE’.
Contained in the message.
Remove all references to this attribute.
Obsolete command attribute, AUD_LABEL.
Set attributes of control object(s) invoking this command
Compatibility action: None; this reference is in syntax that was not
used in ACCELL/SQL.
Contained in the message. This attribute would appear only in an
ACCELL/SQL DEFINE COMMAND or SET COMMAND statements.
Correction
–14412
Explanation
Correction
384
Follow the instructions in the message.
Obsolete attribute, AUTO_ACCEPT.
Not applicable in GUI environment.
Compatibility action: Attribute value is always TRUE.
The ACCELL/SQL AUTO_ACCEPT attribute is not applicable to a
GUI-only environment.
Delete all references to AUTO_ACCEPT and modify any related logic as
needed.
Error Messages
–14413
Explanation
Correction
–14414
Explanation
Correction
–14415
–14416
–14417
–14418
–14419
Error Messages
Obsolete attribute, AUTO_COMMIT.
Use TX_MODE_ADD_RECORD, TX_MODE_DELETE_RECORD, and
TX_MODE_UPDATE_RECORD instead.
Compatibility action: Compiling as is, Manager will interpret as
equivalent accesses to TX_MODE_... attributes
Contained in the message.
Modify the script to use the equivalent TX_MODE_ . . . attributes.
Obsolete attribute, AUTO_EDIT.
Not applicable in GUI environment.
Compatibility action: Attribute value is always TRUE.
The ACCELL/SQL AUTO_EDIT attribute is not applicable to a GUI-only
environment.
Delete all references to AUTO_EDIT and modify any related logic as
needed.
Obsolete attribute, BLINK.
Change font or colors for highlighting.
Compatibility action: Compiling as is; Manager will substitute font
changes for BLINK attribute changes
Obsolete attribute, COL.
Use X in pixel coordinates instead of COL in character coordinates.
Compatibility action: None, unsupported in Unify VISION.
Obsolete attribute, COL_ORIGIN.
Use X in pixel coordinates instead of COL_ORIGIN in character
coordinates.
Compatibility action: None, unsupported in Unify VISION.
Obsolete attribute, CUR_FIELD.
Use CURRENT_FIELD_NAME, new name for same attribute.
Compatibility action: Compiling as CURRENT_FIELD_NAME.
Obsolete attribute, CUR_NEXT_FIELD.
Use CURRENT_NEXT_FIELD_NAME, new name for same attribute.
Compatibility action: Compiling as CURRENT_NEXT_FIELD_NAME.
385
–14420
–144121
–14422
–14424
–14425
–14426
–14427
–14429
–14430
–14431
–14432
–14433
–14434
386
Obsolete attribute, DATA_TYPE.
Use ACCELL_TYPE, new name for same attribute.
Compatibility action: Compiling as ACCELL_TYPE.
Obsolete attribute, DB_LENGTH.
Use DB_COLUMN_LENGTH, new name for same attribute.
Compatibility action: Compiling as DB_COLUMN_LENGTH.
Obsolete attribute, DB_TYPE.
Use DB_COLUMN_TYPE, new name for same attribute.
Compatibility action: Compiling as DB_COLUMN_TYPE.
Obsolete attribute, FIELD_NAME.
Use DB_COLUMN_NAME, new name for same attribute.
Compatibility action: Compiling as DB_COLUMN_NAME.
Obsolete command attribute, FIND_LABEL.
Set attributes of control object(s) invoking this command.
Compatibility action: None; this reference is in syntax
that was not used in ACCELL/SQL.
Obsolete attribute, FIRST_FIELD.
Use FIRST_FIELD_NAME, new name for same attribute.
Compatibility action: Compiling as FIRST_FIELD_NAME.
Obsolete attribute, FORM_NAME.
Use OBJECT_NAME or CLASS_NAME instead.
Compatibility action: Compiling as OBJECT_NAME.
Obsolete attribute, HELP_FORM coordinate.
Compatibility action: Attribute value is always 0.
Obsolete attribute, HELP_FORM_NAME.
Use HELP_TAG instead.
Compatibility action: Compiling as HELP_TAG.
Obsolete command attribute, Keys.
Set key bindings to commands in the Designer.
Compatibility action: None; this reference is in syntax that was not
used in ACCELL/SQL.
Obsolete command attribute, LABEL.
Set attributes of control object(s) invoking this command.
Compatibility action: None; this reference is in syntax that was not
used in ACCELL/SQL.
Obsolete attribute, LOW_INTENSITY.
Change font or colors for highlighting.
Compatibility action: Compiling as is; Manager will substitute font
changes for LOW_INTENSITY attribute changes.
Obsolete attribute, NEXT_FIELD.
Use NEXT_FIELD_NAME, new name for same attribute.
Compatibility action: Compiling as NEXT_FIELD_NAME.
Error Messages
–14435
–14436
Explanation
Correction
–14437
Explanation
Obsolete attribute, PREV_FIELD.
Use PREVIOUS_FIELD_NAME, new name for same attribute.
Compatibility action: Compiling as PREVIOUS_FIELD_NAME.
Obsolete attribute, PREV_FORM.
Use PREV_INSTANCE:OBJECT_NAME.
Compatibility action: Translating to
PREV_INSTANCE:OBJECT_NAME.
Contained in the message.
Follow the instructions in the message.
Obsolete attribute used as RESULT parameter.
Please substitute appropriate Unify VISION attribute.
Compatibility action: None, unable to handle this case automatically.
An ACCELL/SQL attribute that has no precise equivalent was used as a
RESULT parameter in a function call or a SEND MESSAGE statement.
vcpl can perform an appropriate translation in some cases, when an
obsolete attribute is used in a SET statement, but it cannot do this for a
RESULT parameter.
Correction
Modify the logic for both the function call and the function definition to
use the closest equivalent Unify 4GL attribute.
–14438
Obsolete attribute, REVERSE.
Change font or colors for highlighting.
Compatibility action: Compiling as is; Manager will
substitute font changes for REVERSE attribute changes.
Obsolete attribute, ROW.
Use Y in pixel coordinates instead of ROW in character coordinates.
Compatibility action: None, unsupported in Unify 4GL.
Obsolete attribute, ROW_ORIGIN.
Use Y in pixel coordinates instead of ROW_ORIGIN in character
coordinates.
Compatibility action: None, unsupported in Unify 4GL.
–14439
–14440
Error Messages
387
–14441
–14442
–14443
–14444
–14445
–14446
–14447
–14448
–14449
–14450
Explanation
Correction
388
Obsolete attribute, SELECTED_SET_SCROLLBAR.
Not supported in Unify 4GL.
Compatibility action: Compiling reference to ’NONE’ when getting
its value, ignoring assignment when setting its value.
Obsolete attribute, TARGET_FIELD.
Use DB_COLUMN_NAME, new name for same attribute.
Compatibility action: Compiling as DB_COLUMN_NAME.
Obsolete attribute, UNDERLINE.
Change font or colors for highlighting.
Compatibility action: Compiling as is; Manager will substitute font
changes for UNDERLINE attribute changes.
Obsolete attribute, USE_BASE_WINDOW.
Not supported in Unify 4GL.
Compatibility action: Compiling reference to TRUE when getting its
value, ignoring assignment when setting its value.
Obsolete attribute, WINDOW_HEIGHT.
Use HEIGHT in pixels instead of WINDOW_HEIGHT in character
rows.
Compatibility action: None, unsupported in Unify 4GL.
Obsolete attribute, WINDOW_WIDTH.
Use WIDTH in pixels instead of WINDOW_WIDTH in character
columns.
Compatibility action: None, unsupported in Unify 4GL.
Obsolete syntax, BEFORE APPLICATION section.
Use 1st form’s ON CREATE section for application initialization.
Compatibility action: Compiling as ON CREATE.
Obsolete syntax, BEFORE FORM section.
Use ON CREATE, new name for same section.
Compatibility action: Compiling as ON CREATE.
Obsolete syntax, CHOOSE FIRST FORM section.
Use ENTRY_POINT_CLASS_NAME Application attribute or
ON CHOOSE NEXT FORM section
Compatibility action: Compiling as ON CHOOSE NEXT FORM.
Obsolete syntax, CHOOSE NEXT FORM section.
Use ON CHOOSE NEXT FORM.
Compatibility action: Compiling as ON CHOOSE NEXT FORM.
Contained in the message.
Follow the instructions in the message.
Error Messages
–14451
Explanation
Correction
Obsolete syntax, ACTION clause.
Specify AUD_ACTION and FIND_ACTION individually.
Compatibility action: Compiling code to set both attributes.
Unify 4GL does not have a separate ACTION attribute for commands; the
referenced attribute can appear only in the ACCELL/SQL DEFINE
COMMAND section or SET COMMAND statement.
Set both AUD_ACTION and FIND_ACTION as the equivalent to setting
ACTION.
–14452
–14453
Explanation
Correction
–14454
Explanation
Correction
–14455
Obsolete syntax, BUTTON clause.
Commands no longer have attributes for the objects that activate
them. Instead set these attributes on the activator (button) objects.
Compatibility action: Ignoring obsolete clause.
Obsolete command.
Use CANCEL_FORM instead of CANCEL_ZOOM.
Compatibility action: Compiling as CANCEL FORM.
Contained in the message.
Follow the instructions in the message.
Obsolete syntax for command definition.
Use COMMAND instead of DEFINE COMMAND.
Compatibility action: Compiling as COMMAND.
Unify 4GL uses a COMMAND definition rather than the ACCELL/SQL
DEFINE COMMAND statement.
Convert the DEFINE COMMAND section to a COMMAND section. You
may need to delete various obsolete command attribute clauses.
Obsolete command.
RECALL_LAST_ERROR replaces EXPLAIN_ERROR.
Compatibility action: Compiling as RECALL_LAST_ERROR.
Explanation
Correction
Error Messages
Contained in the message. RECALL_LAST_ERROR does not support the
same functionality as EXPLAIN_ERROR, but is sufficiently related to be
considered a replacement.
Replace EXPLAIN_ERROR reference with RECALL_LAST_ERROR
reference, or delete logic referring to EXPLAIN_ERROR.
389
–14456
Obsolete syntax, KEY[S] clause.
Commands no longer have attributes for the keys that activate them;
Instead set key bindings in the [Keys] section of preferences
Compatibility action: Ignoring obsolete clause
Explanation
Contained in the message. The referenced attribute can appear only in the
ACCELL/SQL DEFINE COMMAND section or SET COMMAND
statement.
Correction
–14457
–14458
–14459
Explanation
Correction
Obsolete syntax, LABEL clause.
Commands no longer have attributes for the objects that activate
them;
Instead set these attributes on the activator (button) objects.
Compatibility action: Ignoring obsolete clause.
Obsolete command.
Use DISMISS_FORM instead of PREVIOUS_FORM.
Compatibility action: Compiling as DISMISS_FORM.
Reference to obsolete command, SYSTEM_HELP.
Equivalent function in Unify VISION is purely interactive.
Compatibility action: Ignoring statement.
Contained in the message.
Follow the instructions in the message.
–14460
Reference to Unify 4GL command as a variable.
This may have referred to a general variable in ACCELL/SQL.
Compatibility action: None, using Unify 4GL interpretation.
Explanation
A stored procedure refers to a predefined command as if it were a
variable. This could occur when porting an existing ACCELL/SQL
application, if it had a variable whose name is now used for a new
predefined command.
Correction
390
Follow the instructions in the message.
Change the name of the variable and make sure that no variable names
are the same as the name of a predefined command.
Error Messages
–14461
Explanation
Correction
–14462
Explanation
Correction
–14463
Explanation
Obsolete statement, DISPLAY HELP.
Unify 4GL uses a help system not linked to 4GL actions
Compatibility action: Ignoring statement
Contained in the message.
Examine the usage of DISPLAY HELP in this case. It may be appropriate
to create a normal form or to delete the DISPLAY HELP call and let the
new help system handle this function.
Obsolete statement, DISPLAY TRIM.
Inappropriate to Unify 4GL GUI environment
Compatibility action: Ignoring statement
Contained in the message.
Examine the usage of DISPLAY TRIM and determine an alternative; if
possible, delete this statement.
Obsolete syntax for ENABLE ZOOM statement.
Use Unify 4GL syntax rather than ACCELL/SQL syntax.
Compatibility action: Compiling as is, but ignoring AT clause (if
any).
The ENABLE ZOOM syntax uses clauses that are consistent with the new
CHOOSE FORM and CREATE FORM statements. This is incompatible
with the old syntax.
Correction
–14464
Explanation
Correction
Error Messages
The compiler will compile the ACCELL/SQL syntax with limitations, but
a better solution would be to rewrite the ENABLE ZOOM statement to
use Unify 4GL syntax.
Obsolete statement, ERASE HELP.
Unify 4GL uses a help system not linked to 4GL actions.
Compatibility action: Ignoring this statement.
Contained in the message.
Delete the ERASE HELP statement.
391
–14465
Explanation
Correction
–14466
Contained in the message.
Delete the ERASE TRIM statement.
Obsolete statement, ERASE
with apparent operand syntax error: Expected HELP or TRIM.
Explanation
An ERASE keyword suggests the start of an ACCELL/SQL Release 2
ERASE HELP or ERASE TRIM statement, but the next token is neither
HELP nor TRIM.
Correction
If you started vcpl with the –accept or –warn argument and the help or
trim operand, search for and correct related typographical errors. If you
did not start vcpl with the –accept or –warn argument, find and remove
the obsolete statement.
–14467
Explanation
Correction
–14468
Explanation
Correction
392
Obsolete statement, ERASE TRIM.
Unify 4GL handles textual trim as separate objects, does not support
graphic trim.
Compatibility action: Ignoring this statement.
Obsolete language name, ACCELL, for external function.
Use SCRIPT in UNIFY VISION instead of ACCELL.
Compatibility action: Compiling as SCRIPT function reference.
An EXTERN declaration uses a language name of ACCELL. Although
vcpl recognizes ACCELL, the correct equivalent is SCRIPT.
Change all instances of ACCELL to SCRIPT.
Obsolete syntax, master_application_form::
Use FIRST_INSTANCE: instead.
Compatibility action: Compiling as FIRST_INSTANCE.
Master application forms areno longer used, and variable syntax no
longer uses the :: operator.
Follow the instructions in the message.
Error Messages
–14469
Explanation
Correction
–14470
–14471
Explanation
Correction
–14472
Explanation
Correction
–14473
Obsolete syntax, ON PREVIOUS FORM section.
Use ON DISMISS FORM, new name for same section.
Compatibility action: Compiling as ON DISMISS FORM.
Contained in the message.
Follow the instructions in the message.
Obsolete statement, REFRESH SCREEN.
This function is not supported in Unify 4GL.
Compatibility action: Ignoring this statement.
Obsolete statement, REPAINT SCREEN.
This function is not supported in Unify 4GL.
Compatibility action: Ignoring this statement.
Contained in the message.
Delete the obsolete statement.
Obsolete statement, RESTART TX.
This function is not supported in Unify 4GL.
Compatibility action: Ignoring this statement.
Contained in the message.
Delete the obsolete statement. You may be able to substitute other
statements on an application-specific basis.
Obsolete feature, RESTART TX operation.
This function is not supported in Unify 4GL.
Compatibility action: Using START TX, RECORD CONSISTENCY.
Explanation
Contained in the message. In ON CHOOSE NEXT FORM section.
Correction
Replace RESTART TX with START TX RECORD CONSISTENCY.
Error Messages
393
–14474
Explanation
Correction
–14475
Explanation
Correction
–14476
Explanation
Correction
–14477
Explanation
Correction
394
Obsolete statement, SET COMMAND.
Use assignment to command’s object attributes instead.
Compatibility action: Compiling compatibly for AUD_ACTION and
FIND_ACTION clauses; translating ACTION clause; ignoring LABEL,
AUD_LABEL, FIND_LABEL, and KEYS clauses.
Contained in the message.
Substitute assignment of values to command object attributes in a SET
statement.
Obsolete syntax, ZOOM RETURN VALUES.
Use VALUES TO RETURN, new name for same statement.
(In Unify VISION ALL forms can return values).
Compatibility action: Compiling as VALUES TO RETURN.
Contained in the message.
Follow the instructions in the message.
Statement can only occur in an ON FIELD event section.
The compiler found either an INPUT or a RESTART ON FIELD
statement in an event section that is not the ON FIELD section. The
INPUT or a RESTART ON FIELD statements are valid only in the ON
FIELD section.
Find the INPUT or RESTART ON FIELD statement and move it to an ON
FIELD section.
Statement can only occur in an ON FIND event section.
The compiler found a REJECT RECORD statement in an event section
that is not the ON FIND section. The REJECT RECORD statement is
valid only in the ON FIND section.
Find the REJECT RECORD statement, and move it to an ON FIND
section.
Error Messages
–14478
Explanation
Correction
–14479
Explanation
Correction
–14480
Explanation
Ambiguous command line option
supply more characters to uniquely identify option name.
Too few characters were entered as the initial substring of an option name
to uniquely identify the option. For example, -s could refer to either the
-script or the -symbols option.
Use additional characters to represent a unique initial substring of the
option name. For example, -sc for -script and -sy for -symbols.
Unrecognized command line option
The vcpl command line contained an argument beginning with – that
does not match any valid vcpl command line argument.
Make sure that all command line arguments are valid. For the vcpl
command line syntax, see Unify VISION: Application Reference.
Unable to open file for output.
The compiler tried to open the file named output_file_name and failed.
This error occurs in the following cases:
vcpl was called with the –symbols option and was unable to open
the symbol table output file. This option is for diagnostic purposes
and should be used only under the direction of Unify Customer
Support.
vcpl was called with the –code option and was unable to open the
code output file. This option is for diagnostic purposes and should
be used only under the direction of Unify Customer Support.
Correction
Try these solutions:
Make sure that you have write and execute permission on the
current directory.
Make sure you have read and write permission on the file being
opened.
Make sure that the operating system has enough resources (open
file descriptors and inodes) to open a file.
Error Messages
395
–14481
Explanation
A statement in a script to be used with an ORACLE Version 7 database
contained what was expected to be a stored procedure call, but the
package name (package.) was not followed by a valid procedure name.
Correction
Make sure that the stored procedure call is in the correct format and that
the procedure name is correct.
–14482
Expected ”(” (left parenthesis).
Current text appeared to be a stored procedure call
beginning with ”package.procedure_name”.
Explanation
A statement in a script to be used with an ORACLE Version 7 database
contained what appeared to be a stored procedure call in the format
package.procedure_name, but the procedure name did not include the
parentheses that are required for a call from a script.
Correction
If the statement in question contains a stored procedure call, make sure
that the stored procedure call is in the correct format, including the
parentheses, for example, pkg1.myproc( ).
–14483
–14484
Explanation
Correction
–14485
Explanation
Correction
396
Incorrect syntax for stored-procedure name.
Expected ”package.procedure_name”
Unable to locate #include file.
Check to be sure file exists, check –I options to assure that its
directory is searched for include files.
Unable to locate #include library.
Check to be sure library exists in same project directory as script
being compiled or in a project listed.
Contained in the message.
Follow the instructions in the message.
Right parenthesis omitted.
Will assume at end of #include operand that should represent
“library_file(inclusion)”.
Contained in the message.
None at this time, but to prevent subsequent occurrences of this error, add
the closing parenthesis.
Error Messages
–14486
Explanation
Correction
–14487
Explanation
Correction
–14488
Explanation
Correction
–14489
Explanation
Correction
Error Messages
Invalid syntax for operand of #include.
Operand must be enclosed within double quotes or angle brackets.
Legal forms are:
#include ’inclusion’
#include ’library(inclusion)’
#include “source_filename”
#include <source_filename>
Contained in the message.
Correct the operand as indicated in the message.
Right parenthesis in unexpected position.
Will disregard characters following ) in #include operand that should
represent “library_file(inclusion)”
Contained in the message.
None at this time, but to prevent subsequent occurrences of this error,
make sure that the right parenthesis is positioned correctly or extra
characters are removed.
Unknown preprocessor command.
Identifier following a # character should be the name of a command
recognized by ANSI C preprocessors.
Contained in the message.
Verify the spelling of the preprocessor command. Some common
preprocessor commands are #define, #include, and #ifdef.
Received interrupt, canceling compilation(s).
The compiler received an INT signal through the operating system. The
most common interpretation of this is that the user requested termination
of the running program, usually by typing control C while the compiler is
being run.
None.
397
–14490
REF parameter illegal, cannot be passed to C-hooks or system
functions.
Explanation
Correction
–14491
Explanation
Correction
–14492
You attempted to pass reference parameters to a stored procedure.
Remove the reference parameter from the function definition.
RETURN KEY should not use ”INTO variable_list”.
Compiling as RETURN VALUES INTO variable_list for compatibility
with undocumented ACCELL/SQL behavior.
RETURN KEY cannot be used with a variable list equivalently to
RETURN VALUES; Unify 4GL enforces the specifications.
Use RETURN VALUES if you want to return values into variables.
Cannot call a row-valued stored procedure in an expression.
Explanation
Row-valued stored procedures can be used in Unify 4GL expressions.
Stored procedures of this type return multiple rows and can therefore be
used only as part of a SET statement.
Correction
If the stored procedure is incorrectly defined, redefine the stored
procedure to be a NUMERIC or other data type. Otherwise, modify the
affected stored procedure statements to first store the results of the stored
procedure in a general variable; then use this general variable in the
expressions.
–14493
Explanation
Correction
–14494
Bounded dimensions of a list or matrix cannot be resized.
Contained in the message.
Use unbounded list or matrix.
4GL script or inclusion may be incomplete.
“module” doesn’t end with an end-of-line character.
Explanation
Correction
398
Contained in the message.
Make sure that the script or inclusion is correctly terminated by an
end-of-line character.
Error Messages
–14495
Explanation
Correction
–14496
Explanation
Correction
–14497
Explanation
Correction
–14498
Explanation
Expected an event section or part of a script header.
The script did not start with an event section or script header. For
example, the script may start with statements that are not contained in an
event section, but an event section follows the statements.
Make sure that the statements are introduced by the appropriate event
section or script header.
Script is already defined to be a global function definition,
can’t define form 4GL in same script.
A FORM CLASS declaration appeared after presence of a function
definition. This had already defined the script to be a global function
script.
Make sure that no local function definition is misplaced in a stored
procedure. Local functions must follow the FORM CLASS declaration.
Unable to identify message parameter value.
A SEND MESSAGE statement recognized from the message handler’s
prior declaration or definition that a value must be supplied in the
parameter list, but no corresponding value is present in the SEND
MESSAGE parameter list.
Make sure that no omitted parameter is omitted from the SEND
MESSAGE statement.
Cannot identify form.
TO clause requires an object_ref-valued expression.
A SEND MESSAGE statement did not have a valid form reference in its
TO form_obj_ref_exp clause. Either nothing that follows the TO keyword
can be recognized as an expression or the expression is known at compile
time to have a type other than OBJECT_REF.
Correction
Supply an appropriate form reference, such as
PREV_INSTANCE:OBJECT_ID or $oid.
Error Messages
399
–14499
Explanation
Correction
–14500
Explanation
Correction
–14501
Explanation
Correction
The end of the file was found before a semicolon terminating the current
statement. All SQL statements not enclosed in a BEGIN_SQL/END_SQL
block must be terminated with a semicolon. Note, however, that a
SET . . . SELECT statement that contains an executing block does not
require a semicolon.
Add a semicolon to the end of the appropriate statement.
Illegal attribute use with binary target data, cannot use
CLEAR_FIND_EXP or SEARCH_RANGES attribute.
The script contains an invalid attribute reference for a BINARY variable.
Find the problem attribute reference and either remove the attribute or
change the variable to a variable that can have this attribute set.
Statement illegal in this context. This statement may not occur in the
current event section.
The compiler found an invalid stored procedure statement.
Find the invalid statement and remove it. See Unify DataServer: Writing
Interactive SQL/A Queries for a list of valid stored procedure statements.
–14503
String constant isn’t terminated before end of line.
(Expect some otherwise-inappropriate error reports to follow;
The compiler probably misidentified some necessary 4GL tokens
as part of the unterminated string constant.)
Explanation
A string constant, that started with a single-quote character was not
terminated by another single-quote before the end of the current line.
Correction
–14504
Explanation
Correction
400
Missing SQL statement terminator.
Find and correct the line that is missing the terminating single-quote
character. If you need to define a multiline string constant you can embed
newline characters in the string by using the \n escape sequence.
Can’t include \0 or \x0 in string constants.
A string constant included \0 or \x0. These characters are illegal because
the compiler recognizes them as string terminators.
Rewrite the script so that no string constant contains \0 or \x0.
Error Messages
–14505
Explanation
Correction
–14506
More than one default expression in switch statement.
The compiler found more than one DEFAULT clause in a SWITCH
statement.
Find the SWITCH statement that has the multiple DEFAULT clauses, and
remove all but one of the DEFAULT clauses. See Unify DataServer:
SQL/A Reference for the syntax and usage of the SWITCH statement.
Expected END to terminate SWITCH statement.
Check for END omitted or garbled syntax.
Explanation
At the end of a SWITCH statement, the compiler expected the next token
to be the END keyword.
Correction
Find the stored procedure statement that is missing the END keyword,
and rewrite the statement. See the Unify DataServer: SQL/A Reference for
the syntax and usage of stored procedure statements.
–14507
Explanation
Correction
–14508
Explanation
Correction
Error Messages
Symbol class conflict:
New reference to object suggests
a different object class than prior usage.
The compiler found a second reference to an object that does not agree
with the first reference to the object.
Find the conflicting references to the object and make sure that they
match.
Symbol table capacity exceeded for symbols.
As the compiler processes a script file, it builds three internal tables to
keep track of symbols. These tables are called local, external, and
ambiguous, each tracking a different symbol type. This error occurs if
one of the tables runs out of space.
Reduce the complexity of the script by decreasing the number of
variables in the symbol_type table.
401
–14509
Explanation
Correction
Too many characters in a single token.
No token may be more than 255 characters.
See the message.
Use the concatenation operator to create a string of more than 255
characters, for example:
SET big_string TO
’first 253 characters’ + ’next 253 characters’
–14510
Explanation
Correction
–14511
Explanation
Underscore omitted.
That should be ”TARGET_TABLE”, not ”TARGET TABLE”.
This is a warning message. A FORM CLASS declaration in
TARGET_TABLE clause used the separate keywords TARGET and
TABLE instead of TARGET_TABLE.
Connect TARGET and TABLE with an underscore.
Unable to access directory
for reading and writing temporary files;
Check to be sure that directory name is correct
and that directory permissions allow both read and write access.
The temporary directory cannot be written to; the compiler cannot
continue because it must write files into this directory.
The temporary directory is the directory that was specified by the
TMPDIR configuration variable. If TMPDIR is not set, the temporary
directory is the current working directory.
Correction
–14512
Explanation
Correction
402
Verify that the correct directory is being used as the compiler’s temporary
directory and that the current user has both read and write permission for
this directory.
Timer functions must have precisely one argument.
The compiler found an invalid number of arguments in the timer event
handler function declaration. A Timer function can have only one
argument, one non-result parameter.
Find the timer function declaration and rewrite it with one non-result
parameter.
Error Messages
–14513
Explanation
Correction
–14514
Explanation
Correction
–14515
Explanation
Correction
–14516
Explanation
Correction
–14517
Explanation
Correction
Error Messages
Language for timer functions must be SCRIPT
An EXTERN statement specified a language name other than SCRIPT (C
or STORED), but it gave a function type of TIMER.
Find the problem EXTERN statement and either correct the language
specification or the function type specification.
Too many code words used in the current code section.
Use functions to make current code section smaller.
Explanation in text.
Follow the instructions on the screen.
Expression is too complex,
unable to allocate enough code interpreter registers.
The compiler ran out of internal registers as it attempted to compile a
parsed expression; registers are used to store intermediate information.
This error occurs if the compiler tries to use more than 128 registers
while it processes an expression.
Find the expression that is causing the error and reduce the complexity of
this expression. Use variables to hold intermediate values in the
expression.
Type cannot be specified for an attribute.
The data types of variables can be specified in the LOCAL clause of the
form declaration in a stored procedure. This error indicates that a data
type was found after an attribute rather than a variable.
Find the problem LOCAL clause, and correct the error.
Type cannot be specified for an external variable.
The data types of variables can be specified in the LOCAL clause of the
form declaration in a stored procedure. This error indicates that a data
type was found after an external variable, which is invalid.
Find the problem LOCAL clause, and correct the error.
403
–14518
Explanation
Correction
–14519
Explanation
Correction
Type specified does not match column’s type.
The data types of variables can be specified in the LOCAL clause of a
function declaration in a stored procedure. This error indicates that the
data type specified for a variable is incompatible with the corresponding
database column’s data type.
Find the problem LOCAL clause, and correct the error.
Type can only be specified for a variable.
The data types of variables can be specified in the LOCAL clause of the
form declaration in a stored procedure.
Find the problem LOCAL clause, and correct the error.
–14520
END keyword doesn’t match a preceding BEGIN.
Check for BEGIN omitted or accidentally enclosed in a comment.
Explanation
The script contains an END keyword that is not preceded by a BEGIN
keyword. BEGIN indicates the start of a block of statements; END
terminates the block.
An END without a preceding BEGIN sometimes is the sign of an error in
commenting. If the comment terminator (*/) is omitted, the statements on
the following lines are treated as part of that comment until another */ is
found. This error occurs if a BEGIN is in the statement block that is
disregarded as a comment.
Another commenting error that can produce this a comment nested within
a larger, usually multiline comment. Because comments do not nest, the
inner comment’s */ terminates the outer comment. If the outer comment
contains the word end between that point and the */ intended to terminate
it, the compiler will interpret that word as an isolated END keyword.
Correction
–14521
Explanation
404
Make sure that the stored procedure contains no editing errors and
commenting errors like those described here.
END_SQL keyword doesn’t match a preceding BEGIN_SQL.
Check for BEGIN_SQL omitted or accidentally enclosed in a
comment.
The script contains an END_SQL keyword that has no corresponding
previous BEGIN_SQL keyword. BEGIN_SQL indicates the start of a
block of SQL statements; END_SQL terminates the block.
Error Messages
An END_SQL without a preceding BEGIN_SQL sometimes is a sign of a
commenting error. If the comment terminator (*/) is omitted, the
statements on the following lines are treated as part of that comment until
a */ is found. This error can occur if a BEGIN_SQL was within the
statement block that is disregarded as a comment.
Another commenting error that can produce this a comment nested within
a larger, usually multiline comment. Since comments do not nest, the
inner comment’s */” terminates the outer comment. If the outer comment
is a temporarily disabled section of code that contains an END_SQL
between that point and the */ intended to terminate it, the compiler will
recognize an isolated END_SQL keyword.
Correction
–14522
Explanation
Correction
–14523
Explanation
Make sure that the script contains no editing errors and commenting
errors like those described above.
Invalid use of USING connection_name clause.
Connection override has no meaning for this statement.
A USING [CONNECTION] clause prefixes a statement for which a
connection override is meaningless.
Delete the USING clause.
Variable name refers to object of wrong class.
Variable class must be SCALAR, LIST, or MATRIX.
A variable name given in a list of variables, such as occurs in a RETURN
VALUES clause, referred to the name of a command or a form. Only
variables that can have a value make sense in this context; these variables
are of class SCALAR, LIST, or MATRIX.
A common cause for this error is that the current statement refers to a
name that was intended to represent a variable, but for the name is a
duplicate of the name of a function or stored procedure.
Correction
Error Messages
Make sure that the stored procedure does not have conflicting variable
names.
405
–14524
Explanation
Correction
–14525
Explanation
Correction
–14526
Explanation
Correction
–14527
Explanation
Correction
406
Expected an identifier or attribute.
The compiler expected a reference to a variable. Such a reference can
start with an identifier or a keyword that names an object attribute, but the
compiler found neither.
Find the statement that uses a keyword as a variable name and either
change the variable name or enclose it in quotation marks (”name”).
Attribute inappropriate to this context.
Variable reference here must refer only to name of variable.
or to its VALUE attribute.
A variable list that must contain only the name of a local variable
contained an inappropriate reference to an attribute of the variable.
Delete the inappropriate attribute reference.
Check units.
Width and height are in pixels for Unify VISION,
were in characters for ACCELL/SQL.
This is a compatibility warning message. Unify VISION uses the WIDTH
or HEIGHT attribute of an object. If this is an ACCELL/SQL application
being converted to Unify VISION, the application probably uses these
attributes as character coordinates. In Unify VISION they are pixel
coordinates. Depending on how the application uses these attributes, its
operation may be incorrect.
Modify application logic for consistency with pixel coordinates.
Only ’new:’ or ’old:’ is allowed here.
Form qualifiers are not allowed in stored procedures. You can refer only
to local variables or stored procedure parameters.
Remove the form qualifier from the variable name.
Error Messages
–15800
Explanation
Correction
–15801
Explanation
Correction
–15802
Explanation
There are no errors at this time.
An internal operation has completed successfully.
If this error occurs, please call Unify Customer Support.
There is not enough memory available.
Unify DataServer ran out of memory while executing a function.
First try to reduce the size or complexity of the function. Also make sure
that you commit transactions frequently. If these solutions do not solve
the problem, have your system administrator reconfigure the memory
parameters of your operating system.
A file is not in the proper format.
A file has an unrecognizable magic number. Every file type has an
associated magic number that enables executables to distinguish between
different types of files.
This error occurs when an executable reads a file for which the magic
number does not match the type of file that was expected. The file may
have been corrupted or the user may have made an execution error.
Correction
–15803
Explanation
Correction
–15804
Explanation
Correction
Error Messages
Run the executable to generate the file again, or recover the file from a
backup.
The Manager cannot continue due to a severe error.
An internal error has occurred while executing a function.
This error can result from exhausted resources or an internal program
error. Try alternative statements to achieve the same result. If the error
persists, call Unify Customer Support.
There is not enough memory to continue processing.
Unify DataServer has run out of memory for the function.
Commit transactions frequently and reduce the size or complexity of the
function. If the problem continues, as a last resort, your system
administrator can reconfigure the memory parameters of your operating
system.
407
–15805
Explanation
Correction
–15806
Explanation
Correction
The current user does not have permission to access a file.
The current user did not have permission to access a file.
Check the file permissions and correct them if needed.
An Input/Output (I/O) error has been detected by the system.
The operating system has detected a hardware error in the I/O subsystem.
Try these solutions:
Check the file system and repair if necessary.
Run hardware diagnostics.
If the the first two suggestions do not correct the problem, you
may also need to back up application files.
–15810
Explanation
Correction
–15811
Explanation
Correction
–15812
Explanation
408
Arithmetic overflow has occurred in code for function.
During the conversion of a value from one data type to another an
arithmetic overflow occurred.
Step through your function to determine which variables caused the error.
Change the affected statement to prevent the conversion of values that
could cause overflow.
Arithmetic underflow has occurred in a code for function.
During the conversion of a value from one data type to another an
arithmetic underflow occurred.
Step through your function to determine which variables caused the error.
Change the affected statement to prevent the conversion of values that
could cause overflow.
The specified value is not in a correct DATE format.
The DATEFMT configuration variable determines the current date format.
This error occurs when an invalid date value is represented as a string.
For example, the date value “30/12/88” is invalid for the date format
“MM/DD/YY”, because “30” is not a valid month.
Error Messages
A DATE format is specified by the DATEFMT configuration variable, for
which these are some possible formats:
Correction
Make sure that the DATEFMT configuration variable is set correctly. If the
DATEFMT configuration variable is set correctly, determine which
function statement caused the error and change the statement to prevent
invalid DATE values.
The DATEFMT configuration variable is described in Unify DataServer:
Configuration Variable and Utility Reference.
–15814
Explanation
Correction
–15815
–15816
Explanation
A file cannot be found.
Unify DataServer could not find the specified file.
Make sure that the specified file exists and that you have read access for
the file.
Incompatible data types used in the current operation.
Incompatible data types used in the current operation.
The function was performing an operation that required operands with
matching data types and found an invalid type. Operations likely to cause
this problem are assignments of a value or an attribute and arithmetic
operations, such as addition and multiplication.
For example, you may be trying to add a NUMERIC to a STRING. You
may also have an undefined variable in the expression.
Correction
–15817
Explanation
Correction
Error Messages
Identify the problem function statement and change the statement so that
only correct data types are used in the operation. For more information
about operator compatibility, see Unify DataServer: Writing Interactive
SQL/A Queries.
Division by zero was attempted in the code for function.
A function statement tried to divide by zero. This is an invalid arithmetic
operation.
Modify the function so that it does not try to divide by zero.
409
–15820
Explanation
Correction
–15826
Explanation
Correction
–15827
Explanation
Correction
–15839
Explanation
“Attempt to set a read-only trigger special variable.”
An attempt to set the value of a read-only trigger special variable was
made. See “Stored Procedures and Triggers” in Unify DataServer:
Writing Interactive SQL/A Queries to determine which new: or old:
variables are read-only, depending on the type of trigger.
Remove the offending code. You cannot change the value of a read-only
trigger special variable.
The function just referenced is not active.
The function referenced a variable in a function that is not the current
function. Referencing variables in other functions is not allowed.
Make sure that all variables that are referenced are local to the function.
Change any function:$variable references to variable.
The variable just referenced does not exist in the function.
The function referenced a variable that is not in the function.
Make sure that all variables that are referenced are local to the function.
Change any function:$variable references to variable.
The specified search criteria are invalid.
Search criteria has been specified that is not in the correct format. These
are the valid search criteria metacharacters:
410
Error Messages
These are examples of search criteria for various data types:
Correction
–15840
Explanation
,;, '>8/
=,584/ 70 %,61/
'
'"
&'%#
*+*+
"$(#'
#("%
!$'
$$!
)
Reenter the search criteria by using the correct metacharacters.
Justification specifier in a DISPLAY statement is invalid.
An invalid display justification was used. These are the valid justification
specifiers:
7./
!'
%'
#'%
Correction
–15841
<:;303-,;376
4/0; ./0,<4;
9312;
-/6;/9
Find and correct the statement that contains the invalid display
justification.
There is no current record, so there is no record to delete.
Explanation
The current record cannot be deleted because no record is current.
Correction
Perform a selection to establish a selected set and a current record.
–15848
Explanation
Correction
Error Messages
Bad heap size parameter size.
The AMGR_HPSZ configuration variable is set to the invalid value of size.
Make sure that the AMGR_HPSZ configuration variable is set to a valid
value. .
411
–15850
Explanation
Correction
–15852
Explanation
Correction
–15855
Explanation
Correction
–15859
Explanation
Correction
–15862
Explanation
Correction
412
Bad stack block size parameter size.
The AMGR_STK_B_SZ configuration variable is set to the invalid value of
size.
Make sure that the AMGR_STK_B_SZ configuration variable is set to a
valid value.
Unify 4GL is unable to open the error file ’file_name’.
The file_name file cannot be found.
Make sure that the file_name file exists and that you have read/write
access for it.
Database design has changed since the application was built.
The database information in the function does not match the database
design.
Make sure that the DBPATH and DBNAME configuration variables are set
correctly.
The specified record could not be accessed or locked.
The specified row was locked by another user. The row may have been
deleted.
Wait and try again later. See Unify DataServer: Managing a Database for
more information about transactions and locking.
A subtraction operation was attempted on a string.
A statement tried to subtract a string value. Subtraction is not allowed for
strings.
Find the statement that caused the error and correct it. See Unify
DataServer: Writing Interactive SQL/A Queries for more information
about string values and the subtraction operator.
Error Messages
–15863
The result of a string concatenation operation is too long.
Explanation
A string concatenation operation resulted in a string that was longer than
the maximum length of 256 characters.
Correction
Reduce the length of the strings involved in the concatenation. See Unify
DataServer: Writing Interactive SQL/A Queries for information about
string operations.
–15864
Explanation
Correction
–15867
Explanation
The record(s) selected are locked by other users.
All of the rows referenced by the function are locked.
Try the search operation again later when the rows in question might not
be locked. See Unify DataServer: Managing a Database for more
information about transactions and locking.
Attempt to update the database with an UNDEFINED variable.
The current database operation attempts to update the database with an
UNDEFINED variable, which is not allowed.
Correction
–15874
Explanation
Determine which value is UNDEFINED, define it as one of the valid
data types and retry the insert or update operation again.
A CREATE PIPELINE statement has failed.
A pipe could not be established between the programs listed in the
CREATE PIPELINE statement.
Correction
–15875
Explanation
Correction
Error Messages
Find the CREATE PIPELINE statement that caused the error and make
sure that all the programs in the program list exist, are executable,
operate correctly, and are on the directory search path specified by your
PATH configuration variable.
A CLOSE PIPELINE statement has failed.
The pipe listed in the CLOSE PIPELINE statement could not be
terminated.
Find the CLOSE PIPELINE statement that caused the error and make
sure that a CREATE PIPELINE statement has successfully executed for
this pipeline variable. Also make sure that the pipeline variable’s value
has not changed since the CREATE PIPELINE statement was executed.
413
–15876
Explanation
A pipeline variable does not have the correct data type. Because pipeline
variables contain operating system file descriptors that are integers,
pipeline variables must be of type NUMERIC.
Correction
If the error occurs on a CREATE PIPELINE statement, make sure that the
pipeline variable used is of NUMERIC data type or is UNDEFINED. If
the error occurs on a CLOSE PIPELINE statement, make sure that a
CREATE PIPELINE statement has successfully executed and that the
pipeline variable has not been modified since. The pipeline variable must
have a non-null numeric value.
–15877
Cannot create file specified by OUTPUT IS of CREATE PIPELINE.
Explanation
The CREATE PIPELINE statement’s OUTPUT IS clause has specified an
output file that cannot be created.
Correction
Make sure that the directory where the output file would reside exists and
that the current user has write permission on both the directory and the
file. Also, make sure that you have enough disk space to create the file.
–15878
Explanation
Correction
–15879
Explanation
Correction
414
The pipeline variable must be of type NUMERIC.
Programs in a CREATE PIPELINE statement could not be executed.
One of the programs in the program list of a CREATE PIPELINE
statement could not be executed.
Find the CREATE PIPELINE statement that caused the error and make
sure that all the programs in the program list exist, are executable,
operate correctly, and are on the directory search path specified by your
PATH configuration variable.
There was an abnormal pipeline member termination.
A pipeline could be established, and the pipeline programs were
executed, but one of these programs terminated abnormally.
Find the CREATE PIPELINE statement that caused the error and make
sure that all the programs specified in the CREATE PIPELINE statement
operate correctly.
Error Messages
–15880
Explanation
Correction
–15881
An error has occurred in a CREATE PIPELINE statement.
An operating system error indicated that too many or no tasks have been
started. This error occurs during the execution of a CREATE PIPELINE
statement.
Find the CREATE PIPELINE statement that caused the error and try
reducing the complexity of the CREATE PIPELINE statement. Also
consider using intermediate files.
An invalid display justification type was found.
Explanation
Display justification can be LEFT, RIGHT, or CENTERED. Display
justifications are used in the DISPLAY statement and as values to the
DISPLAY_JUSTIFY screen attribute.
Correction
Find and correct the script statement that contains the invalid display
justification.
–15882
Explanation
Correction
–15883
Explanation
Correction
–15886
Explanation
Correction
Error Messages
Exit the application.
An error was encountered that may prevent the function from continuing
without problem.
Exit the application in an orderly manner.
There were bad arguments to a system function.
A system function call has incorrect arguments.
Find the system function call that caused the error and make sure that the
system function is passed the correct number and types of arguments.
Also make sure that no undefined values are being passed as function
arguments. See Unify DataServer: SQL/A Reference for the syntax and
descriptions for system functions.
The value of a variable is undefined.
An UNDEFINED value was found while trying to use a display format.
Display formats are used in the DISPLAY statement and as values to the
DISPLAY_FORMAT screen attribute.
Find and correct the form script statement that contains the undefined
value.
415
–15887
Explanation
Correction
–15894
Explanation
Correction
–15896
The data type of a variable created or updated by the function does not
match the column type of the database column from which the value is
derived
Make sure that no function introduces an invalid data type. Make sure
that variable types match the data types of their associated
database columns in the INSERT, SELECT, and UPDATE statements. See
Unify DataServer: Writing Interactive SQL/A Queries for more
information about data types.
An illegal default justification type was found.
A default display justification was invalid. This is an internal error and
should not occur in normal execution.
If this error occurs, pleas call Unify Customer Support.
A temporary file could not be created or opened.
Explanation
The temporary file could not be created or opened because you either do
not have write permission on the file or directory, or you are out of disk
space.
Correction
Make sure that you have write permission in the indicated directory and
that you are not out of disk space.
–15897
416
An invalid variable or database type was detected.
Arithmetic operation was attempted on an old-style NULLDATE.
Explanation
NULLDATE is a keyword that represents a null DATE value in
applications developed under ACCELL 1.4 and earlier. One restriction on
NULLDATE values is that certain arithmetic operations, such as addition,
cannot be performed on them.
Correction
Find the statement that contains the reference to the obsolete NULLDATE
keyword and change the statement to use the NULL keyword for DATE
null values.
Error Messages
For information about null values, see Unify DataServer: Writing
Interactive SQL/A Queries.
–15902
Explanation
Correction
–15905
Explanation
Correction
–15906
Explanation
Correction
–15907
Explanation
Correction
Error Messages
There is an undefined boolean variable in a statement.
The boolean expression in a FOR, WHILE, REPEAT, or IF flow control
statement was undefined.
Find the flow control statement that is causing the error and make sure
that all variables in the logical expression are defined. See Unify
DataServer: SQL/A Reference for the syntax and usage of the flow control
statements.
Programs in a WRITE PIPELINE statement could not be executed.
A WRITE PIPELINE statement failed because one of the programs could
not be executed.
Make sure that all the programs in the pipeline exist, are on your path,
and are executable. Also make sure that all the programs in the pipeline
operate correctly.
Function was called with the wrong number of arguments.
Contained in the message.
Find the function call that caused the error and make sure that the
function name is spelled correctly and called with the correct number of
arguments. See Unify DataServer: Writing Interactive SQL/A Queries for
more information about writing stored procedures and other functions.
There was a bad type in type conversion.
An invalid data type was found when converting a value from one data type to another.
Make sure that no function introduced an invalid data type. See Unify
DataServer: Writing Interactive SQL/A Queries for more information
about data types.
417
–15908
Explanation
A time value was invalid. For example, the string “dog” is an invalid
time value, but the string “06:30” is valid if the TIMEFMT configuration
variable is set to “HH:MM”.
Correction
Change the offending statement. See Unify DataServer: Writing
Interactive SQL/A Queries for more information about valid time values.
For information about the TIMEFMT configuration variable, see Unify
DataServer: Configuration Variable and Utility Reference.
–15909
Explanation
Correction
–15910
418
The specified value is not in a correct TIME format.
The specified value is not in a correct BOOLEAN format.
A boolean value was invalid. For example, the strings “dog” is an invalid
boolean value, but the strings “YES” and “n” are valid boolean values if
the BOOLFMT configuration variable is set to “YES/NO”.
Change the offending statement. See Unify DataServer: Writing
Interactive SQL/A Queries for more information about valid boolean
values. For information about the BOOLFMT configuration variable, see
Unify DataServer: Configuration Variable and Utility Reference.
The specified value is not in a correct FLOAT format.
Explanation
A float value was invalid. For example, the strings “1/1/88” and “$1.00”
are invalid float values, but the strings “99.99” and “1.087” are valid
float values. The display format for FLOAT values can be specified by
setting the FLTFMT configuration variable.
Correction
Change the offending statement. See Unify DataServer: Writing
Interactive SQL/A Queries for more information about valid float values.
For information about the FLTFMT configuration variable, see Unify
DataServer: Configuration Variable and Utility Reference.
Error Messages
–15911
Explanation
Correction
–15912
Explanation
Correction
Error Messages
The specified value is not in a correct NUMERIC format.
A numeric value was invalid. For example, the strings “dog” and “99.99”
are invalid numeric values, but the strings “8” and “3557” are valid
numeric values. The display format for NUMERIC values can be specified
by setting the NUMFMT configuration variable.
Change the offending statement. See Unify DataServer: Writing
Interactive SQL/A Queries for more information about valid numeric
values. For information about the NUMFMT configuration variable, see
Unify DataServer: Configuration Variable and Utility Reference.
The specified value is not in a correct AMOUNT format.
An amount value was invalid. For example, the strings “1/1/88” and “1”
are invalid amount values, but the strings “$99.99” and “$1.0” are valid
amount values. The display format for AMOUNT values can be specified
by setting the AMTFMT and CURR configuration variables.
Change the offending statement. See Unify DataServer: Writing
Interactive SQL/A Queries for more information about valid amount
values. For information about the AMTFMT and CURR configuration
variables, see Unify DataServer: Configuration Variable and Utility
Reference.
419
–15913
Explanation
Correction
Could not open the database.
Contained in the message.
Try these solutions:
Make sure you are in the correct directory.
Make sure that the DBNAME and DBPATH configuration variables
are set correctly.
If this is a network connection, make sure that the DBHOST and
CLIENTINFO configuration variables are set correctly. And verify
that the release operates on a network connection. Also make sure
that your database login user name and password are both
specified correctly.
Make sure that you have database access permission and that you
have read/write permission for the database files.
If the database has been shut down, you may not be able to open
the database. Make sure that the AUTOSTART and OWNERSTART
configuration variables do not prevent you from opening the
database.
–15914
Explanation
Correction
–15916
Explanation
Correction
–15918
Could not close the database.
The database cannot be closed because of a problem with system
resources or the operating system or because an internal error has
occurred.
If this error occurs, please call Unify Customer Support.
Could not commit a transaction.
The current transaction cannot be committed because of a problem with
system resources or the operating system or because an internal error has
occurred.
If this error occurs, please call Unify Customer Support.
Illegal undefined value in Unify 4GL to DBMS conversion.
Explanation
Correction
420
Error Messages
–15920
Explanation
Correction
–15921
Explanation
Correction
–15930
Explanation
Correction
–15931
Explanation
Date initialization failed.
Internal date information cannot be initialized because ofa problem with
system resources or the operating system or because an internal error has
occurred.
If this error occurs, please call Unify Customer Support.
Internal operating system error in interrupt handler area.
An operating system error has occurred in the interrupt handler area
because of a problem with system resources or the operating system or
because an internal error has occurred.
If this error occurs, please call Unify Customer Support.
Internal problem with null values.
An invalid null value was found.
Make sure that no function introduced an invalid null value. If this is not
the case, an internal error has probably occurred; please call Unify
Customer Support.
NULL appears in an invalid Unify 4GL script context.
Because the NULL keyword is a null value that has no associated data
type, there are restrictions on where it can occur in a function. Most of
these invalid contexts are caught by the compiler.
However, some instances, such as an assignment of the NULL keyword
to an undefined variable, cannot be caught until the function is executed.
Such an assignment is invalid because the undefined variable has no
associated data type.
Correction
Error Messages
Find the statement that caused this error and make sure that general
variables are defined before assigning the NULL keyword to them. For
more information about null values, see Unify DataServer: Writing
Interactive SQL/A Queries.
421
–15932
Explanation
Correction
Unable to get information on your schema or username.
The function cannot switch to or obtain information about the schema
that contains the application files.
Try these solutions:
Make sure that you are using the correct database and that the
database design referenced in your function matches the current
database design.
Make sure that the schema specified for the function is correct and
that the current user has the correct permissions for running a
function under that schema.
Make sure you have the correct user name and password and that
they are the correct case.
–15933
Explanation
The function cannot obtain information about the current user from the
database.
Correction
Make sure that you are using the correct database and that the database
design referenced in your function matches the current database design.
Also, make sure that the current user has the correct permissions for
running the function in the specified schema.
–15937
Explanation
Correction
–15938
422
Cannot obtain information on a user.
Displayed value has overflowed a field’s display format or length.
During conversion of a value to a string for display in a field the string
value overflowed the display format or field width.
Adjust the display format to accommodate larger values. Make the field’s
length larger. Truncate the string value.
The input string is invalid for the given data type.
Explanation
A string cannot be converted to a data type because the string
is invalid for the given type.
Correction
Find and correct the invalid string value. See Unify DataServer: Writing
Interactive SQL/A Queries for more information about valid data type values.
Error Messages
–15941
Explanation
Correction
Transaction commit or abort failed, function cannot continue.
Under normal conditions, a commit or abort of a transaction should not
fail. This error probably indicates a serious problem in the administration
of the current database.
Try these solutions:
Make sure that the transaction log is not full; this can be caused by
the journal being off line.
Make sure that transaction logging is turned on before you try to
abort a transaction.
Try to determine whether a serious database error has occurred.
HOW?
–15942
Explanation
Correction
–15957
Explanation
Correction
–15958
Explanation
Bad regular expression passed to reg_exp_str_compare$( ).
The reg_exp_str_compare$( ) system function was passed a regular
expression that it could not interpret.
Find the statement that has the bad regular expression argument for
reg_exp_str_compare$( ) and correct it. See Unify DataServer: SQL/A
Reference for more information about the reg_exp_str_compare$( )
system function.
Invalid value for expression evaluation in statement.
This error occurs when specific parameter of a statement has an invalid
value.
Locate the problem statement and make sure all possible values in
question are defined, non-null, and of the correct type.
Could not get database information.
The function could not access its own information about the current
DBMS product to be interfaced with. This error should not normally
occur.
Correction
Error Messages
If this error occurs, please contact Unify Customer Support.
423
–15960
Explanation
Correction
–15961
The number of zoom values returned from a zoom form does not match
the number of variables in the INTO clause of the ENABLE ZOOM
statement on the calling form.
Make sure that a ZOOM RETURN VALUES statement with the same
number of values as the INTO clause of the ENABLE ZOOM statement is
in effect on the zoom form when the command is executed. It is also
important that the data types of the values brought back from the zoom
form match those expected by the calling form.
Record being updated has been modified by another user.
Explanation
The row that the function is trying to update has already been updated by
another user or transaction. The attempted operation is not allowed.
Correction
Try the operation again if you are working on a system with other users.
–15962
Explanation
Record being updated has been deleted by another user.
The row that the function is trying to delete has already been updated by
another user or transaction. The attempted operation is not allowed.
Correction
If you need this record to be in the database, you can re-insert it.
–15963
Record being positioned to has been deleted by another user.
Explanation
Correction
–15976
Explanation
Correction
424
Returned values do not match calling function.
Because the function has locked only the current row, other rows can be
deleted by other users or transactions. This error occurs when the
function tries to access a row that has been deleted by another user or
transaction.
This message is informational in nature and requires no correction.
Function will not fit in the maximum size for the application.
Bad form coordinates for the maximum rows and columns were found in
the resource file. A form has been activated whose position/size exceeds
those maxima.
Change the maximum rows and columns values in your resource file or
change the size or position of the form.
Error Messages
–15984
Explanation
Correction
Not that many lines in the current view file.
You have specified a line number that exceeds the number of lines in the
source file.
Specify a lower number when you execute the command.
–15985
Only the VALUE attribute of a variable can be NULL or UNDEFINED.
Explanation
The specified variable is not associated with the specified function (if one
was specified) or the current function (if none was specified).
Correction
Verify the spelling of the variable and function name (if specified) and
make sure that the variable exists in the specified function. If no function
was specified, specify it.
–15987
Explanation
Correction
–15988
Explanation
Correction
–15990
Explanation
Correction
–15991
Explanation
Correction
Error Messages
The ‘TO’ keyword is missing for this Debugger command.
TO is a required keyword of this command.
Execute the command again with the correct syntax.
That is not a valid value.
The numeric value entered on the command line is not valid.
Reenter the command with a valid value.
An invalid attribute or variable name was specified.
This command requires that you specify a valid form attribute or a valid
variable.
Reenter the command with a valid attribute or variable.
An invalid attribute was specified with this command.
The field attribute that you have specified does not exist or is spelled
incorrectly.
For information about attributes, see Unify DataServer: SQL/A Reference.
425
–15993
Explanation
Correction
–15995
Explanation
Correction
–16000
Invalid argument specified with the breakpoint command.
One of the arguments specified with this breakpoint command is not
valid.
Reenter the command with valid arguments.
Line not executable or file does not belong to debug function.
Either the line number used with this command does not include any
statement, or the current source file is not associated with the
function.
View the source file to obtain a line number that has an executable
statement.
Array referenced using a subscript which is out of bounds.
Explanation
An array reference was made with a subscript that was out of bounds.
Correction
Find the statement that contains the invalid array subscript and correct
the statement.
–16001
Explanation
Correction
–16002
Explanation
Invalid Unify 4GL type used for an array subscript.
An array reference was made with a subscript whose type was not
numeric.
Find the statement that contains the invalid array subscript and make sure
that the types of all array subscripts are numeric.
Ambiguous array referenced in the current function script.
Execution of a function revealed references to ambiguous symbols.
If the symbol references a scalar (non-array) variable, space is
allocated for that variable, and it is made local to the function
being executed.
If the symbol references an array variable, the ammount of space
to allocate for that array cannot be determined, generating an error.
Correction
426
Define the array in a LOCAL clause.
Error Messages
–16003
Explanation
Correction
–16004
Subscript missing from array reference. Value is undefined.
An array was referenced without a subscript in the form script.
Find the array reference that is missing the subscript. Determine which
cell of the array is being referenced and add the array subscript.
The dimensions used to declare the dynamic array are invalid.
Explanation
An array’s size can be dynamically defined at runtime by using variables
as array dimensions in the LOCAL clause. If the variable expressions
resolve to undefined values or non-numeric types, or the lower bound is
greater than the upper bound, an error is generated and the array remains
undefined.
Correction
Make sure that the expressions used to define dynamic arrays resolve to
defined numeric values where the lower bounds are less than or equal to
the upper bounds.
–16005
There is not enough memory to grow an unbounded array.
Explanation
Not enough memory remains to grow an unbounded array. Unbounded
arrays are enlarged or grown when they are referenced by using
subscripts that are beyond their original upper bounds.
Correction
To avoid fragmentation and facilitate determination of the size of array
blocks, when defining unbounded arrays, make a best guess for the size
of the array by using the ESTIMATING clause.
–16007
Parameter type mismatch in Unify 4GL script function.
Explanation
The types of the parameters being passed to a function call do not match
the types in the function definition. This means that the function
declaration where the function is called from is different from the
function definition where the code for the function exists.
Correction
Make sure that the function declaration and the function definition have
matching parameter types.
Error Messages
427
–16008
Explanation
Correction
–16009
An attempt was made to reference an array attribute with a scalar
(non-array) variable.
Make sure that the array being referenced is defined.
List array cannot reference a matrix array attribute.
Explanation
An attempt was made to reference an array matrix attribute with an array
list variable.
Correction
Make sure that the correct array is being referenced. If the correct array is
being referenced, make sure that it has been defined with the correct
number of dimensions. A list array has one dimension, and a matrix array
has two dimensions.
–16010
Explanation
Correction
– 16015
Explanation
Correction
–16016
Explanation
Correction
428
Scalar variable cannot reference an array attribute.
Matrix array cannot reference a list array attribute.
An attempt was made to reference an array list attribute with an array
matrix variable.
Make sure that the correct array is being referenced. If the correct array is
being referenced, make sure that it has been defined with the correct
number of dimensions. A list array has one dimension, and a matrix array
has two dimensions.
An invalid stack address was encountered.
The runtime manager found an error in managing the stack memory area.
This is an internal error and should not occur in the normal function
execution.
If this error occurs, call Unify Customer Support.
This is not a function.
The operation being requested cannot be performed in the context of a
function.
Determine which statement contains the invalid operation and rewrite the
statement. For the syntax and usage for statements that can be used in
stored procedures and related functions, see Unify DataServer: SQL/A
Reference.
Error Messages
–16017
Explanation
Correction
–16018
This function cannot be modified.
An insert, update, or delete operation can not be done on the function
because the function is read only.
Do not attempt to update the function.
The operation is not allowed on the function.
Explanation
An attempt to perform an interactive INSERT, UPDATE, or DELETE
command was denied.
Correction
Verify the schema and user privileges that control which interactive
database operations are permitted for the function.
–16019
Explanation
Correction
–16020
Illegal variable length data in-memory limit: length.
The ACLVARMEMLIM configuration variable was set to an invalid value
of length.
Make sure that the ACLVARMEMLIM configuration variable is set to a
valid value.
Illegal variable length data file directory name:
directory_search_path.
Explanation
The ACLVARDIR configuration variable was set to an invalid value of
directory_search_path.
Correction
Make sure that the ACLVARDIR configuration variable is set to a valid
directory search path and that the specified directory exists.
–16021
Illegal maximum number of open variable length data files: number.
Explanation
The ACLMXOPNVARF configuration variable was set to an invalid value
of number.
Correction
Error Messages
Make sure that the ACLMXOPNVARF configuration variable is set to a
valid number of files.
429
–16024
Explanation
Error reading/accessing a variable length data file.
TEXT and BINARY values whose length exceeds the value of the
ACLVARMEMLIM configuration variable are stored in temporary files. An
attempt to read or access one of these files failed.
Correction
–16025
Explanation
Correction
–16026
Explanation
Correction
–16027
Explanation
Correction
430
Make sure that the directory specified by the ACLVARDIR configuration
variable exists and that the permissions allow read access to the current
user.
Error writing to a variable length data file.
TEXT and BINARY values whose length exceeds the value of the
ACLVARMEMLIM configuration variable are stored in temporary files.
Make sure that the directory specified by the ACLVARDIR configuration
variable exists and has the correct write permissions. Also make sure that
you have not run out of disk space.
A file that was to be created already exists.
The CREATE file mode open option was to be used by a STORE
statement for the output TEXT or BINARY file, but the file to be created
already exists.
Find the offending STORE statement and rewrite it with a different file
open mode option, or remove the file before the STORE statement tries to
re-create it.
An expression or variable must be of type TEXT or BINARY.
An expression or variable was used in a context that requires a TEXT or
BINARY value, but the expression or variable is not TEXT or BINARY.
Find the offending STORE or RETRIEVE statement and rewrite it.
Error Messages
–16029
Explanation
Correction
Cannot ’SET’ text or binary variables in the debugger.
An attempt was made to set a TEXT or BINARY variable from the
debugger.
Make sure that you are referencing the correct variable.
Modify the function to make all columns which are part of the row
identifier required.
Add statements to the function to set default values for all columns
that are part of the row identifier.
–16038
Explanation
Correction
–16039
Attempt to read record(s) with undefined row ids.
This error is identical to error -16037, except that multiple records are
affected.
See the corrective actions recommended for error -16037.
Attempt to read deleted record(s).
Explanation
Another user or transaction has deleted records that are referenced by
your function.
Correction
To prevent records from being deleted by other users, lock the table.
–16040
Invalid value for $info_level.
Explanation
The $info_level system variable has been set to an invalid value and has
been reset to 1. An $info_level of 1 indicates that an intermediate level of
error information is displayed when an error occurs.
Correction
Make sure that your application sets the $info_level system variable to 0,
1, or 2. Any other value is invalid.
–16044
Explanation
Correction
Error Messages
Can’t set Clear to find and search ranges for binary variables.
A search range was specified for a BINARY type variable.
Find the problem search range specification and change the statement so
that it does not refer to a BINARY variable.
431
–16045
Explanation
Correction
–16048
Explanation
Correction
432
A CREATE PIPELINE statement has failed.
A UNIX-format CREATE PIPELINE statement was used on Windows.
Find the CREATE PIPELINE statement and make sure that the statement
includes the OUTPUT IS clause.
A Row ID is required for the current database operation.
An attempt was made to perform an interactive insert, update, or delete
operation on the form’s target table when the target table has nothing that
can be used as a row ID.
Before an interactive operation can be allowed on this target table, you
must add a row ID. The row ID must uniquely identify each row in the
table.
Error Messages
Download PDF
Similar pages