Each message has a message identifier that consists of a prefix (DBA) and the message number. Messages are listed in numeric sequence based upon the message number. These messages are generated by the Control Centre and the DBA Utility to alert you when a warning or error condition occurs.
Cause: An internal error occurred when allocating memory. The application is terminated.
Action: Try closing some applications to release memory. If the problem persists, contact IBM Service.
Cause: An unexpected input value was received from the request. The application is terminated.
Action: Contact IBM Service.
Cause: When processing an alter table request, an inconsistency was detected between the last known table definition and the table definition fetched from the database. The table definition might have changed outside of the context of the administration tool. The table cannot be altered. The request is terminated.
Action: Select the "Refresh" action on the "Tables" pop-up menu to get an updated list of tables from the database. Try altering the table again.
Cause: An invalid connection was detected. A problem can occur if the server is brought down, the currently held connections are no longer valid, and a new connection cannot be obtained. The request is terminated.
Action: Ensure that the server is started. Select the "Connect" action in the pop-up menu of the database that you want to connect to. Try the action again.
If the action fails again, ensure that your network is operating for the target system and that the database is up and running on that system.
If the network is operational, a system internal error might have occurred. Contact IBM Service.
Cause: An invalid connection was detected. The database might have stopped or the connection might no longer exist. The request is terminated.
Action: Ensure that the server is started. Select the "Connect" action in the pop-up menu of the database that you want to connect to. Try the action again.
If the action fails again, ensure that your network is operating for the target system and that the database is up and running on that system.
If the network is operational, a system internal error might have occurred. Contact IBM Service.
Cause: An invalid connection was detected. The database might have stopped or the connection might no longer exist. The request is terminated.
Action: Ensure that the server is started. Select the "Connect" action in the pop-up menu of the database that you want to connect to. Try the action again.
If the action fails again, ensure your network is operating for the target system and that the database is up and running on that system.
If the network is operational, a system internal error might have occurred. Contact IBM Service.
Cause: An error occurred when setting the context type for connections established by the application. The application is terminated.
Action: Contact IBM Service.
Cause: The type of object to be listed was not recognized as a valid type by the application. The application is terminated.
Action: Contact IBM Service.
Cause: The type of request to be performed was not recognized as a valid type by the application. The application is terminated.
Action: Contact IBM Service.
Cause: The type of object to be processed was not recognized as a valid type by the application. The application is terminated.
Action: Contact IBM Service.
Cause: The maximum number of open database connections was reached. The request is terminated.
Action: Either:
Cause: An error occurred when attempting to allocate a connection handle. The application is terminated.
Action: Contact IBM Service.
Cause: The maximum number of objects that can be listed by the application was reached. The maximum number is 20,000.
Action: None
Cause: The type of object to be dropped was not recognized as a valid type by the application. The application is terminated.
Action: Contact IBM Service.
Cause: A latch request failed. The application is terminated.
Action: Contact IBM Service.
Cause: An unlatch request failed. The application is terminated.
Action: Contact IBM Service.
Cause: No error information can be displayed.
Action: See the administration tools log for error information.
Cause: The Administration Server is not started.
Action: Start the Administration Server using the DB2ADMIN START command on the target system and try the action again.
Cause: The object on which the action was requested or a related object is already being used in another action. Modifications to the object or a related object might be in progress.
The requested action cannot be performed at the same time as the current action.
Examples:
The action is not performed.
Action: Try the action again at a later time when the object is available.
Cause: An error occurred opening the administration tools trace file.
Action: Contact IBM Service.
Cause: An error occurred writing to the administration tools trace file.
Action: Contact IBM Service.
Cause: An error occurred when attempting to close the administration tools trace file. Processing continues.
Action: Ensure that the administration tools log file was specified correctly.
Cause: An error occurred when attempting to open the administration tools log file. Processing continues.
Action: Ensure that the administration tools log file was specified correctly.
Cause: An error occurred when attempting to write to the administration tools log file. Processing continues.
Action: Ensure that the administration tools log file was specified correctly and can be written to.
Cause: An error occurred when attempting to close the administration tools log file. Processing continues.
Action: Ensure that the administration tools log file was specified correctly.
Cause: An unrecoverable error occurred.
Action: Contact IBM Service.
Cause: Lock contention in the administration tools was detected.
Action: Contact IBM Service.
Cause: A severe internal error occurred.
Action: Contact IBM Service.
Cause: An application programming interface call did not complete.
Action: Try the operation again or contact your system administrator.
Cause: The requested operation could not complete because it requires a connection to database "<name>". The connection was not successful.
Action: Make sure the database is accessible. Try explicitly connecting to the database using the connect action on the database pop-up menu. A common error on connection is an invalid userid and password. Make sure you have supplied the proper userid and password. Try the operation again or contact your system administrator.
Cause: The requested operation could not complete because it requires an attachment to the instance "<name>". The attachment was not successful.
Action: Make sure the instance is accessible. Try explicitly connecting to the instance using the connect action on the instance pop-up menu. A common error on connection is an invalid userid and password. Make sure you have supplied the proper userid and password. Try the operation again or contact your system administrator.
Cause: Either the dynamic link library "<name>" was not found or an error occurred while reading the file.
Action: Verify that the DLL is installed and undamaged, and its location is part of the LIBPATH parameter in the CONFIG.SYS file.
Cause: Either the object "<name>" you selected to drop, or an item that is owned by the object you selected to drop, is still being used by another administration tool. For example, you might have and ALTER table window open for a database that you are trying to drop. In this case, you cannot drop the database until you close its ALTER table window.
Action: Close all the windows using the object you selected, or close all the windows using items owned by that object, and then retry the command.
Cause: Either the object "<name>" you selected to remove, or an item that is owned by the object you selected to remove, is still being used by another administration tool. For example, you might have and ALTER table window open for a database that you are trying to remove. In this case, you cannot remove the database until you close its ALTER table window.
Action: Close all the windows using the object you selected, or close all the windows using items owned by that object, and then retry the command.
Cause: This operation "<operation>" requires "<name>" to be in a "<name>" state.
Action: Make sure all other pending operations on the selected object are complete, and then retry the command.
Cause: The database configuration was successfully updated, but the active database configuration cannot be changed until all applications are disconnected from the database. Once all applications are disconnected, the changes will come into effect with the first connection to the database.
Action: Ensure that all applications are disconnected from the database, and then reconnect to the database.
Cause: The instance configuration was successfully updated.
Changes to the configuration parameter "dftdbpath" take effect immediately.
For the remaining configuration parameters, the changes do not take effect until all applications have disconnected from the database, and the instance is successfully stopped and started again.
Action: To make all changes take effect, ensure that all applications have disconnected from the database, stop the instance, and then start it again.
You can stop the instance by selecting the stop action on the instance pop-up menu in the Control Center. You can then start the instance by selecting the start action on the instance pop-up menu in the Control Center.
Cause: The database objects in the Control Center are locked when actions, such as Alter Table, are taken against them. Other actions will maintain connections to the database that are required to complete the task.
Action: If you choose to continue with the shutdown, then all locks and connections are forced and the tools will shut down. It can be dangerous to do so, however, because forcing some actions (like Restore Database) halfway through the task can leave the database in a corrupted state.
It is safest to first go back to the DB2 tools and make sure there are no database operations outstanding.
Cause: Snapshot monitoring has been started on one or more database objects and to continue the monitoring, you must have the DB2 tools running.
Action: Choose to continue the shutdown only if you no longer require the Snapshot monitor.
Cause: Applets loaded over the network are usually considered to be untrusted. Different Web browsers and applet viewers may impose different restrictions on untrusted applets including most local system operations (For example, read files, write files, and print files).
Action: Consult your system administrator and see if these restrictions can be relaxed or customized.
Cause: If you choose to clear this setting, you will prevent unauthorized access to this database from this workstation. However, you will be prompted to enter the correct userid and password the next time you connect to this database.
Action: Click on Yes to clear the userid and password setting. Click on No to save the userid and password setting until you exit the Control Center.
Cause: The Control Center detected that the nodetype changed at the instance and is recataloging the instance based on the new information. Depending on the nodetype value for the instance, actions from the Control Center may be different.
Action: If available, try the request again.
Cause: The Nodes Contain Exceptions check box is deselected, but exception containers are specified in the List Exception dialog.
Action: Click on Yes to clear the exception containers list, or click on No or Cancel to reselect the Nodes Contain Exceptions check box.
Cause: Nodetype is a database manager configuration parameter that identifies whether the instance is a single-partition or partitioned environment.
Discovery tries to resolve the nodetype value for you. This distinction between instances is required because actions in the Control Center can be different between single-partition and partitioned environments.
If the reason code is -1, discovery could not map the catalogued instance to a valid DB2 instance.
All other reason codes map to a valid SQL message. Check the help for the corresponding SQL message.
Action: Discovery has the following requirements:
or
Verify the setting of these registry values by entering db2set -all.
Cause: Another database partition was selected, but the changes to the configuration parameters apply to the previously selected database partition.
Action: Click on Yes to obtain the configuration parameter values for the next database partition and discard the changes that were specified for the previously selected database partition.
Cause: The specified exception containers have no common container. Because no common container is specified, the exception container must be defined at every node in the nodegroup.
Action: Click on OK to add containers to the specified nodes.
Cause: The Control Center detected that the nodetype changed at the instance.
Action: Exit the Control Center and restart it.
Cause: Because the cataloged information for the instance is updated, the displayed objects and actions may not be correct.
Action: Select the "Refresh" action from the instance pop-up menu to update the Control Center, then try the request again.
Cause: The JDBC server is currently busy with an existing operation and cannot perform the user operation.
Action: Wait until the JDBC server completes the existing operation and retry the operation.
Cause: Because the amount of memory dedicated to the server is so small, the Performance Configuration SmartGuide cannot make a recommendation.
The suggested values in the "Results Page" are the same as the current values.
Action: 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 Performance Configuration SmartGuide.
Cause: Either the Performance Configuration SmartGuide 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.
Action: 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.
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.
Cause: The Performance Configuration SmartGuide 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.
Action: When you are ready to use the new configuration parameters, stop the instance, and then start the instance.
Rebind your packages if necessary.
Cause: An unexpected error occurred. The Performance Configuration SmartGuide cannot continue.
Action: Contact your system administrator.
Cause: This is a warning that there may not be enough memory dedicated to your server to run the workload that you specified.
Action: Review your selections on previous pages of the Performance Configuration SmartGuide to check that the workload description is appropriate or add more memory to your server.
Cause: The Performance Configuration SmartGuide verifies that the transactions rate is reasonable. The transaction rate may be too high if you are not using a transaction manager.
Action: 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.
Cause: There are currently no entries found in this database directory.
Action: No action is required.
Cause: 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.
Action: Specify a database name that is not being used as an alias, or request that the backup be recovered into the existing database.
Cause: You requested that a backup be recovered into an existing database, but a database no longer exists with this alias.
Action: Select an existing database, or request that the backup be recovered into a new database.
Cause: The restart operation encountered indoubt transactions. This left the database in an inconsistent state. The DBA Utility dropped the connection to the database.
Action: 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.
Cause: This state will prevent the database from being updated. The database must be backed up before any updates can happen.
Action: Back up the database.
Cause: A value is required.
Action: Provide the value and retry the request.
Cause: The value must be within the specified range.
Action: Enter a value in the specified range and retry the request.
Cause: The value entered is not valid.
Action: Correct the value and retry the request.
Cause: The value entered is not valid.
Action: Correct the value and retry the request.
Cause: The value entered is not valid.
Action: Correct the value and retry the request.
Cause: The job was successfully started.
Action: To view the status and output of the job, use the Jobs page on the Journal.
Cause: The job has completed.
Action: To view the status and output of the job, use the Jobs page on the Journal.
Cause: The job was canceled in response to a user request.
Action: No action is required.
Cause: The database has no table spaces.
Action: No action is required.
Cause: The table space has no containers.
Action: No action is required.
Cause: The current list does not contain any new containers.
Action: Select "Add" and fill in the necessary fields to add a container to the list.
Cause: The operation you requested can be performed only if you enter a value for "<name>".
Action: Enter a value, and then click on OK.
Cause: You entered a value that exceeded the maximum number of characters.
Action: Enter a valid value, and then click on OK.
Cause: 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).
Action: Enter a valid name for the tape device, and then click on OK.
Cause: The Control center uses a tape mark blocksize that is not supported by the specified tape device.
Action: Use the Command Line Processor to submit the request. Specify a supported blocksize in the DB2 INITIALIZE TAPE command.
Cause: An unexpected error occurred while operating the specified tape device.
Action: Resubmit the request. If the problem persists, contact your system administrator.
Cause: 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.
Action: To have the status and output of the job logged in the Journal, start the DAS instance first before starting a backup operation.
Cause: The job has completed.
Action: No action is required.
Cause: You can only back up a database at the table space level if you have first enabled that database for forward recovery.
Action: To enable the database for forward recovery, set the database configuration parameters LOGRETAIN or USEREXIT to ON, disconnect all existing applications from the database, and perform an offline backup of the database.
Cause: The value entered is smaller than the minimum "<minimum>" "<units>".
Action: Enter a valid value and retry the request.
Cause: The value entered exceeded the maximum of "<maximum>" of "<units>".
Action: Enter a valid value and retry the request.
Cause: 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.
Action: Enter a valid value and retry the request.
Cause: Each page of data requires 4 KB. So 1 MB of storage is equal to 256 of these 4 KB pages.
Action: Enter a valid value and retry the request.
Cause: 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.
Action: Enter a valid value and retry the request.
Cause: 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.
Action: Make a full offline database backup as soon as possible. If this is not possible, set the LOGARCHIVE parameter to OFF.
Cause: 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.
Action: 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.
Cause: Each table space container must be unique.
Action: Specify a file name or directory that does not currently exists on the system.
Cause: Each table space container must be unique.
Action: Specify a file name or directory that is not currently in your list of new containers.
Cause: Each table space container must be unique.
Action: Change the file name or directory of the container in either the user or temporary tablespace.
Cause: Each table space container must be unique.
Action: Change the file name or directory of the container in either the catalog or temporary tablespace.
Cause: Each table space container must be unique.
Action: Change the file name or directory of the container in either the user or catalog tablespace.
Cause: When a DMS container is created it consumes the full amount of space you allocated to it.
Action: 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.
Cause: The column was not added because a column with the same name is already specified or exists in the table being created or altered.
Action: Specify a different column name.
Cause: The column was not removed because it participates in a primary key or foreign key.
Action: Ensure that the specified column is the correct column to remove. To remove the specified column in a table, modify the primary key or foreign key definitions so that the specified column is no longer referenced.
Cause: The constraint was not added because a constraint with the same name is already specified or exists in the table being created or altered.
Action: Specify a different constraint name.
Cause: The specified object already exists in the list. The action is not performed.
Action: Specify another object or close the window.
Cause: The system, instance, and database specifications do not identify a database that is known to the application. The action is not performed.
Action: 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.
Cause: The specified object no longer exists in the database and cannot be operated on. The request is terminated.
Action: Select the "Refresh" action in the pop-up menu of the object folder to get an updated list of objects.
Cause: The requested action completed, but one or more warning messages were issued.
Action: See the administration tools log for more information.
Cause: The requested action completed. No action was taken against the authorities or privileges on the specified object for the specified user or group.
Action: None
Cause: The action completed with the specified results.
Action: None
Cause: The export action completed successfully with the specified results.
Action: None
Cause: The import action completed successfully with the specified results.
Action: None
Cause: The import or export completed with the specified results.
Action: None
Cause: The load action completed successfully with the specified results.
Action: None
Cause: One or more warnings or errors occurred when copying the table. The table was not copied.
Action: See the administration tools log for more information.
Cause: The copy table action failed because the target table exists.
Action: Either specify a new target table or delete the existing target table and try the action again.
Cause: Privileges were not granted or revoked for the specified user or group.
Action: See the administration tools log for more information.
Cause: The specified identifier contains unbalanced single or double quotes. The naming rules require balanced quotes. The action is not performed.
Action: Correct the identifier and try the action again.
Cause: The specified identifier contains blank characters, which violates the naming rules for ordinary identifiers. The action is not performed.
Action: Remove the blanks or delimit the identifier with double quotes and try the action again.
Cause: The first character of the specified identifier is invalid. It must follow the naming rules for ordinary identifiers. The action is not performed.
Action: Replace the first character with a valid one or delimit the identifier with double quotes then try the action again.
Cause: 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.
Action: 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.
Cause: 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.
Action: No action is required.
Cause: 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.
Action: No action is required.
Cause: 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.
Action: No action is required. However, if you want to remove the need to show this object in the tree, then do the following steps:
Cause: 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.
Action: No action is required.
Cause: You must specify a system name before you can add this new system object.
Action: Specify a system name in the appropriate entry field, and then try the action again.
Cause: 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.
Action: Specify a unique system name, and then try the action again.
Cause: 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.
Action: Select Yes to update the local information now, or select No to leave the local information as it is.
Cause: 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.
Action: Select Yes to update the local information now, or select No to leave the local information as it is.
Cause: 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.
Action: Select Yes to update the local information now, or select No to leave the local information as it is.
Cause: 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.
Action: No action is required.
Cause: 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.
Action: No action is required.
Cause: You must specify an instance name before you can add this new instance object.
Action: Specify an instance name in the appropriate entry field, and then try the action again.
Cause: 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.
Action: Specify a different instance name, and then try the action again.
Cause: You must specify a remote instance before you can add this new instance object.
Action: Specify a remote instance in the appropriate entry field, and then try the action again.
Cause: You must specify a destination name for the selected protocol before you can correctly add this new object.
Action: Specify a destination name in the appropriate entry field, and then try the action again.
Cause: You must specify a file server for the selected protocol before you can correctly add this new object.
Action: Specify a file server in the appropriate entry field, and then try the action again.
Cause: You must specify a workstation name for the selected protocol before you can correctly add this new object.
Action: Specify a workstation name in the appropriate entry field, and then try the action again.
Cause: You must specify a host name for the selected protocol before you can correctly add this new object.
Action: Specify a host name in the appropriate entry field, and then try the action again.
Cause: You must specify a service name for the selected protocol before you can correctly add this new object.
Action: Specify a service name in the appropriate entry field, and then try the action again.
Cause: You must specify a computer name for the selected protocol before you can correctly add this new object.
Action: Specify a computer name in the appropriate entry field, and then try the action again.
Cause: You must specify an instance name for the selected protocol before you can correctly add this new object.
Action: Specify an instance name in the appropriate entry field, and then try the action again.
Cause: 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.
Action: No action is required.
Cause: You must specify a database name before you can add this new database object.
Action: Specify a database name in the appropriate entry field, and then try the action again.
Cause: You must specify an alias before you can add this new database object.
Action: Specify an alias in the appropriate entry field, and then try the action again.
Cause: 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.
Action: Specify a unique alias, and then try the action again.
Cause: All databases that are found under DB2 V5 type system ojects 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.
Action: No action is required.
Cause: A description for the job is required information.
Action: Enter a job description in the entry field, and then click on OK.
Cause: The number of hours for your selection is required information.
Action: Enter a number in the hours entry field.
Cause: To schedule a recurring job, you must specify at least one day of the week for the job.
Action: Select at least one day of the week when scheduling a recurring job.
Cause: The date you specified is not valid. Perhaps the date you have specified is in the past.
Action: Enter a valid date.
Cause: The next execution date and time cannot be calculated, so no jobs can be scheduled. One possible error is when the time specified for a job to be run once is in the past. Remember that the date and time combination must be valid on the managed host where the schedule job is to be run.
Action: Enter a valid date and time combination.
Cause: A name for the script is required information.
Action: Enter a name for the script file, and then click on OK.
Cause: You indicated that you want to record a comment when the job is completed, but the comment entry field is empty.
Action: Enter a comment, or clear the 'Record a comment' check box.
Cause: The command script is saved as a file in the file system. The script path is at most 255 bytes long. The file name part of the script name can be at most 8 bytes long. If an extension is specified, it cannot be longer than 3 bytes. The script name must not contain any blanks. For example, valid script names can be: j:\script\new.cmd c:\data\test\crtdb.bat
Action: Enter a valid script name, and then click on OK.
Cause: A new job was scheduled successfully. You may turn to the journal job summary to view the newly created job.
Action: To view the newly created job, turn to the journal job summary by selecting the Journal icon from the icon bar.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: To perform any action involving the Job Scheduler or the Script Center, the Scheduler service must be up and running.
Action: Restart the Admin. Server, and then retry the command.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: You specified to remove the selected jobs. You have the chance now to double-check the jobs that you selected to remove, and either to continue or to cancel the request.
Action: Select YES to remove the selected jobs. Select NO to cancel the remove request.
Cause: You specified to remove the selected scripts that are currently saved. You have the chance now to double-check the scripts that you selected to remove, and either to continue or to cancel the request.
Action: Select YES to remove the selected scripts. Select NO to cancel the remove request.
Cause: The number of days for your selection is required information.
Action: Enter a number in the days entry field.
Cause:
Action:
Cause: You specified to have your changes not saved in the Script Center. You have the chance now either to continue discarding your changes, or to cancel the request and resume editing.
Action: Select YES to discard the changes. Select NO to resume editing the command script.
Cause: A new script was saved successfully in the Script Center. You may turn to the Script Center to view the new command script.
Action: To view the newly saved script, turn to the Script Center by selecting the Script Center icon from the icon bar.
Cause: The instance name associated with the script file does not exist.
Action: You may select "Edit" from the Script Center to update the instance name to an existing instance.
Cause: The scheduled job cannot be executed because the script file associated with the job does not exist.
Action:
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: You specified to remove the selected job. You have the chance now to double-check the job that you selected to remove, and either to continue or to cancel the request.
Action: Select YES to remove the selected job. Select NO to cancel the remove request.
Cause: You specified to remove the selected script that is currently saved. You have the chance now to double-check the script that you selected to remove, and either to continue or to cancel the request.
Action: Select YES to remove the selected script. Select NO to cancel the remove request.
Cause: The number of weeks for your selection is required information.
Action: Enter a number in the weeks entry field.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: The system name is required information to process the action.
Action: Select a system name from the drop-down list.
Cause: A job that you requested to be rescheduled was rescheduled successfully.
Action:
Cause: A name for the script is required information.
Action: Enter the script name in the entry field, and then click on OK.
Cause: The command script is empty.
Action: Enter the command script content, and then click on OK.
Cause:
Action:
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: The number of months for your selection is required information.
Action: Enter a number in the months entry field.
Cause: To schedule a recurring job, you must specify at least one date per month for the job.
Action: Select at least one date per month when scheduling a recurring job.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause:
Action:
Cause: A description for the script file is required information.
Action: Enter a description for the script file, and then click on OK.
Cause: The script associated with a backup or reorganize table action is not in readable format.
Action: Select a different command script (file?) to view the content of.
Cause: The script associated with a backup or reorganize table action is not in readable format.
Action: Select a different command script file to edit.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: The name of each script file must be unique. You specified a file name that already exists.
Action: Specify an unique script file name.
Cause: The application was unable to access the file in the file system.
Action: Retry the command. If the problem persists, contact your system administrator.
Cause: There is no more room on the disk. Processing cannot continue.
Action: Delete unwanted files from the file system. If the problem persists, contact your system administrator.
Cause: An internal error relating to the hard disk occurred. The application was unable to access a file.
Action: Retry the command. If the problem persists, contact your system administrator.
Cause: The password was invalid for the given userid or the userid is invalid.
Action: Enter a valid userid and password when prompted.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause:
Action:
Cause:
Action:
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: The maximum number of bytes in a line is exceeded.
Action: Rewrite the long line into separate lines without exceeding the limit.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: A new script file with the name "<script name>" was created successfully.
Action: To view the newly created script, turn to the Script Center by selecting the Script Center icon from the icon bar.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: An internal error occurred.
Action: Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
Cause: The name of each script file must be unique within the Script Center. You specified a file name that already exists.
Action: Specify an unique script file name.
Cause: The script file was not found in the file system. The file may have been erased.
Action: Remove the script entry and recreate it.
Cause: db2job executable should be copied to sqllib bin as part of the installation.
Action: Contact your system administrator.
Cause:
Action:
Cause: The name of the instance is required information.
Action: Enter the instance name in the entry field, and then click on OK.
Cause:
Action: Remove jobs that are no longer needed before creating another new job.
Cause:
Action: Remove scripts that are no longer needed before creating another new script.
Cause: The editor cannot handle a file as large as the current one. Data shown had to be truncated.
Action: The entire file can be viewed at the server in the indicated location.
Cause: The script file does not exist anymore.
Action:
Cause: A userid and password for running the job are required.
Action: Enter a valid userid and password for running the job, and then click on OK.
Cause: The specified working directory does not exist so it cannot be used to run the script.
Action: Use the Browse... button to select a valid working directory path.
Cause:
Action:
Cause:
Action:
Cause: File name must be unique.
Action: Specify another file name.
Cause: There is no job output from running the job.
Action: A possible error could be an invalid file extension is used on the operating system. Recreate the script with a valid extension.
Cause: The script cannot be scheduled because you canceled the save action and therefore, the script was not saved in the Script Center.
Action: Save the script and then try scheduling again.
Cause: Only scripts that are saved in the Script Center can be scheduled and run.
Action: Select OK to save the script to the Script Center, or Cancel if you do not want to schedule the script.
Cause:
Action:
Cause:
Action:
Cause: The file "<file name>" currently exists in the file system and the save operation will overwrite its contents.
Action: Select OK if you want to overwrite the contents of the file, or Cancel if you do not want to alter its contents.
Cause: The script "<script name>" currently exists in the Script Center and the save operation will overwrite its contents.
Action: Select OK if you want to overwrite the contents of the script, or Cancel if you do not want to alter its contents.
Cause:
Action:
Cause: A new file with the name "<file name>" was created successfully in the file system.
Action:
Cause: You specified to exit from the Command Center, but the changes to the current script have not yet been saved. Your changes will be lost unless you cancel your exit request.
Action: Select Yes to discard your changes and exit from the Command Center, or select No to cancel the exit request.
Action: Select Yes to discard your changes and to create a new script, or select No to cancel the request.
Cause: You tried to run a script or issue a set of commands, but the Command Center cannot process your command until it has finished processing the current one.
Action: Please wait a few moments and try the command again. To stop the current command, click on the turning gears icon on the tool bar or select "Terminate" from the Results menu on the Results page.
Cause: You specified the name of a file containing a script that you want to import, but the Command Center could not access that file.
Action: Make sure that you have entered the file name correctly on the command line, that the file exists, and that your user ID has read access to that file.
Cause: The system encountered a memory allocation problem when trying to create the Command Center window.
Action: Make sure there is enough memory on your system to run the Command Center, and then try again.
Cause: The command processor environment did not initialize properly.
Action: Make sure you have enough disk space and then try again.
Cause: Command Center has encountered a problem when trying to create an access plan.
Action: Please refer to the help from the previous messages.
Action: Establish a database connection first using the "Connect" statement, and then create an access plan for that database. To see a list of available databases, issue the command "list database directory".
Cause: The statement you used to try to create an access plan is either not in the correct format for a query or is not a query.
Action: Check your statement for errors in query format, make necessary changes, and retry the statement. Refer to Visual Explain documentation for guidance on forming valid queries.
Cause: You don't need to type "db2" before a statement in the Command Center. It is only required at the operating system command prompt.
Action: No action is required.
Cause: The JDBC server does not support multiple WEBCC Command Center sessions. The JDBC server is already busy with an existing Command Center session.
Action: Wait until the current Command Center session is finished and retry the operation.
Cause: You are about to delete the explained statement. This will delete the rows in the explain tables.
Action: Ensure that you want to delete the explained statement.
Cause: You are about to delete the explained statements. This will delete the rows in the explain tables.
Action: Ensure that you want to delete the explained statements.
Cause: An unexpected error occurred causing the operation to stop.
Action: Possible solutions include:
If the problem persists, contact your system administrator.
Cause: The explain snapshot that is requested has been deleted from the explain tables.
Action: Regenerate the snapshot.
Cause: The explain snapshot was created using a newer version or an older version of the database manager from the Visual Explain Tool. The access plan graph cannot be constructed by the Tool.
Action: Use the same version of the database manager as the Visual Explain Tool to graph the explain snapshot.
Cause: The search string is not found in the text being displayed.
Action: None.
Cause: You did not specify a search string.
Action: Specify a search string.
Cause: You did not make a selection in the list.
Action: Select at least one entry in the list.
Cause: There were no columns referenced in the query for the referenced table.
Action: None.
Cause: There are no page fetch pairs statistics stored in the catalog table for this index. Refer to the System Catalog Statistics section in the Administration Guide for more details.
Action: None.
Cause: This access plan did not require the use of any functions.
Action: None.
Cause: There are no column distribution statistics stored in the catalog table for this column. Refer to the System Catalog Statistics section in the Administration Guide for more details.
Action: None.
Cause: There were no indexes defined on the referenced table at the time of explain and there are no indexes currently defined in the table.
Action: None.
Cause: An unexpected error occurred.
Action: Contact your system administrator.
Cause: An unexpected error occurred.
Action: Contact your system administrator.
Cause: An unexpected error occurred causing the operation to stop.
Action: Contact your system administrator.
Cause: An unexpected error occurred causing the operation to stop.
Action: Contact your system administrator.
Cause: Possible problems include:
Action: Possible solutions include:
Cause: Possible problems include:
Action: Specify the correct file name.
Cause: There are no printers installed on your machine.
Action: Install a printer on your machine.
Cause: This access plan did not reference any database objects contained in a table space.
Action: None.
Cause: The snapshot of the access plan graph displayed was created on a code page different from the code page of the window running the Visual Explain Tool. Code page conversion is not successful because the snapshot is too large. The access plan graph is displayed without code page conversion. You may not be able to display the current statistics when you open the statistics windows.
Action: Change the code page of the window running the Visual Explain Tool to the same one used to create the snapshot and display the access plan graph again.
Cause: The snapshot of the access plan graph displayed was created on a code page different from the code page of the window running the Visual Explain Tool. Code page conversion is not successful because the user defined function used to convert between the code pages do not have enough memory to run. The access plan graph is displayed without code page conversion. You may not be able to display the current statistics when you open the statistics windows.
Action: Possible solutions include:
Cause: One or more explain tables have been created under the current user ID. These tables will be used to store the information needed by your dynamic explain request.
Action: None.
Cause: The explain snapshot that is requested has been corrupted in the explain tables.
Action: Regenerate the snapshot.
Cause: This access plan did not reference any database objects contained in a buffer pool.
Action: None.
Cause: Explain tables do not exist.
Action: Create explain tables using one of the following methods:
Cause: The command has invalid syntax.
Action: Issue the command with the -h option to see the correct syntax.
Cause: The specified database name is either empty or too long.
Action: Reissue the command with a valid database name.
Cause: The specified explainable statement text is either empty or too long.
Action: Reissue the command with valid explainable statement text.
Cause: The specified query tag is too long.
Action: Reissue the command with a valid query tag.
Cause: The specified userid is too long.
Action: Reissue the command with a valid userid.
Cause: The specified query number is either too small or too large.
Action: Reissue the command with a valid query number.
Cause: The specified optimization class is not one of the valid values.
Action: Reissue the command with a valid optimization class.
Cause: The database name specified in the command does not exist in the system database directory.
Action: Reissue the command with an existing database name or catalog the database in the system database directory.
The syntax is:
db2vexp -db <database name>
-sql <explainable statement text>
[-queryno <query number>]
[-querytag <query tag>]
[-opt <optimization class>]
[-user <user ID>]
[-password <password>]
[-withsnapshot]
Use -h option to get help information.
Cause: This is the syntax of the db2vexp command.
Action: None.
Cause: The details information of the selected operator is not available for the current release of the DB2 Administration Tools.
Action: None.
Cause: The help information of the selected operator is not available for the current release of the DB2 Administration Tools.
Action: None.
Cause: You have requested to stop monitoring all database objects that are currently monitored and to exit the Snapshot Monitor.
Action: Click on "Yes" to process the request or "No" to ignore it.
Cause: This occurs when:
If the number of performance variables to be displayed in this view exceeds the limit, some performance variables are ignored and are not shown in the view.
Action: If a performance variable that you have selected for viewing is not in the view, use the "Include performance variables" action to remove a performance variable already displayed and select the desired performance variable.
Cause: The Snapshot Monitor has paused the collection of snapshots due to the unexpected error returned by the database manager that is being monitored. This usually occurs when the database manager is stopped or communication with the database manager is interrupted.
Action: Determine the cause of the error from the referenced message.
If you do not wish to continue monitoring, select the "Stop all monitoring" choice from the "Snapshot monitor" menu on any of the Snapshot Monitor windows for the database manager in question.
If you wish to continue monitoring, first correct the error and then select the "Resume monitoring" choice from the "Snapshot monitor" menu on any of the Snapshot Monitor windows for the database manager in question.
Cause: An unexpected error occurred while using Presentation Manager services.
Action: Write down the error identifier returned by Presentation Manager and contact support.
Cause: The database system monitor returned data that is not recognized by the Snapshot Monitor. This can occur due to network problems or internal problems with the database manager system.
Action: Try your action again, and if the error persists please contact support.
Cause: The IBM-supplied performance variable profile is not found in the installation directory.
Action: Either reinstall the Snapshot Monitor, or specify a new performance variable profile to be used. To specify a new profile use the "Open as settings" action from the "Snapshot monitor" menu in any of the views.
Cause: The Snapshot Monitor encountered problems while writing to the specified performance variable profile.
Action: Examine file permissions for the file or the directory where the file resides, and make sure that they allow writing to the file.
Cause: Some of the performance variable definitions in the specified profile are invalid and are not recognized by the Snapshot Monitor.
Action: Examine the errors listed in the error file, fix them, and retry the operation.
Cause: The value entered for the capture interval cannot be used by the Snapshot Monitor, because it does not fall into the specified range.
Action: Type a valid value.
Cause: The performance database has been dropped or uncataloged since the last time the Snapshot Monitor was used.
Action:
Do one of the following actions:
Cause: The performance variable profile last used with the Snapshot Monitor was either deleted or moved to a different location.
Action: Specify a new profile name. Use the "Open as settings" action from the "Snapshot monitor" menu in any view to display the Settings window, and type the profile name in the "Performance variable profile" field.
Cause: You have entered a number that is outside this range.
Action: Enter a value that falls within the range.
Cause: You have selected to copy the IBM-supplied performance variable profile. However, a profile with the identical name already exists in that directory.
Action: Select "OK" to copy the file and to overwrite the existing one, or "Cancel" to ignore the request.
Cause: Upper warning values must always be less than upper alarm values. Lower warning values must always be greater than lower alarm values. Upper warning values must always be greater than lower warning values.
Action: Re-enter your values, and make sure they meet the above conditions.
Cause: At least one of the performance variable definition or global definitions ( such as sampling interval ) of the currently active profile has been changed.
Action: Select "Yes" to save the changes or "No" to discard the changes.
Cause: The performance variable profile selected to be used is not valid or is corrupted due to a system error.
Action: Contact your system administrator.
Cause: The performance variable profile name entered already exists in the file system.
Action: Click on "Yes" to overwrite the existing file, or "No" to cancel the operation.
Cause: A valid data is required in the entry field in order to complete the operation.
Action: Enter a valid data in the corresponding entry field.
Cause: You have specified an invalid DB2 version 2 performance variable profile for migration.
Action: Make sure that the file selected contains a DB2 Version 2 performance variable profile. If the problem persists, contact your system administrator.
Cause: The performance variable ID used already exists in the currently active profile.
Action: Click on "Yes" to overwrite the existing performance variable, or "No to cancel the operation.
Cause: "IBM" can not be used as a creator name for a user-defined performance variable.
Action: Use a different creator name.
Cause: Upper warning values must always be less than upper alarm values. Lower warning values must always be greater than lower alarm values. Upper warning values must always be greater than lower warning values. If the start script checkbox is on, you must provide a script file name in the entry field. If the show message checkbox is on, you must provide a message in the multiline edit field.
Action: Re-enter your values, and make sure they meet the above conditions.
Cause: The performance variable equation is invalid. The error can be caused by the use of invalid performance data elements or variables, syntax errors in the equation, or by not using a 7-bit ASCII character set alphabet.
Action: Refer to the online help for the correct syntax of a performance variable equation and correct the error.
Cause: Depending on the operating system, the profile changes will not be saved if the profile is still in used by the performance monitor.
Action: Stop all monitoring activities and restart to use the profile changes.
Cause: Different source and target profile names are required for the selected operation.
Action: Enter different profile names in the source and target entry fields.
Cause: "db2smpv" is the IBM default performance variable profile and cannot be used as the target profile.
Action: Enter a different profile name in the target entry field.
Cause: The active performance variable profile cannot be used as the target profile in any operation.
Action: Enter a different profile name in the target entry field.
Cause: The disk is full.
Action: Free up some disk space and retry the operation.
Cause: The IBM supplied performance variable ID cannot be used.
Action: Enter a different performance variable ID and retry the operation.
Cause: The performance graph will not work with a scale value of zero.
Action: Enter a valid scale value.
Cause: Full database restore cannot be done from a table space backup image.
Action: None.
Cause: Table space selection is not allowed for the media type.
Action: None.
Cause: Table space selection is not allowed since the database is in backup pending state.
Action: None.
Cause: Full database required when backup image information is entered manually.
Action: None.
Cause: An ATTACH command to the database manager that manages the performance database failed, or the database manager is not cataloged.
No alerts will be recorded. The Snapshot Monitor setting to write alerts has been disabled.
Action: Make sure the database manager that manages the performance database is started and/or cataloged. To re-enable the writing of alerts to the performance database, use the "Open as settings" action from the "Snapshot monitor" menu in any view to display the Settings window. Then select the "Write alerts in performance database" check box.
Cause: The performance database specified in the Snapshot Monitor Settings window does not exist in the system database directory.
No alerts will be recorded. The Snapshot Monitor setting for writing alerts has been disabled.
Action: Specify a new performance database. Use the "Open as settings" action from the "Snapshot monitor" menu in any view to display the Settings window, select the "Write alerts in performance database" check box, and specify the new performance database name.
Cause: The table SSMON_ALERT in the performance database does not have the definition expected by the Snapshot Monitor.
No alerts will be recorded. The Snapshot Monitor setting for writing alerts has been disabled.
Action: Drop the table SSMON_ALERT. Use the "Open as settings" action from the "Snapshot monitor" menu in any view to access the Settings window, select the "Write alerts in performance database" check box. The SSMON_ALERT table will be created for you by the Snapshot Monitor.
Cause: The table SSMON_ALERT was created in the performance database by the Snapshot Monitor, as specified in the Snapshot Monitor Settings window. For details on the format of the SSMON_ALERT table, see the file CALRTTBL.DDL in the samples directory.
Action:
Cause: An unexpected error occurred.
No alerts will be recorded. The Snapshot Monitor setting for writing alerts has been disabled.
Action: Contact your system administrator.
Cause: An unexpected error occurred.
No alerts will be recorded. The Snapshot Monitor setting for writing alerts has been disabled.
Action: Contact your system administrator.
Cause: The table SSMON_ALERT does not exist in the performance database. It may have been deleted.
No alerts will be recorded. The Snapshot Monitor setting for writing alerts has been disabled.
Action: To re-enable the writing of alerts to the performance database, use the "Open as settings" action from the "Snapshot monitor" menu in any view to display the Settings window. Then select the "Write alerts in performance database" check box. The SSMON_ALERT table will be created for you by the Snapshot Monitor.
Cause: You have defined an upper threshold for the specified performance variable, and it was exceeded.
Action: Examine the definition of the performance variable. If the threshold value is not valid, change it to avoid further alerting.
If this is an IBM-supplied performance variable, use the "Performance variable" action from the "Help" menu to display the online help, and examine the description of the performance variable and suggested actions when an alert is generated.
Otherwise, you may want to contact your system administrator for further explanation and investigation.
Cause: You have defined a lower threshold for the specified performance variable, and the performance variable fell below it.
Action: Examine the definition of the performance variable. If the threshold value is not valid, change it to avoid further alerting.
If this is an IBM-supplied performance variable, use the "Performance variable" action from the "Help" menu to display the online help, and examine the description of the performance variable and suggested actions when an alert is generated.
Otherwise, you may want to contact your system administrator for further explanation and investigation.
Cause: The "Cancel" push button in the Logon Window was pressed while working with the performance database. No alerts will be recorded. The Snapshot Monitor setting for writing alerts has been disabled.
Action: To re-enable the writing of alerts to the performance database, use the "Open as settings" action from the "Snapshot monitor" menu in any view to display the Settings window. Then select the "Write alerts in performance database" check box.
Cause: See the server error logs for more information.
Action: Contact your technical service representative with the smcode.
Cause: See the server error logs for more information.
Action: Free up some server resource and retry the operation. If the problem persists, contact your technical service representative with the smcode.
Cause: See the server error logs for more information.
Action: Retry the operation. If the problem persists, contact your technical service representative with the smcode.
Cause: See the server error logs for more information.
Action: Restart the instance. If the problem persists, contact your technical service representative with the smcode.
Cause: See the server error logs for more information.
Action: Retry the operation. If the problem persists, contact your technical service representative with the smcode.
Cause: See the server error logs for more information.
Action: Contact your technical service representative with the smcode.
Cause: The client's country code and code page must be sent to the server so that the data is returned in the correct code page. The snapshot monitor subsystem was unable to determine the active country code or code page.
Action: Refer to your operating system documentation to determine how to set the country code and active code page for your system. Retry the operation after setting the country code and code page.
Cause: The client's country code and code page must be sent to the server so that the data is returned in the correct code page. The snapshot monitor subsystem was unable to set the client's active country code or code page on the server.
Action: Refer to your operating system documentation to determine how to activate the client's country code and active code page on your server's system. Retry the operation after activating the country code and code page.
Cause: The listed Administration Server on system "<name>" is not started.
Action: Start the Administration Server and retry the operation.
Cause: This is a client system setup problem.
Action: Contact IBM Service.
Cause: The listed codepage has not been installed on instance "<name>".
Action: Contact your system administrator. Your administrator should install codepage "<name>" on instance "<name>".
Cause: The listed codepage has not been installed on instance "<name>", at node "<name>".
Action: Contact your system administrator. Your administrator should install codepage "<name>" on instance "<name>" at node "<name>".
Cause: Possible reasons for this problem include: 1) Remote instance name is invalid. 2)Hostname is invalid.
Action: Contact your system administrator.
Cause: The Administration Server "<name>" had an internal error.
Action: Contact your system administrator.
Cause: Communications may not have been started.
Action: Contact your system administrator.
Cause: The /etc/services file at node "<name>" might contain incorrect information.
Action: Contact your system administrator. Your administrator should check that the port name of db2ccmsrv is entered correctly in the /etc/services file on node "<name>".
Cause: The db2nodes.cfg file for instance "<name>" might contain incorrect information.
Action: Contact your system administrator. Your administrator should validate the host name found in the db2nodes.cfg file for instance "<name>".
Cause: A performance or communications problem on the listed node is preventing a response from being sent, or the snapshot capture interval is not long enough to allow each node time to respond to the request.
Action: Contact your system administrator. Your administrator can 1) Validate the performance on the listed node. 2) Increase the snapshot capture interval to allow more time for the node to respond to the snapshot request.
Cause: The db2nodes.cfg file for instance "<name>" might contain incorrect information.
Action: Contact your system administrator.
Cause: The communications subsystem may not have been started.
Action: Contact your system administrator.
Cause: The Event Analyzer only handles traces produced by FILE Event Monitors.
Action: Use a FILE Event Monitor.
Cause: The Event Monitor names specified with the -evm option could not be found in the catalogs for the database specified with the -db option. The Event Monitor may have been dropped or you may be trying to connect to the wrong database.
Action: Make sure that the Database alias specified with the -db is properly cataloged and that the Event Monitor has not been dropped. If the latter is the case, re-create the event monitor.
Cause: The window height required to display the retrieved objects exceeds a system limit.
Action: You can reduce the number of objects displayed in the window by doing the following:
Usage:
db2eva -path evmon-target [-conn [
-db database-alias]] |
-evm evmon-name -db database-alias [-conn]
Cause:
The command parameters for the db2eva command are:
Window Manager Options can be intermixed with the db2eva arguments.
Two modes of operation are provided for reading Event Monitor trace files:
This mode allow users to move trace files from a server and analyze them locally, even if the Event Monitor has been dropped.
When this mode is used, db2eva connects to the database, and issues a 'select target from sysibm.syseventmonitors' to locate the directory where the Event Monitor writes its trace files. The connection is then released, unless -conn is specified. The Event Monitor must not have been dropped when using this mode.
NOTE: Both the -conn and -db options require that the database with which the trace was recorded still exists, and that the user has sufficient access privileges to connect and select from the system catalogs.
Action: Re-issue the command with valid arguments.
Cause: The specified file could not be opened in read-only mode for an unknown cause.
Action: Check the spelling of the directory specified by the -path option, its access authority, and that it contains a non-empty, readable trace file called 00000000.evt.
NOTE: The first trace file for an Event Monitor is always named 00000000.evt and cannot be renamed.
Cause: There is no 00000000.evt file in the directory specified by -path.
Action: Check the spelling of the directory specified by the -path option, its access authority, and that it contains the trace file 00000000.evt.
NOTE: The first trace file for an Event Monitor is always named 00000000.evt and cannot be renamed.
Cause: The -path option specifies a directory that does not exist.
Action: Check the spelling of the directory specified by the -path option, its access authority, and that it contains the trace file 00000000.evt.
NOTE: The first trace file for an Event Monitor is always named 00000000.evt and cannot be renamed.
Cause: The specified file could not be opened in read-only mode. The -path option may be specifying a directory to which you do not have sufficient access authority.
Action:
Cause: The Event Monitor trace file contains unexpected data, or cannot be accessed.
The trace file was likely corrupted during transmission or has been removed.
Action: Transmit your trace files from your server again. When transmitting trace files from a remote server, ensure that the transmission is done in binary mode.
Cause: The first file written to by an Event Monitor is named 00000000.evt and contains a data structure that identifies the trace characteristics. This data structure could not be read. Possible causes:
Action:
Cause: The Event Monitor log header (the first record written to a new trace) specifies whether the trace contains little-endian (e.g., OS/2) or big-endian (e.g., AIX) data. The value found in the trace file specified neither of these two supported types of data.
The trace file was likely corrupted during transmission.
Action: Transmit your trace files from your server again. When transmitting trace files from a remote server, ensure that the transmission is done in binary mode.
Cause: The Event Monitor trace file contains unexpected data.
The trace file was likely corrupted during transmission.
Action: Retransmit your trace files from the server, ensuring that the transmission is done in binary mode.
Cause: For an unknown reason a system error has occurred when trying to initialize the application environment.
Action: Re-issue the command.
Cause:
Action: To delete the event files for the selected event monitor, click on OK. If you do not want to delete the event files, but still want the event monitor removed, click on NO. If you do not want to remove the event monitor, or delete the event files click on CANCEL.
Cause: When creating an event monitor, at least one Event type must be selected.
Action: Select one or more of the Event type check boxes from the Create Event Monitor window.
Cause: The event monitor has been successfully created and has been added to the database list of event monitors.
Action: Click on OK to remove the message.
Cause: Some of the selected event monitors may have been successfully removed, but others were not, because their associated event trace files could not be deleted.
This occurs when either event files are read-only, or they are being used by another active process.
Action: See the message page of the journal notebook for the list of event monitors that were not removed. To delete the files, end the process using them and check the access authority for the files. Then select the event monitor from the list of event monitors and choose remove from the menu.
Cause: If maximum file size in 4K pages is selected on the create event monitor Options window, then the maximum size of the event files must be specified.
Action: Enter a maximum file size of between 1 and 2,147,483,647 4K pages, or you can select the No Maximum option. If the No Maximum option is selected, the maximum number of event files is 1.
Cause: If Maximum number of files is selected on the create event monitor Options window, then the maximum number of event files must be specified.
Action: Enter a maximum number of event files of between 1 and 2,147,483,647, or you can select No Maximum option.
Cause: An event monitor Buffer size in 4K pages must be specified.
Action: You must enter an event monitor buffer size of between 1 and 2,147,483,647 4K pages.
Action: To delete the event files for the selected event monitors, click on OK. If you do not want to delete the event files, but still want the event monitors removed, click on NO. If you do not want to remove the selected event monitors, or delete the event files click on CANCEL.
Cause: The name entered in the event monitor Name field contains one or more characters that are not allowed. An event monitor can contain alphanumerics and must begin with a letter.
Action: Remove from the name any characters that are not alphanumeric and make sure the name begins with a letter.
Cause: When activating an event monitor, the directory that was specified when the event monitor was created must exist. In order to flush its buffers, an event monitor needs an existing file and path.
Action: Create the directory that was specified when creating the event monitor. Try to activate the event monitor again.
Cause: The values for an event monitor's Maximum file size, Maximum number of files, and Buffer size must be between 1 and 2,147,483,647.
Action: Enter a value in the entry fields that is within the given range.
Cause: A character entered in the event monitor name entry field is not a valid character for an event monitor name.
Action: Remove from the event monitor name any characters that are not alphanumeric and make sure the name begins with a letter.
Cause: During the initialization of the event analyzer the dll could not be loaded because the dll has been deleted or removed.
Action: Reinstall the event analyzer by selecting the performance monitor during the installation process.
Cause: The event files for the event monitor could not be deleted because the files are being used by an active process or are read-only.
Action: To delete the files, end the process that is using them and check the access authority for the files. Select the event monitor again and choose remove from the menu.
Cause: The alias name that was entered on the command line has not been cataloged on this machine.
Action: Either catalog the alias on this machine and reenter the command or re-issue the command with a valid alias name.
Cause: The user has requested to view a large trace for an event monitor. Reading the files could take some time to complete.
Action: If you want to continue processing the trace click on OK. If you do not wish to continue processing the trace file then click on NO.
Cause: The event monitor could not be started for the reason specified by "<reason-code>":
Action: To start the event monitor, make sure that the event monitor path is valid, the admin server started, and the proper authorities exist on the device. Click on OK.
If the problem persists, manually create the event monitor directory on the device and click on OK.
To create the event monitor without starting it, deselect the Start now check box and click on OK.
Cause: The directory could not be created for one of the following reasons.
Action: Make sure the proper authorities exist for directory creation.
On non-Intel platforms create the event monitor output directory manually.
Cause: 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.
Action: No action is required.
Cause: The Capture program requires a defined replication source in order to run.
Action: Make sure the Capture program is running.
Cause: The Apply program requires a defined replication source in order to run.
Action: Make sure the Apply program is running.
Cause: This is for your information only.
Action: No action is required.
Cause: This is for your information only.
Action: No action is required.
Cause: This is for your information only.
Action: No action is required.
Cause: This is for your information only.
Action: No action is required.
Cause: This is for your information only.
Action: No action is required.
Cause: The file is currently being used by another action.
Action: Wait until the action is completed and retry your command.
Cause: This message is for your information only.
Action: No action is required.
Cause: The Capture program requires a defined replication source in order to run.
Action: Make sure the Capture program is running.
Cause: This message is for your information only.
Action: No action is required.
Cause: This message is for your information only.
Action: No action is required.
Cause: This message is for your information only.
Action: No action is required.
Cause: This message is for your information only.
Action: No action is required.
Cause: This message is for your information only.
Action: No action is required.
Cause: The control table specified could not be located in the database or was accidently dropped.
Action: Create the control table. See the Tables Chapter for more details.
Cause: This message is for your information only.
Action: No action is required.
Cause: 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.
Action: Correct the error in the SQL statement file and run the file again.
Cause: A prefix character is an alphabetical or numerical character used to distinguish before-image columns in the source table. If a prefix character connot be assigned because all possible prefix characters are already in use, you will receive this warning. The change data table cannot be created.
Action: Uncheck the before-image columns and rerun the action.
Cause: The user has not filled in a required field.
Action: Specify a parameter and select OK.
Cause: The replication action must support your database system in order to run.
Action: Contact your IBM Service representative.
Cause: When cloning a replication subscription, the target server and Apply qualifier fields must be different from the original target server and Apply qualifier fields.
Action: Enter a different target server name or Apply qualifier and select OK.
Cause: The SQL statement contains a syntax error.
Action: 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.
Cause: The SHOW COLUMNS action requires that a table be selected.
Action: Select a table from the Selected Table list box and then press the SHOW COLUMNS key.
Cause: The SQL file either does not exist, is in the wrong subdirectory, or is engaged in another process.
Action: 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.
Cause: The file either does not exist or is in the wrong subdirectory.
Action: Make sure you enter the correct file name on the Replication page of the Tool Settings notebook.
Cause: This message is for your information only.
Action: No action is required if you have already supplied user-defined values in the file.
Cause: The specified keyword is invalid and may be a typographical error.
Action: Use the keywords as given in the default file "DPREPL.DFT".
Cause: The value of this keyword is required for this action to complete.
Action: Specify a value for this keyword in the file.
Cause: At least one item in the column list must be selected for this action to complete.
Action: Select one or more items from the column list and press OK.
Cause: The value of this keyword is either too long, an incorrect data type, or in an incorrect format.
Action: Correct the value and invoke the action again. *------------------------------------------------------------------------
Cause: 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.
Action: Uncheck the before-image column when the truncated name is not unique and rerun the action.
Cause: 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.
Action: No action is necessary if the converted datatypes are acceptable. If they are not acceptable, uncheck the target columns and rerun the action.
Cause: 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.
Action: Contact IBM service if you would like to recommend a specific datatype be supported on the named database in the future.
Cause: 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.
Action: Specify a primary key for the target table in the Target Columns page of the Advanced notebook.