Messages are presented in numerical order. The messages are
categorized as follows:
1 - 499 | ISQL messages |
500 - 699 | SQLAudit messages |
700 - 799 | SQLGEN messages |
1000 - 1999 | Parser and linearizer messages |
2000 - 4999 | SQLCore messages |
7000 - 7999 | Reserved for use in RAISE ERROR |
8000 - 8999 | SQLUtil messages |
9000 - 9999 | ACI messages |
10000 - 12999 | Preprocessor messages |
13000 - 13499 | DBCore messages |
13500 - 13699 | ALLBASE/Turbo CONNECT runtime
messages |
13700 - 15999 | DBCore messages |
16000 - 16999 | DBECon messages |
20000 - 20999 | SQLMigrate messages |
25000 - 29999 | ALLBASE/NET messages |
30000 - 30999 | Data communication NetIPC messages |
31000 - 31899 | Data communication BSD messages |
31900 - 31999 | ALLBASE/NET common messages |
32000 - 32999 | ATCUtil messages |
33000 - 33499 | ALLBASE/DB2 CONNECT messages |
34000 - 34999 | SQLMON messages |
(unnumbered) | Console error messages |
CAUSE and ACTION for Messages |
 |
Each message in this manual is followed by a CAUSE, which
gives information as to why the warning or error occurred. This
is followed by an ACTION, which gives information on how to resolve
the problem, refers the user to an appropriate manual, or suggests contacting
an HP Service Representative or the Response Center. For example:
- 13
- MESSAGE
! not a column name in table !. (DBERR 13)
- CAUSE
The column you specified in the LOAD EXTERNAL command
does not exist in the table specified.
- ACTION
Use the INFO command to check which columns are
in the specified table.
Use of Exclamation Points |
 |
Some messages contain one or more exclamation points (!),
which are replaced by more specific information (such as a number,
filename, or subsystem name) when the condition occurs. For example,
if the filename you specified was PurchDF1, this message is received:
Error erasing file 'PurchDF1'. (DBERR 7)
|
The message is documented in this manual as:
Error erasing file '!'. (DBERR 7)
|