DBA1000-1999

DBA Message ID Message Explanation User Response

DBA1005W

 This action will force both Local Databases and Gateway applications. Do you want to continue?

You requested to force all applications on the instance.

Click Yes to process the request or No to cancel it.

DBA1006E

 An invalid plugin extension has been detected by the Control Center.

The file "db2plug.zip" has been corrupted or not properly setup.

The "db2plug.zip" file should be included in the tools directory under the sqllib directory.

Refer to the documentation for instructions on defining the "db2plug.zip" file and recreate the "db2plug.zip" file.

If the problem persists, contact the system administrator for assistance or use the Control Center trace command to determine if the plugin classes are being loaded. The command "db2cc -tf <filename>" will place the Control Center trace information in the specified filename. When specifying a filename, you must provide the absolute path to the file. To determine if the plugin classes are being loaded, search through the file for lines containing the text "PluginLoader".

DBA1007W

 An invalid object name or parameter was entered. The Control Center will start with the Systems folder as the root of the navigator tree.

An invalid object name means that the system, instance, subsystem, or database name entered cannot be found, either because it does not exist or because the combination of names entered is invalid. For example, the database name entered may exist but not within the specified system name. An invalid parameter means that something other than -h, -i, -sub, or -d was entered.

Ensure that you are using valid object names and parameters, and try again.

DBA1100W

 Less than number MB of memory is dedicated to your server. No recommendation has been made. The current values on the Results Page match the suggested values.

Because the amount of memory dedicated to the server is so small, the Configuration Advisor cannot make a recommendation.

The suggested values in the "Results Page" are the same as the current values.

If you can dedicate more memory to the server, turn to the "Server Page", increase the amount of memory, and try again. Otherwise, click on Cancel to close the Configuration Advisor.

DBA1101I

 Stripe set information about the table space container could not be obtained. Stripe sets will not be shown.

The connected user might not have sufficient authority to obtain stripe set information.

SYSADM authority is required to obtain stripe set information.

DBA1102E

 An error occurred when the Configuration Advisor tried to save the suggested values in a system file.

Either the Configuration Advisor could not create a CFG subdirectory under your instance directory or it could not save a system file containing recommendations into the CFG subdirectory of your instance directory.

Make sure the disk containing the instance directory is not full and you have write access to this disk. Afterwards, click on Done to try again.

DBA1103W

 The Configuration Advisor was unable to assign a minimum amount of memory to the buffer pools due to other memory requirements determined from your responses.

The Configuration Advisor is unable to provide a set of recommendations based on the specified database requirement with the specified memory resource.

Increase the percentage of physical memory allocated, if more memory resource is available. Otherwise, increase the amount of physical memory on the server.

DBA1104I

 The instance and database configuration parameters were successfully updated. The instance name must be stopped before most changes come into effect. You may want to rebind your packages after the new configuration parameters take effect so that the new values will be used during the bind.

The Configuration Advisor has updated the database manager configuration parameters, database configuration parameters, and buffer pool sizes in the SYSBUFFERPOOLS catalog.

The changes will not take effect until the instance is stopped on the server.

Packages were bound with the old configuration parameters. They need to be rebound, after the new parameters take effect, to exploit these new parameters.

When you are ready to use the new configuration parameters, stop the instance, and then start the instance.

Rebind your packages if necessary.

DBA1107E

 An error occurred when the Configuration Advisor tried to get system information from your server.

An unexpected error occurred. The Configuration Advisor cannot continue.

Contact your system administrator.

DBA1108W

 The Configuration Advisor was unable to increase the sizes of the buffer pools due to other memory requirements determined from your responses. The buffer pool sizes are left unchanged. The use of the suggested set of configuration values may cause paging on the server.

This is a warning that there may not be enough memory dedicated to your server to run the workload that you specified.

Review your selections on previous pages of the Configuration Advisor to check that the workload description is appropriate or add more memory to your server.

DBA1109W

 The transactions rate you entered is more than ten times the average number of connected applications. If you are using a transaction manager, ignore this message. If not, consider changing the rate.

The Configuration Advisor verifies that the transactions rate is reasonable. The transaction rate may be too high if you are not using a transaction manager.

If you are using a transaction manager, ignore this message. Otherwise, use a lower number of transactions per minute, or increase the average number of connected applications.

DBA1110I

 The system database directory has no entries.

There are currently no entries found in this database directory.

No action is required.

DBA1111E

 The database alias name already exists for another database.

You requested that a backup be recovered into a new database, but the database name you specified is already used as an alias for an existing database.

When a database is created, the database is cataloged in the system database directory using the database name as the alias, and this alias must be unique.

Specify a database name that is not being used as an alias, or request that the backup be recovered into the existing database.

DBA1112E

 The database alias name was not found in the system database directory.

You requested that a backup be recovered into an existing database, but a database no longer exists with this alias.

Select an existing database, or request that the backup be recovered into a new database.

DBA1113E

 Restart failed because indoubt transactions exist against the database and the connection to the database was dropped.

The restart operation encountered indoubt transactions. This left the database in an inconsistent state. The DBA Utility dropped the connection to the database.

Resolve the indoubt transactions. If they are not resolved, applications must restart the database whenever it is required.

If you are in an XA/DTP environment, and the transaction manager that was using the database is available, instruct it to resolve the indoubt transactions.

Otherwise, use the Command Line Processor to manually complete each indoubt transaction.

DBA1114E

 Database name is in backup pending state. A full backup must be done before the database can be used.

This state will prevent the database from being updated. The database must be backed up before any updates can happen.

Back up the database.

DBA1115E

 Enter a value for name.

A value is required.

Provide the value and retry the request.

DBA1116E

 The value for parameter must be between minimum and maximum.

The value must be within the specified range.

Enter a value in the specified range and retry the request.

DBA1117E

 The value for name is not valid.

The value entered is not valid.

Correct the value and retry the request.

DBA1118E

 The value for name must not exceed maximum.

The value entered is not valid.

Correct the value and retry the request.

DBA1119E

 The value for name must not be smaller than minimum.

The value entered is not valid.

Correct the value and retry the request.

DBA1121I

 A job was created for the request description on system system. Its job number is number. To view the status and output of the job, use the Jobs page on the Journal.

The job was successfully started.

To view the status and output of the job, use the Jobs page on the Journal.

DBA1122I

 The job has completed for the request description on system system. For the status and output of the job, view job number in the Jobs page on the Journal.

The job has completed.

To view the status and output of the job, use the Jobs page on the Journal.

DBA1123I

 Job description is terminated.

The job was canceled in response to a user request.

No action is required.

DBA1126I

 The database has no table spaces.

The database has no table spaces.

No action is required.

DBA1127I

 The table space has no containers.

The table space has no containers.

No action is required.

DBA1128E

 No containers have been specified. Select "Add" in order to create containers.

The current list does not contain any new containers.

Select "Add" and fill in the necessary fields to add a container to the list.

DBA1129E

 Provide a value for name.

The operation you requested can be performed only if you enter a value for name.

Enter a value, and then click on OK.

DBA1130E

 The name entries must not exceed maximum characters.

You entered a value that exceeded the maximum number of characters.

Enter a valid value, and then click on OK.

DBA1131E

 device is not a valid tape device.

The operating system did not accept the specified tape device. Local tape devices are of the form "\\.\TAPEn", where n represents the drive number (0 is the first).

Enter a valid name for the tape device, and then click on OK.

DBA1132E

 Tape device device does not support a tape mark blocksize of blocksize.

The Control center uses a tape mark blocksize that is not supported by the specified tape device.

Use the Command Line Processor to submit the request. Specify a supported blocksize in the DB2 INITIALIZE TAPE command.

DBA1133E

 An error occurred operating tape device device.

An unexpected error occurred while operating the specified tape device.

Resubmit the request. If the problem persists, contact your system administrator.

DBA1134I

 A job was created for the request description. However, no job-related entries can be created in the Journal because the database administrative server (DAS) instance could not be accessed.

The job started successfully, but the status and output of the job will not be logged in the Journal. This can happen if the DAS instance is not started.

To have the status and output of the job logged in the Journal, start the DAS instance first before starting a backup operation.

DBA1135I

 The job has completed for the request description.

The job has completed.

No action is required.

DBA1136E

 A backup at the table space level cannot be performed because the database db is not enabled for rollforward recovery.

You can only back up a database at the table space level if you have first enabled that database for rollforward recovery.

To enable the database for rollforward recovery, you can either:

  • Use the Database Logging Wizard to change your logging type to ARCHIVE logging.
  • Set either the logarchmeth1 or logarchmeth2 database configuration parameter to a value other than OFF, disconnect all existing applications from the database, and perform an offline backup of the database.

DBA1137E

 The value for name must not be smaller than minimum units.

The value entered is smaller than the minimum minimum units.

Enter a valid value and retry the request.

DBA1138E

 The value for name must not exceed maximum units.

The value entered exceeded the maximum of maximum of units.

Enter a valid value and retry the request.

DBA1139E

 You must allocate at least pages for the system catalog.

There cannot be more than pages in each table space container. Each page of data requires 4 KB. So 1 MB of storage is equal to 256 of these 4 KB pages.

Enter a valid value and retry the request.

DBA1140E

 You cannot allocate more than pages pages in a single container.

Each page of data requires 4 KB. So 1 MB of storage is equal to 256 of these 4 KB pages.

Enter a valid value and retry the request.

DBA1141E

 You must allocate at least pages pages in each container.

The minimum number of pages in a table space container is related to the extent size of the table space. It is 5 times the extent size plus one page. So for a table space with an extent size of 32 pages (the default value), the minimum size of a single container is 161 pages.

Enter a valid value and retry the request.

DBA1142W

 The LOGARCHIVE database configuration parameter has currently been set to ON for database name. As soon as all applications have disconnected from the database, the database will be in backup pending state. This state prevents the database from being updated. The database must be backed up before any additional updates can occur.

Before the database manager can start logging each transaction in your database, it must have a full offline database backup to use as a starting point.

Make a full offline database backup as soon as possible. If this is not possible, set the LOGARCHIVE parameter to OFF.

DBA1143E

 You cannot perform an offline backup right now because at least one application is still connected to the database. You can either try again later, or disconnect all applications connected to the database immediately by selecting force from the instance object's pop-up menu.

An offline backup cannot be performed until all applications connected to the selected database have stopped. You can either wait for the applications to disconnect themselves, or you can force the connected applications right now.

Either try the action later, or, to force all applications connected to the selected database immediately, select "Force" from the instance object's pop-up menu.

DBA1144E

 The container container-name already exists.

Each table space container must be unique.

Specify a file name or directory that does not currently exists on the system.

DBA1145E

 The container container-name has been specified more than once.

Each table space container must be unique.

Specify a file name or directory that is not currently in your list of new containers.

DBA1146E

 The container container-name is included in both the user and temporary storage spaces.

Each table space container must be unique.

Change the file name or directory of the container in either the user or temporary table space.

DBA1147E

 The container container-name is included in both the catalog and temporary storage spaces.

Each table space container must be unique.

Change the file name or directory of the container in either the catalog or temporary table space.

DBA1148E

 The container container-name is included in both user and catalog storage spaces.

Each table space container must be unique.

Change the file name or directory of the container in either the user or catalog table space.

DBA1149E

 param-1 does not have enough free space for the containers you specified.

When a DMS container is created it consumes the full amount of space you allocated to it.

Change the location of the container to an area that has more storage, or increase the available storage in the current location of the container.

DBA1150E

 A column with the same name already exists.

The column was not added because a column with the same name is already specified or exists in the table being created or altered.

Specify a different column name.

DBA1151W

 The requested operation was not performed against the column or constraint. Reason code = reason-code.

An attempt was made to add, alter, or remove a column or constraint during table creation or alteration. The reason code given indicates the actual rule violation, as follows:

1

A column or constraint with the same name already exists.

2

The column participates in the primary or distribution key and cannot be removed.

3

The column participates in a unique key and cannot be removed.

4

The column participates in a foreign key and cannot be removed.

5

The column participates in a table dimension and cannot be removed.

6

The column may participate in a table check constraint. The operation was allowed.

7

Primary and unique keys cannot be defined as a subset of all dimension columns.

8

Dimensions cannot be defined such that any primary or unique key becomes a subset of all dimension columns.

9

Primary and unique keys must be defined as supersets of the distribution key.

10

The distribution key must be defined as a subset of all existing primary and unique keys.

11

An object with that column set already exists.

12

The column participates as a partitioning column and cannot be removed.

13

The column participates as a partitioning column and its data type cannot be changed.

14

Columns of XML data type are not supported in partitioned tables.

Correct the condition that is causing the operation to fail and retry the operation.

DBA1152E

 A constraint with the same name already exists.

The constraint was not added because a constraint with the same name is already specified or exists in the table being created or altered.

Specify a different constraint name.

DBA1153E

 The object is already in the list.

The specified object already exists in the list. The action is not performed.

Specify another object or close the window.

DBA1154E

 The specified system, instance, and database do not identify a recognized database.

The system, instance, and database specifications do not identify a database that is known to the application. The action is not performed.

Either ensure that the system, instance, and database names are correct; or add the system, instance, and database that you want to access to the application.

DBA1155E

 The object object-name no longer exists in the database. The request cannot be performed.

The specified object no longer exists in the database and cannot be operated on. The request is terminated.

Select the "Refresh" action in the pop-up menu of the object folder to get an updated list of objects.

DBA1156W

 The request completed with warnings. See the administration tools log for details.

The requested action completed, but one or more warning messages were issued.

See the administration tools log for more information.

DBA1157E

 No authorities or privileges were granted or revoked on object-name for user-name. See the administration tools log for details.

The requested action completed. No action was taken against the authorities or privileges on the specified object for the specified user or group.

None

DBA1158I

 Number of records read during the load = count. Number of records skipped before the load begins = count. Number of rows loaded into the target table = count. Number of records that could not be loaded = count. Number of duplicate rows deleted = count. Number of records loaded successfully and committed to the database = count.

The action completed with the specified results.

None

DBA1159I

 Export completed. item-description = count.

The export action completed successfully with the specified results.

None

DBA1160I

 Import completed. Number of records read during the import = count. Number of records skipped before the import begins = count. Number of rows imported into the target table = count. Number of records that could not be imported = count. Number of duplicate rows deleted = count. Number of records imported successfully and committed to the database = count.

The import action completed successfully with the specified results.

None

DBA1161I

 item-description = count.

The import or export completed with the specified results.

None

DBA1162I

 Load completed. Number of records read during the load = count. Number of records skipped before the load begins = count. Number of rows loaded into the target table = count. Number of records that could not be loaded = count. Number of duplicate rows deleted = count. Number of records loaded successfully and committed to the database = count.

The load action completed successfully with the specified results.

None

DBA1163E

 The table was not copied. See the administration tools log for details.

One or more warnings or errors occurred when copying the table. The table was not copied.

See the administration tools log for more information.

DBA1164E

 The specified target table already exists. The source table was not copied.

The copy table action failed because the target table exists.

Either specify a new target table or delete the existing target table and try the action again.

DBA1165E

 No privileges were granted or revoked for user-name.

Privileges were not granted to or revoked from the specified user or group since no privileges have been changed.

Resubmit the command after making changes to the current privileges.

DBA1166E

 The identifier identifier-name contains unbalanced quotes. Correct the identifier and try the action again.

The specified identifier contains unbalanced single or double quotes. The naming rules require balanced quotes. The action is not performed.

Correct the identifier and try the action again.

DBA1167E

 The identifier identifier-name contains embedded blanks. Correct the identifier and try the action again.

The specified identifier contains blank characters, which violates the naming rules for ordinary identifiers. The action is not performed.

Remove the blanks or delimit the identifier with double quotes and try the action again.

DBA1168E

 The first character in the identifier identifier-name is not valid. Correct the identifier and try the action again.

The first character of the specified identifier is invalid. It must follow the naming rules for ordinary identifiers. The action is not performed.

Replace the first character with a valid one or delimit the identifier with double quotes then try the action again.

DBA1169I

 The command script that can update the instance and database configuration parameters was created successfully. Use the Script Center to run or schedule the script.

A new script was saved successfully in the Script Center. You may open the Script Center to view, run or schedule the new command script.

After the script is run, the changes will not take effect until the instance is stopped on the server.

Packages were bound with the old configuration parameters. They need to be rebound, after the new parameters take effect, to exploit these new parameters.

To view, run or schedule the newly saved script, open the Script Center by selecting the Script Center icon from the icon bar.

After you have run the script and when you are ready to use the new configuration parameters, stop the instance, and then start the instance.

Rebind your packages if necessary.

DBA1170E

 The page size of the table space and the page size of the buffer pool buffer-pool must be equal.

You must choose an existing buffer pool whose page size matches that of the table space you wish to create. The default buffer pool has the default page size of 4K. If any other page size is desired for the table space, a buffer pool with a matching page size must exist.

From the Advanced Table Space window, change the page size of the table space to match that of the buffer pool or change the buffer pool to one whose page size matches that of the table space. If there are no buffer pools of the desired page size, you can create one from the Create Buffer Pool window.

DBA1171N

 The temporary table space tablespace specified cannot be used for this utility operation.

The backup and restore commands cannot be performed on a temporary table space.

Resubmit the command using only valid non-temporary table spaces.

DBA1172W

 Since the database is in backup pending state, you must perform an offline database backup. This has been preselected for you. Other options that are no longer available having been disabled.

The only valid operation for a database in Backup Pending state is to perform an offline database backup. The wizard has ensured that these options are selected. It has also disabled the other options in the wizard that are no longer available.

Complete the wizard, and run the command. It is recommended that you perform a full database backup.

DBA1173N

 A restore at the table space level cannot be performed because the database database is not enabled for rollforward recovery.

You can only restore a database at the table space level if you have enabled the database for rollforward recovery.

To enable the database for rollforward recovery, set either the logarchmeth1 or logarchmeth2 database configuration parameter to a value other than OFF, disconnect all existing applications from the database, and perform an offline backup of the database.

DBA1174I

 You have chosen more than one image for the same database partition. In most cases, you will not wish to do this.

In most scenarios, choosing more than one backup image to restore is not useful, and will actually slow down the total time to complete the restore.

Ensure that only one image for each database partition is selected.

DBA1175W

 This functionality requires an image for each database partition.

Rolling forward to a point in time requires an image for each database partition. You have not chosen all database partitions on the Available Images page, and so cannot use this option.

Return to the Available Images page and select one image for each database partition in your database.

DBA1176N

 The Control Center failed to automatically catalog the Tools Catalog Database database-name for system system-name.
Possible explanations are:
  • The database is specified incorrectly at the DB2 Administration Server for system system-name.
  • The database manager that contains the database is not configured for TCP/IP communication.
Possible solutions include:
  • Verify that the DB2 Administration Server configuration parameters are correctly specified.
  • Verify that the database manager is configured for TCP/IP communications.

If the problem persists, contact IBM Support.

DBA1177N

 A database connection to the Tools Catalog Database database-name cannot be made. SQLCODE sqlcode

A connection to the Tools Catalog Database database-name as defined in the DB2 Administration Server configuration parameters cannot be made.

This message will appear under one of the following conditions:

  1. The Tools Catalog Database has not been created.
  2. The Tools Catalog Database has been created but the DB2 Administration Server configuration parameters have not been updated.
  3. The Tools Catalog Database is configured properly but the connection failed.

Suggestions corresponding to the three conditions are:

  1. Create a Tools Catalog Database by issuing the CREATE TOOLS CATALOG command from the CLP.
  2. Update the DB2 Administration Server configuration parameters to define the Tools Catalog Database. Four parameters need to be udpated with the UPDATE ADMIN CONFIGURATION command:
    • SCHED_ENABLE
    • TOOLSCAT_INST
    • TOOLSCAT_DB
    • TOOLSCAT_SCHEMA
  3. Refer to the user response for the SQLCODE returned from the connect operation.

DBA1178W

 Task task-name was created with a more recent version of the Control Center.

The selected task was created with a more recent version of the Control Center. Some functionality for the task are not supported by the Control Center on the local machine.
You can choose to proceed and edit the task. When saving the task, you can:
  • Save the changes to the existing task. This will cause the loss of functionality that was specific to the more recent version of the Control Center.
  • Save changes by creating a new task. This will not alter the original task.

DBA1179W

 Task task-name created with a more recent version of the Control Center will be overwritten.

A task originally created with a more recent version of the Control Center will be overwritten. Proceeding with this operation will cause the loss of functionality that was specific to the more recent version of the Control Center.
You can choose to:
  • Save the changes to the existing task. This will cause the loss of functionality specific to the more recent version of the Control Center.
  • Save changes by creating a new task. This will not alter the original task.

DBA1180W

 No SQL available to display.

Show SQL only displays the SQL statements that change the current privileges. If no privileges have been changed, no SQL statements are generated.

Resubmit the command after making changes to the current privileges.

DBA1181W

 The catalog partition cannot be backed up at the same time as other database partitions in an offline backup.

In an offline backup, the catalog partition cannot be backed up at the same time as other database partitions. If you continue, the backup will fail.

Ensure that the catalog partition has not been grouped with other database partitions on the "Partitions" page of this wizard.

DBA1183N

 Unable to edit task task-name

The selected task was created with a more recent version of the Control Center. There is no editor associated with this type of task in this version of the Control Center.

Use a newer version of the Control Center to edit this task.

DBA1184W

 The database will immediately be taken offline and a full database backup will be performed.

As part of the execution of this wizard an offline full database backup will now be performed. This operation will remove all current users from the system and make the database unavailable for the duration of the backup.This operation may run for an extended period.

Click OK to continue or Cancel to return back to the wizard.

DBA1185W

 Automatic maintenance is enabled for this database.

This database has been configured for automatic maintenance, and is performing automatic database backups. Instead of performing a manual database backup through the Backup wizard, you may want to modify your automatic backup settings. This is performed using the Configure Automatic Maintenance wizard.

Launch the Configure Automatic Maintenance wizard to configure your automatic database backup settings or continue to manually backup using the Backup wizard.

DBA1186W

 The operation has completed sucessfully, except for the required database backup. Your database is currently in Backup Pending state.

The only valid operation for a database in Backup Pending state is to perform an offline database backup. You can perform an offline backup in the Backup wizard.

Launch the Backup wizard or press Cancel to return.

DBA1187N

 The days of the month entered are invalid.

As part of the specification for the maintenance window you have selected to have it apply only on specific days of the month. The days and day ranges entered contain invalid characters, and/or invalid ranges of days.

Enter a valid list of days and day ranges and press OK.

DBA1188E

 The maintenance settings could not be updated or retrieved.

The automatic maintenance settings are stored in tables in the database. Either the tables could not be accessed or the settings stored within the table contain invalid data.

If the problem persists, contact IBM Support.

DBA1189I

 There are unrecognized settings in the automatic maintenance settings configuration for this database.

The unrecognized settings are ignored.

No action required.

DBA1350I

 The Design Advisor was not able to recommend any indexes. Set a longer time limit on the Calculate page and try calculating recommended objects again.

The Design Advisor was not able to recommend any objects because the maximum search time was too short.
  1. On the Calculate page in the Design Advisor, set a longer time limit or no limit at all.
  2. Try running the Design Advisor again.

DBA1351I

 The Design Advisor was not able to recommend any objects. Set a larger size limit on the Limits page and try calculating recommended objects again.

The Design Advisor was not able to recommend any object because the maximum logical size of all objects was too small.
  1. On the Limits page in the Design Advisor, set a larger maximum logical size or no maximum at all.
  2. Try running the Design Advisor again.

DBA1352I

 The Design Advisor was not able to recommend any objects that will improve the performance of your workload.

DBA1353W

 You specified only one SQL statement in your workload. Your database might have additional activity. Do not drop any objects unless you are sure they are not needed for other reasons.

Since you only specified one SQL statement in your workload, it is unlikely that it represents all of the activity against your database.

The Drop page of the Design Advisor lists all existing objects that were not recommended for this one SQL statement.

Do not drop any objects unless you are sure they are not needed for other reasons.

DBA1354E

 An error occurred while compiling the SQL statements in the specified workload.

The Design advisor encountered a problem while compiling the SQL statements in the specified workload. One or more statements may contain a SQL syntax error. These statements are excluded from the advisor's analysis.

Open the Workload Details Dialog to view the statements which contain an error. From the Workload page, make the necessary corrections by editing the statement in the workload. Once corrected, select Recommendation page to start analysis.

DBA1355E

 The ADVISE and the EXPLAIN tables do not match.

The ADVISE and the EXPLAIN tables do not correspond with the current version of IBM DB2.

If the problem persists, contact IBM Support.

DBA1356E

 The Recommendation Advisor encountered a non-severe error while attempting to retrieve recommendations for alert.

An error occurred while the Recommendation advisor was retrieving information to resolve the current Health Indicator alert.

If the problem persists, contact IBM Support.

DBA1357E

 An error occurred while attemting to launch the GUI-tool

An unexpected error occurred while attempting to launch the specified tool

Attemp the launch the tool using an alternate method. If the problem persists, contact IBM Support.

DBA1358E

 The Design Advisor encountered an unexpected error. Return code = return-code.

If the problem persists, contact IBM Support.

DBA1500E

 The local system object is not allowed to be removed.

The local system object appears in the tree if this is a server installation, and does not appear if this is a client installation. You have no direct control over the removal of this object because it has special properties that are required by the server installation type.

No action is required.

DBA1501E

 The local system object is not allowed to be changed.

The local system object appears in the tree if this is a server installation, and does not appear if this is a client installation. You have no direct control over the changing of this object because it has special properties that are required by the server installation type.

No action is required.

DBA1502E

 The unknown system object is not allowed to be removed.

The unknown system object appears in the tree only if orphaned instances that are not recognized as belonging to any existing system are found. You have no direct control over the removal of this object because it is shown automatically only when needed.
No action is required. However, if you want to remove the need to show this object in the tree, then do the following steps:
  • Expand the unknown system object to show all orphaned instances.
  • If necessary, add new system objects to the control center to contain the orphaned instances.
  • If necessary, use the change action to alter the system name on any remaining orphaned instances.
  • If the unknown instance object also appears, then you also have orphaned databases that are not recognized as belonging to any existing instance Remove the need to show these objects by doing steps similar to these, adding instances or altering databases until no orphans are left to be shown.

DBA1503E

 The unknown system object is not allowed to be changed.

The unknown system object appears in the tree only if orphaned instances that are not recognized as belonging to any existing system are found. You have no direct control over the changing of this object because it is shown automatically only when needed and has only special properties that cannot be changed.

No action is required.

DBA1510E

 Specify a system name.

You must specify a system name before you can add this new system object.

Specify a system name in the appropriate entry field, and then try the action again.

DBA1511E

 The specified system name is already in use. You must specify a system name that is unique.

You specified a system name that matches the name used for another system object in the tree. System names must be unique within the control center, and are case-sensitive. You cannot use the names 'Local' or 'Unknown' because these are system names reserved for use by the local and unknown system objects. To avoid confusion, you should also try not to use the names of existing instances or databases as system names, although the tool does not prevent you from doing this.

Specify a unique system name, and then try the action again.

DBA1520W

 The operating system type for this system object has been detected to be newos, but the local information shows it to be oldos. Do you want to update the local information now to reflect the correct operating system type?

When you add a new system object, you specify an operating system type, which is stored locally for that remote system. Later, when actual connections are made to the remote system, the true operating system type is reported back. It is possible for the original operating system type information to have been set incorrectly so that it does not match the true settings on the remote system. In this case, it is best to update the local information to match what settings truly exist on the remote system.

Select Yes to update the local information now, or select No to leave the local information as it is.

DBA1521W

 The server version type for this system object has been detected to be newtyp, but the local information shows it to be oldtyp. Do you want to update the local information now to reflect the correct server version type?

When you add a new system object, the server version type is automatically set to be either DB2 V5 or DRDA, depending on the operating system type you choose. Later, when actual connections are made to the remote system, the true server version type, which may be a previous release such as DB2 V2, is reported back. In this case, it is best to update the local information to match what settings truly exist on the remote system.

Select Yes to update the local information now, or select No to leave the local information as it is.

DBA1522W

 The operating system type and server version type for this system object have been detected to be newos and newtyp respectively, but the local information shows these to be oldos and oldtyp respectively. Do you want to update the local information now to reflect the correct settings for these values?

When you add a new system object, you specify an operating system type, which is stored locally for that remote system. Also, the server version type is automatically set to be either DB2 V5 or DRDA, depending on the operating system type you choose. Later, when actual connections are made to the remote system, the true operating system type and server version type are reported back. The original settings for this information may have been incorrect so that they do not match the true settings on the remote system. In this case, it is best to update the local information to match what settings truly exist on the remote system.

Select Yes to update the local information now, or select No to leave the local information as it is.

DBA1530E

 The specified system has not been configured to support any protocols that your local system uses.

The specified system has been detected on the network, however the Administration Server for this remote system has not been configured to support any protocols that your local system uses.

You must configure communications on the remote system Administration Server, including the DB2COMM parameter, before you can successfully access it.

DBA1533E

 Unable to export the server profile.

The target file system might not have enough disk space to complete the export operation.

Free some disk space on the target file system and retry the operation. If the problem persists, contact your DB2 system administrator.

DBA1534W

 A valid mail server has not been configured.

The current value of the SMTP_SERVER DB2 Administration Server configuration parameter is not valid.

Use the Troubleshoot Health Alert Notification wizard to identify a valid mail server.

DBA1540E

 The active local instance object is not allowed to be removed.

The active local instance object appears in the tree always as the first instance under the local system object. This is a special instance object used to represent the current DB2INSTANCE environment variable setting. You have no direct control over the removal of this object because it has special properties that are required by the local system.

No action is required.

DBA1541E

 The active local instance object is not allowed to be changed.

The active local instance object appears in the tree always as the first instance under the local system object. This is a special instance object used to represent the current DB2INSTANCE environment variable setting. You have no direct control over the changing of this object because it has special properties that are required by the local system.

No action is required.

DBA1550E

 Specify an instance name.

You must specify an instance name before you can add this new instance object.

Specify an instance name in the appropriate entry field, and then try the action again.

DBA1551E

 The specified instance name is already in use. You must specify an instance name that is unique, otherwise do not specify the instance name and one will be generated for you automatically.

You specified an instance name that either matches the name used for another instance object in the tree, or is being used by a system object in the tree. Instance names must be unique within the control center, and are always capitalized. System objects also use an automatically generated instance name to store their own protocol information, with the instance name usually being a short form of the chosen system name. You cannot use the name 'LOCAL' or the current DB2INSTANCE environment variable setting for the instance name.

Specify a different instance name, and then try the action again.

DBA1552E

 Specify a remote instance.

You must specify a remote instance before you can add this new instance object.

Specify a remote instance in the appropriate entry field, and then try the action again.

DBA1560E

 Specify a destination name.

You must specify a destination name for the selected protocol before you can correctly add this new object.

Specify a destination name in the appropriate entry field, and then try the action again.

DBA1561E

 Specify a file server.

You must specify a file server for the selected protocol before you can correctly add this new object.

Specify a file server in the appropriate entry field, and then try the action again.

DBA1562E

 Specify a workstation name.

You must specify a workstation name for the selected protocol before you can correctly add this new object.

Specify a workstation name in the appropriate entry field, and then try the action again.

DBA1563E

 Specify a host name.

You must specify a host name for the selected protocol before you can correctly add this new object.

Specify a host name in the appropriate entry field, and then try the action again.

DBA1564E

 Specify a service name.

You must specify a service name for the selected protocol before you can correctly add this new object.

Specify a service name in the appropriate entry field, and then try the action again.

DBA1565E

 Specify a computer name.

You must specify a computer name for the selected protocol before you can correctly add this new object.

Specify a computer name in the appropriate entry field, and then try the action again.

DBA1566E

 Specify an instance name.

You must specify an instance name for the selected protocol before you can correctly add this new object.

Specify an instance name in the appropriate entry field, and then try the action again.

DBA1567E

 This action or function is not available for this instance type or the associated system.

The selected action, or associated function, is currently not supported for the type of instance against which the action or function was initiated. Some instance types, for example Satellite Edition, necessarily do not support full functionality.

Refer to the documentation describing available function for this instance type.

DBA1568W

 Database connection was established but did not establish a syncpoint two-phase connection.

An attempt was made to connect to a database using syncpoint two-phase connection type. A connection was established but failed to make a syncpoint two-phase connection. Multisite updates involving this database connection will not be successful.

Check that the multisite update scenario has been configured properly for your environment, ensuring that the coordinating instance is restarted after configuration is complete. If DB2's Syncpoint Manager is being used, check in the db2diag log file to see if it was started successfully.

DBA1569E

 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.

Invoke the Change Instance window and specify the name of the remote instance.

DBA1570E

 The DB2 Administration Server for this system has not been defined.

The current operation requires an attachment to the system's administration server but its instance name has not been specified.

Invoke the change action on the target system and specify its instance name, operating system and any other protocol parameters.

DBA1571W

 The name of the local system does not match the DB2SYSTEM environment variable.

The system name of the local admin node is different from the value of the DB2SYSTEM environment variable.

There are three options:

  • Change the value of the DB2SYSTEM environment variable to match the system name of the local admin node.
  • Uncatalog the local admin node and recatalog it with a system name that matches the value of the DB2SYSTEM environment variable.

DBA1572E

 The instance name instance-name specified is not valid.

The instance name specified is not valid. The instance name may be 1 to 8 characters and all of the characters must be from the database manager base character set. Also, the instance name must not match that of any other catalogued instance.

Specify a different value for the instance name.

DBA1573E

 This action is not available for the selected system.

Some Control Center actions require that an Administration Server be available on the target system. The system that you selected does not have an Administration Server. The requested action is not available for this system.

No action is required.

DBA1580E

 New database objects are not allowed to be added to the unknown instance.

The unknown instance object appears in the tree only if orphaned databases that are not recognized as belonging to any existing instance are found. The tool tries to prevent you from creating new orphans whenever possible, so you are not allowed to add new ones to the unknown instance.

No action is required.

DBA1581E

 Specify a database name.

You must specify a database name before you can add this new database object.

Specify a database name in the appropriate entry field, and then try the action again.

DBA1582E

 Specify an alias.

You must specify an alias before you can add this new database object.

Specify an alias in the appropriate entry field, and then try the action again.

DBA1583E

 The specified alias is already in use.

You specified an alias that matches the alias used for another database object in the tree. Database aliases must be unique within the control center, and are always capitalized.

Specify a unique alias, and then try the action again.

DBA1590W

 The dbase database was created using an earlier version of DB2 than DB2 V5. Only limited function will be allowed for this database until it is migrated.

All databases that are found under DB2 V5 type system objects are first assumed to be DB2 V5 databases. This database has now been detected to actually be a back-level database that has not yet been migrated to the DB2 V5 level. You can still access this database, but only limited function is available for back-level databases until you actually migrate them.

No action is required.