ALLBASE/SQL Message Manual (36216-90213)

Chapter 3 95
ALLBASE/SQL Error Messages: 1-745
ACTION Contact your system administrator.
401 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.
402 MESSAGE Invalid replacement/insertion string. (DBERR
402)
CAUSE In the REDO command, you specified a replacement or
insertion string containing invalid bytes.
ACTION Issue the insert or replace command again, specifying a
valid string.
403 MESSAGE Internal native language support error.
(DBERR 403)
CAUSE An internal Native Language Support error occurred,
probably due to an invalid character in input.
ACTION Issue your command again, specifying valid input. If this
does not solve the problem, contact your system
administrator.
501 MESSAGE Error ! occurred while opening file. (DBERR
501)
CAUSE Error occurred while you were opening a file. Usually the
error is due to file permissions, or the name being
misspelled.
ACTION Check the name of the file to determine if it is spelled
correctly, and check the file permissions assigned.
503 MESSAGE Invalid Command. (DBERR 503)
CAUSE You entered a command that SQLAudit does not
recognize.
ACTION Check the last command entered.
504 MESSAGE Invalid Lock Point found in Audit Point File.
(DBERR 504)
CAUSE The Audit Point File contains a log file lockpoint that is
invalid. You probably used a Recovery File (generated by
the AUDIT command) for the Audit Point file for the
LOCK AUDITPOINT command.
ACTION LOCK AUDITPOINT should only use Audit Point files
that were generated by calling GET AUDITPOINT.
507 MESSAGE Log history does not go back far enough for