Contents. Error Message Descriptions... 7

Transcription

1

2 2

3 Contents Error Message Descriptions

4 4

5 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

6 Once you have found the entry for your error message in the Error Message Descriptions, refer to the and sections. The section provides a more complete description of the condition that caused the error message. The section describes how to resolve the error condition. Some error message entries also have an section that refers to other manuals. If you follow the instructions in the and 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

7 +100 End of scan (or ordered access). 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. 0 No error occurred. No error occurred during the operation. 1 Internal inconsistency fatal. 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. 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. 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 Error Messages 7

8 3 Not enough shared memory; try increasing SHMMAX or decreasing SHMFULL. 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: Transaction manager Try these steps: Reduce the number of active transactions Lock manager File manager Reduce the number of locks Decrease the setting for the LMPROMO variable Commit transactions more frequently 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). Unify DataServer: Configuration Variable and Utility Reference 8 Error Messages

9 4 The database appears to be corrupted (is the root volume really a database?). 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. 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. Unify DataServer: Configuration Variable and Utility Reference Your operating system documentation 5 This feature is not implemented yet. A feature is not yet supported or implemented. Check the availability of RHLI features in the RHLI documentation. Unify DataServer: RHLI Reference 6 The software version does not match the database version. 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. 7 An invalid memory address was supplied as a parameter to an RHLI function. 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 Error Messages 9

10 8 Partial success; see the individual status list. 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 9 Invalid argument/options. An RHLI function received an invalid argument or option. Verify the parameters passed to the RHLI function. Unify DataServer: RHLI Reference 10 Valid, but no work was done. 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. Check the status list errors. Find the RHLI function causing the error and correct the offending list element. Unify DataServer: RHLI Reference 11 An interrupt has occurred. 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 10 Error Messages

11 12 Database file type mismatch possibly not a database file? 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. Unify DataServer: Configuration Variable and Utility Reference Your operating system documentation 13 Database file ID mismatch possibly wrong database version? 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. 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. Unify DataServer Installation documentation. 14 The $UNIFY configuration variable is not defined. 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 Error Messages 11

12 15 Invalid error code. 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. 16 The $UNIFY directory does not exist or is not accessible. 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. Unify DataServer: Configuration Variable and Utility Reference 17 The $UNIFY/unify.msg message file does not exist or is not accessible. 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. 18 Process terminated at user request (typically using shutdb utility). 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. 12 Error Messages

13 21 Not owner. 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. 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. 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. 23 There is no process with the specified process ID. A process has abnormally terminated. Check the errlog file for information. Search for any core files. 24 Interrupted system call. A system call was interrupted. This is an internal error and should not occur during normal operations. Call Customer Support if this error occurs. 25 I/O error. An I/O error has occurred. Since it is usually a hardware problem, user must resolve the situation independent of the database, usually. Error Messages 13

14 26 No such device or address. This is an internal error only and should not occur. If this error occurs, please call Customer Support. 27 The argument list is too long (Consult operating system manual for limit). This is an internal error and should not occur in the normal execution of the database. Check the error message documentation for error number 7 in your Unix system documentation. 28 Exec format error. This is an internal error and should not occur in the normal execution of the database. Check the error message documentation for error number 8 in your Unix system documentation. 29 Bad file descriptor. This is an internal error and should not occur in the normal execution of the database. Check the error message documentation for error number 9 in your Unix system documentation. 30 No children. 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. 14 Error Messages

15 31 No more processes. 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. 32 Not enough memory; try increasing SHMOFFSET. 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 33 Access permission denied on file. An attempt has been made to open a file or shared memory in a mode not allowed by the permissions on the file. 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. 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. Error Messages 15

16 35 Block device required. 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. 36 Object busy. Some internal resource is being used. Check the error message documentation for error number 16 in your Unix system documentation. 37 File already exists. 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. 38 Cross-device link. 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. 39 No such device. 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. 16 Error Messages

17 40 Not a directory. 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. 41 Object is a directory. 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. 42 Invalid OS function argument. 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. 43 File table overflow. 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. Error Messages 17

18 44 Too many file descriptors open (> operating system limit?) This sometimes indicates a problem attaching shared memory segments. 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. 45 Not a typewriter. 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. 46 Text file busy. 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. 47 File too large. 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. 18 Error Messages

19 48 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 system documentation. 49 Illegal seek. 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. 50 Read-only file system. 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. 51 Too many links. 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. 52 Broken pipe. 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. Error Messages 19

20 53 Generic operating system error. 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. 54 Not enough resources. 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. Unify DataServer: Configuration Variable and Utility Reference 55 End-of-file reached. An attempt has been made to read past the end of a database file. A file may have been truncated. 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. Your operating system documentation. 56 Partial read/write encountered. This is an internal error and should not occur in the normal execution of the database. If this error occurs, please call Customer Support. 20 Error Messages

21 57 The software version does not match the shared memory partition version. 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 58 The software version does not match the shared memory segment version. 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 59 Could not attach shared memory at required address. 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 Error Messages 21

22 60 The shared memory segment is already attached. This is an internal error and should not occur in the normal execution of the database. If this error occurs, please call Customer Support. 61 Could not create shared memory incorrect SHMKEY value? This is an internal error and should not occur in the normal execution of the database. If this error occurs, please call Customer Support. 62 Could not create a shared memory segment >= SHMMIN and <= SHMMAX. 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. Unify DataServer: Configuration Variable and Utility Reference 63 File synchronization failed. This is an internal error and should not occur in the normal execution of the database. If this error occurs, please call Customer Support. 22 Error Messages

23 64 A process has abnormally terminated while updating shared memory; database recovery using the irma utility is now necessary. 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 65 Cannot open or create the shared memory lock file ($SHMDIR/shmlk#####). 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 66 Specified processor ID does not exist. The processor specified in the PROCESSOR configuration variable does not exist. Set PROCESSOR to a valid processor ID. 67 Process is running on the wrong processor ID. A process called uopndb while running on the wrong processor. See information on migrate in Unify DataServer: Configuration Variable and Utility Reference. Error Messages 23

24 70 Executable is not licensed. 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. 71 Executable license has expired. Your license for this executable has expired. Contact Customer Support to renew your license. 72 Unable to determine current time. This is an internal error and should not occur in the normal execution of the database. If this error occurs, please call Customer Support. 73 Executable is not licensed for this machine. 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. 74 File seek error. 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. 24 Error Messages

25 75 Unable to install license. The license cannot be installed in the executable. Make sure that the license is being installed in the correct executable. 76 License installation error. 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. 77 Database Server unable to respond; too many users. The remote database cannot be opened because the Database Server is already servicing its licensed maximum number of users. 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. The input date value is invalid. Make sure that the specified value is in correct format and range. 81 No messages in specified range (user changed message file incorrectly?). 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. Error Messages 25

26 100 End of scan (or ordered access). UEEOSCN See error message Bad column count (exceeds maximum column limit). The specified number of columns in a column group must be greater than 0 and less than 9. Correct the number of component columns. 102 Invalid or conflicting options. The options specified for the RHLI function are invalid or contain conflicting values. Verify the options of the function. Unify DataServer: RHLI Reference 103 Invalid segment size specified. 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. 104 Invalid volume ID. 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 26 Error Messages

27 105 File may not be block-special file. 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. 106 No direct table key column specified. 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. 107 Invalid column type for direct table (must be type INTEGER [U_HINT]). 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. 108 Transaction-log is not a file (directory or pipe?). 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. 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

28 109 Transaction-log size is too small (should be at least MAXSYSTX blocks). The size of the database transaction log file (.lg suffix), as specified by the LOGBLK configuration parameter, is smaller than the minimum required size. 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. An attempt has been made to specify more than one primary key column or column group for a table. 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. 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. 112 No column group information specified. An attempt has been made to reference a column group explicitly. Use the column group s component columns instead. 28 Error Messages

29 113 Invalid database ID. 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. 114 Invalid direction specification. 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. 115 No database information specified. 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. 116 Invalid link ID. 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. Error Messages 29

30 117 No volume preference found. 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 118 No user information specified. 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. 119 No volume information specified. 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. 120 Column cannot be combination to itself. An attempt has been made to define a column group with a component column member that is also a column group. Make sure the component members of a column group do not reference other column groups. 121 Schema has been modified cannot open database. 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. Either relink the executable with uld or use ID mapping on the database. 30 Error Messages

31 122 Beginning-of-set reached. 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. 123 End-of-set reached. 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. 124 Volume appears to be active or in use. 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. 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). 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. Correct the volume specifications. Error Messages 31

32 126 Bad volume group ID. An attempt has been made to specify a negative value for a Unix group ID. For information on how to specify Unix group IDs, see your operating system manuals. 127 Bad volume length. 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. 128 Bad volume access mode (0777). 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. 129 Bad volume offset. 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. 32 Error Messages

33 130 Bad volume options. An attempt has been made to specify an invalid volume option. Verify the options on the volume creation statement or function. 131 Bad volume owner ID. 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. 132 Bad volume page size. 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. 133 Bad volume device type. 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. 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. 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. Error Messages 33

34 135 Invalid buffer index (file too small). 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. 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. An attempt has been made to specify a negative value as the expected number of rows for a table. 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. 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. 138 Unknown TEXT/BINARY update mode. An attempt has been made to specify a text or binary operation mode that is invalid. Verify the operation. 34 Error Messages

35 139 Scan (or ordered access) ID is not found (Has the scan been closed?). An attempt has been made to reference a Scan ID that does not exist. 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. 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. 141 Unable to back out operation fatal. 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. 142 Fatal error in B-tree access; rebuild. 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. 143 Error opening B-tree. 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. Error Messages 35

36 144 Combination group 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. 145 Expected a column group, but columns are not members of any column group. 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. 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. 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. 147 Invalid column type. 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. 36 Error Messages

37 148 Data value 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 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. 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. 150 The column data type internal length is larger than maximum 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 you are using. 151 Database already opened. 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. Error Messages 37

38 152 Unknown column type. 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). 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. 154 Duplicate column in column group list. An attempt has been made to create a column group have component member columns with duplicate Column IDs. 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. 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 38 Error Messages

39 156 Duplicate table ID. An attempt has been made to create a link between the same table. Links must exist between two different tables. Correct the link. 157 Invalid database name syntax. The database name string contains a format error. Verify that the correct separator characters are used and that all necessary separator characters are present. 158 Failed to create error log name. 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. 159 Failed to open error log file. An attempt to open the errlog file failed. The database system requires the errlog file. If this error occurs, please call Customer Support. 160 Denied access to file. 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. Error Messages 39

40 161 Failed 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 Customer Support. 162 File create error. 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. 163 File read error. 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. 164 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 of the database. If this error occurs, please call Customer Support. 165 File write error. 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. 40 Error Messages

41 166 Tried to free a nil UNIPCOLL structure pointer. 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. 167 Operation not allowed on tables with data. 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. 168 Bad hash table options (only unique hash tables supported currently). 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. 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. 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. 170 Invalid menu-line position (must be >= 1). 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. Error Messages 41

42 171 Link already exists on child column. 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. 172 Invalid list size specified; verify the count parameter. 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. 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. 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. 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. 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. 42 Error Messages

43 175 Too many scans (and/or ordered accesses) active at once. 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 176 Database Object Name is required. 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. 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. 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. 178 Invalid B-tree ID. 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. Error Messages 43

44 179 This program only operates on remote databases. A program that has been linked to access remote databases only is being used to open a local database. 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. 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). 181 Invalid column ID/not part of common table. 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 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. 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. 44 Error Messages

45 183 Not a column group. 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. 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. 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. 185 The row was NOT deleted. 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. 186 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 Customer Support. Error Messages 45