Chapter 10 ALLBASE/SQL Error Messages: 22800-

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.

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 MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 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 MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 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 MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 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 MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 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 be MANAGER.SYS or have SM capability to execute this command. Users with AM capability can execute ADD ALIAS, CHANGE ALIAS, DELETE ALIAS, ADD USER, CHANGE USER, DELETE USER, and SHOW USER commands on user and alias profiles within their accounts. Users without SM or AM capability, or who are not MANAGER.SYS 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 MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Message Manual, Volume 1 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.

DB2 Connection Type must be G. (DBERR 28013)

You attempted to enter a DB2 Connection Type in the AliasDB file that is not supported.

Enter the DB2 connection type again. The valid DB2 connection type at this time is LU6.2.

Invalid CICS Transaction Type. (DBERR 28014)

You attempted to enter a CICS Transaction Type in the AliasDB file that does not conform to the edit specifications for this field.

Enter the CICS Transaction Type again. Valid CICS transaction types start with a letter and are 4 characters long.

Invalid LU6.2 Time Out Value. (DBERR 28015)

You attempted to enter an LU6.2 time out value that is not in the range.

Enter the LU6.2 Time Out Value again. Valid LU6.2 time out values are in the range 0 to 28800. 0 implies no time outs.

Invalid HP Session Type. (DBERR 28016)

You entered an HP LU6.2 API Session Type in the AliasDB file entry that does not conform to the edit specifications for this field.

Enter the HP Session Type again. Valid HP Session Types are up to 8 characters long.

Invalid Length. (DBERR 28017)

You entered data in the AliasDB file entry that does not conform to the edit specifications for this field.

Enter the length specification again. Valid lengths are integers greater than zero.

LU6.2 Trace Flag must be 0, 1, 2, or 3. (DBERR 28018)

You entered an HP LU6.2 API trace flag value that is not supported.

Enter the LU6.2 Trace Flag again. Valid values for this flag are 0, 1, 2, or 3.

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 or DB2. (DBERR 28021)

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.

Machine type must be IBM. (DBERR 28023)

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 LU6.2. (DBERR 28025)

You entered an invalid datacomm type.

Re-enter a valid datacomm type.

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 MPE/iX file system error occurred.

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

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

An MPE iX file system error occurred.

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

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

An MPE/iX file system error occurred.

Refer to the MPE/iX Error Messages Manual, Volume I 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.

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."

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

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

30004 NetIPC Error:  Network transport not initialized.  (DBERR 30004)
 
30009 NetIPC Error:  Protocol is not active.  (DBERR 30009)
 
30015 NetIPC Error:  Attempt to exceed limit of sockets per process. (DBERR 30015)
 
30016 NetIPC Error:  Out of path descriptors or extensions.  (DBERR 30016)
 
30031 NetIPC Error:  Duplicate socket name.  (DBERR 30031)
 
30036 NetIPC Error:  Table of names is full.  (DBERR 30036)
 
30037 NetIPC Error:  Socket name not found.  (DBERR 30037)
 
30040 NetIPC Error:  Unknown node.  (DBERR 30040)
 
30043 NetIPC Error:  Unable to contact remote registry server.  (DBERR 30043)
 
30044 NetIPC Error:  No response from remote registry server.  (DBERR 30044)
 
30055 NetIPC Error:  Exceeded socket limit.  (DBERR 30055)
 
30059 NetIPC Error:  Socket timeout.  (DBERR 30059)
 
30064 NetIPC Error:  Remote protocol module aborted connection.  (DBERR 30064)
 
30065 NetIPC Error:  Local protocol module aborted connection.  (DBERR 30065)
 
30067 NetIPC Error:  Connection failure detected.  (DBERR 30067)
 
30068 NetIPC Error:  Received graceful release of connection.  (DBERR 30068)
 
30110 NetIPC Error:  Unanticipated protocol error.  (DBERR 30110)
 
30116 NetIPC Error:  Destination unreachable.  (DBERR 30116)
 
30117 NetIPC Error:  Attempt to establish connection failed.  (DBERR 30117)
 
30118 NetIPC Error:  Incompatible version.  (DBERR 30118)
 
30131 NetIPC Error:  Protocol module does not have sufficient resources. (DBERR 30131)
 
30158 NetIPC Error:  Connection request rejected by remote.  (DBERR 30158)

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 HOSTS.NET.SYS file is not set up correctly or there is a datacomm 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.

Local node's hostname cannot be determined. (DBERR 31244)

Local domain name was not set.

Set the local domain name in NMMGR.

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.

Error obtaining passwords for server login. (DBERR 31901)

Internal error. Errors could be in obtaining server process id, building or accessing temporary file or executing MPE/iX commands: LISTUSER, LISTACCT. LISTGROUP.

Check 'Get xxx Passwd' message in server log file hpdanslg.pub.sys (where xxx = user, account or group) for more specific information.

Server login does not exist on server node. (DBERR 31902)

Specified user, account or group does not exist on server.

Check 'Get xxx Passwd - No such login' message in server log file hpdanslg.pub.sys (where xxx = user, account or group) to determine which part of login failed. Have system or account manager create account, user or group or use NETUtil to change server login.

Error streaming server job. (DBERR 31903)

Internal error. Errors could be in obtaining process id, building or accessing temporary file or streaming temporary job.

Check 'Server' message in server log file hpdanslg.pub.sys for more specific information.

Error obtaining home group for server login. (DBERR 31904)

Internal error. Errors could be in obtaining server process id, building or accessing temporary file or executing MPE/iX commands: LISTUSER, LISTACCT. LISTGROUP.

Check 'Get xxx Passwd' message in server log file hpdanslg.pub.sys (where xxx = user, account or group) for more specific information.

No home group specified for server login. (DBERR 31905)

You did not specify a group in the NETUsers file for the mapped server login, and no home group was set up for the server login either.

Use the MPE/iX ALTUSER command to add a home group for the server login, or specify a login group for the server login in the NETUsers file. for more specific information.

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 HOSTS.NET.SYS file or the HOSTS.NET.SYS file does not exist.

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

The PROTOCOL.NET.SYS file does exist or 'tcp' is not in the PROTOCOL.NET.SYS 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 SERVICES.NET.SYS file does not exist or the definition of the ALLBASE/SQL RDA server is not in the SERVICES.NET.SYS 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.

LU 6.2 Security Error. (DBERR 33001)

The IBM system has rejected the LU 6.2 connection attempt.

Correct the security parameters specified in the NETUtil AliasDB file entry.

LU 6.2 Send not allowed, partner LU has send. (DBERR 33003)

The HP side of the LU 6.2 connection has attempted a send when a send is disallowed by the protocol.

This error should not occur. In the event that it does, transmission errors may have occurred. Contact your HP service representative or Response Center.

LU 6.2 Communications connection error. ! ! . (DBERR 33004)

The APPC LU 6.2 routines have detected a communications error.

Follow the action described for this code in the HP LU 6.2 API Reference manual. A brief summary of the error codes may be obtained by issuing the command "print catappc.pub.sys." Certain LU 6.2 codes may indicate problems with the connection layers. For example

Invalid function for foreign access. (DBERR 33121)

The function is not available for foreign access. There are two possible cases for this situation to occur: 1) An attempt has been made to call a Switch routine that is not valid for foreign access

or

2) FDA cannot identify the SQL function in the statement being compiled.

If connected to a foreign DBE, use only those commands that are valid for foreign access.

No DBEnvironment connected. (DBERR 33123)

Connection to a foreign DBE is expected but not found.

Establish the connection to a foreign DBE.

Already connected to a DBE. (DBERR 33124)

An attempt has been made to connect to a DBE while already connected to a foreign DBE.

Release the current DBE connection before connecting to a DBE.

Database server error !. (DBERR 33350)

Database server has detected an error.

Record the database server error number and refer to the list of database server errors,

or

contact your HP Service Representative or Response Center.

Receiving message length is not long enough. (DBERR 33351)

The size of the message buffer is not large enough to receive the message from the database server.

Increase the LU6.2 Input Buffer Length value of the alias definition in the AliasDB file.

The send message length is not long enough. (DBERR 33352)

The size of the message buffer is not large enough to send the message to the database server.

Increase the LU6.2 Output Buffer Length of the alias definition in the AliasDB file.

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 fcontrol $STDINX. (! !) (DBERR 34011)

An MPE/iX file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1.

Unexpected PROCINFO error. (PIN=!, !, !) (DBERR 34013)

An unexpected error was encountered while trying to get the name of the program that the user is running.

Contact your system administrator.

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 a user having SM capability.

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 opened. (HPFOPEN !, !, !, !) (DBERR 34554)

A file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1.

SystemFileName could not be created. (HPFOPEN !, !, !, !) (DBERR 34555)

A file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1.

SystemFileName could not be rewritten. (HPFOPEN !, !, !, !) (DBERR 34556)

A file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1.

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

A file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1.

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

A file system error was encountered.

Refer to the MPE/iX Error Message Manual, Volume 1.

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.

NETWARE LISTENER NOT RUNNABLE ON THIS BUILD. (DBERR 35000)

The ALLBASE/SQL PC API NetWare listener is not available on this version.

Install a version of ALLBASE/SQL that supports NetWare access from ALLBASE/SQL PC API.

Invalid syntax for identifier. (DBERR 35400)

The session name specified in the login string for remote logon is not valid.

Check the session name used for remote logon.

Unidentified user specified in logon. (DBERR 35401)

The user name specified in the login string for remote logon is not valid.

Check the user name used for remote logon.

Unidentified account specified in logon. (DBERR 35402)

The account name specified in the login string for remote logon is not valid.

Check the account name used for remote logon.

Incorrect user password. (DBERR 35404)

The user password you specified for the user.account logon is not valid.

Determine what the correct password is.

Incorrect account password. (DBERR 35405)

The account password specified for logon is not valid.

Determine the correct password.

Incorrect group password. (DBERR 35406)

The group password specified for logon is not valid.

Determine the correct password.

Missing user password. (DBERR 35407)

A user password is required, but was not specified.

Supply the password for the remote logon.

Missing account password. (DBERR 35408)

An account password is required, but was not specified.

Supply the password for the remote logon.

Missing group password. (DBERR 35409)

An group password is required, but was not specified.

Supply the password for the remote logon.

MPE user and account must be supplied. (DBERR 35410)

An incorrectly constructed logon string was given to the server for remote logon.

Supply a correct logon string.

No home group for specified user. (DBERR 35411)

The login user specified does not have a home group and a login group was not specified.

Either specify a login group or assign a home group to the user.

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.

Formal designator does not exist. (DBERR 140337)

Your version of STORE.PUB.SYS does not have the enhancements required for online backup.

Contact your HP Service Representative to obtain a version of STORE.PUB.SYS that supports online backup

or

perform a static store of the DBEnvironment using the procedures described in the "Backup and Recovery" chapter of the ALLBASE/SQL Database Administration Guide.

Formal designator is invalid. (DBERR 140338)

The version of STORE.PUB.SYS that you are attempting to use during an online backup is not valid.

Check to make sure that your version of STORE.PUB.SYS matches the operating system version and has the enhancements required for online backup. For more information about these enhancements, contact your HP Service Representative.