Cause: The requested change would cause (1) the number of allowed concurrent databases to be too large or (2) the number of segments allowed for DB2 to be too small.
The number of allowed concurrent databases is restricted by the maximum number of segments allowed for DB2. The following condition must always be true:
segments >= ((number of databases * 5) + 1)
The requested change is not made.
Action: Do one of the following:
Cause: The requested change would cause the total number of logfiles to be out of range. The following condition must always be true:
logprimary + logsecond <= 128
The requested change is not made.
Action: Do one or both of the following:
Cause: The requested change would cause the maximum number of active applications to be too large for the size of the buffer pool. The following condition must always be true:
bufferpool_size > (number of active_processes * 2)
The requested change is not made.
Action: Do one or both of the following:
Cause: The request is not completed because the value given for "<parameter>" is invalid.
Action: Ensure that the value specified for "<parameter>" is either 0 or 1, then try the request again.
Cause: The user is attempting to modify both the previous log parameters and the new parameters. The application should only support the parameters of the current release.
The request is denied.
Action: Modify only the parameters of the current release and retry the command.
Cause: The value set for database options (SQLF_DETS) is not valid. Valid settings are between 0 and 15. The requested change is not made.
The requested change is not made.
Action: Resubmit the command with a valid database options value.
Cause: The database and database configuration file cannot be accessed because of copy protection.
The user request is denied.
Action: Return to the original database and modify the configuration file to turn the copy protection off, then create a new backup which may be used to restore the database. This must be done by an individual with SYSADM authority. If the original database is no longer available, contact your service representative.
Cause: An error occurred while accessing SQLOGCTL.LFH for the specified database.
The requested change is not made.
Action: Restore the database from a backup copy or recreate the database.
Cause: The user attempted to modify a database manager configuration parameter which is invalid for the given node type. "<node-type-code"> is defined as follows:
The requested change is not made.
Action: Resubmit the request with a valid parameter for the given nodetype.
Cause: The request is not done because the value of "<parameter>" is not within the valid range.
Action: Ensure that the value specified for "<parameter>" is within the valid range, then try the request again.
Cause: The request is not done because the value of "<parameter>" is not within the valid range.
Action: Ensure that the value specified for "<parameter>" is within the valid range, then try the request again.
Cause: The configuration parameter is not set or too long.
Action: Change the value of the configuration parameter to within the maximum length given.
Cause: The configuration parameter is not one of the two values given.
Action: Change the value of the configuration parameter to one of the two values given.
Cause: One or more characters in the tpname is not in the valid range. The characters in the tpname must be one of the following:
Action: Change the tpname and retry the command or function call.
Cause: The number of active processes (maxappls) times the maximum percentage of lock list space for each application (maxlocks) must be greater than or equal to 100. That is:
maxappls * maxlocks >= 100
This ensures that all of the allocated locklist space can be used.
Action: Increase the setting for maxappls, maxlocks, or both.
Cause: An invalid value was specified by dftdbpath. The rules for the default database path on UNIX-based systems are:
The rules for other platforms (such as OS/2, WindowsNT, Windows 95) are:
Action: Change the dftdbpath and retry the command or function call.
Cause: An invalid value was specified for diagpath. The rules for the diagnostic directory path are:
Action: Change the diagpath and retry the command or function call.
Cause: The allowed values for the configuration parameter authentication are SERVER, CLIENT, DCS, or DCE.
The requested change is not made.
Action: Resubmit the command with a valid value for authentication.
Cause: The allowable range for avg_appls is from 1 to the value of maxappls.
The requested change is not made.
Action: One or more of the following:
Cause: The valid values for agentpri are -1, or a three digit number of which the first digit is a priority class ranging from 2 to 4 and the last two digits are a priority level within the class in the range of 00 to 31. The priority class is defined as follows:
For example, the number 304 would correspond to a priority class of 3 (TIMECRITICAL), with a priority level of 4.
Action: Change the value of the configuration parameter to a value within the valid range.
Cause: The request is not completed because the value given for "<parameter>" is too low. "<parameter>" may not be less than "<minimum value>"
Action: Ensure that the value specified for "<parameter>" is within the valid range, then try the request again.
Cause: The request is not completed because the value given for "<parameter>" is invalid. Except for an allowable value of -1, "<parameter>" may not be less than "<minimum value>".
Action: Ensure that the value specified for "<parameter>" is within the valid range, then try the request again.
Cause: The request is not completed because the value given for "<parameter>" is too high. "<parameter>" may not be greater than "<maximum value>"
Action: Ensure that the value specified for "<parameter>" is within the valid range, then try the request again.
"<condition>"
Cause: A valid configuration file must maintain the following relationship:
"<condition>".
The update request could not be completed because the resulting configuration would violate that relationship.
Action: Resubmit the request, ensuring that the relationship is satisfied.
Cause: The database manager configuration parameter "authentication" must have the value "CLIENT" if the value of "<parameter>" is non-default.
The requested change is not made.
Action: Resubmit the command with a valid combination of configuration parameter values.
Cause: The value of SORTHEAP is currently greater than half the value of the database manager configuration parameter SHEAPTHRES. This may cause performance to be less than optimal.
Action: Increase the value of the database manager configuration parameter SHEAPTHRES and/or decrease the value of SORTHEAP so that SHEAPTHRES is at least twice as large as SORTHEAP.
A larger ratio is desirable in most cases. See the Adminstration Guide for recommendations on configuration parameter tuning.