ALLBASE/SQL Message Manual (36216-90213)

98 Chapter3
ALLBASE/SQL Error Messages: 1-745
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.
527 MESSAGE Error ! occurred while opening Recovery File.
(DBERR 527)
CAUSE A file system error occurred while trying to create the
recovery file. This is usually due to an incorrect name
being used, or the file/directory permissions are not set
correctly. This may also be due to a lack of disk space.
ACTION Check the recovery file name specified and make sure it
does not exist before doing the audit. Also check disk
space, and directory permissions.
529 MESSAGE Unacceptable response entered (will use
default). (DBERR 529)
CAUSE An invalid response was entered for the prompt.
SQLAudit will use the default response (which is the first
response listed).
ACTION Check the response that was entered.
533 MESSAGE SYSTEM command unsuccessful. Return code is
!. (DBERR 533)
CAUSE SQLAudit attempted to execute the system command that
was entered and it encountered an error returned from the
operating system.
ACTION Check the command entered to determine if it is a valid
operating system command.
534 MESSAGE No help for that command. (DBERR 534) HELP
keywords are GENERAL, MAIN, and SUMMARY. Type '//'
to leave SQLAUDIT HELP.
CAUSE You attempted to obtain help from SQLAudit on an
unknown subject.
ACTION Check the subject entered. Allowed subjects are any
SQLAudit command, or the keywords GENERAL, MAIN,
or SUMMARY. If you wish to leave the SQLAudit help
facility, type '//'.
535 MESSAGE The requested editor could not be scheduled
due to error !. (DBERR 535)
CAUSE SQLAudit was unable to start the editor that is currently