ALLBASE/SQL Message Manual HP 3000 MPE/iX Computer Systems Seventh Edition Manufacturing Part Number: 36216-90213 E0897 U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents 1. Introduction ALLBASE/SQL Message Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Types of Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 User Defined Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 How Messages are Returned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 4
Preface This manual explains the causes of warning and error conditions which may occur during the use of the following components of ALLBASE/SQL: SQL, ISQL, SQLUtil, the preprocessors, SQLMigrate, NET, or NETUtil as implemented on HP 3000 computers running under the MPE/iX operating system. It also presents actions to be taken in response to these warning and error conditions. ALLBASE/SQL is the basic component of Hewlett-Packard's relational database management system.
Table 1.
1 Introduction Information is returned to the user from ALLBASE/SQL in the form of messages, which are displayed when an unusual condition occurs in ISQL, SQLUtil, SQLAudit, SQLGEN, SQLMigrate, SQLMON, ALLBASE/NET, NETUtil, the preprocessors, or a user-written application program that contains ALLBASE/SQL commands.
Introduction ALLBASE/SQL Message Catalog ALLBASE/SQL Message Catalog Messages are stored in the ALLBASE/SQL message catalog, which must be installed on your system. The name of the message catalog is SQCTxxx.PUB.SYS, where xxx is the numeric representation of the current language. The default message catalog is SQLCT000.PUB.SYS. The default language is NATIVE-3000 (US ASCII). You can also use the following equation to specify a file that is a different group and account: : FILE SQLCT000.PUB.SYS = SomeFile.
Introduction Types of Messages Types of Messages This manual documents two basic types of messages: • Warning messages • Error messages Warning Messages Warning messages are followed by DBWARN and a number enclosed in parentheses. For example: Output will be truncated. (DBWARN 1) Warnings do not cause your program or command to be aborted, but the entire command or the incorrect part of the command is either ignored by ALLBASE/SQL or modified by ALLBASE/SQL so that command processing may continue.
Introduction User Defined Messages User Defined Messages Two statements permit you to create your own messages in ALLBASE/SQL procedures and applications: • RAISE ERROR • PRINT RAISE ERROR The RAISE ERROR statement permits users to define their own message catalogs. The number range 7000 - 7999 is reserved for use in RAISE ERROR. No errors in this range will be generated by ALLBASE/SQL. Each error caused by the RAISE ERROR statement is a regular error that generates a message placed in the message buffer.
Introduction How Messages are Returned How Messages are Returned Depending on the way you are using ALLBASE/SQL, messages will be returned in one of the following ways: • When you use ISQL, SQLUtil, SQLAudit, SQLGEN, SQLMigrate, SQLMON, ALLBASE/NET, or NETUtil interactively, messages are returned to the standard output, which is typically the terminal screen. These messages appear immediately after ALLBASE/SQL encounters a problem.
Introduction Understanding Message Manual Entries Understanding Message Manual Entries Messages are presented in numerical order.
Introduction Understanding Message Manual Entries CAUSE and ACTION for Messages Each message in this manual is followed by a CAUSE, which gives information as to why the warning or error occurred. This is followed by an ACTION, which gives information on how to resolve the problem, refers the user to an appropriate manual, or suggests contacting an HP Service Representative or the Response Center. For example: 13 MESSAGE ! not a column name in table !.
Introduction Using the HELP command Using the HELP command ISQL, SQLAudit, SQLGEN, SQLUtil, NETUtil, SQLMigrate, and SQLMON have HELP commands. The help facility can be used for basic information such as correct syntax for a specific command. For example: isql=> help info; ======================= ISQL INFO Command ======================= The INFO command displays definitions of the columns of a table or view. --- SYNTAX --INF[O] {[Owner.]TableName} {[Owner.]ViewName } --- EXAMPLE --INFO System.
Introduction Understanding Messages Returned from Remote Nodes Understanding Messages Returned from Remote Nodes If you are using ALLBASE/NET, you may receive error and warning messages from a version of ALLBASE/SQL running under an operating system that is different from the operating system of your local node. Although most ALLBASE/SQL error messages are similar across operating systems, there are significant differences in details for messages dealing with file names and user names.
Introduction Connecting to a DBEnvironment Connecting to a DBEnvironment Attempting a CONNECT may result in the display of several messages. When an application issues a command to connect to a DBEnvironment, ALLBASE/SQL first attempts a local connection. If one of the following conditions exists on the local node, ALLBASE/SQL attempts a remote connection: • There is no ALLBASE/SQL software on the local system.
Introduction Connecting to a DBEnvironment Figure 1-1.
Introduction Native Language Support Native Language Support If your system has the proper message files installed, ALLBASE/SQL displays prompts, messages and banners in the language you select; and it displays system dates and time according to local customs. In addition, ISQL accepts responses to its prompts in the native language selected. However, regardless of the native language used, the syntax of ISQL and SQL commands--including punctuation--remains in ASCII.
Introduction Using Other Manuals Using Other Manuals In some cases, you may want to refer to one of the following documents for additional information about ALLBASE/SQL: • All users should refer to the ALLBASE/SQL Reference Manual for in-depth information on basic ALLBASE/SQL terms and concepts, and to the ISQL Reference Manual for ALLBASE/SQL and IMAGE/SQL for information about interactive access to ALLBASE/SQL databases.
Introduction Using Other Manuals 20 Chapter 1
2 ALLBASE/SQL Warning Messages 1 2 3 4 MESSAGE Output will be truncated. (DBWARN 1) CAUSE The SELECT statement generated rows that are longer than the size specified by the PAGEWIDTH option of the SET command. The pagewidth may be set to a maximum of 254 bytes. ACTION Increase the pagewidth value using the ISQL SET command. MESSAGE File '!' already exists. Next SELECT will overwrite.
ALLBASE/SQL Warning Messages 5 6 7 8 9 10 11 12 22 MESSAGE BULK not allowed interactively - ignored. (DBWARN 5) CAUSE You issued a BULK SELECT or BULK FETCH option while in ISQL. ACTION Any SELECT performed in ISQL is automatically treated as a BULK SELECT. BULK is an option for programming with SQL only. Refer to the ALLBASE/SQL Reference Manual for additional information. MESSAGE Transaction terminated. (DBWARN 6) CAUSE EOF was reached on input file.
ALLBASE/SQL Warning Messages (DBWARN 12) 13 14 15 16 17 18 Chapter 2 CAUSE The starting row number specified in the LOAD PARTIAL command was beyond the last line of the file. No rows were loaded. ACTION Issue the LOAD command again, specifying an appropriate starting row. MESSAGE Number of rows specified exceeds number in load file. (DBWARN 13) CAUSE The number of rows specified in the LOAD PARTIAL command was greater than the number of rows between the starting row and the end of the file.
ALLBASE/SQL Warning Messages last byte of a field is the first byte of a two-byte character. 19 20 21 22 23 24 25 24 ACTION Delete the rows loaded. Issue the LOAD command again, specifying field boundaries that coincide with character boundaries. MESSAGE Unable to upshift native language string. (DBWARN 19) CAUSE ISQL was unable to upshift a character string, probably because the string contains one or more invalid bytes. ACTION Issue your command again, specifying valid input.
ALLBASE/SQL Warning Messages 232 233 234 235 236 Chapter 2 CAUSE The ISQL welcome file corresponding to your language cannot be accessed, probably because it does not exist. ACTION Contact your system administrator. MESSAGE ! conversion error on line !, column !. (DBWARN 232) CAUSE There is a problem converting Date, Time, DateTime, or Interval field to internal format when trying to load the data from an external data file.
ALLBASE/SQL Warning Messages when an outfile is specified with the OUTPUT option of the ISQL SET command and more rows qualify for the SELECT than can be viewed within ISQL. The outfile will hold all the rows that can be viewed within ISQL. 302 502 506 522 523 26 ACTION If all the rows of data need to be viewed, use the UNLOAD EXTERNAL command to unload the data to an ASCII file. MESSAGE File Device Full. (DBWARN 302) CAUSE Your storage medium (tape or disk) is full.
ALLBASE/SQL Warning Messages 525 528 MESSAGE Partition ! has no transactions to audit. (DBWARN 523) CAUSE No transaction information was found in the ending audit point for the given partition. This would be possible if no committed transactions have touched the partition, or the transaction information was removed through a hard resync. ACTION No action necessary. MESSAGE SET DBENVIRONMENT command has not been issued yet.
ALLBASE/SQL Warning Messages 705 706 707 711 712 713 714 28 CAUSE Entered prefix was an invalid length. ACTION Re-enter the prefix name with a length of 1 to 5 bytes. MESSAGE Unrecognized command. (DBWARN 705) CAUSE An unknown command was entered. ACTION Enter a valid SQLGEN command. MESSAGE No help for that command. (DBWARN 706) HELP keywords are GENERAL, MAIN, OBJECT, and SUMMARY. Type '//' to leave SQLGEN HELP. CAUSE An unrecognized command was entered for HELP.
ALLBASE/SQL Warning Messages Default null indicator used instead. 715 716 717 718 719 721 Chapter 2 CAUSE An invalid null indicator was entered. ACTION The default null indicator "?" was used. No additional user response is necessary. MESSAGE User needs to have DBA authority to use SQLGEN. (DBWARN 715) Terminating the DBE session. CAUSE User does not have DBA authority to the DBEnvironment. ACTION Before using SQLGEN, the user must obtain DBA authority. MESSAGE No SQL commands generated.
ALLBASE/SQL Warning Messages execution. 722 723 724 725 730 731 732 30 MESSAGE File name is required to start with a letter. (DBWARN 722) CAUSE You did not begin the file name with a letter. ACTION Begin your file name with a letter. MESSAGE Illegal character encountered in file name. (DBWARN 723) CAUSE An illegal character was entered in the file name. ACTION Re-type the file name without the illegal character. MESSAGE Designated Schema File has been purged from system.
ALLBASE/SQL Warning Messages 733 736 1681 1800 1801 1802 1803 Chapter 2 ACTION Exit SQLGEN. Set your NLUSERLANG job control word to match the DBEnvironment language, then invoke SQLGEN. MESSAGE SQLGEN cannot be used on remote DBEnvironments. (DBWARN 733) CAUSE SQLGEN cannot access remote DBEnvironments. ACTION Do not execute SQLGEN on a remote DBEnvironment. MESSAGE No Users qualify for specified generate command. (DBWARN 736) CAUSE No users had the authority for the specified command.
ALLBASE/SQL Warning Messages 1804 1805 1806 1807 1808 2005 32 CAUSE Identifier exceeds maximum allowed in ANSI SQL/89 standard. ACTION Do not use this identifier length if portability is a concern. MESSAGE Use of multiple DISTINCTs within a query or subquery is a non-standard extension. (DBWARN 1804) CAUSE Allowing multiple distincts in a query or subquery is an ALLBASE/SQL extension to the ANSI SQL/89 standard. ACTION Do not use this statement if portability is a concern.
ALLBASE/SQL Warning Messages 2006 2007 2008 2010 2011 2012 Chapter 2 MESSAGE User ! already has ! authorization. (DBWARN 2006) CAUSE You tried to grant an authorization to a user that already has that authorization. ACTION No action is necessary MESSAGE User ! already has ! authorization on !.!. (DBWARN 2007) CAUSE You tried to grant authority on a table or a module to a user that had already been granted authority on the specified table or module.
ALLBASE/SQL Warning Messages 2014 2015 2016 2017 MESSAGE Module !.! not found. (DBWARN 2014) CAUSE The module specified in the EXECUTE or DROP MODULE statement does not exist. ACTION Check your spelling. Ask your database administrator to check the SYSTEM.SECTION view to make sure that the module exists in the DBEnvironment to which the application is connected. MESSAGE Row size of table !.! exceeds ! bytes.
ALLBASE/SQL Warning Messages 2019 2020 2022 2023 Chapter 2 ACTION No action is necessary as long as the actual length of the VARCHAR data does not cause the maximum key length to be exceeded. The key length is determined using the actual data length in the VARCHAR column. If the maximum key length is exceeded, an error will occur when the hash structure is accessed. MESSAGE ASCII definition of view !.! not available for storage.
ALLBASE/SQL Warning Messages 2025 2026 2027 2028 2029 2040 36 ACTION Ignore the warning, or MOVE the DBEFile to a desired device using SQLUtil. MESSAGE User ! has no grantable authority on !.!. (DBWARN 2025) CAUSE You issued a GRANT ALL statement but have no Owner or DBA authority and have no grantable privileges on the table. Nothing was granted. ACTION No action required. MESSAGE REVOKE CASCADE has dropped a view or foreign key.
ALLBASE/SQL Warning Messages 2041 2042 2043 2044 2045 2046 Chapter 2 CAUSE A host variable character string was shorter than a character column in the select list. ACTION Check the string returned to see if it needs to be longer in order to capture all necessary information from the column. If so, modify the declaration of the datatype. MESSAGE NULL values eliminated from the argument of an aggregate function.
ALLBASE/SQL Warning Messages 2050 2051 2052 2053 38 CAUSE Result length of string concatenation exceeds the maximum. ACTION No action needed. MESSAGE LONG column data exceeds defined length. Truncated. (DBWARN 2050) CAUSE The actual long column data is longer than the defined length. The long column data was truncated. ACTION No action is necessary. MESSAGE LONG column data exceeds output file size. Truncated.
ALLBASE/SQL Warning Messages 2054 2056 2059 2060 2061 2062 Chapter 2 MESSAGE Sort length of sort merge join may exceed maximum allowed ! bytes. (DBWARN 2054) CAUSE The sort merge join query specifies a number of columns whose total sort tuple length exceeds the maximum allowable and contains a VARCHAR column. ACTION No action is necessary as long as the length of the VARCHAR data does not cause the maximum sort tuple length to be exceeded.
ALLBASE/SQL Warning Messages 2063 2065 2066 2067 2068 2069 40 ACTION Check and correct the specified partition ids. MESSAGE Some partitions (but not all) failed on Open_Log_Scan. (DBWARN 2063) CAUSE Open_Log_Scan failed to open the scan for some of the specified partitions. ACTION Check the per partition return codes. MESSAGE DML ATOMICITY already set to ! level. (DBWARN 2065) CAUSE The DML ATOMICITY is already set to row or statement level.
ALLBASE/SQL Warning Messages substring returned is shorter than expected and that truncation may occur. 2070 2071 2072 2073 2074 2075 Chapter 2 MESSAGE The transaction was committed, since it is read only. (DBWARN 2070) CAUSE The transaction that was being prepared for COMMIT was found to have no associated updates. The transaction was therefore committed. ACTION No action needed. MESSAGE The transaction was aborted due to deadlock.
ALLBASE/SQL Warning Messages you have validated the module successfully in this manner, you will then be able to use the VALIDATE statement on this module. 2076 2077 2078 2079 2080 2081 2082 42 MESSAGE Failed to validate module !.!. (DBWARN 2076) CAUSE The module specified does not exist. ACTION Check module name in the SYSTEM.SECTION view or with the ISQL LIST INSTALL command. MESSAGE Failed to validate module !.!.(!). (DBWARN 2077) CAUSE An error occurred during validation process.
ALLBASE/SQL Warning Messages 2083 2084 2085 2087 2090 2091 2092 Chapter 2 ACTION If this warning is accompanied by DBERR 2237, check your spelling. Otherwise, the superfluous label may be removed. MESSAGE Multiple rows returned in procedure. (DBWARN 2083) CAUSE A non-cursor SELECT in a procedure returned multiple rows. Only the first row of values was returned in the local variables or parameters. ACTION Use a cursor in procedures for any query that will return more than one row of data.
ALLBASE/SQL Warning Messages DISABLE RULES statement was issued. 2093 2094 2095 2096 2097 2098 2344 44 ACTION No action is necessary. MESSAGE Rules already enabled. (DBWARN 2093) CAUSE ENABLE RULES statement was in effect when this ENABLE RULES statement was issued. ACTION No action is necessary. MESSAGE PRINTRULES already ON. (DBWARN 2094) CAUSE SET PRINTRULES ON statement was in effect when this SET PRINTRULES ON statement was issued. ACTION No action is necessary.
ALLBASE/SQL Warning Messages 2345 2531 2880 3230 3231 3232 3233 5000 Chapter 2 ACTION No action required. MESSAGE User ! already has general INSTALL authority. (DBWARN 2345) CAUSE You granted INSTALL authority to a user who already has the authority. ACTION No action required. MESSAGE Cursor, associated with the aborted query has been closed. (DBWARN 2531) CAUSE The cursor has been closed. ACTION No action required for the closed cursor. Check the aborted query.
ALLBASE/SQL Warning Messages argument of a procedure's PRINT statement back to the procedure caller. 8001 8002 8003 8004 8005 8006 46 ACTION Take whatever action is recommended by the procedure writer. MESSAGE Unable to load all local response options. (DBWARN 8001) CAUSE One or more of the local response options was missing from the message catalog or response contained invalid data. ACTION Contact your system administrator. MESSAGE Local response options are not unique.
ALLBASE/SQL Warning Messages language. 8007 8248 10600 10601 10603 10604 10605 Chapter 2 MESSAGE Local message catalog is not available. Set to ! message catalog. (DBWARN 8007) CAUSE The message catalog file corresponding to your language cannot be accessed, probably because it does not exist. ACTION Contact your system administrator. MESSAGE Maximum Log files exceeded, last log name ignored.
ALLBASE/SQL Warning Messages the DBEnvironment are different. 10606 10607 10608 10609 10610 10611 48 ACTION Set NLUSERLANG to the proper language, if using native data. MESSAGE Native version of ALLBASE/SQL message catalog not accessible. (DBWARN 10606) CAUSE The native version of SQLCTxxx.PUB.SYS was not found. ACTION Install native message catalog, if required. MESSAGE Program name exceeds maximum module name length. Truncated to 20 bytes.
ALLBASE/SQL Warning Messages 10612 10613 10614 10621 10622 10700 10701 Chapter 2 MESSAGE Native version of ALLBASE/SQL message catalog not accessible. (DBWARN 10612) CAUSE The native version of the SQLCTxxx.PUB.SYS message catalog was not found. ACTION Install the native message catalog. MESSAGE User's and DBE's languages are different. (DBWARN 10613) CAUSE The NLUSERLANG job control word and the language of the DBEnvironment are different. ACTION Set NLUSERLANG to the proper language.
ALLBASE/SQL Warning Messages 10750 10979 10980 13026 13343 20010 50 CAUSE A word appears in the COBOL source file which is longer than the maximum allowed length of 30 bytes. ACTION Modify the source file to shorten the word to a length of 30 bytes or less. MESSAGE 'INCLUDE SQLCA' is not declared for embedded SQL statement. (DBWARN 10750) CAUSE You did not include an SQLCA common area in your program.
ALLBASE/SQL Warning Messages catalog in use. (DBWARN 20010) 20011 20014 20300 20550 Chapter 2 CAUSE The ALLBASE/SQL message catalog corresponding to your language cannot be accessed, probably because it does not exist. ACTION Contact your system administrator. MESSAGE *** Bad JOB CONTROL WORD MIGLOGSZ. Default size used.
ALLBASE/SQL Warning Messages 20570 20580 20650 52 ACTION If you have not made a complete backup of the DBEnvironment, type No at the prompt to prevent SQLMigrate from continuing. Make a full backup of the DBEnvironment, and then issue the MIGRATE or PREVIEW command again. MESSAGE WARNING - Table !.! contained the following columns which are not supported under the target release of ALLBASE/SQL. (DBWARN 20570) CAUSE A backward migration was in progress when this message was issued.
ALLBASE/SQL Warning Messages 20660 20670 20680 20690 Chapter 2 MESSAGE WARNING - Table !.! has been created using INTEGRITY CONSTRAINTS, which is not supported under the target version of ALLBASE/SQL (DBWARN 20660). This table is being dropped. CAUSE A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.
ALLBASE/SQL Warning Messages was issued. User data which takes advantage of functionality that is not present in the target release has been detected. 20700 20754 22530 22620 54 ACTION If you need to recover the table, the backup version of the DBEnvironment must be restored. If you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command. MESSAGE WARNING - INDEX has been defined on sixteen (16) columns. (DBWARN 20700). Index ! defined on table !.! is being dropped.
ALLBASE/SQL Warning Messages 22630 22640 22650 22670 Chapter 2 CAUSE A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected. ACTION If you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command. MESSAGE WARNING - Table !.! has been created using INTEGRITY CONSTRAINTS, which is not supported under the target version of ALLBASE/SQL (DBWARN 22630).
ALLBASE/SQL Warning Messages Index ! defined on table !.! will be dropped during the migration. 22690 22695 22700 56 CAUSE A backward migration was PREVIEWED when this message was issued. In the target release, the maximum number of columns on which an index may be defined is fifteen (15). Functionality that is not present in the target release has been detected. ACTION After migration to the target release, recreate the dropped index using fewer columns. MESSAGE WARNING - View !.
ALLBASE/SQL Warning Messages 22710 22720 22730 22740 Chapter 2 MESSAGE WARNING - View !.! is defined on a table or view that is being dropped (DBWARN 22710). This view is also being dropped. The SELECTSTRING from SYSTEM.VIEWDEF for this view is: ! CAUSE A MIGRATE command was in progress when this message was issued. The view is being dropped because a structure that it is dependent upon is being dropped.
ALLBASE/SQL Warning Messages (DBWARN 22740). ObjectDB is not supported under the target version of ALLBASE/SQL. This table/view will be dropped during the migration. 22750 22760 58 CAUSE A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected. ACTION If the object is a table and you need to transfer this data to the target release, use the ISQL UNLOAD EXTERNAL command.
ALLBASE/SQL Warning Messages CATALOG will be created during the START DBE command under the target version of ALLBASE/SQL.
ALLBASE/SQL Warning Messages 22900 22910 22920 22930 60 MESSAGE WARNING - Procedure !.! has been detected in the system catalog (DBWARN 22900). Procedures are not supported under the target version of ALLBASE/SQL, so this information will be dropped during the migration. CAUSE A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected. ACTION No action is necessary.
ALLBASE/SQL Warning Messages was issued. User data which takes advantage of functionality that is not present in the target release has been detected. 22940 22950 22960 Chapter 2 ACTION No action is necessary. MESSAGE WARNING - Module !.! is owned by user HPODBSS, and is assumed to be part of the ObjectDB product (DBWARN 22940). ObjectDB is not supported under the target version of ALLBASE/SQL. This module will be dropped during the migration.
ALLBASE/SQL Warning Messages been detected. 22970 23020 23030 23040 62 ACTION Use the SQLUtil MOVEFILE command to move this DBEFile into a mapped file before attempting the migration. MESSAGE WARNING - DBEFile ! in DBEFileSet ! is a pseudo-mapped file, which is not supported under the target version of ALLBASE/SQL (DBWARN 22970). The MPE/iX filename for this DBEFile is !. CAUSE A backward migration was in progress when this message was issued.
ALLBASE/SQL Warning Messages result set (DBWARN 23040). In other words, the procedure includes at least one SELECT statement with no INTO clause. This feature is not supported under the target version of ALLBASE/SQL, so this procedure will be dropped during the migration. 23050 23060 Chapter 2 CAUSE A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected.
ALLBASE/SQL Warning Messages 23070 23080 23090 23100 64 MESSAGE WARNING - Table !.! has more than 255 columns, which is not supported under the target version of ALLBASE/SQL(DBWARN 23070). This table is being dropped. CAUSE A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected. ACTION No action is necessary.
ALLBASE/SQL Warning Messages ALLBASE/SQL (DBWARN 23100). 23120 23130 23150 Chapter 2 CAUSE A backward migration was PREVIEWED when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected. ACTION SQLMIGRATE will not perform a migration on the DBEnvironment if this DBEFILE remains in this group.account when the MIGRATE command is issued. Use the SQLUtil MOVEFILE command to move this DBEFile into the same group.
ALLBASE/SQL Warning Messages 29007 33002 34073 66 CAUSE A backward migration was in progress when this message was issued. User data which takes advantage of functionality that is not present in the target release has been detected. ACTION You must use the ISQL EXTRACT and INSTALL commands to move these sections into the SYSTEM DBEFileSet before a migration can be attempted. MESSAGE Local database connection failed with DBERR !. Remote access attempted.
ALLBASE/SQL Warning Messages 34074 34075 Chapter 2 ACTION If you need the limit increased, please contact your HP Service Representative or Response Center. MESSAGE Number of indexes exceeds internal maximum (max=!) (DBWARN 34074) CAUSE In shared memory, B-tree index ids are represented by TIDs. During the SET DBENVIRONMENT command, SQLMON reads from SYSTEM.INDEX and SYSTEM.CONSTRAINT to obtain information that maps each B-tree TID to an OWNER.TABLE/INDEX name.
ALLBASE/SQL Warning Messages 34078 34095 34096 34097 34098 68 MESSAGE Number of referential constraints exceeds internal maximum (max=!) (DBWARN 34078) CAUSE In shared memory, referential constraint (PCR) ids are represented by TIDs. During the SET DBENVIRONMENT command, SQLMON reads from SYSTEM.CONSTRAINT to obtain information that maps each PCR TID to an OWNER.TABLE/CONSTRAINT name.
ALLBASE/SQL Warning Messages 34400 34402 34403 34404 34405 Chapter 2 ACTION No action required if 24 is acceptable. MESSAGE Specified lock is not currently held by any users. (DBWARN 34400) CAUSE The LOCK OBJECT screen was being accessed when this message was displayed. The table, page, or row that you specified is not locked. ACTION No action is necessary. Check that you specified the correct lock object. MESSAGE CID not connected to the DBEnvironment.
ALLBASE/SQL Warning Messages in mind that the information displayed may represent locks from two different transactions. 34406 34500 34505 34510 34511 70 MESSAGE Lock information changed while collecting data! (DBWARN 34406) CAUSE The LOCK OBJECT screen was being accessed when this message was displayed. To minimize performance degradation of the DBEnvironment, SQLMON itself never hold locks or latches in the LOCK subsystem; it essentially performs "dirty" reads to collect data.
ALLBASE/SQL Warning Messages displays the transaction limit, and the ACTIVE XACT field displays the current number of active transactions. You may wish to use the SQLUtil ALTDBE command to increase the transaction limit. Also, use the SET command to check the current value of the USERTIMEOUT variable, which specifies the number of seconds that SQLMON will wait before timing out. You may wish to use the SET USERTIMEOUT command to increase the value, and then issue your original command again.
ALLBASE/SQL Warning Messages 34521 34580 72 CAUSE In shared memory, DBEFile ids are represented by integers. During the SET DBENVIRONMENT command, SQLMON normally reads from SYSTEM.DBEFILE to obtain information that maps each integer to a DBEFile name. Because of some error, SQLMON is not able to read from SYSTEM.DBEFILE. Therefore, DBEFile names will be displayed as integers, instead of strings. ACTION Resolve the error, and try again.
3 ALLBASE/SQL Error Messages: 1-745 1 2 MESSAGE Command buffer currently empty. (DBERR 1) CAUSE You issued a RECALL [CURRENT], CHANGE, or START command before any commands had been stored in the command buffer. ACTION Use the HOLD, RECALL FILE, or RECALL HISTORY command to put information into the command buffer. MESSAGE Problem with large command. Maximum length is !.
ALLBASE/SQL Error Messages: 1-745 6 7 8 11 12 13 74 CAUSE The number of copies you specified in the browse PRINT option must be in the range of 1 to 20. ACTION Issue the PRINT command again, specifying a value from 1 through 20. MESSAGE Error when using FCOPY. Code = !. Copies printed is !. (DBERR 6) CAUSE FCOPY is used by ISQL when the PRINT option is specified. An error has occurred and an FCOPY error code has been returned.
ALLBASE/SQL Error Messages: 1-745 14 15 17 18 19 20 21 Chapter 3 MESSAGE '!' is not acceptable as a name for a stored command. (DBERR 14) CAUSE The name you specified for a command file did not conform to operating system specifications. The command was not stored. ACTION Refer to the MPE/iX General User's Reference Manual for file naming conventions. MESSAGE '!' is not acceptable as a file name.
ALLBASE/SQL Error Messages: 1-745 discontinued. An additional error message will be returned. 27 28 29 30 31 32 76 ACTION Refer to the cause and action of the additional error. MESSAGE No column selected from table !. (DBERR 27) CAUSE You did not specify a column name in the LOAD command. ACTION Issue the LOAD command again, specifying a column name. MESSAGE History number must be in the range 1..!.
ALLBASE/SQL Error Messages: 1-745 33 34 35 36 37 38 Chapter 3 CAUSE The option value you specified for the AUTOCOMMIT, CONTINUE, or ECHO option of the SET command was not a valid option. ACTION Issue the command again, specifying a valid option. Refer to the ISQL Reference Manual for ALLBASE/SQL and IMAGE/SQL for additional information on the SET command. MESSAGE Invalid command. (DBERR 33) CAUSE The command you entered while viewing the results of a SELECT statement was not valid.
ALLBASE/SQL Error Messages: 1-745 1 for an explanation of the error code returned. 39 40 MESSAGE File '!' already exists. (DBERR 39) CAUSE The file name you specified to RENAME a file already exists. ACTION If you do not want to overwrite the existing file, reenter the RENAME command specifying a unique file name. Otherwise, either use the ERASE command to remove the existing file or use the RENAME command to rename the existing file first. MESSAGE Error attempting to rename '!' to '!'.
ALLBASE/SQL Error Messages: 1-745 44 45 46 47 49 ACTION Issue the command again, specifying a numeric value. MESSAGE Invalid option. (DBERR 44) CAUSE The option you specified in the SET command is not one of the valid options. The command is aborted and no option is set. ACTION Issue the command again, specifying a valid option.
ALLBASE/SQL Error Messages: 1-745 line. ACTION Correct the command file so that all commands are terminated with a semicolon (;) or reissue the commands which were not executed. 50 51 52 53 54 55 80 MESSAGE Fraction length must be in the range 0..18 (DBERR 50) CAUSE The fraction length you specified in the FRACTION option of the SET command was not within the acceptable range. The fraction length was not changed. ACTION Issue the command again, specifying a fraction length between 0 and 18.
ALLBASE/SQL Error Messages: 1-745 56 57 58 60 61 62 63 Chapter 3 CAUSE Internal error. ACTION Record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE Output file name must be no more than ! bytes. (DBERR 56) CAUSE The output file name you specified in the command is not a valid system file name. ACTION Refer to the MPE/iX Error Message Manual, Volume 1 for additional information on file naming conventions.
ALLBASE/SQL Error Messages: 1-745 64 66 67 69 73 74 82 CAUSE Internal error. ACTION Record the code returned and as much information as possible. Contact your HP Service Representative or Response Center. MESSAGE Semantic error. (DBERR 64) CAUSE An additional message will be returned. ACTION Refer to the cause and action of the additional error message. MESSAGE Name of editor must not be more than ! bytes.
ALLBASE/SQL Error Messages: 1-745 76 77 ACTION Issue the command again, specifying only valid options. Refer to the ISQL Reference Manual for ALLBASE/SQL and IMAGE/SQL for valid options and additional information on the SET command. MESSAGE End of file encountered on input. (DBERR 76) CAUSE You reached EOF on standard input. The program was terminated. ACTION No action is necessary. MESSAGE Could not schedule !.
ALLBASE/SQL Error Messages: 1-745 CAUSE The input file name you specified in the LOAD command was not unloaded with the INTERNAL option or the file name you specified does not exist or was entered incorrectly. ACTION Issue the LOAD command again, specifying the EXTERNAL option or check your spelling. Use the MPE/iX LISTF command to make sure that the specified file exists. 82 83 84 85 86 84 MESSAGE Unidentified error ! occurred on last command. (DBERR 82) CAUSE Internal error.
ALLBASE/SQL Error Messages: 1-745 subcommands of the REDO command are invalid. 87 88 89 90 91 92 Chapter 3 ACTION Issue the REDO command again. Refer to the ISQL Reference Manual for ALLBASE/SQL and IMAGE/SQL for additional information on the REDO command. MESSAGE Must break line - too long. (DBERR 87) CAUSE The bytes you added to the command using the insert subcommand of the REDO command caused the line to be greater than the maximum limit of 80 bytes.
ALLBASE/SQL Error Messages: 1-745 93 94 ACTION No action is necessary. An installation was not required to run this application. MESSAGE Empty installation file. (DBERR 93) CAUSE The installation file you specified is empty. ACTION No action is necessary. MESSAGE Installation stopped due to error. (DBERR 94) CAUSE The file name you specified in the INSTALL command was not a valid file name or the file you specified is currently being accessed by another user.
ALLBASE/SQL Error Messages: 1-745 150 151 ACTION Refer to the cause and action of the additional error message. MESSAGE Invalid character for null indicator. (DBERR 150) CAUSE The character you specified for the null indicator in the LOAD or UNLOAD EXTERNAL command was invalid. ACTION Issue the command again, specifying any single one-byte character for the null indicator except a single quote, double quote, semi-colon, blank, or the current escape character.
ALLBASE/SQL Error Messages: 1-745 177 193 201 202 211 212 88 CAUSE The command you specified can only be used in an application program. ACTION Refer to the ALLBASE/SQL Reference Manual for additional information on the specified command. MESSAGE SELECT cannot be preprocessed interactively with PREPARE. (DBERR 177) CAUSE You tried to PREPARE a SELECT statement interactively. ACTION You can either PREPARE a SELECT programmatically or issue the SELECT statement directly or in a command file.
ALLBASE/SQL Error Messages: 1-745 information as possible and contact your HP Service Representative or Response Center. 213 214 215 216 217 218 219 Chapter 3 MESSAGE Insufficient file space on disc(s). (DBERR 213) CAUSE There is not enough file space on the disk(s) to complete the transaction. ACTION Contact your system administrator. MESSAGE Account does not exist. (DBERR 214) CAUSE The account name you specified does not exist. ACTION Check your spelling.
ALLBASE/SQL Error Messages: 1-745 220 221 222 MESSAGE Security violation, permission denied. (DBERR 220) CAUSE You do not have the required capability for the operation attempted. ACTION Contact your system administrator to get the required capability. MESSAGE User lacks save files (SF) capability. (DBERR 221) CAUSE The command you tried to execute requires SF capability.
ALLBASE/SQL Error Messages: 1-745 224 230 231 237 238 250 251 Chapter 3 MESSAGE File '!' record length is too short. (DBERR 224) CAUSE You tried to UNLOAD with the INTERNAL option to an existing file, but the file record length was shorter than the length of the tuples to be unloaded. ACTION Either increase the record length of the existing file or enter the UNLOAD command again, specifying a different file name. MESSAGE Total output width exceeds maximum of !.
ALLBASE/SQL Error Messages: 1-745 252 253 256 257 263 284 300 301 92 ACTION Refer to the MPE/iX Error Message Manual, Volume 1 for a brief explanation of the error code returned. MESSAGE Seek failed on file '!'. (! !). (DBERR 252) CAUSE An MPE/iX file system error occurred. ACTION Refer to the MPE/iX Error Message Manual, Volume 1 for a brief explanation of the error code returned. MESSAGE LONG data types not allowed through UNLOAD INTERNAL.
ALLBASE/SQL Error Messages: 1-745 308 309 310 311 312 313 314 315 Chapter 3 CAUSE An MPE/iX file system error occurred. ACTION Refer to the MPE/iX Error Message Manual, Volume 1 for an error description. MESSAGE This command is not valid for FDA usage. (DBERR 308) CAUSE You specified an ISQL command that cannot be used when connected to a foreign database. ACTION No action necessary. MESSAGE Already connected. (DBERR 309) CAUSE You have already connected to the specified database.
ALLBASE/SQL Error Messages: 1-745 340 341 342 343 400 94 ACTION Issue the PREPARE statement again without the REPEAT option. MESSAGE Unsupported Format Type with CONVERT option. (DBERR 340) CAUSE The SET CONVERT option is not OFF, and the format type of the input file data specified in the LOAD command is not valid for the target ALLBASE/SQL column. ACTION Issue the LOAD command again with the correct format type.
ALLBASE/SQL Error Messages: 1-745 401 402 403 501 503 504 507 Chapter 3 ACTION Contact your system administrator. MESSAGE Delimiter must be a single-byte character. (DBERR 401) CAUSE You used a multi-byte character as the delimiter in a CHANGE command. ACTION Issue the CHANGE command again, using a single-byte character as the delimiter. MESSAGE Invalid replacement/insertion string.
ALLBASE/SQL Error Messages: 1-745 partition !. (DBERR 507) 508 512 513 514 515 96 CAUSE This error indicates that the log files have wrapped around and overwritten some of the committed transactions for the partition. If this is encountered, the specified partition will be dropped from the list of auditable partitions. ACTION To prevent this from happening, LOCK AUDITPOINT can be used to protect transactions committed after the beginning audit point is defined.
ALLBASE/SQL Error Messages: 1-745 517 519 520 521 524 526 Chapter 3 ACTION Check to make sure the file name used was correct. If the file name is correct, make sure the file and/or directory permissions are correct and that there is enough space to write the file. MESSAGE Native Language Support Error ! encountered. (DBERR 517) CAUSE A native language support (NLS) error was encountered by the last command.
ALLBASE/SQL Error Messages: 1-745 527 529 533 534 535 98 CAUSE The only way this should be possible is if the ending audit point was not generated on the database that is being audited. For instance, if the ending audit point was generated using a different database then used against the audited DBEnvironment, this type of situation can arise. ACTION Determine if the ending audit point file was actually generated against the DBEnvironment being audited.
ALLBASE/SQL Error Messages: 1-745 set. 701 702 703 704 706 707 708 Chapter 3 ACTION Check which editor is currently set (through the SET command). If the editor does not seem valid, change it through the SET EDITOR command. Also check to make sure it is possible to start the editor from outside SQLAudit. MESSAGE SQLGEN Error detected. SQLExplain messages will follow. (DBERR 701) CAUSE An unexpected ALLBASE/SQL error occurred.
ALLBASE/SQL Error Messages: 1-745 710 711 712 714 715 716 717 100 CAUSE An internal error has occurred. ACTION Record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE Invalid SQLType encountered. SQLType = !. (DBERR 710) CAUSE An invalid column type was encountered for one of the tables being described. ACTION Contact your database administrator. MESSAGE Error occurred while opening file.
ALLBASE/SQL Error Messages: 1-745 719 720 721 722 723 724 725 726 Chapter 3 CAUSE You may have entered an invalid editor name. ACTION Read system error messages to determine the cause of the error and take corrective actions. If error persists, contact your system administrator. MESSAGE Encountered ! ! while purging EXPSQLGN. (DBERR 719) CAUSE File system error occurred while purging the temporary file EXPSQLGN used during file expansion.
ALLBASE/SQL Error Messages: 1-745 726) 727 728 729 730 744 745 102 CAUSE A file system error occurred while moving data from the Schema File to the temporary file expsqlgn. ACTION Contact your system administrator. MESSAGE Error occurred while appending to file. (DBERR 727) CAUSE A file system error occurred while opening the Schema File in APPEND mode. ACTION Contact your system administrator. MESSAGE Encountered EOF on input file.
4 ALLBASE/SQL Error Messages: 746-2100 746 747 748 1001 1002 MESSAGE Invalid Constraint Index Type encountered. (DBERR 746) CAUSE Internal Error. ACTION Record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE Invalid Default Type encountered TYPE= (DBERR 747) CAUSE Internal Error. ACTION Record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE Invalid Constraint Type encountered.
ALLBASE/SQL Error Messages: 746-2100 choose a variable name that is less than or equal to 30 bytes. 1003 1004 1005 1006 1007 1008 1009 1010 104 MESSAGE Single-quoted string too long. (DBERR 1003) CAUSE The string enclosed in single quotes in your SQL statement is too long. ACTION Issue the command again, specifying a string which contains less than or equal to 3,996 bytes. MESSAGE Expected end of string character. (DBERR 1004) CAUSE String was not terminated with a quotation mark.
ALLBASE/SQL Error Messages: 746-2100 DBE NEW statement. 1011 1012 1013 1014 1015 1016 Chapter 4 ACTION Issue the START DBE NEW statement again, specifying the DBEFile0 only once. Refer to the ALLBASE/SQL Reference Manual for additional information on the START DBE NEW statement. MESSAGE Duplicate LOG DBEFile clause defined. (DBERR 1011) CAUSE You specified the LOG DBEFILE clause twice in the START DBE NEW or START DBE NEWLOG statement.
ALLBASE/SQL Error Messages: 746-2100 1017 1018 1019 1020 1021 1022 106 CAUSE The owner name you specified in the command(s) exceeds the 20-character maximum allowed for basic names. ACTION Issue the command again, specifying a valid owner name. Refer to the ALLBASE/SQL Reference Manual for naming conventions. MESSAGE Column number for ORDER BY must be greater than 0. (DBERR 1017) CAUSE The column number in the ORDER BY clause was less than or equal zero. The SELECT statement was aborted.
ALLBASE/SQL Error Messages: 746-2100 additional information on data data types. 1023 1024 1025 1026 1027 1028 Chapter 4 MESSAGE Duplicate tables in the FROM list. (DBERR 1023) CAUSE You specified the same table twice in the FROM clause of the statement. The statement was not executed. ACTION Issue the SELECT statement again, specifying each table only once. Refer to the ALLBASE/SQL Reference Manual for additional information on the SELECT statement.
ALLBASE/SQL Error Messages: 746-2100 1030 1031 1032 1038 1039 108 ACTION Modify the command specifying either an UPDATE clause or an ORDER BY clause, but not both. Refer to the ALLBASE/SQL Reference Manual for additional information on the DECLARE CURSOR statement. MESSAGE Host variables not allowed in CREATE VIEW. (DBERR 1030) CAUSE You specified a host variable in the SELECT statement of the VIEW command. ACTION Remove the host variable from the command.
ALLBASE/SQL Error Messages: 746-2100 1040 1041 1042 1043 1044 1045 Chapter 4 ACTION Revise your program to modify the host variable declarations and/or the INSERT statement references to host variables. Refer to the ALLBASE/SQL Reference Manual for additional information on the INSERT statement. MESSAGE User id is too long. (DBERR 1040) CAUSE The length of the DBEUserID you specified was not within the range of 1 through 20 bytes. ACTION Issue the command again, specifying a valid DBEUserID.
ALLBASE/SQL Error Messages: 746-2100 additional information. 1046 1047 1048 1049 1050 1051 1052 110 MESSAGE Failed to allocate heap space (DBERR 1046) CAUSE There was no memory available for your query. ACTION Report this error to your database administrator and try you again later. If the problem persists, record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE Failed to free heap space (DBERR 1047) CAUSE Internal error.
ALLBASE/SQL Error Messages: 746-2100 1053 1054 1055 1057 1058 1059 1060 Chapter 4 CAUSE An SQL statement contained an invalid Native Language Support (NLS) character. ACTION Check the NLS characters in the SQL statement and issue it again. MESSAGE Duplicate LANG clause defined. (DBERR 1053) CAUSE A command was issued with a duplicate LANG clause. ACTION Correct the command and issue it again. MESSAGE Invalid LANG specified.
ALLBASE/SQL Error Messages: 746-2100 disallowed. (DBERR 1060) 1061 1062 1063 1064 1065 112 CAUSE A CONSTRAINT clause was specified with a name starting with 'SQLCON_' in your CREATE TABLE or CREATE VIEW statement. ACTION Remove the CONSTRAINT clause or choose a different constraint name. MESSAGE The syntax PRIMARY KEY may only be used once in CREATE/ALTER TABLE. (DBERR 1061) CAUSE The syntax PRIMARY KEY appears more than once in your CREATE TABLE statement.
ALLBASE/SQL Error Messages: 746-2100 1066 1067 1068 1069 1071 1072 1073 Chapter 4 ACTION Remove the extra constraint(s); if more than one CHECK exists, the expressions within them can be ANDed together within a single CHECK. MESSAGE Illegal hexadecimal number specified. (DBERR 1066) CAUSE You specified non-hexadecimal characters for the BINARY/VARBINARY field. ACTION Refer to the chapter "Data Types" in the ALLBASE/SQL Reference Manual for proper syntax. MESSAGE Invalid location name.
ALLBASE/SQL Error Messages: 746-2100 aggregate function disallowed. (DBERR 1073) 1074 1075 1076 1077 1078 1079 1080 114 CAUSE You used a dynamic parameter as the argument of an aggregate function. ACTION Modify your statement to not use a dynamic parameter as the argument of an aggregate function. MESSAGE Two log files specified without DUAL LOG. (DBERR 1074) CAUSE You have specified two log files without also specifying DUAL LOG.
ALLBASE/SQL Error Messages: 746-2100 1081 1082 1083 1084 1085 1086 1088 Chapter 4 ACTION Check the specified START DBE statement. MESSAGE Duplicate MAXPARTITIONS clause defined. (DBERR 1081) CAUSE The keyword MAXPARTITIONS appears more than once in the START DBE NEW or START DBE NEWLOG clause. ACTION Check the specified START DBE statement. MESSAGE AUDIT LOG specified multiple times.
ALLBASE/SQL Error Messages: 746-2100 1089 1090 1091 1092 1093 1094 1095 116 MESSAGE Duplicate COMMENT PARTITION clause defined. (DBERR 1089) CAUSE You have more than one COMMENT PARTITION clause in the START DBE NEW or START DBE NEWLOG statement. ACTION Check the specified START DBE statement. MESSAGE Dynamic Parameters cannot be used as both the first and the second operands in a BETWEEN predicate.
ALLBASE/SQL Error Messages: 746-2100 ACTION Set the default timeout to a value less than or equal to the maximum timeout limit or set the maximum timeout limit to a value greater than or equal to the default timeout value. 1096 1097 1098 1099 1100 1101 Chapter 4 MESSAGE DEFAULT TIMEOUT specified multiple times. (DBERR 1096) CAUSE You specified the DEFAULT TIMEOUT clause more than once in either the START DBE, START DBE NEW, or STARTDBE NEWLOG statement.
ALLBASE/SQL Error Messages: 746-2100 found in the WITH clause of GENPLAN. 1102 1103 1104 1105 1106 1107 1108 118 ACTION Remove the language, default, or column clause from the WITH clause of GENPLAN. MESSAGE SQL Linearizer internal NLS error. (DBERR 1102) CAUSE Internal error. ACTION Record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE Duplicate VariableName found in the WITH clause of GENPLAN.
ALLBASE/SQL Error Messages: 746-2100 1109 1110 1111 1120 1121 1122 Chapter 4 CAUSE You specified a CHECK constraint with CURRENT_DATETIME. ACTION Remove the use of CURRENT_DATETIME in the CHECK constraint and reissue the statement. MESSAGE ! PARTITION value must be non-zero. (DBERR 1109) CAUSE You specified a DEFAULT, MAXPARTITIONS, or COMMENT partition value of zero in the START DBE NEW or START DBE NEWLOG statement.
ALLBASE/SQL Error Messages: 746-2100 integer value. 1123 1124 1125 1126 1127 1128 120 ACTION Use an integer value for the ReturnStatus in the RETURN statement. MESSAGE Indicator variables are not allowed with parameters or local variables used in a stored procedure statement. (DBERR 1123) CAUSE You attempted to include an indicator variable with a parameter declaration or with a local variable in the CREATE PROCEDURE statement.
ALLBASE/SQL Error Messages: 746-2100 this SQL statement in a stored procedure. (DBERR 1128) 1129 1130 1131 1132 1133 Chapter 4 CAUSE You used the SELECT, FETCH, or REFETCH statement inside a procedure without specifying a local variable or parameter. ACTION Reissue the CREATE PROCEDURE statement including the appropriate local variable or parameter along with the SELECT, FETCH, or REFETCH. MESSAGE OUTPUT option is allowed only for host variables in EXECUTE PROCEDURE.
ALLBASE/SQL Error Messages: 746-2100 1134 1135 1136 1137 1138 122 ACTION Check the SELECT portion of your DECLARE CURSOR statement to make sure there is no INTO clause, and reissue the CREATE PROCEDURE statement. Use the INTO clause in the FETCH statement. MESSAGE Local variable data type is invalid. (DBERR 1134) CAUSE You attempted to use a non-integer local variable or parameter in a SAVEPOINT, ROLLBACK WORK TO SAVEPOINT, or SET TIMEOUT statement in a procedure.
ALLBASE/SQL Error Messages: 746-2100 parameter, aggregate function, TID function, long column function, or date/time conversion function involving a column reference. 1139 1140 1141 1142 Chapter 4 ACTION Rewrite your EXECUTE PROCEDURE statement, eliminating the illegal element from the expression in the actual parameter. MESSAGE The OUTPUT option is not allowed for parameters that contain an expression in the EXECUTE PROCEDURE statement.
ALLBASE/SQL Error Messages: 746-2100 PROCEDURE statement, and ensure that you use a consistent parameter type in the parameter list. Then reissue the EXECUTE PROCEDURE statement. 1143 1144 1145 1146 1147 1150 124 MESSAGE Multiple values provided for single parameter in the EXECUTE PROCEDURE statement. (DBERR 1143) CAUSE You used the same parameter name more than once in a named parameter list in the EXECUTE PROCEDURE statement.
ALLBASE/SQL Error Messages: 746-2100 1151 1152 1153 1154 1155 1156 1157 Chapter 4 ACTION Check the syntax and remove the host variable from your CREATE RULE statement. MESSAGE Duplicate statement type specified in CREATE RULE. (DBERR 1151) CAUSE You defined a RULE with duplicate statement types. ACTION Check the syntax and remove the duplicate statement type from your CREATE RULE statement. MESSAGE TID function disallowed in CHECK constraint or RULE.
ALLBASE/SQL Error Messages: 746-2100 1158 1159 1160 1161 1163 1164 1165 126 ACTION Check the specified SET TRANSACTION or SET SESSION statement. MESSAGE Duplicate LABEL clause defined. (DBERR 1158) CAUSE You included more than one LABEL clause in the SET TRANSACTION or SET SESSION statement. ACTION Check the specified SET TRANSACTION or SET SESSION statement. MESSAGE Duplicate CONSTRAINTS clause defined.
ALLBASE/SQL Error Messages: 746-2100 1166 1167 1168 1169 1170 1171 1600 1601 Chapter 4 ACTION No action required. The duplicate USER TIMEOUT clause will be ignored. MESSAGE Duplicate on TIMEOUT/DEADLOCK clause defined. (DBERR 1166) CAUSE A duplicate TIMEOUT/DEADLOCK clause was specified. ACTION No action required. The duplicate TIMEOUT/DEADLOCK clause will be ignored. MESSAGE Duplicate TERMINATION clause defined. (DBERR 1167) CAUSE A duplicate TERMINATION clause was specified.
ALLBASE/SQL Error Messages: 746-2100 (DBERR 1601) 1602 1603 1604 1605 1606 1607 1608 128 CAUSE A file system error was encountered. ACTION Check the spelling of the DBEnvironmentName in the last command that was issued. Refer to the MPE/iX Error Message Manual, Volume 1 for an error description. MESSAGE Cannot close DBECON file. (! !, RC !, !, !) (DBERR 1602) CAUSE A file system error was encountered. ACTION Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.
ALLBASE/SQL Error Messages: 746-2100 1609 1610 1621 1622 1623 1624 1625 Chapter 4 ACTION Refer to the MPE/iX Error Message Manual, Volume 1 for an error description. MESSAGE Cannot close database or log file. (! !, RC !, !, !) (DBERR 1609) CAUSE A file system error was encountered. ACTION Refer to the MPE/iX Error Message Manual, Volume 1 for an error description. MESSAGE Cannot purge database or log file. (! !, RC !, !, !) (DBERR 1610) CAUSE A file system error was encountered.
ALLBASE/SQL Error Messages: 746-2100 1626 1629 1640 1680 1682 1683 130 CAUSE You attempted to either RESTORE a backup copy of a DBEnvironment or RESTORELOG a backup copy of a log file, but you provided an invalid name for the file or tape device containing the backup. ACTION Check your spelling. Issue the command again, specifying a valid StoreFileName. MESSAGE Security Violation. (RC !, !, !, !) (DBERR 1626) CAUSE You do not have the required capability for the operation that was attempted.
ALLBASE/SQL Error Messages: 746-2100 1684 1685 1686 1687 1688 1689 1690 1813 Chapter 4 MESSAGE Cannot close message catalog (!). (DBERR 1684) CAUSE An unexpected error was encountered when trying to close the ALLBASE/SQL message catalog. ACTION Contact your system administrator. MESSAGE Failed loading keyword (!). (DBERR 1685) CAUSE An unexpected error occurred while trying to obtain information from the ALLBASE/SQL message catalog.
ALLBASE/SQL Error Messages: 746-2100 1814 1815 2032 2033 2034 2035 2036 132 MESSAGE Conflict ! statements or conflict conditions on ! statement occur in SETOPT statement. (DBERR 1814) CAUSE ! statements or conditions on ! statement in SETOPT are conflicting. ACTION Remove incorrect ! statement or incorrect conditions from ACCESS statement and reexecute SETOPT and the query. MESSAGE WITH clause of GENPLAN is not allowed in the GENPLAN on a section.
ALLBASE/SQL Error Messages: 746-2100 Statements" chapter of the ALLBASE/SQL Reference Manual. 2100 Chapter 4 MESSAGE ALLBASE/SQL not running. (DBERR 2100) CAUSE An SQL statement was issued before a DBE session was started. ACTION Start a DBE session with the CONNECT or START DBE statement, then issue the SQL statement again.
ALLBASE/SQL Error Messages: 746-2100 134 Chapter 4
5 ALLBASE/SQL Error Messages: 2101-2419 2101 2102 2103 2105 2106 2107 MESSAGE ALLBASE/SQL already started. (DBERR 2101) CAUSE A START DBE or CONNECT statement was entered after a DBE session was already started. ACTION No action is necessary. MESSAGE Command requires a transaction to be in progress. (DBERR 2102) CAUSE A COMMIT WORK or ROLLBACK WORK statement was issued before a transaction was started. ACTION No action is necessary. To begin a transaction, issue a BEGIN WORK statement.
ALLBASE/SQL Error Messages: 2101-2419 2108 2109 2200 2201 2202 2203 2204 136 CAUSE The release of the ALLBASE/SQL software does not match the version of the DBEnvironment. ACTION Use the migration tool, SQLMigrate, to migrate the DBEnvironment forward to the proper version or use an older release of the ALLBASE/SQL software. MESSAGE DBEnvironment corrupted during previous migration.
ALLBASE/SQL Error Messages: 2101-2419 with the DBEFileSet named in the same command. 2205 2206 2207 2208 2209 2210 Chapter 5 ACTION Ask your database administrator to check the SYSTEM.DBEFILE view to verify which DBEFileSet the DBEFile is associated with. MESSAGE DBEFile ! already associated with DBEFileSet !. (DBERR 2205) CAUSE The ADD DBEFILE statement contained a DBEFile that is already a member of the DBEFileSet specified. ACTION No action is necessary. MESSAGE Table/View !.
ALLBASE/SQL Error Messages: 2101-2419 one table specified in the query. 2211 2212 ACTION Execute your query again, specifying the table name as well as the column name. MESSAGE Column ! not found. (DBERR 2211) CAUSE The column you specified in the query does not exist in any of the specified tables. ACTION Check your spelling. If you still receive this error ask your database administrator to check the SYSTEM.COLUMN view to make sure that the specified column does exist.
ALLBASE/SQL Error Messages: 2101-2419 modules. 2216 MESSAGE Module !.! not found. (DBERR 2216) CAUSE You tried to execute the OPEN CURSOR statement or the DROP MODULE statement on a non-existent section or the module in the DROP MODULE statement does not exist. 2218 2219 2220 2221 2222 Chapter 5 ACTION Check your spelling. If you still receive this error, ask your Database Administrator to check the SYSTEM.SECTION view to make sure that the module exists in the specified DBEnvironment.
ALLBASE/SQL Error Messages: 2101-2419 The same index name was used in creating indexes on two tables with the same owner. 2223 2224 2225 2226 2227 140 ACTION Use the syntax DROP INDEX IndexName FROM [Owner.] TableName to specify which table's index should be dropped. MESSAGE Index !.! not found. (DBERR 2223) CAUSE A non-existent index was specified in the DROP INDEX statement without an associated table. ACTION Check your spelling.
ALLBASE/SQL Error Messages: 2101-2419 2228 2229 2230 2231 Chapter 5 ACTION Make sure the AuthorizationName specified is neither an owner of existing objects in the DBEnvironment nor a grantor of authority on existing objects. To check ownership, query SYSTEM.TABLE and SYSTEM.GROUP. To check authorities, query SYSTEM.TABAUTH and SYSTEM.COLAUTH. MESSAGE Duplicate column ! found in joined table.
ALLBASE/SQL Error Messages: 2101-2419 (non-LONG) data type for each parameter. 2232 2233 2234 2235 2236 2237 2238 142 MESSAGE Duplicate parameter !. (DBERR 2232) CAUSE You specified a parameter name twice in the CREATE PROCEDURE statement. ACTION Issue the statement again, specifying unique parameter names. MESSAGE OUTPUT specified for a parameter not declared as OUTPUT. (DBERR 2233) CAUSE In the EXECUTE PROCEDURE statement, you specified OUTPUT for a non- OUTPUT parameter.
ALLBASE/SQL Error Messages: 2101-2419 condition in an IF or WHILE statement or the expression in a parameter or variable assignment. Procedure execution terminated. (DBERR 2238) 2239 2240 2241 2242 Chapter 5 CAUSE An error occurred in evaluating the condition or expression. ACTION Refer to the accompanying error message for additional information. MESSAGE Procedure !.! not found. (DBERR 2239) CAUSE The procedure you specified in the statement does not exist in the DBEnvironment.
ALLBASE/SQL Error Messages: 2101-2419 2243 2244 2245 2246 2247 144 MESSAGE Execution of procedure of !.! was invalidated. (DBERR 2243) CAUSE The procedure executed a statement that invalidated any further execution of the procedure, such as DROP PROCEDURE or TRANSFER OWNERSHIP of the procedure. ACTION Modify the procedure definition if you did not intend to invalidate the procedure during its execution. Otherwise, no action is required.
ALLBASE/SQL Error Messages: 2101-2419 2248 2249 2250 2251 2252 2253 2254 Chapter 5 ACTION Re-issue the OPEN command, omitting the KEEP option. MESSAGE The ADVANCE statement is allowed only for a procedure cursor. (DBERR 2248) CAUSE The ADVANCE statement was issued against a cursor, but the cursor was not defined on an EXECUTE PROCEDURE statement. ACTION There is no need for the ADVANCE statement for a non-procedure cursor. Use the OPEN, FETCH, and CLOSE statements.
ALLBASE/SQL Error Messages: 2101-2419 2255 2256 2257 2258 2259 146 ACTION Identify the constraint violated and determine the proper value for the INSERT or UPDATE. MESSAGE View CHECK OPTION constraint violated. (DBERR 2255) CAUSE A check constraint on the view named for the INSERT or UPDATE was violated during its execution. ACTION Identify the view definition violated (under the topmost WITH CHECK OPTION view) and determine the proper value for the INSERT or UPDATE.
ALLBASE/SQL Error Messages: 2101-2419 2260 2261 2262 2263 2264 2265 Chapter 5 MESSAGE Unnamed CHECK constraint on column ! references other columns. (DBERR 2260) CAUSE You defined an unnamed CHECK constraint on a single column contains references to other columns. ACTION Identify the unnamed constraint which fits this condition and either remove the references to the other columns or make the check constraint a table level check constraint.
ALLBASE/SQL Error Messages: 2101-2419 than OUTPUT ONLY. 2266 2267 2268 2269 2270 2275 2276 148 MESSAGE Unnamed CHECK constraint invalid. (DBERR 2266) CAUSE An unnamed CHECK constraint will not be executable and so is not valid. ACTION Identify the unnamed constraint which fits this condition and identify the problem with this CHECK constraint by examining the error or errors prior to this one. Correct the problem of those errors in order to make the CHECK constraint executable.
ALLBASE/SQL Error Messages: 2101-2419 a foreign key. (DBERR 2276) 2277 2278 2279 2280 Chapter 5 CAUSE You attempted to revoke an authority which is currently depended on by the specified user, class or group (directly or indirectly) to authorize a foreign key.
ALLBASE/SQL Error Messages: 2101-2419 2281 2282 2283 2284 2285 2286 150 ACTION Check the constraint type in SYSTEM.CONSTRAINT and ensure that the type of the constraint is not "H", for hash. MESSAGE Maximum number of columns allowed in a UNIQUE/PRIMARY KEY/FOREIGN KEY is !. (DBERR 2281) CAUSE The unique or referential constraint exceeds the maximum number of columns allowed in a unique or referential constraint. ACTION Define the unique or referential constraint on columns within this limit.
ALLBASE/SQL Error Messages: 2101-2419 2287 2288 2289 2290 2291 2292 Chapter 5 CAUSE The named column appears in an integrity constraint but was not defined in the CREATE TABLE. ACTION Re-issue the command with referential constraints defined on columns being defined in the statement. MESSAGE Cannot drop a table with a UNIQUE/PRIMARY KEY constraint supporting another table's FOREIGN KEY constraint. (DBERR 2287) CAUSE You tried to drop a table with a UNIQUE or PRIMARY KEY constraint.
ALLBASE/SQL Error Messages: 2101-2419 due to execution errors. (DBERR 2292) 2293 2294 2295 2296 152 CAUSE No rows were added, altered or removed by your statement because of an error during execution. Examine the accompanying error messages to determine the cause. ACTION Determine the row(s) causing the error and remove them from the statement's field of effect before reissuing the command.
ALLBASE/SQL Error Messages: 2101-2419 2297 2300 2301 2302 2303 Chapter 5 ACTION Modify the query to have a CHAR or VARCHAR data type column on the LIKE predicate. MESSAGE FOREIGN KEY column ! data type DECIMAL(!,!) doesn't match PRIMARY KEY data type DECIMAL(!,!). (DBERR 2297) CAUSE You entered a value in the referencing column which has a different precision and scale than the precision and scale of the PRIMARY KEY referenced column.
ALLBASE/SQL Error Messages: 2101-2419 2304 2305 2306 2307 2308 2309 154 MESSAGE Cannot revoke DBA authority from session owner !. (DBERR 2304) CAUSE You tried to REVOKE DBA authority from yourself. ACTION Refer to the ALLBASE/SQL Database Administration Guide for additional information on when you can revoke DBA authority. MESSAGE Use REVOKE ! to revoke GRANT !.
ALLBASE/SQL Error Messages: 2101-2419 2310 2311 2312 2313 2314 2315 Chapter 5 CAUSE The AuthorizationName is different than the DBEUserID executing the CREATE SCHEMA statement. You do not have DBA authority, nor are you a member of a group whose name is the AuthorizationName specified in the CREATE SCHEMA statement. ACTION Ensure that you have proper authorization to execute the CREATE SCHEMA statement. MESSAGE User ! does not have DBA authority.
ALLBASE/SQL Error Messages: 2101-2419 name in the manner specified in the second parameter; or a CONNECT was attempted with a DBEUserID equivalent to an existing group name. ACTION Remove the existing usage before re-issuing the CREATE GROUP, or issue it with a different group name; or drop the group to permit the connection; or do not attempt to CONNECT with that DBEUserID. 2316 2317 2318 2319 2321 156 MESSAGE User or group ! owns object(s) in the DBEnvironment.
ALLBASE/SQL Error Messages: 2101-2419 different from your DBEUserid name so that this problem will not occur in the future. 2322 2323 2324 2325 2326 Chapter 5 MESSAGE User ! already has ! authorization on !.! from a different grantor. (DBERR 2322) CAUSE Attempted to GRANT the specified authority to a user who has the authority from another grantor already, and you would not be able to revoke that authority. ACTION Repeat the GRANT without that user and/or authorization.
ALLBASE/SQL Error Messages: 2101-2419 doing so would not cause a cycle). 2327 2328 2329 2330 2331 158 MESSAGE GRANT of ! authority to ! on !.!.! causes a cycle. (DBERR 2327) CAUSE Attempted to GRANT the specified authority which would cause a cycle of grants in the authority list. ACTION Examine the chain of grants to determine if the cycle can be broken, or have someone else perform the grant (if their doing so would not cause a cycle).
ALLBASE/SQL Error Messages: 2101-2419 2332 2333 2334 2335 2336 2337 Chapter 5 MESSAGE User not authorized to revoke ! on !.! from user/group !. (DBERR 2332) CAUSE You are not the OWNER, DBA, or grantor of the specified privilege on the specified table to the specified user/group. ACTION Have the system administrator determine the grantor of the privilege and have that person perform the revoke, or have the table owner or a DBA perform the revoke. MESSAGE User not authorized to revoke ! on !.
ALLBASE/SQL Error Messages: 2101-2419 2338 2339 2340 2341 160 CAUSE You attempted to grant a table level authority with a different grantability from an existing column level authority which this would override (WITH GRANT OPTION was specified on only one of the grants). ACTION Re-issue the grant without the specified authorization, or revoke the specified authorization and then reissue the grant. MESSAGE User ! does not have OWNER, DBA, or direct GRANTABLE ! authority on !.!.
ALLBASE/SQL Error Messages: 2101-2419 2342 2343 2346 2347 2350 2352 2353 Chapter 5 MESSAGE TRANSFER OWNERSHIP of !.! to ! causes a cycle of ! authority on column !. (DBERR 2342) CAUSE Attempted to transfer a table upon which the specified authority existed, and that transfer would cause a cycle of grants in the authority list for that authority on that table.
ALLBASE/SQL Error Messages: 2101-2419 2354 2355 2356 CAUSE The named rule definition's EXECUTE PROCEDURE clause will not be executable and so is not valid. ACTION Identify the problem with the rule definition by examining the error or errors accompanying this one. Correct the problem identified in those errors in order to make the rule's EXECUTE PROCEDURE clause executable. MESSAGE Rule !.! not found. (DBERR 2354) CAUSE The named rule was not found.
ALLBASE/SQL Error Messages: 2101-2419 had the NULL value. 2361 2362 2363 2364 2365 2366 2367 Chapter 5 ACTION Check the value given to the RAISE ERROR statement and ensure that it is not null. MESSAGE Error number must be positive for RAISE ERROR. (DBERR 2361) CAUSE The error number given to the RAISE ERROR statement was negative or zero. ACTION Check the value given to the RAISE ERROR statement and ensure that it is greater than zero.
ALLBASE/SQL Error Messages: 2101-2419 constraint column. (DBERR 2367) 2370 2371 2372 2373 2390 2400 164 CAUSE A RENAME COLUMN statement was issued for a check constraint column. ACTION Check constraints on a renamed column will be disallowed. Determine if an incorrect column was renamed or take other appropriate action. MESSAGE Rule firing invalidated current section (!.!(!)).
ALLBASE/SQL Error Messages: 2101-2419 table/view !.!. (DBERR 2400) 2402 2404 2405 2406 2407 2408 Chapter 5 CAUSE The number of columns you specified in the ALTER TABLE, CREATE TABLE, or CREATE VIEW statement was greater than the maximum number of columns allowable. ACTION Issue the command again ensuring that the total number of columns does not exceed 1023. MESSAGE Maximum number of tables per module exceeded.
ALLBASE/SQL Error Messages: 2101-2419 length greater than the maximum allowed. 2409 2410 2411 2412 ACTION Reduce the minimum tuple length of the table and reissue the statement. MESSAGE Length of index ! on table !.! exceeds ! bytes. (DBERR 2409) CAUSE The index you attempted to create exceeds the maximum key length. ACTION Recreate your index using a column or combination of columns that is less than the maximum number of bytes. MESSAGE Tuple exceeded maximum length.
ALLBASE/SQL Error Messages: 2101-2419 2414 2415 2416 2417 2418 2419 Chapter 5 ACTION Try to reduce the number of factors. MESSAGE Length of column ! in table !.! below minimum ! bytes. (DBERR 2414) CAUSE You tried to create a LONG or CHAR column of length 0. ACTION Create the column with at least the minimum length. MESSAGE Number of operators in internal predicate exceed maximum (!). (DBERR 2415) CAUSE A predicate containing one or more OR operators was too complicated.
ALLBASE/SQL Error Messages: 2101-2419 168 Chapter 5
6 ALLBASE/SQL Error Messages: 2420-2795 2420 MESSAGE INSERT rejected: Values do not match number of columns. (DBERR 2420) CAUSE The number of values in the INSERT statement exceeded the number of columns in the INSERT list or the number of select list items did not match the number of columns in the insert list. 2421 2422 ACTION Issue the INSERT statement again, specifying a valid number of columns. Use the INFO command to get a list of columns in the table.
ALLBASE/SQL Error Messages: 2420-2795 in Pascal or C programs, check the value you specified for data types in the dynamic format nodes of SQLDA. 2423 2424 2425 2426 2428 2429 170 MESSAGE Number of Selects in command exceeds maximum !. (DBERR 2423) CAUSE The maximum number of Selects in a command has been exceeded. ACTION Issue the command again, specifying the maximum number or fewer. MESSAGE SelectList counts are not equal in UNION command.
ALLBASE/SQL Error Messages: 2420-2795 maximum length of the sort tuple. Refer to the ALLBASE/SQL Reference Manual for additional information on the SELECT statement. The maximum sort tuple size can be calculated from the formula presented in Appendix A of the ALLBASE/SQL Database Administration Guide. 2430 2431 2432 2433 2434 2435 Chapter 6 MESSAGE Invalid decimal precision ! - Allowed range is ! - !. (DBERR 2430) CAUSE The decimal precision you specified was not within the valid range.
ALLBASE/SQL Error Messages: 2420-2795 2436 2437 2438 2439 2440 172 CAUSE You issued a BEGIN WORK with an invalid priority option. ACTION Reissue the BEGIN WORK with a priority within the valid range. MESSAGE Invalid decimal parameter - Scale ! exceeds precision !. (DBERR 2436) CAUSE The decimal scale was greater than the precision value. ACTION Refer to the "Data Types" chapter in the ALLBASE/SQL Reference Guide for complete information about valid decimal values.
ALLBASE/SQL Error Messages: 2420-2795 2449 2450 2452 MESSAGE TRANSFER OWNERSHIP OF MODULE is not supported. (DBERR 2449) CAUSE You specified the MODULE option of the TRANSFER OWNERSHIP statement. However, the ownership of modules cannot be transferred. ACTION DROP the existing modules and preprocess the program with the -o option. MESSAGE BEGIN WORK MULTI is not supported. (DBERR 2450) CAUSE You attempted to use the MULTI option for the BEGIN WORK statement.
ALLBASE/SQL Error Messages: 2420-2795 2501 2502 ACTION Before dropping the DBEFileSet, drop the DBEFiles then remove them. Remember that the DBEFiles must be empty before they can be dropped. MESSAGE DBEFileSet has no DBEFiles. (DBERR 2501) CAUSE You created a table in an empty DBEFileSet and then tried to INSERT into that table. ACTION ADD a DBEFile to the DBEFileSet before attempting an INSERT statement. MESSAGE ! space exhausted in DBEFileSet !.
ALLBASE/SQL Error Messages: 2420-2795 mixed. (DBERR 2507) 2508 CAUSE You attempted to ALTER a non-empty DBEFile to a type other than mixed. ACTION The type of a non-empty DBEFile can be changed from TABLE or INDEX to MIXED. No other changes are allowed. MESSAGE DBEFileSet has no DBEFile of required DBEFile type.
ALLBASE/SQL Error Messages: 2420-2795 !. (DBERR 2513) 2514 2515 CAUSE You specified a number of primary pages for the hash in the CREATE TABLE statement which was not within the valid range. ACTION Issue the CREATE TABLE statement again, specifying a valid number of primary pages. MESSAGE Hash key uniqueness or UNIQUE/PRIMARY KEY constraint violated.
ALLBASE/SQL Error Messages: 2420-2795 contain DBEFiles large enough that the primary pages for the hash table can be allocated using 16 or fewer DBEFiles. 2520 2521 2522 2523 Chapter 6 ACTION Create additional DBEFiles large enough that the primary pages for the hash table can be allocated using 16 or fewer DBEFiles. MESSAGE Not enough space in DBEFileset for hash primary pages.
ALLBASE/SQL Error Messages: 2420-2795 initial size. 2524 2525 2526 2527 2528 2529 2530 2600 178 MESSAGE Connection ID ! does not exist. (DBERR 2524) CAUSE The Connection ID specified does not exist. ACTION Use a valid Connection ID. MESSAGE Transaction ID ! does not exist. (DBERR 2525) CAUSE The Transaction ID specified does not exist. ACTION Use a valid Transaction ID. MESSAGE Attempting to terminate current query. (DBERR 2526) CAUSE The current query is being terminated.
ALLBASE/SQL Error Messages: 2420-2795 2601 2602 2603 2604 2605 2606 2607 Chapter 6 MESSAGE Integer divide by zero. (DBERR 2601) CAUSE The result of an arithmetic operation within an expression caused an integer value to be divided by zero. ACTION Look at your data to find where this error occurred and make any necessary changes to your expression. MESSAGE Extended precision overflow on operation !.
ALLBASE/SQL Error Messages: 2420-2795 2609 2610 2615 2616 2617 2618 180 CAUSE The result of an arithmetic operation within an expression caused a packed decimal value to be divided by zero. ACTION Look at your data to find where this error occurred and make any necessary changes. MESSAGE Incompatible data types ! and ! in expression. (DBERR 2609) CAUSE You attempted to mix numeric and character data types in an expression in the select list, the WHERE clause, or the SET clause.
ALLBASE/SQL Error Messages: 2420-2795 Center. 2619 2620 2621 2622 2623 2624 2625 2626 Chapter 6 MESSAGE Invalid date entered, February 29th invalid for non-leap year. (DBERR 2619) CAUSE You tried to insert a datetime value which was not valid. ACTION Enter the correct date. MESSAGE Result of DATE/TIME arithmetic exceeds maximum value allowed. (DBERR 2620) CAUSE The arithmetic produced a value greater than the maximum allowed.
ALLBASE/SQL Error Messages: 2420-2795 size. (DBERR 2626) 2627 2628 2629 2630 2631 2632 2633 182 CAUSE You tried to insert a date value of incorrect length. ACTION Verify that all date literals in the query are of the correct size. MESSAGE Time value contains a field greater than valid range allowed. (DBERR 2627) CAUSE You tried to insert a time value which was not valid. ACTION Verify that all fields of all time literals are within the valid range.
ALLBASE/SQL Error Messages: 2420-2795 2634 2635 2636 2637 2638 2639 2641 Chapter 6 ACTION Verify that all interval literals in the query are specified in the default specification "DDDDDDD HH:MI:SS.FFF" where "DDDDDDD" can be 1 to 7 digits. MESSAGE Size of interval literal less than valid default size. (DBERR 2634) CAUSE You tried to insert an interval value of incorrect length. ACTION Verify that all interval literals in the query are of the correct size.
ALLBASE/SQL Error Messages: 2420-2795 specification. (DBERR 2641) 2642 2643 2644 2645 2646 2647 2650 184 CAUSE A unit in the format specification was specified twice, or two units which contain identical units. ACTION Re-issue the command with a valid format specification. MESSAGE Invalid data type for second parameter of datetime function. (DBERR 2642) CAUSE Data type of second parameter is not valid. ACTION Please check the documentation for valid format types.
ALLBASE/SQL Error Messages: 2420-2795 detected in SQLCORE. The most likely cause of this would be an uninitialized VARCHAR host variable used in an insert or an uninitialized VARCHAR length field in the buffer used in a bulk insert. 2651 2652 2653 2654 2655 2656 Chapter 6 ACTION Make sure that all VARCHAR host variables are properly initialized. MESSAGE DEFAULT literal type ! is not compatible with the corresponding column data type !.
ALLBASE/SQL Error Messages: 2420-2795 2657 2658 2659 2660 186 ACTION Make sure the source character string contains an appropriate representation of a numeric value with no extraneous characters added. MESSAGE CAST target data type too small. (DBERR 2657) CAUSE The size in bytes of the specified target data type is too small to hold the value being converted. ACTION Specify a larger target data type. MESSAGE Numeric/Binary conversion must be of equal length.
ALLBASE/SQL Error Messages: 2420-2795 this is not true. 2661 ACTION When converting to BINARY, make sure that the specified size of the BINARY matches the size of the source (8 bytes). If converting to VARBINARY, make sure that the specified size of the VARBINARY is at least the size of the source. When converting from BINARY or VARBINARY to a Date/Time type, the source should be 8 bytes. MESSAGE Invalid TID format.
ALLBASE/SQL Error Messages: 2420-2795 VARBINARY, LONG BINARY or LONG VARBINARY. 2700 2701 2702 2703 2705 188 ACTION Change the search string parameter in POSITION/INSTR to appropriate type. MESSAGE INSERT/UPDATE/DELETE disallowed on a join. (DBERR 2700) CAUSE You attempted to INSERT, UPDATE, or DELETE on a multiple table view. ACTION You cannot perform an INSERT, UPDATE, or DELETE on multi-table views.
ALLBASE/SQL Error Messages: 2420-2795 or you are doing a GROUP BY with a SELECT * and you have failed to reference all of the columns in the specified table in the GROUP BY clause. 2706 2707 2708 2709 2710 Chapter 6 ACTION Issue the SELECT statement again, specifying only aggregate functions and columns referenced in the GROUP BY clause In the case of SELECT *, be sure to reference all columns produced by the expansion of the * in the GROUP BY clause.
ALLBASE/SQL Error Messages: 2420-2795 2711 2712 2716 2717 2718 2719 190 CAUSE You attempted to insert through a view, where the view contains a subquery which references the same base table the view is based upon. Such an insert is not allowed. ACTION Insert directly through the base table, or use a view not containing subqueries which reference the same table as the view. MESSAGE Qualifier !.! (column !) is different from input table.
ALLBASE/SQL Error Messages: 2420-2795 table/view !.!. (DBERR 2719) 2720 2724 2725 2726 2730 2731 Chapter 6 CAUSE You do not have the required authority to execute GENPLAN on the named table or view. ACTION Contact your database administrator to obtain the required authority or sign on as a user who does have the required authority. MESSAGE INSERT/UPDATE/DELETE disallowed on system tables (!.!). (DBERR 2720) CAUSE You attempted to INSERT, UPDATE or DELETE to a system table.
ALLBASE/SQL Error Messages: 2420-2795 SYSTEM.ACCOUNT. 2732 2740 2741 2742 2743 2744 2749 192 MESSAGE Invalid number of columns in view column list. (DBERR 2732) CAUSE The number of columns in the CREATE VIEW statement did not match the number of columns in the SELECT statement for the view. ACTION Issue the command again using the same number of columns in both the CREATE VIEW statement and the SELECT statement. MESSAGE Invalid savepoint number.
ALLBASE/SQL Error Messages: 2420-2795 or after an ADVANCE returned an sqlcode of 200 (no more result sets). ACTION Issue an ADVANCE statement after opening the cursor, and before trying to fetch results. or Check for an sqlcode of 200 on an ADVANCE statement before attempting to fetch results. 2750 2752 2753 2754 MESSAGE Module !.!(!) has DBEFileSet error. (DBERR 2750) CAUSE You tried to use DECLARE CURSOR or to PREPARE a section in a non-existent DBEFileSet.
ALLBASE/SQL Error Messages: 2420-2795 2757 2758 2759 2760 CAUSE You issued an UPDATE or DELETE statement with a CURRENT OF CURSOR clause without preceding it with a FETCH statement or you terminated the transaction between the FETCH and DELETE or UPDATE statement. ACTION A FETCH statement must precede any DELETE or UPDATE WHERE CURRENT operation within the transaction. MESSAGE Update column list not in cursor update column list.
ALLBASE/SQL Error Messages: 2420-2795 ACTION Modify your program to include indicator variables with columns that might contain null values or issue the INSERT or UPDATE statement again, specifying only non-null values for columns created with the NOT NULL option. or drop the procedure and recreate it, either omitting the NOT NULL option in the WITH RESULT clause, or modifying the procedure SELECT statements so that no null values will be retrieved.
ALLBASE/SQL Error Messages: 2420-2795 2765 2766 2768 2769 2770 2771 196 MESSAGE DDL commands disabled. (DBERR 2765) CAUSE The DDL Enabled flag in the DBECon file was set to NO when you attempted to execute DDL (data definition language) commands. ACTION STOP the DBEnvironment, use the SQLUtil ALTDBE command to set the DDL Enabled flag to YES, then START the DBEnvironment and proceed with data definition. MESSAGE Unable to revalidate section while DDL commands are disabled.
ALLBASE/SQL Error Messages: 2420-2795 SELECT...ORDER BY or SELECT DISTINCT. These operations need to build temporary tables, and if KEEP CURSOR WITH NOLOCKS is in effect, the consistency between permanent and temporary tables cannot be guaranteed between transactions. 2772 2773 2774 2775 2776 Chapter 6 ACTION Revise the program to open the cursor with the KEEP CURSOR WITH LOCKS option. MESSAGE Cursor !.!(!) containing SUBQUERY is not allowed in the REFETCH command.
ALLBASE/SQL Error Messages: 2420-2795 operator. 2777 2778 2779 2780 2781 2782 2783 198 MESSAGE Dynamic parameter as the operand of a unary arithmetic operator disallowed. (DBERR 2777) CAUSE You specified a dynamic parameter in a NULL predicate or a minus sign is specified in front of the dynamic parameter. ACTION Modify your statement to not contain a dynamic parameter in a NULL predicate nor a minus sign in front of a dynamic parameter.
ALLBASE/SQL Error Messages: 2420-2795 2784 2785 2786 2787 2788 Chapter 6 MESSAGE DDL statement not allowed in PREPARE REPEAT command. (DBERR 2784) CAUSE Data definition language statements (CREATE TABLE, CREATE INDEX, DROP TABLE, etc.) are not allowed in a PREPARE command with the REPEAT option. ACTION Do not use the REPEAT option for DDL commands. MESSAGE The starting position is invalid for the SUBSTRING function.
ALLBASE/SQL Error Messages: 2420-2795 dynamic parameters in the prepared statement. 2790 2791 2792 2793 2794 2795 200 MESSAGE CANNOT use DROP PARTITION on DEFAULT partition. (DBERR 2790) CAUSE You attempted to drop the DEFAULT partition. ACTION This partition cannot be dropped. Its partition number can be changed with the START DBE NEWLOG statement. MESSAGE Cannot CREATE PARTITION !. (DBERR 2791) CAUSE You attempted to create a partition named NONE or DEFAULT.
7 ALLBASE/SQL Error Messages: 2800-8220 2800 2801 2802 2803 2804 MESSAGE Table's language is not compatible with DBE's language. (DBERR 2800) CAUSE The language you specified for the table is neither the same as DBEnvironment's language, nor NATIVE-3000. ACTION Make sure the table's language is either NATIVE-3000 or the same as the DBEnvironment's language. MESSAGE Column's language not compatible table/DBE's language.
ALLBASE/SQL Error Messages: 2800-8220 NATIVE-3000. 2805 2806 2807 2808 2809 2810 202 ACTION Issue the CREATE PROCEDURE statement again, specifying either the procedure/DBEnvironment language or NATIVE-3000 for the parameter, or specifying no parameter language. MESSAGE NLINFO error !. Language ID = !. (DBERR 2805) CAUSE An error was returned from the NLS library routine NLINFO, with the specified language. ACTION Check the validity of your NLS data and reissue the statement.
ALLBASE/SQL Error Messages: 2800-8220 2811 2812 2813 2814 2815 2816 Chapter 7 ACTION Check the correctness of operations. Either audit logging for the DBEnvironment should be turned on (this may be done through the START DBE NEWLOG statement) or the ENABLE AUDIT LOGGING statement is not valid. MESSAGE Insufficient size specified for the new SCR. (DBERR 2811) CAUSE Note that it is possible to change the MAXPARTITIONS parameter through the START DBE NEWLOG statement.
ALLBASE/SQL Error Messages: 2800-8220 2817 2818 2819 2820 2821 2822 204 CAUSE The specified starting point for opening a log scan has been overwritten. ACTION Use a Wrapper DBE to recover the needed log records or hard resync the partition. MESSAGE Invalid audit log record found. (DBERR 2817) CAUSE The log record being applied in an Apply_Log was not a valid audit log record.
ALLBASE/SQL Error Messages: 2800-8220 2823 2824 2825 2826 2827 2828 2829 2830 Chapter 7 ACTION Eliminate the duplicates and try again. MESSAGE Open log scan failed due to missing log file (sequence #!). (DBERR 2823) CAUSE A log needed for the log scan being opened has been purged. ACTION For a resync application, perform a hard resync. Auditing cannot be done. MESSAGE More than one tuple qualified for key column search.
ALLBASE/SQL Error Messages: 2800-8220 2831 2832 2833 2834 2836 2837 3228 2881 206 CAUSE Attempted to start a transaction with a global identifier that already exists. ACTION Try again with a unique GTRID. MESSAGE The global transaction identifier is unknown. (DBERR 2831) CAUSE The specified global transaction identified does not exist in the DBE. ACTION Check the validity of the GTRID. MESSAGE A transaction scan is already opened.
ALLBASE/SQL Error Messages: 2800-8220 2882 2884 2885 2901 2902 2909 Chapter 7 CAUSE You have the space default on the DBEFileSet you tried to drop. ACTION Change the space default or modify your command. MESSAGE Cannot revoke ! default on DBEFileSet ! from !. (DBERR 2882) CAUSE The authority you tried to revoke is a DEFAULT for the user. ACTION Change the space default or modify your command. MESSAGE User ! does not have explicit ! authority on DBEFileSet !.
ALLBASE/SQL Error Messages: 2800-8220 2910 2912 2913 2914 2915 208 ACTION Modify either your EXECUTE or CLOSE statement or the related PREPARE statement so that there is a one to one mapping of output dynamic parameters. MESSAGE Number of input values does not match the number of dynamic parameters in the referenced section. (DBERR 2910) CAUSE The number of input values in the USING clause of an OPEN or EXECUTE statement is not equal to the number of dynamic parameters in the prepared statement.
ALLBASE/SQL Error Messages: 2800-8220 clause of an OPEN or EXECUTE statement is greater than the length of the data type of the corresponding dynamic parameter in the prepared statement. 2916 2917 2918 2919 2920 2921 Chapter 7 ACTION Modify the definition of the referenced input value to be compatible in length with the corresponding dynamic parameter. MESSAGE Invalid Table/View/Column in the dynamic format computation.
ALLBASE/SQL Error Messages: 2800-8220 operation ADD. (DBERR 2921) 2922 CAUSE The result of an addition operation with INTEGER or FLOAT operands is either too big or too small for the hardware to accommodate. ACTION Modify the expression to yield a result within the limits for the data type. MESSAGE PUBLICROW is not allowed on a hash table. (DBERR 2922) CAUSE You are trying to define a hash on a PUBLICROW table, and this combination is not supported.
ALLBASE/SQL Error Messages: 2800-8220 has an invalid pointer pointing to a parameter buffer. 3004 3005 3006 ACTION Record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE Invalid parameter-buffer length in ALLBASE/SQL request block. (DBERR 3004) CAUSE Internal error. ALLBASE/SQL request block (JRB) has an invalid parameter buffer length.
ALLBASE/SQL Error Messages: 2800-8220 query or an internal error occurred. ACTION Correct SQLNRows and re-preprocess your program or record as much information as possible and contact your HP Service Representative or Response Center. 3024 3025 3026 3040 3041 3042 212 MESSAGE Column number ! in node ! out of range. (DBERR 3024) CAUSE Internal error. ACTION Record as much information as possible and contact your HP service representative or Response Center.
ALLBASE/SQL Error Messages: 2800-8220 TERMINATE USER statement for your login name. Any active transactions for your login name were terminated. 3043 3047 3050 3051 3052 3053 Chapter 7 ACTION Contact the person who issued the TERMINATE USER statement and reconnect to the DBEnvironment. MESSAGE Command rejected - User session is terminating now. (DBERR 3043) CAUSE Your database administrator or another user connected to the DBEnvironment issued a TERMINATE USER statement for your login name.
ALLBASE/SQL Error Messages: 2800-8220 DBE or CONNECT statement. 3054 3055 3056 3057 3058 3059 3060 214 ACTION Check your spelling. If you still receive this error, use the MPE/iX REPORT command to make sure that the group exists in the specified account. MESSAGE File System Error - Nonexistent DBEFile or log file. (DBERR 3054) CAUSE You attempted to access a DBEFile or log file which is missing. ACTION Use the SQLUtil SHOWDBE command and/or SELECT information from SYSTEM.
ALLBASE/SQL Error Messages: 2800-8220 3061 3062 3063 3064 3065 3066 Chapter 7 CAUSE The file name specified in the CREATE DBEFILE statement already exists. ACTION Issue the command again, specifying a unique file name. MESSAGE File System Error - (! !). (DBERR 3061) CAUSE An MPE/iX file system error occurred. ACTION Refer to the MPE/iX Error Message Manual, Volume I for an error description. MESSAGE Location already used for another Tempspace.
ALLBASE/SQL Error Messages: 2800-8220 3067 ACTION Check your spelling. Issue the command again, specifying a valid DBECon file. MESSAGE DBECon Error - Privileged file violation. (DBERR 3067) CAUSE The operation attempted requires privileged capabilities or the DBEnvironment name specified in the START DBE or CONNECT statement is not a DBECon file.
ALLBASE/SQL Error Messages: 2800-8220 group and account. If your CONNECT statement is for a remote DBEnvironment, read about the action to be taken in the second message. 3072 3073 3074 3075 3076 3077 3078 3079 Chapter 7 MESSAGE DBECon Error - Invalid file reference. (DBERR 3072) CAUSE The file name specified is not valid. ACTION Check your spelling. Refer to the MPE/iX General User's Reference Manual for information on file naming conventions.
ALLBASE/SQL Error Messages: 2800-8220 3079) 3080 CAUSE The DBECon file is inaccessible because the security access of the DBECon file has been changed. ACTION Correct the security access of the DBECon file. MESSAGE DBECon error - Attempted a MULTI user session on a SINGLE user DBEnvironment.
ALLBASE/SQL Error Messages: 2800-8220 3102 3103 3104 3105 3106 Chapter 7 ACTION First, issue a START DBE statement or a CONNECT (if AutoStart is enabled). Next, stop the DBEnvironment. Finally, attempt the START DBE NEWLOG again. MESSAGE START DBE disallowed. Need rollforward recovery. (DBERR 3102) CAUSE The DBEnvironment is still in a fuzzy state.
ALLBASE/SQL Error Messages: 2800-8220 command. 3200 3201 3202 3203 3205 3206 3208 3209 220 MESSAGE Invalid LONG column I/O syntax. (DBERR 3200) CAUSE You specified a long column input or output target which is not correct. ACTION Check the > or < I/O redirection syntax. MESSAGE Invalid LONG column file name. (DBERR 3201) CAUSE The file name is incorrect. ACTION Refer to the MPE/iX General User's Reference Manual for information on file naming conventions.
ALLBASE/SQL Error Messages: 2800-8220 3210 3211 3220 3221 3222 3223 3224 3225 Chapter 7 MESSAGE Negative length value not allowed for LONG column INSERT. (DBERR 3210) CAUSE You specified a negative value for the length of the long value to be read from the heap. ACTION Remove the unary minus sign from the length specification and reissue the statement. MESSAGE Length specified is greater than allowed. (DBERR 3211) CAUSE The length of the long value to be read from the heap is too large.
ALLBASE/SQL Error Messages: 2800-8220 been defined as a long data type. 3226 3227 3228 3241 3242 3244 3245 3248 222 ACTION Remove the UNIQUE HASH clause from the CREATE TABLE syntax, or the long column from the UNIQUE HASH clause. MESSAGE LONG column disallowed on INSERT from SELECT. (DBERR 3226) CAUSE You tried to insert a column defined as a long data type in a type II INSERT statement. ACTION Remove the long column from the SELECT clause in the INSERT statement.
ALLBASE/SQL Error Messages: 2800-8220 3300 3301 3302 3303 3304 3305 3306 Chapter 7 CAUSE The input or output parameter has an incorrect data type. ACTION Change to the correct data type. MESSAGE DBEFile ! is currently DETACH-ed. (DBERR 3300) CAUSE You attempted to DETACH an already DETACHed DBEFile. ACTION None. MESSAGE Attempting to ATTACH an already attached DBEFile !. (DBERR 3301) CAUSE You attempted to ATTACH an already ATTACHed DBEFile. ACTION None.
ALLBASE/SQL Error Messages: 2800-8220 may be needed before ATTACHing), and restart the transaction. 3307 3308 3309 3310 3311 3500 3501 224 MESSAGE Cannot partially rollforward the SYSTEM DBEFileset or any DBEFile in it. (DBERR 3307) CAUSE You attempted to perform a partial rollforward on the SYSTEM.DBEFileSet or a DBEFile in the SYSTEM DBEFileSet. ACTION Perform a complete rollforward recovery. MESSAGE OMNIBACK error !.
ALLBASE/SQL Error Messages: 2800-8220 3550 3551 3552 4000 4001 4002 4003 4004 Chapter 7 ACTION No action. MESSAGE !.!(!) is not a permanent section or it is a procedure. (DBERR 3550) CAUSE You attempted to EXTRACT a section which is not a permanent section, or it is a procedure. ACTION EXTRACT a section which is a permanent section and it is not a procedure. MESSAGE TBL of ! is needed to EXTRACT !.!(!). (DBERR 3551) CAUSE The tuple buffer length is too small for the linear tree.
ALLBASE/SQL Error Messages: 2800-8220 4005 4006 4007 4008 CAUSE ALLBASE/SQL internal input heap overflow. Input command was too long or too complicated. ACTION Try to simplify the input command. Reduce the amount of table and column qualifications as much as possible. If necessary, record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE ALLBASE/SQL memory allocation failed. (DBERR 4005) CAUSE ALLBASE/SQL cannot allocate run-time memory.
ALLBASE/SQL Error Messages: 2800-8220 or you may be able to use BEGIN WORK CS or BEGIN WORK RU to prevent this error. 4009 MESSAGE ALLBASE/SQL shared memory allocation failed in DBCore. (DBERR 4009) CAUSE ALLBASE/SQL ran out of run-time control block space. Your transaction was rolled back.
ALLBASE/SQL Error Messages: 2800-8220 and contact your HP Service Representative or Response Center. 4051 4053 4054 4059 4111 4112 4116 228 MESSAGE ALLBASE/SQL internal error at ! (! ). (DBERR 4051) CAUSE Internal error. ACTION Record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE ALLBASE/SQL internal error (! !).
ALLBASE/SQL Error Messages: 2800-8220 4117 4118 4150 4200 4201 4250 8101 Chapter 7 MESSAGE Number of multiple CONNECTs exceeds the maximum limit, 32. (DBERR 4117) CAUSE You have attempted to issue a CONNECT statement when you already have 32 connections. ACTION DISCONNECT at least one of your existing connections and reissue the CONNECT statement. MESSAGE Invalid JRB version is found.
ALLBASE/SQL Error Messages: 2800-8220 entered incorrectly. 8102 8103 8111 8115 8116 8118 8131 230 ACTION Use the SQLUtil HELP command or refer to the ALLBASE/SQL Database Administration Guide to obtain a list and description of valid SQLUtil commands. MESSAGE Command not yet implemented. (DBERR 8102) CAUSE The command name you entered does not exist or was entered incorrectly.
ALLBASE/SQL Error Messages: 2800-8220 8132 8133 8160 8201 8202 8203 8204 8205 Chapter 7 CAUSE The specified file is not a DBEFile. ACTION Issue the command again, specifying a valid DBEFile. MESSAGE File '!' not accessible. (! !). (DBERR 8132) CAUSE An MPE/iX file system error occurred. ACTION Refer to the MPE/iX Error Message Manual, Volume 1 for an error description. MESSAGE Internal error occurred. (! !). (DBERR 8133) CAUSE An MPE/iX file system error occurred.
ALLBASE/SQL Error Messages: 2800-8220 1. 8206 8207 8208 8209 8210 8211 8212 8213 8214 232 MESSAGE RESTORE failed. (! !). (DBERR 8206) CAUSE An MPE/iX file system error occurred. ACTION Refer to the MPE/iX Error Message Manual, Volume 1. MESSAGE Operation not performed; illegal capability. (DBERR 8207) CAUSE You do not have the capability to perform the specified command. ACTION Contact a user who has the required capability.
ALLBASE/SQL Error Messages: 2800-8220 8215 8216 8217 8218 8219 8220 Chapter 7 CAUSE You cannot access the System Catalog due to another error. ACTION Refer to the cause and action of the additional error. MESSAGE BUILD failed. (! !) (DBERR 8215) CAUSE An MPE/iX file system error occurred. ACTION Refer to the MPE/iX Error Message Manual, Vol. 1. MESSAGE Permission denied. (DBERR 8216) CAUSE You tried to issue PURGEFILE and you do not have the correct authority.
ALLBASE/SQL Error Messages: 2800-8220 234 Chapter 7
8 ALLBASE/SQL Error Messages: 8221-10999 8221 8222 8223 8224 8225 8226 MESSAGE Internal NLS error. (DBERR 8221) CAUSE The local language table corresponding to your language cannot be accessed, probably because the environment file or custdatatable file does not exist. ACTION Contact your system administrator. MESSAGE Message catalog not available - see system administrator. (DBERR 8222) CAUSE The message catalog file cannot be accessed, probably because it does not exist.
ALLBASE/SQL Error Messages: 8221-10999 older release of the ALLBASE/SQL software. 8227 8228 8229 8230 8231 8232 8233 8234 236 MESSAGE DBEnvironment corrupted during previous migration. (DBERR 8227) CAUSE At some prior time, a migration attempt failed which corrupted the DBEnvironment in the process. ACTION Restore the DBEnvironment from the backup. MESSAGE Option String too long (maximum 80 bytes). (DBERR 8228) CAUSE The specified option string exceeds the maximum buffer length.
ALLBASE/SQL Error Messages: 8221-10999 8235 8236 8238 8249 8270 8271 Chapter 8 CAUSE You specified an invalid input device when issuing a RESTORELOG command. ACTION Check with your system administrator to obtain the correct device name. MESSAGE No such user exists on system. (DBERR 8235) CAUSE The user name you specified in the RESTORE command does not exist. ACTION Check your spelling and enter the command again, specifying a valid name.
ALLBASE/SQL Error Messages: 8221-10999 mapped using the SQLUtil MOVEFILE command. Then reissue the STOREONLINE command. 8273 8274 9126 10000 10001 10002 10003 10004 238 MESSAGE Too many files, MAX = 128 files. (DBERR 8273) CAUSE Number of files exceeds the limit. ACTION Keep the number of files to be within 128. MESSAGE Too many files, MAX = 256 files. (DBERR 8274) CAUSE Number of files while restoring exceeds the limit. ACTION Keep the number of files within 256 while restoring.
ALLBASE/SQL Error Messages: 8221-10999 (DBERR 10004) 10005 10006 10007 CAUSE The EXECUTE IMMEDIATE statement contained a host variable. ACTION Eliminate the host variable from the EXECUTE IMMEDIATE statement in the source file and re-preprocess your program. MESSAGE Too many columns in dynamic FETCH. (DBERR 10005) CAUSE There was not enough buffer space for the number of columns specified in the FETCH statement.
ALLBASE/SQL Error Messages: 8221-10999 10010 10011 10012 10013 10014 10015 10016 10017 240 ACTION Contact your system administrator. MESSAGE DBEnvironment name too long. (DBERR 10010) CAUSE The DBEnvironment name specified at run-time exceeds the maximum of 128 bytes fully qualified. ACTION Re-run your application, specifying a valid DBEnvironment name. MESSAGE PREPARE invalid with host variable. (DBERR 10011) CAUSE The PREPARE statement contained a host variable.
ALLBASE/SQL Error Messages: 8221-10999 10017) 10018 10019 10020 10021 10022 10023 Chapter 8 CAUSE The linear tree node could not be allocated or deallocated. This may be caused by a memory resource failure. ACTION Try your program again later. If the condition persists, then record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE Invalid setting in PARMCB.CODE_FLAG. (DBERR 10018) CAUSE An unknown PARMCB.
ALLBASE/SQL Error Messages: 8221-10999 10024 10025 10026 10027 10028 10029 10030 10031 242 MESSAGE Invalid version number specified in the SQLX SQLPA parameter. (DBERR 10024) CAUSE An unknown SQLPA.VERSION setting was passed to the SQLX interface. ACTION Specify a valid SQLPA.VERSION setting. MESSAGE Invalid version number specified in the SQLX PARMCB parameter. (DBERR 10025) CAUSE An unknown PARMCB.VERSION setting was passed to the SQLX interface. ACTION Specify a valid PARMCB.
ALLBASE/SQL Error Messages: 8221-10999 number of input host variables. 10032 10033 10034 10035 10036 10037 10038 Chapter 8 ACTION Correct the PARMS.PARMBUF_FMT parameter. MESSAGE Number of DATABUF formats did not match the SQL command. (DBERR 10032) CAUSE The DATABUF.BUFFER_FMT is passed when not needed, or is not passed when needed, or does not match the number of input host variables. ACTION Correct the DATABUF.BUFFER_FMT parameter.
ALLBASE/SQL Error Messages: 8221-10999 10039 10040 10041 10042 10043 10044 10045 244 ACTION Correct the value of PARMCB.COLUMNS.NUM_COLUMNS. MESSAGE Invalid number of formats specified. (DBERR 10039) CAUSE The number of format elements you specified is either less than or equal to 0, or greater than 1024. ACTION Specify the correct number of format elements. MESSAGE No more WSL records to transmit. (DBERR 10040) CAUSE A Transmit_Log reader has encountered the end of log.
ALLBASE/SQL Error Messages: 8221-10999 size_used is smaller than the smallest WSL record possible, or that the size_used is greater than the number of bytes reserved in the log buffer (as indicated by the buffer_size field in the arglist). 10046 10047 10048 Chapter 8 ACTION Check that the size_used is less than or equal to the buffer_size field in the arglist. The size_used being passed to Apply_Log should also be checked against the value that was returned by Transmit_Log.
ALLBASE/SQL Error Messages: 8221-10999 10049 10050 10051 10052 246 MESSAGE No apply WSL records transaction currently active. (DBERR 10049) CAUSE Apply_Log encountered a WSL record that was not a BEGIN WORK record, and the BEGIN WORK WSL record has not been processed for the transaction. One cause is if the Apply_Log transaction was aborted and the user tries to continue applying log records without starting at the beginning of the transaction.
ALLBASE/SQL Error Messages: 8221-10999 10053 10054 10055 10056 Chapter 8 CAUSE Get_Scr or Modify_Scr encountered an invalid partition id passed in from the user. For Get_Scr, the partition id in error must be in the array pointed to be the partition_array field in the arglist. For Modify_Scr, the partition id must be in the SCR array for mode 1 (UPDATE SCR), or the partition array for mode 2 (DELETE SCR). All partition ids are required to be positive, non-zero numbers.
ALLBASE/SQL Error Messages: 8221-10999 application should be modified to use less. If the heap allocation has previously worked on the system, first check the number of users on the system, then use SQLMON to see global swap space utilization plus heap usage for individual user processes. If numerous scans are open on the same DBE, the problem could be alleviated if the open scans are combined into one open scan (and thus only one set of scan control blocks).
ALLBASE/SQL Error Messages: 8221-10999 10063) 10064 10065 10066 10067 10068 10069 10071 Chapter 8 CAUSE The format node type you specified in one of the format array elements is invalid. ACTION Record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE Invalid PARMCB.PARMS.PARMBUF_LEN specified. (DBERR 10064) CAUSE The length you specified in PARMCB.PARMS.PARMBUF_LEN is less than or equal to zero. ACTION Specify a valid length in PARMCB.
ALLBASE/SQL Error Messages: 8221-10999 10074 10075 10076 10077 10080 10081 250 CAUSE Internal error. ACTION Record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE Invalid offset for last record passed. (DBERR 10074) CAUSE This can be returned by audit_log when the last_rec_offset field contains an invalid value.
ALLBASE/SQL Error Messages: 8221-10999 record as much information as possible and contact your HP Service Representative or Response Center. 10082 10083 10084 10085 10086 10087 Chapter 8 MESSAGE Internal error. Could not allocate or deallocate the GCB. (DBERR 10082) CAUSE The Global Control Block could not be allocated or deallocated, possibly because of a memory resource failure. ACTION Try your program later.
ALLBASE/SQL Error Messages: 8221-10999 or ROLLBACK WORK, and retry the statement. 10088 10089 10090 10091 10092 MESSAGE XA Interface rmfail error occurred. (DBERR 10088) CAUSE A resource manager failure has occurred in the XA interface. ACTION Refer to the X/OPEN XA Interface standard for possible causes. MESSAGE Error occurred opening the module file. (DBERR 10089) CAUSE The specified module file could not be opened.
ALLBASE/SQL Error Messages: 8221-10999 10094 10095 10096 10900 10901 10902 Chapter 8 ACTION Ensure that the module file exists and that it has the correct read/write permissions. If the condition persists, then record as much information as possible and contact your HP Service Representative MESSAGE Error occurred closing the module file. (DBERR 10094) CAUSE The specified module file could not be closed. ACTION Ensure that the module file exists.
ALLBASE/SQL Error Messages: 8221-10999 10903 10904 10905 10906 10907 10908 10909 254 CAUSE The DBEnvironment name specified in the invocation line for the preprocessor was too long. ACTION Invoke the preprocessor again, specifying a valid DBEnvironment name. Refer to the ALLBASE/SQL Reference Manual for naming conventions. MESSAGE DBEnvironment name missing.
ALLBASE/SQL Error Messages: 8221-10999 10910 10911 10912 10913 10914 Chapter 8 CAUSE The preprocessor INFO string included both PRESERVE and REVOKE options or duplicate PRESERVE or REVOKE options. ACTION Invoke the preprocessor again eliminating the invalid PRESERVE and REVOKE combination or specifying the PRESERVE or REVOKE option only once. MESSAGE SYNTAX option may only be specified once. (DBERR 10910) CAUSE You specified the SYNTAX option more than once in the preprocessor INFO string.
ALLBASE/SQL Error Messages: 8221-10999 10915 10916 10917 10918 10919 10920 256 MESSAGE SYNTAX option may not be used with any other option. (DBERR 10915) CAUSE You specified additional options in the preprocessor invocation line along with the SYNTAX option. ACTION Invoke the preprocessor again, specifying the SYNTAX option as the only option if you want to run the preprocessor in syntax checking mode.
ALLBASE/SQL Error Messages: 8221-10999 10921 MESSAGE Input source file not found. (DBERR 10921) CAUSE The preprocessor could not locate a file name SQLIN. ACTION Issue a FILE command to identify the file containing the source program to be preprocessed before invoking the preprocessor again: :FILE SQLIN = MySource.MyGroup.MyAcct 10922 MESSAGE System error in opening input source file.
ALLBASE/SQL Error Messages: 8221-10999 10929 10931 10932 10933 10934 10935 10936 258 MESSAGE No ending semicolon before end of file. (DBERR 10929) CAUSE An SQL statement was not ended with a semicolon. ACTION Check your Pascal program to make sure that all SQL statements are ended with a semicolon and then re-preprocess your program. MESSAGE Syntax error in program header. (DBERR 10931) CAUSE Your program statement contained a syntax error.
ALLBASE/SQL Error Messages: 8221-10999 following the specified line. Refer to the ALLBASE/SQL application programming guide for the language you are using for additional information. 10937 10938 10939 10940 10941 10942 Chapter 8 MESSAGE Syntax error caused skip to end of DECLARE SECTION. (DBERR 10937) CAUSE An unrecognized syntax error occurred in the host variable declaration section.
ALLBASE/SQL Error Messages: 8221-10999 10943 10944 10945 10946 10947 10948 260 CAUSE The size you specified for the FORTRAN host variable is not valid for that type of host variable. ACTION Modify the declaration of the host variable so that it is a valid size. Refer to the ALLBASE/SQL FORTRAN Application Programming Guide for additional information on host variables. MESSAGE Include file open error.
ALLBASE/SQL Error Messages: 8221-10999 10949 10950 10951 10953 ACTION Correct the syntax in your WHENEVER clauses and re-preprocess your program. Keep in mind that valid conditions are SQLWARNING, SQLERROR, and NOT FOUND. Valid actions are STOP, GOTO, and CONTINUE. MESSAGE Undeclared host variable. (DBERR 10949) CAUSE The SQL statement you specified a host variable which was either not declared or was incorrectly declared in the host variable declaration section.
ALLBASE/SQL Error Messages: 8221-10999 or contact your database administrator to obtain the required CONNECT authority. 10954 10955 MESSAGE Cannot begin transaction. (DBERR 10954) CAUSE A transaction could not begin. An additional message will be returned. ACTION Refer to the cause and action of the additional message. MESSAGE Cannot drop module. (DBERR 10955) CAUSE You do not have the required authority to drop the specified module or an additional message will be returned.
ALLBASE/SQL Error Messages: 8221-10999 10960 10961 10962 10963 10964 10965 Chapter 8 CAUSE The SQL statement referenced a cursor which had not been declared. ACTION Insert a DECLARE CURSOR statement before referencing the cursor and re-preprocess your program. MESSAGE Insufficient input host variables. (DBERR 10960) CAUSE You specified too few input host variables in the OPEN statement to cover the columns specified in the cursor declaration.
ALLBASE/SQL Error Messages: 8221-10999 10966 10967 10968 10969 10970 10971 264 ACTION Modify the command to specify a value within the valid limits. MESSAGE No prepared query found by this command name. (DBERR 10966) CAUSE The EXECUTE statement contained a command name which was not prepared in the same subprogram unit. ACTION Check your spelling. If the command name is correct, insert an appropriate PREPARE statement before the EXECUTE statement and re-preprocess your program.
ALLBASE/SQL Error Messages: 8221-10999 10972 10973 10974 10975 10976 10977 Chapter 8 CAUSE Additional messages will be returned. ACTION Refer to the cause and action of the additional messages. MESSAGE Fields of type SQLIND must follow non-SQLIND fields. (DBERR 10972) CAUSE Fields of type SQLIND cannot be the first field in a host variable record declaration nor immediately follow another SQLIND field.
ALLBASE/SQL Error Messages: 8221-10999 10978 10982 10983 10984 10985 10990 266 ACTION Refer to the cause and action of the additional error messages. MESSAGE ALLBASE/SQL statement parser error. (DBERR 10978) CAUSE An error condition was detected by the statement parser. Additional error messages will be returned. ACTION Refer to the cause and action of the additional error messages. MESSAGE No ending single quote before end of line.
ALLBASE/SQL Error Messages: 8221-10999 10992 10993 10994 10995 10996 10998 CAUSE An error occurred while the preprocessor was writing to a file. ACTION Record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE Host variable type must be integer or short integer. (DBERR 10992) CAUSE The data type of the host variable is invalid. ACTION Declare the host variable as an integer or a small integer.
ALLBASE/SQL Error Messages: 8221-10999 10999 268 ACTION Reinvoke the preprocessor specifying an output filename containing less than or equal to 9 bytes (excluding extensions). MESSAGE Preprocessor Internal Error (!). (DBERR 10999) CAUSE Unknown escape occurred in the preprocessor. ACTION Record the number returned and as much information as possible and contact your HP Service Representative or Response Center.
9 ALLBASE/SQL Error Messages: 11007-22540 11007 11012 11013 11014 11015 11016 MESSAGE Invalid module/owner name. (DBERR 11007) CAUSE The module or owner name you specified in the preprocessor invocation line was invalid. ACTION Invoke the preprocessor again, specifying a valid module or owner name. Refer to the ALLBASE/SQL Reference Manual for naming conventions. MESSAGE Too many routines within subprogram.
ALLBASE/SQL Error Messages: 11007-22540 11017 11018 11019 11020 11021 11022 11023 270 ACTION Verify that native language support is properly installed. MESSAGE Out of preprocessor symbol table memory. (DBERR 11017) CAUSE You used too many host variables or cursor names. ACTION Reduce the number of host variables or cursor names or use subprograms. MESSAGE File ! open error. (Paserr 692). (DBERR 11018) CAUSE You tried to open a file with a Pascal statement.
ALLBASE/SQL Error Messages: 11007-22540 maximum DBEnvironment name length. 11024 11025 11026 11028 11200 11201 Chapter 9 MESSAGE Host variable declaration too large for this usage. (DBERR 11024) CAUSE You specified a host variable with a declared length greater than the maximum allowed length. ACTION Specify a host variable with a declared length less than or equal to the maximum allowed length. Consult the ALLBASE/SQL Reference Manual for the maximum allowed length.
ALLBASE/SQL Error Messages: 11007-22540 11202 11203 11204 MESSAGE Host variable must have USAGE COMPUTATIONAL. (DBERR 11202) CAUSE The declaration for the StartIndex or NumberOfRows value in a BULK command is invalid. ACTION Declare the host variable as PIC S9(4) or PIC S9(9) and re-preprocess your program. MESSAGE Host variable must not be a table.
ALLBASE/SQL Error Messages: 11007-22540 11209 11210 11211 11212 11213 Chapter 9 CAUSE The keyword COPY was encountered within another COPY statement. COPY is a keyword which can only be used to specify the start of a COPY statement. ACTION Terminate previous COPY statement before beginning another COPY statement. Verify that the COPY statement follows conventions specified in the HP COBOL II/XL Reference Manual. MESSAGE Copy file open error.
ALLBASE/SQL Error Messages: 11007-22540 11300 11301 11400 11500 11502 11503 11504 274 ACTION Change the copy file specification so that it does not exceed the maximum number of characters for a valid file name. MESSAGE Illegal continuation line, ignored. (DBERR 11300) CAUSE The statement contains an illegal continuation character. The current line is ignored. ACTION Specify a valid continuation character in the source file. MESSAGE Statement too long for FORTRAN.
ALLBASE/SQL Error Messages: 11007-22540 your program had an invalid field type. 11506 11507 11508 13130 13131 13132 Chapter 9 ACTION Modify the DECLARE section of your program specifying a valid field type. MESSAGE Label must start with alphabetic character. (DBERR 11506) CAUSE A label in a WHENEVER statement started with a number or some other non-alphabetic character. ACTION Change the label to start with an alphabetic character. MESSAGE Nested structures disallowed in host variables.
ALLBASE/SQL Error Messages: 11007-22540 duplicates. 13153 13261 13262 13310 MESSAGE DBEFile does not belong to specified DBEFileSet. (DBERR 13153) CAUSE The specified DBEFile does not belong to the specified DBEFileSet as required by the requested function. ACTION Check the specified DBEFile and DBEFileSet. MESSAGE DBCore could not find free page buffer. (DBERR 13261) CAUSE Due to the number of current users, DBCore was unable to find free page buffer space.
ALLBASE/SQL Error Messages: 11007-22540 (DBERR 13313) 13317 13318 13319 13320 13322 Chapter 9 CAUSE The ADDLOG command expects either one file name in single logging mode or two file names in dual logging mode. You may have tried to enter more or less than the permitted number of names. ACTION Check the logging mode and number of log names you specified. MESSAGE DBEnvironment has already finished recovery.
ALLBASE/SQL Error Messages: 11007-22540 without first having done a SETUPRECOVERY. 13323 13324 13325 13326 13331 13338 13339 278 ACTION Issue the SETUPRECOVERY command before the RECOVERLOG or ENDRECOVERY commands. MESSAGE Log does not contain an archive checkpoint. (DBERR 13323) CAUSE An archive checkpoint was not written to the log file, so the log file cannot be used for rollforward recovery.
ALLBASE/SQL Error Messages: 11007-22540 13345 13346 CAUSE You attempted a SETUPRECOVERY followed by either another SETUPRECOVERY or by a set of RECOVERLOG commands and then another SETUPRECOVERY. ACTION Remove the extra SETUPRECOVERY command. MESSAGE DBE in ARCHIVE mode. Cannot overwrite with NON ARCHIVE logging. (DBERR 13345) CAUSE STOREONLINE was attempted with NON_ARCHIVE logging option. However, the DBEnvironment is in archive mode.
ALLBASE/SQL Error Messages: 11007-22540 14031 14035 14038 14044 14045 14046 14047 280 ACTION Refer to the cause and action of the additional message. MESSAGE DBCore shared memory access error. (DBERR 14031) CAUSE Unable to access DBCore shared memory segments. Your current transaction was rolled back. ACTION Record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE DBCore shared memory overflow.
ALLBASE/SQL Error Messages: 11007-22540 or The system clock was set backward incorrectly. To ensure that recovery works correctly, ALLBASE/SQL requires that the date/time of the current action is later than the date/time of the preceding action. If the date/time of the current action is earlier than the date/time of the previous action (as is the case when this message is returned), ALLBASE/SQL will not function until the date/time of the current action is later than the date/time of the previous action.
ALLBASE/SQL Error Messages: 11007-22540 14059 14066 14067 14071 14072 14073 282 ACTION Record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE DBCore File Close error. (DBERR 14059) CAUSE ALLBASE was not able to close the file. File name may not be correct. ACTION Supply the correct file name. MESSAGE DBECon Error - File is invalid.
ALLBASE/SQL Error Messages: 11007-22540 14074 14075 14076 14081 MESSAGE DBCore internal error ! - Transaction rolled back. (DBERR 14074) Please record the above message including both numbers. CAUSE An internal error caused your current transaction to be rolled back. ACTION Record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE DBCore internal error ! - Rollforward recovery required.
ALLBASE/SQL Error Messages: 11007-22540 14083 14084 14092 14101 14102 14103 14200 284 MESSAGE Log file is not in use. (DBERR 14083) CAUSE Note that the STORELOG command operates in two modes - one in which the user may specify a log id and one in which the user does not. In the latter case, DBCore will simply scan the log directory looking for the oldest log ready to back up.
ALLBASE/SQL Error Messages: 11007-22540 14201 14202 15047 15048 20027 20029 Chapter 9 ACTION The transaction is aborted by ALLBASE/SQL but the application needs to terminate at this point. Issue a START DBE NEWLOG with a larger MAXPARTITIONS. MESSAGE Multiple database environments updated in the same transaction. (DBERR 14201) CAUSE A transaction attempted to replicate logging against more than one database id. ACTION Check the transaction logic.
ALLBASE/SQL Error Messages: 11007-22540 the file named AASQLMIG. This is a temporary file used by SQLMigrate. This file is located in the same group as the DBECon file. 20031 20032 20034 20035 20036 20040 286 ACTION Take the necessary steps to purge this file before attempting again the SQLMigrate command which caused this error. MESSAGE Cannot purge existing user log file (! !, !, !).(DBERR 20031) CAUSE An error occurred while trying to purge a log file named in the DBECon file.
ALLBASE/SQL Error Messages: 11007-22540 20041 20042 20043 20044 20045 20046 20047 20048 Chapter 9 MESSAGE *** Cannot close expanded DBECON file. (! !, !) (DBERR 20041) CAUSE A file system error was encountered. ACTION Refer to the system administration manual. MESSAGE *** Cannot purge expanded DBECON file. (! !, !) (DBERR 20042) CAUSE A file system error was encountered. ACTION Refer to the system administration manual. MESSAGE *** Cannot write to expanded DBECON file.
ALLBASE/SQL Error Messages: 11007-22540 20049 20050 20051 20052 20053 20054 20055 20056 288 ACTION Refer to the system administration manual. MESSAGE *** Cannot write to BBSQLMIG file. (! !, !) (DBERR 20049) CAUSE A file system error was encountered. ACTION Refer to the system administration manual. MESSAGE *** Cannot rename BBSQLMIG file to DBECON file. (! !, !) (DBERR 20050) CAUSE A file system error was encountered. ACTION Refer to the system administration manual.
ALLBASE/SQL Error Messages: 11007-22540 20070 20080 20200 20201 20202 20203 Chapter 9 CAUSE Command was entered incorrectly. ACTION Issue the command again. You can use the HELP command to verify your syntax. MESSAGE *** SQLMIGRATE log file (AASQLMIG) already exists. (DBERR 20070) CAUSE AASQLMIG, a temporary file used by SQLMigrate, already exists in the same location as the DBECON file. Another user is probably running SQLMigrate on another DBEnvironment at the same time.
ALLBASE/SQL Error Messages: 11007-22540 keyword BACKWARD is only used when migrating a newer version DBEnvironment to one that is compatible with an older release of ALLBASE/SQL. 20204 20205 20206 20207 20208 290 ACTION Either change the keyword BACKWARD to FORWARD, or change the target version. Issue the command again. MESSAGE *** Cannot PREVIEW FORWARD to earlier version. (DBERR 20204) CAUSE A logic error was encountered in the command.
ALLBASE/SQL Error Messages: 11007-22540 available that will migrate your DBEnvironment. 20209 20210 20211 20220 MESSAGE *** DBEFileName is too long. Maximum length is !. (DBERR 20209) CAUSE The allowable length for the DBEFileName was exceeded. ACTION Issue the command again, using a valid DBEFileName. MESSAGE *** SystemFileName name is too long. Maximum length is !. (DBERR 20210) CAUSE The allowable length for the SystemFileName was exceeded.
ALLBASE/SQL Error Messages: 11007-22540 On HP-UX (csh): % setenv MIGLOGSZ 1000 On HP-UX (sh or ksh): $ MIGLOGSZ=1000 $ export MIGLOGSZ In the examples above, the size of the temporary log file will be 1000 pages. Set the MIGLOGSZ variable to the value needed to accomplish a migration for your DBEnvironment. 20330 20335 20336 20337 20340 292 MESSAGE ERROR - DBEFileName already exists in !. (DBERR 20330) CAUSE A row exists in SYSTEM.
ALLBASE/SQL Error Messages: 11007-22540 DBEFILE statement again. 20350 20360 20518 20520 20530 22540 Chapter 9 MESSAGE ERROR - DBEFileName has not been CREATED in !. (DBERR 20350) CAUSE You issued an ADD DBEFILE statement before a CREATE DBEFILE statement had been issued. ACTION Issue the CREATE DBEFILE statement, and then issue the ADD DBEFILE command again. MESSAGE ERROR - DBEFileName has already been ADDED to a DBEFILESET.
ALLBASE/SQL Error Messages: 11007-22540 ACTION Issue a CREATE DBEFILE statement followed by an ADD DBEFILE statement to add space to the SYSTEM DBEFileSet. If you are concerned about the amount of additional space being added, CREATE and ADD multiple small DBEFiles, rather than one large one. After the migration is complete, perform an UPDATE STATISTICS on SYSTEM.TABLE. Review SYSTEM.DBEFILE to determine the empty DBEFiles in the SYSTEM DBEFileset, and remove them.
10 ALLBASE/SQL Error Messages: 2280022800 23005 26002 26003 26004 MESSAGE DBEnvironment has already been started (DBERR 22800) CAUSE A REPAIR command was in progress when this message was issued. Another user is currently accessing the DBEnvironment. The REPAIR command may only be issued when the database is idle. ACTION Please try again later. MESSAGE START DBE NEWLOG disallowed. Need rollforward recovery.
ALLBASE/SQL Error Messages: 22800- 26005 26006 26007 26008 26009 26010 296 CAUSE An MPE/iX file system error occurred. ACTION Refer to the MPE/iX Error Message Manual, Volume 1 for an error description. MESSAGE ``Unlock on NETUsers file failed. (! !) (DBERR 26005) CAUSE An MPE/iX file system error occurred. ACTION Refer to the MPE/iX Error Message Manual, Volume 1 for an error description. MESSAGE ``Read failed on NETUsers file.
ALLBASE/SQL Error Messages: 22800- 26011 26012 26013 27002 27003 27004 Chapter 10 MESSAGE ``Write failed on temporary NETUsers file. (! !) (DBERR 26011) CAUSE An MPE/iX file system error occurred. ACTION Refer to the MPE/iX Error Message Manual, Volume 1 for an error description. MESSAGE Insufficient memory to allocate buffer. (DBERR 26012) CAUSE There is not enough memory to allocate buffer space for a new profile. ACTION Do not complete the operation.
ALLBASE/SQL Error Messages: 22800- 27005 27006 27007 27008 27009 27010 27011 298 ACTION Refer to the MPE/iX Error Message Manual, Volume 1 for an error description. MESSAGE Unlock on AliasDB file failed. (! !) (DBERR 27005) CAUSE An MPE/iX file system error occurred. ACTION Refer to the MPE/iX Error Message Manual, Volume 1 for an error description. MESSAGE Read failed on AliasDB file. (! !) (DBERR 27006) CAUSE An MPE/iX file system error occurred.
ALLBASE/SQL Error Messages: 22800- 28001 28002 28003 28004 28005 28006 28007 Chapter 10 ACTION Refer to the MPE/iX Error Message Manual, Volume 1 for an error description. MESSAGE Invalid NETUtil command. (DBERR 28001) CAUSE An invalid command was entered. ACTION Type HELP for a list of valid NETUtil commands. MESSAGE Insufficient capability, command disallowed. (DBERR 28002) CAUSE You must be MANAGER.SYS or have SM capability to execute this command.
ALLBASE/SQL Error Messages: 22800- 28008 28009 28010 28011 28012 28013 28014 28015 300 ACTION Refer to the MPE/iX Error Message Manual, Volume 1 for an error description. MESSAGE Invalid Machine Type. (! !) (DBERR 28008) CAUSE An invalid machine type was entered. Valid machine types are HP 3000 S900, HP 9000 S800, or HP 9000 S300. ACTION Re-enter the machine type. MESSAGE Invalid Datacom Type. (DBERR 28009) CAUSE You entered an invalid data communication type.
ALLBASE/SQL Error Messages: 22800- 28016 28017 28018 28019 28021 28022 28023 Chapter 10 CAUSE You attempted to enter an LU6.2 time out value that is not in the range. ACTION Enter the LU6.2 Time Out Value again. Valid LU6.2 time out values are in the range 0 to 28800. 0 implies no time outs. MESSAGE Invalid HP Session Type. (DBERR 28016) CAUSE You entered an HP LU6.2 API Session Type in the AliasDB file entry that does not conform to the edit specifications for this field.
ALLBASE/SQL Error Messages: 22800- 28024 28025 28030 28031 28032 28033 28034 28035 28036 302 ACTION Re-enter a valid machine type. MESSAGE Datacomm type must be ARPA or NS. (DBERR 28024) CAUSE You entered an invalid datacomm type. ACTION Re-enter a valid datacomm type. MESSAGE Datacomm type must be LU6.2. (DBERR 28025) CAUSE You entered an invalid datacomm type. ACTION Re-enter a valid datacomm type. MESSAGE Cannot migrate NETUsers file backward.
ALLBASE/SQL Error Messages: 22800- 28037 28038 28039 28040 28041 29001 29002 29003 Chapter 10 ACTION Refer to the MPE/iX Error Messages Manual, Volume I for an error description. MESSAGE Open failed on server list file. (! !) (DBERR 28037) CAUSE An MPE/iX file system error occurred. ACTION Refer to the MPE/iX Error Messages Manual, Volume I for an error description. MESSAGE Lock failed on server list file. (! !) (DBERR 28038) CAUSE An MPE/iX file system error occurred.
ALLBASE/SQL Error Messages: 22800- 29004 29010 29011 29440 30000 CAUSE A CONNECT or START DBE statement is expected. ACTION Add the appropriate statement to the application. MESSAGE The ALLBASE/SQL and ALLBASE/NET software on the server machine are older than the ALLBASE/SQL and ALLBASE/NET software on the client machine. (DBERR 29004) CAUSE You are running incompatible releases of ALLBASE/SQL and ALLBASE/NET on the client and server machines.
ALLBASE/SQL Error Messages: 22800- 30031 NetIPC Error: (DBERR 30031) Duplicate socket name. 30036 NetIPC Error: (DBERR 30036) Table of names is full. 30037 NetIPC Error: (DBERR 30037) Socket name not found. 30040 NetIPC Error: 30040) Unknown node. (DBERR 30043 NetIPC Error: Unable to contact remote registry server. (DBERR 30043) 30044 NetIPC Error: No response from remote registry server. (DBERR 30044) 30055 NetIPC Error: (DBERR 30055) Exceeded socket limit.
ALLBASE/SQL Error Messages: 22800- have sufficient resources. (DBERR 30131) 30158 NetIPC Error: rejected by remote. 31000 31004 31009 31014 31022 31023 31024 306 Connection request (DBERR 30158) ACTION Refer to the NetIPC Error Codes in the HP 9000 NetIPC Programmer's Guide. MESSAGE Datacommunication BSD failure. (DBERR 31000) CAUSE A data communication error occurred. ACTION Record as much information as possible and contact your HP Service Representative or Response Center.
ALLBASE/SQL Error Messages: 22800- 31032 31216 31219 31221 31222 31223 31225 Chapter 10 ACTION Close some files, then try to connect again. MESSAGE The send cannot be completed, because the connection has been shutdown either by the remote peer or by the client process. (DBERR 31032) CAUSE A data communication error occurred or the peer process does not exist. ACTION Record as much information as possible and contact your HP Service Representative or Response Center.
ALLBASE/SQL Error Messages: 22800- HP Service Representative or Response Center. 31226 31227 31229 31232 31233 31235 31238 308 MESSAGE The address is already in use. (DBERR 31226) CAUSE You tried to start the listener daemon, but it has already been started. ACTION No action necessary. MESSAGE The specified address is not available. (DBERR 31227) CAUSE The HOSTS.NET.SYS file is not set up correctly or there is a datacomm error.
ALLBASE/SQL Error Messages: 22800- transmission timeout. (DBERR 31238) 31239 31241 31243 31244 31900 31901 Chapter 10 CAUSE Internal timeout reached. ACTION Try to connect again. MESSAGE The attempt to connect to a remote system was rejected. (DBERR 31239) CAUSE An internal error occurred. The listener daemon is down. ACTION Remove the tmp/hpdaARPA.log or the tmp/hpdaNS.log file and restart the listener daemon. Verify that the ARPA listener is running.
ALLBASE/SQL Error Messages: 22800- 31902 31903 31904 31905 31992 31994 310 MESSAGE Server login does not exist on server node. (DBERR 31902) CAUSE Specified user, account or group does not exist on server. ACTION Check 'Get xxx Passwd - No such login' message in server log file hpdanslg.pub.sys (where xxx = user, account or group) to determine which part of login failed. Have system or account manager create account, user or group or use NETUtil to change server login.
ALLBASE/SQL Error Messages: 22800- user name. If it is the correct user name, add it to the server's password file. 31995 31996 31997 31998 31999 MESSAGE Hostname not found or the hosts file cannot be opened. (DBERR 31995) CAUSE The hostname cannot be found in the HOSTS.NET.SYS file or the HOSTS.NET.SYS file does not exist. MESSAGE The protocol file cannot be opened or the protocol name 'tcp' is not found. (DBERR 31996) CAUSE The PROTOCOL.NET.SYS file does exist or 'tcp' is not in the PROTOCOL.
ALLBASE/SQL Error Messages: 22800- attempt. 33003 33004 ACTION Correct the security parameters specified in the NETUtil AliasDB file entry. MESSAGE LU 6.2 Send not allowed, partner LU has send. (DBERR 33003) CAUSE The HP side of the LU 6.2 connection has attempted a send when a send is disallowed by the protocol. ACTION This error should not occur. In the event that it does, transmission errors may have occurred. Contact your HP service representative or Response Center. MESSAGE LU 6.
ALLBASE/SQL Error Messages: 22800- 33123 33124 33350 MESSAGE No DBEnvironment connected. (DBERR 33123) CAUSE Connection to a foreign DBE is expected but not found. ACTION Establish the connection to a foreign DBE. MESSAGE Already connected to a DBE. (DBERR 33124) CAUSE An attempt has been made to connect to a DBE while already connected to a foreign DBE. ACTION Release the current DBE connection before connecting to a DBE. MESSAGE Database server error !.
ALLBASE/SQL Error Messages: 22800- 34006 34008 34009 34010 34011 34013 34020 34021 314 MESSAGE DBCORE error. (FNC !, RC !, !, ! !) (DBERR 34006) CAUSE An unexpected internal error was encountered. ACTION Record as much information as possible and contact your HP Service Representative or Response Center. MESSAGE Unexpected INTERNAL error. (!, !, !, !) (DBERR 34008) CAUSE An unexpected internal error was encountered.
ALLBASE/SQL Error Messages: 22800- possible and contact your HP Service Representative or Response Center. 34022 34023 34030 34031 34071 34072 34076 Chapter 10 MESSAGE Number of data buffers not equal to DBECON value! (!, !, !) (DBERR 34022) CAUSE The size of the data buffer pool in memory does not match the size that is recorded in the DBECON file. ACTION Record as much information as possible and contact your HP Service Representative or Response Center.
ALLBASE/SQL Error Messages: 22800- Service Representative or Response Center. 34077 34100 34102 34103 34104 34105 34106 34107 34120 316 MESSAGE Number of qualifying locks exceeds internal maximum (max=!) (DBERR 34077) CAUSE A limit has been reached. ACTION Use the SET LOCKFILTER or SET LOCKTABFILTER commands to reduce the number of locks that qualify. If you need the limit increased, please contact your HP Service Representative or Response Center. MESSAGE Input too long.
ALLBASE/SQL Error Messages: 22800- length is !. (DBERR 34120) 34121 34122 34501 34502 34503 34504 34507 Chapter 10 CAUSE The allowable length for the SystemFileName was exceeded. ACTION Issue the command again. MESSAGE DBEFile name is not valid for this DBEnvironment. (DBERR 34121) CAUSE You did not specify a valid DBEFile name. ACTION Issue the command again. MESSAGE DBEFileSet name is not valid, or has no DBEFiles. (DBERR 34122) CAUSE You did not specify a valid DBEFileSet name.
ALLBASE/SQL Error Messages: 22800- 34530 34531 34540 34541 34550 34551 34552 34553 34554 318 MESSAGE DBEFileSetName is too long. Maximum length is !. (DBERR 34530) CAUSE The allowable length for the DBEFileSetName was exceeded. ACTION Issue the command again. MESSAGE DBEFileName is too long. Maximum length is !. (DBERR 34531) CAUSE The allowable length for the DBEFileName was exceeded. ACTION Issue the command again. MESSAGE OWNER.TABLE is too long. Maximum length is !.
ALLBASE/SQL Error Messages: 22800- 34555 34556 34557 34560 34585 34610 Chapter 10 CAUSE A file system error was encountered. ACTION Refer to the MPE/iX Error Message Manual, Volume 1. MESSAGE SystemFileName could not be created. (HPFOPEN !, !, !, !) (DBERR 34555) CAUSE A file system error was encountered. ACTION Refer to the MPE/iX Error Message Manual, Volume 1. MESSAGE SystemFileName could not be rewritten. (HPFOPEN !, !, !, !) (DBERR 34556) CAUSE A file system error was encountered.
ALLBASE/SQL Error Messages: 22800- DBEnvironment, and the tables that exist within them. 34630 35000 35400 35401 35402 35404 35405 35406 320 MESSAGE The timeout expired during an attempt to "Get Statistics" on a temporary table within DBEFileset ! (DBERR 34630). CAUSE SQLMON was not able to obtain some internal resource that was needed to complete the last command. ACTION You may wish to use the SET DBEFILESET command to specify another DBEFileset, and issue your original command once again.
ALLBASE/SQL Error Messages: 22800- 35407 35408 35409 35410 35411 35414 140336 CAUSE The group password specified for logon is not valid. ACTION Determine the correct password. MESSAGE Missing user password. (DBERR 35407) CAUSE A user password is required, but was not specified. ACTION Supply the password for the remote logon. MESSAGE Missing account password. (DBERR 35408) CAUSE An account password is required, but was not specified. ACTION Supply the password for the remote logon.
ALLBASE/SQL Error Messages: 22800- enhancements required for online backup. ACTION Contact your HP Service Representative to obtain a version of STORE.PUB.SYS that supports online backup or perform a static store of the DBEnvironment using the procedures described in the "Backup and Recovery" chapter of the ALLBASE/SQL Database Administration Guide. 140338 322 MESSAGE Formal designator is invalid. (DBERR 140338) CAUSE The version of STORE.PUB.
