![]() |
![]() |
This chapter describes the messages issued by Tivoli Data Protection for WebSphere Application Server. The messages begin with the prefix DKP and are listed in numerical order.
DKP0000E | Profile not specified. |
Explanation: Tivoli Data Protection for WebSphere Application Server cannot locate the profile.
User Response: Ensure that a profile is available. Note that the call must have the following form: tdpws -p initWAS.utl ...
DKP0004E | Function not defined. |
Explanation: You passed an invalid argument to Tivoli Data Protection for WebSphere Application Server.
User Response: Valid functions are: -f backup, -f restore, -f delete, and -f inquire.
DKP0005I | Start of program at: time |
Explanation: The program has been started.
User Response: None.
DKP0020I | End of program at: time |
Explanation: The program has finished.
User Response: None.
DKP0021I | Elapsed time: elapsedtime |
Explanation: The time needed for the complete backup was elapsedtime.
User Response: None.
DKP0023I | Time: current_time
Done: saved_bytes (percent) of bytes Estimated end time: end_time |
Explanation: Tivoli Data Protection for WebSphere Application Server finished saving a specific object at current_time. The saved_bytes amount of the total number of bytes have been saved. percent shows the percentage. This Tivoli Data Protection for WebSphere Application Server call will be completed at the estimated end_time.
User Response: None.
DKP0024I | Return code is: return code |
Explanation: Shows the return code of Tivoli Data Protection for WebSphere Application Server. A return code of 0 means no errors or warnings occurred. If the return code is 1, at least one warning was issued by the program. If the return code is 2, at least one error message was issued.
User Response: For return codes other than 0, check the run log for warnings or error messages.
DKP0027I | Time: current_time
Objects: current_num of total_num in process: file_name MGMNT-CLASS: management_class TSM Server: server name. |
Explanation: Tivoli Data Protection for WebSphere Application Server started saving current_num files at current_time. The total number of files to save is total_num. The file file_name is currently being processed. The files are transferred to the Tivoli Storage Manager server server name, which stores them in the Management Class management_class.
User Response: None.
DKP0030I | Time: current_time
Objects: current_num of total_num in process: file_name Size: bytes MB TSM Server: server name. |
Explanation: Tivoli Data Protection for WebSphere Application Server completed saving current_num files at current_time. The total number of files to save is total_num. The file file_name is currently being processed. The Tivoli Storage Manager server server name is selected.
User Response: None.
DKP0031W | Object not found or not accessible: objectname. |
Explanation: The object was not found or is not accessible to Tivoli Data Protection for WebSphere Application Server.
User Response: Check path and name and the permissions of that object and try again.
DKP0032E | Error opening file file name: system error description |
Explanation: A system error occurred during opening of the file file name. system error description will describe the error in more detail.
User Response: Read the system error description.
DKP0033E | Error opening file file name: system error description |
Explanation: See DKP0032E.
User Response: See DKP0032E.
DKP0049I | Please enter password for node nodename on server server name |
Explanation: The password for the node nodename on the Tivoli Storage Manager server server name has to be entered for storing it in the Tivoli Data Protection for WebSphere Application Server configuration file.
User Response: Enter the password for the corresponding Tivoli Storage Manager server.
DKP0050I | Please enter password for node nodename on server server name again |
Explanation: In order to avoid typing errors, you have to enter the password twice.
User Response: Enter the password again.
DKP0051I | Password successfully verified for node nodename on server server name. |
Explanation: The password for the node nodename on the Tivoli Storage Manager server server name was changed successfully.
User Response: None.
DKP0052E | Password verification for node nodename on server server name failed. |
Explanation: The password you entered for the node nodename on the Tivoli Storage Manager server server name was wrong.
User Response: Enter the password again. If this error still exists, contact your Tivoli Storage Manager administrator.
DKP0053I | Time: current_time
Objects: current_num of total_num done: file_name with: bytes saved with description object_desc. |
Explanation: Tivoli Data Protection for WebSphere Application Server completed saving current_num file at current_time. The total number of files to be saved is total_num. The file file_name with the size bytes is saved with the description object_desc.
User Response: None.
DKP0054I | Time: current_time
Objects: current_num of total_num done: file_name with: bytes restored with description object_desc. |
Explanation: Tivoli Data Protection for WebSphere Application Server completed restoring of current_num file at current_time. The total number of files to be restored is total_num. The file file_name with the size bytes is restored with the description object_class.
User Response: None.
DKP0055I | Object objectname with size saved with description description. |
Explanation: The object objectname was saved successfully.
User Response: None.
DKP0056I | Object objectname with size restored with description description. |
Explanation: The object objectname was restored successfully.
User Response: None.
DKP0059E | You have to set the environment variable DSMI_CONFIG to the full filename of the Tivoli Storage Manager client option file 'dsm.opt'. |
Explanation: Tivoli Storage Manager client option file not found.
User Response: Verify that the Tivoli Storage Manager option file dsm.opt is pointed to by DSMI_CONFIG.
DKP0060E | The parameter parameter is not known. |
Explanation: The command parameter parameter for Tivoli Data Protection for WebSphere Application Server is unknown.
User Response: Check the specified command parameter and try again.
DKP0061W | The output file file name is not valid. |
Explanation: The specified output file file name could not be created.
User Response: Check that file name is a valid file name on your operating system. Also check that the application has the appropriate permissions to create the file within the specified directory. The directory must already exist. If the file already exists, rename the old one.
DKP0062E | The input file file name is not valid. |
Explanation: Tivoli Data Protection for WebSphere Application Server is not able to read the input file file name correctly.
User Response: Check the path and name of the output file and the appropriate file access permission.
DKP0063E | The UTL file file name is not valid. |
Explanation: Tivoli Data Protection for WebSphere Application Server is not able to read the input file file name correctly.
User Response: Check the path and name of the output file and the appropriate file access permission.
DKP0064E | The option 'option' is unknown. |
Explanation: A Tivoli Data Protection for WebSphere Application Server option is invalid or unknown.
User Response: Check the specified option(s) and try again.
DKP0065E | The argument is missing for option 'option'. |
Explanation: Every Tivoli Data Protection for WebSphere Application Server option requires an argument.
User Response: Insert the missing argument and try again.
DKP0101I | Session session: Please enter 'cont' to continue or 'stop' to cancel. |
Explanation: If Tivoli Data Protection for WebSphere Application Server is running in unattended mode (profile keyword BATCH), it terminates the current run if operator intervention is required.
User Response: Enter 'cont' or 'stop'.
DKP0102I | Your reply: 'reply'. |
Explanation: Tivoli Data Protection for WebSphere Application Server indicates the reply you made.
User Response: None.
DKP0451I | This version of Tivoli Data Protection for WebSphere Application Server will expire on 'date'. |
Explanation: This is a test version that will expire on 'date'.
User Response: None.
DKP0452E | This version of Tivoli Data Protection for WebSphere Application Server has expired. |
Explanation: This is a test version that has expired.
User Response: Order a release version of Tivoli Data Protection for WebSphere Application Server or contact your IBM/Tivoli Sales Representative.
DKP0453W | This version of Tivoli Data Protection for WebSphere Application Server will expire in 'number' days. |
Explanation: This is a test version with a time limit. It will expire in 'number' days.
User Response: Order a release version of Tivoli Data Protection for WebSphere Application Server or contact your IBM/Tivoli Sales Representative before the version expires.
DKP0454I | *** This copy is NOT FOR RESALE. *** |
Explanation: This version is not for resale.
User Response: None.
DKP0455E | License file 'file name' does not exist. |
Explanation: The license file 'agent.lic' was not found where expected.
User Response: Make sure that the 'agent.lic' file resides in the same directory as the initWAS.utl file.
DKP0456E | Unable to access license file 'file name'. |
Explanation: Unable to access license file.
User Response: Make sure the access permissions allow read/write access.
DKP0457E | License file file name contains invalid data/checksum. |
Explanation: The license file is invalid.
User Response: Make sure you have the right agent.lic file for the right platform installed. 'agent.lic' files are platform dependent.
DKP1000E | Syntax error in line line: 'statement' |
Explanation: The statement statement in the Tivoli Data Protection for WebSphere Application Server profile is unknown or incorrect.
User Response: Correct the error and try again.
DKP1001E | Syntax error in file 'file name'. Exiting Program. |
Explanation: Tivoli Data Protection for WebSphere Application Server has detected an syntax error in the file file name and stops any action.
User Response: Correct the error(s) in the file file name and try again.
DKP1002E | BACKUPIDPREFIX must be number_of_characters characters. |
Explanation: The length of BACKUPIDPREFIX must be number_of_characters characters.
User Response: Enter a BACKUPIDPREFIX with the required length (e.g., TDP_WS).
DKP1004W | You should specify the BACKUPIDPREFIX before the TRACEFILE statement, so that the BACKUPIDPREFIX can be used in the tracefile name. |
Explanation: The BACKUPIDPREFIX is used to build the Name of the tracefile. Therefore, BACKUPIDPREFIX must be specified before the TRACEFILE statement.
User Response: Define a 6-character BACKUPIDPREFIX in the Tivoli Data Protection for WebSphere Application Server profile (e.g., TDP_WS).
DKP1005W | The tracefile name 'trace_filename' should be absolute. |
Explanation: None.
User Response: Specify an absolute tracefile name, for example /tmp/tdpws_tracefile.
DKP1006E | The SERVERNAME must be less than max_char characters. |
Explanation: You have used a SERVERNAME with more than max_char characters.
User Response: Use a shorter SERVERNAME.
DKP1007E | The NODENAME must be less than max_char characters. |
Explanation: You have used a NODENAME with more than max_char characters.
User Response: Use a shorter NODENAME.
DKP1008E | The MANAGEMENTCLASSNAME must be less than max_char characters. |
Explanation: You have used a MANAGEMENTCLASSNAME with more than max_char characters.
User Response: Use a shorter MANAGEMENTCLASSNAME.
DKP1009W | Please set MULTIPLEX to a number between 1 and max_multiplex. Now it is set to act_multiplex. |
Explanation: You have set multiplexing to an unsupported number. Tivoli Data Protection for WebSphere Application Server now uses act_multiplex.
User Response: Set multiplexing to a number between 1 and max_multiplex.
DKP1010W | The configfile name 'configuration_filename' should be absolute. |
Explanation: None.
User Response: Specify an absolute file name, for example /usr/tivoli/tsm/tdpwas/initWAS.bki
DKP1012E | The configfilename 'configuration_filename' could not be opened. |
Explanation: Tivoli Data Protection for WebSphere Application Server is unable to read the file configuration_filename.
User Response: This error could have various reasons, try the following:
DKP1013E | Profile not found or permissions denied : 'profile_filename'. |
Explanation: Tivoli Data Protection for WebSphere Application Server is unable to open the profile profile_filename.
User Response: Ensure that the profile initWAS.utl is readable by Tivoli Data Protection for WebSphere Application Server.
DKP1016W | The trace file name 'file name' could not be opened for writing! |
Explanation: The trace file could not be opened for writing.
User Response: Ensure that you have specified a correct path for the trace file.
DKP1017E | The server 'server name' is already defined. Please use another name! |
Explanation: The server you want to configure is already defined.
User Response: Specify another server name. Server names have to be unique.
DKP1200E | Can't read/write file: file name. |
Explanation: Tivoli Data Protection for WebSphere Application Server is unable to read or write a data file (file name) of a tablespace being backed up or restored.
User Response: Check the file access permission of the affected file(s). Try again.
DKP1201E | There are no Tivoli Storage Manager Servers available. |
Explanation: Tivoli Data Protection for WebSphere Application Server cannot locate a Tivoli Storage Manager server.
User Response: Install and specify at least one Tivoli Storage Manager server in the Tivoli Data Protection for WebSphere Application Server profile (keyword SERVER).
DKP1203E | Not enough sessions available (number of sessions required and number of sessions available). |
Explanation: The sum of available sessions specified in the server statement (parameter SESSIONS) does not cover the required number of sessions (parameter MAX_SESSIONS).
User Response: Change the values of the corresponding parameters in the Tivoli Data Protection for WebSphere Application Server profile, so that the condition mentioned in the explanation is fulfilled.
DKP1208E | The object 'file name' will be retried [retry_num] |
Explanation: There was an error with the object file_name. Tivoli Data Protection for WebSphere Application Server will try to save/restore the object one retry_num times.
User Response: Look at the error messages in the Tivoli Data Protection for WebSphere Application Server protocol and solve the error for the next run.
DKP1209E | Object not found or not accessible 'objectname'. |
Explanation: Tivoli Data Protection for WebSphere Application Server cannot locate the object objectname.
User Response: Check the file permissions for objectname and try again. If the problem persists, contact Tivoli Data Protection for WebSphere Application Server support.
DKP1211E | There is something wrong with your CONFIG_FILE 'file name'. |
Explanation: There is a problem with your Tivoli Data Protection for WebSphere Application Server configuration file setup.
User Response: Check the file permission and the file name specified in the Tivoli Data Protection for WebSphere Application Server profile keyword CONFIG_FILE.
DKP1213I | Program ended with code = 'return code' |
Explanation: The return code of the program is displayed.
User Response: None.
DKP1214E | TSM Error: 'error text' |
Explanation: The specified TSM error occurred.
User Response: Check error text and correct the problem.
DKP1215I | Average transmission rate was 'number' GB/h ('number' MB/sec). |
Explanation: The average transmission rate is displayed.
User Response: None.
DKP1216E | There are no backup management classes available. |
Explanation: The backup management classes you have specified in your initWAS.utl file are not correct.
User Response: Check the management classes on the TSM server and specify correct ones.
DKP1217E | There are no archive management classes available. |
Explanation: The archive management classes you have specified in your initWAS.utl file are not correct.
User Response: Check the management classes on the TSM server and specify correct ones.
DKP2000I | Successfully connected to PROLE on port portnumber. |
Explanation: One of the Tivoli Data Protection for WebSphere Application Server modules initiated a successful connection to the background process Prole on port portnumber.
User Response: None.
DKP2001E | Socket error while connecting to PROLE: reason. |
Explanation: The Tivoli Data Protection for WebSphere Application Server background process Prole is not running or is listening on the wrong port.
User Response: Check if the background process Prole on the local or remote system is running and listening on port port number. The name of the system can be taken from the message preceding this one. It will be one of the following: DKP8000I, DKP8003I, DKP8006I or DKP8008I.
DKP2002E | No valid callback function of type func_type supplied. |
Explanation: Internal Tivoli Data Protection for WebSphere Application Server error
User Response: Contact Tivoli Data Protection for WebSphere Application Server support.
DKP2003I | File file_name, BID deleted. |
Explanation: The file file_name with the backup ID BID was deleted from the Tivoli Storage Manager.
User Response: None.
DKP2004E | Connection to PROLE lost. |
Explanation: During Tivoli Data Protection for WebSphere Application Server operation the connection to Prole was lost. Network problems could be the reason.
User Response: Check your network environment and if Prole is still running and try again.
DKP2005E | Illegal parameter in message from Prole. Exiting... |
Explanation: This error occurs if the versions of Prole and the other Tivoli Data Protection for WebSphere Application Server modules do not match.
User Response: Check the version of Prole and all modules you are currently using.
DKP2006E | General exception in dispatcher. Exiting... |
Explanation: Internal Tivoli Data Protection for WebSphere Application Server error.
User Response: Contact Tivoli Data Protection for WebSphere Application Server support.
DKP2007E | Unknown Port: port |
Explanation: The port specified for communication with the background process Prole is unknown.
User Response: Check the port value specified when Prole was started.
DKP2008E | Unable to connect to PROLE. |
Explanation: Internal Tivoli Data Protection for WebSphere Application Server error.
User Response: Contact Tivoli Data Protection for WebSphere Application Server support.
DKP2009I | Deleting all versions with version Number <= version_number. |
Explanation: All full database backups and their corresponding redo log backups will be deleted from Tivoli Storage Manager storage, if their version number is less than or equal to version_number.
User Response: None.
DKP2010E | Error occurred processing FRONTEND |
Explanation: An error occurred during the frontend processing.
User Response: Check the frontend script/program and the settings in the Tivoli Data Protection for WebSphere Application Server profile (keyword FRONTEND) and try again.
DKP2011E | Error occurred processing BACKEND. |
Explanation: An error occurred during the backend processing.
User Response: Check the backend script/program and the settings in the Tivoli Data Protection for WebSphere Application Server profile (keyword BACKEND) and try again.
DKP2012E | Passwords do not match. Try again. |
Explanation: The first and second password you entered do not match.
User Response: Enter the password correctly.
DKP2013I | Starting FRONTEND Program. |
Explanation: The frontend program is executing.
User Response: None.
DKP2014I | FRONTEND program finished. |
Explanation: The frontend program is finished.
User Response: None.
DKP2015I | Starting BACKEND program. |
Explanation: The backend program is executing.
User Response: None.
DKP2016I | BACKEND program finished. |
Explanation: The backend program is finished.
User Response: None.
DKP2017I | Blocksize is set to num_bytes bytes. |
Explanation: The operational blocksize of Tivoli Data Protection for WebSphere Application Server is num_bytes bytes.
User Response: None.
DKP2018E | Exception in main message loop: 'description' |
Explanation: An error occurred during processing. The error may contain a descriptive text.
User Response: Contact your service representative.
DKP2019E | Socket error while connecting to Prole on port 'number' for tracing: 'description' |
Explanation: During processing, a socket error occurred on port 'number'. 'description' may contain the system error text.
User Response: Check the 'description'. If the error persists, contact your service representative.
DKP2020E | Error occurred for trace connection to Prole on port 'number'. |
Explanation: The network connection that is used for tracing generated an error on port 'number'.
User Response: Contact your service representative.
DKP2021E | Unable to delete file 'file name': 'description' |
Explanation: Unable to delete the file 'file name'. 'description' may contain the system error text.
User Response: Check the 'description'. If the error persists, contact your service representative.
DKP2022E | Unable to change mode of file 'file name': 'description' |
Explanation: Unable to change mode of file 'file name'. 'description' may contain the system error text.
User Response: Check the 'description'. If the error persists, contact your service representative.
DKP2023E | Error occurred during trace connection to Prole. Tracing will stop now. |
Explanation: Error occurred during trace connection to Prole.
User Response: Tracing will stop. If the problem persists, contact your service representative.
DKP4000W | The attributes of file 'file name' cannot be restored. Reason: errno (error_num) error_desc. |
Explanation: The file file name was restored successfully but one or more file attributes (permission, ownership, date/time) of the file file name cannot be restored correctly.
User Response: Check the error number error_num and the error description error_desc to avoid this problem in the future. An initial solution could be to set the appropriate correct permission for the file file name manually.
DKP4001E | File 'file name' cannot be created. Reason: errno (error_num) error_desc. |
Explanation: The file file name to be restored could not be created/written. It is possible, that you do not have the appropriate rights for writing the file file name to the destination path.
User Response: Check the error number error_num and the error description error_desc to avoid this problem in the future. Furthermore, check the write permission of the user who started the restore.
DKP4002E | Error during restore of file 'file name'. Reason: errno (error_num) error_desc. |
Explanation: An error occurs during the restore process of the file file name.
User Response: Check the error number error_num and the error description error_desc to avoid this problem in the future.
DKP4003E | Error reading file file name. Only read num_bytes out of all_bytes. |
Explanation: An error occurs reading the file file name. Only num_bytes of all_bytes could be read.
User Response: Try your last action again. If the error still exists, contact Tivoli Data Protection for WebSphere Application Server support.
DKP4004E | Error writing file filename. Only wrote num_bytes out of all_bytes. |
Explanation: An error occurs writing the file file name. Only num_bytes of all_bytes could be written.
User Response: Try your last action again. If the error still exists, contact Tivoli Data Protection for WebSphere Application Server support.
DKP4005E | Error allocating memory block for file file name. BLOCKSIZE may be too large. |
Explanation: Tivoli Data Protection for WebSphere Application Server was not able to request new memory blocks during the backup of file file name.
User Response: Verify that you have set a valid value for BLOCKSIZE. If you are not sure what value is valid, comment it out so the default value is used. Furthermore, you can check if you have enough RAM available with your machine. Also, check the memory usage during backup. It may be necessary to stop another application, increase memory, or change the configuration of Tivoli Data Protection for WebSphere Application Server.
DKP4006E | Error allocating memory block for file file name. BLOCKSIZE may be too large. |
Explanation: See DKP4005E.
User Response: See DKP4005E.
DKP5000E | Tivoli Storage Manager Error: error_message |
Explanation: During a connection of Tivoli Data Protection for WebSphere Application Server to Tivoli Storage Manager server, a Tivoli Storage Manager error error_message occurred.
User Response: Use the Tivoli Storage Manager Messages guide and correct the Tivoli Storage Manager server error. Try your last action again.
DKP5001E | Tivoli Storage Manager Error: error_message |
Explanation: See DKP5000E.
User Response: See DKP5000E.
DKP5002E | Tivoli Storage Manager Error: error_message |
Explanation: See DKP5000E.
User Response: See DKP5000E.
DKP5003E | Tivoli Storage Manager Error: error_message |
Explanation: See DKP5000E.
User Response: See DKP5000E.
DKP5004E | Tivoli Storage Manager Error: error_message |
Explanation: See DKP5000E.
User Response: See DKP5000E.
DKP5005E | Tivoli Storage Manager Error: error_message |
Explanation: See DKP5000E.
User Response: See DKP5000E.
DKP5006E | Tivoli Storage Manager Error: error_message |
Explanation: See DKP5000E.
User Response: See DKP5000E.
DKP5007E | Tivoli Storage Manager Error: error_message |
Explanation: See DKP5000E.
User Response: See DKP5000E.
DKP5008E | Tivoli Storage Manager Error: error_message |
Explanation: See DKP5000E.
User Response: See DKP5000E.
DKP5009E | Tivoli Storage Manager Error: error_message |
Explanation: See DKP5000E.
User Response: See DKP5000E.
DKP5010E | Tivoli Storage Manager Error: error_message |
Explanation: See DKP5000E.
User Response: See DKP5000E.
DKP5011E | Tivoli Storage Manager Error: error_message |
Explanation: See DKP5000E.
User Response: See DKP5000E.
DKP7009E | Cannot connect to media manager. |
Explanation: Tivoli Data Protection for WebSphere Application Server is not able to connect to the Tivoli Storage Manager server.
User Response: Check the Tivoli Storage Manager API environment variables DSMI_DIR and DSMI_CONFIG.
DKP7010E | Permission denied. |
Explanation: The permission for a connection to the Tivoli Storage Manager server are not valid.
User Response: Check your Tivoli Storage Manager client (API client) permission. For further information contact your Tivoli Storage Manager administrator.
DKP8000I | Host "hostname": start backup of database "database name". |
Explanation: Tivoli Data Protection for WebSphere Application Server is now performing a backup of the database database name on the host hostname.
User Response: Watch for the corresponding message DKP8002I.
DKP8001E | Error: error message |
Explanation: An error in one of the subcomponents has been encountered. error message has been issued by the corresponding subsystem, which should describe the problem or reason of the error in more detail.
User Response: Correct the problem and try again.
DKP8002I | Host "hostname": backup of database database name with ID backup ID successfully finished. |
Explanation: The backup of the database database name on host hostname has completed successfully.
User Response: None.
DKP8003I | Host "hostname": start backup. |
Explanation: The backup of files specific to WebSphere Application Server has been started on host hostname.
User Response: Watch for the corresponding message DKP8004I.
DKP8004I | Host "hostname": backup with ID backup ID successfully finished. |
Explanation: The backup of the files specific to WebSphere Application Server on host hostname has completed successfully.
User Response: None.
DKP8005I | Now restoring number files for backup with ID backup ID. |
Explanation: Tivoli Data Protection for WebSphere Application Server will restore number files on the local host.
User Response: None.
DKP8006I | Host "hostname": start restore of database "database name". |
Explanation: Tivoli Data Protection for WebSphere Application Server is performing a restore of the database database name on host hostname.
User Response: Watch for the corresponding message DKP8007I.
DKP8007I | Host "hostname": database "database name" successfully restored. |
Explanation: The restore of the database database name on host hostname has completed successfully.
User Response: None.
DKP8008I | Host "hostname": start restore. |
Explanation: The restore of files specific to WebSphere Application Server has been started on host hostname.
User Response: Watch for the corresponding message DKP8009I.
DKP8009I | Host "hostname": successfully restored. |
Explanation: The restore of files specific to WebSphere Application Server has completed successfully.
User Response: None.
DKP8010I | Preparing to delete all files for backup ID backup ID. |
Explanation: All files loaded under backup ID backup ID will now be deleted.
User Response: None.
DKP8011I | Querying for files for backup with ID backup ID. |
Explanation: Tivoli Data Protection for WebSphere Application Server is querying the Tivoli Storage Manager server for all files that belong to the backup ID backup ID. This may take some time.
User Response: None.
DKP8012I | Host "hostname": BID backup ID successfully deleted. |
Explanation: The backup ID backup ID has been successfully deleted on the Tivoli Storage Manager server.
User Response: None.
DKP8013I | Administrative database was backed up offline. Other hosts will be skipped. |
Explanation: If all WebSphere Application Servers of the current administrative domain are stopped, the administrative database will be backed up in offline mode. In this case, the other nodes of this domain cannot be determined and are not backed up.
User Response: Such a backup can only be used to restore the administrative database and nothing else.
DKP8015I | Examining configuration. |
Explanation: Tivoli Data Protection for WebSphere Application Server is determining the hosts of the WebSphere administrative domain and the objects on each host to back up. This may take some time.
User Response: None.
DKP8016I | Please enter the backup ID to restore and press ENTER: |
Explanation: When you invoke Tivoli Data Protection for WebSphere Application Server with the option '-f restore', you will be prompted for the backup ID to restore. See message DKP8018I.
User Response: Enter the ID of the backup you want to restore and press the ENTER key.
DKP8017I | Please enter the backup IDs to delete and press ENTER twice: |
Explanation: When you invoke Tivoli Data Protection for WebSphere Application Server with the option '-delete', you are prompted to enter the backup IDs to delete.
User Response: Enter the backup IDs to delete. Press ENTER after each backup ID. Press ENTER twice to terminate the list.
DKP8018I | Found number backup IDs: |
Explanation: Tivoli Data Protection for WebSphere Application Server prints how many and which backup IDs are currently stored on the TSM server.
User Response: None.
DKP8904I | User exit started on start_date_and_time. |
Explanation: Log File Manager processing started on start_date_and_time.
User Response: None.
DKP8905I | User exit completed on end_date_and_time. |
Explanation: Log File Manager processing ended on end_date_and_time.
User Response: None.
DKP8906I | User exit completed with return code return_code. |
Explanation: Log File Manager processing completed with return code return_code.
User Response: If the return code is not 0, this indicates that the Log File Manager could not complete the request successfully. In this case, check the log for error messages and respond to them. If the reason for a bad return code cannot be determined, save the log and contact your service representative.
DKP8907W | WARNING: The installed message catalog has an incompatible version [version.release.modification_level.level]. The default English messages will be used instead. |
Explanation: A message catalog is installed, but its version is not compatible with the version of the Log File Manager. Possible reason: The message catalog was installed with an earlier version of Tivoli Data Protection for WebSphere Application Server. The Log File Manager will use the default English messages instead of the installed message catalog.
User Response: Install the current version of the message catalog.
DKP8908W | WARNING: The message catalog could not be opened. The default English messages will be used instead. |
Explanation: The Log File Manager was not able to open the message catalog. Most probably, a message catalog was not installed in the path. Refer to the Tivoli Data Protection for WebSphere Application Server documentation for assistance on how to install the message catalog.
User Response: Install the current version of the message catalog.
DKP8910E | Invalid option option detected in call of executable. |
Explanation: The Log File Manager was called with an invalid option.
User Response: If the Log File Manager was called by DB2, save the log and call your service representative.
DKP8911E | Value for option option missing in call of executable. |
Explanation: The Log File Manager was called with an option whose value was not specified.
User Response: If the Log File Manager was called by DB2, save the log and call your service representative.
DKP8912E | Invalid option value value detected in call of executable. |
Explanation: The Log File Manager was called with an invalid option value.
User Response: If the Log File Manager was called by DB2, save the log and call your service representative.
DKP8913E | Option(s) option_list missing in call of executable. |
Explanation: Required options are missing in a call of the Log File Manager.
User Response: If the Log File Manager was called by DB2, save the log and call your service representative.
DKP8920E | Error opening file file for mode mode: error_information. |
Explanation: A file could not be opened by the Log File Manager in the mode requested.
User Response: Check the error information given in the message and respond accordingly.
DKP8921E | Error writing to file file: error_information. |
Explanation: The Log File Manager could not write to a file.
User Response: Check the error information given in the message and respond accordingly.
DKP8922E | Error renaming file source_filename to new name target_filename: error_information. |
Explanation: The Log File Manager could not rename a file.
User Response: Check the error information given in the message and respond accordingly.
DKP8923E | Error closing file file: error_information. |
Explanation: The Log File Manager could not close a file.
User Response: Check the error information given in the message and respond accordingly.
DKP8924E | No access_mode access for path path_name: error_information. |
Explanation: The required access is not granted for path path. Processing has been stopped.
User Response: Check the error information given in the message and respond accordingly.
DKP8925W | File file was not found. Nothing to be done. |
Explanation: The Log File Manager was called with a request for file file, but the file cannot be located. If this was an archive request, an earlier request might not have returned to DB2 in time, so that DB2 retried the action. If the earlier request succeeded in the meantime, DB2 might have renamed the redo log file. If this was a retrieve request the end of logs was probably reached.
User Response: None.
DKP8929E | Error setting up environment variable variable: error_information. |
Explanation: An environment variable could not be set.
User Response: Check the error information given in the message and respond accordingly.
DKP8930E | Syntax error in file file, line line_number: too many tokens. |
Explanation: Too many tokens were encountered while parsing file file at line line_number.
User Response: Correct the file syntax.
DKP8931E | Syntax error in file file, line line_number: unknown parameter keyword. |
Explanation: An unknown keyword was encountered in file file.
User Response: Correct the file syntax.
DKP8932E | Syntax error in file file, line line_number: no value found for parameter keyword. |
Explanation: A parameter value is missing in file file.
User Response: Correct the file syntax.
DKP8933E | No section found for database database_name, node node_number in profile file. |
Explanation: The profile for the Log File Manager does not contain a section for the DB2 node issuing an archive or retrieve request. There is no configuration information available for this request. Processing has been stopped, and the request cannot be satisfied.
User Response: Include a section of configuration information for the database node indicated in the message in the Log File Manager profile. The section must start with the keywords
LOG_DB_NAME database_name LOG_DB_NODE node_number
DKP8934W | Warning: Syntax error in file file, line line_number: parameter keyword value ignored. |
Explanation: The keyword in the indicated line of profile file was ignored. Possible reasons:
User Response: Correct file contents if necessary.
DKP8935E | Syntax error in file file, line line_number: invalid parameter value value for parameter keyword. |
Explanation: The profile file contains an invalid parameter value for keyword.
User Response: Correct file contents.
DKP8936E | Inconsistent information found in output of executable: data. |
Explanation: An executable was called. When analyzing its output, inconsistent information was encountered.
User Response: Save the log and contact your service representative.
DKP8937E | Required parameter keyword missing in section for database database_name, node node_number in profile file. |
Explanation: A required parameter was not specified in the profile. Processing is stopped.
User Response: Correct the file contents by specifying all required parameters.
DKP8940E | Error calling executable: error_information. |
Explanation: An error occurred when calling an executable.
User Response: Check the error information and respond accordingly.
DKP8941I | Return code from call to executable: return_code |
Explanation: An executable was called and completed with the return code indicated.
User Response: If the return code is not 0, this indicates that the Log File Manager could not complete the request successfully. In this case, check the log for error messages and respond to them. If the reason for a bad return code cannot be determined, save the log and contact your service representative.
DKP8942E | No output from call to executable. |
Explanation: A called executable did not generate the output expected. Possible reasons:
User Response: Check that the executable is accessible in the path.
DKP8998I | Trace file: file |
Explanation: Tracing is switched on. The trace can be found in the path indicated.
User Response: None.
DKP8999E | Internal system error. Please contact your service representative. Error information: error_information |
Explanation: An internal system error occurred.
User Response: Save the log and contact your service representative.
DKP9000E | System error: error |
Explanation: Tivoli Data Protection for WebSphere Application Server has found the following error: error. This is a 'catch-all' error code for unpredictable system errors.
User Response: Contact your service representative.
DKP9001E | Internal error: error |
Explanation: Tivoli Data Protection for WebSphere Application Server has found the following internal error: error.
User Response: Contact Tivoli Data Protection for WebSphere Application Server support.