Chapter 11 ALLBASE/SQL Error Message 20047-140336

*** Cannot close BBSQLMIG file. (! !, !) (DBERR 20047)

A file system error was encountered.

Refer to the system administration manual.

*** Cannot purge BBSQLMIG file. (! !, !) (DBERR 20048)

A file system error was encountered.

Refer to the system administration manual.

*** Cannot write to BBSQLMIG file. (! !, !) (DBERR 20049)

A file system error was encountered.

Refer to the system administration manual.

*** Cannot rename BBSQLMIG file to DBECON file. (! !, !) (DBERR 20050)

A file system error was encountered.

Refer to the system administration manual.

*** Illegal command. (DBERR 20051)

SQLMigrate did not recognize the command that was entered.

Use the HELP command or refer to the ALLBASE/SQL Database Administration Guide to determine the valid SQLMigrate commands.

Input too long. Maximum length is !. (DBERR 20052)

The total length of the input line exceeded the allowed limit.

Issue the command again.

*** Input limit reached. No semicolon found. (DBERR 20053)

SQLMigrate commands must be terminated with a semicolon. None was found in the input string submitted.

Issue the command again.

*** Unexpected semicolon found. (DBERR 20054)

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.

Issue the command again without the illegal semicolon.

*** Unexpected end of input. (DBERR 20055)

An error was encountered trying to retrieve the next command.

Check the output and input to determine if all commands executed properly.

*** Illegal syntax. (DBERR 20056)

Command was entered incorrectly.

Issue the command again. You can use the HELP command to verify your syntax.

*** SQLMIGRATE log file (AASQLMIG) already exists. (DBERR 20070)

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.

Try again later.

*** Cannot create BBSQLMIG file. (! !, !) (DBERR 20080)

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.

Try again later.

*** Invalid target version. Use the SHOW VERSIONS command. (DBERR 20200)

The release of SQLMigrate being used does not support the version that was specified in the last command.

Use the SHOW VERSIONS command to determine the valid versions that may be used with this release of SQLMigrate.

*** DBEnvironmentName is too long. Maximum length is !. (DBERR 20201)

A DBEnvironmentName is restricted to operating system file naming conventions.

Refer to the A Beginner's Guide to HP-UX for information on file naming conventions.

*** Cannot MIGRATE FORWARD to earlier version. (DBERR 20202)

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.

Either change the keyword FORWARD to BACKWARD, or change the target version. Issue the command again.

*** Cannot MIGRATE BACKWARD to later version. (DBERR 20203)

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.

Either change the keyword BACKWARD to FORWARD, or change the target version. Issue the command again.

*** Cannot PREVIEW FORWARD to earlier version. (DBERR 20204)

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.

Either change the keyword FORWARD to BACKWARD, or change the target version. Issue the command again.

*** Cannot PREVIEW BACKWARD to later version. (DBERR 20205)

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.

Either change the keyword BACKWARD to FORWARD, or change the target version. Issue the command again.

*** DBEnvironment is already compatible with target version. (DBERR 20206)

The version of the DBEnvironment is already the same as the target version of the command.

If the target version was incorrectly specified, modify it and issue the command again.

*** Existing DBEnvironment not supported by SQLMigrate (DBERR 20207)

The release of SQLMigrate being used does not support migrations for the DBEnvironment specified in the command.

Contact your HP Service Representative or Response Center to determine if another release of SQLMigrate is available that will migrate your DBEnvironment.

*** DBEnvironment version is not recognized by SQLMigrate. (!) (DBERR 20208)

The release of SQLMigrate being used does not recognize the version number of your DBEnvironment, and cannot support migrations for it.

Contact your HP Service Representative or Response Center to determine if another release of SQLMigrate is available that will migrate your DBEnvironment.

*** DBEFileName is too long. Maximum length is !. (DBERR 20209)

The allowable length for the DBEFileName was exceeded.

Issue the command again, using a valid DBEFileName.

*** SystemFileName name is too long. Maximum length is !. (DBERR 20210)

The allowable length for the SystemFileName was exceeded.

Issue the command again, using a valid SystemFileName.

*** Migration path is not supported by SQLMIGRATE (!,!).(DBERR 20211)

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.

Specify a valid migration path.

Log full. (DBERR 20220)

The log file is full.

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.

ERROR - DBEFileName already exists in !. (DBERR 20330)

A row exists in SYSTEM.DBEFILE which has a DBEFNAME that is the same as the DBEFileName that was specified.

Issue the CREATE DBEFILE statement again, using a different DBEFileName.

ERROR - DBEFILE size is too small. Minimum size is !. (DBERR 20335)

The "WITH PAGES = " parameter did not meet minimum requirements.

Issue the CREATE DBEFILE statement again, using a larger value in the "WITH PAGES = " parameter.

ERROR - DBEFILE size is too large. Maximum size is ! (DBERR 20336)

The "WITH PAGES = " parameter exceeded maximum requirements.

Issue the CREATE DBEFILE statement again, using a smaller value in the "WITH PAGES = " parameter.

ERROR - SystemFileName already exists. (DBERR 20340)

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.

Use a different SystemFileName, and issue the CREATE DBEFILE statement again.

ERROR - DBEFileName has not been CREATED in !. (DBERR 20350)

You issued an ADD DBEFILE statement before a CREATE DBEFILE statement had been issued.

Issue the CREATE DBEFILE statement, and then issue the ADD DBEFILE command again.

ERROR - DBEFileName has already been ADDED to a DBEFILESET. (DBERR 20360)

The row for DBEFileName in SYSTEM DBEFILE indicates that the DBEFSNAME has already been assigned.

The name specified in the ADD DBEFILE statement was probably incorrect. Modify it, and issue the command again.

ERROR - User is not DBECreator. (DBERR 20518)

Only the DBECreator or the superuser is authorized to use SQLMigrate.

Contact someone having the proper capabilities to use SQLMigrate.

ERROR - Invalid DBECON file format detected. (DBERR 20520)

Migration is not supported for this DBEnvironment using SQLMigrate.

UNLOAD and LOAD your data to install another release of ALLBASE/SQL.

ERROR - Previous failed attempt to MIGRATE detected. (DBERR 20530)

SQLMigrate was used is the past to migrate the DBEnvironment, but the migration was unsuccessful.

Purge the DBEnvironment and restore the backup version before attempting migration again.

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.

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.

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.

DBEnvironment has already been started (DBERR 22800)

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.

Please try again later.

START DBE NEWLOG disallowed. Need rollforward recovery. (DBERR 23005)

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.

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.

System error in Listener on the server node. (HP-UX errno !) (DBERR 25000)

An HP-UX error occurred within the listener.

Refer to the usr/include/errno.h file for an error description.

No matching profile found in the NETUsers file. (DBERR 26002)

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.

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.

New value(s) already exists in NETUsers file, operation not performed. (DBERR 26003)

The NETUser name you specified is already in the NETUsers file.

Enter a unique NETUser name.

Lock on NETUsers file failed. (! !) (DBERR 26004)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Unlock on NETUsers file failed. (! !) (DBERR 26005)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Read failed on NETUsers file. (! !) (DBERR 26006)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Write failed on NETUsers file. (! !) (DBERR 26007)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

File system error on NETUsers file. (! !) (DBERR 26008)

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.

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.

The NETUsers file is empty. (DBERR 26009)

You tried to "show" profiles in an empty NETUsers file. Profiles in the NETUsers file have been deleted.

Contact the system administrator to add profiles to the NETUsers file.

Open failed on temporary NETUsers file. (! !) (DBERR 26010)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Write failed on temporary NETUsers file. (! !) (DBERR 26011)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Insufficient memory to allocate buffer. (DBERR 26012)

There is not enough memory to allocate buffer space for a new profile.

Do not complete the operation. Record as much information as possible and contact your HP Service Representative or Response Center.

The NETUsers file is being accessed. Operation could not be performed. (DBERR 26013)

The NETUsers file is currently open by someone else and cannot be deleted.

Try again later.

No matching profile found in the AliasDB file. (DBERR 27002)

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.

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

New value(s) already exists in AliasDB file, operation not performed. (DBERR 27003)

The alias name which you are trying to add or change already exists in the AliasDB file.

Enter a unique alias name.

Lock on AliasDB file failed. (! !) (DBERR 27004)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Unlock on AliasDB file failed. (! !) (DBERR 27005)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Read failed on AliasDB file. (! !) (DBERR 27006)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Write failed on AliasDB file. (! !) (DBERR 27007)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

File system error on AliasDB file. (! !) (DBERR 27008)

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.

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.

The AliasDB file is empty. (DBERR 27009)

You tried to "show" profiles from an empty AliasDB file. Profiles in the AliasDB file have been deleted.

Contact the system administrator.

Open failed on temporary AliasDB file. (! !) (DBERR 27010)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Write failed on temporary AliasDB file. (! !) (DBERR 27011)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Invalid NETUtil command. (DBERR 28001)

An invalid command was entered.

Type HELP for a list of valid NETUtil commands.

Insufficient capability, command disallowed. (DBERR 28002)

You must have superuser capability to execute this command. A non-superuser can use only the EXIT, HELP, QUIT, SHOW ALIAS, and SYSTEM commands.

Ask the system administrator to execute the command.

Open failed on NETUsers file. (! !) (DBERR 28003)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Open failed on AliasDB file. (! !) (DBERR 28004)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Backup failed on NETUsers file. (! !) (DBERR 28005)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Backup failed on AliasDB file. (! !) (DBERR 28006)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Read failed on message catalog. (! !) (DBERR 28007)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Invalid Machine Type. (! !) (DBERR 28008)

An invalid machine type was entered. Valid machine types are HP 3000 S900, HP 9000 S800, or HP 9000 S300.

Re-enter the machine type.

Invalid Datacom Type. (DBERR 28009)

You entered an invalid data communication type. The data communication type must be NS or ARPA.

Re-enter the data communication type.

Invalid Database Server Type. (DBERR 28010)

You entered an invalid database management system type. Currently, the only valid database management system is ALLBASE/SQL.

Re-enter the database management system type.

The AliasDB file has not been created. (DBERR 28011)

The AliasDB file does not exist.

Ask the system administrator to use the ADD ALIAS command to create the AliasDB file.

Name cannot start with the wildcard character. (DBERR 28012)

You tried to add a name to the AliasDB file or NETUsers file beginning with an '*'.

Re-enter the AliasName or NETUser name without the wildcard character.

Name is too long. (DBERR 28019)

You entered a DBEnvironment name, node name or login name in the AliasDB or NETUsers file which was too long.

Enter the name again. The maximum length for a DBEnvironment name is 128 bytes; the maximum length for a node name is 256 bytes; and the maximum length for a login name is 56 bytes.

Database server type must be ALLBASE/SQL. (DBERR 28020)

You entered an invalid database server type.

Re-enter a valid database server type.

Machine type must be HP9000 {S300, S400, S700 or S800} or HP3000 S9000. S900. (DBERR 28022)

You entered an invalid machine type.

Re-enter a valid machine type.

Datacomm type must be ARPA or NS. (DBERR 28024)

You entered an invalid datacomm type.

Re-enter a valid datacomm type.

Datacomm type must be ARPA. (DBERR 28028)

ARPA is the only valid datacomm type if the client and/or server is running HP-UX 10.0 or greater.

Change datacomm type to ARPA.

Cannot migrate alias (!) for server (!). (DBERR 28029)

This error could occur due to the following reasons :

The actions correspond to the above causes.

Cannot migrate NETUsers file backward. (DBERR 28030)

No previous migration of NETUsers file has occurred.

No action is necessary.

Cannot migrate AliasDB file backward. (DBERR 28031)

No previous migration of AliasDB file has occurred.

No action is necessary.

Cannot migrate client login (!) for client node name (!). (DBERR 28032)

An error occurred attempting to migrate client profile.

Check previous error message, which indicates where error occurred during migration.

Open failed on log file. (! !) (DBERR 28033)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Lock failed on log file. (! !) (DBERR 28034)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Unlock failed on log file. (! !) (DBERR 28035)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Write failed on log file. (! !) (DBERR 28036)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Open failed on server list file. (! !) (DBERR 28037)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Lock failed on server list file. (! !) (DBERR 28038)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Unlock failed on server list file. (! !) (DBERR 28039)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Write failed on server list file. (! !) (DBERR 28040)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Backup failed (! !) on file !. (DBERR 28041)

An HP-UX file system error occurred.

Refer to the /usr/include/sys/errno.h file for an error description.

Invalid message type received. (DBERR 29001)

An internal error occurred. The client node or the server node received an invalid message type.

Contact your HP Service Representative or Response Center.

Insufficient memory to allocate buffer for message. (DBERR 29002)

There is not enough memory to allocate a buffer for the outgoing message.

Try again later.

CONNECT or START DBE command expected. (DBERR 29003)

A CONNECT or START DBE statement is expected.

Add the appropriate statement to the application.

The ALLBASE/SQL and ALLBASE/NET software on the server machine are older than the ALLBASE/SQL and ALLBASE/NET software on the client machine. (DBERR 29004)

You are running incompatible releases of ALLBASE/SQL and ALLBASE/NET on the client and server machines.

Ensure that the release of ALLBASE/NET and ALLBASE/SQL on your client node is not more recent than the software on the server node.

Cannot create a DBE or new log files from a diskless node (DBERR 29005)

You have executed a START DBE NEW or START DBE NEWLOG statement from a diskless node.

Create the DBE or new log files on the server node in the diskless cluster. Then set up ALLBASE/NET to remotely access the database from the diskless node.

Invalid SQLX message buffer pointer. (DBERR 29010)

An ALLBASE/SQL internal error was encountered.

Record as much information as possible and contact your HP Service Representative or Response Center.

Unsupported remote command. (DBERR 29011)

The command is not supported by ALLBASE/NET.

Refer to the ALLBASE/NET User's Guide for a list of supported commands.

Incorrect machine type in AliasDB file. (DBERR 29440)

You are trying to access an HP3000 system but your AliasDB file specified an HP 9000 system.

Change the machine type field of the AliasDB file profile to "HP 3000 S900."

Security violation detected on server machine. (DBERR 29441)

Security violation on the server.

Check the server.

Datacommunication NS failure. NetIPC Error Code (!). (DBERR 30000)

NetIPC returned an error. Some NetIPC errors which have been mapped to DBERRs are listed here:

Refer to the NetIPC Error Codes in the HP 9000 NetIPC Programmer's Guide.

Datacommunication BSD failure. (DBERR 31000)

A data communication error occurred.

Record as much information as possible and contact your HP Service Representative or Response Center.

The connect sequence was interrupted before completion. (DBERR 31004)

The connect sequence could not be completed.

Restart the application.

Invalid virtual circuit descriptor. (DBERR 31009)

An internal error occurred. The internal virtual circuit descriptor is not the one from the successful connect call.

Record as much information as possible and contact your HP Service Representative or Response Center.

Invalid data pointer specified in ARPA sockets call. (DBERR 31014)

An internal error occurred.

Record as much information as possible and contact your HP Service Representative or Response Center.

Invalid parameter specified in ARPA sockets call. (DBERR 31022)

An internal error occurred.

Record as much information as possible and contact your HP Service Representative or Response Center.

The system's table of open files is full. (DBERR 31023)

The socket call cannot be accepted because the system's table is full.

Try to connect again later.

The peer-process descriptor table is full. (DBERR 31024)

The socket call cannot be accepted because the application's open file exceeds the per-process limit.

Close some files, then try to connect again.

The send cannot be completed, because the connection has been shutdown either by the remote peer or by the client process. (DBERR 31032)

A data communication error occurred or the peer process does not exist.

Record as much information as possible and contact your HP Service Representative or Response Center.

The virtual circuit descriptor is a file, not a socket. (DBERR 31216)

An internal error occurred.

Record as much information as possible and contact your HP Service Representative or Response Center.

The type of socket and protocol do not match. (DBERR 31219)

An internal error occurred.

Record as much information as possible and contact your HP Service Representative or Response Center.

The specified protocol is not supported. (DBERR 31221)

An internal error occurred.

Record as much information as possible and contact your HP Service Representative or Response Center.

The specified socket type is not supported. (DBERR 31222)

An internal error occurred.

Record as much information as possible and contact your HP Service Representative or Response Center.

ARPA network services have not been installed on this system. (DBERR 31223)

An attempt has been made to access a remote database from a system where networking services have not been installed.

Install networking services on the system.

The specified address family is not supported. (DBERR 31225)

An internal error occurred.

Record as much information as possible and contact your HP Service Representative or Response Center.

The address is already in use. (DBERR 31226)

You tried to start the listener daemon, but it has already been started.

No action necessary.

The specified address is not available. (DBERR 31227)

The /etc/hosts file is not set up correctly or there is an data communication error

Record as much information as possible and contact your HP Service Representative or Response Center.

The network cannot be reached from this host. (DBERR 31229)

The network has not been set up.

Record as much information as possible and contact your HP Service Representative or Response Center.

The connection was reset by peer process. (DBERR 31232)

A data communication error occurred or the peer process was terminated.

Record as much information as possible and contact your HP Service Representative or Response Center.

Insufficient resources available to complete socket operation. (DBERR 31233)

The cause depends on which ARPA sockets function called failed. However, this error is an indication that there are not enough system resources available to complete the system call.

Try again later.

The socket is not connected or the socket has not completed the connect sequence with its peer. (DBERR 31235)

The application ignored the error message from the connect call and continued to run the application which caused the internal usage of the descriptor from the failed call.

Check the application error messages. Try to connect after correcting the error.

The connection timed out due to a transmission timeout. (DBERR 31238)

Internal timeout reached.

Try to connect again.

The attempt to connect to a remote system was rejected. (DBERR 31239)

An internal error occurred. The listener daemon is down.

Remove the tmp/hpdaARPA.log or the tmp/hpdaNS.log file and restart the listener daemon. Verify that the ARPA listener is running. Refer to the ALLBASE/NET User's Guide for more information. If this does not solve the problem, record as much information as possible and contact your HP Service Representative or Response Center.

The server node is down. (DBERR 31241)

Unable to communicate with the server.

Reboot the system. If this does not solve the problem record as much information as possible and contact your HP Service Representative or Response Center.

Hardware error on interface card. (DBERR 31243)

There is a hardware error on the interface card.

Record as much information as possible and contact your HP Service Representative or Response Center.

Invalid login in NETUsers file. (DBERR 31900)

Incorrect syntax for server login in NetUsers file.

Check 'Idtfy_clnt INVALID LOGIN' message in server log file hpdanslg.pub.sys for server login used. Run NETUtil to correct server login.

Corresponding ALLBASE/NET error not found for error (!) (DBERR 31992)

An error number has been generated that cannot be handled by the client.

Record as much information as possible and contact your HP Service Representative or Response Center.

No entry found in password file on server node. (DBERR 31994)

The user name you specified by the PC API logon is not defined on this server.

Verify that the user name sent by the PC is the correct user name. If it is the correct user name, add it to the server's password file.

Hostname not found or the hosts file cannot be opened. (DBERR 31995)

The hostname cannot be found in the /etc/hosts file or the /etc/hosts file does not exist.

Check the hosts file for the correct hostname. Make sure it is spelled correctly in the AliasDB file.

or

ask the system administrator to set up the file.

The protocol file cannot be opened or the protocol name 'tcp' is not found. (DBERR 31996)

The /etc/protocols file does not exist or 'tcp' is not in the /etc/protocols file.

Ask the system administrator to set up the file or to correct the file. Refer to the LAN installation manual for information on this file.

The services file cannot be opened or the profile for 'DAServer' is not in the services file. (DBERR 31997)

The /etc/services does not exist or the definition of the ALLBASE/SQL RDA server is not in the /etc/services file.

Ask the system administrator to set up the services file or to correct the file. Refer to the LAN installation manual for information on this file.

Remote hpsqlproc process terminated prematurely. (DBERR 31998)

The server process terminated before the application finished.

Restart the application.

The data communication service is undefined. (DBERR 31999)

The data communication type you specified in the AliasDB file is undefined

or

an abnormal situation occurred.

Correct the profile in the AliasDB file or contact your HP Service Representative or Response Center.

Installation error detected. Check permissions and owner. (DBERR 34001)

The permissions, owner, or group of /usr/bin/sqlmon are incorrect.

Change the attributes of /usr/bin/sqlmon so that the permission is 4555, the owner is hpdb, and the group is bin.

Cannot create temporary file under /tmp. (! !) (DBERR 34002)

A file system error was encountered. /tmp is probably full.

Contact your system administrator.

TERMINFO data error. Using default HP terminal values. (DBERR 34003)

An unexpected error was encountered while obtaining valid escape sequences for your terminal.

Check the value of the TERM environment variable. Contact your system administrator to verify that your terminal type has been added to the /usr/lib/terminfo database.

Cannot start session. (RC !, !, !, !) (DBERR 34004)

An unexpected error was encountered when trying to connect to the DBEnvironment.

Look for an additional message that provides more information.

Cannot terminate session. (RC !, !, !, !) (DBERR 34005)

An unexpected error was encountered when trying to release from the DBEnvironment.

Look for an additional message that provides more information.

DBCORE error. (FNC !, RC !, !, ! !) (DBERR 34006)

An unexpected internal error was encountered.

Record as much information as possible and contact your HP Service Representative or Response Center.

Unexpected INTERNAL error. (!, !, !, !) (DBERR 34008)

An unexpected internal error was encountered.

Record as much information as possible and contact your HP Service Representative or Response Center.

Cannot attach to shared memory (RC !, !) (DBERR 34009)

An unexpected error was encountered.

Record as much information as possible and contact your HP Service Representative or Response Center.

Cannot detach from shared memory (!) (DBERR 34010)

An unexpected error was encountered.

Record as much information as possible and contact your HP Service Representative or Response Center.

Cannot allocate memory for data buffer structure (! !, !) (DBERR 34020)

An unexpected error was encountered.

Contact your system administrator.

Cannot get data buffer pool head! (DBERR 34021)

An unexpected error was encountered while trying to find the data buffer pool in memory.

The database administrator might have issued a STOP DBE statement. If not, record as much information as possible and contact your HP Service Representative or Response Center.

Number of data buffers not equal to DBECON value! (!, !, !) (DBERR 34022)

The size of the data buffer pool in memory does not match the size that is recorded in the DBECON file.

Record as much information as possible and contact your HP Service Representative or Response Center.

Cannot get current buffer information! (DBERR 34023)

An unexpected error was encountered while sampling the data buffer pool.

Record as much information as possible and contact your HP Service Representative or Response Center.

Could not find DBEFILE statistics in JMACRE buffer (DBERR 34030)

An unexpected error was encountered.

Record as much information as possible and contact your HP Service Representative or Response Center.

Could not find INDEX statistics in JMACRE buffer (DBERR 34031)

An unexpected error was encountered.

Record as much information as possible and contact your HP Service Representative or Response Center.

Number of sessions exceeds internal maximum (max=!) (DBERR 34071)

A limit has been reached.

If you need the limit increased, please contact your HP Service Representative or Response Center.

Number of latches exceeds internal maximum (max=!) (DBERR 34072)

A limit has been reached.

If you need the limit increased, please contact your HP Service Representative or Response Center.

Number of data buffers exceeds internal maximum (max=!) (DBERR 34076)

A limit has been reached.

If you need the limit increased, please contact your HP Service Representative or Response Center.

Number of qualifying locks exceeds internal maximum (max=!) (DBERR 34077)

A limit has been reached.

Use the SET LOCKFILTER or SET LOCKTABFILTER commands to reduce the number of locks that qualify. If you need the limit increased, please contact your HP Service Representative or Response Center.

Input too long. Maximum length is !. (DBERR 34100)

The total length of the input line exceeded the allowed limit.

Issue the command again.

Unexpected end of input. (DBERR 34102)

An error was encountered trying to retrieve the next command.

Check the output and input to see if all commands executed properly.

Illegal syntax. (DBERR 34103)

Command was entered incorrectly.

Issue the command again. You can use the help facility to verify your syntax.

Illegal integer. (DBERR 34104)

Numeric value was entered incorrectly.

Issue the command again.

Integer value out of range. (min=!,max=!) (DBERR 34105)

The number specified was not between the min and max values listed in the message.

Issue the command again.

Illegal OWNER.TABLE value. (DBERR 34106)

You did not specify a valid table name.

Issue the command again.

Illegal PAGE/ROW ID value. (DBERR 34107)

You did not specify a valid value.

Issue the command again.

SystemFileName name is too long. Maximum length is !. (DBERR 34120)

The allowable length for the SystemFileName was exceeded.

Issue the command again.

DBEFile name is not valid for this DBEnvironment. (DBERR 34121)

You did not specify a valid DBEFile name.

Issue the command again.

DBEFileSet name is not valid, or has no DBEFiles. (DBERR 34122)

You did not specify a valid DBEFileSet name.

Issue the command again.

DBEnvironmentName is too long. Maximum length is !. (DBERR 34501)

The allowable length for the DBEnvironmentName was exceeded.

Issue the command again.

MAINT is too long. Maximum length is !. (DBERR 34502)

The allowable length for the maintenance word was exceeded.

Issue the command again.

Incompatible DBEnvironment version (!). (DBERR 34503)

The version of the DBEnvironment is incompatible with the version of the program.

Contact your database administrator, who probably needs to use SQLMigrate.

Not authorized to use SQLMONITOR on this DBEnvironment. (DBERR 34504)

You are not the DBECreator or superuser.

Sign on as a user who does have the required authority.

Database in SINGLE-USER MODE. Cannot use SQLMONITOR. (DBERR 34507)

The DBEnvironment must be started in multi-user mode in order for SQLMonitor to connect to it.

Try again later.

DBEFileSetName is too long. Maximum length is !. (DBERR 34530)

The allowable length for the DBEFileSetName was exceeded.

Issue the command again.

DBEFileName is too long. Maximum length is !. (DBERR 34531)

The allowable length for the DBEFileName was exceeded.

Issue the command again.

OWNER.TABLE is too long. Maximum length is !. (DBERR 34540)

The allowable length for the OWNER.TABLE was exceeded.

Issue the command again.

PAGE/ROW ID is too long. Maximum length is !. (DBERR 34541)

The allowable length for the PAGE/ROW ID was exceeded.

Issue the command again.

SystemFileName is too long. Maximum length is !. (DBERR 34550)

The allowable length for the SystemFileName was exceeded.

Issue the command again.

SystemFileName could not be opened. (! !, !, !, !) (DBERR 34551)

A file system error was encountered.

Refer to the system administration manual.

SystemFileName could not be created. (! !, !, !, !) (DBERR 34552)

A file system error was encountered.

Refer to the system administration manual.

SystemFileName could not be rewritten. (DBERR 34553)

A file system error was encountered.

Refer to the system administration manual.

SystemFileName could not be closed. (! !, !, !, !) (DBERR 34557)

A file system error was encountered.

Refer to the system administration manual.

Environment variable is too long. Maximum length is !. (DBERR 34559)

The total length of the environment variable name exceeded the allowed limit.

Issue the command again.

Could not write to SystemFileName. (FSERR !, !, !, !) (DBERR 34560)

A file system error was encountered.

Refer to the system administration manual.

Timeout expired (! seconds, FNC !) (DBERR 34585)

SQLMON was not able to obtain some internal resource that was needed to complete the last command (for example, perhaps another session had obtained an X (exclusive) or an IX (intent exclusive) lock on a table that SQLMON was trying to read from).

You may wish to use the SET USERTIMEOUT command to set a higher timeout value and issue your original command once again.

The timeout expired during an attempt to "Get Statistics" on table !.!, which exists within DBEFileset ! (DBERR 34610).

SQLMON was not able to obtain some internal resource that was needed to complete the last command (for example, perhaps another session had obtained an X (exclusive) or an IX (intent exclusive) lock on the table that SQLMON was trying to read from).

You may wish to use the SET DBEFILESET command to specify another DBEFileset, and issue your original command once again. You can visit the STATIC screen to determine the DBEFileSets that exist within your DBEnvironment, and the tables that exist within them.

The timeout expired during an attempt to "Get Statistics" on a temporary table within DBEFileset ! (DBERR 34630).

SQLMON was not able to obtain some internal resource that was needed to complete the last command.

You may wish to use the SET DBEFILESET command to specify another DBEFileset, and issue your original command once again. You can visit the STATIC screen to determine the DBEFileSets that exist within your DBEnvironment, and the tables that exist within them.

Incorrect user password. (DBERR 35404)

The password given for the logon user is not valid.

Determine what the correct password is.

Login string format is invalid. (DBERR 35412)

The login string received does not conform to the MPE login syntax.

Supply a correct login string.

Invalid function code, !, received. (DBERR 35414)

The server received a function code from the PC that it was not expecting.

Record all error information and call your HP representative.

Out of system resources. (DBERR 140336)

The system is overloaded and new processes cannot be created.

Check for hung processes

or

run the process when fewer processes are running.