DBA6000-7999

DBA Message ID Message Explanation User Response

DBA6001I

 The replication subscription set, subscription-set, is in use. Please try again later.

The Apply program is currently processing the replication subscription and this action cannot be deactivated. Wait until the Apply program has completed its processing and retry your command.

No action is required.

DBA6002I

 The replication source, source-name-1.source-name-2, was defined successfully. To begin capturing changes to the replication source, start the Capture program from the command line.

The Capture program requires a defined replication source in order to run.

Make sure the Capture program is running.

DBA6003I

 The replication subscription was defined successfully. To begin replicating the subscription set, ensure that the Apply program has been started from the command line.

The Apply program requires a defined replication source in order to run.

Make sure the Apply program is running.

DBA6004I

 The replication subscription was successfully changed.

This is for your information only.

No action is required.

DBA6005I

 The replication sources were successfully removed.

This is for your information only.

No action is required.

DBA6006I

 The replication source, source-name, could not be removed.

This is for your information only.

No action is required.

DBA6007I

 The replication subscription, subscription-name, could not be removed.

This is for your information only.

No action is required.

DBA6008I

 The replication subscriptions were successfully removed.

This is for your information only.

No action is required.

DBA6009I

 file-name is locked by another action.

The file is currently being used by another action.

Wait until the action is completed and retry your command.

DBA6010I

 The join was successfully defined.

This message is for your information only.

No action is required.

DBA6012I

 The replication source was defined successfully. To begin capturing changes to the replication source, ensure that the Capture program has been started from the command line.

The Capture program requires a defined replication source in order to run.

Make sure the Capture program is running.

DBA6013I

 The replication subscription was successfully updated.

This message is for your information only.

No action is required.

DBA6014I

 The replication subscription was successfully cloned.

This message is for your information only.

No action is required.

DBA6015I

 The SQL statements for this action have been saved in a file for future editing and execution.

This message is for your information only.

No action is required.

DBA6016I

 The SQL script file has been run successfully.

This message is for your information only.

No action is required.

DBA6100I

 The Apply program will only perform full refresh copies to this set.

This message is for your information only.

No action is required.

DBA6101E

 The table, table-name-1.table-name-2, cannot be found.

The control table specified could not be located in the database or was accidentally dropped.

Create the control table. See the Tables Chapter for more details.

DBA6102I

 This action may take some time to complete. Please wait...

This message is for your information only.

No action is required.

DBA6103E

 The SQL file, file-name, cannot be run.

The user may have edited the SQL statement file for a replication action, such as defining a replication source, and there is an error in the SQL statement file.

Correct the error in the SQL statement file and run the file again.

DBA6104W

 No unique prefix character was found. The prefix character will be set to NULL.

A prefix character is an alphabetical or numerical character used to distinguish before-image columns in the source table. If a prefix character cannot be assigned because all possible prefix characters are already in use, you will receive this warning. The change data table cannot be created.

Uncheck the before-image columns and rerun the action.

DBA6105E

 The field, field-name, requires your input.

The user has not filled in a required field.

Specify a parameter and select OK.

DBA6106E

 The replication action does not currently support this database system.

The replication action must support your database system in order to run.

Contact your IBM Service representative.

DBA6107E

 Please enter a different value for the field, field-name.

When cloning a replication subscription, the target server and Apply qualifier fields must be different from the original target server and Apply qualifier fields.

Enter a different target server name or Apply qualifier and select OK.

DBA6108E

 The action cannot be completed due to a syntax error.

The SQL statement contains a syntax error.

Check the SQL reference for the proper syntax. For subscription actions, check the where clause, the rows page, or the CREATE column. For define-join actions, check the CREATE VIEW statement.

DBA6109E

 SHOW COLUMNS action cannot be completed.

The SHOW COLUMNS action requires that a table be selected.

Select a table from the Selected Table list box and then press the SHOW COLUMNS key.

DBA6110E

 The SQL file, file-name, cannot be opened.

The SQL file either does not exist, is in the wrong subdirectory, or is engaged in another process.

Make sure you enter the correct file name and that the file is in the correct subdirectory. If the file is engaged in another process, terminate the process and reenter the file name.

DBA6111E

 The file, file-name, cannot be opened.

The file either does not exist or is in the wrong subdirectory.

Make sure you enter the correct file name on the Replication page of the Tool Settings notebook.

DBA6112I

 You have chosen to substitute user-defined values to define replication objects in the Tool Settings notebook. Please supply these values in the file file-name.

This message is for your information only.

No action is required if you have already supplied user-defined values in the file.

DBA6113E

 keyword is an invalid keyword in file file-name.

The specified keyword is invalid and may be a typographical error.

Use the keywords as given in the default file "DPREPL.DFT".

DBA6114E

 The value for keyword keyword cannot be found in file file-name.

The value of this keyword is required for this action to complete.

Specify a value for this keyword in the file.

DBA6115E

 None of the items in the column list were selected. This action cannot be completed.

At least one item in the column list must be selected for this action to complete.

Select one or more items from the column list and press OK.

DBA6116E

 The value for keyword keyword is invalid in file file-name.

The value of this keyword is either too long, an incorrect data type, or in an incorrect format.

Correct the value and invoke the action again.

DBA6117W

 The before-image column column-list was truncated to number bytes because the length of the original column was at the database limit before being appended to the before-image prefix before-image-prefix.

The length of the column from the original source table was at the database limit. When appended to the before-image prefix, some characters at the end of the column name were truncated to fit the database limit. This new before-image column name may no longer be unique because the truncated characters may be needed to guarantee a unique name.

Uncheck the before-image column when the truncated name is not unique and rerun the action.

DBA6118W

 Datatypes datatype-list are not supported on the database database. The datatypes will be converted to datatype-list in the SQL script.

Some datatypes from the source are not supported on the named database. However, equivalent datatypes could be found on the named database. The generated SQL statements will use the converted datatypes in place of the unsupported datatypes.

No action is necessary if the converted datatypes are acceptable. If they are not acceptable, uncheck the target columns and rerun the action.

DBA6119W

 Datatypes datatype-list are not supported on the database database. The columns containing these datatypes will be excluded from the SQL script.

Some datatypes from the source are not supported on the named database. No equivalent datatypes could be found on the named database. The generated SQL statements will exclude any columns containing the unsupported datatypes.

Contact IBM service if you would like to recommend a specific datatype be supported on the named database in the future.

DBA6120W

 The source table table-name was not defined with a primary key. Specify a primary key for the target table in the Target Columns page.

The define subscription action could not find a qualifying primary key for the source table, therefore the define subscription could not determine an appropriate primary key for the target table.

Specify a primary key for the target table in the Target Columns page of the Advanced notebook.

DBA6121W

 An incompatible Java Runtime Environment has been detected. Please verify that the required level of the Java Runtime Environment has been installed.

The installed Java runtime is not supported by the DB2 Java application.

Refer to the Control Center readme.htm for information on prerequisite Java Runtime Environment levels.

DBA6123E

 The requested action cannot be performed because the schema names of the objects exceed number bytes in length.

The data replication components support schema names up to 128 bytes in length. You tried to perform a replication action against objects that have longer schema names. The action cannot be performed.

Select objects whose schema names are 128 bytes or less, and perform the action again.

DBA6124W

 The requested action cannot be performed on some of the objects you selected because the schema names of the objects exceed number bytes in length.

The data replication components support schema names up to 128 bytes in length. You tried to perform a replication action against some objects that have longer schema names. The action will be performed only on those objects whose schema names are 128 bytes or less.

No action is required.

DBA6125W

 The field field, contains a schema name exceeding number bytes in length. The schema name will be truncated to number bytes.

The data replication components support schema names up to 128 bytes in length. The schema name in the field exceeds 128 bytes and it will be truncated to 128 bytes.

No action is required. However, you can type a shorter schema name in the field, if you do not want the existing schema name truncated.

DBA7000E

 The license for product-name could not be removed. RC = return-code.

The license could not be removed. Either the license could not be found in the nodelock file or the nodelock file could not be updated.

Check the permissions of the nodelock file and that the license exists in it.

The location of the file is platform specific:
  • AIX - /var/ifor/nodelock
  • Windows operating systems - $DB2PATH/license/nodelock
  • All other operating systems - /var/lum/nodelock

DBA7001E

 The license could not be added to the nodelock file. RC = return-code.

There was an error transmitting the license file or installing the license.

Please check the permissions of the nodelock file. The location of the file is platform specific:

  • AIX - /var/ifor/nodelock
  • Windows operating systems - $DB2PATH/license/nodelock
  • All other operating systems - /var/lum/nodelock

Alternatively you can also add the license using the command line utility db2licm.

If the problem persists please contact IBM Service.

DBA7002E

 The license certificate is invalid. Please try the command again with a valid license file. RC = return-code.

The license certificate contained in the file specified does not contain a valid db2 license or is in an unrecognizable format.

Please obtain a valid DB2 license certificate from your IBM representative or authorized dealer.

DBA7003W

 The list of current users could not be retrieved. RC = return-code.

The daemon or service that tracks the users is not functioning correctly or has not been started. You must have either the concurrent user policy or registered user policy activated.

Turn on a either the concurrent user policy or registered user policy and restart all the instances.

If the problem persists contact IBM Service.

DBA7004E

 The registered user could not be removed from the registered user list. RC = return-code.

The registered user list on the server could not be updated with the changes you have requested.

Check to make sure the user exists and that this is a valid action for this product. If the problem persists contact IBM Service.

DBA7005E

 The registered user could not be added. RC=return-code.

The registered user list on the server could not be updated with the changes you have requested.

Check to make sure the username is valid and ensure that the registered user policy is valid for this product. If the problem persists contact IBM Service.

DBA7006E

 The license policy could not be updated. RC = return-code.

The attempt to update the license policy for this product did not succeed.

Restart the instance and the License Server using the command db2licd -xxx. On a Windows operating system, you can also restart the instance and the License Server using the Services Control Manager.

If the problem persists contact IBM Service.

DBA7007E

 The statistics regarding license usage could not be retrieved. RC = return-code.

Either the statistics are corrupt, there was a communication error, or no data is available. Data is generated on connects and disconnects after a policy is updated and the instances are restarted.
If the statistics are corrupt you can remove the statistics database. This will remove all previously collected statistics. The location is platform specific and depends on where the product is installed.
  • UNIX - DB2 installation directory/misc/db2licst
  • Windows operating systems -DB2 installation directory\license\db2licst.dat

DBA7008I

 The license policy will not take effect fully until the instances are restarted.

When the instances are restarted it rereads the license configuration.

Restart the instances on the server.

DBA7009E

 This product product does not support the specified license policy. RC = return-code.

The license policy specified is not available for use with this product.

Specify a valid license policy.

DBA7010E

 The License Center was unable to retrieve a list of products from the specified server. RC = return-code.

The list of products on this server could not be obtained.

Please restart the administration instance and the Control Center and try again. If the problem persists contact IBM Service.

DBA7011E

 You do not have proper authority to perform the specified action.

The user does not have permission to perform this operation.

Please login with a userid that has the proper permissions to perform this command.

DBA7012E

 No statistics are available for the specified time period.

No statistics are available for the time period that you specified.

Please enter a valid date range where statistics exist.

DBA7013E

 The license certificate filename could not be found. Please try the command again with a valid license file. RC = return-code.

The file specified does not exist or cannot be read.

Please obtain a valid DB2 license certificate from your IBM representative or authorized dealer.

DBA7014E

 Restart the Control Center and the administration instance and try the command again.

Restart the Control Center and the administration instance and try the command again.

If the problem persists please call IBM Service.

DBA7015E

 The license for DB2 OLAP Server cannot be updated. The DB2 OLAP processes are currently active.

DB2 cannot update the license for DB2 OLAP Server while DB2 OLAP Server is running.

To update your OLAP license, please stop all OLAP processes and reinstall this DB2 license.

DBA7016E

 The selected system does not have any instances specified.

A valid DB2 instance for the selected system was not found. Verify that you have properly cataloged at least one valid DB2 instance residing on the selected DB2 system.

Catalog a valid DB2 instance for the selected system, restart Control Center and try the command again.

DBA7017E

 No valid DB2 instances were found on the selected system.

A valid DB2 instance for the selected system was not found. Verify that the selected systems has at least one working DB2 instance.

Create a valid DB2 instance on the selected system and try the command again.

DBA7018E

 The number of processors on the server exceeds the number of processor entitlements for this product.

You are exceeding the number of processors allowed by your license agreement.

Purchase additional processor based entitlements from your IBM representative or authorized dealer and update your license using the db2licm command.

DBA7019E

 No supported DB2 instances were found on the selected system.

A supported DB2 instance for the selected system was not found. Verify that the selected system has at least one DB2 instance supported by this version of DB2 License Center.

Create a supported DB2 instance on the selected system and try the command again.

DBA7100W

 The file file-name could not be opened. The page page-name in the Information Center, which corresponds to that file, will not be shown.

The data for the Information Center is stored in a number of NDX files. The file file-name might be missing from the correct directory.

Ensure that the NDX files are installed on the file system.

Pages in the Information Center and their corresponding NDX files:
  • Concepts - db2booksuc.ndx
  • Tasks - db2tasksuc.ndx
  • Reference - db2refsuc.ndx
  • Troubleshooting - db2msgsuc.ndx
  • Sample Programs - db2sampsuc.ndx
  • Tutorials - db2webuc.ndx

DBA7101E

 The Information Center cannot be displayed because none of the Information Center's NDX files can be opened.

The Information Center must read at least one NDX file to display any links to DB2 information.

The data for the Information Center is stored in a number of NDX files. The files might be missing from the file system.

Ensure that the NDX files are located in the file system.

Pages in the Information Center and their corresponding NDX files:
  • Concepts - db2booksuc.ndx
  • Tasks - db2tasksuc.ndx
  • Reference - db2refsuc.ndx
  • Troubleshooting - db2msgsuc.ndx
  • Sample Programs - db2sampsuc.ndx
  • Tutorials - db2webuc.ndx

DBA7102W

 The file file-name is not formatted properly. The following lines were ignored: line-numbers. Ensure that these lines are formatted correctly.

Each line in an NDX file must be in the form of a comma-separated list. Here is an example:

"IBM",1,"IBM Home Page", http://www.ibm.com
The format of the list is as follows:
1
The name of the entry as it appears in the tree or list of items in the Information Center
2
The number representing the category of this entry
3
The description that appears on the status line when this item is selected
4
The full Web address indicating the location of the entry
If you have edited this file, ensure that each line is formatted properly as follows:
  • The name and description must start and end with double quotation marks.
  • The name and description cannot contain any double quotation marks.
  • Use commas as separators.
  • The first entry in the file is a number corresponding to the number of entries in the file. You must update this number manually if you add or remove entries.

DBA7200E

 A maximum of 10 columns can be selected as input to a geocoder.

More than 10 columns were selected as input to a geocoder.

Move column names from the Selected columns box to the Available columns box until the Selected Columns box lists 10 names or fewer.

DBA7201E

 The database is not enabled to perform Spatial Extender operations.

The database must be enabled for Spatial Extender before you can perform Spatial Extender operations.

Right-click the database and select Spatial Extender->Enable from the menu.

DBA7300W

 Database database-name cannot be displayed because it does not have a valid node cataloged.

There is no entry in the node directory corresponding to the node name provided for the specified database in the database directory.

Ensure that there is a node catalog entry corresponding to the node at which the database was cataloged.

DBA7301W

 There are no instances to display in the Health Center.

There are no entries in the node catalog and DB2INSTANCE is not set.

Catalog a node or specify the default DB2 instance on the client.

DBA7302E

 Alert information cannot be retrieved for instance instance-name or any of its objects because the instance catalog partition is down.

The health monitor cannot be queried for alert information because the instance partition and monitor are down.

Restart the database partition and try the action again.

DBA7303E

 Alert information cannot be retrieved for instance instance-name or any of its objects because the instance is down.

The health monitor cannot be queried for alert information because the instance and monitor are down.

Restart the instance and try the action again.

DBA7304W

 The object that was selected object-name is no longer present under the current toggle filter.

The selected object changed state on the most recent refresh of the data. Therefore, the object is no longer viewable in the navigation view on the current toggle filter selection.

Select another instance or database from the current toggle filter selection or select a different toggle button to view other states.

DBA7305E

 The alert that was selected no longer exists.

The selected alert no longer exists in the health monitor.

If the NOTIFYLEVEL setting is set to include the alert type, review the administration notification log to see details on the alert.

DBA7306E

 The alert no longer exists. Do you want to close the Details dialog?

The current details dialog is showing information on an alert that no longer exists.

Click on Yes to close the dialog, or click on No to leave the details dialog open.

DBA7307W

 The database manager configuration parameter value has changed since the dialog was last refreshed. Do you want to continue?

The value for the configuration parameter was changed since this details dialog was last refreshed.

Click on Yes to apply the change and overwrite the current setting, or click on No to return to the details dialog. If you click on No, refresh the contents of the dialog to see the current setting of the configuration parameter.

DBA7308W

 The database configuration parameter value has changed since the dialog was last refreshed. Do you want to overwrite the current value?

The value for the configuration parameter was changed since this details dialog was last refreshed.

Click on Yes to apply the change and overwrite the current setting, or click on No to return to the details dialog. If you click on No, refresh the contents of the dialog to see the current setting of the configuration parameter.

DBA7309W

 One or both threshold setting values have changed since the dialog was last refreshed. Do you want to overwrite the current values?

The value for the warning and/or alarm thresholds have changed since the details dialog was last refreshed.

Click on Yes to apply the change and overwrite the current setting, or click on No to return to the details dialog. If you click on No, refresh the contents of the dialog to see the current setting of the threshold values.

DBA7310I

 The threshold setting configuration updates have been applied.

The threshold setting configuration updates have been applied.

No action is required.

DBA7311I

 The configuration parameter update has been applied.

The configuration parameter update has been applied. It can take some time before the changes take effect.

No action is required.

DBA7312I

 The configuration settings have been reset to the original install default settings.

The configuration settings have been reset to the original install default settings. These health indicator settings were used at product install time as the initial settings for the health monitor.

No action is required.

DBA7313I

 The configuration settings for object object-name have been reset to the current object default health indicator settings.

The configuration settings for the specified object have been reset to the current object default health indicator settings. These settings are based on the global health indicator default settings for the object type of the specified object.

No action is required.

DBA7314W

 The updated configuration settings can be applied to existing objects. Do you want to propagate all changes to existing objects and overwrite current settings on those objects? If you select No, only the default settings will be updated.

The new global default health indicator settings can be propagated to all existing objects that are affected based on the object type for the changed health indicators. The global settings can be updated without propagating changes to existing objects.

Click on Yes to apply the global default health indicator updates and these changes to existing objects, or click on No to apply only the global default health indicator setting updates.

DBA7315W

 You must provide a script location that is accessible by all database partitions for the action to succeed on all database partitions. Do you want to continue creating the script?

The script being defined must be accessible to all database partitions for the alert action to succeed on all database partitions.

Click on Yes to continue creating the script, or click on No to return to the Script Details dialog.

DBA7316E

 You have chosen a start record value greater than the highest record number in the notification log. No records can be returned.

There are fewer records in the notification log than specified as the argument for start record. No records can be displayed.

Decrease the start record number in the filter condition.

DBA7317W

 You have chosen an end record value greater than the highest record number in the notification log. Do you want to continue?

The notification log has fewer records that are specified as the end record count. Log records can only be retrieved to the end of the file.

Click on Yes to retrieve all the log records up to the end of the file, or click on No to change the filter condition.

DBA7318I

 There are currently number alerts in the Health Center. For more details, launch the Health Center from the toolbar or from the beacon on the status line.

There are current alerts to be viewed in the Health Center.

No action is required.

DBA7319E

 The selected instance instance-name has been dropped since the last refresh.

The selected object no longer exists so alert information cannot be retrieved.

Recreate the object and re-try the action.

DBA7320E

 The selected database database-name has been dropped since the last refresh.

The selected object no longer exists so alert information cannot be retrieved.

Recreate the object and re-try the action.

DBA7321E

 The object object-name for which this alert was generated has been dropped. The requested action cannot be completed.

The selected object no longer exists so the action cannot be completed.

Recreate the object and re-try the action.

DBA7323I

 Removing the contact from the contact list does not change any configured notification settings in the Task Center or Health Monitor.

Any notification actions using the removed contact will not be updated. These notification actions will fail.

Remove any notification actions involving the removed contact.

DBA7324I

 Contact contact-name selected for notification no longer exists. The contact has been removed from the selected list.

Invalid contacts have been removed from the list selected for health notification.

No action required.

DBA7325W

 There are unsaved changes in the dialog. Do you want to discard the changes and refresh the details?

You have chosen the refresh or reset option on this dialog. All unapplied changes will be discarded.

Select No, if you want to retain the changes. Otherwise, select Yes to discard any unapplied changes.

DBA7326E

 No scheduler systems could be found. Task actions cannot be specified.

No scheduler systems are cataloged in the admin node directory. Therefore, no tasks can be located for the Select Tasks dialog.

Ensure the DB2 Administration Server for the scheduler system is cataloged in the admin node directory.

DBA7327I

 The configuration parameter updates have been applied. These changes to the global object type defaults do not affect existing settings for specific database objects.

The updated configuration settings apply only to the global default health indicator settings. If you have previously specified settings for a health indicator on a particular object, those settings will not be affected by these changes.

No action is required.

DBA7328I

 Evaluation has been disabled on the health indicator for the selected alert. The health indicator will not be evaluated on the Health Monitor refresh.

The alert configuration for the health indicator of the selected alert has been updated to disable evaluating thresholds or states. This change will not be reflected until the next time the health monitor refreshes.

No action is required.

DBA7329W

 Task task-name cannot be found in the task metadata. Task name is shown as task-id-number.task-suffix-number.

The Select Actions dialog retrieves the task name for task actions from the task metadata. There was no task matching the task id number and suffix number in the task metadata so a task name cannot be displayed in the dialog.

Check that the task exists in the metadata. If it has been deleted, update the action for the health indicator with the correct task id number and suffix number.

DBA7330E

 The action cannot be completed on this instance because its remote instance name is not known.

The remote instance name field is an optional parameter and was not specified. To perform this action on a remote instance, the remote instance name must be known.

Drop and recatalog the instance specifying the REMOTE_INSTANCE parameter.

DBA7331W

 There are one or more orphaned contacts in the health notification con tact list for the instance instance-name.

An orphaned contact is a contact that exists in the health notification contact list but is not defined in the contact list stored on the system specified by the CONTACT_HOST configuration parameter of the DB2 administration server.

Currently, there is at least one orphaned contact in the health notification contact list for the instance instance-name.

If you do not need the orphaned contacts any more, delete them. Otherwise, redefine them so that they will receive health alert notifications. You can use the Troubleshoot Health Alert Notification wizard to perform these actions.

DBA7332W

 The filter for the monitoring task monitoring-task-name is too complex to be displayed.

The filter for the monitoring task monitoring-task-name is too complex to be displayed in the Set Up Activity Monitor wizard. As a result, you will not be able to view or modify the filter using the Set Up Activity Monitor wizard.

To view the filter, query the view SYSTOOLS.AM_TASKS. To modify the filter, call the stored procedure SYSPROC.AM_SAVE_TASK.

DBA7500N

 The threshold value specified is not within the threshold range.

The threshold value specified is not valid. It has been reset to its previous value.

Specify a value within the valid range.

DBA7501N

 The configuration parameter value specified is not within the valid range.

The configuration parameter value specified is not valid. It has been reset to its previous value.

Specify a value within the valid range.

DBA7502N

 The specified configuration parameter value is not valid.

The configuration parameter value specified is not valid. It has been reset to its previous value.

Specify a valid configuration parameter value.

DBA7503N

 The specified threshold value is not valid.

The threshold value specified is not valid. It has been reset to its previous value.

Specify a valid number.

DBA7504N

 An instance attachment is required to invoke Memory Visualizer.

Memory Visualizer requires an instance attachment in order to be able to display the memory utilization and allocation.

Select or specify a version 8.1 instance or higher.

DBA7510W

 The action is not currently available with this version of the DB2 server. For this action, the DB2 server must be at level db2-version.

The Control Center client and the DB2 Server are at different levels. The requested action is not available for the current level of the DB2 server. The DB2 server must be at level db2-version.

Upgrade the DB2 server to the required level.

DBA7511W

 The action is not currently available with this version of the database. For this action, the database must be at level db-version.

The requested action is not available for the current level of the database. The database must be at level db-version.

Upgrade the database to the required level.

DBA7512W

 The action is not currently available because the required license is not found.

The requested action is not available because the DB2 Administration Server is not started or because the license is not installed.

Ensure the DB2 Administration Server is started and that the required license is installed.

DBA7513W

 The action is not currently available.

The action may not be available for the following reasons:

  1. The correct license is not installed
  2. The correct product is not installed.
  3. The client and the DB2 server are at different levels.
  4. The DB2 Administration Server is not started.
  1. Ensure the proper license is installed.
  2. Ensure the product is installed.
  3. Ensure the client and the DB2 server are at the same level.
  4. Ensure the DB2 Administration Server is started.

DBA7514W

 A satellite control database could not be found for the instance instance.

A satellite control database does not exist in instance instance, or it is not cataloged in the database directory.

To work with a satellite control database in instance instance, ensure that it is created and cataloged in the database directory. Or you can work with satellite control databases in other instances (if any).

DBA7515W

 Since the database is a down level server, new options that are not available in previous versions have been removed or disabled.

Since you are connected to a down level server, the new options that are not available on your server version have been disabled or are no longer available.

Complete the dialog, and run the command.

DBA7516N

 Memory Visualizer could not find the specified data file.

The specified file does not exist or it is an invalid Memory Visualizer data file.

Verify that the file name specified is correct.

DBA7517N

 Memory Visualizer could not write to the specified data file.

Memory Visualizer could not save the data file to the specified path and file name.

Verify that the specified path exists and that the file permissions are correct.

DBA7604N

 No storage management snapshot for the current database partition group can be found.

To take a storage management snapshot, from the Control Center, expand the object tree until you find the database partition group object. Right-click the database partition group object and select Manage Storage from the pop-up menu.

Choose a different option on the Redistribute Strategy page to proceed with the redistribute wizard, or close the wizard and take a storage snapshot first before continuing with the redistribute operation.

DBA7608N

 An error occurred when attempting to create the registry for stepwise redistribute settings for database-name.database-partition-group-name.

Without the registry records the stepwise redistribute tasks will fail.

Verify your file permissions and recreate the redistribute settings registry records using the Wizard.

DBA7609W

 The database partition group is not partitioned.

The current database partition group contains only one database partition.

There is no need for running redistribute utility for it.

DBA7610W

 The table is not distributed.

The table is defined under a database partition group which contains only one database partition.

No data distribution file is created for the given table.

Altering the distribution key can only be done to a table whose table space is associated with a single-partition database partition group.

You can add or drop distribution keys, using the ALTER TABLE statement.

You can also use the Design Advisor to migrate from a single-partition to a multiple-partition database. Search the Information Center for a topic called: "Using the Design Advisor to migrate from a single-partition to a multiple-partition database".

DBA7611N

 The stepwise redistribute property type is not valid.

The requested stepwise redistribute property entry cannot be retrieved or updated.

Enter a valid property type.

DBA7612N

 An error has occurred when accessing file.

The possible reasons include:

  • File format error
  • Communication error
  • Memory allocation error when reading from file

Fix any format errors in the file. Check the db2diag log file for more information to help resolve the communication or memory allocation errors. Rerun the application.

DBA7613W

 Affected tables within the database partition group may be locked and unavailable for long periods of time.

Redistribution can be a log-intensive activity.

It is recommended to run redistribute on a test database before running it on your production system to determine how long the redistribution will take.

To minimize the risk of running out of active log space during a redistribute, it is recommended that you perform some or all of the following actions:
  • Reduce or eliminate other log-intensive database activities
  • Use infinite logging
  • Use stepwise redistribution as recommended by the Wizard

DBA7614W

 Affected tables within the database partition group may be locked and unavailable for long periods of time when redistributing multiple database partition groups.

Redistribution can be a log-intensive activity.

It is recommended to run redistribute on a test database before running it on your production system to determine how long the redistribution will take.

To minimize the risk of running out of active log space during a redistribute, it is recommended that you perform some or all of the following actions:
  • Reduce or eliminate other log-intensive database activities
  • Use infinite logging
  • Schedule the redistribution of each database partition group to happen at a different time to minimize contention for available log space
  • Use stepwise redistribution as recommended by the Wizard

DBA7615N

 One or more tables required by the application are not defined with the expected definition.
The tables the application is trying to access do not match the expected definition. This may be caused by one or more of the following problems:
  • Table does not exist
  • Table column definition is not the same as expected

The tables may have to be dropped and recreated with the appropriate definition. If this error is being encountered during a drop, then you can force the tables to be dropped by specifying the FORCE option in the drop command.

DBA7616N

 Invalid partition weight for stepwise redistribute operation.

The value of the partition weight must be between 0 to 32767.

Enter an integer within the valid range and try again.

DBA7617N

 One or more input parameters do not contain valid values expected by the routine.
This may be caused by one or more of the following problems:
  • Numerical parameter is out of the expected range
  • Object referenced by a parameter may no longer exist

Verify your input parameters with the routine specification, and try again.

DBA7618W

 Verify that all databases at instance instance-name are cataloged.

When adding database partitions to an instance, all temporary table spaces for all databases must be altered with new containers on the new database partitions. A database must be cataloged at that instance for the Add Database Partition wizard to detect its temporary table spaces.

Review the list of databases on the first page of the Add Database Partition wizard.

If there are any databases missing:
  1. Close the wizard.
  2. Close the Add Database Partitions launchpad.
  3. Add the missing databases to the databases folder in the Control Center.

If there are databases listed that do not actually exist at the instance, remove them from the databases folder in the Control Center.

DBA7619W

 Verify that all databases at instance instance-name are cataloged.

When dropping database partitions from an instance, all data in all databases needs to be moved off the affected database partitions. A database must be cataloged at that instance for the Add Database Partition wizard to detect its database partition groups.

Review the list of databases in the Drop Database Partition from Database Partition Groups window.

If there are any databases missing:
  1. Close the window.
  2. Close the Drop Database Partitions launchpad.
  3. Add the missing databases to the databases folder in the Control Center.

If there are databases listed that do not actually exist at the instance, remove them from the databases folder in the Control Center.

DBA7620N

 There is no distribution key defined for the given table.

A distribution key is a column (or group of columns) that is used to determine the database partition in which a particular row of data is stored. Tables without a distribution key are only allowed in single-partition database partition groups. Without a distribution key, a data distribution file cannot be generated, and data distribution analysis cannot be performed.

Altering the distribution key can only be done to a table whose table space is associated with a single-partition database partition group.

You can add or drop distribution keys, using the ALTER TABLE statement.

You can also use the Design Advisor to migrate from a single-partition to a multiple-partition database. Search the Information Center for a topic called: "Using the Design Advisor to migrate from a single-partition to a multiple-partition database".

DBA7621W

 Tables require distribution keys before they can be redistributed from one to many database partitions. Review the database design before moving from one to many database partitions.

A distribution key is required to partition table data across a set of database partitions.

Tables without a distribution key are only allowed in single-partition database partition groups.

Use the Alter Table notebook to add distribution keys to all tables that will be partitioned.

Consider creating different database partition groups. Usually, smaller tables can stay on a small number of database partitions, even just one, while larger tables should be distributed across all or most of the database partitions.

Altering the distribution key can only be done to a table whose table space is associated with a single-partition database partition group.

You can add or drop distribution keys, using the ALTER TABLE statement.

You can also use the Design Advisor to migrate from a single-partition to a multiple-partition database. Search the Information Center for a topic called: "Using the Design Advisor to migrate from a single-partition to a multiple-partition database".

DBA7627N

 Unable to load snapshot data.

The selected snapshot no longer exists.

Select a different snapshot from the Current Snapshot list on the Storage Management toolbar.

If no other snapshot exists, you can capture a new snapshot by right clicking on a database, database partition group, or table space, and selecting the Capture Snapshot menu option.

DBA7628N

 Drop Database Partition task must start after the last data redistribution is complete. The last redistribution task is scheduled to start at start-date start-time.

All data redistribution tasks must be completed before the Drop Database Partition task can run. Redistribution moves the data off the database partitions that will be dropped.

Choose a new start time for the Drop Database Partition task or just save it to the Task Center and run it manually once all the redistribution tasks are complete.

DBA7630W

 The following hosts could not be found: host-names.

Add Database Partition will fail if these host names cannot be found on the network. Host names specified must refer to existing systems at the time that this Add Database Partition task is scheduled to execute.

Verify that all of the listed host names are correct. Ensure that the specified host names exist when this task is scheduled to execute.

DBA7631W

 The instance instance-name will be stopped and restarted when this task is run.
The script to be executed contains the following commands: 
db2stop force db2start

This will stop the database instance, refusing access to all connected applications. All databases in this instance will not be available while the instance restarts.

Run this task, which will restart the instance at the scheduled time, or schedule the task to run at a different time, or save the task to the Task Center and run it later.

DBA7632N

 The database partitions database-partitions cannot be removed from the following database partition groups partition-groups.

All database partition groups must have at least one database partition.

When altering a database partition group, you must keep at least one database partition in the database partition group. If you do not want any database partitions in the database partition group, you must drop that database partition group and lose any existing data.

DBA7633N

 The database partitions partition-names cannot be dropped because they are catalog partitions for one or more databases.

A catalog partition cannot be dropped without first dropping the corresponding database. On Windows systems, you cannot drop database partition 0.

Select one or more other database partitions to drop from the instance, or drop the databases for the catalog partition you wish to drop before trying to drop the database partition.

DBA7634N

 The container name container-name is invalid.

The container name must be a valid path if the container type is directory or file, or a valid raw device if the container type is raw device.

Redefine the container name to a valid path or raw device then attempt to change it, or add a new container and then remove the invalid one.

DBA7666W

 Configuration changes have been made for the previously selected database partition. Do you want to save the changes?

Another database partition was selected, but the configuration changes to the previously selected database partition have not been saved.

Click Yes to obtain the configuration parameter values for the next database partition and save the changes that were specified for the previously selected database partition.

Click No to obtain the configuration parameter values for the next database partition and discard the changes that were specified for the previously selected database partition.

Click Cancel to go back to the configuration parameter values for the previously selected database partition.

DBA7900N

 The SYSPROC.ALTOBJ stored procedure input parameter parameter is invalid.

An invalid parameter value was specified.
Reissue the stored procedure call with valid parameter values:
  • parameter 1 (IN), execModeName, choose from one of the following six values: 'GENERATE', 'VALIDATE', 'APPLY_CONTINUE_ON_ERROR', 'APPLY_STOP_ON_ERROR', 'UNDO' and 'FINISH'
  • parameter 2 (IN), sqlStmt, valid CREATE TABLE DDL is expected
  • parameter 3 (IN/OUT), alterId, use -1 if no alter plan and ID has been previously generated, use the previously generated integer id, if a existing plan is to be followed
  • parameter 4 (OUT), msg, use ? in the call statement

DBA7901W

 There has been a request to transform column column-name from source type source-type to target type target-type. However, there is no default casting function available.

The stored procedure attempts to use built-in scalar column functions to transform the existing data in the table from its source type into its target type. There is no built-in column function that can perform the data type transformation requested. Ensure that a UDF is created to transform the data, otherwise the existing data may not be transferred to the new table.

If you have a column function that can transform the data to its target type, update the SYSTOOL.ALTOBJ_INFO table with the following statement:


UPDATE SYSTOOLS.ALTOBJ_INFO_V
SET SQL_STMT='edited SELECT statement'
WHERE ALTER_ID='<alterId>'
AND SQL_OPERATION='SELECT'
AND EXEC_MODE LIKE '_1____'

Alternatively, change the target column type specified in the third parameter, so that there is a built-in column function that can be used for data transformation. Then call the stored procedure again with the new input.

DBA7902N

 The table to be altered contains at least one column data type that is not supported by the SYSPROC.ALTOBJ stored procedure.

DATALINK type, structured type UDTs, and reference type UDTs are not supported. The SYSPROC.ALTOBJ stored procedure cannot be used to alter a table containing non-supported column data types.

Do not attempt to alter a table containing non-supported column data types.

DBA7903N

 The table type is not supported by the SYSPROC.ALTOBJ stored procedure.

The following types of tables cannot be altered using SYSPROC.ALTOBJ:

  • Materialized Query Tables.
  • Type tables or a tables that are the scope of any existing reference column.
  • Remote tables referenced by a nickname.
  • Tables with activated row or column level access control.
  • Tables protected with row level LBAC.

Do not attempt to alter the table using the SYSPROC.ALTOBJ stored procedure.

DBA7904N

 The user does not have authority-name authority, which is required to run the SYSPROC.ALTOBJ stored procedure.

DBADM authority is required to run the SYSPROC.ALTOBJ stored procedure.

Obtain the necessary authority before running the stored procedure.

DBA7905N

 The drop column action cannot be performed at the same time as adding or renaming columns.

When dropping existing columns, column names are used to match the existing columns to their new definitions. When adding or renaming columns, the column index is used to match the existing and the new columns.

The drop column operation must be attempted separately from adding or renaming column operations, however you can add and rename columns at the same time. The sequence of the existing columns cannot be changed using alter.

If you need to perform more than one type of alter operation, the SYSPROC.ALTOBJ must be called multiple times, one for each compatible alter operation group using different DDLs.

DBA7906N

 The number of SQL statement generated for the alter process exceeds the expected limit.

This may occur when a large number of related objects for the table being altered, such as triggers, aliases, views, SQL stored procedures, and materialized query tables.

The SYSPROC.ALTBJ stored procedure cannot be used to alter the given table.

DBA7907W

 The alter process completed with errors.

This warning may occur when there are related objects of the table that are dependent on the columns that have been changed, or the existing data cannot be transformed into the their target data type, or conform to the new constrains.
Use the SYSPROC.ALTBJ stored procedure with the following parameter inputs so that the related objects can be recreated. 
CALL SYSPROC.ALTBJ('UNDO', CAST 
   (NULL AS VARCHAR(2)), alterID, ?)

Or examine the errors in the SYSTOOLS.ALTOBJ_INFO_V, update the SQL statements that caused runtime error, and run the stored procedure again in APPLY mode.

DBA7908E

 Some of the functions are not available because a set of stored procedures has not been installed for subsystem-name. The following stored procedures may be missing: stored-procedures.
The Control Center could not perform any of the following:
  • Call SYSPROC.DSNUTILS to determine which utilities are installed.
  • Call SYSPROC.DSNWZP to retrieve the subsystem parameters.
  • Locate at least one of the OS/390 Enablement stored procedures.

Ensure that the OS/390 Enablement stored procedures and DB2 stored procedures DSNWZP and DSNUTILS are installed and that the activation steps were performed. See the DB2 management Clients Program Directory for more information.