DBA2000-2999

DBA Message ID	Message	Explanation	User Response
DBA2000E	You have not specified a job description.	A description for the job is required information.	Enter a job description in the entry field, and then click on OK.
DBA2001E	You have not specified the number of hours for your selection.	The number of hours for your selection is required information.	Enter a number in the hours entry field.
DBA2002E	You must select at least 1 day of the week for your selection.	To schedule a recurring job, you must specify at least one day of the week for the job.	Select at least one day of the week when scheduling a recurring job.
DBA2003E	You specified a date that is not valid.	The date you specified is not valid. Perhaps the date you have specified is in the past.	Enter a valid date.
DBA2004E	You specified a date or time or combination of date and time that is not valid.	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.	Enter a valid date and time combination.
DBA2005E	You have not specified a script name.	A name for the script is required information.	Enter a name for the script file, and then click on OK.
DBA2006E	You have not specified a comment.	You indicated that you want to record a comment when the job is completed, but the comment entry field is empty.	Enter a comment, or clear the 'Record a comment' check box.
DBA2007E	You specified a script name that is not valid.	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	Enter a valid script name, and then click on OK.
DBA2008I	Job `job-id` was created successfully.	A new job was scheduled successfully. You may turn to the journal job summary to view the newly created job.	To view the newly created job, turn to the journal job summary by selecting the Journal icon from the icon bar.
DBA2009E	A system error occurred. A Scheduler InfoBase call was unsuccessful. RC = `return-code`. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2010E	The Scheduler service is not up and running. Restart the Admin. Server, and then retry the command.	To perform any action involving the Job Scheduler or the Script Center, the Scheduler service must be up and running.	Restart the Admin. Server, and then retry the command.
DBA2011E	A system error occurred. Scheduling type (DBA or PGM) is not valid. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2012E	A system error occurred. OS error was detected. RC = `return-code`. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2013E	The job id was not found. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2014E	A system error occurred. Unable to change the status of the job. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2015E	A system error occurred. Memory allocation was unsuccessful in client. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2016E	A system error occurred. Scan handle is not valid. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2017I	Are you sure you want to remove the selected jobs?	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.	Select YES to remove the selected jobs. Select NO to cancel the remove request.
DBA2018I	Are you sure you want to remove the selected saved scripts?	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.	Select YES to remove the selected scripts. Select NO to cancel the remove request.
DBA2019E	You have not specified the number of days for your selection.	The number of days for your selection is required information.	Enter a number in the days entry field.
DBA2020E	A system error occurred. Unable to determine script type. Command script was not executed.
DBA2021I	Are you sure you want to discard your changes?	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.	Select YES to discard the changes. Select NO to resume editing the command script.
DBA2022I	Command script `script-id` was created successfully.	A new script was saved successfully in the Script Center. You may turn to the Script Center to view the new command script.	To view the newly saved script, turn to the Script Center by selecting the Script Center icon from the icon bar.
DBA2023E	Instance `instance-name` does not exist. Command script was not executed.	The instance name associated with the script file does not exist.	You may select "Edit" from the Script Center to update the instance name to an existing instance.
DBA2024E	Command script `script-id` does not exist.	The scheduled job cannot be executed because the script file associated with the job does not exist.
DBA2025E	A system error occurred. This problem may also be related to memory allocation on the client. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2026I	Are you sure you want to remove the selected job?	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.	Select YES to remove the selected job. Select NO to cancel the remove request.
DBA2027I	Are you sure you want to remove the selected saved script?	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.	Select YES to remove the selected script. Select NO to cancel the remove request.
DBA2028E	You have not specified the number of weeks for your selection.	The number of weeks for your selection is required information.	Enter a number in the weeks entry field.
DBA2029E	A system error occurred. Scheduler key was not found. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2030E	You did not specify a system name. Select one from the list.	The system name is required information to process the action.	Select a system name from the drop-down list.
DBA2031I	Job `job-id` was rescheduled successfully.	A job that you requested to be rescheduled was rescheduled successfully.
DBA2032E	You have not specified a script name.	A name for the script is required information.	Enter the script name in the entry field, and then click on OK.
DBA2033E	You have not entered the command script.	The command script is empty.	Enter the command script content, and then click on OK.
DBA2034I	Command script `script-id` was updated successfully.
DBA2035E	A system error occurred. Unable to retrieve the command script `script-id`. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2036E	A system error occurred. Unable to create the command script. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2037E	A system error occurred. Unable to replace the command script `script-id`. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2038E	A system error occurred. Unable to copy the command script `script-id`. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2039E	You have not specified the number of months for your selection.	The number of months for your selection is required information.	Enter a number in the months entry field.
DBA2040E	You must select at least 1 day of the month for your selection.	To schedule a recurring job, you must specify at least one date per month for the job.	Select at least one date per month when scheduling a recurring job.
DBA2041E	A system error occurred. Unable to remove the command script `script-id`. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2042E	A system error occurred. Unable to run the command script `script-id`. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2043I	Job `job-id` was created successfully for running command script `script-id`.
DBA2044E	You have not specified a script description.	A description for the script file is required information.	Enter a description for the script file, and then click on OK.
DBA2046E	Command script `script-id` is system-generated. Content cannot be edited.	The script associated with a backup or reorganize table action is not in readable format.	Select a different command script file to edit.
DBA2047E	A system error occurred. The script type is unknown. Restart the Admin. Server., and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2048E	The file name you specified already exists. Specify a different script file name.	The name of each script file must be unique. You specified a file name that already exists.	Specify an unique script file name.
DBA2049E	A system error occurred. File access was denied.	The application was unable to access the file in the file system.	Retry the command. If the problem persists, contact your system administrator.
DBA2050E	A system error occurred. The disk is full.	There is no more room on the disk. Processing cannot continue.	Delete unwanted files from the file system. If the problem persists, contact your system administrator.
DBA2051E	A system error occurred. A hard disk error occurred.	An internal error relating to the hard disk occurred. The application was unable to access a file.	Retry the command. If the problem persists, contact your system administrator.
DBA2052E	Unable to execute the job due to logon failure. Userid = `user-id`.	The password was invalid for the given userid or the userid is invalid.	Enter a valid userid and password when prompted.
DBA2053E	A system error occurred. Unable to remove job history entry.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2054E	A system error occurred. Unable to run job `job-id`.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2055E	Command script `script-id` has been removed from the Script Center.
DBA2056I	Command script `script-id` was not changed.
DBA2057E	A system error has occurred. The path was not valid.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2058E	A line in the file is greater than `number` bytes.	The maximum number of bytes in a line is exceeded.	Rewrite the long line into separate lines without exceeding the limit.
DBA2059E	A system error occurred. There was a sharing violation.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2060E	A system error occurred. Unable to copy script `script-id`.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2061I	Script `script-name` was created successfully.	A new script file with the name `script name` was created successfully.	To view the newly created script, turn to the Script Center by selecting the Script Center icon from the icon bar.
DBA2062E	A system error occurred. Unable to create a new script. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2063E	A system error occurred. Unable to retrieve the results of job `job-id`. Restart the Admin. Server, and then retry the command.	An internal error occurred.	Restart the Admin. Server, and then retry the command. If the problem persists, contact your system administrator.
DBA2064E	A Script Center record already exists for this script file name. Specify a different script file name.	The name of each script file must be unique within the Script Center. You specified a file name that already exists.	Specify an unique script file name.
DBA2065E	A system error occurred. The script file does not exist in the file system.	The script file was not found in the file system. The file may have been erased.	Remove the script entry and recreate it.
DBA2067I	The REORG TABLE command completed successfully.
DBA2068E	You have not entered the instance name.	The name of the instance is required information.	Enter the instance name in the entry field, and then click on OK.
DBA2069W	The maximum number of `number` jobs has been created. Please remove obsolete jobs.		Remove jobs that are no longer needed before creating another new job.
DBA2070W	The maximum number of `number` scripts has been created. Please remove obsolete scripts.		Remove scripts that are no longer needed before creating another new script.
DBA2071W	The maximum number of `number` bytes has been reached. Data shown is truncated. The complete file `file-name` can be found at the server.	The editor cannot handle a file as large as the current one. Data shown had to be truncated.	The entire file can be viewed at the server in the indicated location.
DBA2072E	The script associated with job `job-id` has been removed from the Script Center.	The script file does not exist anymore.
DBA2073E	You have not specified a userid and password.	A userid and password for running the job are required.	Enter a valid userid and password for running the job, and then click on OK.
DBA2074E	A system error occurred. The working directory path was not valid.	The specified working directory does not exist so it cannot be used to run the script.	Use the Browse... button to select a valid working directory path.
DBA2075I	Job `job-id` has been submitted. Use the Jobs page on the Journal to view the results.
DBA2076E	The job terminated abnormally.
DBA2077E	File name `file-name` already exists in the file system.	File name must be unique.	Specify another file name.
DBA2078E	An unexpected error occurred. There is no job output.	There is no job output from running the job.	A possible error could be an invalid file extension is used on the operating system. Recreate the script with a valid extension.
DBA2081W	The file `file-name` exceeds the maximum number of bytes (`maximum-bytes`) for the Script Center. You must use an external editor to view or edit the file.	The file is larger than the maximum size that the Script Center can display.	Use an external editor to view or edit the file.
DBA2082W	The file permissions for the script do not allow Script Center to read the script with the current user ID.	The file permissions for the script do not allow Script Center to read the script with the current user ID.	Ensure that you have set appropriate file permissions for the script.
DBA2083I	You are about to edit a dialog based task and in doing so will remove the ability to edit it with its dialog. Do you wish to continue?	The task you are about to edit was created by a DBA Tools dialog or a Wizard. It is recommended to use the 'Edit with dialog' action on this task instead of editing it manually. If you choose to edit this task manually, you will lose the ability to 'Edit with dialog' in the future. Other capabilities may also be lost, such as detailed 'Show Progress'.	Select 'No' to keep the task in a dialog based task format. Select 'Yes' to convert the task to a simple task and continue editing it manually.
DBA2151E	The script cannot be scheduled because it was not saved.	The script cannot be scheduled because you canceled the save action and therefore, the script was not saved in the Script Center.	Save the script and then try scheduling again.
DBA2152I	The script has to be saved to the Script Center before it can be scheduled.	Only scripts that are saved in the Script Center can be scheduled and run.	Select OK to save the script to the Script Center, or Cancel if you do not want to schedule the script.
DBA2153I	File `file-name` was opened successfully.
DBA2154I	Script `script-name` was opened successfully.
DBA2155I	Do you want to overwrite file `file-name`?	The file `file name` currently exists in the file system and the save operation will overwrite its contents.	Select OK if you want to overwrite the contents of the file, or Cancel if you do not want to alter its contents.
DBA2156I	Do you want to overwrite script `script-name`?	The script `script name` currently exists in the Script Center and the save operation will overwrite its contents.	Select OK if you want to overwrite the contents of the script, or Cancel if you do not want to alter its contents.
DBA2157I	File `file-name` was updated successfully.
DBA2158I	File `file-name` was created successfully.	A new file with the name `file name` was created successfully in the file system.
DBA2160I	The script has to be saved to the Task Center before it can be scheduled.	Only scripts that are saved in the Task Center can be scheduled and run.	Select OK to save the script to the Task Center, or Cancel if you do not want to schedule the script.
DBA2161I	Do you want to overwrite script `script-name`?	The script `script name` currently exists in the Task Center and the save operation will overwrite its contents.	Select OK if you want to overwrite the contents of the script, or Cancel if you do not want to alter its contents.
DBA2171I	Do you want to discard all your changes to the script, and exit from the Command Center?	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.	Select Yes to discard your changes and exit from the Command Center, or select No to cancel the exit request.
DBA2172I	Do you want to discard your changes to the current script, and create a new script?		Select Yes to discard your changes and to create a new script, or select No to cancel the request.
DBA2173I	The Command Center is still processing a command. Try again later.	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.	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.
DBA2174E	The file `file-name` specified on the command line could not be opened. Make sure that the file exists and that you have read access to the file, and then try again.	You specified the name of a file containing a script that you want to import, but the Command Center could not access that file.	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.
DBA2175E	There is not enough memory to create the Command Center window. The application cannot continue.	The system encountered a memory allocation problem when trying to create the Command Center window.	Make sure there is enough memory on your system to run the Command Center, and then try again.
DBA2176E	The system environment did not initialize. The application cannot continue. Restart the database manager and try again, or contact your local support personnel.	The command processor environment did not initialize properly.	Make sure you have enough disk space and then try again.
DBA2177E	The system could not create an access plan because a problem relating to Visual Explain has occurred.	Command Center has encountered a problem when trying to create an access plan.	Please refer to the help from the previous messages.
DBA2178E	You need a database connection in order to create an access plan. Use the "Connect" statement to connect to a database, and then try the command again.		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".
DBA2179E	An access plan cannot be created because the statement you used is not in the correct format or is not a query.	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.	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.
DBA2180I	The program name "db2" before the statement will be ignored because it is not required.	You don't need to type "db2" before a statement in the Command Center. It is only required at the operating system command prompt.	No action is required.
DBA2181I	The Command Center is not available at this time. Retry this operation later.	The JDBC server does not support multiple WEBCC Command Center sessions. The JDBC server is already busy with an existing Command Center session.	Wait until the current Command Center session is finished and retry the operation.
DBA2182N	A script name following the pattern `script-name-pattern` cannot be saved because the Script Center already contains too many scripts with names that follow the same pattern. Remove old scripts that follow this pattern from the Script Center then invoke the `tool-name` again.	There are too many automatically generated scripts with names like `script_name_pattern`.	In the Script Center, remove at least one script with a name like `script_name_pattern`, then invoke the `tool_name` again.
DBA2192E	Database connection failed.	A JDBC connection to the database failed. SQL Assist requires a JDBC connection to function.
DBA2193W	`window-name` cannot run without `program-name`. Ensure that the Database Tools subcomponent is installed.	To invoke `window-name`, the `program-name` application must be installed on the server. By default, the Database Tools subcomponent of the Administration and Configuration Tools component is selected during installation. The Database Tools subcomponent must be selected during installation in order for the `program-name` application to be installed.	Ensure the Database Tools subcomponent is installed. If Database Tools was not selected during the installation of the database server, you will need to run DB2 Setup again. 1 Stop all DB2 services. 2 Run DB2 Setup. 3 Select Custom install. 4 Uncheck all components except Administration and Configuration Tools. 5 In the details for Administration and Configuration Tools, select Database Tools. 6 Complete the install. 7 Restart all DB2 services. 8 Use the `window-name`.
DBA2194E	The XQuery Assist component could not be opened.	The XQuery Assist component is part of the IBM Data Studio, which might not be properly installed.	Reinstall IBM Data Studio.