HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Continued)
340 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. If you did not intend to convert the
data in the input file, execute the SET CONVERT OFF
command and issue the LOAD command again.
----------------------------------------------------------------------------
341 MESSAGE Description file not allowed with CONVERT option.
(DBERR 341)
CAUSE You specified a description file in the LOAD
command when the SET CONVERT option is not OFF.
ACTION Issue the LOAD command again without the
description file parameter. If you did not intend
to convert the data in the input file, execute the
SET CONVERT OFF command and issue the LOAD command
again.
----------------------------------------------------------------------------
342 MESSAGE Unsupported Data Format. (DBERR 342)
CAUSE The SET CONVERT option is not OFF, and the data
type of the ALLBASE/SQL column specified in the
LOAD command is unsupported.
ACTION Issue the LOAD command with an ALLBASE/SQL data
type that is supported by the conversion operation.
If you do not want to convert the data in the input
file, execute the SET CONVERT OFF command and issue
the LOAD command again.
----------------------------------------------------------------------------
343 MESSAGE Data type of ! not supported with the CONVERT
option. (DBERR 343)
CAUSE The SET CONVERT option is not OFF, and the data
type of the ALLBASE/SQL column specified in the
LOAD command is unsupported.
ACTION Issue the LOAD command with an ALLBASE/SQL data
type that is supported by the conversion operation.
If you do not want to convert the data in the input
file, execute the SET CONVERT OFF command and issue
the LOAD command again.
----------------------------------------------------------------------------
400 MESSAGE Unable to load native language information.
(DBERR 400)
CAUSE The character set attribute and upshift tables for
your language could not be loaded.
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
partition !. (DBERR 507)
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. If it is
necessary to get the unaudited transactions, the
SQLUtil command WRAPDBE can be used to retrieve
them. See the ALLBASE/SQL Database Administration
Guide to determine how best to do this.
----------------------------------------------------------------------------
508 MESSAGE Unable to open scan for partition ! due to status
of !. (DBERR 508)
CAUSE An unexpected error occurred while opening the log
file scan for the given set of partitions.
ACTION Contact your HP Service Representative or Response
Center.
----------------------------------------------------------------------------
512 MESSAGE Log scan could not be successfully opened.
(DBERR 512)
CAUSE Due to previous errors, the log scan could not be
opened. No auditing is possible for the given list
of partitions when this happens.
ACTION Verify the list of partitions is correct and check
the previous reported errors to determine possible
actions.
----------------------------------------------------------------------------
513 MESSAGE Error ! occurred while reading Audit Point File.
(DBERR 513)
CAUSE A file system error occurred while reading the
Audit Point File. Usually this may occur if an
invalid Audit Point File has been entered.
ACTION Check the file name entered to determine if
correct.
----------------------------------------------------------------------------
514 MESSAGE File is not a valid Audit Point File. (DBERR
514)
CAUSE SQLAudit has determined that the file is not an
Audit Point File.
ACTION Check the file name entered to determine if
correct.
----------------------------------------------------------------------------
515 MESSAGE Error ! occurred while writing Audit Point File.
(DBERR 515)
CAUSE You encountered a file system error while trying to
create and write out the audit point information
into the file. Usually this is caused by file
permissions, or possibly lack of disk space.
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.
----------------------------------------------------------------------------
517 MESSAGE Native Language Support Error ! encountered.
(DBERR 517)
CAUSE A native language support (NLS) error was
encountered by the last command. This usually
means that the proper language was not correctly
installed on the system, or that you may have an
invalid language specified.
ACTION Check with the system administrator to insure that
your language has been installed on the system, and
check the language to ensure it is correct.
----------------------------------------------------------------------------
519 MESSAGE Non Existent File entered. (DBERR 519)
CAUSE You entered a file name that does not exist on the
system.
ACTION Check the file name that was entered to ensure it
is correct.
----------------------------------------------------------------------------
520 MESSAGE Error ! occurred while closing file. (DBERR 520)
CAUSE A file system error occurred while closing a file.
This may be due to the file or directory
permissions, or a lack of disk space on the system.
ACTION Check the file and directory permissions, and the
amount of disk space on the system.
----------------------------------------------------------------------------
521 MESSAGE Invalid partition number entered. (DBERR 521)
CAUSE You entered a partition number or name which is not
allowed. Partition numbers must be in the range of
1 to 32767 inclusive. Valid partition names are
DEFINITION, STORAGE, AUTHORIZATION, and SECTION.
ACTION Check the partition name or number that was
entered.
----------------------------------------------------------------------------
524 MESSAGE Ending Audit Point missing partition instance !
(!). (DBERR 524)
CAUSE This should only be possible if the database has
been hard resynced by an ALLBASE/REPLICATE user.
ACTION Determine if the database is being used as a master
or slave in an ALLBASE/REPLICATE environment and
whether it has been hard resynced lately. If it
has been hard resynced, a new beginning audit point
should be defined after the hard resync has
finished.
----------------------------------------------------------------------------
526 MESSAGE Transaction encountered that is greater than
ending transaction for partition instance ! (!).
(DBERR 526)
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 set.
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.
----------------------------------------------------------------------------
701 MESSAGE SQLGEN Error detected. SQLExplain messages will
follow. (DBERR 701)
CAUSE An unexpected ALLBASE/SQL error occurred.
ACTION Read the accompanying SQLExplain message to
determine the reason for the error and take
corrective action. If the error persists, contact
your database administrator.
----------------------------------------------------------------------------
702 MESSAGE Internal error. Missing message for SQLCODE of
!. (DBERR 702)
CAUSE The ALLBASE/SQL message catalog does not contain
the message associated with error encountered.
ACTION Contact your database administrator.
----------------------------------------------------------------------------
703 MESSAGE Could not CONNECT to DBEnvironment. (DBERR 703)
CAUSE SQLGEN could not connect to the DBEnvironment,
possibly because the name was not entered correctly
or the AUTOSTART option is OFF.
ACTION Correct conditions that may have caused the error.
If the error persist contact your database
administrator.
----------------------------------------------------------------------------