SQL5001N "<authorization-ID>" does not have the authority to change the database manager configuration file.
Explanation: The user attempted to Update or Reset the database manager configuration file without having SYSADM authority.
The requested change is not made.
User Response: Do not attempt to change the database manager configuration file without appropriate authorization. Contact a user with SYSADM authority if a change is required.
SQL5005C System Error.
Explanation: A system error, probably an I/O error, was encountered while accessing a configuration file.
The command cannot be processed.
User Response: Resubmit the command.
If the error persists, check the db2diag.log file for details and ensure that the configuration file is accessible. If unable to resolve the problem, contact an IBM Service Representative for assistance.
SQL5010N The path name to the database manager configuration file is not valid.
Explanation: An error occurred while determining the path for the database manager configuration file. The database manager directory structure may have been altered.
The command cannot be processed.
User Response: Resubmit the command. If the error continues, reinstall the database manager.
SQL5012N The entry in the database manager configuration file for the maximum number of segments allowed for the DB2 kernel is not in the valid range.
Explanation: The value for the maximum number of segments allowed for the DB2 kernel must be between 8 and 8192.
The requested change is not made.
User Response: Resubmit the command with a valid value for the maximum number of DB2 segments allowed.
SQL5018N The entry in the database manager configuration file for the maximum number of remote connections to the workstation (numrc) is not in the valid range.
Explanation: The value for the maximum number of remote connections to the workstation must be between 1 and 255.
The requested change is not made.
User Response: Resubmit the command with a valid value for the maximum number of remote connections to the workstation.
SQL5020N The entry in the database manager configuration file for the node name for the workstation (nname) is not valid.
Explanation: The node name specified in the configuration command is not valid. The node name may be 1 to 8 characters. All the characters must be chosen from the database manager base character set.
The command cannot be processed.
User Response: Resubmit the command with a valid node name.
SQL5021N The entry in the database manager configuration file for the index recreation time (indexrec) is not valid. Possible values are 1 (during index access) and 2 (during database restart).
Explanation: An invalid value was passed to Configuration Services for the Index Recreation Time flag (indexrec) in the database manager configuration file. The invalid value may have been entered through the Command Line Processor or through a program API call. The only valid values for the API call are 1 (during database access), and 2 (during database restart). The valid values for the command line processor are ACCESS and RESTART.
The update to the database manager configuration file is rejected.
User Response: Repeat the update request, entering one of the possible values.
SQL5022N The entry in the database configuration file for the index recreation time (indexrec) is not valid. Possible values are 0 (use system setting), 1 (during index access), and 2 (during database restart).
Explanation: An invalid value was passed to Configuration Services for the Index Recreation Time flag (indexrec) in a database configuration file. The invalid value may have been entered through the Command Line Processor or through a program API call. The only valid values for the API call are 0 (use system setting), 1 (during index access), and 2 (during database restart).
The valid values for the command line processor are SYSTEM, ACCESS, and RESTART.
The update to the database configuration file is rejected.
User Response: Repeat the update request, entering one of the possible values.
SQL5025C The database manager configuration file is not current.
Explanation: The database manager configuration file has been updated since you connected to the database. It is not compatible with the configuration for the database to which you are connected.
No access is allowed to the database manager configuration file.
User Response: Wait until all applications disconnect from the databases. Issue the stop database manager command, and then issue the start database manager command.
If installing the sample database, drop it and install the sample database again.
SQL5028N The value of sysadm_group must be the primary group of the instance owner.
Explanation: An attempt was made to update sysadm_group in the database manager configuration file. For Version 2 of DB2 on Unix-based platforms, this value is only allowed to be the primary group of the instance owner.
User Response: Use the primary group of the instance owner to update this field in the database manager configuration file on Unix-based platforms.
SQL5030C The release number is not valid.
Explanation: The release number in the database manager configuration file or database configuration file is not valid.
The command cannot be processed.
User Response: Verify that the release levels of your database and DB2 match.
If installing the sample database, drop it and install the sample database again.
sqlcode: -5030
sqlstate: 58031
SQL5035N The database requires migration to the current release.
Explanation: The database was created on a lower level system release. The Migrate Database command must be used to convert the database to the current release level.
The command cannot be processed.
User Response: Perform the Migrate Database command before attempting to use the database with the current system release.
If this message is received during a restore, drop the existing database before proceeding.
sqlcode: -5035
sqlstate: 55001
SQL5040N One of the socket addresses required by the TCP/IP server support is being used by another process.
Explanation: One of the socket addresses required by the server either is in use by another program, or has not been freed completely by the TCP/IP subsystem after the database manager has been stopped.
User Response: If you have just issued db2stop, wait for a couple of minutes so that the TCP/IP subsystem has enough time to clean up its resources. Otherwise, make sure no other programs on your workstation are using the port numbers reserved for your service name in the /etc/services file. The port number is a component of a socket address.
SQL5042N One of the communication protocol server support processes failed to start up.
Explanation: Due to system call failure, or a communication subsystem call failure, one of the communication protocol server support processes did not start up successfully.
User Response: You can investigate the problem by either:
SQL5043N Support for one or more communications protocols failed to start successfully. However, core database manager functionality started successfully.
Explanation: Communication protocol support did not start successfully for one or more protocols. Possible reasons can include the following:
You can still connect to the server with communication protocols that did start successfully. Local clients can also connect to the server.
User Response: The database manager attempts to start all communication protocols specified by the DB2COMM environment variable.
Check the diagnostic log (db2diag.log) for details on this error. The log will contain more information on the cause of the error and also which communication protocol(s) did not start successfully.
This error only affects communication protocols specified by the DB2COMM environment variable.
SQL5047C Insufficient memory to execute this function.
Explanation: There is not enough memory available to execute this function.
The function cannot be completed.
User Response: Stop the application. Possible solutions include:
SQL5048N The release level of the database client is not supported by the release level of the database server.
Explanation: Database clients can only access database servers with a release level which is in the range of one level lower than the client to two levels higher than the client.
User Response: One or more of the following:
SQL5050C The content of the database manager configuration file is not valid.
Explanation: The database manager configuration file is not valid. The file may have been altered by a text editor or a program other than the database manager.
The command cannot be processed.
User Response: Reinstall the database manager.
SQL5051N An object qualified by "<qualifier>" cannot be created in schema "<schema-name>".
Explanation: An object created in a CREATE SCHEMA statement is qualified by "<qualifier>" which is different from the schema name. All objects created in a CREATE SCHEMA statement must be either qualified by the schema name "<schema-name>" or not qualified. Unqualified objects are implicitly qualified by the schema name.
The statement cannot be processed.
User Response: Explicitly qualify the object in the schema with "<schema-name>" or remove "<qualifier>" from the object name.
sqlcode: -5051
sqlstate: 42875
SQL5055C The content of the database configuration file is not valid.
Explanation: The database configuration file for the database is not valid. The file may have been altered by a text editor or a program other than the database manager.
User Response: Recreate the database or restore it from a backup version.
sqlcode: -5055
sqlstate: 58031
SQL5060N The configuration parameter token specified is invalid.
Explanation: A token number specified in the sqlfupd structure passed to a Configuration Services API is not valid. It does not represent any of the supported configuration parameters. Alternatively, if an UPDATE was attempted, the token specified may be that of an unmodifiable configuration parameter.
User Response: Choose a valid token number from those specified in the description of the Configuration Services API in the Application Development Guide. Recode the call to the API, and rerun the program.
SQL5061N An invalid pointer to structure sqlfupd was passed to Configuration Services.
Explanation: The pointer to structure sqlfupd passed as a parameter to one of the Configuration Services APIs was invalid. It is either NULL, or does not point to an allocated block of memory of the size indicated by the count parameter. See the Application Development Guide for more information.
User Response: Correct the code which invokes the Configuration Services API, and retry the API call.
SQL5062N An invalid pointer was passed within the sqlfupd structure to Configuration Services.
Explanation: The structure sqlfupd passed as a parameter to one of the Configuration Services APIs contained an invalid pointer. The pointer is either NULL, or does not point to an allocated block of memory. Each token passed in the structure must have a corresponding pointer to a field that is either passed in or out of the API. See the Application Development Guide for more information.
User Response: Correct the code which invokes Configuration Services, and rerun the program.
SQL5065C The nodetype value in database manager configuration file is not valid.
Explanation: The nodetype parameter in the database manager configuration file is not valid.
The command cannot be processed.
User Response: Reinstall the database manager.
SQL5070N The count parameter in the configuration command is not valid. It must be greater than 0.
Explanation: The count value passed as a parameter to a Configuration Services API must be greater than 0.
The command cannot be processed.
User Response: Correct the code which invokes Configuration Services, and rerun the program.
SQL5075N The configuration utility was interrupted.
Explanation: An interrupt was received by the configuration utility. The user may have pressed the interrupt key sequence.
The command was not processed. Any requested change is not made.
User Response: Resubmit the command.
SQL5081N The entry in the database configuration file for the size of the buffer pool (buffpage) is not in the valid range.
Explanation: The minimum value for the size of the buffer pool is two times the maximum number of active processes (maxappls). The maximum value for the size of the buffer pool is 524288 (number of 4KB pages) and is operating system dependent. The maximum value under AIX is 51000 (204000 for DB2 Enterprise - Extended Edition) (4KB pages). Under HP-UX, the value must be between 16 and 150000 (4KB pages).
The requested change is not made.
User Response: Resubmit the command with a valid value for the size of the buffer pool.
SQL5083N The entry in the database configuration file for the initial log file size (logfile) is not in the valid range.
Explanation: The value for the initial log file size must be between 12 and (2**32 - 1).
The requested change is not made.
User Response: Resubmit the command with a valid value for the initial log file size.
SQL5091N The entry in the database configuration file for the size of one log file extension (logext) is not in the valid range.
Explanation: The value for the size of one log file extension must be between 4 and 256.
The requested change is not made.
User Response: Resubmit the command with a valid value for the size of one log file extension.
SQL5092N The entry in the database configuration file for the maximum allowable number of log file extensions (logmaxext) is not in the valid range.
Explanation: The value for the maximum allowable number of log file extensions must be between 0 and (2 * 10**6).
The requested change is not made.
User Response: Resubmit the command with a valid value for the maximum allowable number of log file extensions.
SQL5093N The entry for the database configuration parameter for the size of the agent heap is not in the valid range.
Explanation: The value for the size of the agent heap must be between 2 and 85.
The requested change is not made.
User Response: Resubmit the command with a valid value for the agent heap size.
SQL5099N The new path to the log (newlogpath) in the database configuration file is not valid.
Explanation: The path to the log file is not valid for one of the following reasons:
The requested change is not made.
User Response: Resubmit the command with a valid value for the new log path.
sqlcode: -5099
sqlstate: 08004