HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Cont.)
20042 MESSAGE *** Cannot purge expanded DBECON file. (! !, !)
(DBERR 20042)
CAUSE A file system error was encountered.
ACTION Refer to the system administration manual.
----------------------------------------------------------------------------
20043 MESSAGE *** Cannot write to expanded DBECON file. (! !,
!) (DBERR 20043)
CAUSE A file system error was encountered.
ACTION Refer to the system administration manual.
----------------------------------------------------------------------------
20044 MESSAGE *** Cannot rename DBECON file to BBSQLMIG file.
(! !, !) (DBERR 20044)
CAUSE A file system error was encountered.
ACTION Refer to the system administration manual.
----------------------------------------------------------------------------
20045 MESSAGE *** Cannot allocate expanded DBECON file. (! !,
!) (DBERR 20045)
CAUSE A file system error was encountered. There
probably is not enough extra disk space on your
system.
ACTION Refer to the system administration manual. Try to
create more free disk space before using SQLMigrate
again.
----------------------------------------------------------------------------
20046 MESSAGE *** Cannot open BBSQLMIG file. (! !, !) (DBERR
20046)
CAUSE A file system error was encountered when trying to
create a file named BBSQLMIG in the same directory
as the DBECon file. It probably already exists.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1.
Remove any files named BBSQLMIG from the same
directory as the DBECon file before using
SQLMigrate again.
----------------------------------------------------------------------------
20047 MESSAGE *** Cannot close BBSQLMIG file. (! !, !) (DBERR
20047)
CAUSE A file system error was encountered.
ACTION Refer to the system administration manual.
----------------------------------------------------------------------------
20048 MESSAGE *** Cannot purge BBSQLMIG file. (! !, !) (DBERR
20048)
CAUSE A file system error was encountered.
ACTION Refer to the system administration manual.
----------------------------------------------------------------------------
20049 MESSAGE *** Cannot write to BBSQLMIG file. (! !, !)
(DBERR 20049)
CAUSE A file system error was encountered.
ACTION Refer to the system administration manual.
----------------------------------------------------------------------------
20050 MESSAGE *** Cannot rename BBSQLMIG file to DBECON file.
(! !, !) (DBERR 20050)
CAUSE A file system error was encountered.
ACTION Refer to the system administration manual.
----------------------------------------------------------------------------
20051 MESSAGE *** Illegal command. (DBERR 20051)
CAUSE SQLMigrate did not recognize the command that was
entered.
ACTION Use the HELP command or refer to the ALLBASE/SQL
Database Administration Guide to determine the
valid SQLMigrate commands.
----------------------------------------------------------------------------
20052 MESSAGE Input too long. Maximum length is !. (DBERR
20052)
CAUSE The total length of the input line exceeded the
allowed limit.
ACTION Issue the command again.
----------------------------------------------------------------------------
20053 MESSAGE *** Input limit reached. No semicolon found.
(DBERR 20053)
CAUSE SQLMigrate commands must be terminated with a
semicolon. None was found in the input string
submitted.
ACTION Issue the command again.
----------------------------------------------------------------------------
20054 MESSAGE *** Unexpected semicolon found. (DBERR 20054)
CAUSE A semicolon was found in the input string in an
unexpected location. Semicolons are allowed
either: 1) at the end of the command or 2) in the
DBEnvironmentName, when the operating system file
naming convention allows it.
ACTION Issue the command again without the illegal
semicolon.
----------------------------------------------------------------------------
20055 MESSAGE *** Unexpected end of input. (DBERR 20055)
CAUSE An error was encountered trying to retrieve the
next command.
ACTION Check the output and input to determine if all
commands executed properly.
----------------------------------------------------------------------------
20056 MESSAGE *** Illegal syntax. (DBERR 20056)
CAUSE Command was entered incorrectly.
ACTION Issue the command again. You can use the HELP
command to verify your syntax.
----------------------------------------------------------------------------
20070 MESSAGE *** SQLMIGRATE log file (AASQLMIG) already
exists. (DBERR 20070)
CAUSE AASQLMIG, a temporary file used by SQLMigrate,
already exists in the same location as the DBECON
file. Another user is probably running SQLMigrate
on another DBEnvironment at the same time.
ACTION Try again later.
----------------------------------------------------------------------------
20080 MESSAGE *** Cannot create BBSQLMIG file. (! !, !) (DBERR
20080)
CAUSE BBSQLMIG, a temporary file used by SQLMigrate,
already exists in the same location as the DBECON
file. Another user is probably running SQLMigrate
on another DBEnvironment at the same time.
ACTION Try again later.
----------------------------------------------------------------------------
20200 MESSAGE *** Invalid target version. Use the SHOW
VERSIONS command. (DBERR 20200)
CAUSE The release of SQLMigrate being used does not
support the version that was specified in the last
command.
ACTION Use the SHOW VERSIONS command to determine the
valid versions that may be used with this release
of SQLMigrate.
----------------------------------------------------------------------------
20201 MESSAGE *** DBEnvironmentName is too long. Maximum
length is !. (DBERR 20201)
CAUSE A DBEnvironmentName is restricted to operating
system file naming conventions.
ACTION Refer to the MPE/iX General User's Reference Manual
for information on file naming conventions.
----------------------------------------------------------------------------
20202 MESSAGE *** Cannot MIGRATE FORWARD to earlier version.
(DBERR 20202)
CAUSE A logic error was encountered in the command. The
keyword FORWARD is only used when migrating an
older version DBEnvironment to one that is
compatible with a newer release of ALLBASE/SQL.
ACTION Either change the keyword FORWARD to BACKWARD, or
change the target version. Issue the command
again.
----------------------------------------------------------------------------
20203 MESSAGE *** Cannot MIGRATE BACKWARD to later version.
(DBERR 20203)
CAUSE A logic error was encountered in the command. The
keyword BACKWARD is only used when migrating a
newer version DBEnvironment to one that is
compatible with an older release of ALLBASE/SQL.
ACTION Either change the keyword BACKWARD to FORWARD, or
change the target version. Issue the command
again.
----------------------------------------------------------------------------
20204 MESSAGE *** Cannot PREVIEW FORWARD to earlier version.
(DBERR 20204)
CAUSE A logic error was encountered in the command. The
keyword FORWARD is only used when previewing an
older version DBEnvironment to one that is
compatible with a newer release of ALLBASE/SQL.
ACTION Either change the keyword FORWARD to BACKWARD, or
change the target version. Issue the command
again.
----------------------------------------------------------------------------
20205 MESSAGE *** Cannot PREVIEW BACKWARD to later version.
(DBERR 20205)
CAUSE A logic error was encountered in the command. The
keyword BACKWARD is only used when previewing a
newer version DBEnvironment to one that is
compatible with an older release of ALLBASE/SQL.
ACTION Either change the keyword BACKWARD to FORWARD, or
change the target version. Issue the command
again.
----------------------------------------------------------------------------
20206 MESSAGE *** DBEnvironment is already compatible with
target version. (DBERR 20206)
CAUSE The version of the DBEnvironment is already the
same as the target version of the command.
ACTION If the target version was incorrectly specified,
modify it and issue the command again.
----------------------------------------------------------------------------
20207 MESSAGE *** Existing DBEnvironment not supported by
SQLMigrate (DBERR 20207)
CAUSE The release of SQLMigrate being used does not
support migrations for the DBEnvironment specified
in the command.
ACTION Contact your HP Service Representative or Response
Center to determine if another release of
SQLMigrate is available that will migrate your
DBEnvironment.
----------------------------------------------------------------------------
20208 MESSAGE *** DBEnvironment version is not recognized by
SQLMigrate. (!) (DBERR 20208)
CAUSE The release of SQLMigrate being used does not
recognize the version number of your DBEnvironment,
and cannot support migrations for it.
ACTION Contact your HP Service Representative or Response
Center to determine if another release of
SQLMigrate is available that will migrate your
DBEnvironment.
----------------------------------------------------------------------------
20209 MESSAGE *** DBEFileName is too long. Maximum length is
!. (DBERR 20209)
CAUSE The allowable length for the DBEFileName was
exceeded.
ACTION Issue the command again, using a valid DBEFileName.
----------------------------------------------------------------------------
20210 MESSAGE *** SystemFileName name is too long. Maximum
length is !. (DBERR 20210)
CAUSE The allowable length for the SystemFileName was
exceeded.
ACTION Issue the command again, using a valid
SystemFileName.
----------------------------------------------------------------------------
20211 MESSAGE *** Migration path is not supported by SQLMIGRATE
(!,!).(DBERR 20211)
CAUSE SQLMigrate can only be used for a migration path
to/from the release of ALLBASE/SQL on which
SQLMigrate came. The attempted migration was for a
path that did not involve the current release of
ALLBASE/SQL.
ACTION Specify a valid migration path.
----------------------------------------------------------------------------
20220 MESSAGE Log full. (DBERR 20220)
CAUSE The log file is full.
ACTION If you see this message, you should notify your HP
Service Representative or Response Center, because
a problem probably exists in SQLMIGRATE.
During the MIGRATE, PREVIEW, CREATE DBEFILE, and
ADD DBEFILE commands, SQLMIGRATE "connects" to the
DBEnvironment by performing a START DBE NEWLOG
command using a temporary log file. On MPE/iX, the
file is named "AASQLMIG" and is created in the same
group as the DBECON file. On HP-UX, the file is
named "/tmp/AASQLMIGxxxxxx", where "xxxxx" is a
unique id for each SQLMIGRATE process.
SQLMIGRATE needs to create it's own log file for
several reasons, but the most important ones are 1)
the existing log file(s) may not be compatible with
the newest release, and 2) the existing log file(s)
may not have enough free space on them. SQLMIGRATE
creates the log in non-archive mode (so it is
circular), and tries to use it efficiently so that
a log full condition does not occur.
As a workaround, you can increase the size of the
temporary log file (the default size is 400 pages)
by issuing one of the following before running
SQLMIGRATE:
On MPE/iX:
: setjcw MIGLOGSZ 1000
On HP-UX (csh):
% setenv MIGLOGSZ 1000
On HP-UX (sh or ksh):
$ MIGLOGSZ=1000
$ export MIGLOGSZ
In the examples above, the size of the temporary
log file will be 1000 pages. Set the MIGLOGSZ
variable to the value needed to accomplish a
migration for your DBEnvironment.
----------------------------------------------------------------------------
20330 MESSAGE ERROR - DBEFileName already exists in !. (DBERR
20330)
CAUSE A row exists in SYSTEM.DBEFILE which has a DBEFNAME
that is the same as the DBEFileName that was
specified.
ACTION Issue the CREATE DBEFILE statement again, using a
different DBEFileName.
----------------------------------------------------------------------------
20335 MESSAGE ERROR - DBEFILE size is too small. Minimum size
is !. (DBERR 20335)
CAUSE The "WITH PAGES = " parameter did not meet minimum
requirements.
ACTION Issue the CREATE DBEFILE statement again, using a
larger value in the "WITH PAGES = " parameter.
----------------------------------------------------------------------------