This chapter describes the messages issued by Tivoli Data Protection for R/3 for Oracle. The messages begin with the prefix BKI and are listed in numerical order.
BKI0000E | Profile not specified. |
Explanation: Tivoli Data Protection for R/3 cannot locate the profile.
User Response: Ensure that a profile is available. Notice that the BACKINT call must have the following form: backint -p init<SID>.util....
BKI0004E | Function not defined. |
Explanation: SAPDBA, BRBACKUP, or BRARCHIVE passed an invalid argument to Tivoli Data Protection for R/3.
User Response: Ensure that you have the correct version of SAPDBA, BRBACKUP, or BRARCHIVE installed. Valid functions are: -f backup or -f restore or -f password or -f delete or -f inquire.
BKI0005I | Start of backint program at:time |
Explanation: Tivoli Data Protection for R/3 received control from SAPDBA, BRBACKUP, BRARCHIVE or BRRESTORE at time.
User Response: None
BKI0006E | Type for backup not defined [type]. Please use 'file' or 'file_online'. |
Explanation: Tivoli Data Protection for R/3 expects as backup type parameter only file or file_online.
User Response: If you start Tivoli Data Protection for R/3 manually to do a backup, ensure that the type option (-t) receives the correct arguments (file or file_online). If your Tivoli Data Protection for R/3 has been invoked by one of the SAP database utilities (e.g., BRBACKUP), ensure that the SAP backup profile init<SID>.sap is customized correctly.
BKI0020I | End of backint program at: time |
Explanation: Tivoli Data Protection for R/3 returned control to SAPDBA, BRBACKUP, BRARCHIVE, or BRRESTORE at time.
User Response: none
BKI0021I | Elapsed time: elapsedtime |
Explanation: The time needed for the complete backup was elapsedtime.
User Response: None
BKI0023I | Time: current_time
Done: saved_bytes(percent)of bytes Estimated end time: end_time |
Explanation: Tivoli Data Protection for R/3 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 R/3 call will be completed at the estimated end_time.
User Response: None
BKI0024I | Return code is: return code |
Explanation: Shows the return code of Tivoli Data Protection for R/3. 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.
BKI0027I | 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 R/3 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
BKI0030I | 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 R/3 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
BKI0031W | Object not found or not accessible: objectname. |
Explanation: The object was not found or is not accessible to Tivoli Data Protection for R/3.
User Response: Check path and name and the permissions of that object and try again.
BKI0032E | 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.
BKI0033E | Error opening file file name: system error description |
Explanation: See BKI0032E.
User Response: See BKI0032E.
BKI0049I | 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 R/3 configuration file.
User Response: Enter the password for the corresponding Tivoli Storage Manager server.
BKI0050I | 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.
BKI0051I | 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
BKI0052E | 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.
BKI0053I | Time: current_time
Objects: current_num of total_num done: file_name with: bytes saved with description object_desc. |
Explanation: Tivoli Data Protection for R/3 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
BKI0054I | Time: current_time
Objects: current_num of total_num done: file_name with: bytes restored with description object_desc. |
Explanation: Tivoli Data Protection for R/3 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
BKI0055I | Object objectname with size saved with description description. |
Explanation: The object objectname was saved successfully.
User Response: None
BKI0056I | Object objectname with size restored with description description. |
Explanation: The object objectname was restored successfully.
User Response: None
BKI0059E | 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.
BKI0060E | The parameter parameter is not known. |
Explanation: The command parameter parameter for Tivoli Data Protection for R/3 is unknown.
User Response: Check the specified command parameter and try again.
BKI0061W | 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.
BKI0062E | The input file file name is not valid. |
Explanation: Tivoli Data Protection for R/3 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.
BKI0063E | The UTL file file name is not valid. |
Explanation: Tivoli Data Protection for R/3 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.
BKI0064E | The option 'option' is unknown. |
Explanation: A Tivoli Data Protection for R/3 option is invalid or unknown.
User Response: Check the specified option(s) and try again.
BKI0065E | The argument is missing for option 'option'. |
Explanation: Every Tivoli Data Protection for R/3 option requires an argument.
User Response: Insert the missing argument and try again.
BKI0101I | Session session: Please enter 'cont' to continue or 'stop' to cancel. |
Explanation: If Tivoli Data Protection for R/3 is running in unattended mode (profile keyword BATCH), it terminates the current run if operator intervention is required.
User Response: Enter 'cont' or 'stop'.
BKI0102I | Your reply: 'reply'. |
Explanation: Tivoli Data Protection for R/3 indicates the reply you made.
User Response: None
BKI0400I | TDP is waiting for BRBACKUP |
Explanation: Tivoli Data Protection for R/3 is waiting for BRBACKUP to set a tablespace in the begin/end backup mode.
User Response: None
BKI0405I | TDP waited num_sec sec. for BRBACKUP in util_file_online communication. |
Explanation: Tivoli Data Protection for R/3 waited num_sec seconds for BRBACKUP to set a tablespace in begin/end backup mode.
User Response: None
BKI0410E | Cannot open or delete switch file 'file name'. Check permissions. |
Explanation: If Tivoli Data Protection for R/3 is not correctly installed (as the root user on UNIX or administrator group on Windows NT) then Tivoli Data Protection for R/3 is not able to open the necessary communication file to the SAP R/3 system.
User Response: Check the file permission.
BKI0411E | Maximum time waiting for BRBACKUP expired. |
Explanation: The SAP database utilities did not respond within the expected time.
User Response: Contact your R/3 administrator.
BKI0412E | BRBACKUP was not able to switch requested tablespace in BEGIN BACKUP mode. |
Explanation: Tivoli Data Protection for R/3 could not continue the backup, because BRBACKUP was not able to switch the requested tablespace in BEGIN backup mode. This is necessary for locking the tablespace.
User Response: Contact your R/3 administrator.
BKI0450I | Version 2 restore: file |
Explanation: A restore of data backed up with Tivoli Data Protection for R/3 version 2 was executed.
User Response: None
BKI0451I | This version of Tivoli Data Protection for R/3 will expire on 'date'. |
Explanation: This is a test version that will expire on 'date'.
User Response: None.
BKI0452E | This version of Tivoli Data Protection for R/3 has expired. |
Explanation: This is a test version that has expired.
User Response: Order a release version of Tivoli Data Protection for R/3 or contact your IBM/Tivoli Sales Representative.
BKI0453W | This version of Tivoli Data Protection for R/3 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 R/3 or contact your IBM/Tivoli Sales Representative before the version expires.
BKI0454I | *** This copy is NOT FOR RESALE. *** |
Explanation: This version is not for resale.
User Response: None.
BKI0455E | 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 init<SID>.utl file.
BKI0456E | Unable to access license file 'file name'. |
Explanation: Unable to access license file.
User Response: Make sure the access permissions allow read/write access.
BKI0457E | 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.
BKI1000E | Syntax error in line line: 'statement' |
Explanation: The statement statement in the Tivoli Data Protection for R/3 profile is unknown or incorrect.
User Response: Correct the error and try again.
BKI1001E | Syntax error in file 'file name'. Exiting Program. |
Explanation: Tivoli Data Protection for R/3 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.
BKI1002E | 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., SAP___, BKI___).
BKI1003W | Please set REDOLOG_COPIES to a number between 1 and max_copies. Now it is set to act_copies. |
Explanation: Tivoli Data Protection for R/3 currently supports 1 to 9 copies of offline redo log files.
User Response: Adapt the REDOLOG_COPIES settings in the Tivoli Data Protection for R/3 profile.
BKI1004W | 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 characters long BACKUPIDPREFIX in the Tivoli Data Protection for R/3 profile (e.g., SAP___, BKI___).
BKI1005W | The tracefile name 'trace_filename' should be absolute. |
Explanation: None
User Response: Specify an absolute tracefile name, for example /oracle/C21/saptrace/tracefile.
BKI1006E | 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.
BKI1007E | 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.
BKI1008E | 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.
BKI1009W | 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 R/3 now uses act_multiplex.
User Response: Set multiplexing to a number between 1 and max_multiplex.
BKI1010W | The configfile name 'configuration_filename' should be absolute. |
Explanation: None
User Response: Specify an absolute file name, for example /oracle/C21/dbs/initC21.bki.
BKI1011W | The sortfile name 'sortfile_filename' should be absolute. |
Explanation: None
User Response: Specify an absolute file name, for example /oracle/C21/dbs/sortfile.
BKI1012E | The configfilename 'configuration_filename' could not be opened. |
Explanation: Tivoli Data Protection for R/3 is unable to read the file configuration_filename.
User Response: This error could have various reasons, try the following:
BKI1013E | Profile not found or permissions denied : 'profile_filename'. |
Explanation: Tivoli Data Protection for R/3 is unable to open the profile profile_filename.
User Response: Ensure that the SAP backup profile init<SID>.sap contains a valid entry util_par_file for the Tivoli Data Protection for R/3 profile. Furthermore, this file must be readable by Tivoli Data Protection for R/3.
BKI1014I | The parameter PERF_MONITOR is no longer supported. Now it is enabled by default. |
Explanation: For version 2.7 or later of Tivoli Data Protection for R/3, the Performance Monitor of the Administration Assistant can be used by default. Therefore, the profile parameter PERF_MONITOR is no longer needed.
User Response: None
BKI1015I | The parameter BACKAGENT is no longer needed. |
Explanation: For version 2.7 or later of Tivoli Data Protection for R/3,, only one executable, called BACKINT, will be provided and needed. The former executable, called BACKAGENT, will no longer supported or needed.
User Response: None
BKI1016W | 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.
BKI1017E | 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.
BKI1200E | Can't read/write file: file name. |
Explanation: Tivoli Data Protection for R/3 is unable to read or write a datafile (file name) of a tablespace being backed up or restored.
User Response: Check the file access permission of the affected file(s). Try again. If the problem still exists, contact the SAP R/3 administrator.
BKI1201E | There are no Tivoli Storage Manager-Servers available. |
Explanation: Tivoli Data Protection for R/3 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 R/3 profile (keyword SERVER).
BKI1202E | You must specify either
MAX_SESSIONS or all off MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS and MAX_RESTORE_SESSIONS |
Explanation: There is a setup error with the SESSIONS parameters within the Tivoli Data Protection for R/3 profile.
User Response: Specify either MAX_SESSIONS and one of the more specific parameters MAX_ARCH_SESSIONS, MAX_BACK_SESSIONS or MAX_RESTORE_SESSIONS or all of the three specific session parameters without the MAX_SESSIONS parameter.
BKI1203E | Not enough sessions available (number of sessions required and number of sessions available). |
Explanation: The sum of available sessions specified in the various server statements (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 R/3 profile, so that the condition mentioned in the explanation is fulfilled.
BKI1205E | If you want num_redo REDOLOGCOPIES on Tivoli Storage Manager-Server servername, you should give me at least num_mc different Archive Management Classes. |
Explanation: Tivoli Data Protection for R/3 requires that the number of different Archive Management Classes (parameter BRARCHIVEMGTCLASS) on the Tivoli Storage Manager servers is equal to or greater than the number of redo log copies (parameter REDOLOG_COPIES).
User Response: Define at least as many different Archive Management Classes as redo log copies requested.
BKI1206W | If you want num_redo REDOLOGCOPIES on Tivoli Storage Manager-Server server name, you should give me at least num_mc different Archive Management Classes. |
Explanation: The message appears during a BRBACKUP run. A BRARCHIVE run afterwards would be failed.
User Response: Define at least as many different Archive Management Classes as redo log copies requested.
BKI1207E | Directory backup not supported |
Explanation: This option is not yet available.
User Response: Wait for a future release of Tivoli Data Protection for R/3, which supports this option.
BKI1208E | The object 'file name' will be retried [retry_num] |
Explanation: There was an error with the object file_name. Tivoli Data Protection for R/3 will try to save/restore the object one retry_num times.
User Response: Look at the error messages in the Tivoli Data Protection for R/3 protocol and solve the error for the next run.
BKI1209E | Object not found or not accessible 'objectname'. |
Explanation: Tivoli Data Protection for R/3 cannot locate the Oracle object objectname.
User Response: The backup integrity is affected. Contact the SAP or Tivoli Data Protection for R/3 support.
BKI1210E | Input file not found or not accessible 'file name'. |
Explanation: Tivoli Data Protection for R/3 cannot locate the temporary file file name. This file contains the list of Oracle objects to be backed up/restored. It is passed to Tivoli Data Protection for R/3 by BRBACKUP, BRARCHIVE or BRRESTORE.
User Response: Ensure, that you have the correct version of SAPDBA, BRBACKUP, BRARCHIVE or BRRESTORE installed.
BKI1211E | There is something wrong with your CONFIG_FILE 'file name'. |
Explanation: There is a problem with your Tivoli Data Protection for R/3 configuration file setup.
User Response: Check the file permission and the file name specified in the Tivoli Data Protection for R/3 profile keyword CONFIG_FILE.
BKI1212W | The file 'file name' was not found in the manual sorting file. |
Explanation: The file you want to back up was not found in the manual sorting file.
User Response: Check and correct the manual sorting file so that it contains all the files you are backing up.
BKI1213I | Program ended with code = 'return code' |
Explanation: The return code of the program is displayed.
User Response: None.
BKI1214E | TSM Error: 'error text' |
Explanation: The specified TSM error occurred.
User Response: Check error text and correct the problem.
BKI1215I | Average transmission rate was 'number' GB/h ('number' MB/sec). |
Explanation: The average transmission rate is displayed.
User Response: None.
BKI1216E | There are no BRBACKUPMGTCLASSES available. |
Explanation: The BRBACKUPMGTCLASSES you have specified in your init<SID>.utl file are not correct.
User Response: Check the management classes on the TSM server and specify correct ones.
BKI1217E | There are no BRARCHIVEMGTCLASSES available. |
Explanation: The BRARCHIVEMGTCLASSES you have specified in your init<SID>.utl file are not correct.
User Response: Check the management classes on the TSM server and specify correct ones.
BKI2000I | Successfully connected to PROLE on port portnumber. |
Explanation: One of the Tivoli Data Protection for R/3 modules BACKINT or the backup library libtdp_r3 initiated a successful connection to the background process Prole on port portnumber.
User Response: None
BKI2001E | Socket error while connecting to PROLE: reason. |
Explanation: The Tivoli Data Protection for R/3 background process Prole is not running.
User Response: Start Prole manually and try again.
BKI2002E | No valid callback function of type fkt_type supplied. |
Explanation: Internal Tivoli Data Protection for R/3 error
User Response: Contact the Tivoli Data Protection for R/3 support.
BKI2003I | 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
BKI2004E | Connection to PROLE lost. |
Explanation: During Tivoli Data Protection for R/3 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.
BKI2005E | Illegal parameter in message from Prole. Exiting... |
Explanation: This error occurs if the version of Prole and of the executable BACKINT or the backup library libtdp_r3 does not match.
User Response: Check the version of Prole and BACKINT/backup library libtdp_r3 you are currently using.
BKI2006E | General exception in dispatcher. Exiting... |
Explanation: Internal Tivoli Data Protection for R/3 error.
User Response: Contact the Tivoli Data Protection for R/3 support.
BKI2007E | Unknown Port: port |
Explanation: The port specified for the communication between Prole and Backint is unknown.
User Response: Check the port value specified when Prole was started. Additionally, check the environment variable PROLE_PORT for the Backint environment. These two values must match.
BKI2008E | Unable to connect to PROLE. |
Explanation: Internal Tivoli Data Protection for R/3 error.
User Response: Contact the Tivoli Data Protection for R/3 support.
BKI2009I | 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
BKI2010E | 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 R/3 profile (keyword FRONTEND) and try again.
BKI2011E | 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 R/3 profile (keyword BACKEND) and try again.
BKI2012E | Passwords do not match. Try again. |
Explanation: The first and second password you entered do not match.
User Response: Enter the password correctly.
BKI2013I | Starting FRONTEND Program. |
Explanation: The frontend program is executing.
User Response: None
BKI2014I | FRONTEND program finished. |
Explanation: The frontend program is finished.
User Response: None
BKI2015I | Starting BACKEND program. |
Explanation: The backend program is executing.
User Response: None
BKI2016I | BACKEND program finished. |
Explanation: The backend program is finished.
User Response: None
BKI2017I | Blocksize is set to num_bytes bytes. |
Explanation: The operational blocksize of Tivoli Data Protection for R/3 is num_bytes bytes.
User Response: None
BKI2018E | 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.
BKI2019E | 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.
BKI2020E | 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.
BKI2021E | 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.
BKI2022E | 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.
BKI2023E | 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.
BKI4000W | 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.
BKI4001E | 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.
BKI4002E | 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.
BKI4003E | 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 please contact the Tivoli Data Protection for R/3 support.
BKI4004E | 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 please contact the Tivoli Data Protection for R/3 support.
BKI4005E | Error allocating memory block for file file name. BLOCKSIZE may be too large. |
Explanation: Tivoli Data Protection for R/3 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 R/3.
BKI4006E | Error allocating memory block for file file name. BLOCKSIZE may be too large. |
Explanation: See BKI4005E.
User Response: See BKI4005E.
BKI5000E | Tivoli Storage Manager Error: error_message |
Explanation: During a connection of Tivoli Data Protection for R/3 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.
BKI5001E | Tivoli Storage Manager Error: error_message |
Explanation: See BKI5000E.
User Response: See BKI5000E.
BKI5002E | Tivoli Storage Manager Error: error_message |
Explanation: See BKI5000E.
User Response: See BKI5000E.
BKI5003E | Tivoli Storage Manager Error: error_message |
Explanation: See BKI5000E.
User Response: See BKI5000E.
BKI5004E | Tivoli Storage Manager Error: error_message |
Explanation: See BKI5000E.
User Response: See BKI5000E.
BKI5005E | Tivoli Storage Manager Error: error_message |
Explanation: See BKI5000E.
User Response: See BKI5000E.
BKI5006E | Tivoli Storage Manager Error: error_message |
Explanation: See BKI5000E.
User Response: See BKI5000E.
BKI5007E | Tivoli Storage Manager Error: error_message |
Explanation: See BKI5000E.
User Response: See BKI5000E.
BKI5008E | Tivoli Storage Manager Error: error_message |
Explanation: See BKI5000E.
User Response: See BKI5000E.
BKI5009E | Tivoli Storage Manager Error: error_message |
Explanation: See BKI5000E.
User Response: See BKI5000E.
BKI5010E | Tivoli Storage Manager Error: error_message |
Explanation: See BKI5000E.
User Response: See BKI5000E.
BKI5011E | Tivoli Storage Manager Error: error_message |
Explanation: See BKI5000E.
User Response: See BKI5000E.
BKI7001E | Backup file 'file name' already exists. |
Explanation: This is an RMAN internal error.
User Response: See your Oracle documentation or contact your Oracle database administrator.
BKI7002E | Bad mode specified. |
Explanation: This is an RMAN internal error.
User Response: See your Oracle documentation or contact your Oracle database administrator.
BKI7009E | Cannot connect to media manager. |
Explanation: Tivoli Data Protection for R/3 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.
BKI7010E | 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.
BKI7012E | Invalid arguments during call of 'function'. |
Explanation: This is an RMAN internal error.
User Response: See your Oracle documentation or contact your Oracle database administrator.
BKI7020E | Bad handle 'rman_handle' during call of 'function'. |
Explanation: This is an RMAN internal error.
User Response: See your Oracle documentation or contact your Oracle database administrator.
BKI7021E | Bad flags during call of 'function'. |
Explanation: This is an RMAN internal error.
User Response: See your Oracle documentation or contact your Oracle database administrator.
BKI9000E | System error: error |
Explanation: Tivoli Data Protection for R/3 has found the following error: error. This is a 'catch_all' error code for unpredictable system errors.
User Response: Contact your system representative.
BKI9001E | Internal error: error |
Explanation: Tivoli Data Protection for R/3 has found the following internal error: error.
User Response: Contact the Tivoli Data Protection for R/3 support.