HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Continued)
20336 MESSAGE ERROR - DBEFILE size is too large. Maximum size
is ! (DBERR 20336)
CAUSE The "WITH PAGES = " parameter exceeded maximum
requirements.
ACTION Issue the CREATE DBEFILE statement again, using a
smaller value in the "WITH PAGES = " parameter.
----------------------------------------------------------------------------
20337 MESSAGE ERROR - DBEFILE name cannot be partially or fully
qualified. (DBERR 20337)
CAUSE The DBEFileName you specified was qualified by an
MPE/iX group or account.
ACTION Issue the command again with an unqualified
DBEFileName.
----------------------------------------------------------------------------
20340 MESSAGE ERROR - SystemFileName already exists. (DBERR
20340)
CAUSE Either the SystemFileName already exists as a
physical file, or a row exists in SYSTEM.DBEFILE
which has a FILEID that is the same as the
SystemFileName.
ACTION Use a different SystemFileName, and issue the
CREATE DBEFILE statement again.
----------------------------------------------------------------------------
20350 MESSAGE ERROR - DBEFileName has not been CREATED in !.
(DBERR 20350)
CAUSE You issued an ADD DBEFILE statement before a CREATE
DBEFILE statement had been issued.
ACTION Issue the CREATE DBEFILE statement, and then issue
the ADD DBEFILE command again.
----------------------------------------------------------------------------
20360 MESSAGE ERROR - DBEFileName has already been ADDED to a
DBEFILESET. (DBERR 20360)
CAUSE The row for DBEFileName in SYSTEM DBEFILE indicates
that the DBEFSNAME has already been assigned.
ACTION The name specified in the ADD DBEFILE statement was
probably incorrect. Modify it, and issue the
command again.
----------------------------------------------------------------------------
20518 MESSAGE ERROR - User is not DBECreator. (DBERR 20518)
CAUSE Only the DBECreator or the system manager is
authorized to use SQLMigrate.
ACTION Contact someone having the proper capabilities to
use SQLMigrate.
----------------------------------------------------------------------------
20520 MESSAGE ERROR - Invalid DBECON file format detected.
(DBERR 20520)
CAUSE Migration is not supported for this DBEnvironment
using SQLMigrate.
ACTION UNLOAD and LOAD your data to install another
release of ALLBASE/SQL.
----------------------------------------------------------------------------
20530 MESSAGE ERROR - Previous failed attempt to MIGRATE
detected. (DBERR 20530)
CAUSE SQLMigrate was used is the past to migrate the
DBEnvironment, but the migration was unsuccessful.
ACTION Purge the DBEnvironment and restore the backup
version before attempting migration again.
----------------------------------------------------------------------------
22540 MESSAGE ERROR - Insufficient space in the SYSTEM
DBEFileSet. (DBERR 22540)
DBEFile(s) containing ! pages need to be added to
the SYSTEM DBEFileSet before attempting the
migration.
CAUSE The space estimate calculated during the PREVIEW
command indicates that more space is needed for the
migration than is currently present in the SYSTEM
DBEFileSet.
ACTION Issue a CREATE DBEFILE statement followed by an ADD
DBEFILE statement to add space to the SYSTEM
DBEFileSet.
If you are concerned about the amount of additional
space being added, CREATE and ADD multiple small
DBEFiles, rather than one large one. After the
migration is complete, perform an UPDATE STATISTICS
on SYSTEM.TABLE. Review SYSTEM.DBEFILE to determine
the empty DBEFiles in the SYSTEM DBEFileset, and
remove them. Remember to leave about 20% of the
pages free for the temporary processing needs of
ALLBASE/SQL.
----------------------------------------------------------------------------
22800 MESSAGE DBEnvironment has already been started (DBERR
22800)
CAUSE A REPAIR command was in progress when this message
was issued. Another user is currently accessing
the DBEnvironment. The REPAIR command may only be
issued when the database is idle.
ACTION Please try again later.
----------------------------------------------------------------------------
23005 MESSAGE START DBE NEWLOG disallowed. Need rollforward
recovery. (DBERR 23005)
CAUSE SQLMIG cannot be used on a DBEnvironment that has
incomplete transactions in its log. You probably
did not follow the steps required for forward
migration, which are documented in the "DBA Tasks
and Tools" chapter of the ALLBASE/SQL Database
Administration Guide.
ACTION Restore the old version of the operating system and
the old version of ISQL onto your machine. Run the
old version of ISQL and issue a START DBE statement
to resolve the incomplete transactions in the log.
----------------------------------------------------------------------------
26002 MESSAGE No matching profile found in the NETUsers file.
(DBERR 26002)
CAUSE ALLBASE/SQL attempted to connect to a remote
DBEnvironment. Two error messages may be
displayed. This is the second message and
indicates that the NETUser profile either does not
exist or was entered incorrectly in the NETUsers
file.
ACTION Add the NETUser name to the NETUsers file or use
the SHOW USER command to check for correct spelling
of NETUser names in the NETUsers file.
----------------------------------------------------------------------------
26003 MESSAGE New value(s) already exists in NETUsers file,
operation not performed. (DBERR 26003)
CAUSE The NETUser name you specified is already in the
NETUsers file.
ACTION Enter a unique NETUser name.
----------------------------------------------------------------------------
26004 MESSAGE Lock on NETUsers file failed. (! !) (DBERR
26004)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------
26005 MESSAGE Unlock on NETUsers file failed. (! !) (DBERR
26005)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------
26006 MESSAGE Read failed on NETUsers file. (! !) (DBERR
26006)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------
26007 MESSAGE Write failed on NETUsers file. (! !) (DBERR
26007)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------
26008 MESSAGE File system error on NETUsers file. (! !)
(DBERR 26008)
CAUSE ALLBASE/SQL attempted to connect to a remote
DBEnvironment. Two error messages may be
displayed. This is the second message and
indicates that there is no NETUsers file or that
the permissions are not set correctly.
ACTION If the DBEnvironment you want to connect to is on
the local node, check the spelling of the
DBEnvironment name. If the DBEnvironment you want
to connect to is on a remote node, have the system
administrator set up the NETUsers file.
----------------------------------------------------------------------------
26009 MESSAGE The NETUsers file is empty. (DBERR 26009)
CAUSE You tried to "show" profiles in an empty NETUsers
file. Profiles in the NETUsers file have been
deleted.
ACTION Contact the system administrator to add profiles to
the NETUsers file.
----------------------------------------------------------------------------
26010 MESSAGE Open failed on temporary NETUsers file. (! !)
(DBERR 26010)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------
26011 MESSAGE Write failed on temporary NETUsers file. (! !)
(DBERR 26011)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------
26012 MESSAGE Insufficient memory to allocate buffer. (DBERR
26012)
CAUSE There is not enough memory to allocate buffer space
for a new profile.
ACTION Do not complete the operation. Record as much
information as possible and contact your HP Service
Representative or Response Center.
----------------------------------------------------------------------------
26013 MESSAGE The NETUsers file is being accessed. Operation
could not be performed. (DBERR 26013)
CAUSE The NETUsers file is currently open by someone else
and cannot be deleted.
ACTION Try again later.
----------------------------------------------------------------------------
27002 MESSAGE No matching profile found in the AliasDB file.
(DBERR 27002)
CAUSE ALLBASE/SQL attempted to connect to a remote
DBEnvironment. Two error messages may be
displayed. This is the second message and
indicates that the alias profile either does not
exist or was entered incorrectly in the AliasDB
file.
If this is the only error message returned, you are
using a diskless machine to access a DBEnvironment
on another machine.
ACTION Ask the system administrator to enter an alias
profile in the AliasDB file or check the spelling
of the DBEnvironment name in the AliasDB file. For
more information on configuring ALLBASE/NET in
order to access a remote DBEnvironment, refer to
the ALLBASE/NET User's Guide
----------------------------------------------------------------------------
27003 MESSAGE New value(s) already exists in AliasDB file,
operation not performed. (DBERR 27003)
CAUSE The alias name which you are trying to add or
change already exists in the AliasDB file.
ACTION Enter a unique alias name.
----------------------------------------------------------------------------
27004 MESSAGE Lock on AliasDB file failed. (! !) (DBERR
27004)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------
27005 MESSAGE Unlock on AliasDB file failed. (! !) (DBERR
27005)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------
27006 MESSAGE Read failed on AliasDB file. (! !) (DBERR 27006)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------
27007 MESSAGE Write failed on AliasDB file. (! !) (DBERR
27007)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------
27008 MESSAGE File system error on AliasDB file. (! !) (DBERR
27008)
CAUSE ALLBASE/SQL attempted to connect to a remote
DBEnvironment. Two error messages may be
displayed. This is the second message and
indicates that there is no AliasDB file or that the
permissions are not set correctly.
ACTION If the DBEnvironment you want to connect to is on
the local node, check the spelling of the
DBEnvironment name. If the DBEnvironment you want
to connect to is on a remote node, have the system
administrator set up the AliasDB file.
----------------------------------------------------------------------------
27009 MESSAGE The AliasDB file is empty. (DBERR 27009)
CAUSE You tried to "show" profiles from an empty AliasDB
file. Profiles in the AliasDB file have been
deleted.
ACTION Contact the system administrator.
----------------------------------------------------------------------------
27010 MESSAGE Open failed on temporary AliasDB file. (! !)
(DBERR 27010)
CAUSE An MPE/iX file system error occurred.
ACTION Refer to the MPE/iX Error Message Manual, Volume 1
for an error description.
----------------------------------------------------------------------------