SQL/MP Messages Manual

Message Handling
HP NonStop SQL/MP Messages Manual—427720-006
1-2
Errors and Warnings
Errors and Warnings
An SQL/MP message can be a warning or an error:
•
A warning has a positive number associated with it. A warning indicates that your
request completed successfully but might not be optimal. The text of the message
contains information that describes why the warning occurred.
You might want to perform some action to ensure the most efficient request
handling and outcome. For example, if statistics are not available, the SQL/MP
software executes the request but issues a warning because optimal path
information was not available. You might want to make sure statistics are available
before attempting a similar request.
•
An error message can have a negative or positive number associated with it. For
example, audit fix-up processes and the file system can return error messages with
positive numbers. An error indicates that your request did not complete
successfully. The error message contains information that describes why the
request failed.
You can perform some action to make the request complete successfully. For
example, if a query returns a security error that indicates you cannot access a
table, you must have appropriate security access before the request will complete
successfully.
Thus, both warnings and errors notify you of a situation that might require attention.
All audit fix-up messages listed in Section 15, Audit Fix-Up Messages (16000 to
16999) of this manual and the file-system messages listed in Section 16, File-System
Messages of this manual are errors. The messages in Sections 2 through 14 of this
manual can be returned as errors, warnings, or both. This manual does not distinguish
between errors and warnings in individual message descriptions.
Future Changes to Messages
HP might change the SQL message content from release to release to:
•
Add new messages as needed.
•
Modify messages according to these guidelines:
°
Change wording of messages (including message text and cause, effect, and
recovery descriptions) when necessary. Note, however, that if changes in
wording alter the meaning of a message, HP creates a new message instead
of changing the existing message.
°
Add message variables after existing variables.
•
Delete messages after the messages are obsolete for at least three SQL/MP
releases.