DBA4000-4999

DBA Message ID	Message	Explanation	User Response
DBA4000W	Are you sure you want to stop monitoring?	You have requested to stop monitoring all database objects that are currently monitored and to exit the Performance Monitor.	Click "Yes" to process the request or "No" to cancel it.
DBA4001I	There is no monitor summary for your selection.	You requested to show monitor activity on a level of object in which nothing is being monitored. There is no summary activity to be shown.	Retry the action when a monitor is started on a object that corresponds to the level you have selected.
DBA4002W	Are you sure you want to stop monitoring `name`?	You have requested to stop monitoring an object that is currently being monitored.	Click "Yes" to process the request or "No" to cancel it.
DBA4003I	Only the default level is changed for IBM supplied monitors.	For an IBM-supplied monitor, the only attribute that you can change is the level for which this monitor is designated as the default.
DBA4004E	Multiple selection is only allowed for the Remove action.	You selected more than one monitor from the list of monitors. The only action you can perform on multiple objects is Remove.	Deselect all monitors except one from the list and retry the action.
DBA4005W	Are you sure you want to remove the selected monitors?	You requested to remove the selected monitors from the list.	Click "Yes" to process the request or "No" to cancel it.
DBA4006W	Are you sure you want to reset the counters?	You requested to reset the database counters.	Click "Yes" to process the request or "No" to cancel it.
DBA4007W	Are you sure you want to stop monitoring all objects in this level?	You have requested to stop monitoring all objects in this level that are currently being monitored.	Click "Yes" to process the request or "No" to cancel it.
DBA4008W	Are you sure you want to stop monitoring all database partitions in this object?	You have requested to stop monitoring all database partitions in this object that are currently being monitored.	Click "Yes" to process the request or "No" to cancel it.
DBA4009I	The IBM supplied monitors are being created.	The IBM supplied monitors are being created. This may take a while.
DBA4010E	The Performance Monitor encountered a problem and cannot continue. Retry the action. If the problem persists, take a trace at the client and the server, and contact support personnel.	Unexpected error has occurred.	Take a trace at the client and the server and contact support.
DBA4011E	The program `name` is not a valid name. The program cannot be run. Check the name and retry the action.	You have specified an invalid program name.	Specify a valid program name and retry the action.
DBA4012E	The program `name` cannot be run. The currently executing thread is not allowed to execute the specified program.	A security exception is thrown when executing the program specified. Run command works in application mode only.	Retry the action when you run Control Center as an application.
DBA4013I	Database manager node `name` is down.	From the Tools settings, node status page, you have selected to be informed about database manager node status when it is down.	Restart the database manager node to continue processing.
DBA4014I	The state of database manager node `name` is unknown.	From the Tools settings, node status page, you have selected to be informed about database manager node status when the state is unknown.
DBA4015E	`name` contains invalid input. Please re-enter the entry.	Your entry contains invalid character.	Retry your action with new entry.
DBA4016E	New monitor cannot be created. The maximum number of monitors is `number`.	The create or save as or copy request fails. The maximum number of monitors has been reached.	Remove unused monitors and retry your action.
DBA4017E	The monitoring connection cannot be established. The maximum number of monitoring connections is `number`.	The maximum number of monitoring connections has been reached.	Retry your action later or stop any running monitoring session on your machine.
DBA4018W	Your entry in `name` is too long. The maximum number of characters is `number`. Your entry is truncated.	Your entry has exceeded the limit.
DBA4019E	Your entry in `name` is too long. The maximum number of characters is `number`. Retry your action with valid input.	Your entry has exceeded the limit.	Retry the action with valid input.
DBA4020W	You made changes to the performance monitor `name`. Do you want to save your changes?	You made one or more changes to the performance monitor that are not yet saved, and you requested to exit from the Show Monitor window or set the running monitor a different monitor. Your changes will be lost unless you click Yes.	Click "Yes" to process the request or "No" to cancel it.
DBA4021W	You made changes to the performance variable settings for `name`. Do you want to apply your changes to the next snapshot?	You made one or more changes to the performance variable settings that are not yet saved, and you selected a different performance variable to work with. Your changes will be lost unless you click Yes.	Click "Yes" to apply the changes to the next snapshot of "No" cancel it.
DBA4023E	You entered a combination of alarm and warning threshold values that is not valid for performance variable `name`. Change one or more threshold values and try again.	The upper alarm threshold value must be greater than the upper warning threshold value and so on; that is, upper alarm threshold value > upper warning threshold value > lower warning threshold value > lower alarm threshold value. The threshold value is a float no longer than 9 digits.	Verify the threshold values and try the operation again.
DBA4024W	The Summary page cannot show more than `number` columns. Turn to the Details page to see all the performance variables.	The Summary page currently displays as many columns as it can accommodate, but some performance variables are not shown.	Turn to the Details page to see all the performance variables.
DBA4025W	The `type` view cannot show more than `number` performance variables.	The maximum number of performance variables are shown.	Remove one or more performance variables from the `type` view before adding more.
DBA4026E	A non-applicable monitor has been set as default for this level.	The monitor must include at least one performance variable for this level.	Modify the monitor to include at least one performance variable for this level.
DBA4027I	Monitoring has not been started as there is nothing to monitor.	Currently there are no databases or gateway connections to be monitored for this instance.	Catalog a database or gateway connection to start monitoring.
DBA4060E	The Performance Monitor is currently active with another monitor for this instance.	Only one monitor can be active at a time per instance. For example, if your default monitor for databases is different from your default monitor for connections, you will not be able to monitor databases and monitor (or list) connections at the same time.	In the List Monitors window, you can: Find out which monitor is running and stop it so you can specify a different one. Find out which monitor is running and specify it for your next monitoring action. Create a monitor that contains performance variables for all levels, and then select it as your default monitor for each level.
DBA4065E	The threshold value cannot be blank or contain more than 9 characters. Enter a valid threshold value.	You entered a threshold value which is not valid or your value has been modified internally. For example, 123456789 will be modified to 123,456,789.0 which exceeds the number of characters allowed in the threshold.	Re-enter the threshold value and retry your action.
DBA4070E	The JDBC server encountered a problem. The list of performance monitors could not be processed.	An unexpected problem is encountered.	Verify that the JDBC server is up and running. If it is, take a trace at the JDBC server and then contact support personnel.
DBA4071W	Some monitors are currently in use locally. The refreshed list shows local monitors only.	The list of monitors is refreshed with local monitors only.	To show the complete list, stop the active monitors and retry the operation.
DBA4072E	This monitor name already exists. Specify a unique name.	Performance monitor names in a JDBC server must be unique regardless of the monitor's creator.	Specify a unique monitor name.
DBA4074E	The JDBC server encountered a problem. The operation could not be performed.	An unexpected problem is encountered.	Verify that the JDBC server is up and running. If it is, take a trace at the JDBC server and then contact support personnel.
DBA4075E	This performance monitor is empty so it cannot be saved. Add at least one performance variable to the monitor and retry the operation.	Monitors need to contain at least one performance variable in order to be valid.	Add at least one performance variable to the monitor and retry the operation.
DBA4076E	The action cannot be performed because you are not the creator of the monitor.	You must own the monitor to be able to change, rename or remove it.	If you were trying to change a monitor, copy it under a different name and then change it.
DBA4079E	This monitor is currently in use locally. Stop the monitor, and then remove or rename it.	You cannot remove or rename an active monitor.	Stop the monitor before removing or renaming it.
DBA4080E	This monitor is currently in use remotely. Wait till the monitor is stopped, and then remove or rename it.	You cannot remove or rename an active monitor.	Wait till the monitor is stopped before removing or renaming it.
DBA4083E	This monitor could not be found. Another user might have removed it. Stop all monitoring and then refresh your list of monitors.	Another user might have removed the monitor that you are using.	Stop all monitoring and refresh your list of monitors.
DBA4090E	Connection to the JDBC server has ended abnormally. Close the Control Center and retry the operation. If the problem persists, take a trace at the JDBC server and contact support personnel.	An unexpected error has occurred.	Close the Control Center and retry the operation. If the problem persists, take a trace at the JDBC server and contact support personnel.
DBA4095I	This function has not been implemented on this object.	This function has been planned for a future release but is not currently implemented on this object.	None.
DBA4220I	Full database restore cannot be done from a table space backup image.	Full database restore cannot be done from a table space backup image.	None.
DBA4221I	Table space selection is not allowed for the media type.	Table space selection is not allowed for the media type.	None.
DBA4222I	Table space selection is not allowed since the database is in backup pending state.	Table space selection is not allowed since the database is in backup pending state.	None.
DBA4223I	Full database required when backup image information is entered manually.	Full database required when backup image information is entered manually.	None.
DBA4730E	Performance monitoring encountered a problem while accessing the monitor server. Monitoring cannot continue. smcode: `Error-code`	See the Administration Server error logs for more information.	Contact your technical service representative with the smcode.
DBA4731E	A resource problem occurred on the Monitor Server. smcode: `Error-code`	See the Administration Server error logs for more information.	Free up some server resource and retry the operation. If the problem persists, contact your technical service representative with the smcode.
DBA4732E	A problem occurred when trying to attach to the database instance. smcode: `Error-code`	See the Administration Server error logs for more information.	Retry the operation. If the problem persists, contact your technical service representative with the smcode.
DBA4733W	The monitored database instance is stopped. Restart the instance. smcode: `Error-code`	See the Administration Server error logs for more information.	Restart the instance. If the problem persists, contact your technical service representative with the smcode.
DBA4734E	Performance monitoring encountered a problem while accessing the monitor server. smcode: `Error-code`	See the Administration Server error logs for more information.	Retry the operation. If the problem persists, contact your technical service representative with the smcode.
DBA4735E	A problem occurred when trying to attach to the database instance. smcode: `Error-code`	See the Administration Server error logs for more information.	Contact your technical service representative with the smcode.
DBA4736E	Unable to determine the current territory code or current code page in use on the client. smcode: `Error-code`	The client's territory code and code page must be sent to the server so that the data is returned in the correct code page. The Monitor Server was unable to determine the active territory code or code page.	Refer to your operating system documentation to determine how to set the territory code and active code page for your system. Retry the operation after setting the territory code and code page.
DBA4737E	Unable to set the current client territory code or current code page on the server. smcode: `Error-code`	The client's territory code and code page must be sent to the server so that the data is returned in the correct code page. The Monitor Server was unable to set the client's active territory code or code page on the server.	Refer to your operating system documentation to determine how to activate the client's territory code and active code page on your server's system. Retry the operation after activating the territory code and code page.
DBA4738E	The Administration Server on system `name` is not started. smcode: `Error-code`	The listed Administration Server on system `name` is not started.	Start the Administration Server and retry the operation.
DBA4739E	The client system's code page could not be determined. The client system might not be set up correctly. smcode: `Error-code`	This is a client system setup problem.	Contact IBM Service.
DBA4740E	The client code page `name` is not available on instance `name`. smcode: `Error-code`	The listed code page has not been installed on instance `name`.	Contact your system administrator. Your administrator should install code page `name` on instance `name`.
DBA4741E	The client code page `name` is not available on instance `name`, at node `name`. smcode: `Error-code`	The listed code page has not been installed on instance `name`, at node `name`.	Contact your system administrator. Your administrator should install code page `name` on instance `name` at node `name`.
DBA4742E	The Administration Server `name` cannot be found. smcode: `Error-code`	Possible reasons for this problem include: 1) Remote instance name is not valid. 2)Hostname is not valid.	Contact your system administrator.
DBA4743E	The Administration Server `name` detected a problem. sqlcode: `Error-code`. smcode: `Error-code`	The Administration Server `name` had an internal error.	Contact your system administrator.
DBA4744E	The Control Center could not communicate with the parallel tools on instance `name` at node `name`. Try starting communications. smcode: `Error-code`	Communications may not have been started.	Contact your system administrator.
DBA4745E	The TCP/IP port configuration between the Control Center and its listener (db2cclst) on instance `name` at node `name` is not correct. smcode: `Error-code`	The /etc/services file at node `name` might contain incorrect information.	Contact your system administrator. Your administrator should check that the port name of db2ccmsrv is entered correctly in the /etc/services file on node `name`.
DBA4746E	Instance node host name `name` is not valid on instance `name`. smcode: `Error-code`	The db2nodes.cfg file for instance `name` might contain incorrect information.	Contact your system administrator. Your administrator should validate the host name found in the db2nodes.cfg file for instance `name`.
DBA4747E	The Performance Monitor did not receive a response from node `name` within the snapshot capture interval. smcode: `Error-code`	A performance or communications problem on the listed node is preventing a response from being sent, or the snapshot capture interval is not long enough to allow each node time to respond to the request.	Contact your system administrator. Your administrator can 1) Validate the performance on the listed node. 2) Increase the snapshot capture interval to allow more time for the node to respond to the snapshot request.
DBA4748E	Logical node `name` on instance `name` is not valid. smcode: `Error-code`	The db2nodes.cfg file for instance `name` might contain incorrect information.	Contact your system administrator.
DBA4749E	The Monitor Server on instance `name` is unable to establish communications with node `name`. smcode: `Error-code`	The communications subsystem may not have been started.	Start the db2cclst process on the specified node. If problem still persists, contact your system administrator.
DBA4750E	The instance being switched to does not exist. smcode: `Error-code`	See the Administration Server error logs for more information.	Contact your technical service representative with the smcode.